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] Stuck in Bootloader - Please help

Hi Guys
Wondering if you can help, I have checked other threads with similar titles but to no avail for my problem in which I post.
I was moving from leedriod extreme rom to viper rom.
I made the mistake of flashing the boot.img zip file rather than just the .img file.
This keeps putting me into the an unlocked bootloader, I have gone to my cwm recovery as i backed up prior to doing so, however when I restore and it completes it, I reboot and it still goes to bootloader, I tried an older restore point and I get the same.
could anyone please help me?
Many thanks
Mick

Have you tried reflashing boot.IMG ?
Sent from my HTC One X

Reflash the boot.img and you should be fine, if all fails run the RUU.

Hi and thank you for your replies.
I tried flashing the boot img with the flasher that the viper rom comes with, however kept saying failed.
I have since locked and unlocked the boot locker
locked as i wanted to run the stock rom and unlocked due to not having enough battery.
I amm currently carrying out the battery .bat mod in which it charges it up every 6 seconds.
Would you suggest I try again with the boot.img file or just go straight to stock rom?
p.s. i have latest cwm and left it on charge and it did not charge, is this related?

I will get there said:
Hi Guys
Wondering if you can help, I have checked other threads with similar titles but to no avail for my problem in which I post.
I was moving from leedriod extreme rom to viper rom.
I made the mistake of flashing the boot.img zip file rather than just the .img file.
This keeps putting me into the an unlocked bootloader, I have gone to my cwm recovery as i backed up prior to doing so, however when I restore and it completes it, I reboot and it still goes to bootloader, I tried an older restore point and I get the same.
could anyone please help me?
Many thanks
Mick
Click to expand...
Click to collapse
Have you tried wiping dalvik cache?

Hi Bossman
Yes tried wipe dalvik cache also full factory reset too!

Maybe the boot.img is corrupted? Try re-downloading.
How did you flash your boot.img? You should just extract the zip file and use their bat file to flash.
After that, re-install re-install the rom again. should be resolved.

1. Go into fastboot mode on phone
2. Load up command prompt and execute fastboot erase cache
3. Reflash boot.img
4. Flash Superwipe from ARHD thread
5. Reflash LeeDroid
Should work..

berniebennybernard said:
1. Go into fastboot mode on phone
2. Load up command prompt and execute fastboot erase cache
3. Reflash boot.img
4. Flash Superwipe from ARHD thread
5. Reflash LeeDroid
Should work..
Click to expand...
Click to collapse
+1 for this try it and if it got worked then you can move to viper later.
Sent from my HTC One X using Tapatalk 2

[Q] HTC one x stuck in bootloader, no OS found one sd

Hey guys, i've been searching, reading and googling almost anything that could help me with my situation right now.
I recently rooted my phone n soon after i decided to run a custom ROM on it. I followed the instructions,
till i reach a part in recovery mode (TWRP) i selected factory wipe which wiped everything from my sd card,
when i realized this i unplugged my phone and it kept rebooting over and over i tried to use adb sideload option
but i keep getting an error that its unable to mount.
i also tried to factory reset and the problem was still there.
i am all out of options and i really dont know what to do
right now, please help me.. :crying:

Tou did not flash the rom zip file and boot.img?

You can enter bootloader mode by holding down the volume down button.
Then you can re-flash a custom recovery via fastboot.
Then you can mount your USB and copy a custom ROM to storage.
And then flash the custom ROM, but don't forget to also flash the boot.img via fastboot (it's in the zip of the custom ROM)

robchongke said:
Tou did not flash the rom zip file and boot.img?
Click to expand...
Click to collapse
yes i did.. but remember i accidentally deleted everything including the rom.zip that was on the sd part of the htc one x

webpatrick said:
You can enter bootloader mode by holding down the volume down button.
Then you can re-flash a custom recovery via fastboot.
Then you can mount your USB and copy a custom ROM to storage.
And then flash the custom ROM, but don't forget to also flash the boot.img via fastboot (it's in the zip of the custom ROM)
Click to expand...
Click to collapse
i already have TWRP on it do i need to do a re-flash it? if so which one is suitable. thanks i'm going to try and see if this works for me

try to flash the rom maybe it still there. If not Mount your phone via recovery so you can put your rom zip file then flash.

robchongke said:
try to flash the rom maybe it still there. If not Mount your phone via recovery so you can put your rom zip file then flash.
Click to expand...
Click to collapse
ok will try that as well.. but what i normally get is that its unable to mount sd card n i get an error.. hopefully it was just a bad ROM i downloaded.. gonna try again

[Q] Disaster, fu***ed up everything? Stuck in bootloader

Hi there,
today I definitely ****ed up my phone.
So: I tried the Ice Cold Jelly 4.3 CR, everything worked, but it was pretty unstable and the batterylife was horrible.
So I decided to go back to ARHD 31.3 but in a hurry I forgot to flash the boot.img ( kinda dumb ).
So now I'm stuck in the bootloader and ( I don't know why ) the phone doesn't get recognized by my PC ( Win 8.1 ), the recovery doesn't work ( CWM 5.8.x.x ) and the phone doesn't boot in the installed Rom ( of course ).
Any Ideas? thx

Fastboot erase cache
Fastboot flash boot boot.IMG
Fastboot erase cache

melhookv12 said:
Fastboot erase cache
Fastboot flash boot boot.IMG
Fastboot erase cache
Click to expand...
Click to collapse
Well thanks a lot, but this doesn't help me, because, as I already wrote, the phone doesn't get recognized by my pc, so there is no fastboot commands possible.
Pc says the connected usb device seems to be broken please reconnect and try again

And what happens if you go in recovery to mounts and storage and mount the phone to the pc?
If it doesnt work out I suggest you flash philz recovery which also has updated touch drivers. The phone should pop up and you'll be able to copy a Rom to flash.
If that doesnt work reinstall drivers.
Sent from my HTC One X using xda app-developers app

Stefan0vic said:
And what happens if you go in recovery to mounts and storage and mount the phone to the pc?
If it doesnt work out I suggest you flash philz recovery which also has updated touch drivers. The phone should pop up and you'll be able to copy a Rom to flash.
If that doesnt work reinstall drivers.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
When I trie to get into recovery the phone loads CWM and shows it for a sec, but reboots as if it would crash.
So there is no Recovery to load into.
I can't install another recovery because the phone doesn't get out of fastboot mode.
I tried nearly al kind of drivers but none of em worked.

psyko93 said:
When I trie to get into recovery the phone loads CWM and shows it for a sec, but reboots as if it would crash.
So there is no Recovery to load into.
I can't install another recovery because the phone doesn't get out of fastboot mode.
I tried nearly al kind of drivers but none of em worked.
Click to expand...
Click to collapse
Well you can get into fastboot which means you can flash stuff?
try to flash philz recovery.
tried factory reset?

Stefan0vic said:
Well you can get into fastboot which means you can flash stuff?
try to flash philz recovery.
tried factory reset?
Click to expand...
Click to collapse
I tried factory reset, well actually I managed to get into fastboot with the phone getting recognized by my pc. Now my battery is to low to flash and i'm running the charge .bat script, hopefully it'll work

psyko93 said:
I tried factory reset, well actually I managed to get into fastboot with the phone getting recognized by my pc. Now my battery is to low to flash and i'm running the charge .bat script, hopefully it'll work
Click to expand...
Click to collapse
Pretty sure it will, after you have enough battery to flash stuff
flash philz touch recovery (recommended)
go to mounts & storage > mount usb storage
take a ROM zip of your choice and copy it once it recognizes.
Do a full wipe
flash the .zip file
reboot to bootloader and flash the boot.img

[SOLVED] How do you enter recovery mode for TWRP ? (Bootloop)

Hello everyone. I was attempting to install the Liquid Smooth 3.0 Beta ROM but it said failed in red words. So i wiped again and installed my backup. Its been stuck in boot loop. I've looked and can't seem to find how to enter recovery mode. I tried holding power + volume up + home and it just restarts the phone before it gets to the boot loop screen. Also, once I get in recovery mode, what would be the next step to fix the boot loop? Right now im reinstalling the ROM I had on backup (intergalactic) . Or should I wipe and re-install the backup?
Thanks
EDIT: Found the combo ( Volume up + home ). Now restoring my backup. If this doesn't fix the bootloop what should I do? Also when I mount my USB in recovery it doesn't show up on my computer.

TrippyAzN said:
Hello everyone. I was attempting to install the Liquid Smooth 3.0 Beta ROM but it said failed in red words. So i wiped again and installed my backup. Its been stuck in boot loop. I've looked and can't seem to find how to enter recovery mode. I tried holding power + volume up + home and it just restarts the phone before it gets to the boot loop screen. Also, once I get in recovery mode, what would be the next step to fix the boot loop? Right now im reinstalling the ROM I had on backup (intergalactic) . Or should I wipe and re-install the backup?
Thanks
EDIT: Found the combo ( Volume up + home ). Now restoring my backup. If this doesn't fix the bootloop what should I do? Also when I mount my USB in recovery it doesn't show up on my computer.
Click to expand...
Click to collapse
If you get to recovery mode, try doing a hard wipe/reset to return your phone to its original settings. You will lose all saved data so please keep your backup. Your phone may not be recognized by the computer in recovery mode but in download mode. Are you using custom recovery or stock recovery? If custom, which one?

Larry2999 said:
If you get to recovery mode, try doing a hard wipe/reset to return your phone to its original settings. You will lose all saved data so please keep your backup. Your phone may not be recognized by the computer in recovery mode but in download mode. Are you using custom recovery or stock recovery? If custom, which one?
Click to expand...
Click to collapse
Hello. How do I Hard Reset? I am using TWRP recovery mode. I've tried download mode and still not recognized. I also downloaded the latest driver.

TrippyAzN said:
Hello. How do I Hard Reset? I am using TWRP recovery mode. I've tried download mode and still not recognized. I also downloaded the latest driver.
Click to expand...
Click to collapse
Good! With TWRP, you will see the wipe option on the home screen immediately you get into recovery mode. Just do the standard wipe and then reboot to system.

Larry2999 said:
Good! With TWRP, you will see the wipe option on the home screen immediately you get into recovery mode. Just do the standard wipe and then reboot to system.
Click to expand...
Click to collapse
Just did that, still at the boot screen

TrippyAzN said:
Just did that, still at the boot screen
Click to expand...
Click to collapse
Sometimes, it may take several minutes after the reset for your phone to finally boot up so you may have to wait a bit before deciding it didn't work. However, do you recall what (stock) Android version you had before you attempted to flash the custom ROM?

Larry2999 said:
Do you recall what (stock) Android version you had before you attempted to flash the custom ROM?
Click to expand...
Click to collapse
Before I rooted? I was Jelly Bean 4.1.2 I think. But I flashed many Custom ROMs, the last one was 4.3 . The one I was installing was 4.4.2. But I dont think thats the problem, It just said failed to flash. And the back up restore was successful, just a boot loop. If I could get my computer to recognize my phone I could put my original ROM download in and flash that.

TrippyAzN said:
Before I rooted? I was Jelly Bean 4.1.2 I think. But I flashed many Custom ROMs, the last one was 4.3 . The one I was installing was 4.4.2. But I dont think thats the problem, It just said failed to flash. And the back up restore was successful, just a boot loop. If I could get my computer to recognize my phone I could put my original ROM download in and flash that.
Click to expand...
Click to collapse
Normally, if it was just a case of your phone getting stuck in a boot loop, a hard wipe/reset will fix that. If it's still not coming on, then it could be a slightly more severe case of firmware failure which, thankfully, can be easily recovered from since you can get into download and recovery modes. Your best option now would be to flash an official (stock) ROM to get your phone back in working order. From what you've said about the firmware history, stock Android 4.3 would be your best bet as you probably have the 4.3 boot-loader already. You can download the zip file you will find in the discussion thread below and flash this via TWRP recovery. The process is fairly simple. Download the zip file to your PC - do not extract. Verify the MD5. Copy to a micro SDHC card. Place the card in your phone. Boot to recovery mode. Select install and navigate your way to the zip file you just copied. Swipe across the screen to confirm installation. Wait for installation to complete. Clear your cache/dalvik. Reboot your system. Good luck!
http://forum.xda-developers.com/showthread.php?t=2658486
Before flashing custom ROMs, it is always helpful to do a lot of research as there is no easier way to brick or backdoor your phone.
NB
You need a special app to verify MD5. It's just a check to ensure you have the correct file and it downloaded correctly. If you do not have the app, check that the zip you have is about 933MB after download.

Larry2999 said:
Normally, if it was just a case of your phone getting stuck in a boot loop, a hard wipe/reset will fix that. If it's still not coming on, then it could be a slightly more severe case of firmware failure which, thankfully, can be easily recovered from since you can get into download and recovery modes. Your best option now would be to flash an official (stock) ROM to get your phone back in working order. From what you've said about the firmware history, stock Android 4.3 would be your best bet as you probably have the 4.3 boot-loader already. You can download the zip file you will find in the discussion thread below and flash this via TWRP recovery. The process is fairly simple. Download the zip file to your PC - do not extract. Verify the MD5. Copy to a micro SDHC card. Place the card in your phone. Boot to recovery mode. Select install and navigate your way to the zip file you just copied. Swipe across the screen to confirm installation. Wait for installation to complete. Clear your cache/dalvik. Reboot your system. Good luck!
http://forum.xda-developers.com/showthread.php?t=2658486
Before flashing custom ROMs, it is always helpful to do a lot of research as there is no easier way to brick or backdoor your phone.
NB
You need a special app to verify MD5. It's just a check to ensure you have the correct file and it downloaded correctly. If you do not have the app, check that the zip you have is about 933MB after download.
Click to expand...
Click to collapse
Which do I download? First or second link? Also How should I get my computer to recognize my phone? And if I do that, flashing a fresh ROM wont fix the boot loop?

TrippyAzN said:
Which do I download? First or second link? Also How should I get my computer to recognize my phone? And if I do that, flashing a fresh ROM wont fix the boot loop?
Click to expand...
Click to collapse
You need the first one since you are on TWRP. You are not connecting your phone to the computer at all so there is no worry about that. You only need to download the image to your computer and then copy it to an external Micro SD card using another device like a camera, phone, SDHC card reader/writer or SDHC card adapter if your PC has the required slot. Once you have the recovery image saved on to the external SD card, insert the card into your phone and boot into recovery mode. You will then install the zip from the card. This ROM should not only fix the boot loop, it will restore your phone to as near factory settings as possible including resetting your flash counter, installing the complete stock system and stock recovery.
Once you have your phone back in working order, you can revert to flashing custom ROMs but please be very careful and do all the research you need. Specifically, you should avoid any ROMs that may attempt to mess with your boot-loader.

Larry2999 said:
You need the first one since you are on TWRP. You are not connecting your phone to the computer at all so there is no worry about that. You only need to download the image to your computer and then copy it to an external Micro SD card using another device like a camera, phone, SDHC card reader/writer or SDHC card adapter if your PC has the required slot. Once you have the recovery image saved on to the external SD card, insert the card into your phone and boot into recovery mode. You will then install the zip from the card. This ROM should not only fix the boot loop, it will restore your phone to as near factory settings as possible including resetting your flash counter, installing the complete stock system and stock recovery.
Once you have your phone back in working order, you can revert to flashing custom ROMs but please be very careful and do all the research you need. Specifically, you should avoid any ROMs that may attempt to mess with your boot-loader.
Click to expand...
Click to collapse
Thanks for your help! That was a great idea, moving my SD card to a different device then putting the .zip in there and flashing from my device. Worked Perfectly. Didn't even have to use the restore file you linked me, I just re-flashed the old ROM i was using ( brand new, not the back up ). And its starting up now, all of my apps, widgets, wallpapers, and messages are exactly how I left them. Which is weird because of how many times I wiped and the fact that I re-flashed a brand new ROM lol.
Man this makes me not want to change ROMs anymore. Small stuff like this makes me paranoid. I don't have a back up phone lol

TrippyAzN said:
Thanks for your help! That was a great idea, moving my SD card to a different device then putting the .zip in there and flashing from my device. Worked Perfectly. Didn't even have to use the restore file you linked me, I just re-flashed the old ROM i was using ( brand new, not the back up ). And its starting up now, all of my apps, widgets, wallpapers, and messages are exactly how I left them. Which is weird because of how many times I wiped and the fact that I re-flashed a brand new ROM lol.
Man this makes me not want to change ROMs anymore. Small stuff like this makes me paranoid. I don't have a back up phone lol
Click to expand...
Click to collapse
Glad to know your phone is now functioning normally. One of your earlier restore operations probably restored your data whilst the new ROM you flashed restored the system without deleting data. Thankfully, you didn't lose anything. Now the phone is back to normal, please be careful with flashing ROMs especially custom ones.