Database Info

[Q] Moto G - TWRP/CWM Do Not Open in Bootmode

I've followed instructions to unlock my bootloader which is done. I'm not sure if - "Device is unlocked. Status Code 3:" is correct or not, but that is what I see.
After unlocking I flashed TWRP 2.6.3.0-xt1032.img and it flashed correctly according to adb (attached). When I reboot the phone into bootloader and select recovery the screen just goes blank. I also tried "recovery-clockwork-touch-6.0.4.7-falcon.img", which seemed to flash OK in adb. The bootloader screen goes blank when I select recovery on the phone for CWM as well.
Both recovery flashes showed a similar result on the phone - this paste is for CWM
In Moto bootmode:
USB Connected
cmd: getvarartition-type:recovery
cmd: getvar:max-download-size
cmd: download:07b2000
cmd: flash:recovery
Mismatched partition zize (recovery)
The phone has stock Android 5.0.2 installed and still works, but I can't get any further than flashing the recovery image in adb. I did flash the logo.bin in adb and it seemed to flash correctly .
I'm running Windows 8.1, USB 3 ports.
Is there something I'm missing, or a different way to do the root? I'm stuck at this point, but luckily can run with the stock ROM for now.
I would appreciate any help I can get, Thanks

both recoveries you have used are seemingly outdated for lollipop bootloader. i would suggest you to try out the newly built TWRP (which is not yet publicly released) cant post URLs here yet but search for '[RECOVERY][falcon]TWRP 2.8.7.0 touch recovery [2015-06-24]' here in XDA
---------- Post added at 11:14 PM ---------- Previous post was at 11:03 PM ----------
here is the URL: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621

koshikas said:
both recoveries you have used are seemingly outdated for lollipop bootloader. i would suggest you to try out the newly built TWRP (which is not yet publicly released) cant post URLs here yet but search for '[RECOVERY][falcon]TWRP 2.8.7.0 touch recovery [2015-06-24]' here in XDA
---------- Post added at 11:14 PM ---------- Previous post was at 11:03 PM ----------
here is the URL: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Click to expand...
Click to collapse
I tried and same result. After flashing with adb - disconnect USB , boot into bootloader, down to recovery, push power button and blank screen. Normal power up does the same thing as does factory. Ad I can confirm the version is 41.18.
Thanks

jjcdennis said:
I tried and same result. After flashing with adb - disconnect USB , boot into bootloader, down to recovery, push power button and blank screen. Normal power up does the same thing as does factory. Ad I can confirm the version is 41.18.
Thanks
Click to expand...
Click to collapse
these blank screens are quiet frustrating, can you get hold of the stock firmware for your model and flash back the stock recovery first and then try again with latest custom recoveries

koshikas said:
these blank screens are quiet frustrating, can you get hold of the stock firmware for your model and flash back the stock recovery first and then try again with latest custom recoveries
Click to expand...
Click to collapse
I had problems last weekend after trying to go to CM12.1 after rooting and ending up in a bootloader loop. I ended up using a KitKat stock rom and mfastboot2 and typed in all of the lines - it worked. The phone then updated to 5.0.2 via auto update.
I don't have that stock from the network update, but found this one - XT1034_Retail_Canada_502_Stock_Untouched which contains 3 files, Meta-inf, system and boot.img. I don't see a recovery in the folder. I'm not really sure what to look for and how to do this.
Thanks

jjcdennis said:
I had problems last weekend after trying to go to CM12.1 after rooting and ending up in a bootloader loop. I ended up using a KitKat stock rom and mfastboot2 and typed in all of the lines - it worked. The phone then updated to 5.0.2 via auto update.
I don't have that stock from the network update, but found this one - XT1034_Retail_Canada_502_Stock_Untouched which contains 3 files, Meta-inf, system and boot.img. I don't see a recovery in the folder. I'm not really sure what to look for and how to do this.
Thanks
Click to expand...
Click to collapse
make sure you get exactly a stock ROM that is made for your model. trying firmware made for other models is surefire way of bricking you phone. usually the stock firmware images ending with '*.xml.zip' do have a 'recovery.img' in them.

koshikas said:
make sure you get exactly a stock ROM that is made for your model. trying firmware made for other models is surefire way of bricking you phone. usually the stock firmware images ending with '*.xml.zip' do have a 'recovery.img' in them.
Click to expand...
Click to collapse
Thanks again.
If I find a correct ROM (I do have a KitKat 4.4.4 version), do I flash back with adb, or with mfastbootv2?
The ROM I showed was from here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
I have also found a firmware link on this thread "http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795" that looks to be in the correct format. There are thorough instructions on how to flash the firmware, but I am not sure if this will fix my issue or not.
Would appreciate any advice on how to proceed.
Thanks

I finally understood your comment "...can you get hold of the stock firmware for your model and flash back the stock recovery first and then try again with latest custom recoveries". I got a copy of the stock firmware, extracted the recovery from it and flashed it via adb to the phone - ok. I then tried to get into phone fastboot recovery, but was faced with the blank screen again. I flashed twrp 2.8.7.0 and the same thing in fastboot recovery - blank screen. I also tried cwm 6.0.5.1 and the same thing, blank screen.
ADB sees the device and accepts the commands, but the Motorola fastboot recovery doesn't open any of the recoveries. Nothing else in the bootloader seems to work ie: Factory - blank screen.
Every one of the recovery files other than the stock recovery shows a pink colored error "Mismatched partition size (recovery).
Anybody have any ideas as to what I can do to get a recovery to work?
Is there a different way to root this phone?

@jjcdennis i think you should post this to one of the active threads, since nobody with experience (this is well beyond mine) has dropped in yet. i would highly recommend; http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621

Moved to http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621

Stuck in an EDL loop...

After flashing Lineage, the phone got stuck in an EDL loop after the initial reboot. Only sign on life is that it's recognized as a Qualcomm 9008 device in windows.
I did a full backup with EDL tools before getting started. Restoring this backup didn't resolve the issue. Also tried the reset command from edl-master; it executed successfully but the phone didn't wake up.
Anything else I should try?

Got the phone to work again. In case anyone else gets stuck in my position, here's what ultimately worked after lots of trial an error:
Downloaded the official Android 10 update from ZTE.
Extracted the payload using extract_android_ota_payload https://github.com/cyxx/extract_android_ota_payload
For some reason the extract would crap out in Windows; worked fine in Linux.
I then used the edl-master library to individually copy all the files to the device with _a and _b suffixes added. Most of the files go to lun4. There are 2 with the _a version in lun1 and the _b version in lun2. You can use the printgpt command to see which ones go where. After this the phone came back to life.
I was able to regain root by using Magisk to patch the boot image and then writing it back in EDL mode.

jc717 said:
Got the phone to work again. In case anyone else gets stuck in my position, here's what ultimately worked after lots of trial an error:
Downloaded the official Android 10 update from ZTE.
Extracted the payload using extract_android_ota_payload https://github.com/cyxx/extract_android_ota_payload
For some reason the extract would crap out in Windows; worked fine in Linux.
I then used the edl-master library to individually copy all the files to the device with _a and _b suffixes added. Most of the files go to lun4. There are 2 with the _a version in lun1 and the _b version in lun2. You can use the printgpt command to see which ones go where. After this the phone came back to life.
I was able to regain root by using Magisk to patch the boot image and then writing it back in EDL mode.
Click to expand...
Click to collapse
JC,
How were you able to get Magisk to patch the Android 10 boot image? I tried it, flashed the modded Boot IMG in EDL mode, and got the "Your device is corrupt. It cannpt be trusted and will no boot" message. I tried power cycling the phone and it went back to Bootlooping.

karlnorth said:
JC,
How were you able to get Magisk to patch the Android 10 boot image? I tried it, flashed the modded Boot IMG in EDL mode, and got the "Your device is corrupt. It cannpt be trusted and will no boot" message. I tried power cycling the phone and it went back to Bootlooping.
Click to expand...
Click to collapse
Is your bootloader unlocked?

jc717 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
No. I can't figure out how to get the Bootloader to unlock on Android 10.0. Do you know of any way that I can revert to Android 9.x US build?

karlnorth said:
No. I can't figure out how to get the Bootloader to unlock on Android 10.0. Do you know of any way that I can revert to Android 9.x US build?
Click to expand...
Click to collapse
I've achieved an unlocked bootloader! Now I'm trying to figure out how to revert to a US build of Android 9.0

Could you please possibly elaborate on what you mean by the edl master library? Sorry, I have never had to work with edl type stuff before. I successfully extracted the payload I'm just not sure where to go from there. Thank you.

jc717 said:
Got the phone to work again. In case anyone else gets stuck in my position, here's what ultimately worked after lots of trial an error:
Downloaded the official Android 10 update from ZTE.
Extracted the payload using extract_android_ota_payload https://github.com/cyxx/extract_android_ota_payload
For some reason the extract would crap out in Windows; worked fine in Linux.
I then used the edl-master library to individually copy all the files to the device with _a and _b suffixes added. Most of the files go to lun4. There are 2 with the _a version in lun1 and the _b version in lun2. You can use the printgpt command to see which ones go where. After this the phone came back to life.
I was able to regain root by using Magisk to patch the boot image and then writing it back in EDL mode.
Click to expand...
Click to collapse
how did you flash it back to the devices
and do you have the file for edl now
i am stuck in to edl and alot of trial for flashing the rom get error

jc717 said:
After flashing Lineage, the phone got stuck in an EDL loop after the initial reboot. Only sign on life is that it's recognized as a Qualcomm 9008 device in windows.
I did a full backup with EDL tools before getting started. Restoring this backup didn't resolve the issue. Also tried the reset command from edl-master; it executed successfully but the phone didn't wake up.
Anything else I should try?
Click to expand...
Click to collapse
Hi jc717,
I am same situation you described, i was tried restore from my EDL backup but didn't work. How can fix this, could you explain simple as step by step for beginners, thanks.

I managed to brick my X3

Hi forum,
I tried really hard and in the end I think I've hardbricked my phone. Of course, I started with unlocking my bootloader and flashing TWRP. I then tried flashing a custom ROM (Nitrogen) so the process for that was:
Flash miui_SURYAGlobal_V12.0.2.0.QJGMIXM_c8f2531a02_10.0
Wipe
Install ROM
Install GAPS
All went well, after which I flashed Magisk's manager which I think corrupted my ramdisk and /sdcard folder. The phone wouldn't boot into system and went straight into recovery. I'm unfamiliar with the new android folder structure, however my /sdcard folder was corrupted (all folders were just random base64 text). After that I did a full system wipe for some reason, and couldn't flash the stock firmware from recovery anymore with messages like:
Failed to mount ´/vendor´
Failed to mount ´/product´
Click to expand...
Click to collapse
Now this is where I probably messed up the most. I downloaded the EEA stock fastboot image instead of the global one. I flashed it with MiFlash and all went well. But now when the phone rebooted it went into the Nitrogen logo and was stuck there for half an hour. I thought something was up so I now downloaded the global image, went into fastboot, tried to flash it but I couldn't due to the "Flash xbl error". This is when I knew I really **** the bed. Both the global and eea image wouldn't flash because of that error. I left fastboot and my phone wouldn't boot again.
Good news is I installed the Qualcomm drivers and my phone at least shows up as a Qualcomm device and is detected by QFIL. I quickly tried flashing the stock global rom with QFIL but I got Sahara errors that could be due to other stuff but I don't want to push it any further before asking you guys. Any advice?
Update: The current state is black screen, however I can get it to flash stock ROM until it asks for authentication and tells me I'm not authorized to do this ( I'm guessing this is EDL). Should I ask my vendor if they provide such services?

Ask this guy to flash through edl. +7 967 777-15-98
It costs about 30 USD.
To boot into edl you need to specifically boot though key combinations or testpoint.
I would recommend against flashing a China based rom on a global device. Don't switch versions around as you can mess up your persist.img partition.
Try running the bat flash script directly into cmd and don't relock bootloader.

Hi,
Two friend try to restore with Edl, success, but phone still bricked...

I got the same scenariS.
---------- Post added at 06:51 PM ---------- Previous post was at 06:47 PM ----------
Hopefully someone can help us

jcyrdrgz said:
I got the same scenario right now after I wipe my data and tried to install v12.0.3.0 EEA coming from Havoc OS.
---------- Post added at 06:51 PM ---------- Previous post was at 06:47 PM ----------
Hopefully someone can help us with the EDL thing for MiFlash
Click to expand...
Click to collapse
Do you know where are points edl ?
---------- Post added at 08:11 PM ---------- Previous post was at 07:59 PM ----------
jcyrdrgz said:
I got the same scenario right now after I wipe my data and tried to install v12.0.3.0 EEA coming from Havoc OS.
---------- Post added at 06:51 PM ---------- Previous post was at 06:47 PM ----------
Hopefully someone can help us with the EDL thing for MiFlash
Click to expand...
Click to collapse
Fake points in red
True in green
https://www.mediafire.com/view/c7mdrgjgi83nrjl
Credit to @mahajant99 at télégram

what exactly is causing this? where did you go wrong

I think you messed up somewhere else. EEA should be flashable on Global phones. EEA is just European version of the Global ROM that ships with stuff like Google Dialer. And besides, when you flash Global MIUI on Chinese phone you just get an error that it can't be used

Deleted

Speedo.thc said:
Do you know where are points edl ?
---------- Post added at 08:11 PM ---------- Previous post was at 07:59 PM ----------
Fake points in red
True in green
https://www.mediafire.com/view/c7mdrgjgi83nrjl
Credit to @mahajant99 at télégram
Click to expand...
Click to collapse
Oh I doesn't open the battery cover of my phon

jcyrdrgz said:
Oh I doesn't open the battery cover of my phone to do that. It's just automatically being detected as Qualcomm 9008 something under Device Manager which means that it's on EDL Mode without touching those points.
The only solution I have in mind is to wait for the latest fastboot file for v12.0.3.0 EEA (Because this is the last update my phone have, which i think causing the problem not letting me flash the V12.0.2.0 EEA due to rollback protection) so that I can see if it MiFlash will let me flash it without the EDL Authentication.
Or somebody who has the capability to edit the firehouse for the firmware to disable the EDL Authentication.
Click to expand...
Click to collapse
You can wait, it's right.
At the point that you enter edl like the command "fastboot oem edl" you have more luck to unbrick device.
For your information we are minimum 3 to get brick now , more than yours coz it's not booting in edl but die.
Flashing (paid) with edl didn't help anymore.

Speedo.thc said:
You can wait, it's right.
At the point that you enter edl like the command "fastboot oem edl" you have more luck to unbrick device.
For your information we are minimum 3 to get brick now , more than yours coz it's not booting in edl but die.
Flashing (paid) with edl didn't help anymore.
Click to expand...
Click to collapse
Well, I'm planning to visit a service center by the end of the week

jcyrdrgz said:
Well, I'm planning to visit a service center by the end of the week if v12.0.3.0 fastboot file is still not out. I'm just really tired of searching for hundred+ threads already about this EDL Authentication when I tried to flash the v12.0.2.0. I really hope that they'll release it soon and it will let me flash it without the EDL Auth Acct.
Click to expand...
Click to collapse
Hi, no bypass for PocoX3 actually.
But you can miss time and download virus in search.

Have you tried a deep flash cable to force the phone into EDL-mode?
I'm not sure that it still works, but it was a solution to save a bricked Xiaomi a couple of years ago.

how I solve the same situation
SKULLHEADHJ said:
Hi forum,
I tried really hard and in the end I think I've hardbricked my phone. Of course, I started with unlocking my bootloader and flashing TWRP. I then tried flashing a custom ROM (Nitrogen) so the process for that was:
Flash miui_SURYAGlobal_V12.0.2.0.QJGMIXM_c8f2531a02_10.0
Wipe
Install ROM
Install GAPS
All went well, after which I flashed Magisk's manager which I think corrupted my ramdisk and /sdcard folder. The phone wouldn't boot into system and went straight into recovery. I'm unfamiliar with the new android folder structure, however my /sdcard folder was corrupted (all folders were just random base64 text). After that I did a full system wipe for some reason, and couldn't flash the stock firmware from recovery anymore with messages like:
Now this is where I probably messed up the most. I downloaded the EEA stock fastboot image instead of the global one. I flashed it with MiFlash and all went well. But now when the phone rebooted it went into the Nitrogen logo and was stuck there for half an hour. I thought something was up so I now downloaded the global image, went into fastboot, tried to flash it but I couldn't due to the "Flash xbl error". This is when I knew I really **** the bed. Both the global and eea image wouldn't flash because of that error. I left fastboot and my phone wouldn't boot again.
Good news is I installed the Qualcomm drivers and my phone at least shows up as a Qualcomm device and is detected by QFIL. I quickly tried flashing the stock global rom with QFIL but I got Sahara errors that could be due to other stuff but I don't want to push it any further before asking you guys. Any advice?
Update: The current state is black screen, however I can get it to flash stock ROM until it asks for authentication and tells me I'm not authorized to do this ( I'm guessing this is EDL). Should I ask my vendor if they provide such services?
Click to expand...
Click to collapse
I installed twrp and the xiaomi eu and my phone ended in twrp only boot with sdcard partition encrypted, tried to write with miflash fastboot rom I get xbl error , reboot in twrp format data then installed xiaomi eu.zip without any problem so far.

SKULLHEADHJ said:
Hi forum,
I tried really hard and in the end I think I've hardbricked my phone. Of course, I started with unlocking my bootloader and flashing TWRP. I then tried flashing a custom ROM (Nitrogen) so the process for that was:
Flash miui_SURYAGlobal_V12.0.2.0.QJGMIXM_c8f2531a02_10.0
Wipe
Install ROM
Install GAPS
All went well, after which I flashed Magisk's manager which I think corrupted my ramdisk and /sdcard folder. The phone wouldn't boot into system and went straight into recovery. I'm unfamiliar with the new android folder structure, however my /sdcard folder was corrupted (all folders were just random base64 text). After that I did a full system wipe for some reason, and couldn't flash the stock firmware from recovery anymore with messages like:
Now this is where I probably messed up the most. I downloaded the EEA stock fastboot image instead of the global one. I flashed it with MiFlash and all went well. But now when the phone rebooted it went into the Nitrogen logo and was stuck there for half an hour. I thought something was up so I now downloaded the global image, went into fastboot, tried to flash it but I couldn't due to the "Flash xbl error". This is when I knew I really **** the bed. Both the global and eea image wouldn't flash because of that error. I left fastboot and my phone wouldn't boot again.
Good news is I installed the Qualcomm drivers and my phone at least shows up as a Qualcomm device and is detected by QFIL. I quickly tried flashing the stock global rom with QFIL but I got Sahara errors that could be due to other stuff but I don't want to push it any further before asking you guys. Any advice?
Update: The current state is black screen, however I can get it to flash stock ROM until it asks for authentication and tells me I'm not authorized to do this ( I'm guessing this is EDL). Should I ask my vendor if they provide such services
Hi hows your pocox3 today
Click to expand...
Click to collapse

skullheadhj, did you ever resolve this issue. I got the same thing as you "not authorized" after an almost 13000 second "flashing screen. I tried Qfil, same error. I do get the port as #4 in miflash and in Device Manager ports&lpt/ I have had to uninstall and reinstall the qualcom driver, as for some reason the PC gets a USB error.
SO I'm stuck here still looking for a solution.

jjcdennis said:
skullheadhj, did you ever resolve this issue. I got the same thing as you "not authorized" after an almost 13000 second "flashing screen. I tried Qfil, same error. I do get the port as #4 in miflash and in Device Manager ports&lpt/ I have had to uninstall and reinstall the qualcom driver, as for some reason the PC gets a USB error.
SO I'm stuck here still looking for a solution.
Click to expand...
Click to collapse
when i was in ur problem i just flash stock rom via miflash
but need still UBL UNLOCK
ORIGNAL ROM PHONE ( I MEAN UR PHONE IS GLOBAL / CHINA / INDIA / INDONESIA )
CAREFULL WITH BASE PHONE ROM
BECAUSE AS I KNOW IF UR PHONE WAS CHINA AND U TRY TO FLASH WITH GLOBAL / INDIA IT WILL BRICK / EVEN LOCK / EVEN DIED
so after that u need to go service center < last hope

Phone boots into fastboot, system files corrupted

Hi! My old phone is booting into fastboot mode, when I try to boot normally I get a black screen, the "Power off" button appears when I hold the power button. The bootloader is not unlocked and the phone was never rooted. Wiping the user partition does not help. It is visible in fastboot mode and I can enter stock recovery, though trying to adb sideload a stock rom returns an error (footer is wrong; signature verification failed). Trying to fastboot boot twrp or recovery.img doesn't work either. I've ran out of ideas, what should I do to get this phone to work?

Try flashing the stock ROM with fastboot. I'm pretty sure ADB doesn't let you flash onto your phone because using your phone with ADB means that it's still powered on - which can cause some issues. You can also try and unlock your bootloader through fastboot, and then flash a recovery and custom ROM.

Both failed. I attached the errors I recieved.

crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try "fastboot bootloader unlock", maybe. Also: Is there a flashall.bat in the stock ROM folder? If there is: Connect your device while in fastboot, and double-click it.

crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try this maybe. I know you can't wipe through the stock ROM, so, try the command: "fastboot -w". That'll wipe everything off the device.
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own. Moto G (3rd Gen) Factory Firmware Images - Provided by Firmware TEAM - Please report broken links. New Mirrors welcome...
forum.xda-developers.com

I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.

crepper4454 said:
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
Click to expand...
Click to collapse
Try this: https://forum.xda-developers.com/t/guide-osprey-fastboot-flashing-factory-firmware-images.3187750/

It says there that the "preflash validation failed" error occurs when the firmware being flashed is older than the one already installed. I will try downloading a newer version and flashing it. Will update here.

Update: I have dowloaded a newer rom and tried to flash it. This time got different errors (picture attached, this went for every sparsechunk). I think I know the reason but I do not know how to solve it. This might not be the exact stock rom of this phone so I cannot flash it with a locked bootloader. Could someone help me finding the correct rom or suggest a different solution?

Yooooo. I have the Moto e5 Cruise and so does my wife. We bought them in 2018 from Cricket and last night hers went to emmc failure, also known scientifically as 'no worky' mode.
The phone would only load in fastboot and had tried to use my Moto RSD tool to reflash but the phone would not detect in anything but fastboot mode.. Here's where it gets interesting....
There is a piece of software called the Lenovo (which now owns Moto) Rescue and Smart Assistant that can reflash your phone back to factory, no matter your sub-variant (cricket, metro, etc). Without having a fresh backup on hand, you're going to be beholden to the last cloud sync or manual backup you have because all data will be wiped in the below process.
BTW: Just run the assistant as it seems to be the easiest 'back-to-stock/working' tool I can find. Going to fastboot alone yielded weird errors since i didn't have the unlock code for the 'fastboot oem unlock [code goes here]' command.
**RESTORATION PROCESS**
This will apply to multiple Lenovo/Moto Mobility devices. Unknown at this time how many have been impacted by this seemingly pre-planned failure on Lenovo's part.
If your phone is stuck in fastboot mode where MTK download mode does not load, nor does adb, follow these simple steps:
(NOTE: BACKUP YOUR FILES IF POSSIBLE)
1. Click the link above to be directed to the Lenovo software download page and run the installer on your PC (Sorry Mac users :'().
2. The software, once installed, will require you to sign up for OR link a google, fb, g+, etc account to it for purposes of creating a Lenovo ID. Once signed in, click on 'Rescue Now'.
3. With your phone in fastboot mode, allow the software to download the firmware for your phone.
4. Once the firmware has finished downloading and validating, click on 'Rescue Now' once again. Your phone will begin the reflashing process.

That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .

crepper4454 said:
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
Click to expand...
Click to collapse
No problemo! Glad it worked!

Cannot get oem unlock token oneplus 8 tmobile (in2017)

So I purchased a tmobile op8 and it arrived yesterday, after setting up the phone and network unlocking (which happened basically instantaneously after applying for it which i found odd), I am currently trying to unlock bootloader in the hopes of converting it to the international firmware. I am on software version 11.0.5.7.IN55CB
The problem I am facing is that whenever i try to do "adb devices" while the phone is powered on it works and lists it, but when the phone is in fastboot mode it does not list the device. Also when i do "fastboot oem get_unloock_code" it gets stuck at waiting for devices. I have read through numerous posts both here and on the op forums talking about this and some listed solutions such as going into windows optional updates and updating google bootloader or something, while others said to check that bootloader is unlocked (i did both and didnt work). Any tips? Also, could someone please link to the correct adb and driver downloads as I am getting mixed results when searching which is the correct download.

Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.

FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Thanks, worked like a charm. Now to wait 7 business days fml

if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk

PrivyetCyka said:
if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk
Click to expand...
Click to collapse
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol

DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
i have t-m version and i have converted it to international software firmware also gets changed but by your self you won't be able to get 2 sim support because there is only one imei in phone. all the rom's work exacly the same as they do on global version not a single difference currently running a12 aex rom no problems at all

DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind

d.tat said:
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind
Click to expand...
Click to collapse
Can this be done without TWRP or does this have to be done after I root?

DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great

DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
no root needed to install or boot into twrp

d.tat said:
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great
Click to expand...
Click to collapse
Ok, thanks for clarification

FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface

DamianF7 said:
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface
Click to expand...
Click to collapse
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged in and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.

FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery.
2. Flash recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery NAMEOFFILE.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Use this command "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks for the reply man. Believe it or not this is exactly what I did lol. Got it working again and am now rooted on international oos 11.

FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!

SilverZero said:
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!
Click to expand...
Click to collapse
Glad you got it man, worth all the trouble to get to a clean version of OOS without T-MO's junk and spying xD

FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged on and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?

nmuntz said:
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?
Click to expand...
Click to collapse
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.

FoxyDrew said:
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.
Click to expand...
Click to collapse
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!

nmuntz said:
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!
Click to expand...
Click to collapse
I've never seen that MSM tool, but the one I use doesn't have any Sprint files at all. Not sure where you found that MSM but use this one for future reference.
No you don't need to flash global before a ROM.