Database Users

Error mode: error 11 no recovery, error 2 failed to load

Help
I tried to relock my bootloader but when the device restarted it went straight to error mode.
I managed to boot straight back to full system but whenever I restart it goes back to error mode. I cant enter fastboot or recovery mode.
I sont know what to do now any help
Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Try to boot it again in the full system and from there try to unlock your bootloader.
If you done that, reinstall the software.

How can I unlock bootloader without fastboot? If I attempt to enter fastboot or anything that requires reboot I end up on that screen.

Hmm....
Have you tried rebooting to fastboot using adb?

Johnny TDN said:
Try to boot it again in the full system and from there try to unlock your bootloader.
If you done that, reinstall the software.
Click to expand...
Click to collapse
Johnny TDN said:
Hmm....
Have you tried rebooting to fastboot using adb?
Click to expand...
Click to collapse
I tried but still get to error mode.....I have tried many times

Then i don't know anymore dude. Have you tried reinstalling the firmware using the 3 button method?

elliotn said:
I tried but still get to error mode.....I have tried many times
Click to expand...
Click to collapse
Hello
tested with the toolkit 0.0.0.12.
to see if he recognizes the phone.
he should at least write your serial number.
if that is the case.
you can use DC-unlocker. to open FRP and can be the bootloader.
just an idea.

Dc unlocker needs cash and it doesn t always work.

I am doubting buying DC,unlocker in case,it doesn't work and I will lose money.... I will try toolkit.

3 button upgrade doesn't work either.

I have the same problem after I tried to relock my bootloader using SRKToolHuawei-STABLE-V1.3-20160619 with my bootloader code.
Have you found a solution?
I can boot back into os b394 after I let the battery run out to 0%
I haven't found a way to repair my recovery and fastboot yet because rebooting into fastboot always get's me back to that first error
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)
Then I have to wait for my battery to run out again
Any help to get fast boot and a working recovery back would be appreciated.

Use Huawei multi tool ,then flash system, custom,recovery image ,
If stock recovery opens then use Dload method

shankarjdhv125 said:
Use Huawei multi tool ,then flash system, custom,recovery image ,
If stock recovery opens then use Dload method
Click to expand...
Click to collapse
I got stock recovery back with the warning that my device is unlocked. Now I get stuck at 'Your device is booting now'. After some time it reboots and opens eRecovery which I cannot use.
How do I get anything on my phone to continue with dload and which firmware would you advice me to flash if I finally get there.
Should I, if even possible at the moment, choose an older firmware version?
Edit: Would the original service rom help? Found it here https://forum.xda-developers.com/huawei-p9lite/help/original-service-rom-huawei-p9-lite-vns-t3688120 but my build number seems too high as the version I need only mentions b381 and b383 not the 394 I currently have..

Same problem for me
No way to shutdown the phone, someone have solved?
Now I'm waiting for the battery to full drain

Hi guys i ve made mistake because i wanted to update to latest release media pad m3 but i could not be able to boot to stock recovery after i flash recovery img extracted from update.app and second time i flash recovery2.img to erecovery partition and i got the same issue error Func No 11(recovery image) and Error NO 2 (load failed) . I also put the update.app to dload folder on sd card but update system is not starting i press volume up and down and power button at same time but is not working.I tried also with huawei multitool but is not working is not recognize my device. Please guys is any other solution to fix this ?Thank You!

I just fixed after power off device and then press volume down and plug the usb cable to pc and i was able to recognize my device and i have use huawei multiTool to unbrick my tablet media pad m3 and has work.

Almost the same problem, help please!!!
Hi guys someone can help me? I have a Honor 9 lite(LLD-L31). Android version 8.0
I apologize but I'm a new user and i don't have much practice with modding in general.
I tried to install root permission in my device. I get bootloader unlock code by DC-unlocker and installed TWPR on my device.
When i went in recovery the error " Failed to unmount '/system'(Device or resource busy)" rushed, so I tried to format data in order to give partition available. I tried again to flash file.zip but the search was empty so I downloaded a most recent version(3.2.3) of TWPR in recovery ramdisk.
Now if i try to log into recovery mode appear the same error (Error! func NO 11 / NO 2).
I can do everything aside going in recovery mode. How can I resolve it? Is it possible to reset to factory settings and try again?
I hope I have explained well the problem.

elliotn said:
3 button upgrade doesn't work either.
Click to expand...
Click to collapse
how about this 3 button method??

Astarothkun said:
I got stock recovery back with the warning that my device is unlocked. Now I get stuck at 'Your device is booting now'. After some time it reboots and opens eRecovery which I cannot use.
How do I get anything on my phone to continue with dload and which firmware would you advice me to flash if I finally get there.
Should I, if even possible at the moment, choose an older firmware version?
Edit: Would the original service rom help? Found it here https://forum.xda-developers.com/huawei-p9lite/help/original-service-rom-huawei-p9-lite-vns-t3688120 but my build number seems too high as the version I need only mentions b381 and b383 not the 394 I currently have..
Click to expand...
Click to collapse
Could you write down the steps you took to get back in fastboot for me? I'm having troule geting there myself after draining battery.

I fixed it after nothing else here worked.
So this is mostly so I dont ever forget the solution again, but also to possibly help others.
I also have to say that I had the problem with an P8 Lite, but all my problems matched almost exaclty, so It might help you too.
And a third disclaimer: I have no idea if you can flash the stock firmware without having the bootloader unlocked.
If you dont have it unlocked, try this wonderful updated guide: [Links are disabled for me so google this: "Droidhunter unlock huawei bootloader" and pick the article by droithunter.com]
And yes DC-Unlocker, suprisingly actually works (at least for me) and buying their bootloader unlock code was worth the 4 bucks.
So here is the solution:
1. Somehow, however needed get into fastboot. As I couldn't use the volume/power key combo myself, I somehow force reset the phone, pressing various buttons until I managed to boot into it again. I then used the adb bridge to boot into fastboot (google how to connect adb, then use "adb reboot bootloader" to get into the fastboot menu).
2. Download your phone models default stock rom/Update.app (also google that).
3. Extract the Update.app file.
4. Download and use the HuaweiUpdateExtractor tool and open the Update.app file (google again helps).
5. Select the "09.recovery.img" entry (the one with the green arrow on the left), rightclick and select "extract selected" and save it somewhere where you can find it.
6. Open your Fastboot console on PC (its often the same as the ADB console used before, especially if you use Minimal Fastboot and ADB, which I would recommend).
7. Make sure your phone is in Fastboot mode (not recovery) and connected to the pc.
7.1 Make sure your bootloader is unlocked. It might work with a locked one because youre just flashing stock firmware but eh might break more. Its worth the 4 bucks to unlock the bootloader first. (and yes DC unlocker looks super sketchy but somehow it actually worked for me and wasnt a scam).
8. Flash a custom recovery onto the phone (pretty much the same way you flash twrp, but instead of the twrp image you use the .img file you just extracted from the Update.app; Also dont try flashing twrp directly, it will probably not work).
The command to do so is: "fastboot flash recovery [filepath to the .img file without the brackets]".
9. Use the command "fastboot reboot".
10. If your phone doesnt boot normally, use the key combinations to get into the normal recovery screen and recover from a file or whatever (other guides should work from here).
Extra Steps:
As my recovery image was obviously so broken that even flashing twrp on top of it didnt work until I flashed the original reovery image, I went into my phones settings and did a factory reset. Directly after I installed twrps (see google) and set it up so it had full control. Afterwards I rooted and installed LinageOS cause frick EMUI rn).
Hope this helps anyone. If you have any questions feel free to ask me.

[TWRP & ROOT] Ticwatch E/S & Unroot Instructions for Updates - v003

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAIMER:
I'm not responsible for any damaged watches or other broken things! All of this is still heavily in development and mainly a developer release, not at all recommended for normal usage!
The following tutorial CAN brick your watch if you're not careful enough! Once again I'm not taking any responsibility!
This has only been tested on Android N so far, Android O is not yet fully tested!​
---------------------------------------------------------
Please read before doing anything:
This is a port of TWRP for the Ticwatch E. Currently we're not able to boot it via fastboot (well, it technically does but there's an issue with the video driver) and when trying to flash it the watch will instantly flash the stock recovery over it upon reboot.
To avoid this we have to do a little workaround! Once you reboot your watch it'll restore the stock recovery again! After following these steps your watch will be stuck in a bootloop which we'll fix too tho.
Please keep the Changelog below in mind and read what's working and what's not before asking. We may or may not have seen this issue before already.
Files you'll need:
v003 of "TWRP for Ticwatch E" (and most likely S) - OneDrive Mirror
Stock Recovery for Ticwatch E (and most likely S) - OneDrive Mirror
ADB and Fastboot drivers installed (I recommend "15 Seconds ADB Installer")
Changelog:
Updated Instructions:
Slightly updated the instructions so you won't lose any data if you're already on an bootloader unlocked watch!
v003 (OneDrive Mirror):
Managed to make TWRP persistent! Check Instructions on how to.
v002 (OneDrive Mirror):
Now includes systemless root package inside the TWRP image so you're able to root your watch!
v001 (OneDrive Mirror):
Initial release, no ADB so far. Can't be booted from fastboot directly either due to weird fastboot behavior and has to be flashed first. However upon normal reboot Mobvoi decided to flash over the stock recovery again so we have to do a workaround.
Instructions:
The new Instructions by Luxios require a few less steps AND if you've already unlocked your watch before you won't even lose data!
Enable ADB in the Developer Settings
Once done connect your watch to your computer and do "adb reboot bootloader"
THIS WILL RESET YOUR WATCH:*Once in fastboot mode type "fastboot oem unlock" (if you already have an unlocked bootloader you [font=Verdana, Arial, Helvetica, sans-serif]can skip this[/font])
Follow the on-screen instructions on your watch to unlock it (if you already have an unlocked bootloader you can skip this)
Reboot via "fastboot reboot" and wait until Android Wear fully starts up
One started reboot to the bootloader via the same command as above
Once the bootloader shows up again type "fastboot flash recovery TWRP_TicwatchE_v003.img"
After that type "fastboot oem reboot-recovery" to reboot to the TWRP recovery
In order to make TWRP persistent you need to go to "Install" > "Install ZIP" > "supersu" > "TicwatchE_TWRP_keeper.zip" and flash it
Upon rebooting you may notice it'll get stuck in an infinite TWRP bootloop. To fix this boot into TWRP, then choose "Reboot" > "Bootloader", back in fastboot type "fastboot boot StockRecovery_TicwatchE.img" and wait a few seconds, a few reboots later Android Wear should start right up again.
If you want to root your watch reboot it once again with "adb reboot recovery" and go to the same folder as above, tho this time flash "SuperSU-2.79-wear_systemless.zip"
Unroot/Remove TWRP for Android O Update:
Go to this thread to also update directly to the last Android O update and revert all customizations: https://forum.xda-developers.com/sm...es/android-o-super-easy-ticwatch-e-s-t3789835
Have fun!

You're the best! I'm gonna try as soon as I can, and let you know.

Ok, I'm trying to flash it.
Problem is, it flashes, but when I do fastboot reboot, it will boot in android wear instead that TWRP.
If then I reboot in the recovery with adb reboot recovery, it will be already the stock recovery again... Any tip?

Piereligio said:
Ok, I'm trying to flash it.
Problem is, it flashes, but when I do fastboot reboot, it will boot in android wear instead that TWRP.
If then I reboot in the recovery with adb reboot recovery, it will be already the stock recovery again... Any tip?
Click to expand...
Click to collapse
If your bootloader is (or was) already unlocked you have to lock and then unlock it again for it to work.

Yes sorry, I noticed that right after posting, but I've bad network.
Now seems to have gone all fine, I'm booting it, I'm only unsure it flashed SuperSU well, since it shown an error at the end of the script, although the rest of the log seemed to report all to go fine.

Piereligio said:
Yes sorry, I noticed that right after posting, but I've bad network.
Now seems to have gone all fine, I'm booting it, I'm only unsure it flashed SuperSU well, since it shown an error at the end of the script, although the rest of the log seemed to report all to go fine.
Click to expand...
Click to collapse
The guy who made it initially did send me a picture of it successfully rooted. Should work, errors can happen since TWRP can't write to all partitions yet.

Sadly it looks like SuperSU failed to root. It gave a data partition mounting error at the end of the script, don't know if it is normal. TWRP isn't able to mount data either.
EDIT: Looks like I found a way to boot TWRP without having to lock/unlock bootloader.
Doing this, I managed to boot TWRP after setting the watch up, and in this way, it didn't fail to mount /data. Let's see...
EDIT2: now SuperSU still fails, but for a different reason. I'm gonna ensure that it failed though.
EDIT3: su command responded, so seems that root works. I'll do some more tests.

TWRP is now persistent! Check the updated guide

Rooting succeeded!
Seems like I managed to root the smartwatch using the version 2. For the moment I'm happy like this, next times I'll indeed use new procedures.
EDIT: Yes, I rooted it.
My steps (the ones on OP are the recommended ones):
-Bootloader unlock;
-Boot in Android Wear to enable ADB from Settings;
-Reboot in bootloader with "adb reboot bootloader";
-Flashed this TWRP v2;
-"fastboot reboot", then "adb reboot recovery" as soon as adb was detected while booting.
In this way I managed to avoid the system to flash stock recovery over TWRP.
By the way, I don't recommend my way of rooting it, it's less safe, just follow the updated instructions in OP.
Huge thanks to @EpicLPer

Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.

BackCheck said:
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
Click to expand...
Click to collapse
If the watch doesn't turn off even after holding the button for a minute then you've damaged something else than just the recovery. Holding down the button normally triggers all the time no matter what, even if you'd have bricked it.

BackCheck said:
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
Click to expand...
Click to collapse
You can flash again the stock recovery with spflash tool.

EpicLPer said:
If the watch doesn't turn off even after holding the button for a minute then you've damaged something else than just the recovery. Holding down the button normally triggers all the time no matter what, even if you'd have bricked it.
Click to expand...
Click to collapse
I really wish I knew what. All I did was flash a bad recovery, pretty sure something was was wrong with the ram disk. All I get is the splash logo for 3 seconds and a brief vibrate.
Luxios said:
You can flash again the stock recovery with spflash tool.
Click to expand...
Click to collapse
I think I need a scatter file to even get started. I've never used the tool so any other instructions would be greatly appreciated.

Great to hear someone that it is working on this! What about Android Wear updates? Did you try if it is possible to install them using TWRP?
Edit 1: Just tried to install twrp but inside "supersu" folder there is only "SuperSU-2.79-wear_systemless.zip", where can I find "TicwatchE_TWRP_keeper.zip"?

elios93 said:
Great to hear someone that it is working on this! What about Android Wear updates? Did you try if it is possible to install them using TWRP?
Edit 1: Just tried to install twrp but inside "supersu" folder there is only "SuperSU-2.79-wear_systemless.zip", where can I find "TicwatchE_TWRP_keeper.zip"?
Click to expand...
Click to collapse
I have the same problem...
EDIT: I have a Ticwatch S.

Niktendo said:
I have the same problem...
EDIT: I have a Ticwatch S.
Click to expand...
Click to collapse
I've managed to install it anyway. First check if it is not already installed using command
Code:
adb reboot recovery
If it does not work try this after you are in bootloader:
Code:
fastboot flash recovery TWRP_TicwatchE_v003.img
fastboot reboot
Then, as suggested by @Piereligio send this command as soon as possible while the watch is booting:
Code:
adb reboot recovery
This should work
However it is interesting that you have a S model. By sharing the build.prop of your device should be possible unlock all watchfaces for E model for instance!

elios93 said:
I've managed to install it anyway. First check if it is not already installed using command
Code:
adb reboot recovery
If it does not work try this after you are in bootloader:
Code:
fastboot flash recovery TWRP_TicwatchE_v003.img
fastboot reboot
Then, as suggested by @Piereligio send this command as soon as possible while the watch is booting:
Code:
adb reboot recovery
This should work
However it is interesting that you have a S model. By sharing the build.prop of your device should be possible unlock all watchfaces for E model for instance!
Click to expand...
Click to collapse
This is the best way i found to install the TWRP recovery:
- Unlock the boot loader
- Reboot, wait until android start again
- Reboot again in boot loader mode
- flash the twrp v003 recovery
- type:
Code:
fastboot oem reboot-recovery
- Flash the twrp keeper zip package
- flash the root zip package (if you want root)

EpicLPer said:
The guy who made it initially did send me a picture of it successfully rooted. Should work, errors can happen since TWRP can't write to all partitions yet.
Click to expand...
Click to collapse
Can you get me the device tree or at least BoardConfig.mk used for this? I have a working watch (still working on recovering the old one) and I think I can get the rest of the partitions working but I would really like to avoid any more mistakes.
Luxios said:
This is the best way i found to install the TWRP recovery:
- Unlock the boot loader
- Reboot, wait until android start again
- Reboot again in boot loader mode
- flash the twrp v003 recovery
- type:
Code:
fastboot oem reboot-recovery
- Flash the twrp keeper zip package
- flash the root zip package (if you want root)
Click to expand...
Click to collapse
That 'fastboot oem reboot-recovery' command sure is a nice find!

Hey, bought my ticwatch e used online.
The watch is almost new and everything works as it should, but it has these two developer orriented apps preinstalled and can’t be uninstalled via settings neither with a factory reset.
They dont do anything but i just want to remove them
https://photos.app.goo.gl/gTNg5QCPzBtKgnzy1
And yeah the watch also generates a bug report by itself everyday i also want to stop that lol

hassanabid94 said:
Hey, bought my ticwatch e used online.
The watch is almost new and everything works as it should, but it has these two developer orriented apps preinstalled and can’t be uninstalled via settings neither with a factory reset.
They dont do anything but i just want to remove them
https://photos.app.goo.gl/gTNg5QCPzBtKgnzy1
And yeah the watch also generates a bug report by itself everyday i also want to stop that lol
Click to expand...
Click to collapse
Maybe it's a specific developer unit. Don't do anything with it yet, we could loom further into this if it is something special.

Do you know how recovery essential phone from the corrupt?

After several steps after installed twrp, now my essential phone is like these:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Chiminwon said:
After several steps after installed twrp, now my essential phone is like these:
Click to expand...
Click to collapse
Could you rephrase what your question is? I would like to help but can't figure out what you are explaining. I'm assuming you have unlocked the bootloader. I had some problems with this phone at first too. Most of the problems when compared to other phones is that Essential Phone has 2 partitions, like the Pixel. For simplicity, one is sort of the ACTIVE side and the other INACTIVE side. It has some learning. If you are just trying to get up and running try these steps...
1- Wipe data using fastboot command fastboot -w ---- locate the Stock ROM section in Essentials forum here on XDA and get the current STOCK build for your needs. Download it. And flash it in fastboot using the flash-all.bat file. Most will flash the files to both partitions, if it does not use the command in the next step to switch partitions and flash the other side too. This will set your phone back to stock and it should boot nicely. If you wish to root then proceed. BOOT INTO THE STOCK OS EVEN IF YOU ARE STILL GOING TO ROOT THE DEVICE. JUST BOOT UP, THEN REBOOT TO THE BOOTLOADER. DONT SIGN INTO YOUR GOOGLE AND DO NOT SET LOCK OR PASSWORD OR FINGERPRINT YET
2- Follow step one and then reboot into fastboot and use command fastboot set_active other --------- this will do two things. It will switch your partition and also tell you which one it switched to. There is an A side and a B sideFOR THIS EXAMPLE WE WILL PRETEND THAT AFTERYOU SWITCHED YOU ARE ON SIDE B
3- Stay in fastboot and flash twrp11mata using fastboot command fastboot flash boot exactTWRPfilename.img ------ this will boot you into TWRP on the B side
This next rule is very importantTWRP flashes a zip and a img file different. ZIP ROM FILES FLASH TO THE OPPOSITE PARTITION, IMG FILES flash to the partition that you are currently using. So, if you booted into TWRP on the "b" side and without switching flashed a new kernel or boot image it would install to the same "b" side you are on. If you did the same with a ROM it would install to the 'a" side. So, at some point you have to switch sides from within TWRP in the Reboot tab.
4- Copy your Roms/files to your phones internal memory and then flash using twrp. Flash the ROM not sideload. Flashing is for new roms, sideload is for updates to existing ROM. Back to our example, you booted into TWRP on side b, if you install new rom it will install on side A. Lets keep that idea going for the example. BE AWARE THAT IN THIS TYPE OF DEVICE, using our example where we flashed the rom to the A side (from TWRP on the B side), that side will not have TWRP. It will have stock recovery.
5- once the rom is flashed reboot system. (wipe cache / dont wipe cache.. I havent noticed a difference with either mindset) It will switch your partitions upon reboot if you don't do anything else in twrp.
So for our example this is what happened:
Wiped data from both partitions of the PH-1, side "a" and side "b"
Went BACK-TO-STOCK on BOTH sides
BOOTED INTO STOCK ROM ON THE SIDE WE WISH TO BE OUR ACTIVE SIDE***DID NOT SET UP GOOGLE OR PIN/FINGERPRINT/PASSCODE****
reboot into bootloader
Used Fastboot to switch partitions and installed TWRP to the INACTIVE side. Boot into twrp.
In TWRP, copied new files to phone storage the flashed new ROM Remember it will install it to the other side which is our ACTIVE side
reboot system.
If this helped at all and got you running great. Rooting is simple from here. This phone was the first device I ever rooted so I took my lumps so I hope I offered some tips that I didn't find or understand fully at first. Happy exploring. Ask away if I can help further.

KingBeefy said:
Could you rephrase what your question is? I would like to help but can't figure out what you are explaining. I'm assuming you have unlocked the bootloader. I had some problems with this phone at first too. Most of the problems when compared to other phones is that Essential Phone has 2 partitions, like the Pixel. For simplicity, one is sort of the ACTIVE side and the other INACTIVE side. It has some learning. If you are just trying to get up and running try these steps...
1- Wipe data using fastboot command fastboot -w ---- locate the Stock ROM section in Essentials forum here on XDA and get the current STOCK build for your needs. Download it. And flash it in fastboot using the flash-all.bat file. Most will flash the files to both partitions, if it does not use the command in the next step to switch partitions and flash the other side too. This will set your phone back to stock and it should boot nicely. If you wish to root then proceed. BOOT INTO THE STOCK OS EVEN IF YOU ARE STILL GOING TO ROOT THE DEVICE. JUST BOOT UP, THEN REBOOT TO THE BOOTLOADER. DONT SIGN INTO YOUR GOOGLE AND DO NOT SET LOCK OR PASSWORD OR FINGERPRINT YET
2- Follow step one and then reboot into fastboot and use command fastboot set_active other --------- this will do two things. It will switch your partition and also tell you which one it switched to. There is an A side and a B sideFOR THIS EXAMPLE WE WILL PRETEND THAT AFTERYOU SWITCHED YOU ARE ON SIDE B
3- Stay in fastboot and flash twrp11mata using fastboot command fastboot flash boot exactTWRPfilename.img ------ this will boot you into TWRP on the B side
This next rule is very importantTWRP flashes a zip and a img file different. ZIP ROM FILES FLASH TO THE OPPOSITE PARTITION, IMG FILES flash to the partition that you are currently using. So, if you booted into TWRP on the "b" side and without switching flashed a new kernel or boot image it would install to the same "b" side you are on. If you did the same with a ROM it would install to the 'a" side. So, at some point you have to switch sides from within TWRP in the Reboot tab.
4- Copy your Roms/files to your phones internal memory and then flash using twrp. Flash the ROM not sideload. Flashing is for new roms, sideload is for updates to existing ROM. Back to our example, you booted into TWRP on side b, if you install new rom it will install on side A. Lets keep that idea going for the example. BE AWARE THAT IN THIS TYPE OF DEVICE, using our example where we flashed the rom to the A side (from TWRP on the B side), that side will not have TWRP. It will have stock recovery.
5- once the rom is flashed reboot system. (wipe cache / dont wipe cache.. I havent noticed a difference with either mindset) It will switch your partitions upon reboot if you don't do anything else in twrp.
So for our example this is what happened:
Wiped data from both partitions of the PH-1, side "a" and side "b"
Went BACK-TO-STOCK on BOTH sides
BOOTED INTO STOCK ROM ON THE SIDE WE WISH TO BE OUR ACTIVE SIDE***DID NOT SET UP GOOGLE OR PIN/FINGERPRINT/PASSCODE****
reboot into bootloader
Used Fastboot to switch partitions and installed TWRP to the INACTIVE side. Boot into twrp.
In TWRP, copied new files to phone storage the flashed new ROM Remember it will install it to the other side which is our ACTIVE side
reboot system.
If this helped at all and got you running great. Rooting is simple from here. This phone was the first device I ever rooted so I took my lumps so I hope I offered some tips that I didn't find or understand fully at first. Happy exploring. Ask away if I can help further.
Click to expand...
Click to collapse
Hello
I have an essential ph1 phone I bought new from a friend
I registered my google account and secured the phone with a fingerprint
While the update request protection orio8.1 agreed to download and update
Complete the phone Download the update The installation process then stuck a logo ,,
Now the phone is working on fastboot mode only
I can not log into recovery
bootloader lock
oem lock
usb debogen lock
I could not flash any picture ....
I hope anyone who can help me help me solve the problem and thank you

@mouraj2 have you done both commands:
Fastboot flashing unlock
Fastboot flashing unlock critical
---both are needed
Also, I'd recommend getting the current build for your ph-1 from here on xda or essential. Find the firmware you need/want and flash the BTS (back to stock) flash-all.bat. That flashes from fastboot lol. Don't download the OTA get the images file. Easier.
I don't know much about modding phones in general but i can work my way around a ph-1 for sure lol. PM me if u have any more questions

KingBeefy said:
@mouraj2 have you done both commands:
Fastboot flashing unlock
Fastboot flashing unlock critical
---both are needed
Also, I'd recommend getting the current build for your ph-1 from here on xda or essential. Find the firmware you need/want and flash the BTS (back to stock) flash-all.bat. That flashes from fastboot lol. Don't download the OTA get the images file. Easier.
I don't know much about modding phones in general but i can work my way around a ph-1 for sure lol. PM me if u have any more questions
Click to expand...
Click to collapse
The bootloader does not open
C:\Program Files (x86)\Minimal ADB and Fastboot>Fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: -0.000s

mouraj2 said:
The bootloader does not open
C:\Program Files (x86)\Minimal ADB and Fastboot>Fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: -0.000s
Click to expand...
Click to collapse
You need to boot the phone and get into developer mode.
You will need to go into settings, about and tap the build 7 times.
Then go into developer settings and enable boot loader unlock.

tech_head said:
You need to boot the phone and get into developer mode.
You will need to go into settings, about and tap the build 7 times.
Then go into developer settings and enable boot loader unlock.
Click to expand...
Click to collapse
I can not phone stuck on the logo
It does not go into recovery also attached to the logo

mouraj2 said:
The bootloader does not open
C:\Program Files (x86)\Minimal ADB and Fastboot>Fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: -0.000s
Click to expand...
Click to collapse
Go to the essential website and download the latest windows drivers for the PH-1. It's not communicating with the phone. When you type the command "fastboot devices" it is probably not showing any connection to the device , right ?

KingBeefy said:
Could you rephrase what your question is? I would like to help but can't figure out what you are explaining. I'm assuming you have unlocked the bootloader. I had some problems with this phone at first too. Most of the problems when compared to other phones is that Essential Phone has 2 partitions, like the Pixel. For simplicity, one is sort of the ACTIVE side and the other INACTIVE side. It has some learning. If you are just trying to get up and running try these steps...
1- Wipe data using fastboot command fastboot -w ---- locate the Stock ROM section in Essentials forum here on XDA and get the current STOCK build for your needs. Download it. And flash it in fastboot using the flash-all.bat file. Most will flash the files to both partitions, if it does not use the command in the next step to switch partitions and flash the other side too. This will set your phone back to stock and it should boot nicely. If you wish to root then proceed. BOOT INTO THE STOCK OS EVEN IF YOU ARE STILL GOING TO ROOT THE DEVICE. JUST BOOT UP, THEN REBOOT TO THE BOOTLOADER. DONT SIGN INTO YOUR GOOGLE AND DO NOT SET LOCK OR PASSWORD OR FINGERPRINT YET
2- Follow step one and then reboot into fastboot and use command fastboot set_active other --------- this will do two things. It will switch your partition and also tell you which one it switched to. There is an A side and a B sideFOR THIS EXAMPLE WE WILL PRETEND THAT AFTERYOU SWITCHED YOU ARE ON SIDE B
3- Stay in fastboot and flash twrp11mata using fastboot command fastboot flash boot exactTWRPfilename.img ------ this will boot you into TWRP on the B side
This next rule is very importantTWRP flashes a zip and a img file different. ZIP ROM FILES FLASH TO THE OPPOSITE PARTITION, IMG FILES flash to the partition that you are currently using. So, if you booted into TWRP on the "b" side and without switching flashed a new kernel or boot image it would install to the same "b" side you are on. If you did the same with a ROM it would install to the 'a" side. So, at some point you have to switch sides from within TWRP in the Reboot tab.
4- Copy your Roms/files to your phones internal memory and then flash using twrp. Flash the ROM not sideload. Flashing is for new roms, sideload is for updates to existing ROM. Back to our example, you booted into TWRP on side b, if you install new rom it will install on side A. Lets keep that idea going for the example. BE AWARE THAT IN THIS TYPE OF DEVICE, using our example where we flashed the rom to the A side (from TWRP on the B side), that side will not have TWRP. It will have stock recovery.
5- once the rom is flashed reboot system. (wipe cache / dont wipe cache.. I havent noticed a difference with either mindset) It will switch your partitions upon reboot if you don't do anything else in twrp.
So for our example this is what happened:
Wiped data from both partitions of the PH-1, side "a" and side "b"
Went BACK-TO-STOCK on BOTH sides
BOOTED INTO STOCK ROM ON THE SIDE WE WISH TO BE OUR ACTIVE SIDE***DID NOT SET UP GOOGLE OR PIN/FINGERPRINT/PASSCODE****
reboot into bootloader
Used Fastboot to switch partitions and installed TWRP to the INACTIVE side. Boot into twrp.
In TWRP, copied new files to phone storage the flashed new ROM Remember it will install it to the other side which is our ACTIVE side
reboot system.
If this helped at all and got you running great. Rooting is simple from here. This phone was the first device I ever rooted so I took my lumps so I hope I offered some tips that I didn't find or understand fully at first. Happy exploring. Ask away if I can help further.
Click to expand...
Click to collapse
mouraj2 said:
Hello
I have an essential ph1 phone I bought new from a friend
I registered my google account and secured the phone with a fingerprint
While the update request protection orio8.1 agreed to download and update
Complete the phone Download the update The installation process then stuck a logo ,,
Now the phone is working on fastboot mode only
I can not log into recovery
bootloader lock
oem lock
usb debogen lock
I could not flash any picture ....
I hope anyone who can help me help me solve the problem and thank you
Click to expand...
Click to collapse
The computer knows the phone in fastboot mode Shaper that the bootloader is closed and did not accept the opening and did not accept the update There is no way to cancel the update from the fastboot commands to complete the update

KingBeefy said:
Could you rephrase what your question is? I would like to help but can't figure out what you are explaining. I'm assuming you have unlocked the bootloader. I had some problems with this phone at first too. Most of the problems when compared to other phones is that Essential Phone has 2 partitions, like the Pixel. For simplicity, one is sort of the ACTIVE side and the other INACTIVE side. It has some learning. If you are just trying to get up and running try these steps...
1- Wipe data using fastboot command fastboot -w ---- locate the Stock ROM section in Essentials forum here on XDA and get the current STOCK build for your needs. Download it. And flash it in fastboot using the flash-all.bat file. Most will flash the files to both partitions, if it does not use the command in the next step to switch partitions and flash the other side too. This will set your phone back to stock and it should boot nicely. If you wish to root then proceed. BOOT INTO THE STOCK OS EVEN IF YOU ARE STILL GOING TO ROOT THE DEVICE. JUST BOOT UP, THEN REBOOT TO THE BOOTLOADER. DONT SIGN INTO YOUR GOOGLE AND DO NOT SET LOCK OR PASSWORD OR FINGERPRINT YET
2- Follow step one and then reboot into fastboot and use command fastboot set_active other --------- this will do two things. It will switch your partition and also tell you which one it switched to. There is an A side and a B sideFOR THIS EXAMPLE WE WILL PRETEND THAT AFTERYOU SWITCHED YOU ARE ON SIDE B
3- Stay in fastboot and flash twrp11mata using fastboot command fastboot flash boot exactTWRPfilename.img ------ this will boot you into TWRP on the B side
This next rule is very importantTWRP flashes a zip and a img file different. ZIP ROM FILES FLASH TO THE OPPOSITE PARTITION, IMG FILES flash to the partition that you are currently using. So, if you booted into TWRP on the "b" side and without switching flashed a new kernel or boot image it would install to the same "b" side you are on. If you did the same with a ROM it would install to the 'a" side. So, at some point you have to switch sides from within TWRP in the Reboot tab.
4- Copy your Roms/files to your phones internal memory and then flash using twrp. Flash the ROM not sideload. Flashing is for new roms, sideload is for updates to existing ROM. Back to our example, you booted into TWRP on side b, if you install new rom it will install on side A. Lets keep that idea going for the example. BE AWARE THAT IN THIS TYPE OF DEVICE, using our example where we flashed the rom to the A side (from TWRP on the B side), that side will not have TWRP. It will have stock recovery.
5- once the rom is flashed reboot system. (wipe cache / dont wipe cache.. I havent noticed a difference with either mindset) It will switch your partitions upon reboot if you don't do anything else in twrp.
So for our example this is what happened:
Wiped data from both partitions of the PH-1, side "a" and side "b"
Went BACK-TO-STOCK on BOTH sides
BOOTED INTO STOCK ROM ON THE SIDE WE WISH TO BE OUR ACTIVE SIDE***DID NOT SET UP GOOGLE OR PIN/FINGERPRINT/PASSCODE****
reboot into bootloader
Used Fastboot to switch partitions and installed TWRP to the INACTIVE side. Boot into twrp.
In TWRP, copied new files to phone storage the flashed new ROM Remember it will install it to the other side which is our ACTIVE side
reboot system.
If this helped at all and got you running great. Rooting is simple from here. This phone was the first device I ever rooted so I took my lumps so I hope I offered some tips that I didn't find or understand fully at first. Happy exploring. Ask away if I can help further.
Click to expand...
Click to collapse
Hi King,
I am hoping you can help. I never enabled USB debugging. I did wipe the phone but cannot run any ADB commands, only fastboot commands. The phone will not run recovery and I'm really hoping I can get some help to recover this phone. Essential won't help as the phone is off warranty. I was able to unlock the phone but cannot seem to load anything via Fastboot as the phone won't allow loading due to the USB debugging not being enabled. I was hoping for a way to enable it via Fastboot.
Thanks,
Grant

mouraj2 said:
Hello
I have an essential ph1 phone I bought new from a friend
I registered my google account and secured the phone with a fingerprint
While the update request protection orio8.1 agreed to download and update
Complete the phone Download the update The installation process then stuck a logo ,,
Now the phone is working on fastboot mode only
I can not log into recovery
bootloader lock
oem lock
usb debogen lock
I could not flash any picture ....
I hope anyone who can help me help me solve the problem and thank you
Click to expand...
Click to collapse
I have the same problem here,
My phone is stuck on Essential log when I turned it on,
I can access Bootloader normally but the device is locked so I cant flash it,
Recovery is corrupted, when I try to star it, it shows only the the Essential log and freeze so I can not format or wipe or sideload.
OEM Locked and unchecked
USB Debugging is unchecked
and I can't flash anything,
Did you managed to unlock it through Fastboot command or any other way ?
I wish I can just login to the recovery or unlock it so I can flash it clean,
Kindly help me if you found a way out
Thank you

You are both out of luck. I don't know what everyone is thinking by telling you to do all the normal instructions to fix your phones when you plainly say that you get a CORRUPT red warning a boot and at recovery, and you never OEM unlocked your phones to be able to unlock the boot-loader. So I am sorry to tell you this but your phones are garbage. I have the same red corrupt warning at boot and recovery just goes to boot-loader, but I DID unlock my boot-loader, so I am going to erase my critical partitions and flash them on both slots to see if that works. Funny thing, I finally figured out a way to boot into the OS... I just boot and when the red corrupt warning comes on I press the volume buttons randomly and hold them down randomly and at some odd point it just boots up. So weird, it is definitely a bad flash that didn't stick or the image was corrupt, or maybe the image was modded incorrectly. I flashed a patched boot image and that's when the red corrupt warning came up. I am not saying it was the patched boot file, I might have flashed it wrong, like over an already patched boot, which I read is a no no. But now I wonder....should I erase the critical partitions and flashall? And does that "erase" command wipe the partition's data or the partition as a whole??? Or, should I try formatting the critical partitions instead? Anyone know what the correct course of action is here? Or even just what is the BEST one is??? I was lucky to get into the OS because I lost USB debug when I flashed the latest security update trying to fix this. Also, I burned through a data cable somehow too. SMH. OK, Please advise me as to what I should do so that I don't Essentially end up using this phone as part of my chimney. TYIA!
---------- Post added at 03:40 PM ---------- Previous post was at 03:35 PM ----------
A.I.M said:
I have the same problem here,
My phone is stuck on Essential log when I turned it on,
I can access Bootloader normally but the device is locked so I cant flash it,
Recovery is corrupted, when I try to star it, it shows only the the Essential log and freeze so I can not format or wipe or sideload.
OEM Locked and unchecked
USB Debugging is unchecked
and I can't flash anything,
Did you managed to unlock it through Fastboot command or any other way ?
I wish I can just login to the recovery or unlock it so I can flash it clean,
Kindly help me if you found a way out
Thank you
Click to expand...
Click to collapse
OEM locked is unchecked and you have no access to it? Thats a brick. Unless you can get an ADB connection while your phone bootloops.
SOMEtimes I could get in before my phone booted but highly unlikely.

LineageOS starts booting, but then phone goes to Qualcomm Crash Dump Mode

Hello,
I am new to phone rooting/modding, this is my first time trying to install a custom ROM (lineageOS) to my OnePlus 8 Pro.
First, I followed this guide for rooting, installing TWRP and then Magisk. The only different thing that I did was, when flashing TWRP, not usingfastboot flash recovery twrp-image-filename.img, but fastboot flash recovery_a/b twrp-image-filename.img, because I read that the former may lead to a boot loop.
Everything worked. Then I proceeded to Install LineageOS on instantnoodlep, where it said I needed to upgrade my stock OS to Oxygen 11/Android 11 first (it came with O10/A10). I did that successfully.
However, it turned out that O11/A11 had overwritten TWRP with the stock recovery. So I flashed TWRP again. This too was successful.
I decided not to install the LineageOS with the LineageOS recovery, as in the official guide, but through TWRP. I copied the LineageOS image to phone memory, booted to TWRP, selected Wipe and did a Factory Reset - Wipes Data, Cache and Dalvik (DID NOT choose Advanced Wipe, probably this was the problem?)
After the reset, I selected the LineageOS ZIP file and installed it.
After booting to system, LineageOS starts loading, but after 4-5 mins I see
QUALCOMM CrashDump Mode
--------------------------------------------------
Panic requested on external modem boot failure
mdm_force_reset
Any help for getting out of this?
It will be MUCH appreciated.

Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.

Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.

MaybeDontAsk said:
Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.
Click to expand...
Click to collapse
The unlock command would be:
Code:
fastboot flashing unlock

Thanks for the suggestions, I will try them when I get to my home PC, I'm at work now.
In the meantime: can someone explain to me what is the exact procedure for installing LineageOS with the latest TWRP image? More specifically, which options in "Advanced Wipe" should be checked, because in all the tutorials I found they were using old versions of TWRP which did not include the "system" option. Mine had it, so I decided not to use Advanced Wipe at all and use the default wipe options (this is also what they did in one of the tutorials). Could this be the cause for the crash dump error?
Also, I am kind of reluctant to re-lock the bootloader and go back to stock OxygenOS. I still have access to the (LineageOS) recovery mode (it overwrote TWRP). Can I try doing something from there, like maybe overwriting it with TWRP again, then wiping everything (the right way) and installing LineageOS again?

Well when ever I get a Qualcomm crash dump error I always like to go back to stock and re do everything fresh just in case something else goes wrong but if you just don't wanna go back to stock you can do this:
If you wanna overwrite lineage os recovery you can reboot into the bootloader, and just do fastboot flash recovery (drag and drop twrp image here)
So it will be something like:
Code:
fastboot flash recovery C:\Users\YourUsername\Desktop\(recovery name).img
Or if you have the twrp image in the same place at platform-tools you can do:
Code:
fastboot flash recovery (recovery.img)
Or a one time twrp boot:
Code:
fastboot boot C:\Users\YourUsername\Desktop\(recovery name).img
Or:
Code:
fastboot boot (recovery name).img
But like I said it's probably better to re-lock the bootloader to start fresh then you can unlock it again and do anything else. Good Luck.
Anyways in TWRP Navigate To:
Wipe>Advanced Wipe> Dalvik/Cache>Data>swipe to wipe
Go back to TWRP home
Advanced>Adb Sideload
Now in PC cmd do:
Code:
adb sideload (drag and drop lineage os zip here)
Hit Enter And Wait Until It Finishes Flashing
Now For The Google Apps (GAPPS):
Download Nik GAPP From:
NikGApps - Custom Google Apps Package!
NikGapps Website
nikgapps.com
Select "Download"
Then look through all packages and read what each one contains, I would go with either core or basic. But you may need another apps so just read and choose.
Once you choose, click "download now"
Navigate To Folder
Releases>NikGAPPS R if lineage is 18.1(Android 11)>Latest Version>then choose from here and download.
Back to TWRP
If the download for gapps Finished:
Navigate to:
Advanced>adb sideload
Back On CMD:
Flash Gapps:
Code:
adb sideload (drag and drop NikGAPPS zip)
once it finishes:
On TWRP go back to home menu and navigate to:
Wipe>Format Data>Type "yes">Hit Enter>Go Back To TWRP Menu>Reboot>System if it says "no rom is installed" just swipe to confirm reboot, Lineage OS Is Actually Already Flashed. Good Luck!
I know this is long but it's really not lol.

@MaybeDontAsk
Thanks a lot! I will try again via TWRP first. I don't want to re-lock the bootloader just yet, because I fear something may go wrong in the process and I may end up with a bricked phone AND a locked bootloader, and that will really be the worst scenario, from what I've read in forums.
As for the GAPPS part - I don't plan to install them. Just a LineageOS image will be fine.

Alright well hope everything goes well and yeah I also feared I may end up bricking my device with the msm download tool but I've already done it multiple times.
It has fixed a lot of issues for me wether it is that the device is booting straight into recovery or fastboot or that it's not even booting up!

Just something about TWRP: when I tried just booting to it, the phone froze on the "Fastboot Mode" splash screen and stopped there. So I had to use the flash option.
Also, about flashing: I should use
Code:
fastboot flash recovery (recovery.img)
and not
Code:
fastboot flash recovery_a (recovery.img)
fastboot flash recovery_b (recovery.img)
right?
Just double checking to make sure.

Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?

freeride01 said:
Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
View attachment 5543241
I forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?
Click to expand...
Click to collapse
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.

MaybeDontAsk said:
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.
Click to expand...
Click to collapse
Alright.
I gotta find a Windows PC though, I am on Linux/Fedora.
My OxygenOS before the wipe was 11.0.10.10.IN11BA, I guess from the list I should download "OOS 11.0.4.4", because its the latest.
I'll post again when there is some progress.

MaybeDontAsk said:
Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.
Click to expand...
Click to collapse
OK, I got my hands on a Windows 10 PC. I downloaded and extracted the MSM tool and watched the video you linked.
There is no Win7 version of the .exe file, so I guess I'll use the "normal" one anyway.

Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?

freeride01 said:
Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?
Click to expand...
Click to collapse
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.

MaybeDontAsk said:
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.
Click to expand...
Click to collapse
Hi again,
I did the whole process again and when I did adb sideload I got this:
Code:
[[email protected] phone root]$ adb sideload lineage-18.1-20220214-nightly-instantnoodlep-signed.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Now what? There's a slide in TWRP that says "Swipe to start sideload", should I swipe it?
EDIT: Maybe Ishould use adb install as described here?

No, you need to reinstall the adb interface drivers, search up on how to do it on Linux.
Tht link you put is for installing apk directly from adb and not roms.

But adb seems to work, adb devices returns my phone ID.

It says something like "(Device ID) | Sideload?
If yes then reboot both the laptop/pc and phone.

Code:
[[email protected] phone_root]$ adb devices
List of devices attached
19356f32 recovery
(changed some digits in serial no. for privacy)

1050F Bricked - Will not start in anything but DNX mode. Help!

Hi all,
I made a series of mistakes that got me to where I am now. All I intended on doing was repairing my dad's tablet which was running atrociously slowly. I tried to follow some steps, but improvised as I was getting errors and ended up making things a lot worse...
Now tuning on the tablet will directly go to a command line interface with a long series of errors and these are the last 2 lines:
Rich (BB code):
blkD :HardDisk - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0) /HD(14,GPT,80868086-8086-8086-8086-000000000008,0x646828,0x16D47D8)
blkE :BlockDevice - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0)
Press ESC in 1 seconds to skip startup.nsh, any other key to continue.
Shell> _
In this state it cannot be interacted with and won't be detected by my PC over USB.
This happens for normal, recovery and bootloader modes. The only mode that I can access is DNX mode but attempting to boot droidboot will result in the same command line UI described above, including when trying to restore the BIOS using the PC executable (which I assume needs to enter fastboot mode, which it can't do...).
What can I do now? Any way to get anything working in the above screen or through DNX?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp.img when all I have access to on the tablet is DNX mode?
Detailed history below...:
HISTORY
1)
The tablet is a Lenovo Yoga Tab 2 1050F. It was running very slowly to the point where my dad just didn't bother to use it. I thought it would be wise to factory reset it as a first step. There is no option to do so within the Lenovo skin of Android so I started by going into recovery mode and performed a factory reset from there.
After it rebooted, the Android UI would loop back to the language selection after connecting to a WiFi network and I would get "Unfortunately Google Play Services has stopped." error message. It would just loop through the Language Selection > Connect to WiFi network pages over and over.
2)
Having installed CM on my old S3 back in the day, I thought I could go about the same process and flash a gapps ZIP file in recovery mode. That didn't work, I got an error because the zip was unsigned.
I thought I could install TWRP to flash unsigned zips, reinstall Gapps and get the tablet passed the Android UI loop.
3)
I followed this guide on XDA to install an unofficial TWRP (which involved unlocking the bootloader). It didn't work because I couldn't flash over ADB (because the tablet couldn't allow Developer Mode since it was stuck in the Android UI loop). So I flashed as many files as I could in fastboot.
I eventually flashed the TWRP recovery.img but that didn't work : when turning on to Recovery mode it would just go back to the bootloader screen.
4)
I thought I must have screwed up something up so I tried to restore the BIOS using an executable I found but I realized the tablet was already upgraded to Lollipop and the only BIOS restoration exe was for Kitkat. Sure enough it got even worse and I could no longer boot Android.
5)
I still had bootloader and fastboot though so I followed a guide to restore the tablet to the original OS (which ironically I already downloaded before trying to get TWRP but forgot about and didn't unpack). I set up Intel Platform Tools but the flash process didn't work because it went to droidboot and then lost USB connection. On the Intel program it would just stay stuck at 20% Wiping ESP. It would time out twice and then give me a final error message.
6)
So I thought to explore the flash.xml file provided to see if I could do the steps manually. I knew it was stuck at wipe ESP because in droidboot it couldn't get commands from PC. So I went into fastboot and wiped ESP manually myself! Little did I know how foolish this was to do because I was simply unable to flash the provided ESP.img again. Following this I lost access to the bootloader.
7)
I found a guide to restore a bricked 1050F here on XDA but it needs droidboot which now goes to the command line UI described at the top of this post. When attempting to restore the kitkat BIOS again, droidboot is also needed which results in the same cmd UI.
8)
Which leads me to where I am now which is that the tablet doesn't boot to: normal, recovery, bootloader/fastboot or droidboot. Which is why I am now asking for help. What can I do?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp when all I can get access to is DNX mode?
Thanks for reading this far and if you have any more ideas, please let me know, thanks in advance.

Any help please?

Hi, any help please?

Hi all, would anyone like to chime in?

It would seem an update (I think from 2020)has been floating around the net for a while.
I recently decided to revisit my 1050f after I found a replacement screen to change my original one as it was cracked.
At first everything worked Okay but then the tablet decided to do this update,which has totally messed my pad up.
As I have all the old files on my computer from years back,I thought go the the re-install of everything,no matter what I do from Command lines to using "bios restore tool " and intel lite tool with both the original "kitkat" roms and modified roms,nothing will make my pad work again.
I think Lenovo have deliberately released software to break our pads.
I know all my files are good as I have reloaded them before when I was not happy with some things I did.