Related
Hey everyone,
Hopefully someone can help me with this situation. I haven't been able to find relevant information yet.
I'm currently running a Rooted Incredible with the latest Virtuous ROM. I'm trying to flash back to the stock .17 kernel from HTC, but ANY kernel I flash onto it causes the screen to load up as far as the red eye, stall and then reboot causing a constant loop. The only way I can get beyond this so far is just flashing my recovery image. I've installed from ROM manager and checked to wipe data/cache (backed up before of course!) and have even booted into recovery manually and flashed from the download folder and the actual zip file. Before that I've wiped data and dalvik cache. I can't figure out what I'm missing here. Any suggestions??? I hope I haven't crippled my Droid by doin this.
DL the new stock kernel to pc mount card to pc put the new kernel somewhere you'll remember then reinstall sdcard and try flashing the kernel that way if you haven't already
Sent from my ADR6300 using XDA App
Hypcrsy said:
Hey everyone,
Hopefully someone can help me with this situation. I haven't been able to find relevant information yet.
I'm currently running a Rooted Incredible with the latest Virtuous ROM. I'm trying to flash back to the stock .17 kernel from HTC, but ANY kernel I flash onto it causes the screen to load up as far as the red eye, stall and then reboot causing a constant loop. The only way I can get beyond this so far is just flashing my recovery image. I've installed from ROM manager and checked to wipe data/cache (backed up before of course!) and have even booted into recovery manually and flashed from the download folder and the actual zip file. Before that I've wiped data and dalvik cache. I can't figure out what I'm missing here. Any suggestions??? I hope I haven't crippled my Droid by doin this.
Click to expand...
Click to collapse
You should not be wiping data when flashing a new kernel.
How does that differ from flashing it from recovery if I may ask? I figured I had done everything properly and even after just going to recovery, wiping dalvik, wiping data then flashing I keep getting the issue.
I'm actually at work at the moment and don't have access to my PC to download it. But I'll give it a shot when I get home. Luckily flashing my recovery image works just fine, I'm just stumped why now it wants to cause me grief.
Hypcrsy said:
How does that differ from flashing it from recovery if I may ask? I figured I had done everything properly and even after just going to recovery, wiping dalvik, wiping data then flashing I keep getting the issue.
I'm actually at work at the moment and don't have access to my PC to download it. But I'll give it a shot when I get home. Luckily flashing my recovery image works just fine, I'm just stumped why now it wants to cause me grief.
Click to expand...
Click to collapse
At the most, you should be wiping dalvik. You should not be wiping data when flashing a kernel. Doing so will result in the self-inflicted grief you're experiencing.
najaboy said:
You should not be wiping data when flashing a new kernel.
Click to expand...
Click to collapse
Sorry I just saw this post immediately after I replied. I thought wiping data applied for both flashing ROMS and kernels.
najaboy said:
At the most, you should be wiping dalvik. You should not be wiping data when flashing a kernel. Doing so will result in the self-inflicted grief you're experiencing.
Click to expand...
Click to collapse
^This. Only wipe dalvik, not data.
Ok I'll give it a shot while I'm here. I was flashing over to the new edition of Kings and it just became incredibly unstable when interacting with SetCPU, so I was just going to go back to the stock HTC one, that's when I got the first constant bootloop. I'll give it a shot and let you guys know what happens. Thanks for the feedback.
Yeah the reload worked this time, I don't know why it was giving me such an issue when I could have sworn it was working ok every other time I've done it before. Any reasons why I'd be getting such a hard time from Kings Kernel 6? I've seen so many rave reviews with it but everytime I have it on my phone it lasts me about ten minutes and then goes back to that same constant boot cycle.
Hypcrsy said:
Yeah the reload worked this time, I don't know why it was giving me such an issue when I could have sworn it was working ok every other time I've done it before. Any reasons why I'd be getting such a hard time from Kings Kernel 6? I've seen so many rave reviews with it but everytime I have it on my phone it lasts me about ten minutes and then goes back to that same constant boot cycle.
Click to expand...
Click to collapse
thats weird anyone else having that problem? haven't tried 6 yet
Sent from my ADR6300 using XDA App
You only need to wipe dalvik if going to and from one with HAVS, but it doesn't hurt to be safe.
Sent from my ADR6300 using XDA App
Thanks for the assistance everyone. I finally got the darn thing stable. But I'm still curious about the kings kernel 6. I was stoked to try it because I was hoping it would be stable. I was having that instability issue with 5. Anyone else know what I'm talking about???
Sent from my rooted Droid Incredible!!
Hypcrsy said:
Thanks for the assistance everyone. I finally got the darn thing stable. But I'm still curious about the kings kernel 6. I was stoked to try it because I was hoping it would be stable. I was having that instability issue with 5. Anyone else know what I'm talking about???
Sent from my rooted Droid Incredible!!
Click to expand...
Click to collapse
Not exactly. I was running 5 on SkyRaider 3.3.2 for a while, then all of a sudden I started having horrible lag while unlocking the phone and for about 7-10 seconds afterwards. Is this what you're referencing? When I switched to BFS6, I didn't have the problem. But the problem did kick in a while after install of 5 (few weeks), I didn't have 6 that long. 6 seemed pretty solid. Give 6 a shot, if you don't like it, just flash something else. Nandroid just to be safe, too.
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS4.
Yeah I always nandroid just in case when I do any serious modification, but I was experiencing the same issue with 6 as I was with 5. Just checking the different limits with SetCPU, anytime I went over 1.1 for overclocking the phone would stay on for about 15-20 seconds and then reboot, get as far as the red eye and then reboot again. That was as far as I ever got with his kernels which is unfortunate.
When testing SetCPU and overclocking, make sure you don't have set on boot enabled.
Sent from my ADR6300 using XDA App
Thanks I'll give it a shot later on.
recently, my phone has just started a habit of randomly rebooting. i was using myn rls5 with net kernel 4.3.2, but i decided to try something different in an attempt to stop the problem, so i went to mikfroyo with its default kernel. right after i startthe phone and it gets to the homescreen, it starts restarting again. i cleared data and cache between roms, and im using clockworkmod 3.0.0.5
You should always perform a full wipe, to include factory/data, when flashing a new rom.
teh roxxorz said:
You should always perform a full wipe, to include factory/data, when flashing a new rom.
Click to expand...
Click to collapse
i did. every time
ryohei47 said:
i did. every time
Click to expand...
Click to collapse
Also, the dalvik, under advanced? And not flashing a kernel with it?
I found out that Clockwork never cleared Dalvik for me. I changed to AR and after clearing the dalvik I stopped getting reboots or bootloops. Maybe your phone doesn't like the new Clockwork...
Shigster said:
I found out that Clockwork never cleared Dalvik for me. I changed to AR and after clearing the dalvik I stopped getting reboots or bootloops. Maybe your phone doesn't like the new Clockwork...
Click to expand...
Click to collapse
that could be it. everytime i install RA though, it complains and doesnt boot into recovery correctly
oohhh. that sucks. try unrooting or using a stock rom for a while. if it keeps rebooting when you browse the web, play games, anything that works the phone, then there is nothing you can do. the phone is fried. wait until it is bad enough that you can do it whenever you want by firing up a game and playing for a few minutes. then bring to the sprint store and they will replace. hah why do i have to be the person who brings the bad news?
again, try unrooting first. you can even leave s-off to re root easily. if you have no reboots, then the problem can be fixed.
i feel so bad giving this news... hah
My phone recently started doing this. Doesn't matter what ROM I'm on, doesn't matter if I un-root with a factory RUU or re-root, doesn't matter what recovery I use, doesn't matter if I completely format my SD card or boot without one. It got to the point I had to take it to Sprint and have them order me a new one.
It would randomly reboot and then go into a bootloop that not even a factory reset would cure, just decides when to stop bootlooping on its own and occasionally works.
ryohei47 said:
that could be it. everytime i install RA though, it complains and doesnt boot into recovery correctly
Click to expand...
Click to collapse
If you're using ROM Manager, don't! Download the PC36IMG.zip file from amon's thread and place it on the root of your SD card. Shutdown your device. While pressing the down arrow key, press the power button. You will then enter the bootloader screen. After a few seconds, a few lines of text will appear and the bootloader will automatically detect the. PC36IMG.zip file and prompt you to install it. Follow the prompts to install. The installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. The recovery version will be listed at the bottom of the screen. Go to the wipe menu and wipe EVERYTHING except the SD card itself then go to the flash menu and flash whatever rom you wish to flash.
Posting & replying via the XDA Premium app
awesomeindeed said:
My phone recently started doing this. Doesn't matter what ROM I'm on, doesn't matter if I un-root with a factory RUU or re-root, doesn't matter what recovery I use, doesn't matter if I completely format my SD card or boot without one. It got to the point I had to take it to Sprint and have them order me a new one.
It would randomly reboot and then go into a bootloop that not even a factory reset would cure, just decides when to stop bootlooping on its own and occasionally works.
Click to expand...
Click to collapse
Were you one of the unlucky ones who were using CM7 when the bootlooping began?
Posting & replying via the XDA Premium app
dougjamal said:
Were you one of the unlucky ones who were using CM7 when the bootlooping began?
Posting & replying via the XDA Premium app
Click to expand...
Click to collapse
No, I had already moved away from CM7 when it began. It started out of nowhere and just got worse on a daily basis.
I had also never used Unrevoked. I rooted with toast's original root method way back last August or so and was using the .76 ENG bootloader.
I had similar issues, in terms of both posts, and it got to the point that I just got it replaced from Sprint. It just progressively got worse no matter what was done. Has happened to others ... sounds like the phone might just be going.
=(
sent from my
My new phone arrived today. It's a refurb. HW 0003. Made it about 2 hours without a random reboot. Made it about another 4 before doing it again. This sucks.
awesomeindeed said:
My new phone arrived today. It's a refurb. HW 0003. Made it about 2 hours without a random reboot. Made it about another 4 before doing it again. This sucks.
Click to expand...
Click to collapse
Damn, that sucks. Is that stock, before u even rooted it? I would just take it right back to Sprint.
Sent from my PC36100 using XDA App
k2buckley said:
Damn, that sucks. Is that stock, before u even rooted it? I would just take it right back to Sprint.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yep, stock. Only apps installed are GoSMS and XDA. I guess I'll give it a factory reset and see if that fixes it, or else it's going back.
awesomeindeed said:
My new phone arrived today. It's a refurb. HW 0003. Made it about 2 hours without a random reboot. Made it about another 4 before doing it again. This sucks.
Click to expand...
Click to collapse
umm... might have been one of the 2 i got with that problem... srry!
i just hate unrooting, the whole process will end up taking a few hours. im probably gonna unroot, and if the basics work, i'll just stick with some simple z4 root and call it a day. any other options? cause htis is already my second phone, not exactly crazy about getting a third.
ryohei47 said:
i just hate unrooting, the whole process will end up taking a few hours. im probably gonna unroot, and if the basics work, i'll just stick with some simple z4 root and call it a day. any other options? cause htis is already my second phone, not exactly crazy about getting a third.
Click to expand...
Click to collapse
Unrooting take like 5 minutes...flash s-on tool, then the 5 minutes to run the ruu, then another 5 minutes to re-root.
ryohei47 said:
recently, my phone has just started a habit of randomly rebooting. i was using myn rls5 with net kernel 4.3.2, but i decided to try something different in an attempt to stop the problem, so i went to mikfroyo with its default kernel. right after i startthe phone and it gets to the homescreen, it starts restarting again. i cleared data and cache between roms, and im using clockworkmod 3.0.0.5
Click to expand...
Click to collapse
My phone never has random reboots. Never. And I have a list of roms as long as my arm that I have flashed.
HipKat said:
My phone never has random reboots. Never. And I have a list of roms as long as my arm that I have flashed.
Click to expand...
Click to collapse
There are a bunch of bad EVOs floating around. If you have this problem, you're more likely to get one of these as a refurb as they are the ones they get back. They'll replace the display, etc. But its the mobo that is probably the issue, and they don't replace that. They probably just make sure that it boots up and can make a call..
Sent from my PC36100 using Tapatalk
Ok, so last night I got my phone totally back to stock. So today I decided that stock is boring lets try CM10! I followed all the instructions for my phone a SGH-989D to a tee. The phone boots up and displays the CM Circle logo and just sits there spinning away forever. It's quite pretty really, but the functionality seems to be a little lacking. Any idea how to get past this? I have pulled my battery and factory wipe/ deleted cache / wiped dalvik already. And yes, when I get home I can wipe back to total factory, but I would like to give CM10 a try if possible. Thank you for your time!
My first question would be how long are you waiting? First boot after a clean flash will take a long time. If you've waited more than an hour, then you might have a problem.
What recovery are you using? If cwm, try using darksidecachewipe zip before you reboot to system.
Sent from my cm_tenderloin using xda app-developers app
KaneHusky said:
My first question would be how long are you waiting? First boot after a clean flash will take a long time. If you've waited more than an hour, then you might have a problem.
Click to expand...
Click to collapse
Yeah I waited like 30 min ish, which is way longer than any other ROM i have used. I had all sorts of issues afterwards as well just getting it back to stock. I am now on ICS stock ROM for Telus atm, maybe I'll try the stable CM10 over Christmas break when my phone is not so important. Was annoying being at work all day and having it now work...lol
i installed the new moar. clean install. now it runs fine. battery life is great. but i have a big issue. for some reason it sometimes just goes to the bootloader and freezes up. have to gett back into recovery and reflash to get passed the bootloader again. done this mutiiple times so far. not running anything crazy either just some texts and phone calls. please if there a way to fix or something im not doing. please let me know. thanks.
yotaking said:
i installed the new moar. clean install. now it runs fine. battery life is great. but i have a big issue. for some reason it sometimes just goes to the bootloader and freezes up. have to gett back into recovery and reflash to get passed the bootloader again. done this mutiiple times so far. not running anything crazy either just some texts and phone calls. please if there a way to fix or something im not doing. please let me know. thanks.
Click to expand...
Click to collapse
What do you mean it goes into the bootloader. Need some specifics of precisely what you mean. And what do you mean by bootloader, are you talking about recovery or download mode?
Sent from my SPH-L710 using Tapatalk 2
GiantJay said:
What do you mean it goes into the bootloader. Need some specifics of precisely what you mean. And what do you mean by bootloader, are you talking about recovery or download mode?
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
I believe they means the boot animation. Unless I'm mistaken, they're getting stuck in a bootloop. I'm really interested in which Kernel option they chose when installing it. I'd say that choosing a different one would fix the bootloop issues (I tried the optimized stock one recently and that seemed to work well).
I'd suggest that the next time it happens go into recovery and clear cache and dalvik cache. Reboot phone and see if that fixes the problem (give the phone time to boot up after clearing cache). If that doesn't work, you can try fixing permissions in Recovery (I doubt that'd fix a bootloop, but it might be worth trying).
Finally if none of the above work, I'd try downloading the MOAR rom again, but double-check md5 sums to make sure it's a good download. When installing it, start with the stock kernel and see if it occurs again.
I was on Tweaked 1.0 and was loving every minute of it. Until i heard that we had just got new kit kat roms. So i made a back up and proceeded to install the new Liquid. Coming from Note 2, It felt like I was in AOSP heaven again. But needless to say i shouldn't have been so excited for a alpha build just yet. A couple of things i needed weren't working just yet so i went back into twrp and wiped everything. Once i had restored my tweaked backup i booted up and it started constantly boot looping. So this is what i did. I wiped everything again (including system) and just flashed the tweaked rom. It kept loading up over and over to a screen that said "Process System is not responding, Close it?" So i wiped again and re-flashed the Liquid and i got nothing. Lastly i grabbed the Stock MI7 md5 and flashed it with odin three times. It finishes every time, but still the same system error when booting up. Can anyone please help me fix my phone. All help is much appreciated.
Man I'm telling you the smarter the phones are becoming the more problems it gives us. I used to be a flashaholic back on the note 2 now with the note 3 I had a brickloop out of nowhere. I'm freaked as to flash things unto my rom for real
Sent from my SM-N900T using xda app-developers app
Precisely
Exactly what i mean. With my Note 2 i flashed very frequently, but almost never had problems like these. I'm also glad to hear i'm not the only one whose had those random brickloops. It doesn't seem to matter what rom it is. Everything goes fine for a good while then out of nowhere, constant rebooting. I think if I can fix my phone this time i'm gonna just go stock rooted
treytreytaylor said:
Exactly what i mean. With my Note 2 i flashed very frequently, but almost never had problems like these. I'm also glad to hear i'm not the only one whose had those random brickloops. It doesn't seem to matter what rom it is. Everything goes fine for a good while then out of nowhere, constant rebooting. I think if I can fix my phone this time i'm gonna just go stock rooted [/QUOT
If you read through the forum for the note 3 this is a common problem after a restore of the efs partition on older twrp editions. flash this to fix
Click to expand...
Click to collapse
Ill flash roms and mods to my hearts content.. One thing you won't catch me doing its restoring a backup. Hell I won't even make a ⊼ nandroid .. Lol
sent from my ??????? note 3?
treytreytaylor said:
I was on Tweaked 1.0 and was loving every minute of it. Until i heard that we had just got new kit kat roms. So i made a back up and proceeded to install the new Liquid. Coming from Note 2, It felt like I was in AOSP heaven again. But needless to say i shouldn't have been so excited for a alpha build just yet. A couple of things i needed weren't working just yet so i went back into twrp and wiped everything. Once i had restored my tweaked backup i booted up and it started constantly boot looping. So this is what i did. I wiped everything again (including system) and just flashed the tweaked rom. It kept loading up over and over to a screen that said "Process System is not responding, Close it?" So i wiped again and re-flashed the Liquid and i got nothing. Lastly i grabbed the Stock MI7 md5 and flashed it with odin three times. It finishes every time, but still the same system error when booting up. Can anyone please help me fix my phone. All help is much appreciated.
Click to expand...
Click to collapse
Don't restore jack. No recovery is right as of yet for this. Phones are very temper mental
NOTE 3
BACARDILIMON said:
Don't restore jack. No recovery is right as of yet for this. Phones are very temper mental
NOTE 3
Click to expand...
Click to collapse
second to last release of twrp (2.6.3.7) says it fixed the efs back-up does this not address the back up issue?
slamindamalibu said:
second to last release of twrp (2.6.3.7) says it fixed the efs back-up does this not address the back up issue?
Click to expand...
Click to collapse
I know they said that bit it did for a few. Just don't trust me been thru it
NOTE 3
Lesson learned. No more backing up with twrp. I was fine with good ol' Titanium Backup. But anyways, found a fix for this. Took a couple minutes.
http://forum.xda-developers.com/showthread.php?t=2471421
treytreytaylor said:
Lesson learned. No more backing up with twrp. I was fine with good ol' Titanium Backup. But anyways, found a fix for this. Took a couple minutes.
http://forum.xda-developers.com/showthread.php?t=2471421
Click to expand...
Click to collapse
That fix works but has also failed me. Just try and not use backups
NOTE 3
treytreytaylor said:
Lesson learned. No more backing up with twrp. I was fine with good ol' Titanium Backup. But anyways, found a fix for this. Took a couple minutes.
http://forum.xda-developers.com/showthread.php?t=2471421
Click to expand...
Click to collapse
the file i attached is just a script that does exactly this flashed through recovery.
What about CWM?
Sent from my SM-N900T using xda app-developers app
BACARDILIMON said:
Don't restore jack. No recovery is right as of yet for this. Phones are very temper mental
NOTE 3
Click to expand...
Click to collapse
I have restored multiple multiple backups already on twrp latest and more recently with cwm.. So they are pretty solid guys.. I do have the brickloop fix on SD though.. Thanks to twrp,, and Just in case I need it again.
Sent from my SM-N900T using Tapatalk
jdidtht said:
I have restored multiple multiple backups already on twrp latest and more recently with cwm.. So they are pretty solid guys.. I do have the brickloop fix on SD though.. Thanks to twrp,, and Just in case I need it again.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
I have used both and they both are the same. But do a restore and if ur phone likes it ur ok if not then u get boot loop or brick. As long as he knows it it is his gamble to make
NOTE 3
i was using jedi rom then i tried to flash darthstalker romnow i'm stuck in a boot loop and when it does finally boot it says process system isn't responding, if i choose wait i get the drop down menu with toggles and that's it rest of the screen is black if i hold power button i get power off or reboot option only. if i choose close it goes into a boot loop. haven't got anything that's been able to fix it yet. help pls
Yea this happened to me a couple of days ago. Im done restoring from backups now.
Sent from my SM-N900T using Tapatalk