Database Info

TWRP-3.2.0-0-sailfish.img Installing.

I followed the instructions on https://www.xda-developers.com/how-to-install-twrp/
when i run -- fastboot flash recovery twrp-2.8.x.x-xxx.img
(in my case -- fastboot flash recovery twrp-3.2.0-0-sailfish.img)
target reported max download size of 536870912 bytes
sending 'recovery' (26520 KB)...
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED ((remote: partition [recovery] doesn't exist
finished. total time 1.000s
I also tried this method from https://twrp.me/google/googlepixel.html
Installation:
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
this all seemed to go ok.... but i still dont have root ?????
any help to what i'm doing wrong ?

smudge100 said:
I followed the instructions on https://www.xda-developers.com/how-to-install-twrp/
when i run -- fastboot flash recovery twrp-2.8.x.x-xxx.img
(in my case -- fastboot flash recovery twrp-3.2.0-0-sailfish.img)
target reported max download size of 536870912 bytes
sending 'recovery' (26520 KB)...
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED ((remote: partition [recovery] doesn't exist
finished. total time 1.000s
I also tried this method from https://twrp.me/google/googlepixel.html
Installation:
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
this all seemed to go ok.... but i still dont have root ?????
any help to what i'm doing wrong ?
Click to expand...
Click to collapse
TWRP does not provide root privileges. You need to use Magisk 14.5 for root privileges on the Pixel. Link for Magisk:
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589

phaino00 said:
TWRP does not provide root privileges. You need to use Magisk 14.5 for root privileges on the Pixel. Link for Magisk:
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Click to expand...
Click to collapse
Is there a guide anywhere on installing Magisk on the OG Pixel? I got TWRP installed and I have no password set so everything is decrypted. But whenever I boot my phone, I get errors about system stuff crashing and can't use my phone.
Do I need to install ElementalX as well? What could I be doing wrong?

daddylonglegs said:
Is there a guide anywhere on installing Magisk on the OG Pixel? I got TWRP installed and I have no password set so everything is decrypted. But whenever I boot my phone, I get errors about system stuff crashing and can't use my phone.
Do I need to install ElementalX as well? What could I be doing wrong?
Click to expand...
Click to collapse
Try a fresh install of the complete firmware, letting it wipe everything including data. Magisk v14.5 build 1456 works fine for me with the final 8.1.

daddylonglegs said:
Is there a guide anywhere on installing Magisk on the OG Pixel? I got TWRP installed and I have no password set so everything is decrypted. But whenever I boot my phone, I get errors about system stuff crashing and can't use my phone.
Do I need to install ElementalX as well? What could I be doing wrong?
Click to expand...
Click to collapse
Just as @roirraW "edor" ehT mentioned, do a completely fresh install of the December Factory Image. Boot into system and set up. Reboot into bootloader and install TWRP 3.2.0.0 via fastboot. Install Magisk 14.5 and reboot system. (In TWRP, you will want to hit cancel when prompted for pin/password, then select read only and install Magisk 14.5 via usb-otg). All should be good.
Hope this helps.

phaino00 said:
Just as @roirraW "edor" ehT mentioned, do a completely fresh install of the December Factory Image. Boot into system and set up. Reboot into bootloader and install TWRP 3.2.0.0 via fastboot. Install Magisk 14.5 and reboot system. (In TWRP, you will want to hit cancel when prompted for pin/password, then select read only and install Magisk 14.5 via usb-otg). All should be good.
Hope this helps.
Click to expand...
Click to collapse
Thanks but I have my phone set up so perfectly that the idea of losing all the data on my apps, their locations on my home screens, my widgets and how they are set up, etc. is something I don't think I can bring myself to do
I did install the complete factory image; the only thing I changed was I removed the -w command. Why is completely wiping the phone necessary to install Magisk anyway?

daddylonglegs said:
Thanks but I have my phone set up so perfectly that the idea of losing all the data on my apps, their locations on my home screens, my widgets and how they are set up, etc. is something I don't think I can bring myself to do
I did install the complete factory image; the only thing I changed was I removed the -w command. Why is completely wiping the phone necessary to install Magisk anyway?
Click to expand...
Click to collapse
Wiping the phone completely is not necessary to install Magisk, just recommended if issues persist.

be sure you have the right magisk version: 14.5 if you have the latest 8.1

smudge100 said:
I followed the instructions on https://www.xda-developers.com/how-to-install-twrp/
when i run -- fastboot flash recovery twrp-2.8.x.x-xxx.img
(in my case -- fastboot flash recovery twrp-3.2.0-0-sailfish.img)
target reported max download size of 536870912 bytes
sending 'recovery' (26520 KB)...
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED ((remote: partition [recovery] doesn't exist
finished. total time 1.000s
Click to expand...
Click to collapse
Make sure you've got the latest platform-tools: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
I was getting the same error until I updated the platform tools. Maybe it's a new version of fastboot? Regardless, fastboot boot [TWRPnamehere].img worked for me with the new tools/fastboot.

[Guide] Unlock Bootloader, Get Root and Flash TWRP Recovery

Warning: This guide is a WiP and is NOT complete. DO NOT FOLLOW THIS GUIDE UNTIL THIS MESSAGE IS REMOVED.
You will require ADB and Fastboot installed on your computer.
First you will need to send a private message to the_lazer with your IMEI and Serial Number and they will give you a key to unlock the bootloader.
Wherever you see KEY in this guide replace that with the key you got given.
Second you will need to download Magisk from here, rename that file to
Code:
magisk.zip
Then download the TWRP.img from here.
If the touch screen doesn't work on TWRP then press the power button so the screen sleeps and then press it again so it wakes up and it should work.
Make sure your device has "Enable OEM Bootloader Unlocking" enabled in settings.
Plug your device into your computer and turn the device off.
Hold the power and volume up buttons, if it has a menu where reboot to bootloader or fastboot is a option then do that.
Once in fastboot mode on your computer run:
Code:
fastboot oem key KEY
fastboot oem unlock
Press the volume up button on the phone and it should unlock successfuly.
Once that is done you will need to run:
Code:
fastboot boot TWRP.img
Note that you should NOT flash twrp yet as it will give "red state" error and prevent your device from booting.
Then once in TWRP if it asks for a password then click cancel. If that doesn't work then press the power button and then press it again so the screen sleeps and wakes up then swipe to unlock and click cancel again.
Swipe to allow modifications then click Advanced and then ADB Sideload and swipe.
Next run
Code:
adb sideload magisk.zip
and it will flash magisk.
Magisk will provide root and patch the bootloader so it will still boot past the "orange state" screen.
Next go back twice and click Reboot and then Bootloader.
Then on your computer run
Code:
fastboot flash recovery TWRP.img
That will now flash TWRP.
The reason you need to flash TWRP after you have flashed magisk is because magisk is required to patch the bootloader so that it will actualy boot.
Then run
Code:
fastboot reboot
and you should eventualy reboot to android, give it about 30mins to boot just to be safe.
Then install Magisk Manager from
Code:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
.
You should now have a working rooted Nokia 3 which uses Magisk.
TODO: Add troubleshooting section and steps to follow if something goes wrong.

Any feedback? Does anyone want to pm me and try it safely?

JakesDen said:
Any feedback? Does anyone want to pm me and try it safely?
Click to expand...
Click to collapse
Don't worry, then next time someone asks about rooting their Nokia 3 I will be sure to point them to this thread, and I like how you described the process. It's very easy to understand. I already have my phone rooted and i'm sticking with my stock recovery because of updates

redweaver said:
Don't worry, then next time someone asks about rooting their Nokia 3 I will be sure to point them to this thread, and I like how you described the process. It's very easy to understand. I already have my phone rooted and i'm sticking with my stock recovery because of updates
Click to expand...
Click to collapse
Thanks :3

nice guide, did you encounter any crashes like SuperSU or it runs normal without errors?

SkaboXD said:
nice guide, did you encounter any crashes like SuperSU or it runs normal without errors?
Click to expand...
Click to collapse
Runs flawlessly and doesn't crash or bootloop.
However if you enable a magisk module which causes a bootloop then you would have to factory reset the device unless /data is decrypted in which case you can just delete the folder the magisk module is located in. I will add to the guide instructions on how to have a decrypted /data partitionlater.

SkaboXD said:
nice guide, did you encounter any crashes like SuperSU or it runs normal without errors?
Click to expand...
Click to collapse
QUOTE=virenhp;75052054]I have Unlocked bootloader in Nokia 3 TA 1032
I flashed Trwp Successfully but Still Getting Stock Recovery when entered to Recovery Mode. Please Help Me .. How Can I get Twrp Recovery. Thank Yo

virenhp said:
QUOTE=virenhp;75052054]I have Unlocked bootloader in Nokia 3 TA 1032
I flashed Trwp Successfully but Still Getting Stock Recovery when entered to Recovery Mode. Please Help Me .. How Can I get Twrp Recovery. Thank Yo
Click to expand...
Click to collapse
if flashing doesn't work, use this command: fastboot boot recovery.img
You will boot to twrp successfully but you need to do this every time when you want twrp.

I followed your guide step by step but when rebooting after TWRP flash, the phone does not boot into system. No matter how i try to reboot the android logo pop up with orange state and the next thing is TWRP loading. I can boot into bootloader, so i tried flashing magisk and TWRP again, but no success. Any help would be appreciated

I will try this method the next time I get an ota update. Wasn't sure if it was the superSU or the xposed that was causing the errors. After this update i've confirmed it's the SU.
I've never used magisk before. Hope it won't conflict with xposed

I recommend not using SuperSu.
You can however install magisk and then use magisk manager to install a systemless xposed.
Just don't use the official regular xposed or your device won't boot.

redweaver said:
I will try this method the next time I get an ota update. Wasn't sure if it was the superSU or the xposed that was causing the errors. After this update i've confirmed it's the SU.
I've never used magisk before. Hope it won't conflict with xposed
Click to expand...
Click to collapse
I recommend not using SuperSu.
You can however install magisk and then use magisk manager to install a systemless xposed.
Just don't use the official regular xposed or your device won't boot.

Please make sure to quote me so I get notified if you respond.

it's good and easy guide, i got my nokia 3 rooted in 30mins

Send me the adress where i'm sending private messege

Tayyabmadina said:
Send me the adress where i'm sending private messege
Click to expand...
Click to collapse
Just click "New Private Message" and enter "the_lazer" in the "Recipient Username" field.
Or message them from https://forum.xda-developers.com/member.php?u=3665957

Thank you

i did everything like on tutorial but when i finish it. it boot to TWRP

redweaver said:
I will try this method the next time I get an ota update. Wasn't sure if it was the superSU or the xposed that was causing the errors. After this update i've confirmed it's the SU.
I've never used magisk before. Hope it won't conflict with xposed
Click to expand...
Click to collapse
My Nokia3 roadacts:
- Developper mode OK
- Unlocked OK
- Install magisk & TWRP
fastboot boot TWRP.img
downloading 'boot.img'...
OKAY [ 0.406s]
booting...
OKAY [ 0.047s]
finished. total time: 0.484s
adb sideload magisk.zip
Total xfer: 1.59x
fastboot flash recovery TWRP.img
target reported max download size of 134217728 bytes
sending 'recovery' (13916 KB)...
OKAY [ 0.437s]
writing 'recovery'...
OKAY [ 0.734s]
finished. total time: 1.188s
- Install SuperSU
fastboot reboot
rebooting...
finished. total time: 0.016s
fastboot reboot
adb sideload SuperSU-v2.82-201705271822.zip
That's the only way I found to install SuperSU, cause I don't succed to put the zip in my phone: All mounts in TWRP failed : USB (a R1 warning PC appears), internal... I had transfert the zip in the Nokia before doing all but I don't know where it's located when I browse in TWRP.
According to the trace I saw on the phone when I did the adb sideload, SuperSU install and config seems to be OK, but I'm no sure.
When I open a term on the phone, navigate in the filesystem, I can't do su but see a SuperSU path with an install shell that failed...
My 2 problems:
1/ is SuperSU OK ?
2/ I'm block : how to go back to Andoid to execute root checker or SuperSU, always boot on TWRP ?
Need Help.

JBData said:
My Nokia3 roadacts:
- Developper mode OK
- Unlocked OK
- Install magisk & TWRP
fastboot boot TWRP.img
downloading 'boot.img'...
OKAY [ 0.406s]
booting...
OKAY [ 0.047s]
finished. total time: 0.484s
adb sideload magisk.zip
Total xfer: 1.59x
fastboot flash recovery TWRP.img
target reported max download size of 134217728 bytes
sending 'recovery' (13916 KB)...
OKAY [ 0.437s]
writing 'recovery'...
OKAY [ 0.734s]
finished. total time: 1.188s
- Install SuperSU
fastboot reboot
rebooting...
finished. total time: 0.016s
fastboot reboot
adb sideload SuperSU-v2.82-201705271822.zip
That's the only way I found to install SuperSU, cause I don't succed to put the zip in my phone: All mounts in TWRP failed : USB (a R1 warning PC appears), internal... I had transfert the zip in the Nokia before doing all but I don't know where it's located when I browse in TWRP.
According to the trace I saw on the phone when I did the adb sideload, SuperSU install and config seems to be OK, but I'm no sure.
When I open a term on the phone, navigate in the filesystem, I can't do su but see a SuperSU path with an install shell that failed...
My 2 problems:
1/ is SuperSU OK ?
2/ I'm block : how to go back to Andoid to execute root checker or SuperSU, always boot on TWRP ?
Need Help.
Click to expand...
Click to collapse
I haven't used magisk before, but I was under the opinion that you didn't need to sideload or flash supersu once you've sideloaded magisk. Maybe you need to read up on activating root with magisk

My OnePlus 7 Pro is bricked.

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.

adb problem

hi
I would like to install twrp image, but adb says device not found, while on the list it sees, the serial nr is there..
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?

When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"

Hunter3U said:
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Click to expand...
Click to collapse
+1 for this.
Folks often mix up fastboot and adb. They are related, but different. Different operation requirements and functions.
adb:
- Only works in OS, or alternately in TWRP.
- Requires debugging toggled on in settings.
Fastboot:
- Only works in bootloader-fastboot mode.
- Does not require debugging to be toggled on.
Fastboot is typically what you want for unlocking bootloader, and booting TWRP (for root, etc.).
---------- Post added at 09:04 AM ---------- Previous post was at 09:00 AM ----------
ii9 said:
adb says device not found
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
Click to expand...
Click to collapse
Not completely clear based on your description. But is sounds like you are trying to do "adb devices" and then "fastboot flash twrp.img"?
In fastboot, you want to do "fastboot devices" (no quotes) and should see the phone's ID number in response.
Then you want to do "fastboot boot twrp.img" to boot TWRP, then flash the TWRP installer zip within TWRP. This is per the recommended install guide from the TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Although it's hard to determine exactly what you did wrong, unless you provide a more detailed sequence of what you did, and with the exact commands.
And to be clear, your bootloader is unlocked, correct?

well, sorry for being noob, for me was never a problem with older phones. I always managed to root, put twrp, change rom without any pc, but this double slot system kills me
so I managed to wipe everything before, vendor, sytem.., all
I wanted to put the havoc rom after formatting, but there was 5 local disks when I opened the phone folder on the pc, and obviously didn't copy the files on it. Therefore I did reboot to recovery, since that I had only the fastboot screen.
After that I unbricked it, all was fine again on the stock
After opened again the bootloader (yes, also before it was) installed the twrp.img, Installed the twrp zip, reboot it.
I followed the steps from havoc, but it said error 7, few times I tried. I reboooted the recovery again, and now I'm again the fastboot only, doesn't even show the warning msg about open bl, and doesn't go anywhere again.
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?

ii9 said:
*SNIP*
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
Click to expand...
Click to collapse
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian

Did you do fastboot flash boot imagename or fastboot flash recovery imagename

runningnak3d said:
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Click to expand...
Click to collapse
I guess I lost it, time to accept the stock rom :crying:
I' not that old, but I can understand now why my grandma doesn't know even what is a phone
At the end I managed to do the unbrick again, after I installed havoc, I get rid of the error 7, and it showed me st like qualcomm crashdump, I was about to give up, but I went back to twrp installed again, now it's fine. Such a pity that it's not stable yet, I don't dare to touch after this..
tHanks for the info, in case I'll ever need I'll try to read again another 100x maybe I'll find out.
Bradl79 said:
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
Click to expand...
Click to collapse
fastboot flash boot imagename
I did this

ii9 said:
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
Click to expand...
Click to collapse
I think you are doing something wrong.
boot.img is basically a kernel, not TWRP.
Booting TWRP and flashing a boot.img are two completely different things.
It would help if you cut/paste the actual command you typed, so we can see what you did.
The command should be: fastboot boot twrp.img
That isn't what you did.
---------- Post added at 11:55 AM ---------- Previous post was at 11:48 AM ----------
ii9 said:
fastboot flash boot imagename
I did this
Click to expand...
Click to collapse
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Seems similar, but this does something very different from the command you used. Syntax in fastboot/adb is absolutely ciritical. Always type fastboot and adb commands exactly as indicated, and double check everything before issuing the command.
fastboot boot twrp.img This boots the image file that is named. Note that you are not flashing anything with this command. Think of it as a remote boot of the TWRP file that is on your computer.
fastboot flash boot imagename This flashes the named file to the boot partition (basically the kernel)

If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed

redpoint73 said:
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Click to expand...
Click to collapse
Sorry, I messed up with the copy and paste, I didn't sleep too much in the last days for the hot, I'm a bit heavy in the head, pls exuse my bs. I also tried this one that you wrote, but didn't manage to boot still.. I have no clue what went wrong, but again, thanks, in case I can come back to read again.
Hunter3U said:
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
Click to expand...
Click to collapse
Not exactly, the end goal to have a clean rom, with basic custumization, that even stock should include in my opinion, like disable headups.., extended screen etc. Plus without google staff, for me it's too strict. As in this moment not so many choice, havoc looked the most near to my wishes, in fact very nice after these hours, I guess I'll be fine with it when the bugs will disappear.
Anyway 1-7 was always without problem. Today after 2 unbrick and bl opening what I did is, through fastboot I entered to the img, from there I flashed the zip, reboot recovery to make sure it stays. I put files on the phone, wiped dalvik and data, install rom+twrp and as it is written here and also on that thread, I rebooted recovery. And I wanted to repeat the flash, but I had the internal storage 0mb thing. So I needed to format data (that's the solition I found) and reboot again, put back files, flash, reboot, flash again, and after I got that qualcomm crashdump screen. I hold the up+power to get back to twrp (or down, not sure) and I flashed again, but only once, so after it worked finally. Since that I'm fine
But sure I need to learn this stuff, it cannot be that I always face st that nobody else does
I hope the managed soon the ota for custom roms and we can do it easy and quick without setting the phone over and over again with all the apps, settings.. (probably only me in the world need to do so, as I start to loose it with the tech staff)
Poor phone is just couple of weeks old, but already saw everything
Thanks for writing

If it means anything to you, I use stock OOS+TWRP+Magisk+Renovate ICE+Xposed (to ignore the secure flag, otherwise Netflix doesn't work over HDMI). Everything works, including Google Pay.

[SOLVED]Oneplus 7 stuck in fastbootmode after trying to restore a backup from TWRP

My bootloader is unlocked, I was rooted with Magisk and i had twrp recovery installed as well. A few modules were installed and i had made a backup about 3 weeks ago. Yesterday i tried restoring the backup in twrp and it seemed to restore properly without errors . When i pressed reboot in the end the phone went to the fastboot mode screen and has since been there. All i can do is turn it off and regardless of what i pick, (START, Restart Bootloader, Recovery mode) it just starts into fastboot mode. Confused as to what i should do now and why this happened in the first place. All the threads i found were only for the 7 pro so i didnt want to risk anything by following those. Please advice on what i should do.
Edit : The problem was solved by flashing the STOCK ROM for android 9 which is what i was on when the device was softbricked.

hi
Hi, download adb fastboot and twrp recovery image for guacamoleb. then open a new command prompt (CMD) in the same location and run the following commands:
Code:
fastboot flash recovery (file name of twrp that you download).img
after that by holding volume up + power reboot to twrp recovery that you just installed via adb fastboot command.
when you enter on twrp recovery, install twrp recovery zip, and magisk 19.3 zip (download and copy on phone storage first, after you enter on twrp when reboot, you can connect your phone with computer or USB that contain twrp recovery zip and magisk or copy to phone storage) after this step install twrp zip first than magisk and then reboot.
i hope i helped.
sorry for my english , is not my native language.

klediY said:
Hi, download adb fastboot and twrp recovery image for guacamoleb. then open a new command prompt (CMD) in the same location and run the following commands:
Code:
fastboot flash recovery (file name of twrp that you download).img
after that by holding volume up + power reboot to twrp recovery that you just installed via adb fastboot command.
when you enter on twrp recovery, install twrp recovery zip, and magisk 19.3 zip (download and copy on phone storage first, after you enter on twrp when reboot, you can connect your phone with computer or USB that contain twrp recovery zip and magisk or copy to phone storage) after this step install twrp zip first than magisk and then reboot.
i hope i helped.
sorry for my english , is not my native language.
Click to expand...
Click to collapse
Thank you for the reply. Unfortunately i am stuck in the very first step. After typing C:\adb\Oneplus 7>fastboot flash recovery twrp-3.3.1-1-guacamoleb.img in cmd the following happens
target reported max download size of 805306368 bytes
sending 'recovery' (56612 KB)...
OKAY [ 1.220s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.228s
I have tried using fastboot boot recovery instead in cmd. The following error comes up
cannot load 'recovery': No such file or directory.
I have checked whether the device is connected by typing in fastboot devices and it shows as connected. Any other suggestions will be helpful.

wolfsbane169 said:
Thank you for the reply. Unfortunately i am stuck in the very first step. After typing C:\adb\Oneplus 7>fastboot flash recovery twrp-3.3.1-1-guacamoleb.img in cmd the following happens
target reported max download size of 805306368 bytes
sending 'recovery' (56612 KB)...
OKAY [ 1.220s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.228s
I have tried using fastboot boot recovery instead in cmd. The following error comes up
cannot load 'recovery': No such file or directory.
I have checked whether the device is connected by typing in fastboot devices and it shows as connected. Any other suggestions will be helpful.
Click to expand...
Click to collapse
Something similar happened to me, I was on OOS 10 stable and wiping the system and data from TWRP got in fastboot mode without being possible to do anything else. The way that I solved was flashing from fastboot the OOS 10 stable posted rom here: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478 This will erase all your data but you will unbrick your phone.
One important thing, if you are on android 10 you can't flash TWRP via fasboot, maybe that's the problem you are having right now.
Hope this helps

ryupunk said:
Something similar happened to me, I was on OOS 10 stable and wiping the system and data from TWRP got in fastboot mode without being possible to do anything else. The way that I solved was flashing from fastboot the OOS 10 stable posted rom here: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478 This will erase all your data but you will unbrick your phone.
One important thing, if you are on android 10 you can't flash TWRP via fasboot, maybe that's the problem you are having right now.
Hope this helps
Click to expand...
Click to collapse
Ok so thank you for the help and you were right. Now i have an all new different problem. In a nutshell i flashed the stock ROM for android 9 while i was in android 10. I completely forgot you aren't supposed to do that. As a result i cant even access fastboot mode now. Can you please tell me how i can fix this problem?

wolfsbane169 said:
Ok so thank you for the help and you were right. Now i have an all new different problem. In a nutshell i flashed the stock ROM for android 9 while i was in android 10. I completely forgot you aren't supposed to do that. As a result i cant even access fastboot mode now. Can you please tell me how i can fix this problem?
Click to expand...
Click to collapse
I think that you will need to use the MSM tool, it looks like you have a hard brick, the good news is that oneplus devices can be revived in almost all cases. I have never used the tool but I found some posts that might help you. Best of luck!
XDA Oneplus 7 thread
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
XDA Oneplus 7 pro thread
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Oneplus forum guide
https://forums.oneplus.com/threads/...ide-for-a-hard-bricked-oneplus-7-pro.1041896/

ryupunk said:
I think that you will need to use the MSM tool, it looks like you have a hard brick, the good news is that oneplus devices can be revived in almost all cases. I have never used the tool but I found some posts that might help you. Best of luck!
XDA Oneplus 7 thread
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
XDA Oneplus 7 pro thread
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Oneplus forum guide
https://forums.oneplus.com/threads/...ide-for-a-hard-bricked-oneplus-7-pro.1041896/
Click to expand...
Click to collapse
I have tried using it but the problem is that MSM download tool does not detect my phone. i have uninstalled and let windows automatically update qualcomm drivers. I have also made windows manually install them after uninstalling.