Database Users

[Q] Trouble With Flashing CM10.2 and Wrong Kernel

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

[Q] Bootloop after downgrading CM 11 to 10.2.1

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.

restore from backup fails

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?

Will flashing a stock firmware with odin reset a custom rom?

I have the batman rom installed on my g95ff now since my stock rom got boot looped when i tried to flash a boot logo that was a size too big.When that happened i flashed the stock firmware with odin aswell as stock recovery and it let me clear my cache/factory reset my phone to fix it.Sadly i lost my bootlogo and boot animation collection i had stored but i had most of my important apps backed up with titanium,so to make up for the lost data i rerooted with twrp,installed the batman rom and restored my apps back.The rom is really neat since i can customize more ui things such as the status bar aswell as my nav bar color which couldnt be done on the stock rom.So now that im familiar with installing roms,would i be able to try other ones simply by reflashing the stock firmware over the batman rom and reinstalling twrp?

So you're asking how you can try other custom ROMs?
You don't need to flash the stock ROM and flash TWRP every time you want to try a new custom ROM. It's MUCH easier than that.
You just need to backup your apps as normal with Titanium Backup, then boot into TWRP. From the Wipe menu, wipe system, data, cache, and dalvik-cache.
Then just flash the new ROM zip file as normal in TWRP, and you're done.

the_scotsman said:
So you're asking how you can try other custom ROMs?
You don't need to flash the stock ROM and flash TWRP every time you want to try a new custom ROM. It's MUCH easier than that.
You just need to backup your apps as normal with Titanium Backup, then boot into TWRP. From the Wipe menu, wipe system, data, cache, and dalvik-cache.
Then just flash the new ROM zip file as normal in TWRP, and you're done.
Click to expand...
Click to collapse
So as long as you wipe your phone you can install custom roms over anough anoughter custom rom.Sounds simple enough then.

iostoandroidconvert said:
So as long as you wipe your phone you can install custom roms over anough anoughter custom rom.Sounds simple enough then.
Click to expand...
Click to collapse
Yep, the "System" partition is where the ROM is installed. When you wipe that, you're essentially wiping the ROM from your phone.

[Question] How to restore TWRP backup of stock 8.0 ROM, after flashing 8.1 ROM

Before going into the subject, I'll say that I have tried to seach this matter in XDA and Google, but nothing showed up.
Okay, so my matter is that I can't restore my backup of stock rom(8.0) after I flash a 8.1 rom. I've backuped with official TWRP "recovery-3.2.1-2-oreo.img".
My procedures are :
back up stock 8.0(system, data, cache, efs) with official TWRP "recovery-3.2.1-2-oreo.img"
flash oreo rom(with wiping internel, data, system, cache) and boot it fine.
restore my stock backup with same TWRP
boot system
The results are :
Goes past boot logo
Boot animation('android one' with colors sliding) shows up
and... just infinite loop of boot animation.
The ROM I used is RR.
I think the main problem is related with encryption.... Just my thought, tho.
So what I'm asking is :
1. If you face the same problem as me?
2. If you aren't and you restore goes fine, please tell me your procedures including ROM used and TWRP used.
3. Whether it is safe to decrypt stock rom?
Thanks in advance!

You don't need to flash stock ROM again. You have a system image backup(system, data, cache, efs), right? Wipe data , system, cache if you are coming from any other ROM. Then reboot to bootloader. Boot into latest TWRP from Fastboot (don't flash). Then go to restore and restore the system image you had backed up. Don't restore efs if you haven't lost your IMEI.

I've done exactly as ypu told, but it doesn't boot...
Did you manage to restore without problem with your method?

Yes I was able to. No problem here.

What TWRP did you use? Also, what ROM have you flashed?

Used the latest TWRP by MohanCM for Oreo. I did it when I was on Lineage os and wanted to go to stock

@guy_infinity Okay, thanks for your answer! Gonna try out later, once more.

Hmmm.... Still didn't boot up.
I thought I had to do everything from the begining, but flashing stock with save userdata option rescued me.
P.S. does anyone know about the error E: recv error on uevent?

try flashing stock rom using mi flash and after flashing restore normally using latest twrp/deadman's without system image voila everything will be back

@arjunbalan1994 Big thanks for your suggestion! Will try that too later

Hi, did you solve your restore problem? I have the same w/ my Redmi Note 5 and stock Miui backup after flashing RR.
Thanks for your help

I was use 8.1 root and twrp recovery. Yesterday fastboot flash may rom and update 2nd may OTA

Don't understand : May rom is Miui rom?
And did you restore your miui rom 8.0 backup ith twpr after the fastboot flash stock?