TWRP Boot Command Not Working - OnePlus 7 Pro Questions & Answers

I am on the DP 3 beta and wanted to go back to my custom ROM so i went to boot to TWRP and i get booting FAILED (remote: unknown command). So i used the rollback file to go back to 9.0 and i get the same error. Anyone know why this isn't working all the sudden?

I had the same issue.

sabrdawg said:
I had the same issue.
Click to expand...
Click to collapse
I fixed it. It's an issue with earlier versions of OOS 9.5.10 fixed it.

Got the same problem on 9.5.11.

TechOut said:
I am on the DP 3 beta and wanted to go back to my custom ROM so i went to boot to TWRP and i get booting FAILED (remote: unknown command). So i used the rollback file to go back to 9.0 and i get the same error. Anyone know why this isn't working all the sudden?
Click to expand...
Click to collapse
U can not fastboot boot twrp on anything before 9.5.6 or 7 and none of the q betas I've tried allow fastboot boot so u have to fastboot flash boot twrp.img to current slot and if the kernel doesn't match the q beta kernel it won't boot.
So find one that matches.

The fastboot boot command is broken on developer previews as well as versions older than 9.5.7

Related

how do you root this and put twrp?

im used to Nexus 6 which is differnt way...this is LO4 model bootloader is unlocked
i got drivers installed but not sure which files to use or how to do it
am i reading right? there is no lo4 root? if not any idea how long untill there will be?
Same procedure as L09
leo5111 said:
am i reading right? there is no lo4 root? if not any idea how long untill there will be?
Click to expand...
Click to collapse
Flash TWRP normally, then Magisk latest Beta
what do i put in fastboot to flash it? and do i use the berkly 3.2.10 one?
anyone? because i tried fastboot command with twrp 3.2.10 and it it says it went but then when i try to boot into it says software failure? so i think im using wrong version or command?
ok i dont know WTF it installed twrp i can even get phone to go into twrp but it reboots back out to fastboot rescue mode?
tried 3.2.11 and it just loops back to fastboot...i read that they could block magisk would that stop installtion of twrp as well? i uses fastboot command fastboot flash recovery_ramdisk TWRP.img yes i named the image TWRP.img
did huawei allready start blocking magisk/twrp install? because it will say twrp installed BUT will go into twrp for like 10 seconds and then reboot to fastboot and phone updated itself like yesterday
says im on build bkl-lo4 8.1.0.120 "c567" emui version 8.0.0 android 8.1.0 security patch july 1st kernal 4.4.103+ tues july 17th
https://openkirin.net/ i installed lineage from that ran it through fastboot after reinstalling stock rom
found out my issue i think before i re-installed the recovery with the downloader on the phone it would not kill the messed up twrp was on it and when it went to stock recovery woud not let me wipe it, re-install fixed all that i think first time i installed twrp ran wrong command and installed twrp to wrong place, now ill try installing twrp now that i know proper fast boot is fastboot flash recovery_ramdisk TWRP.img correct?
i give up for now im on lineage with that other app tried installing twrp with that command and does same crap goes into twrp for like 10 seconds then kicks out to fastboot
i dont know WTF i ran this................ fastboot flash recovery_ramdisk TWRP.img does one of 2 things either "A" boots into twrp for like 10 sec and kicks back out to fastboot or says software install failure or something like that oh ya its not bootlooped though if you just let phone go it will reboot into OS

Unable to boot TWRP.IMG

Ive downloaded TWRP.img from official site
unlocked BL > fastboot boot twrp.img
i get this error
"failed (remote: 'unknown command')
any ideas?
ive even used the MSM tool to go back to 9.5.3
unlocked BL
rebooted BL and tried "fastboot boot twrp.img" with the same error.
i think if you update to 9.5.8 the bootloader no longer accepts fastboot boot commands.
virtyx said:
Ive downloaded TWRP.img from official site
unlocked BL > fastboot boot twrp.img
i get this error
"failed (remote: 'unknown command')
any ideas?
ive even used the MSM tool to go back to 9.5.3
unlocked BL
rebooted BL and tried "fastboot boot twrp.img" with the same error.
Click to expand...
Click to collapse
9.5.3 does not have that capability, update to 9.5.4
Bradl79 said:
9.5.3 does not have that capability, update to 9.5.4
Click to expand...
Click to collapse
i have updated to 9.5.8 via fastboot same problem
ill try 9.5.7 via local updater.
Confirmed working on 9.5.4.
Not sure about others yet.
virtyx said:
i have updated to 9.5.8 via fastboot same problem
ill try 9.5.7 via local updater.
Click to expand...
Click to collapse
slayerh4x said:
Confirmed working on 9.5.4.
Not sure about others yet.
Click to expand...
Click to collapse
ok works on 9.5.7 via local updater
ill try 9.5.8 i think the fastboot updater breaks this functionality somehow because i fastbooted 9.5.7 and it didnt work earlier. but doing it via local updater works.
virtyx said:
Ive downloaded TWRP.img from official site
unlocked BL > fastboot boot twrp.img
i get this error
"failed (remote: 'unknown command')
any ideas?
ive even used the MSM tool to go back to 9.5.3
unlocked BL
rebooted BL and tried "fastboot boot twrp.img" with the same error.
Click to expand...
Click to collapse
Are you typing in 'twrp.img' or dragging and dropping the actual file into adb?
I tried the command with 9.5.8 and it works well with both CMD and Powershell using minimal ADB files. Looking well, not sure if twrp official is able to boot that way or is meant to be used for just flashing. maybe the one in the guide twrp-3.3.1-29, 30,31 etc-guacamole.img are the ones you should use.
GUGUITOMTG4 said:
I tried the command with 9.5.8 and it works well with both CMD and Powershell using minimal ADB files. Looking well, not sure if twrp official is able to boot that way or is meant to be used for just flashing. maybe the one in the guide twrp-3.3.1-29, 30,31 etc-guacamole.img are the ones you should use.
Click to expand...
Click to collapse
Just tested and I agree. Try the latest Unofficial TWRP
Bradl79 said:
Just tested and I agree. Try the latest Unofficial TWRP
Click to expand...
Click to collapse
Doesn't work if you flash the rom via fastboot for some reason, flashed via local update and it worked
virtyx said:
Doesn't work if you flash the rom via fastboot for some reason, flashed via local update and it worked
Click to expand...
Click to collapse
I think this has something to do with slot A/B. I saw other folks having problems with "fastboot boot" for TWRP not working, until they switched slots.
redpoint73 said:
I think this has something to do with slot A/B. I saw other folks having problems with "fastboot boot" for TWRP not working, until they switched slots.
Click to expand...
Click to collapse
hmm maybe
i just flashed zip in local updater and it worked again.
hi guys , how to flash using local updater ? i have the same case i am new
Guys , I am new here , I had a stuck in fastboot then using msm tool back to 9.5.3 . I re did the unlock and then whenver I tried to install twrp using fastboot , it shows remote : unknown error
How I can install twrp and magisk ?? And update to 10 ?
I need step by step please . Considering I am on 9.5.3 OEM unlocked but I am unable to use fastboot boot option.
flash stock rom using fast boot
new_world_2006 said:
Guys , I am new here , I had a stuck in fastboot then using msm tool back to 9.5.3 . I re did the unlock and then whenver I tried to install twrp using fastboot , it shows remote : unknown error
How I can install twrp and magisk ?? And update to 10 ?
I need step by step please . Considering I am on 9.5.3 OEM unlocked but I am unable to use fastboot boot option.
Click to expand...
Click to collapse
I just got my phone 2 days ago. So I started on 9.5.3 or something. Upgraded to 10 and rooted it by following a guide which is just the usual root method for me but I didn't want to screw anything up.
So I suggest just stay unrooted and upgrade to A10. Then root like normal (fastboot boot twrp, flash twrp zip, flash magisk). That's all I did and I'm having no issues on my phone.

OnePlus 6 unable to boot into TWRP -- cannot reinstall OOS. Next steps?

OnePlus 6, Ubuntu 18.04. I think I've basically wiped everything.
I am trying to follow https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 but I can't get either of these to boot:
Code:
fastboot boot TWRP.img
or
Code:
fastboot boot twrp-3.3.1-2-enchelada.img
Doing this gives me the OnePlus logo with "Fastboot Mode" underneath and it hangs.
I've tried
Code:
fastboot --set-active=b
fastboot flash slot_b TWRP.img
and
Code:
fastboot flash slot_b twrp-3.3.1-2-enchilada.img
Rebooting into slot_b recovery gives me the warning about "The boot loader is unlocked and software integrity cannot be guaranteed. ... PRESS POWER KEY TO PAUSE BOOT" and then it hangs.
I am trying to get back to stock OOS so I can try Havoc but I'll settle for the former just to get the phone working.
I have a nandroid backup, I rsynced my /sdcard, and I have a Titanium backup.
I really need some guidance here...
What should I make of
Code:
$fastboot erase recovery
erasing 'recovery'...
FAILED (remote: Check device console.)
iconoclasthero said:
OnePlus 6, Ubuntu 18.04. I think I've basically wiped everything.
I am trying to follow https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 but I can't get either of these to boot:
Code:
fastboot boot TWRP.img
or
Code:
fastboot boot twrp-3.3.1-2-enchelada.img
Doing this gives me the OnePlus logo with "Fastboot Mode" underneath and it hangs.
I've tried
Code:
fastboot --set-active=b
fastboot flash slot_b TWRP.img
and
Code:
fastboot flash slot_b twrp-3.3.1-2-enchilada.img
Rebooting into slot_b recovery gives me the warning about "The boot loader is unlocked and software integrity cannot be guaranteed. ... PRESS POWER KEY TO PAUSE BOOT" and then it hangs.
I am trying to get back to stock OOS so I can try Havoc but I'll settle for the former just to get the phone working.
I have a nandroid backup, I rsynced my /sdcard, and I have a Titanium backup.
I really need some guidance here...
Click to expand...
Click to collapse
What rom was installed last before all this began.
MrSteelX said:
What rom was installed last before all this began.
Click to expand...
Click to collapse
Havoc OS (Havoc-OS-v3.1-20200120-enchilada-Official.zip). The problem was that somehow my pin got corrupted/changed after my first couple of boots into Havoc. That precipitated a big mess.
That said, I switched to my desktop (also running Ubuntu 18.04) and got a new version of the SDK directly from android.com, and replaced the files that came from the repo. That was able to do the formatting and install the stock image so now I just need to go through the procedure again...
I wish I'd had a better sense of what was going on with the partition table/fstab/blkid because I was able to get in with adb shell and I theoretically could have manually formatted...
iconoclasthero said:
OnePlus 6, Ubuntu 18.04. I think I've basically wiped everything.
I am trying to follow https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 but I can't get either of these to boot:
Code:
fastboot boot TWRP.img
or
Code:
fastboot boot twrp-3.3.1-2-enchelada.img
Doing this gives me the OnePlus logo with "Fastboot Mode" underneath and it hangs.
I've tried
Code:
fastboot --set-active=b
fastboot flash slot_b TWRP.img
and
Code:
fastboot flash slot_b twrp-3.3.1-2-enchilada.img
Rebooting into slot_b recovery gives me the warning about "The boot loader is unlocked and software integrity cannot be guaranteed. ... PRESS POWER KEY TO PAUSE BOOT" and then it hangs.
I am trying to get back to stock OOS so I can try Havoc but I'll settle for the former just to get the phone working.
I have a nandroid backup, I rsynced my /sdcard, and I have a Titanium backup.
I really need some guidance here...
Click to expand...
Click to collapse
It looks like you had android 10 and you flashed official twrp, which is android 9 only, which happened to me before. I could recommend using this to flash OOS through fastboot.
[email protected] said:
It looks like you had android 10 and you flashed official twrp, which is android 9 only, which happened to me before. I could recommend using this to flash OOS through fastboot.
Click to expand...
Click to collapse
I haven't checked to see what, if any, recovery is on there now. I'm assuming that the stock one was flashed on when I was able to get 10.3.0-OnePlus6Oxygen_22_OTA_042_all_1912142031_0fb330-FASTBOOT.zip. Now that I've got it working again, how do I put Havoc on it? Isn't that based on Android 10 ... ?
I found this in one of the many tabs I had open from figuring all this out: https://del.dog/pelihovape.txt. I wish it had some version numbers!
iconoclasthero said:
I haven't checked to see what, if any, recovery is on there now. I'm assuming that the stock one was flashed on when I was able to get 10.3.0-OnePlus6Oxygen_22_OTA_042_all_1912142031_0fb330-FASTBOOT.zip. Now that I've got it working again, how do I put Havoc on it? Isn't that based on Android 10 ... ?
I found this in one of the many tabs I had open from figuring all this out: https://del.dog/pelihovape.txt. I wish it had some version numbers!
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815 ?
iconoclasthero said:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815 ?
Click to expand...
Click to collapse
iconoclasthero said:
I haven't checked to see what, if any, recovery is on there now. I'm assuming that the stock one was flashed on when I was able to get 10.3.0-OnePlus6Oxygen_22_OTA_042_all_1912142031_0fb330-FASTBOOT.zip. Now that I've got it working again, how do I put Havoc on it? Isn't that based on Android 10 ... ?
I found this in one of the many tabs I had open from figuring all this out: https://del.dog/pelihovape.txt. I wish it had some version numbers!
Click to expand...
Click to collapse
I was looking around but I could not find what is going on with Havoc OS. I would probably recommended choosing a better maintained ROM with up to date instructions and support. Maybe Pixen or something. I was only able to find this old thread. Maybe you have better luck.
But if you really want Havoc, figure out first if it is androdi 9 or 10. If it is 10, use malfuriono unofficial twrp. If it is 9, you have to downgrade to OOS 9.0.9 first. Also, dirty flashes tend to cause problems, I would not recommended doing that. Make sure you wipe appropriate partitions

Need help for soft brick (eRecovery not working)

What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
hey i can help ! which version of twrp are you trying to flash ?
lmaohelp said:
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
Click to expand...
Click to collapse
The update website isn't going to come back anytime soon. But if you just don't mind opening your device again(you need to access the test point), there's a fix. this method doesn't just need anything. even if your device is hard bricked, it can get you back running. This was described in a youtube video with working links based on a forum on xda.
link : click here
I got a similar problem recently but I flashed update.zip of emui 8 - > Bootlooped - > factory reset with twrp - > successfully booted but doesn't get past the setup screen. Fix : flashed a gsi treble image(based on android 10) - > working perfect except for camera and volte.
Venkata Lochan Nune said:
The update website isn't going to come back anytime soon. But if you just don't mind opening your device again(you need to access the test point), there's a fix. this method doesn't just need anything. even if your device is hard bricked, it can get you back running. This was described in a youtube video with working links based on a forum on xda.
link : click here
I got a similar problem recently but I flashed update.zip of emui 8 - > Bootlooped - > factory reset with twrp - > successfully booted but doesn't get past the setup screen. Fix : flashed a gsi treble image(based on android 10) - > working perfect except for camera and volte.
Click to expand...
Click to collapse
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
King_of_Android said:
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
Click to expand...
Click to collapse
My bad , I thought the update website to be huawei's official one(something like update.hicloud and all isn't it?). Well, thanks for the information but I still prefer gsi. It's buttery smooth .
And one more thing, if you follow the youtube video I mentioned, you don't need any gsi. You can get your device back on stock EMUI 5.
King_of_Android said:
hey i can help ! which version of twrp are you trying to flash ?
Click to expand...
Click to collapse
Hey I have a doubt... Will the recoveries we find in twrp official website / app work on EMUI 8? I wanted to try them but I'm afraid I might brick my device again. Getting it back is a hectic thing and I already had to face it thrice. LOL .
King_of_Android said:
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
Click to expand...
Click to collapse
Hi, thanks for trying to help! I am using the website to install the firmware but I am having problems with it currently, and I made a post about it, if you could help me with that it would be greatly appreciated.
lmaohelp said:
Hi, thanks for trying to help! I am using the website to install the firmware but I am having problems with it currently, and I made a post about it, if you could help me with that it would be greatly appreciated.
Click to expand...
Click to collapse
I tried using that website but I wasn't able to figure out how to use it. So just left it. Did you try the method which I described earlier?
Venkata Lochan Nune said:
I tried using that website but I wasn't able to figure out how to use it. So just left it. Did you try the method which I described earlier?
Click to expand...
Click to collapse
I haven't tried to use the method you posted yet, because it is a bit more lengthy and complicated. If the method I was using does not work I'll use the video and let you know how it goes. Thanks!
lmaohelp said:
I haven't tried to use the method you posted yet, because it is a bit more lengthy and complicated. If the method I was using does not work I'll use the video and let you know how it goes. Thanks!
Click to expand...
Click to collapse
Well, just clear these things:
Is your bootloader still unlocked?
Did you try using another recovery image instead of the one you are getting error for?
Venkata Lochan Nune said:
Well, just clear these things:
Is your bootloader still unlocked?
Did you try using another recovery image instead of the one you are getting error for?
Click to expand...
Click to collapse
My bootloader is still unlocked, yes. However, I did not try to flash another recovery image, as I was not sure where I could find one that worked. I forgot which image I used at first but it had worked the first time, so that was why I did not bother finding a different recovery. Do you have a suggestion for a recovery to install?
lmaohelp said:
My bootloader is still unlocked, yes. However, I did not try to flash another recovery image, as I was not sure where I could find one that worked. I forgot which image I used at first but it had worked the first time, so that was why I did not bother finding a different recovery. Do you have a suggestion for a recovery to install?
Click to expand...
Click to collapse
I'm attaching one that works with emui 8 try using it (Remember you have to flash it to recovery_ramdisk).
Well after reading your post 1 again, I think there's no such partition as recovery_ramdisk(because it will be there only from android 8). So find a recovery in google which works on hi6250 devices with emui 4. That should work. Update me with the result
lmaohelp said:
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
Click to expand...
Click to collapse
hi
can you boot into recovery (must be TWRP) at the moment? then try the following...click the link in post 3 and in youtube expand the info...then click the unbrick link and download the oeminfo.
on the phone (TWRP) recovery flash the oeminfo in to the oeminfo partion...reboot to erecovery and then download the stock rom....after this reboot into system
i had unbrick some huawei devices with this method and it helps e´very time
solong
speedson
speedson said:
hi
can you boot into recovery (must be TWRP) at the moment? then try the following...click the link in post 3 and in youtube expand the info...then click the unbrick link and download the oeminfo.
on the phone (TWRP) recovery flash the oeminfo in to the oeminfo partion...reboot to erecovery and then download the stock rom....after this reboot into system
i had unbrick some huawei devices with this method and it helps e´very time
solong
speedson
Click to expand...
Click to collapse
His problem us with twrp.
He can only access fastboot but isn't able to flash twrp...
Venkata Lochan Nune said:
Well after reading your post 1 again, I think there's no such partition as recovery_ramdisk(because it will be there only from android 8). So find a recovery in google which works on hi6250 devices with emui 4. That should work. Update me with the result
Click to expand...
Click to collapse
So I have tried many different recoveries, such as ones for EMUI 4 and 5 and flashing directly to recovery, which gave me an error "image verification failed", and flashing an EMUI 8 to ramdisk would give me the same error as before. I think the partitions on this device is really messed up lol. Also, when I type fastboot reboot recovery, it would just get stuck at the loading screen, so does that mean there is no working recovery installed?
lmaohelp said:
So I have tried many different recoveries, such as ones for EMUI 4 and 5 and flashing directly to recovery, which gave me an error "image verification failed", and flashing an EMUI 8 to ramdisk would give me the same error as before. I think the partitions on this device is really messed up lol. Also, when I type fastboot reboot recovery, it would just get stuck at the loading screen, so does that mean there is no working recovery installed?
Click to expand...
Click to collapse
Maybe yes. Did you try directly booting the image without flashing?
Code:
fastboot boot recovery.img
Venkata Lochan Nune said:
Maybe yes. Did you try directly booting the image without flashing?
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
Yup, I tried that as well, and it told me "invalid command"
lmaohelp said:
Yup, I tried that as well, and it told me "invalid command"
Click to expand...
Click to collapse
Well as you said, you partitions must have been really messed up. I have no other ideas except the test point method.
Are you trying anything else?
Ok we have some option that could help you...
Im read in the 4PDA (the russian XDA xD) forum that it should be possible to flash the oeminfo by fastboot command. So just download the HWOTA_BLN_Eng and expand it. Then go to 7 or 8 Folder and there you go to oeminfo folder. There you choose the right one for your Device and local area...for example BLN-L21 (Device) C432 (European Area)
Extract the file to your desktop and rename it to BLN-L21C432.img
--->be sure that you have the right Device driver installed and the right ADB driver for your device to<---
ok now Copy and Paste the BLN-L21C432.img to ADB folder and start command with admin rights
start the phone into fastboot mode
--->bootloader must be unlocked<---
in the command
fastboot flash oeminfo BLN-L21C432.img
wait for the result and it can not hurt to pray a bit in this moment...hihi
if this have success...you type in command
fastboot reboot
wait to the screen you can press 3 seconds Vol+ to go into erecovery....connect to wlan and it should work step by step like it should.
after download and recover the stock rom reboot and go again to erecover by press Vol+ for 3 seconds and now go to the second option...wipe data/factory reset and write yes+enter
in stock recovery wipe Data after that wipe Cache...reboot and wait that system boot the initial boot for first setup.
If this will not working...tell me what honor 6x you have and wich local area you are from and wich firmware you stock had before you doing wronng
good luck bro
solong
speedson

Can't Boot to twrp recovery (just displying twrp logo)

Hi guys,
just received from my sister a oneplus 6 and i tried to flash a new custom rom after updating the system. I was following the guide posted on these forum but, when i tried to boot from fastboot to twrp it just display endless the twrp logo. I tried to boot with an older twrp or blu spark but nothing, they all make QUALCOMM crashdump, just the latest never go past the twrp logo. Tried to search for someone with a similar problem but i couldnt find anything about my same problem. Thanks in advance.
Enossob said:
Hi guys,
just received from my sister a oneplus 6 and i tried to flash a new custom rom after updating the system. I was following the guide posted on these forum but, when i tried to boot from fastboot to twrp it just display endless the twrp logo. I tried to boot with an older twrp or blu spark but nothing, they all make QUALCOMM crashdump, just the latest never go past the twrp logo. Tried to search for someone with a similar problem but i couldnt find anything about my same problem. Thanks in advance.
Click to expand...
Click to collapse
Which android version are you? 9 10 11?
1. Unlock Bootloader (if is already unlocked, skip this step)
2. download platform tools and unpack
3. copy twrp img and installer zip to platform tools folder location
4. open cmd
5. reboot phone to bootloader
6. write in cmd fastboot erase userdata
7. then write fastboot boot twrp-file-image-name.img
8. twrp is booted, go to advanced and choos option Flash current twrp
9. if is done, then reboot to recovery
10. go to wipe option, choose format data and type yes
11. now you can flash rom using rom flashing instructions
12. remember, after done rom flashing, FLASH twrp installer
@Noob9496 hey dude thanks, i found Someone who had my same problem and I resolved too with fastboot erase userdata so I could had finally boot into twrp cause that was my main problem.
@croperas yeah that was the problem too, cause when I had finally my sweet rom, syberia os (the only android 12 available atm for op6) I tried to go back to the recovery but can't, tried reinstall everything but I couldn't so after some research couldn't find anything, but anyone who had problems with recovery almost always had problems with incompatible versions (like twrp for android 10 but had android 11) so I then realized it isn't still available a custom recovery for android 12 for op6. So after erasing everything its all fine. Thanks a lot guys really appreciated.
Enossob said:
@Noob9496 hey dude thanks, i found Someone who had my same problem and I resolved too with fastboot erase userdata so I could had finally boot into twrp cause that was my main problem.
@croperas yeah that was the problem too, cause when I had finally my sweet rom, syberia os (the only android 12 available atm for op6) I tried to go back to the recovery but can't, tried reinstall everything but I couldn't so after some research couldn't find anything, but anyone who had problems with recovery almost always had problems with incompatible versions (like twrp for android 10 but had android 11) so I then realized it isn't still available a custom recovery for android 12 for op6. So after erasing everything its all fine. Thanks a lot guys really appreciated.
Click to expand...
Click to collapse
Glad it worked out for you
Noob9496 said:
1. Unlock Bootloader (if is already unlocked, skip this step)
2. download platform tools and unpack
3. copy twrp img and installer zip to platform tools folder location
4. open cmd
5. reboot phone to bootloader
6. write in cmd fastboot erase userdata
7. then write fastboot boot twrp-file-image-name.img
8. twrp is booted, go to advanced and choos option Flash current twrp
9. if is done, then reboot to recovery
10. go to wipe option, choose format data and type yes
11. now you can flash rom using rom flashing instructions
12. remember, after done rom flashing, FLASH twrp installer
Click to expand...
Click to collapse
Enossob said:
@Noob9496 hey dude thanks, i found Someone who had my same problem and I resolved too with fastboot erase userdata so I could had finally boot into twrp cause that was my main problem.
@croperas yeah that was the problem too, cause when I had finally my sweet rom, syberia os (the only android 12 available atm for op6) I tried to go back to the recovery but can't, tried reinstall everything but I couldn't so after some research couldn't find anything, but anyone who had problems with recovery almost always had problems with incompatible versions (like twrp for android 10 but had android 11) so I then realized it isn't still available a custom recovery for android 12 for op6. So after erasing everything its all fine. Thanks a lot guys really appreciated.
Click to expand...
Click to collapse
I have the same problem after flashing OO 11.1.2.2. I made a mistake flashing the wrong patched image to get rooted again but doing this I lost the access to twrp and now there is no recovery anymore. If I try to boot into any older version of twrp I receive a crashdump, if I try to boot to twrp 3.6.0 it gets stuck to logo. If I use the command "fastboot erase userdata" do I lose something?
tenderloin83 said:
I have the same problem after flashing OO 11.1.2.2. I made a mistake flashing the wrong patched image to get rooted again but doing this I lost the access to twrp and now there is no recovery anymore. If I try to boot into any older version of twrp I receive a crashdump, if I try to boot to twrp 3.6.0 it gets stuck to logo. If I use the command "fastboot erase userdata" do I lose something?
Click to expand...
Click to collapse
Yeah, everything
Enossob said:
Yeah, everything
Click to expand...
Click to collapse
Is there another way to restore twrp?
I don't use twrp anymore. Attached is Magisk patched boot for OP6 11.1.2.2 I patched from the latest payload.
fastboot flash boot_a magisk_patched-23000_OP6_11.1.2.2.img
fastboot flash boot_b magisk_patched-23000_OP6_11.1.2.2.img
tenderloin83 said:
Is there another way to restore twrp?
Click to expand...
Click to collapse
Install the twrp installer directly from magisk
What I did was trying to install Lineage OS 18.1 (the latest nightly from Jan 11 2022) with Lineage OS Recovery. Following the official wiki I always got stuck in the lineage os boot animation. Never got past that. Tried to fastboot boot twrp.img but TWRP stuck on logo. I think I never tried to boot twrp with the userdata erased. I think I will try it.
Anyone trying to install the twrp, check out SHRP recovery for OP6/t. Boot the img and flash the zip from that thread. tested works with both OP6 and OP6t in OOS 11.1.2.2.

Categories

Resources