Unlock bootloader without PC in zenfone 2. - ZenFone 2 General

I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
1. Update your software image to V2.20.40.139 or latest version
2. Download Unlock Device App: Unlock boot loader from this link dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UnlockApp_ze551ml_20150723.apk
3.Install the app on device. Open it and follow the instructions.
(It will take couple of minutes and reboots)
You will get a white Asus screen instead of black that mean you successfully unlocked your bootloader.

What's the point, i mean it was known.

Be ware, using official bootloader unlocker will void your warranty!

Related

[Q] Htc Evo 4G Autoroot 2.3 having trouble

Hey guys, I was trying to root my phone, just so I can overclock it a bit so it goes faster ;_;
and now its stuck at the red triangle and not sure what to do ..... this is what the log thing says...
Starting ADB server...
** daemon not running. starting it now on port 5037 *
* daemon started successfully *
Checking MTD configuration...
Phone uses the old block size.
Firmware version "3.70.651.1"
batter is at 100 percent.
The ADB Shell does not have root permissions. Installing exploit...
Rooting...
Looking for Root...
Got Root!
Checking for needed files...
Pushing res\flash_image to /data/local/flash)image...
Pushing res\mtd-eng.img to /sdcard/mtd-eng.img...
pushing res\URFSOFF.zip to /sdcard/URFSOFF.zip...
Pushing res\URFSON.zip to /sdcard/URFSOn.zip...
Flashing misc partition...
Rebooting in to bootloader...
Verifying bootloader status...
Bootloader shows Firmware version "1.17.651.1"
hbootpreupdate set at "11"
Verified the phone has the older MTD setup with hBoot version "2.10.0001"
Verified NAND is locked.
Setting RUU mode...
*
* Flashing Firmware...
*
* It is very important that you do not interrupt this while flashing.
* Unplugging or turning the phone off while it is flashing can easily brick
* your phone.
Rebooting...
Waiting for the phone...
Phone is finalizing the flash, waiting...
Waiting for the phone...
** daemon still not runninerror: cannot connect to daemon
** daemon still not runninerror: cannot connect to daemon
** daemon still not runninerror: cannot connect to daemon
** daemon still not runninerror: cannot connect to daemon
Found the pohone connected as "device"
Giving the phone time to configure itself...
Rebooting into recovery...
Waiting for the phone...
** daemon still not runninerror: cannot connect to daemon
** daemon still not runninerror: cannot connect to daemon
** daemon still not runninerror: cannot connect to daemon
** daemon still not runninerror: cannot connect to daemon
** daemon still not runninerror: cannot connect to daemon
Should I turn the phone off and try turning it on? I don't want to risk breaking it, if its still "flashing" its been stuck at the red triangle for about 10-15 minutes now...
It sounds like maybe the recovery didn't flash correctly. Pull the battery, it wont brick it. Then boot to the bootloader, and see if it is s on or s off. If its s off, we will try flashing a recovery. Give me a minute to get on my laptop, and ill post a recovery for ya.
Sent from my PC36100 using XDA App
Edit: I attatched a PC36IMG of Amon Ra recovery V2.3. Make sure it's just named PC36IMG, and put it on the main directory of your sd card. Boot to the bootloader, and after a few seconds it'll scan and ask you to update. Press Vol up to select yes. After that completes, try entering recovery and see if it worked. (this is all presuming that you are S off)
k2buckley said:
It sounds like maybe the recovery didn't flash correctly. Pull the battery, it wont brick it. Then boot to the bootloader, and see if it is s on or s off. If its s off, we will try flashing a recovery. Give me a minute to get on my laptop, and ill post a recovery for ya.
Sent from my PC36100 using XDA App
Edit: I attatched a PC36IMG of Amon Ra recovery V2.3. Make sure it's just named PC36IMG, and put it on the main directory of your sd card. Boot to the bootloader, and after a few seconds it'll scan and ask you to update. Press Vol up to select yes. After that completes, try entering recovery and see if it worked. (this is all presuming that you are S off)
Click to expand...
Click to collapse
I checked the bootloader and it says that S is still on. @[email protected] I'm gonna try putting your file in the SD card, and try autoroot 2.3 again, or should I use 2.2 ?
no use the newest, there were no code updates after 2 (i think) just updates to the files. try again....
edit: ya i realized where the script went wrong. you got eng build flashed fine, but the bootfrompc recovery never was pushed. just run the script again. if you get stuck at the same place again, just pull the usb and plug back in.
So weird now.... whenever I try running Autoroot 2.3 it says it must be syn... but when I syn it says the following:
=================================
Starting ADB server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Checking MTD configuration...
Phone uses the old block size.
Firmware version '1.17.651.1'
Battery is at 82 percent.
Got Root!
Checking for needed files...
ERROR Could not access the SD card!
Make sure your phone is set to charge only and your phone is reading the SD card
properly.
Press any key to exit...
====================================
However, if I try running it in Charge Only mode... it says this....
================
Starting ADB server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
The phone could not be found or was not ready. ADB and Fastboot report it as
'disconnected' instead of the expected 'device'. Make sure ADB debugging is
turned on, the phone is in the correct mode and that you are using HTC's Evo
drivers that come with HTC Sync.
Press any key to exit...
====================================
SO CONFUSING @[email protected]
so do what it says... mount in charge only, make sure usb debugging is on (it might have turned off on the eng build, just double check) and plug in nice and snug. i'm sure xhausx will have u all fixed up by tomorrow if i dont first.
Now it says it can't read the SD card in charge mode... omg lol, ima reboot the phone. maybe that will work.
soooo much work, all I wanted to do was overclock the CPU a bit, THATS ALL ;_;
so much easier on the huwai ascend xD
Well... I'm new on this forums, but can provide a small donation if some one can help me root my phone so I can overclock it I already have SetCPU purchased.
I'm kinda noob, so be patient >.<, thanks!
use unrevoked lol.
I dont care how my phone gets rooted, I just want to overclock it, would prefer the easiest most noobiest way of doing it, if you dont mind ^^;;
My friend is good at this stuff, but his away on vacation for the next 2 weeks, what terrible timing :\
unrevoked, I think I tried that? Not sure... could you provide a link? Thanks!!
I was about to say...
Btw you can get much better (and I'm talking like 50% increase) without overclocking by flashing the newest cm7 nightly once it is released...
mic.mayorga said:
use unrevoked lol.
Click to expand...
Click to collapse
Sent from my PC36100
I don't know if it helps but maybe you have an intermittent flaky cable? Only other suggestion that I did, but highly doubt it actually helped me, was literally don't move yourself. What I mean is if you accidentally moved the cable or phone, there could be a less than one percent chance that the data hiccuped.
I really doubt this but when I flashed mine, I was on my bed with the laptop and phone on the palmrest. I didn't move myself on the bed for fear I might cause the phone to brick. It sounds crazy I know!
I doubt it too but with previous phones, the data cable they give you isn't the greatest quality. Sometimes some cables, the microusb plug doesn't seat and lock itself in the socket. I am grasping at straws and this probably isn't what is wrong but it is just ideas...
Or maybe it is a sign that you shouldn't overclock it.
dkdude36 said:
I was about to say...
Btw you can get much better (and I'm talking like 50% increase) without overclocking by flashing the newest cm7 nightly once it is released...
Sent from my PC36100
Click to expand...
Click to collapse
Okay... so I shouldn't root the phone then? I mainly just want to increase its performance and maybe get rid of some of these useless apps it comes with.
I forgot to mention, I bought the phone 2 days ago, from Sprint all stock, and they updated the phone there, so its got all the latest updates and such, and I noticed that interferes with roots? So does that mean I can't root right now?
The only rooting experience I got is from Huawei Ascend Cricket... was easy as downloading file, clicking perma root, and it was done... xD, now if only evo was that easy :S
No of course you can root and you need to in order to flash a rom. Try unrevoked it is also one click
mashalyssa said:
Okay... so I shouldn't root the phone then? I mainly just want to increase its performance and maybe get rid of some of these useless apps it comes with.
I forgot to mention, I bought the phone 2 days ago, from Sprint all stock, and they updated the phone there, so its got all the latest updates and such, and I noticed that interferes with roots? So does that mean I can't root right now?
The only rooting experience I got is from Huawei Ascend Cricket... was easy as downloading file, clicking perma root, and it was done... xD, now if only evo was that easy :S
Click to expand...
Click to collapse
Sent from my PC36100
mic.mayorga said:
use unrevoked lol.
Click to expand...
Click to collapse
Agreed...its the only way I tell people to use
The sd card thing is just a bug in this version, it doesn't recognize the card if you are running the old Eclair software. You can get around it by updating back to froyo or by starting it while the phone is in fastboot or the recovery.
Aha so here is xgausx... I was wondering when you would get here man! So ya listen to him its his auto root script...
xHausx said:
The sd card thing is just a bug in this version, it doesn't recognize the card if you are running the old Eclair software. You can get around it by updating back to froyo or by starting it while the phone is in fastboot or the recovery.
Click to expand...
Click to collapse
Sent from my PC36100
xHausx said:
The sd card thing is just a bug in this version, it doesn't recognize the card if you are running the old Eclair software. You can get around it by updating back to froyo or by starting it while the phone is in fastboot or the recovery.
Click to expand...
Click to collapse
Okay thanks!! I will try it in fastboot, hope it works >_<
Some have also mentioned it working better using htc sync from Sprint instead of HTC's website, may be worth a try.
http://shop2.sprint.com/en/software_downloads/pda_smartphone/htc_evo.shtml
xHausx said:
Some have also mentioned it working better using htc sync from Sprint instead of HTC's website, may be worth a try.
http://shop2.sprint.com/en/software_downloads/pda_smartphone/htc_evo.shtml
Click to expand...
Click to collapse
I got this.
Starting ADB server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Searching for phone...
Found the phone connected as 'recovery'
Setting up a temporary Recovery...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Pushing amon_ra_1.8-mod to /...
Checking MTD configuration...
Phone uses the old block size.
Making NANDroid backup, this will take several minutes. Please wait...
NANDroid finished, dumping recovery log...
Setting auto-update command to flash Unrevoked Forever...
Rebooting the recovery...
Waiting for the phone...
Phone is flashing Unrevoked Forever, you should see a circular icon with a green
arrow pointing down for a moment and then it will restart a couple of times...
Phone exited Recovery mode.
Waiting for the phone...
Rebooting into the bootloader...
Waiting for the phone...
Verifying bootloader status...
Bootloader shows Firmware Version '1.17.651.1'
Your NAND is still locked! Rooting Failed.
Rebooting...
Please post your autorootlog.txt file to the XDA thread or send it to me
directly at [email protected]
If your phone is not bootable you can restore it by flashing the RUU through
Fastboot. To get there turn your phone on while holding Vol. Down *NOT VOL UP*,
then push Power to select FASTBOOT. You will see "FASTBOOT USB" highlighted
with red when it is ready.
It is very important that your battery does not die while restoring. If needed
your phone will always be able to charge when turned off.
Press any key to exit...
mashalyssa said:
I got this.
Starting ADB server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Searching for phone...
Found the phone connected as 'recovery'
Setting up a temporary Recovery...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Pushing amon_ra_1.8-mod to /...
Checking MTD configuration...
Phone uses the old block size.
Making NANDroid backup, this will take several minutes. Please wait...
NANDroid finished, dumping recovery log...
Setting auto-update command to flash Unrevoked Forever...
Rebooting the recovery...
Waiting for the phone...
Phone is flashing Unrevoked Forever, you should see a circular icon with a green
arrow pointing down for a moment and then it will restart a couple of times...
Phone exited Recovery mode.
Waiting for the phone...
Rebooting into the bootloader...
Waiting for the phone...
Verifying bootloader status...
Bootloader shows Firmware Version '1.17.651.1'
Your NAND is still locked! Rooting Failed.
Rebooting...
Please post your autorootlog.txt file to the XDA thread or send it to me
directly at [email protected]
If your phone is not bootable you can restore it by flashing the RUU through
Fastboot. To get there turn your phone on while holding Vol. Down *NOT VOL UP*,
then push Power to select FASTBOOT. You will see "FASTBOOT USB" highlighted
with red when it is ready.
It is very important that your battery does not die while restoring. If needed
your phone will always be able to charge when turned off.
Press any key to exit...
Click to expand...
Click to collapse
thats kind of weird, can you go into the recovery and use the StartRecovery script to bring up AmonRA on your phone? Once it comes up you will be able to mount the sd card as a disk drive by using the USB MS mode, then look for a file called soff.txt on it. That should show what happened to cause unrevoked forever to fail. Can you also double check whether or not it shows s-on or s-off in your bootloader?

[TUT]|Unlocking Bootloaders|Rooting|Flashing Kernels|Unbricking|via Flashtools

{
"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"
}
Code:
> Disclaimer <
#include
/* This tutorial it's for Xperia X8/W8 user with 11W29 and below only
* I don't own a Xperia X8 anymore
* Do It with your own risk
* This may not be the complete or the best way of doing it
*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this tutorial
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
I will be covering on the sub-topic of :
☞ ϟUnlocking Bootloader
☞ ϟRooting
☞ ϟFlashing Kernels
☞ ϟUnbricking
Why unlock bootloader ?
*Allowing custom kernel to be loaded for better performance and newer android version goodies
Stock Kernel are from Android Eclair therefore it's dusty and old
It's risky ?
* Yes very risky if you don't follow method and precaution properly with resulting into Hard Brick
How can i unlock my bootloaders?
WARNING WARNING WARNING MAKE SURE YOU HAVE ALREADY READ ON THIS POST BEFORE PROCEEDING
You must have these installed :
SEUS PC COMPANION
Latest Version Of Flashtool (Grab it from http://androxyde.github.com/ )
Gordon Driver (Already inside the flashtool package)
You phone enabled with USB Debugging (enable debugging > settings > application > development )
Once Again Do Check The manufacturing date is at the back sticker on the phone for 11W29 and below (Any trial to unlock above 11W29 will resulting into a permanent brick)
☞ ϟ 1 Steps To Unlock (Via Flashtool)
Make sure you devices is fully charge and all the required program and drivers are installed
Connect Your Phone to pc via usb and let the Flashtool to detect your device.
Once detect head over to "Plugins" tabs > select your device
When the Flashtool start unlocking it will have to restart the device automatically
If the program required you to disconnect the usb and reconnect (Follow all the steps)
On the final boot reconnect your phone to the pc and it will finalize unlocking
You're now unlocked your bootloaders
Why Rooting my phone?
I explained over my HTC One X thread here
☞ ϟ 2 Steps to root (Via Flashtool)
Make sure you have enabled USB Debugging for this procedure
Connect your phone via usb and wait for flashtool to detect
Once detected head over to "Advanced" tab and choose root
You may select any of the both rooting method.
Follow your the instruction
Once complete disconnect your phone and see if there's superuser and busybox installed
If there's then you are rooted!
☞ ϟ 3 Steps To Flash Kernel (Only for those unlocked their kernel follow ☞ ϟ 1)
Make sure you have enabled USB Debugging for this procedure
Connect your phone via usb and wait for flashtool to detect
Once detected press the [ϟ] icon & select flashmode
Select the kernel for the version of android of you're about to flash
Turn off your phone and reconnect it while holding the back button and release it when the flashtool detect
Disconnect the phone and reboot after flashing completed
☞ ϟ 4 Unbricking
How to classified soft bricked?
-Bootlooping (Staying at bootanimation)
-Connect a usb and having green LED light
-Connect a usb and having red LED light (Maybe still on luck if stay on)
This can be fixed by flashing the original 2.1 firmware the same method flashing kernel ☞ ϟ 3
How to classified Hard bricked?
-Doesn't boot up
-Led doesn't light up
-Doesn't charge
I have done this far and what can i do next?
Well you may consider start flashing rom into your device/tweak and share your creation
Do Read on
[TUT]Make Your Own Vanilla IceCream Rom [Custom Rom][Lightweight,Smooth&cool]
[HOW-TO]Report Problem and Bug [Proper Way]
Together we fight for less unwanted spam and provide quality rom's
Reserved #!
Awesome initiative, Zack.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
:what: i thought the thread was for |Unlocking Bootloaders|Rooting|Flashing Kernels|Unbricking|via Flashtools
correct that part?
thanks for the post though.. will help some people
still left.. the rom thing...
CnC-ROCK said:
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
:what: i thought the thread was for |Unlocking Bootloaders|Rooting|Flashing Kernels|Unbricking|via Flashtools
correct that part?
thanks for the post though.. will help some people
Click to expand...
Click to collapse
Corrected.
This post need minor tweaks and improvement from time to time :fingers-crossed:
sgt. meow said:
Awesome initiative, Zack.
Click to expand...
Click to collapse
Good work..
Good try. I hope that the thread will be improved as the time goes.
I have some corrections and some comments.
Ill start with the comments, I think your starting is too much but its fun, the rooting part should be before the unlocking part and you maybe need to add more,but I'm not worry about this as it is a new thread
Lest correct some things
The manufacturing date is at the back sticker on the phone and not on the battery,that's very important because the date on the battery can tell for example 11w26 and on the phone 11w33 and this virtual x8 will have hard brick....
When you go for unlocking another important factor is the simlock,I know you have link a thread about the danger but you maybe want to add it.
I had found another thing but I just can't remember it...lol..
Sent from my X8 using xda premium
Great tutorial!
Great tutorial.. I unlocked my sister's W8! Thank you..
I rooted the phone, yet forgot to unlock the bootloader. Is following the method described viable to unlock the bootloader, or will it somehow brick/be detrimental to the phone.
Being a sticky I think this thread should be correct as much as possible.
Hence I request the OP to implement the corrections pointed out by stamatis to this thread asap.
Guess I bricked my phone. When I try and switch it on, it vibrates and then gets stuck at the Sony Ericsson text. Can someone please help ASAP? I tried the method of reflashing it to its original firmware but it's not working. I don't know why.
coolredwine said:
Guess I bricked my phone. When I try and switch it on, it vibrates and then gets stuck at the Sony Ericsson text. Can someone please help ASAP? I tried the method of reflashing it to its original firmware but it's not working. I don't know why.
Click to expand...
Click to collapse
Don't worry you can fix it, follow this guide.
Hey i can't found add device in plugin tabs?
I try to unlock my boot loader, but my phone had locked by e-mail and pattern. Now it ask me to answer the question but i forget all.
Can i still unlock it.
And anybody can help me????
:crying::crying::crying::crying:
masruri3 said:
Hey i can't found add device in plugin tabs?
I try to unlock my boot loader, but my phone had locked by e-mail and pattern. Now it ask me to answer the question but i forget all.
Can i still unlock it.
And anybody can help me????
:crying::crying::crying::crying:
Click to expand...
Click to collapse
USB debugging on?
If not do a wipe from recovery
:flipoff2: DEVILS NEVER CRY:flipoff2:
thanks
Thank you for this overview!
wI have a question, does unlocking the bootloader also openline the phone?
angel.grin said:
wI have a question, does unlocking the bootloader also openline the phone?
Click to expand...
Click to collapse
Aaaaand what's openline?
see boot animation without rebooting
angel.grin said:
wI have a question, does unlocking the bootloader also openline the phone?
Click to expand...
Click to collapse
If you mean sim unlocking ,no it doesn't.
What if after selecting "Plugins" nothing appears ??
My phone is detected correctly...
18/034/2013 00:34:52 - INFO - Device connected with USB debugging on
18/034/2013 00:34:54 - INFO - Connected device : E15
18/034/2013 00:34:54 - INFO - Installed version of busybox : N/A
18/034/2013 00:34:54 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29 / Build number : 2.1.1.A.0.6
Click to expand...
Click to collapse
Log from s1tool
Welcome to S1 identify tool
TO CONNECT NEXT PHONES
X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING S1_EROM VER "R8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/00BC"
LOADER VERSION: "R4A045"
MODEL (from GDFS): E15i
SOFTWARE VERSION: 1236-9291_2.1.1.A.0.6
CUSTOM VERSION: 1241-4645_R5B
FILESYSTEM VERSION: WORLD-1-8_2.1.1.A.0.6
SERIAL NO: CB511RJ0FK
NOT RECOGNIZED SIMLOCK CERTIFICATE
MAYBE YOU SHOULD UNLOCK PHONE BY SETOOL2 ?
Elapsed:8 secs.
Click to expand...
Click to collapse
Phone was simlock unlocked. It costed about 20€ almost year ago, but i don't know which metod...
Question
Ist there really no possibility to unlock a bootloader with 11W29?

[Q] Unlocking bootloader no warranty dialog

Hey, I'm trying to install Android 5.0 Lollipop, afaik i got the whole package done there is only one thing stuck on my path..
long story short: i dont get the warranty dialogue of bootloader to unlock.
I'm stuck here:
console says:
--> adb reboot bootloader
-->fastboot oem unlock
-->waiting for device
but my mobile phone should get the warranty screen to apply yes/no..
this screen never shows up..

Is this a Bootloader issue or OS problem as to why I have a Galaxy J5 Hard Brick?

Hello All,
I'm a fairly new coder and I recently Hard Bricked my Samsung J5 5.1.1
Is this a Bootloader issue or OS problem as to why I have a Galaxy J5 Hard Brick?
Here's how it happened:
* I rooted the phone
* Wanted to enable more storage (4GB to 14GB) via SD Card
* Gained Super User access and had total file control via an app (I can't remember which one). I then found my way to an area where I could transfer the entire phones files (to include the OS files) to the SD Card - so I did
* The dialog box to restart the phone popped up and I pressed restart
From there the phone has not startup (not able to pwr+home or pwr+home+dwn), can't be found in device manager via USB, and can't be found via adb reboot fastboot (gives a *daemon stated successfully* error: device not found)
Why won't it turn on? Is this a boot loader issue or an OS problem?

OEM locked and unable to boot into OS

Device: Oneplus 8 pro
I have tried to install PixelExperience ROM by following their official WIKI: https://wiki.pixelexperience.org/devices/instantnoodlep/install/
And everything worked perfectly, the phone butted into custom rom without any issues.
Just after doing so, I rebooted the phone to bootloader and proceeded to install custom "avb_custom_key" in order to lock OEM again. After completing this step the phone doesn't boot, it displays yellow message "your device has loaded a different operating system" and just boots into bootloader menu.
I can't unlock OEM again because I can't reach developer menu.
Any ideas or did I just screwed up big time?
For future generations: fixed it using OnePlus Provided unbrick tool https://forum.highonandroid.com/t/how-to-unbrick-oneplus-8-or-8-pro/181
If not for this tool - my device would bein the trash can now. Thank you OnePlus.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com

Categories

Resources