So I was running CM10.1 nightlies with Franco Kernel and decided to make the jump to CM10.2. The ROM and gApps flash went just fine, but like a dummy, I flashed the version of Franco kernel that I'd been using before, which I guess is not compatible with 4.3. The phone seemed to be softbricked and would just hang at the Cyanogen boot animation. I can get into recovery and I've tried to reflash both CM10.1 and CM10.2 - both hang at the boot animation. I can go back to my stock backup just fine, but then when I try to flash CM again (either version), I have the same hanging problem. Does CM store like a memory of the kernel that you have flashed and try to revert to that? Why can't I flash CM again once I've gone back to stock (and the stock kernel)? Would reflashing the stock image fresh (rather than using a TWRP backup) change anything? I'm pretty inexperienced with this and would appreciated any help. Thanks in advance!
alphamini said:
So I was running CM10.1 nightlies with Franco Kernel and decided to make the jump to CM10.2. The ROM and gApps flash went just fine, but like a dummy, I flashed the version of Franco kernel that I'd been using before, which I guess is not compatible with 4.3. The phone seemed to be softbricked and would just hang at the Cyanogen boot animation. I can get into recovery and I've tried to reflash both CM10.1 and CM10.2 - both hang at the boot animation. I can go back to my stock backup just fine, but then when I try to flash CM again (either version), I have the same hanging problem. Does CM store like a memory of the kernel that you have flashed and try to revert to that? Why can't I flash CM again once I've gone back to stock (and the stock kernel)? Would reflashing the stock image fresh (rather than using a TWRP backup) change anything? I'm pretty inexperienced with this and would appreciated any help. Thanks in advance!
Click to expand...
Click to collapse
Just to be sure how much juice was left while you were flashing CM rom?? Reading your problem I would suggest you to do a fresh Stock image installation and then try flashing CM 10.2.
Have you tried restoring your NANDROID backup, if you made one??
Rohit02 said:
Just to be sure how much juice was left while you were flashing CM rom?? Reading your problem I would suggest you to do a fresh Stock image installation and then try flashing CM 10.2.
Have you tried restoring your NANDROID backup, if you made one??
Click to expand...
Click to collapse
I have restored the NANDROID backup successfully, but unfortunately I was lazy and only have the backup from when I first got the phone.
I backed everything up with Titanium Backup right before I tried to flash CM10.2. If I do a complete stock reflash, do I lose all the data I backed up with TB? I do have some app data that I would really like to keep if possible.
One other resort I thought of was flashing a different custom ROM (Paranoid Android maybe?) and then restoring my TB backup. Would there be any reason that I shouldn't be able to reflash CM after I've restored the stock NANDROID?
alphamini said:
I have restored the NANDROID backup successfully, but unfortunately I was lazy and only have the backup from when I first got the phone.
I backed everything up with Titanium Backup right before I tried to flash CM10.2. If I do a complete stock reflash, do I lose all the data I backed up with TB? I do have some app data that I would really like to keep if possible.
One other resort I thought of was flashing a different custom ROM (Paranoid Android maybe?) and then restoring my TB backup. Would there be any reason that I shouldn't be able to reflash CM after I've restored the stock NANDROID?
Click to expand...
Click to collapse
Try this.
As you are able to go in recovery,
Wipe cache , dalvik cache, system, data install PA 3.97 flash pa_gapps then supersu v1.51(for root,also enable app+adb from developer option)
wipe cache and dalvck again and reboot..
P.S : Charge your battery first to 80% minimum and flash the rom.
If the above doesn't help,
Backup all you valuable data into pc, backup app+data through TB move it to pc and flash the factory image through fastboot.
Rohit02 said:
Try this.
As you are able to go in recovery,
Wipe cache , dalvik cache, system, data install PA 3.97 flash pa_gapps then supersu v1.51(for root,also enable app+adb from developer option)
wipe cache and dalvck again and reboot..
P.S : Charge your battery first to 80% minimum and flash the rom.
If the above doesn't help,
Backup all you valuable data into pc, backup app+data through TB move it to pc and flash the factory image through fastboot.
Click to expand...
Click to collapse
I ended up flashing the stock image and completely wiping all data. I then tried to install CM10.2 again and it still hung at the CM boot animation for about 15 minutes. It shouldn't take that long to flash, right?
alphamini said:
I ended up flashing the stock image and completely wiping all data. I then tried to install CM10.2 again and it still hung at the CM boot animation for about 15 minutes. It shouldn't take that long to flash, right?
Click to expand...
Click to collapse
Did you use the Franco.Kernel for the JSS build?
Sent from my Nexus 4 using Tapatalk 4
Related
Any ideas on this one? I don't get any errors on the restore, but I am stuck on the eye every time I boot. I have tried wiping cache and dalvik cache.
About to just restore from Matt's tool, but this has me worried, you know?
Coronado is dead said:
Any ideas on this one? I don't get any errors on the restore, but I am stuck on the eye every time I boot. I have tried wiping cache and dalvik cache.
About to just restore from Matt's tool, but this has me worried, you know?
Click to expand...
Click to collapse
Well, have to say, thanks matt. The included RSD helped.
I forgot I was also restoring stock over CM10, which may have also been the issue, but I am back into the phone now.
You shouldn't have issues restoring backup from the older version, and you shouldn't have issues restoring a stock build over CM. Did you use the restore option or did you try to install the backup?
Sent from my Slim Scorpion-mini
RikRong said:
You shouldn't have issues restoring backup from the older version, and you shouldn't have issues restoring a stock build over CM. Did you use the restore option or did you try to install the backup?
Sent from my Slim Scorpion-mini
Click to expand...
Click to collapse
I have no idea what caused the issue. I did a backup of CM10, wiped data, cache, dalvik, and system. Hit restore on my old Stock backup (created in TWRP, not safestrap), wiped dalvik and cache again, and rebooted (and allowed TWRP to fix root first). It booted to the droid eye, but then just hung there for about 10 minutes.
I used Matt's utility to restore the system and it failed (tried to install the same part of system over and over again, 3mb in 4 seconds, 100k in .4 seconds, over and over again). So I had to force stop that and use RSD which worked fine.
No idea what all that was about.
So I think I found the culprit. My backups from the older version of TWRP don't have BOOT, only SYSTEM and DATA. So I was probably having my stock rom install while the CM10 BOOT was still in place.
The more you know
I was on Google edition using faux kernal. I decided to restore my stock rooted nandroid using twrp and I believe something went wrong. My phone rebooted on its own after the restore and everything went wrong from there. Force closes galore. I checked the kernal and it was still faux kernal so I figured that was the problem. I decided to wipe and restore one more time. This time it went smooth and I had the option to reboot when it was complete. Everything is running perfect but the weird thing is that the kernal appears to be stock now...
I'm very confused. Some Google searches led me to believe that a nandroid does not save your kernal but my kernal clearly changed on my second restore.
Does a nandroid restore kernal? What is the stock kernal for the i337 and is it around this site because I can't find it anywhere?
My kernal version reads...
3.4.0-453947
[email protected] #1
Sat April 27 17:06:05 kst 2013
Can someone confirm this is stock?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Cataligh said:
I was on Google edition using faux kernal. I decided to restore my stock rooted nandroid using twrp and I believe something went wrong. My phone rebooted on its own after the restore and everything went wrong from there. Force closes galore. I checked the kernal and it was still faux kernal so I figured that was the problem. I decided to wipe and restore one more time. This time it went smooth and I had the option to reboot when it was complete. Everything is running perfect but the weird thing is that the kernal appears to be stock now...
I'm very confused. Some Google searches led me to believe that a nandroid does not save your kernal but my kernal clearly changed on my second restore.
Does a nandroid restore kernal? What is the stock kernal for the i337 and is it around this site because I can't find it anywhere?
My kernal version reads...
3.4.0-453947
[email protected] #1
Sat April 27 17:06:05 kst 2013
Can someone confirm this is stock?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Yep, that's the stock kernel.
I'm not sure about TWRP. I know there are different options to save different partitions when creating a Nandroid with TWRP.
But there is something else I've been noticing through various posts about the S4. It seems that sometimes, with CWM, TWRP, or even ODIN, that some people have to flash files twice before they take. I'm not sure why it would be that way or if it's just a bunch of people screwing up on the first flash, but it sure seems that way. Maybe this is just one of those phones that depending on which lot you get, needs to be flashed twice?
yeah, Scott may be right. I don't think these recoveries are quite up to speed yet for the S4. Esp TWRP. I just like and have been use to TWRP UI.
Heard good things about Phil's Touch CWM--haven't tried yet. But, haven't restored yet either. Shabby's seems solid too. But, Phil's will restore both TWRP and CWM nandroids.
If you nandroided boot partition then the kernel should be restored
Only thing not touched in nandroids is radio
simply restoring the boot image from a nandroid will restore the kernel to what was backed up. I ALWAYS have a nandroid of a full factory ROM on my SD card in case I get problems. technically you don't even need to clear cache / dalvik cache.
note that some kernels actually flash more than the kernel and update Bluetooth and/or WiFi drivers, and would require more than the boot image to be restored.
keeping a fully stock ROM nandroid should be flashing 101... I've gotten into situations where I've had md5 mid matches when restoring backups, lost imei, all kinds of fun stuff. almost always doing a full factory reset/cache wipe/dalvik wipe/system format before restoring stock will fix those type of problems. after that I've had good luck then restoring the "problem" backup. very rarely have I ever had to Odin back to stock.
I installed a custom rom(GPE 5.0)on my i337m from Android 4.4.2 Stock ROM. I made a Nandroid backup with twrp 2830 before flashing the new rom. After playing with it a while I decided to go back to 4.4.2 using the Nandroid backup.
The Nandroid restore was successful(did a factory wipe before restore). However now I am getting force close non stop(seems like every app after the boot animation). I did a second restore without factory wipe and same problem. How can I get my backup restored properly?
If I install a custom rom(tried Goldfinger v9 among others), they boot fine. Any help would be greatly appreciated.
Thanks
TRoN_1 said:
I installed a custom rom(GPE 5.0)on my i337m from Android 4.4.2 Stock ROM. I made a Nandroid backup with twrp 2830 before flashing the new rom. After playing with it a while I decided to go back to 4.4.2 using the Nandroid backup.
The Nandroid restore was successful(did a factory wipe before restore). However now I am getting force close non stop(seems like every app after the boot animation). I did a second restore without factory wipe and same problem. How can I get my backup restored properly?
If I install a custom rom(tried Goldfinger v9 among others), they boot fine. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
Sounds like your nandroid is corrupted.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Sounds like your nandroid is corrupted.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I tried again, this time I did advanced wipe and selected the usual system, cache, dalvik etc...and also format internal sd. When I restored the nandroid backup it finally worked properly. Pretty sure the backup is not corrupted.
Hello,
I downgraded my N4 from CM 11 to 10.2.1. The phone boots, optimizes apps but doesn't complete the boot process/starting apps and I'm stuck in a bootloop. Should have done my research before downgrading! What do I do now? I have a nandroid backup from CWM on an external disk but I would prefer not wiping data. Would flashing the 10.2.1 kernel then the 10.2.1 ROM work? How about reflashing [dirty] the CM 11 ROM? Any suggestions or guidance would be appreciated deeply. :crying:
boeder9 said:
Hello,
I downgraded my N4 from CM 11 to 10.2.1. The phone boots, optimizes apps but doesn't complete the boot process/starting apps and I'm stuck in a bootloop. Should have done my research before downgrading! What do I do now? I have a nandroid backup from CWM on an external disk but I would prefer not wiping data. Would flashing the 10.2.1 kernel then the 10.2.1 ROM work? How about reflashing [dirty] the CM 11 ROM? Any suggestions or guidance would be appreciated deeply. :crying:
Click to expand...
Click to collapse
Turn off the phone then boot into recovery and then do a factory reset (aka: wipe) and then flash the ROM that you want to downgrade.
taodan said:
Turn off the phone then boot into recovery and then do a factory reset (aka: wipe) and then flash the ROM that you want to downgrade.
Click to expand...
Click to collapse
Is there no other way but a wipe?
Also, if I may bother you with some questions:
1. Can I do an adb backup in fastboot mode?
2. If I do a CWM backup and then a wipe, will the backup be erased
boeder9 said:
Is there no other way but a wipe?
Also, if I may bother you with some questions:
1. Can I do an adb backup in fastboot mode?
2. If I do a CWM backup and then a wipe, will the backup be erased
Click to expand...
Click to collapse
When you do a factory reset, it won't wipe your nandroid backup. You can do a nandroid backup via adb commands, but it is easier to do it in recovery.
taodan said:
When you do a factory reset, it won't wipe your nandroid backup. You can do a nandroid backup via adb commands, but it is easier to do it in recovery.
Click to expand...
Click to collapse
Thank you so much. When I do restore nandroid, is there any way I can selectively choose what segments of the backup I want. Eg. I do a backup NOW from recovery (CWM), wipe, install ROM and then restore selected files or apps ie I don't want the kernel etc. Is that possible?
I flashed CM11 once more, cleared caches, and booted..works fine..I'll backup what needs to be backed up and will do a wipe tomorrow UNLESS I get used to the hideous esthetics of Kit Kat in the interim.
So I made a backup as I wanted to dirty flash PN again to change kernel. My phone bootlooped after I flashed PN and franco kernel. So i decided to restore my working backup..still boot looping... WHY?! this phone never successfully restores backups in my experience.
gman88667733 said:
So I made a backup as I wanted to dirty flash PN again to change kernel. My phone bootlooped after I flashed PN and franco kernel. So i decided to restore my working backup..still boot looping... WHY?! this phone never successfully restores backups in my experience.
Click to expand...
Click to collapse
Try flashing stock boot image back to device first. Then do a factory wipe and then try the restore.
XxMORPHEOUSxX said:
Try flashing stock boot image back to device first. Then do a factory wipe and then try the restore.
Click to expand...
Click to collapse
How do i do that? Never done that before!! Thanks
gman88667733 said:
How do i do that? Never done that before!! Thanks
Click to expand...
Click to collapse
Look in heisenburgs guide about restoring. The steps to flash the factory images is the same. Just do the boot.img
I think i solved the issue, thank you for the help, I appreciate it a lot
I managed to get my backup restored.. But it gives me a google services force close.. Whyyyy
Wipe your cache and dalvik cache. It should clear up the issue.
Ok, so I have NEVER been able to successfully restore from a backup made using TWRP when the backup was of a Cyanogen based ROM.
I've tried selecting every box/option for the backup thus creating a big arse file and even those don't successfully install during a restore attempt.
The only backup I have the will successfully install is the one I made immediately after installing TWRP of the stock rom.
When I attempt to restore my CM13 rom it usually gets to around 10 to 14 percent complete and then suddenly just reboots and seems to be stuck on the boot loading image forever until my patience runs out and I flash back to stock.
Any ideas guys? I would LOVE to be able to restore one of my CM13 backups.
I'm on Nexus 6p using newest TWRP and had backed up a couple CM13 nightlies.
Currently running CM13 snapshot.
theinvid said:
Ok, so I have NEVER been able to successfully restore from a backup made using TWRP when the backup was of a Cyanogen based ROM.
I've tried selecting every box/option for the backup thus creating a big arse file and even those don't successfully install during a restore attempt.
The only backup I have the will successfully install is the one I made immediately after installing TWRP of the stock rom.
When I attempt to restore my CM13 rom it usually gets to around 10 to 14 percent complete and then suddenly just reboots and seems to be stuck on the boot loading image forever until my patience runs out and I flash back to stock.
Any ideas guys? I would LOVE to be able to restore one of my CM13 backups.
I'm on Nexus 6p using newest TWRP and had backed up a couple CM13 nightlies.
Currently running CM13 snapshot.
Click to expand...
Click to collapse
Have you read my guide?
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
You definitely shouldn't be selecting all options in the backup menu. You only need to select system, data, boot, and vendor. And obviously only restore those.
Heisenberg said:
Have you read my guide?
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
You definitely shouldn't be selecting all options in the backup menu. You only need to select system, data, boot, and vendor. And obviously only restore those.
Click to expand...
Click to collapse
Thanks for the information. Ok I made a backup of only the 4 things listed...before I made the backup I made sure that I had NO security of any kind.
This time the backup got to 100% and then asked me to reboot the system. I was excited...thinking this had actually worked this time...only to find that it stays stuck io the GOOGLE plash screen...it never makes it to the boot animation.
The original stock backup still works...and in looking at that backup it only had 3 things backed up (no vendor).
Suggestions???
At this point a backup has failed once again and I'll have to spend hours getting it back the way I had it.
theinvid said:
Thanks for the information. Ok I made a backup of only the 4 things listed...before I made the backup I made sure that I had NO security of any kind.
This time the backup got to 100% and then asked me to reboot the system. I was excited...thinking this had actually worked this time...only to find that it stays stuck io the GOOGLE plash screen...it never makes it to the boot animation.
The original stock backup still works...and in looking at that backup it only had 3 things backed up (no vendor).
Suggestions???
At this point a backup has failed once again and I'll have to spend hours getting it back the way I had it.
Click to expand...
Click to collapse
You could try restoring the backup without the vendor, but then you'll need to flash the appropriate vendor image to suit the ROM that you're restoring.
tried
Heisenberg said:
You could try restoring the backup without the vendor, but then you'll need to flash the appropriate vendor image to suit the ROM that you're restoring.
Click to expand...
Click to collapse
tried that. it also failed.
Now things seem to be worse. I restore the original stock backup and then from there begin the process again of installing Cyanogenmod 13...only no matter what I do to install it...it gets stuck on the Google unlock screen.
I've tried.
Factory Reset - Install Just CM13 snapshot = fail
Factory Reset - Install CM13 snapshot and Gapps = fail
Factory Reset - Install CM13 snapshot and Gapps and Xposed and Vendor file fix thingy = Fail
a few other combinations all failing the same way.
A phone is worthless to me if I can't run CM13 I "NEED" to customize!!
Please help.
theinvid said:
tried that. it also failed.
Now things seem to be worse. I restore the original stock backup and then from there begin the process again of installing Cyanogenmod 13...only no matter what I do to install it...it gets stuck on the Google unlock screen.
I've tried.
Factory Reset - Install Just CM13 snapshot = fail
Factory Reset - Install CM13 snapshot and Gapps = fail
Factory Reset - Install CM13 snapshot and Gapps and Xposed and Vendor file fix thingy = Fail
a few other combinations all failing the same way.
A phone is worthless to me if I can't run CM13 I "NEED" to customize!!
Please help.
Click to expand...
Click to collapse
Are you flashing the appropriate vendor image for the ROM after you've flashed the ROM? When you say factory reset are you just choosing the factory reset option in TWRP? If so, you should instead go into the advanced wipe section and wipe system, data, cache, and dalvik cache. CM isn't the only ROM out there with customisation, there are other ROMs that have the same or more level of customisation available.
theinvid said:
tried that. it also failed.
Now things seem to be worse. I restore the original stock backup and then from there begin the process again of installing Cyanogenmod 13...only no matter what I do to install it...it gets stuck on the Google unlock screen.
I've tried.
Factory Reset - Install Just CM13 snapshot = fail
Factory Reset - Install CM13 snapshot and Gapps = fail
Factory Reset - Install CM13 snapshot and Gapps and Xposed and Vendor file fix thingy = Fail
a few other combinations all failing the same way.
A phone is worthless to me if I can't run CM13 I "NEED" to customize!!
Please help.
Click to expand...
Click to collapse
also simply tried a Factory Reset followed by reboot and that failed in the same way.
currently it would seem that Screw'd ROM is successfully installing. hmm
what's up with my CM13??
I hope I like this ROM
theinvid said:
currently it would seem that Screw'd ROM is successfully installing. hmm
what's up with my CM13??
I hope I like this ROM
Click to expand...
Click to collapse
I really don't know, there's no reason it shouldn't install. You must be missing something, or perhaps the zip is corrupt, did you check the MD5?