Hey all,
I have a Dev edition and I recently updated it to the NC2 leak and used the lean kernel. It was working ok, but I had at least one lockup/reboot a day. So today I decided I wanted to try the new 4.4-based Hyperdrive ROM.
I replaced Philz recovery with TWRP 2.7 and then booted into it. I wiped the device, and then flashed the first of the two files that are a part of Hashcode's kernel (as I saw it seems to be more stable). I then flashed the Hyperdrive ROM, and the second file (fix) from Hashcode. I then tried to boot.
It gets stuck on the Note 3 Splash screen with the custom unlocked padlock icon, but will not load up. It isn't in a bootloop, I just sits there.
I went back into recovery, wiped, and tried again. Nothing. Same problem.
What am I missing? How can I fix this?
Thanks!
-Rob
Related
I previously had a different rom installed just fine (Modaco). I wanted to install Cyanogenmod, so I followed instructions, wipe, install rom and gapps, reboot. It was stuck on the cyanogenmod animation forever. I also tried a different rom (4.2.1 Linario) and same problem.
I was forced to go back to stock. Went back to factory stock, rooted once again, installed CWM, and tried installing rom again and it just wont go past the boot animation.
Ive attached a logcat, hopefully someone could tell me what the problem is.
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...
I just got a N7. It came with stock 4.4.2 but I unlocked and flashed a few 4.4 ROMs to try out (Liquid, CM, OMNI). Anyway, I figured I might want to try a 4.3 ROM so I flashed one. It didn't boot. Went back and installed the 4.4 ROM and all was good. I thought maybe I needed to flash a 4.3 factory image first, so I did. I fastbooted (verb) everything in the JWR66Y directory and OMG it booted. Great, time to flash a ROM, right? Nope. Flashed CWM touch 6.0.4.3 again and it booted using the stock ROM/kernel but after I flashed a custom ROM, it just sits at the boot screen. The obvious answer here would be to have patience and wait. I have waited for 35+ minutes at the bootanimation screen with no sign of booting. This is on any 4.3 ROM I try. However, it will boot right up if I flash the stock JWR66Y system and boot images. What do you think, kernel related or am I missing something more obvious?
My GS4 is pissing me off for the last two days. I'm on the task650 4.3 rom. I rebooted and it's stuck at the Samsung Custom screen. I tried booting into TWRP recovery and cleared cache/dalvik/fixed permissions, and rebooted. Still stuck at that screen. Tried reinstalling the ROM.zip file. Nope. Now I can't even get into TWRP. Its stuck at the blue screen.
So basically I'm stuck at either the blue team win screen or the black samsung custom screen. What am I doing wrong?
is there any 4.3 stock TW rooted rom out there I can flash? I'm fed up with all this
Also, what's the best way to switch recoveries from TWRP to CWM? Can I just odin the file off their website for the AT&T variant? No?
Hi!
Last night I installed bootloader on my A500. And noticed problems right away.
Problem #1: I can't boot into recovery using RECOVERY menu in bootloader. I flashed CWM as secondary kernel and can boot that way. But I think there is something wrong. Also HOME button didn't work.
Problem #2. Right after installing bootloader I was able to boot into my system (ICS). Then i installed rooted deodex stock ROM. This time my tablet kept crashing launcher.
Problem #3. I installed Omni unofficial light ROM, gapps and SU. Creared cache etc. Tried to boot - tablet gets stuck on boit animation - ANDROID sign with running lights.
Does somebody have an idea what is wrong?
Any help appreciated!