My OnePlus 7 Pro is bricked. - OnePlus 7 Pro Questions & Answers

My OnePlus 7 Pro is bricked. - OnePlus 7 Pro Questions & Answers

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.

Related

How to root my Moto G 3 with Android version 6.0.1

I have seen threads but nothing related to the 6.0.1 version. Please do help

jerry94 said:
I have seen threads but nothing related to the 6.0.1 version. Please do help
Click to expand...
Click to collapse
6.0 or 6.0.1... no difference, must do manual systemless install

acejavelin said:
6.0 or 6.0.1... no difference, must do manual systemless install
Click to expand...
Click to collapse
how to do that?

Already answered google it
Sent from my MotoG3 using Tapatalk

flash supersu zip in twrp.. to simple

HelpMeruth said:
flash supersu zip in twrp.. to simple
Click to expand...
Click to collapse
This doesn't work... if you just flash the latest SuperSU in TWRP, a 3rd/4th Gen Moto device will fail to boot because SuperSU's install script does not recognize that this device must have a systemless install. You must start TWRP and before flashing go to Advanced - Terminal and enter "echo SYSTEMLESS=true>>/data/.supersu" so the SuperSU install script will parse the file and know it has to do a systemless install.

jerry94 said:
I have seen threads but nothing related to the 6.0.1 version. Please do help
Click to expand...
Click to collapse
Check this tutorial
forum.xda-developers.com/2015-moto-g/general/guide-install-twrp-root-xposed-t3294588
Or this one(better)
forum.xda-developers.com/2015-moto-g/general/root-how-to-root-moto-g-2015-android-t3320113e

Nikos dima said:
Check this tutorial
forum.xda-developers.com/2015-moto-g/general/guide-install-twrp-root-xposed-t3294588
Or this one(better)
forum.xda-developers.com/2015-moto-g/general/root-how-to-root-moto-g-2015-android-t3320113e
Click to expand...
Click to collapse
C:\Program Files\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.313s]
booting...
FAILED (remote failure)
finished. total time: 0.391s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (8122 KB)...
OKAY [ 0.313s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.344s
C:\Program Files\Minimal ADB and Fastboot>
I tried to flash Twrp but iam getting this

Root 6.0.1
jerry94 said:
I have seen threads but nothing related to the 6.0.1 version. Please do help
Click to expand...
Click to collapse
I was also facing the same problem First of all u need to unlock bootloader then at bootloader "fastboot boot recovery.img" change your name twrp to recovery after that you will gets boot into twrp from there flash https://www.androidfilehost.com/?fid=24269982087018189 this file
Hit like if I'm helped you

I followed all the steps of unlocking the bootloader using AdB and Fastboot. After I enter my unique key it sends some commands rather than showing that the device is unlocked.

jerry94 said:
I followed all the steps of unlocking the bootloader using AdB and Fastboot. After I enter my unique key it sends some commands rather than showing that the device is unlocked.
Click to expand...
Click to collapse
Check this video to unlock bootloader. https://youtu.be/BCRpCEtcZ_c and if you are getting errors just search in google for solution

jerry94 said:
I followed all the steps of unlocking the bootloader using AdB and Fastboot. After I enter my unique key it sends some commands rather than showing that the device is unlocked.
Click to expand...
Click to collapse
Can you screenshot it and post it here?
Sent from my Motorola XT1575 using XDA Labs

acejavelin said:
Can you screenshot it and post it here?
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
I have unlocked the bootloader and flashed twrp now. It opened the twrpmode.i booted the fone.But after that while opening the recovery mode in fastboot it is showing 'no command'

jerry94 said:
I have unlocked the bootloader and flashed twrp now. It opened the twrpmode.i booted the fone.But after that while opening the recovery mode in fastboot it is showing 'no command'
Click to expand...
Click to collapse
If you are getting "No command" that is not TWRP, it is the factory recovery...
When you install TWRP with `fastboot flash recovery twrp.img` you must start TWRP, allow it to make changes to the system, then go to TWRP's reboot menu and select Reboot to Recovery. This action will permanently set TWRP as the recovery, otherwise the OS has a script which will restore the stock recovery on boot.
Proper way to flash TWRP, in my opinion, on a new (to TWRP) Moto device once the bootloader is unlocked:
1) fastboot boot twrp.img
2) do NOT tick "Never show this screen again on boot" and select Keep Read Only button
3) do a complete backup in TWRP, preferably to the microSD card. Make a copy of this backup and store it away safely for possible future use and keep a copy on the device if possible
4) reboot into bootloader
5) fastboot flash recovery twrp.img
6) start Recovery (TWRP)
7) tick "Never show this screen again on boot" and swipe to allow modification
8) go to Reboot and select Recovery **IMPORTANT** this step allows TWRP to "lock" itself in and prevent the OS from replacing it with the stock recovery again
9) TWRP should start again, and it should not prompt you at all and just go to the TWRP menu
10) Do what you wish in TWRP (flash SuperSU, install ROM, or whatever) if anything
11) Reboot - System
Replace twrp.img with the appropriate filename from http://twrp.me for the device. If you have already made changes to the system, just start at step #4

acejavelin said:
<< Proper way to flash TWRP, in my opinion, on a new (to TWRP) Moto device once the bootloader is unlocked:
1) fastboot boot twrp.img
2) do NOT tick "Never show this screen again on boot" and select Keep Read Only button
3) do a complete backup in TWRP, preferably to the microSD card. Make a copy of this backup and store it away safely for possible future use and keep a copy on the device if possible
4) reboot into bootloader
5) fastboot flash recovery twrp.img
6) start Recovery (TWRP)
7) tick "Never show this screen again on boot" and swipe to allow modification
..
..
.. >>
Click to expand...
Click to collapse
I've seen these steps a few times (OK, many times, with all the threads started on this exact question).
I'm just curious.. Why does it work? i.e. How is rebooting into TWRP without installing it, then immediately turning around, installing it, and running it... how is that different from just installing it first thing and running it? Like, what's going on internally that makes those two things different?
Thanks x
Sent from my Nexus 7 using XDA Labs

beachfl said:
I've seen these steps a few times (OK, many times, with all the threads started on this exact question).
I'm just curious.. Why does it work? i.e. How is rebooting into TWRP without installing it, then immediately turning around, installing it, and running it... how is that different from just installing it first thing and running it? Like, what's going on internally that makes those two things different?
Thanks x
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
OK... Booting TWRP without installing has nothing to do with functionality of TWRP, it is only to get a clean backup or if you want to root without installing TWRP. TBH, this entire piece is optional and could be skipped, but if you can get a clean backup it sure can makes things easier down the road.
When you flash TWRP, it is flashed... it is written into the recovery partition of your device, but if you start the operating system at this point there is a script (or something, going from my memory of the Nexus 4 which has a script that sat in /system that ran on each boot, so this has been an issue for a while in some devices) that re-writes the recovery it isn't "official". But, but flashing TWRP, allowing it to make changes, then rebooting into TWRP again, it gives TWRP a chance to do something that stops the restoring to official process to stop. I am not sure of the specific details, and I am not sure it really matters, but it works.

acejavelin said:
... Booting TWRP without installing has nothing to do with functionality of TWRP.. .
Click to expand...
Click to collapse
I get that thank you!
Sent from my Nexus 7 using XDA Labs

Huawei Honor 6 H60-L12 bricked

Hello all
A friend of mine has a Huawei Honor 6 H60-L12.
He tried to do a firmware update and he bricked the phone.
I bought it and I am desperately trying to recover it.
Here is what I know about the phone:
It had Android 5.1.1
It had Emui 3.1 and was trying to upgrade to 4.0
(Probably was rooted)
It is H60-L12
No matter what I do, I cannot enter recovery mode with the 3 button trick.
I can anytime enter Fastboot mode.
I tried to unbrick it with HONOR Multi-Tool, everything seems to work alright, but flashing boot.img fails. After unbrick I should enter recovery mode but it does not work, phone remains stuck with the Honor logo.
Computer connects to phone in Fastboot mode, Multi-tool and fastboot command works, I also have the drivers installed.
I know that after bricking the rooted phone, I should restore it and remove root before upgrade but I cannot get there.
Please advise
Best regards,
Janos

janos666 said:
Hello all
A friend of mine has a Huawei Honor 6 H60-L12.
He tried to do a firmware update and he bricked the phone.
I bought it and I am desperately trying to recover it.
Here is what I know about the phone:
It had Android 5.1.1
It had Emui 3.1 and was trying to upgrade to 4.0
(Probably was rooted)
It is H60-L12
No matter what I do, I cannot enter recovery mode with the 3 button trick.
I can anytime enter Fastboot mode.
I tried to unbrick it with HONOR Multi-Tool, everything seems to work alright, but flashing boot.img fails. After unbrick I should enter recovery mode but it does not work, phone remains stuck with the Honor logo.
Computer connects to phone in Fastboot mode, Multi-tool and fastboot command works, I also have the drivers installed.
I know that after bricking the rooted phone, I should restore it and remove root before upgrade but I cannot get there.
Please advise
Best regards,
Janos
Click to expand...
Click to collapse
Instead of using the honor multi tool, why don't you use the Android SDK platform tools and connect to your phone through adb. You can solve any problem using that. You have to do everything manually but it works and never disappoints as long as you can enter fastboot mode.
Download android SDK and install it. Run the program and only choose platform tools to download. You don't need anything else
Download the latest firmware for your phone and unzip it to get dload folder which will have an update.app in it.
Download Huawei update extractor and open update.app in it.
Extract recovery, boot, Cust and system images from update.app and save them to the platform tools folder.
Flash them using adb and then do a forced update.
Will work wonders. If you need any help or need more info, please let me know.

Hello muradulislam
First of all, thank you for trying to help me.
I tried something similar to your suggestion but I still have problems.
Let me explain.
My phone is H60-L12
Latest stable firmware which I found is this one:
H60-L02-L12_EMUI3.1_Android5.1_C00B535.zip
I extracted the boot, cust, recovery and system images with Huawei update extractor.
My device is detected in fastboot mode, fastboot devices gives me this result:
c:\adb>fastboot devices
F6CDU15117010953 fastboot
When I try to flash the boot.img, it gives me this error:
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (10274 KB)...
OKAY [ 1.092s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 1.135s
I tried to continue with the rest but I think this is useless.
Please tell me what to do.
Best regards,
Janos

janos666 said:
Hello muradulislam
First of all, thank you for trying to help me.
I tried something similar to your suggestion but I still have problems.
Let me explain.
My phone is H60-L12
Latest stable firmware which I found is this one:
H60-L02-L12_EMUI3.1_Android5.1_C00B535.zip
I extracted the boot, cust, recovery and system images with Huawei update extractor.
My device is detected in fastboot mode, fastboot devices gives me this result:
c:\adb>fastboot devices
F6CDU15117010953 fastboot
When I try to flash the boot.img, it gives me this error:
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (10274 KB)...
OKAY [ 1.092s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 1.135s
I tried to continue with the rest but I think this is useless.
Please tell me what to do.
Best regards,
Janos
Click to expand...
Click to collapse
My expertise are quite limited but may be, just may be (wishful thinking), you can to flash the twrp recovery specific for your phone. Boot into that and flash a custom ROM from there.
It may not work as I guess, boot.img is needed before entering recovery but give it a try. It never hurts.

Come on, guys!
There must be somebody who can help me.
Guillermo, panamera2011 and muradulislam tried to help me and I want to thank you for their patience.
Problem is, that I am still missing something.
There are 2 weeks now, each day after work I try to revive this phone.
These are the facts I know:
Tried the programs on 4 different machines, Windows 7, Windows 8.1, Windows 10, 32 bit and 64 bit versions.
Tried different sets of drivers (the one from Android SDK, the Universal ADB drivers, the ones installed by multi-tool)
Result is always the same.
I can flash anytime, any version of cust.img recovery.img and system.img but I can flash only the boot.img which is resulting from an EMUI2.3 or EMUI3.0 package.
If I try to flash boot.img from EMUI3.1 or EMUI4.0, I get the following error:
sending 'boot' (10274 KB)...
OKAY [ 1.103s]
writing 'boot'...
FAILED (remote: flash write failure)
Click to expand...
Click to collapse
I tried flashing different stock or CWM or TWRP recoveries. They all are written correctly, but I cannot enter any recovery mode.
Someone advised me to try to flash fastboot.img. It is not working, gives error.
I have already many hours and maybe hundreds of firmware writes, I downloaded around 100 GB of firmwares....
There must be an idea how to save this phone.
I am open to any decent advice.
Best regards,
Janos

janos666 said:
Come on, guys!
There must be somebody who can help me.
Guillermo, panamera2011 and muradulislam tried to help me and I want to thank you for their patience.
Problem is, that I am still missing something.
There are 2 weeks now, each day after work I try to revive this phone.
These are the facts I know:
Tried the programs on 4 different machines, Windows 7, Windows 8.1, Windows 10, 32 bit and 64 bit versions.
Tried different sets of drivers (the one from Android SDK, the Universal ADB drivers, the ones installed by multi-tool)
Result is always the same.
I can flash anytime, any version of cust.img recovery.img and system.img but I can flash only the boot.img which is resulting from an EMUI2.3 or EMUI3.0 package.
If I try to flash boot.img from EMUI3.1 or EMUI4.0, I get the following error:
sending 'boot' (10274 KB)...
OKAY [ 1.103s]
writing 'boot'...
FAILED (remote: flash write failure)
I tried flashing different stock or CWM or TWRP recoveries. They all are written correctly, but I cannot enter any recovery mode.
Someone advised me to try to flash fastboot.img. It is not working, gives error.
I have already many hours and maybe hundreds of firmware writes, I downloaded around 100 GB of firmwares....
There must be an idea how to save this phone.
I am open to any decent advice.
Best regards,
Janos
Click to expand...
Click to collapse
@DigiGoon
You can flash boot.img from emui 2.3 or 3.0? If its written correctly then may be you can try to boot into that emui version by flashing Cust, system and recovery from the same firmware?
Your last hope is Huawei customer service.

Yes, I can flash cust, recovery and system from the same EMUI2.3 or 3.0 package, but I am still unable to boot recovery.
Unfortunately, Huawei customer service will not help me because phone is H60-L12 (Chinese version) and they don't provide support only for L04

janos666 said:
Yes, I can flash cust, recovery and system from the same EMUI2.3 or 3.0 package, but I am still unable to boot recovery.
Unfortunately, Huawei customer service will not help me because phone is H60-L12 (Chinese version) and they don't provide support only for L04
Click to expand...
Click to collapse
Well, I have mentioned DigiGoon in the previous reply. May be he can help a bit.

@janos666
You can always put your desired boot.img in a flashable zip, and flash it via TWRP recovery.

Hi DigiGoon!
No, I cannot, because I was never able to access any kind of recovery

janos666 said:
Hi DigiGoon!
No, I cannot, because I was never able to access any kind of recovery
Click to expand...
Click to collapse
You can't mix LP and MM ROMs and IMG files. If you want to downgrade, for example, from MM to LP you must use B800 transitional package.
So you must use IMG files from last installed working ROM.

muradulislam said:
@DigiGoon
You can flash boot.img from emui 2.3 or 3.0? If its written correctly then may be you can try to boot into that emui version by flashing Cust, system and recovery from the same firmware?
Your last hope is Huawei customer service.
Click to expand...
Click to collapse
zinko_pt said:
You can't mix LP and MM ROMs and IMG files. If you want to downgrade, for example, from MM to LP you must use B800 transitional package.
So you must use IMG files from last installed working ROM.
Click to expand...
Click to collapse
Hi zinko_pt
Thank you for your reply.
So this means that I should find out what version he flashed? He told me that flashing firmware went OK, but after reboot, phone wasn't starting anymore.

janos666 said:
Hi zinko_pt
Thank you for your reply.
So this means that I should find out what version he flashed? He told me that flashing firmware went OK, but after reboot, phone wasn't starting anymore.
Click to expand...
Click to collapse
Sure. I would go from there as I sometimes mixed boot.img from LP or MM and always got bootloop. I would stick to IMG files from last installed ROM.

janos666 said:
Hi zinko_pt
Thank you for your reply.
So this means that I should find out what version he flashed? He told me that flashing firmware went OK, but after reboot, phone wasn't starting anymore.
Click to expand...
Click to collapse
If it was Marshmallow, you have to flash transition package as zinko_pt said, otherwise you have to flash all the IMG files of Lollipop.
And after executing this command from fastboot mode
Code:
fastboot reboot
do you see notification LED light up?

DigiGoon said:
If it was Marshmallow, you have to flash transition package as zinko_pt said, otherwise you have to flash all the IMG files of Lollipop.
And after executing this command from fastboot mode
Code:
fastboot reboot
do you see notification LED light up?
Click to expand...
Click to collapse
Hi DigiGoon !
Sorry, which one is the flash transition package?
Which parts to flash from it?
Which is notification LED? I can see only one red LED blinking sometimes, but only when battery is low.

DigiGoon said:
If it was Marshmallow, you have to flash transition package as zinko_pt said, otherwise you have to flash all the IMG files of Lollipop.
And after executing this command from fastboot mode
Code:
fastboot reboot
do you see notification LED light up?
Click to expand...
Click to collapse
Isn't there an option to flash all img files from fastboot?
P.S. I just got new info from the guy who flashed it first time. He says he tried to write version:
H60-L02-L12_emui3.1_android5.1_c00B535

Is there such thing as "not correctly unlocked" or "partially unlocked" bootloader?
When i try to write some parts of the firmware, i get the following error:
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
Normally this would mean that the bootloader is NOT unlocked, but anyway i test it, it says unlocked.
If i type fastboot oem get-bootinfo, i get the following result:
c:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.003s]
finished. total time: 0.005s
Click to expand...
Click to collapse
Also the fastboot screen displays in red "PHONE UNLOCKED"
I can write some parts of the firmware, but not the fastboot.img, and boot.img only from EMUI2.3 or EMUI3.0
Please help me

janos666 said:
Is there such thing as "not correctly unlocked" or "partially unlocked" bootloader?
When i try to write some parts of the firmware, i get the following error:
FAILED (remote: Command not allowed)
Normally this would mean that the bootloader is NOT unlocked, but anyway i test it, it says unlocked.
If i type fastboot oem get-bootinfo, i get the following result:
c:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.003s]
finished. total time: 0.005s
Also the fastboot screen displays in red "PHONE UNLOCKED"
I can write some parts of the firmware, but not the fastboot.img, and boot.img only from EMUI2.3 or EMUI3.0
Please help me
Click to expand...
Click to collapse
Some threads mention of locking and unlocking your device again. Give that a try. May help...

muradulislam said:
Some threads mention of locking and unlocking your device again. Give that a try. May help...
Click to expand...
Click to collapse
I don't have the unlock code that's why I cannot try to relock it... And in this state I cannot get the necessary info to obtain the unlock code.
Anyway, when I tried to unlock with a bogus unlock code (1234567812345678), it gave me an error something like this:
Command failed, bootloader already unlocked.

janos666 said:
I don't have the unlock code that's why I cannot try to relock it... And in this state I cannot get the necessary info to obtain the unlock code.
Anyway, when I tried to unlock with a bogus unlock code (1234567812345678), it gave me an error something like this:
Command failed, bootloader already unlocked.
Click to expand...
Click to collapse
The info you are missing is device id, another user got his device id using Huawei hacker toolkit v 1.4, his model was h60-L02. May be you can give it a try.
You have to lock it before trying to unlock again.
Fastboot OEM lock xxxxxxxxxxxxxxxx...

[SOLVED] Installed LineageOS with custom LineageOS Recovery then locked bootloader

I got LineageOS installed, restarted to bootloader and locked bootloader.
I can now:
Get into LineageOS Recovery
Boot to LineageOS ROM
I cannot:
Unlock bootloader
Unlock flashing
Unlock OEM from developer options (Option is greyed out)
What I tried, rooting and trying the following adb commands.
HTML:
adb root
adb shell setprop ro.oem_unlock_supported 1
Got the error:
HTML:
setprop: failed to set property 'ro.oem_unlock_supported' to '1'
I can only run LineageOS and go into LineageOS recovery and Adb sideload from recovery and install rooting apps.
Help! Want to 'fastboot flashing unlock'
Video:
https://vimeo.com/304615053
UPDATE:
UPDATE: Solution given by the dev razorloves(https://forum.xda-developers.com/member.php?u=614507) the dev who mantains the LineageOS ROM for Pixel details here:
https://forum.xda-developers.com/showpost.php?p=78361157&postcount=32

I am not sure, and I think someone else can chime in but, I have always heard that you never ever relock the bootloader with anything custom for the Pixel. Have you tried the fastboot flashing unlock critical command? I am not sure the exact command but if you Google it you will see. I think thats about your only hope.

Archangel said:
I am not sure, and I think someone else can chime in but, I have always heard that you never ever relock the bootloader with anything custom for the Pixel. Have you tried the fastboot flashing unlock critical command? I am not sure the exact command but if you Google it you will see. I think thats about your only hope.
Click to expand...
Click to collapse
Yeah, I goofed up.
Tried unlock_critical
HTML:
[email protected]:~$ fastboot flashing unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.029s
[email protected]:~$ fastboot flashing unlock_critical
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.013s
[email protected]:~$
What I cannot understand is I have a perfectly working LineageOS ROM and LineageOS Custom Recovery. There should ideally be a way

I guess on the bright side at least you have a working phone and a custom rom. But as far as removing it or going back to stock I am not that sure because I believe you need to be unlocked to do that and the system is locked down tight now. I am sure someone else smarter than me will help with an answer, sorry brother wish I could help more.
tomatosmoothie said:
Yeah, I goofed up.
Tried unlock_critical
HTML:
[email protected]:~$ fastboot flashing unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.029s
[email protected]:~$ fastboot flashing unlock_critical
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.013s
[email protected]:~$
What I cannot understand is I have a perfectly working LineageOS ROM and LineageOS Custom Recovery. There should ideally be a way
Click to expand...
Click to collapse

Archangel said:
I guess on the bright side at least you have a working phone and a custom rom. But as far as removing it or going back to stock I am not that sure because I believe you need to be unlocked to do that and the system is locked down tight now. I am sure someone else smarter than me will help with an answer, sorry brother wish I could help more.
Click to expand...
Click to collapse
Nah man, thanks for looking in, sometimes, when your banging your head against a wall, it's nice if at least someone looks in lol, I would feel so alone if no one replied Thank you!
Pondering of flashing the Unofficial LOS 16 which has been created by the same dev as the Official LOS 15 via LOS Recovery. to change things up.

I hearya nothings worse than having a problem and your the only one. Did that on a few phones. I have the Pixel 3 too now and I stay stock with some small edits and my Substratum themes running. I love the custom roms but sometimes they can be a real pain. Yeah I would give LOS 16 a try I guess what do you have to lose.
tomatosmoothie said:
Nah man, thanks for looking in, sometimes, when your banging your head against a wall, it's nice if at least someone looks in lol, I would feel so alone if no one replied Thank you!
Pondering of flashing the Unofficial LOS 16 which has been created by the same dev as the Official LOS 15 via LOS Recovery. to change things up.
Click to expand...
Click to collapse

tomatosmoothie said:
Pondering of flashing the Unofficial LOS 16 which has been created by the same dev as the Official LOS 15 via LOS Recovery. to change things up.
Click to expand...
Click to collapse
Sorry I don't have experience with that situation and hope someone with the knowledge will be able to help you, but in the meantime I just wanted to chime in because you are pretty lucky in your misfortune to have a working phone, usually relocking bootloader while on a custom ROM results in a bootloop 99.9% of the time. So I would advise not tinkering with your ROM but focusing on finding a way either to unlock bootloader or to get back to stock firmware.

bafforosso said:
Sorry I don't have experience with that situation and hope someone with the knowledge will be able to help you, but in the meantime I just wanted to chime in because you are pretty lucky in your misfortune to have a working phone, usually relocking bootloader while on a custom ROM results in a bootloop 99.9% of the time. So I would advise not tinkering with your ROM but focusing on finding a way either to unlock bootloader or to get back to stock firmware.
Click to expand...
Click to collapse
Thanks, I was thinking the same thing, also, the idea was to flash a ROM that would be able to allow OEM unlocking in dev options, but I feel maybe LOS Recovery is not allowing me to unlock.
Also thinking of flashing stock factory image via LOS Recovery.
I will tread carefully though, thanks.

No way your bl is locked.
Sent from my Pixel XL using Tapatalk

lafester said:
No way your bl is locked.
Click to expand...
Click to collapse
Hmm yeah I was wondering the same as it would be a pretty serious security bug if a locked bootloader let's a device with LOS boot. Could it be that only the "unlockability" switch was switched off but it did not really locked your bootloader, just the ability to modify it's status?
Don't you get the "open padlock" / "your device software can't be checked for corruption..." screen when you boot?
I think you really should try flashing stock firmware.

bafforosso said:
Hmm yeah I was wondering the same as it would be a pretty serious security bug if a locked bootloader let's a device with LOS boot. Could it be that only the "unlockability" switch was switched off but it did not really locked your bootloader, just the ability to modify it's status?
Don't you get the "open padlock" / "your device software can't be checked for corruption..." screen when you boot?
I think you really should try flashing stock firmware.
Click to expand...
Click to collapse
"Your device has loaded a different operating system" is what I get at boot and a "OS fingerprint" below that.
No padlock on the google screen.
I'm waiting for a factory image to download and will try flashing.
LOS Recovery is flashing LOS Nightlies so there is some flashing happening, only question is will LOS Recovery flash a Pixel Factory Image.

tomatosmoothie said:
"Your device has loaded a different operating system" is what I get at boot and a "OS fingerprint" below that.
No padlock on the google screen.
I'm waiting for a factory image to download and will try flashing.
LOS Recovery is flashing LOS Nightlies so there is some flashing happening, only question is will LOS Recovery flash a Pixel Factory Image.
Click to expand...
Click to collapse
Sorry I mixed things up : use the flash-all.sh (or flash-all.bat if using Windows) script with your device in fastboot mode as described on the stock firmwares download page.
[Correct but not for flashing stock firmware]
No idea, never used, but you should be able to "fastboot boot" into twrp and flash.
Don't flash twrp afterwards as it is known to cause bootloops under some circumstances with the December update, and as a rule of thumb with A/B partition devices just keep stock recovery and use a computer to "fastboot boot" into TWRP when you need to flash something, it is a lot safer (still talking about stock firmware as I don't know anything about LOS/LOS recovery).

bafforosso said:
No idea, never used, but you should be able to "fastboot boot" into twrp and flash.
Don't flash twrp afterwards as it is known to cause bootloops under some circumstances with the December update, and as a rule of thumb with A/B partition devices just keep stock recovery and use a computer to "fastboot boot" into TWRP when you need to flash something, it is a lot safer (still talking about stock firmware as I don't know anything about LOS/LOS recovery).
Click to expand...
Click to collapse
Tried that earlier, didn't work. Trying now.
Advanced Restart is enabled in Dev options.
Restarted to bootloader.
HTML:
[email protected]:~$ fastboot boot '/media/twrp-3.2.3-1-sailfish.img'
Downloading 'boot.img' OKAY [ 1.064s]
booting (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 9.237s
[email protected]:~$

tomatosmoothie said:
Tried that earlier, didn't work. Trying now.
Advanced Restart is enabled in Dev options.
Restarted to bootloader.
HTML:
[email protected]:~$ fastboot boot '/media/twrp-3.2.3-1-sailfish.img'
Downloading 'boot.img' OKAY [ 1.064s]
booting (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 9.237s
[email protected]:~$
Click to expand...
Click to collapse
Sorry edited my post because I mixed up things, my bad.
No recovery needed to flash stock firmware, just use instructions from the Stock Firmware Download Page

bafforosso said:
Sorry edited my post because I mixed up things, my bad.
No recovery needed to flash stock firmware, just use instructions from the Stock Firmware Download Page
Click to expand...
Click to collapse
Yeah, that page says flash unlock is required
Hoping, LOS Recovery will flash it, since it's flashing LOS Nightlies.
HTML:
[email protected]:~$ fastboot flashing unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.025s
[email protected]:~$ fastboot flashing unlock_critical
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.034s
[email protected]:~$ fastboot oem unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.027s
[email protected]:~$

tomatosmoothie said:
Yeah, that page says flash unlock is required
Hoping, LOS Recovery will flash it, since it's flashing LOS Nightlies.
Click to expand...
Click to collapse
If what I suspect - that the bootloader is not the original one but a modded one from LOS and in fact it is not really enforcing the locked state but just locks use of the fastboot unlock/lock instructions or some similar behaviour - then you have to try steps 5. and 6. no matter what is the output of the previous commands.
As you wish, it is your phone but if you don't try we'll never know...

bafforosso said:
If what I suspect - that the bootloader is not the original one but a modded one from LOS and in fact it is not really enforcing the locked state but just locks use of the fastboot unlock/lock instructions or some similar behaviour - then you have to try steps 5. and 6. no matter what is the output of the previous commands.
As you wish, it is your phone but if you don't try we'll never know...
Click to expand...
Click to collapse
Yeah, there is one more catch. You cannot choose a file in LOS Recovery, it is encrypted.
So the only choice is "adb sideloar file.zip"

bafforosso said:
If what I suspect - that the bootloader is not the original one but a modded one from LOS and in fact it is not really enforcing the locked state but just locks use of the fastboot unlock/lock instructions or some similar behaviour - then you have to try steps 5. and 6. no matter what is the output of the previous commands.
As you wish, it is your phone but if you don't try we'll never know...
Click to expand...
Click to collapse
Yeah, there is one more catch. You cannot choose a file in LOS Recovery, it is encrypted.
So the only choice is "adb sideload file.zip"

tomatosmoothie said:
Yeah, there is one more catch. You cannot choose a file in LOS Recovery, it is encrypted.
So the only choice is "adb sideloar file.zip"
Click to expand...
Click to collapse
Come on man please, I know you're probably tired of this but I stated that "No recovery needed to flash stock firmware, just use instructions from the Stock Firmware Download Page" and nowhere does it states anything about recovery, adb push, sideload or what not...
Here is a simplification of the part of the instructions on that page you should follow, everything has to be done from your computer with your phone plugged to it in fastboot mode :
On your computer, download stock firmware full image for your device.
Unzip the stock firmware image just downloaded.
Open a terminal and navigate to the unzipped stock firmware image directory.
Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system
P.S.: Forgot to warn but this will delete all your data from your phone.

bafforosso said:
Come on man please, I know you're probably tired of this but I stated that "No recovery needed to flash stock firmware, just use instructions from the Stock Firmware Download Page" and nowhere does it states anything about recovery, adb push, sideload or what not...
Here is a simplification of the part of the instructions on that page you should follow, everything has to be done from your computer with your phone plugged to it in fastboot mode :
On your computer, download stock firmware full image for your device.
Unzip the stock firmware image just downloaded.
Open a terminal and navigate to the unzipped stock firmware image directory.
Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system
P.S.: Forgot to warn but this will delete all your data from your phone.
Click to expand...
Click to collapse
Got a Permission denied.
HTML:
[email protected]:/media/disk2/LineageOS/Pie/Pie_Official_Factory/sailfish-ppr2.181005.003.a1$ ./flash-all.sh
bash: ./flash-all.sh: Permission denied

[SOLVED] No boot in TWRP possible. Under no circumstances...

I have a strange problem with my brand new Mi Mix 2s.
My procedure from the beginning:
Unlook using tool from Xiaomi. For this I had to wait 72h.
Subsequently, the unlooking was considered successful.
For this I used my notebook with Windows7 (no VM).
Now I got the needed files and want to start with the installation of TWRP.
I also use my notebook but with Linux, my everyday operating system.
I have set the phone to fastboot mode (vol-down + power).
With fastboot devices you can find the phone. But commands like flash or boot end in a frozen console.
Unusual. Now I try it again in Windows7 (dualboot). The same problem.
Then I try the Windows10 game computer of my son.
The commands are confirmed as successful.
But in fact nothing happens. Nothing is flashed and I am not in the TWRP to boot.
Here the console output:
Code:
#[twrp.ing = twrp-3.2.3-0-polaris.img]
F:\platform-tools>fastboot boot twrp.img
creating boot image...
creating boot image - 43386880 bytes
Downloading 'boot.img' OKAY [ 0.914s]
booting OKAY [ 0.071s]
Finished. Total time: 1.051s
#[black screen]
F:\platform-tools>fastboot devices
19cf4510 fastboot
F:\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (42368 KB) OKAY [ 0.951s]
Writing 'recovery' OKAY [ 0.201s]
Finished. Total time: 1.165s
F:\platform-tools>fastboot devices
19cf4510 fastboot
F:\platform-tools>fastboot boot twrp.img
creating boot image...
creating boot image - 43386880 bytes
Downloading 'boot.img' OKAY [ 0.910s]
booting FAILED (remote: 'Failed to load/authenticate boot image: 00000050')
Finished. Total time: 1.009s
F:\platform-tools>fastboot devices
19cf4510 fastboot
F:\platform-tools>fastboot reboot
Rebooting
Finished. Total time: 0.004s
#[reboot]
Unfortunately, I am not aware of any possibilities to solve the problem further.
Does anyone have suggestions or ideas?

Which TWRP are you flashing? Are you sure that it is the proper file for mix 2s?
What happens when you reboot the phone after flashing recovery with vol+ and power?
Flash twrp then restart manually holding vol+ and power buttons.

malimukk said:
Which TWRP are you flashing? Are you sure that it is the proper file for mix 2s?
What happens when you reboot the phone after flashing recovery with vol+ and power?
Flash twrp then restart manually holding vol+ and power buttons.
Click to expand...
Click to collapse
Yes. It is this version: https://eu.dl.twrp.me/polaris/
I have tried your tip. Does not work either.

Can it be helpful to close the bootloader and perform unloocking again?
How is the usual way to lock the device again? Using fastboot, or are there other solutions?
Can I really reopen the bootloader afterwards?
Can someone confirm that multiple opening is possible with the MIunlock tool?

yabow said:
Can it be helpful to close the bootloader and perform unloocking again?
How is the usual way to lock the device again? Using fastboot, or are there other solutions?
Can I really reopen the bootloader afterwards?
Can someone confirm that multiple opening is possible with the MIunlock tool?
Click to expand...
Click to collapse
Yes you can unlock again. I've done it myself.
I am not sure what is happening in your situation. Which MIUI version are you running?
I'd suggest you to flash a more recent version of MIUI with the Mi Flash tool.
Perhaps MIUI developer 8.12.27 version.
Let it boot to system after flashing
Then turn off, flash twrp, disconnect cable,
reboot from fastboot with Power and Vol+
No other ideas honestly

malimukk said:
Yes you can unlock again. I've done it myself.
I am not sure what is happening in your situation. Which MIUI version are you running?
I'd suggest you to flash a more recent version of MIUI with the Mi Flash tool.
Perhaps MIUI developer 8.12.27 version.
Let it boot to system after flashing
Then turn off, flash twrp, disconnect cable,
reboot from fastboot with Power and Vol+
No other ideas honestly
Click to expand...
Click to collapse
I have
MIUI-Version 10.2.1.0 GLOBAL
Model M1803D5XA
and using
fastboot version 28.0.1-4986621
on Windows10
I have tried with Linux, but here the comandline hangs and nothing happends...
Do you think i have to use a developer ROM? This can be a problem?

yabow said:
I have
MIUI-Version 10.2.1.0 GLOBAL
Model M1803D5XA
and using
fastboot version 28.0.1-4986621
on Windows10
I have tried with Linux, but here the comandline hangs and nothing happends...
Do you think i have to use a developer ROM? This can be a problem?
Click to expand...
Click to collapse
For me sometimes fastboot just does not want to work on my laptop, then I switch usb ports and it magically works again. It is usually an issue on the PC. try abother cable as well. You cab also try to uninstall your adb/fastboot drivers and install these: https://forum.xda-developers.com/showthread.php?t=2588979
Preferably on the Windows10 machine you have, as it seems closest to working.
Miui version should not be relevant, but it might be that yours is somehow messed up. I would suggest you to avoid using the mi flash tool for now as it uses fastboot to flash the different images and it might cause other issues as clearly fastboot is somehow broken. You can try to update to a dev rom thorough the phone update app?
Btw when you do fastboot boot twrp.img you have to keep the cable plugged in

Didn't change anything. Damn it.

check this
read this page (need a translater)
in MiMix2s_Xiaomi.eu_Firmware yoo find a install_TWRP.bat in folder 02_TWRP
exchange and rename your new twrp to the name in the folder
https://tradingshenzhen.com/de/cont...sh-tutorial-global-firmware-xiaomieu-firmware

So, I tried some TWRP versions (v15, v14, and others) to get the black-screen error again and again. Version v8 finally allowed me to boot into TWRP. Yeah!
Before I closed the bootloader,
got a message about a destroyed device,
reloaded the stock-ROM with MI-flash,
booted TWRP v8 from this thread,
only saw cryptic files and just used an OTG adapter to install more *imgs and *zips.
Not everything works as it should yet, but it will...
Thanks for your help.

yabow said:
So, I tried some TWRP versions (v15, v14, and others) to get the black-screen error again and again. Version v8 finally allowed me to boot into TWRP. Yeah!
Before I closed the bootloader,
got a message about a destroyed device,
reloaded the stock-ROM with MI-flash,
booted TWRP v8 from this thread,
only saw cryptic files and just used an OTG adapter to install more *imgs and *zips.
Not everything works as it should yet, but it will...
Thanks for your help.
Click to expand...
Click to collapse
Your storage is encrypted, that's why you have the "cryptic files".
TWRP v8 can not decrypt your storage, the latest version can though

[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.

Database Info

welcome