I used to be running fission 2.4.3 with a 2.3.315 system. I made a backup in recovery. Then I flashed the 2.3.315 sbf and did the ota update to 2.3.340.
Could I restore this backup in recovery even though it was done with a previous system version? I know from experience that flashing a previous system version will brick the phone. Will this have the same effect?
Sent from my DROIDX using XDA App
no.the ota changed your boot loader the backup does not work with the new boot loader.
Related
I backed up my DI18 stock install using CW Recovery. I then installed a leaked version of DK17. I'd like to return to DI18, but when I try to do a recovery the phone hangs on the Samsung logo (after I finish the recovery and reboot).
Do I need to use Odin to go back to stock DI18 and THEN restore my phone using CW Recovery?
I just did this last night after I noticed Froyo to be too buggy. YOu have to back to stock DI18, root it then install clockwork. Then simply restore, mine works great.
Thanks! That's what I thought. I figured it was a firmware conflict or something that was blocking my boot up to 2.1/DI18.
I'm installing Clockwork now.
I was running CM6.1.1, did a backup using Clockworkmod recovery 2.5.x.x. Updated CW recovery to 3.0.0.5, then flashed GingerVillain 1.5. Decided it wasn't for me, so I wiped and then restored my CM6.1.1 image. Restore completes okay, reboot and now I'm stuck at the HTC screen. Also tried wiping and restarting, still stuck.
Is CWM 3.0 not capable of restoring Froyo roms? Do I need to reflash 2.5.x.x, then restore my CM6.1.1?
Thanks in advance!
Sorry for being so quick to make a thread. Reflash of Clockworkmod 2.5.1.3 allowed me to restore and boot my backup. Problem solved.
Before the problem, I had a 4.1.1 rooted unlocked N7 with original ROM. I decided to apply the OTA update (03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip) from TWRP recovery using the option to manually install zip updates.
The tablet rebooted, and I used Voodoo OTA RootKeeper to regain root access. Everything worked fine, I had no error messages at any moment during the procedure and the 4.1.2 update was applied successfully, as I could verify in the info section and by testing the landscape mode.
But, when I try to reboot in recovery using the option in ROM Manager, all I get is the little robot on his back image without any message. The only way to get out of this screen is to press the power button for a few seconds until it reboots into Android. Everything is fine except the recovery mode.
I tried to reflash the recovery image using Wug's Toolkit to no avail. I tried CWM, TWRP and stock recoveries but none worked. I always get the same screen with the robot on his back when I try to boot into recovery. Booting normally is always fine, only recovery seems to be affected. If I use Wug's toolkit to boot a temporary TWRP recovery image, it works but I want to be able to boot as before, with ROM Manager.
Any ideas? Is there a solution other the wipe it all and restart from scratch?
[edit] I can start into Fastboot but if I try to go to recovery from there, the same thing happens...
I fixed it by flashing the older 3.34 bootloader. So something is wrong with the new 3.41 bootloader.
There is nothing wrong with the process.
Its the users interpretation of how it works.
After updating, the file that flashes the stock recovery on boot is put back.
So he flashed in custom recovery.
Booted at which point the custom recovery is replaced with stock
Then wonders why he can't access custom recovery anymore.
Just reflash custom recovery
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
There is nothing wrong with the process.
Its the users interpretation of how it works.
After updating, the file that flashes the stock recovery on boot is put back.
So he flashed in custom recovery.
Booted at which point the custom recovery is replaced with stock
Then wonders why he can't access custom recovery anymore.
Just reflash custom recovery
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Not true. I flashed the update through cwm and everything went fine. When you reboot the system, cwm asks if you want to flash recovery and keep root. I denied to flash the stock recovery and I kept the root. After that you can't get into recovery at all (stock or cwm or whatever). but if I downgrade my bootloader to 3.34 everything is ok. I also installed new bootloader through cwm manually again and after that I can't boot into recovery.
Btw... How to flash bootloader.raw with fast boot???
Sent from my Nexus 7 using Tapatalk 2
sikagoon7 said:
I think you are a bit misinformed. When you flash the OTA the recovery-from-boot.p is installed by default. It resets the recovery to stock every time you reboot. CWM does nothing to remedy this. The only way to fix it is to remove or rename the file to disable its function. After and ONLY after this will you be able to flash recoveries by choice and boot into them.
And while it is your choice to use whatever recovery you desire I personnaly think using stock recovery and adb sideload is the safest when it comes to signed stock OTA.zips. After that you can root and flash your recovery of choice as if you have a brand new device.
When it comes to the bootloader. Stock system, boot, and recovery verify which bootloader you are using. JRO03D looks for 3.34 and JZO54K looks for 3.41. I don't know the implications of switching them but I don't think I will test that. I've already had a bad experience with dismantling a bootloader. The bootloader is an IMG file. Download the JRO03D factory image from Google's website and extract it. Inside will be a file named bootloader-grouper-3.34.img. THAT is the stock JRO03D bootloader and that is what you need to flash using: fastboot flash bootloader bootloader-grouper-3.34.img.
Click to expand...
Click to collapse
Yes I know that and did that from the beginning (renamed the file) but the point is that you can't boot into recovery (stock or whatever). It tries to boot into recovery I think but it reboots again and loads the OS. I'm using 3.34 booatloader with 4.12 and haven't got any probs yet.
Finally Got it Working
I tried one last thing yesterday. I got into ROM Manager and used the option to flash CWM Recovery. Then I rebooted in CWM (using the ROM Manager option). All was fine and when I chose the option to reboot, CWM asked me if I would like to make the custom recovery permanent because it would otherwise be rewritten at boot (this is what caused my problems, I believe). I choose to do so and it worked normally after that.
I then downloaded the TWRP recovery (http://www.teamw.in/project/twrp2/103) and installed it with Wug's Toolkit using the option to flash a permanent Recovery from a file. I didn't modify the "recovery-from-boot.p" file because I thought that CWM already did that. Tested booting into recovery again and all is finally OK with TWRP.
One of the benefits of the 4.1.2 update is that I can now boot into recovery from the Fastboot menu.
I'm in the same boat, ended up flashing the factory image for jz054k (which included the new bootloader) to try and fix.. now I'm without root and without a recovery..
I'm unlocked, but flashing alternative recoveries just doesn't work right now.. can't boot them up.
Did the original author ever get this resolved?
-m
diomark said:
I'm in the same boat, ended up flashing the factory image for jz054k (which included the new bootloader) to try and fix.. now I'm without root and without a recovery..
I'm unlocked, but flashing alternative recoveries just doesn't work right now.. can't boot them up.
Did the original author ever get this resolved?
-m
Click to expand...
Click to collapse
There are mixed reports on bootloader 3.41 and booting recovery. I have not been able to properly boot recovery from 3.41 under any circumstances. If you have this issue as well, flash the 3.34 bootloader from JRO03D. Doing this has allowed me to use recovery again.
I was running 4.1.2 with old bootloader 3.34 and had a SOD while my Nexus was charging last night.
In Faux123's kernel thread, he told me:
You should use the new boot loader and stick with CWM for now until TWRP get their stuff compatible with 4.1.2. Boot loader initialize the power regulators to some know state for the machine to boot until the kernel takes over.. and the new kernel is expecting it to be initialize certain ways... This was the biggest difference between 4.1.1 and 4.1.2... so I HIGHLY recommend using the matching bootloader...
Click to expand...
Click to collapse
Steps I had to take to get 4.1.2 (rooted, stock rom, custom kernel):
flash stock 4.1.1 boot.img and recovery.img
flash 4.1.1 bootloader 3.34
flash recovery TRWP recovery
flash SuperSU (regain root)
flash CWM lastest recovery 6.0.1.5 (beta) based on Faux123 advice above
flash 4.1.2 bootloader 3.41
No problems so far. This whole process has taken days...
I'm finally where I want to be.
Oops, wrong thread...
Hello guys.
I want to downgrade my defy+ from CM11 to stock android.
Before update the recovery and install CM11 i made a backup with CWM and now i want to restore this backup.
How can i do this? Can i install CWM using the kitkat on my phone?
Sorry for the dumb question, but I'm afraid of doing something wrong.
lucashs said:
Hello guys.
I want to downgrade my defy+ from CM11 to stock android.
Before update the recovery and install CM11 i made a backup with CWM and now i want to restore this backup.
How can i do this? Can i install CWM using the kitkat on my phone?
Sorry for the dumb question, but I'm afraid of doing something wrong.
Click to expand...
Click to collapse
I have discovered that I need it too because my phone is loked and, to enter my carrier unlock code, i need to restore my backup made with CWM.
Looking for the same.
Yesterday i have installed 2ndInit to get back CWM recovery and restore my original stock ROM image.
Android can not complete the full boot, showing the intro of my carrier during a hour while loading Android.
Reinstalled TWRP and recovered my CM11 backup.
I will try again and, if not suceded, i will flash my carrier SBF to unlock my phone.
I will inform any news about CWM restore stock ROM.
TicoDePano said:
Yesterday i have installed 2ndInit to get back CWM recovery and restore my original stock ROM image.
Android can not complete the full boot, showing the intro of my carrier during a hour while loading Android.
Reinstalled TWRP and recovered my CM11 backup.
I will try again and, if not suceded, i will flash my carrier SBF to unlock my phone.
I will inform any news about CWM restore stock ROM.
Click to expand...
Click to collapse
I think this happens because the roms use different file systems
Try the Aroma Wiper to change the file system:
http://forum.xda-developers.com/showthread.php?t=2202674
I'll try this, but now i'm without time, then i report if it work.
I got my phone working.
http://forum.xda-developers.com/motorola-defy/help/tim-brasil-signal-cm11-t2824983#post54683596
About revert to stock ROM, only doing a factory reset to format my data partition fix the boot (I did not try AROMA or safewipe.zip).
I do not tried to restore data from my stock dump after got my phone working because it was not my objective, but i think that it is possible and simple after get it working.
Thanks.
I'm on OOS 3.0 and wanting to flash 3.0.1 through stock recovery. I currently have the modified version of TWRP flashed. I'm trying to get stock recovery back but it won't boot into it. It displays the OnePlus logo and hangs there while TWRP runs fine. Can somebody help?
P.S. It's rooted and I haven't tried reflashing the system partition.
Sent from my beloved OnePlus 2 using Tapatalk
Did you solved this? I'm in the same situation and don't know how to get back stock recovery
RafaySid said:
I'm on OOS 3.0 and wanting to flash 3.0.1 through stock recovery. I currently have the modified version of TWRP flashed. I'm trying to get stock recovery back but it won't boot into it. It displays the OnePlus logo and hangs there while TWRP runs fine. Can somebody help?
P.S. It's rooted and I haven't tried reflashing the system partition.
Sent from my beloved OnePlus 2 using Tapatalk
Click to expand...
Click to collapse
If u r rooted then without wiping system partition u can't updated oxygen os 3.0.1 or 3.0.2 with stock recovery too .
So if u want to switch oxygen os 3.0.x go thru twrp and first take backup of ur data partition wipe everything except internal memory and flash new oxygen os then restore ur backedup data .
---------- Post added at 09:36 AM ---------- Previous post was at 09:34 AM ----------
jceballos said:
Did you solved this? I'm in the same situation and don't know how to get back stock recovery
Click to expand...
Click to collapse
U should also follow the same.
Yes I solved it. It turned out I was using an older modified recovery for OP2.
Sent from my OnePlus 2 using Tapatalk
If you are on OOS + TWRP and want to get back stock recovery:
1. Go into TWRP recovery
2. Go into mount and opt READ ONLY mount
3. Reboot system
OOS will overwrite the recovery with stock recovery during boot