I am having a little difficulty understanding some things about s-on and I hope someone will take the time to explain some of this for me and others.
So, I understand the basic process of S-on flashing..Rom, boot img, upgrading separately through an ruu file.
My question is when I do a nandroid backup, it seems to back up the boot image (not sure if its an image but the boot sector). When I restore a nandroid, it can restore the boot.
If I can do this through a nandroid, why do I have to load the boot files separately on all of the custom ROMs...(ie, PH98img.zip)?
Piaband said:
I am having a little difficulty understanding some things about s-on and I hope someone will take the time to explain some of this for me and others.
So, I understand the basic process of S-on flashing..Rom, boot img, upgrading separately through an ruu file.
My question is when I do a nandroid backup, it seems to back up the boot image (not sure if its an image but the boot sector). When I restore a nandroid, it can restore the boot.
If I can do this through a nandroid, why do I have to load the boot files separately on all of the custom ROMs...(ie, PH98img.zip)?
Click to expand...
Click to collapse
Nandroid can't restore the boot image when your phone is s-on, you still need to flash it separately. Now if you're going from one rom to another that uses the same kernel, you can get away without flashing it.
I suggest you read this for more info on s-on/s-off - http://forum.xda-developers.com/showthread.php?t=1641670
mjones73 said:
Nandroid can't restore the boot image when your phone is s-on, you still need to flash it separately. Now if you're going from one rom to another that uses the same kernel, you can get away without flashing it.
I suggest you read this for more info on s-on/s-off - http://forum.xda-developers.com/showthread.php?t=1641670
Click to expand...
Click to collapse
This was exactly my concern. If I start moving from one leak to another, I wasn't sure if I could just Nandroid back. I think its time to S-off
Piaband said:
This was exactly my concern. If I start moving from one leak to another, I wasn't sure if I could just Nandroid back. I think its time to S-off
Click to expand...
Click to collapse
It does make life easier if you're a frequent rom flasher.
Piaband said:
This was exactly my concern. If I start moving from one leak to another, I wasn't sure if I could just Nandroid back. I think its time to S-off
Click to expand...
Click to collapse
You actually can nandroid back if you use Con's nandroid recovery helper http://forum.xda-developers.com/showthread.php?t=1547496&highlight=nandroid+recovery+helper
If you flash this first.. it will boot you to bootloader to flash a ph98img.. flash that and hit ok to reboot. It will boot you back to recovery and you can now restore your nandroid with boot kernel and all I used this exclusively when I was S-on and it was the closest to being S-off as you could be . I would still S-off when you can , but you could use this method to switch between backups and other roms until then.
mjh68 said:
You actually can nandroid back if you use Con's nandroid recovery helper http://forum.xda-developers.com/showthread.php?t=1547496&highlight=nandroid+recovery+helper
If you flash this first.. it will boot you to bootloader to flash a ph98img.. flash that and hit ok to reboot. It will boot you back to recovery and you can now restore your nandroid with boot kernel and all I used this exclusively when I was S-on and it was the closest to being S-off as you could be . I would still S-off when you can , but you could use this method to switch between backups and other roms until then.
Click to expand...
Click to collapse
Does this create a new boot kernel when you create a backup? And then does it place in on the sd card when you restore?
If so, that would be incredible.
No it literally takes your recovery and dumps it in a ph98img.zip file and flashes the recovery to the boot partition. Then when you restore a nandroid it will restore the boot img. I guess you could theoretically flash roms made for s-off this way too.
Sent from my ADR6425LVW using XDA
Related
Hi, everyone. I am sure someone is going to shaking their heads at my idiocy after reading this post but I hope someone can save me. So I went to all that trouble to update my phone to ICS from Gingerbread and retain S-off and rooted. After playing with it a little, I decided I like my previous state better. Before I updated my phone, I backed up my phone using the clockworkmod recovery that was installed using revolutionary's tool. That was also the recovery that I flashed after I updated to ICS. So I figure all I have to do was restore the backup. I boot into recovery and all I did was select "backup\recovery" and then the date that I did the backup. The restore finished and I rebooted my system. Everything should be fine now, right? Wrong! As the phone bootup, it would read HTC then Sprint before rebooting again and again. I never reach the lockscreen. Right now I can still reach recovery through the bootloader but that is it.
So how can I recover? Was I supposed to wipe something before restoring? If so, which options am i supposed to use (wipe all data?) because specific details will prevent me from making another bonehead move. If not, what do I do?
Problem is, I got impatient to downgrade from ICS and never bothered to backup after the update to ICS. Just a reminder to all that "backup, backup and backup). So I am stucked right now and need help. HELPPPPPPP......
Tommy
I can see from my bootloader that it is still HBoot 1.58 instead of HBoot 1.4 before the ICS update. Would flashing the boot.img from the clockworkmod backup work?
xionchen4628 said:
Hi, everyone. I am sure someone is going to shaking their heads at my idiocy after reading this post but I hope someone can save me. So I went to all that trouble to update my phone to ICS from Gingerbread and retain S-off and rooted. After playing with it a little, I decided I like my previous state better. Before I updated my phone, I backed up my phone using the clockworkmod recovery that was installed using revolutionary's tool. That was also the recovery that I flashed after I updated to ICS. So I figure all I have to do was restore the backup. I boot into recovery and all I did was select "backup\recovery" and then the date that I did the backup. The restore finished and I rebooted my system. Everything should be fine now, right? Wrong! As the phone bootup, it would read HTC then Sprint before rebooting again and again. I never reach the lockscreen. Right now I can still reach recovery through the bootloader but that is it.
So how can I recover? Was I supposed to wipe something before restoring? If so, which options am i supposed to use (wipe all data?) because specific details will prevent me from making another bonehead move. If not, what do I do?
Problem is, I got impatient to downgrade from ICS and never bothered to backup after the update to ICS. Just a reminder to all that "backup, backup and backup). So I am stucked right now and need help. HELPPPPPPP......
Tommy
Click to expand...
Click to collapse
xionchen4628 said:
I can see from my bootloader that it is still HBoot 1.58 instead of HBoot 1.4 before the ICS update. Would flashing the boot.img from the clockworkmod backup work?
Click to expand...
Click to collapse
You need to downgrade your bootloader to something lower than 1.58 if you want to run ROM's based on GB or AOSP. You can go back to 1.4 if you want, or the Jbear GB (1.50.5050) version. You should leave the rest of your firmware at the ICS level.
The bootloaders can be found in this post. Download the one you want, put it in the root of your SD card, rename it to PG86IMG.zip and flash it from the current bootloader. You should then be able to boot your CWM backup, and don't forget to delete the PG86IMG.zip file from the root of your SD card after you flash it.
ramjet73
Thanks, ramjet. My phone is back to the state that it was in before my ICS update. Sorry for all the work that you put in to help me upgrade in the first place. Since I restore from my GB backup, all I did was flash the bootloader and everything went to normal. If somewhere done the line, I decided to update to ICS again, I know all the steps that need to be done (thanks to you and all the users who provided the various files). Thanks again. I love this community!
ramjet73 said:
You need to downgrade your bootloader to something lower than 1.58 if you want to run ROM's based on GB or AOSP. You can go back to 1.4 if you want, or the Jbear GB (1.50.5050) version. You should leave the rest of your firmware at the ICS level.
The bootloaders can be found in this post. Download the one you want, put it in the root of your SD card, rename it to PG86IMG.zip and flash it from the current bootloader. You should then be able to boot your CWM backup, and don't forget to delete the PG86IMG.zip file from the root of your SD card after you flash it.
ramjet73
Click to expand...
Click to collapse
xionchen4628 said:
Thanks, ramjet. My phone is back to the state that it was in before my ICS update. Sorry for all the work that you put in to help me upgrade in the first place. Since I restore from my GB backup, all I did was flash the bootloader and everything went to normal. If somewhere done the line, I decided to update to ICS again, I know all the steps that need to be done (thanks to you and all the users who provided the various files). Thanks again. I love this community!
Click to expand...
Click to collapse
Well the rest of firmware (other than the hboot) is now updated to the Sprint ICS 2.89.651.2 level, so you should be able to run the ICS ROM's that don't require the 1.58 bootloader and there are quite a few of those. So it wasn't a waste of time and effort.
ramjet73
Morning all, yesterday, i was having problems with my phone, so i relocked it, and put the Stock O2 Uk Ruu file back on it, it then prompted me for a software update, which I accepted to do.
Anyway, all was going fine, decided to re-flash my phone, and try the modded rom again, unfortunatley the Rom seemed corrupt for some reason, i did make a nandroid back up of the New stock rom, just be on the safe side.
So i decided to re-lock the phone again and run the Stock RUU, but in the updating process, it gave me a error saying this is the wrong Ruu, i presume it was something to do with my Hboot also being updated ?
Is there anyway at all , i can downgrade the Hboot to the previous one, so i can run the Stock Ruu?
All is not lost as i am using the nandroid backup at the moment.
Thanks
Schumi 01 said:
Is there anyway at all , i can downgrade the Hboot to the previous one, so i can run the Stock Ruu?
Click to expand...
Click to collapse
you can't downgrade hboot
flash recovery, flash kernel, install rom. ready!
skdubg said:
you can't downgrade hboot
flash recovery, flash kernel, install rom. ready!
Click to expand...
Click to collapse
Damn that's a shame, maybe i will stick with my recovery image for now then, and hopefully there will be a new Ruu available in the future.
Thanks
Schumi 01 said:
Damn that's a shame, maybe i will stick with my recovery image for now then, and hopefully there will be a new Ruu available in the future.
Thanks
Click to expand...
Click to collapse
It's best to keep updated with the latest hboot anyway. There were users having issues with some custom roms, because they did not have the latest hboot.
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
It's best to keep updated with the latest hboot anyway. There were users having issues with some custom roms, because they did not have the latest hboot.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Cheers Andro, going to do a fresh install tonight of the custom Rom, hopefully, i had a bad install, phone is working fine on the Nandroid back up, so no big problem really.
Schumi 01 said:
Cheers Andro, going to do a fresh install tonight of the custom Rom, hopefully, i had a bad install, phone is working fine on the Nandroid back up, so no big problem really.
Click to expand...
Click to collapse
Hopefully it was just a bad download. Do a "fastboot erase cache" after you flash the kernel, and do a full wipe in recovery (you can always flash the data.img from you nandroid if you really need too. Although if the rom is of a diffrent base to your nandroid it may cause issues) Hopefully that will stop your problems
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
Hopefully it was just a bad download. Do a "fastboot erase cache" after you flash the kernel, and do a full wipe in recovery (you can always flash the data.img from you nandroid if you really need too. Although if the rom is of a diffrent base to your nandroid it may cause issues) Hopefully that will stop your problems
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Cheers Andro,
It seems to be working fine now, must have been a bad install.
Just one quick question say i did want to go back to Stock through a nandroid backup,
If i get the boot img, and the recovery img, from the stock nandroid,
is it a case of
flashing the stock img,
restore the nandroid backup
then flash the recovery
relock device and reboot ?
Thanks
Edit ignore the above, just read that the recovery image from the nandroid is not stock.
Schumi 01 said:
Cheers Andro,
It seems to be working fine now, must have been a bad install.
Just one quick question say i did want to go back to Stock through a nandroid backup,
If i get the boot img, and the recovery img, from the stock nandroid,
is it a case of
flashing the stock img,
restore the nandroid backup
then flash the recovery
relock device and reboot ?
Thanks
Edit ignore the above, just read that the recovery image from the nandroid is not stock.
Click to expand...
Click to collapse
Thats the general procedure. Don't worry about stock recovery. If you look in development. There are a few posts where people have posted stock recoveries.
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
Thats the general procedure. Don't worry about stock recovery. If you look in development. There are a few posts where people have posted stock recoveries.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Thanks again Andro, just one more thing if you dont mind, are stock recovery's different for different Hboots, and are all stock recoveries the same for any international roms.
Thanks
Schumi 01 said:
Thanks again Andro, just one more thing if you dont mind, are stock recovery's different for different Hboots, and are all stock recoveries the same for any international roms.
Thanks
Click to expand...
Click to collapse
No. As far as i know (and have tried) stock recoverys are the same no matter what hboot you have. Obviously at&t have a diffrent kernel. So we cnt use there recovery.
Sent from my HTC One X+ using Tapatalk 2
If I am S-On, is there a way to set it up so that i don't have to manually flash the boot.img every time? Btw, I am using TWRP
TRWP includes HTC Dumlock which makes it easier, but you'll always have to do some level of extra work when you're s-on. That's just the facts of life with HTC.
gleggie said:
If I am S-On, is there a way to set it up so that i don't have to manually flash the boot.img every time? Btw, I am using TWRP
Click to expand...
Click to collapse
S-off your phone, it's the only way to allow boot.img to be installed automatically along with a rom/kernel installer/etc..
Check out the second section of the TWRP OP: http://forum.xda-developers.com/showthread.php?t=1902381
It basically replaces your bootloader with a copy of recovery that is allowed to flash boot.img files directly, after which you have to replace the default boot again before you can boot. It lets you flash a kernel completely PC free, but it doesn't necessarily make it easier or simpler. There are still extra steps involved if you are s-on.
mjones73 said:
S-off your phone, it's the only way to allow boot.img to be installed automatically along with a rom/kernel installer/etc..
Click to expand...
Click to collapse
If you don't flash often I don't recommend going s-off. It makes it easier to brick the phone.
feralicious said:
If you don't flash often I don't recommend going s-off. It makes it easier to brick the phone.
Click to expand...
Click to collapse
I was just pointing out the only way to avoid manually flashing boot.img is to s-off.
Personally I've been s-off since the day the process was released and I've flashed numerous roms without issue.
I did the wire trick and now I have a different hboot. And now my phone will not boot. It keeps looping through the HTC screen. How can I put the 2.25.0000 hboot back on? It says 2.25.2525 now. And =Juopunuutbear= at the top. Help.
2.25.2525 is a hex edited version of 2.25.0000 that lets you use extended fastboot commands. There's no need to get rid of it, and changing it won't help you boot. It sounds like the backups weren't restored properly at the end of the process. Were you on the stock ROM? Weird issues like that happen a lot when you're on a non-stock ROM. Reflash your recovery through fastboot and restore your nandroid. (You did backup before you s-off'ed, right?) If you don't have a backup, reflash your ROM.
shrike1978 said:
2.25.2525 is a hex edited version of 2.25.0000 that lets you use extended fastboot commands. There's no need to get rid of it, and changing it won't help you boot. It sounds like the backups weren't restored properly at the end of the process. Were you on the stock ROM? Weird issues like that happen a lot when you're on a non-stock ROM. Reflash your recovery through fastboot and restore your nandroid. (You did backup before you s-off'ed, right?) If you don't have a backup, reflash your ROM.
Click to expand...
Click to collapse
I was on ViperRez. I tried restoring my nandroid. It didn't work. Tried updating using the Android Police RUU 4.03.605.2. And now it just keeps restarting into hboot.
joeymagnus1 said:
I was on ViperRez. I tried restoring my nandroid. It didn't work. Tried updating using the Android Police RUU 4.03.605.2. And now it just keeps restarting into hboot.
Click to expand...
Click to collapse
you will need to run the ruu twice. the first time it only updates 4 things. second will update the whole phone.
after that you will need to flash a recovery of your choice
then restore viper rom or start fresh
synisterwolf said:
you will need to run the ruu twice. the first time it only updates 4 things. second will update the whole phone.
after that you will need to flash a recovery of your choice
then restore viper rom or start fresh
Click to expand...
Click to collapse
Took three times to flash. But it started. fwooo! I'll redo the recovery later. Thanks for your help.Off to work.
joeymagnus1 said:
Took three times to flash. But it started. fwooo! I'll redo the recovery later. Thanks for your help.Off to work.
Click to expand...
Click to collapse
glad it worked.
hi i need to get some clarification. i want to unlock and s-of with sunshine ut to install a custom recovery before i need to do a nandroid back up of my stock rom and recovery how could i do that if i dont know how to use adb i havent messed with my htc ever i used a g2 so i know rootinf i just need help with this
You can't make a nandroid of your stock recovery without adb; at least any method that I know of. adb is not difficult to learn, and its quite critical to know, both for performing a variety of functions, and an invaluable tool for recovering from problems. I highly recommend having adb setup, and knowing the basic functions (and that is really all that is needed).
That being said, making a nandroid of your stock ROM and recovery isn't really necessary, as the AT&T version of the M8 has RUUs that will easily return your phone to (nearly) stock condition if needed.
Thanks for that I also wanted to know if I flash that ruu to go back to stock how can I get the stock recovery or is it included
Jacobz1996 said:
Thanks for that I also wanted to know if I flash that ruu to go back to stock how can I get the stock recovery or is it included
Click to expand...
Click to collapse
Stock recovery is included in the RUU, as implied in my previous post. RUU is a complete image, includes all partitions (recovery, hboot, radio, ROM, etc.).
So from my twrp I just flash the ruu and that's it ?
Jacobz1996 said:
So from my twrp I just flash the ruu and that's it ?
Click to expand...
Click to collapse
You don't flash an RUU from recovery. Its a .exe that you run with your computer connected to a PC.
Or there is a bootable version that was created by an XDA user, that doesn't require a PC (posted in General forum section).
Either way, once its running the RUU will walk you through step-by-step, its very easy to use. Just backup any personal data before you RUU, as the phone will be wiped.