I saw that TWRP was updated to 2.3.3, so I first made a backup of boot and recovery partitions in TWRP and named the backup "recovery" with compression enabled. I then rebooted system to use Flash Image GUI and the device hung at the boot animation. I reflashed the kernel in fastboot, wiped cache and dalvik, and it still hangs. I can still boot into recovery (never actually updated). Do I need to reflash the ROM? Was running King Kang and b6.
Edit: Well ended up doing a full wipe restoring rom and tibu. Still no idea what happened though. Making a backup shouldn't mess anything up like this...
Related
I have the Nexus S 4G from Sprint and I was trying out the new recovery from TeamWin. Here is what I did:
flashed TeamWin recovery, boot into recovery, made nandroid backup (compressed), reboot into recovery, full wipe, restore nandroid, reboot.
With those steps everything went fine and my phone was running as normal, so I decided to add another step to my testing of the new recovery.
reboot into recovery, full wipe, flash cm7 nightly, boot into freshly installed rom, setup rom as normal. Then I booted back into recovery, full wipe, restore nandroid, reboot.
This time it boots into bootloader saying no boot image or recovery found and this is where the trouble begins. I booted into recovery, and its still teamwin recovery so I try to restore nandroid again and same results. So I go and fastboot flash clockworkmod recovery and boot into it. I try to restore nandroid that I have backed up for clockworkmod and it says can't write boot image. I tried newer version of clockworkmod with no result. I tried fastboot flash back to stock and still boot image won't flash. Tried odin and it hangs at the boot image also.
Anybody have any ideas that I can try, or am I just screwed?
Bump
Sent from my PC36100 using XDA App
I tried to flash a cm10 rom and i did thought i flashed the boot.img separately as i read you have to but it was stuck booting for at least 25 min so i gave up with that and tried to restore from a backup i made with twrp. I restored from the backup and tried to reboot but nothing happens, it shows the htc screen and then turns black and thats it. I can go into bootloader and recovery but im not sure what to do to get back. Should i try a ruu?
ez4nick said:
I tried to flash a cm10 rom and i did thought i flashed the boot.img separately as i read you have to but it was stuck booting for at least 25 min so i gave up with that and tried to restore from a backup i made with twrp. I restored from the backup and tried to reboot but nothing happens, it shows the htc screen and then turns black and thats it. I can go into bootloader and recovery but im not sure what to do to get back. Should i try a ruu?
Click to expand...
Click to collapse
Maybe it was a bad restore? or a bad backup? You could try restoring from your backup again.
Or blaze on and see if you can get CM10 up and running.
Did you wipe /cache/dalvik/system when coming from stock (before installing)? I've seen situations (on other devices), Where I've had to delete the /data partition as well, I'm not sure why it wouldn't boot, but it refused to get past the CM load screen until the /data partition was wiped. If it's a new phone and you don't have too much on the sdcard, this might be worth trying.
Once you have TWRP flashing ROM's shouldn't be too bad, it's just the "fastboot flash boot boot.img" that catches people out usually.
you still have to flash boot.img separate before/after a twrp restore.
Grab the boot.img from a stock rom
Wipe cache/dalvik
Factory reset
Bootloader, fastboot usb, then fastboot flash boot boot.img
Then restore the backup
Thanks everyone for the responses, I was able to get it working after trying a few more times and wiping everything. Not sure why it didnt work earlier but all of a sudden after trying it just worked.
Sorry if this has already been asked; I tried searching, but I couldn't find anything.
I'm running Exodus version 5.1-20150911-NIGHTLY-bacon, TWRP 2.8.6, Exodus stock kernel
I'm trying to update to a new nightly, but I always get stuck in a bootloop.
Here's what I do:
Reboot to recovery
Nandroid backup
Wipe data, system, cache, Dalvik
Flash the new ROM (I tried COS 12.1 once, but it didn't work; I mostly try flashing the latest Exodus nightly_
(sometimes) Flash xposed-v74-sdk22-arm-by-romracer (it doesn't make a difference if I don't flash it)
Restore only the data from the last nandroid
Now when I reboot I'll just be stuck in the boot animation or I'll be able to pass the animation and I'll just be stuck in a loop setting up the apps.
If I don't flash xposed, but still restore the nandroid I'll boot up faster, but I get System UI has Stopped and then the phone goes into a boot animation loop
If I don't restore the nandroid it works fine and boots up way faster.
How can I update while keeping my app data (my xposed data isn't that important to me if that'll make a difference)?
RustySpackleford said:
Sorry if this has already been asked; I tried searching, but I couldn't find anything.
I'm running Exodus version 5.1-20150911-NIGHTLY-bacon, TWRP 2.8.6, Exodus stock kernel
I'm trying to update to a new nightly, but I always get stuck in a bootloop.
Here's what I do:
Reboot to recovery
Nandroid backup
Wipe data, system, cache, Dalvik
Flash the new ROM (I tried COS 12.1 once, but it didn't work; I mostly try flashing the latest Exodus nightly_
(sometimes) Flash xposed-v74-sdk22-arm-by-romracer (it doesn't make a difference if I don't flash it)
Restore only the data from the last nandroid
Now when I reboot I'll just be stuck in the boot animation or I'll be able to pass the animation and I'll just be stuck in a loop setting up the apps.
If I don't flash xposed, but still restore the nandroid I'll boot up faster, but I get System UI has Stopped and then the phone goes into a boot animation loop
If I don't restore the nandroid it works fine and boots up way faster.
How can I update while keeping my app data (my xposed data isn't that important to me if that'll make a difference)?
Click to expand...
Click to collapse
Why are you bothering to wipe if you're restoring your nandroid data anyway? Restoring the data is just canceling the wipe you just did. If you want to flash and keep your data just dirty flash the ROM update (a dirty flash means installing the zip while only wiping cache and dalvik cache).
Heisenberg said:
Why are you bothering to wipe if you're restoring your nandroid data anyway? Restoring the data is just canceling the wipe you just did. If you want to flash and keep your data just dirty flash the ROM update (a dirty flash means installing the zip while only wiping cache and dalvik cache).
Click to expand...
Click to collapse
I didn't realize that.
Edit: How do you clean flash and keep your data?
RustySpackleford said:
I didn't realize that.
Edit: How do you clean flash and keep your data?
Click to expand...
Click to collapse
You can't, that would defeat the purpose of a clean flash.
so i wanted to backup my oneplus one using twrp 3.0 and for some reason i decided to wipe the cache before i backed it up. I went to wipe (just the regular cache) and it kept trying to wipe but it never succeeded so i just forced rebooted it went back to twrp and backed up my phone. Once the backup was done i tried to boot it up and i was met with a boot loop. Then i kept rebooting my phone and no luck. then i tried to completely wipe my phone. well just a factory reset. it didn't work i was greeted with an error saying my cache is not mounted or something like that. so now i cant even wipe anything at all and i think twrp has a feature where you can access files from recovery and that doesn't work for me. adb isnt working either i was trying to push a file. What im trying to do is flash a newer version of twrp or try to adb sideload my same rom. but i dont have access to my same rom cause the links are down. my rom is minimal os btw. any ideas ?
Edit: I've fixed the problem by booting into fastboot and flashing a newer version of twrp 3.0.2. then i wiped the cache and it was successful. then i booted up and it works!
Hi,
I have tested the liquidremix rom which is great, but I still wanted to go back to my stock OSS
So I started TWRP, hit restore, everything seem to work fine, but when I reboot the system I'm stuck at the boot animation.
When I reboot the device to TWRP and check the file manager or my backup folder there are only cryptic and weird letters...
How do I restore my backup properly ?
Try to go back to TWRP 3.2.1.0 i think that that works
everything is gone, you will have to restore with the brick tool, happened to me last week and still not sure why, apparently backing up with TWRP you only need to ticket DATA and that's it.
You need to do two things whenever you restore with TWRP. First is factory reset in TWRP before the restore (that will wipe data). Second is restore system, boot, and data ONLY.
The weird file names and cryptic letters is from the encryption from the old rom. I strongly recommend that you invest in an OTG flash drive so you can store TWRP backups on it. Then you can properly wipe the phone. On the plus side this has happened to me before and I never needed anything special like the unbrick tool to get my TWRP backup up and running smoothly.
and there is a better twrp than twrp. The official is by Dees Troy and the un-official one by Joe Moss Jr. is here. https://forum.xda-developers.com/oneplus-6/development/recovery-twrp-3-2-2-0-touch-recovery-t3813317
Joe's big improvement is a usable 'mtp', ie. access that thumb drive.
Also puts the vibration back in to the key press.
First if you r seeing weired letters in twrp like xdjdhdhdhd folders. Then go to fastboot mode flash newest twrp. Img then ij recovery first flash your liquid remix furst, then flash twrp installer zip niw reboot to recovery.
Now factory reset your phone.
Now if you have oos backup. Then restore everything except system.
And then restore system alone at last now reboot it will work.
your gonna need the flashable oos 5.1x which is one here
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
fastboot to twrp
abd push the stock.zip to the phone <-assuming you know this.
and flash it from twrp.
reboot
fastboot twrp again and flash twrp.
this is where decryption comes in handy
Restoring backups with twrp will fail almost all the time. I've yet to do a successful restore and I've tried every method. You're gonna have to flash back to stock OOS and start over.
If anyone has successfully restored more than one backup then I would start a new thread with the exact method you used.
That worked.
I still wonder why not to restore system.
If I take a nandroid backup should one backup
system or system image, data or data image ?
I was trying a new rom the Resurection Remix V6.2.0 Android 8.1.0. i wanted to go back to my TWRP Backup of OOS 5.11 . I wiped data/cache/System . Tried to restore rom . it restored successfully but i didnt do wipe data thing. when i tried to reboot twrp blu, the recovery was lost. then i had to fastboot boot reovery. and lot of wierd folders were created on my phone internal memory. All data lost.
i had to flash the full 5.11 stock zip via twrp. tried to reboot again lost in bootloop. Switched back to stock recovery and make a factory reset then it booted.
switched off the phone back to Blu spark TWRP. again wipe data cache and system. Then restore the TWRP Backup previously double saved on a usb drive. This Time it restored successfully and booted as well fine.
i think i should have made a factory reset or format data before restoring from A Lineage OS Rom OS to OOS TWRP Backup
thats what made the whole internal drive mess and to be formatted as well
My Question is it only important to format data and then restore twrp or also backup and make restore of system.img of OOS backup as well