Any recommendations on removing TWRP and restoring stock recovery so I can move up to 7.1.1?
I don't have a backup of the old recovery.
Moogagot said:
Any recommendations on removing TWRP and restoring stock recovery so I can move up to 7.1.1?
I don't have a backup of the old recovery.
Click to expand...
Click to collapse
Flash the boot.img from the stock system image. This has been mentioned many times around this forum. Search is your friend.
cntryby429 said:
This has been mentioned many times around this forum. Search is your friend.
Click to expand...
Click to collapse
I've spent hours searching everything from "Stock Bootloader" to "Remove TWRP" with no luck. Any advice?
Moogagot said:
I've spent hours searching everything from "Stock Bootloader" to "Remove TWRP" with no luck. Any advice?
Click to expand...
Click to collapse
Well, it's actually everywhere. However, you have to discern what apply to you and what do not. That's the danger of a public forum such a this. Everyone has an opinion. Sometimes, an inaccurate answer is provided. Most other times, the incorrect question was originally posed.
In your case, you don't need to go back to the original stock image. Assuming your bootloader is still unlocked, just flash 7.1.1 and get on with your life. Download 7.1.1 stock image from the Google developers' web site. Extract it. Edit the flash-all.bat file to remove the -w switch if you don't want to lose userdata. Boot the phone into bootloader. Execute flash-all.bat. Then you have 7.1.1.
If you don't have a recovery backup, then you're taking a risk. I have not only a recovery backup, but more importantly, a complete set of Titanium backup on my laptop.
Moogagot said:
I've spent hours searching everything from "Stock Bootloader" to "Remove TWRP" with no luck. Any advice?
Click to expand...
Click to collapse
Download the factory image for the version of Android that you're currently running. Look inside the zip and you'll find another zipped file. Open that and you'll see a file in there that's named boot.img. Extract the boot.img file the same folder as your fastboot is in, open a command prompt in that folder flash it with fastboot.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
That will get you back to the stock bootloader and stock recovery.
robocuff said:
Download the factory image for the version of Android that you're currently running. Look inside the zip and you'll find another zipped file. Open that and you'll see a file in there that's named boot.img. Extract the boot.img file the same folder as your fastboot is in, open a command prompt in that folder flash it with fastboot.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
That will get you back to the stock bootloader and stock recovery.
Click to expand...
Click to collapse
I tried flashing some other stuff and it bricked Google is sending out a replacement.
Moogagot said:
I tried flashing some other stuff and it bricked Google is sending out a replacement.
Click to expand...
Click to collapse
Well, hope there's not a next time, but power + volume up should take you to the recovery menu. It's next to impossible to brick phones any more. Lord knows I try daily to see how I can brick my phones, just so I can assist others.
quangtran1 said:
Well, hope there's not a next time, but power + volume up should take you to the recovery menu. It's next to impossible to brick phones any more. Lord knows I try daily to see how I can brick my phones, just so I can assist others.
Click to expand...
Click to collapse
I broke recovery. I just says "No Command"
Moogagot said:
I broke recovery. I just says "No Command"
Click to expand...
Click to collapse
No you didn't, at that screen with "No Command":
Hold the Power button and press Volume Up once, and a menu will appear.
Moogagot said:
I broke recovery. I just says "No Command"
Click to expand...
Click to collapse
Come on man, you can do it next time. Please?
http://lmgtfy.com/?q=no+command+stock+recovery+pixel
krelvinaz said:
No you didn't, at that screen with "No Command":
Hold the Power button and press Volume Up once, and a menu will appear.
Click to expand...
Click to collapse
No menu appears. I just get a flash and back to no command.
I can get into the bootloader, but again, any option leads to the No Command screen.
Ok, from the bootloader I was able to manually flash a different image and things are looking a little better.
I now have the dancing dots and ADB see's a device attached. PROGRESS!
The devices throws errors on bootup, but it runs for now.
Please ignore. Posted to wrong thread. Sorry!
Here's the easiest way I've found to update. You'll need TWRP, so go ahead and download it - https://twrp.me/devices/googlepixel.html. Put the img file on your computer and the zip file on your phone. You'll boot into TWRP by using the "Fastboot boot" command. DO NOT "fastboot flash" it or you'll have to re-flash the boot image to get your phone out of a bootloop.
Now that you're in TWRP, you'll need the OTA file. I've only tested going up one increment so I suggest doing it that way. If you're brave, go ahead and download the latest OTA - https://developers.google.com/android/ota. Worst case TWRP won't flash it and you'll have to go back and do them incrementally.
Now that you're in TWRP and have the OTA and TWRP-RC1.zip on your phone, flash the update just like you would a rom. As soon as it successfully flashes (and before you reboot), flash the TWRP zip.
I did this incrementally from NMF260 > NMF26U > NMF26V without any issues. I believe it'll work as long as you're moving up an OTA just as the phone would have normally received them. Just remember to flash TWRP every time after you install the OTA as it gets overwritten with each OTA.
Sent from my Pixel using Tapatalk
Google needs to start voiding warranty for people who want to unlock bootloader
Moogagot said:
I broke recovery. I just says "No Command"
Click to expand...
Click to collapse
I Know this post is old, I am just researching but, sounds to me like you really need to search, read, and actually learn before you attempt anything on your phone. I am not being hateful or rude, just pointing out the obvious....
Related
I've looked through other posts about this and nothing seems to help. I went to actually UNroot my Xoom so I can install the latest update because I had no use for a root, but when I went to do fastboot flash system system.img with the stock .img file, it takes forever then gives me an error... I don't know how to get past this. I just want my Xoom back to normal, even if I can get it back to a rooted normal I can live with that.
(Also, the first first time I tried unrooting, I realized I used the wrong device files. I used the Verizon ones, when I only have WiFi.)
Somebody please help me, or I feel like I have an expensive paperweight.
Also, whenever I go to restart, I'm stuck at the boot logo screen and no matter which boot.img I flash, it won't go past it.
hocplyr98 said:
I've looked through other posts about this and nothing seems to help. I went to actually UNroot my Xoom so I can install the latest update because I had no use for a root, but when I went to do fastboot flash system system.img with the stock .img file, it takes forever then gives me an error... I don't know how to get past this. I just want my Xoom back to normal, even if I can get it back to a rooted normal I can live with that.
(Also, the first first time I tried unrooting, I realized I used the wrong device files. I used the Verizon ones, when I only have WiFi.)
Somebody please help me, or I feel like I have an expensive paperweight.
Also, whenever I go to restart, I'm stuck at the boot logo screen and no matter which boot.img I flash, it won't go past it.
Click to expand...
Click to collapse
Did you have ClockworkMod recovery installed? If so, do you know how to boot into CWM recovery? Disconnect from thr computer if connected, and press power and volume up to hard reboot and when you get to the dual core image, wait about three seconds, then press volume down and you should see android recovery in upper left corner, then press volume up and press power to select it.
I'm suggesting this in the hope that you did a nandroid backup before you decided to mess around and that you could somehow still access it.
If not, do you now have the correct system image files in your platforms or tools folder in order to flash from fastboot? Can you get to the "starting fastboot protocol?"
Look for your correct 3.2 wifi images here:
http://forum.xda-developers.com/showthread.php?t=1080963
Commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Good luck!
okantomi said:
Can you get to the "starting fastboot protocol" screen?
Click to expand...
Click to collapse
yes if you somehow get into fast boot your problems can be solved.
I do not know whether by pressing vol up at boot time you can go to fastboot protocol screen.
okantomi said:
Did you have ClockworkMod recovery installed? If so, do you know how to boot into CWM recovery? Disconnect from thr computer if connected, and press power and volume up to hard reboot and when you get to the dual core image, wait about three seconds, then press volume down and you should see android recovery in upper left corner, then press volume up and press power to select it.
I'm suggesting this in the hope that you did a nandroid backup before you decided to mess around and that you could somehow still access it.
If not, do you now have the correct system image files in your platforms or tools folder in order to flash from fastboot? Can you get to the "starting fastboot protocol?"
Look for your correct 3.2 wifi images here:
http://forum.xda-developers.com/showthread.php?t=1080963
Commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Good luck!
Click to expand...
Click to collapse
Not sure if I have CWM installed, but I can access fastboot and that's not really helping. I'll try again with the link you provided, but I'm able to flash everything BUT system.img. I'll try again and get back to you.
UPDATE: Yeah... It's doing the exact same thing. It's stuck at fastboot flash system system.img. It just says that it's sending it and it takes a long time before an error message pops up saying that there are too many links.
UPDATE UPDATE: Okay, now, even in fastboot, it doesn't let me flash boot.img. I don't know what to do anymore
hocplyr98 said:
Not sure if I have CWM installed, but I can access fastboot and that's not really helping. I'll try again with the link you provided, but I'm able to flash everything BUT system.img. I'll try again and get back to you.
UPDATE: Yeah... It's doing the exact same thing. It's stuck at fastboot flash system system.img. It just says that it's sending it and it takes a long time before an error message pops up saying that there are too many links.
UPDATE UPDATE: Okay, now, even in fastboot, it doesn't let me flash boot.img. I don't know what to do anymore
Click to expand...
Click to collapse
This is where you need to talk to the experts. Go to #xoom at freenode.net and get some assistance.
okantomi said:
This is where you need to talk to the experts. Go to #xoom at freenode.net and get some assistance.
Click to expand...
Click to collapse
Not very much help from the "experts" there. I was completely ignored, and nobody responded to me...
hocplyr98 said:
Not very much help from the "experts" there. I was completely ignored, and nobody responded to me...
Click to expand...
Click to collapse
It's impossible to brick a Xoom. You can make or buy a factory cable and flash stock images from Motorola and follow up with OTA upgrades or flash whatever custom stuff you desire. The below links should save your Xoom. Don't forget to hit the thanks button
http://forum.xda-developers.com/showthread.php?t=1077414
http://developer.motorola.com/products/software/?pubid=987654
http://forum.xda-developers.com/showthread.php?t=1108518
Although if you're going to give up and aren't comfortable to continue working with it I would be very interested in purchasing it, you can PM me if interested.
Saintfyre said:
Although if you're going to give up and aren't comfortable to continue working with it I would be very interested in purchasing it, you can PM me if interested.
Click to expand...
Click to collapse
Keep an eye out on ebay, I just got a xoom on there with launcher force closing repeatedly for $264
Sent from my ADR6400L using XDA App
davidsos said:
It's impossible to brick a Xoom. You can make or buy a factory cable and flash stock images from Motorola and follow up with OTA upgrades or flash whatever custom stuff you desire. The below links should save your Xoom. Don't forget to hit the thanks button
http://forum.xda-developers.com/showthread.php?t=1077414
http://developer.motorola.com/products/software/?pubid=987654
http://forum.xda-developers.com/showthread.php?t=1108518
Click to expand...
Click to collapse
Not impossible but not as likely as you would think with the 100 "I think I bricked My xoom threads floating around.
To the OP...if you do not even know whether clockwork modified recovery is installed on your device then I am not sure you have the knowledge necessary to be messing with your device...I guess most people need to learn the hard way...
I have followed the instructions on the root guide for this phone. I got the bootloader unlocked. When I got to this part:
3: reboot your phone into hboot and then into fastboot if you are not already there
4:
Code:
fastboot flash recovery recovery.img
this is presuming the recovery.img is in the same directory as fastboot, you can either move it or point the code to it directly
Click to expand...
Click to collapse
I start having problems. I can boot into hboot. Then I can choose fastboot. From there, there is no option for "flash recovery" but there is one for just "recovery." I choose that and my phone just reboots back to normal. Plus, on my last phone, when I erwad through the root guide, it went through making the recovery image, but this guide did not do that. I am a beginner (obviously), so what am I missing? I can't do the nandroid backup until it's rooted, and I don't have a backup image. Plus that thing with my phone rebooting back into normal usage after selecting " recovery" from the menu, what do I do about that?
chisao101 said:
I have followed the instructions on the root guide for this phone. I got the bootloader unlocked. When I got to this part:
I start having problems. I can boot into hboot. Then I can choose fastboot. From there, there is no option for "flash recovery" but there is one for just "recovery." I choose that and my phone just reboots back to normal. Plus, on my last phone, when I erwad through the root guide, it went through making the recovery image, but this guide did not do that. I am a beginner (obviously), so what am I missing? I can't do the nandroid backup until it's rooted, and I don't have a backup image. Plus that thing with my phone rebooting back into normal usage after selecting " recovery" from the menu, what do I do about that?
Click to expand...
Click to collapse
Read there, begin with #791. Same problem with rooting like you.
old.splatterhand said:
Read there, begin with #791. Same problem with rooting like you.
Click to expand...
Click to collapse
Thanks. So if I want to flash a new ROM, do I do it the same way? Do I need to open the CMD prompt and type in those same commands, but point it to the ROM I want?
chisao101 said:
Thanks. So if I want to flash a new ROM, do I do it the same way? Do I need to open the CMD prompt and type in those same commands, but point it to the ROM I want?
Click to expand...
Click to collapse
You need the CMD prompt to flash a recovery and from recovery you can flash Superuser to become root or flash roms (from recovery).
old.splatterhand said:
Read there, begin with #791. Same problem with rooting like you.
Click to expand...
Click to collapse
old.splatterhand said:
You need the CMD prompt to flash a recovery and from recovery you can flash Superuser to become root or flash roms (from recovery).
Click to expand...
Click to collapse
Ok, this is what's happening now. I hold the volume down key and power key. It boots into hboot (i think that's what it's called). I scroll down to recovery and hit the power key. It immediately goes to the logo screen with a message that says "This build is for development purposes only. Do not distribute outside of HTC ithout HTC's written permission. Failure to comply may lead to legal action."
It just stays there until I remove the battery and start over.
Am I missing a step?
chisao101 said:
Ok, this is what's happening now. I hold the volume down key and power key. It boots into hboot (i think that's what it's called). I scroll down to recovery and hit the power key. It immediately goes to the logo screen with a message that says "This build is for development purposes only. Do not distribute outside of HTC ithout HTC's written permission. Failure to comply may lead to legal action."
It just stays there until I remove the battery and start over.
Am I missing a step?
Click to expand...
Click to collapse
What have you done? Fastboot flash recovery recovery.img?
The recovery you need, is in fastboot folder on pc, renamed to recovery.img?
chisao101 said:
Ok, this is what's happening now. I hold the volume down key and power key. It boots into hboot (i think that's what it's called). I scroll down to recovery and hit the power key. It immediately goes to the logo screen with a message that says "This build is for development purposes only. Do not distribute outside of HTC ithout HTC's written permission. Failure to comply may lead to legal action."
It just stays there until I remove the battery and start over.
Am I missing a step?
Click to expand...
Click to collapse
Am I supposed to type into the cmd prompt again: "flashboot flash recovery superuser.zip"?
old.splatterhand said:
What have you done? Fastboot flash recovery recovery.img?
The recovery you need, is in fastboot folder on pc, renamed to recovery.img?
Click to expand...
Click to collapse
Yes, this is exactly what I did.
chisao101 said:
"flashboot flash recovery superuser.zip"?
Click to expand...
Click to collapse
Don't type this!!!
This can brick your device!
Now, what cmd did you use, look at the prompt.
The recovery seems not to be flashed correctly, thats why it is not booting to recovery!
And look, how it is written: fastboot not flashboot
Copy and paste, otherwise you can damage your phone!
old.splatterhand said:
Don't type this!!!
This can brick your device!
Now, what cmd did you use, look at the prompt.
The recovery seems not to be flashed correctly, thats why it is not booting to recovery!
And look, how it is written: fastboot not flashboot
Copy and paste, otherwise you can damage your phone!
Click to expand...
Click to collapse
Ok, I made a folder on my PC:
C:\Android
Inside that folder I have these files:
adb.exe
AdbWinApi.dll
CMD starten
fastboot.exe
Superuser.zip
trecovery.img
I moved these files to my SD card:
trecovery.img (renamed to recovery.img)
Superuser.zip
I started my phone holding the volume down, and it booted to the hboot screen with a menu that has these items:
fastboot
recovery
factory reset
clear storage
simlock
image crc
show barcode
I selected "fastboot" from the menu, and it went to a new menu with these menu items:
bootloader
reboot
reboot bootloader
power down
I plugged the phone into the USB.
I clicked the CMD starten
I typed this:
fastboot flash recovery recovery.img
I hit enter and got this message in the CMD prompt:
sending 'recovery' (7456 KB)...
OKAY [ 1.042s]
writing 'recovery'...
OKAY [ 1.988s]
finished. total time: 3.031s
C:\Android>
When I go back to the previous menu and select "recovery" it just boots and hangs on the HTC One screen. If I take the battery out and reboot normal, it works fine with my stock Android install, like nothing happened.
chisao101 said:
I moved these files to my SD card:
trecovery.img (renamed to recovery.img)
Click to expand...
Click to collapse
The recovery.img must be in same folder as fastboot.exe, on pc, not in sdcard!
But i don't what you have flashed then...
old.splatterhand said:
The recovery.img must be in same folder as fastboot.exe, on pc, not in sdcard!
But i don't what you have flashed then...
Click to expand...
Click to collapse
I just went through the whole process again and it is working now! I must have missed something the first time.
So after it booted into recovery, I saw where it says "install zip from SD card"
I looked up the superuser.zip and installed it. It seemed to go ok, and it is rebooting now.
So this just means that the phone is now rooted, correct?
chisao101 said:
I just went through the whole process again and it is working now! I must have missed something the first time.
So after it booted into recovery, I saw where it says "install zip from SD card"
I looked up the superuser.zip and installed it. It seemed to go ok, and it is rebooting now.
So this just means that the phone is now rooted, correct?
Click to expand...
Click to collapse
You can check, if you have a Superuser app in appdrawer.
But i see, you are on boost, which recovery did you flash?
Give me the link to the thread, please! Cause boost need its own recovery!
old.splatterhand said:
You can check, if you have a Superuser app in appdrawer.
But i see, you are on boost, which recovery did you flash?
Give me the link to the thread, please! Cause boost need its own recovery!
Click to expand...
Click to collapse
ClockworkMod Recovery for ICS, which is linked to : https://www.dropbox.com/s/tgcdztlzmi2bd35/trecovery.img
I got it from that guide that you sent me to earlier in this thread. That's the same guide I was already using before I started the thread too.
Where can I find the correct recovery for Boost?
chisao101 said:
ClockworkMod Recovery for ICS, which is linked to : https://www.dropbox.com/s/tgcdztlzmi2bd35/trecovery.img
I got it from that guide that you sent me to earlier in this thread. That's the same guide I was already using before I started the thread too.
Where can I find the correct recovery for Boost?
Click to expand...
Click to collapse
It did not install the superuser correctly because it's not in my app drawer.
I also noticed that the recovery menu is kinda shifted to the side a little bit, so it's hard to read until I start scrolling. Yeah, this has to be the wrong recovery.
You can use this or the boost variant from here.
old.splatterhand said:
You can use this or the boost variant from here.
Click to expand...
Click to collapse
That first link doesn't work. It goes to the right thread, but when you go to download the file, it is not found.
I got the other one, and I'm about to flash it.
Any suggestions for a stable version of JB for this phone?
P.S. Thanks for all your help. You have been awesome!
chisao101 said:
That first link doesn't work. It goes to the right thread, but when you go to download the file, it is not found.
I got the other one, and I'm about to flash it.
Any suggestions for a stable version of JB for this phone?
P.S. Thanks for all your help. You have been awesome!
Click to expand...
Click to collapse
There is only one jb for boost i know and you have to be S-off for it.
old.splatterhand said:
There is only one jb for boost i know and you have to be S-off for it.
Click to expand...
Click to collapse
Will the unrevoked3 tool work for this phone to get S-off? I just read about it, and this looks like it's for the EVO and a couple of other phones, but it's not clear on whether I can use it on the One SV.
chisao101 said:
Will the unrevoked3 tool work for this phone to get S-off? I just read about it, and this looks like it's for the EVO and a couple of other phones, but it's not clear on whether I can use it on the One SV.
Click to expand...
Click to collapse
No, don't do this!!!
Moonshine S-off. But there i could not assist, i used another method which is not available for boost.
Edit:
Wooooot, Post Number 1000!
Hoping someone can help. I've unlocked bootloader easily, however, im having a problem flashing recovery. Each time i get failed remote error image is not a boot image....it starts to write and then fails. ive tried with cwm and twrp. i am placing the file in my adb folder, and renaming it to recovery.img so really i dont know whats wrong. never had this issue ever before. i checked to see if it was flashed, and nothing was there, showing a dead robot with an exclamation. cannot figure it out!
it goes in the same folder on your computer as where fastboot is located. then fastboot flash recovery recovery.img
I have fastboot, adb and recovery image in the same folder on my desktop.
mgf8384 said:
I have fastboot, adb and recovery image in the same folder on my desktop.
Click to expand...
Click to collapse
the android laying on its back is the stock recovery btw. did you rename the recovery properly? is it still an img file?
mgf8384 said:
Each time i get failed remote error image is not a boot image....
Click to expand...
Click to collapse
Its not a boot image, Its a recovery image. You sure your typing the correct command?
Esit: Just done some googling and someone had the same problem. Was due to a bad download.
Edit 2: ah just read again and you said you tried 2 types of recovery. Scrap my 1st edit then?
Sent from my Nexus 5 using XDA mobile app
mgf8384 said:
Hoping someone can help. I've unlocked bootloader easily, however, im having a problem flashing recovery. Each time i get failed remote error image is not a boot image....it starts to write and then fails. ive tried with cwm and twrp. i am placing the file in my adb folder, and renaming it to recovery.img so really i dont know whats wrong. never had this issue ever before. i checked to see if it was flashed, and nothing was there, showing a dead robot with an exclamation. cannot figure it out!
Click to expand...
Click to collapse
You'll just be doing wrong and no, nothing needs to be in the same folder of you installed it properly. Click the link in my signature to the sticky thread and read my adb and fastboot thread.
Also ensure "hide known file extensions" is turned off in windows.
If you need more help, you should post screenshots of your cmd window.
Sent from my Nexus 5 using Tapatalk
Thank you all. Setting somewhere in my PC I think. When .img.img was typed it worked. ( i tried fastboot flash recovery rec and then hit tab) Checked properties in the recovery zip and it's named just recovery.img so don't understand why it had to be typed twice? If anyone knows please tell me so I can correct it.
mgf8384 said:
Thank you all. Setting somewhere in my PC I think. When .img.img was typed it worked. ( i tried fastboot flash recovery rec and then hit tab) Checked properties in the recovery zip and it's named just recovery.img so don't understand why it had to be typed twice? If anyone knows please tell me so I can correct it.
Click to expand...
Click to collapse
the way it was renamed.
There's no need to rename it....for future flashes.
KJ said:
There's no need to rename it....for future flashes.
Click to expand...
Click to collapse
i rename it to simple 3-4 letter words, for ease of typing
simms22 said:
i rename it to simple 3-4 letter words, for ease of typing
Click to expand...
Click to collapse
Just brought it up, cause in this case...he wouldn't have had an issue if he left it.
But yeah, I do that too. Lol
mgf8384 said:
Thank you all. Setting somewhere in my PC I think. When .img.img was typed it worked. ( i tried fastboot flash recovery rec and then hit tab) Checked properties in the recovery zip and it's named just recovery.img so don't understand why it had to be typed twice? If anyone knows please tell me so I can correct it.
Click to expand...
Click to collapse
Because you had "hide file extensions" on in windows like I said.
File was called whatever.img but you can only was whatever because. .img is hidden. So when you rename it, it only let's you rename whatever (leaving .img hidden and unchanged) so you rename what's visible to recovery.img and results are obvious
(whatever).img > (recovery.img).img
So the quick lesson - turn off "hide known file extensions" in windows. Not just for this reason but for your own security. .exe files with word doc icons etc
Sent from my Nexus 5 using Tapatalk
---------- Post added at 08:42 AM ---------- Previous post was at 08:41 AM ----------
simms22 said:
i rename it to simple 3-4 letter words, for ease of typing
Click to expand...
Click to collapse
Or type first letter or two then press tab
Sent from my Nexus 5 using Tapatalk
Hello everyone.
I had to move back to the factory image because of a bad flash. After resetting, i try to install TWRP or CWM using fastboot. The recovery works the first time its installed, but goes away when I reboot my phone. By goes away i mean I see googles recovery (dead robot) once I reboot the phone and then boot into recovery.
I tried to flash a ROM while TWRP works but once I do, I cant see any of my files on the SD card. This means I cannot flash anything even if I booted in TWRP and this brings me back around to flashing the factory image.
Any help is much appreciated.
siddjazz said:
Hello everyone.
I had to move back to the factory image because of a bad flash. After resetting, i try to install TWRP or CWM using fastboot. The recovery works the first time its installed, but goes away when I reboot my phone. By goes away i mean I see googles recovery (dead robot) once I reboot the phone and then boot into recovery.
I tried to flash a ROM while TWRP works but once I do, I cant see any of my files on the SD card. This means I cannot flash anything even if I booted in TWRP and this brings me back around to flashing the factory image.
Any help is much appreciated.
Click to expand...
Click to collapse
Go to general and read the sticky thread about 5.0 roms and recovery
So I bought my shield tablet back in March, used it until about may I think. Was browsing the internet then it suddenly crashed and got stuck on the Nvidia boot screen. tried to reboot several times. Nothing. So I forgot about it and thought I would just google the reset option later when I had time. Now since June I have tried everything! From factory reset to fast boot and adb my pc won't even recognize my tablet. Also I never turned on usb dbugging cause I didn't even know what that was. I even gave it to the IT guys at work and they couldn't fix it. Now after reading everything there is to read on this problem and trying to fix it myself I'm stuck on the no command screen with the dead android robot. And now I hear there is a recall do to the battery, I can't even check what type I have. So if someone can please help me I would be much appreciative. Also this happened after updating to the latest OS.
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Can you flash twrp and boot to it?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Hello,
Did you use "Fastboot flash recovery.img" as your command line??
I believe it is "Fastboot flash recovery recovery.img"
If you were able to unlock bootloader you're on the right track.
Sent from a Locked Bootloader
Yes I used "fastboot flash recovery recovery.img" but every command after that keeps telling me "failed to write file"
danjull said:
Can you flash twrp and boot to it?
Click to expand...
Click to collapse
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Ace0169 said:
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Click to expand...
Click to collapse
TWRP (Team Win Recovery Project) is a custom recovery that you can flash on your device. You can flash it like the stock recovery over fastboot. With TWRP you can make full system backups, installing roms or other stuff, wipe partitions and more. Keep trying to install the drivers on your pc. Try to use another usb slot or boot your pc into test mode to install the driver. If you can still access the bootloader, you have really good chances to rescue your device.
Okay will try that. Thanks man.
Ace0169 said:
Okay will try that. Thanks man.
Click to expand...
Click to collapse
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Mojar7070 said:
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Click to expand...
Click to collapse
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
Those official nVidia recovery images come with smaller .img files such as recovery.img, system.img, etc. You'll need to flash those one by one ("fastboot flash recovery recovery.img", then run "fastboot flash system system.img", etc. etc.) or you can just run the flashall script that I think is included in the nVidia images.
Otherwise, if you want to flash TWRP, you'll need to download the TWRP recovery (you can rename it to "twrp-recovery.zip"). Then you'll need to "fastboot flash twrp-recovery.zip" in order to flash the twrp recovery to your tablet.
Mojar7070 said:
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Click to expand...
Click to collapse
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Ace0169 said:
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Click to expand...
Click to collapse
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Mojar7070 said:
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Click to expand...
Click to collapse
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Ace0169 said:
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Click to expand...
Click to collapse
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
koop1955 said:
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
Click to expand...
Click to collapse
Select "fastboot protocol"? Is that correct?
Ace0169 said:
Select "fastboot protocol"? Is that correct?
Click to expand...
Click to collapse
So i selected "fastboot protocol" it blipped for a second then brought me back to the bootloader. tried flashing again and once i reached the fastboot flash system system.img it said write failed again. did it not engage the "fastboot protocol"?
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
koop1955 said:
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
Click to expand...
Click to collapse
@Ace0169 Same, not sure what else to tell you. Sorry sir.
Sent from a Locked Bootloader
My wife's Rooted Nexus 5, stock 6.0.1 phone has become unusable. After deleting some contacts she gets a popup that "Android.process.acore has stopped" every couple of seconds.
Searching for solutions on the web I've
Deleted her contacts data and cache
Deleted her contacts storage data and cache
Reset app preferences
Disabled contacts
And nothing stops it.
Is there a solution to this problem?
Thanks.
Is it possible to restore a working nandroid made on a different nexus 5 to the messed up nexus 5?
maybeme2 said:
My wife's Rooted Nexus 5, stock 6.0.1 phone has become unusable. After deleting some contacts she gets a popup that "Android.process.acore has stopped" every couple of seconds.
Searching for solutions on the web I've
Deleted her contacts data and cache
Deleted her contacts storage data and cache
Reset app preferences
Disabled contacts
And nothing stops it.
Is there a solution to this problem?
Thanks.
Is it possible to restore a working nandroid made on a different nexus 5 to the messed up nexus 5?
Click to expand...
Click to collapse
you need to flash again the stock rom. try using nexus toolkit.
https://forum.xda-developers.com/google-nexus-5/development/toolkit-wugs-nexus-root-toolkit-v1-8-3-t2517778
you can get the stock roms here.
https://forum.xda-developers.com/google-nexus-5/development/rom-android-m-preview-2-flashable-zip-t3157299
Thank you. I thought I might need to reflash the rom. I was trying to avoid it because flashing roms always makes me nervous. But I'll just have to do it.
Xposed is also installed on the phone. I assume I will need to uninstall that first too. Ugh!
maybeme2 said:
Thank you. I thought I might need to reflash the rom. I was trying to avoid it because flashing roms always makes me nervous. But I'll just have to do it.
Xposed is also installed on the phone. I assume I will need to uninstall that first too. Ugh!
Click to expand...
Click to collapse
Try flashing just the system image and not the whole rom. You'll be able to save all your apps and data that way.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Try flashing just the system image and not the whole rom. You'll be able to save all your apps and data that way.
Click to expand...
Click to collapse
That would be great!
Never done that. I'll search the web for just the 6.0.1 system image. I assume that's different from the "factory image" from https://developers.google.com/android/images
Could you point me in the right direction?
maybeme2 said:
That would be great!
Never done that. I'll search the web for just the 6.0.1 system image. I assume that's different from the "factory image" from https://developers.google.com/android/images
Could you point me in the right direction?
Click to expand...
Click to collapse
Download the factory image, it's a zip file. Extract it and inside is another zip file. Extract that too. Inside that are a number of .img files, one of which is the system.img. You'll use that one. Use fastboot to flash it, fastboot flash system system.img. If you've never used fastboot Google "15 second adb xda" The first thing that should pop up is a tool by Snoop05. That'll install fastboot and adb on your PC.
Sent from my [device_name] using XDA-Developers Legacy app
You are wonderful jd1639. Thank you very much.
What you suggested worked like a charm. I flashed the system.img successfully. Took no time.
Unfortunately, it did not solve the Android.process.acore bug.
So I decided to just flash the entire rom and go that route. That's where I ran into problems.
1. I did adb reboot bootloader
and then flash-all
which resulted in something about system img not found (even though I had moved everything into the same folder).
Now, the phone is now no longer rooted and I can no longer get into recovery. And adb reboot bootloader no longer works. I get "error device offline".
I'm not that knowledgeable in android and flashing and am stuck. What should I do?
Ok, solved the offline problem. Disconnected and reconnected the USB cable.
But still no go. Here's what I get with flash-all
For some reason my paste of the results won't show when I save.....
Essentially,
Ok, solved the offline problem. Disconnected and reconnected the USB cable.
But still no go. Here's what I get with flash-all
For some reason my paste of the results won't show when I save.....
Essentially, it says archive does not contain 'boot.sig', archive does not contain 'recovery.sig'.
Sorry, error.
maybeme2 said:
Sorry, error.
Click to expand...
Click to collapse
The no .sig stuff is normal and you don't need to worry about it. Just ignore it and let the flash continue and do its thing.
Let me know if that works.
Sent from my [device_name] using XDA-Developers Legacy app
Unfortunately, I can't ignore it because it stops with "press any key to exit". So I exit.
Wish you lived next door. I would be glad to pay you to do it.....
maybeme2 said:
Unfortunately, I can't ignore it because it stops with "press any key to exit". So I exit.
Wish you lived next door. I would be glad to pay you to do it.....
Click to expand...
Click to collapse
Does it flash anything before it gets to the press and key? It should flash the bootloader and modem before it gets to the .sig stuff. Or does it immediately go to the press any key? If it goes immediately to the press any key then it sound like the PC isn't recognizing the N5. If that's the case boot into the bootloader, press power and vol up and down keys at the same time. Once it boots into the bootloader then connect it to your PC. Then using fastboot issue the command, fastboot devices If your PC recognizes the N5 it'll spit out a long alpha/numeric number on your pc. About 16 characters long.
If you get the alpha/numeric then go to the folder of the second zip file you extracted. There should be boot, cache, etc image files. Then open a command window /power shell there and we'll flash all the partitions manually. Issue the following commands, one after the other once the previous one ends.
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
If any of those don't work let me know which one.
Sent from my [device_name] using XDA-Developers Legacy app
Thank you again.
Thank you jd1639.
All the flashing worked when I did it sequentially as you suggested. Don't know why the batch file got stuck but no matter, you saved the day.
So it is now factory fresh. Please remind me how to root it.
Thank you so much for hanging in there to help a total stranger.
maybeme2 said:
Thank you jd1639.
All the flashing worked when I did it sequentially as you suggested. Don't know why the batch file got stuck but no matter, you saved the day.
So it is now factory fresh. Please remind me how to root it.
Thank you so much for hanging in there to help a total stranger.
Click to expand...
Click to collapse
No problem. To root download twrp for the N5. I Google teamwin nexus 5. It'll be a .img file. Also download supersu. Google supersu 2.82 sr5. To flash twrp boot into the bootloader and with fastboot flash it, fastboot flash recovery twrp.img. Twrp.img is the full file name of the download. Then boot into recovery (it'll be twrp). From recovery your PC will see the N5 and you'll be able to copy supersu to the download folder of the N5. Then flash it in twrp (install) supersu will be a zip file.
Sent from my [device_name] using XDA-Developers Legacy app
Problems never end.
1. I successfully flashed twrp.img using fastboot. But when I go to recovery I get the empty robot with the red exclamation mark. (No twrp recovery)
2. Other problem: the 32Gb nexus 5 now shows only 16Gb.
maybeme2 said:
Problems never end.
1. I successfully flashed twrp.img using fastboot. But when I go to recovery I get the empty robot with the red exclamation mark. (No twrp recovery)
2. Other problem: the 32Gb nexus 5 now shows only 16Gb.
Click to expand...
Click to collapse
Yep, you're having fun. The problem is twrp is not sticking. But first let's solve the memory issue, which is fairly common. The red ! Is the stock recovery. It's been awhile since I've messed with it so you might have to play around with it a little. When you get the ! Press and release the power and vol up keys. Timing is important so that's where the playing around comes in. It might be vol down or both vol. If you get it right it'll go into the stock recovery, don't ask why you need to mess with the keys and it won't just go into recovery and not go through the ! crap.
Anyway, once you get into recovery go to factory reset and reset the device. That will solve the memory issue.
Now to twrp, instead of flashing twrp you'll want to boot into it. Use fastboot and the command fastboot boot twrp.img. Once in twrp get supersu on your device and then flash it. Then go to reboot in twrp and boot into the bootloader. Then use fastboot to flash twrp, fastboot flash recovery twrp.img. Twrp should stick now.
Edit: to get into stock recovery it's power and both vol keys. Press, hold about 1/2 second, and release.
Sent from my [device_name] using XDA-Developers Legacy app
Yes I'm having fun...... (that's why non-experts are scared to do things which the experts say "not to it - which is true when everything works)
The 32Gb becoming 16 is a problem I encountered previously on another nexus 5. So I noted its solution : the fix is to wipe cache and data. Catch 22: how to do that when you can't get into recovery? I was going to search for a way to wipe cache and data using fastboot when I read your message.
I'll try to do what you advise. Fingers crossed.