I have tried everything to get this phone to boot up. I was downloading the Oreo B2 via OTA, not sideloading. While the update was installing, I went about my business. I walked away for a few minutes and came back to a phone that just sat at the boot screen. I let it sit for about an hour, thinking that was some how normal. After an hour, I hard powered down and it came back to the same screen. I have rebooted at least 50 times now with no luck.
I can boot into fastboot, but not recovery. If I try to go into recovery, it goes to the boot screen and sits there. I have tried to switch partitions, it is stuck on A, without luck. The bootloader is locked and I can not remote unlock it via fastboot. Nor can I manually change the boot partition to B.
I have an open ticket with Essential, but they have been blowing me off and basically told me I'm out of luck since I was in their Beta program. They told me to go to XDA. A$$wipes! Any help you can offer is greatly appreciated since I'm stuck with a bricked phone and having to use an old iPhone since I cannot be without a phone.
Exact problem happened to me last week and a very helpful XDA member saved me.
Just hook up phone to pc by adb, type in 'fastboot devices' (while in fastboot mode) and install 7.1.1 os again. You'll lose everything but at least you won't be softbricked anymore.
Edit: sorry, just read you do not have unlock bootloader so this probably won't work.
Have you tried wiping data in while in fastboot? That might get it to boot.
Sent from my PH-1 using Tapatalk
You don't need an unlocked bootloader to sideload the install (following the BETA instructions: https://www.essential.com/developer/beta-builds
Since you can use fastboot, it looks like you have working ADB environment, so you should be able to follow those instructions. The STOCK recovery works very differently than TWRP, so make sure you follow those intructions, particularly the "Apply update from ADB" part. It took me a while to understand this, especially because the type on the screen is so tiny, I couldn't tell any words were changing.
I'm having the same issue (stuck on the boot logo "powered by android" screen) and I can get into fastboot mode, however if I try to go into recovery mode it just gets stuck on the boot screen again.
When in fastboot mode, the device state is "locked" is there any ways to get this fixed?
You could try: (you will lose all your data)
fastboot -w
fastboot reboot
ilpolpi65 said:
You could try: (you will lose all your data)
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
Here's what I've got
Code:
fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
erasing 'userdata'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.002s
It's still having the same issue..
update im still stuckk
Have you tried booting to bootloader and mounting /system?
This is obviously corruption of the firmware, and has nothing to do with wiping userdata. Download the full firmware and flash all of it through fastboot.
I also have my phone stuck The bot is closed and I can not do anything
V0idst4r said:
This is obviously corruption of the firmware, and has nothing to do with wiping userdata. Download the full firmware and flash all of it through fastboot.
Click to expand...
Click to collapse
I also have my phone stuck
The bot is closed and I can not do anything
Same here
It can't get passed the logo and I can't get any command in adb to go in fastboot. And recovery is a no go. Yay
Ph-1 stuck at boot, bootloader locked
kuyzz said:
update im still stuckk
Click to expand...
Click to collapse
We're able to fix the issue???
Related
Hello guys,
Sorry for my bad English
My phone just turned off even if the battery is almost full. When I turned it on its stuck in a boot loop. Sometimes it's goes to a screen where it would say process not responding. It's still on the stock ROM and recovery. I didn't try to root it or flash anything on it.
I tried some troubleshooting like flashing the firmware from the Asus website but it didn't work. Please help
Have you try flashing from Micro SD card in stock recovery?
M Huzaifah said:
Have you try flashing from Micro SD card in stock recovery?
Click to expand...
Click to collapse
Thank you for the reply bro. I already did and it's still not working.
To reset the phone in cases like this, one could also use fastboot.
Boot in fastboot mode by pressing VolumeUp button while switching on the phone, then connect the phone to a PC with a usb cable (you must have fastboot/adb drivers installed). You can now open a command prompt and use the commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
The second command erase all the user's data on the phone.
The last command erases the operating system and you must install the full firmware in zip format from the recovery afterward (with a microSD card or with a PC via ADB sideload).
you can install custom recovery?
I had a boot loop issue too. I could solve it by entering fastboot and trying using the defaut roms boot.img through fastboot. You can extract the boot.img from any firmware image file from the Asus site.
Code:
fastboot boot boot.img
BubuXP said:
To reset the phone in cases like this, one could also use fastboot.
Boot in fastboot mode by pressing VolumeUp button while switching on the phone, then connect the phone to a PC with a usb cable (you must have fastboot/adb drivers installed). You can now open a command prompt and use the commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
The second command erase all the user's data on the phone.
The last command erases the operating system and you must install the full firmware in zip format from the recovery afterward (with a microSD card or with a PC via ADB sideload).
Click to expand...
Click to collapse
After these commands, had to do a wipe data/factory reset prior to update from sd card (adb sideload not work at alll).
but no luck, keep boot looping...
---------- Post added at 11:26 PM ---------- Previous post was at 11:23 PM ----------
sofamensch said:
I had a boot loop issue too. I could solve it by entering fastboot and trying using the defaut roms boot.img through fastboot. You can extract the boot.img from any firmware image file from the Asus site.
Code:
fastboot boot boot.img
Click to expand...
Click to collapse
this command result error:
downloading 'boot.img'...
OKAY [ 0.796s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.802s
used this instead: fastboot flash boot boot.img (with boot.img extracted from firmware)
target reported max download size of 268435456 bytes
sending 'boot' (24547 KB)...
OKAY [ 0.813s]
writing 'boot'...
OKAY [ 0.733s]
finished. total time: 1.550s
but my case is serious, giving up
maybe you should unlock the bootloader before trying those commands
why don't u try, adb sideload option once, give it a try
i dont know what firmware my dads ze550kl is...
and it is bootlooping continously....
what is best files to flash via recovery update from sd card method?
i want to save my dads internal memory
Try this:
fastboot boot recovery.img
Click to expand...
Click to collapse
This may result an error if you don't flash the right file,it depends on your firmware version. I have a file that works on lolipop (twrp.).
I had the same issue, as my device was on warranty period i took it to the service centre and they said the mother board is damaged
Im facing the same problem I installed a new ROM from SD card and it was successfully done but the phone is still stuck in boot loop and unfortunately my USB debugging is disabled my bootloader is locked and my phone is not rooted and it's in stock recovery can anyone please help me
BubuXP said:
To reset the phone in cases like this, one could also use fastboot.
Boot in fastboot mode by pressing VolumeUp button while switching on the phone, then connect the phone to a PC with a usb cable (you must have fastboot/adb drivers installed). You can now open a command prompt and use the commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
The second command erase all the user's data on the phone.
The last command erases the operating system and you must install the full firmware in zip format from the recovery afterward (with a microSD card or with a PC via ADB sideload).
Click to expand...
Click to collapse
heyy, even i deleted recovery by using
fastboot erase recovery
then, after that my phone stucked on fastboot mode..
and when i flash the recovery , it finished propery but there is nothing happen in my phone still stucked into fastboot mode..
when i press power+volume(-) only fastboot mode is opened..
what to do now??
how to reinstall bootloader (recovery or twrp)??
plz help guyzz//:crying::crying:
I face the same bootloop problem with my mother's cellphone. The bootloader is locked and USB debug is disabled.
I tried to flash stock img via adb sideload, and although it succeed, after factory reset in Recovery (and pull battery several time) I could finally get into the "setup wizard" of Android system.
However, the system will go into bootloop again when the wizard goes to "wifi" setup. The phone will not go into setup wizard again unless I do a factory reset (and battery pull) again...
It seems there are some hardware failure at Wifi component (Since I already erase all \data, \cache), and this failure caused reboot of the system...
Any idea?
mayankarya837 said:
heyy, even i deleted recovery by using
fastboot erase recovery
then, after that my phone stucked on fastboot mode..
and when i flash the recovery , it finished propery but there is nothing happen in my phone still stucked into fastboot mode..
when i press power+volume(-) only fastboot mode is opened..
what to do now??
how to reinstall bootloader (recovery or twrp)??
plz help guyzz//:crying::crying:
Click to expand...
Click to collapse
hey did u finnd any solution for this>???
So i just saw the new Oxygen OS 3.1.0 is out in OTA form. Me being rooted i tried flashing it through twrp, which i had installed before. (i should also note that i had Xposed installed too, on Oxygen OS 3.0.2) now i think i might have gotten my zip file wrong and installed a previous version. The boot animation is the square, triangle and circle one. It just goes through my apps and tries to update them for eternity. When i try putting the device into recovery (power+vol down) it just freezes on the oneplus logo. I later discovered that i can use fastboot when in that mode. I tired flashing twrp but i couldnt boot into it. fastboot boot recovery.img didnt work either, giving me this:
downloading 'boot.img'...
OKAY [ 0.746s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.011s
Now i have no idea what to do. I'm sure I've made SOME kind of mistake along the way, but i cant find a way to fix this. I have a nandriod backup of just before flashing if that might help.
fastboot reboot-bootloader puts me in fastboot mode but it doesnt change anything.
also, ADB naturally wont detect the phone whatsoever.
Ill be very glad for any help! Thanks!
Are the drivers accurate? Does your PC recognize your device as it should in Device Manager? That's usually what I check first when I have fastboot errors. I think the only way to fix this is through fastboot... so I would focus on trying to get that to work first.
SynderBlack said:
So i just saw the new Oxygen OS 3.1.0 is out in OTA form. Me being rooted i tried flashing it through twrp, which i had installed before. (i should also note that i had Xposed installed too, on Oxygen OS 3.0.2) now i think i might have gotten my zip file wrong and installed a previous version. The boot animation is the square, triangle and circle one. It just goes through my apps and tries to update them for eternity. When i try putting the device into recovery (power+vol down) it just freezes on the oneplus logo. I later discovered that i can use fastboot when in that mode. I tired flashing twrp but i couldnt boot into it. fastboot boot recovery.img didnt work either, giving me this:
downloading 'boot.img'...
OKAY [ 0.746s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.011s
Now i have no idea what to do. I'm sure I've made SOME kind of mistake along the way, but i cant find a way to fix this. I have a nandriod backup of just before flashing if that might help.
fastboot reboot-bootloader puts me in fastboot mode but it doesnt change anything.
also, ADB naturally wont detect the phone whatsoever.
Ill be very glad for any help! Thanks!
Click to expand...
Click to collapse
**** man. I'm in the same boat as of a few hours ago. I was having a ProxyController wakelock and the few Google results I saw told me I should reflash the modem. I accidentally flashed the old modem (OOS2, I believe). I can't boot into my rom OR TWRP. BUT fastboot does work. I also get the "remote: dtb not found" error when trying to boot from the recovery image.
As long as we have fastboot, we can always go back to OOS 3 using the various unbrick methods. I'm trying to avoid having to go through that whole mess of re-rooting/unlock the bootloader etc etc. I'll post on here if I'm successful.
Update: I NEED a functional phone so I just went and erased everything. Sorry I couldn't be of much help to you man. What I did:
I went here and downloaded the fastboot version of OOS3 and converted the bat scripts into bash scripts (I only have Linux computers near me right now...; the commands in that bat script are exactly the same as they would be in bash, I just had to rename the ".bat" to ".sh" and make it executable). I'm back in OOS 3 now, unfortunately. There IS a way mentioned on the page below that talks about how you can prevent userdata from being formatted, but I didn't really care too much. Hope that helps.
http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
I recently re-flashed MAXIMUM Overdrive after experiencing some battery issues. Upon doing the dalvik, cache, system and data wipes, then reinstalling the ROM, I found myself sitting on the Welcome screen, and unable to get past it after confirming the account my phone had before.
I've tried getting into TWRP to no avail. The Vol Down and power, then yes on both factory resets just takes me to twrp, resets the phone, then reboots, not allowing me to do anything. I can get into Fastboot, but no route to recovery from there. ADB doesn't recognize since I haven't been able to turn on usb debugging yet.
Does anyone happen to have any ideas? I'm basically sitting on a brick at the moment. I'll buy you lunch or a beer if you can manage to be the solution
which variant? if its the vzw(your profile) boot into fastboot and on the computer type
Code:
fastboot erase system
then
Code:
fastboot reboot
and that will force twrp to load.
me2151 said:
which variant? if its the vzw(your profile) boot into fastboot and on the computer type
Code:
fastboot erase system
then
Code:
fastboot reboot
and that will force twrp to load.
Click to expand...
Click to collapse
It's the T-Mobile US Variant. H18. That didn't work unfortunately, presumably because it's the tmo variant.
Output:
Code:
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
FAILED (remote: unknown command)
finished. total time: 0.020s
I also tried fastboot format:ext4 system. That failed as well.
I'm just curious how it got stuck in this loop to begin with since I wiped pretty much everything.
Solved by restoring firmware to stock with LGUP
Dear everyone,
I am stuck in fastboot. I installed the greek TWRP, and cleaned my data by typing ''yes''.
I connected my phone to my PC to put a ROM zip on it, but it only glitched out (it showed multiple storages in Windows)
I restarted my phone, and it won't boot in recovery. When I try to boot to recovery via adb, it just shows
PS C:\adb> fastboot boot recovery.img
Downloading 'boot.img' OKAY [ 0.616s]
booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
I am really scared now that my phone is hard bricked. Not sure why though.
Flashing a fastboot ROM wont work either, it just says flash done instantly.
I have done this so many times on my other Xiaomi phones I had without any problems.
And also, is it possible to turn the phone off for now? Because I dont want to have the fastboot screen burned in.
Regards
Jordytjes said:
Dear everyone,
I am stuck in fastboot. I installed the greek TWRP, and cleaned my data by typing ''yes''.
I connected my phone to my PC to put a ROM zip on it, but it only glitched out (it showed multiple storages in Windows)
I restarted my phone, and it won't boot in recovery. When I try to boot to recovery via adb, it just shows
PS C:\adb> fastboot boot recovery.img
Downloading 'boot.img' OKAY [ 0.616s]
booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
I am really scared now that my phone is hard bricked. Not sure why though.
Flashing a fastboot ROM wont work either, it just says flash done instantly.
I have done this so many times on my other Xiaomi phones I had without any problems.
And also, is it possible to turn the phone off for now? Because I dont want to have the fastboot screen burned in.
Regards
Click to expand...
Click to collapse
Did you try flashing the fixed russian twrp? When I flashed the greek twrp on my phone and rebooted through adb it didn't reboot so I rebooted manually and it rebooted into stock recovery. I rebooted into fastbood and flashed the fixed twrp and it worked. If you can get into fastbood you have a chance of reflashing twrp or flashing stock rom so I don't think its bricked yet
Aserar said:
Did you try flashing the fixed russian twrp? When I flashed the greek twrp on my phone and rebooted through adb it didn't reboot so I rebooted manually and it rebooted into stock recovery. I rebooted into fastbood and flashed the fixed twrp and it worked. If you can get into fastbood you have a chance of reflashing twrp or flashing stock rom so I don't think its bricked yet
Click to expand...
Click to collapse
You are my hero! Thank you so much!
this is soft brick, try to flash another twrp as the above user mentioned.
Dear all, Pls help me )':
Similar to other post, my situation goes like this
1)my magisk manager was hidden (Renamed)
2)tried updated magisk apk no issue, just the main magisk updates which i updated within app (selected recommended) it return errors.
3)did a restart then unable to boot to normal android environment.
4)stuck in boot screen whereas shown 'your device is corrupt.....'
5)firstly was able to boot into TWRP recovery mode
6)my mistake was flash magisk 21.4.zip on top
7)now stuck in fastboot bootloop which shows "BOOTLOADER VERSION -" and "BASEBAND VERSION -" as empty!
8)no longer able to access TWRP
9)reboot bootloader -> brings it back straight to fastboot mode, Power off and on -> brings it back straight to fastboot mode, Start recovery -> brings it back straight to fastboot mode Just fastboot working.
my device details.
-using last version of Oxygen OS (android 9) on my Oneplus 6T . did not upgrade to android 10
-cant remember if my USB debugging in dev mode settings is turned off
Troubleshoot i did so far
-i have tried flash twrp-3.3.1-27-fajita-Pie-mauronofrio.img from fast boot which return this error
C:\adb>fastboot boot twrp-3.3.1-27-fajita-Pie-mauronofrio.img
downloading 'twrp-3.3.1-27-fajita-Pie-mauronofrio.img'...
OKAY [ 0.666s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.679s
Hi, Hopefully someone can assist you here....
Only possible way is to pull the boot.img from the Fastboot ROMs Thread. Otherwise you may have to try MSM to unbrick your device.
Huskied said:
Only possible way is to pull the boot.img from the Fastboot ROMs Thread. Otherwise you may have to try MSM to unbrick your device.
Click to expand...
Click to collapse
greatly appreciate your help! flashing fastboot rom works.
however during booting up phone everytime is will shown "Your device is corrupt it can't be trusted". - fixed by further applying latest OTA updates
[deleted]
Huskied said:
Only possible way is to pull the boot.img from the Fastboot ROMs Thread. Otherwise you may have to try MSM to unbrick your device.
Click to expand...
Click to collapse
@Huskied Will flashing only the boot.img delete all data from internal storage?
I want to boot into a twrp.img so I can decrypt and recover the data but I get the same failure to authenticate error.
spinergist said:
@Huskied Will flashing only the boot.img delete all data from internal storage?
I want to boot into a twrp.img so I can decrypt and recover the data but I get the same failure to authenticate error.
Click to expand...
Click to collapse
flashing boot.img will only touch boot and nothing else.
Huskied said:
flashing boot.img will only touch boot and nothing else.
Click to expand...
Click to collapse
If I understand correctly, and before I get too excited about getting my data back, then does that mean I can fix this authenticate error without losing my encrypted data if I do fastboot flash boot boot.img?
(I have some book chapters from my novel that I really don't want to risk losing so its important to figure out if twrp will let me decrypt the data if I flash the new boot.img)
spinergist said:
If I understand correctly, and before I get too excited about getting my data back, then does that mean I can fix this authenticate error without losing my encrypted data if I do fastboot flash boot boot.img?
(I have some book chapters from my novel that I really don't want to risk losing so its important to figure out if twrp will let me decrypt the data if I flash the new boot.img)
Click to expand...
Click to collapse
If it doesn't boot and you can't your data back, Dirty flashing might be the last hope. Otherwise, Data will stay encrypted unfortunately.