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)
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...
Heres my situation:
I installed the froyo rom without installing the new CWM first. So i tried renaming the new cwm and replacing it with update.zip to no success, and never reverted back to the old one. Now i decided to revert back to stock, install the new CWM, and than flash the froyo rom. But something went wrong.
I flashed odin stock-i500-vzw-system.tar.md5, and upon reboot it sounds the vzw sound, but stays in the samsung bootup screen, and it won't go into recovery because my update.zip is broken.
My odin for some reason fails every time i try to flash the old recovery, or the old kernels, it only wants to flash system.tar.
Thats as detailed as i can get it for now, any help would be great.
look around for some different stock odin files. i had a hard time with flashing cwm files as my phone just wouldnt accept them for some reason.
i'm gonna try adrenalyn's system.tar, kernel and CWM DI01 package, see if this works. keep fingers crossed
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.
2 days ago i foolishly flashed to a stock rooted deodexed MJA zip from Cyanogenmod 10.2. (NO I DID NOT MAKE A BACK UP. I DID do a full data/cache wipe before i flashed) Things got really weird after that. Phone would not boot past the yellow sprint screen. I had a few different backups that must have been old so i tried restoring to an older Triforce MF9 backup that i had from 2 months ago. After that i was stuck on the triforce boot animation. I thought "maybe my kernel got mixed up when i tried flashing to MJA". Downloaded and flashed stock MF9 kernel NO LUCK.
Ended up using ODIN to install a factory stock .tar of MF9... same boot loop, cleared cache(this succeeded), tried clearing dalvik cache (but it failed). It booted up and YAY stock MF9 WITH ROOT. So after all the sprint bloatware loaded up i was prompted for an OTA 4.3 updated. I foolishly accepted. So my phone shuts down into recovery installs the update then goes to CWM and says "fix root? yes or no" i hit "yes". Since then NOTHING has worked.
I tried to ODIN back to MF9 again as mentioned before, nothing. I thought it may be a kernel issue, I found no info on the new MJA kernel. I successfully used ODIN to flash philz recovery.tar so now im on philz instead of CWM or TWRP. I attempted to flash the original stock rooted MJA.zip that got me into this mess, but no luck. I now can not get passed the "Samsung Galaxy S4 screen" (tried clearing caches, and battery pull too). Im downloading "KERNEL-SPR-L720VPUEMJA-1382157965.tar" & "SPR-L720VPUEMJA-20131030154609.zip" at the moment to flash with ODIN. Also i might add, it seems like any recovery i use, TWRP, CWM, Philz they dont fully install the rom .zip's. I hit "install zip from ext/sd-card" and its like a 2 second installation. NO MATTER WHAT ZIP I TRY. Kernels seem to flash okay.
I dont care about root, or knox. I just want my phone again lol.
Try going here
Tallyphillips said:
2 days ago i foolishly flashed to a stock rooted deodexed MJA zip from Cyanogenmod 10.2. (NO I DID NOT MAKE A BACK UP. I DID do a full data/cache wipe before i flashed) Things got really weird after that. Phone would not boot past the yellow sprint screen. I had a few different backups that must have been old so i tried restoring to an older Triforce MF9 backup that i had from 2 months ago. After that i was stuck on the triforce boot animation. I thought "maybe my kernel got mixed up when i tried flashing to MJA". Downloaded and flashed stock MF9 kernel NO LUCK.
Ended up using ODIN to install a factory stock .tar of MF9... same boot loop, cleared cache(this succeeded), tried clearing dalvik cache (but it failed). It booted up and YAY stock MF9 WITH ROOT. So after all the sprint bloatware loaded up i was prompted for an OTA 4.3 updated. I foolishly accepted. So my phone shuts down into recovery installs the update then goes to CWM and says "fix root? yes or no" i hit "yes". Since then NOTHING has worked.
I tried to ODIN back to MF9 again as mentioned before, nothing. I thought it may be a kernel issue, I found no info on the new MJA kernel. I successfully used ODIN to flash philz recovery.tar so now im on philz instead of CWM or TWRP. I attempted to flash the original stock rooted MJA.zip that got me into this mess, but no luck. I now can not get passed the "Samsung Galaxy S4 screen" (tried clearing caches, and battery pull too). Im downloading "KERNEL-SPR-L720VPUEMJA-1382157965.tar" & "SPR-L720VPUEMJA-20131030154609.zip" at the moment to flash with ODIN. Also i might add, it seems like any recovery i use, TWRP, CWM, Philz they dont fully install the rom .zip's. I hit "install zip from ext/sd-card" and its like a 2 second installation. NO MATTER WHAT ZIP I TRY. Kernels seem to flash okay.
I dont care about root, or knox. I just want my phone again lol.
Click to expand...
Click to collapse
you need to try to install the Triforce MJA/4.3.1 kernal/MJA modem all at the same time. IDK what happened on the first try to boot loop you but once you updated the modem to mja you can't flash MF9 modem/kernel on top of it. Try that and let me know.
Tallyphillips said:
2 days ago i foolishly flashed to a stock rooted deodexed MJA zip from Cyanogenmod 10.2. (NO I DID NOT MAKE A BACK UP. I DID do a full data/cache wipe before i flashed) Things got really weird after that. Phone would not boot past the yellow sprint screen. I had a few different backups that must have been old so i tried restoring to an older Triforce MF9 backup that i had from 2 months ago. After that i was stuck on the triforce boot animation. I thought "maybe my kernel got mixed up when i tried flashing to MJA". Downloaded and flashed stock MF9 kernel NO LUCK.
Ended up using ODIN to install a factory stock .tar of MF9... same boot loop, cleared cache(this succeeded), tried clearing dalvik cache (but it failed). It booted up and YAY stock MF9 WITH ROOT. So after all the sprint bloatware loaded up i was prompted for an OTA 4.3 updated. I foolishly accepted. So my phone shuts down into recovery installs the update then goes to CWM and says "fix root? yes or no" i hit "yes". Since then NOTHING has worked.
I tried to ODIN back to MF9 again as mentioned before, nothing. I thought it may be a kernel issue, I found no info on the new MJA kernel. I successfully used ODIN to flash philz recovery.tar so now im on philz instead of CWM or TWRP. I attempted to flash the original stock rooted MJA.zip that got me into this mess, but no luck. I now can not get passed the "Samsung Galaxy S4 screen" (tried clearing caches, and battery pull too). Im downloading "KERNEL-SPR-L720VPUEMJA-1382157965.tar" & "SPR-L720VPUEMJA-20131030154609.zip" at the moment to flash with ODIN. Also i might add, it seems like any recovery i use, TWRP, CWM, Philz they dont fully install the rom .zip's. I hit "install zip from ext/sd-card" and its like a 2 second installation. NO MATTER WHAT ZIP I TRY. Kernels seem to flash okay.
I dont care about root, or knox. I just want my phone again lol.
Click to expand...
Click to collapse
You cant go from aosp to tw. You need to go back to stock. Just odin back to mj9 stock. Then reroot and use that rom with philz rec
Sent from my SPH-L720 using xda app-developers app