Database Users

[Q] after installing new kernel, cannot get into recovery, multiple crashes, hangs

i just installed this kernel
http://forum.xda-developers.com/showthread.php?t=1804374
and since then, i have had multiple problems. multiple things force close, programs dont load, everything hands (like when i hit power off, it just hangs with the circle then everything freezes up and i have to hold power button for 15 - 20 secs to turn off device).
cannot get into recovery - everytime i try to from bootloader it hangs at the google page and if i try to get into from rom manager, rom manager doesnt even load
does anyone have any suggestions?
thanks in advance!

bump.. since i changed the post.

joshtb86 said:
i just installed this kernel
http://forum.xda-developers.com/showthread.php?t=1804374
and since then, i have had multiple problems. multiple things force close, programs dont load, everything hands (like when i hit power off, it just hangs with the circle then everything freezes up and i have to hold power button for 15 - 20 secs to turn off device).
cannot get into recovery - everytime i try to from bootloader it hangs at the google page and if i try to get into from rom manager, rom manager doesnt even load
does anyone have any suggestions?
thanks in advance!
Click to expand...
Click to collapse
Have you tried flashing the stock kernel via fastboot?

comminus said:
Have you tried flashing the stock kernel via fastboot?
Click to expand...
Click to collapse
can you link me to it? the only one I can find is from another post and it includes init.d support.
thanks!

fck.. this is not good. I tried using wugs toolkit and flashed the stock kernel with init.d support but it got messed up somewhere after it installed a temporary recovery and now it boots straight into recovery and I cannot boot into the actual tablet. I just flashed the stock 4.1.2 rom here
http://forum.xda-developers.com/showthread.php?t=1929270
and still cannot boot into the tablet its booting straight to recovery
can anyone help?

joshtb86 said:
fck.. this is not good. I tried using wugs toolkit and flashed the stock kernel with init.d support but it got messed up somewhere after it installed a temporary recovery and now it boots straight into recovery and I cannot boot into the actual tablet. I just flashed the stock 4.1.2 rom here
http://forum.xda-developers.com/showthread.php?t=1929270
and still cannot boot into the tablet its booting straight to recovery
can anyone help?
Click to expand...
Click to collapse
Flash back to stock http://forum.xda-developers.com/showthread.php?t=1907796

comminus said:
Flash back to stock http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
I think I was able to flash the factory stock image because I finally got it to boot, but its in the "android is upgrading" phase, so I will post after if this worked or if I tried the above.
thanks!

now it is intermittently booting up and intermittently booting straight into recovery.

I believe ive fixed it. I booted back into the OS 3 times and no booting into recovery. thanks!

joshtb86 said:
I believe ive fixed it. I booted back into the OS 3 times and no booting into recovery. thanks!
Click to expand...
Click to collapse
I'm having the same issue now after flashing faux's kernel. You had to reflash a stock image from the toolkit to fix it?

VanillaG0rilla said:
I'm having the same issue now after flashing faux's kernel. You had to reflash a stock image from the toolkit to fix it?
Click to expand...
Click to collapse
yes except it took multiple multiple times to work and actually stick. i thought i had it and it was booting fine and it is booting fine now, but my performance is abysmal. its like 25% of what it was.
i have no poewr because of hurricane sandy (on coimputer at work) so i cant even use it or update it. i am strongly considering OEM relocking the tablet and starting over from scratch. performance is almost back to the lag we had before 4.1.2 was released.

[Q] TWRP hanging/locking at initial screen

I just flashed back to MDL stock then upgraded to MF9 and installed TWRP 2.6.0.0 and about half the time when I boot into TWRP it hangs at the initial teamwin screen. I have to reboot by phone 3-4 times to get it load in to TWRP when this happens. Anyone have any ideas what could be the issue? I previously had TWRP 2.5.0.2 installed and never had these issues so I am not sure if its something with the new version of TWRP or possibly an issue with the new firmware.

masterosok said:
I just flashed back to MDL stock then upgraded to MF9 and installed TWRP 2.6.0.0 and about half the time when I boot into TWRP it hangs at the initial teamwin screen. I have to reboot by phone 3-4 times to get it load in to TWRP when this happens. Anyone have any ideas what could be the issue? I previously had TWRP 2.5.0.2 installed and never had these issues so I am not sure if its something with the new version of TWRP or possibly an issue with the new firmware.
Click to expand...
Click to collapse
I thought this was the issue with the 2.5.0.3 that was subsequently pulled. I'm still on 2.5.0.2 (and I guess I'm going to stick with this version as long as I can)

Dude the same thing happened to me. It also sometimes took EXTREMELY long to flash files and wipe dalvick/cache. Like it would literally take 1 minute to wipe dalvick/cache sometimes. I reverted back to 2.5.0.2 and loving it. I don't think I'll switch back anytime soon because it runs perfect and I've literally never had any issues with it!!

jj14 said:
I thought this was the issue with the 2.5.0.3 that was subsequently pulled. I'm still on 2.5.0.2 (and I guess I'm going to stick with this version as long as I can)
Click to expand...
Click to collapse
Joe0113 said:
Dude the same thing happened to me. It also sometimes took EXTREMELY long to flash files and wipe dalvick/cache. Like it would literally take 1 minute to wipe dalvick/cache sometimes. I reverted back to 2.5.0.2 and loving it. I don't think I'll switch back anytime soon because it runs perfect and I've literally never had any issues with it!!
Click to expand...
Click to collapse
Thanks for the info... I'll flash 2.5.0.2 back

masterosok said:
Thanks for the info... I'll flash 2.5.0.2 back
Click to expand...
Click to collapse
just FYI, other people reporting similar issues with 2.6
http://forum.xda-developers.com/showthread.php?t=2262999&page=24

Always had that issue with TWRP. Switched over to CWM, I prefer CWM anyway.
Sent from my SPH-L720 using xda app-developers app

N4 upgrade failed

Help me XDA, you're my only hope...
First, background: I bought my Nexus 4 over the internet, because it was never officially released in Belgium. I had to have the screen replaced, and let a 3rth party do it. Glass damage isn't covered by the warranty and it would mean sending my phone by international mail if i used the official warranty people. They told me that the also had to replace the proximity sensor.
My phone worked perfectly afterwards. Until I tried to install the automatic upgrade to 4.3.
First it stopped at the X-logo screen and became very hot. I contacted play support and did all the things they advised (including a factory reset, rebooting in safe mode), none of it works. I found someone with the same problem who managed to get past the X-screen by flashing back the 4.2.2 radio version. And that worked: the phone booted and the update started.
However, since that moment I got a lot of problems:
- random shutdowns
- random locking of the SIM card
- phone not starting unless plugged in charger.
Worst of all, reflashing stock images for 4.2 and 4.2.2 or AOKP does nothing to solve these problems. I also tried a new SIM card, and still nothing.
I'm at my wit's end now. Could there be a driver issue? Any other things I can try?
TIA

Possibly a driver issue and also reflashing does not help meaning that you need to flash an other kernel.
Sent from my Nexus 4 using Tapatalk 4

andyabc said:
Possibly a driver issue and also reflashing does not help meaning that you need to flash an other kernel.
Click to expand...
Click to collapse
any suggestions for a good kernel that can run stock android?

If your goal was to upgrade to stock 4.3, you can follow efrant's guide to flash the factory image at at http://forum.xda-developers.com/showthread.php?t=2010312&highlight=efrant. Just be sure to download the JWR66V image and use the updated file names when you flash since the file names in this guide are for the Android 4.2 image.

BobWalker said:
If your goal was to upgrade to stock 4.3, you can follow efrant's guide to flash the factory image at at http://forum.xda-developers.com/showthread.php?t=2010312&highlight=efrant. Just be sure to download the JWR66V image and use the updated file names when you flash since the file names in this guide are for the Android 4.2 image.
Click to expand...
Click to collapse
Well, I tried again. (For the 6th time this month) No different as before: it's been stuck on the X screen for 20 minutes now and getting warmer.
EDIT: I finally managed to get into the recovery menu. No idea why it wouldn't let me use volume up + power...

As suggested in the guide I deleted cache and a factory wipe.
My phone is still stuck at the X screen...
any other suggestions, anyone?

Joenr76 said:
As suggested in the guide I deleted cache and a factory wipe.
My phone is still stuck at the X screen...
any other suggestions, anyone?
Click to expand...
Click to collapse
Try installing PA 3.97 with this kernel: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-Kernel-4.3_JWR66V_HALFBREED.zip
Sent from my Nexus 4 using Tapatalk 4

andyabc said:
Try installing PA 3.97 with this kernel: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-Kernel-4.3_JWR66V_HALFBREED.zip
Click to expand...
Click to collapse
I never did that before: do I flash the kernel first or the Rom first? Are there any guides?
EDIT: I just read that Paranoid Android comes with the halfbreed kernel included. Is that the one you linked too?

Before jumping into the kernel thing (also because i wanted to be able to work with a device that can actually boot), I reinstalled the 4.2.2 factory image. It took about 5 minutes for the first shutdown to happen. *sigh*
And without plugging it in, it goes into a boot loop (going to x screen for a while, then restarting.) When I plug it in, it starts immediately, but shows the battery as empty. It was 63% when it shut itself down.
It's a clean install, I just don't understand...

Okay so, I'm assuming you have a custom recovery like TWRP. Open it and flash the newest boot loader and radio. Then flash Paranoid Android and GApps. Then try flashing Faux kernel and clearing cache/dalvik. If you still have problems, then I have no idea
Sent from my Nexus 4 using xda premium

Open up your phone to see the battery is securely checked and to see if all the components are okay. Then look do a full wipe of cache,dalvik,system,data,and sd (internal storage). Then use wugs toolkit to a upgrade on a clean flash. Double check to make sure you wipe everything!
Sent from my Nexus 4 using Tapatalk 4

TheNerd:] said:
Open up your phone to see the battery is securely checked and to see if all the components are okay.
Click to expand...
Click to collapse
Apparently, my battery had expanded so much that it was pushing at everything in the phone. I ordered a new one and put it in. In 4.2.2 I have no problems anymore with random shut-downs.
However, when I run the OTA upgrade, the phone stays on the X-logo screen. Just like last time. I expect that was why the battery got blown: the first time I ran the OTA, I did it at night and only checked the phone in the morning.
I fixed my N4 by reflashing an older radio (48, IIRC). I have no idea why the newest radio won't work...

Joenr76 said:
Apparently, my battery had expanded so much that it was pushing at everything in the phone. I ordered a new one and put it in. In 4.2.2 I have no problems anymore with random shut-downs.
However, when I run the OTA upgrade, the phone stays on the X-logo screen. Just like last time. I expect that was why the battery got blown: the first time I ran the OTA, I did it at night and only checked the phone in the morning.
I fixed my N4 by reflashing an older radio (48, IIRC). I have no idea why the newest radio won't work...
Click to expand...
Click to collapse
Try flashing 4.3 via the factory image. Then use this guide to flash the factory image to the phone.

tykate said:
Try flashing 4.3 via the factory image. Then use this guide to flash the factory image to the phone.
Click to expand...
Click to collapse
Tried that before. I did some research and I guess this is relevant: http://www.androidpolice.com/2013/0...rops-on-some-nexus-4-handsets-fixes-in-sight/ Especially since I ordered my Nexus from the Netherlands.
I'll have to wait until that bug gets fixed until I can upgrade my radio.

GE ROM, won't reboot

Hi,
I flashed the google edition rom a few weeks ago, all was working fine. This morning, I decided to flash a stock rom from sammobile (was this a bad idea)? I used CF autoroot and twerp custom recovery. It failed. So wiped everything, reflashed the google edition rom, but when I reboot the phone it gets stuck showing "Samsung galaxy s4" white text.
To boot it again i have to wipe data, cache and dalvik, then reflash the ROM, then qipe cache and dalvik, then it reboots. But when I turn it off then on again the whole process starts again.
Can anybody tell me what I'm doing wrong? This is the same ROM that worked faultlessly for weeks...
Thanks

Did u wait long enough, first reboot after flashing a new rom can take a while.
Sent from my GT-I9505 using XDA Premium HD app

richard2311 said:
Did u wait long enough, first reboot after flashing a new rom can take a while.
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah, I gave it 5 minutes, but it's not even getting to the boot animation.
When I tried to flash the stock rom could that have messed something up? It said failed, then for ages after that, it kept saying "error-failed to open \data\data .... I/O error" in twrp.
To avoid that I have to wipe data seperately, reboot recovery, then flash the ROM again from scratch. Every time I reboot the phone I have to do a full wipe and flash the rom before it even boots..

dickson123 said:
Yeah, I gave it 5 minutes, but it's not even getting to the boot animation.
When I tried to flash the stock rom could that have messed something up? It said failed, then for ages after that, it kept saying "error-failed to open \data\data .... I/O error" in twrp.
To avoid that I have to wipe data seperately, reboot recovery, then flash the ROM again from scratch. Every time I reboot the phone I have to do a full wipe and flash the rom before it even boots..
Click to expand...
Click to collapse
Have a read if this great guide: http://forum.xda-developers.com/showpost.php?p=43340522&postcount=3297

mobileguynz said:
Have a read if this great guide: http://forum.xda-developers.com/showpost.php?p=43340522&postcount=3297
Click to expand...
Click to collapse
Ok, thanks, I'll give it a go later. I'm at work and was hoping for a solution that didn't require ODIN (work PC too locked-down )

dickson123 said:
Ok, thanks, I'll give it a go later. I'm at work and was hoping for a solution that didn't require ODIN (work PC too locked-down )
Click to expand...
Click to collapse
Well depending on which stock ROM you flashed you maybe affected by the enabled SElinux issue see https://plus.google.com/app/basic/stream/z13xxnmzvyeihn00w23wcdp55terwvove

mobileguynz said:
Well depending on which stock ROM you flashed you maybe affected by the enabled SElinux issue see https://plus.google.com/app/basic/stream/z13xxnmzvyeihn00w23wcdp55terwvove
Click to expand...
Click to collapse
I don't understand what the issue is though. I'm not doing anything different than I did 3 weeks ago, and yet this time it doesn't work.
It's now gotten to the stage where it won't boot at all, just sits at the white text, no boot animation.
Is it possible that flashing a stock un-rooted ROM has messed it up somehow? Technically it never flashed because it just failed immediately.

dickson123 said:
I don't understand what the issue is though. I'm not doing anything different than I did 3 weeks ago, and yet this time it doesn't work.
It's now gotten to the stage where it won't boot at all, just sits at the white text, no boot animation.
Is it possible that flashing a stock un-rooted ROM has messed it up somehow? Technically it never flashed because it just failed immediately.
Click to expand...
Click to collapse
If you flashed the latest stock ROM it maybe be one with Knox and that has a secure boot loader and kernel secure Selinux Knox stops you from modifying and installing.
Try using ausdims v16 kernel or wadams Adam kernel for stock roms. Note when I flashed the last ROM waited 10 minutes and had do a wipe and reset for it to boot see last pages for discussion http://forum.xda-developers.com/showthread.php?t=2250824
http://forum.xda-developers.com/showthread.php?t=2250824

[Q] Radio Dead, No Cellular

I've spent two days flashing, re-flashing radios, different ROMs, stock, rooted, not rooted, locked, unlocked and cannot get any cell service. Phone was rocking LTE with PAC ROM a few days ago then cell service just stopped working.
Also, any version other than stock 4.2 causes a boot loop.
Really....really weird.
Was using on T-Mobile...very happily.
I think I fried my radio.
Anybody have any advice? About to call Google to try to get RMA
Cheers!

have you tried a different simcard, or your simcard in a different phone?

Yes, tried different sims
simms22 said:
have you tried a different simcard, or your simcard in a different phone?
Click to expand...
Click to collapse
Yes, I sure have. My IMEI is being shown as "Uknown".
Tried *#*#4636#*#* and none of the phone setting stick. I tried to "Select Radio Band" but when I choose "USA" it kicks back an error.
Could using the Hybrid modems have caused this problem?
What are the chances of Google replacing my phone, purchased in June?

Boot loop
stenosis said:
I've spent two days flashing, re-flashing radios, different ROMs, stock, rooted, not rooted, locked, unlocked and cannot get any cell service. Phone was rocking LTE with PAC ROM a few days ago then cell service just stopped working.
Also, any version other than stock 4.2 causes a boot loop.
Really....really weird.
Was using on T-Mobile...very happily.
I think I fried my radio.
Anybody have any advice? About to call Google to try to get RMA
Cheers!
Click to expand...
Click to collapse
Any time I load anything but 4.2, I get a boot loop. I've tried several different ROM's - and boot loop on every one. Watching CyanogenMod spinning for 10 minutes right now...about to give up.
Is there any logs I can look at?

stenosis said:
Any time I load anything but 4.2, I get a boot loop. I've tried several different ROM's - and boot loop on every one. Watching CyanogenMod spinning for 10 minutes right now...about to give up.
Is there any logs I can look at?
Click to expand...
Click to collapse
I had a similar issue, had to do this

Looking forward to using this!
lopezk38 said:
I had a similar issue, had to do this
Click to expand...
Click to collapse
WOW!! This looks like fun!!!
Thank you so much, you are very kind.
Will be sure to report results!
Cheers!

No luck
lopezk38 said:
I had a similar issue, had to do this
Click to expand...
Click to collapse
Tried this procedure, no luck. Radio still won't turn on...
This puppy has had it....RMA time.
Thanks for the help!