Related
How do I backup my phone before doing a hard reset, unlocking the boot loader or installing a ROM?
use something like mybackup pro and post in the correct section next time
In Cwm there is a back up restore option
Sent from my HTC VLE_U using XDA
yes, But the OP doesnt have CWM yet, To get it he will need to unlock bootloader, Which resets the phone.
azzledazzle said:
yes, But the OP doesnt have CWM yet, To get it he will need to unlock bootloader, Which resets the phone.
Click to expand...
Click to collapse
does it also delete the "sd card" contents?
I don't think that the stock recovery supports nandroid backup. you'll need at least an unlocked bootloader and a costum recovery go make a nandroid Backup. So Only way is crossing fingers when flashing recovery.
Sent from my HTC One S using XDA
Bricolo_fr said:
does it also delete the "sd card" contents?
Click to expand...
Click to collapse
No just a factory reset. Meaning all apps and data will be gone...
Or so ive heard anyway, I unlocked mine as soon as i received it, so i wouldnt have noticed if it was wiped or not lol
Thread cleaned up a bit and moved
I just flashed the 4.1.2 factory image on my i9023, but I can't find this script anywhere, in order to stop Android from overwriting the custom recovery.
Did something change, that I'm not aware of?
Sent from my Nexus S using xda app-developers app
The new cwm recovery asks you when you exit if you like to disable stock recovery flashing
Sent from my Nexus S using xda app-developers app
raducux said:
The new cwm recovery asks you when you exit if you like to disable stock recovery flashing
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
not a big fan of the new cwm. I wonder what happened to the script....
Logomotph said:
I just flashed the 4.1.2 factory image on my i9023, but I can't find this script anywhere, in order to stop Android from overwriting the custom recovery.
Did something change, that I'm not aware of?
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
It doesn't exist anymore, even on 4.1.1. Guess Google got rid of it.
madd0g said:
It doesn't exist anymore, even on 4.1.1. Guess Google got rid of it.
Click to expand...
Click to collapse
If I remember properly, the official ota still has it, it only disappeared on L.
So, how do you manually disable recovery rewrite, if it's no longer there?
Logomotph said:
If I remember properly, the official ota still has it, it only disappeared on L.
So, how do you manually disable recovery rewrite, if it's no longer there?
Click to expand...
Click to collapse
I remember flashing JRO03E and it wasn't there already. You don't need to disable anything, since the recovery doesn't get rewritten without the script (didn't you try booting into custom recovery to see if it stuck?). If someone wants the stock recovery, it's in the image archive anyway.
[edit] After some thinking - I was stating that the factory images don't include it, but I checked the OTA zips (JRO03E and L) and you're correct for those, they DO include the script.
madd0g said:
I remember flashing JRO03E and it wasn't there already. You don't need to disable anything, since the recovery doesn't get rewritten without the script (didn't you try booting into custom recovery to see if it stuck?). If someone wants the stock recovery, it's in the image archive anyway.
[edit] After some thinking - I was stating that the factory images don't include it, but I checked the OTA zips (JRO03E and L) and you're correct for those, they DO include the script.
Click to expand...
Click to collapse
You're right, it stuck. Although, when I flashed the L factory image, it didn't stick for some reason, so I assumed this will do the same. Thanks!
Sent from my Nexus S using xda app-developers app
I'm sure this is discussed already but I can't seem to find it so if someone can help me or point me in the right direction.
I have a VZW GS3 that I have rooted, unlocked the boot loader and flashed CWM recovery. I then made a nandroid.
The main reason I did this was because I wanted Jelly Bean, and since Verizon is the slowest, I didn't want to wait so I installed custom ROMs.
Now that Verizon has released JB, I want to go back to my nandroid and then use the OTA firmware update service to upgrade.
Am I missing anything along the way that's essential for this to work?
Will the updated software re-root and/or relock my bootloader?
Will this automatically update the Baseband from my current VRLG7 to whatever the new one is?
One other thing, Will I still have CWM recovery after this happens? or will it revert back to stock recovery? or do I need to manually do anything to the recovery?
You're doing this to ultimately stay stock? Do you intend on flashing roms again or no? If you did a nandroid just after ONLY rooting and unlocking bootloader then restore it. Here's a step by step:
1) boot into CWM, restore your rooted, stock nandroid
2) Download EZ recovery, flash stock recovery
3) Wait for OTA
The OTA will relock your bootloader and unroot your phone. The JB OTA will also update your modem, and everything else, to VRBLK3.
One other thing, Will I still have CWM recovery after this happens? or will it revert back to stock recovery? or do I need to manually do anything to the recovery?
Click to expand...
Click to collapse
No, you will lose CWM if you do what I detail above. The OTA will fail if you still have CWM installed.
SlimSnoopOS said:
You're doing this to ultimately stay stock? Do you intend on flashing roms again or no?
Click to expand...
Click to collapse
For the time being I intend on remaining stock, but I still want to root. Maybe once CM10.1 becomes stable, I'll go back to it, as of now I've had too many bugs with 10 nightlys and stable and 10.1 nightlys.
SlimSnoopOS said:
If you did a nandroid just after ONLY rooting and unlocking bootloader then restore it
Click to expand...
Click to collapse
I don't recall, but it's possible I did it after flashing CWM recovery, would that make a difference?
Thanks for your help!
levilib said:
For the time being I intend on remaining stock, but I still want to root. Maybe once CM10.1 becomes stable, I'll go back to it, as of now I've had too many bugs with 10 nightlys and stable and 10.1 nightlys.
I don't recall, but it's possible I did it after flashing CWM recovery, would that make a difference?
Thanks for your help!
Click to expand...
Click to collapse
Nah I was just verifying to see if you modified any system settings or apps while on ICS TW. You should be in the clear as long as you reset CWM to stock recovery if all you did was root, unlock, then perform a nandroid.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Nah I was just verifying to see if you modified any system settings or apps while on ICS TW. You should be in the clear as long as you reset CWM to stock recovery if all you did was root, unlock, then perform a nandroid.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
before I restore the nandroid in CWM, do I need to do any wiping? cache, dalvik or full wipe?
levilib said:
before I restore the nandroid in CWM, do I need to do any wiping? cache, dalvik or full wipe?
Click to expand...
Click to collapse
Absolutely.
Sent from my SCH-I535 using xda app-developers app
so which wipe(s) do I need to do?
levilib said:
before I restore the nandroid in CWM, do I need to do any wiping? cache, dalvik or full wipe?
Click to expand...
Click to collapse
No you do not, the nan will overwrite everything anyways. If you feel better then factory reset and clear caches, but it's not necessary.
Sent from my VS920 4G using xda app-developers app
thanks
I followed the instructions above and I'm back on my rooted TW.
When i try and update i get the following message:
Service Unavailable
To check for system updates, go to Settings > About device when service is available
What's wrong, how do i fix that?
searched around on google and a lot of people had the same warning error, multiple solutions were offered but none of them worked.
in the end, I ended up installing from odin completely stock unrooted, locked bootloader etc 4.0.4 (as f i want to return my phone to verizon) and once i did that it automatically updated to 4.1.1
I have Verizons S3. I recently rooted and unlocked the bootloader and have TWRP recovery. I was on 4.1 JB. I made a Nandroid Backup of System and Data. I then flashed the CM10.1 Monthly ROM, and all seemed to be working fine. However, I was having some issues with my app backups and the weird "emulated" directory structure. So I decided to go back to my Nandroid Backup and start over.
I went into TWRP, did a factory reset, cleared System Data, cache/dvalick cache, then I restored the Nandroid Backup (system and data). TWRP said it was successful and asked to reboot. When I did, the Samsung logo flashes, and then the screen stays black. I tried going back into recovery, but it won't let me. I can get to download though.
I think I'm going to have to use Odin to reflash a ROM as I can't get into recovery, right? But I'm also trying to understand what I did wrong. Did I forget a step? Did it have something to do with differences between 4.1 and 4.2? I'm new to this, and have searched the forums but can't find anything that answers my questions specifically. I appreciate the help.
anacree said:
I have Verizons S3. I recently rooted and unlocked the bootloader and have TWRP recovery. I was on 4.1 JB. I made a Nandroid Backup of System and Data. I then flashed the CM10.1 Monthly ROM, and all seemed to be working fine. However, I was having some issues with my app backups and the weird "emulated" directory structure. So I decided to go back to my Nandroid Backup and start over.
I went into TWRP, did a factory reset, cleared System Data, cache/dvalick cache, then I restored the Nandroid Backup (system and data). TWRP said it was successful and asked to reboot. When I did, the Samsung logo flashes, and then the screen stays black. I tried going back into recovery, but it won't let me. I can get to download though.
I think I'm going to have to use Odin to reflash a ROM as I can't get into recovery, right? But I'm also trying to understand what I did wrong. Did I forget a step? Did it have something to do with differences between 4.1 and 4.2? I'm new to this, and have searched the forums but can't find anything that answers my questions specifically. I appreciate the help.
Click to expand...
Click to collapse
You're supposed to backup "boot.img" as well. I'm pretty sure boot.img is the kernel which you failed to backup. The phone won't boot into your nandroid because the kernel wasn't restored as well. In TWRP: system, data, and boot are all supposed to be backed up simultaneously if you want to restore the entire nandroid. Odin flash and make sure to do a proper nandroid with all three that I listed.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
You're supposed to backup "boot.img" as well. I'm pretty sure boot.img is the kernel which you failed to backup. The phone won't boot into your nandroid because the kernel wasn't restored as well. In TWRP: system, data, and boot are all supposed to be backed up simultaneously if you want to restore the entire nandroid. Odin flash and make sure to do a proper nandroid with all three that I listed.
Click to expand...
Click to collapse
Ah, perhaps that "boot" checkbox wasn't check. =P So basically the CM10.1 boot.img is still there, but now the wrong ROM is there so it won't boot? Can I just flash the boot.img with Odin now, or will I need to do a full ROM flash?
anacree said:
Ah, perhaps that "boot" checkbox wasn't check. =P So basically the CM10.1 boot.img is still there, but now the wrong ROM is there so it won't boot? Can I just flash the boot.img with Odin now, or will I need to do a full ROM flash?
Click to expand...
Click to collapse
Flash nandroid and then try to flash a kernel. Might work Idk. Worth a shot.
sent telepathically
---------- Post added at 07:14 PM ---------- Previous post was at 07:13 PM ----------
jdub251 said:
Flash nandroid and then try to flash a kernel. Might work Idk. Worth a shot.
sent telepathically
Click to expand...
Click to collapse
Edit. Are you still not able to get into recovery? Sorry missed that in your post.
sent telepathically
jdub251 said:
Are you still not able to get into recovery? Sorry missed that in your post.
Click to expand...
Click to collapse
No, when I do the button combo for recovery, the word "Samsung" flashes, then "Galaxy S3" logo, but after that nothing...just blank screen. I was on stock Verizon s3 before this, so I guess I need to put that kernel back on the phone? Is the kernel the same as the bootloader? Can I use the unlocked bootloader referenced in this post: http://forum.xda-developers.com/showthread.php?t=1974114?
So, I tried using Odin to flash back the stock JB 4.1.1 kernel, which should have matched my Nandroid backup, but then I got an unlocked padlock on my splash screen and then the yellow triangle. blah. so i flashed a stock no wipe rom and that got me back into touchwiz, but I cant get into recovery no matter what i do. And I still have the padlock. I think I may need to do a stock full wipe rom?
anacree said:
So, I tried using Odin to flash back the stock JB 4.1.1 kernel, which should have matched my Nandroid backup, but then I got an unlocked padlock on my splash screen and then the yellow triangle. blah. so i flashed a stock no wipe rom and that got me back into touchwiz, but I cant get into recovery no matter what i do. And I still have the padlock. I think I may need to do a stock full wipe rom?
Click to expand...
Click to collapse
If you flashed a fully stock rom then you need to root, unlock, and install your custom recovery again.
Sent from my SCH-I535 using xda app-developers app
Ok, so I finally got time to try this again after flashing back to (what I thought) was stock Jelly Bean 4.1. I was following the directions here in this thread: http://forum.xda-developers.com/showthread.php?t=2046439
I get the VRALEC bootchain fine, phone reboots and all seems well. I got to flash TWRP 2.4, do a batter pull, and when I try to boot into recovery mode suddenly there is the Samsung splash screen with an unlocked padlock on it. Then the screen goes black and doesn't go into recovery. When I release the buttons, the phone then boots into the OS. I can still get to the download mode, but for some reason I can't get into a custom recovery. Any help on this? Please?
I used this file to wipe my phone back to stock JB: COMBINATION_I535VRBLK3_I535VZWBLK3_381038_REV09_user_low_ship.tar.md5
Thanks for the assistance. =)
Redo step three like the directions state.
Edit : In that thread, some folks even suggest waiting 5-10 mins after its successfully flashed before booting into recovery.
Sent from my SCH-I535 using xda app-developers app
Forgot to followup here, but I got it working. I left my phone plugged in after flashing the recovery for like 15 minutes. I also released the power button on trying to boot into recovery once the Samsung logo appeared. I finally got into recovery and was so happy. Thanks for the help!
Running mastamoon's unofficial CM 10.1. =)
anacree said:
Running mastamoon's unofficial CM 10.1. =)
Click to expand...
Click to collapse
Perfect! Glad you've got it all working properly!
Sent from my SCH-I535 using xda app-developers app
So I installed the lateat CM12 nightly, wasn't really impressed yet and went to go restore my backup and once it's done restoring, it get stuck at the bootscreen animation. Just keeps going and going abs going. I used the latest cwm touch recovery as CM12 is not compatible with MultiROM. I would just flash the factory img back but my computer decided to it doesn't ever want to recognize adb avid fastboot on Linux.
Anyone know where I can find a flashable zip for the factory 5.0.1 ROM? Any help would be appreciated!
Try googling Nexus 5 factory image...
Here's a flashable 5.0 : http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
Niflheimer said:
Here's a flashable 5.0 : http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
Click to expand...
Click to collapse
Now I'm assuming I'd have to unroot it and flash stock recovery and lock the bootloader to get it to update to 5.0.1?
No, it's flashable in your custom recovery. It's 5.0 though
Sent from my Nexus 5 using XDA Free mobile app
Yeap , ota needs stock recovery. Also , switch to twrp since cwm isn't playing nice with L.
jd1639 said:
No, it's flashable in your custom recovery. It's 5.0 though
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I was talking about the 5.0.1 update but thanks.
Niflheimer said:
Yeap , ota needs stock recovery. Also , switch to twrp since cwm isn't playing nice with L.
Click to expand...
Click to collapse
I'm on the stock ROM you linked too, stock recovery, and unrooted but, when I get the update for 5.0.1 and try and install it, I get an error. Do I need to relock my boatloader?
asd87 said:
I'm on the stock ROM you linked too, stock recovery, and unrooted but, when I get the update for 5.0.1 and try and install it, I get an error. Do I need to relock my boatloader?
Click to expand...
Click to collapse
You're on a custom Rom. The ota isn't going to work. And you don't need to relock your bootloader. If you can afford to wipe your data download the 5.0.1 factory image. Extract it and use the flash-all.bat
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You're on a custom Rom. The ota isn't going to work. And you don't need to relock your bootloader. If you can afford to wipe your data download the 5.0.1 factory image. Extract it and use the flash-all.bat
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
My computer is Linux, and adb and fastboot for whatever reason unknown to me, won't install. That's why I asked for a zip file of the factory image. Thanks for the help though.
asd87 said:
My computer is Linux, and adb and fastboot for whatever reason unknown to me, won't install. That's why I asked for a zip file of the factory image. Thanks for the help though.
Click to expand...
Click to collapse
Well, unfortunately, there isn't a 5.0.1 flashable rom available right now. If you can't get fastboot to work on your Linux machine you're kind of sol as you need to be 100% stock to get the ota to work. That means stock recovery in your case. Google recovery zip collection xda. There's a custom recovery flashable stock recovery there.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Well, unfortunately, there isn't a 5.0.1 flashable rom available right now. If you can't get fastboot to work on your Linux machine you're kind of sol as you need to be 100% stock to get the ota to work. That means stock recovery in your case. Google recovery zip collection xda. There's a custom recovery flashable stock recovery there.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I have the stock 5.0 recovery that I installed through Flashify. I'll barrow a windows computer or something lol
asd87 said:
I have the stock 5.0 recovery that I installed through Flashify. I'll barrow a windows computer or something lol
Click to expand...
Click to collapse
I'd work on getting adb/fastboot working on your Linux machine. You're going to need it in the long run.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I'd work on getting adb/fastboot working on your Linux machine. You're going to need it in the long run.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I've spent hours trying to get it work one night. I'll do some note searching for more advice and again thanks.
jd1639 said:
I'd work on getting adb/fastboot working on your Linux machine. You're going to need it in the long run.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Did some more digging, got it install, and flashed the factory img for 5.0.1 and twrp recovery then superSU through twrp.
Mods please lock the thread thanks.
Get wugfreshes Toolbox. It has access to all factory images. Some people are not fans of "one click solutions" but this has never let me down.
There's a flushable zip on here also. Put it in a search in the app and you should come across it. It IS the full version.
Did you ever find out why the CWM restore led to getting stuck on boot animation??
Just ran into this last night. Tried restoring 2 different CWM backups and both got stuck on boot animation.
I eventually got a new ROM flashed. Going to try TWRP recovery I suppose.
I know I never had this problem with 4.4, this was the first time I have restored a LP ROM..
one7dchevy said:
Did you ever find out why the CWM restore led to getting stuck on boot animation??
Just ran into this last night. Tried restoring 2 different CWM backups and both got stuck on boot animation.
I eventually got a new ROM flashed. Going to try TWRP recovery I suppose.
I know I never had this problem with 4.4, this was the first time I have restored a LP ROM..
Click to expand...
Click to collapse
My guess would be; cwm hasn't been optimized for Lollipop. Cyanogen has just recently started working on 5.0 and they probably haven't touched the recovery too much. But that's just my guess.
asd87 said:
My guess would be; cwm hasn't been optimized for Lollipop. Cyanogen has just recently started working on 5.0 and they probably haven't touched the recovery too much. But that's just my guess.
Click to expand...
Click to collapse
Yea figured something like that.
Got TWRP installed, will try to update after my next nandroid restore so that any old CWM users will know..