Hi. I'm new to this whole rooting and flashing stuff. Anyways, I got a YU Yuphoria and it's already rooted. But recently my CM default File Manager has stopped responding. So I uninstalled it via Titanium Backup ( Pardon me if I'm being noob Lol ) and flashed the CM File manger via custom recovery. But still it was not opening up. So I tried to install it via F-Droid and that too failed to open up (Which was an old version of CM File manager). I really like the File Manager. So despite all these failures I'm determined to have it back working. So I was wondering if flashing the latest CM nightly would do the trick. Could someone help me out on this?
Related
Hi, I've rooted and flashed ROMs on previous devices but this has me stumped.
I installed CM 10.1.3 using a guide from unlockr
However I forgot to install Gapps (was blindly following the guide)
No bother, I downloaded Gapps for CM 10.1 from the official Cyanogen wiki page
However I'm getting constant google services force closes and Play store cannot update anything without an error.
I managed to install ROM manager via SD card, however it is constantly force closing, so I can't boot into recovery or flash a new ROM.
Does anyone know how I can start fresh, or flash a new ROM & Gapps, bearing mind ROM Manager will not work (reinstalled and cleared cache/data to no avail).
Some important info
- Galaxy Tab 2 10.1 (p5110)
- Rooted
- CWM recovery
- CM 10.1.3
P.S. I thought I could reinstall a ROM through ODIN, however I don't know how to install Cyanogen mod though ODIN as it's a zip file.
Any advice on this would be great, and I can provide more info. if needed.
Are you sure they're for CM 10.1? It sounds like you've got the wrong gapps version.
-Sent from my Samsung Galaxy Tab 2 7.0
Hi,
I've been using the same old rom for a year or so (slim rom or sth). Lately i tried updating it to something else, but I get this when I start installing rom in TWRP: Error executing updater binary in zip (...). It works the same way every rom i tried.
UPDATE:
Kinda looks like i can install slim rom 4.3 (so i suppose i could install any 4.3), but none of 4.4 works.
Best regards.
Tried to flash CWM recovery from rommanager app, but it said "Failed to flash recovery...".
please help
Download latest recovery from http://forum.xda-developers.com/nexus-s/development/crespo-philz-touch-t2284670
Then try to flash the ROM. It seems your recovery is very old.
gunlok said:
Hi,
I've been using the same old rom for a year or so (slim rom or sth). Lately i tried updating it to something else, but I get this when I start installing rom in TWRP: Error executing updater binary in zip (...). It works the same way every rom i tried.
UPDATE:
Kinda looks like i can install slim rom 4.3 (so i suppose i could install any 4.3), but none of 4.4 works.
Best regards.
Tried to flash CWM recovery from rommanager app, but it said "Failed to flash recovery...".
please help
Click to expand...
Click to collapse
gunlok said:
Hi,
I've been using the same old rom for a year or so (slim rom or sth). Lately i tried updating it to something else, but I get this when I start installing rom in TWRP: Error executing updater binary in zip (...). It works the same way every rom i tried.
UPDATE:
Kinda looks like i can install slim rom 4.3 (so i suppose i could install any 4.3), but none of 4.4 works.
Best regards.
Tried to flash CWM recovery from rommanager app, but it said "Failed to flash recovery...".
please help
Click to expand...
Click to collapse
@smit.sanghavi is right.
You need KitKat compatible Recovery. Update your recovery and then try to flash the ROM.
K guys, wanted to try all you said, but there's another problem.
I discovered my nexus isn't rooted. Bootloader unlocked, but any root checker says its unrooted (of course it was before...). So I'm trying to reroot it but when im connecting my phone via usb in bootloader windows 7 doesn't recognize the device. When the phone is connected in recovery or in normal usb debugging mode it recognizes it as adb android, looks good to me. I go back to booloader and i get "Windows has stopped this device because it has reported problems. (Code 43)" in Devices.
Installed the drivers on few different ways.
So.... what now ?
UPDATE: solved
Hey guys, I Know this phone is old but please help me
I was using official 2.3.5 ROM and it was getting old so I thought to root and install an ICS Rom so i rooted and installed MIUi ICS ROM (http://forum.xda-developers.com/showthread.php?t=2029969) it was really nice and i thought to install Aurora Rom(http://forum.xda-developers.com/showthread.php?t=1492957) and it was Awsome! so i got into installing new ROMs and i was installing new ROMs almost every week and one day i saw CM 11 KitKat ROM for Huawei U8800 and I wanted to install it but before that i had to install Ble-Part Partition (http://forum.xda-developers.com/showthread.php?t=2615712) i flashed it succesfully and i installed the 2.2 version after that i flashed CWM 6.0.4.6 and i installed KitKat CM11 without any problems!
After some time using it for some time i thought to go back to Aurora as CM 11 was a little buggy and Aurora was the most stable ROM but as i was installing Aurora, i accidently formatted Boot instead of formatting System and without realizing it i flashe Aurora which flashed very quickly rather unexpectedely, and when i rebooted a blue screen appeared. I (surprised) installed official 2.3.5 ROM via dload and when it had installed the phone went into bootloop and i performed a factory data reset and it booted normally. But when i rebooted the phone again again it went to bootloop again. So i installed official 2.2 ROM and it installed succesfully and it never bootlooped in 2.2 ROM. But i wanted to install Aurora but it needs a .35 kernel and whenever i install 2.3.5 it keeps on bootlooping and i cant root it, though i can root 2.2 ROM easily and install .32 ROMs but they are quite old and I want to install ICS, JellyBean or KitKat Rom, which unfortunately i cant
Just in case you would be wondering i have tried many methods to go back to stock partition and none of them works and i have 1.8 GB storage! I have read that distorted partition can cause bootloops on 2.3.5 ROM so if anyone can help me to fix this problem, ill be very grateful as this is a very important phone to me!
And if you have any questions please ask!
So i recently got a g2 from tmobile store. I went ahead and updated to lollipop, rooted and installed newest twrp via autorec. This is my first LG device but i figured out yhe different bootstacks to go along with certain roms. I am able to install roms, back them up and restore just fine with full knowledge of proper methods ( wiping and such) except cyanogenmod. Ive tried cm10,11, and 12. Every try i get an error similar to Error "executing update binary in zip failed". I dont know what im doing wrong. I tried going back to an older twrp but couldn't get it to install either. Help
I've used CM12.1 based ROMs for a while now, and with my talent have managed to brick my bacon (oneplus one global 64GB), and unbrick it (using this guide)
I've restored it to stock with no problem using this tool.
my problem begins when i try to update to any LP ROM - flashing such ROMs' zip files in TWRP returned "E: error executing updater binary in zip". i found two solutions to this error:
1. first one is described in this thread. i ditched this method after it got me stuck in bootloop every time after flashing a ROM
2. second one (probably the way it should be done) is to update device firmware like described in this oneplus forums thread. flashing this zip indeed allowed me to successfully install my ROM but with one big problem - the SIM card is detected for a few seconds (even then the device wont find any networks) and then drops to "no SIM card detected - emergency calls only" then it gets detected again and so on...
I've also tried flashing some different modems like described here but it didn't change anything
have anyone encountered any network related problem after upgrading to a CM12.1 based ROM or have any idea how to solve my problem (mobile network connections won't function after upgrading to cm12 firmware)?
help would be very appreciated!
edit: if it helps, i also found that OTA updating to the latest build XNPH44S also breaks the phone's ability to connect to a mobile network
Get the oneplus one build which was released as a fix to ghost touch.. It is nothing but oxygenOS!! Backup ur data and follow the instructions and flash the oxygen rom then wait for the first boot after first boot just update ur recovery to latest twrp and get the bacon firmware update zip file from any of the major rom threads like blisspop or exodus then flash that then flash the latest cm12.1 nightly and AK kernel(optional) then boot it up!!!
Transmitted via Bacon
yashshan said:
Get the oneplus one build which was released as a fix to ghost touch.. It is nothing but oxygenOS!! Backup ur data and follow the instructions and flash the oxygen rom then wait for the first boot after first boot just update ur recovery to latest twrp and get the bacon firmware update zip file from any of the major rom threads like blisspop or exodus then flash that then flash the latest cm12.1 nightly and AK kernel(optional) then boot it up!!!
Transmitted via Bacon
Click to expand...
Click to collapse
1. TWRP must be installed before installing OxygenOS as it comes as a flashable zip and not an OTA/Cyanodgen update...
2. installing OxygenOS was no problem without the firmware, however after it booted i noticed it broke my mobile communications in a very similar way, so no luck with that one.
3.even after installing oxygen the firmware update is required to install anything like a CM nightly or a CM based LP ROM, and my problem was that this firmware upgrade broke my network connection, so i don't see how that could help me in any way
3.1 after flashing OxygenOS not even the firmware update would allow me to install a different ROM...
4. i linked the forum thread my firmware update came from (also found a similar suggestion in a YouTube video) and couldn't find any reference to it in any of the main ROMs' threads like you suggested, they all just say to install TWRP wipe everything and flash their zip (some say to flash a nightly before)
any other ideas? I'm starting to get desperate around my suddenly not-so-functional bacon :crying:
!!SOLVED!!
steps:
1. flash the latest CM12S fastboot image
2 .delete line 2 "aassert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1");" from the updater-script file in the custom ROM's ZIP installation file
3. flash the "hacked" zip file with no problem
4. enjoy your custom ROM installed bacon, WITH your mobile connection.
thanks for the help anyway!