I'm testing CM 12.1 and came from the official Kitkat rom. I had to flash CWM via fastboot (thread here) in order to install CM 12.1. It worked, but I was stuck with that Cyanogen recovery that comes with CM 12.1. I tried flashing CWM and TWRP, but my phone went into a boot loop. I was forced to reflash 12.1. I also tried installing a newer version of TWRP via XZRecovery, but it got stuck and never installed anything. Here are my problems:
Can't make nandroid backups
Unable to flash Xposed zip for Lollipop 5.1
Is it possible to run CM 12.1 and have a regular recovery like CWM/TWRP?
I do, so yeah definitely possible. But I don't use a "regular" recovery, but the FOTA Recovery version of TWRP. This recovery is installed in a partition of the system which won't get overwritten by the CM Recovery when upgrading. Just search for "FOTA TWRP Z3" via google or XDA and you should be good to go.
Omario-242 said:
I do, so yeah definitely possible. But I don't use a "regular" recovery, but the FOTA Recovery version of TWRP. This recovery is installed in a partition of the system which won't get overwritten by the CM Recovery when upgrading. Just search for "FOTA TWRP Z3" via google or XDA and you should be good to go.
Click to expand...
Click to collapse
I've been on Kitkat for about 4 months and have no idea how I missed that. I installed it and it works perfectly. Thank you!
Related
Hi,
My mom has an Asus TF300T running JB 4.2.1. She tried to root and flash OmniROM by herself and borked it somehow. Unfortunately, she didn't do any backup...
She entered the fastboot screen and there she selected wipe. Then she flashed openrecovery-twrp-2.6.3.0-tf300tg-JB.blob using fastboot.
Now I am trying to help her rescue it.
It's operational, the OS loads up fine and she can use it, install apps etc.
I can get to the fastboot screen and from there to the TWRP no problem, but TWRP can't mount anything besides system.
No dalvik partition, no data partition, not even the SD or external SD.
Naturally, I can't flash another rom...
Tried executing "fix permissions" from the TWRP menu, it didn't help.
Downloaded the latest official Asus blob file TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip and flashed it using fastboot, hoping it will restore the missing partitions but it didn't make any difference.
Also tried CWM - same issue.
Any ideas?
Thanks,
Sefi
chompy18 said:
Hi,
My mom has an Asus TF300T running JB 4.2.1. She tried to root and flash OmniROM by herself and borked it somehow. Unfortunately, she didn't do any backup...
She entered the fastboot screen and there she selected wipe. Then she flashed openrecovery-twrp-2.6.3.0-tf300tg-JB.blob using fastboot.
Now I am trying to help her rescue it.
It's operational, the OS loads up fine and she can use it, install apps etc.
I can get to the fastboot screen and from there to the TWRP no problem, but TWRP can't mount anything besides system.
No dalvik partition, no data partition, not even the SD or external SD.
Naturally, I can't flash another rom...
Tried executing "fix permissions" from the TWRP menu, it didn't help.
Downloaded the latest official Asus blob file TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip and flashed it using fastboot, hoping it will restore the missing partitions but it didn't make any difference.
Also tried CWM - same issue.
Any ideas?
Thanks,
Sefi
Click to expand...
Click to collapse
You are flashing the wrong TWRP. Flash: openrecovery-twrp-2.6.3.0-tf300tg-42.blob
Also If you are installing the KitKat OmniROM, you need TWRP 2.7+
cmendonc2 said:
You are flashing the wrong TWRP. Flash: openrecovery-twrp-2.6.3.0-tf300tg-42.blob
Also If you are installing the KitKat OmniROM, you need TWRP 2.7+
Click to expand...
Click to collapse
Wow! I missed that completely!!
That actually sounds promising.
Yeah, I want to flash KitKat OmniROM, so does the TWRP2.7+ also have a 42 version like the 2.6.30 or just flash TWRP 2.7+ ?
Thanks for your reply!
Sefi
chompy18 said:
Wow! I missed that completely!!
That actually sounds promising.
Yeah, I want to flash KitKat OmniROM, so does the TWRP2.7+ also have a 42 version like the 2.6.30 or just flash TWRP 2.7+ ?
Thanks for your reply!
Sefi
Click to expand...
Click to collapse
Actually, looking in the TWRP site here: http://techerrata.com/browse/twrp2/tf300t, there is no 2.7 version..
So, I'm just making sure, I should flash openrecovery-twrp-2.6.3.0-tf300t-4.2.blob and that should allow TWRP to mount the partitions, right?
What if I want to flash OmniROM KitKat (4.4)? Should I just flash 2.7 over openrecovery-twrp-2.6.3.0-tf300t-4.2.blob?
Thanks,
Sefi
chompy18 said:
Actually, looking in the TWRP site here: http://techerrata.com/browse/twrp2/tf300t, there is no 2.7 version..
So, I'm just making sure, I should flash openrecovery-twrp-2.6.3.0-tf300t-4.2.blob and that should allow TWRP to mount the partitions, right?
What if I want to flash OmniROM KitKat (4.4)? Should I just flash 2.7 over openrecovery-twrp-2.6.3.0-tf300t-4.2.blob?
Thanks,
Sefi
Click to expand...
Click to collapse
This guide has all the links, just flash omnirom instead of cm. There's only a 42 version, so make sure your bootloader is stock V10.6.1.27.1 or V10.6.1.27.5 or V10.6.1.15.3 . upgrade your bootloader if you are on V10.6.1.8.
http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
cmendonc2 said:
This guide has all the links, just flash omnirom instead of cm. There's only a 42 version, so make sure your bootloader is stock V10.6.1.27.1 or V10.6.1.27.5 or V10.6.1.15.3 . upgrade your bootloader if you are on V10.6.1.8.
http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
Click to expand...
Click to collapse
Thanks man! it worked!!!
I had to flash openrecovery-twrp-2.6.3.0-tf300t-4.2 and after it, upgrade to TWRP-TF300T-2_7_0_1 for complete SELinux support, only then could I flash omni-4.4.2-20140416-tf300t-NIGHTLY.
You rock!
Sefi
Today i updated my recovery from twrp 2.6.3 to twrp 2.8 in order to install cm12 RC4..Rom failed to install so i tried to restore the backup i made..it failed too recover as well..i decided to freshly install cm10.2 as i was using it before all this.after all the wiping .the rom installed without any problem but when i rebooted the phone to system its stuck on htc screen..i have tried installing other roms include stock rom but similar result upon booting..RUU is not available for my radio 1.12.82.08...i dont know what to do now please help asap as i dont have any other cellphone
pico_lover said:
Today i updated my recovery from twrp 2.6.3 to twrp 2.8 in order to install cm12 RC4..Rom failed to install so i tried to restore the backup i made..it failed too recover as well..i decided to freshly install cm10.2 as i was using it before all this.after all the wiping .the rom installed without any problem but when i rebooted the phone to system its stuck on htc screen..i have tried installing other roms include stock rom but similar result upon booting..RUU is not available for my radio 1.12.82.08...i dont know what to do now please help asap as i dont have any other cellphone
Click to expand...
Click to collapse
Please change the recovery to flash other roms, the recovery provided in cm12 OP cannot flash other roms... In order to flash other rom please flash other recovery...
pico_lover said:
Today i updated my recovery from twrp 2.6.3 to twrp 2.8 in order to install cm12 RC4..Rom failed to install so i tried to restore the backup i made..it failed too recover as well..i decided to freshly install cm10.2 as i was using it before all this.after all the wiping .the rom installed without any problem but when i rebooted the phone to system its stuck on htc screen..i have tried installing other roms include stock rom but similar result upon booting..RUU is not available for my radio 1.12.82.08...i dont know what to do now please help asap as i dont have any other cellphone
Click to expand...
Click to collapse
use TWRP 2.7.0.0 FOR cm10.2(i'm using it).for CM11 RC3 and CM11RC4 use modified recovery given in respective post.
don't restore backup of one recovery with other
flash superwipe before flashing any ROM.
http://forum.xda-developers.com/showpost.php?p=48859393&postcount=5
So guys, I've been at this for days.
I was originally using AK's kernel, TWRP Recovery and the official 44S ROM, but had issues with logging being disabled, so I fugured I'd go for the cm12 nightlies. I installed the latest AK kernel (102), updated TWRP to 2.8.4.1 and tried to dirty flash the 20150130 nightly, just to find that I'm stuck on the boot screen. I then on found about a firmware update that I installed after I wiped everything clean. Installed cm12 again and I was stuck in the same bootloop. I've even tried cm11 with the intention to OTA to cm12, but that had the same issue. That went through many different ROM's I've tried. I am kind of fed up by now and I would appreciate any input.
Thanks.
So you initially tried to dirty flash CM12 over CM11S? And you did that after flashing the AK kernel? If so you've got one major problem there: never dirty flash when switching ROMs or Android versions, you did both in one hit. And the minor problem: you're meant to flash a kernel after flashing a ROM, if you do it the other way around the stock kernel from the ROM zip just overwrites the custom kernel.
Anyway, I think your best bet is to flash the stock images with fastboot, see section 8 of my guide thread .
Transmitted via Bacon
I can flash any 11S rom, but the problem is installing and booting into cm12. But I think I'll just wait for 12S as it should come up soon. Would be cool if I had access to nightlies though.
Well' you can't win them all.
There's no reason why you shouldn't be able to flash the nightlies? Did you update your firmware appropriately before flashing CM12?
Transmitted via Bacon
@timmaaa I am also wondering why does he face bootloop issues every time. If there is no essential change in the latest OTA update (like updated bootloader) maybe his recovery doesn't wipe /system properly.
Hey, @BigWaxx, did you manually format /system in TWRP before flashing CM12? If yes, maybe give a try with PhilZ recovery.
tetakpatalked from Nexus 7 flo
tetakpatak said:
@timmaaa I am also wondering why does he face bootloop issues every time. If there is no essential change in the latest OTA update (like updated bootloader) maybe his recovery doesn't wipe /system properly.
Hey, @BigWaxx, did you manually format /system in TWRP before flashing CM12? If yes, maybe give a try with PhilZ recovery.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
It's definitely possible, the firmware is the most likely culprit at this stage though.
Transmitted via Bacon
I have updated the firmware properly before that. Also no other custom ROM runs - not only cm12. I've tried cm11, OmniROM, TGM, BlissPop and temarek.
I have also tried CWM, but not PhilZ. I made sure to format everything - even internal storage. I've tried both F2FS and EXT4 as filesystems for /system.
I will try PhilZ though.
Cheers.
Hello!
I bought a Moto G falcon 2 mounts ago. Running CM12 everything was good.
I flashed a cm12.1, then my falcon started to crash randomly (mostly because i didn't flash the proper Gapps). So I wanted to revert back to KitKat to make a proper flash since the beginning, wich was ofc a bad idea. So I flashed the 4.4.4 stock ROM and now am in soft brick. I'm stuck at boot logo (The boot loader unlocked one). I tried to flash a stock 5.1 ROM (GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip) without any success.
My bootloader is updated to 4118, I can boot in recovery/bootloader.
Any ideas how to boot again? Thank you!
I_HAVE_NO_IDEA said:
Hello!
I bought a Moto G falcon 2 mounts ago. Running CM12 everything was good.
I flashed a cm12.1, then my falcon started to crash randomly (mostly because i didn't flash the proper Gapps). So I wanted to revert back to KitKat to make a proper flash since the beginning, wich was ofc a bad idea. So I flashed the 4.4.4 stock ROM and now am in soft brick. I'm stuck at boot logo (The boot loader unlocked one). I tried to flash a stock 5.1 ROM (GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip) without any success.
My bootloader is updated to 4118, I can boot in recovery/bootloader.
Any ideas how to boot again? Thank you!
Click to expand...
Click to collapse
Well if you can boot into the recovery and if its custom (TWRP) wipe all the data on your phone. Second I would try to flash a ROM onto your device such as Resurrection Remix and see if that works. Update on your progress.
Thank you for your answer.
I tried to wipe data/factory reset, but twrp throws some error messages.
Unable to mount /data, /cache, /system and all derivatives.
I tried to flash a ROM through twrp but I think I can't because of that partition mess. I can't adb push to /sdcard, or sideload (seems to require /data).
I think that my issue is that I flashed the 4.4.4 gpt.bin, and I shouldn't have. If I'm right, is there any way to recover from this?
I_HAVE_NO_IDEA said:
Thank you for your answer.
I tried to wipe data/factory reset, but twrp throws some error messages.
Unable to mount /data, /cache, /system and all derivatives.
I tried to flash a ROM through twrp but I think I can't because of that partition mess. I can't adb push to /sdcard, or sideload (seems to require /data).
I think that my issue is that I flashed the 4.4.4 gpt.bin, and I shouldn't have. If I'm right, is there any way to recover from this?
Click to expand...
Click to collapse
I crashed my S3 using camera on old cm12.1 and got into loop with services stopped. Try and D/L the new 4 22 and Slim ggaps 20150422 wipe chache and devik and reinstall cm and ggaps get it working this is what I did but I haven't read any info except to find a file for Odin but don't think you can use Odin. It be nice to have stable way to downgrade. The flash will hopefully get your phone working.
vtails said:
I crashed my S3 using camera on old cm12.1 and got into loop with services stopped. Try and D/L the new 4 22 and Slim ggaps 20150422 wipe chache and devik and reinstall cm and ggaps get it working this is what I did but I haven't read any info except to find a file for Odin but don't think you can use Odin. It be nice to have stable way to downgrade. The flash will hopefully get your phone working.
Click to expand...
Click to collapse
Thank you. But I can't flash a cm12.1 atm (see my post below). I can only flash through fastboot. I'm not sure I properly understood you, what do you call 4 22 ?
FYI I managed to boot again. Here's what I did:
Flash a 5.x ROM, try to boot to let the system make partitions and stuff (I think)
Boot in TWRP and saw that system and cache were not mountable, so I wiped them.
Flash a cm12.1 (+ Gapps) and here we go!
Thank you for your help!
Please refer this development thread https://forum.xda-developers.com/xperia-l/orig-development/mod-multirom-xperia-l-t3397663 . Been trying long to check out multirom and everytime I end up with a Bricked device and have to do a flash..
SO the problem is I tried flashing multirom with stock and doesn't seem to work. That's when I got to know that it doesn't work with stock ROM . Hence I tried with CM 12.1. Used dd Install Method to flash latest TWRP 3.0.2 on CM 12.1 and installed the multirom-20160614-v33x-UNOFFICIAL-taoshan.zip. It goes into Bootloop and stuck at sony logo everytime i try. Also I tried with LineageOS 14.1. Help Appreciated.:angel:
darklord717 said:
Please refer this development thread https://forum.xda-developers.com/xperia-l/orig-development/mod-multirom-xperia-l-t3397663 . Been trying long to check out multirom and everytime I end up with a Bricked device and have to do a flash..
SO the problem is I tried flashing multirom with stock and doesn't seem to work. That's when I got to know that it doesn't work with stock ROM . Hence I tried with CM 12.1. Used dd Install Method to flash latest TWRP 3.0.2 on CM 12.1 and installed the multirom-20160614-v33x-UNOFFICIAL-taoshan.zip. It goes into Bootloop and stuck at sony logo everytime i try. Also I tried with LineageOS 14.1. Help Appreciated.:angel:
Click to expand...
Click to collapse
It's not working with latest MM versions and never with android N! Because it's development is not continued in Xperia L (unfortunately ). But I think it's working with Resurrection Remix MM with being installed as primary ROM, and some older versions like Lollipop as secondary ROM ( lol I'm using this method now with RRemix MM & Stryflex MM v1.0 ! )
After installing first ROM using some other TWRP recoveries, go to recovery again and install multiROM recovery, then reboot to recovery again and install v33x zip file. Now go to main menu in recovery and select advanced option on top and install the second ROM in external sd card!
Now both of ROMs should work without any problem!
Partially solved now
Kungfu73 said:
It's not working with latest MM versions and never with android N! Because it's development is not continued in Xperia L (unfortunately ). But I think it's working with Resurrection Remix MM with being installed as primary ROM, and some older versions like Lollipop as secondary ROM ( lol I'm using this method now with RRemix MM & Stryflex MM v1.0 ! )
After installing first ROM using some other TWRP recoveries, go to recovery again and install multiROM recovery, then reboot to recovery again and install v33x zip file. Now go to main menu in recovery and select advanced option on top and install the second ROM in external sd card!
Now both of ROMs should work without any problem!
Click to expand...
Click to collapse
First of all Thanks man for taking up time for responding
I did a full wipe and then put up lineageOS 14.1 which comes equipped with a TWRP 3.0.2 recovery(or the one that I flashed through adb lol) and tried it again this time being more careful.. flashed the multirom recovery and then rebooted.. FINALLY got it this time flashed the MULTIROM too.. VOILA! done!
Now I have a different issue though... When I add a new ROM (CM 12.1) the lollipop one to the sd card I go through a new phase of errors. It says the nightly can't be used for flashing other than multirom now and ended with some errors and failed ! P.S The nightly is nt corrupted cuz i used it few days back and it was working just fine..
darklord717 said:
First of all Thanks man for taking up time for responding
I did a full wipe and then put up lineageOS 14.1 which comes equipped with a TWRP 3.0.2 recovery(or the one that I flashed through adb lol) and tried it again this time being more careful.. flashed the multirom recovery and then rebooted.. FINALLY got it this time flashed the MULTIROM too.. VOILA! done!
Now I have a different issue though... When I add a new ROM (CM 12.1) the lollipop one to the sd card I go through a new phase of errors. It says the nightly can't be used for flashing other than multirom now and ended with some errors and failed ! P.S The nightly is nt corrupted cuz i used it few days back and it was working just fine..
Click to expand...
Click to collapse
Good to hear that! Ok, I think there is two ways to solve this issue.
First, you may simply test and use another ROM for secondary!
Second way is longer and you should have an external sd card with more space (like 8GB and up).
First, full backup this ROM, and then clean flash 12.1 ROM to be primary.
Next, backup this ROM too, and then recover the first backup and go to recovery again, and now, go to advanced tab and choose "add a rom" and select install from backups, and use that second backup to be installed as secondary ROM. It should work now!
And remember that: the chance of booting android N after installing second ROM, is very low. It may bootloop! because as I said, development of multiROM for our phone is not continued.
Kungfu73 said:
Good to hear that! Ok, I think there is two ways to solve this issue.
First, you may simply test and use another ROM for secondary!
Second way is longer and you should have an external sd card with more space (like 8GB and up).
First, full backup this ROM, and then clean flash 12.1 ROM to be primary.
Next, backup this ROM too, and then recover the first backup and go to recovery again, and now, go to advanced tab and choose "add a rom" and select install from backups, and use that second backup to be installed as secondary ROM. It should work now!
And remember that: the chance of booting android N after installing second ROM, is very low. It may bootloop! because as I said, development of multiROM for our phone is not continued.
Click to expand...
Click to collapse
Shall try that and get back to you.. thanks mate!!!