Let me explain my story.
Rooted phone, installed dual recovery, decided to have some xposed modules, installed a ton, went into a boot animation, went into recovery and decided to clear system and now I can only access fastboot mode. I tried to fastboot flash boot Z3_DooMLoRD_AdvStkKernel_v01_FW-93.img, but i get FAILED (remote: Command not allowed) at the end so it doesn't work.
I don't think my bootloader is unlocked. So I guess I bricked my phone unless someone has a way to fix it. I literally rooted my phone two days ago.
Flashtool says the same thing.
Model number: D6603.
EDIT: Currently testing if I can flash an FTF.
EDIT: Praise the lord, flashing a new FTF works amazing.
/Thread.
Hi,
I'v got used Razer phone today with Oreo 8.1, tried to unlock boot but it failed. Commands I've ran so far (debug and oem unlock both on)
adb reboot bootloader
got the download mode
android bootloader interface version 11 driver from google.
fastboot -i 0x1532 devices
xxx40xxxx fastboot (xx are numbers)
then
fastboot -i 0x1532 flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.004s
on the phone download mode words disappeared and no driver appear in the PC
also tried another root method with posted here in XDA for Oreo but still not working.
Please I need help as I bought the phone to root and enjoy it
Majed
NeverMind, used another laptop and i was able to do it... I think AMD has some usb filters or something
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.
Hello Everyone, I lost my hope with google pixel.
Let me tell you my problem.
1. Custom Rom installed
2. Oem unlock disabled in developer settings
3. and I accidentally locked the boot loader
4. and top of that not been able to boot into recovery because I lost it when I locked the boot loader I think
so as a result I always get this error
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
I tried
flashing unlock
fastboot oem unlock
fastboot flashing unlock_critical
After 2/3 months of relentless trying I lost hope.If anyone can help please help me.
iqbal.jewel said:
Hello Everyone, I lost my hope with google pixel.
Let me tell you my problem.
1. Custom Rom installed
2. Oem unlock disabled in developer settings
3. and I accidentally locked the boot loader
4. and top of that not been able to boot into recovery because I lost it when I locked the boot loader I think
so as a result I always get this error
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
I tried
flashing unlock
fastboot oem unlock
fastboot flashing unlock_critical
After 2/3 months of relentless trying I lost hope.If anyone can help please help me.
Click to expand...
Click to collapse
You can't fix it. :crying:
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.