As described here: http://forum.xda-developers.com/showthread.php?t=2018518, the thread says that it is the upgraded radio that causes a bootloop.
Before I ran into this problem, I created a backup of my stock rom. When my phone started having problems, I tried restoring my phone using the backup, but it didn't work. Why?
When running a backup, doesn't it make a copy of the whole phone? If the updated radio was the problem causing my bootloop, why doesn't the recovery restore the radio as well?
Also, is there any way to prevent my phone from receiving the OTA radio update?
infinitefusion said:
As described here: http://forum.xda-developers.com/showthread.php?t=2018518, the thread says that it is the upgraded radio that causes a bootloop.
Before I ran into this problem, I created a backup of my stock rom. When my phone started having problems, I tried restoring my phone using the backup, but it didn't work. Why?
When running a backup, doesn't it make a copy of the whole phone? If the updated radio was the problem causing my bootloop, why doesn't the recovery restore the radio as well?
Also, is there any way to prevent my phone from receiving the OTA radio update?
Click to expand...
Click to collapse
Was it a nandroid backup (with CWM)? If so, doing a full wipe might (?) fix the problem.
infinitefusion said:
As described here: http://forum.xda-developers.com/showthread.php?t=2018518, the thread says that it is the upgraded radio that causes a bootloop.
Before I ran into this problem, I created a backup of my stock rom. When my phone started having problems, I tried restoring my phone using the backup, but it didn't work. Why?
When running a backup, doesn't it make a copy of the whole phone? If the updated radio was the problem causing my bootloop, why doesn't the recovery restore the radio as well?
Also, is there any way to prevent my phone from receiving the OTA radio update?
Click to expand...
Click to collapse
U flashed a new rom?
Sent from my One V using xda premium
R: [Q] Why doesn't restoring a backup fix the bootloop?
When I restore it doesn't flash the kernel on its own so I always flash the kernel anyways
Sent from my One V using xda app-developers app
Related
I just tried flashing the new wimax update and it went through and succeeded, but now my phone reboots after a minute or 2 once it's fully booted. If I'm in recovery mode it doesn't have that problem at all. I'm using baked 1.5.
michaelm718 said:
I just tried flashing the new wimax update and it went through and succeeded, but now my phone reboots after a minute or 2 once it's fully booted. If I'm in recovery mode it doesn't have that problem at all. I'm using baked 1.5.
Click to expand...
Click to collapse
Have you tried the standard "wipe cache and data, then reflash your ROM"?
Noxious Ninja said:
Have you tried the standard "wipe cache and data, then reflash your ROM"?
Click to expand...
Click to collapse
I have re-flashed the wimax radio and wiped the dalvik/regular chache and did a factory reset.
did you wipe? that will solve most of your problems with out the need of a thread being made.
DomSim said:
did you wipe? that will solve most of your problems with out the need of a thread being made.
Click to expand...
Click to collapse
First of all, mods please move my topic to Q&A. I did not mean to post this in this forum. Also yes I've wiped everything about a million times.
michaelm718 said:
First of all, mods please move my topic to Q&A. I did not mean to post this in this forum. Also yes I've wiped everything about a million times.
Click to expand...
Click to collapse
Did you try flashing an older version or a nandroid? If you are using clockwork make sure signature checking is turned on too, you could have a corrupted file.
xHausx said:
Did you try flashing an older version or a nandroid? If you are using clockwork make sure signature checking is turned on too, you could have a corrupted file.
Click to expand...
Click to collapse
I tried flashing an older version and that didn't work either. What is this thing about nandroid? How do I go about that?
Edit: I fixed it by restoring google proprietary stuff(forgot the name) and restored nand. Which one fixed it? I have no idea, but it basically restored me to factory 2.1, but with root access. Mods please lock/ delete this. It's in the wrong forum and I apologize. Thank you
michaelm718 said:
I tried flashing an older version and that didn't work either. What is this thing about nandroid? How do I go about that?
Click to expand...
Click to collapse
A nandroid is a backup of your system you can make from the recovery, it's always a good idea to make one before you flash anything. I'm not sure if that covers your radios though.
Do you use titanium backup or anything? Without knowing how your phone is set up (what recovery you are using, etc) the only thing I can think of would be to flash the engineering bootloader. That should fix it but you would have to reinstall your ROM afterwards.
xHausx said:
A nandroid is a backup of your system you can make from the recovery, it's always a good idea to make one before you flash anything. I'm not sure if that covers your radios though.
Do you use titanium backup or anything? Without knowing how your phone is set up (what recovery you are using, etc) the only thing I can think of would be to flash the engineering bootloader. That should fix it but you would have to reinstall your ROM afterwards.
Click to expand...
Click to collapse
The nandroid restore worked because I had a backup I made while following the guide. I fixed it doing that, but while trying to update the radio to the current one again figuring if it messed up I can restore it and again the same problem came up, but this time nandroid restore wont work and it's telling me to use adb restore, but adb says your device is not found.
BTW all of my phones stuff come directly from the idiot proof guide(recovery etc)
bump... I'm sorry I'm sitting here with a semi broken phone. Is it possible to download someone else's nandroid back up and install it on mine? I know it will fix my problem as it already did, but for some reason now it's telling me to do it with adb, but my usb seems to not be working either.
I did a nandroid backup of my phone before going to CM7, after that I decided I want to go back, but it won't let me restore. It does the whole restore process but restarts CWM in the middle of restoring data.
I tried to narrow it down and it seems it crashed when restoring "com.htc.messages".
Can anyone help me? I was on Android Revolution 2.0.1.1 going to PNK Crispy Duck.
EDIT #1: I tried restoring again and it seemed to frezze when restoring something like "pdu"? Which is also in the data catergory, but the size of the backup - 1.14GB - seems to be right size, considering its bigger than my last back up - ~1.09G - so I don't know what the problem is :S
kamranh3 said:
I did a nandroid backup of my phone before going to CM7, after that I decided I want to go back, but it won't let me restore. It does the whole restore process but restarts CWM in the middle of restoring data.
I tried to narrow it down and it seems it crashed when restoring "com.htc.messages".
Can anyone help me? I was on Android Revolution 2.0.1.1 going to PNK Crispy Duck.
Click to expand...
Click to collapse
Which version of CWM are you using? It is known that backup and restores are f**ked up the newest version of CWM
Anyways, what you can try is to flash Android Revolution HD and then try to check if restore works then. It requires a bit of your time but it maybe worth trying.
sphuyal said:
Which version of CWM are you using? It is known that backup and restores are f**ked up the newest version of CWM
Anyways, what you can try is to flash Android Revolution HD and then try to check if restore works then. It requires a bit of your time but it maybe worth trying.
Click to expand...
Click to collapse
Im using CWM 2.5.1.3, so I really don't know where I could go wrong
kamranh3 said:
Im using CWM 2.5.1.3, so I really don't know where I could go wrong
Click to expand...
Click to collapse
Have you tried wiping everything before restoring??
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!
I know it says unlocking my device will void the warranty, but is there any way I can re-lock it later on so I could send it in for repairs or something in the event I have to do that? Would they be able to tell if I had previously unlocked it?
Yes...you can simply restore the device and relock the bootloader. The toolkit in the stickies in Verizon galaxy nexus development makes all that very easy.
Sent from my Galaxy Nexus using xda app-developers app
Awesome, just needed confirmation I could do that if I had any problems. Thanks!
You can flash the stock images and relock the bootloader, and they can't tell.
One more question. I have CWM installed and made a backup in it (plus an apps backup in Titanium)
If I, say, install CM9 and something weird happens (for instance, the radio magically stops working), will restoring from that CWM backup restore stuff like the radio and such (in addition to my stock 4.0.2 ROM, etc)??
EDIT: So I've backed up my apps with Titanium, but now the guide I am using says to wipe my device in CWM before installing a new ROM. If I do that, won't it also wipe the backup I just made?
Matt08642 said:
One more question. I have CWM installed and made a backup in it (plus an apps backup in Titanium)
If I, say, install CM9 and something weird happens (for instance, the radio magically stops working), will restoring from that CWM backup restore stuff like the radio and such (in addition to my stock 4.0.2 ROM, etc)??
Click to expand...
Click to collapse
CWM backs up your ROM, kernel, recovery and data. Not your radio or bootloader. But all the radios are available in the radio thread and all the boot loaders are available in the bootloader thread
Matt08642 said:
EDIT: So I've backed up my apps with Titanium, but now the guide I am using says to wipe my device in CWM before installing a new ROM. If I do that, won't it also wipe the backup I just made?
Click to expand...
Click to collapse
No, a wipe in CWM will not wipe /sdcard.
Sent from my Galaxy Nexus using Tapatalk 2
Hello everyone,
I have rooted and unlocked my bootloader, and installed CWM 6.0.2 I believe (summer 2012). I was using 4.3 Deodexed ROM and decided to upgrade to 4.4, so I mad a nandroid backup through CWM. Then I found out that 4.4 required me to update my CWM to 6.0.4.3, so I did. After upgrading CWM, I was unable to restore my old 6.0.2 backup. Is there any way to restore it, or do I have to downgrade CWM?
If I need to downgrade CWM, can I first perform a backup of my current 4.4 ROM and then downgrade, or is there a chance it will mess with old CWM?
Thanks in advance,
silentz0r
Sorry for bumping, I have noticed that after upgrading CWM, it made new directories into /sdcard and moved my old directories into /sdcard/0. I tried copying the contents of the old CWM directory into the new one (/blobs and /backup) and tried to restore, but still got the same error message notifying me that no backup is found. Is there no way to restore an old CWM backup with newer CWM?
If anyone ever has this problem, I suggest installing ROM Manager. My backups spontaneously started working through ROM Manager (even in CWM recovery). I have no idea why the backup could not be found before, but using this pretty much fixed itself. Marked as Solved.
silentz0r_ said:
If anyone ever has this problem, I suggest installing ROM Manager. My backups spontaneously started working through ROM Manager (even in CWM recovery). I have no idea why the backup could not be found before, but using this pretty much fixed itself. Marked as Solved.
Click to expand...
Click to collapse
Thanks for the heads up!
But shouldn't you just have made a back-up before CWM upgrade, then upgrade CWM, make another backup (just in case) and then install 4.4?
I am still on 4.3 and I will do it this way in the near future.