Hi guys,
Before I rooted and flashed new roms on my M8, I took a nandroid backup of my phone as it came out of the box. However, I can't seem to restore this anymore. I'm not sure if it's a problem with the backup I took or if it's just not possible. I have restored backups of other custom roms and they have been fine.
I'm not that fussed as I'm hopeful an RUU will come out eventually. I'd just like to understand why.
I have an International unlocked M8 bought in the UK.
Thanks!
leongwengheng said:
Hi guys,
Before I rooted and flashed new roms on my M8, I took a nandroid backup of my phone as it came out of the box. However, I can't seem to restore this anymore. I'm not sure if it's a problem with the backup I took or if it's just not possible. I have restored backups of other custom roms and they have been fine.
I'm not that fussed as I'm hopeful an RUU will come out eventually. I'd just like to understand why.
I have an International unlocked M8 bought in the UK.
Thanks!
Click to expand...
Click to collapse
Which recovery did you backup with, which are you running now, and at any point did you do the GPE conversion?
Sir-Fix-a-Lot said:
Which recovery did you backup with, which are you running now, and at any point did you do the GPE conversion?
Click to expand...
Click to collapse
Hi, mate. I did the back up in TWRP 2.7.0.2 - although now I am on TWRP 2.7.1.0. Not sure if that makes a difference?
Yes I did convert to GPE at the beginning. Here's how I got to where I am today:
1) Flashed TWRP 2.7.0.2
2) Did a nandroid backup of factory state
3) Converted to GPE using Graffixnyc RUU
4) Flashed Skydragon GPE
5) Then I wanted to try Skydragon Sense, so I changed CID to 11111111, flashed stock recovery and did factory reset
6) Flashed TWRP 2.7.1.0 to replace stock recovery
7) Now I am currently using Skydragon Sense
I thought I would be able to restore the backup from step 1 after doing step 5. It would be nice to know I can still go back to the phone in that state if I ever decide to sell.
Thanks for your help!
leongwengheng said:
Hi, mate. I did the back up in TWRP 2.7.0.2 - although now I am on TWRP 2.7.1.0. Not sure if that makes a difference?
Yes I did convert to GPE at the beginning. Here's how I got to where I am today:
1) Flashed TWRP 2.7.0.2
2) Did a nandroid backup of factory state
3) Converted to GPE using Graffixnyc RUU
4) Flashed Skydragon GPE
5) Then I wanted to try Skydragon Sense, so I changed CID to 11111111, flashed stock recovery and did factory reset
6) Flashed TWRP 2.7.1.0 to replace stock recovery
7) Now I am currently using Skydragon Sense
I thought I would be able to restore the backup from step 1 after doing step 5. It would be nice to know I can still go back to the phone in that state if I ever decide to sell.
Thanks for your help!
Click to expand...
Click to collapse
You need to undo the GPE conversion since it has resized your system partition. Follow this guide:
Going back to Sense from [RUU] Google Edition Conversion.Graffixync UPDATE 12th May
In the last part where it says to flash a ROM, just restore your backup, but have a ROM handy just in case.
Sir-Fix-a-Lot said:
You need to undo the GPE conversion since it has resized your system partition. Follow this guide:
Going back to Sense from [RUU] Google Edition Conversion.Graffixync UPDATE 12th May
In the last part where it says to flash a ROM, just restore your backup, but have a ROM handy just in case.
Click to expand...
Click to collapse
Thanks for the quick reply!
I have followed this procedure already (that's how I'm running Skydragon Sense rom now). Before I flashed the Skydragon rom, I tried to restore the first backup I did, but it failed. I have successfully flashed ViperOne and Skydragon Sense though, so I'm sure I have successfully re-converted it away from the GPE partition. I'll try to restore it again now and see what happens.
leongwengheng said:
Thanks for the quick reply!
I have followed this procedure already (that's how I'm running Skydragon Sense rom now). Before I flashed the Skydragon rom, I tried to restore the first backup I did, but it failed. I have successfully flashed ViperOne and Skydragon Sense though, so I'm sure I have successfully re-converted it away from the GPE partition. I'll try to restore it again now and see what happens.
Click to expand...
Click to collapse
You could try loading TWRP 2.7.0.2 and restoring from there, but it shouldn't be an issue with 2.7.1.0
leongwengheng said:
1) Flashed TWRP 2.7.0.2
2) Did a nandroid backup of factory state
Click to expand...
Click to collapse
Shouldn't you boot recovery and then do a nandroid backup before flashing recovery?
If you've flashed recovery and then made a nandroid backup i guess you won't have a backup of your factory settings.
Niorun said:
Shouldn't you boot recovery and then do a nandroid backup before flashing recovery?
If you've flashed recovery and then made a nandroid backup i guess you won't have a backup of your factory settings.
Click to expand...
Click to collapse
Stock recovery won't make a backup, only a custom recovery. He did right, flashed TWRP, and make a backup of the stock ROM it was loaded with. He's having issues restoring it.
That's a damn good point. I've only ever backed things up using custom recoveries. Never thought of using the stock recovery. I guess I can never get back to factory stock then.
I should be able to get back to the factory ROM though (albeit rooted and with flash recovery)?
Sent from my HTC One_M8 using XDA Free mobile app
leongwengheng said:
That's a damn good point. I've only ever backed things up using custom recoveries. Never thought of using the stock recovery. I guess I can never get back to factory stock then.
I should be able to get back to the factory ROM though (albeit rooted and with flash recovery)?
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Read my post above, the stock recovery cannot backup, only a custom recovery can. Your steps were proper. Is there an RUU available for your model, or a .zip to be flashed with fastboot?
Let me rephrase:
Shouldn't you boot custom recovery and then do a nandroid backup before flashing custom recovery?
If you've flashed custom recovery and then made a nandroid backup i guess you won't have a backup of your factory settings.
Sir-Fix-a-Lot said:
Read my post above, the stock recovery cannot backup, only a custom recovery can. Your steps were proper. Is there an RUU available for your model, or a .zip to be flashed with fastboot?
Click to expand...
Click to collapse
As far as I was aware, there are no stock RUU's available for any M8 at the moment?
Niorun said:
Let me rephrase:
Shouldn't you boot custom recovery and then do a nandroid backup before flashing custom recovery?
If you've flashed custom recovery and then made a nandroid backup i guess you won't have a backup of your factory settings.
Click to expand...
Click to collapse
leongwengheng said:
1) Flashed TWRP 2.7.0.2
2) Did a nandroid backup of factory state
Click to expand...
Click to collapse
That's what he did. He wouldn't have been able to make the backup without booting the custom recovery, so append his steps like this:
1) Flashed TWRP 2.7.0.2
1a) Booted recovery
2) Did a nandroid backup of factory state
---------- Post added at 02:50 AM ---------- Previous post was at 02:50 AM ----------
leongwengheng said:
As far as I was aware, there are no stock RUU's available for any M8 at the moment?
Click to expand...
Click to collapse
There is. What is your model? The intl unlocked?
Niorun said:
Let me rephrase:
Shouldn't you boot custom recovery and then do a nandroid backup before flashing custom recovery?
If you've flashed custom recovery and then made a nandroid backup i guess you won't have a backup of your factory settings.
Click to expand...
Click to collapse
Generally you should boot custom recovery and mare a nandroid backup.Philz allows you to backup your stock recovery.But twrp doesnot.Yes if he has flashed custom recovery without taking the bkup of stock recovery he wont have full 100% stock rom.Also if the op provides details of what version on stock rom and cid he is using then we might be able to get a stock recovery for him.
Sir-Fix-a-Lot said:
That's what he did. He wouldn't have been able to make the backup without booting the custom recovery, so append his steps like this:
1) Flashed TWRP 2.7.0.2
1a) Booted recovery
2) Did a nandroid backup of factory state
---------- Post added at 02:50 AM ---------- Previous post was at 02:50 AM ----------
There is. What is your model? The intl unlocked?
Click to expand...
Click to collapse
Yeah, International unlocked (bought in UK).
leongwengheng said:
As far as I was aware, there are no stock RUU's available for any M8 at the moment?
Click to expand...
Click to collapse
Please provide what version of stock rom u r using.Also give the output of the following: fastboot getvar all
We wnat to know if u r s-off and whai tis your cid and mid.
Sir-Fix-a-Lot said:
That's what he did. He wouldn't have been able to make the backup without booting the custom recovery, so append his steps like this:
1) Flashed TWRP 2.7.0.2
1a) Booted recovery
2) Did a nandroid backup of factory state
---------- Post added at 02:50 AM ---------- Previous post was at 02:50 AM ----------
There is. What is your model? The intl unlocked?
Click to expand...
Click to collapse
Booting to and flashing are different things.
I mean:
1: fastboot boot recovery <recovery.img>
2: nandroid backup
3: fastboot flash recovery <recovery.img>
Only that way you are able to perform a nandroid of your factory settings. I believe...
Niorun said:
Booting to and flashing are different things.
I mean:
1: fastboot boot recovery <recovery.img>
2: nandroid backup
3: fastboot flash recovery <recovery.img>
Only that way you are able to perform a nandroid of your factory settings. I believe...
Click to expand...
Click to collapse
Yep u r right.
Jyotirdeb said:
Generally you should boot custom recovery and mare a nandroid backup.Philz allows you to backup your stock recovery.But twrp doesnot.Yes if he has flashed custom recovery without taking the bkup of stock recovery he wont have full 100% stock rom.Also if the op provides details of what version on stock rom and cid he is using then we might be able to get a stock recovery for him.
Click to expand...
Click to collapse
Thanks for your input. I foolishly didn't take a note of the CID before I changed it to GOOGL01 the first time, but I'm definite it began with HTC followed by some numbers.
Before doing a factory reset when switching away from GPE, I flashed the firmware 1.54.401.5.
Jyotirdeb said:
Please provide what version of stock rom u r using.Also give the output of the following: fastboot getvar all
We wnat to know if u r s-off and whai tis your cid and mid.
Click to expand...
Click to collapse
Once this info is provided, he can look here for a ROM
http://forum.xda-developers.com/showthread.php?t=2701376
and this thread may be of some help:
http://forum.xda-developers.com/showthread.php?t=2694600
I'm still looking for the RUU thread
Related
Hi,
I'm currently using ViperX JB rom with Clockwork recovery. I'm reading that TWRP is a better option for flashing OTA's.
Quick question - is there any problems with flashing TWRP over the top of Clockwork? In other words, do I just boot into fastboot and type "fastboot flash recovery nameofrecovery.img", followed by "fastboot erase cache"?
Also, will that affect the rom, ie will it need to be reflashed?
Thanks in advance.
Yeah, just flash the new recovery, it'll be fine.
And no you do not have to reflash the rom......
Keep in mind that you can't restore CWM backups in TWRP. Otherwise it's all good.
Sent from my One X
TToivanen said:
Keep in mind that you can't restore CWM backups in TWRP. Otherwise it's all good.
Click to expand...
Click to collapse
Right, but you can make a TWRP backup, or flash back CWM to restore a CWM backup.
Ah, of course, I forgot about my nandroid backup!
Thankyou all for the replies.
Hi
I have a HTC one X rooted phone with stack 4.1.1
I get a message that there is a new update 3.20.401.1
After download it tells me to reboot. My phone then goes to ClockWorkmode (CWM)
It stoops there. I do not find any zip file to install.
Any tips for this, or should I just ignore this?
Thanks
Jotne said:
Hi
I have a HTC one X rooted phone with stack 4.1.1
I get a message that there is a new update 3.20.401.1
After download it tells me to reboot. My phone then goes to ClockWorkmode (CWM)
It stoops there. I do not find any zip file to install.
Any tips for this, or should I just ignore this?
Thanks
Click to expand...
Click to collapse
To install official updates u need to have stock recovery which comes with phone, but u have CWM
Jotne said:
Hi
I have a HTC one X rooted phone with stack 4.1.1
I get a message that there is a new update 3.20.401.1
After download it tells me to reboot. My phone then goes to ClockWorkmode (CWM)
It stoops there. I do not find any zip file to install.
Any tips for this, or should I just ignore this?
Thanks
Click to expand...
Click to collapse
You just need to flash stock recovery through fastboot again mate then on booting up you should be able to install the update. Or you could install a custom rom with that base without having to flash recovery :good:
Thanks for quick reply.
If I go for a custom room, what is the best out there?
Do I loose anything by not upgrading the stock room?
Jotne said:
Thanks for quick reply.
If I go for a custom room, what is the best out there?
Do I loose anything by not upgrading the stock room?
Click to expand...
Click to collapse
they are all pretty damn good roms mate! too hard to choose really, just best to flash em, and see remember to make a nandroid backup also
u shouldn't loose anything apart from bloatware
If you want a custom based on stock, i suggest Android revolution, Viper Rom, or SD ROM.
Sent from my HTC One X using xda premium
CM10.1 ROM
Click to expand...
Click to collapse
UFFFFF
I did try out Cyanogen lastest image, that do work fine.
But I have to look long for how to find out that I needed to extract boot.img from the cyanogen zip file and install this with flashboot.
But now I like to go back to my original rom. I did take a nandroid backup, and also have an older nandroidbackup.
Its not possible to make the phone go back. When I start restor, all looks ok MD5 etc, but then gets this message
Error while restoring /system!
Do I have to do more flashboot stuf to go back?
I am still able reinstall Cyanogen from zip file. But my Cyanogen backup also fail.
Why
Edit. The Cyanogen Image is 4.2.2 and Orginal image is 4.1.1. Could that be any problem?
Jotne said:
UFFFFF
I did try out Cyanogen lastest image, that do work fine.
But I have to look long for how to find out that I needed to extract boot.img from the cyanogen zip file and install this with flashboot.
But now I like to go back to my original rom. I did take a nandroid backup, and also have an older nandroidbackup.
Its not possible to make the phone go back. When I start restor, all looks ok MD5 etc, but then gets this message
Error while restoring /system!
Do I have to do more flashboot stuf to go back?
I am still able reinstall Cyanogen from zip file. But my Cyanogen backup also fail.
Why
Edit. The Cyanogen Image is 4.2.2 and Orginal image is 4.1.1. Could that be any problem?
Click to expand...
Click to collapse
Are you sure you've made the backup with the same recovery as you are attempting to restore it with?
The Android version shouldn't really matter, but there may be exceptions for some things.
Sent from my HTC One X using xda premium
Jotne said:
UFFFFF
I did try out Cyanogen lastest image, that do work fine.
But I have to look long for how to find out that I needed to extract boot.img from the cyanogen zip file and install this with flashboot.
But now I like to go back to my original rom. I did take a nandroid backup, and also have an older nandroidbackup.
Its not possible to make the phone go back. When I start restor, all looks ok MD5 etc, but then gets this message
Error while restoring /system!
Do I have to do more flashboot stuf to go back?
I am still able reinstall Cyanogen from zip file. But my Cyanogen backup also fail.
Why
Edit. The Cyanogen Image is 4.2.2 and Orginal image is 4.1.1. Could that be any problem?
Click to expand...
Click to collapse
If you are using CWM recovery u should be able to go into the backup file (under clockwork mod/backup on sd) and take the boot.img u need to flash via fastboot there. Put it in your fastboot file and then flash using "fastboot flash boot boot.img"
So I should take the boot.img from the backup, run fastimage and restore it?
Then try to restore the backup using clockworkmod?
I am not user if the backup was made with
recovery-clockwork-touch-5.8.2.7-endeavoru.img or
recovery-clockwork-touch-5.8.3.1-endeavoru.img
Is it important to restore with correct version? If so how to see what version that was used?
I am not able to go back to my old image
Not sure why, but the Cyanogenmod does not give me any Mobil data (3G etc)??
I tried to restore the boot.img from correct backup using flashboot flash boot boot.img and then try to restore.
But still I get Error while restoring /system!
Some note:
I made a backup of my working Cyanogenmod, this I am able to restore without getting the restoring error.
No I also have tried recovery-clockwork-touch-5.8.4.0-endeavoru.img
But there are some different thing going on.
When I first tested to restore my original image, I get menu like this when trying to restore:
Code:
Yes-Restore
No
Go-Back
Now I do get:
Code:
No
No
No
No
No
Yes-Restore
No
No
No
*** Go back
Have I used another clockworkmode to make the backup?
If you want to be sure you use the same recovery as where the nandroid is made with ? Flash the recovery.img from the nandroid folder.
Then flash the boot.img from the nandroid folder, go into recovery :
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then restore the nandroid.
Thanks
You saved my day.
It seems that the backup was done with CWM based v6.0.2.7
Not sure where I have got this version.
Latest version listed here: http://www.clockworkmod.com/rommanager is 5.8.4.0 and not 6.0.2.7 that I have used
Here http://forum.xda-developers.com/showthread.php?t=1941630 is 6.0.3.2 listed
What is the latest version of CWM for HTC ONE x and where to get it?
And last, what is the best to use
Yeah well after all the replies i thought i chip in give my 2 cents
This is one of the latest i use now.
http://db.tt/SPXdFfPw
Everything is working fine and I start to understand how its connected together.
But there are one thing that still puzzle me, the boot.img
When and why do I need to change that when I go to and from CM 10.1.2 (4.2.2) and Original image 4.1.1
What trigger the need of the change?
Should not this be restored correctly when I restore a backup. (In Clockwork mode)?
Does this work automatically whit Philz recovery 5.6.1.img?
I do like to change image in my phone without need a PC to run fastboot !!
When you change rom you need to flash the corresponding boot.img from that particular rom or nandroid backup.
We can't flash boot.img files via recovery because we have s-on devices so fastboot is a must.
Wilts panttsic
Ok, thats some sad, but thanks a lot for you help here
No problem.
CASE CLOSED !
Mr Hofs said:
No problem.
CASE CLOSED !
Click to expand...
Click to collapse
Another one for the Hof!!! :good:
exocetdj said:
Another one for the Hof!!! :good:
Click to expand...
Click to collapse
1 for Hofs = 1 for everybody mate.....we all are helping here !
HI,
I have a europen (international) htc one x 32gb, currently running miu 3.5.7
i want to get back to stock and I was looking at the threads about how to do this using a ruu but I'm not sure how to continue:
my cid is E11
my versions is 3.20.401.1
i first wanted to use a nandroid backup but the file here is not on dropbox anymore:
http://forum.xda-developers.com/show....php?t=1975140
so then i thought to try it with a ruu and this should be the right ruu I think:
OTA_ENDEAVOR_U_JB_45_S_HTC_Europe_3.20.401.1-3.14.401.31_R_release_314818virsindn3qwws1r2.zip
but it is only 36 MB and there is no executable file in it ...
is there another ruu i can use or another method to get back to stock?
tnx!
artenbe said:
HI,
I have a europen (international) htc one x 32gb, currently running miu 3.5.7
i want to get back to stock and I was looking at the threads about how to do this using a ruu but I'm not sure how to continue:
my cid is E11
my versions is 3.20.401.1
i first wanted to use a nandroid backup but the file here is not on dropbox anymore:
http://forum.xda-developers.com/show....php?t=1975140
so then i thought to try it with a ruu and this should be the right ruu I think:
OTA_ENDEAVOR_U_JB_45_S_HTC_Europe_3.20.401.1-3.14.401.31_R_release_314818virsindn3qwws1r2.zip
but it is only 36 MB and there is no executable file in it ...
is there another ruu i can use or another method to get back to stock?
tnx!
Click to expand...
Click to collapse
That ruu is only an ota which stands for over the air update, I can try and find the right one for you
Edit: I don't think there is an ruu for your version so I think the only way to get back to stock is a nandroid which is not on dropvox anymore as you said.. Mr hofs uploaded it I believe if you can get in contact with him he might still have the nandroid for you
Sent from my HTC One X using xda app-developers app
Thought so, but I can;t find a nandroid nackup either,
the mr hoff ones are no longer active apparently ...
http://db.tt/hZfIDBOC
Mr Hofs said:
http://db.tt/hZfIDBOC
Click to expand...
Click to collapse
thanks you so much kind sir
No problem ! And restore this stock recovery too if you wish to update via official HTC ota
http://db.tt/pO3jumMa
Mr Hofs said:
No problem ! And restore this stock recovery too if you wish to update via official HTC ota
http://db.tt/pO3jumMa
Click to expand...
Click to collapse
I just wanted to ask if it would be ok to flash the 3.14 recovery
one more question:
I used getRIL and it says this:
RIL: unknown
baseband: 5.1204.162.29
is this ok/normal or is it rom specific (miui)?
and by flashing this backup etc, does this also get the original kernel etc?
my kernel now is 3.1.10n3okernel_v33-gf404256-dirty
so in other words: is everything back to the original and can i be sure i have the right radio etc?
Restore the nandroid and also flash back the boot.img from the nandroid backup. Then you have stock kernel + modules.
Mr Hofs said:
Restore the nandroid and also flash back the boot.img from the nandroid backup. Then you have stock kernel + modules.
Click to expand...
Click to collapse
hi,
i tried restoring your backup but it saus: error while restoring /system
i downloaded your file, put it in the backup folder, flashed boot.img and erased cache, then restored back-up
edit: also did a full wipe, same problem
Flash also the recovery.img to be sure you are using the same one as it is made with
And also enter mounts and storage and format all except sdcard
Mr Hofs said:
Flash also the recovery.img to be sure you are using the same one as it is made with
And also enter mounts and storage and format all except sdcard
Click to expand...
Click to collapse
i flashed the recovery but I guess I had to do it after the backup was restored?
now i have a red triangle screen when i want to boot into recovery..
that was stupid i know... so what do i do now?
No no no.......
Flash the recovery.img from the nandroid backup folder, flash the boot.img from the backup folder. Make a full wipe
Factory reset
Wipe cache partition
Advanced-wipe dalvik cache
Mounts & storage-format cache,data,system
Then restore the nandroid backup and THEN restore the stock recovery i gave you in that separate link !
Mr Hofs said:
No no no.......
Flash the recovery.img from the nandroid backup folder, flash the boot.img from the backup folder. Make a full wipe
Factory reset
Wipe cache partition
Advanced-wipe dalvik cache
Mounts & storage-format cache,data,system
Then restore the nandroid backup and THEN restore the stock recovery i gave you in that separate link !
Click to expand...
Click to collapse
Thanks a lot! it worked
I know
Well good its solved ! :thumbup:
CASE CLOSED !
Mr Hofs said:
I know
Well good its solved ! :thumbup:
CASE CLOSED !
Click to expand...
Click to collapse
Sorry but still have a problemo
it says my android versions is 4.1.1 but there is a 4.2 for this device no?
When I ask for update it says there are no updates available...
I thought it would be completely back to stock and able to receive updates?
Yes but there is indeed no further update at this moment
Mr Hofs said:
Yes but there is indeed no further update at this moment
Click to expand...
Click to collapse
Can I jump in here as Mr Hofs seems to have a lot of knowledge.
I did a restore of my One-X to stock rom according to this tutorial.
http://design-extreme.net/restore-htc-one-x-to-stock-rom/
This all went well and without problems. The RUU I flashed is this one.
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed
When I now startup the phone it all works perfect. Then the phone says there is an OTA (to 3.20 I believe)
I download and install the OTA and the phone restarts, but after restarts the phone's touchscreen does not work anymore.
I solved this for now by installing the 3.14RUU again, then it works again. But of course I would like to be able to install the OTA's
To me it sounds like a driver problem in the new version that prevents the touchscreen from working. You or anyone else have idea how to solve this?
Xanion said:
Can I jump in here as Mr Hofs seems to have a lot of knowledge.
I did a restore of my One-X to stock rom according to this tutorial.
http://design-extreme.net/restore-htc-one-x-to-stock-rom/
This all went well and without problems. The RUU I flashed is this one.
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed
When I now startup the phone it all works perfect. Then the phone says there is an OTA (to 3.20 I believe)
I download and install the OTA and the phone restarts, but after restarts the phone's touchscreen does not work anymore.
I solved this for now by installing the 3.14RUU again, then it works again. But of course I would like to be able to install the OTA's
To me it sounds like a driver problem in the new version that prevents the touchscreen from working. You or anyone else have idea how to solve this?
Click to expand...
Click to collapse
No-One?:crying:
HTC One X Nandroid Restore.
Mr Hofs said:
I know
Well good its solved ! :thumbup:
CASE CLOSED !
Click to expand...
Click to collapse
Mr Hofs. I've followed your instructions to the letter, but when I do the recovery of the Nandroid using CWM v5.8.4.0 I get an error
MD5 sums.....
Erasing boot before restore....
Restoring boot image....
Restoring system....
Error while restoring /system!
Please help
fazq01 said:
Mr Hofs. I've followed your instructions to the letter, but when I do the recovery of the Nandroid using CWM v5.8.4.0 I get an error
MD5 sums.....
Erasing boot before restore....
Restoring boot image....
Restoring system....
Error while restoring /system!
Please help
Click to expand...
Click to collapse
Flash the recovery.img from the nandroid backup first. Then make a full wipe and restore the nandroid. That will solve the restore error.
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!
Hello everybody, it is time to update to Nougat and I'm ready to do it.
According to this thread https://forum.xda-developers.com/showpost.php?p=59745198&postcount=3
I need a system_image and stock recovery backup for being able to do an OTA.
I did it and I must restore the system_image and the stock recovery as written in point 8.
But according to this other thread https://forum.xda-developers.com/showpost.php?p=64299835&postcount=4
in Hidden Content point 13, I must backup the system_image, the stock recovery and the boot image.
I have only backupped system_image and recovery and I can download boot.emmc.win from the second thead, but I wish to ask:
Is it really necessary to restore boot.emmc.win? Now I'm on ViperOneM9 4.3.0
Why @Captain_Throwback didn't mention it in his official TWRP thread?
I thank you in advance anyone may help me to get the OTA in the right way
Balteck said:
Hello everybody, it is time to update to Nougat and I'm ready to do it.
According to this thread https://forum.xda-developers.com/showpost.php?p=59745198&postcount=3
I need a system_image and stock recovery backup for being able to do an OTA.
I did it and I must restore the system_image and the stock recovery as written in point 8.
But according to this other thread https://forum.xda-developers.com/showpost.php?p=64299835&postcount=4
in Hidden Content point 13, I must backup the system_image, the stock recovery and the boot image.
I have only backupped system_image and recovery and I can download boot.emmc.win from the second thead, but I wish to ask:
Is it really necessary to restore boot.emmc.win? Now I'm on ViperOneM9 4.3.0
Why @Captain_Throwback didn't mention it in his official TWRP thread?
I thank you in advance anyone may help me to get the OTA in the right way
Click to expand...
Click to collapse
If I didn't mention it, then you don't have to do it .
@Captain_Throwback can you maybe explain that a little further? I made the experience that people are facing problems if they return from a custom rom to a stock rom and don't wipe their phone. That's why I added the wiping step to my instructions. After that several users reported that their phones didn't boot after they restored the first version of my backups (which lacked the boot.img). Therefore, I thought the boot.img is needed as well and all backups got replaced over a year ago with the current version which includes the boot.img.
However, all this is based on the reports of users who had problems with returning back to stock. I've never faced these issues myself. So if there is anything wrong with my instructions I'll correct them, of course.
Sent from my HTC One M9 using XDA Labs
I thought it's impossible to backup the stock recovery seeing as twrp is needed to be flashed to make the backup..
Beamed in by telepathy.
shivadow said:
I thought it's impossible to backup the stock recovery seeing as twrp is needed to be flashed to make the backup..
Beamed in by telepathy.
Click to expand...
Click to collapse
Since firmware 3.x you can boot TWRP via fastboot from the bootloader without overwriting the currently installed stock recovery.
Flippy498 said:
@Captain_Throwback can you maybe explain that a little further? I made the experience that people are facing problems if they return from a custom rom to a stock rom and don't wipe their phone. That's why I added the wiping step to my instructions. After that several users reported that their phones didn't boot after they restored the first version of my backups (which lacked the boot.img). Therefore, I thought the boot.img is needed as well and all backups got replaced over a year ago with the current version which includes the boot.img.
However, all this is based on the reports of users who had problems with returning back to stock. I've never faced these issues myself. So if there is anything wrong with my instructions I'll correct them, of course.
Click to expand...
Click to collapse
Not sure what to explain - OTA does no verification on boot.img. So it doesn't have to be stock for an OTA to install. It's that simple.
Captain_Throwback said:
Not sure what to explain - OTA does no verification on boot.img. So it doesn't have to be stock for an OTA to install. It's that simple.
Click to expand...
Click to collapse
OK. I guess there was a little misunderstanding.
The current version of my instructions is meant to be used if you want to return to a clean stock system. (In other words the ability to install OTAs, again, is only a side effect.) I never was talking about the boot.img being necessary for being able to install the OTA. I thought you were saying that the boot.img wouldn't be needed inside a backup if you do a full wipe before the restoration and that the phone would still boot.
Sent from my HTC One M9 using XDA Labs
I'm little confused now.
For installing an OTA update I MUST have an untouched system partition and stock recovery.
But the steps I need to do are:
1) backup apps and settings
2) restore untouched system partiton and stock recovery partition from TWRP, doing a factory reset (wipe data, dalvik and cache)
3) boot the original stock OS, configure wifi and go to Software Update
4) download OTA(s)
5) apply update and reboot phone
6) with ADB start TWRP recovery and backup the new stock recovery and the new stock system_image
7) flash TWRP and new custom ROM
8) restore apps and settings from point 1)
So, is it possible that at step 3 my HTC cannot boot because I didn't restore the boot partition (I'm coming from ViperOneM9 4.3.0)?
Or is there a simpler method, without backuping, wiping, restoring?
Flippy498 said:
Since firmware 3.x you can boot TWRP via fastboot from the bootloader without overwriting the currently installed stock firmware.
Click to expand...
Click to collapse
Looks liks i used an out of date tutorial then.. What a bugger..
Beamed in by telepathy.
Anyone can confirm me that my previous steps are right?
So I may uodate to Android n without doubt
Thank you very much