It doesn't boot for more than 1 second.
Something like this has happened a couple times - it randomly rebooted and bootlooped forever. I fixed it before by flashing the ROM again.
As soon as the boot animation comes up, it freezes and reboots. I still have access to the recovery, if I vol up on boot.
Things I have tried:
Reflashed the rom
Flashed a new rom
Flashed rom with no root/gapps
Flashed a new recovery
Cleaned all the partitions
Fixed all the partitions
Any suggestions would be greatly appreciated
Thanks
I think maybe it's the power button pressed ever.
Does TWRP screen lock or do you have any strange behavior?
Are you wearing any cover? If so, try removing.
If you flashed clean from other roms, maybe do a factory install by Xiaomi Tools, in the latter case.
Stay tuned with the rom version for the reason of ARB.
Good lucky.
Related
OK, so long time lurker/flasher, but rarely poster. I've been flashing roms for a while now (up to ICS), and wanted to go back to something more stable and complete. I'm on downloaded Nil's Rom, wiped system,boot,cache, etc. and ran a couple superwipe scripts to make sure. I flashed the rom, it booted once, said I needed to do a data wipe again, so I rebooted to recovery, wiped data/factory reset, and now I can't get past the white boot screen.
I can't get into HBOOT or recovery. No vibes except the 3 vibes when I tried power+volume up. I've looked through a couple older threads, but the solutions seem to be related to other problems. Anybody have any advice on a thread/steps to undertake?
EDIT: Looks like ADB shows up in device manager, if that helps
Try a battery pull, then volume down + power.
Well, I'm not sure what I did that works, but my combinations of battery pulls and button presses eventually got me into hboot, then recovery, then a nandroid restore.
Mods can delete this thread if needed.
Thanks for the attention!
Well.
1. Wiping after flashing a sense 3 or sense 3.5 ROM will cause bootloops which is why your ROM didn't boot up. You'd need to Nandroid or flash again.
2. Hboot is indeed volume down+power. Volume up+power will give you the 3 vibes.
No need to delete thread. Just add [RESOLVED] to the beginning of the title.
Sent from my Galaxy Nexus using Tapatalk
Hi All,
Got a problem with my HOX. Rooted, and was running Franco kernel and PKMN ROM. Had a few issues so flashed back to stock kernel, wiped and reinstalled ROM.
Now I've got a problem; boots up, get a sense lock screen, then when I unlock I just get a white screen with HTC logo on that doesn't go away.
Help!
I've reflashed stock boot.img in fastboot, I've done a fastboot erase cache and still have same issue.
EDIT:
Well, got it to boot. Going thru setup now and it's INCREDIBLY SLOW. It's like it's underclocked to 100mhz or something. It's completely unusable - hitting "Next" in the Android setup menu takes 30 secs to process etc... This is kind of what was starting to happen before I wiped and reflashed - could it be I have corrupt storage or something?
landwomble said:
Hi All,
Got a problem with my HOX. Rooted, and was running Franco kernel and PKMN ROM. Had a few issues so flashed back to stock kernel, wiped and reinstalled ROM.
Now I've got a problem; boots up, get a sense lock screen, then when I unlock I just get a white screen with HTC logo on that doesn't go away.
Help!
I've reflashed stock boot.img in fastboot, I've done a fastboot erase cache and still have same issue.
EDIT:
Well, got it to boot. Going thru setup now and it's INCREDIBLY SLOW. It's like it's underclocked to 100mhz or something. It's completely unusable - hitting "Next" in the Android setup menu takes 30 secs to process etc... This is kind of what was starting to happen before I wiped and reflashed - could it be I have corrupt storage or something?
Click to expand...
Click to collapse
Did you remember to install kernel modules AFTER you installed your ROM? Roms come with their own kernels and the kernel modules are already installed under /system/lib. So unless you flash the kernel modules after the ROM, ROMs kernel modules get installed instead.
Yes, I did. Got it working now though - not sure what it was but mounted USB storage and got windows to scan the storage - then re-downloaded the ROM and flashed again. Weird....!
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
Hi Guys.
So i flashed a few roms lately. started with EmotionMiUi then CM10, Omega, Alliance and well a few more.
i did a full wipe and cleared all caches each times and only had a few minor problems with the different ROMS that i was able to fix.
So i now returned to MiUi and have had it running for about a week. Tried some DPi modding yesterday, and did notice that it took longer time to boot and boot into recovery. i flashed the Xpose DPi remover, and continued using my phone. i have rebooted about 3 times today. And the last reboot caused the phone to enter the eternal "Samsung Galaxy Note II - N7100" boot static "animation".
Now i have tried pulling the battery several times, tried booting into recovery and the only thing that will let me boot into anything is power + home + volume down.
i have obtained the official samsung firmware ROM for my phone.
is my way ahead to "just" flash it using Odin, and i will have my good times back ?
Maybe try to clear Data and Cache partitions first?
mat9v said:
Maybe try to clear Data and Cache partitions first?
Click to expand...
Click to collapse
Just to clear you're stuck at the start screen( the screen it shows Note 2 and model number)?
If so, then i have no clue
If your phone goes in a bootloop ( startscreen then samsung logo animation, blank screen, start screen, samsung logo animation...) I have faced this issue while flashing Stock ROMs and you can clear this by doing a factory reset though i have no clue whether this is the correct one for MIUI ROM.
prabukannappan said:
Just to clear you're stuck at the start screen( the screen it shows Note 2 and model number)?
If so, then i have no clue
If your phone goes in a bootloop ( startscreen then samsung logo animation, blank screen, start screen, samsung logo animation...) I have faced this issue while flashing Stock ROMs and you can clear this by doing a factory reset though i have no clue whether this is the correct one for MIUI ROM.
Click to expand...
Click to collapse
i was stuck at the very first startscreen that just stayed there. i had been messing around with some DPi and a lot of tweaks.
i used Odin from my PC to flash the official firmware, then i used Philz recovery to format and clean before flashing my MiUi V5 ROM.
ALL works great.
Brand new Pixel 3 XL
Enabled OEM Unlocking
Enabled USB Debugging
Unlocked Bootloader
Copied twrp-pixel3-installer-crosshatch-3.2.3-5.zip to my phone
Rebooted into bootloader
fastboot boot c:\...\twrp-3.3.1-3-crosshatch.img
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Wiped system/data/cache
Flashed AOSiP-9.0-Official-crosshatch-20190722.zip
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Rebooted
When the system rebooted, it brought me into bootloader. I selected Start and then it rebooted into Bootloader again. I then figured something went wrong with installing AOSiP, so I booted into recovery.... from TWRP, I wiped system/data/cache/storage/data in attempt to start over and flash the ROM again. This time, I rebooted the system after the wipe and upon rebooting, the phone never turned back on. Pressing and holding the power button for long periods of time doesn't seem to do anything. Any ideas where I went wrong and more importantly if I bricked my phone? Thx.
EDIT: Tried holding volume down and power button for 10+ seconds and it booted into bootloader. Not really sure where to go from here.
EDIT 2: I tried booting into Recovery. It went back to the black screen. I had to use volume down and power button to get back into bootloader. Fastboot devices does detect the phone. I'm guessing this is a softbrick and I can follow the softbrick tutorial from here? Either way, it'd be nice to know where I took a wrong turn if anybody knows. Thanks.
EDIT 3: It may also be worth mentioning that I confirmed all the md5sum's before flashing the zips or booting the img.
thex2 said:
Brand new Pixel 3 XL
Enabled OEM Unlocking
Enabled USB Debugging
Unlocked Bootloader
Copied twrp-pixel3-installer-crosshatch-3.2.3-5.zip to my phone
Rebooted into bootloader
fastboot boot c:\...\twrp-3.3.1-3-crosshatch.img
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Wiped system/data/cache
Flashed AOSiP-9.0-Official-crosshatch-20190722.zip
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Rebooted
When the system rebooted, it brought me into bootloader. I selected Start and then it rebooted into Bootloader again. I then figured something went wrong with installing AOSiP, so I booted into recovery.... from TWRP, I wiped system/data/cache/storage/data in attempt to start over and flash the ROM again. This time, I rebooted the system after the wipe and upon rebooting, the phone never turned back on. Pressing and holding the power button for long periods of time doesn't seem to do anything. Any ideas where I went wrong and more importantly if I bricked my phone? Thx.
EDIT: Tried holding volume down and power button for 10+ seconds and it booted into bootloader. Not really sure where to go from here.
EDIT 2: I tried booting into Recovery. It went back to the black screen. I had to use volume down and power button to get back into bootloader. Fastboot devices does detect the phone. I'm guessing this is a softbrick and I can follow the softbrick tutorial from here? Either way, it'd be nice to know where I took a wrong turn if anybody knows. Thanks.
EDIT 3: It may also be worth mentioning that I confirmed all the md5sum's before flashing the zips or booting the img.
Click to expand...
Click to collapse
Nevermind, @sliding_billy has the answer.
I
thex2 said:
Brand new Pixel 3 XL
Enabled OEM Unlocking
Enabled USB Debugging
Unlocked Bootloader
Copied twrp-pixel3-installer-crosshatch-3.2.3-5.zip to my phone
Rebooted into bootloader
fastboot boot c:\...\twrp-3.3.1-3-crosshatch.img
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Wiped system/data/cache
Flashed AOSiP-9.0-Official-crosshatch-20190722.zip
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Rebooted
When the system rebooted, it brought me into bootloader. I selected Start and then it rebooted into Bootloader again. I then figured something went wrong with installing AOSiP, so I booted into recovery.... from TWRP, I wiped system/data/cache/storage/data in attempt to start over and flash the ROM again. This time, I rebooted the system after the wipe and upon rebooting, the phone never turned back on. Pressing and holding the power button for long periods of time doesn't seem to do anything. Any ideas where I went wrong and more importantly if I bricked my phone? Thx.
EDIT: Tried holding volume down and power button for 10+ seconds and it booted into bootloader. Not really sure where to go from here.
EDIT 2: I tried booting into Recovery. It went back to the black screen. I had to use volume down and power button to get back into bootloader. Fastboot devices does detect the phone. I'm guessing this is a softbrick and I can follow the softbrick tutorial from here? Either way, it'd be nice to know where I took a wrong turn if anybody knows. Thanks.
EDIT 3: It may also be worth mentioning that I confirmed all the md5sum's before flashing the zips or booting the img.
Click to expand...
Click to collapse
If you can get to BL and fastboot devices is recognizing it, you are only soft bricked. Do a flash-all of the factory image. You will be starting over with the exception of OEM unlock and BL unlock. Once you are up and running, go back to BL, change slots and do the flash-all again. Of course, you will be setting up again but you should be clean. Be sure to use the last Android 9 factory image for flash-all if you are not intending to go to 10 yet. There is one rock solid custom ROM for 10 (Havoc). Take a read of the install instructions as it doesn't use TWRP (not available for 10 yet). It does need the flash-all of November factory image done to both slots, so if you are looking at that do it immediately IMO since you will have to wipe anyways.
If you wipe system in TWRP then you have to flash a ROM from there. That is why it went blank when you rebooted. You have nothing to boot up on.
ADB a stock file and start over...it's not bricked.
Thank you for the help guys. I will work on fixing the issue tonight. Also, thanks for the suggestion on the Havoc ROM, but I'm staying with Android 9 because of the menu navigation button at the bottom right of the older apps... https://www.androidpolice.com/2019/...utton-has-finally-been-retired-in-android-10/
thex2 said:
Thank you for the help guys. I will work on fixing the issue tonight. Also, thanks for the suggestion on the Havoc ROM, but I'm staying with Android 9 because of the menu navigation button at the bottom right of the older apps... https://www.androidpolice.com/2019/...utton-has-finally-been-retired-in-android-10/
Click to expand...
Click to collapse
Havoc also had pie builds if you wanted to try.