Active Topics
-
[HOWTO] Comprehensive Firmware Flashing Guide for N9 (1,580)
to Nokia N9 / N950 by aspergerguy - 9 hrs, 48 mins ago -
Nokia N9-00 Prototype Build S1.12 (RM-680 codename "Dali") (250)
to Nokia N9 / N950 by en0s - 3 days, 6 hrs ago -
[Announce] Maebble - Pebble support for Maemo (118)
to Applications by glo-worm - 3 days, 18 hrs ago -
Possible to flash Leste to eMMC? (6)
to Maemo 7 / Leste by Eri - 4 days, 8 hrs ago - more...
|
nieldk
|
2013-12-31
, 14:42
|
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#81
|
the restore most likely worked at least to be able to fastboot - to get a command prompt. The question now is, what was done when having command prompt?
|
|
2013-12-31
, 14:46
|
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#82
|
if you try what was posted in
http://talk.maemo.org/showpost.php?p...4&postcount=54
then
ifconfig eth1 192.168.42.18 netmask 255.25.255.0 up
telnet 192.168.42.17
you should be at coomand prompt and perhaps stskeep can help from there?
http://talk.maemo.org/showpost.php?p...4&postcount=54
then
ifconfig eth1 192.168.42.18 netmask 255.25.255.0 up
telnet 192.168.42.17
you should be at coomand prompt and perhaps stskeep can help from there?
|
2013-12-31
, 14:50
|
|
Posts: 46 |
Thanked: 11 times |
Joined on Jun 2013
|
#83
|
after fastboot it says <waiting for device>
meanwhile I emailed the jolla care
meanwhile I emailed the jolla care
|
|
2013-12-31
, 14:54
|
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#84
|
did you
1 power off device
2 hold vol down (keep holding)
3. plug in usb cable
1 power off device
2 hold vol down (keep holding)
3. plug in usb cable
|
|
2013-12-31
, 14:59
|
|
Posts: 46 |
Thanked: 11 times |
Joined on Jun 2013
|
#85
|
if i do this way the phone displays fastboot mode, manufacturer and product
then sudo ifconfig -a
doesn't show eth1 as an option
and fastboots output is: FAILED (remote: access denied. need privilege!)
if i
1 shut down
2 hold volume down
3 press power on
4 plug the usb
it displays only the jolla logo and
sudo ifconfig -a
shows eth1 too
after fastboot it says <waiting for device>
then sudo ifconfig -a
doesn't show eth1 as an option
and fastboots output is: FAILED (remote: access denied. need privilege!)
if i
1 shut down
2 hold volume down
3 press power on
4 plug the usb
it displays only the jolla logo and
sudo ifconfig -a
shows eth1 too
after fastboot it says <waiting for device>
| The Following User Says Thank You to ZioBilly For This Useful Post: | ||
|
|
2013-12-31
, 15:04
|
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#86
|
then you still have the locked bootloader. which cant do a good reset in your case (what we tried before).
I think now unfortunately your only option is Jolla Care
I think now unfortunately your only option is Jolla Care
|
|
2014-01-09
, 23:23
|
|
Posts: 193 |
Thanked: 348 times |
Joined on Dec 2009
|
#87
|
Anyway to do this on a windows machine?
 |
|
2014-01-10
, 07:52
|
|
Posts: 1,671 |
Thanked: 11,478 times |
Joined on Jun 2008
@ Warsaw, Poland
|
#88
|
Originally Posted by wormdrummer
From XDA developers of all places:
Anyway to do this on a windows machine?
Dude, go to your device manager.
Find the Device with the little ? and then maybe a yellow !.
Right click that device and select Update Driver.
When the window pops up (on Windows 7 32bit), select, Browse My Computer for driver software, then on the next screen, click on the bottom that says, LET ME PICK.
Then it will ask you the device type.
Here you go down to Network Adapters.
Then when it asks you to select manufacturer, skip Microsoft and select Microsoft Corporation.
Then, select Remote NDIS based Internet Sharing Device.
Hit next, it will say it's not safe, etc etc, proceed to install it.
You should be set. I hope that helps.
| The Following 3 Users Say Thank You to Stskeeps For This Useful Post: | ||
|
|
2014-01-15
, 19:27
|
|
Posts: 2 |
Thanked: 0 times |
Joined on Jan 2014
@ Norway
|
#89
|
Long story short:
My jolla phone started acting a bit strangely so i decided to restore it to factory settings. it "never" finished ( i waited about an hour) and i pulled the battery ( thinking i am a complete ***** ). restarted the phone. And BootLoop.
I then started the recovery trough telnet and after six hours it had restored the / and /home images but was "hanging" on:
[CLEANUP] Umounting /mnt
I have now booted the image provided in this thread and tried mounting /dev/mmcblk0p28.
it doesn't take long for ls to "hang" and a quick inspection with top
reveals that 50% CPU [btrfs-cache-1]
A quick google search provides this: https://bugs.launchpad.net/ubuntu/+s...s/+bug/1088986
so anyone have any idea what i can do to recover my device?
I emailed care 3 days ago. But they probably have there hands full.
And it would be great to not send the phone back to Jolla.
Thanks in advance.
My jolla phone started acting a bit strangely so i decided to restore it to factory settings. it "never" finished ( i waited about an hour) and i pulled the battery ( thinking i am a complete ***** ). restarted the phone. And BootLoop.
I then started the recovery trough telnet and after six hours it had restored the / and /home images but was "hanging" on:
[CLEANUP] Umounting /mnt
I have now booted the image provided in this thread and tried mounting /dev/mmcblk0p28.
it doesn't take long for ls to "hang" and a quick inspection with top
reveals that 50% CPU [btrfs-cache-1]
A quick google search provides this: https://bugs.launchpad.net/ubuntu/+s...s/+bug/1088986
so anyone have any idea what i can do to recover my device?
I emailed care 3 days ago. But they probably have there hands full.
And it would be great to not send the phone back to Jolla.
Thanks in advance.
|
|
2014-01-16
, 08:22
|
|
Posts: 2 |
Thanked: 0 times |
Joined on Jan 2014
@ Norway
|
#90
|
update:
After a couple of hours the btrfs-cache-1 probably got done with whatever it was doing. and i could unmount the root filesystem cleanly. I started the recovery process one more time and this time it completed after about an hour. still boot loop though..
After a couple of hours the btrfs-cache-1 probably got done with whatever it was doing. and i could unmount the root filesystem cleanly. I started the recovery process one more time and this time it completed after about an hour. still boot loop though..