I've always been curious about this, So I figured I'd ask. I know 'Hot Reboot' restarts the framework so then what does a normal 'Reboot' do?
Which would you prefer? Which have u seen better results with???
Hot reboot is a faster version of a reboot
they do pretty much the same thing
tho i believe a reboot completely shuts off first.
I would say a hot reboot is plenty good.
Hot reboot reboots only the android shell. I.e. software only. Reboot reboots software and hardware.
Related
Hi all.
Basically wondering if there are any stock leaked GB roms that have fast boot? And as a part of this inquiry, I was wondering what it is that makes them fast boot, is it the ROM itself, the kernel, the recovery etc?
Rory
I believe all Sense ROMs have fast boot (you mean the thing similar to hibernate, yes?) since it is a part of the ROM.
I know the LeeDroid has a hot reboot, which boots faster than the normal reboot, however I don't think it's as fast as the fast reboot from stock rom.
Enjoy! said:
I know the LeeDroid has a hot reboot, which boots faster than the normal reboot, however I don't think it's as fast as the fast reboot from stock rom.
Click to expand...
Click to collapse
Hot reboot is not quite the same thing as fast boot. Fast boot is kinda like hibernate, it saves the current state and puts the phone in a sleep mode.
Hot reboot on the other side just makes the phone reboot faster, since it doesn't shut it down but merely restart the OS.
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
This is the hspa version.
svntsvn said:
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
Click to expand...
Click to collapse
The android icon you're referring to sounds like the stock recovery. In order to flash a ROM (even stock) from recovery mode, you'll need to load a custom recovery. This requires the device to be unlocked.
Not very often a stock setup needs to be restored. Generally, with the stock setup, only the /data partition is wiped (revert to factory default) and the issues are cleared. Not sure why a stock setup would need to be restore.
If you're still going to pursue reloading the system, without access to the normal android mode, the best route will be using fastboot. This can be done on a mac and the fastboot commands should be the same.
Hope that helps get a start!
This happened me earlier. I was able to factory reset it, which, unfortunately really annoyed me because I hadn't saved a backup..
Before the "Google" logo shows up, press and hold the power button and the volume up and down buttons.
Then go into recovery mode using the volume buttons.
When it reboots, you get that Droid with the hazard sign (which I know you're at, but just for the sake of others who need help) all you have to do is hold down the power button and WHILE it's held, press the volume up or down button and move to "Factory Reset". When you hold down the power button and press the volume rocker, a little menu will appear. It should only take a few minutes then.
Hope this helps. Apparently this is a WiFi issue. I'll definitely be keeping backups as of now..
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
svntsvn said:
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
Click to expand...
Click to collapse
I had the exact same problem happen last night with UI crashing and then the getting stuck at the boot animation. I was desperately searching online, looking to find a solution that didn't involve rebooting to factory setting and came across this post and did exactly what you did and it WORKED, very strange, I really wanna know what caused that!!!!
I've had the same problem with my Galaxy Nexus. I received it on December 21st, with stock 4.0.1 build. No root or unlock attempt at any time. On January 2nd I experienced this problems (UI process crash, screen not responding, reboot and stuck in boot animation).
The only solution was to do a factory reset and start over.
On January 10th same problem, same solution. Second factory reset.
I got the 4.0.2 OTA just two days after that. I thought that would resolve the problem. The phone seemed more stable, with less FC's and no trace of the UI crash. Indeed it lasted long...
Exactly until January 24th when I picked up the phone and seemed in the sleep of dead. Removed the battery, restarted the phone... and stuck in the boot animation.
Do you have any advice? Should I return the phone? Aside from those specific problems I am quite happy with the SGN and Android 4 in general. And I use it quite a lot (I have a very long train commute) without other problems.
Again...
It happened again!!
I don't know what to do anymore, this is not a usable phone when I have to reinstall and reconfigure every 3 weeks.
I may have found the problem
Well, not me exactly, but this bug report seems to fit the problem and the charging workaround. Seems to be a problem the file used to store the battery stats and draw the charge graph.
It also fits my usage (I try not to charge it up until 100%).
I can't post links to the forum, the issue is id number 24518 which you can find in code.google.com/p/android/
I run a rooted SG S3 on stock 4.1.1 with an old 3.0.56 kt747 kernel
Until recently, I've been running this set up for years without any problems.
I've also updated fairly recent CWM along with the latest SU.
As the title states, my phone has been turning off automatically. After weeks of troubleshooting, I noticed a pattern.
When I press the power button, there are three different scenarios that happen.
The phone goes to sleep normally
The phone goes to sleep and immediately wakes up to the lock screen
The phone displays the shut off menu
If scenario 1 occurs, everything is fine and runs perfectly for an indefinite amount of time until i attempt to put the phone to sleep again.
but, if scenario 2 or 3 occurs, the phone automatically shuts down abruptly, within 1-5 seconds.
This problem still occurs even when I boot into safe mode, and I have eliminated the SD card as a suspect. Furthermore, booting the phone up has become extremely difficult. The boot would sometimes crash after the samsung logo, after the splash screen, or during the boot animation. It takes somewhere around 3-5 tries to fully boot up the phone.
Booting into CWM recovery is still possible, but even that sometimes crashes mid-way. I've also noticed that at certain times, when I click the power button to select an action in CWM, it actually double clicks (thankfully CWM is tolerant to that) and cancels the action I was trying to do. I've done some googling and found that an over sensitive power button is a common occurrence in this model, and while that may explain why the 3 different power button scenarios occur, it still doesn't explain the crash.
Finally, I seemed to have remedied the automatic shut off problem several times by wiping cache from CWM. When I first started having these problems and began troubleshooting, wiping the cache eliminated the problem for about a week before the problem came back. When it did, I uninstalled some apps and re-wiped the cache which eliminated the problem again for several days. However, these periods become shorter and shorter, and now wiping cache does not seem to help at all. I've also tried wiping the delvik cache, but it didn't help.
I'm stumped right now. Any suggestions would be appreciated before I try some more large-scale attempts such as resetting my phone or taking it apart. Thanks everyone!
This definitely fits more in your large-scale attempts category, but it is what I'd try.
I'd grab the stock 4.1.1 firmware from sammobile.com and Odin back to stock. You're fortunate to be on the old firmware, so you can Odin back to stock. When Odin completes successfully, pull battery don't let the phone reboot normally (untick auto reboot in Odin). Boot straight into the stock recovery and do a full wipe. Then reboot your phone normally.
Doing this will correct any problems that exist with your internal storage to the extent possible. If you've still got problems after doing this, it is probably a hardware issue.
jason2678 said:
This definitely fits more in your large-scale attempts category, but it is what I'd try.
I'd grab the stock 4.1.1 firmware from sammobile.com and Odin back to stock. You're fortunate to be on the old firmware, so you can Odin back to stock. When Odin completes successfully, pull battery don't let the phone reboot normally (untick auto reboot in Odin). Boot straight into the stock recovery and do a full wipe. Then reboot your phone normally.
Doing this will correct any problems that exist with your internal storage to the extent possible. If you've still got problems after doing this, it is probably a hardware issue.
Click to expand...
Click to collapse
Yeah, that's part of the reason why i didn't want to upgrade the bootloader for the newer firmwares. I messed around with my phone this morning and its been avoiding the problem ever since. Not exactly sure what I did though lol. Thanks for the reply, I'll try it if the problem comes back over the next few days.
Your phone isn't "crashing," your power button is malfunctioning. The fix is pretty easy. You will need to open your phone up and scrape it off (the phone can be turned on without it). There are youtube videos that show how to remove it.
Hello,
I've recently realize something strange with my m8 although it is not a recent issue. Whenever the i try to hot reboot my phone, the phone would not start up. However, the manual reboot is fine. So whenever an app requires hot reboot, I have to force the phone to shut down and boot again. Any ideas as to why?
Thank you
Xplained
I know flashing roms are easy. But it might be difficult for newcomers like me. I have always a question in mind what'll happen if my phone shut down due to low battery in fastboot/recovery. If I format the OS before shutdown, is it possible to charge the phone offline without no OS then continue flashing roms?
##Following things happened with me.
I was in MIUI 12.5. I installed Pixel Recovery to flash PE12 via adb sideload. Then I cleared all data/cache. When I tried to update the rom by sideload, it didn't work. I wanted to search the internet and as it would take time, I tried to turn the phone off. I couldn't even shut the phone to save battery. Whenever I pressed power button, instead of shutting down, it always took me to the bootloader menu. Thats when I thought about this question.
that question is so out of the box, i doubt anyone can give you an answer with proof
but yes, i believe it is possible to charge even without OS and no, i dont have any proof to back this up
That's why you need to charge phone first at least until 50% up before flashing any rom.. otherwise if still happen phone shutdown while flashing, yes you still can recover as long your phone bootloader still at unlocked stats also phone still can go into fastboot
If it shuts down when in fastboot/recovery because the battery is empty, you simply charge it and reboot, that should cause no harm. Shutting down while flashing a ROM however is a totally different story. You might get lucky and be able to boot the phone back into fastboot/recovery or you could end up with a paperweight.
jadephyre said:
If it shuts down when in fastboot/recovery because the battery is empty, you simply charge it and reboot, that should cause no harm. Shutting down while flashing a ROM however is a totally different story. You might get lucky and be able to boot the phone back into fastboot/recovery or you could end up with a paperweight.
Click to expand...
Click to collapse
I did shutdown the phone within fastboot to cancel flash all and lock....then booted in forced fastboot end flashed with flash all to not lock the bootloader....and had no prob....! I think those partitions are protected against those scenarios....
Following things happened with me.
I was in MIUI 12.5. I installed Pixel Recovery to flash PE12 via adb sideload. Then I cleared all data/cache. When I tried to update the rom by sideload, it didn't work. I wanted to search the internet and as it would take time, I tried to turn the phone off. I couldn't even shut the phone to save battery. Whenever I pressed power button, instead of shutting down, it always took me to the bootloader menu. Thats when I thought about this question.
Addymore said:
I did shutdown the phone within fastboot to cancel flash all and lock....then booted in forced fastboot end flashed with flash all to not lock the bootloader....and had no prob....! I think those partitions are protected against those scenarios....
Click to expand...
Click to collapse
No. NO NO NO and NO.
You were lucky. This can totally brick your phone. Critical partitions are being modified in the Flashing-process.
There is no protection.
If your phone shuts down during the Flashing-process, your phone can get bricked (black screen) and you can't even boot Fastboot & Recovery anymore. I know this. I have experience.
You must ensure that you have enough Battery (I recommend 75% Battery at least), that the USB connection is stable (will not disconnect randomly), and that your PC won't crash/shut down.
IF IT HAPPENS, that the Flashing-process errors out, DON'T REBOOT THE PHONE. If you do so, you won't be able to enter Fastboot anymore. You must stay in Fastboot. Just reconnect USB, and try again to Flash. Just don't reboot the phone.
Sorry for fear-mongering, but this is definitely dangerous and not to be taken lightly.
dreamytom said:
No. NO NO NO and NO.
You were lucky. This can totally brick your phone. Critical partitions are being modified in the Flashing-process.
There is no protection.
If your phone shuts down during the Flashing-process, your phone can get bricked (black screen) and you can't even boot Fastboot & Recovery anymore. I know this. I have experience.
You must ensure that you have enough Battery (I recommend 75% Battery at least), that the USB connection is stable (will not disconnect randomly), and that your PC won't crash/shut down.
IF IT HAPPENS, that the Flashing-process errors out, DON'T REBOOT THE PHONE. If you do so, you won't be able to enter Fastboot anymore. You must stay in Fastboot. Just reconnect USB, and try again to Flash. Just don't reboot the phone.
Sorry for fear-mongering, but this is definitely dangerous and not to be taken lightly.
Click to expand...
Click to collapse
I think it is because I forced fastboot mode after few seconds of starting flashing....by the way I was avoid the flash and lock option that I selected by error while I wanted flash and clean...
I think, there is no ptoblem, fastboot Mode is Read Only Memory, no one can write/edit this think.
No matter you abort the flashing prosses , or the device loss power from battery, didn't affect the fastboot sector/bios on PC
*IMO