So, I have read several threads and feel that a solution is there, but I just can't seem to find the detailed instructions on how to fix it. Apologies if I have missed it and you can direct me to that one.
I have tried the xperia companion software recovery and the software update two different times. Both times they said it was successful. However, the watch would still get stuck on the 4 symbols or dots.
I tried doing the factory reset on the watch itself, but that did not help the booting process.
When I press the recovery, I get the android guy laying down with a red exclamation mark in a red triangle.
It appears that fixing it can not be done on win 10, but I do have access to a pc with ubuntu/linux that I have used.
Since I'm getting the red triangle, I'm guessing the OS is corrupt.
Any detailed instructions or pointing me to a proper thread would be appreciated.
That's a bootloop.
In recovery: swipe the guy away (from top to bottom works best). Then you should see the menu.
ranf said:
That's a bootloop.
In recovery: swipe the guy away (from top to bottom works best). Then you should see the menu.
Click to expand...
Click to collapse
Hey, thanks. So, I see the menu. I did the wipe data factory refresh and still nothing except the 4 symbols grinding away.
So, is see a "mount" option. I'm guessing that is where the watch is then mounted as a drive to a pc where where one could have files transferred from the pc to the watch. Would that be the next step or do I need to perform the partition option on the watch?
Sorry, I just am trying to get detailed instructions. BTW, I did notice that the OS is 6.0.1. I have read that many have downgraded to 5.1.1 as it may have been better for gps and battery life. Also, that is when this watch crashed was during the update.
Any detailed instructions from here would be greatly appreciated...again. Thanks
When a factory reset doesn't help it, the easiest way is the "repair" option in Xperia Companion. Basically it downloads the complete firmware (200-250MB) and flashes all the partitions. Very much like a factory image for a Nexus.
I don't know what mount actually does.
ranf said:
When a factory reset doesn't help it, the easiest way is the "repair" option in Xperia Companion. Basically it downloads the complete firmware (200-250MB) and flashes all the partitions. Very much like a factory image for a Nexus.
I don't know what mount actually does.
Click to expand...
Click to collapse
Thanks. As mentioned in the original post, that was tried...now three times to no avail. I did both options in the repair area of xperia. So, I'm guessing there is a more serious hardware issue or I need to somehow use something other than the xperia companion to remedy the situation. I had also tried the update again and it said it was successful, but there was not difference in the behavior of the watch...just the 4 dots/symbols going on forever.
I'm willing to root the device, but I just have not seen or probably better stated, understood how to do it. I am sort of a newbie and thus need detailed instructions. If the watch is bricked after that, then so be it. It is not doing any good right now anyways. Can some even point me to such a thing or help in writing it down?
Perhaps a stupid question, but after doing the repair thru xperia, I let it sit and grind for a good 20 minutes. I presume that is ample time for it to repair itself. Is that reasonable?
Repair is not the same as update in XC.
ranf said:
Repair is not the same as update in XC.
Click to expand...
Click to collapse
Thanks. Agree which is why I mentioned both the repair and the update were done on the watch and of course separately on XC.
So, basically, I have tried every option in xperian companion (repair and update) and the factory reset, clear cache and the partition option that come up on the watch itself. So, my next thougt was the to root it and try either downgrading the os or repairing in thru the root process. If someone could provide either a link or help with very detailed directions (for the complete idiot) on how to root it with that idea of replacing or repairing the os, that would be very much appreciated.
golfnut22 said:
Thanks. Agree which is why I mentioned both the repair and the update were done on the watch and of course separately on XC.
Click to expand...
Click to collapse
That wasn't so clear for me.
golfnut22 said:
So, basically, I have tried every option in xperian companion (repair and update) and the factory reset, clear cache and the partition option that come up on the watch itself. So, my next thougt was the to root it and try either downgrading the os or repairing in thru the root process. If someone could provide either a link or help with very detailed directions (for the complete idiot) on how to root it with that idea of replacing or repairing the os, that would be very much appreciated.
Click to expand...
Click to collapse
You can install this (Lollipop):
http://forum.xda-developers.com/smartwatch-3/orig-development/rom-sony-smartwatch-3-rom-t3367728
or this (Marshmallow):
http://forum.xda-developers.com/sma...sony-smartwatch-3-marshmallow-mec24h-t3382450
In Ubuntu you install fastboot this way:
Code:
sudo apt-get install android-tools-fastboot
You may want to create an udev rule, so that a normal user can access the watch in fastboot mode:
https://ranf.wordpress.com/2015/02/21/ubuntu-udev-rule-for-sony-smartwatch-3-swr50/
Otherwise you have to run fastboot with sudo.
I'd start with formatting cache and userdata:
1. get into recovery
2. from there get into fastboot (maybe it is called bootloader here, can't remember)
3. check connection
Code:
fastboot devices -l
4. format
Code:
fastboot format cache
fastboot format userdata
fastboot reboot
---------- Post added at 06:10 PM ---------- Previous post was at 06:07 PM ----------
golfnut22 said:
Since I'm getting the red triangle, I'm guessing the OS is corrupt.
Click to expand...
Click to collapse
Can you post a photo of that?
ranf said:
That wasn't so clear for me.
You can install this (Lollipop):
http://forum.xda-developers.com/smartwatch-3/orig-development/rom-sony-smartwatch-3-rom-t3367728
or this (Marshmallow):
http://forum.xda-developers.com/sma...sony-smartwatch-3-marshmallow-mec24h-t3382450
In Ubuntu you install fastboot this way:
Code:
sudo apt-get install android-tools-fastboot
You may want to create an udev rule, so that a normal user can access the watch in fastboot mode:
https://ranf.wordpress.com/2015/02/21/ubuntu-udev-rule-for-sony-smartwatch-3-swr50/
Otherwise you have to run fastboot with sudo.
I'd start with formatting cache and userdata:
1. get into recovery
2. from there get into fastboot (maybe it is called bootloader here, can't remember)
3. check connection
Code:
fastboot devices -l
4. format
Code:
fastboot format cache
fastboot format userdata
fastboot reboot
---------- Post added at 06:10 PM ---------- Previous post was at 06:07 PM ----------
Can you post a photo of that?
Click to expand...
Click to collapse
Thank you. And, sorry for the senior memory moment. I could not remember if it was recovery or repair in XC. Anyway, I think it is fair to say that I have tried every "canned" option in either XC or on the watch for recovery, repair and update to no avail.
Nice and thanks for the coding. I will also take a hard look at the links to see if I can proceed. When I fixed my HP Touchpad, there was a nice little toolbox that one could use to easily do a complete data reset, then load the three files and it would do the rest. That was all done in Ubuntu.
I'll report back once I get going.
Is it fair to say that as long as you do not mess with the bootloader, that you cannot brick the watch? After reading 12 or 13 threads, that seemed to be one of the comments. I did look at all the thread titles...17 pages to try and find things that were similar and they pointed to what we have already discussed in using XC, etc. So, I'll try another way that is outlined above.
I have attached the picture of the android guy with exclamation mark. Hopefully you will be able to see it.
golfnut22 said:
Thank you. And, sorry for the senior memory moment. I could not remember if it was recovery or repair in XC. Anyway, I think it is fair to say that I have tried every "canned" option in either XC or on the watch for recovery, repair and update to no avail.
Nice and thanks for the coding. I will also take a hard look at the links to see if I can proceed. When I fixed my HP Touchpad, there was a nice little toolbox that one could use to easily do a complete data reset, then load the three files and it would do the rest. That was all done in Ubuntu.
I'll report back once I get going.
Click to expand...
Click to collapse
Yes please do so.
golfnut22 said:
Is it fair to say that as long as you do not mess with the bootloader, that you cannot brick the watch?
Click to expand...
Click to collapse
You can play a lot with the watch without bricking. Doesn't mean it's impossible.
golfnut22 said:
After reading 12 or 13 threads, that seemed to be one of the comments. I did look at all the thread titles...17 pages to try and find things that were similar and they pointed to what we have already discussed in using XC, etc. So, I'll try another way that is outlined above.
I have attached the picture of the android guy with exclamation mark. Hopefully you will be able to see it.
Click to expand...
Click to collapse
A bit small but that's just the recovery droid?
To me that means more like "proceed with caution" than denoting a serious error condition.
ranf said:
That wasn't so clear for me.
or this (Marshmallow):
http://forum.xda-developers.com/sma...sony-smartwatch-3-marshmallow-mec24h-t3382450
Ok, so I downloaded 4 files. 2 of them were for two different cores: one was for 2 core and the other for 4 cores. Which one is proper or what's the difference for this watch?
In Ubuntu you install fastboot this way:
Code:
sudo apt-get install android-tools-fastboot
Yes, got it and that was easy.
You may want to create an udev rule, so that a normal user can access the watch in fastboot mode:
https://ranf.wordpress.com/2015/02/21/ubuntu-udev-rule-for-sony-smartwatch-3-swr50/
I tried the first command on the link two different times and I get vim: command not found. So I continued on.
Otherwise you have to run fastboot with sudo.
I'd start with formatting cache and userdata:
1. get into recovery
If this procedure is done on the watch by holding the power button until you get the "insert usb" connection screen, then quickly tapping the power button twice to bring up the next four screens possible screens by pressing the power button 1 time to move to the next screen (fastboot, recovery, normal boot, factory reset), I went into the recovery screen and did the wipe cache partition first and then the wipe data/factory refresh.
However, if those steps above are to be done on the ubuntu, then I'm lost already.
2. from there get into fastboot (maybe it is called bootloader here, can't remember)
If this is to see fastboot on the watch as one of the 4 screens noted above, that is easy. If it is to double press the power button while on the fastboot screen, I did that, but don't know what you mean by the next step..."check connection"
3. check connection
Code:
fastboot devices -l
4. format
Code:
fastboot format cache
fastboot format userdata
fastboot reboot
So assuming that I can eventually get thru step 4, how and do I get the watch to recognize or get the 3 files (assuming I do not need both the 2 and 4 core files)?
---------- Post added at 06:10 PM ---------- Previous post was at 06:07 PM ----------
Can you post a photo of that?
Click to expand...
Click to collapse
So, in the "previewing of my response or comments based on the instructions, it looks like I did not do the "multi-quote" correctly. I hope you can decipher what I said, as I have commented on the steps so far in your comment back to me and what I was able to do and not do at this point. I would appreciate any help you can further offer.
I went thru the whole process again or at least starting with the command "sudo -s". I got thru it all except when I tried to install the rom file with the signature check box checked, it failed. The first time I did it, I did not check the box, but when rebooting as noted above is just cycled thru twice then went to the android recovery guy.
"vim" is an editor. You can use any other (like nano or even gedit).
with "fastboot devices -l" you either get "offline" which means the udev rule doesn't work,
or you get an output starting with fastboot.
Most likely much easier:
Code:
sudo -s
fastboot devices -l
fastboot format cache
fastboot format userdata
fastboot reboot
exit
ranf said:
"vim" is an editor. You can use any other (like nano or even gedit).
with "fastboot devices -l" you either get "offline" which means the udev rule doesn't work,
or you get an output starting with fastboot.
Most likely much easier:
Code:
sudo -s
fastboot devices -l
fastboot format cache
fastboot format userdata
fastboot reboot
exit
Click to expand...
Click to collapse
OK, so not sure what the editor comment fix is, but I'll look into that later.
So, as mentioned I was able to get fastboot on the pc. However, the first time I entered "fastboot devices -1", it said waiting for device.
This morning when I read your new message, I did the sudo command to get fastboot again on the pc (I had already got the watch "running fastboot" per its screen), then entered "fastboot devices -1", and I get "invalid option -- '1'.
Also, after entering the first command "sudo -s", the next command line changed with the first word "root" and the end on the command line changed from ":~$" to ":~#".
golfnut22 said:
OK, so not sure what the editor comment fix is, but I'll look into that later.
So, as mentioned I was able to get fastboot on the pc. However, the first time I entered "fastboot devices -1", it said waiting for device.
This morning when I read your new message, I did the sudo command to get fastboot again on the pc (I had already got the watch "running fastboot" per its screen), then entered "fastboot devices -1", and I get "invalid option -- '1'.
Click to expand...
Click to collapse
That's a lowercase L (for longer output).
ranf said:
That's a lowercase L (for longer output).
Click to expand...
Click to collapse
I got vim working or at least loaded.
Yep, was using number 1 instead of small letter l. Thanks.
I ran thru the commands and on the writing cache at the end, it said "Failed (remote: Device locked)" . The same failure message was on the userdata command at the end. What should I do next
Edit: I found where you have to start with command "fastboot oem unlock" and enter it twice. Now I was able to wipe cache and userdata.
After performing the above fastboot commands and disconnecting watch. I powered up the watch and it is still cycling thru or stuck on the 4 dots or symbols. Sooooo,
I hate to keep asking, but is it correct to say I now need to repair/replace/update the OS? And if so, I'm not sure exactly how to do that. Can you advse?
Here I think are the next steps: (this was copied from your link above for MM)
Quote:
Installation:
Put ROM to your virtual SDCard
I don't know how to do this first step. Can you advise?
Boot into TWRP recovery
I don't know how to put TWRP on the watch unless it is part of the first step. Can you advise?
Select "Install", and choose ROM zip file
This appears easy after the step 1 and 2 above are complete.
After installation completed- reboot watch
If necessary - make full wipe
Quote:
Downloads
MWD49B
How would I know this is my watch? I have seen several different ones for the SW3.
I have downloaded all of the below files, but there are two that are similar. One is 4 cores and the other is for 2 cores. Do you know which one I should use or what the differences would be?
SWR50_6.0.1_MWD49B.zip v3
MEC24H
SWR50_6.0.1_MEC24H v2 (4 cores version)
SWR50_6.0.1_MEC24H v2 (2 cores version)
Recovery
TWRP recovery
1. boot TWRP: if it is a .zip unzip it. If it already is an .img file proceed.
2. sudo fastboot boot twrp.img
We don't install, only boot into it temporarily.
3. I usually see a new Nautilus (ubu filemanager) window pop up on my Ubuntu box (because MTP is enabled in TWRP)
4. you could now drag and drop the ROM.zip you want into that window.
5. now on the watch in TWRP select install
MWDxx MECxx are the build numbers. MWDxx being the newest.
2 or 4 cores doesn't make much of difference. The stock Sony kernel disables 2 cores (for powersaving reasons I suppose).
---------- Post added at 04:21 PM ---------- Previous post was at 04:18 PM ----------
golfnut22 said:
Also, after entering the first command "sudo -s", the next command line changed with the first word "root" and the end on the command line changed from ":~$" to ":~#".
Click to expand...
Click to collapse
You ran a root shell. The prompt shows this with a #.
ranf said:
That wasn't so clear for me.
You can install this (Lollipop):
http://forum.xda-developers.com/smartwatch-3/orig-development/rom-sony-smartwatch-3-rom-t3367728
or this (Marshmallow):
http://forum.xda-developers.com/sma...sony-smartwatch-3-marshmallow-mec24h-t3382450
In Ubuntu you install fastboot this way:
Code:
sudo apt-get install android-tools-fastboot
You may want to create an udev rule, so that a normal user can access the watch in fastboot mode:
https://ranf.wordpress.com/2015/02/21/ubuntu-udev-rule-for-sony-smartwatch-3-swr50/
Otherwise you have to run fastboot with sudo.
I'd start with formatting cache and userdata:
1. get into recovery
2. from there get into fastboot (maybe it is called bootloader here, can't remember)
3. check connection
Code:
fastboot devices -l
4. format
Code:
fastboot format cache
fastboot format userdata
fastboot reboot
---------- Post added at 06:10 PM ---------- Previous post was at 06:07 PM ----------
Can you post a photo of that?
Click to expand...
Click to collapse
ranf said:
1. boot TWRP: if it is a .zip unzip it. If it already is an .img file proceed.
2. sudo fastboot boot twrp.img
We don't install, only boot into it temporarily.
3. I usually see a new Nautilus (ubu filemanager) window pop up on my Ubuntu box (because MTP is enabled in TWRP)
4. you could now drag and drop the ROM.zip you want into that window.
5. now on the watch in TWRP select install
MWDxx MECxx are the build numbers. MWDxx being the newest.
2 or 4 cores doesn't make much of difference. The stock Sony kernel disables 2 cores (for powersaving reasons I suppose).
---------- Post added at 04:21 PM ---------- Previous post was at 04:18 PM ----------
You ran a root shell. The prompt shows this with a #.
Click to expand...
Click to collapse
Again, thank you for being very patient with some very basic questions. Ok, so I think I'm getting close. However, here are more basic questions before proceeding.
1. The watch has been disconnected since the previous steps where I wiped cache and userdata and exited fastboot. I also used XC to see if it would repair and update. To my surprise, now both of those functions failed. Do I need to start all over with the "sudo -s" command and proceed to make sure? If not, where would I start?
2. What status is the watch in when I do your #2 instruction? Is it in the connect usb screen or in fastboot. I'm guessing fastboot.
3. The file I have downloaded is the img file. On your #2 instruction, in Ubuntu, where should the img file be located when I enter "sudo fastboot boot twrp.img". I'm guessing the desktop, but wanted to make sure.
4. After your step #4 of dragging the file, do I need to exit out of Linux fastboot, then disconnect the watch, then power down then up the watch to see "install" in TWRP?
2. yes "fastboot running"
3. my Downloads land in ~/Downloads.
just run
Code:
cd
cd Downloads
to go there and fastboot boot from there. If it's in ~/Desktop well then go there.
4. stay in TWRP
Twrp screen is on the watch.
However,on the pc, I did not get the new file manager to place the new rom zip file. So, I'm not sure where or how to get the zipped file in the "install" folder. Any ideas? Thanks.
With TWRP visibly on the watch now, at the same time, can I use the command in ubuntu "sudo adb sideload <rom.zip>? I've been trying to find ways to get the rom.zip file in the watch...although I have not tried anything yet.
golfnut22 said:
Twrp screen is on the watch.
However,on the pc, I did not get the new file manager to place the new rom zip file. So, I'm not sure where or how to get the zipped file in the "install" folder. Any ideas? Thanks.
Click to expand...
Click to collapse
Ideas? Always.
AFAIK you can adb into a running TWRP.
Try this:
Code:
sudo apt-get install android-tools-adb
adb devices -l
# if you "see" your watch
adb push ROMfilename.zip /sdcard/
Oh BTW: what's your Ubuntu version?
Code:
lsb_release -a
is telling you that.
Related
How To Re-Flash Stock Image
Assuming you have ADB and everything setup already....
1. I just did this for practice. I did not need to do it –but I wanted to do it successfully before I “needed” to do it. I thought I would expand a little on the process and make it a little more noob friendly.
2. Getting started.
a. Read through the entire set of instructions first.
b. I am not responsible if you BORK your phone. I BORKED mine using someone else’s instructions and tried to write a very detailed step-by-step to help others out– but it is completely possible I have also made some small error in the instructions.
3. This will completely wipe your phone – including the SD partition – so transfer any files you need before you do this.
4. This will not re-lock your bootloader. It will remain unlocked.
5. Syntax (spelling, spaces, periods, dashes, CAPITOL, or lower case) matters. There were some spelling errors and file extensions left off the commands – and that will not work.
6.I used the file…
mysid-icl53f-factory-65895fa8.tgz
…which is 4.0.2 for the cdma/lte galaxy nexus [code name = toro/mysid]. The file is located here...
http://www.google.co...NiI9yTxKdUyW1tA
7. Unzip the file (I used 7.zip to do this).
Then you will have a .tar file…
mysid-icl53f-factory-65895fa8.tar
8. Unzip that file and you should end up with a folder…
mysid-icl53f
Inside that folder you will have five files…
i. bootloader-toro-primekk15.img
ii. flash-all.sh
iii. radio-cdma-toro-i515.ek05.img
iv. radio-toro-i515.ek02.img
v. image-mysid-icl53f.zip
Do not unzip “image-mysid-icl53f.zip”
9. Go ahead and copy and paste all these files to your directory…
/android/platform-tools
(or whatever directory you work from. You do not need the “flash-all.sh” so you do not have to copy it).
10. Open the Command Prompt in the directory where you have placed the necessary files by navigating to the directory, pressing shift, and then right mouse click (normally “C: /android/tools” or C: /android/platform-tools). This will bring up the dialogue box and you can select “open a command window here”.
11. Then enter the command…
adb devices
[…this should return your serial number…]
12. enter the command…
adb reboot-bootloader
[wait for bootloader – you should here 2 alert sounds – not just 1]
13. enter the command…
fastboot flash bootloader bootloader-toro-primekk15.img
14. enter the command…
fastboot reboot-bootloader
[wait]
15. enter the command…
fastboot flash radio radio-toro-i515.ek02.img
16. enter the command…
fastboot reboot-bootloader
[wait]
17. enter the command…
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
18. enter the command…
fastboot reboot-bootloader
19. enter the command…
fastboot -w update image-mysid-icl53f.zip
20. So you know, steps 17 (flashing the cdma radio) and step 19 (flashing the update image) took longer than the rest so don't freak out - just be patient. If you did the steps in the proper order after entering the last command your phone should reboot on its own and be completely “fresh”. If you made mistakes (like I did the first time) and flashed the radios out of order (like I did) or did not wait long enough for an “Okay” dialogue (like I did) then when you reboot you will have no signal and no phone number and you will have to go through the process again and do it right (like I did).
Hope this helps someone.
Credit goes to JW at that other site for the fastboot commands. I just added detail for the write up.
Great guide, but what if the serial number doesn't show up?
Thank you for the excellent walkthrough. I am following it, but when I enter "adb devices" at the command prompt I receive "list of devices attached" but no serial number. Also, my Nexus displays: "Fastboot Command Read Error -2147483647". I did a battery pull after getting stuck in a bootloop, and am trying to recover. I can unlock and relock the bootloader, but that is the only command that is working.
Ominous39061 said:
Thank you for the excellent walkthrough. I am following it, but when I enter "adb devices" at the command prompt I receive "list of devices attached" but no serial number. Also, my Nexus displays: "Fastboot Command Read Error -2147483647". I did a battery pull after getting stuck in a bootloop, and am trying to recover. I can unlock and relock the bootloader, but that is the only command that is working.
Click to expand...
Click to collapse
if it does not return a serial number than the phone is not being recognized. I believe that there are 2 different sets of drivers that are needed. Let me look for the link and info.
the fact that it returns "list of devices attached" but no number means that it is not finding your device which means it is probably a driver issue. let me see what I can come up with. But I am no expert at any of this.
Ok - so I just did some testing of my own. I ran into the same problem as you. And I know that I have the drivers installed. So what I did was try and "shut down" any thing that could interfere with with ADB/Fastboot.
Any tethering apps that you may have - PDA NET, Easy Tether, etc, could possibly do this. Also - when you plug your phone in - and the Auto Play options pop up for FTP (File Transfer Protocol) - X out of that.
I initially plugged in my phone. Opened the command prompt in my platform-tools folder. typed in...
adb devices
...and I got the same message as you. I then "turned off" everything that could be causing problems with the process. I unplugged the phone and replugged it in (and closed the dialog box again) and then re-opened the command prompt and entered...
adb devices
...and then I got the proper return message.
thepolishguy said:
Ok - so I just did some testing of my own. I ran into the same problem as you. And I know that I have the drivers installed. So what I did was try and "shut down" any thing that could interfere with with ADB/Fastboot.
Any tethering apps that you may have - PDA NET, Easy Tether, etc, could possibly do this. Also - when you plug your phone in - and the Auto Play options pop up for FTP (File Transfer Protocol) - X out of that.
I initially plugged in my phone. Opened the command prompt in my platform-tools folder. typed in...
adb devices
...and I got the same message as you. I then "turned off" everything that could be causing problems with the process. I unplugged the phone and replugged it in (and closed the dialog box again) and then re-opened the command prompt and entered...
adb devices
...and then I got the proper return message.
Click to expand...
Click to collapse
I got the same problem with mine i dont have anything like pda net installed but nothing i have tried is able to get adb to list my phone
Getting the same issue myself...help!
Thank you so much I'm a total noob with this stuff but your guide was very helpful!
Noev said:
I got the same problem with mine i dont have anything like pda net installed but nothing i have tried is able to get adb to list my phone
Click to expand...
Click to collapse
ChuckTu said:
Getting the same issue myself...help!
Click to expand...
Click to collapse
Ok - so another member posted this...
ADB/Naked Drivers
...and I have heard some people say that it was very helpful. So hopefully this will help you guys to get your devices recognized.
Then there is also this thread and the OP said this...
Code:
On your windows PC. Use the root guide by bman
( [url]http://rootzwiki.com...nlock-and-root/[/url] )
and download the third option for drivers. Extract all
of these tho wherever you have your fast boot
( for me it was c:/users/thatmayh3mguy/) then run
fastboot in the cmd. The adbapi.DLL file will be there
and will make the fast boot work. I didn't have the sdk
installed ( fresh install of win 7 ultimate last week and
don't have it all set up yet) and it worked
thread...
adb help/getting your drivers installed correctly
OK - here is also another method that I found. I have PDA Net installed and I did not have any issues with fastboot. Here are some instructions that say the drivers that PDA Net use are the same drivers that you need for fastboot. So here is a link to the thread and hopefully one of these methods is going to work for you.
Installing PDA Net to solve your fastboot problems
ah ha - just read something else that I should have thought of...
If your phone is already in bootloader - the command...
adb devices
...will not work. so if you are in bootloader you should try the command...
fastboot devices
...instead and see if that returns anything for you.
just wanted to jump back in hear and say i was able to get mine working again. adb was allowing me to lock/unlock the bootloader i toggled that on and off then when i went to boot my phone it took a long time to boot but finally did. Thanks for all the help was in a real jam there for a minute. I used the naked adb drivers posted above not sure if that did anything but it worked for me. Thanks again!
Noev said:
just wanted to jump back in hear and say i was able to get mine working again. adb was allowing me to lock/unlock the bootloader i toggled that on and off then when i went to boot my phone it took a long time to boot but finally did. Thanks for all the help was in a real jam there for a minute. I used the naked adb drivers posted above not sure if that did anything but it worked for me. Thanks again!
Click to expand...
Click to collapse
cool. glad to hear it.
trying this with a Linux OS
So I have a Samsung Galaxy Nexus on Verizon and I put 4.0.4 (IMM30B) using the Galaxy Nexus ToolKit on Windows. Since then I've had a few issues with performance so I want to go back to stock (ICF53F) then maybe goto latest IMM76K (I think). I've retrieved the zip file from steps above and untar'd the file, but when I try to flash the boot file it just sits there waiting for device. I'm not sure what it's waiting for. I'm in fastboot mode and then plugged in the phone to the usb cord but nothing happens.
Any ideas?
UPDATE:
I figured out the issue. On a linux machine using fastboot requires super user privileges. Maybe an update to the instructions may be in order?
CMD keeps telling me waiting for device.
How long will it takes first time?
this after entering: fastboot flash bootloader bootloader-toro-primekk15.img
ladyminnie said:
CMD keeps telling me waiting for device.
How long will it takes first time?
this after entering: fastboot flash bootloader bootloader-toro-primekk15.img
Click to expand...
Click to collapse
Does "fastboot devices" return your device?
If not, you may have a driver issue.
Sent from my Galaxy Nexus using Tapatalk 2
A mistake I made a while ago, if you are sure that you have already installed ADB drivers, and your device still isn't being recognized by ADB..
Be sure USB Debugging is checked on.
Sent from my Galaxy Nexus using Tapatalk 2
adb devices returns my number from the phone
adb reboot-bootloader does bring my phone into bootloader
than it stops with the next command. I waited for 45 minutes/
---------- Post added at 07:03 PM ---------- Previous post was at 06:57 PM ----------
usb debugging was/is still on
The white small led is lightning up every 10 seconds orso
problem solved with:
http://forum.xda-developers.com/showthread.php?t=1766475
Yes, there are tutorials out there on how to recover from total disaster, which is really useful. I've actually used those last month to recover from HTC BOOT SCREEN logo, but i can still see a couple of folks out there who can't get out of the problem...
This guide will be helpful to those who don't have back-up on their CWM and no ROM saved on their SD card
I'm doing this guide to at least minimize the confusions or the need in posting on how to FIX their phone, i checked the STICKY threads and there's no clear guide on how to do it VIA "CMD", all information below are gathered around the web, xda forums, and some from my experience, thanks to them
I'm just trying to help out and make things easier.
If this thread helped you with your problem, you can always HIT THANKS & RATE above and to the posts that I linked here
HERE'S HOW:
1. Turn off then plug your device, and wait till it says "Device Connected" on your task bar
2. NOW we need to check if you have the driver installed for you're device, just simply right click the "My Computer>Properties>Device Manager"
3. If there will be an EXCLAMATION MARK or QUESTION MARK (not sure of the two) on your HTC device, you need to download the correct driver
4 go here and download the correct driver
5. Once Downloaded, go back to Device Manager, Right click your connected device with Exclamation/Question mark, then choose Update Driver>Browse Files>Select your downloaded driver, once finished. you can close those windows and proceed to next step.
6. Create a New Folder into your drive C:, rename it "fastboot"
7. Download fastboot files here, extract>copy all extracted files to the fastboot folder that you've just created.
8. Now, we need to make sure that the ADB inside the fastboot folder that we created is working, on how to check? go here
9. This is important, BREATHE, RELAX, and SMILE Now to the next step....
10. We need to download the CWM here, just choose the latest unofficial test recovery with USB issues fixed and automount and any ROM that you like here
11. After downloading, we must rename the ROM to update.zip and CWM to recovery.img
12. Extract the ROM and get the boot.img inside
13. COPY boot.img, update.zip and recovery.img to fastboot folder
14. Put your phone into fastboot mode with unlocked bootloader
15. Flash boot with command "fastboot flash boot boot.img"
16. After flashing, Boot recovery using "fastboot flash recovery recovery.img" command
17. After flashing recovery.img, use command "adb push update.zip /sdcard/update.zip" to send the ROM to phone, just be patient, it might not respond for a couple of minutes since the ROM file is big which is usually 500mb,
AS PER ckpv5 there's some changes to this new recovery, see below:
ckpv5 said:
step 10 : Download the latest recovery: http://xda.richardtrip.org/HTC/reco...kwork-touch-5.8.3.1-endeavoru_fixedadbusb.img
step 16 : In fastboot mode :
fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru_fixedadbusb.img
fastboot erase cache
enter recovery, the sdcard is auto-mounted, means that you can directly access the sdcard by connecting the usb cable to pc. Copy the ROM.zip or update.zip to sdcard.
step 17 : no need
step 18 : Install the ROM from update.zip in recovery
Click to expand...
Click to collapse
18. Install the ROM from update.zip in recovery
19. Reboot your phone and everything should be working again, just be patient with the first reboot, it might take some time to open
20. If still stuck? go back to fastboot usb, type this command to CMD, "fastboot erase cache" then "fastboot reboot-bootloader"
21. That's all, enjoy your One X again
*******************************************
NOTE:
- If step 17 is not happening, just don't rename the ROM file to update.zip, leave as it is, and use this command instead, "adb push update.zip /sdcard/EXACT NAME OF THE ROM.zip"
*******************************************
COMMON QUESTIONS OF THE NEWBIES:
How to enter fastboot?
- Hold down POWER BUTTON + VOLUME DOWN, wait for atleast 3-5 seconds
How to open CMD?
- Simply click the Start button of your PC, you should see there CMD or COMMAND PROMPT or you can TYPE CMD in the search panel and hit Enter
How can i open the fastboot folder via CMD?
- Once CMD is open, type "cd c:\fastboot" hit enter, then you can enter the commands, use c:\ if fastboot files is located in your drive c, d:\ if located in your drive d...
*******************************************
You can also go to this STICKY THREAD for additional reference.
If i missed something, please feel free to comment, much appreciated
That's All, hope it helps.. Have a Good Day!
mikey0105 said:
16. After flashing, Boot recovery using "fastboot boot recovery.img" command
Click to expand...
Click to collapse
I really appreciate you putting this together. As with most things on this forum, keeping it in a place where it could be easily discovered is the real trick. God help those of us that ask a question that was asked 2 years ago and is now buried deep within the forum. Lots of Android people get all twisted up about that.
Question: on step 16, did you mean to say "fastboot flash recovery recovery.img"? Or is that the Mac/Linux syntax I'm thinking of?
freicook said:
I really appreciate you putting this together. As with most things on this forum, keeping it in a place where it could be easily discovered is the real trick. God help those of us that ask a question that was asked 2 years ago and is now buried deep within the forum. Lots of Android people get all twisted up about that.
Question: on step 16, did you mean to say "fastboot flash recovery recovery.img"? Or is that the Mac/Linux syntax I'm thinking of?
Click to expand...
Click to collapse
oh! thanks, TYPO.. I'll edit it now, its should be "fastboot flash recovery recovery.img"
this is exactly what I'm lookin' for! after messing my phone.. you are a champ! thanks for compiling everything...
mr_tonysmith said:
this is exactly what I'm lookin' for! after messing my phone.. you are a champ! thanks for compiling everything...
Click to expand...
Click to collapse
No worries... feel free to go back here every time you mess your phone! just kidding..
With the latest recovery, there is no need for step 17.
Just connect the cable, the USB Storage is mounted. If it is not pop-up, open your My Computer, you will see the HTC Storage drive. Copy the ROM.zip and flash.
ckpv5 said:
With the latest recovery, there is no need for step 17.
Just connect the cable, the USB Storage is mounted. If it is not pop-up, open your My Computer, you will see the HTC Storage drive. Copy the ROM.zip and flash.
Click to expand...
Click to collapse
thanks for the info buddy! I'll edit my post and put this info!
ckpv5 said:
With the latest recovery, there is no need for step 17.
Just connect the cable, the USB Storage is mounted. If it is not pop-up, open your My Computer, you will see the HTC Storage drive. Copy the ROM.zip and flash.
Click to expand...
Click to collapse
thanks for the info buddy! I'll edit my post and put this info!
EDIT: before i edit the post, just a clarification... we cannot access the SD card from my computer if the device will not open right? can you please explain further? the process of this new recovery? thanks much!
step 10 : Download the latest recovery: http://xda.richardtrip.org/HTC/reco...kwork-touch-5.8.3.1-endeavoru_fixedadbusb.img
step 16 : In fastboot mode :
fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru_fixedadbusb.img
fastboot erase cache
enter recovery, the sdcard is auto-mounted, means that you can directly access the sdcard by connecting the usb cable to pc. Copy the ROM.zip or update.zip to sdcard.
step 17 : no need
step 18 : Install the ROM from update.zip in recovery
ckpv5 said:
step 10 : Download the latest recovery: http://xda.richardtrip.org/HTC/reco...kwork-touch-5.8.3.1-endeavoru_fixedadbusb.img
step 16 : In fastboot mode :
fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru_fixedadbusb.img
fastboot erase cache
enter recovery, the sdcard is auto-mounted, means that you can directly access the sdcard by connecting the usb cable to pc. Copy the ROM.zip or update.zip to sdcard.
step 17 : no need
step 18 : Install the ROM from update.zip in recovery
Click to expand...
Click to collapse
thanks! i've already added this info
still not working
first of all; thanks for this thread, this was what i was looking for. (I have a clean One X, with no rom on my sd card or something installed.)
I followed your steps -still breathing and smiling too, but i get stuck @ step 17 Cmd gives me an error: device not found. What am i doing wrong?
thanks in advance,
San
edit:
when the phone is off i get:
C:\Android>adb devices
List of devices attached
HT23KW103963 recovery
and when i turn the phone on in fastboot USB mode i get:
C:\Android>adb devices
List of devices attached
snowflakesan said:
first of all; thanks for this thread, this was what i was looking for. (I have a clean One X, with no rom on my sd card or something installed.)
I followed your steps -still breathing and smiling too, but i get stuck @ step 17 Cmd gives me an error: device not found. What am i doing wrong?
thanks in advance,
San
edit:
when the phone is off i get:
C:\Android>adb devices
List of devices attached
HT23KW103963 recovery
and when i turn the phone on in fastboot USB mode i get:
C:\Android>adb devices
List of devices attached
Click to expand...
Click to collapse
there's a quoted instruction @ page 1...
AS PER ckpv5 there's some changes to this new recovery, see below:
Originally Posted by ckpv5
step 10 : Download the latest recovery: http://xda.richardtrip.org/HTC/recov...ixedadbusb.img
step 16 : In fastboot mode :
fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru_fixedadbusb.img
fastboot erase cache
enter recovery, the sdcard is auto-mounted, means that you can directly access the sdcard by connecting the usb cable to pc. Copy the ROM.zip or update.zip to sdcard.
step 17 : no need
step 18 : Install the ROM from update.zip in recovery
argh, it was kinda late, so i must have missed that part
Working like a charm now, thanks man!
snowflakesan said:
argh, it was kinda late, so i must have missed that part
Working like a charm now, thanks man!
Click to expand...
Click to collapse
good for you buddy! enjoy
mikey0105 said:
Yes, there are tutorials out there on how to recover from total disaster, which is really useful. I've actually used those last month to recover from HTC BOOT SCREEN logo, but i can still see a couple of folks out there who can't get out of the problem...
This guide will be helpful to those who don't have back-up on their CWM and no ROM saved on their SD card
I'm doing this guide to at least minimize the confusions or the need in posting on how to FIX their phone, i checked the STICKY threads and there's no clear guide on how to do it VIA "CMD", all information below are gathered around the web, xda forums, and some from my experience, thanks to them
I'm just trying to help out and make things easier.
If this thread helped you with your problem, you can always HIT THANKS & RATE above and to the posts that I linked here
HERE'S HOW:
1. Turn off then plug your device, and wait till it says "Device Connected" on your task bar
2. NOW we need to check if you have the driver installed for you're device, just simply right click the "My Computer>Properties>Device Manager"
3. If there will be an EXCLAMATION MARK or QUESTION MARK (not sure of the two) on your HTC device, you need to download the correct driver
4 go here and download the correct driver
5. Once Downloaded, go back to Device Manager, Right click your connected device with Exclamation/Question mark, then choose Update Driver>Browse Files>Select your downloaded driver, once finished. you can close those windows and proceed to next step.
6. Create a New Folder into your drive C:, rename it "fastboot"
7. Download fastboot files here, extract>copy all extracted files to the fastboot folder that you've just created.
8. Now, we need to make sure that the ADB inside the fastboot folder that we created is working, on how to check? go here
9. This is important, BREATHE, RELAX, and SMILE Now to the next step....
10. We need to download the CWM here, just choose the latest unofficial test recovery with USB issues fixed and automount and any ROM that you like here
11. After downloading, we must rename the ROM to update.zip and CWM to recovery.img
12. Extract the ROM and get the boot.img inside
13. COPY boot.img, update.zip and recovery.img to fastboot folder
14. Put your phone into fastboot mode with unlocked bootloader
15. Flash boot with command "fastboot flash boot boot.img"
16. After flashing, Boot recovery using "fastboot flash recovery recovery.img" command
17. After flashing recovery.img, use command "adb push update.zip /sdcard/update.zip" to send the ROM to phone, just be patient, it might not respond for a couple of minutes since the ROM file is big which is usually 500mb,
AS PER ckpv5 there's some changes to this new recovery, see below:
18. Install the ROM from update.zip in recovery
19. Reboot your phone and everything should be working again, just be patient with the first reboot, it might take some time to open
20. If still stuck? go back to fastboot usb, type this command to CMD, "fastboot erase cache" then "fastboot reboot-bootloader"
21. That's all, enjoy your One X again
*******************************************
NOTE:
- If step 17 is not happening, just don't rename the ROM file to update.zip, leave as it is, and use this command instead, "adb push update.zip /sdcard/EXACT NAME OF THE ROM.zip"
*******************************************
COMMON QUESTIONS OF THE NEWBIES:
How to enter fastboot?
- Hold down POWER BUTTON + VOLUME DOWN, wait for atleast 3-5 seconds
How to open CMD?
- Simply click the Start button of your PC, you should see there CMD or COMMAND PROMPT or you can TYPE CMD in the search panel and hit Enter
How can i open the fastboot folder via CMD?
- Once CMD is open, type "cd c:\fastboot" hit enter, then you can enter the commands, use c:\ if fastboot files is located in your drive c, d:\ if located in your drive d...
*******************************************
You can also go to this STICKY THREAD for additional reference.
If i missed something, please feel free to comment, much appreciated
That's All, hope it helps.. Have a Good Day!
Click to expand...
Click to collapse
16 don't make sense. Think you meant flash recovery not boot.
(at the recovery part ).
Just used this method to dig myself out of a whole I stupidly dug for myself.
Top work!
---------- Post added at 01:33 PM ---------- Previous post was at 01:26 PM ----------
This thread should really be stickied or some such. perfect for n00bs who've done silly things...
I hope you can help me. I thought I was having the same problem as snowflakesan, but I've tried these steps and I can't get into CWM. I've tried flashing every version I can find of clockworkmod, 5.8.3.1, the fixedadbusb version of 5.8.3.1, and 5.8.4.0. Each time I get stuck on the HTC screen with a message at the bottom saying
"This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action."
I can flash TWRP v2.1.7, but not CWM. TWRP seems to work fine except that I can't transfer any files to the sdcard from TWRP because adb says "device not found."
Any ideas on what to try next?
have you installed the drivers for your computer? try and follow the steps carefully from number 1, you might have missed something?
wile i am try to update anything over cmd i am getting following messeg on cmd error: device not found.
and i have correctly installed the driver files too
can you help on this please
Didn't work
I had an one x that was stuck at boot screen. I installed the clockwork 5.8.4.0 and cleaned cache (both through fastboot) but now when i try to load the new recovery the phone just keeps rebooting. I load bootloader, choose recovery and then it just keeps restaring...what do you think could be the problem?
Thanks again for all your help. It is much appreciated.
Not sure what's going on here.. I unrooted my kindlefire with update.zip but I forgot to wipe to factory reset before i flashed update.zip and when i rebooted my kindle i noticed that A ! symbol popped up with "Sorry" that says "The application Calendar Storage (process com.android.providers.calendar) has stopped unexpectedly. Please try again" That isn't the only problem, i click force close and another prompt comes up saying "The process android.process.acore has stopped unexpectedly. Please try again" It waits a few seconds, then proceeds to do a fast reboot? It comes up with the yellow kindle fire and immediately after it boots up it shows the errors.
Not sure what to do. Tried installing TWRP but the kindle doesn't stay on long enough so right now I'm pretty unconvinced of anything..
Any help would be greatly appreciated.
You just need to fast quickly get to factory reset and reset it try from a powered off position it may give you a few seconds extra to complete the task...
Thepooch said:
You just need to fast quickly get to factory reset and reset it try from a powered off position it may give you a few seconds extra to complete the task...
Click to expand...
Click to collapse
I'm not sure how to get there.. I don't have any form of backup installed. It's on the complete default rom
Edit: Found out how to get to factory reset, only to discover that I need a 40% charge, when mine is less than 5% and won't charge any more because of my problem
Still haven't figured this out. Can't use my kindle at all until this is fixed :/
iKrotos said:
Still haven't figured this out. Can't use my kindle at all until this is fixed :/
Click to expand...
Click to collapse
You're most likely going to have to put the device into fastboot mode to fix this problem. You can quickly send a sequence of adb commands to put the device into fastboot before the system crashes...
http://forum.xda-developers.com/showthread.php?t=1638452
by using the "Getting to fastboot mode" section above. That seems sketchy at best. Otherwise, you can get a factory cable...
http://forum.xda-developers.com/showthread.php?t=1550999
and put it into fastboot mode that way. In either case, you'll want to delete the userdata partition...
Code:
fastboot -i 0x1949 erase userdata
Then the next time you boot the device normally (by changing the bootmode back to 4000 if it isn't already), the system software will remake that partition and it should boot normally.
kinfauns said:
You're most likely going to have to put the device into fastboot mode to fix this problem. You can quickly send a sequence of adb commands to put the device into fastboot before the system crashes...
http://forum.xda-developers.com/showthread.php?t=1638452
by using the "Getting to fastboot mode" section above. That seems sketchy at best. Otherwise, you can get a factory cable...
http://forum.xda-developers.com/showthread.php?t=1550999
and put it into fastboot mode that way. In either case, you'll want to delete the userdata partition...
Code:
fastboot -i 0x1949 erase userdata
Then the next time you boot the device normally (by changing the bootmode back to 4000 if it isn't already), the system software will remake that partition and it should boot normally.
Click to expand...
Click to collapse
Read the beginners guide for KF, Found about about ADB fastboot etc. Going to install ADB tomorrow and try to figure this all out. Thanks.
I can't do this. It's been over a month. My kindle is finished..
iKrotos said:
I can't do this. It's been over a month. My kindle is finished..
Click to expand...
Click to collapse
"I can't do this"
Well that explains everything, doesn't it? It's a good thing you explained your problem in such great detail or I might spend time trying to help you fix your Kindle thinking you "could" do it. Phew. Saved us all a lot of time, thank you.
I made the same mistake of flashing the stock update without wiping and factory resetting.
The device will boot, then immediately give the calendar and android.process.acore errors for about 20 seconds before rebooting. It doesn't give me enough time to do a factory reset through the menu before it restarts.
After reading up on basic guides and downloading the necessary software, I can't find a way to get to fastboot, and I'm afraid even the noob guides are just confusing me more at this point.
From what I can understand, I'll probably have to get a factory cable to force the device into fastboot, because the Kindle reboots before the PC has a chance to recognize it, but what happens then? I've read the ADB for dummies guides, and searched the forum for and I still can't really understand how to execute the commands.
Can anyone link a relevant thread, or maybe give some dumbed-down advice?
LaszloToth said:
I made the same mistake of flashing the stock update without wiping and factory resetting.
The device will boot, then immediately give the calendar and android.process.acore errors for about 20 seconds before rebooting. It doesn't give me enough time to do a factory reset through the menu before it restarts.
After reading up on basic guides and downloading the necessary software, I can't find a way to get to fastboot, and I'm afraid even the noob guides are just confusing me more at this point.
From what I can understand, I'll probably have to get a factory cable to force the device into fastboot, because the Kindle reboots before the PC has a chance to recognize it, but what happens then? I've read the ADB for dummies guides, and searched the forum for and I still can't really understand how to execute the commands.
Can anyone link a relevant thread, or maybe give some dumbed-down advice?
Click to expand...
Click to collapse
Get a factory cable and then we can work on fixing your device.
One thing you have to know about entering commands is that computers have no more intelligence than, say, an ordinary rock. Meaning, they are not able to think on their own. They don't have the capacity to make their own decisions. Everything is laid out for them via sets of instructions. ADB and fastboot are programs with their own sets of instructions embedded into them, so in order to use them, you must direct the computer to those programs. When entering commands from the command line, the computer will search only the present working directory for those commands (plus any directories in it's PATH, but that is a subject for another time). When you open a command prompt in Windows, it will start in a specific directory (folder). Normally in Windows its the "Documents and Settings" folder (if I remember correctly). When you enter a command like "adb devices", the computer will search it's own set of built in commands for the first word (command) in the command line (in this case, adb). If that command isn't in it's set of built in commands, it searches the present working directory. In all likelihood, adb will not be in in the first present working directory when the command prompt opens up so you have to redirect it. There are several ways to do this. You can make sure the directory containing adb is in your PATH, but there's a little bit of learning involved and it's unnecessary unless you intend to enter a LOT of adb commands. You can change directories (cd) to the correct folder, but if you don't know what you're doing it can get very confusing and frustrating. The easiest and most straight forward way of doing this is to locate the directory containing adb and fastboot then "Shift + right-click, on that folder and select "Open command window here". The command window that opens is where you'll enter your adb/fastboot commands. Apart from that, you must really know the commands you're using, how they're used and what they do, or you're just wasting your time.
Does or kindle gets recognized.. if so there is a chance to recover
Sent from my MB526 using Tapatalk 2
soupmagnet said:
Get a factory cable and then we can work on fixing your device.
One thing you have to know about entering commands is that computers have no more intelligence than, say, an ordinary rock. Meaning, they are not able to think on their own. They don't have the capacity to make their own decisions. Everything is laid out for them via sets of instructions. ADB and fastboot are programs with their own sets of instructions embedded into them, so in order to use them, you must direct the computer to those programs. When entering commands from the command line, the computer will search only the present working directory for those commands (plus any directories in it's PATH, but that is a subject for another time). When you open a command prompt in Windows, it will start in a specific directory (folder). Normally in Windows its the "Documents and Settings" folder (if I remember correctly). When you enter a command like "adb devices", the computer will search it's own set of built in commands for the first word (command) in the command line (in this case, adb). If that command isn't in it's set of built in commands, it searches the present working directory. In all likelihood, adb will not be in in the first present working directory when the command prompt opens up so you have to redirect it. There are several ways to do this. You can make sure the directory containing adb is in your PATH, but there's a little bit of learning involved and it's unnecessary unless you intend to enter a LOT of adb commands. You can change directories (cd) to the correct folder, but if you don't know what you're doing it can get very confusing and frustrating. The easiest and most straight forward way of doing this is to locate the directory containing adb and fastboot then "Shift + right-click, on that folder and select "Open command window here". The command window that opens is where you'll enter your adb/fastboot commands. Apart from that, you must really know the commands you're using, how they're used and what they do, or you're just wasting your time.
Click to expand...
Click to collapse
Thanks, I've read up a bit more about the ADB and Fastboot commands, and I think I have a better grasp on them now, and your explanation of where I need be as far as changing directories in the command prompt really clears things up.
From reading your advice earlier in this thread, my best option would probably be to wipe the existing user data on the device that I forgot about before re-flashing the stock Kindle update by changing directories to the folder which contains ADB.exe and Fastboot.exe, then running the "fastboot -i 0x1949 erase userdata" command once I've connected the device with a factory cable. By doing this, would I be essentially restoring the device as if it were brand new again? Aside from erasing user data, are there any other ADB or Fastboot commands that I should run?
Also, assuming the ADB drivers are installed properly, once I've plugged in the device with the factory cable, will KFU immediately recognize the device, or will I need to first run the "fastboot -i 0x1949 erase userdata" command to get it back to stock first before I get 4000 status in KFU? I'm wondering if I could just plug in the factory cable, root and flash TWRP via KFU, then wipe and factory reset the user data from within TWRP, or would that be going about it backwards?
Thanks again fro the help!
---------- Post added at 02:31 PM ---------- Previous post was at 02:24 PM ----------
kishorev said:
Does or kindle gets recognized.. if so there is a chance to recover
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
No, the KFU status is "unknown" and Windows doesn't even really have time to recognize that the device is connected via USB, since the Kindle will reboot every 15-20 seconds.
I've ordered a factory cable, so hopefully it will be a pretty straight-forward fix once I get it.
Had a similar problem of rebooting every 10 sec or so..I left it on charge overnight and it worked..it got charged decent enough for me to help recover it..
Just try charging it overnight it might just work..I always feel using factory cable shd be the last resort
Sent from my Kindle Fire using Tapatalk 2
LaszloToth said:
Thanks, I've read up a bit more about the ADB and Fastboot commands, and I think I have a better grasp on them now, and your explanation of where I need be as far as changing directories in the command prompt really clears things up.
From reading your advice earlier in this thread, my best option would probably be to wipe the existing user data on the device that I forgot about before re-flashing the stock Kindle update by changing directories to the folder which contains ADB.exe and Fastboot.exe, then running the "fastboot -i 0x1949 erase userdata" command once I've connected the device with a factory cable. By doing this, would I be essentially restoring the device as if it were brand new again? Aside from erasing user data, are there any other ADB or Fastboot commands that I should run?
Also, assuming the ADB drivers are installed properly, once I've plugged in the device with the factory cable, will KFU immediately recognize the device, or will I need to first run the "fastboot -i 0x1949 erase userdata" command to get it back to stock first before I get 4000 status in KFU? I'm wondering if I could just plug in the factory cable, root and flash TWRP via KFU, then wipe and factory reset the user data from within TWRP, or would that be going about it backwards?
No, the KFU status is "unknown" and Windows doesn't even really have time to recognize that the device is connected via USB, since the Kindle will reboot every 15-20 seconds.
I've ordered a factory cable, so hopefully it will be a pretty straight-forward fix once I get it.
Click to expand...
Click to collapse
One thing you need to realize, is that once you get custom recovery installed, you will rarely ever need to use fastboot commands. Fastboot commands really only need to be used when everything else fails. Custom recovery and the latest version of the FireFireFire bootloader have probably 90% of the functionality that fastboot has, so unless those options aren't available to you, try to avoid fastboot altogether.
Most Kindle Fire problems are fixed by wiping the system, data & cache (factory reset) partitions and reinstalling the ROM.
Your first course of action should be to get TWRP and FireFireFire installed, if they aren't already. For this you will need fastboot commands. In order to issue fastboot commands, you need to be in fastboot mode. I'm guessing this is most likely not the case. Unfortunately, without a system to boot to, or the FireFireFire bootloader (blue Kindle Fire logo) installed, you have no chance of getting into fastboot without a factory cable.
The factory cable will get you into fastboot so you can reinstall custom recovery and reinstall a new ROM. You can then use the custom recovery to install a new bootloader (never wipe to install a bootloader BTW). Chances are, that is all you need to fix your device. You should keep your device powered off (hold power button for 20 seconds), until the factory cable arrives.
Hope that helps.
soupmagnet said:
One thing you need to realize, is that once you get custom recovery installed, you will rarely ever need to use fastboot commands. Fastboot commands really only need to be used when everything else fails. Custom recovery and the latest version of the FireFireFire bootloader have probably 90% of the functionality that fastboot has, so unless those options aren't available to you, try to avoid fastboot altogether.
Most Kindle Fire problems are fixed by wiping the system, data & cache (factory reset) partitions and reinstalling the ROM.
Your first course of action should be to get TWRP and FireFireFire installed, if they aren't already. For this you will need fastboot commands. In order to issue fastboot commands, you need to be in fastboot mode. I'm guessing this is most likely not the case. Unfortunately, without a system to boot to, or the FireFireFire bootloader (blue Kindle Fire logo) installed, you have no chance of getting into fastboot without a factory cable.
The factory cable will get you into fastboot so you can reinstall custom recovery and reinstall a new ROM. You can then use the custom recovery to install a new bootloader (never wipe to install a bootloader BTW). Chances are, that is all you need to fix your device. You should keep your device powered off (hold power button for 20 seconds), until the factory cable arrives.
Hope that helps.
Click to expand...
Click to collapse
So instead of using fastboot to wipe the user data, I should use it to install TWRP? Can you give me the fastboot command for that? Or can I do that with KFU once I plug in the factory cable?
http://forum.xda-developers.com/showpost.php?p=23747804
Thanks soupmagnet, I got the factory cable today and was able to flash FFF and TWRP with fastboot commands, and it's working like it should again. You help has been much appreciated.
same problem with kindle fire.
LaszloToth said:
Thanks soupmagnet, I got the factory cable today and was able to flash FFF and TWRP with fastboot commands, and it's working like it should again. You help has been much appreciated.
Click to expand...
Click to collapse
hi, i am new here and i got exact the same problem with you, i just ordered the factory cable, can you please give the step by step procedure on solving this problem with the factory cable. your help will be appreciated, thanks.
Thepooch said:
You just need to fast quickly get to factory reset and reset it try from a powered off position it may give you a few seconds extra to complete the task...
Click to expand...
Click to collapse
:good::good::good::good::good::good: works for me thank you
ok, today i had the same problem because i didn't wipe the factory restore!
The solution WASN'T the Factory Cable (I was considering buying one)!
Very easy:
Linux and SOUPKIT! were the solution, when the tablet boots up immediately hit the install recovery, after installing recovery, just set to boot into recovery.
Now is very much you can do (ex. wipe everything and than install update.zip all over)
Very much thank you to the guy who made SOUPKIT! (u've saved my S many many times )
Hello,
Anyone facing issues of random reboots on ZenFone 2 4gb/32gb model?
If yes, how to come over this issue?
Mine is a WW version. Bought it from FlipKart. Un-rooted.
Suhas_JS said:
Hello,
Anyone facing issues of random reboots on ZenFone 2 4gb/32gb model?
If yes, how to come over this issue?
Mine is a WW version. Bought it from FlipKart. Un-rooted.
Click to expand...
Click to collapse
You could back up any important information you had, format the phone and then sideload either the stock firmware (available from Asus) or the pre-rooted images available here.
kibmikey1 said:
You could back up any important information you had, format the phone and then sideload either the stock firmware (available from Asus) or the pre-rooted images available here.
Click to expand...
Click to collapse
Just hard reset or complete wiping of cache, dalvik, data, root and then reload the stock/pre-rooted ROM?
It's what I would try.
Download these, if you don't have them:
Intel USB Driver
ADB & Fastboot Tool
and either stock ROM from Asus or
if you prefer, the same latest ROM pre-rooted from here. Make sure you have the ROMS in your platform-tools folder of the adb/fastboot tool you downloaded.
Once you have everything you need:
Restart your phone and hold volume up to enter fastboot/bootloader.
Test the connection from your pc adb/fastboot terminal by typing: fastboot devices. You should see numbers and device listed. If not, double check your driver installation and try again. Once the connection's established,
Enter the following fastboot commands:
fastboot format system
fastboot format cache
fastboot format data
Once completed, you have two methods to install the ROM of your choice. You can unzip the pre-rooted rom and install each partition individually. Note, you need to unzip system.img into the folder with the other img's. Once again, be sure to copy these img's to the platform-tools folder of the adb/fastboot tool. These fastboot commands are:
fastboot flash fastboot droidboot.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Once completed, use the volume selection menu to do a normal boot into Android, and setup from there.
Alternatively you could sideload the Asus ROM from adb in recovery. To do this, use the volume selection menu to do a reboot into recovery mode. In recovery, select install update from ADB. In your adb/fastboot terminal type:
adb devices (to check connection)
adb sideload (either drag and drop the ROM or enter the /path)
Once it loads, reboot into system, and setup from there.
Please do research this and make sure this is what you want to do. I hope this helps.
Edit: I know these instructions can be found elsewhere, but I couldn't in good conscience advise someone to wipe their phone and not help them. I'd never ask someone else to do something I wouldn't do.
Thanks a ton mate
Sent from my ASUS_Z00AD using XDA Free mobile app
i suspect this has alot to do with android 5.0. asus needs to work on getting 5.1 to the device.
Suhas_JS said:
Thanks a ton mate
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
what rom did you install? latest or stock?
did you follow the step one or alternative??
please help me i got the same problem.
kibmikey1 said:
It's what I would try.
Download these, if you don't have them:
stock ROM from Asus[/URL] or
if you prefer, the same latest ROM pre-rooted from here. Make sure you have the ROMS in your platform-tools folder of the adb/fastboot tool you downloaded.
Once you have everything you need:
Restart your phone and hold volume up to enter fastboot/bootloader.
Test the connection from your pc adb/fastboot terminal by typing: fastboot devices. You should see numbers and device listed. If not, double check your driver installation and try again. Once the connection's established,
Enter the following fastboot commands:
fastboot format system
fastboot format cache
fastboot format data
Once completed, you have two methods to install the ROM of your choice. You can unzip the pre-rooted rom and install each partition individually. Note, you need to unzip system.img into the folder with the other img's. Once again, be sure to copy these img's to the platform-tools folder of the adb/fastboot tool. These fastboot commands are:
fastboot flash fastboot droidboot.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Once completed, use the volume selection menu to do a normal boot into Android, and setup from there.
Alternatively you could sideload the Asus ROM from adb in recovery. To do this, use the volume selection menu to do a reboot into recovery mode. In recovery, select install update from ADB. In your adb/fastboot terminal type:
adb devices (to check connection)
adb sideload (either drag and drop the ROM or enter the /path)
Once it loads, reboot into system, and setup from there.
Please do research this and make sure this is what you want to do. I hope this helps.
Edit: I know these instructions can be found elsewhere, but I couldn't in good conscience advise someone to wipe their phone and not help them. I'd never ask someone else to do something I wouldn't do.
Click to expand...
Click to collapse
following the process i have install stock rom... with adn sideloader... this version is not suporrted so download 1.0.32 form other place.. sucessfully install the rom . don't know yet the problem is solved or not.. but i will post update after using .. thanks man.. atlest after viewing lots of form alon with asus whole day.. following urs sucessfully able install the rom with adb sideload. thanks a lot. now hope it will work fine.
---------- Post added at 06:54 PM ---------- Previous post was at 06:48 PM ----------
kowsar684 said:
following the process i have install stock rom... with adn sideloader... this version is not suporrted so download 1.0.32 form other place.. sucessfully install the rom . don't know yet the problem is solved or not.. but i will post update after using .. thanks man.. atlest after viewing lots of form alon with asus whole day.. following urs sucessfully able install the rom with adb sideload. thanks a lot. now hope it will work fine.
Click to expand...
Click to collapse
no problem is still there ...... should i install pre root rom???
---------- Post added at 07:01 PM ---------- Previous post was at 06:54 PM ----------
what is the difference between stock ROM and pre root ROM???
can't install stock rom. how to flass
kibmikey1 said:
It's what I would try.
Download these, if you don't have them:
Intel USB Driver
ADB & Fastboot Tool
and either stock ROM from Asus or
if you prefer, the same latest ROM pre-rooted from here. Make sure you have the ROMS in your platform-tools folder of the adb/fastboot tool you downloaded.
Once you have everything you need:
Restart your phone and hold volume up to enter fastboot/bootloader.
Test the connection from your pc adb/fastboot terminal by typing: fastboot devices. You should see numbers and device listed. If not, double check your driver installation and try again. Once the connection's established,
Enter the following fastboot commands:
fastboot format system
fastboot format cache
fastboot format data
Once completed, you have two methods to install the ROM of your choice. You can unzip the pre-rooted rom and install each partition individually. Note, you need to unzip system.img into the folder with the other img's. Once again, be sure to copy these img's to the platform-tools folder of the adb/fastboot tool. These fastboot commands are:
fastboot flash fastboot droidboot.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Once completed, use the volume selection menu to do a normal boot into Android, and setup from there.
Alternatively you could sideload the Asus ROM from adb in recovery. To do this, use the volume selection menu to do a reboot into recovery mode. In recovery, select install update from ADB. In your adb/fastboot terminal type:
adb devices (to check connection)
adb sideload (either drag and drop the ROM or enter the /path)
Once it loads, reboot into system, and setup from there.
Please do research this and make sure this is what you want to do. I hope this helps.
Edit: I know these instructions can be found elsewhere, but I couldn't in good conscience advise someone to wipe their phone and not help them. I'd never ask someone else to do something I wouldn't do.
Click to expand...
Click to collapse
Thanks a million man.
This saved me instead of sending back the phone rto newegg after a failed cache format.
Repped!!!
I have folowed all step successfuly but reboots are still there, i can't do **** about them, mostly happen installing / updating apps and playing games, sometime it's just random, listening music.
more ideas about why it's happen?
I have recently had a spate of random reboots. Thought it was flip cover causing problem, still the same. Its the 32Gb, 4Gb ram, 1.8mhz model.
Phone is stock, all updates applied and problem happening much more after last update, 22.
sandozer said:
I have recently had a spate of random reboots. Thought it was flip cover causing problem, still the same. Its the 32Gb, 4Gb ram, 1.8mhz model.
Phone is stock, all updates applied and problem happening much more after last update, 22.
Click to expand...
Click to collapse
If you have been using the phone as an ordinary consumer, I would suggest to get a replacement if that's within your entitlement. Just my personal opinion.
Sent from my ASUS_Z00AD
Anyone get a random shutdown with the 2.19.40.20 firmware? Happened to me overnight/this morning, at 98 to 96% charge. First time this has happened with this device.
No last_kmsg to share, so will keep a watch on it for now...
Edit: happened a second time, this afternoon. Maybe I will upgrade to 2.19.40.22, or at least install TWRP to see if I can grab a last_kmsg (if I can find it) to see what's going on..
chooks06 said:
If you have been using the phone as an ordinary consumer, I would suggest to get a replacement if that's within your entitlement. Just my personal opinion.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
Yes, good advice ! Unfortunately I bought it in Hong Kong at the beginning of April. It has had no problems, seems like the last update upset something. Maybe 5.1 will do me a favour . . . .
@sandozer..5.1 will do a lot of good for a lot of people
sandozer said:
Yes, good advice ! Unfortunately I bought it in Hong Kong at the beginning of April. It has had no problems, seems like the last update upset something. Maybe 5.1 will do me a favour . . . .
Click to expand...
Click to collapse
If you have not tried resetting the phone, it may be worth a try, though painful to start setting up all over again. You can try using the stock ASUS back up app to do your back up..
Sent from my ASUS_Z00AD
I am on 22 and have random reboots as well?
I had 2 random reboots on the 2gb/16gb version, but I think it was USB cable related. I'd plug the phone into the car and do something fast and then lock it, POOF! Reboot. It hasn't happened in awhile though and I believe I did an OTA update afterwards.
This How-to is special. This is for when all else fails or you've just reached a point when the device's software is broken and doesn't flash or run correctly.
I'd messed up my device pretty badly. This will also work for you if you are having key_info issues.
If your partitions are broken. If your phone is refusing to flash. If your phone is bootlooping without reason.
Performance issues of any other sort including but not limited to Fingerprint, Bluetooth, Audio, Wi-Fi, NFC and MSIM.
READ IT A FEW TIMES. DO NOT MISS ANY STEPS.
Code:
[B][CENTER]*** DISCLAIMER***[/CENTER][/B]
DOING THIS WILL ABSOLUTELY WIPE EVERYTHING ON YOUR DEVICE. PARTITIONS INCLUDED.
I AM NOT RESPONSIBLE FOR ANY OUTCOME FROM IT.
EVEN IF IT MEANS THERMONUCLEAR WAR OR YOUR SIGNIFICANT OTHER/ FAMILY ATTEMPTING TO KILL YOU
REQUIREMENTS - ALL MUST BE MET
WINDOWS COMPUTER with functioning USB 2.0 ports. I said 2.0.
Original cable or one you know for SURE has no issues in it. I personally prefer the OnePlus cables.
ORIGINAL SOFTWARE(Linked in the post)
UNLOCKED ROBIN [MUST]
Lots of patience (SERIOUSLY)
SOFTWAREThe USB driver for your Robin and ONLY the 7.1.1 N108 image. LINK
ADB and FASTBOOT from this XDA Thread -> LINK
HOW TO - READ TWICE. EXECUTE ONCE.1. Start with USB Driver I used windows 10 to do this.
Right Click downloaded Robin USB Driver.
Properties -> Compatibility -> Run this program in compatibility mode-> Windows XP SP3
Hit Apply -> Ok -> Run installer -> Follow Steps.
Finish Installer -> REBOOT (I mean it)
2. Unzip your rom to a folder. For Example C:\N108
3. Go to the folder where you have unpacked your ROM. Unzip the contents of the Minimal ADB and Fastboot into that folder. Overwrite ALL existing files.
4. Click FILE-> Open Command Promt -> Open Command Prompt as ADMINISTRATOR -> Click Allow. CD to your folder. If you are using another drive you'll have to go X: followed by cd X:\<your folder name>
5.Type this in the command window
Code:
set ANDROID_PRODUCT_OUT=<LOCATION OF YOUR ROM>
LEAVE THIS COMMAND WINDOW OPEN.
6. inside your rom folder Right Click -> New - >Text Document
7. Copy the following into the first line of your document and save it.
Code:
board=NBQ_BSP
Save the file as
Code:
android-info.txt
8. Recheck that you did all those steps. You CANNOT miss a single one.
9. Put the phone into FASTBOOT mode. Hit the power button -> First screen -> Press any volume key -> Navigate to Fastboot and hit the power button. Your phone is now in fastbooot mode.
10. Connect the cable and DO NOT move it once it is connected. Do NOT connect ANY other phone during this process.
11. Check your Device Manager. It should say that there is an Android Fastboot Device connected.
12. Switch back to your command window. NOW READ THE NEXT STEPS AND COPY PASTE THEM ONE AT A TIME> DON'T MAKE A MISTAKE.
13. TYPE
Code:
fastboot devices
you will get a response with fastboot and a device number.
Make sure only the Robin is connected. NOTHING ELSE.
If it does not come up you messed up the Fastboot/ADB install.
14. NOW; THIS IS THE TRICKY PART. DON'T mess up. DON'T disturb the phone/cable/computer. Don't do ANYTHING else.
WAITThen next step will leave the phone looking like it is doing NOTHING. That's ok. It takes a VERY long time.
type the following into the command prompt
Code:
fastboot -i 0x2c3f -w flashall
AT THIS POINT it will say something like
Code:
Target report size <number>
LEAVE THE DEVICE AND WALK AWAY. Get a snack.
15. After sometime. The script will say succeeded and the phone will reboot.
16. Congratulate yourself on your patience. you have a fresh installed device.
If you want to custom ROM read on ->
1. Download the latest TWRP here
2. Reboot to fastboot mode.
3. fastboot "fastboot -i 0x2c3f flash recovery <twrp image name>"
4. Reboot to recovery
5. Swipe to allow modifications.
6. Wipe -> Format Data -> Yes.
7. Copy your favourite ROM to internal storage.
8. Flash it. You are one your way!
Saving it. Just in case.
Hi @valhallen.282,
I followed your instructions and all went well, however, when flashing system image I am getting the following error. Am I doing something wrong here? Appreciate your help.
sending sparse 'system' (516282 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 12.979s
minhajlk said:
Hi @valhallen.282,
I followed your instructions and all went well, however, when flashing system image I am getting the following error. Am I doing something wrong here? Appreciate your help.
sending sparse 'system' (516282 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 12.979s
Click to expand...
Click to collapse
What cable are you on and what port? That sounds like it is starting the wipe and not finishing it.
valhallen.282 said:
What cable are you on and what port? That sounds like it is starting the wipe and not finishing it.
Click to expand...
Click to collapse
I am using the original cable on USB 2 port.
Sent from my Nexus 5 using XDA Labs
minhajlk said:
I am using the original cable on USB 2 port.
Click to expand...
Click to collapse
I'd start with trying a different cable or using it the other way around. (yes I know it sounds stupid.) But that's just the way it is. (I know this because my stock cable has stopped working. ) You could try the One Plus cables. They seem to be of exceptional build quality.
valhallen.282 said:
I'd start with trying a different cable or using it the other way around. (yes I know it sounds stupid.) But that's just the way it is. (I know this because my stock cable has stopped working. ) You could try the One Plus cables. They seem to be of exceptional build quality.
Click to expand...
Click to collapse
Ok I will try that out and get back to you. Thanks mate.
Sent from my Nexus 5 using XDA Labs
Did this but got an error
Here's how my steps went
Code:
set ANDROID_PRODUCT_OUT=C:\User\[USER]\Documents\N108
created the text file, placed it into the n108 folder
then after flash all i got this
Code:
fastboot -i 0x2c3f -w flashal
load_file: could not allocate -1373637176 bytes
error could not load system.img
what do
JaxXzTwitch said:
Here's how my steps went
created the text file, placed it into the n108 folder
then after flash all i got this
what do
Click to expand...
Click to collapse
Are you unlocked is the first question.
Second is - adb is running from within the specified folder or outside it.
Third is what cable. Without details it's difficult to analyze what you've faced.
valhallen.282 said:
Are you unlocked is the first question.
Second is - adb is running from within the specified folder or outside it.
Third is what cable. Without details it's difficult to analyze what you've faced.
Click to expand...
Click to collapse
Yes i'm unlocked
it's within the target folder,
using stock cable, i've used it on adb before and it's only a few days old so i think it isn't ruined
Do you currently have a working TWRP? If you do suggest you go in and wipe EVERYTHING.
INCLUDING System + Data + Caches + Internal. Immediately reboot to bootloader. Yes it warms you of no OS loaded that's fine.
Then try again.
Yes it needs that drastic sometimes. As long as you have fastboot you can always come back to TWRP and an empty device.
valhallen.282 said:
Do you currently have a working TWRP? If you do suggest you go in and wipe EVERYTHING.
INCLUDING System + Data + Caches + Internal. Immediately reboot to bootloader. Yes it warms you of no OS loaded that's fine.
Then try again.
Yes it needs that drastic sometimes. As long as you have fastboot you can always come back to TWRP and an empty device.
Click to expand...
Click to collapse
i'm kind of hesitant to do that, because i get errors when plugging in my phone and it won't recognize it sometimes, and fastboot won't complete flashes.
JaxXzTwitch said:
i'm kind of hesitant to do that, because i get errors when plugging in my phone and it won't recognize it sometimes, and fastboot won't complete flashes.
Click to expand...
Click to collapse
see now that's important information. That means your cable IS on it's way out! NextBit built a fantastic phone but an utterly design oriented non functional cable.I'd suggest buying or borrowing a One Plus USB-C cable.
However - explain your errors please.
it could be the cable, but it's only days old, i get "this usb device has malfunctioned and is not recognized by windows" errors, or my device will read as connected, but offline, when i execute "adb devices", running "adb kill-server" doesn't bring it back either
JaxXzTwitch said:
Here's how my steps went
Code:
set ANDROID_PRODUCT_OUT=C:\User\[USER]\Documents\N108
created the text file, placed it into the n108 folder
then after flash all i got this
Code:
fastboot -i 0x2c3f -w flashal
load_file: could not allocate -1373637176 bytes
error could not load system.img
what do
Click to expand...
Click to collapse
I had this issue with N88 and N108, here is what I did:
Once the flash has failed, reboot back to bootloader by holding Volume Down and Power until the screen goes off, then release Power, then press Power again to boot, all while still holding Volume Down.
Once back into Fastboot mode, open a new Command prompt (cmd.exe), change to the directory with the files and type "fastboot -1 0x2c3f flash system system.img" and wait for it to finish (parse 6/6).
Once that has finished type "fastboot reboot" to reboot and then leave it alone until you see the purple "Welcome" screen.
Hope this helps.
DJ_SpaRky said:
I had this issue with N88 and N108, here is what I did:
Once the flash has failed, reboot back to bootloader by holding Volume Down and Power until the screen goes off, then release Power, then press Power again to boot, all while still holding Volume Down.
Once back into Fastboot mode, open a new Command prompt (cmd.exe), change to the directory with the files and type "fastboot -1 0x2c3f flash system system.img" and wait for it to finish (parse 6/6).
Once that has finished type "fastboot reboot" to reboot and then leave it alone until you see the purple "Welcome" screen.
Hope this helps.
Click to expand...
Click to collapse
+DJ_SpaRky
is the net result of your flash method same as the original intentions ie
This will also work for you if you are having key_info issues.
If your partitions are broken.
If your phone is refusing to flash.
If your phone is bootlooping without reason.
Performance issues of any other sort
iluvatrix said:
+DJ_SpaRky
is the net result of your flash method same as the original intentions ie
This will also work for you if you are having key_info issues.
If your partitions are broken.
If your phone is refusing to flash.
If your phone is bootlooping without reason.
Performance issues of any other sort
Click to expand...
Click to collapse
Just a fix for the "cannot find system.img" error.
DJ_SpaRky said:
Just a fix for the "cannot find system.img" error.
Click to expand...
Click to collapse
so would this be considered a successful flash back to stock?
& fixed broken partitions as well?
iluvatrix said:
so would this be considered a successful flash back to stock?
& fixed broken partitions as well?
Click to expand...
Click to collapse
Yes, back to Stock, not sure about broken partitions, never had that problem.
Yes back to stock and fully repaired partitions. The OP says so specifically.
The NextBit method is simply a wipe and overwrite. This is wipe, rebuild, rewrite from scratch.