I rooted it and installed OMNI rom but am finding that when I go to reboot the phone it hangs on the 5 second screen until I forcibly shut it off and turn it back on. It doesnt matter if its from the rom into recovery or from recovery back to the rom. It always hangs. Does anybody have any idea how to fix this?
Edit: the title should be Not CLEANLY Rebooting
I just tried wiping cache(s) and system then reinstalling OMNI and gapps, rebooting to recovery (which worked fine) and installing SuperSU but on the next reboot to system its currently hanging on the Robin screen again.
And now the touchscreen is flaking out. The phone is going back.
kevria said:
I rooted it and installed OMNI rom but am finding that when I go to reboot the phone it hangs on the 5 second screen until I forcibly shut it off and turn it back on. It doesnt matter if its from the rom into recovery or from recovery back to the rom. It always hangs. Does anybody have any idea how to fix this?
Edit: the title should be Not CLEANLY Rebooting
Click to expand...
Click to collapse
Ok, your issue is not a thing. What it does, after the five seconds, is sticks at that screen. It still boots up though, just takes 5 seconds longer.
I had left the phone sitting there for over 5 minutes without it doing anything but this is moot since I returned the phone because of a slew of issues with it.
Boot crash omni-7.1.2-20171018-ether-WEEKLY - NEXTBIT
Using the omni-7.1.2-20171018-ether-WEEKLY on a brand new, out of the box Nextbit Robin. I followed the install process to the letter, the device boots to the OMNI animation, then a series of error screens pop up. Clicking through the successive screens, it is evident that there are 3 errors are looping. One is GUI, and I did not note the others.
Had I done something wrong? or does this ROM have issues with the Robin?
You should probably post in the Omni thread for better visibility. Try checking the md5sum of your download, might be corrupt. Are you flashing anything else at the same time as the Omni zip? Gapps, SuperSU?
WoodenMind said:
You should probably post in the Omni thread for better visibility. Try checking the md5sum of your download, might be corrupt. Are you flashing anything else at the same time as the Omni zip? Gapps, SuperSU?
Click to expand...
Click to collapse
Thanks for the suggestion, I will repost in Omni.
I had loaded Magisk first, but not in the install manifest.
I had included the MD5 and the MD5 validated during install from the zip.
I loaded Paranoid Android as a sanity check, and this worked. Presently running PA although I would like to try omni..
I appreciate your prompt response and recommendation.
Thanks again
Related
I was flashing the newest cm10 as I do every few days. I flash that, then inverted apps, then kernel, then reboot and never had a problem. Now I am getting a blank screen after the "Samsung Galaxy SIII" splash with the button back-lights lit. Nothing else happens, no response. Never had an issue, but now I am worried. Any help here?
EDIT: I tried booting into recovery a few times with no success. Just tried it again and held all 3 buttons past the recovery flash on the top of the screen. Booted into that and re-flashed the update by itself. Phone just booted back up. Not sure what happened, but all is well in my s3 land again.
Usually not a good idea to flash a ROM and kernel at the same time. I know you said that that's the way you've been doing it buuuut....what happened to your phone is the symptom of your phone trying to match up a ROM and separate kernel at the same time, it got confused while booting lol. Best practice it ROM, gapps, reboot system let phone fully boot, reboot recovery and install kernel. Its an extra step but usually avoids what happened to you.
If your using ktoonsez kernel he has a special build for the latest nightly for people with the same problem as yours, it's not in the op, start from the end of the thread and work backwards.
Sent from my SGH-I747 using Tapatalk 2
Hello! I'm trying to update my Kindle Fire (orig) from Jandycane 1.8 to JB4.2. I've gotten into TWRP and made a backup, then did the factory reset and flashed the Jelly Bean zip file. It appears that I'm stuck partway through that flash, so I was hoping to get some help. Here's the text of the screen output:
Formatting Data using make_ext4fs...
Done.
Formatting Cache using make_ext4fs...
Done.
Using rm -rf on .android_secure
Updating partition details...
Installing '/sdcard/jb-4.2-kfire-hashcode-12-18.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Updating partition details...
And that's where I'm stuck - it's been sitting at this one particular point for about an hour now. I haven't gotten the normal "Success" message across the top, and I still see the three big buttons at the bottom ("Wipe Cache/Dalvik", "Home", and "Reboot System"). It's not completely frozen since I can scroll back up through the TWRP command history, but it's not moving forward. I know sometimes a flash takes some time, but it's never taken this long to flash the ROM before (I've done it a handful of times with previous versions of Jandycane), so I think it's clear something is wrong. But, I'm reluctant to start pushing buttons at random. Anyone have any ideas?
Thanks!
***UPDATE***
I got impatient and backed away from the previous screen, then tried repeating the wipe/flash process. I get the same result every time - it just hangs, with no success message. I verified the MD5 of the file on my Windows laptop prior to copying it onto my KF, but now that I've wiped it I don't know for sure how to verify it on the KF itself (or if I even need to). Upon rebooting, I see the default boot animation (I believe from Jandycane, if I recall correctly), but it never actually boots up. At this point I'm planning to let the animation go overnight, and see if it eventually completes and boots up. I'd welcome any guidance or suggestions anyone might have...
***UPDATE #2***
It never booted, so I started the process over again. Now I'm getting a "Status 7" error every time I try to flash. I have done multiple factory resets and wiped cache/Dalvik, but still getting the Status 7 error. A bit of searching makes it look like the error may be the result of a problem with TWRP...? I started this process on v2.3.1.1, but have now flashed the recovery back to 2.2.2.1. Unfortunately...now I can't boot at all. After flashing the recovery image, I'm stuck on the opening screen with the "Kindle Fire" across the middle and "Booting..." at the bottom. If I hold the power button down for 10 seconds to force a shutdown and then power it back on, my Windows Device Manager shows the "Android ADB Interface" for about 1.5 seconds, then it goes away again. It appears I'm now in limbo. Help, anyone?
What recovery (version) are you using?
What partitions are you wiping before attempting to install a ROM?
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
What recovery (version) are you using?
What partitions are you wiping before attempting to install a ROM?
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
I started with v2.3.1.1, but have now flashed the recovery to 2.2.2.1. I'm not wiping any particular partitions - just using the TWRP commands to do the factory reset and wiping of cache and Dalvik cache. At the moment, I cannot even get back into TWRP, though. Just stuck on the booting screen.
Okay, looks like I am now back in fastboot mode. I unplugged the KF for a couple minutes, then issued the command "fastboot -i 0x1949 oem idme bootmode 5001" and plugged it back in. It picked up the device as soon as it came up, and now appears to be waiting for additional adb commands. Don't know if that helps anything or not.
It looks like I can boot into mode 4000, 4002, or 5001, but can't get anywhere after that - anytime I try to reboot it goes back into the endless booting loop. I'm not sure what to try from the fastboot prompt to get past the booting loop and back to TWRP where I can install a functional ROM. Any ideas?
Ah-ha! I tried flashing TWRP 2.3.3.1, and it came right up. The endless booting loop must have been related to the TWRP version. I'm going to try wiping everything again and reinstalling the JB ROM now...
And, now we've come full circle back to the original problem - no success message, hung on "Updating partition details...".
I'm out of ideas. Restored back to previous Jandycane ROM.
I'd still like to make this upgrade work, though, so if anyone has some suggestions on what went wrong (or what I did wrong), I'd really appreciate it. Thanks!
Uncheck the "rm -rf" option in TWRP and try again.
Also, be sure to wipe system and factory reset.
"That's a special kind of stupid. The kind that makes me laugh."
Any update on this problem carl? I kinda sorta have the same issue... sort of.
guruizzy said:
Any update on this problem carl? I kinda sorta have the same issue... sort of.
Click to expand...
Click to collapse
I haven't tried it again yet. I might give it another shot this weekend, though. I'll be sure to come back and update when I do.
"Status 7" error when flashing jellybean
I don't know if i'm doing anything wrong but I can't seem to flash any jellybean roms. I always get Status 7 error. I do all wipes before installing. Any ideas?
More info:
FFF V1.4a
TWRP V2.2.2.1
CM7
mist8rioso said:
I don't know if i'm doing anything wrong but I can't seem to flash any jellybean roms. I always get Status 7 error. I do all wipes before installing. Any ideas?
More info:
FFF V1.4a
TWRP V2.2.2.1
CM7
Click to expand...
Click to collapse
I've had the same issue before and it was fixed with a reboot. Have you tried that.
yes, I have tried reboot after wiping/ before flashing but still get the error. Very frustrating.
FYI...I'm rethinking this flash. The primary motivation for doing it was because I was suddenly having charging and performance issues. I finally figured out that the cause was a faulty power cord. Now that I've replaced it, things are working fine (and class has started up again), so I probably won't mess with it. Just didn't want to leave anyone hanging.
CyanogenMod version: 11.0-InstallerXNPQ09Q
Hello, I just installed CM on my S3 via the one-click install. Now I have problems powering off or rebooting my phone. I select "Reboot" from the power menu, and click OK. Then it hangs displaying the "Reboot phone" window, displaying the busy animation and saying "Rebooting...". Power off does much the same thing. Is there any solution to my problem? I have to take the battery out to shut the phone down. Once turned off, it starts up just fine.
Sometimes, though, the phone restarts properly. I don't know what would make the difference.
I recommend flashing a custom recovery and flashing cm11 from recovery after doing a full wipe.
audit13 said:
I recommend flashing a custom recovery and flashing cm11 from recovery after doing a full wipe.
Click to expand...
Click to collapse
That's what I ended up doing. I've been running it now several days and everything is working fine. I should have done that in the first place, oh well. The installer sure didn't leave a good impression on me, but now that I have successfully installed CM and it is working, I love it!
I upgraded to MM back the beginning of the month, tripped my Knox bit (I had rooted via PingPong root on Lollipop), but I was eager to go to MM and try Xposed so I could improve the horrible battery life.
I had the system working fine, rooted using CFAR, and no problems. Randomly, about a week ago, it just "lost" root. I wasn't sure why, and CFAR from Odin wouldn't bring it back. I did a flash with SuperSU in TRWP yesterday and it worked, and I did a NANDroid backup, saved it to my computer, and installed Xposed... On a stock ROM.
And my phone has been a continuously rebooting brick ever since, no matter what I do.
So, I've tried everything I can think of. Because my data was completely backed up, I did a complete wipe, and nothing. I tried flashing the Xposed-uninstaller.zip and that supposedly worked, but the phone reboots about 53 seconds after it starts up, continuously, no matter what.
I've tried the default MM firmware, tried letting it go through it's paces on its own (but it just reboots every 53-57 seconds), and also tried with a fresh clean default MM ROM, which does dump TRWP, then restart into the default bootloader, have it dump the cache and do a complete re-wipe, and nothing. Still restarts.
With the stock MM firmware load, the first boot it always stops at 32%, reboots, and when it comes back up it sometimes makes it through "optimizing xx of 30 applications" but always reboots and comes back to it over and over, ad infinitum. Sometimes it makes it to 30, usually it doesn't, but it always fails, reboots, and comes back to the same menu on a stock ROM.
ADP and MTP in TRWP work fine, and all my data is backed up. So, I'm willing to do anything to the device; nothing left on it to care about (I already tried NAND erase in Odin and format partitions in TRWP). It still continuously reboots at around 53 seconds.
I've also tried custom ROMs loaded up from TRWP (Renegade 1.1 and TeamSPR V3). They apparently load - everything looks/works great from inside TRWP - then invariably they reboot at about the 53 second mark. Can't even get Renegade past the boot screen.
Nothing was done hardware-wise to break it; the Knox bit flipped three weeks ago, and the SuperSU upgrade had been working fine. The action that killed it was attempting to install the Xposed framework on a default ROM that only had SuperSU installed. But I've since installed a default ROM and ran the Xposed uninstall to no avail. The uninstall Zip in TRWP gave all the right responses that it worked, but it still rebooted 53 seconds after restart. Continuously.
I don't even know how to go back to Lollipop because attempts to load G920PVPU1AOCF in Odin gives me an immediate failure of "SW REV. CHECK FAIL. DEVICE: 3, BINARY: 1," so downgrading appears to be out of the question.
Someone has to have seen something like this before or there's something I'm missing. About the only thing I can think of is to try a custom ROM install and force the Xposed framework again without even letting it boot up (because it won't anyway) from a TRWP install. I'm going to attempt that while hopefully someone else comes up with ideas for me...
rebooting
people have had luck letting their phone battery die completely and rebooting after charging just a little bit. make sure its completely discharged before rebooting
zee3are0 said:
I upgraded to MM back the beginning of the month, tripped my Knox bit (I had rooted via PingPong root on Lollipop), but I was eager to go to MM and try Xposed so I could improve the horrible battery life.
I had the system working fine, rooted using CFAR, and no problems. Randomly, about a week ago, it just "lost" root. I wasn't sure why, and CFAR from Odin wouldn't bring it back. I did a flash with SuperSU in TRWP yesterday and it worked, and I did a NANDroid backup, saved it to my computer, and installed Xposed... On a stock ROM.
And my phone has been a continuously rebooting brick ever since, no matter what I do.
So, I've tried everything I can think of. Because my data was completely backed up, I did a complete wipe, and nothing. I tried flashing the Xposed-uninstaller.zip and that supposedly worked, but the phone reboots about 53 seconds after it starts up, continuously, no matter what.
I've tried the default MM firmware, tried letting it go through it's paces on its own (but it just reboots every 53-57 seconds), and also tried with a fresh clean default MM ROM, which does dump TRWP, then restart into the default bootloader, have it dump the cache and do a complete re-wipe, and nothing. Still restarts.
With the stock MM firmware load, the first boot it always stops at 32%, reboots, and when it comes back up it sometimes makes it through "optimizing xx of 30 applications" but always reboots and comes back to it over and over, ad infinitum. Sometimes it makes it to 30, usually it doesn't, but it always fails, reboots, and comes back to the same menu on a stock ROM.
ADP and MTP in TRWP work fine, and all my data is backed up. So, I'm willing to do anything to the device; nothing left on it to care about (I already tried NAND erase in Odin and format partitions in TRWP). It still continuously reboots at around 53 seconds.
I've also tried custom ROMs loaded up from TRWP (Renegade 1.1 and TeamSPR V3). They apparently load - everything looks/works great from inside TRWP - then invariably they reboot at about the 53 second mark. Can't even get Renegade past the boot screen.
Nothing was done hardware-wise to break it; the Knox bit flipped three weeks ago, and the SuperSU upgrade had been working fine. The action that killed it was attempting to install the Xposed framework on a default ROM that only had SuperSU installed. But I've since installed a default ROM and ran the Xposed uninstall to no avail. The uninstall Zip in TRWP gave all the right responses that it worked, but it still rebooted 53 seconds after restart. Continuously.
I don't even know how to go back to Lollipop because attempts to load G920PVPU1AOCF in Odin gives me an immediate failure of "SW REV. CHECK FAIL. DEVICE: 3, BINARY: 1," so downgrading appears to be out of the question.
Someone has to have seen something like this before or there's something I'm missing. About the only thing I can think of is to try a custom ROM install and force the Xposed framework again without even letting it boot up (because it won't anyway) from a TRWP install. I'm going to attempt that while hopefully someone else comes up with ideas for me...
Click to expand...
Click to collapse
Stick it in Odin mode and let it die, once it gets to the point where you cannot turn it on anymore, it's good :good:
1619415 said:
Stick it in Odin mode and let it die, once it gets to the point where you cannot turn it on anymore, it's good :good:
Click to expand...
Click to collapse
I just let it go through the boot loop all night...
AND IT TOTALLY WORKED!
Thanks to both you and wright0101!
zee3are0 said:
I just let it go through the boot loop all night...
AND IT TOTALLY WORKED!
Thanks to both you and wright0101!
Click to expand...
Click to collapse
NP, glad it worked:good:
So my phone has been perfect for over a year. Within the first month of owning it I rooted, installed TWRP, and jumped on CM13. Been updating nightlies all year long once every week or so and enjoying the phone. Its really been perfect. Tonight after work I jump in my car, throw it on my car charger, and drive home. When I get home I notice for some reason I have no cell service (Emergency Call Only) so I reboot. That was the end. The reboot got stuck on the CM boot screen flashing the circle out around the CM face over and over and over. So, I pop the battery, try again, same thing.
Well, being that I have rooted and flashed for years now I figured Id wipe dalvik and cache. Tried that, same thing. Did a full wipe and reinstalled the nightly from my SD card. This time I thought I made progress as it set up all the apps. Then it just hangs on "starting apps" and then it sits there forever. Never boots. Doesnt loop or restart or anything, just says its starting apps.
So, jump on here and find the bootloop issue. My serial is 505x so I was wondering if maybe thats my issue. Decide to download the all in one flash zip from here...
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
and I flash that. Stock rom works without any issue. Fired it up, logged in, no problems. Huh. Do a restart and even though I flashed that file it still shows bootloader unlocked as the LG logo comes up, and boots into TWRP as normal as well. Figured well I flashed a stock rom, lets give CM13 a try again. I download a fresh nightly through my pc and transfer it over via usb so I know its good. Full wipe, flash, reboot, hangs at "starting apps" again.
Now I am lost. The stock rom sucks and my love for this phone is based around what it is with CM installed. Am I missing something here? I really want to get back to CyanogenMod and away from the clunky slow stock rom.
Any input is greatly appreciated. Thank you all.
EDIT: Well went through the Android setup steps after flashing the stock rom so I would have a phone until this was all figured out. Turned out its not working. After setup I am not getting "Process System Isn't Reponding: wait or close" No matter what I do the phone is so slow or laggy I cant use it. Its trying to download my apps and restore my phone from my Google account but it just hangs up. No idea what to do at this point. Is my kernel messed up? Its a totally clean flash. What the heck. 3am, I give up, hopefully someone has insight in the morning. Thank you all.
ride1226 said:
So my phone has been perfect for over a year. Within the first month of owning it I rooted, installed TWRP, and jumped on CM13. Been updating nightlies all year long once every week or so and enjoying the phone. Its really been perfect. Tonight after work I jump in my car, throw it on my car charger, and drive home. When I get home I notice for some reason I have no cell service (Emergency Call Only) so I reboot. That was the end. The reboot got stuck on the CM boot screen flashing the circle out around the CM face over and over and over. So, I pop the battery, try again, same thing.
Well, being that I have rooted and flashed for years now I figured Id wipe dalvik and cache. Tried that, same thing. Did a full wipe and reinstalled the nightly from my SD card. This time I thought I made progress as it set up all the apps. Then it just hangs on "starting apps" and then it sits there forever. Never boots. Doesnt loop or restart or anything, just says its starting apps.
So, jump on here and find the bootloop issue. My serial is 505x so I was wondering if maybe thats my issue. Decide to download the all in one flash zip from here...
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
and I flash that. Stock rom works without any issue. Fired it up, logged in, no problems. Huh. Do a restart and even though I flashed that file it still shows bootloader unlocked as the LG logo comes up, and boots into TWRP as normal as well. Figured well I flashed a stock rom, lets give CM13 a try again. I download a fresh nightly through my pc and transfer it over via usb so I know its good. Full wipe, flash, reboot, hangs at "starting apps" again.
Now I am lost. The stock rom sucks and my love for this phone is based around what it is with CM installed. Am I missing something here? I really want to get back to CyanogenMod and away from the clunky slow stock rom.
Any input is greatly appreciated. Thank you all.
EDIT: Well went through the Android setup steps after flashing the stock rom so I would have a phone until this was all figured out. Turned out its not working. After setup I am not getting "Process System Isn't Reponding: wait or close" No matter what I do the phone is so slow or laggy I cant use it. Its trying to download my apps and restore my phone from my Google account but it just hangs up. No idea what to do at this point. Is my kernel messed up? Its a totally clean flash. What the heck. 3am, I give up, hopefully someone has insight in the morning. Thank you all.
Click to expand...
Click to collapse
You really have to investigate by adb. Look into the dmesg output and logcat as well. Maybe your sdcard is corrupt or 100 other issues are possible as well. What device do you own? H811? unlocked?
.
I have rooted my lg g4 h811 and am trying to flash cm 14, after flashing it through twrp, my phone stuck in bootloop. i try o put it in recovery but it only gives me factory reset option which i did several times but still stuck on bootloop. what should i do?
kunate said:
I have rooted my lg g4 h811 and am trying to flash cm 14, after flashing it through twrp, my phone stuck in bootloop. i try o put it in recovery but it only gives me factory reset option which i did several times but still stuck on bootloop. what should i do?
Click to expand...
Click to collapse
There are several users reporting that the latest cm version bootloop the best option is to start in download mode and Flash with LGUP Stock ROM.
You could also try to boot into Download Mode and then flash the latest twrp and then Boot into Factory Reset Mode again