[Q] Stuck in Bootload with any ROM - Nexus 4 Q&A, Help & Troubleshooting

Hi there,
I installed CM a while ago via App + Wininstaller. Yesterday I wanted to install PAC ROM instead to my N4 but I got stuck in bootloop. So I tried many different ROMS - AOKP, CM and even Stock-ROM (4.4.4) but everytime I got stuck in a bootloop.
So far I managed to recover it with the toolkit and I got Stock-ROM again. After that I followed Step-by-Step rooting-Guide, installed CWM/TWRD (I tried both) and again: Bootloops... I checked the MD5s and everything was okay. Once after Toolkit Recovery I got various errors in TWRD when trying to install via ZIP (tried SD-Card and sideload) like "unable to open zip" or "can't write to /tmp/"...
Well I realy like to try PAC ROM instead of CM but at this point the only possibility for a custom rom is CM via the installer-combo (apk/windows).
Any suggestens?

Related

[Q] S4 doing weird behavior when flashing rom

ok, I am using a GT-19505, root with CF-Auto-root, using TWRP recovery
the problem is, when I put a rom in sd card and try to flash it, it will usually says fail (I am sure I get the right version for my device, and I tried many different rom), no matter how many times I re-download the rom, it will says it failed. Even if it success (i.e. omega 7.1 rom), it got stuck in the boot screen forever. I tried to use odin to flash a stock rom, but it also got stuck in boot screen for half an hour before I pull battery.
so far the only successful flashing is a cyanogenmod nightly on 7/14 (I tried other days one, but they all failed to flash). I tried to restore that rom after attempt to flash another rom (omega 7.1), but find out it was factory reset after boot up. I got into the recovery and see that my data partition has 1016154 MB of stuff through the backup option.
I have no idea what had happen, and how to solve it, can someone help?

[Q] Stuck on bootlogo after flashing custom rom

I've encountered a strange problem with my nexus 7. As soon as I install a custom rom (I've tried the latest nightly of Carbon and Slimbean) with a full wipe my device does not boot up. It stucks on the carbon, respective slimbean, bootscreen. Another strange thing is that the latest CM nightly seems to work without any problems.
I even tried to flash a factory image and then reflashed the recovery (TWRP 2.6.3) to try the mentioned custom roms again. Still no luck - CM did work again.
So, do you guys have a solution to this problem? I've used both roms in the past as my daily driver, so I am out of ideas for now...
No suggestion, but I just flashed SlimBean on mine from a full wipe, and I'm having the same issue.
I tried SlimBean again, and it worked. Here's what I did:
1. Updated my bootloader. Mine was still 4.13, and it looks like the most recent version is 4.23. I flashed the img from this post using NRT.
2. Went back to unrooted stock with NRT. (I had to update my bootloader to do this.)
3. Let it boot back into unrooted stock, wept with joy, made a nandroid from NRT.
4. Flashed the SlimBean 1.9 weekly and minimal gapps from NRT's advanced area.
5. Watched in amazement as it boots obediently. Let sit about 10 min, and rebooted.
I'm essentially lazy, so yes I used NRT instead of manually pushing everything with ADB. ADB was plan B. It was briefly plan A, but I got tired of trying to convince the Android SDK that I did in fact have the Java JDK installed.
Mhhhh....
PatrickMac said:
I've encountered a strange problem with my nexus 7. As soon as I install a custom rom (I've tried the latest nightly of Carbon and Slimbean) with a full wipe my device does not boot up. It stucks on the carbon, respective slimbean, bootscreen. Another strange thing is that the latest CM nightly seems to work without any problems.
I even tried to flash a factory image and then reflashed the recovery (TWRP 2.6.3) to try the mentioned custom roms again. Still no luck - CM did work again.
So, do you guys have a solution to this problem? I've used both roms in the past as my daily driver, so I am out of ideas for now...
Click to expand...
Click to collapse
Well I have the same problem with booting Ubuntu touch.... Either it's stuck on white Google Logo or stuck on Cyanogenmod Logo... Have flashed it with TWRP and MultiROM...

TWRP Recovery error when flashing zips fix

Hi guys, so I recently tried to install a ROM (Bliss) and well TWRP gave me an error saying 'error executing updater binary in zip'. I could not install any other ROM via recovery neither. Google was telling me that other people (on different phones) and they had reflashed their primary ROM and then flashed their new ROM straight after but I have no way to flash something via TWRP at all, so I thought there are two fixes: first, try and install stock ROM via Odin, or change my recovery. Luckily, I found CWM Recovery and my life was saved. Yep!

GT-I9505 not allowing any custom ROM after CM13??

Hi,
Yesterday I "blindly" installed the latest CM nightly without noticing that I was installing CM13... After the install, no Google App was working (as expected). When I noticed I had installed CM13, I tried downloading OpenGapps (all from nano to stock for ARM, -not ARM64-), and none of these can be installed, I always get an error (Status Code 1). After a lot of trying, I coundn't even make a wipe (I got an error while formatting data).
After flashing a stock ROM via Odin, the phone worked again, so I tried reinstalling. Now the issue I have is that I can't install any custom ROM to the phone, I have tried flashing CyanogenmodRecovery (for CM12 and CM13) and CWM 6.0.4.7, all of them let me install the latest CM12.2 nightly (26.12), but the phone always hangs on the Cyanogenmod Bootscreen. Wiping is not showing any errors anymore.
Any thoughts? Am I missing something? I am relatively new to the S4, and I got mine already with CM11 on it, and until yesterday I was always able to update without any issues... Am I missing some step?
Small update: I get some errors in the recovery logs: unable to mount /efs. I don't understand why I get this error when a OEM Kitkat works, but well, will keep trying, maybe I find a way to get it working...
1. Use TWRP, CWM is outdated.
2. "Nightly" realeases are testing firmwares. CM13 for GT-i9505 is in early releases too. They have lot of bugs still.
3. - Download the latest stable CM firmware: HERE and copy it to your SDCARD external + Gapps (ARM+ android 5.1 + nano).
- Go to DOWNLOAD MODE and flash TWRP. Boot in TWRP - Select Wipe - Advanced Wipe and wipe all (less usb-otg and external memory).
- Flash CM12.1 firmware and GApps then. Reboot and enjoy.
Use TWRP. Google for s4 twrp. On that page you will also have various install instructions. Afterwards you can flash pretty much any custom rom.
Well, tried exactly these steps, I only skipped gapps for now. I installed following version: cm-12.1-20151117-SNAPSHOT-YOG7DAO1JN-jfltexx. However the phone still hangs while booting... I will let it for a while and see if it boots, but I think it's still stuck... The stock Samsung Kitkat flashes properly from Odin and can be booted... Really strange. Is there anything I can do to see what's going on? I only get the Cyanogenmod Bootscreen, but no adb access...
Well, I am getting some errors: unable to mount /efs... This seems to be the problem, no idea why this is happening... I will keep looking around for a fix... I still don't quite understand why a stock KitKat works...
mschmiedel said:
Hi,
Yesterday I "blindly" installed the latest CM nightly without noticing that I was installing CM13... After the install, no Google App was working (as expected). When I noticed I had installed CM13, I tried downloading OpenGapps (all from nano to stock for ARM, -not ARM64-), and none of these can be installed, I always get an error (Status Code 1). After a lot of trying, I coundn't even make a wipe (I got an error while formatting data).
After flashing a stock ROM via Odin, the phone worked again, so I tried reinstalling. Now the issue I have is that I can't install any custom ROM to the phone, I have tried flashing CyanogenmodRecovery (for CM12 and CM13) and CWM 6.0.4.7, all of them let me install the latest CM12.2 nightly (26.12), but the phone always hangs on the Cyanogenmod Bootscreen. Wiping is not showing any errors anymore.
Any thoughts? Am I missing something? I am relatively new to the S4, and I got mine already with CM11 on it, and until yesterday I was always able to update without any issues... Am I missing some step?
Small update: I get some errors in the recovery logs: unable to mount /efs. I don't understand why I get this error when a OEM Kitkat works, but well, will keep trying, maybe I find a way to get it working...
Click to expand...
Click to collapse
Try dowloading the rom from a thread here on the forum.
You didn't mention what phone model you got so I assume it is a GT-I9505. You can find the official thread in the I9505 original android development section. The maintainer is AntaresOne.
It is the GT-I9505, I now was able to install a stock Kitkat, and it now is allowing me to update via OTA, (first time I got a message that I had a "changed" phone and OTA was disabled). I will let it install this way and see what happens.
Last time I tried with TWRP I was getting the error "unable to mount /efs", but after flashing an ODIN ROM the phone works, I have LTE Data and can place and receive calls, IMEI is there, so I am now confused about what can be wrong.
When this OTA update works, I will try to reflash TWRP via Odin (and not mess around with heimdall anymore), and see if then I can install CM12...
I downloaded the version from the Cyanogenmod site, the latest stable CM12.1 release, so I guess it should be as good as downloading it from an xda thread...
I don't know. It's worth a try.
If you get errors about efs,be careful.The EFS partition contains the most important stuff like your IMEI.There are some backup/restore tools of EFS, you should check them out.Wipe everything,flash cm,then restore EFS backup.

(sovled)Bootloop after installing custom rom in TWRP in Z00LD HELP!!!

i had installed custom rom and recovery(lineage 14.1 & twrp)
it was working fine until the lineage updater downloaded an update and asked me to install it.
but i didnt read the instructions properly and now every time i reboot my Z00ld it gets stuck in a bootloop
how can i get out of the loop.
here are few things ive tried already:
i had a backup after installing the custom rom (the 1st time), the backup didnt work.
so i wiped the whole OS and tried to install the rom again. it completes the installation process without any errors but after completing, it just boots back to the TWRP recovery.
How am i supposed to get out of this loop.
(this happened only after the updater downloaded an update and tried to install it. )
hi guys i need urgent help here please!!
i had installed custom rom and recovery(lineage 14.1 & twrp)
it was working fine until the lineage updater downloaded an update and asked me to install it.
but i didnt read the instructions properly and now every time i reboot my Z00ld it gets stuck in a bootloop
how can i get out of the loop.
here are few things ive tried already:
i had a backup after installing the custom rom (the 1st time), the backup didnt work.
so i wiped the whole OS and tried to install the rom again. it completes the installation process without any errors but after completing, it just boots back to the TWRP recovery.
How am i supposed to get out of this loop.
(this happened only after the updater downloaded an update and tried to install it. )[/QUOTE]
Update : i just had to install stock rom and reinstall the custom rom
hemanthevil said:
hi guys i need urgent help here please!!
i had installed custom rom and recovery(lineage 14.1 & twrp)
Click to expand...
Click to collapse
Lineage seems to be no more available for Z00LD. I'm trying to install any custom roms on my Z00LD (I'm new on rooting and/or installing new roms) but I am not sure about which one is available for that model. Could anyone help me please? Thanks.
Regards.

Categories

Resources