I had D80120a.. I downgraded to D80110c.. Then rooted phone.. Then installed twrp with dd.. Every Rom and gapps I tried flashing fails..
The thread said to install a certain rom before flashing any other rom. which I think it's just stock 4.4.2 .. File name.. D801-4.4.2-recovery.zip
So now I'm rooted, twrp, and this stock 4.4.2 rom..
I tried installing cm stable, failed, liquid smooth, failed, cmb? Failed, and heatshiver.. Heatshiver installed.. Flashed PA gapps failed, cm gapps, failed, some other kk gapps, failed.. Cmb gapps installed.. Booted.. And got nothing, black screen, no launcher, just soft buttons and a blank notification menu, so flashed this D801_4.4.2_recovery.zip and that's where I'm at now..
Also only twrp 2.6.3.2 I think it was would flash.. No other versions
urhaxable said:
I had D80120a.. I downgraded to D80110c.. Then rooted phone.. Then installed twrp with dd.. Every Rom and gapps I tried flashing fails..
The thread said to install a certain rom before flashing any other rom. which I think it's just stock 4.4.2 .. File name.. D801-4.4.2-recovery.zip
So now I'm rooted, twrp, and this stock 4.4.2 rom..
I tried installing cm stable, failed, liquid smooth, failed, cmb? Failed, and heatshiver.. Heatshiver installed.. Flashed PA gapps failed, cm gapps, failed, some other kk gapps, failed.. Cmb gapps installed.. Booted.. And got nothing, black screen, no launcher, just soft buttons and a blank notification menu, so flashed this D801_4.4.2_recovery.zip and that's where I'm at now..
Also only twrp 2.6.3.2 I think it was would flash.. No other versions
Click to expand...
Click to collapse
did you use autorec?
No, just downgraded, rooted with ioroot, then used dd to write twrp to recovery partition..
I just installed autorec and now I have twrp 2.7.0.0 and liquid smooth and banks gapps successfully installed.. So what was bad? Bootloader? Partitions? I thought that installing that first rom D801_4.4.2_recovery.zip was supposed to fix partitions and such.
Oh well, it works now, thanks! I didn't think I need autorec since I installed twrp manually using dd..
Maybe I should post on some of those tutorials as they are missing steps..
Although I don't think anyone will be using them now that you can root and install recovery right from D80120a now.
Related
Hey guys, I've seen this issue before yet I've tried everything in a few threads now but have no idea what is happening,I have tried using search function yet no solution has fixed my problem.
Problem:
When installing custom ROMs the installation goes fine. I put the ROM on the sdcard, follow instructions for flashing e.g wipe data/cache etc and then flash GAPPS. However I get stuck on the boot logo of every ROM. I've tried both TWRP and CWM recoveries, both with no luck. Also tried not flashing GAPPS and just trying to flash the ROM to no avail.
Current state of phone:
The phone is currently running stock firmware via downloading factory image and flashing in boot-loader : stock boot, recovery, system image etc
The phone works fine when rooted on stock firmware. E.g no custom rom yet rooted.
Could really do with some help guys, any ideas?
muqy said:
Hey guys, I've seen this issue before yet I've tried everything in a few threads now but have no idea what is happening,I have tried using search function yet no solution has fixed my problem.
Problem:
When installing custom ROMs the installation goes fine. I put the ROM on the sdcard, follow instructions for flashing e.g wipe data/cache etc and then flash GAPPS. However I get stuck on the boot logo of every ROM. I've tried both TWRP and CWM recoveries, both with no luck. Also tried not flashing GAPPS and just trying to flash the ROM to no avail.
Current state of phone:
The phone is currently running stock firmware via downloading factory image and flashing in boot-loader : stock boot, recovery, system image etc
The phone works fine when rooted on stock firmware. E.g no custom rom yet rooted.
Could really do with some help guys, any ideas?
Click to expand...
Click to collapse
same problem simple solution another user informed me of.
simply donwgrade to 4.3 JB stock rom through fastboot. Then you are able to flash a custm rom from the 4.3 stock rom.
Its crazy i have to do this but it worked for me, now im running the xperience rom which is a rom based on 4.4.2 kk.
the 4.3 android stock firmwares are linked somewhere in the FAQ's as well as the guide to ffastboot lash it.
peace.
chairsz said:
same problem simple solution another user informed me of.
simply donwgrade to 4.3 JB stock rom through fastboot. Then you are able to flash a custm rom from the 4.3 stock rom.
Its crazy i have to do this but it worked for me, now im running the xperience rom which is a rom based on 4.4.2 kk.
the 4.3 android stock firmwares are linked somewhere in the FAQ's as well as the guide to ffastboot lash it.
peace.
Click to expand...
Click to collapse
Hey man, worked a charm thanks!
For users who may have the same problem:
After flashing 4.3 onto the device it did NOT boot.
- However I then went into the bootloader flashed custom recovery, I used cwm.
- Then I went into recovery, used adb to push the rom and gapps onto sdcard
- Full wipe and then installed rom. Then installed gapps
Working fine.
Cheers chairsz :good::good:
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
I had the latest version of CM11 on my Opo 64 GB, was also using Multirom and Miui 4.10.24.
Tried to install the 4.10.31 version, but i did it wrong (i did not go into TWRP, then Multirom, add zip and install, but i just selected install rom and flashed the 4.10.31 zip file).
Now, the main CM11 OS is lost, i cannot boot into it, and i cannot also boot into MIUI.
So, how can i get my CM11 back?
I tried flashing the official version but it gives me error while trying to install it through TWRP.
Also if i reboot the phone and try to choose the MIUI it says
"error, kexec-hardboot support is required to boot this rom.
install kernel with kexec-hardboot support to your internal rom.
Any help would be greatly appreciated!
kidstretch said:
I had the latest version of CM11 on my Opo 64 GB, was also using Multirom and Miui 4.10.24.
Tried to install the 4.10.31 version, but i did it wrong (i did not go into TWRP, then Multirom, add zip and install, but i just selected install rom and flashed the 4.10.31 zip file).
Now, the main CM11 OS is lost, i cannot boot into it, and i cannot also boot into MIUI.
So, how can i get my CM11 back?
I tried flashing the official version but it gives me error while trying to install it through TWRP.
Also if i reboot the phone and try to choose the MIUI it says
"error, kexec-hardboot support is required to boot this rom.
install kernel with kexec-hardboot support to your internal rom.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
I'm probably not understanding, but can you boot from off , into recovery then > TWRP?
JeffDC said:
I'm probably not understanding, but can you boot from off , into recovery then > TWRP?
Click to expand...
Click to collapse
Yes I can, managed to install MIUI only, latest version.
I also installed Multirom again (on MIUI) and it downloaded cm11s kernel).
Ok managed to go back to my old miui os, now I have 2 miui os and no cm11, also downloaded the Franco kernel 30. How can i check if the cm11 that i had before is still there, if not how can i install it again without screwing my already working miui?
update:
After some tests, this is what's happening.
I believe I have no CM11S on my phone, that is gone!
I have the MIUI V5 running, but when i flash the franco kernel, the phone is stuck on boot (1+1 logo), i have to flash the kernel_kexec_bacon_cm11s to make it boot in MIUI (working).
So, now i have a working rom that works through Mutlirom and I cannot flash a working CM11S rom on the phone.
Any help would be great guys!
So I've had a chinese version of the opo since last summer, first thing I did was root it and unlock bootloader etc. I've been running a rom for quite a while (really embarrassing, but can't remember what rom). And I tried to flash a new one, but I got greeted with the message "error executing updater binary in zip". I've tried most things, updating firmware, updating to latest recovery, wiped everything, then trying to install, then rebooting and trying again, but no luck. Running CM12 nightlies work, so does oxygenos, however they're not that good tbh. Would love any help
Roxkyp said:
So I've had a chinese version of the opo since last summer, first thing I did was root it and unlock bootloader etc. I've been running a rom for quite a while (really embarrassing, but can't remember what rom). And I tried to flash a new one, but I got greeted with the message "error executing updater binary in zip". I've tried most things, updating firmware, updating to latest recovery, wiped everything, then trying to install, then rebooting and trying again, but no luck. Running CM12 nightlies work, so does oxygenos, however they're not that good tbh. Would love any help
Click to expand...
Click to collapse
Flash latest CM12.1 nightly first
And then flash your desired ROM
Or else
Flash factory images of latest version Cyanogen OS 12.1 and then flash TWRP and then your desired ROM
Guide to flash ROMs and factory images >> http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Mr hOaX said:
Flash latest CM12.1 nightly first
And then flash your desired ROM
Or else
Flash factory images of latest version Cyanogen OS 12.1 and then flash TWRP and then your desired ROM
Guide to flash ROMs and factory images >> http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Click to expand...
Click to collapse
Unfortunately these methods did not work for me, I can get on 12.1, but when I want to flash something else (resurection rom in this case) I get the error.
Its a firmware issue you need the correct firmware
I wanted to install cutom rom in my Mi4i working on MIUI 8, so I installed TWRP from toolkit , which also installed SuperSU.But I don't know if my bootloader was unlocked or not?
I saw in a youtube video to flash MIUI 6 first to install Custom rom or you might endup in BOOTLOOP.
In TWRP I wiped Dalvik,Data,Cache,System.
Went to INSTALL, tried installing MIUI6 but that package failed to install. Giving error unable to mount.
I tried custom rom crDroid and it installed but when I restarted I WAS STUCK IN BOOTLOOP.
After a heartattack I finally flashed MIUI8 with MiFLASHER using fastboot image of MIUI 8.
SO, I want to ask IS THERE A WAY TO INSTALL CUSTOM ROM ,IF I AM ON MIUI 8????
And that bootloop was caused beacuse I didn't unlock bootloader when I installed crDroid???
Thanx in advance. Please somebody help???
singharpit800 said:
I wanted to install cutom rom in my Mi4i working on MIUI 8, so I installed TWRP from toolkit , which also installed SuperSU.But I don't know if my bootloader was unlocked or not?
I saw in a youtube video to flash MIUI 6 first to install Custom rom or you might endup in BOOTLOOP.
In TWRP I wiped Dalvik,Data,Cache,System.
Went to INSTALL, tried installing MIUI6 but that package failed to install. Giving error unable to mount.
I tried custom rom crDroid and it installed but when I restarted I WAS STUCK IN BOOTLOOP.
After a heartattack I finally flashed MIUI8 with MiFLASHER using fastboot image of MIUI 8.
SO, I want to ask IS THERE A WAY TO INSTALL CUSTOM ROM ,IF I AM ON MIUI 8????
And that bootloop was caused beacuse I didn't unlock bootloader when I installed crDroid???
Thanx in advance. Please somebody help???
Click to expand...
Click to collapse
I would suggest you to install Resurrection Remix as it is based on miui8 firmware.
You were stuck in bootloop because crDroid was based on miui6 firmware and probably your installation of the same was failed ( Like you're saying )
Since you get "Heart Attack", Prefer clean install.
Wipe system, data, cache, dalvik cache.
Flash Rom, gapps,
Reboot to system.
Note:- To install custom ROMs based on miui6 firmware, first of all, flash the provided firmware in the thread instead of flashing the whole miui6.
Ask further if it doesn't work.
Hit thanks if helped.