Related
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
sticktornado said:
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
Click to expand...
Click to collapse
I know, I flashed the correct number of system images that were in the zip file.
Thanks,
rent0n said:
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
Click to expand...
Click to collapse
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
rent0n said:
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
Click to expand...
Click to collapse
I tried that and it didn't work. When I try to go into recovery mode the phone keeps bootlooping.
One thing I noticed is that when I try to format cache or userdata I get this error:
Code:
$ fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.013s
I think there might be something wrong with the file system in my partitions. How can I manually format my partitions?
Thanks,
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
therealduff1 said:
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
Click to expand...
Click to collapse
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
rent0n said:
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
Click to expand...
Click to collapse
What os were you running when the phone screwed up ?
therealduff1 said:
What os were you running when the phone screwed up ?
Click to expand...
Click to collapse
I was running 5.1.1 when I got the notification for the 6.0 update.
I've noticed that trying to flash 5.1.1 firmware with fastboot gives me errors (preflash validation failed) while the 6.0 work "fine" (i.e.: I get OKAY after every step but then the phone is always stuck in a bootloop).
Thanks!
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
therealduff1 said:
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
Click to expand...
Click to collapse
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
rent0n said:
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
Click to expand...
Click to collapse
Have you gave this a try?
heavy_metal_man said:
Have you gave this a try?
Click to expand...
Click to collapse
Yes, no luck unfortunately.
I think I might have flashed the 5.1.1 bootloader after all - is there any way to recover from there?
Thanks,
Bump!
Does anyone have any other suggestion please?
Thanks,
Last bump
I'm going to sell this on eBay as non-working then unless someone comes up with a clever solution?
Thanks for your help!
Try flashing once more starting with the gpt.bin (that should hopefully take care of raw partition error) and skipping the bootloader altogether. Also, may be worthwhile to try mfastboot.exe instead of fastboot.exe.
I have this same issue, but I haven't flash 5.1.1 Files, I Only tried with 6.0 Brazil Retail.
I also tried to flash gpt to get rid of the "raw" partition, everything goes ok but still displaying that error. Anyone can help?
I got the same problem with my Moto E 2015... If I find a solution I will reply it in this topic..
I got LineageOS installed, restarted to bootloader and locked bootloader.
I can now:
Get into LineageOS Recovery
Boot to LineageOS ROM
I cannot:
Unlock bootloader
Unlock flashing
Unlock OEM from developer options (Option is greyed out)
What I tried, rooting and trying the following adb commands.
HTML:
adb root
adb shell setprop ro.oem_unlock_supported 1
Got the error:
HTML:
setprop: failed to set property 'ro.oem_unlock_supported' to '1'
I can only run LineageOS and go into LineageOS recovery and Adb sideload from recovery and install rooting apps.
Help! Want to 'fastboot flashing unlock'
Video:
https://vimeo.com/304615053
UPDATE:
UPDATE: Solution given by the dev razorloves(https://forum.xda-developers.com/member.php?u=614507) the dev who mantains the LineageOS ROM for Pixel details here:
https://forum.xda-developers.com/showpost.php?p=78361157&postcount=32
I am not sure, and I think someone else can chime in but, I have always heard that you never ever relock the bootloader with anything custom for the Pixel. Have you tried the fastboot flashing unlock critical command? I am not sure the exact command but if you Google it you will see. I think thats about your only hope.
Archangel said:
I am not sure, and I think someone else can chime in but, I have always heard that you never ever relock the bootloader with anything custom for the Pixel. Have you tried the fastboot flashing unlock critical command? I am not sure the exact command but if you Google it you will see. I think thats about your only hope.
Click to expand...
Click to collapse
Yeah, I goofed up.
Tried unlock_critical
HTML:
[email protected]:~$ fastboot flashing unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.029s
[email protected]:~$ fastboot flashing unlock_critical
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.013s
[email protected]:~$
What I cannot understand is I have a perfectly working LineageOS ROM and LineageOS Custom Recovery. There should ideally be a way
I guess on the bright side at least you have a working phone and a custom rom. But as far as removing it or going back to stock I am not that sure because I believe you need to be unlocked to do that and the system is locked down tight now. I am sure someone else smarter than me will help with an answer, sorry brother wish I could help more.
tomatosmoothie said:
Yeah, I goofed up.
Tried unlock_critical
HTML:
[email protected]:~$ fastboot flashing unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.029s
[email protected]:~$ fastboot flashing unlock_critical
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.013s
[email protected]:~$
What I cannot understand is I have a perfectly working LineageOS ROM and LineageOS Custom Recovery. There should ideally be a way
Click to expand...
Click to collapse
Archangel said:
I guess on the bright side at least you have a working phone and a custom rom. But as far as removing it or going back to stock I am not that sure because I believe you need to be unlocked to do that and the system is locked down tight now. I am sure someone else smarter than me will help with an answer, sorry brother wish I could help more.
Click to expand...
Click to collapse
Nah man, thanks for looking in, sometimes, when your banging your head against a wall, it's nice if at least someone looks in lol, I would feel so alone if no one replied Thank you!
Pondering of flashing the Unofficial LOS 16 which has been created by the same dev as the Official LOS 15 via LOS Recovery. to change things up.
I hearya nothings worse than having a problem and your the only one. Did that on a few phones. I have the Pixel 3 too now and I stay stock with some small edits and my Substratum themes running. I love the custom roms but sometimes they can be a real pain. Yeah I would give LOS 16 a try I guess what do you have to lose.
tomatosmoothie said:
Nah man, thanks for looking in, sometimes, when your banging your head against a wall, it's nice if at least someone looks in lol, I would feel so alone if no one replied Thank you!
Pondering of flashing the Unofficial LOS 16 which has been created by the same dev as the Official LOS 15 via LOS Recovery. to change things up.
Click to expand...
Click to collapse
tomatosmoothie said:
Pondering of flashing the Unofficial LOS 16 which has been created by the same dev as the Official LOS 15 via LOS Recovery. to change things up.
Click to expand...
Click to collapse
Sorry I don't have experience with that situation and hope someone with the knowledge will be able to help you, but in the meantime I just wanted to chime in because you are pretty lucky in your misfortune to have a working phone, usually relocking bootloader while on a custom ROM results in a bootloop 99.9% of the time. So I would advise not tinkering with your ROM but focusing on finding a way either to unlock bootloader or to get back to stock firmware.
bafforosso said:
Sorry I don't have experience with that situation and hope someone with the knowledge will be able to help you, but in the meantime I just wanted to chime in because you are pretty lucky in your misfortune to have a working phone, usually relocking bootloader while on a custom ROM results in a bootloop 99.9% of the time. So I would advise not tinkering with your ROM but focusing on finding a way either to unlock bootloader or to get back to stock firmware.
Click to expand...
Click to collapse
Thanks, I was thinking the same thing, also, the idea was to flash a ROM that would be able to allow OEM unlocking in dev options, but I feel maybe LOS Recovery is not allowing me to unlock.
Also thinking of flashing stock factory image via LOS Recovery.
I will tread carefully though, thanks.
No way your bl is locked.
Sent from my Pixel XL using Tapatalk
lafester said:
No way your bl is locked.
Click to expand...
Click to collapse
Hmm yeah I was wondering the same as it would be a pretty serious security bug if a locked bootloader let's a device with LOS boot. Could it be that only the "unlockability" switch was switched off but it did not really locked your bootloader, just the ability to modify it's status?
Don't you get the "open padlock" / "your device software can't be checked for corruption..." screen when you boot?
I think you really should try flashing stock firmware.
bafforosso said:
Hmm yeah I was wondering the same as it would be a pretty serious security bug if a locked bootloader let's a device with LOS boot. Could it be that only the "unlockability" switch was switched off but it did not really locked your bootloader, just the ability to modify it's status?
Don't you get the "open padlock" / "your device software can't be checked for corruption..." screen when you boot?
I think you really should try flashing stock firmware.
Click to expand...
Click to collapse
"Your device has loaded a different operating system" is what I get at boot and a "OS fingerprint" below that.
No padlock on the google screen.
I'm waiting for a factory image to download and will try flashing.
LOS Recovery is flashing LOS Nightlies so there is some flashing happening, only question is will LOS Recovery flash a Pixel Factory Image.
tomatosmoothie said:
"Your device has loaded a different operating system" is what I get at boot and a "OS fingerprint" below that.
No padlock on the google screen.
I'm waiting for a factory image to download and will try flashing.
LOS Recovery is flashing LOS Nightlies so there is some flashing happening, only question is will LOS Recovery flash a Pixel Factory Image.
Click to expand...
Click to collapse
Sorry I mixed things up : use the flash-all.sh (or flash-all.bat if using Windows) script with your device in fastboot mode as described on the stock firmwares download page.
[Correct but not for flashing stock firmware]
No idea, never used, but you should be able to "fastboot boot" into twrp and flash.
Don't flash twrp afterwards as it is known to cause bootloops under some circumstances with the December update, and as a rule of thumb with A/B partition devices just keep stock recovery and use a computer to "fastboot boot" into TWRP when you need to flash something, it is a lot safer (still talking about stock firmware as I don't know anything about LOS/LOS recovery).
bafforosso said:
No idea, never used, but you should be able to "fastboot boot" into twrp and flash.
Don't flash twrp afterwards as it is known to cause bootloops under some circumstances with the December update, and as a rule of thumb with A/B partition devices just keep stock recovery and use a computer to "fastboot boot" into TWRP when you need to flash something, it is a lot safer (still talking about stock firmware as I don't know anything about LOS/LOS recovery).
Click to expand...
Click to collapse
Tried that earlier, didn't work. Trying now.
Advanced Restart is enabled in Dev options.
Restarted to bootloader.
HTML:
[email protected]:~$ fastboot boot '/media/twrp-3.2.3-1-sailfish.img'
Downloading 'boot.img' OKAY [ 1.064s]
booting (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 9.237s
[email protected]:~$
tomatosmoothie said:
Tried that earlier, didn't work. Trying now.
Advanced Restart is enabled in Dev options.
Restarted to bootloader.
HTML:
[email protected]:~$ fastboot boot '/media/twrp-3.2.3-1-sailfish.img'
Downloading 'boot.img' OKAY [ 1.064s]
booting (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 9.237s
[email protected]:~$
Click to expand...
Click to collapse
Sorry edited my post because I mixed up things, my bad.
No recovery needed to flash stock firmware, just use instructions from the Stock Firmware Download Page
bafforosso said:
Sorry edited my post because I mixed up things, my bad.
No recovery needed to flash stock firmware, just use instructions from the Stock Firmware Download Page
Click to expand...
Click to collapse
Yeah, that page says flash unlock is required
Hoping, LOS Recovery will flash it, since it's flashing LOS Nightlies.
HTML:
[email protected]:~$ fastboot flashing unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.025s
[email protected]:~$ fastboot flashing unlock_critical
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.034s
[email protected]:~$ fastboot oem unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.027s
[email protected]:~$
tomatosmoothie said:
Yeah, that page says flash unlock is required
Hoping, LOS Recovery will flash it, since it's flashing LOS Nightlies.
Click to expand...
Click to collapse
If what I suspect - that the bootloader is not the original one but a modded one from LOS and in fact it is not really enforcing the locked state but just locks use of the fastboot unlock/lock instructions or some similar behaviour - then you have to try steps 5. and 6. no matter what is the output of the previous commands.
As you wish, it is your phone but if you don't try we'll never know...
bafforosso said:
If what I suspect - that the bootloader is not the original one but a modded one from LOS and in fact it is not really enforcing the locked state but just locks use of the fastboot unlock/lock instructions or some similar behaviour - then you have to try steps 5. and 6. no matter what is the output of the previous commands.
As you wish, it is your phone but if you don't try we'll never know...
Click to expand...
Click to collapse
Yeah, there is one more catch. You cannot choose a file in LOS Recovery, it is encrypted.
So the only choice is "adb sideloar file.zip"
bafforosso said:
If what I suspect - that the bootloader is not the original one but a modded one from LOS and in fact it is not really enforcing the locked state but just locks use of the fastboot unlock/lock instructions or some similar behaviour - then you have to try steps 5. and 6. no matter what is the output of the previous commands.
As you wish, it is your phone but if you don't try we'll never know...
Click to expand...
Click to collapse
Yeah, there is one more catch. You cannot choose a file in LOS Recovery, it is encrypted.
So the only choice is "adb sideload file.zip"
tomatosmoothie said:
Yeah, there is one more catch. You cannot choose a file in LOS Recovery, it is encrypted.
So the only choice is "adb sideloar file.zip"
Click to expand...
Click to collapse
Come on man please, I know you're probably tired of this but I stated that "No recovery needed to flash stock firmware, just use instructions from the Stock Firmware Download Page" and nowhere does it states anything about recovery, adb push, sideload or what not...
Here is a simplification of the part of the instructions on that page you should follow, everything has to be done from your computer with your phone plugged to it in fastboot mode :
On your computer, download stock firmware full image for your device.
Unzip the stock firmware image just downloaded.
Open a terminal and navigate to the unzipped stock firmware image directory.
Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system
P.S.: Forgot to warn but this will delete all your data from your phone.
bafforosso said:
Come on man please, I know you're probably tired of this but I stated that "No recovery needed to flash stock firmware, just use instructions from the Stock Firmware Download Page" and nowhere does it states anything about recovery, adb push, sideload or what not...
Here is a simplification of the part of the instructions on that page you should follow, everything has to be done from your computer with your phone plugged to it in fastboot mode :
On your computer, download stock firmware full image for your device.
Unzip the stock firmware image just downloaded.
Open a terminal and navigate to the unzipped stock firmware image directory.
Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system
P.S.: Forgot to warn but this will delete all your data from your phone.
Click to expand...
Click to collapse
Got a Permission denied.
HTML:
[email protected]:/media/disk2/LineageOS/Pie/Pie_Official_Factory/sailfish-ppr2.181005.003.a1$ ./flash-all.sh
bash: ./flash-all.sh: Permission denied
My Honor View10 is stuck at 'Your device is booting now', cannot enter recovery. I tried rectifying my twrp that couldn't unmount anything and wiped up almost everything, but ended up with a boot loop.
Now my device is stuck at 'Your device has been unlocked and can't be trusted. Your device is booting now' screen. I tried using the dload method to restore everything back but the device won't go past this screen.
I tried flashing it using fastboot mode by flashing system, ramdisk and what not, did get a success every time, still, the device won't go past this.
I need genuine help on this, please. Anyone? @2WildFirE? @Einwod? @shashank1320 @oreopie
All this perhaps happened because I tried changing the file system of data and system from twrp.
ankan1993 said:
My Honor View10 is stuck at 'Your device is booting now', cannot enter recovery. I tried rectifying my twrp that couldn't unmount anything and wiped up almost everything, but ended up with a boot loop.
Now my device is stuck at 'Your device has been unlocked and can't be trusted. Your device is booting now' screen. I tried using the dload method to restore everything back but the device won't go past this screen.
I tried flashing it using fastboot mode by flashing system, ramdisk and what not, did get a success every time, still, the device won't go past this.
I need genuine help on this, please. Anyone? @2WildFirE? @Einwod? @[email protected]
All this perhaps happened because I tried changing the file system of data and system from twrp.
Click to expand...
Click to collapse
Why you tried changing filesystem on data?
Twrp isn't ready for pie ? atm
Flash stock recovery and erecovery, then boot to erecovery and restore from there
2WildFirE said:
Why you tried changing filesystem on data?
Twrp isn't ready for pie ? atm
Flash stock recovery and erecovery, then boot to erecovery and restore from there
Click to expand...
Click to collapse
Because custom recovery wouldn't mount anything.
Had no idea that twrp isn't ready for pie.
For both stock and ereccovery, do I use ramdisk_recovery command?
2WildFirE said:
Flash stock recovery and erecovery, then boot to erecovery and restore from there
Click to expand...
Click to collapse
How exactly would one go about this?
fastboot flash erecovery_ramdisk ERECOVERY_RAMDI.img for example only results in FAILED (remote: 'Command not allowed').
Bootloader is unlocked.
If I'm right, try fastboot flash erecovery erecovery.img
2WildFirE said:
If I'm right, try fastboot flash erecovery erecovery.img
Click to expand...
Click to collapse
Sadly there is no erecovery.img and if i try to flash either of the many erecovery files into what i assume would be their respective partitions i get the same error.
Which i thought was a good sign because that might have meant that i couldn't have ****ed them up. But maybe it isn't.
OK try erecovery ramdisk and erecovery kernel to flash
PHP:
fastboot flash erecovery_kernel ERECOVERY_kerne.img
Sending 'erecovery_kernel' (24576 KB) OKAY [ 0.587s]
Writing 'erecovery_kernel' FAILED (remote: 'Command not allowed')
Finished. Total time: 0.614s
for example, the result is always the same.
2WildFirE said:
Why you tried changing filesystem on data?
Twrp isn't ready for pie ? atm
Flash stock recovery and erecovery, then boot to erecovery and restore from there
Click to expand...
Click to collapse
UPDATE: When I reboot the smartphone it displays "Data partition was damaged seriously! and you are recommended to format it to recover your phone".
Smartphone works, but even after a factory reset it still displays that message when it boots up it gets stuck at 'Booting up'.
What can I do @2WildFirE?
180190 said:
PHP:
fastboot flash erecovery_kernel ERECOVERY_kerne.img
Sending 'erecovery_kernel' (24576 KB) OKAY [ 0.587s]
Writing 'erecovery_kernel' FAILED (remote: 'Command not allowed')
Finished. Total time: 0.614s
for example, the result is always the same.
Click to expand...
Click to collapse
Because this is not the right command to give. I am not sure what the right command would be though.
Okay, so I have recovered my phone after spending a sleepless night working on it.
Tried several combinations to see this resolved.
But, what really worked out for me was that I discharged my device twice and kept trying flashing stock rom and several relative recoveries.
After flashing stock recovery I discharged my device. Once it came back, it took me to erecovery.
From there, I started downloading the file from the recovery and did a reboot after the installation.
My Honor is working fine now.
ankan1993 said:
But, what really worked out for me was that I discharged my device twice and kept trying flashing stock rom and several relative recoveries.
After flashing stock recovery I discharged my device.
Click to expand...
Click to collapse
What exactly have you done?
Sinerty said:
What exactly have you done?
Click to expand...
Click to collapse
Flashed the 9.0 full ota files several times, flashed full otas of 8.0. Flashed a random recovery from an older ota. I then discharged my device as I was totally out of options. When I put it on charge it turned back on and after few minutes took me to erecovery.
And now I cannot root my device as twrp isn't there for pie yet. Honor sucks.
Thread closed since it's a duplicate.
Please read here: https://forum.xda-developers.com/honor-view-10/help/honor-view10-stuck-device-booting-enter-t3889376
Hello guys I need some help. I'm stuck in fastboot mode with no recovery or OS too l, let me retrace my steps.
I had my px3 rooted on stock but I was bored with stock and tried to flash bootleggers rom and followed instructions to wipe "everything" but internal storage, so I did including storage under internal storage and flashed the ROM and twrp with it. After it just rebooted back to recovery every time I tried normal boot. (I'm assuming I F'd up by wiping storage). So I googled what to do about looping recovery and one suggestion was to factory reset so I did; I can no longer access recovery. I've tried flashing factory image, flashing the twrp zip, trying to boot straight to twrp, I can't get to adb sideload and it says "no valid slot to boot" on fastboot screen any suggestions?
Got another on fastboot, "error booting boot.img"
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
fury683 said:
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
Click to expand...
Click to collapse
Yes it does and I've got everything from twrp .zip and .IMG, factory images and ota zip.
I did make progress just now and switched to slot B and got TWRP to show up:laugh: might just sideload OTA and pretend this never happened
Update, adb sideload taking too long to start
wergrun said:
Yes it does and I've got everything from twrp .zip and .IMG, factory images and ota zip.
I did make progress just now and switched to slot B and got TWRP to show up:laugh: might just sideload OTA and pretend this never happened
Update, adb sideload taking too long to start
Click to expand...
Click to collapse
You need to get back to fastboot, and run the flash all bat file from the full factory image.
TonikJDK said:
You need to get back to fastboot, and run the flash all bat file from the full factory image.
Click to expand...
Click to collapse
I tried that but I keeps giving me an error, I'll post it when I get the chance
Problem SOLVED! used video by MaowDroid "Pixel 2 (XL): Un-root and return to stock using factory images"
fury683 said:
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
Click to expand...
Click to collapse
I have the same issue, except my computer will not recognize the device in fastboot. I tried two different computers, Windows 10 and laptop running Linux.
wergrun said:
Problem SOLVED! used video by MaowDroid "Pixel 2 (XL): Un-root and return to stock using factory images"
Click to expand...
Click to collapse
Followed the video, but I get an error:
'FAILED (remote: Failed to write to partition Not Found)'
I've tried: bootloader, bootloader_a, bootloader_b and bootloader_other and get the same error.
I'm stuck....
SS823 said:
Followed the video, but I get an error:
'FAILED (remote: Failed to write to partition Not Found)'
I've tried: bootloader, bootloader_a, bootloader_b and bootloader_other and get the same error.
I'm stuck....
Click to expand...
Click to collapse
I did get that too but it was because I forgot to put a space after "bootloader_a ", are you Stuck at around the 9 minute steps?
Yes, right around the end at 9 minutes. Everything works fine - bootloader, radio, etc. When I get to the end of the img zip file I get this message:
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.360s
I am at a loss.
Dear community. I screwed up.
I purchased my new OP7P and in all my excitement, logically, the first thing I went to do was to unlock the bootloader, install TWRP and root it, which I did successfully because I am pretty familiar with this on multiple phones. Long story short, here's what I did, and where my problem lies:
1. Went to install the Havoc Custom ROM by following their installation instructions, went ahead and booted to TWRP recovery
2. As instructed, wiped dalvik and /data
3. Flashed Havoc ROM and here is the part where I was supposed to flash TWRP installer
4. Forgot to reflash TWRP installer and rebooted to the now nonexisting recovery. - getting the dead android icon with the message "NO COMMAND"
5. After holding VOLUP + POWER managed to turn it off and then turn it on again with just POWER to be greeted with a message warning me that I am in a bootloop
and that I have two options; to try again or to "reset to factory settings", which I did, which booted me into the HavocOS.
The main problem here is that for some reason whenever I try to repeat the TWRP installation process using fastboot, by entering "fastboot boot twrp.img", it gives me the following error:
downloading 'boot.img'...
OKAY [ 1.340s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.343s
I have tried this on both Linux & Windows, same deal. The TWRP website has mentioned that if this happens I need root, but how do I root my phone without TWRP or "fastboot boot", and how do I install TWRP on the OP7P without livebooting TWRP?
Any help at all is truly appreciated. Thanks guys.
Download the MSM tool here and restore your phone. I've never used it but it gets everyone out of a brick.
I've used this tool a few times and it has gotten me out of a jam, just be sure to download the correct version for your phone. AFA your fastboot error, I got that until I let the OTA update to 9.5.11, then it worked again. https://forum.xda-developers.com/oneplus-7-pro/development/tool-tool-one-driversunlocktwrpfactory-t3930862
x3lade said:
The main problem here is that for some reason whenever I try to repeat the TWRP installation process using fastboot, by entering "fastboot boot twrp.img", it gives me the following error:
downloading 'boot.img'...
OKAY [ 1.340s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.343s
Click to expand...
Click to collapse
Try to fastboot boot the TWRP build -70 from here: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
It fixes the problem with "fastboot boot" not working on the official Android Q update. Not sure why that would apply to your case (custom ROM after already successfully installing TWRP). But it's very easy to try, and certainly can't hurt. And the error message you are getting is exactly the same as the official Android Q problem.