Database Users

Restoreing ROM w/ CWM - What am I missing?

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...

Broken Wi-Fi & Camera after TWRP

So I have the Razr M Retail, and I was rooted with Safestrap and running Hashcode0f's CM10, completely stable. Yesterday I decided to move to TWRP with the bootloader unlock, so I backed up my ROM to an external SD, and also separately used TiBu to backup my apps, and then used mattlgroff's Razr M Utility to unlock the BL and flash TWRP, which all went fine. Then I wiped internal storage and restored my backup from TWRP. It restored and booted fine, but the Wi-Fi and camera didn't work. The Wi-Fi is stuck to a toggled off position in the settings, and it's greyed out so I can't change it. If I click to see networks, it gets stuck in "Turning Wi-Fi on..." and I never see anything. The camera force closes with "Can't connect to camera." Since I hadn't been sure from the start that a restore would work, I was expecting trouble at this point, so I flashed a fresh version of CM10 from Hashcode's goo.im with the intention of restoring my apps with TiBu. It booted, but it seemed like it was running slow and the Wi-Fi didn't work, with the same issue as before. I didn't try the camera. I messed around with a few things trying to get it to work, and although nothing worked, I tried doing all of these separately and then reflashing:
a) Flash stock Moto 4.1.2 with the utility
b) Restore my stock rooted Moto 4.1.1 with safestrap (Just sayin, this gets weird, I end up with both TWRP and Safestrap)
c) Restore to b) and then restore my CM10 backup as a Safestrap ROM-slot 1
d) Dial *#*#526#*#* to reset Wi-Fi driver (did nothing afaik)
ALSO, I charged the phone last night and this morning at 8:30 it was at 100% battery. 3 hours later, with wi-fi, data, and GPS all off, and using the phone very very lightly, it was at 46%, so there is significant battery drain coming from somewhere.
Any help or suggestions would be greatly appreciated.

First off, you need to fastboot back to stock and start over. TWRP didn't break your phone, restoring a backup from SS did. If you flash a fresh CM10 build, not a backup, you should be okay and you should only get the bugs that are associated with CM10.
Ok, now you're going to ask why the backup didn't work. SS is designed to work on top of the stock boot.img, but CM10 has its own boot.img and that's the reason that CM10 builds were so buggy when used with SS. When you saved CM10 with SS, it probably saved the stock boot.img with it and the stock boot.img is not going to make CM10 happy. If you had saved a stock based ROM and tried to restore it, you probably would have been okay.
Now, with all that being said, if you fastboot back to 4.1.2, then you'll need to use a 4.1.2 based ROM or a CM build. If you want to use a 4.1.1 based ROM, you'll need to flash the 4.1.1 boot.img, prior to flashing the ROM. You battery is probably dying so quickly because CM10 is trying to fight with the stock kernel. You need to fastboot and flash clean.

Tmfle from
Thanks for the info, but it didn't work
I used the utility to fastboot flash stock Recovery and System, then root with Motochopper, and flash TWRP. I then used TWRP to wipe system and flash a fresh version of CM10, and when it booted there was noticeable graphics lag, and Wi-Fi and Camera didn't work.
I'll flash back to stock for tonight, hope you have another idea =\

VoraciousGhost said:
Thanks for the info, but it didn't work
I used the utility to fastboot flash stock Recovery and System, then root with Motochopper, and flash TWRP. I then used TWRP to wipe system and flash a fresh version of CM10, and when it booted there was noticeable graphics lag, and Wi-Fi and Camera didn't work.
I'll flash back to stock for tonight, hope you have another idea =\
Click to expand...
Click to collapse
Yeah, stop using CM builds. The camera and WiFi are known issues on those builds. What I told you solved the issue with your backed up CM build. This is the reason I don't use CM, they are all buggy right now. There was new one released with a different camera. See how that works for you.
What were your steps for install?
-Boot into recovery
-Wipe cache/dalvik, FDR
-Reboot recovery
-Mount system
-Flash ROM
-Wipe cache/dalvik
-Reboot system
FYI, I never wipe system, only cache/dalvik and FDR. Some people swear by wiping system, I don't do it.

RikRong said:
Yeah, stop using CM builds. The camera and WiFi are known issues on those builds. What I told you solved the issue with your backed up CM build. This is the reason I don't use CM, they are all buggy right now. There was new one released with a different camera. See how that works for you.
What were your steps for install?
-Boot into recovery
-Wipe cache/dalvik, FDR
-Reboot recovery
-Mount system
-Flash ROM
-Wipe cache/dalvik
-Reboot system
FYI, I never wipe system, only cache/dalvik and FDR. Some people swear by wiping system, I don't do it.
Click to expand...
Click to collapse
Hmm, I think I figured it out, or at least part of it, I'll make sure in the morning. Back in December-ish, before the bootloader unlock, Hashcode was releasing new CM10 builds every few days. Only the latest, dated 12/05, had working Wi-Fi, and that's what my backup should be. Now that I look at goo.im again, the only build on there is dated 11/14, and that's the one that I thought was 'fresh' but it never had working Wi-Fi or camera to begin with. Now I read through the CM10 thread here on XDA and I see that mic213 is building more current CM10 releases with more features working, and Hashcode has removed all of his builds except one (no idea why it's this particular one instead of the latest).
As for my install steps, they were actually:
-Boot into recovery
-Format Data (I said wipe system earlier, but I meant format data, as system gets wiped as part of it)
-I didn't reboot recovery, usually do but I got lazy
-Flash ROM (system was already mounted for me? )
-Wipe caches
-Reboot
So yeah, in the morning I'll download and flash mic213's build from here and I'm pretty sure that should work.

VoraciousGhost said:
Hmm, I think I figured it out, or at least part of it, I'll make sure in the morning. Back in December-ish, before the bootloader unlock, Hashcode was releasing new CM10 builds every few days. Only the latest, dated 12/05, had working Wi-Fi, and that's what my backup should be. Now that I look at goo.im again, the only build on there is dated 11/14, and that's the one that I thought was 'fresh' but it never had working Wi-Fi or camera to begin with. Now I read through the CM10 thread here on XDA and I see that mic213 is building more current CM10 releases with more features working, and Hashcode has removed all of his builds except one (no idea why it's this particular one instead of the latest).
As for my install steps, they were actually:
-Boot into recovery
-Format Data (I said wipe system earlier, but I meant format data, as system gets wiped as part of it)
-I didn't reboot recovery, usually do but I got lazy
-Flash ROM (system was already mounted for me? )
-Wipe caches
-Reboot
So yeah, in the morning I'll download and flash mic213's build from here and I'm pretty sure that should work.
Click to expand...
Click to collapse
Yeah, definitely use Mic's builds, they are more current. TWRP shows that the sytem is mounted, but it is fact not. That's why you need to reboot recovery. When you reboot, you'll see that it's not mounted.

Mic's CM10 is very, very stable. Very good build.
10.1 is a little more buggy but still a good build.
Sounds like you're either using one of Hash's old builds or new, buggy ones. Mic is the way to go for now
Sent from my Nexus 7 using Tapatalk HD

Phone soft-bricks upon flashing any Touchwiz-based rom?

Hi XDA, I'm a relatively new owner to Android phones (3 weeks) and have a problem that I can't find any leads on.
I cannot flash any Touchwiz-based ROMS without the phone going into a boot loop and having to reflash via Odin. I know that AOSP ROMS work fine because I use goomanager to flash CM10, Carbon, and Liquid smooth previously. The problem only occurs with touchwiz roms. Here is the rundown of how I noticed the problem:
I download Crash ROM and move it to my internal SD card. I install TWRP via goomanager. I then use goomanager to wipe the data, cache, and dalvik cache, and to install the Crash ROM zip. The phone gets to the samsung logo then gets stuck in a boot loop.
I reflash it through Odin using the tutorial at GalaxyS4root and it boots fine. I use goomanager to reinstall TWRP and try flashing it through TWRP instead, again doign a full wipe of the data, system, cache, and dalvik cache. Same thing occurs and I reflash through Odin.
Fast-forward to last night; I decide to try another Touchwiz rom, this time Wicked ROM. I download it and put it on the internal SD card; using TWRP I wipe it again, and install it. Aroma Installer comes up and I make sure to select AT&T as my carrier. I get to the end of the installation and the phone reboots. This time its much worse than it was with Crash ROM, the phone is vibrating to signal it starting up, but the screen stays blank and then a few seconds later it vibrates again. This repeats constantly and the phone also couldn't boot into recovery mode (but it could boot to download mode). So I tried reflashing it twice, but the issue persisted. Through google I determined it to be a stuck power button. I've returned the phone to AT&T to be replaced for faulty hardware and am awaiting its return.
So now is where I ask you guys. I've spent a solid hour googling this and nothing related to my problem comes up. So does anyone have any experience with the S4 not being able to flash touchwiz based roms? Or could anyone point me to any leads as to why this would occur that I can investigate further?
Thanks for the help.
-Tryer
EDIT: I'm pretty sure it wasn't MF3 because I could flash certain ROMS fine.

You made sure to flash a touchwiz kernel? And if you have AT&T model you made sure to use either auto-loki recovery or flash the loki zip?

DeadlySin9 said:
You made sure to flash a touchwiz kernel? And if you have AT&T model you made sure to use either auto-loki recovery or flash the loki zip?
Click to expand...
Click to collapse
For Wicked ROM, in the Aroma installer it asked which kernel I wanted, I don't remember for sure but I either chose Stock or Deviant. I'm still new to Android device so does GooManager or TWRP auto-loki? If not then I did not flash loki over either, I'm not sure if this would keep touchwiz ROMS from running but allow AOSP ROMS to run.

Tryer1234 said:
For Wicked ROM, in the Aroma installer it asked which kernel I wanted, I don't remember for sure but I either chose Stock or Deviant. I'm still new to Android device so does GooManager or TWRP auto-loki? If not then I did not flash loki over either, I'm not sure if this would keep touchwiz ROMS from running but allow AOSP ROMS to run.
Click to expand...
Click to collapse
Just skimmed the OP and thread a bit - sounds like you need to loki your kernels, basically. TWRP doesn't auto-loki, but do a quick search for loki-doki.zip - if flashed immediately after flashing a kernel (or rom with kernel), it will patch the kernel to take advantage of the Loki exploit in aboot. You pretty much have to do this for every/any kernel that's not 100% pure stock. Some recoveries (like CWM I believe) will auto-loki, but I don't ever rely on these. I just always flash loki-doki.

Aou said:
Just skimmed the OP and thread a bit - sounds like you need to loki your kernels, basically. TWRP doesn't auto-loki, but do a quick search for loki-doki.zip - if flashed immediately after flashing a kernel (or rom with kernel), it will patch the kernel to take advantage of the Loki exploit in aboot. You pretty much have to do this for every/any kernel that's not 100% pure stock. Some recoveries (like CWM I believe) will auto-loki, but I don't ever rely on these. I just always flash loki-doki.
Click to expand...
Click to collapse
Thanks, how would I loki something like Wicked ROM though, which once it finishes with Aroma installer, immediately reboots the phone and bricks itself? I don't have a chance to loki as I can't get back to TWRP before that occurs. Also there is a chance the new phone I receive will have MF3, will rooting and using Loki allow me to use Odin to restore it, or is there as of yet no way to reflash the stock ROM on MF3 devices?

Tryer1234 said:
Thanks, how would I loki something like Wicked ROM though, which once it finishes with Aroma installer, immediately reboots the phone and bricks itself? I don't have a chance to loki as I can't get back to TWRP before that occurs. Also there is a chance the new phone I receive will have MF3, will rooting and using Loki allow me to use Odin to restore it, or is there as of yet no way to reflash the stock ROM on MF3 devices?
Click to expand...
Click to collapse
when the device reboots after the aroma install, i would pull the battery, replace it and use the 3-button combo to enter custom recovery. then i'd flash the loki-doki zip. thats just me though. i hate aroma.
http://lmgtfy.com/?q=what+is+loki+doki
also: http://forum.xda-developers.com/showthread.php?t=2292157

[Q] N910G won't boot after TWRP restore?

Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS

MrDhark32 said:
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
Click to expand...
Click to collapse
This http://forum.xda-developers.com/note-4/help/n910c-to-stock-rom-cm13-t3321132 :good:

One possible solution is to flash the appropriate stock rom via odin. After booting, install twrp and root your phone. After this you can restore your previously saved stock rom via twrp.

MrDhark32 said:
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
Click to expand...
Click to collapse
Sorry no help from me but I have a similar problem. At some point mine quit booting to TWRP and I got a huge OTA update a few days ago and every time I try to boot into recovery it ends up in Stock Recovery only after going to little android saying installing updates(it fails & eventually goes to stock recovery.) I did a reset and still have 5.1.1 installed and still have the same behavior.
I have the professional version of the unified toolkit and it says if it is still booting into stock recovery select options 7, 3 which I did but it didn't fix the problem. I think what's getting me is it thinks there are still system updates to install.

"Camera Failed" After Restoring in TWRP

I restored a backup from a few weeks ago after trying out a marshmallow based ROM (I was on lollipop prior) and after the restore process, my old phone interface came up and it was as if I never flashed the newer rom at all as expected, however, now my camera does not work at all and I could use a hand figuring out how to resolve this issue.
Things I've tried:
- Rebooting (obviously)
- Clearing cache/dalvik from recovery
- Clearing the camera app's data and cache
When I restored my backup, I chose not to restore 'boot' and 'recovery' because while I was on the marshmallow rom, I unlocked my phone's bootloader and installed TWRP (as opposed to using SafeStrap) and I didn't want to lose it.
Samsung Galaxy S5 GM-900V
Android 5.0
Baseband: G900VVRU2BOG5
Build: OptimalRom 15-5
Marshmallow rom I referenced: Norma_Note5Port_V3.4_VZW
Any advice?

So I've formatted dalvik/cache/data/internal storage and installed the older rom (OptimalRom 15-2 ) again. Did the initial setup and the camera still didn't work. I tried reflashing a known-good kernel that's compatible with this rom and that didn't seem to help.
Can anyone point me in the right direction on how to resolve this? Something must have been flashed when I installed the Note 5 rom that wasn't when I went back to OptimalRom. I just don't know what. I'll keep searching and experimenting. Thankfully I have a real recovery menu now so softbricking isn't as big of a deal.

GoTeamScotch said:
So I've formatted dalvik/cache/data/internal storage and installed the older rom (OptimalRom 15-2 ) again. Did the initial setup and the camera still didn't work. I tried reflashing a known-good kernel that's compatible with this rom and that didn't seem to help.
Can anyone point me in the right direction on how to resolve this? Something must have been flashed when I installed the Note 5 rom that wasn't when I went back to OptimalRom. I just don't know what. I'll keep searching and experimenting. Thankfully I have a real recovery menu now so softbricking isn't as big of a deal.
Click to expand...
Click to collapse
Since you have TWRP now, try doing a complete and clean wipe. Go into recovery, Wipe, Advance Wipe and select Cache, Dalvik cache, Data and Internal and swipe. Then back out to Wipe and swipe twice on the slider and install the OptimalRom of choice. then install the PB1 firmware NO Bootloader. If you still have an issue then try with the ROM kernal and flash it which I think it'sthe OG5 Kernal No Bootloader. The reason for doing this particular wipe is to get anything that may be left over from a previous ROM. This is my preference and habit from when I started running ROM's on my S3. Beanstown103 and others had recommended doing this in TWRP and haven't had any issues or problems by doing this since. Hope this may help

Thanks al50. I will give that a shot. Sorry but I'm not familiar with "PB1 firmware". what are you referencing there?

GoTeamScotch said:
Thanks al50. I will give that a shot. Sorry but I'm not familiar with "PB1 firmware". what are you referencing there?
Click to expand...
Click to collapse
It's the version that your phone is on. Look in About Phone in settings. Anyways, that’s the Zip file you install after you install the ROM. But if you're already on PB1 then you don't have to worry about that. If you have issues with the camera then try flashing the No bootloader kernal that was made for that ROM, which I believe it was OG5 but check the OP to be for sure