Database Users

Solved:I guess I'm stuck in boot loop....now what?

Ok guys..... newbie here .... literally I'm new to Boot unlocking, root, Flashing etc.
Anyway I have followed this forum for so long that I decided to take plunge yesterday and get my hands dirty.
Here is what I did:
Unlock bootloader, root and install recovery on my Atrix 4G. Atrix was @ 2.3.4 and 4.5.91 during unlocking & root.
Rebooted the phone and everything seems to be in place. Atrix loaded like the way I bought it 7 months back. No problem until now.
Also created a restore folder on my external SD. Worked fine and was successful in creating backup with time stamp
Now here are my steps and subsequent issues that I'm facing:
1. Downloaded CM9 zip file from this thread(http://forum.xda-developers.com/showthread.php?t=1500535) along with Gapps to my external SD
2.Entered recovery mode during bootup and tried to flash CM9 and Gapps. Flashing seem to have gone well and completed (note I did not do clear data, clear cache or clear dalvik cache under advanced options being a newbie)
3. Reboot the phone and can only see red Moto logo and unlocked on top. Left for about 5 minutes and nothing happened.
4.Did a battery pull and entered recovery mode. wiped data, cache & cleared dalvik cache
5.Went to Install zip from sdcard option and tried to reflash CM9. Flashing seems to have gone well and completed
6. Reboot phone and again can only see Moto Red logo with unlock on top and nothing more.
7.Battery pull followed by recovery. But This time I tried to restore from my external SD. also wiped data, cache & dalvik cache
8.Restore took about 3 minutes and completed.
9.Reboot the phone. Now the phone boots and goes to Rethink possible screen and get sstuck.
10. Left it for 1 hr....nothing.
11.tried steps 7-9 again and still stuck in "Rethink possible" screen during boot.
What did I do wrong? Did I soft brick the phone? I can still enter recovery mode and read my internal and external SD and can see all files. i hope I didn't brick my phone doing this. If I did, I would regret!
Here are my options:
1.Try a stable ROM like CM7 and see what happens. I didn't want to do too much damage so haven't tried this option yet.
2.I know there is a way to hide 'unlock' during boot up (if someone can point to it obviously). Hide the 'unlock' and return the phone to ATT and tell them that phone would not boot after 2.3.6 update and get a refurbished one
Please let me know what your thoughts are. I'm currently crapping on my pants
Edit: I just tried Newtrino rom and stuck @ Moto screen which says unlock.
Edit 3/4/2012: Please go to the last post for the solution. Tenfar's CWM is old and cannot deal with latest ROMs. Use ROMRACERS latest CWM or touch based Koush's CWM for future ROM flashing.
Old CWMs will give you sleepless nights!

Ok tried restore again after wiping data, cache & dalvik cache.
Now after reboot, My Moto Logo screen says unlock and just starts flashing.
I can still get into recovery......
can someone please help me......

What you can do is: install a "stable" ROM of Gingerbread:
--Go in recovery, put a .zip of the ROM on your sdcard (with your computer), and after wiping data, install it .zip.
--Or you install a new ROM with fastboot
Anyway, be careful with your battery, because if it is empty, with no ROM on your phone, it'll be crap!

vsg005 said:
What you can do is: install a "stable" ROM of Gingerbread:
--Go in recovery, put a .zip of the ROM on your sdcard (with your computer), and after wiping data, install it .zip.
--Or you install a new ROM with fastboot
Anyway, be careful with your battery, because if it is empty, with no ROM on your phone, it'll be crap!
Click to expand...
Click to collapse
thank you for your response. However I tried that already Nutrino GB ROM. Again, I would go to 'M' screen which says unlocked and its stuck there for ever.
I used tenfar's CWM. Not sure if I need to use any other CWM. Also since my phone doesn't boot, I'm not sure how I can install any other CWM

Masterguy said:
thank you for your response. However I tried that already Nutrino GB ROM. Again, I would go to 'M' screen which says unlocked and its stuck there for ever.
I used tenfar's CWM. Not sure if I need to use any other CWM. Also since my phone doesn't boot, I'm not sure how I can install any other CWM
Click to expand...
Click to collapse
Don't worry, soft bricks are easy to recover on the Atrix thanks to us being able to access fastboot.
For flashing a new recovery:
While your phone is off, press Volume Up + Power to power up, then release when a menu appears on your screen and navigate with volume down until you see Fastboot, select it with the volume up key.
Get the necessary files for fastboot, place them all in a folder called "moto" in your C: drive, and type in the following in a cmd window (assuming you're using windows and that the recovery image is called recovery.img):
C:/Moto> fastboot flash recovery recovery.img
C:/Moto> fastboot -w
C:/Moto> fastboot reboot
Now access your recovery wipe dalvik cache, cache, factory reset and then flash a new ROM. It SHOULD boot without issues. I personally use Koush's Clockworkmod Touch, also remember that Neutrino tends to get "stuck" sometimes after the first attempt to boot and requires a battery pull and then you try to boot again. (It takes a while)

littleemp said:
Don't worry, soft bricks are easy to recover on the Atrix thanks to us being able to access fastboot.
For flashing a new recovery:
While your phone is off, press Volume Up + Power to power up, then release when a menu appears on your screen and navigate with volume down until you see Fastboot, select it with the volume up key.
Get the necessary files for fastboot, place them all in a folder called "moto" in your C: drive, and type in the following in a cmd window (assuming you're using windows and that the recovery image is called recovery.img):
C:/Moto> fastboot flash recovery recovery.img
C:/Moto> fastboot -w
C:/Moto> fastboot reboot
Now access your recovery wipe dalvik cache, cache, factory reset and then flash a new ROM. It SHOULD boot without issues. I personally use Koush's Clockworkmod Touch, also remember that Neutrino tends to get "stuck" sometimes after the first attempt to boot and requires a battery pull and then you try to boot again. (It takes a while)
Click to expand...
Click to collapse
Many people also seem to have suggested RACEROM CWM. Which one would you suggest? I'm so nervous about all this now. Just have this butterfly in my stomach

flash the latest recovery and wipe everything in recovery and flash neutrino again. It should work after that. try neutrino 2.2 though. 2.5 still has it's kinks.

1st off, relax. It's difficult to brick your phone from this point Just don't get any bright ideas with .sbfs lol.
As others have said, make sure you're on latest recovery.
Question: are you installing from internal or external SD? Internal is recommended for flashing most ROMs.
Sent from my MB860 using xda premium

Masterguy said:
Many people also seem to have suggested RACEROM CWM. Which one would you suggest? I'm so nervous about all this now. Just have this butterfly in my stomach
Click to expand...
Click to collapse
As someone else said, the ONLY thing you should NEVER do is flash an .sbf or go through an OTA update, that's a surefire way to hard brick your phone. From this point on it's VERY DIFFICULT to completely brick your phone using software only.
RomRacer's CWM is based I think on v5.0.2.7? Koush's latest recovery is v5.8.1.5. I honestly couldn't name any tangible differences other than the touch interface, which is the reason I use it in the first place. (I hate mashing volume keys like a madman) It really doesn't matter which CWM you use, but when I soft bricked my phone I recovered with CWM Touch.
I would recharge your battery to 100% before trying to recover it, as that is one less headache to worry about, but if your phone starts saying 'Battery is too low to flash', do not panic, you only need a USB cable you don't mind sacrificing (doesn't have to be new). I will go into detail in case you actually need to do this.
Just make sure you use the fastboot -w command and wipe EVERYTHING through CWM before trying to flash anything else.

Solved:boot loop issue
littleemp said:
As someone else said, the ONLY thing you should NEVER do is flash an .sbf or go through an OTA update, that's a surefire way to hard brick your phone. From this point on it's VERY DIFFICULT to completely brick your phone using software only.
RomRacer's CWM is based I think on v5.0.2.7? Koush's latest recovery is v5.8.1.5. I honestly couldn't name any tangible differences other than the touch interface, which is the reason I use it in the first place. (I hate mashing volume keys like a madman) It really doesn't matter which CWM you use, but when I soft bricked my phone I recovered with CWM Touch.
I would recharge your battery to 100% before trying to recover it, as that is one less headache to worry about, but if your phone starts saying 'Battery is too low to flash', do not panic, you only need a USB cable you don't mind sacrificing (doesn't have to be new). I will go into detail in case you actually need to do this.
Just make sure you use the fastboot -w command and wipe EVERYTHING through CWM before trying to flash anything else.
Click to expand...
Click to collapse
Thanks I was able to fix my boot up issue using ROMRACERS CWM. I didn't use any command prompt or anything. I just downloaded zip file from this thread, entered recovery mode -->Install Zip from SD card --> Chose ROMRACERS zip --> it automatically flashed the recovery and I then rebooted recovery under advanced options.
After that Wiped data,cache & Dalvik Cache and proceeded to install CM9 and it booted up up flawlessly.
I'm kind of surprised that tenfar didn't add a not to use his CWM as the latest ROMs use latest ext format.
That seems to be issue. However, I'm pleased with your guidance and final output. Thanks a lot dude.

Masterguy said:
Thanks I was able to fix my boot up issue using ROMRACERS CWM. I didn't use any command prompt or anything. I just downloaded zip file from this thread, entered recovery mode -->Install Zip from SD card --> Chose ROMRACERS zip --> it automatically flashed the recovery and I then rebooted recovery under advanced options.
After that Wiped data,cache & Dalvik Cache and proceeded to install CM9 and it booted up up flawlessly.
I'm kind of surprised that tenfar didn't add a not to use his CWM as the latest ROMs use latest ext format.
That seems to be issue. However, I'm pleased with your guidance and final output. Thanks a lot dude.
Click to expand...
Click to collapse
Thank you sooo much. I was having this exact problem. I did what you suggested and my phone works. Thanks!

stuck in recovery

i flashed the CWM update zip, booted into CWM, wiped, and now im trying to install the EOS rom
it goes smoothly and i get no errors, but it boots into CWM every single boot now.,,

Pushed the older 6006 cwm and flashed, no errors, still boots into 6010.. ?

http://forum.xda-developers.com/showthread.php?p=22897771
Found this thread. For transformer Prime but hopefully it fixes my issue. If this is a bad idea lmk.
If not, Will try around midnight when I get back home

Woops,
Found this too
http://forum.xda-developers.com/showthread.php?t=1781250

Did you flash the CWM.zip in TWRP? I ask because there was a known issue when flashing CWM from TWRP you would get stuck in a recovery loop. I had the same issue and had to flash the stock .img to get out of it. Good luck.

i flashed the CWM zip that was posted in the CWM thread, bout to try and get myself free..
::success.
booted into bootloader
flashed bootloader, restarted, booted into my rom...
rebooted back into bootloader
flashed recovery
wipe/flash normally

I'm in the same exact situation, Could you share with me how you got it to boot into bootloader? I've been trying for awhile now. As I'm stuck in CWM I'm thus far unable to use adb. I'm a total adb noob so there is probably something quite simple I'm missing. Thanks in advance for any help.

Vektor67 said:
I'm in the same exact situation, Could you share with me how you got it to boot into bootloader? I've been trying for awhile now. As I'm stuck in CWM I'm thus far unable to use adb. I'm a total adb noob so there is probably something quite simple I'm missing. Thanks in advance for any help.
Click to expand...
Click to collapse
Press volume down when it boots (right before and while the Google logo shows up)

jamesst20 said:
Press volume down when it boots (right before and while the Google logo shows up)
Click to expand...
Click to collapse
Thanks for the reply, I've tried that many times. It's not working. I wish I had read this thread carefully and learned that it might be dangerous to flash cwm zip from TWRP, I had no idea.
The thing is is that it never really shuts down properly(thought I remembered a power off option on one of my epic 4g cwm) So when I press the power button while on the reboot system now option, that is what it does but back to recovery. I tried the volume button as you suggested as well as every other combination I could think of. :~(

Well in messing with drivers(uninstalling old drivers/devices installing universal naked driver) I had the nexus 7 q3 tool waiting for adb to enter fastboot and reflash TWRP so I could restore) and the tool suceeded in kicking me into fastboot(with an error in the toolkit) The toolkit stopped communicating though. I want to use the toolkit to reflash back to stock now that I'm in the bootloader screen.
I'm a bit nervous though, some warning about flashing asus stock blobs being a sure way to HardBrick. I think I'll wait until I get better information. I am on the bootloader screen, but I'm certain my bootloader as it sits is messed up from flashing CWM.
*Edit* Success!! I used this ; "[Guide] Returning to Stock and/or Unbricking your device"located here, http://forum.xda-developers.com/showthread.php?t=1781250 (not sure how to go about inserting a descriptive link sry :~( I'm now back to stock and ready to brick it again...umm, I mean, root and flash like there's no tomorrow. hehe Thanks for the input.:good::good:

[Q] All methods of factory/hard reset seem to work, but then boots into old system

I'm having the weirdest problem and I'm wondering whether it is hardware or software. I have searched everywhere and only found one person with a similar situation and he had already sent it back for repair before anyone responded with things for him to try.
My 16gb Nexus 7 is rooted/unlocked using the Nexus Root Toolkit and at the latest OTA version. It had been working fine for months. Suddenly one day I had serious problems (which I can discuss if anyone cares, but I don't think the original problems are relevant at this point.) I gave up troubleshooting and decided to do a factory reset. But no matter what method I do, the next time I boot the device it comes back into my same buggy system and nothing was wiped or reset at all. All of these methods appear to work and give the normal messages you would expect, but then nothing changed. It's like the Flash ram is somehow set to read-only so attempts to write to it are failing.
What I have tried:
Settings Factory Data Reset and press the Erase Everything button. The tablet pauses a while, then shuts down and reboots. The old system comes back.
I go into recovery mode, choose function wipe data/factory reset, scroll down to Yes to confirm it. A bunch of progress messages show on the screen that the partitions are being formatted. I boot afterwards and the old system comes back.
I follow all the steps in articles like this: http://forum.xda-developers.com/showthread.php?t=1907796
Every fastboot command completes normally with progress messages showing that it worked. I reboot and the old system comes back.
Here is another clue: The fastboot oem lock command completes normally, but nothing changes. The padlock icon at the next boot is still open.
That's why I say that the tablet is acting as though the Flash memory is set to read-only somehow because nothing ever changes. Is it possible that this is a hardware problem, or is there something else I can do in software?

Bump One for OP
hope your problem gets solved...

I go into recovery mode, choose function wipe data/factory reset, scroll down to Yes to confirm it. A bunch of progress messages show on the screen that the partitions are being formatted. I boot afterwards and the old system comes back.
Click to expand...
Click to collapse
1. If you wipe this way and then do not install another rom, then the old system will just reload.
2. Which recovery are you using TWRP or CWM? Maybe try an alternative recovery?
3. Go into recovery/mounts and storage/ then select format system and then install another rom such as stock and see what happens..

killall said:
1. If you wipe this way and then do not install another rom, then the old system will just reload.
2. Which recovery are you using TWRP or CWM? Maybe try an alternative recovery?
3. Go into recovery/mounts and storage/ then select format system and then install another rom such as stock and see what happens..
Click to expand...
Click to collapse
1. I guess my wording was ambiguous. When I said that the old system comes back, I didn't mean only that the old OS comes back, but that EVERYTHING comes back immediately including all my apps, settings, wallpaper, widgets, everything looks like it always did. I don't get the first-time screens inviting me to log in, or anything like that. The system boots completely normally as though I hadn't used those methods of wiping the user data.
Also one of the things I tried was loading a new system using fastboot commands and the new system seemed to get loaded OK. But I reboot and the buggy system is back and my user data has not been wiped.
2. I'm not sure what you mean and will research that later this evening. For now, I can tell you that I used the Nexus Root Toolkit and I am using whatever it installed.
3. I'm not sure what you mean, but will research that and if I can figure it out, I will try it this evening.
Is it a clue that the command "fastboot oem lock" seems to work, but the lock status doesn't change?

What I am trying to say (very badly) is the system on your phone will hold all your settings along with the OS. When you factory reset/wipe data, it will clear everything out....but, if you then reboot the phone, it will have to reload the old OS as it has nothing to load otherwise. This will include all your previous apps and settings.
When you have wiped all your data, you need to install another 'system/rom' to allow the phone to boot it. Or as I said, it will just reboot the old one.
Try looking for a rooted stock rom in a zip file like this one and put it on your sd card. When you have entered recovery and wiped data/factory reset, then select install from sd card, find the zip and select. The recovery will then flash it and when you reboot, you should be at the setup pages.
Using the Nexus toolkit and ADB is challenging at the best of times. Maybe it is easier if you just use the recovery method as explained above.

killall said:
What I am trying to say (very badly) is the system on your phone will hold all your settings along with the OS. When you factory reset/wipe data, it will clear everything out....but, if you then reboot the phone, it will have to reload the old OS as it has nothing to load otherwise. This will include all your previous apps and settings.
When you have wiped all your data, you need to install another 'system/rom' to allow the phone to boot it. Or as I said, it will just reboot the old one.
Try looking for a rooted stock rom in a zip file like this one and put it on your sd card. When you have entered recovery and wiped data/factory reset, then select install from sd card, find the zip and select. The recovery will then flash it and when you reboot, you should be at the setup pages.
Using the Nexus toolkit and ADB is challenging at the best of times. Maybe it is easier if you just use the recovery method as explained above.
Click to expand...
Click to collapse
When I go into the recovery mode at boot time, the menu says I am using "Android system recovery <3e>"
According to all documentation I have seen, erasing the user partition is all I should need to do to wipe out all of my data, and this works perfectly on a different tablet that I have. I really shouldn't need to do anything else, which is why my situation is so strange.
The Nexus 7 doesn't have an SD card slot so I can't do the things you are saying that involve installing things from sd. Maybe there is a way to do the same thing via the portion of Flash that simulates an sd card, but the recovery menus don't have any way to do that, at least not that I can find.

I saw that you are rooted then I assumed you were using a custom recovery like Clockworkmod or TWRP.
When I wrote SD I meant the internal storage, sorry for the confusion.
I would be flashing a recovery again, it seems to be causing the problem. You can do this through Nexus tools.

killall said:
I saw that you are rooted then I assumed you were using a custom recovery like Clockworkmod or TWRP.
When I wrote SD I meant the internal storage, sorry for the confusion.
I would be flashing a recovery again, it seems to be causing the problem. You can do this through Nexus tools.
Click to expand...
Click to collapse
When you say to use "Nexus tools", do you mean the the tools that are part of the Nexus Root Toolkit? I did use those tools to format and rebuild the recovery partition, and it didn't help at all.
If you mean tools that I need to install as apps within Android, that isn't possible at the moment because the tablet is so unstable that when I reboot, I get all my old stuff for a few seconds so I know nothing changed, and then it reboots before I have a chance to do anything.
If you mean that I should mount the Android flash ram as a folder on my PC, I only seem to be able to do that for the few seconds that the system is booted and then the folder drops off. The only mode where I can keep the tablet powered on and stable is the boot menu and the recovery menu. Is there a way to mount the drive at that time?

Phonetrips said:
When you say to use "Nexus tools", do you mean the the tools that are part of the Nexus Root Toolkit? I did use those tools to format and rebuild the recovery partition, and it didn't help at all.
If you mean tools that I need to install as apps within Android, that isn't possible at the moment because the tablet is so unstable that when I reboot, I get all my old stuff for a few seconds so I know nothing changed, and then it reboots before I have a chance to do anything.
If you mean that I should mount the Android flash ram as a folder on my PC, I only seem to be able to do that for the few seconds that the system is booted and then the folder drops off. The only mode where I can keep the tablet powered on and stable is the boot menu and the recovery menu. Is there a way to mount the drive at that time?
Click to expand...
Click to collapse
Fast boot a custom recovery. Fastboot recovery c:/path/recovery.IMG
Path being whatever path you have to the recovery you chose to download. Then wipe data/factory reset, maybe wipe cache and dalvik since you're there. Then reboot, see what happens. Still buggy, download another ROM, there are stock-ish ones out there, or you can choose cm or AOKP
Sent from my Nexus 7 using xda app-developers app

VonEsch said:
Fast boot a custom recovery. Fastboot recovery c:/path/recovery.IMG
Path being whatever path you have to the recovery you chose to download. Then wipe data/factory reset, maybe wipe cache and dalvik since you're there. Then reboot, see what happens. Still buggy, download another ROM, there are stock-ish ones out there, or you can choose cm or AOKP
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Iv'e done all that and nothing changes whatsoever. The problem isn't that I have a buggy Android system, but rather that all commands to format and erase that system are ignored.

Actually I was wrong, I never did load a recovery image like you said, although I did at one point use one that the Nexus Root Toolkit installed.
So I found a recovery image, downloaded it, and did this:
fastboot flash recovery openrecovery-twrp-2.3.3.0-grouper.img
But nothing changes, partly because maybe I don't know what to do with this thing that I just loaded. If I use the menu to go into recovery mode, I get the normal recovery menu I have always gotten.

Phonetrips said:
Actually I was wrong, I never did load a recovery image like you said, although I did at one point use one that the Nexus Root Toolkit installed.
So I found a recovery image, downloaded it, and did this:
fastboot flash recovery openrecovery-twrp-2.3.3.0-grouper.img
But nothing changes, partly because maybe I don't know what to do with this thing that I just loaded. If I use the menu to go into recovery mode, I get the normal recovery menu I have always gotten.
Click to expand...
Click to collapse
Flash the cwm one, maybe that will work?
Sent from my Galaxy Nexus using xda app-developers app

Phonetrips said:
Iv'e done all that and nothing changes whatsoever. The problem isn't that I have a buggy Android system, but rather that all commands to format and erase that system are ignored.
Click to expand...
Click to collapse
VonEsch said:
Flash the cwm one, maybe that will work?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Before I try a different one, can you please tell me what is supposed to happen after I give that fastboot command to flash the recovery image, Should the tablet go into that recovery manager immediately, or do I need to do something first to make it show up?
I went ahead and found/downloaded the cwm one. The same thing happened: I don't see it running and if I go into recovery mode I get the normal recovery, not this one.

killall said:
What I am trying to say (very badly) is the system on your phone will hold all your settings along with the OS. When you factory reset/wipe data, it will clear everything out....but, if you then reboot the phone, it will have to reload the old OS as it has nothing to load otherwise. This will include all your previous apps and settings.
When you have wiped all your data, you need to install another 'system/rom' to allow the phone to boot it. Or as I said, it will just reboot the old one.
Click to expand...
Click to collapse
Sorry, but this is completely wrong. When you do a factory reset, it wipes /data and /cache, which doesn't affect the OS at all because the OS resides on the /system partition. When you do a factory reset and reboot, you will run into the initial setup screen for whatever ROM you have installed. No user data/apps will be present.
Phonetrips said:
Before I try a different one, can you please tell me what is supposed to happen after I give that fastboot command to flash the recovery image, Should the tablet go into that recovery manager immediately, or do I need to do something first to make it show up?
I went ahead and found/downloaded the cwm one. The same thing happened: I don't see it running and if I go into recovery mode I get the normal recovery, not this one.
Click to expand...
Click to collapse
This seems really screwy. I'd say either your device is defective, or... Well I don't really know what else it could be. The fact that fastboot commands fail is a good indicator that something is screwed up. Have you tried wiping things through fastboot? It may be worth a shot, just know how to flash a ROM through it when you're done. I'm talking "fastboot erase -----" where ---- is replaced by system, data, or whatever. Just DO NOT erase the bootloader. Boot, however, is fine.
If all of this fails, it would seem that the device memory is defective.
About your recovery question, it will only go into recovery when you tell it to either from bootloader or ADB. And stock Android will try to remove CWM, so first time you need to go to recovery straight from the bootloader and let it make itself permanent when it asks.
Sent from my Nexus 7 using Tapatalk HD

korockinout13 said:
Sorry, but this is completely wrong. When you do a factory reset, it wipes /data and /cache, which doesn't affect the OS at all because the OS resides on the /system partition. When you do a factory reset and reboot, you will run into the initial setup screen for whatever ROM you have installed. No user data/apps will be present.
Yes, this is what is supposed to happen, but on my machine when I do all those things, there is absolutely no change and the system continues to boot exactly as it was.
This seems really screwy. I'd say either your device is defective, or... Well I don't really know what else it could be. The fact that fastboot commands fail is a good indicator that something is screwed up. Have you tried wiping things through fastboot? It may be worth a shot, just know how to flash a ROM through it when you're done. I'm talking "fastboot erase -----" where ---- is replaced by system, data, or whatever. Just DO NOT erase the bootloader. Boot, however, is fine.
If all of this fails, it would seem that the device memory is defective.
About your recovery question, it will only go into recovery when you tell it to either from bootloader or ADB. And stock Android will try to remove CWM, so first time you need to go to recovery straight from the bootloader and let it make itself permanent when it asks.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I have used fastboot erase ---- and fastboot format --- for system and everything else. Whether or not I flash new code to those partitions, all of this is ignored and the system continues to boot as it always has, with all my stuff.
After flashing the alternate recovery images, absolutely nothing changes when I choose Recovery Mode from the fastboot menu.

I talked to Google Play support and they sending out a replacement one. They never asked whether I had ever unlocked or rooted it and I didn't volunteer anything, just told them the symptoms I am having. But I have to send the old one back after I receive the new one, and there is a chance they won't accept if for warranty service when they see it,

Phonetrips said:
I talked to Google Play support and they sending out a replacement one. They never asked whether I had ever unlocked or rooted it and I didn't volunteer anything, just told them the symptoms I am having. But I have to send the old one back after I receive the new one, and there is a chance they won't accept if for warranty service when they see it,
Click to expand...
Click to collapse
That is true, since you can't change anything, they will probably know you voided the warranty. The only thing you could do is brick it permanently by erasing the bootloader... Not sure if that would work/help.
Sent from my Nexus 7 using Tapatalk HD

Help! Flashed stock recovery and now dead tablet

Hello i downloaded the stock recovery for my nexus 10 because i wanted to go back to stock for the sooon to come 4.3 android update. I tried using the command to flash but it didnt work so i downloaded flashify and used that to flash. It said it completeded and told me to either flash more stuff or reboot. I rebooted and it went to a dead android with a warning in the chest area :crying: I tried holding power to shut off tablet for 30 seconds but it turns right back on into dead android image. I can get into fastboot if i hold volume up while it turns on but now the only choice is start and it says downloading do not turn off target. If you know whats wrong please help me. Is there anyway to fix this without flashing stock?

abdel12345 said:
Hello i downloaded the stock recovery for my nexus 10 because i wanted to go back to stock for the sooon to come 4.3 android update. I tried using the command to flash but it didnt work so i downloaded flashify and used that to flash. It said it completeded and told me to either flash more stuff or reboot. I rebooted and it went to a dead android with a warning in the chest area :crying: I tried holding power to shut off tablet for 30 seconds but it turns right back on into dead android image. I can get into fastboot if i hold volume up while it turns on but now the only choice is start and it says downloading do not turn off target. If you know whats wrong please help me. Is there anyway to fix this without flashing stock?
Click to expand...
Click to collapse
There might be. Using onboard flashing tools is not a good idea since it doesn't seem like you know what you're doing (no offense) with the low-level tools. You should be able to dirty flash your ROM from stock (although you do realize that the stock recovery will be useless to you if you're trying to update to 4.3 over a custom ROM, right? Or if you're on a stock rooted ROM that flashing will unroot you?) to leave your /data partition intact.
When you said "the command to flash", I assume you're referring to "fastboot flash recovery <path-to-recovery.img>". You will need to rerun that, probably flashing a custom recovery. If your system boots correctly after this, then you can go ahead and reflash your stock recovery (and the problem would likely have been a messed up partition). If not, then you can try to boot into the custom recovery to do a dirty flash of your ROM (i.e. a flash without using factory wipe). If that doesn't work either, you can open up a .zip of your ROM and use "fastboot flash system <path-to-system.img>", pointing to the system image in your ROM. That should generally get you at least bootable again.

Rirere said:
There might be. Using onboard flashing tools is not a good idea since it doesn't seem like you know what you're doing (no offense) with the low-level tools. You should be able to dirty flash your ROM from stock (although you do realize that the stock recovery will be useless to you if you're trying to update to 4.3 over a custom ROM, right? Or if you're on a stock rooted ROM that flashing will unroot you?) to leave your /data partition intact.
When you said "the command to flash", I assume you're referring to "fastboot flash recovery <path-to-recovery.img>". You will need to rerun that, probably flashing a custom recovery. If your system boots correctly after this, then you can go ahead and reflash your stock recovery (and the problem would likely have been a messed up partition). If not, then you can try to boot into the custom recovery to do a dirty flash of your ROM (i.e. a flash without using factory wipe). If that doesn't work either, you can open up a .zip of your ROM and use "fastboot flash system <path-to-system.img>", pointing to the system image in your ROM. That should generally get you at least bootable again.
Click to expand...
Click to collapse
Yes I don't really know what I'm doing. I'm on stock. Anyways I'll try what you said about flashing custom recovery again and thanks for the reply. I just really don't want to lose all my data or else I wouldve flashed stock by now
Sent from my Xperia Play (r800x)

abdel12345 said:
Yes I don't really know what I'm doing. I'm on stock. Anyways I'll try what you said about flashing custom recovery again and thanks for the reply. I just really don't want to lose all my data or else I wouldve flashed stock by now
Sent from my Xperia Play (r800x)
Click to expand...
Click to collapse
Not a problem. These tools are really useful when they work, but it's definitely better to know how to do it when things go wrong (and they almost always will at least once). Just keep a level head about it and don't panic. Fastest way to lose data, that.

ok thanks. Well i got it booting and i decided im just going to back up everything with titanium backup and reflash stock with wugs toolkit

OK I'm a big idiot I did all this for no reason. I flashed back to stock with wugsroot kit and apparently it wiped all SD data so I lost all my titanium backups as well as pictures and apps and everything. Damn I'm stupid. Well I guess now that I lost all my data I might as well flash a custom ROM :banghead::banghead:
Sent from my Xperia Play (r800x)

Us996 TWRP not sticking

I'm using the tutorial on the LineageOS wiki for the Us996. I've unlocked the bootloader via official means from LG, but when it comes time to send the recovery via fastboot, it successfully sends and writes it, it even let's me boot into it, after pulling the battery, and using the correct button commands. But if I restart and try to enter again I'm greeted by the official erase everything recovery.
Does anyone know what I'm doing wrong? Do I need to flash root to get the recovery to stick?

Take a look at this video. If you have TWRP installed right, and are going to it through a battery pull and the power button volume down combination, then the screen that comes up looks scary and looks like you'll "format" your phone, but as you see in this video, you don't.

baldybill said:
Take a look at this video. If you have TWRP installed right, and are going to it through a battery pull and the power button volume down combination, then the screen that comes up looks scary and looks like you'll "format" your phone, but as you see in this video, you don't.
https://www.youtube.com/watch?v=https://www.youtube.com/watch?v=tDq0qMbgjL4
Click to expand...
Click to collapse
See I've gotten into TWRP, then I reboot system(actual Android not just restarting recovery).the problem is When I power off my phone and tried to get back into TWRP, I clicked yes and yes and it proceeded to wipe my phone. TWRP wasn't there just factory reset lol

lowsnamebrand said:
See I've gotten into TWRP, then I reboot system(actual Android not just restarting recovery).the problem is When I power off my phone and tried to get back into TWRP, I clicked yes and yes and it proceeded to wipe my phone. TWRP wasn't there just factory reset lol
Click to expand...
Click to collapse
Not sure why it isnt happening automatically (it usually does when flashing things like magisk to root) but when you get into twrp or with root rename /system/recovery-from-boot.p to /system/recovery-from-boot.bak. If in twrp first go into the mount page and uncheck the box at the bottom that says something about system read only first, then you can use the file manager.
Or since it sounds like you want to flash lineage, just flash the lineageos zip (and then optionally opengapps and root). Be sure to format data too (wipe->format data->yes). Then if you dont have lineage on an sdcard ready to go you could reboot recovery so that the formatted data is ready then connect to pc and send the zips over by using adb push C:\path\to\lineage.zip /sdcard/

Phoenix591 said:
Not sure why it isnt happening automatically (it usually does when flashing things like magisk to root) but when you get into twrp or with root rename /system/recovery-from-boot.p to /system/recovery-from-boot.bak. If in twrp first go into the mount page and uncheck the box at the bottom that says something about system read only first, then you can use the file manager.
Or since it sounds like you want to flash lineage, just flash the lineageos zip (and then optionally opengapps and root). Be sure to format data too (wipe->format data->yes). Then if you dont have lineage on an sdcard ready to go you could reboot recovery so that the formatted data is ready then connect to pc and send the zips over by using adb push C:\path\to\lineage.zip /sdcard/
Click to expand...
Click to collapse
What I'm thinking about doing is flashing TWRP again, on first boot(of TWRP) backing up my current rom(stock) and trying to boot into recovery again, because if it doesn't stick again, it'll wipe but at least I'll have a backup.
I've noticed a lot of different root files which would you recommend?

lowsnamebrand said:
What I'm thinking about doing is flashing TWRP again, on first boot(of TWRP) backing up my current rom(stock) and trying to boot into recovery again, because if it doesn't stick again, it'll wipe but at least I'll have a backup.
I've noticed a lot of different root files which would you recommend?
Click to expand...
Click to collapse
Sorry for the double post but does the "LG factory reset" stay even after having TWRP installed? Like will I always have to answer yes twice to enter TWRP?

lowsnamebrand said:
Sorry for the double post but does the "LG factory reset" stay even after having TWRP installed? Like will I always have to answer yes twice to enter TWRP?
Click to expand...
Click to collapse
Yes thats always the same.
If you don't flash lineage or something to root stock (I reccommend magisk since the alternative, Supersu, is owned by some Chinese company, and magisk has various modules that do many things) and don't rename /system/recovery-from-boot.p manually (theres a file manager under advanced in twrp) the stock rom will use that file to reflash stock recovery any time it boots.

Phoenix591 said:
Yes thats always the same.
If you don't flash lineage or something to root stock (I reccommend magisk since the alternative, Supersu, is owned by some Chinese company, and magisk has various modules that do many things) and don't rename /system/recovery-from-boot.p manually (theres a file manager under advanced in twrp) the stock rom will use that file to reflash stock recovery any time it boots.
Click to expand...
Click to collapse
Awesome I think my issue is not renaming that file and the stock rom reinstalling stock recovery. I've used SuperSU, never used magisk, is there a stickied release thread for it?

lowsnamebrand said:
Awesome I think my issue is not renaming that file and the stock rom reinstalling stock recovery. I've used SuperSU, never used magisk, is there a stickied release thread for it?
Click to expand...
Click to collapse
Its got more than a thread, has a whole section. Anyway heres the main release thread

Phoenix591 said:
Its got more than a thread, has a whole section. Anyway heres the main release thread
Click to expand...
Click to collapse
You've been a huge help, thank you! I'll report back later tonight, when I can actually work on my phone

So i was able to obtain root aswell as installed twrp, the only issue I had was every rom I tried refused to boot. They just hung at the loading screen, that includes the back up I'd made of stock, is there something I missed?

lowsnamebrand said:
So i was able to obtain root aswell as installed twrp, the only issue I had was every rom I tried refused to boot. They just hung at the loading screen, that includes the back up I'd made of stock, is there something I missed?
Click to expand...
Click to collapse
If you mean the boot animation, the very first time can take a good while, like 20 minutes. Also make sure you've formatted /data if you havnt yet especially going to lineage.

Phoenix591 said:
If you mean the boot animation, the very first time can take a good while, like 20 minutes. Also make sure you've formatted /data if you havnt yet especially going to lineage.
Click to expand...
Click to collapse
Sorry for the late reply, yeah I think I just let the boot animation go for around 5, I'm gonna have to try reflashing it and hoping for the best, I'll be sure to answer back when I get a chance

OK, I know this is an old thread - but I just got a replacement US996 phone; my old standby has a charger plug problem so I decided to get another one and put a rooted stock Oreo ROM on it. However, I'm having the same issue as the OP. Get into fastboot, flash TWRP (I have the 3.3.1-0 version, as the newer 3.3.1-1 version does not have any download mirrors). The flash appears to go just fine, it says the write was completed. However, when I reboot into adb mode and do "adb reboot recovery" I get "no command" and the little droid with his belly hatch open. So obviously TWRP wasn't flashed. The OP says he eventually was able to get it to work and install root. How did you fix the issue?
Do I still need to do the old recowvery shenanigans that we had to do back when the phone first came out?
Thanks!

I believe you MUST use the button combo to reboot into twrp.
See here:
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239/post78513963

pistacios said:
I believe you MUST use the button combo to reboot into twrp.
See here:
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239/post78513963
Click to expand...
Click to collapse
I've done that. The problem is that TWRP hasn't actually been installed via fastboot flash recovery - it goes through the motions, SAYS it's been installed, but when I do the button combo, it actually does reset my phone rather than booting into TWRP.
---------- Post added at 09:36 AM ---------- Previous post was at 08:55 AM ----------
Disregard the above. Flashed it again (4th time), and it finally took.

The same happened with my wife's US996 now that you mention it. Took a few tries and was a bit frustrating.
When I flashed TWRP on mine it was a "one and done".
Glad you got it sorted.

Thanks - all good. Rooted stock Oreo ROM installed, working great.