Database Info

[Q] Flashed the LPX13D image and now my recovery is gone.

Hi Guys,
Hoping you can help me with this.
I was originally running Slimkat 4.4.4 and had the latest TWRP installed.
I downloaded the file for LPX13D and extracted all of the files right down to the Flash-all.bat and the images for bootloader, radio, and the system.
I ran the Flash-all.bat, and it installed everything successfully. The device booted, and voila, I am on 5.0 now.
The problem now, is that when I reboot into recovery, I am instead met with the little android guy laying on his back, with a red triange/exclamation point in his chest.
No problem, I say to myself. I'll just flash TWRP manually.
So I go to the bootloader, and try the command fastboot flash recovery recovery.img (renamed to make it faster to type.)
It goes through the motions, and says it was successful.
But when I go to recovery, it's the same red triange guy still.
I tried pressing volume up, power+volume up, etc. No dice. After about 30 seconds, it reboots on it's own back to system.
When I connect it to the Nexus Root Toolkit, and click on Flash recovery, and then choose TWRP latest, I get a window that pops up that tells me :
______
File Dependency Download
Status: Stock Kernel: Not Present - Need to download (this is in red)
Then a button that says "Download + Update All File Dependencies"
So what's my best option here? Should I let the NRT update the dependencies?

Try to flash cwm and tell me what happens

Isus <3 said:
Try to flash cwm and tell me what happens
Click to expand...
Click to collapse
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.

deleted

Stupendousman2012 said:
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.
Click to expand...
Click to collapse
Twrp is not optimized yet well like cwm is for andorid l

Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Lethargy said:
I flashed the new developer preview for 5 minutes or so then went to revert. Recovery wouldn't boot not matter what I flashed, until I flashed a KK userdata.img. So it seems like the new developer preview changes the internal storage/data partition more then the old one.
Click to expand...
Click to collapse
Don't try getting around it. Nothing to do with anything else.
Isus <3 said:
Twrp is not optimized yet well like cwm is for andorid l
Click to expand...
Click to collapse
What? CWM is outdated.

Lethargy said:
Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Don't try getting around it. Nothing to do with anything else.
What? CWM is outdated.
Click to expand...
Click to collapse
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
I also flashed the boot.img and the supersu update to get root working, and it seems to be going well now.
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.

Stupendousman2012 said:
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
Click to expand...
Click to collapse
Flash userdata.img and your TWRP will work properly.
Stupendousman2012 said:
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
Click to expand...
Click to collapse
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
Stupendousman2012 said:
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.
Click to expand...
Click to collapse
It says that because CWM is outdated.

Lethargy said:
Flash userdata.img and your TWRP will work properly.
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
It says that because CWM is outdated.
Click to expand...
Click to collapse
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?

Stupendousman2012 said:
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?
Click to expand...
Click to collapse
Yeah. Don't need to boot into recovery and wipe data since flashing a .img with fastboot while in bootloader erases it first then flashes. Just make sure you backup your stuff, including internal storage, off to a PC first if you have anything important.

Until L is officially released, we're using the below thread
http://forum.xda-developers.com/show....php?t=2796217
Android "L" Developer Preview Help, Troubleshooting, Q&A
Sent from my Nexus 5 using Tapatalk

Bricked shield Tablet, fastboot only works.

Going through some of the threads here got me as far as being able to use fastboot on my bricked Shield.
I would like to ask if anyone can give me some pointers what to try next.
The previous owner tried to flash Lineage OS onto the Tablet using CWM but this failed and he probably wiped some needed partition.
I tried to flash new partitions and this works but I can not start the Shield and it won't boot into CWM. The strange thing is that I tried flashing TWRP and even though that started it did not boot through. And after a simple Shield reboot the CWM logo popped upmagain.....:confused
I was convinced I could fix this but I am beginning to think that this Tablet is a goner...
Any thoughts would ne appreciated.

What happens if you download an original recovery image from Nvidia for your model, and flashboot flash all 5 (recovery, boot, system, userdata, blob)? Do you get any fastboot errors? If the partition structure is corrupted, you'll see some sort of error message.
If the blob is messed up sometimes TWRP won't start. I suggest getting a factory image and trying again, then giving it a long time to boot. Once mine took 20 minutes at the Nvidia screen.

I did try flashing the original image from Nvidia including the other 4 images. One of the first things I tried. I woyld like to get it back to factory default. This went without issues an no errors. I might not have given it enough tine to but but still CWM seems to be on.
Will give it another try and post a screenshot.
Sent from my SM-G935F using Tapatalk

Here is a dump of the flash log. After flashing I reboot and the CWM logo pops up after a few minutes and gets stuck.
D:\Downloads\Shield Fix\Drivers\ADB FastBoot\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 100663296 bytes
sending 'recovery' (9758 KB)...
OKAY [ 0.384s]
writing 'recovery'...
OKAY [ 0.320s]
finished. total time: 0.709s
D:\Downloads\Shield Fix\Drivers\ADB FastBoot\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.394s]
booting...
OKAY [ 0.017s]
finished. total time: 0.417s

Think it is done for, after flashing TWRP numerous times it let me get to the start screen for TWRP it then hangs. When you reboot the Shield and want to go to the recovery again you get the dead android.
PS. I can sometimes get into TWRP but it fails on everything I do. Would there be a terminal solution for this? Like re-creating partitions?

Unlock your bootloader?
Sent from my ZTE A2017U using Tapatalk

It is already unlocked I am afraid.
Sent from my SM-G935F using Tapatalk

sn0r said:
It is already unlocked I am afraid.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Try to flash the attached file. Remember to unzip it first! Flash with:
"fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb"

Flashed the battery file and did another flash of NVIDIA's recovery image and even-tough it says everything is flashed correctly when I reboot I get the CWM logo and nothing more. When I do get into TWRP and try to flash a ROM I get messages errors like attached.

sn0r said:
Flashed the battery file and did another flash of NVIDIA's recovery image and even-tough it says everything is flashed correctly when I reboot I get the CWM logo and nothing more. When I do get into TWRP and try to flash a ROM I get messages errors like attached.
Click to expand...
Click to collapse
Then my guess would be some problems with the internal storage which may not be repairable.

Using fastboot try the following
Fastboot erase cache
Fastboot format cache
Fastboot format userdata
Make sure your tablet is in bootloader mode first though.
Sent from my pa_osprey using Tapatalk

Proper way to restore Nandroid backup?

I did do a search and found and tried a couple different recommended? methods that r supposed to work. Didn't for me.
What is the PROPER procedure to make a backup with twrp then restore it if needed. THANKS

Boot twrp, backup, backup all options.
Boot twrp, restore, choose the backup you want to restore, tick all options, swipe right for restore.
You sure u searched?

Yes
whizeguy said:
Boot twrp, backup, backup all options.
Boot twrp, restore, choose the backup you want to restore, tick all options, swipe right for restore.
You sure u searched?
Click to expand...
Click to collapse
Yes I searched more than once, different people trying different things. Tried what you suggested a couple times already before I posted creep.

https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
Is there something wrong with this guide you mean? It works without issues here......
Guess rooting is too easy on OnePlus devices aswell ?

whizeguy said:
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
Is there something wrong with this guide you mean? It works without issues here......
Guess rooting is too easy on OnePlus devices aswell ?
Click to expand...
Click to collapse
you are really funny man. he is right . there is no thread which guides you how to restore nandroid on oneplus 6 .
i have tried all the methods posted in oneplus 6 xda.
Only 1 time i have been able to restore successfully. on OOS 5.1.11.
Tried more than 7 times to restore on android pie. with encrypted and decrypted both ways always issues like twrp lost or bootloop on blank screen
The post you are referring to shows general method of how to backup and restore via TWRP. And i assure the twrp doesnt work as intened . This a/b partition is f... PITA.
If any one knows how to successfully restore a nandroid backup on stable pie, please share.
im so fedup of this nonsense. i might go back to samsung devices for easy custom installations

kingwicked said:
you are really funny man. he is right . there is no thread which guides you how to restore nandroid on oneplus 6 .
i have tried all the methods posted in oneplus 6 xda.
Only 1 time i have been able to restore successfully. on OOS 5.1.11.
Tried more than 7 times to restore on android pie. with encrypted and decrypted both ways always issues like twrp lost or bootloop on blank screen
The post you are referring to shows general method of how to backup and restore via TWRP. And i assure the twrp doesnt work as intened . This a/b partition is f... PITA.
If any one knows how to successfully restore a nandroid backup on stable pie, please share.
im so fedup of this nonsense. i might go back to samsung devices for easy custom installations
Click to expand...
Click to collapse
Whizeguy is a know it all, his posts are mostly about belittling people not helping. And yes restoring backups is a pain. No success here either

so try to backup without the image system and image vendor ... then to restore after doing wipe again reboot to recovery...

kingwicked said:
you are really funny man. he is right . there is no thread which guides you how to restore nandroid on oneplus 6 .
i have tried all the methods posted in oneplus 6 xda.
Only 1 time i have been able to restore successfully. on OOS 5.1.11.
Tried more than 7 times to restore on android pie. with encrypted and decrypted both ways always issues like twrp lost or bootloop on blank screen
The post you are referring to shows general method of how to backup and restore via TWRP. And i assure the twrp doesnt work as intened . This a/b partition is f... PITA.
If any one knows how to successfully restore a nandroid backup on stable pie, please share.
im so fedup of this nonsense. i might go back to samsung devices for easy custom installations
Click to expand...
Click to collapse
At that time backups worked, in that thread there was ways that worked. You had to put the backup on the pc, format, install same rom as your backup and restore it without booting. Now on pie... Nothing works, but 2 months ago, it did.
trsix said:
Whizeguy is a know it all, his posts are mostly about belittling people not helping. And yes restoring backups is a pain. No success here either
Click to expand...
Click to collapse
Your posts are really helpful I see.. Don't throw rocks in a glass house. (edit: guess the roof came down when someone called you out on your bs doing the same lol pathetic)
New threads are about topics already answered alot.might be why one gets tired of it.. I don't know. People just don't know how to use the forum
The way I do it now is I use swift backup to backup apps+data. Makes the job easier atleast, but I know it's not the same as before. Decrypting and use twrp might be an option.. Never tried it.

I am decrypted and here's what I do:
backup only boot, system, data and efs, at time of restore do it without any wipes, once restore is complete flash twrp reboot recovery, now Flash magisk 17.1 and reboot recovery, now flash dm_verity_force_encrption disabler, now reboot system, it works for me 9 out of 10 times, hope this helps, cheers.

vtec303 said:
I am decrypted and here's what I do:
backup only boot, system, data and efs, at time of restore do it without any wipes, once restore is complete flash twrp reboot recovery, now Flash magisk 17.1 and reboot recovery, now flash dm_verity_force_encrption disabler, now reboot system, it works for me 9 out of 10 times, hope this helps, cheers.
Click to expand...
Click to collapse
well i am decrypted too. :good:
will try it once need arises to restore
thanks a lot for your help mate.
have you performed a restore on pie rom yet with above mentioned success rate?

kingwicked said:
well i am decrypted too. :good:
will try it once need arises to restore
thanks a lot for your help mate.
have you performed a restore on pie rom yet with above mentioned success rate?
Click to expand...
Click to collapse
yes I have been on pie since beta 1, now I am on beta 4, cheers.

vtec303 said:
yes I have been on pie since beta 1, now I am on beta 4, cheers.
Click to expand...
Click to collapse
i had a need to restore my nandroid on pie. and i failed with above method mate. device was rebooting in fastboot mode after restore and twrp lost when i restarted with above steps
I was stuck on black screen with notification light on.\
i tried to adb fastboot boot twrp blu got this error
>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.630s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.651s
then i tried this command
fastboot flash boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
target reported max download size of 536870912 bytes
sending 'boot_a' (28788 KB)...
OKAY [ 0.666s]
writing 'boot_a'...
OKAY [ 0.116s]
finished. total time: 0.803s
then also flashed to partition b
fastboot flash boot_b twrp-3.2.3-x_blu_spark_v9.86_op6.img
target reported max download size of 536870912 bytes
sending 'boot_b' (28788 KB)...
OKAY [ 0.669s]
writing 'boot_b'...
OKAY [ 0.148s]
finished. total time: 0.841s
tried to fastboot boot twrp blu spark but failed
then tried to fastboot official twrp that worked
restored my backup which was saved on phone and thankfully sdcard didnt get messed maybe because of being decrypted
but still was not able to boot into system
then i adb pushed OOS Pie Stable zip to phone
flashed OOS Pie without any wipes as previous backup was restored.
flashed twrp Blu spark and tried to boot into system
but still returned back to twrp but now on blu spark
flashed magisk 17.1
restarted system
and voila backup has been restored on OOS PIE.
it had password and fingerprint even that made no issue

kingwicked said:
i had a need to restore my nandroid on pie. and i failed with above method mate. device was rebooting in fastboot mode after restore and twrp lost when i restarted with above steps
I was stuck on black screen with notification light on.\
i tried to adb fastboot boot twrp blu got this error
>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.630s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.651s
then i tried this command
fastboot flash boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
target reported max download size of 536870912 bytes
sending 'boot_a' (28788 KB)...
OKAY [ 0.666s]
writing 'boot_a'...
OKAY [ 0.116s]
finished. total time: 0.803s
then also flashed to partition b
fastboot flash boot_b twrp-3.2.3-x_blu_spark_v9.86_op6.img
target reported max download size of 536870912 bytes
sending 'boot_b' (28788 KB)...
OKAY [ 0.669s]
writing 'boot_b'...
OKAY [ 0.148s]
finished. total time: 0.841s
tried to fastboot boot twrp blu spark but failed
then tried to fastboot official twrp that worked
restored my backup which was saved on phone and thankfully sdcard didnt get messed maybe because of being decrypted
but still was not able to boot into system
then i adb pushed OOS Pie Stable zip to phone
flashed OOS Pie without any wipes as previous backup was restored.
flashed twrp Blu spark and tried to boot into system
but still returned back to twrp but now on blu spark
flashed magisk 17.1
restarted system
and voila backup has been restored on OOS PIE.
it had password and fingerprint even that made no issue
Click to expand...
Click to collapse
very sorry to hear you ran into problems, as I have mentioned before my method only works if only three partitions are backed up, boot, system and data, if any other partition are/is in the backup, it will not restore especially vendor and vendor image, next time when you do a nand backup only check boot, system and data as well as efs if you want, hope this helps, cheers.

Does your method of restoring nandroid backup only work if you are decrypted?
Mine is encrypted. Would your method still work?

ausaras said:
Does your method of restoring nandroid backup only work if you are decrypted?
Mine is encrypted. Would your method still work?
Click to expand...
Click to collapse
Same question here.

Redwingsyummy said:
I did do a search and found and tried a couple different recommended? methods that r supposed to work. Didn't for me.
What is the PROPER procedure to make a backup with twrp then restore it if needed. THANKS
Click to expand...
Click to collapse
This is what I do and it always works.
BACKUP - only do the backup for boot, system, and data. That is all that works anyway
STEPS TO RESTORE
1. Clean flash the room you made the backup on. If using OOS like I am just use a fastboot rom. It will wipe everything for you and makes this possible.
2. Start the rom up and complete the initial setup - you don't need to sign in to Google or install any apps just get through the setup or this will not work
3. If TWRP was installed on the phone for the backup, install the same version of it here. Same thing applies for magisk. When this is all done reboot to recovery.
4. Restore system, data, and boot only.
5. Reboot to system and enjoy.
I know this is complex and a serious pain in the butt, but it is the only way I found to make this thing work. Let me know if you have any questions.

tabletalker7 said:
This is what I do and it always works.
Click to expand...
Click to collapse
Thanks for for sharing your working process.
1. Do you follow the advice of guides around there that suggest to disable lock screen before the backup?
2. Your system is encrypted, right? Or you decrypted it?
3. What version of TWRP and OOS did you use for your successful backup/restore?

fred_gaou said:
Thanks for for sharing your working process.
1. Do you follow the advice of guides around there that suggest to disable lock screen before the backup?
2. Your system is encrypted, right? Or you decrypted it?
3. What version of TWRP and OOS did you use for your successful backup/restore?
Click to expand...
Click to collapse
1. I came up with this all on my own, and while some people removed the lock screen stuff, I didn't. There are a few files you will need to delete to remove the lock screen password, but the fingerprint and facial recognition still worked.
2. My system is encrypted - the encryption problems people ran into was from different roms running with different Android security updates. By reinstalling the same rom as the backup was made on, you remove that problem.
3. This worked with both official and bluspark TWRP and on every official OOS rom, and I even tried it on a few of the open betas, until I got sick of the open betas. I haven't tried it on OOS 9.0.3 yet, but I doubt there is a problem there.
EDIT: The file that needs deleted is data/system/locksetting.db you can delete it with the TWRP file manager, and this process also works on OOS 9.0.3

tabletalker7 said:
1. I came up with this all on my own, and while some people removed the lock screen stuff, I didn't. There are a few files you will need to delete to remove the lock screen password, but the fingerprint and facial recognition still worked.
EDIT: The file that needs deleted is data/system/locksetting.db you can delete it with the TWRP file manager, and this process also works on OOS 9.0.3
Click to expand...
Click to collapse
Yes. This guide from @funkwizard for OP6T lists all files, if present, that should be deleted in /data/sytem/ if any one forgot to disable unlock screen during backup.
tabletalker7 said:
2. My system is encrypted - the encryption problems people ran into was from different roms running with different Android security updates. By reinstalling the same rom as the backup was made on, you remove that problem.
Click to expand...
Click to collapse
Good to know.
tabletalker7 said:
3. This worked with both official and bluspark TWRP and on every official OOS rom, and I even tried it on a few of the open betas, until I got sick of the open betas. I haven't tried it on OOS 9.0.3 yet, but I doubt there is a problem there.
Click to expand...
Click to collapse
Very valuable feedback. Thanks for sharing your experiences.

fred_gaou said:
Yes. This guide from @funkwizard for OP6T lists all files, if present, that should be deleted in /data/sytem/ if any one forgot to disable unlock screen during backup.
Click to expand...
Click to collapse
OP6T? I learned this stuff on my Axon 7. Guess I just figured it was common knowledge by now.

[HELP] Bricked Oneplus 6 (even worst than Qualcomm CrashDump)

I need help with my op6.
I was using LOS (Unlocked+rooted) until now and I accidentally brick my device, now it's stuck at the bootloader screen.
It doesn't matter if I'm trying to get into the system/recovery.
These are the steps that I did to get here (as far as I can remember):
Wipe system, data, and cache.
Flash latest OxygenOS (9.0.4) using TWRP (blu_spark_v9.96).
Flash TWRP.
Reboot to TWRP
This time it didn't ask me to unlock it with my pattern, and I saw that all of my files in the sdcard folder are encrypted.
I pressed the other partition (A) manually and reboot to TWRP.
It got stuck on the recovery screen.
I flashed TWRP via ADB.
Now the A partitions files are encrypted, I tried to manually move to partition B again, but stuck at crash dump after reboot.
I flashed TWRP via ADB, this time to B.
And now it's stuck at the bootloader...
I can't use the MsmDownloadTool because it's the bootloader and not the crashdump screen, the tool doesn't recognize the device in order to unbrick it.
I even tried to use this guide, but it didn't help, the msmtool still don't recognize it.
I tried to flash TWRP via ADB and this is what I got:
Code:
C:\Users\Folio\Downloads>fastboot flash recovery twrp-3.2.3-x_blu_spark_v9.96_op
6.img
target reported max download size of 536870912 bytes
sending 'recovery' (28892 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.625s
I also tried these commands:
Code:
C:\Users\Folio\Downloads>fastboot getvar current-slot
current-slot: b
finished. total time: -0.000s
C:\Users\Folio\Downloads>fastboot flash boot_b twrp-3.2.3-x_blu_spark_v9.96_op6.
img
target reported max download size of 536870912 bytes
sending 'boot_b' (28892 KB)...
OKAY [ 0.617s]
writing 'boot_b'...
OKAY [ 0.140s]
finished. total time: 0.773s
C:\Users\Folio\Downloads>fastboot boot twrp-3.2.3-x_blu_spark_v9.96_op6.img
downloading 'boot.img'...
OKAY [ 0.608s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.640s
But it didn't really do anything...
I'm out of ideas, what should I do next?

just go use the unbrick tool ?

I've been in your situation a lot of times in the beginning when I started to know about A/B partitioning.
Just fastboot the stock rom found here and you will boot easily in OOS.. Although your internal will be formatted every time you do this.
By the way, when you go to OOS from any ROM, you will always have to format internal storage to make OOS boot. (The step you didnt do in mentioned steps)
Fastboot ROM - https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665

Blunts47 said:
just go use the unbrick tool ?
Click to expand...
Click to collapse
As I mentioned.
Yes, I have tried that already.
Joyarup said:
I've been in your situation a lot of times in the beginning when I started to know about A/B partitioning.
Just fastboot the stock rom found here and you will boot easily in OOS.. Although your internal will be formatted every time you do this.
By the way, when you go to OOS from any ROM, you will always have to format internal storage to make OOS boot. (The step you didnt do in mentioned steps)
Fastboot ROM - https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
I never saw in any other guide that It's necessary to also wipe the internal storage.
The OP6 imaging prosses is even more agonizing than I thought it is. :crying:
I'll try the guide that you sent me and will update, thanks for that.

lyor said:
As I mentioned.
Yes, I have tried that already.
I never saw in any other guide that It's necessary to also wipe the internal storage.
The OP6 imaging prosses is even more agonizing than I thought it is. :crying:
I'll try the guide that you sent me and will update, thanks for that.
Click to expand...
Click to collapse
I agree with you, the A/B partitioning is just a pain in the back.
Try that guide, just let your phone boot into fastboot, plug in pc and run the batch file in the zip of the rom and let it proceed.

Joyarup said:
I agree with you, the A/B partitioning is just a pain in the back.
Try that guide, just let your phone boot into fastboot, plug in pc and run the batch file in the zip of the rom and let it proceed.
Click to expand...
Click to collapse
WOW, how is this guide is not more popular?
Anyhow, you just saved my as5 man, thank you!

lyor said:
WOW, how is this guide is not more popular?
Anyhow, you just saved my as5 man, thank you!
Click to expand...
Click to collapse
Haha, glad to be useful. I know right, fastbooting ROMs are not popular these days. Everyone just follows the unbrick tool..
Enjoy!!

btw, can I now move freely to any other ROM without touching (flashing) the stock ROM?

lyor said:
btw, can I now move freely to any other ROM without touching (flashing) the stock ROM?
Click to expand...
Click to collapse
Yes, if you are booted to OOS once, you can flash any ROMs now. But remember while flashing back the OOS, you will need to wipe internals.

Joyarup said:
Yes, if you are booted to OOS once, you can flash any ROMs now. But remember while flashing back the OOS, you will need to wipe internals.
Click to expand...
Click to collapse
Oh yes, one last thing.
Will I be able to install them without flashing TWRP every time after them (for both of the A/B slots)?

lyor said:
Oh yes, one last thing.
Will I be able to install them without flashing TWRP every time after them (for both of the A/B slots)?
Click to expand...
Click to collapse
Always flash ROM zip + Twrp
Then reboot to TWRP then flash gapps and magisk(if any).
And never change boot partition through twrp, it will brick you. It's kinda buggy...

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.