Related
HI all, i own a Honor 6 L02 and i have the following brick problems.
1. in normal boot i get RESCUE MODE error! func no9 func_boot_kernel
2.when i try to boot in recovery i get RESCUE MODE error no 10 func_boot_recovery
3when i try 3 buttons i get the same as no2
4.when i try fastboot(my phone is unlocked) i cannot flash ANYTHING from pc because i get failed remote command not allowed.
which i think is the major problem
I think it all initiated when i was in 532 lollipop and flashed wrong recovery(recovery for L04) in order to flash superuser which i did and everything was okay indeed.Until i wanted to move back to 316 stable kitkat, but i couldnot flash stock recovery because of the fail command not alowed,so i Installed Flashify ,flashed TWRP and then tried to flash image through twrp.
After rebooting i got bricked.ANY solutions?
Nobody can suggest a solution ? smth to begin from?
pudup said:
Is your bootloader unlocked? If so then the fastboot commands should work. Does your phone show up when you type "fastboot devices"?
If all fastboot still doesn't work, try updating the drivers. Download the latest multi tool and use that. Just flash a stock rom with multi tool or flash all the individual img files with fastboot manually.
Click to expand...
Click to collapse
Thanks for the reply.My bootloader says phone unlocked ,so i supposse it is.My phone shows up when i type fastboot devices.
Im using the latest multitool (and also tried different versions) and have installed the drivers on a fresh formatted windows 8.1 laptop!
the disaster problem is that i cannot flash ANYTHING with fastboot flash commands.For example:
sending recovery okay
writing recovery Failed error remote command not allowed.im getting this error with every single image file(boot,cust , system,recovery stock or custom)
pudup said:
Can you try locking your bootloader? Lock your bootloader and then switch off. Then unlock it and try flashing a recovery.
Also try this command after placing, let's say the twrp.img file for kitkat, in the fastboot folder.
"fastboot boot twrp.img"
That boots directly into twrp without flashing it. See if that works.
Click to expand...
Click to collapse
This is what i get when i try to relock bootloader
* daemon not runnig.starting it now on port 5037
daemon started successfully
T2FDU1482900...... fastboot
...
Failed (remote:stat not match)
finished total time 0.003
If i try to unlock it (although it s written phone unlocked) i get
FAILED ( remoteassword wrong)
shouldnt i get smth like bootloader already unlocked?
The weird thing is im 100% sure that im using the correct bootloader password because i have gotten
it from 3 different sources(local huawei,chinese site huawei a year ago, and the tool a guy has posted here on xda)
Last i have copied twrp.img in the folder and tried the command
fastboot boot twrp.img
downloading 'boot.img'
OKAY [1.047s]
booting...
FAILED(remote:command not allowed)
Thank you for your help,i appreciate it
Using fastboot flash your rom recovery again and your rom recovery
---------- Post added at 07:59 PM ---------- Previous post was at 07:55 PM ----------
dimikon said:
This is what i get when i try to relock bootloader
* daemon not runnig.starting it now on port 5037
daemon started successfully
T2FDU1482900...... fastboot
...
Failed (remote:stat not match)
finished total time 0.003
If i try to unlock it (although it s written phone unlocked) i get
FAILED ( remoteassword wrong)
shouldnt i get smth like bootloader already unlocked?
The weird thing is im 100% sure that im using the correct bootloader password because i have gotten
it from 3 different sources(local huawei,chinese site huawei a year ago, and the tool a guy has posted here on xda)
Last i have copied twrp.img in the folder and tried the command
fastboot boot twrp.img
downloading 'boot.img'
OKAY [1.047s]
booting...
FAILED(remote:command not allowed)
Thank you for your help,i appreciate it
Click to expand...
Click to collapse
you flash TWRP RECOVERY in your BOOT partition it is Wrong
in fast boot do that
for Boot.img (your rom num)
fastboot flash boot boot.img
for recovery (your rom num)
fastboot flash recovery recovery.img
adhamamar said:
Using fastboot flash your rom recovery again and your rom recovery
---------- Post added at 07:59 PM ---------- Previous post was at 07:55 PM ----------
you flash TWRP RECOVERY in your BOOT partition it is Wrong
in fast boot do that
for Boot.img (your rom num)
fastboot flash boot boot.img
for recovery (your rom num)
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
My friend,,, every image i try to flash via fastboot (recovery,boot,system,cust) gives me FAILED error:remote command not allowed
what i did with the twrp.img was the thing that the other guy advised to see if it would work
do you have a TWRP backup of your rom? if yes try restore it ....
if not
Search on this site for TWRP backup for your build num and Change the serial number for the backup copy with your phone serial number (folder name and change inside recovery.log file) (http://4pda.ru/forum/index.php?showtopic=671958&st=920)
adhamamar said:
do you have a TWRP backup of your rom? if yes try restore it ....
if not
Search on this site for TWRP backup for your build num and Change the serial number for the backup copy with your phone serial number (folder name and change inside recovery.log file) (http://4pda.ru/forum/index.php?showtopic=671958&st=920)
Click to expand...
Click to collapse
Thank you very much , but how will i be able to restore it ??? i cannot boot into recovery ,i get error no FUNC_BOOT_RECOVERY
read this http://forum.xda-developers.com/showpost.php?p=56662843&postcount=2945
adhamamar said:
read this http://forum.xda-developers.com/showpost.php?p=56662843&postcount=2945
Click to expand...
Click to collapse
No luck,what this tool does is similar to the multitool unbrick,just tries to flash the images in an automated way,and gives me the
FAILED error remote command not allowed
pudup said:
Sorry but it seems your phone is hard bricked. Take it to a service center.
The "command not allowed" error usually comes up for locked bootloaders or in some cases when usb debugging is not switched on. There is nothing i can think of right now for you to do.
I suggest you lie to the people at the service center and tell them this happened while you were doing a normal update that was given to you OTA.
Click to expand...
Click to collapse
what do you think would be the cost for repairing? i have asked at the local Huawei but they wont repair it because it is not bought from E.U. ,is there any chance that somebody would repair it without sending it back to china(after all guarantee is lost ,i own it for 1,5 years)
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..
Im fairly new at this kinda thing so i didnt know what i was doing. i tried flashing TWRP using fastboot but when i entered "fastboot boot recovery.img" it said "FAILED (remote: dtb not found). So i tried using the TWRP app and flashed my recovery, but when i went to recovery it was still stock recovery. And then because i didnt know what i was doing i flashed TWRP using the app to my boot and now when i boot it just shows the mi logo. Ive tried flashing it using MiFlash but the results were just the same. Pls help me
Nobic said:
Im fairly new at this kinda thing so i didnt know what i was doing. i tried flashing TWRP using fastboot but when i entered "fastboot boot recovery.img" it said "FAILED (remote: dtb not found). So i tried using the TWRP app and flashed my recovery, but when i went to recovery it was still stock recovery. And then because i didnt know what i was doing i flashed TWRP using the app to my boot and now when i boot it just shows the mi logo. Ive tried flashing it using MiFlash but the results were just the same. Pls help me
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
fastboot reboot when pressing vol up maybe?
"FAILED (remote: dtb not found).
Click to expand...
Click to collapse
You choose the wrong TWRP for flash to mi4c. Probably TWRP version for nougat rom flashed on lollipop rom.
Here https://forum.xda-developers.com/showpost.php?p=71120584&postcount=9 follow the steps & you'll be fine. Next time doesn't do anything stupid & read all the introductions before mess with your phone.
Ive tried flashing it using MiFlash but the results were just the same.
Click to expand...
Click to collapse
It can't be same if you flash xiaomi official rom using MiFlash. Looks like you are not flashed it properly. do it corrently .
My OnePlus 7 Pro keep booting into fastboot mode. Neither I can access recovery nor can start the phone. It's always comes back to recovery.
Please help me getting it done.
Bootloader is unlocked.
You haven't given enough info, tell us step by step how your "Bootloader is unlocked".
We would need to know if you did it properly, you probably need to go into the recovery and perform a "Full wipe". Unlocking the bootloader usually does that anyway.
The normal method is:
Enabled developer settings by pressing the version number in the about section 7 times and entering your pin
Copy the adb developer folder from the mounted OnePlus driver partition you usually get on your computer when attaching the phone, into a folder on your hard drive, and enable adb in developer settings.
In developer settings enable "OEM unlocking"
Reboot into fastboot mode
Open a command window (with admin privileges) in the folder you copied to your hard drive (In Windows, hold down shift and right click inside the folder, then click "Open Command Window..."
Run the command "fastboot oem unlock"
Accept the prompt shown on the phone
This will wipe the phone back to factory reset so ensure you have backed up your data, although you should be doing that before you even start.
Flash the appropriate TWRP recovery partition (which afaik isn't even available yet so I'm not sure why you would unlock the bootloader so soon to be honest
If you didn't perform those steps or performed them in the wrong order then you've done it wrong.
Performing a factory reset in the recovery partition may get it booting again but it's hard to know with the minimal information you've provided.
Although again, why are you unlocking the bootloader when there hasn't been a TWRP version released yet? You won't be able to flash anything, not even Magisk.
I've unlocked bootloader by command of OEM unlocking.
After than the unlock, I rebooted it's again And installed some Magisk file, which made it stuck at fastboot.
I can't access the Recovery nor can restart Phone.
All I can do is switched it off And get back into fastboot again after.
Yeah, you can't flash things with the default recovery (That's just made for flashing the default builds), that's most likely why. Magisk was made to be flashed with TWRP.
Did you use the test TWRP here? If so, then go to that thread for help.
If you can get into the OnePlus recovery you could maybe grab a build from here and flash the default rom back, then start again using the guide I showed you but, tbh, I would wait until a good TWRP build is established and Magisk is confirmed to be working.
That thread also looks like it has the default recovery image too so you can flash that back on the phone with :
fastboot flash recovery filename (Just put the recovery image into the same folder as your adb.exe and fastboot.exe
Then see if you can reboot into it and flash the stock rom back on from the same thread.
How can I get things done back, all I've is fastboot.
It's a New set, please help (
dmishra639 said:
How can I get things done back, all I've is fastboot.
It's a New set, please help (
Click to expand...
Click to collapse
If you have fastboot, I've just told you how to get the default recovery back in above.
---------- Post added at 05:45 PM ---------- Previous post was at 05:28 PM ----------
Reading that thread again, flashing recovery is not as simple as it used to be due to the A/B partition model used now, so you'll need to read the instructions shown for recovery. My guess is that you didn't read them properly and flashed the recovery to the wrong partition. If you have flashed that TWRP then you need to seek support in that thread.
It's not gonna work with me,
Even if I'll download the zip file it's only flashable with a Twrp or Stock recovery. As stock recovery is not working.
Even if I'll try to flash a Twrp recovery it's showing up an error to me :
PS C:\adb> fastboot devices
420bdc60 fastboot
PS C:\adb> fastboot boot C:\adb\recovery.img
downloading 'boot.img'...
OKAY [ 0.585s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.636s
PS C:\adb> fastboot flash recovery C:\adb\recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (18828 KB)...
OKAY [ 0.575s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.580s
PS C:\adb>
dmishra639 said:
It's not gonna work with me,
Even if I'll download the zip file it's only flashable with a Twrp or Stock recovery. As stock recovery is not working.
Even if I'll try to flash a Twrp recovery it's showing up an error to me :
PS C:\adb> fastboot devices
420bdc60 fastboot
PS C:\adb> fastboot boot C:\adb\recovery.img
downloading 'boot.img'...
OKAY [ 0.585s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.636s
PS C:\adb> fastboot flash recovery C:\adb\recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (18828 KB)...
OKAY [ 0.575s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.580s
PS C:\adb>
Click to expand...
Click to collapse
This will sound stupid, but I had similar issues with the pixel and it was due to drivers and the port. Tried from a different machine and worked. Do you have the luxury to do so ?
Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.
dmishra639 said:
Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.
Click to expand...
Click to collapse
Grab this fastboot rom and flash...
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Why are you trying to flash recovery partitions when they don't exist on this device? Recovery is on the boot partition.
dmishra639 said:
Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.
Click to expand...
Click to collapse
Since you are familiar with custom rom,unlocked bootloader etc you should had known already that you must NOT flash any kind Magisk staff without having proper and functional twrp.
Even if it flashed successful that doesn't mean will work after reboot and normal restart.
That why you've brick your device.
And on the other hand with A/B partition things has changed dramatically evolving all custom made staff and how they works.
Oneplus device not work the same way as Xiaomi you've described.
Sent from my iPad using Tapatalk Pro
LLStarks said:
Why are you trying to flash recovery partitions when they don't exist on this device? Recovery is on the boot partition.
Click to expand...
Click to collapse
paatha13 said:
Since you are familiar with custom rom,unlocked bootloader etc you should had known already that you must NOT flash any kind Magisk staff without having proper and functional twrp.
Even if it flashed successful that doesn't mean will work after reboot and normal restart.
That why you've brick your device.
And on the other hand with A/B partition things has changed dramatically evolving all custom made staff and how they works.
Oneplus device not work the same way as Xiaomi you've described.
Sent from my iPad using Tapatalk Pro
Click to expand...
Click to collapse
Any post that describe exactly what changed? I havent flashed custom roms/kernels in close to two years due to OOS being satisfying enough. What I have done is fastboot into twrp and flash magisk(I believe). Will I still be able to do that with OP7 Pro?
dmishra639 said:
My OnePlus 7 Pro keep booting into fastboot mode. Neither I can access recovery nor can start the phone. It's always comes back to recovery.
Please help me getting it done.
Bootloader is unlocked.
Click to expand...
Click to collapse
I forget the command, but change the boot slot and try to reboot.
tech_head said:
I forget the command, but change the boot slot and try to reboot.
Click to expand...
Click to collapse
Fastboot flash boot C://path/to/recovery.img
SysAdmNj said:
Any post that describe exactly what changed? I havent flashed custom roms/kernels in close to two years due to OOS being satisfying enough. What I have done is fastboot into twrp and flash magisk(I believe). Will I still be able to do that with OP7 Pro?
Click to expand...
Click to collapse
You can read over here on 6T device details of how thing work with A/B partition.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
https://twrp.me/oneplus/oneplus6t.html
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
Also follow this thread about 7 Pro situation and how well work over time
[RECOVERY][3.3.1-2][guacamole]Unofficial TWRP recovery for OnePlus 7 Pro(Testing)
Sent from my iPad using Tapatalk Pro
joemossjr said:
Fastboot flash boot C://path/to/recovery.img
Click to expand...
Click to collapse
Man, thank you so much
You literally made my day,
Wht I've did wrong in a flow was I had given the command: fastboot flash boot and the magisk location.
That was a stupidity, all I forgot was the command.
Now I used the same command and then used oxygen os fastboot flashable all bat file, as suggested by a member.
And here's my phone back. )
Thanks
In case, I'm completely New to OnePlus
It someone suggest me how to Root OnePlus 7 Pro normally, cuz I've to edit the build prop due to some reason.
My bootloader is unlocked but can't flash custom recovery.
dmishra639 said:
In case, I'm completely New to OnePlus
It someone suggest me how to Root OnePlus 7 Pro normally, cuz I've to edit the build prop due to some reason.
My bootloader is unlocked but can't flash custom recovery.
Click to expand...
Click to collapse
I remember when I edit the buildi prob on my v20 to be recognized as a pixel so google assistant can work and that bricked my device.
Robert235 said:
I remember when I edit the buildi prob on my v20 to be recognized as a pixel so google assistant can work and that bricked my device.
Click to expand...
Click to collapse
Man I've a 2gb daily add on (for 3 months), which will only gonna work with my previous device (Redmi note 5 pro).
So, I've to change OnePlus as Note 5 Pro as same.
I've did that tons of time on my past phone,it never did a brick TBH.
after updating to android q dp3 on my t mobile version of one plus 7 pro to get my bootloader unlocked i restarted into fast boot to install twrp and i followed multiple post of people doing it but i get the error msg below or it says the same thing but it says success. i even tried fastboot flash boot twrp.img. after doing it i restart and it goes right to fastboot and not twrp. Do i have to downgrade out of dp3 first? im stuck any help would be appreciated!
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.209s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.211s
I forgot to mentioned that it worked the very first time and i got into twrp following the video on here xda posted but i failed to flash a custom rom and it was stuck in the splash screen when i installed havoc os rom and i used msm tool to revert back to stock and start over now i cant get twrp re installed
bj8622 said:
I forgot to mentioned that it worked the very first time and i got into twrp following the video on here xda posted but i failed to flash a custom rom and it was stuck in the splash screen when i installed havoc os rom and i used msm tool to revert back to stock and start over now i cant get twrp re installed
Click to expand...
Click to collapse
you need atleast on oos 9.5.7 firmware to able flash twrp again
can i instALL TWRP if im on 9.5.11? right now im on the 9.5.1 downgrade from dp3
bj8622 said:
can i instALL TWRP if im on 9.5.11? right now im on the 9.5.1 downgrade from dp3
Click to expand...
Click to collapse
Yes, also 9.5.10 works
benny3 said:
Yes, also 9.5.10 works
Click to expand...
Click to collapse
What do you flash to get back to 9.5.10 or 9.5.11? Using the downgrade re-locked my bootloader.