Hey Guys, I flashed CM10 last night and before doing it I forgot to make a nandroid backup so what would I do to get back to stock??
HTC ONE X
HTC_001
Hello again!
There's a stock backup made by me in this thread: http://forum.xda-developers.com/showthread.php?t=1975140
Pick the 3.14.401.31/HTC__001. You need to have twrp recovery and a 1.3x hboot.
Restore by putting the backup on /sdcard/TWRP/BACKUPS/ and restoring like normal.
Also flash the linked boot.img.
Cheers!
Sent from my One X
For future reference and for other XDA users,
MAKE A NANDROID BACK UP, JUST DO IT.
Related
Hello people.
So i unlocked my phone and rooted it and before installing a custom rom i nandroid backed up the stock rom via cwm.
Then i flashed a custom one and also backed it up.
Problem is that if i try to restore either of the two backups i get a md5 mismatch and they won't restore...
Is cwm backup broken? Or am i SO unlicky that both of my backups got corrupted??
Many thanks in advance
Sent from my CoreDroid powered HTC One X via Tapatalk 2
the only time i've had this problem is when i try to restore a back-up created by an older version of the recovery
jazznaura said:
the only time i've had this problem is when i try to restore a back-up created by an older version of the recovery
Click to expand...
Click to collapse
I solved it a long time ago
The problem was due to renaming the backup
Thanks for the input though!
Hi Guys,
I have a (dummy) question... I hope you can answer me...
I run 'Venom Flasher' for changing from FAUX 010VF to NCX 2.17-6.
After reboot the cell stoped in white screen.
I tryed all wipe, including factory reset, and there is no way to launch system.
I decided to restore a Nandroid backup, beliving this backup will restore all system, including kernel (FAUX).
After reset the system launch... but... For my surprise the kernel running is the NCX...
How is it possible?
For me a Nandroid backup should restore including the kernel...
Am I crazy or what did I do wrong?
Thanks all!!!
Ps.: the nandroid backup was done with Rom Manager.
You have to extract the boot.IMG from your nandroid and flash that in fastboot, then restore your nandroid. Without s-off, recovery can't flash the boot.IMG
sent from my One X using xda venom premium
Since we don't have soff, kernels must be flashed manually from a pc/mac using fastboot. Just make sure you flash that from your nandroid backup and no other version.
Sent from my HTC One X using xda premium
I am currently using cm10 with hellboy kernel and have a cvm backup of stock rom. I was wondering if *touchwood* something were to happen to the custom rom will a simple recovery be enough to get back to sense? or is there some kernel which will have to be flashed first? or is ruu the only way of going back to sense?
if u have a nandroid backup of stock ROM u can restore it and flash the boot.img found inside that particular backup.if u do not have a stock backup u will have to apply ruu or u can even restore nandroid backups of stock ROM found on XDA.
Sent from my One V
I just want to confirm this and it might be a foolish question... But if I'm using AOKP and I have a CM10.1 backup, can I do a restore to that backup and it will restore to that ROM as well? Or do I need to re-flash CM10.1 before restoring the backup?
Thanks, still figuring all this out!
The backup contains everything of the rom. Apps/contacts...you name it. Make sure when you are coming from another rom back to the backup to flash the boot.img from the backup !
Mr Hofs said:
The backup contains everything of the rom. Apps/contacts...you name it. Make sure when you are coming from another rom back to the backup to flash the boot.img from the backup !
Click to expand...
Click to collapse
Thanks for the quick answer! It actually looks like CWM automatically does the boot.img as well! At least for AOKP back to CM10.1...
Thanks again!
A nandroid backup contains all ! ,the recovery at the time of backing up. Even the boot.img. restoring a nandroid backup wont restore the boot img. It needs to be flashed manually
Hey guys, just a quick question about restoring from a nandroid backup. Let's assuming I'm using custom rom A and made a nandroid backup of it. Then later on, I change to custom rom B and made another nandroid backup of that.
Well, assuming the boot.img from both custom rom A and B are different, then say if I were to restore back to custom rom A, I would have to re-flash the boot.img for that rom correct? OR, will restoring custom rom A from the nandroid backup also flash the boot.img for me automatically?
I came from other phones where flashing a new rom or from a nandroid backup is simply a one-step process. HTC One X is the first phone I've used where I have to deal with flashing the boot.img as an additional step as well, so just wanna confirm if this is the case for a nandroid restore as well.
chaoscreater said:
Hey guys, just a quick question about restoring from a nandroid backup. Let's assuming I'm using custom rom A and made a nandroid backup of it. Then later on, I change to custom rom B and made another nandroid backup of that.
Well, assuming the boot.img from both custom rom A and B are different, then say if I were to restore back to custom rom A, I would have to re-flash the boot.img for that rom correct? OR, will restoring custom rom A from the nandroid backup also flash the boot.img for me automatically?
I came from other phones where flashing a new rom or from a nandroid backup is simply a one-step process. HTC One X is the first phone I've used where I have to deal with flashing the boot.img as an additional step as well, so just wanna confirm if this is the case for a nandroid restore as well.
Click to expand...
Click to collapse
You have to flash the boot.img for the ROM you're restoring through fastboot. Recovery cannot flash boot.img for you since you need S-OFF, which impossible to achieve (let's not go there).
tomascus said:
You have to flash the boot.img for the ROM you're restoring through fastboot. Recovery cannot flash boot.img for you since you need S-OFF, which impossible to achieve (let's not go there).
Click to expand...
Click to collapse
yup got it. Thanks!