I upgraded from early version of ViperRom on my Sprint HTC ONE to Viper 1.1.0.
Steps process ->
- Downloaded through GooManager
- Create backup
- Reboot into recovery
- Install -> Viper 1.1.0
- Reboot phone
... Phone stuck in boot loop
I couldn't restore the original backup because the phone will reboot before completed.
- Created a backup in TWRP
- Restore to factory
- Install 1.1.0 again
.... 1.1.0 ran fine except I get "Setting has stopped working"
- Reinstall
.... 1.1.0 is stable and working well.
I restore from the TWRP file and it goes right back to exactly before I wiped (data/aps/music/ect...) except it still bootloops
I would like to extract all the good info from the TWRP backup without it bootlooping
Is this possible?
UPDATE
I downloaded Nandroid and I can restore my call log, texts, and apps. I have a few permission issues but those are working themselves out. I can't however, restore my media.
Related
Recently I flashed Clockwork Recovery v3.005(?) so I could install AOSPCMod. As always I go to Nand Backup to create a backup. Everything was fine until it reached On The Hunt.OGG and it stuck for a while. So I pulled the battery after waiting around 10-15 minutes. Reboot and it's just stuck at the black HTC screen.
I can reboot to recovery, so do I just flash the ROM? I'm clueless
*Update* I removed my SD card from the phone and checked it out. The system backed up about 900 MB alone. Still don't know if this was the problem?
*Update 2* Flashed ClockworkMod Recovery v2.5.0.1 and everything seems to be working fine again
So I had alot of issues rooting but im finally in, all rooted. Downloaded ROM Manager from the market and installed CWM. Says its successful, but when I manually reboot into CWM i get a error, so I cant install the 1.1 fix
Any ideas?
Really no one knows? This sucks!
This normally happens when recovery is not flashed properly. Did you try flashing again via Rom Manager? Also when you flash, does the screen show something like "Rom Manager has been granted super user permissions"?
ya, it flashes successfully through rom manager....
I think the problem is when I was trying to go back to 1.0.1 I flashed a restore through CWM. Then I whiped the /system and /data folders. The directions said to do this but I didnt realize I was supposed to do this BEFORE flashing not after. Basically I had no restore partition left so when I went and let it fail to boot 8x i got a error, and i had no OS. I ended up doing the N/Pwr, it restored, then i got a bootable CWM, booted into it and flashed the 1.0.1. But not everything seems, odd.
I can go into Rom Manager and install CWM fine, it says installation successful. But if I reboot into recovery, I get the error. I really need this fixed but im thinking it may be easier to just use a bootable CWM. Any ideas? I need to get 1.1 on here before I lose root
DroidHam said:
I think the problem is when I was trying to go back to 1.0.1 I flashed a restore through CWM. Then I whiped the /system and /data folders. The directions said to do this but I didnt realize I was supposed to do this BEFORE flashing not after. Basically I had no restore partition left so when I went and let it fail to boot 8x i got a error, and i had no OS. I ended up doing the N/Pwr, it restored, then i got a bootable CWM, booted into it and flashed the 1.0.1. But not everything seems, odd.
I can go into Rom Manager and install CWM fine, it says installation successful. But if I reboot into recovery, I get the error. I really need this fixed but im thinking it may be easier to just use a bootable CWM. Any ideas? I need to get 1.1 on here before I lose root
Click to expand...
Click to collapse
I fixed this by downloading the latest busybox from the market, installed it, then ran the "fix permissions" from Rom Manager. I then reinstalled the latest CWM, and it would allow me to reboot into recovery.
Ok, in short I can't restore my rom after flashing Cyanogenmod 7 RC1. If I try to recover the phone remain locked in recovery mode.
That's the full story anyway:
Had a Galaxy S with Android 2.3.3 (Italy) rooted with CF-root
Made a backup with clockworkmod (no problem)
Made data/app backup with titanium backup (no problem)
Flashed Cyanogenmod 7 RC1 (no problem)
Restore Titaniun backup, have all my app back but had the first problem. None of my data has been restored, contacts, sms, calls... nothing. Why I ask?
Found that I can't access my sd card, read about the downgrade to froyo. Ok, time to restore to my original rom.
Made a restore of my nandroid backup, via rom manager.
BANG, phone hang up at boot on Galaxy S initial logo.
Ok, don't panic, restored an Eclair 2.1-u1 Rom via odin/download mode. Build XWJM7, Base XXJM3 (I read Flashing Eclair is safer)
Tried to update Android via Kies, but I get a message that my version cannot be upgraded.
Rooted Eclair via oneclickroot, installed rom manager/clockworkmod and tried again to restore my rom backup.
The restore seems to go Ok but the phone is stucked in recovery mode (2e). I get the Galaxy S logo for a few second, then logo disappear and reappear an phone go in recovery mode saying:
installing multi-csc
can't access to /system/csc/itv/system/
successfully applied multi-csc.
There is no way to go on, if I choose update.zip, phone go to clockworkmod recovery. Tried to restore an older backup, same result.
Now I'm again on Eclair.
So is there a way to have my original rom back via clockworkmod? Or I have to flash original CSC/MODEM/CODE via odin?
Thanks for helping.
I think your best choice is to flash from odin in download mode with a clean stock rom with re-partition to start again on a good base.
I made some other test.
Extracted the .img from cwm backup. The boot.img file is corrupted on both backup, file are identical so I though there's a problem backing up bootloader on my phone with cwm.
So I tried to recover all but boot. When I reboot (from eclair, cwm 2.5.1.2) in recovery mode I always get to android recovery 2e. As before if I select update.zip (and update is not present) system get me to cwm recovery. I select advanced restore and system ecc. but get the same problem the before: I get stucked in android recovery.
So again I flash via odin this time to gingerbread, rooted with cf-root, launch cwm manager tried for the last time to recover my damned backup.
And UA-TA! has my phone restored.
Any one has I idea why I was able to restore my rom (and app/data) only AFTER I restored my rom in another way?
I also made backup but it was giving error when i try to restor it
dadyal said:
I also made backup but it was giving error when i try to restor it
Click to expand...
Click to collapse
What error do you get?
Am using HTC Incredible S HBOOT 2.00
I recently unlocked the bootloader and installed ClockworkMod recovery and Cyanogenmod 7.1 ROM.
Before installing I took the backups properly. I tried restoring the same before installing the new rom. It was restored successfully.
The issue came when i booted with Cyanogen and used that for sometimes. and now I wanted to restore it.
I did reset the phone and wiped off davik cache as well.
I restore one of the versions and it resore everything and given a message ""Error while restoring /sdcard/.android_secure!"" at the end and I rebooted the phone, It kept on rebooted in recovery mod.
Am unable to use my mobile now. As a beginner to android I dont know wat to do.
Please help me ASAP. I want to get rid of this.
possible corrupt backup or old version of cwm. Try reinstalling the rom.
Hey guys, having some issues restoring a backup of a GPE ROM that I made with ROM Manager on a working device. It goes through the process of doing the restore and then boots to the google splash screen, but never goes past that point (waited 45 minutes twice).
The ROM is GPE 5.0.1 rooted. I'm using the lastest recovery from clockwork mod and have tried several times. Not finding anything on the web regarding this issue. Perhaps the backup is just borked?? Im (obviously) S-Off and unlocked. Not sure why im not able to restore to my prevous state. Works like a charm with cyanogenmod ROMS...
Any thoughts?
I want to help but I don't entirely get what you did.
so you made a backup and you can't restore it, right? I have some questions, if you were kind enough to answer them, I may be able to help you:
> What "ROM Manager" did you create your backup with?
> Is it an entire ROM backup, like the TWRP, CWM do it?
> What Android Version is the backup?
I am thinking that you might didn't backup the boot partition properly so you can't boot your phone. there would be a compatibility issue with your boot.img and the system and data partition. So you can boot but because of the compatibility issues you can't boot entirely and keep stuck in the bootloop. that's what I think what it is but I am not 100% sure so I asked you the questions above.
And it would be very helpful if you could make a photo of the backup restore screen (inside cwm/twrp .. with whatever of those you are trying to restore the backup)