Related
Ok, so I did my first root last night with my G2x and flashed CM7 onto it using the instructions here for GB. The process didn't seem to go through at first because it kind of froze for awhile, but when I took out the battery and put it back in it loaded up. (I understand I may have made a mistake here.)
I thought all was good but then I tried to boot up Clockwork recovery to flash the GAPPs zip and everytime I tried it wouldn't go through the screens it is supposed to.
I'd hold the down volume and power buttons and the first LG (white) would show. Then it would bring up a cyan colored horizontal loading bar under the LG. I continue to hold the buttons hoping to see the cyan LG but then screen changes to a box with an orange arrow pointing to an android logo. There is a loading bar under this as well. If I let go here it loads up CM7 but if I continue holding on it takes me to the S/W screen.
I've tried this multiple times but I've kinda given up. I even tried individually installing the apks from the GAPPS zip but only a few of them successfully installed.
At a loss .Please let me know what I can do.
Let me guess. You flashed CWM via ROM manager?
Follow he guide here and let us know how it goes:
http://forum.xda-developers.com/showthread.php?t=1056847
Also, before you install the ROM use the wipe tool in my sig.
I appreciate the response but I did use that thread to flash it.
ae2012 said:
Ok, so I did my first root last night with my G2x and flashed CM7 onto it using the instructions here for GB. The process didn't seem to go through at first because it kind of froze for awhile, but when I took out the battery and put it back in it loaded up. (I understand I may have made a mistake here.)
I thought all was good but then I tried to boot up Clockwork recovery to flash the GAPPs zip and everytime I tried it wouldn't go through the screens it is supposed to.
I'd hold the down volume and power buttons and the first LG (white) would show. Then it would bring up a cyan colored horizontal loading bar under the LG. I continue to hold the buttons hoping to see the cyan LG but then screen changes to a box with an orange arrow pointing to an android logo. There is a loading bar under this as well. If I let go here it loads up CM7 but if I continue holding on it takes me to the S/W screen.
I've tried this multiple times but I've kinda given up. I even tried individually installing the apks from the GAPPS zip but only a few of them successfully installed.
At a loss .Please let me know what I can do.
Click to expand...
Click to collapse
When it get to the point where "the cyan colored horizontal loading bar" let go of the volume and power button and see if it boots into CWM.
Ok, I tried that and it went to that android logo screen again. Then it went to a black screen and then the cyan LG logo screen. From there it booted up CM7.
I just noticed when I try to boot into Clockwork it erases everything I added to it including contacts and apps I installed.
ae2012 said:
Ok, I tried that and it went to that android logo screen again. Then it went to a black screen and then the cyan LG logo screen. From there it booted up CM7.
I just noticed when I try to boot into Clockwork it erases everything I added to it including contacts and apps I installed.
Click to expand...
Click to collapse
Try rooting process all over again... just make sure battery have plenty of charge and make sure during any of the process there's no interruptions... let us know what happen after that...
Sent from my LG-P999 using xda premium
I will unroot and try again. A few questions though:
I'm reading and it looks like I need to be able to boot into CWR to be able to unroot...is using ROM Manager a safe alternative?
And also, while I followed the instructions for flashing through the thread you provided last time, I read that I may need to erase/wipe certain types of data before I do so to avoid the market problems. Can someone provide me information on that?
I just want to make sure I do this right a second time.
ae2012 said:
I will unroot and try again. A few questions though:
I'm reading and it looks like I need to be able to boot into CWR to be able to unroot...is using ROM Manager a safe alternative?
And also, while I followed the instructions for flashing through the thread you provided last time, I read that I may need to erase/wipe certain types of data before I do so to avoid the market problems. Can someone provide me information on that?
I just want to make sure I do this right a second time.
Click to expand...
Click to collapse
No need to unroot... as long as your computer still detect your phone... just flash everything again... I mean since you want to root... I would just do all the rooting process again... and reflash clock work... don't use rom manager to flash clockwork mod...
Or
And since you can't get into clockwork... you can just try flashing clockwork again... no rom manager
Sent from my LG-P999 using xda premium
Sweet, so I reflashed CWR and CM7 and I got my contacts back and several other minor issues were corrected.
I am experiencing a new problem now though. Whenever I try to download from the market it tells me "[App name] could not be downloaded due to an error."
What can be done to fix this?
ae2012 said:
Sweet, so I reflashed CWR and CM7 and I got my contacts back and several other minor issues were corrected.
I am experiencing a new problem now though. Whenever I try to download from the market it tells me "[App name] could not be downloaded due to an error."
What can be done to fix this?
Click to expand...
Click to collapse
Try flashing Google apps again. Cm7 doesn't include them in their builds.
Sent from my LG-P999
Worked like a charm. Thanks, yall are the best.
ae2012 said:
I will unroot and try again. A few questions though:
I'm reading and it looks like I need to be able to boot into CWR to be able to unroot...is using ROM Manager a safe alternative?
And also, while I followed the instructions for flashing through the thread you provided last time, I read that I may need to erase/wipe certain types of data before I do so to avoid the market problems. Can someone provide me information on that?
I just want to make sure I do this right a second time.
Click to expand...
Click to collapse
Rom Manager is not a safe alternative. Stay with Nvidia ClockworkMod.
Its should be a blue lg logo when you have to let go of the buttons.
Sent from my LG-P999 using xda premium
ae2012 said:
I will unroot and try again. A few questions though:
I'm reading and it looks like I need to be able to boot into CWR to be able to unroot...is using ROM Manager a safe alternative?
And also, while I followed the instructions for flashing through the thread you provided last time, I read that I may need to erase/wipe certain types of data before I do so to avoid the market problems. Can someone provide me information on that?
I just want to make sure I do this right a second time.
Click to expand...
Click to collapse
Every time before you re- flash a rom I would recommend doing a data/factory reset within clockwork recovery. then Wipe your cache. And then even a wipe of the dalvic cache under advanced settings. Then flash the rom then gapps. Then reboot. Its called doing a clean install. It just makes everything smoother when re- flashing. And if your apps ever not update like that again just fix the permissions in clockworkmod then reboot. It usually fixes it. And i don't recommend flashing directly from the rom manager. Do it from recovery instead. Hope this helps.:thumbup:
Sent from my LG-P999 using XDA
[edit]
Sent from my G2X.
Rocking stock CM 7.2.0-RC1
Similar issue, totally different outcome...
Ladies and Gentlemen (and low-lifes),
I have found myself in a similar situation, after recently flashing a ROM, to where I am now unable to boot into CW Recovery. The ROM flashed is working fine but when I attempt to boot into recovery I get a black screen and it never progresses beyond that. I have attempted to reflash of course via NVFlasher and from all indications it's been a successful flash. That said, the results remain the same... black screen.
FYI: I have not yet attempted to flash back to Stock Recovery.
•Current Rom - Owain's Domination v77 (a great ROM by the way)
•Current kernel - Harsh's 3.0.32
•Used Nullifier to prep device for ROM install (as I have been doing for sometime now)
If anyone has any experience w/this issue or any advice going forward I would greatly appreciate it.
UPDATE: (that was fast huh?) .................................................................................................................................................................................................
So I went ahead and flashed the Stock Recovery, tested and got access. I then flashed CWM 5.0.2.0 and to my delight was able to see the CWM console. I let go of the power and volume down buttons and the phone rebooted. Now the ROM will not boot, just sits in a forever cycle on the splash screen and the results continue to be the same as recently mentioned for attempting to get into the freshly flashed recovery.
dark ma++er said:
UPDATE: (that was fast huh?) .................................................................................................................................................................................................
So I went ahead and flashed the Stock Recovery, tested and got access. I then flashed CWM 5.0.2.0 and to my delight was able to see the CWM console. I let go of the power and volume down buttons and the phone rebooted. Now the ROM will not boot, just sits in a forever cycle on the splash screen and the results continue to be the same as recently mentioned for attempting to get into the freshly flashed recovery.
Click to expand...
Click to collapse
Ok, I will bring my concerns to an end now. I forced CWM to remain in play by not letting go of the power and vol. down buttons then using my thumb to see if I could stroll through options in CWM. Once I accessed a few it remain stable. I nullified and re-flashed my ROM and all seems ok in my personal corner of the universe. I am now able to boot into CWM without issue.
Anyone one else experiencing a stall when rebooting using SKy ICS 4,2F-4.5A?
If I reboot either from CWM or from using the drop down or the power button, the phone hangs up with a black screen and all the LED buttons lit up? Then I have to hold the power button down to do a hard reboot.
I have reflashed numerous times and have come through numerous updates and this one issue persists.
Anyone?
Rogers
Kernel RUXLF3
Update 4.2F - 4.5A
Radio:UCLF5
No problem here. You have installed busy box, fixed permissions, and the usual stuff?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I got the exact same issue, busy box installed, permissions fixed. Tried flashing everything again didn't solve it, kernel etc.
The only thing I didn't try is radio, are you using rogers radio as well?
Also it happens if I just try shut down the phone.
Try doing a backup in cwm, then just immediately restore that backup... often fixes that problem for me on sky ics.
kishke said:
I got the exact same issue, busy box installed, permissions fixed. Tried flashing everything again didn't solve it, kernel etc.
The only thing I didn't try is radio, are you using rogers radio as well?
Also it happens if I just try shut down the phone.
Click to expand...
Click to collapse
I got it resolved but only by fluke. Flashed 4.2-5b as well as the CYMBALINE kernel (an attempt to resolve bluetooth connection issues) and now everything boots fine.
Thanks
I flashed the kernel without it being solved. I did the backup+restore and I think it seems to have fixed it, I'll do some more checking tomorrow kinda late here but thanks!
Btw after you flashed 4.5a you didn't need to flash b
Had the same problem after doing a fresh 4.2 R2 base install. I let the phone fully cache (5 mins or so) and I tried rebooting to CWM to flash the 5A update and the phone hung on shutdown and my cap lights stayed lit up. I realized I forgot to install busybox after 1st boot-up per the OP instructions. So I held power button for 10secs, rebooted, installed busybox and it rebooted fine into CWM to flash update. Weird, never seen that before.
DudelePOWski said:
Anyone one else experiencing a stall when rebooting using SKy ICS 4,2F-4.5A?
If I reboot either from CWM or from using the drop down or the power button, the phone hangs up with a black screen and all the LED buttons lit up? Then I have to hold the power button down to do a hard reboot.
I have reflashed numerous times and have come through numerous updates and this one issue persists.
Anyone?
Rogers
Kernel RUXLF3
Update 4.2F - 4.5A
Radio:UCLF5
Click to expand...
Click to collapse
Running Rogers ICS stock here rooted and busybox first, then flashed the modded UXCLF3 Kernel, hangs on the Rogers animation and the touch keys stay on whenever I try to shut down or reboot the phone, have to pull the battery all the time, trying the Backup + Restore route now, hope it works otherwise I'll have a brick and a phone that won't turn off
howlingmoon12 said:
Running Rogers ICS stock here rooted and busybox first, then flashed the modded UXCLF3 Kernel, hangs on the Rogers animation and the touch keys stay on whenever I try to shut down or reboot the phone, have to pull the battery all the time, trying the Backup + Restore route now, hope it works otherwise I'll have a brick and a phone that won't turn off
Click to expand...
Click to collapse
It worked for me, worst case you can hold the power key for 10s to turn it off.
The issue me and I think also the other guy had was black screen and touch key lights.
DudelePOWski said:
Anyone one else experiencing a stall when rebooting using SKy ICS 4,2F-4.5A?
If I reboot either from CWM or from using the drop down or the power button, the phone hangs up with a black screen and all the LED buttons lit up? Then I have to hold the power button down to do a hard reboot.
I have reflashed numerous times and have come through numerous updates and this one issue persists.
Anyone?
Rogers
Kernel RUXLF3
Update 4.2F - 4.5A
Radio:UCLF5
Click to expand...
Click to collapse
This has been answered in the dev thread. Here is the solution . You need to flash it with cwm touch. I have no idea why but with cwm the older cwm you get hung up rebooting or shutting down. It will also hang when fixing permissions. I have also read that twrp was working also.
Cwm touch can be found here half way down the thread.
http://forum.xda-developers.com/showthread.php?t=1704630
Sent from my SAMSUNG-SGH-I727 using xda premium
I had it and I'm using cwm touch 5.8.1.3 .
if all else fails check the md5 checksums of all downlads, or redownload and check its md5, use touch cwm or as sean is using it now twrp recovery, and read my sig
kishke said:
I flashed the kernel without it being solved. I did the backup+restore and I think it seems to have fixed it, I'll do some more checking tomorrow kinda late here but thanks!
Btw after you flashed 4.5a you didn't need to flash b
Click to expand...
Click to collapse
I went from 4.5a update (fresh base install) to 5b update.
I just downloaded the newest CM release (10.0.0 stable) and upgraded. For some reason every time I attempt to boot up my phone it sends me directly into recovery (clockwork). Its almost like a boot loop, but I go into recovery instead. I've tried reflashing to an older nightly version of CM10 that I know works, but it consistently just sends me back to recovery when I go to reboot. I tried a Nandroid restore, same thing. I'm not new to flashing Roms, and went through all the rituals (wiping data/cache, etc). Never have had any trouble flashing Roms in this particular phone.
I can't get into fast boot either, always goes into recovery. Has anyone seen anything like this before? I'm running out of ideas of my own. Any ideas are appreciated. There's a beer in it for the best information leading to the reconstitution of this jobby.
Sent from my Nexus 7 using xda app-developers app
CounterSolar said:
I just downloaded the newest CM release (10.0.0 stable) and upgraded. For some reason every time I attempt to boot up my phone it sends me directly into recovery (clockwork). Its almost like a boot loop, but I go into recovery instead. I've tried reflashing to an older nightly version of CM10 that I know works, but it consistently just sends me back to recovery when I go to reboot. I tried a Nandroid restore, same thing. I'm not new to flashing Roms, and went through all the rituals (wiping data/cache, etc). Never have had any trouble flashing Roms in this particular phone.
I can't get into fast boot either, always goes into recovery. Has anyone seen anything like this before? I'm running out of ideas of my own. Any ideas are appreciated. There's a beer in it for the best information leading to the reconstitution of this jobby.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Getting into fast boot is tricky...hold down arrow and push power, then release vol after boot.
Are you flashing boot.img properly in fastboot?
OK. I got it semi sorted out. It turns out there is a bug of some kind, I am not sure if it is special to the One S or what, but it is to mine. CWM gets thrown into a sort of boot loop if the device is charging while attempting to restart, and won't boot either into the rom nor into fastboot. It won't respond to adb either. It just keeps going into recovery. And it won't shut off. This happens when charging for some reason.
After I took the USB cable out I reset it with volume +, volume -, and power. I guess HTC put that little trick in there to simulate removing the battery since you can't take the battery out of the back. That effectively shut the phone off. Then I was able to get into fastboot and connect with adb. I put Team Win Recovery on there instead of CWM for now, and got into recovery. Wiped everything, and flashed the extra rom I had on there.
I am still unable to flash CM10 stable, it just goes into bootloop if I try, but at least I have my phone back. Hopefully I will be able to figure out if there is a way to kick start it on there, or whatever bug is solved. Look forward to trying it when its (or I'm) not broken.
Sent from my Nexus 7 using xda app-developers app
CounterSolar said:
OK. I got it semi sorted out. It turns out there is a bug of some kind, I am not sure if it is special to the One S or what, but it is to mine. CWM gets thrown into a sort of boot loop if the device is charging while attempting to restart, and won't boot either into the rom nor into fastboot. It won't respond to adb either. It just keeps going into recovery. And it won't shut off. This happens when charging for some reason.
After I took the USB cable out I reset it with volume +, volume -, and power. I guess HTC put that little trick in there to simulate removing the battery since you can't take the battery out of the back. That effectively shut the phone off. Then I was able to get into fastboot and connect with adb. I put Team Win Recovery on there instead of CWM for now, and got into recovery. Wiped everything, and flashed the extra rom I had on there.
I am still unable to flash CM10 stable, it just goes into bootloop if I try, but at least I have my phone back. Hopefully I will be able to figure out if there is a way to kick start it on there, or whatever bug is solved. Look forward to trying it when its (or I'm) not broken.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The One S isn't offically supported by CWM. It sounds like you need to try and flash the boot.img in fastboot.
Try TWRP...it will be better
Sent whit HTC ONE S
That's weird. CM10 comes up as an update...
Either way, I tried flashing the 11/11/2012 nightly through twrp and came up the same thing, would just bootloop and not go into the rom. Fortunately I could still access both recovery and fastboot, so I went back to a previous nightly from last week, and after a (painfully long/manual) titanium restore, I'm back to normal. I'll have to investigate what is going on later when I have some extra time to commit to it.
Sent from my Nexus 7 using xda app-developers app
Yeah dc211 was right. I'm using hboot 1.14, had to go and flash boot.img in fastboot. Install went smoothly after that. Thanks for the input y'all.
Sent from my Nexus 7 using xda app-developers app
boot loop
CounterSolar said:
That's weird. CM10 comes up as an update...
Either way, I tried flashing the 11/11/2012 nightly through twrp and came up the same thing, would just bootloop and not go into the rom. Fortunately I could still access both recovery and fastboot, so I went back to a previous nightly from last week, and after a (painfully long/manual) titanium restore, I'm back to normal. I'll have to investigate what is going on later when I have some extra time to commit to it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Before you flash this you need to remove "qrngd" file from the rom . The file is located at system-bin-qrngd.
I was able to flash 10.0.0 without removing qrngd. So far it hasn't been a problem. I read somewhere that file is some sort of random number generator, but that it isn't clear whether its even used anymore. Also, they say its more of a problem with earlier nightlies, especially with people using HBOOT < 1.14. It might be just junk DNA in the system files, or they may have patched the problem. I will keep my eye on it though, and will report back if I get any spooky behavior.
Sent from my Nexus 7 using xda app-developers app
jazz452 said:
Before you flash this you need to remove "qrngd" file from the rom . The file is located at system-bin-qrngd.
Click to expand...
Click to collapse
That was fixed in the 11/09/12 nightly, so its not an issue anymore.
http://forum.xda-developers.com/showpost.php?p=33867937&postcount=2209
Hi, i have been looking for answers on the forum, and i learn new things but not how to fix this or what is causing it.
I have buyed i997 from a reseller. He sayd it doesnt work because it have bootloop, but i thinks that is not too much problem getting it working again, so i started searching for the pc drivers n software, then i find here in the forum the stock rom with and without root, i tested them both with odin and the bootloop stills present. I wipe cache and do a factory reset but it keep bootlooping, then think maybe if i update to latest AT&T rom, but no luck.Sometimes the phone just start and theres no bootloop but its very rare and most of the time when i get to the lock screen or setup manager suddently a gapps or something crash and my phome freezes and reboot. I flashed the carbon-jb-v1.6 and suddently it worked fine, no more bootloop and everything smooth,no crashes etc.. then i installed Facebook app and when i was ttyping a message the phone froze up and then restarts, and the bootloop came again, and im stuck on it, and when i pass it, which is very rare, i start typing info in the startup manager and the phone freezes and reboot.. I wipe/format cache, dalvik, factory reset, formated system and data before and after flashing the carbon rom again and it keeps bootlooping. Somebody have similar problems or know how to fix it?
Thanks
P.d. sorry for my bad english.
jakov.90 said:
Hi, i have been looking for answers on the forum, and i learn new things but not how to fix this or what is causing it.
I have buyed i997 from a reseller. He sayd it doesnt work because it have bootloop, but i thinks that is not too much problem getting it working again, so i started searching for the pc drivers n software, then i find here in the forum the stock rom with and without root, i tested them both with odin and the bootloop stills present. I wipe cache and do a factory reset but it keep bootlooping, then think maybe if i update to latest AT&T rom, but no luck.Sometimes the phone just start and theres no bootloop but its very rare and most of the time when i get to the lock screen or setup manager suddently a gapps or something crash and my phome freezes and reboot. I flashed the carbon-jb-v1.6 and suddently it worked fine, no more bootloop and everything smooth,no crashes etc.. then i installed Facebook app and when i was ttyping a message the phone froze up and then restarts, and the bootloop came again, and im stuck on it, and when i pass it, which is very rare, i start typing info in the startup manager and the phone freezes and reboot.. I wipe/format cache, dalvik, factory reset, formated system and data before and after flashing the carbon rom again and it keeps bootlooping. Somebody have similar problems or know how to fix it?
Thanks
P.d. sorry for my bad english.
Click to expand...
Click to collapse
the most inexpensive solution:
http://forum.xda-developers.com/showthread.php?t=1912599
qkster said:
the most inexpensive solution:
http://forum.xda-developers.com/showthread.php?t=1912599
Click to expand...
Click to collapse
Thanks man, but you think it can be the power button? When i unplug the battery and put it again the phone doesnt turn on or something, and when it boot up when i lock the screen with the power button it works fine. I set the cpu governor to conservative and since yesterday i didnt have any problem, but sometimes the phone reboots when typing, i think its someting with the processor or when the phone have little ram or something.
Thanks.
jakov.90 said:
Thanks man, but you think it can be the power button? When i unplug the battery and put it again the phone doesnt turn on or something, and when it boot up when i lock the screen with the power button it works fine. I set the cpu governor to conservative and since yesterday i didnt have any problem, but sometimes the phone reboots when typing, i think its someting with the processor or when the phone have little ram or something.
Thanks.
Click to expand...
Click to collapse
If you ran the phone on complete stock GB or FROYO and you are getting boot loops, it may be a hardware issue.
One of the few things that will give you boot loop with the samsung logo while using the phone is the power button.
Either way, it's no big deal to open it and clean it up to see if the problem goes away.
qkster said:
If you ran the phone on complete stock GB or FROYO and you are getting boot loops, it may be a hardware issue.
One of the few things that will give you boot loop with the samsung logo while using the phone is the power button.
Either way, it's no big deal to open it and clean it up to see if the problem goes away.
Click to expand...
Click to collapse
Thanks bud, I will try cleaning the button. Also I want to ask, is there something to log everything when the phone start? Or something to test the hardware functionality?
Thank you for your time
post number #112
http://forum.xda-developers.com/showthread.php?t=1437548&page=13
qkster said:
post number #112
http://forum.xda-developers.com/showthread.php?t=1437548&page=13
Click to expand...
Click to collapse
Thank you, the post its the number #122
jakov.90 said:
Thanks bud, I will try cleaning the button. Also I want to ask, is there something to log everything when the phone start? Or something to test the hardware functionality?
Thank you for your time
Click to expand...
Click to collapse
Bootlog Uptime will keep a record of all boots from an Android OS perspective ... It will also track crashes... It won't track events outside of a complete restart (i.e. power button bootloops.. But those are pretty obvious when they occur)
For hardware testing, try Z Device Test... That won't tell you about the buttons though... If your screen turns on without pressing power button or from any other standard event (like receiving a text or a phone call), or the phone restarts by itself, time to get cleaning..
Sent from my SAMSUNG-SGH-I997 using xda premium
Zen Arcade said:
Bootlog Uptime will keep a record of all boots from an Android OS perspective ... It will also track crashes... It won't track events outside of a complete restart (i.e. power button bootloops.. But those are pretty obvious when they occur)
For hardware testing, try Z Device Test... That won't tell you about the buttons though... If your screen turns on without pressing power button or from any other standard event (like receiving a text or a phone call), or the phone restarts by itself, time to get cleaning..
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Hey thanks, that was very useful.. i risky miself to do a stock flrom flashing with pit checking the Nand erase all option in Odin 3.07, and the random reboots are gone :laugh:. Now i have one question, Do i need an special kernel for JB 4.2.2? i plan to flash the Carbon-jb-v1.6 rom but i dont know if i need another kernel
I'm glad to hear you solved your issue.
For JB, use the kernel provided with the rom.
Sent from my SAMSUNG-SGH-I997 using xda premium
Phone is rooted with latest TWRP, Cataclysm rom, and Franco kernel. It started happening when I flashed r11 Franco kernel and when I reboot the phone, it shuts down instead. I couldn't start the phone holding down the power button and I held it for over 20 seconds. I thought I bricked my phone. After few minutes fussing with the buttons, it finally booted up. However, every time I reboot my phone, it'll do the same and I had to fuss around the buttons keeping them press down for several minutes before it'll boot up to system or boot loader. As far as I can see, it can boot to recovery & system with no issue. I'm wondering if I need to flash to stock and reflash it again. Anyone knows anything about this or had same issue, please help. Thanks.
Sent from my Nexus 5 using xda app-developers app
Listen like the kernel is the problem. So flash another one (easy way) or go back to stock.
If it's working fine then, it was the kernel which made this happens.
Much success
CHEERS
Sent from my Nexus 5 using XDA Premium 4 mobile app
Ack-nak said:
Phone is rooted with latest TWRP, Cataclysm rom, and Franco kernel. It started happening when I flashed r11 Franco kernel and when I reboot the phone, it shuts down instead. I couldn't start the phone holding down the power button and I held it for over 20 seconds. I thought I bricked my phone. After few minutes fussing with the buttons, it finally booted up. However, every time I reboot my phone, it'll do the same and I had to fuss around the buttons keeping them press down for several minutes before it'll boot up to system or boot loader. As far as I can see, it can boot to recovery & system with no issue. I'm wondering if I need to flash to stock and reflash it again. Anyone knows anything about this or had same issue, please help. Thanks.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
This is what happens: it gets stuck in the rebooting process. It doesn't properly shut down, it just hangs with the screen turned off.
Try flashing the stock kernel. Does it do the same?
abaaaabbbb63 said:
This is what happens: it gets stuck in the rebooting process. It doesn't properly shut down, it just hangs with the screen turned off.
Try flashing the stock kernel. Does it do the same?
Click to expand...
Click to collapse
Flashed with stock kernel and it's still doing the same thing. I also restore back to stock 4.4 with stock kernel and it's still doing the same. Do I need to unroot and root again then flash rom, kernel, and etc? Don't really want to do that if I don't have to but guess I have no choice? Thanks again.
Yep, do a factory reset and see if it's working fine again... I'm thinking so.
CHEERS
Sent from my ME301T using XDA Premium 4 mobile app
Update: I've decided to just wipe it all and start over by unroot and root again which solved the problem. It's rebooting correctly and not stuck in that awful black screen boot loop. Thanks.
Sent from my Nexus 5 using xda app-developers app
Ack-nak said:
Update: I've decided to just wipe it all and start over by unroot and root again which solved the problem. It's rebooting correctly and not stuck in that awful black screen boot loop. Thanks.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
what do you mean unroot and root again?
biggiephat said:
what do you mean unroot and root again?
Click to expand...
Click to collapse
This means, going back on to the stock firmware. This will remove the root for sure.
After that starting with rooting again.
Hope this answers your question
CHEERS
Sent from my Nexus 5 using XDA Premium 4 mobile app