Well, it has been baffling me for a while now. Simply put, no matter what, all backups that I have of Haykuro 6.0.1, and other ROMs that use both the new and old SPL no long work. The flashing goes fine, but when starting up, all I get is a bootloop. I am using CM's recovery image, could it possible be the recovery image? I doubt it as before, even with CM's recovery image I've been able to successfully backup and restore until recently. (After flashing JAC's hero it seems to have stopped working..)
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
so yes my phone is rooted and all. i've always been flashing roms over and over. but ever since i flashed the AOSP 2.2 OTA my recovery image goes back to stock after reboot. so i have to use ROM manager to keep reflashing a recovery for me. This is the first rom i have that is doing this. Is there a way to fix it or just make it permanent?
fixed it. i just flashed another rom.
When I first got my epic back in November, and I started playing around with CWM, Odin and different ROMs, I found that when I tried a different ROM, (DK18 at the time), when I tried to restore my original ROM, after restore, the phone wouldn't boot. I had never been able to restore my origial build without first ODINing the original build version back (DI18), root/CWM the load and THEN restore the backup, at which time it would work fine. After that, a friend told me that CWM doesn't wipe the phone whe way ODIN does, and that I needed to wipe everything first. I hadn't done any "playing around" since then.
Fast forward to today, I decided to try Cyanogen's 6.1 pre-beta 11.1. Copied the zip to my SD card, booted into recovery, wiped everything 3x, flashed the Cyanogen ROM and rebooted. It booted fine, but turns out it was totally unusable on my phone, although it looks like it will be really nice once complete and stable. I poked around a bit, looked at what was in the various menus, then decided to go back. Booted into recovery, wiped everything 3x, did full restore, and...... No boot. Hung at "Samsung" screen. Tried it again with the same results.
In the end, I had to do the same thing I had to do in the past: ODIN DI18 back in, One-Click v2.5.5, reboot into recovery, did full restore and now phone is back to "perfect health" right where it was before I flashed the Cyanogen ROM.
Can anyone tell me what I'm doing wrong? I would think it would be possible to backup and restore in the fashion I was trying.
Thanks,
Dave
The kernel and modem dont get backed up with cwm so its not a complete restore.
Sent from my Epic4g using the Inernet
When your flashing a new rom, usually it includes a different kernel. In the case of flashing a froyo rom (assuming you meant DK17 instead of DK18) or Cyanogen, I doubt the kernel is compatible with stock DI18.
When restoring a nandroid backup via CWM, it restores everything but the original kernel (modem only flashable from Odin), which is why your having issues after a restore. You have a froyo kernel + Eclair rom = no boot/bootloop. If you had a flashable zip of the stock kernel on your sdcard, you could flash that before/after the restore (but before rebooting) and it might work then.
Another issue you may have had with Cyanogen, from what I have read, is that you should have updated the modem.bin via Odin (to DK28) before flashing the rom.
Thanks, that would explain a few things. I guess the Cyanogen probably went bonkers due to the DI18 modem. Yes, I meant DK17, not DK18 . I'll dig up a flashable DI18 kernel and give it another go.
Are there any recoveries that will get everything? I'm told Amon Ra does, but it's not available for the Epic, and from reading, probably never will be. IMO, a FULL A to Z backup of the flash would be far better then the way CWM works at this time. Or is it a hardware limitation that prevents anything from getting 100% of the flash?
I'm having similar issues. It's not just the modem as I was on ACS deodexed DK28 with DK28 modem prior to trying Cyanogen. I can restore to any backups I made prior to mods, but anything that includes the Gingerbread theme doesn't work. I'm told it has something to do with the kernel, but even reflashing the ACS stock DK28 ROM prior to restore didn't work. So it looks like a complete flash via Odin is going to be required in many cases prior to restoring from CWM. That's my last hope.
I may try the cyanogen again tonight (and this time, flash the DK28 modem lol) and see what happens... before I do, I'll grab a flashable DI18 kernel, and see if I can restore withou odin (except for the modem). Worst case, can always use odin to recover. Kind of a pain, but it works.
Sent from my Epic 4G
I have a related stupid question, I'm on cm6 but I'm starting to miss being able to use wifi so can I just flash another dk28 rom or do I have to odin it back?
If your sticking with a rom that uses the same modem (DK28) then you should be able to just flash the new rom after wiping the data and cache (assuming the new rom includes a kernel, which I would think it would)
I have a similar question. I've been playing with a whole slew of ROM's (had the epic for about three weeks or so) I keep coming back to Quantom, but my quesiton is, I'm getting really fed up of having to reconfigure all my apps after a reflash of a new ROM (upgrade, tryain a different product, etc) Yeah the google syncing works nice, but configuring mail accounts, signatures, etc, gets old quick. Can you do an advanced restore of just the apps or use a similar method to restore your settings?
Can anyone suggest a good flashable DI18 kernel? The one I found here appears to be an update from DI07, so when I tried to flash it, it errored. Had to ODIN the stock back in again...
UPDATE: After completely wiping everything(recovery, ROM, bootloader, etc), and putting it back in with fastboot I no longer have this problem. My recovery probably just got corrupted or something while getting sent over to the device.
Got my Nexus 7 3 days ago, had it unlocked and all that jazz within the hour(thanks to the people who put the stuff together). It's great, but I have a problem with flashing .zip files in recovery. It doesn't matter what type of thing I'm wanting to flash(ex-kernel,rom, or even the uber-simple 720p camera mod), if I don't do a full wipe before flashing, then it just ends up boot looping my device. The boot loop doesn't turn the phone all the way off, just the boot animation. Sometimes the launcher will pop up for half a second and then go back to the boot animation.
For example, whenever I flashed the rasbeanjelly rom, I first flashed that, then rebooted(got excited and forgot about gapps) and checked it out. Remembering about gapps, I went back to recovery and flashed gapps. Then it boot looped the animation. After flashing gapps again(trying different combos of wiping cache/davlik), I flashed the rasbeanjelly rom again, and then gapps immediately afterwards. Still a bootloop. So I did a full wipe(including data this time), sideloaded my .zips, and then it flashed and rasbeanjelly booted up with gapps just fine.
This exact same problem has been happening with every .zip that I try to flash(running TWRP, yes all my stuff is updated). If I want to flash a kernel, I have to flash it when I flash my ROM or else I'll get boot loop. I can't really make any modifications without having to completely wipe my device(which is annoying because I carry a lot of data around on my stuff)
I'm asking if there is a way to flash a .zip without having to completely wipe my device. I'm not a noob to android at all(ROM cooker over at androidforums), but I can't figure it out, I'd love to make stuff for the grouper but this is kind of a big roadblock for me. Logcat isn't helping either. Hopefully I just skimmed over something and it's a simple fix. Thank you for your tips/suggestions/solutions.
EDIT: forgot to mention something. When I flash a new ROM and get it going, I always make a full backup in recovery. If I flash something, and boot loop it, I can't restore it correctly. Recovery says that it restores all good, but it still boot loops(even though I just restored a backup of a non-boot looping system from no more than 5 minutes ago).
If I read your post correctly, you've only tried this on one ROM. Try the same thing on CM10 or PA or whatever you want.
korockinout13 said:
If I read your post correctly, you've only tried this on one ROM. Try the same thing on CM10 or PA or whatever you want.
Click to expand...
Click to collapse
I've actually used several, and it seems to be happening on all of them. I've tried flashing things with PA, CM10, Stock, and RasberryJelly. The kernels I have attempted to flash have been Trinity, Motley, and Franco. All with no success and boot looping me :/