Hey I want to know the exact steps to COMPLETELY wipe my G2 in Clockwork Recovery WITH OUT deleting the new ROM and GAPPS. I've been having horrendous sound search errors and now out of no where the system glitched and a lot of my options are missing. I'm on cyanogenmod CM 11 using 6/13 nightly.
Related
I have been running CM10.2 on my Nexus 7 since I bought it. It has been running fine until recently and now the Google Play Market will not work, browsers are crashing and other apps are crashing all over the place. I am trying to flash another Rom onto it but keep getting errors during the flash about the zips not being able to be opened and such. I am also getting errors trying to use the Unified Nexus Toolkit, because the CM is 4.3.1 and this build is not in the list for the toolkit so I have been trying to use Custom Rom (JB) from the top of the list but it goes into TWRP that it downloaded and used on a temp load but once in TWRP it can't connect with device to do a nandroid backup.
I am running TWRP Multi-rom as the Recovery and I am, trying to flash CyanFox for Grouper. Could I be getting errors because I am running the Multi-rom instead of plain TWRP or CWM? If so, can I flash a new recovery onto the Nexus 7 without wiping my CM10.2 because it is not yet backed up.
If you know of any easier ways to get this done let me know. Any advice is appreciated. Thanks in advanced!!!
Update: I have now went ahead and wiped system, dalvik, cache and factory data reset and have tried flashing both cyanfox and beanstalk harmony. Both are giving me a Status 7 Error. Any ideas why?
Hey I want to know the exact steps to COMPLETELY wipe my G2 in Clockwork Recovery WITH OUT deleting the new ROM and GAPPS. I've been having horrendous sound search errors and now out of no where the system glitched and a lot of my options are missing. I'm on cyanogenmod CM 11 using 6/13 nightly
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.
Hi, new here.
I am having difficulties after rooting and reflashing my A700 to Kitkat.
Started with JB 4.1.1.1.
I was successful at rooting, flashing clockword mod recover 6.0.4.4, installing cm-11-20141112-SNAPSHOT-M12-a700.zip image and the google apps image.
Now, my A700 only boots back into Clockword Mod Recovery.
I have reflashed everything again, following the same instructions.
What am I doing wrong? I have been reading but cannot find anything to help.
I was expecting for it to boot into a new user inteface like I had with the stock rom.
Did you wipe data and factory reset before fashing CM & Gapps ?
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!!!