I've been trying various roms for a while now and tried out Cookies&Cream 1.3.0 as the latest flavor.
Problem is now I can't reboot, power down, or boot into recovery at all. It also goes into sleep of death and drains the battery in under 8 hours. I've tried WUG's toolkit, nexus 7 toolkit, flashing TWRP or CWM, and nothing works. it's gets stuck on rebooting screen and does nothing. Eventually it goes back into sleep of death and have to hard start it and it reverts back to cookies&cream 1.3.0 with no apps installed. I can reinstall apps but no recovery sticks and still wont allow me to reboot into recovery.
Any thoughts would be most welcome as it's barely usable in the current state.
nvm
finally got it into fastboot mode and was able to flash twrp and now into recovery mode. sadly none of the updated roms I downloaded stuck but at least it's up and running and it's only time being spent re downloading things. could be worse.
Turns out it ended up being the kernel that was causing the problem. It was one meant for 4.1.1 and I had updated to a ROM that was 4.1.2 based. I'm just thankful it was fixable.
Sent from my Nexus 7 using xda app-developers app
My nexus 4 was rooted a while back before I got the OTA 4.3 android update via system update. Everything went fine then with that download. I was a bit anxious to get the 4.4 kit kat release and having seen it appear in system update 2 days ago I decided I was gonna download it yesterday and I did. After it finished the phone restarted and then was stuck in an infinite loop. I had no backup and so I decided to wipe; after which I had no operating system. I downloaded the
factory rom image of 4.4 (stock_mako_KRT16S.zip),
radio (cwm-radio-mako-m9615a-cefwmazm-2.0.1700.97.zip)
and bootloader (KK_4-4_BOOTLOADER.zip)
I flashed the radio first then then bootloader and both fine, then when it was turn for the factory rom it said error extracting file.. the dreaded status 7 error.
Anyways, I figured since it wasn't working I'd just go for a custom rom and I had rasbeanjelly on my phone from back when I rooted but never got around to flashing. So I thought I would try it and it flashed along with the gapps 4.3 but I've had several huge glitches such as the phone moving slowly and missing important google apps such as camera and such.
So I was up all night trying to figure out how to go back to stock rom and do a recovery and everything I tried was no luck. Kept running into the status 7 error. Watched a few videos that suggested I get Wug's Nexus Root Toolkit to unroot and then lock my bootloader and then flash a stock recovery. It didn't work because I realised one severe difference.
MY NEXUS 4 HAS A NEXUS 7 BUILD NUMBER.. I googled the internet and nothing..
Anyways. Says android 4.3
Build: JSS15Q
rasbeanjelly build: fri aug 23 2013 (probably old)
I just wanna know how I can get back to stock.
And I lost my root privileges as well when I flashed rasbean.
Any other information can be provided. THANKS MUCH.
Hey XDA, just a long time stalker who has finally given up trying to find his solution on already posted items (I think 10 hours of trail and error means I'm not gonna catch what I'm failing to see...)
When I first got my galaxy s4 I downloaded KangaBean and it was on 4.2.2 I believe. Today I decided I should upgrade to 4.4.2 since I've only been hearing good things about it, and I wanted the slight updates that came with it.
Well, I have a AT&T s4, sgh-i337 that was on CWM 6 when I tried updating to another ROM, the first one I tried was GOOGLE EDITION 4.4.2 BY DANVDH. Did a wipe, cache, dalvik, format system, flashed it, flashed loki doki, said no to re-root/root fix prompt that followed, then I came to the yellow triangle, I thought that was odd, believed I missed something.
So, I downloaded TWRP 2.5.0.2 like the thread suggested, tried again, no luck. Then I tried Unoffical Carbon KitKat, which just caused the "Samsung Custom" logo to stay on indefinitely (I let it sit for 40 minutes before giving up.) After 2 failed ROMs, I tried KangaKat, updated version of KangaBean, so it should be just dandy right? Narp, same luck. This one boots, then reboots into recovery.
At this point I considered myself to be stupid in some way so obvious that I would die before I noticed it. So, then I just flashed the stock firmware thats like 2.5 gb through odin, re-rooted and installed CWM 6.0.4.4 LOKI'd and tried to flash KangaKat, being confident it would work this time, again I got boot to the logo and then reboot into recovery.
At this point I attempted the other 2 ROMs again, multiple times.
After some sobbing, I re-did the stock firmware, tried again, failed again.
My sadness turned into rage, I just destroyed one of my micro sd to usb-s because it was being annoying and I was annoyed, I took a picture and got over it.
I tried a 3rd time with the re-flashing stock firmware and tried with twrp again, no cigar.
Now, after MANY hours and MANY false hopes... I shall be using my blackberry and hoping to return to android soon, if somebody can help me figure out what I'm missing. Many thanks ahead!
Did you do lokidoki after?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Did you doa hard reboot clear the cache and davlik after it got stuck on the lock screen ? It seems odd that it would just not boot up at all. I was about to wonder if maybe it was the CM kernel bug that will keep it from booting past the initial screen but you tried aGE rom so...
So I have been running CM11 since January and finally got around to updating to KitKat to see what was new and because CM11 wasn't using the kitkat kernel which I assume is what caused all the SoDs and instabilities in all the ROMs. Well now I'm on stock and I'm suffering horrible battery life in comparison (17 hours with 4 screen on vs 36 hours with 8 screen on). I tried flashing CM11 and it worked but after a day or two I wanted to try a new ROM. Carbon was one that I saw near the top of one of the G2 development forums so I decided to try that. Went through the normal process to flash a ROM and it bootlooped when I rebooted. My backup also boot looped and I had to use some method to go back to 12B since I had no ROM or anything on my phone. Got back to 24A and I tried flashing Malladus to see if a stock based ROM would work and it looped. Restored my backup and tried CM11 and it also looped. Now I'm sitting on stock with Verizon's bloat hogging resources and battery and a phone that won't flash and boot successfully. Is there any way I can fix this? Has anyone seen this before?
TLDR: phone won't flash a ROM without bootlooping since 24A update
Only gonna bump this once but I really hope the right person sees this. Really confused as to why my phone won't properly boot after a clean ROM flash
So i have been using Android L pv-79 Developer preview since it first came out flashing updates and kernels without an issue. Today i flashed a newer kernel by defconoi switched on intelli thermal and uv by 75, everything was running normal for hours. I take my phone out of my pocket and its on the google boot logo. Tried booting into recovery but it still stuck on the google boot logo. So i fast booted cam recovery nothing happened then i fast booted the 4.4.4 stock image successfully and I'm still stuck.. some assistance on this matter would be really helpful. Need to fix this before work.
Thanks
Edit: Fastbooted 4.2.2 and still the same issue.