• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Various ROM problems

kool kat2

kool kat2

Android Expert
One is that one of my backups doesn't get service. I don't get the no SIM message, just no data or signal at all. I teflashed the rom from scratch and that fixed it but now im terrified of backups :p
It was business sense, the latest release.

Another is every time I try to flash rezRom i get sent into power cycles. As soon as I get to the lick screen it reboots. I followed the instructions exactly (i know, you're thinking "yea right") wiped everything and nothing. I just gave up on it for the time being but does anyone have any ideas to what it could be? (assuming im following directions right)
 
You can't just restore any ol' backup and expect it to work with whatever ROM/kernel/boot partition you have. That's why all ROM install instructions say wipe the phone before installing. The same reasoning applies to restoring backups... unless you restore the entire /system, /data and /boot partitions, there's no guarantee the software in the partitions will be compatible with each other. Without more details about what you did, we won't be able to provide much more help.
 
thornev said:
You can't just restore any ol' backup and expect it to work with whatever ROM/kernel/boot partition you have. That's why all ROM install instructions say wipe the phone before installing. The same reasoning applies to restoring backups... unless you restore the entire /system, /data and /boot partitions, there's no guarantee the software in the partitions will be compatible with each other. Without more details about what you did, we won't be able to provide much more help.
Click to expand...

Makes sense. I was just surprised because i haven't had a problem restoring backups before on other phones and devices so i thought it was a bit weird that this backup was messing up for me. I'm new to amon ra recovery as well so this is a learning process for me. Thanks for the response, ill look more into what i did and see if I can figure out what went wrong.

Edit: I was under the impression that the backups created contained everything to just work once flashed. Assuming I wiped everything, shouldn't the backup have worked? Does the .img file have to be flashed for the backup?
 
First of all, you need to tell us what you used to do the backup and what you backed up. Nandroid backups are the best because they backup the 3 partitions I mentioned and, theoretically, should restore the state of the phone to what it was when you performed the backup. When you restore, you want to restore everything, not individual .img files.

In order to perform a Nandroid backup, you need a custom recovery from which to do it. AmonRa and Clockworkmod are the 2 most popular. I use AmonRa which has a Nandroid backup menu option. When you select the Nandroid backup with AmonRa, you are prompted for which partitions to backup. system, data and boot should always be backed up. cache is optional as it will be regenerated during normal phone use and, as far as I know, doesn't contain any system or application settings.

That's the short of it. If you did all that and your restore failed, that's unusual.
 
thornev said:
First of all, you need to tell us what you used to do the backup and what you backed up. Nandroid backups are the best because they backup the 3 partitions I mentioned and, theoretically, should restore the state of the phone to what it was when you performed the backup. When you restore, you want to restore everything, not individual .img files.

In order to perform a Nandroid backup, you need a custom recovery from which to do it. AmonRa and Clockworkmod are the 2 most popular. I use AmonRa which has a Nandroid backup menu option. When you select the Nandroid backup with AmonRa, you are prompted for which partitions to backup. system, data and boot should always be backed up. cache is optional as it will be regenerated during normal phone use and, as far as I know, doesn't contain any system or application settings.

That's the short of it. If you did all that and your restore failed, that's unusual.
Click to expand...


I used amon ra for the backup. I went to nand backup and the recovery did its thing. When I went to do the restore, a menu came up with three things marked off. I didn't mess with that menu. I wioed data, cache and dalvik and tried wiping system as well on one of the many times I tried. Everything seemed to work fine except the signal... I guess take it as a bad backup?
 
The signal, I believe, is in the radio which is implemented in firmware. I'm not sure in which partition the firmware lives or if it is backed up even with a Nandroid backup.

What do you see displayed for the signal icon in the top status bar? What happens if you turn the radio off and back on (i.e. go into Airplane Mode and then exit Airplane Mode)? I've read that turning on WiFi sometimes causes the signal icon to be hidden. Try turning off WiFi and see if the signal icon comes back. Are you able to use the phone at all?
 
kool kat2 said:
Edit: I was under the impression that the backups created contained everything to just work once flashed. Assuming I wiped everything, shouldn't the backup have worked? Does the .img file have to be flashed for the backup?
Click to expand...

if you booted to a permanent recovery to restore a nandroid backup then YES,you NEED to flash its kernel seperately,if you are restoring a rom with an imcompatible kernel(i.e. ICS to gingerbread)

however...

if you put your phone in fastboot,and launch recovery from there with the command:
fastboot boot <recoveryname>.img
then you will be able to resotre backups normally. i have done it several times,it works. i usually wipe data/factory reset,wipe cache,wipe dalvik cache,wipe boot,wipe system then restore the backup.

you never had troubles with the permanent recovery on other devices becasue they were prolly not HTCdev unlocked ;) htcdev does not allow the boot partition to be written to from the recovery partition,only from fastboot. your other devices,if rooted via some other hack or exploit had functional recoveries that were able to write to the boot partition(and thus automatically restore and flash kernels)
 
thornev said:
The signal, I believe, is in the radio which is implemented in firmware. I'm not sure in which partition the firmware lives or if it is backed up even with a Nandroid backup.

What do you see displayed for the signal icon in the top status bar? What happens if you turn the radio off and back on (i.e. go into Airplane Mode and then exit Airplane Mode)? I've read that turning on WiFi sometimes causes the signal icon to be hidden. Try turning off WiFi and see if the signal icon comes back. Are you able to use the phone at all?
Click to expand...

The signal icon is grey bars with a red x over them. Toggling 4g or airplane mode did nothing. I didn't test wifi but I did toggle that and found networks. The phone was useable (although without any signal, it wasn't really ;))
 
scotty85 said:
if you booted to a permanent recovery to restore a nandroid backup then YES,you NEED to flash its kernel seperately,if you are restoring a rom with an imcompatible kernel(i.e. ICS to gingerbread)

however...

if you put your phone in fastboot,and launch recovery from there with the command:
fastboot boot &lt;recoveryname&gt;.img
then you will be able to resotre backups normally. i have done it several times,it works. i usually wipe data/factory reset,wipe cache,wipe dalvik cache,wipe boot,wipe system then restore the backup.

you never had troubles with the permanent recovery on other devices becasue they were prolly not HTCdev unlocked ;) htcdev does not allow the boot partition to be written to from the recovery partition,only from fastboot. your other devices,if rooted via some other hack or exploit had functional recoveries that were able to write to the boot partition(and thus automatically restore and flash kernels)
Click to expand...

Thanks for this info. Just to see if I understood right or didn't, you're saying that restoring a backup when recovery is launched in fastboot with the command doesn't require the kernel to be flashed separately?
 
for roms that are based on the leaked software, do i have to flash the leaked update first before flashing these roms? im assuming yes but i want to make sure
 
kool kat2 said:
for roms that are based on the leaked software, do i have to flash the leaked update first before flashing these roms? im assuming yes but i want to make sure
Click to expand...

yes,you do.

to avoid some tense moments when flashing the leak,i would pretty strongly reccomend to relock,and flash the 2.01.605.11 RUU first.

i flashed the leak overtop of business sense and my phone freaked out,lol. ended up having to flash it 3 times to get it working,and i hed this in the middle of it:
IMAG0009-1.jpg


:eek:
 
scotty85 said:
yes,you do.

to avoid some tense moments when flashing the leak,i would pretty strongly reccomend to relock,and flash the 2.01.605.11 RUU first.

i flashed the leak overtop of business sense and my phone freaked out,lol. ended up having to flash it 3 times to get it working,and i hed this in the middle of it:
IMAG0009-1.jpg


:eek:
Click to expand...

Uh oh haua yea i wanna avoid that. (although I already had some problems as you can see from my posts in the other thread:rolleyes:)

So first relock, flash old ruu (through adb on the commands? The way the permanent recovery was flashed?) THEN flash New ruu? And this will take care of hboot as well?
 
kool kat2 said:
Uh oh haua yea i wanna avoid that. (although I already had some problems as you can see from my posts in the other thread:rolleyes:)

So first relock, flash old ruu (through adb on the commands? The way the permanent recovery was flashed?) THEN flash New ruu? And this will take care of hboot as well?
Click to expand...

you can relock and run the 2.01.605.11 RUU as a .exe file, or as a PH98IMG. or you could follow the directions to flash the 2.01.605.11 "mini-ruu" then relock after. however youre comfortable doing it is fine,i think you just want to be on stock software when you relock and run the leaked RUU.

you can run the leak by renaming PH98IMG and putting on your sd card,or by putting it into your adb/fastboot file and flashing it in fastboot just like the mini-ruu: fastboot flash zip rezound_ics_androidpolice_3.11.605.22.zip if you dont rename it.

either way,be forwarned that after the hboot pre-update,the phone will boot back to bootloader,possibly powering off for a few seconds in the process. dont panic,just give it a few seconds for bootloader to come back up.

if youre running the ruu in fastboot,be aware that you will get a 'hboot pre update fail! please flush again immediately' error,wich is normal. wait for the RUU screen to come back on,then run fastboot flash zip rezound_ics_androidpolice_3.11.605.22.zip again immediately. if youre on stock software,it should finish the second time.

for S&Gs,heres how it went for me:
-booted to fastboot
-launched recovery
-made a backup of business sense 2.3
-booted back to fastboot
-relocked
-immediately got the security warning
-erased cache,put it in ruu mode
-ran zip with above command
-hboot preupdate failed. powered off.
- i didnt wait for RUU mode,went ahead and entered the command again
-phone came on in fastboot,not ruu mode. showed status bars while cmd window was "sending zip,parsing,etc"
-error in cmd window "update fail! remote not allowed" :eek: and then tampered popped up. powered off. this time i waited for bootloader to come back up before entering any commands.
-erased cache again(i think),put in ruu mode
-flashed zip a third time with the above command
-picked up where it had left off,and finished this time. *sigh of releaf* ;)
-finished,booted,gave it a few minutes to settle. enable usb debug,boot back to bootloader.
-security warning and tampered were gone hooray! :D
-re-unlocked with original unlock token
-reboot,let settle,enable usb debug. boot to bootloader
-back to unlocked,but tampered was back. :mad: dammit!
-launched recovery,flashed superuser. rebooted. let settle
-signed into google,download titanium,restore rest of apps. good to go:cool:

so my bootloader screens(hboot and fastboot) still say tampered,but it doesnt seem to affect anything. hope that helps. :)
 
so i went back to stock fine. everything worked. then i tried to do the leak through PH98IMG. when the list of things that are updating came out, it went out of order and didnt finish. when it rebooted i was still on GB and my sd card is not visible. Ill try to do it through adb and see what happens. BTW, I checked the md5 and it checked out fine.

EDIT: tried again, just like that again because i was too lazy to get all complicated with it :p

all is well with the world now, ... hopefully lol, thanks for all the help, i dont know where id be right now if it wasnt for your detailed instructions and patience scotty
 
You must log in or register to reply here.
Back
Top Bottom