I just recently unlocked the bootloader on my soft-bricked Mate SE.
When it said to unlock it, it also said it was going to factory reset.
I was going to install TWRP to restore a full backup.
It now gets stuck in a loop factory resetting and I don't have access to fastboot.
I'm stuck in this bootloop and can someone help me?
also, I do have a working fastboot, and recovery partition, I just for
some reason can't do anything else, when I reboot it brings up the EMUI
factory reset screen.
tomjfmu said:
also, I do have a working fastboot, and recovery partition, I just for
some reason can't do anything else, when I reboot it brings up the EMUI
factory reset screen.
Click to expand...
Click to collapse
Let my phone run out of battery, plugged it in,
vol down and it got into fastboot finally.
Related
Hi,
I've attempted the JB update
http://forum.xda-developers.com/showthread.php?t=1737899..
fastboot flash boot boot.img etc.. which said all was well..
But now find that my phone will not boot up, doesn't get past the Google and unlock screen.
I've tried all combinations of volume buttons, I can get to the fasboot menu where I can choose either Recovery Mode, Power Off, Start or Restart bootloader.
None of these appear to do anything, recovery goes to the google a screen followed by an Android on it's back with an exclamation mark over it.. then goes to the Google and unlocked icon screen and stays there...
I fear my phone is bricked... Please help..
bevnet said:
Hi,
I've attempted the JB update
http://forum.xda-developers.com/showthread.php?t=1737899..
fastboot flash boot boot.img etc.. which said all was well..
But now find that my phone will not boot up, doesn't get past the Google and unlock screen.
I've tried all combinations of volume buttons, I can get to the fasboot menu where I can choose either Recovery Mode, Power Off, Start or Restart bootloader.
None of these appear to do anything, recovery goes to the google a screen followed by an Android on it's back with an exclamation mark over it.. then goes to the Google and unlocked icon screen and stays there...
I fear my phone is bricked... Please help..
Click to expand...
Click to collapse
1.) Your phone is far from bricked at all. You have access to the boot loader (i.e. the screen with the options). The recovery you're seeing is stock recovery. All you need to do is go into boot loader and fastboot flash recovername (CWM) and you will have your custom recovery back to wipe data and reinstall a rom or restore a nandroid backup
Mine is doing the same thing, weird thing is, it was working since yesterday on jellybean, it just randomly froze this morning and and now won't boot..
im currently at work so i don't have admin rights to do a fastboot flash..
any idea why it would randomly stop working when i havn't flashed anything on it besides the jb rom?
Sorted..
Thanks for the comments.. yeah i was over-reacting a bit there..
I downloaded the Galaxy Nexus Toolkit, got a stock rom form gopogle, flashed it.. back to normal, well, it will be after i restore the CWM backup i took.. phew..
Thanks again
Ian.
Still stuck
I'm also stuck in the same situation(google with the unlock screen). I fear I'm a little more stuck. I also can see the recovery/restartbootloader screen. However, everything I try still comes back to that same google screen and gets hung up. Need some help!
this has happened twice today and i think it from using volume+
Steelbully said:
I'm also stuck in the same situation(google with the unlock screen). I fear I'm a little more stuck. I also can see the recovery/restartbootloader screen. However, everything I try still comes back to that same google screen and gets hung up. Need some help!
Click to expand...
Click to collapse
Boot into recovery, wipe cache, Reboot
Long story short installed substratum and it was working fine, had a navbar theme already running and installed another one. Few hours later rebooted phone and when it booted back up systemui crashed and it went into bootlooping into that over and over again. Now it bootloops a few times and goes into a recovery menu that only gives me the options to try rebooting again or a factory data reset.
The phone boots into bootloader/fastboot just fine and I can get into recovery but the only options I have are 'try again' and 'factory data reset' I know that FDR is basically my only option and so be it. BUT IF POSSIBLE I want to try and backup the internal data or at least as much of it as possible.
So, is it possible to backup any internal data with only having access to bootloader/fastboot.
I've spent over an hour searching to this answer but either I was searching wrong or simply was not able to find the answer. Pixel XL is 100% stock. Never modded, never rooted, stock recovery, stock latest official Oreo from OTA update.
So again. Absolutely no access to the OS. Only access bootloader/fastboot and a form of the recovery menu and I would like to somehow backup the internal data. I don't care about apps or any app data, specifically just the user data if at all possible. If not well then I'm screwed and that's that.
Hello,
Happened to me also something like this. The phone rebooted and the only option were those presented to you also. But, I pressed the "Try again". If this still doesn't work, when the device is rebooting, and the white screen appears, try and hold on to the power button until the moving dots appear.
Also, this didn't wipe anything on my device.
Hope this is useful to you.
moraritza1 said:
Hello,
Happened to me also something like this. The phone rebooted and the only option were those presented to you also. But, I pressed the "Try again". If this still doesn't work, when the device is rebooting, and the white screen appears, try and hold on to the power button until the moving dots appear.
Also, this didn't wipe anything on my device.
Hope this is useful to you.
Click to expand...
Click to collapse
Does nothing. Just reboots back into recovery. I've tried Try Again probably 100 times and nothing ever changes. Even safe mode does not work. The SystemUI is completely dead.
I'm 90% sure there is no way to fix the phone other than factory data reset and I'm fine with that. I just want to know if I can backup anything from bootloader/fastboot before I do that.
Have you tried using ADB to boot ( not flash ) a custom recovery, and from there to backup the phone, and after if it's possible, to use the USB-OTG to copy that backup to an USB memory stick?
Looking at the Substratum FAQ in the app it says that if you experience a bootloop you should be able to flash /storage/emulated/0/substratum/SubstratumRescue.zip in recovery and it should fix the boot loop.
matt0720 said:
Looking at the Substratum FAQ in the app it says that if you experience a bootloop you should be able to flash /storage/emulated/0/substratum/SubstratumRescue.zip in recovery and it should fix the boot loop.
Click to expand...
Click to collapse
As Matt already mentioned, there's a rescue zip file which comes by default with substratum. It's purpose is to remove all overlays which you've currently installed.
In case you don't have a custom recovery installed you can simply boot into twrp via adb (without having flash the recovery)
Android-xp said:
As Matt already mentioned, there's a rescue zip file which comes by default with substratum. It's purpose is to remove all overlays which you've currently installed.
In case you don't have a custom recovery installed you can simply boot into twrp via adb (without having flash the recovery)
Click to expand...
Click to collapse
What if you're bootloader locked? Is there a way to recover from a bad overlay?
You could try to flash the factory image if you've unlocked the BL, just remove the -w from the flash all script
bobby janow said:
What if you're bootloader locked? Is there a way to recover from a bad overlay?
Click to expand...
Click to collapse
If you have checked the option to potentially allow unlocking your bootloader in dev-settings you can use fastboot to unlock your bootloader and boot into the bootable recovery image
I tried to update to the latest update to the Razer Phone and was able to install it successfully, but when I went to install Magisk on the new update, it caused the Wifi to stop working. For that reason, I tried to restore my old TWRP backup I made prior to updating which everything was working before updating. I wiped cache, dalvik, data and system and restored my old backup. Now when I try to boot, it gets stuck at the Razer logo and doesn't get past that. I also tried wiping data and restoring the system image only to no avail and it didn't do anything.
Have you tried booting to TWRP and booting The other [email protected]
How long did you wait on the Razer logo.. When I reset my phone after relocking it.. It took 10+min for first boot. I was scared it wasn't gonna work but I just left it alone and it eventually booted itself up
mikeandjaimie said:
How long did you wait on the Razer logo.. When I reset my phone after relocking it.. It took 10+min for first boot. I was scared it wasn't gonna work but I just left it alone and it eventually booted itself up
Click to expand...
Click to collapse
Thanks. I'll try that and see if it works. But I let it sit for 5 or so minutes.
Edit: I'll go ahead and add it was stuck at the Razer logo. It never got to the actual boot animation.
Edit 2: I let it sit for 20+ minutes and it wouldn't boot or get past the Razer logo.
RUNNERX said:
Have you tried booting to TWRP and booting The other [email protected]
Click to expand...
Click to collapse
Yes I've tried switching slots and it didn't work.
Any luck with the stuck at logo screen? I followed instructions from Razer and fkashall and now it won't boot to recovery download or system . It just hangs at the logo screen for better part of 2 hours now so it's not a waiting game .. any luck in fixing yours?
hi there, same here after flashing google pixel experience on razer phone1. seems to be a general problem for many users. Any hints?
Best regards
Michael
I have the same problem, but I wasn't updating or installed any new app. I was just ordering food from an app and then all of a sudden my phone restared and got stuck in a bootloop.
I reflashed the stock rom, over and over, slot a or slot b, hoping that would fix it somehow... it's just stuck there now. I could go into download mode and recovery mode. but, it's only until there.
now it's bootloop until it gets into download mode...
ThatGuy94 said:
I tried to update to the latest update to the Razer Phone and was able to install it successfully, but when I went to install Magisk on the new update, it caused the Wifi to stop working. For that reason, I tried to restore my old TWRP backup I made prior to updating which everything was working before updating. I wiped cache, dalvik, data and system and restored my old backup. Now when I try to boot, it gets stuck at the Razer logo and doesn't get past that. I also tried wiping data and restoring the system image only to no avail and it didn't do anything.
Click to expand...
Click to collapse
I could fix it. After flashing (even Android Pi) you have to do a factory reset.
IMPORTANT: THE FACTORY RESET IN TWRP DOES NOT WORK. So you have to flash the boot-sector in your system partition with the stock boot.img and reset to STOCK RECOVERY by typing "fastboot reboot" and pressing the vol-up button. Once in stock recovery, do a factory reset and return to bootloader. Now you can flash the boot.partition with twrp boot.img, install in recovery the stock boot.img, install the twrp-installer.zip and reboot to system. The bootlogo will not stuck anymore.
I hope, I could help you. Do not forget to backup before trying.
Best regards
Mellus
sry for my bad english
My one plus 5t is stuck on logo after an official update and the bootloader is locked.
Is there any way to unlock bootloader without access to OS (OEM unlock), so that I can flash any custom recovery?
Or any other solution from experts?
Use fastboot to OEM unlock.
Read up on some tutorials, this one is easy to fix.
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
That thread should get you going.
Nick502 said:
Use fastboot to OEM unlock.
Read up on some tutorials, this one is easy to fix.
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
That thread should get you going.
Click to expand...
Click to collapse
I read this but they are saying that you have to go to setting and developer option to enable oem unlock first, but i cant access to my device because my device is stuck on logo screen.
kashan69 said:
I read this but they are saying that you have to go to setting and developer option to enable oem unlock first, but i cant access to my device because my device is stuck on logo screen.
Click to expand...
Click to collapse
I would suggest you do this first:
https://downloads.oneplus.com/oneplus-5t/oneplus_5t_oxygenos_5.1.1/
Then you should be able to boot to android again. Then tick the OEM lock button
Just enter stock recovery mode and do a wipe factory reset. If it doessnt work, just falsh official oxygen os and do the factory reset again.
If the reset doeesn't work there is a cheat that will work if encrypted and your data is backed up... Open the stock recovery which will require a password. Select the dont remember button at the bottom. It will warn you that procedding will wipe your phone. Do it. The recovery will wipe and reboot your phone with the stock image you just tried to flash. You WILL lose data.
If you cant access the stock recovery or TWRP you can boot either on your PC and perform a wipe from there. You can then move a stock image over to root and flash it with the stock recovery.
I have this same issue, stuck on one plus logo on boot. Can enter fast boot menu but can not enter recovery mode.
Do you still have that problem?
kashan69 said:
I read this but they are saying that you have to go to setting and developer option to enable oem unlock first, but i cant access to my device because my device is stuck on logo screen.
Click to expand...
Click to collapse
I want to help you Do you still have that problem?
Do a factory reset in stock recovery. If it doesn't work, then use this guide
https://forum.xda-developers.com/on...5t-unbricking-tool-confirmation-t3733012
AIsmael said:
I want to help you Do you still have that problem?
Click to expand...
Click to collapse
I still have this problem. Stuck at logo and I can't get to recovery mode. Can you help me please?
I am having the same issue. After the android 10 update and after my first restart, it gets stuck on first android boot screen. Not ever the oneplus screen is shows and phone screen becomes dark with led on in grey color. I tried wiping the cache and did a factory reset too but it did not work. Help me what to do. Also where can I find android OS image list of 5T and a process to flash it through PC (ADB commands may be or something else?)
Someone pls help me. My Oneplus 5t stuck in logo screen & not moving to any further screens.
1. Switched Off the phone
2. Now turning it ON & logo screen has come
3. After 5 to 6 seconds logo screen disappears & white LED indication starts glowing.
Pls suggest what to do.
Have the same problem, MSM tool doesn't help.
farrukh.pasha said:
I am having the same issue. After the android 10 update and after my first restart, it gets stuck on first android boot screen. Not ever the oneplus screen is shows and phone screen becomes dark with led on in grey color. I tried wiping the cache and did a factory reset too but it did not work. Help me what to do. Also where can I find android OS image list of 5T and a process to flash it through PC (ADB commands may be or something else?)
Click to expand...
Click to collapse
SuryaLava said:
Someone pls help me. My Oneplus 5t stuck in logo screen & not moving to any further screens.
1. Switched Off the phone
2. Now turning it ON & logo screen has come
3. After 5 to 6 seconds logo screen disappears & white LED indication starts glowing.
Pls suggest what to do.
Click to expand...
Click to collapse
Do you have any success?
Ryav said:
Have the same problem, MSM tool doesn't help.
Do you have any success?
Click to expand...
Click to collapse
I fixed this! Disassembled, disconnected battery, inserted usb cable, got message about battery, connected battery, started!
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.