Develop Bugs

[Q] Updating stock ROM without wiping?

guys, I am have stock 4.0.2 rooted with CWM, is there a way to update stock rom (when stock 4.0.3 comes out) without wiping data?
I know I could do all kinds of MyBackupPro or Titanium Backup, but still it's quite a bit of hassle especially I can't keep anything in Internal Storage, anyone got an idea on this?

Easiest way would be to go ahead and flash the factory recovery back rather than clockworkmod. If you are on stock now and are wanting to get the 4.0.3 OTA when its pushed than you really don't need clockwork. If you flash the factory recovery back that we will be able to get the OTA and not worry about a data wipe. Flashing the factory recovery will not effect your current root at all so you stay rooted.

badassirocz said:
Easiest way would be to go ahead and flash the factory recovery back rather than clockworkmod. If you are on stock now and are wanting to get the 4.0.3 OTA when its pushed than you really don't need clockwork. If you flash the factory recovery back that we will be able to get the OTA and not worry about a data wipe. Flashing the factory recovery will not effect your current root at all so you stay rooted.
Click to expand...
Click to collapse
wow, thanks, so, I'm assuming I could use the same tool (GNex Toolkit) to flash back my factory recovery, right? besides, what if I did flash a custom kernel (like Jame Bond), do I need to flash back that too? or I could just leave it and the OTA would overwrite the kernel with stock kernel?
thanks!

You should be able to use that tool kit or you can just use fastboot and do the following after downloading the proper factory image from google and extracting the recover.img as for the kernel I don't believe it will effect the OTA at all.
- copy the recovery.img file to the directory that contains your fastboot utility
- start-up a terminal/command session
- put your phone into fastboot / bootloader mode
- type the following fastboot command to flash the stock recovery:
Code:
fastboot flash recovery recovery.img

OP, your internal storage doesn't get wiped when flashing a new ROM.. The virtual SD card is left untouched.
Also I'm pretty sure you lose root if you accept an OTA update.. but you can easily reroot.

badassirocz said:
You should be able to use that tool kit or you can just use fastboot and do the following after downloading the proper factory image from google and extracting the recover.img as for the kernel I don't believe it will effect the OTA at all.
- copy the recovery.img file to the directory that contains your fastboot utility
- start-up a terminal/command session
- put your phone into fastboot / bootloader mode
- type the following fastboot command to flash the stock recovery:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
thanks! would give it a try!
joshnichols189 said:
OP, your internal storage doesn't get wiped when flashing a new ROM.. The virtual SD card is left untouched.
Also I'm pretty sure you lose root if you accept an OTA update.. but you can easily reroot.
Click to expand...
Click to collapse
um. I am not so sure it would be the case for Galaxy Nexus, data wipe before (like my GS2) just means user data, but for Galaxy Nexus, last time i tried it wipe my internal storage as well. when I'm using the GN toolkit to flash 4.0.2 image downloaded from Google, it wiped my data and storage, do you mean there is a way to flash Google image without wiping for GN ?

Found answer.....

speedin said:
Found answer.....
Click to expand...
Click to collapse
answer of....?

hongkongtom said:
answer of....?
Click to expand...
Click to collapse
I asked if it was possible to update OTA when your phone is unlocked, and with CWM.. The answer is "yes" if you have stock recovery instead of CWM....

speedin said:
I asked if it was possible to update OTA when your phone is unlocked, and with CWM.. The answer is "yes" if you have stock recovery instead of CWM....
Click to expand...
Click to collapse
great, while knowledge never have enough, my next question is "How could I manually flash (instead of OTA) stock Google image (in case 4.0.x got out) without wiping my GN?" (assuming I am coming from earlier stock rom)

[Q] Has Android Revolution HD install bricked my phone? [Solved]

Hello All.
This is the first time I have tried to put a custom ROM on an HTC so I am still learning the ropes.
I tried to follow the instructions in the first post. So... In sequence, this is what I did...
HTC One X unlocked with htcdev.com (S-ON) or S-OFF (coming soon)
This seemed to go without a hitch. On the HBoot screen (I think that is what it is called) it tells me I am now unlocked.
ClockworkMod Recovery or 4EXT Touch Recovery (coming soon)
I installed the official version as per the instructions here.
The last instruction that seemed to work successfully was this:
Code:
fastboot flash boot recovery-clockwork-touch-5.8.2.4-endeavouru.img
Then I tried
Code:
fastboot reboot
which put me into recovery mode.
<EDIT> The instructions here have now been corrected to:
Code:
fastboot flash recovery recovery-clockwork-touch-5.8.2.4-endeavouru.img
</EDIT>
Choosing the reboot option from recovery just bounces me back into recovery mode but I understand from the instructions I should be able to boot into a working phone!
Has something gone wrong?
If I use the volume down + power button I can enter HBoot mode. From here I can select Fastboot. Connecting via USB to my computer seems to work fine, as I see Fastboot USB on my phone, and I when I execute this...
Code:
fastboot devices
I get something like this
Code:
List of devices attached
HTXXXXXXXXXX device
I am now unsure how to continue because I think something has gone wrong and I should have a working phone at this point.
Do I press ahead and try to install the Firmware package from here? Unless this lets me boot into a working phone (which I don’t believe it will), it still leaves me with the problem that for a One X, without a removable SD card I don’t know how to transfer and run the "Super Wipe" script, nor transfer and flash Android Revolution ROM via recovery.
Do I need to do something with
Code:
fastboot flash
?
Please help as she is threatening to dump me for destroying her 2-day-old phone.

It's
Code:
fastboot flash [B]recovery[/B] recovery-clockwork-touch-5.8.2.4-endeavouru.img
not boot..
Solution for you is to go into bootloader, flash recovery with the command i gave you and then reboot into recovery and install the rom..
After that everything should be ok and your phone will boot into ARHD without any problem.

delete please

anko184 said:
It's
Code:
fastboot flash [B]recovery[/B] recovery-clockwork-touch-5.8.2.4-endeavouru.img
not boot..
Solution for you is to go into bootloader, flash recovery with the command i gave you and then reboot into recovery and install the rom..
After that everything should be ok and your phone will boot into ARHD without any problem.
Click to expand...
Click to collapse
Thanks
It looks like the instructions I followed previously had an error then.
<EDIT> The instructions were incorrect, but have now been corrected </EDIT>
I will follow your instructions. But what about the RUU that is mentioned in the instructions? It is not clear how or when I should flash it. Presumably I flash the RUU before I do the ARHD flash... ???

mwhincup said:
Thanks
It looks like the instructions I followed previously had an error then.
I will follow your instructions. But what about the RUU that is mentioned in the instructions? It is not clear how or when I should flash it. Presumably I flash the RUU before I do the ARHD flash... ???
Click to expand...
Click to collapse
You don't need to flash any RUU or firmware unless your phone wasn't shipped with 1.26, which i don't think it was.
Just try flashing the recovery with the correct command and then the rom. If your phone doesn't boot after that then you may try the firmware but i'm sure you won't need it.

anko184 said:
You don't need to flash any RUU or firmware unless your phone wasn't shipped with 1.26, which i don't think it was.
Just try flashing the recovery with the correct command and then the rom. If your phone doesn't boot after that then you may try the firmware but i'm sure you won't need it.
Click to expand...
Click to collapse
So, I understand that you are telling me:
Flashing CWM recovery will rectify my current problem and restore my phone to a workable state.
Booted normally, I can copy the ARHD ROM to the internal SD (not sure what the location for this will be).
I then reboot into recovery and 'Install Zip from SD card'.
Click to expand...
Click to collapse
Is this correct?

mwhincup said:
So, I understand that you are telling me:
Is this correct?
Click to expand...
Click to collapse
Wait before you flash anything, if you don'talready have arhd on your internal sd you may be in trouble if you do superwipe
Sent from my HTC One X using XDA

mwhincup said:
So, I understand that you are telling me:
Is this correct?
Click to expand...
Click to collapse
Without trying to sound like a ****, if you don't understand what you are doing you should read more to understand the whole process before attempting it.

bagofcrap24 said:
Wait before you flash anything, if you don'talready have arhd on your internal sd you may be in trouble if you do superwipe
Click to expand...
Click to collapse
Good advice, I am sure. However my problem now is getting into a working phone so that I can transfer the ROM onto the internal SD.
Can't wait to get home and try it!

what you have done is replaced your boot sector with a recovery image, that is the reason why you cant boot your phone as normal so even flashing the recovery correctly will not allow your phone to boot up.
as your phone cannot boot up you cannot transfer any files to the internal memory of your phone in order to flash ARHD
at present there is a problem with the official version of ClockworkMod Recovery so i personally would reccommend using the interim version HERE
and flash with fastboot flash recovery r1-modaco-recovery-clockwork-touch-endeavoru.img
As you have [email protected]$ked your boot partition up you will also want to download THIS
this is an insecure boot image (thanks to paul from modaco) I have just extracted the part you will need from his package
with this you will need to be in fastboot again and type fastboot flash boot boot.img
obviously you will need to copy both of the files to the same directory as fastboot is on your PC in order to send them
by flashing the boot section with the insecure boot here it will allow your phone to boot up normally again, once it has booted normally you can then copy the ARHD and superwipe to your internal SD card
to access recovery
power off phone by holding power button for 10seconds
power on with power+voldown
select recovery from hboot screen with voldown then power to select
your phone will reboot and then you will be in recovery
do a nandroid backup incase anything goes wrong
then flash the superwipe script
then flash ARHD 1.2.2
all is good

animaleyes76 said:
Without trying to sound like a ****, if you don't understand what you are doing you should read more to understand the whole process before attempting it.
Click to expand...
Click to collapse
You are correct of course, however, there comes a point where the only way to learn is to actually do something. I have flashed numerous ROMS on my Galaxy S, and before doing this I have read numerous guides trying to better understand the procedures for HTC devices.
I have tried to follow what appeared to be a step-by-step guide, however, either there has been a malfunction, or it appears there may be two important bits of information missing from that guide:
Flashing CWM recovery leaves the phone in a state that it won't boot normally, and consequently...
The ARHD ROM should be loaded onto the internal SD at the very beginning of the procedure
Click to expand...
Click to collapse

Thanks all of you so much for your effort. It's much appreciated.
bagofcrap24 said:
what you have done is replaced your boot sector with a recovery image, that is the reason why you cant boot your phone as normal so even flashing the recovery correctly will not allow your phone to boot up.
Click to expand...
Click to collapse
@bagofcrap24 I may have misled you with a typo in the first post. (See my edit)
d'oh

edit : just read updated info
so what happens when you choose recovery and press power from the hboot screen
i'm understanding that when doing a normal reboot it just sends you straight into hboot?
power on with voldown
press voldown to select recovery
press power to select recovery
you should either see CWM or the stock recovery
again looking at what you have written, if you just do a normal reboot and its putting you straight into recovery then you probably have flashed recovery onto the boot partition

bagofcrap24 said:
edit : just read updated info
so what happens when you choose recovery and press power from the hboot screen
i'm understanding that when doing a normal reboot it just sends you straight into hboot?
power on with voldown
press voldown to select recovery
press power to select recovery
you should either see CWM or the stock recovery
again looking at what you have written, if you just do a normal reboot and its putting you straight into recovery then you probably have flashed recovery onto the boot partition
Click to expand...
Click to collapse
I'll get back to you with some definitive answers in 3 hours or so. Sorry, I'm at work now.

bagofcrap24 said:
so what happens when you choose recovery and press power from the hboot screen
Click to expand...
Click to collapse
power on with voldown
press voldown to select recovery
press power to select recovery
Click to expand...
Click to collapse
I get a circular yellow 'recycling' symbol, followed a few seconds later by a magenta triangle with an exclamation mark. (Is this the stock recovery?). Then the phone restarts and I end up back in the Clockworkmod recovery.
i'm understanding that when doing a normal reboot it just sends you straight into hboot?
Click to expand...
Click to collapse
No. A normal reboot (without holding the Vol down key) sends me straight to clockworkmod recovery.
I can get to HBoot with Vol down+Power on startup.

mwhincup said:
I get a circular yellow 'recycling' symbol, followed a few seconds later by a magenta triangle with an exclamation mark. (Is this the stock recovery?). Then the phone restarts and I end up back in the Clockworkmod recovery.
No. A normal reboot (without holding the Vol down key) sends me straight to clockworkmod recovery.
I can get to HBoot with Vol down+Power on startup.
Click to expand...
Click to collapse
Right this means you did mess up the boot and recovery partitions, the one where you have the exclamation mark is the stock recovery which means you didn't flash cwm to the recovery partition.
the fact that you get to recovery on a normal boot also suggests as I suspected that you have flashed recovery on to the boot partition, follow the instructions I put up earlier about flashing the boot.IMG and redo the recovery.IMG and you should be fine
Sent from my HTC One X using XDA

bagofcrap24 said:
what you have done is replaced your boot sector with a recovery image, that is the reason why you cant boot your phone as normal so even flashing the recovery correctly will not allow your phone to boot up.
as your phone cannot boot up you cannot transfer any files to the internal memory of your phone in order to flash ARHD
at present there is a problem with the official version of ClockworkMod Recovery so i personally would reccommend using the interim version HERE
and flash with fastboot flash recovery r1-modaco-recovery-clockwork-touch-endeavoru.img
As you have [email protected]$ked your boot partition up you will also want to download THIS
this is an insecure boot image (thanks to paul from modaco) I have just extracted the part you will need from his package
with this you will need to be in fastboot again and type fastboot flash boot boot.img
obviously you will need to copy both of the files to the same directory as fastboot is on your PC in order to send them
by flashing the boot section with the insecure boot here it will allow your phone to boot up normally again, once it has booted normally you can then copy the ARHD and superwipe to your internal SD card
to access recovery
power off phone by holding power button for 10seconds
power on with power+voldown
select recovery from hboot screen with voldown then power to select
your phone will reboot and then you will be in recovery
do a nandroid backup incase anything goes wrong
then flash the superwipe script
then flash ARHD 1.2.2
all is good
Click to expand...
Click to collapse
Your analysis is quite correct. All is indeed good! Thanks very much. The boot image worked as described. I will now transfer Superwipe and the ROM.

Make sure you do a nandroid backup first, it was lucky this time but if you mess up your system partition you may find yourself with no way of putting files on without unrooting and restoring the ruu
Sent from my HTC One X using XDA

bagofcrap24 said:
Make sure you do a nandroid backup first, it was lucky this time but if you mess up your system partition you may find yourself with no way of putting files on without unrooting and restoring the ruu
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Done!
Everything worked as you said it would.
I now have ARHD installed and running brilliantly.
Thanks again

mwhincup said:
Done!
Everything worked as you said it would.
I now have ARHD installed and running brilliantly.
Thanks again
Click to expand...
Click to collapse
Glad you fixed it and sorry for being a bit harsh earlier.. was having a bad day

Jelly Bean animation locked

Need some help. I have a Verizon Galaxy Nexus and did bootloader and rooted my phone. Yeah!! Tried to install JellyBean and ran into a problem. The animation of Jellybean is locked what do I do? Need some serious help. I am able to get to Fastboot mode.

coachv said:
Need some help. I have a Verizon Galaxy Nexus and did bootloader and rooted my phone. Yeah!! Tried to install JellyBean and ran into a problem. The animation of Jellybean is locked what do I do? Need some serious help. I am able to get to Fastboot mode.
Click to expand...
Click to collapse
The animation is locked? I don't understand what you mean. Are you stuck at the boot logo (Google screen) or the boot animation (flashing X)? Either way, you can just go into your custom recovery, wipe data, and try flashing again if you are waiting on it to boot for that long. Some users have experienced waiting 5 minutes before it actually started up.

Agreed.
Initial boot on my Toro took 5-6 minutes.
It was butter ever since, however.
Give it a minute.
And make sure you're properly installing a rom (post 2 from the link in my signature).
Edit:
Anton&Juba.
Tag-teaming 'ze noobs until it goes out of style.

It's flashing X on Boot animation. It has stayed in that mode for hours. I am confused and can not back into my phone. Reading other posts, I am able to get back to Fastboot mode. What do I do next? I appreciate your help. Thanks

coachv said:
It's flashing X on Boot animation. It has stayed in that mode for hours. I am confused and can not back into my phone. Reading other posts, I am able to get back to Fastboot mode. What do I do next? I appreciate your help. Thanks
Click to expand...
Click to collapse
I see. So you're in a bootloop. What do you mean fastboot mode? Because I know some users get confused with the terms... I'm assuming you're able to enter the Bootloader (screen with android belly open, where you are able to move through some menu options with your up and down volume keys)? Note, this is not the screen with the Android and red exclamation point. If you are able to boot into bootloader, you should be able to enter your custom recovery (Clockworkmod Recovery?) and wipe data and either flash a rom (same one or new one) and try again, or restore a backup you made. If you're set on using fastboot commands, you can always flash Nexus Factory Images, although this will wipe your SD card. I recommend getting into your custom recovery and wiping and flashing or restoring. If you don't have a custom recovery, you can always flash a custom recovery (fastboot flash recovery recoveryname.img) and flash a custom rom or restore from there. Here is CWM recovery incase you don't have a custom recovery, or you have reverted back to stock (Android with red exclamation point).

yes the android belly is open. I just don't the steps that I need to do from here. This is where I get lost.

coachv said:
yes the android belly is open. I just don't the steps that I need to do from here. This is where I get lost.
Click to expand...
Click to collapse
Can you scroll through the menu options with your volume keys? And one of the options should be "reboot recovery." Do that one.

Yes I can scroll with volume controls. Here are my options: start, restart bootloader, recovery mode and power off

coachv said:
Yes I can scroll with volume controls. Here are my options: start, restart bootloader, recovery mode and power off
Click to expand...
Click to collapse
Okay dude.
1.) Move your volume keys to select recovery mode
2.) press the power button to actually select that option
3.) You will boot into your custom recovery
4.) EITHER Wipe Data, wipe cache, wipe dalvik, and then flash a new rom (or try re-flashing this jellybean rom you're having problems with) OR restore from a backup you have previously made (which I hope you did just incase something worse happens in the future).
You do know how to navigate through your custom recovery, right?

My 5x bootloops and I can't even get into recovery..

My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?

redg8gt said:
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
Click to expand...
Click to collapse
Curious, what happens if you flash recovery.img into the boot partition?

It's a nexus device so you should be ok with warranty and an unlocked bootloader.
Sent from my Nexus 9 using XDA Free mobile app

redg8gt said:
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
Click to expand...
Click to collapse
try clean flashing a stock image in fastboot. wipe everything.

k.s.deviate said:
try clean flashing a stock image in fastboot. wipe everything.
Click to expand...
Click to collapse
I manually flashed everything that the flash-all.bat file does, twice. I'm going to try to get it replaced with the warranty.
I can't help but think it is a hardware problem given that everything seems to work perfectly flashing it with factory images and then nothing happens when I try to boot it up.

sfhub said:
Curious, what happens if you flash recovery.img into the boot partition?
Click to expand...
Click to collapse
... is this different than flashing using fastboot? I flashed the stock recovery several times and redownloaded and tried again. TWRP didn't work either.

redg8gt said:
... is this different than flashing using fastboot? I flashed the stock recovery several times and redownloaded and tried again. TWRP didn't work either.
Click to expand...
Click to collapse
What I was suggesting is
fastboot flash boot recovery.img
previously you would have been trying
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I was suggesting flashing your boot partition using the recovery.img on the assumption that the recovery partition emmc might be damaged along with parts of the user partition.
If the boot partition area of the emmc is still good, flashing the recovery.img in there will allow recovery to startup.
Recovery and boot are basically 95% the same image. The partitions sizes are the same. So basically from a flashing standpoint, they are interchangeable.
The difference is the boot partition is automatically selected by the boot loader, while the recovery partition needs special button presses to start.
If you flash the boot partition with the recovery.img, then recovery should just start up automatically without special button presses.

sfhub said:
What I was suggesting is
fastboot flash boot recovery.img
previously you would have been trying
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I was suggesting flashing your boot partition using the recovery.img on the assumption that the recovery partition emmc might be damaged along with parts of the user partition.
If the boot partition area of the emmc is still good, flashing the recovery.img in there will allow recovery to startup.
Recovery and boot are basically 95% the same image. The partitions sizes are the same. So basically from a flashing standpoint, they are interchangeable.
The difference is the boot partition is automatically selected by the boot loader, while the recovery partition needs special button presses to start.
If you flash the boot partition with the recovery.img, then recovery should just start up automatically without special button presses.
Click to expand...
Click to collapse
I think you mean fastboot boot recovery.img. Not fastboot flash boot recovery.img. That'll hopefully boot you into recovery without actually flashing it.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
I think you mean fastboot boot recovery.img. Not fastboot flash boot recovery.img. That'll hopefully boot you into recovery without actually flashing it.
Click to expand...
Click to collapse
Nope, I actually meant what I wrote. I wanted to test the theory that the emmc in the recovery partition is damaged and the easiest way to do that is to flash the recovery onto the boot partition, which might not be damaged.
The partitions are the same size so you won't damage the phone, you'll just cause the phone to boot the kernel which autostarts recovery instead of the kernel that tries to boot android.
fastboot boot recovery.img will just load recovery straight into memory across the USB cable. It won't allow diagnosis of whether the emmc in that section is damaged.

Ok, but if the EMMC is bad in any partition the device is still hosed.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Ok, but if the EMMC is bad in any partition the device is still hosed.
Click to expand...
Click to collapse
Actually that isn't necessarily true. While Emmc can have catastrophic failure, Emmc often has partial failure.
We discovered this when google added SecureTRIM to the kernel on the Samsung Epic Touch. The emmc was getting corrupted by this change and we found that we could lock out certain sections of the emmc by adjusting partition tables and have a functioning phone.
I figure this phone is going back for RMA anyway, so might as well get some useful failure analysis out of it.

redg8gt said:
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
Click to expand...
Click to collapse
Try to do a factor oem lock and then unlock to completely wipe the phone , then try to adb sideload stock 6.0.1 ?

okay here's what you need to do:
1) Try the LG UP tool. There's a thread somewhere in 5x forums. 90% chances are that it will fix everything as it repartitions back to stock.
2) If the above does not work, then do this: Download the platform tools, shift right click, open command prompt, switch off the phone, connect it to pc and power on. Once you are past the google logo, type adb devices, it should show up there on the pc, if it doesn't then try the command again. once the device shows up on the command prompt, type adb logcat, once you have around 3-4 minutes of boot up logs on the cmd, copy everything and post it here, one of us will take a look and tell you what exactly is the problem.

Here is the link, http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740. Member bitdomo has been a savior on many nexus devices.
Sent from my Nexus 9 using XDA Free mobile app

The phone is indeed heading back to Google for a (refurb) replacement. I had tried to directly boot into recovery using both the stock recovery and twrp and had the same result. For the sake of science, I will try the LG tool later and see if I can get it working.

sfhub said:
What I was suggesting is
fastboot flash boot recovery.img
previously you would have been trying
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I was suggesting flashing your boot partition using the recovery.img on the assumption that the recovery partition emmc might be damaged along with parts of the user partition.
If the boot partition area of the emmc is still good, flashing the recovery.img in there will allow recovery to startup.
Recovery and boot are basically 95% the same image. The partitions sizes are the same. So basically from a flashing standpoint, they are interchangeable.
The difference is the boot partition is automatically selected by the boot loader, while the recovery partition needs special button presses to start.
If you flash the boot partition with the recovery.img, then recovery should just start up automatically without special button presses.
Click to expand...
Click to collapse
I just tried this. Still bootloops.

Siddheshpatil said:
okay here's what you need to do:
1) Try the LG UP tool. There's a thread somewhere in 5x forums. 90% chances are that it will fix everything as it repartitions back to stock.
2) If the above does not work, then do this: Download the platform tools, shift right click, open command prompt, switch off the phone, connect it to pc and power on. Once you are past the google logo, type adb devices, it should show up there on the pc, if it doesn't then try the command again. once the device shows up on the command prompt, type adb logcat, once you have around 3-4 minutes of boot up logs on the cmd, copy everything and post it here, one of us will take a look and tell you what exactly is the problem.
Click to expand...
Click to collapse
1) I think I'm going to keep it broken so there is no issue whenever I send it in. I wish I would have waited to call Google. I'm curious now whether that would have worked.
2) There is no past the Google logo.. it resets before it gets past it.

redg8gt said:
I just tried this. Still bootloops.
Click to expand...
Click to collapse
Could you try 2 other things
1) try the fastboot boot recovery.img suggested earlier to confirm your recovery image can boot across USB cable
2) if not, please post a SHA1 hash for your recovery.img and which Android version you got the image from
This will just confirm that the recovery image that you are using is bootable in absence of the EMMC and if not, confirm whether the recovery.img is corrupted or not.

I experienced something similar when I moved from MM to N without wiping data. The data partition got encrypted even though I flashed that fedpatcher. Just couldn't get into twrp beyond its splash screen. The issue here might be unrelated, but I'd suggest a format userdata.

I got this problem a month ago , tried wiping everything and flash stock using fastboot command , then i got 9008 mode .
No recovery no downloads mode no fastboot . (Sometimes can go to fastboot try flash using nrt / manually , nothing happend)

Stock, Locked BL, Cannot Boot OS - Save User Files

My Android Knowledge is pretty good, however I have NEVER dealt with a stock recovery. I have a friend's 5x that will not boot into the OS, it's just bootlooping. Fixing that is not my issue, I'll deal with that easily. However, I do want to pull his photos and other user data off the emulated storage partition before wiping it to fix his boot. Is there anyway within the stock recovery or within fastboot to use adb or something else I'm unaware of to pull user files? Again, bootloader is LOCKED, so flashing a custom recovery to access adb from within recovery is not an option. I use Linux, is there a way to mount the user data partition from within the stock recovery or within fastboot so I can pull these files off the device before I reset it for him?

I never had this problem but have you tried the pull files option in NRT, it is able to do a lot of things with loked Bl, Stock Recovery?

annoyingduck said:
My Android Knowledge is pretty good, however I have NEVER dealt with a stock recovery. I have a friend's 5x that will not boot into the OS, it's just bootlooping. Fixing that is not my issue, I'll deal with that easily. However, I do want to pull his photos and other user data off the emulated storage partition before wiping it to fix his boot. Is there anyway within the stock recovery or within fastboot to use adb or something else I'm unaware of to pull user files? Again, bootloader is LOCKED, so flashing a custom recovery to access adb from within recovery is not an option. I use Linux, is there a way to mount the user data partition from within the stock recovery or within fastboot so I can pull these files off the device before I reset it for him?
Click to expand...
Click to collapse
Not easily. The userdata partition is encrypted and you have a locked phone, so essentially you would need to hack the phone.
If you had an unlocked phone, you could boot into TWRP and you know the rest.

Vulkaistos said:
I never had this problem but have you tried the pull files option in NRT, it is able to do a lot of things with loked Bl, Stock Recovery?
Click to expand...
Click to collapse
If it can't be done manually, NRT won't be able to do it either. Plus I feel that toolkits will someday become the foundation for the demise of humanity as a whole.
sfhub said:
Not easily. The userdata partition is encrypted and you have a locked phone, so essentially you would need to hack the phone.
If you had an unlocked phone, you could boot into TWRP and you know the rest.
Click to expand...
Click to collapse
That's what I'm coming up with. I'm wondering if the adb sideload option within the stock recovery will grant me access to traditional adb commands instead of it's singular purposed commands - I'll find out soon. On another note, looks like I might not even be able to flash a system image for him either. Apparently now an OEM unlock option needs to be checked off in DEV options - which will require a bootable OS. So strange. Hopefully at a minimum a recovery reset will at least get the phone booting. If not, I won't be able to even unlock his BL to flash a fresh system image without having a currently bootable OS in order to check off that OEM unlock option. By the sounds of it, current locked BL Nexus's turn a softbrick into a hardbrick with no way to recover?!? Very un-Nexus!!

annoyingduck said:
That's what I'm coming up with. I'm wondering if the adb sideload option within the stock recovery will grant me access to traditional adb commands instead of it's singular purposed commands - I'll find out soon. On another note, looks like I might not even be able to flash a system image for him either. Apparently now an OEM unlock option needs to be checked off in DEV options - which will require a bootable OS. So strange. Hopefully at a minimum a recovery reset will at least get the phone booting. If not, I won't be able to even unlock his BL to flash a fresh system image without having a currently bootable OS in order to check off that OEM unlock option. By the sounds of it, current locked BL Nexus's turn a softbrick into a hardbrick with no way to recover?!? Very un-Nexus!!
Click to expand...
Click to collapse
adb sideload doesn't have full adb access, only adb sideload.
You can flash without unlocking if you download the FULL OTA google started providing a couple of months ago. This can be flashed via adb sideload and is essentially equivalent to factory image, but flashable from stock recovery without needing to unlock bootloader. Factory reset when done and it will have same effect as flashing factory image.

sfhub said:
adb sideload doesn't have full adb access, only adb sideload.
You can flash without unlocking if you download the FULL OTA google started providing a couple of months ago. This can be flashed via adb sideload and is essentially equivalent to factory image, but flashable from stock recovery without needing to unlock bootloader. Factory reset when done and it will have same effect as flashing factory image.
Click to expand...
Click to collapse
Yeah, just tried that. Still not booting. Something's corrupted, may even be hardware related. At this point it seems only a full image flash would be the only option to get the device to even boot - which simply cannot be done due to the OEM unlock option not being enabled. Me no likely that new addition
Sent from my XT1575 using Tapatalk

annoyingduck said:
Yeah, just tried that. Still not booting. Something's corrupted, may even be hardware related. At this point it seems only a full image flash would be the only option to get the device to even boot - which simply cannot be done due to the OEM unlock option not being enabled. Me no likely that new addition
Click to expand...
Click to collapse
The FULL OTA *is* a full image flash.
Did you factory reset?

The image flash fails, then reads succeeded. Still will not boot past the splash screen. Hangs, then goes black. I don't think the OTA zips flash all partitions like the factory image does.
Sent from my XT1575 using Tapatalk

annoyingduck said:
The image flash fails, then reads succeeded. Still will not boot past the splash screen. Hangs, then goes black. I don't think the OTA zips flash all partitions like the factory image does.
Click to expand...
Click to collapse
Guarantee they (the FULL OTA from factory image site) do. Open up the zip file. They even flash in more granular detail than the factory image. The only thing it doesn't do is wipe user/cache, which can be performed by factory reset.
I don't know what it means for the image flash to fail then read succeeded.

sfhub said:
Guarantee they (the FULL OTA from factory image site) do. Open up the zip file. They even flash in more granular detail than the factory image. The only thing it doesn't do is wipe user/cache, which can be performed by factory reset.
I don't know what it means for the image flash to fail then read succeeded.
Click to expand...
Click to collapse
Neither do I, it's a first.
Sent from my XT1575 using Tapatalk

annoyingduck said:
Neither do I, it's a first.
Click to expand...
Click to collapse
Sorry, I should be more clear, could you list what it says.
It sounds like the flash script is not checking for errors at the end so there is some error flashing within one of the partitions, but the overall script is saying everything good.