Timeline:
Flashed Onyx 4.2
Flashed EugeneKernel A11
Installed OCLF through Clockwork
---everything was working fine, but im anal about my phone and decided i wanted to nandroid restore back to 2.1, so heres that time line:
Disabled OCLF
Factory Wiped
Installed JAC-OV/UV Kernel (2.1 compatible)
Went to Nandroid Restore
I noticed that the restore finished way more quickly than usual, but clockwork said it finished successfully. so i went to reboot and it rebooted into stock recovery. odd. so i chose "reinstall packages" to flash back into clockwork, and now everytime it says "replacing recovery with Clockworkmod recovery" it then goes to "Vibrant" screen, and boots back into stock recovery. (same thing happens if i simply try to reboot, i always get sent back to stock recovery)
So is this happening because Clockworkmod LagFix edition is not compatible with my 2.1 kernel?? If so, is there a way to correct this WITHOUT using Odin?? ( i tried to adb push my old clockworkmod update.zip, in hopes that it would just overwrite the current one, it pushes successfully but same symptoms still occur)
Thanks ahead! (also, since i just backed up my sdcard today, id be more than willing to wipe my sdcard, if theres a way to do that through ADB without needing to be in ADB shell)
Related
I tried yesterday to one-click root my MT3G following unlockr.
Got the Amon-Ra recovery on there, but it hung on the green MT3G splash screen when I tried flashing cyanogen 4.1.11 .
Waited like over 20 minutes. So I took out battery, and tried to boot again. Same thing. So I rebooted into recovery and tried flashing ROM again.
No matter what ROM I tried, I got a "E:Can't open /sdcard/update.zip (bad)" message. (I redownloaded ROMs from different sources given the message thinking maybe they were bad or incomlplete, but nothing worked).
I finally did a nandroid restore.
Now I'm not sure where I am. Given that I restored my stock nandroid backup, my understanding is I'm no longer rooted. Though, I am still able to boot into the Amon-Ra recovery. which I thought would have not still been possible. I downloaded better terminal and tried typing "su" but it wouldn't let me continue, so that confirms not rooted, right?
Do I run the recovery flasher app again (which is still on the phone), and reflash a recovery image? Or should I delete the app and redownload the recovery flasher apk.
Just not sure how to safely retry.
You need to provide more details about your process. I actually unrooted mine previously done with Cyanogen Recovery and rerooted with same instructions on that site only this time with Amon Ra recovery image without problems. In my case I wanted the option of formatting partitions. Maybe you should try Cyanogen stable Rom first, like 3.68.1 version. I had an issue with 4.1.11.1 after I partitioned the card so I did 3.68.1>4.0.4>4.1.11.1.
Okay so last night I was putting on a new theme on my phone(MT3G/32B/T-MO Branded).
After applying the update, rebooted and it started to hang. Tried running one of the nandroid backups that I have saved and it booted backup but all sorts of processes kept force closing, not allowing me to do anything.
Tried a few more nandroid backups, with same results, so I decided to flash the stock firmware back on. So I put the sappimg.nbh file on sdcard and updated it with that.
Now the stock image ALWAYS works with no problem. It lets me flash a new recovery image with Recovery Flasher(Tried Rav 1.2 and CM-1.4). Both recovery images work but when trying to update with a new rooted rom it sits at the first splash screen forever. I've tried a few roms like CM-4.0.4 and 4.1.11.1.
By this time i thought maybe the roms were corrupt so I downloaded a new CM-4.1.11.1 and it took a while but it did boot up, but once i put in my log in info it just froze on the home screen. Rebooted and stuck at the first splash again.
Remember how I said I reverted back to stock firmware? well once I did that and after all this trouble, I tried running a nandroid backup and no matter which one I run, it being and old one or if i just make a new backup they all come out with the same error: "Nandroid failed:run "nandroid-mobile.sh restore" from adb.
Any ideas??? At the moment i'm downloading CM-4.0.4 to try that because i've had problems with 4.1.11.1 and flashing that without having 4.0.4 already flashed. So i will try 4.0.4 right now, hopefully it works and if it does I will update to 4.1.11.1
Thanks guys, first post so don't be too rough...
my experience with that is solvet by booting recovery ROM from say raon and choose wipe data, then reboot
lupascu.marius said:
Okay so last night I was putting on a new theme on my phone(MT3G/32B/T-MO Branded).
After applying the update, rebooted and it started to hang. Tried running one of the nandroid backups that I have saved and it booted backup but all sorts of processes kept force closing, not allowing me to do anything.
Tried a few more nandroid backups, with same results, so I decided to flash the stock firmware back on. So I put the sappimg.nbh file on sdcard and updated it with that.
Now the stock image ALWAYS works with no problem. It lets me flash a new recovery image with Recovery Flasher(Tried Rav 1.2 and CM-1.4). Both recovery images work but when trying to update with a new rooted rom it sits at the first splash screen forever. I've tried a few roms like CM-4.0.4 and 4.1.11.1.
By this time i thought maybe the roms were corrupt so I downloaded a new CM-4.1.11.1 and it took a while but it did boot up, but once i put in my log in info it just froze on the home screen. Rebooted and stuck at the first splash again.
Remember how I said I reverted back to stock firmware? well once I did that and after all this trouble, I tried running a nandroid backup and no matter which one I run, it being and old one or if i just make a new backup they all come out with the same error: "Nandroid failed:run "nandroid-mobile.sh restore" from adb.
Any ideas??? At the moment i'm downloading CM-4.0.4 to try that because i've had problems with 4.1.11.1 and flashing that without having 4.0.4 already flashed. So i will try 4.0.4 right now, hopefully it works and if it does I will update to 4.1.11.1
Thanks guys, first post so don't be too rough...
Click to expand...
Click to collapse
???
I've wiped so many times i can't even remember. Before and after each thing i said that i did a wipe...so no go on that, but it doesn't matter anymore. i've updated to rooted Donut 1.6 now. Thanks anyways tho
I backed up my DI18 stock install using CW Recovery. I then installed a leaked version of DK17. I'd like to return to DI18, but when I try to do a recovery the phone hangs on the Samsung logo (after I finish the recovery and reboot).
Do I need to use Odin to go back to stock DI18 and THEN restore my phone using CW Recovery?
I just did this last night after I noticed Froyo to be too buggy. YOu have to back to stock DI18, root it then install clockwork. Then simply restore, mine works great.
Thanks! That's what I thought. I figured it was a firmware conflict or something that was blocking my boot up to 2.1/DI18.
I'm installing Clockwork now.
I was running CM6.1.1, did a backup using Clockworkmod recovery 2.5.x.x. Updated CW recovery to 3.0.0.5, then flashed GingerVillain 1.5. Decided it wasn't for me, so I wiped and then restored my CM6.1.1 image. Restore completes okay, reboot and now I'm stuck at the HTC screen. Also tried wiping and restarting, still stuck.
Is CWM 3.0 not capable of restoring Froyo roms? Do I need to reflash 2.5.x.x, then restore my CM6.1.1?
Thanks in advance!
Sorry for being so quick to make a thread. Reflash of Clockworkmod 2.5.1.3 allowed me to restore and boot my backup. Problem solved.
Hey guys, I have a weird issue. I recently (re)aquired a MyTouch 3G Slide after selling my old one. The other I rooted back when rooting was still super-hard. I bought it the day it came out, and had CyanogenMod7 running beautifully and everything.
The "new" mytouch 3g slide I aquired was factory reset (s-on) on 2.1. I tried to update to 2.2, but HTCs website doesnt seem to have the files anymore. So I rooted it using UniversalAndroot. I tried to run RomManager to flash recovery, but as you know, it no longer supports 2.1 and below, so that sucked.
I found an old version on here, flashed it as update.zip, and everything was good.
Now that I'm rooted I flash CyanogenMod7 and GAPPS. Everything installs fine, except GAPPS didn't. So I reboot into recovery, and I see it's stock again. Hmmm, strange. I install update.zip again, recovery comes back, I flash GAPPS again, this time only the market installs. Fine with me.
I reboot into recovery to make a back-up after installing everything. Strange...stock recovery AGAIN. Install update.zip, everything is fine, create my backup, reboot and I update CWM through RomManager, everything's good. Reboot into recovery. STOCK RECOVERY AGAIN.
It seems the only way to get into CWM is to flash update.zip (luckily only takes a few seconds), but is there anyway to make it stick? I had to force update SuperUser as well, and a few other things.
So my question is, if I downgrade to stock 2.2 from HTC, root, then reupgrade to Cyanogenmod 7, would all my issues be fixed?
Update.zip will NOT change the recovery; it will only allow you to use the custom recovery for that certain time. You must obtain the recovery image(recovery.img) and then boot into fastboot(press vol-down+power, then press power) and, on your computer, move the recovery.img to the same directory as fastboot and then, still on your computer, type fastboot flash recovery recovery.img, and there you go