Ok I have a 5x and it was setup like this:
6.0.1, rooted, elemental x kernel
I got curious and wanted to try out N, so I made a full back up (every box checked) in TWRP. I then copied the whole entire TWRP folder onto my computer with the backup inside that folder.
I then proceeded to flash N, which went fine and tried it for a day or so and wanted to go back to my backup of 6.0.1, so I flashed the phone entirely back to 6.0.1 (all stock images), then copied the folder back onto the phones internal sd, then flashed twrp...booted into twrp and choose to restore that backup and it starts restoring for a while and then reboots, and bootloops. Phone also says its corrupted during boot.
Is there any way I can get back on that backup?
thanks
@joho5 did you flash the same security patch as you were on when you backed up the phone? That might be the issue.
If I were you I'd just flash the latest images, flash TWRP, then just restore data from TWRP. If that works you can flash EX and SuperSU and be almost back to where you were.
Sent from my SM-G930V using Tapatalk
Related
Just flashed the new AOKP milestone 2 yesterday. It was working fine until this morning when it spontaneously went into the google logo boot loop. Went into CMR and deleted data/cache, tried to reflash any roms. Starts to flash the rom but quits after giving an "offset xxxxx" error. Reboot gets the boot loop again. Please help.
Hey
Search on here for roms to flash using Odin or adb/fastboot.
Your phone is grand you just need to flash a stock rom using one of the above methods. Then you can re-root and apply your roms again
Good luck!
Yes. As above you need to find stock images and flash in fast boot.
Sent from my Galaxy Nexus using xda premium
Yeah, I just flashed the stock rom using fastboot yesterday. Can't do that on my computer at work. Another thing is that the restore using CWM doesn't seem to work for me. Backs up fine but I get an error at the end of the restore process(forget the exact error right now).
Not looking forward to restoring all my data and apps again for the third time in the past two days. I hate how it's difficult to using Titanium Backup to restore since the internal SD card is erased. I did back up to dropbox, but the restore only restored 6 apps from there. Ugh. Any way to transfer my backup files off the phone in CWM to my computer? Thanks
I use appmanager (team android) for backup. It lets you back up all apps, then you can copy the backup folder onto your computer. Then once you rebuild your phone, install appmanager again and copy over the backup folder. Some roms have the auto restore feature which installs all your apps once you sign into your Google account on the phone. I hate when these things happen, restoring apps is always a pain. Best of luck anyway.
Ok so I used to have a Samsung Captivate and knew how to root and flash ROMs, was pretty used to it.
I tried to do the same on my HOX, but ran into a bootloop and subsequently I think I've deleted everything on my phone. I used Hasoon2000's All in one kit and unlocked my bootloader, flashed TWRP v 2.3.3.0, but my problem arose after I tried to flash the kernel. It stayed in bootloop so I figured I'd back out and just restore back to the backup I made before flashing the kernel. However, after "successfully" restoring back I was still stuck in bootloop somehow. I know this isn't supposed to happen, it's supposed to restore back to the exact state of your phone at the time.
Anyways, I thought maybe I just needed to wipe things. I looked around and found a source that said to wipe cache, dalvik, factory reset, and system. Wipe those 4, but not external storage or android secure. So I wiped those 4 and I intended to try the backup again but it turns out that cleared everything on my phone. Now when I hit "restore" there is nothing to select. I also used to have a custom rom on the virtual sdcard, but that's gone too.
When in TWRP and I go into "install" the only thing in /sdcard is now TWRP. After looking around, it looks like my only option is to mount the phone to my computer via TWRP and somehow download the standard OS for my One X again. Also in the Mount menu it lists "mount system, mount data, mount cache, mount sd card" I can only check the first 3 options and when I do my computer asks me if I want to format it. I guess I can't mount the sd card because I deleted everything?
If anyone has the time to help me out that would be AMAZING. Right now I don't even care about being able to flash my custom ROM, I just want to get my phone back to functionality. I would love a conversation and would be willing to gmail chat if willing.
Also my phone is the ATT version, 2.20 (or I guess it was before I deleted everything).
Thank you in advance for any help.
I guess the fastest way to get your phone working again is using RUU file, you ll find how to do it here (method 2) or here
It stayed in bootloop so I figured I'd back out and just restore back to the backup I made before flashing the kernel. However, after "successfully" restoring back I was still stuck in bootloop somehow. I know this isn't supposed to happen, it's supposed to restore back to the exact state of your phone at the time.
Click to expand...
Click to collapse
Restoring backup doesnt restore kernel ( boot.img ), you have to flash it manually with fastboot.
Dude. U think htc offers same freedom as Samsung . U are WRONG. If u flash a rom or restore a backup. U also need to flash boot.img separately from pc. Use fastboot flash boot boot.img. i assume you know the basics. Htc don't have s-off , so writing to nand protected system storage is restricted. If u read a little you might have got this. This will solve boot loop prob
Sent from my HTC One X using Tapatalk 2
Fixed
Thanks Yasounet. I managed to flash viper in the end.
Any reason to choose one method over the other?
I'm running rooted stock 4.3 (MK1) on SM-P600 and I've done a nandroid backup in TWRP (which I'm assuming I can restore if I don't like KK).
drdoombot said:
Any reason to choose one method over the other?
I'm running rooted stock 4.3 (MK1) on SM-P600 and I've done a nandroid backup in TWRP (which I'm assuming I can restore if I don't like KK).
Click to expand...
Click to collapse
Odin is clean install (wipe everything flash a fresh O/S). OTA is upgrade or dirty flash, you still able to keep your setup and all your installed apps. If your phone is running smooth without any issue then OTA should be fine. If you have weird issues, then Odin is recommended. I see you already have TWRP and probably already rooted that means you can not use OTA method and if you use Odin you will wipe out everything including TWRP, root, your setup all the download apps, system/user data and so on. Your phone will be like a new one. This bring us to the point that you will NOT able to restore 4.3 (you will need to reflash TWRP and so on..) and we have mix reports about once you on Kitkat it's not possible to flash back 4.3 due to different bootloader.
buhohitr said:
Odin is clean install (wipe everything flash a fresh O/S). OTA is upgrade or dirty flash, you still able to keep your setup and all your installed apps. If your phone is running smooth without any issue then OTA should be fine. If you have weird issues, then Odin is recommended. I see you already have TWRP and probably already rooted that means you can not use OTA method and if you use Odin you will wipe out everything including TWRP, root, your setup all the download apps, system/user data and so on. Your phone will be like a new one. This bring us to the point that you will NOT able to restore 4.3 (you will need to reflash TWRP and so on..) and we have mix reports about once you on Kitkat it's not possible to flash back 4.3 due to different bootloader.
Click to expand...
Click to collapse
I updated via Odin and it was a dirty flash and everything works fine. I can still create a folder on the external sd and copy a file from the internal sd to the folder that I created on the external sd.
Regards
colin
colint3 said:
I updated via Odin and it was a dirty flash and everything works fine. I can still create a folder on the external sd and copy a file from the internal sd to the folder that I created on the external sd.
Regards
colin
Click to expand...
Click to collapse
The same for me, but I had to root it again. The root was lost, but everything alse working fine. ( I have sm-p601)
Any help or guidance will be appreciated.
I just got a replacement phone from Verizon with 46A and these are the steps i followed to try and restore a stock rooted lollipop rom from my old phone.
-flashed to 10B by TOT method
-rooted with Stump
-downloaded TWRP from play store
-flashed and got to TWRP recovery successfully
-created a new backup with just the boot.img
-placed the old nandroid backup in that folder
-wiped cache and dalvik/art
-flashed XDABBEB's VS985 24B bootstack
-restored my nandroid backup
...and then i kept getting a "secure boot error" at startup. Boot verification error. I could only get onto TWRP and download mode. I don't know what i did wrong. I looked through this forum for solutions but couldn't find any. So long story short, i ended up flashing back to 10B via TOT method. Any solutions to restore my old backup?
also another strange thing was when i moved my old backup to the new folder, it wouldn't show the checkboxes for boot, data, system etc to restore. i had to place the old backup in the same folder with the boot.img and i had to copy and replace it with the old backup for it to show when trying to restore it.
That used to happen to me when the boot image wasn't bumped. Can you try flashing the sharpening mod so boot can be bumped, and see if it solves your problem?
myclarity said:
That used to happen to me when the boot image wasn't bumped. Can you try flashing the sharpening mod so boot can be bumped, and see if it solves your problem?
Click to expand...
Click to collapse
Thanks for your help. Where can i locate the sharpening mod? Also before i do this again, should i backup my 10b rom i'm on now?
Hello
Need some help figuring out how to go back to stock.
I have already downloaded the latest TWRP backup and recovery for my CID (621). Used 1.92.709.1 version by @topjohnwu.
I put it into the TWRP Backup folder and restored it. Now phone bootloops when I turn it on.
The question is: what am I doing wrong?
(I was running LeeDroid 4.00 Nougat ROM on the moment I decided to go back to stock)
I had the same problem yesterday when I was trying to revert to stock my self.
Turned out I had forgot to format (Did a wipe instead) the data partition and the now un-decryptable encryption was messing up the boot process.
Rebooted into twrp and formated (Not wiped) the data partition -wich also removes the encryption- and it booted normally.
I still had some other issues though, think it's because I was recovering from a sort-off allready messed up backup I guess, so I ended up flashing back the stock recovery and did an RUU update to the most recent stock nougat from SD instead. As a bonus I was able to do a Oreo OTA the moment it booted the forst time.
Elegiacal said:
Hello
Need some help figuring out how to go back to stock.
I have already downloaded the latest TWRP backup and recovery for my CID (621). Used 1.92.709.1 version by @topjohnwu.
I put it into the TWRP Backup folder and restored it. Now phone bootloops when I turn it on.
The question is: what am I doing wrong?
(I was running LeeDroid 4.00 Nougat ROM on the moment I decided to go back to stock)
Click to expand...
Click to collapse
Is your firmware newer than 1.92.709.1? If so you'll either need a newer backup that matches your firmware version or an RUU.zip that is the same or newer than you current firmware version.
What made you want to go back?