Related
I rooted my Unlocked xl 2 using a method I found online. Used it a couple of days rooted and decided to go back to stock so....
I downloaded the factory image, ran the flash -all.bat and everything was good. Next I went back to my boot loader to re lock it, ran the command , selected yes.
After I hit yes to re lock the boot loader I got the following error. COULD NOT FIND A VALID OPERATING SYSTEM.
Any help would be greatly appreciated.
skullymullins said:
I rooted my Unlocked xl 2 using a method I found online. Used it a couple of days rooted and decided to go back to stock so....
I downloaded the factory image, ran the flash -all.bat and everything was good. Next I went back to my boot loader to re lock it, ran the command , selected yes.
After I hit yes to re lock the boot loader I got the following error. COULD NOT FIND A VALID OPERATING SYSTEM.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
1. fastboot flashing unlock
2. fastboot flashing unlock_critical
3. Reboot the phone if prompted
4. flash firmware using flash-all script again. Read the results and watch for errors that might explain the problem and which partition (a or b) it is flashing to.
5. fastboot --set-active=b (or a. Just set it to whichever partition the script was not flashing to.)
6. flash firmware with flash-all script again to flash the alternate partition
Ok Thanks Ill give that a try..
skullymullins said:
Ok Thanks Ill give that a try..
Click to expand...
Click to collapse
And don't relock until you are 100 percent certain it is ok. I suggest waiting until you get the next update to be sure. Actually I suggest not relocking it but if you insist then wait and make sure the next update goes ok.
TonikJDK said:
And don't relock until you are 100 percent certain it is ok. I suggest waiting until you get the next update to be sure. Actually I suggest not relocking it but if you insist then wait and make sure the next update goes ok.
Click to expand...
Click to collapse
When I tried the command . fastboot --set-active b i got the unknown command error
skullymullins said:
When I tried the command . fastboot --set-active b i got the unknown command error
Click to expand...
Click to collapse
You rooted your phone with a method you found online??? Hmmmm, that's curious. Hope that didn't do any internal damage. Anyways, when your in fastboot mode, and type in "fastboot devices" do you get your device ID number??
TheSt33v said:
1. fastboot flashing unlock
2. fastboot flashing unlock_critical
3. Reboot the phone if prompted
4. flash firmware using flash-all script again. Read the results and watch for errors that might explain the problem and which partition (a or b) it is flashing to.
5. fastboot --set-active b (or a. Just set it to whichever partition the script was not flashing to.)
6. flash firmware with flash-all script again to flash the alternate partition
Click to expand...
Click to collapse
I told one person that was having trouble also to instead of doing step 4 instead download Deuces bootloop kit and allow it to flash your phone for you because I noticed a few people were not flashing in fastboot properly the pixel is different from the prior phones they are used to there are many more Sig files that were not all getting flashed thoroughly causing issues. Deuces kit does it all perfect and it's pretty easy to set up and go
skullymullins said:
When I tried the command . fastboot --set-active b i got the unknown command error
Click to expand...
Click to collapse
Maybe that command works also. I use
Fastboot --set-active=b
skullymullins said:
When I tried the command . fastboot --set-active b i got the unknown command error
Click to expand...
Click to collapse
Sorry, the previous post is right. You need an = in there.
hello guys I had a big problem with my moto g5, they were flashing it by commands and everything was fine, just that by accident I omitted two commands "fastboot erase
fastboot oem fb_mode_clear ", and I put fastboot reboot and the screen went black I tried to do the fastboot but could not detect what I do? I thank you in advance for your answers.
Can your phone still boot into the bootloader?
Exanneon said:
Can your phone still boot into the bootloader?
Click to expand...
Click to collapse
no friend, does not turn on the screen, but if it detects it on my computer and when I put "fastboot devices" it does not detect it
[QUOTE="Exanneon, post: 76364176, member: 7764771"]Can your phone still boot into the bootloader?[/QUOTE]
no friend, does not turn on the screen, but if it detects it on my computer and when I put "fastboot devices" it does not detect it
Plug your device in and install RSD lite, then try to flash stock firmware from there: https://forum.xda-developers.com/showthread.php?t=2637338
.
Exanneon said:
Plug your device in and install RSD lite, then try to flash stock firmware from there: https://forum.xda-developers.com/showthread.php?t=2637338
Click to expand...
Click to collapse
no bro, is that I do not see the fastboot mode this black screen does not give if I highlight brightness or something but if the computer detects it, but not the rsd
I just bricked my phone :crying: :crying:
I wanna get back to the official rom, after trying android P (without make it work).
(the rom is from http://en.miui.com/download-354.html)
But I run the wrong script and take the flash_all_lock.img
And my device is stuck on android 8.1 bootloop (It boot, but i get an animated line loop ...)
Any ideas or tricks before i get it back to warranty ?
Thanks
Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.
BubuXP said:
Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.
Click to expand...
Click to collapse
But since I flashed the official rom with data whipe, I'm unable to go to dev option and enter OEM Unlocking .... And Fastboot respond me that my device is locked
Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem
droopeur said:
Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem
Click to expand...
Click to collapse
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.
BubuXP said:
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
Click to expand...
Click to collapse
In fact, both work, but my phone still stucked at the bootloader (infinite line animation in both cases).
BubuXP said:
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
Click to expand...
Click to collapse
Yes I can enter recovery and I have already tried this, but I always end up with the error:
Code:
E: Unknow volume for path [/sideload/package.zip]
Verifying update package...
Update package verification took 17.3 s (result 0)
Installing update...
E:Error il /sideload/package.zip (Status 1)
Installation aborted
BubuXP said:
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.
Click to expand...
Click to collapse
Yes of course !
But I revert to stock rom with Mi Flash and I click on Flash all and lock, since the telephone should have been "brand new" it should not have any problems but ...
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...
after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool
LUNARIO said:
after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool
Click to expand...
Click to collapse
But since I can't activate OEM I can't unlock bootloader....
try this http://www.xiaomitool.com/ not sure if it works on our phone but maybe can unlock the bootloader so you can use miflash
Have you sideloaded the zip? I think it's better to copy the OTA zip to microSD than ADB sideload.
droopeur said:
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...
Click to expand...
Click to collapse
There should be only two methods for entering EDL:
1- request authorization in en.miui.com forum. Sometimes the admins accept requests to give an account one EDL flash permission (but I don't know if it works with AndroidOne devices).
2- finding the test point in the phone's motherboard.
Hi guys,
i tried to install this twrp but it doesnt work...
so i searched on internet and i found another article, i tried to check the current partition and install in another way
for first:
fastboot getvar current-slot
after i do this
fastboot boot_b recovery.img
and then
fastboot set_active b
so nothing to do....but right now my MI A2 lite not boot.
i try again to check my partition but this time i have no replay.
i have unlocked bootloader but i cant go to recovery and i cant boot!!
someone can help me please?
I HAVE THE SAME PROBLEM
everything you said is completely simillar to mine. Can someone help us? Or did you already fix it? Please help me i need my phone working.
I have same problem fastboot flash but after that, it started to reboot automatically. The phone was automatically turning off and on. I again did a "clean all and lock" via miflash tool but still now, no result!
I can boot into recovery without having any problem. But when I boo to setup country date....etc, it starts its auto rebooting process,
Any help ?
droopeur said:
But since I can't activate OEM I can't unlock bootloader....
Click to expand...
Click to collapse
Same situation here. I am desperate!! Did you solve it?
Isso resolve
steledama said:
Same situation here. I am desperate!! Did you solve it?
Click to expand...
Click to collapse
gadgetsfarm.com/download-mi-a2-lite-fastboot-rom-v9-6-4-download/[/url]
How to unbrick?
Hey guys. I bricked my Mi2 Lite as well. Is there any step by step way to unbrick?
had the same problem, was stuck in the bootloop even after I flashed img with MiFlash! NOTE: MY BOOTLOADER WAS UNLOCKED!!! (LUCKLY I DID NOT TRIED FLASH ALL AND UNLOCK!)
headed to this thread
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
did not work, I get error saying FAILED
but after i used
Code:
fastboot oem edl
I went to MiFlash and used "Clean all" option (again note DON'T use "Clean all and lock"!!!). It took around 5 minutes to flash and my notif. light blinked whole the time. After it say "Success" I was able to normaly boot the phone again
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
Hi, where i can find MI A2 Lite Tool Kit? i open my device and i can put in EDL mode., my computer detect my pone in EDL mode, but i can not know do.
I like bypass FRP, can anybody help me
Thanks.
mr_techno said:
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
Click to expand...
Click to collapse
Hi all,
I also had same problem and I just resolve it.
My phone was in bootloop mode after stock rom flashing...
You don't need apply "fastboot oem edl" !
Just be sure your device is unlocked.
Download first stock rom (V9.6.4.0.ODLMIFF Firmware for Mi A2 Lite). If you flash last ROM, it don't work.
Flash it with XiaoMiFlash tool (don't forget to enable "Clean All") in bottom of the tool.
After reboot, you can apply OTA updates.
Enjoy !
I bought a refurbished Razer phone one from the official razer eBay page, and it's stuck on download mode. I haven't tried flashing anything, I haven't even ever been to the home screen. What can I do to fix this?
Get the Google USB Driver and make sure your Razer phone is installed with these drivers
https://developer.android.com/studio/run/win-usb
Get Android SDK Platform Tools for latest ADB and fastboot tool
https://developer.android.com/studio/releases/platform-tools
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...
It says "Waiting for any device" the problem is that it's not recognized by the computer.
Thank you ! Same problem. This is halp! after first run, works. Question, can I block it now? and how please... fastboot flashashing lock ?
Now I can block back? fastboot flashashing lock ?
ShadowVlican said:
Get the Google USB Driver and make sure your Razer phone is installed with these drivers
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...
Click to expand...
Click to collapse
Hello. Same problem. ( I bought a refurbished Razer phone one from the official razer eBay page, and it's stuck on download mode. I haven't tried flashing anything). It helped me. Now I can block back? fastboot flashashing lock ? Please, sorry my english...
EDIT: The links did not copy paste appropriately. I fixed them now.
These are all posts from various places in this thread:
https://forums.redflagdeals.com/raz...b-1yr-warranty-8gb-64gb-octacore-9-0-2336958/
"Find the driver here:
https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip
unzip the files/folder to a location you will remember
Follow the instructions below, point the windows driver update to the .inf file in that folder then driver will install. Make sure you have the latest Android platform tools, the link is also in the PDF below.
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
open a command prompt from within the Android sdk folder while the phone is still in download mode (phone stays and reboots to download mode through each process below making the process fairly easy)
type: fastboot devices
your phone should show up once drivers are installed correctly
type: fastboot flashing unlock
use the phone vol + - and power to select yes
phone should stay in download mode
type: fastboot flashing unlock_critical
use vol + - and power to select yes
phone should stay in download mode
Download the firmware image below or if you want to try the following command type: fastboot set_active a && fastboot reboot
to see if the phone boots, not sure if all the phones have Android installed. One poster below seems to and also seems to have his bootloader unlocked. This won't be the case for everyone. If phone does not boot continue downloading the firmware to install it
https://s3.amazonaws.com/cheryl-factory-images/cheryl-o-global-6033.zip
unzip all the files and put them in the android sdk folder, from the same command prompt if you're on Windows
type: flash_all.bat
For Mac type: flash_all.sh
Will take a few minutes but firmware will install. These instructions are for RFD members that do not either 1) want the hassle of RMA or 2) take a chance at voiding the warranty (any phone flashing via adb is frowned upon by Razer)"
------------------------------------------------------------
"Yes. Reverse the locking procedure. Put phone back into Download mode (from power off, press and hold Vol up and then plug phone into computer) then issue fastboot commands to lock boatloader starting with critical."
------------------------------------------------------------
"if you have a ryzen pc and getting some error while unlocking... dont plug the phone in at the beginning... type the command when it says [waiting for device] then plug it in ... also dont forget to unlock critical right after"
Now I can block back? fastboot flashashing lock ?
ShadowVlican said:
Get the Google USB Driver and make sure your Razer phone is installed with these drivers
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...
Click to expand...
Click to collapse
it helped, now it is loaded; but after each reboot it writes, the phone is unlocked and that it is unsafe. can it be blocked back, is it safe that everything continues to work? please write what commands to enter?
365Thanks said:
it helped, now it is loaded; but after each reboot it writes, the phone is unlocked and that it is unsafe. can it be blocked back, is it safe that everything continues to work? please write what commands to enter?
Click to expand...
Click to collapse
Repeat the unlock commands using lock instead of unlock but in reverse order so:
fastboot flashing lock_critical
fastboot flashing lock
again you must place the phone in download mode (powered off...hold volume down key down...plug in) between each command and follow the onscreen instructions.
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...[/QUOTE]
flopticalcube said:
Repeat the unlock commands using lock instead of unlock but in reverse order so:
fastboot flashing lock_critical
fastboot flashing lock
again you must place the phone in download mode (powered off...hold volume down key down...plug in) between each command and follow the onscreen instructions.
Click to expand...
Click to collapse
after each command you need to disconnect from the computer? fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
I used to enter these commands , the instructions were only after 1
I did not turn off the phone and the question on the screen was only after the first command. I probably entered only 1 command <if it was necessary to disconnect phone? ... thank you for help.
Sudo.
If ur using linux - run it with sudo. always run fastboot with sudo
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot set_active a
error: Device does not support slots
On the screen I get: your device is corrupted and cannot be trusted and cannot reboot
Simply disable Developer options and the any settings you altered there will revert to baseline.
If that doesn't get it then it's not Developer options...
blackhawk said:
Simply disable Developer options and the any settings you altered there will revert to baseline.
If that doesn't get it then it's not Developer options...
Click to expand...
Click to collapse
Thanks for answering
The device may boot into a bootloader or an error on the screen
EranG90 said:
Thanks for answering
The device may boot into a bootloader or an error on the screen
Click to expand...
Click to collapse
You locked the bootloader while running modified software.
Unlock it again
Code:
fastboot oem unlock
craznazn said:
You locked the bootloader while running modified software.
Unlock it again
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Thank you
I have now done that and the screens are in the same condition as in the pictures
It is good? Should I keep waiting? (I don't know really what to do, I am new at this. I don't know even if the device got the commend from the pc)
We can't really help you until you confirm what you did to get it in this state in the first place?
Did you install the OxygenOS 12 Developer Preview?
Did you try rooting by replacing the stock boot.img?
Please confirm what caused this in the first place as changing something in the developer settings alone would not cause this.
djsubterrain said:
We can't really help you until you confirm what you did to get it in this state in the first place?
Did you install the OxygenOS 12 Developer Preview?
Did you try rooting by replacing the stock boot.img?
Please confirm what caused this in the first place as changing something in the developer settings alone would not cause this.
Click to expand...
Click to collapse
Sorry like I said before I am new at this
I have change somting in the DSU option. I think this was the Acronyms
I believe I chosed GSI+"Somting"
then the device rebbot with qualcomm screen and then the error apper
EranG90 said:
Sorry like I said before I am new at this
I have change somting in the DSU option. I think this was the Acronyms
I believe I chosed GSI+"Somting"
then the device rebbot with qualcomm screen and then the error apper
Click to expand...
Click to collapse
OK, If you used DSU to try out the Android 12 Developer Preview your bootloader needs to be unlocked, try running :
fastboot oem unlock
Bear in mind it will wipe the phone though, then reboot back into the Android 11 rom, set it up and THEN try DSU.
You need to have previously allowed bootloader unlocking in your developer options (see below)
djsubterrain said:
OK, If you used DSU to try out the Android 12 Developer Preview your bootloader needs to be unlocked, try running :
fastboot oem unlock
Bear in mind it will wipe the phone though, then reboot back into the Android 11 rom, set it up and THEN try DSU.
Click to expand...
Click to collapse
Thank you
I have run this command and waited 40 min with thoose screen and stop becuse I did't saw nothing in progressing.
It is good? Should I keep waiting? (I don't know really what to do, I don't know even if the device got the command from the pc)
EranG90 said:
Thank you
I have run this command and waited 40 min with thoose screen and stop becuse I did't saw nothing in progressing.
It is good? Should I keep waiting? (I don't know really what to do, I don't know even if the device got the command from the pc)
Click to expand...
Click to collapse
Thank you so mach
I fixed my Pc usb and done the command and unlock oem
now I got only bootloader in my device
the recovery and the start options reboot the phone to the bootloader only
What I need to do now do get androird 11 back to the device?
EranG90 said:
Thank you so mach
I fixed my Pc usb and done the command and unlock oem
now I got only bootloader in my device
the recovery and the start options reboot the phone to the bootloader only
What I need to do now do get androird 11 back to the device?
Click to expand...
Click to collapse
If you're stuck on bootloader only you can try running these commands in fastboot :
fastboot -w
fastboot --set-active=a
fastboot reboot
If the phone does not boot properly then try these :
fastboot -w
fastboot --set-active=b
fastboot reboot
"fastboot -w" wipes your userdata. The "fastboot --set-active" command tells the phone which A/B slot you want to use, "fastboot reboot" is the command to restart the phone.
If you just keep getting sent back to fastboot and it won't boot then you're likely going to have to use the MSM tool to restore the phone to factory settings.
djsubterrain said:
If you're stuck on bootloader only you can try running these commands in fastboot :
fastboot -w
fastboot --set-active=a
fastboot reboot
If the phone does not boot properly then try these :
fastboot -w
fastboot --set-active=b
fastboot reboot
"fastboot -w" wipes your userdata. The "fastboot --set-active" command tells the phone which A/B slot you want to use, "fastboot reboot" is the command to restart the phone.
If you just keep getting sent back to fastboot and it won't boot then you're likely going to have to use the MSM tool to restore the phone to factory settings.
Click to expand...
Click to collapse
Really really thank you
I have tried all 4 commands (-w, --setactive=a/b and reboot)
all of them after I turn off and back on my phone show me the bootloader
can you send me a link to how I use the MSM tool to restore the phone to factory settings?
You have a LE2120 so there is no msm package publicly available yet.
In the screenshots, it shows that your fastboot drivers are not installed. Did you fix that first? The command take less than a second to run.
craznazn said:
You have a LE2120 so there is no msm package publicly available yet.
In the screenshots, it shows that your fastboot drivers are not installed. Did you fix that first? The command take less than a second to run.
Click to expand...
Click to collapse
Yes all the commands are run very fast it is no longer whiting for device
and the device state is unlock
what can I do to get android 11 on my phone? I am really new in this
EranG90 said:
Yes all the commands are run very fast it is no longer whiting for device
and the device state is unlock
what can I do to get android 11 on my phone? I am really new in this
Click to expand...
Click to collapse
try
Code:
fastboot reboot fastboot
and what shows up?
https://forum.xda-developers.com/t/...u-via-msm-no-unlock-bin-needed.4272837/unread
You can download and take the flashall.bat from this conversion guide and download your version of oneplus9pro rom to your pc then use payload dumper to extract all images, then place the flashall.bat in the same folder as all your files you dumped then plug ur phone in(while it is on bootloader screen) and double click the flashall.bat
craznazn said:
try
Code:
fastboot reboot fastboot
and what shows up?
Click to expand...
Click to collapse
thank you for answring
that what show up:
Rebooting into fastboot OKAY [ 0.004s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Shooter7889 said:
https://forum.xda-developers.com/t/...u-via-msm-no-unlock-bin-needed.4272837/unread
You can download and take the flashall.bat from this conversion guide and download your version of oneplus9pro rom to your pc then use payload dumper to extract all images, then place the flashall.bat in the same folder as all your files you dumped then plug ur phone in(while it is on bootloader screen) and double click the flashall.bat
Click to expand...
Click to collapse
Thank you
I will try anything to fix that but I am new in all this
Where I am download the flashall.bat? where I save it? How to run it?
I have download the global version for onplus9pro. What I need to do with it?
https://androidfilehost.com/?fid=14943124697586337355
This is the link to the op's zip(he created for the thread for converting tmobile variants to EU). . Click the link and download the zip, put it on your pc, then u have to extract all files. The flashall.bat is one off the files in that zip.. Then Google search the Chinese version of tue latest op9pro OS11.. Get it on your pc. U have to use payload dumper(which you will need to search android get on ur pc, extracted as well). Then once u get payload dumper ready, and ur rom, take them payload.bin from ur rom folder and put it in the payload input folder. Then double click the payload.bin and it will slowly extract all your files and put them into the payload output folder. Once it's done take the flashall.bat and put it in there. Then ur ready to plug ur phone in(in bootloader mode) and double click the flashall.bat
Shooter7889 said:
https://androidfilehost.com/?fid=14943124697586337355
This is the link to the op's zip(he created for the thread for converting tmobile variants to EU). . Click the link and download the zip, put it on your pc, then u have to extract all files. The flashall.bat is one off the files in that zip.. Then Google search the Chinese version of tue latest op9pro OS11.. Get it on your pc. U have to use payload dumper(which you will need to search android get on ur pc, extracted as well). Then once u get payload dumper ready, and ur rom, take them payload.bin from ur rom folder and put it in the payload input folder. Then double click the payload.bin and it will slowly extract all your files and put them into the payload output folder. Once it's done take the flashall.bat and put it in there. Then ur ready to plug ur phone in(in bootloader mode) and double click the flashall.bat
Click to expand...
Click to collapse
And honestly, you could prob just download the zip I mentioned, the first one just to get the flashall.bat, and just extract it, plug ur phone in(in bootloader mode) and click the flashall.bat. It would put the EU version of OS on your phone. Use cld then use the loavl update in system settings to switch to ur variant after. Much easier.