Database Users

Revert back to locked state after unofficial unlock (Redmi note 3 pro/SD)

Hi All, I have unlocked the bootloader the unnofical way and i am on global 7.1.7.0(LHOMICL) with twrp and root.
I now have recieved the official sms to unlock from xiaomi.
Already i had to open the phone 3 times to get into edl mode. I really dont wont to open the phone agian.
When i try to unlock the tool answers no need to unlock. I think this is because i flashed the adapted emmc_appsboot.mbn and boot.img thru fastboot.
Do i have to change te rom to another version before i try thru edl or fastboot? What is the best procedure to official unlock now because i read a lot of bricks if they try to revert back to original state.
Can some one give me a detailed guide? Thanx in advance.

You need to flash a fully stock edl ROM on top of your current setup.
This will wipe out your hacked bootloader and throw the original (still locked) one back onto your device.
Then just unlock as usual. I did the procedure myself today already as I got my unlock notification today as well.

Ok thnx for the info. I have changed this global rom 7.1.7.0 in great extend and dont wont to lose this setup.
So can I backup my current setup with twrp with the hacked bootloader.
Flash the complete global 7.1.7.0 in edl mode. Unlock with the unlock tool.
Root the rom and install twrp.
After this can i restore the backup with the hacked bootloader with twrp?
I dont know how the unlock tool of xiaomi works, so i could leave the official bootloader in place when i do the restore with twrp and only replace system and data partition or can i flash all the parts back with twrp to keep the unlock?
Wich procedure will keep the official unlock in place or will this unlock stick always?

davegrond said:
Hi All, I have unlocked the bootloader the unnofical way and i am on global 7.1.7.0(LHOMICL) with twrp and root.
I now have recieved the official sms to unlock from xiaomi.
Already i had to open the phone 3 times to get into edl mode. I really dont wont to open the phone agian.
When i try to unlock the tool answers no need to unlock. I think this is because i flashed the adapted emmc_appsboot.mbn and boot.img thru fastboot.
Do i have to change te rom to another version before i try thru edl or fastboot? What is the best procedure to official unlock now because i read a lot of bricks if they try to revert back to original state.
Can some one give me a detailed guide? Thanx in advance.
Click to expand...
Click to collapse
Plz could you help me and tell me where you got the hacked unlocked bootloader cause I bricked my redmi note 3 pro snap dragon and only only fastboot is available and when I try to flash it I get the message device locked boot locked can not flash and plz hobe me a detaild link and downloads and how to flash also I did not get the unlock code and how to get the locked one back z original plz help best regards

Plz indeed to know how to hack the bootloader cause I bricked my phone and I need to make it life

MrColdbird said:
You need to flash a fully stock edl ROM on top of your current setup.
This will wipe out your hacked bootloader and throw the original (still locked) one back onto your device.
Then just unlock as usual. I did the procedure myself today already as I got my unlock notification today as well.
Click to expand...
Click to collapse
please give a detailed tutorial how to do it. I am now in AOSP with unofficially unlocked bootloader. How to relock it again to unlock officially?

Relock Bootloader
I see many asking how to Relock Bootloader, especially those who had unlocked unofficially.
The steps to be followed are following:
(1) Turn on USB debugging for your phone;
Go to Settings -- About Phone --> Touch 7 times on "MIUI version" to Enable Developer Options.
Now go to Settings - Additional Settings - Developer Options --> USB debugging.
Enable USB Debugging and Connect to PC.
(2) Download Fastboot ROM (file extension .tgz or .tar) from
Code:
http://en.miui.com/a-234.html
(3) Boot into EDL
adb devices (to check it's connected)
adb reboot edl
(4) Use MI Flash Tool to Flash the Fastboot ROM
PS: It is assumed that person knows how to get drivers installed for phone if not already, use ADB command as well as know MI Flash Tool basics.
@BRoy_98 @ioosis @davegrond : hope this helps.
@MrColdbird Thanks for the tip

BRoy_98 said:
please give a detailed tutorial how to do it. I am now in AOSP with unofficially unlocked bootloader. How to relock it again to unlock officially?
Click to expand...
Click to collapse
Thx
Sent from my Redmi Note 3 using XDA-Developers mobile app

Unable to relock
Someone please let me know how to relock the bootloader.
I tried flashing the global rom using flash tool but still it says unlocked when i check it from fastboot mode.

anwar08 said:
Someone please let me know how to relock the bootloader.
I tried flashing the global rom using flash tool but still it says unlocked when i check it from fastboot mode.
Click to expand...
Click to collapse
On MiFlash, select folder of Fastboot ROM, then click on Advanced, and in fastboot script select flash_all_lock.bat. After it, close MiFlash then open it again and check in advanced if flash_all_lock.bat comes selected. If yes, close advanced box and flash ROM. Don't forget to close and open MiFlash after choose flash_all_lock.bat script, it's important step. And you can do it in Fastboot mode, don't need to go to EDL mode to flash the ROM.

andersonaragao said:
On MiFlash, select folder of Fastboot ROM, then click on Advanced, and in fastboot script select flash_all_lock.bat. After it, close MiFlash then open it again and check in advanced if flash_all_lock.bat comes selected. If yes, close advanced box and flash ROM. Don't forget to close and open MiFlash after choose flash_all_lock.bat script, it's important step. And you can do it in Fastboot mode, don't need to go to EDL mode to flash the ROM.
View attachment 3854529 View attachment 3854530 View attachment 3854531 View attachment 3854532
Click to expand...
Click to collapse
Am using the 32 bit beta version and there is no Advanced option

anwar08 said:
Am using the 32 bit beta version and there is no Advanced option
Click to expand...
Click to collapse
see if it's in Configuration.

warranty
does rooting redmi note 3 void warranty bcuz it has a locked bootloader and cannot root without unlocking it ????
and can we lock bootloader again for warranty claims ????
plzz help ???
ty.

Why can't we directly update the device..
Like after flashing miui ROM (7.1)then installing (8.1)....will the bootloader get locked....
?....somebody have any idea place help out

Q. Can the device be rooted without voiding warranty?
A. Yes, by unlocking the BL unofficially.
Q. Once rooted and on MiUI, can I update using Updater?
A. No! You'll lock your BL and end up in a bootloop. Instead, use the updater to download the zip file, reboot into recovery (TWRP or ZCX) flash the zip first and then the universal boot.img patched/lazy flasher and reboot to system.

I followed the method mentioned in the replies to relock the bootloader, i.e, flashed the fastboot rom in edl mode
But for some strange reason, when I entered the fastboot mode and checked whether the bootloader is locked or not by "fastboot oem device-info", it said "Device Unlocked: True"
The main problem came when I booted into the ROM; It broke all kinds of wireless connections. The wifi malfunctioned, the phone wouldn't read the SIM cards etc.
Is there a solution? Please help
Thanks

[guide] how to fix totally dead redmi note 4 | stuck in bootloop | qfil flashing

Hello everyone, in today's guide I will tell you all how to fix bootloop problem in Redmi note 4
NOTE: THIS FIX IS FOR THOSE WHOSE PROBLEM DIDN'T GET FIXED EVEN AFTER FLASHING WITH MIFLASH
QFIL is a tool which is used to flash stock firmwares in Qualcomm smartphones.
Prerequisites:
1)Bricked Redmi note 4 (lol I guess you have that already if you are reading this)
2) Working USB cable (You really dont want yourself smashing your head and then finding out faulty cable)
3) QPST Version 2.7.438.3 (Google it)
4) Unlocked bootloader
5) Platform Tools (For passing OEM EDL command)
6) Stock fastboot MIUI ROM (IMPORTANT: Use V8.1.10.0.MCFMIDI from here: http://bigota.d.miui.com/V8.1.10.0....DI_20161228.0000.00_6.0_global_7557bfe334.tgz)
7)QDLoader HS-USB Driver for Redmi Note 4X
Note: I'm not responsible if you mess up your device the mentioned process helped me and others in fixing our devices. You yourself are responsible!
Steps:
1) Open QFIL tool from C:\Program Files\Qualcomm\QPST\bin or wherever you installed it. Run as administrator!
Note: Don't use older version QPST, because you will get an error message when writing userdata section.
2) In QFIL choose Flat Build option.
3) Make sure you you have extracted the above ROM file onto desktop
4) In QFIL tool browse and locate .mbn file
(Named like: prog_emmc_firehose_8953_ddr.mbn)
5) Click on Load XML and select rawprogram0.xml and patch0.xml inside your Fastboot ROM folder.
6) Now turn off your phone and enter Fastboot mode by pressing ans holding power button+vol down button. After that open platform tools folder downloaded above and right click opening cmd in that folder and write following command:
fastboot oem edl
And hit enter (The above command does require your bootloader to be unlocked so kindly keep that in mind before passing the command)
7) Your phone will exit Fastboot mode and red led will start blinking and your phone will be detected as COM port in QFIL tool.
8) At last hit download button, if you did everything right process should begin and end saying download complete.
9) You can now remove your phone and keep holding power button till it boots up. First boot will take some time.
Optional step 10) If you loose your IMEI in flashing process then you can flash your IMEI using Qualcomm IMEI tool (If you face problem in this then comment and i will come up with another guide regarding IMEI flashing)
Hope it helps, if yes be sure you hit that thumbs up button it gives me good feeling lol ?
Reply if you face any problem
Peace!

addymishra said:
Hello everyone, in today's guide I will tell you all how to fix bootloop problem in Redmi note 4
NOTE: THIS FIX IS FOR THOSE WHOSE PROBLEM DIDN'T GET FIXED EVEN AFTER FLASHING WITH MIFLASH
QFIL is a tool which is used to flash stock firmwares in Qualcomm smartphones.
Prerequisites:
1)Bricked Redmi note 4 (lol I guess you have that already if you are reading this)
2) Working USB cable (You really dont want yourself smashing your head and then finding out faulty cable)
3) QPST Version 2.7.438.3 (Google it)
4) Unlocked bootloader
5) Platform Tools (For passing OEM EDL command)
6) Stock fastboot MIUI ROM (IMPORTANT: Use V8.1.10.0.MCFMIDI from here: http://bigota.d.miui.com/V8.1.10.0....DI_20161228.0000.00_6.0_global_7557bfe334.tgz)
7)QDLoader HS-USB Driver for Redmi Note 4X
Note: I'm not responsible if you mess up your device the mentioned process helped me and others in fixing our devices. You yourself are responsible!
Steps:
1) Open QFIL tool from C:\Program Files\Qualcomm\QPST\bin or wherever you installed it. Run as administrator!
Note: Don't use older version QPST, because you will get an error message when writing userdata section.
2) In QFIL choose Flat Build option.
3) Make sure you you have extracted the above ROM file onto desktop
4) In QFIL tool browse and locate .mbn file
(Named like: prog_emmc_firehose_8953_ddr.mbn)
5) Click on Load XML and select rawprogram0.xml and patch0.xml inside your Fastboot ROM folder.
6) Now turn off your phone and enter Fastboot mode by pressing ans holding power button+vol down button. After that open platform tools folder downloaded above and right click opening cmd in that folder and write following command:
fastboot oem edl
And hit enter
7) Your phone will exit Fastboot mode and red led will start blinking and your phone will be detected as COM port in QFIL tool.
8) At last hit download button, if you did everything right process should begin and end saying download complete.
9) You can now remove your phone and keep holding power button till it boots up. First boot will take some time.
Optional step 10) If you loose your IMEI in flashing process then you can flash your IMEI using Qualcomm IMEI tool (If you face problem in this then comment and i will come up with another guide regarding IMEI flashing)
Hope it helps, if yes be sure you hit that thumbs up button it gives me good feeling lol
Reply if you face any problem
Peace!
Click to expand...
Click to collapse
Hi,
after your manual, download success, the device restarts, but it then gets stuck with the MI logo?
What can I do?
sieg

sieg01 said:
Hi,
after your manual, download success, the device restarts, but it then gets stuck with the MI logo?
What can I do?
sieg
Click to expand...
Click to collapse
Hello there,
First of all make sure that you are flashing the fastboot rom which I mentioned in the thread.
Now coming to your problem, open QFIL tool and open configuration panel. You will see many options, check for 'Erase before Download' option and make sure its unchecked then try flashing again. If the problem persist then send me screenshot of QFIL tool along with configuration.
All the best!

addymishra said:
Hello there,
First of all make sure that you are flashing the fastboot rom which I mentioned in the thread.
Now coming to your problem, open QFIL tool and open configuration panel. You will see many options, check for 'Erase before Download' option and make sure its unchecked then try flashing again. If the problem persist then send me screenshot of QFIL tool along with configuration.
All the best!
Click to expand...
Click to collapse
Hi again,
I have flashed again and in the " download configuration " I set " Erase before Download", please see the Attachment, unfortunately the same device restarts, but it then gets stuck with the MI logo?

sieg01 said:
Hi again,
I have flashed again and in the " download configuration " I set " Erase before Download", please see the Attachment, unfortunately the same device restarts, but it then gets stuck with the MI logo?
Click to expand...
Click to collapse
Dear, you DON'T NEED TO SELECT "ERASE BEFORE DOWNLOAD" !!! Now listen carefully what to do-:
1) Download mi flash tool and mi unlock tool
2) Your bootloader must be locked now so unlock it with mi unlock (Don't worry just use your mi account it will unlock successfully)
3) Once unlocked flash the fastboot rom in fastboot mode using mi flash tool. IMPORTANT: MAKE SURE YOU SELECT "CLEAN ALL" OPTION
4) Now when flashed your device will restart. Dont let it boot up. Press and hold power+volume down button till you enter into fastboot
5) From fastboot enter EDL mode using "fastboot oem edl" command. Red light will blink
6) Open QFIL and make sure "Erase before download" IS *NOT* SELECTED
7)Click download and you should be good to go
All the best

addymishra said:
Dear, you DON'T NEED TO SELECT "ERASE BEFORE DOWNLOAD" !!! Now listen carefully what to do-:
1) Download mi flash tool and mi unlock tool
2) Your bootloader must be locked now so unlock it with mi unlock (Don't worry just use your mi account it will unlock successfully)
3) Once unlocked flash the fastboot rom in fastboot mode using mi flash tool. IMPORTANT: MAKE SURE YOU SELECT "CLEAN ALL" OPTION
4) Now when flashed your device will restart. Dont let it boot up. Press and hold power+volume down button till you enter into fastboot
5) From fastboot enter EDL mode using "fastboot oem edl" command. Red light will blink
6) Open QFIL and make sure "Erase before download" IS *NOT* SELECTED
7)Click download and you should be good to go
All the best
Click to expand...
Click to collapse
1. My redmi is unlocked ( from Xiaomi )
2. MI flash tool don`t work, because I get error: can not found file flash_all.bat, so I dont`t use this tool

sieg01 said:
1. My redmi is unlocked ( from Xiaomi )
2. MI flash tool don`t work, because I get error: can not found file flash_all.bat, so I dont`t use this tool
Click to expand...
Click to collapse
In order to use mi flash correctly kindly place the fastboot rom in C: drive root directory then try flashing, it will work. Its a bug of mi flash

Hi I followed your all 9 steps in the first post. However, me too is stuck in 'mi' logo nothing happens waiting after 10 minutes
Then I followed the following steps, flashed by mi tool followed by QFIL. But my QFIL didn't have "ERASE BEFORE DOWNLOAD" option. I downloaded the exact QPST version 2.7.438.3 from gsmhosting forum.
Still the phone boots and stuck with 'mi' logo forever. I have tried flashing other ROMs like RR, lineageOS from TWRP but each of the ROM is stuck while booting . Only miuiPro "miuipro_v7.0_mido_v9.2.1.0_NCFCNEK.zip" manages to boot but keeps rebooting after every 2-3 seconds. My phone has been useless for 3 long days.
addymishra said:
Dear, you DON'T NEED TO SELECT "ERASE BEFORE DOWNLOAD" !!! Now listen carefully what to do-:
1) Download mi flash tool and mi unlock tool
2) Your bootloader must be locked now so unlock it with mi unlock (Don't worry just use your mi account it will unlock successfully)
3) Once unlocked flash the fastboot rom in fastboot mode using mi flash tool. IMPORTANT: MAKE SURE YOU SELECT "CLEAN ALL" OPTION
4) Now when flashed your device will restart. Dont let it boot up. Press and hold power+volume down button till you enter into fastboot
5) From fastboot enter EDL mode using "fastboot oem edl" command. Red light will blink
6) Open QFIL and make sure "Erase before download" IS *NOT* SELECTED
7)Click download and you should be good to go
All the best
Click to expand...
Click to collapse

biits1993 said:
Hi I followed your all 9 steps in the first post. However, me too is stuck in 'mi' logo nothing happens waiting after 10 minutes
Then I followed the following steps, flashed by mi tool followed by QFIL. But my QFIL didn't have "ERASE BEFORE DOWNLOAD" option. I downloaded the exact QPST version 2.7.438.3 from gsmhosting forum.
Still the phone boots and stuck with 'mi' logo forever. I have tried flashing other ROMs like RR, lineageOS from TWRP but each of the ROM is stuck while booting . Only miuiPro "miuipro_v7.0_mido_v9.2.1.0_NCFCNEK.zip" manages to boot but keeps rebooting after every 2-3 seconds. My phone has been useless for 3 long days.
Click to expand...
Click to collapse
Try downloading the lastest version from here:
https://androidmtk.com/download-qpst-flash-tool
Erase before download must be unchecked
And remember first boot does take some time so be patient a little. Hope it works!

addymishra said:
Try downloading the lastest version from here:
https://androidmtk.com/download-qpst-flash-tool
Erase before download must be unchecked
And remember first boot does take some time so be patient a little. Hope it works!
Click to expand...
Click to collapse
Hi, Thank you very much, I managed to boot the ROM using QFil , however in setup wizard I can't get past the getting device security info in mi account setup. Besides, dialogues for lots "app stopped working" keeps coming. and also there are frequent reboots

addymishra said:
In order to use mi flash correctly kindly place the fastboot rom in C: drive root directory then try flashing, it will work. Its a bug of mi flash
Click to expand...
Click to collapse
Hi,
II managed to flash successfully with MIflash tool, but after switching it on
do I have permanent boot loop with MI logo? Andere Fastboot ROM`s will MIflash nicht machen. Please look my Screenshot.
Greating

biits1993 said:
Hi, Thank you very much, I managed to boot the ROM using QFil , however in setup wizard I can't get past the getting device security info in mi account setup. Besides, dialogues for lots "app stopped working" keeps coming. and also there are frequent reboots
Click to expand...
Click to collapse
Strange :/ you can try miflash tool for that case. Download the lastest mi flash tool, enter into EDL mode using "fastboot oem edl" command then in mi flash drop down menu in left corner select "flash_factory.bat" and click flash. It will take around 400 seconds. Make sure you are in edl mode with red blinking light otherwise it will wipe your IMEI. Hope it works!

sieg01 said:
Hi,
II managed to flash successfully with MIflash tool, but after switching it on
do I have permanent boot loop with MI logo? Andere Fastboot ROM`s will MIflash nicht machen. Please look my Screenshot.
Greating
Click to expand...
Click to collapse
Are you able to enter into setup wizard? If not then try the procedure I posted above using factory flash. After flashing with mi flash once again try flashing with QFIL. It's sometimes hit or miss :/

addymishra said:
Are you able to enter into setup wizard? If not then try the procedure I posted above using factory flash. After flashing with mi flash once again try flashing with QFIL. It's sometimes hit or miss :/
Click to expand...
Click to collapse
Hi,
I don`t able to enter into setup wizard, because boot-loop, so I done following:
1. mi flash factory flash-successfully
2. mi flash flash once again-successfully
3. flashing with QFIL- successfully
After switch-on again boot loop every 22 seconds with mi-logo
Do you have any more tips for me?
Greating
sieg

sieg01 said:
Hi,
I don`t able to enter into setup wizard, because boot-loop, so I done following:
1. mi flash factory flash-successfully
2. mi flash flash once again-successfully
3. flashing with QFIL- successfully
After switch-on again boot loop every 22 seconds with mi-logo
Do you have any more tips for me?
Greating
sieg
Click to expand...
Click to collapse
Man, I think its some sort of hardware issue then. Or maybe your messed up your blobs or your partitions real bad and corrupted them. QFIL helped in my case. Got no more tips, maybe its time to visit service center brother One last shot you can give is to try flashing with QFIL first then with Mi Flash. That's last hope! All the best!

flash failed in QFIL please help

sohanaw said:
flash failed in QFIL please help
Click to expand...
Click to collapse
Which version of QFIL and which ROM are you flashing with? I managed to flash the said version in OP through QFIL without any error. However, other official versions like 9.xx fail to be flashed by QFIL

A solution that worked after all these troubles
Hi everyone,
This post is for those who are still struggling with 'cool' bootloop in Redmi note 4x irrespective of stock, custom ROMS, you are flashing.
Before all these steps I flashed "mido_global_images_V8.1.10.0.MCFMIDI_20161228.0000.00_6.0_global_7557bfe334.tgz" using QFIL first, then miFlash tool. I was greeted by "can't decrypt phone".
Refer to the OP
Then I flashed lazy_flasher and managed to boot into the stock ROM but couldn't get past the Mi account setup. Even my Keyboard app keeps stopping, so annoying.
The the below Steps I followed redeemed me of this agony powered by xiaomi:
1. Downloaded this firmware==>"global-mido-firmware-7.12.14.zip"
Mokee ROM==>"MK71.2-mido-201803080920-NIGHTLY"
open gapps arm-64, 7.1, pico
open gapps arm-64, 7.1, nano [BOTH] from gapps
2. flashed TWRP=3.1.1-0[official version] from the xda
Code:
fastboot flash recovery [name_of_recovery_image_of_twrp]
3. Entered into Recovery==>WIPE=>Advanced WIPE=> select all partitions==>WIPE[can leave Internal storage unchecked]
4. Then Format Data==>yes
5. Copied firmware, Mokee ROM, pico and nano gapps [4 items] to internal storage
6. Flashed downloaded firmware, then MOKEE ROM, then gapps-nano
7. Reboot to recovery
8. After entering Recovery, Reboot to system
Hopefully we will see mi logo, then Mokee robot animating soon enough. It will take you to setup wizard within 5-10 minutes, If you see any Google apps [Gboard in my case] stopping,
it may mean that google Play services were not installed properly[Don't know why]. In my case I couldn't set up Google account/framework first time. If it happens, go to settings,
enable developer options tapping BUILD version==>then enable USB debugging.
Then reboot to Recovery
Flash gapps-pico.
Do factory reset from Recovery, simple wipe.
Then reboot to System.[DON'T install TWRP as system app etc]
For me, this time I was able to setup google account from the setup wizard. Google service framework has been working without any issues. [ Again Don't know why]
This time I have been able to install my desired apps from playstore
Few more words:
Firstly, I tried flashing only pico, but I couldn't set up the google account, no matter how many times I reboot to recovery, wipe Dalvik-cache etc, then flash pico.
I described exactly what I did that worked out for me. There could be many possible orders, combinations, but I don't have time for that.
I tried to flash Alexy's "RR-N-v5.8.5-20180121mido_alexy.zip" ROM in combination with this firmware but it just will hang TWRP while flashing. only this MOKEE ROM worked with this firmware for me.
I wasted full 3 days for fixing this device. And no intention to tinker with it anymore, my communication has been in a mess!.
While in stock MIUI 'google *apps keeps stopping" just annoyed me as hell, so decided to switch, and after 3 days of disgusting 'Waiting period for bootloader UNLOCK' I couldn't even install a working stock
MIUI ROM now, maybe cheap hardware issue offered by Xiaomi. They have just made everything complex. This is my first and last device from them. My previous Moto G3 was amazing and would be with me had it not been stolen
Will be happy to help regarding this issue, and thank you the OP of this thread, who helped me realize that this device is still able to boot.
Wishing everyone in this note 4x trouble good luck!!

biits1993 said:
Hi everyone,
This post is for those who are still struggling with 'cool' bootloop in Redmi note 4x irrespective of stock, custom ROMS, you are flashing.
Before all these steps I flashed "mido_global_images_V8.1.10.0.MCFMIDI_20161228.0000.00_6.0_global_7557bfe334.tgz" using QFIL first, then miFlash tool. I was greeted by "can't decrypt phone".
Refer to the OP
Then I flashed lazy_flasher and managed to boot into the stock ROM but couldn't get past the Mi account setup. Even my Keyboard app keeps stopping, so annoying.
The the below Steps I followed redeemed me of this agony powered by xiaomi:
1. Downloaded this firmware==>"global-mido-firmware-7.12.14.zip"
Mokee ROM==>"MK71.2-mido-201803080920-NIGHTLY"
open gapps arm-64, 7.1, pico
open gapps arm-64, 7.1, nano [BOTH] from gapps
2. flashed TWRP=3.1.1-0[official version] from the xda
Code:
fastboot flash recovery [name_of_recovery_image_of_twrp]
3. Entered into Recovery==>WIPE=>Advanced WIPE=> select all partitions==>WIPE[can leave Internal storage unchecked]
4. Then Format Data==>yes
5. Copied firmware, Mokee ROM, pico and nano gapps [4 items] to internal storage
6. Flashed downloaded firmware, then MOKEE ROM, then gapps-nano
7. Reboot to recovery
8. After entering Recovery, Reboot to system
Hopefully we will see mi logo, then Mokee robot animating soon enough. It will take you to setup wizard within 5-10 minutes, If you see any Google apps [Gboard in my case] stopping,
it may mean that google Play services were not installed properly[Don't know why]. In my case I couldn't set up Google account/framework first time. If it happens, go to settings,
enable developer options tapping BUILD version==>then enable USB debugging.
Then reboot to Recovery
Flash gapps-pico.
Do factory reset from Recovery, simple wipe.
Then reboot to System.[DON'T install TWRP as system app etc]
For me, this time I was able to setup google account from the setup wizard. Google service framework has been working without any issues. [ Again Don't know why]
This time I have been able to install my desired apps from playstore
Few more words:
Firstly, I tried flashing only pico, but I couldn't set up the google account, no matter how many times I reboot to recovery, wipe Dalvik-cache etc, then flash pico.
I described exactly what I did that worked out for me. There could be many possible orders, combinations, but I don't have time for that.
I tried to flash Alexy's "RR-N-v5.8.5-20180121mido_alexy.zip" ROM in combination with this firmware but it just will hang TWRP while flashing. only this MOKEE ROM worked with this firmware for me.
I wasted full 3 days for fixing this device. And no intention to tinker with it anymore, my communication has been in a mess!.
While in stock MIUI 'google *apps keeps stopping" just annoyed me as hell, so decided to switch, and after 3 days of disgusting 'Waiting period for bootloader UNLOCK' I couldn't even install a working stock
MIUI ROM now, maybe cheap hardware issue offered by Xiaomi. They have just made everything complex. This is my first and last device from them. My previous Moto G3 was amazing and would be with me had it not been stolen
Will be happy to help regarding this issue, and thank you the OP of this thread, who helped me realize that this device is still able to boot.
Wishing everyone in this note 4x trouble good luck!!
Click to expand...
Click to collapse
will try this tonight, thanks bhai

sohanaw said:
will try this tonight, thanks bhai
Click to expand...
Click to collapse
Let me know bro what happens, hope it works for you
I wanted to use RR rom though, but in the end no ROM worked for me except this one. So I'm just happy with it.

Any help will do.

Hello Everyone,
I really need help regarding this matter. I came from Evolution X 3.0 custom rom, now when I flash to stock rom, I flashed the Nougat version instead of Pie.
Now my dilemmas are the following:
1. Stuck in bootloop
2. Unable to unlock bootloader since I'm unable to boot it to the system
3. Tried all the other guide including this post except for number 2, since I don't know how to do that, and number 6, since I'm unable to open it for now: https://forum.xda-developers.com/showpost.php?p=78219944&postcount=224
Since this is the case, should I need to proceed with number 6 or is there any other methods I can use?

kevinzareno said:
Hello Everyone,
I really need help regarding this matter. I came from Evolution X 3.0 custom rom, now when I flash to stock rom, I flashed the Nougat version instead of Pie.
Now my dilemmas are the following:
1. Stuck in bootloop
2. Unable to unlock bootloader since I'm unable to boot it to the system
3. Tried all the other guide including this post except for number 2, since I don't know how to do that, and number 6, since I'm unable to open it for now: https://forum.xda-developers.com/showpost.php?p=78219944&postcount=224
Since this is the case, should I need to proceed with number 6 or is there any other methods I can use?
Click to expand...
Click to collapse
For step 2 you need to install Mi A1 device's drivers first, so you'll be allowed to use fastboot and adb commands from PC to your device.
The command shown on that step is just what you have to type when you open cmd at file's and adb-fastboot folder. Just paste the name of the file you've to load and install "adb sideload thisiswhatiwanttoinstall.zip".
You can find a better way to understand this procedure, by reading those rooting methods with TWRP... obviously not those with 1-click-root ones... look for those that make use of "adb-fastboot", since there, after TWRP custom Recovery is flashed, you're able to sideload Magisk to it to it in order to be also flashed on your device.
It's a pretty easy task once you have managed to install device's drivers well and have "adb-fastboot" tools, to open cmd from it's folder and start to run adb or fastboot commands to your device.

KaaMyA said:
For step 2 you need to install Mi A1 device's drivers first, so you'll be allowed to use fastboot and adb commands from PC to your device.
The command shown on that step is just what you have to type when you open cmd at file's and adb-fastboot folder. Just paste the name of the file you've to load and install "adb sideload thisiswhatiwanttoinstall.zip".
You can find a better way to understand this procedure, by reading those rooting methods with TWRP... obviously not those with 1-click-root ones... look for those that make use of "adb-fastboot", since there, after TWRP custom Recovery is flashed, you're able to sideload Magisk to it to it in order to be also flashed on your device.
It's a pretty easy task once you have managed to install device's drivers well and have "adb-fastboot" tools, to open cmd from it's folder and start to run adb or fastboot commands to your device.
Click to expand...
Click to collapse
I see. We'll will this work even if the bootloader is locked? I can't really unlock it

kevinzareno said:
I see. We'll will this work even if the bootloader is locked? I can't really unlock it
Click to expand...
Click to collapse
First of all be sure you could complete that tutorial you're following.
You're flashing device's firmware, that will put all on its place.
It's not like flashing a ROM, you're trying to unbrick device's software.

if you have enabled oem unlock in Development Settings then you can unlock bootloader by fastboot cmd "fastboot oem unlock" or if it not works try flashing stock pie rom with Miflash tool and if Miflash tool not works try QFIL
just a tip: when you flash stock rom with miflash tool and don't want to relock bootloader just remove the lines with "fastboot flash userdata" and "fastboot oem lock" in flash script "flash_all.bat" or "flash_all_except_storage.bat"
---------- Post added at 05:47 AM ---------- Previous post was at 05:43 AM ----------
just boot into EDL mode and try flashing with MiFlash tool.
i was revive my device with QFIL. QFIL automatically reboot device into EDL mode

Lg v20 h91820h t-mobile bootloader cannot be unlocked - android 8 oreo

UPDATE:
I successfully unlocked the bootloader, flashed twrp, rooted, updated kernel and roms, tweaking gpu cpu for performance in pubg etc, greenify, flashify, power nap everything.
xposed framework take you in bootloop for this device.
now i am on kernel mk2000, superv20 rom, h91810u, 7 nougat.
if in future anyone feels any problem i am always here.
remember: linus is your friend for this device, and windows 10 suck.
and
sudo $(which fastboot) did miracles for me....
old post:
Hello everyone.
i am new here and i am sorry in advance if i did something wrong. i will come directly to the point.
model number: LG V20 T-MOBILE VERSION, H91820H, NON USA, Currently on oreo android 8.
we are not talking about any kind of roms kernels roots or anything here. just a simple question. " can this model's boot loader be unlocked ? like ever ? or not "
cause i have tried everything, when i say everything i mean everything. followed several posts on internet videos on you tube posts on XDA, tried using multiple PCs, multiple data cables, multiple drivers but for some reason i don't know what, this model's boot loader cannot be unlocked.
THE ERROR:
<WAITING FOR DEVICE> till eternity.
what i have done till now ?
1. lg drivers installed.
2. adb drivers installed with adb fastboot files.
3. updating legacy android adb interface driver, done.
4. went in to boot loader then connected the data cable and updated driver, done.
5. usb debugging oem unlock options activated, done.
6. restarted pc multiple times to update drivers, done.
we all know all it takes is 3 easy commands to unlock bootlaoder
adb reboot bootloader
fastboot oem unlock
fastboot reboot
but in my case i always stuck at 2nd command. waiting for device is shown and nothing happens.
then i ran command, adb devices>> it shows
List of devices attached
adb server is out of date. killing...
* daemon started successfully *
LGH9182bfc6bdc device
next i put the command, fastboot devices and nothing is shown i just go to the next line... c:\adb>
so this is for sure that my device is not connected to the fastboot.
now my only question is, can this device bootloader unlock or not ? so that i stop pushing my limits.
any help will be appreciated.
regards.

X_BlackBurn_X said:
Hello everyone.
i am new here and i am sorry in advance if i did something wrong. i will come directly to the point.
model number: LG V20 T-MOBILE VERSION, H91820H, NON USA, Currently on oreo android 8.
we are not talking about any kind of roms kernels roots or anything here. just a simple question. " can this model's boot loader be unlocked ? like ever ? or not "
cause i have tried everything, when i say everything i mean everything. followed several posts on internet videos on you tube posts on XDA, tried using multiple PCs, multiple data cables, multiple drivers but for some reason i don't know what, this model's boot loader cannot be unlocked.
THE ERROR:
<WAITING FOR DEVICE> till eternity.
what i have done till now ?
1. lg drivers installed.
2. adb drivers installed with adb fastboot files.
3. updating legacy android adb interface driver, done.
4. went in to boot loader then connected the data cable and updated driver, done.
5. usb debugging oem unlock options activated, done.
6. restarted pc multiple times to update drivers, done.
we all know all it takes is 3 easy commands to unlock bootlaoder
adb reboot bootloader
fastboot oem unlock
fastboot reboot
but in my case i always stuck at 2nd command. waiting for device is shown and nothing happens.
then i ran command, adb devices>> it shows
List of devices attached
adb server is out of date. killing...
* daemon started successfully *
LGH9182bfc6bdc device
next i put the command, fastboot devices and nothing is shown i just go to the next line... c:\adb>
so this is for sure that my device is not connected to the fastboot.
now my only question is, can this device bootloader unlock or not ? so that i stop pushing my limits.
any help will be appreciated.
regards.
Click to expand...
Click to collapse
Are you following this > https://r.tapatalk.com/shareLink/to...3&share_fid=3793&share_type=t&link_source=app
[ROOT] - lafsploit - H918 (any version up to and including 20h) - now n00b friendly
Sent from my HD1907 using Tapatalk

Thanks for thanks for replying on a short notice I have seen this post there is no reason to follow any of the post because the very first stage is to unlock the bootloader but as I cannot unlock the bootloader there is no point in following any of the posts my problem is what ever way I follow I am unable to to unlock the bootloader in fact what I can see is whenever I try to type in command ADB devices IC e my phone but when I type fastboot devices nothing happens it's like my phone is not in the fastboot that is why why I cannot unlock the bootloader I have tried every possible step mentioned on the internet and on various forums I also go through some videos on YouTube those guys follow the same steps and unlock their bootloader but my device cannot unlock for some reason so if you lovely people can help me out and figure out what exactly I am doing wrong as I have followed every step of unlocking the bootloader I've installed all the drivers I have updated all the drivers I have done exactly e all three steps which has been asked but still no luck thank you

clsA said:
Are you following this > https://r.tapatalk.com/shareLink/to...3&share_fid=3793&share_type=t&link_source=app
[ROOT] - lafsploit - H918 (any version up to and including 20h) - now n00b friendly
Sent from my HD1907 using Tapatalk
Click to expand...
Click to collapse
To be very precise after following the first step while unlocking the bootloader in the second step when we type fast boot devices it should show some hexadecimal numbers and it should confirm us that our device is in the fastboot mode but in my case whenever I type this command nothing happens that means my device is not recognised to go in the bootloader this is the main problem there is no point in following any of the posts if you cannot complete the very first stage of unlocking your bootloader if you can figure out what exactly is the problem I will be thankful to you because I have followed every step possible I've updated every ADB drivers LG drivers but nothing is helping out as even before starting the procedure of unlocking the bootloader my device is not going in the fast boot also I noticed one thing when I try to go inside the bootloader screen before that in my device manager it is shown as composit device but after that I think it gets disconnected fastboot oem unlock cannot work as it gives a message of waiting for the device after going are using the command ADB reboot bootloader so my problem is the command fastboot oem unlock is pretty useless as it waits for the device and it's stuck there forever please help me out if you can I will be thankful to you regards

X_BlackBurn_X said:
To be very precise after following the first step while unlocking the bootloader in the second step when we type fast boot devices it should show some hexadecimal numbers and it should confirm us that our device is in the fastboot mode but in my case whenever I type this command nothing happens that means my device is not recognised to go in the bootloader this is the main problem there is no point in following any of the posts if you cannot complete the very first stage of unlocking your bootloader if you can figure out what exactly is the problem I will be thankful to you because I have followed every step possible I've updated every ADB drivers LG drivers but nothing is helping out as even before starting the procedure of unlocking the bootloader my device is not going in the fast boot also I noticed one thing when I try to go inside the bootloader screen before that in my device manager it is shown as composit device but after that I think it gets disconnected fastboot oem unlock cannot work as it gives a message of waiting for the device after going are using the command ADB reboot bootloader so my problem is the command fastboot oem unlock is pretty useless as it waits for the device and it's stuck there forever please help me out if you can I will be thankful to you regards
Click to expand...
Click to collapse
Did you downgrade to software version H91810P? Because that should be the first thing you have to do to get everything else to work afterwards.

C D said:
Did you downgrade to software version H91810P? Because that should be the first thing you have to do to get everything else to work afterwards.
Click to expand...
Click to collapse
Thanks for the reply.
Can you please clear me one thing. To downgrade from h91820h to h91810p you need to unlock bootloader if i am not wrong. And in that case we will be back to square 1.
Its not about installing custom rom kernel recovery root or anything. Its only about unlocking the bootloader which i cannot do.
I hope you understand my pain.
I just want to unlock my bootloader thats it.
It used only 3 commands.
1. Adb devices - shows my device.
2. Fastboot devices - no fastboot device found.
This is the problem. When you cannot find any fastboot device even updating driver by going inside the bootloader the entire mission gets failed.
I cant find any solution for this. I dont know for what reason my device cannot be listed in fastboot mode.

X_BlackBurn_X said:
Thanks for the reply.
Can you please clear me one thing. To downgrade from h91820h to h91810p you need to unlock bootloader if i am not wrong. And in that case we will be back to square 1.
Its not about installing custom rom kernel recovery root or anything. Its only about unlocking the bootloader which i cannot do.
I hope you understand my pain.
I just want to unlock my bootloader thats it.
It used only 3 commands.
1. Adb devices - shows my device.
2. Fastboot devices - no fastboot device found.
This is the problem. When you cannot find any fastboot device even updating driver by going inside the bootloader the entire mission gets failed.
I cant find any solution for this. I dont know for what reason my device cannot be listed in fastboot mode.
Click to expand...
Click to collapse
fastboot doesn't work when the phone is booted up
adb reboot bootloader
followed by fastboot devices
Note: flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP
Example:
D:\fastboot>adb devices
List of devices attached
LGUS99740047103 device
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot oem device-id
...
(bootloader) ----------------------------------
(bootloader) Device-ID
(bootloader) F3D7DE171C893D55082EAE38270125EF
(bootloader) DA7CB3E78B1DB5709A2CA8********
(bootloader) ----------------------------------
OKAY [ 0.060s]
finished. total time: 0.060s
D:\fastboot>fastboot reboot
rebooting...
finished. total time: 0.008s
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot getvar unlocked
unlocked: no
finished. total time: 0.003s
Click to expand...
Click to collapse

X_BlackBurn_X said:
Thanks for the reply.
Can you please clear me one thing. To downgrade from h91820h to h91810p you need to unlock bootloader if i am not wrong. And in that case we will be back to square 1.
Its not about installing custom rom kernel recovery root or anything. Its only about unlocking the bootloader which i cannot do.
I hope you understand my pain.
I just want to unlock my bootloader thats it.
It used only 3 commands.
1. Adb devices - shows my device.
2. Fastboot devices - no fastboot device found.
This is the problem. When you cannot find any fastboot device even updating driver by going inside the bootloader the entire mission gets failed.
I cant find any solution for this. I dont know for what reason my device cannot be listed in fastboot mode.
Click to expand...
Click to collapse
As clsA said, flashing firmware does not require an unlocked bootloader.
Look at parts 1 and 2 of the other step by step guide here:
https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258

clsA said:
fastboot doesn't work when the phone is booted up
adb reboot bootloader
followed by fastboot devices
Note: flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP
Example:
Click to expand...
Click to collapse
Thanks for the solution. May be this is it. All the time i have been doing it wrong.
Solution : flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP.
I will downgrade from 20h to 10p now and will give you feedback on this soon. Thanks a ton for showing a noob like me the right direction to work.

X_BlackBurn_X said:
Thanks for the solution. May be this is it. All the time i have been doing it wrong.
Solution : flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP.
I will downgrade from 20h to 10p now and will give you feedback on this soon. Thanks a ton for showing a noob like me the right direction to work.
Click to expand...
Click to collapse
No problem the link @C D posted above seems to have all the working links for you

clsA said:
No problem the link @C D posted above seems to have all the working links for you
Click to expand...
Click to collapse
well we have a new problem now.
lgup error 0x2bc invalid command response code = 0x80000202 at 4 percent while flashing.
did i just brick my phone now ? as it says dont unplug until you are done and we have been getting same error again and again.
used the provided kdz file flashing as an upgrade.

ok so the new problem is... may be i was trying to flash h91810p naugaut on to a oreo h91820h
and if i am not wrong at this stage i messed up pretty bad my phone is stuck in donwload mode wont boot up and i need to flash back 20h again to get out of this mess. can anyone hlp me ....
i just wanna know h91810p downgrading from 91820h is possible or not ? cause one is naugaut and one is oreo.

UPDATE:
i was flashing wrong h91810p thats why it was showing error. on another website i got the file compatible to my phone t mobile version and flash was successful.
now i am on h91810p software version andriod 7.
problem UPDATE:
i still cant unlock bootloader. same problem as before downgrading from h91820h.
adb devices shows device.
adb reboot bootloader
fastboot devices gives no result.
phone cannot enter in fastboot mode. the problem still remains the same even after changing the software.
kindly help guys

clsA said:
fastboot doesn't work when the phone is booted up
adb reboot bootloader
followed by fastboot devices
Note: flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP
Example:
Click to expand...
Click to collapse
hello clsA
"
D:\fastboot>adb devices
List of devices attached
LGUS99740047103 device
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot oem device-id
after this it only says waitng for device"
now i am on h91810p as i was instructed. can you please help.
its all happening the same way it was happening when was on h91820h.
fastboot devices cannot be found.
once it reboots in bootloader then it should detect a fastboot device but it doesnot and adb is also lost there.
kindly help.

NEW UPDATE:
my lg v20 now on software h91810p is actually a T MOBILE version. and when i researched more about it i found out T MOBILE deliberately locks the boot loader of many devices and its unlockable.
possible work around can be if the software version installed on your phone can some how be an international version of your ROM, then only you can unlock the bootloader else none of your commands will work. now i am trying to flash this phone using an international ROM version if i succeed i will update. but according to my knowledge flashing other roms other than t mobile ones will definitely give errors in LGUP.

X_BlackBurn_X said:
NEW UPDATE:
my lg v20 now on software h91810p is actually a T MOBILE version. and when i researched more about it i found out T MOBILE deliberately locks the boot loader of many devices and its unlockable.
possible work around can be if the software version installed on your phone can some how be an international version of your ROM, then only you can unlock the bootloader else none of your commands will work. now i am trying to flash this phone using an international ROM version if i succeed i will update. but according to my knowledge flashing other roms other than t mobile ones will definitely give errors in LGUP.
Click to expand...
Click to collapse
Do not flash another model's firmware onto the H918! Doing so will permanently brick your phone. The H918 in particular is incompatible with all other variants' software. Also, flashing H918 firmware onto any other model will also brick that phone.

C D said:
Do not flash another model's firmware onto the H918! Doing so will permanently brick your phone. The H918 in particular is incompatible with all other variants' software. Also, flashing H918 firmware onto any other model will also brick that phone.
Click to expand...
Click to collapse
hello
thanks for the reply.
i know we cannot flash any other phones firmware on to this model.
i was thinking of flashing specifically lg v20 h91810p international stock firmware, one is t mobile and one is international stock rom of same model.
cause t mobile is not allowing me to unlock the bootloader but an international stock rom will.
i have seen people doing on t mobile on youtube videos i dont know how they are doing it.
my problem is :
" as in message sent to various senior on this topic"
LG V20 H91810P, T MOBILE BOOTLOADER CANNOT BE UNLOCKED
HELLO
can you please help me out on a quest to unlock my bootloader of lg v20 h91810p. i have downgraded from h91820h to h91810p and still all the adb commands fail to make my phone go in to fastboot mode. i just cannot enter in fastboot mode,
adb devices shows my device
|but fastboot devices in bootloader mode doesnot show my device at all.
updated all the drivers used multiple pcs usb ports but no luck at all.,
what am i possibly doing wrong can you please help me out? i will be thankful to you.
on a side note i think t mobile has lockedd my bootloader so that i canoot unlock it,
regards

X_BlackBurn_X said:
hello
thanks for the reply.
i know we cannot flash any other phones firmware on to this model.
i was thinking of flashing specifically lg v20 h91810p international stock firmware, one is t mobile and one is international stock rom of same model.
cause t mobile is not allowing me to unlock the bootloader but an international stock rom will.
i have seen people doing on t mobile on youtube videos i dont know how they are doing it.
my problem is :
" as in message sent to various senior on this topic"
LG V20 H91810P, T MOBILE BOOTLOADER CANNOT BE UNLOCKED
HELLO
can you please help me out on a quest to unlock my bootloader of lg v20 h91810p. i have downgraded from h91820h to h91810p and still all the adb commands fail to make my phone go in to fastboot mode. i just cannot enter in fastboot mode,
adb devices shows my device
|but fastboot devices in bootloader mode doesnot show my device at all.
updated all the drivers used multiple pcs usb ports but no luck at all.,
what am i possibly doing wrong can you please help me out? i will be thankful to you.
on a side note i think t mobile has lockedd my bootloader so that i canoot unlock it,
regards
Click to expand...
Click to collapse
Did you make the Linux USB boot stick
Are you following the guide at all?
PART 3: CREATING A BOOTABLE LINUX USB USING FWUL
DOWNLOAD FWUL_v2.7_x86_64_15GB.zip FROM THE LINK BELOW AND EXTRACT THE IMAGE FILE SOMEWHERE IN YOUR PC.
https://androidfilehost.com/?w=files&flid=214529
DOWNLOAD RUFUS FROM BELOW AND INSTALL
https://rufus.akeo.ie/
INSERT A PEN DRIVE IN YOUR PC AND RUN RUFUS.
INSIDE RUFUS SELECT THE IMAGE FILE AND SELECT START (AFTER SELECTING START SELECT DD MODE IN THE DIALOGUE BOX) TO CREATE A BOOTABLE PEN DRIVE (WARNING: THIS WOULD FORMAT YOUR PEN DRIVE)
NOW YOU SHOULD BOOT YOUR PC FROM THE BOOTABLE USB STICK WHICH YOU HAVE JUST CREATED
THIS WOULD MAKE YOUR PC RUN LINUX OS
TYPE PASSWORD AS linux AND ENTER
Sent from my HD1907 using Tapatalk

clsA said:
Did you make the Linux USB boot stick
Are you following the guide at all?
PART 3: CREATING A BOOTABLE LINUX USB USING FWUL
DOWNLOAD FWUL_v2.7_x86_64_15GB.zip FROM THE LINK BELOW AND EXTRACT THE IMAGE FILE SOMEWHERE IN YOUR PC.
https://androidfilehost.com/?w=files&flid=214529
DOWNLOAD RUFUS FROM BELOW AND INSTALL
https://rufus.akeo.ie/
INSERT A PEN DRIVE IN YOUR PC AND RUN RUFUS.
INSIDE RUFUS SELECT THE IMAGE FILE AND SELECT START (AFTER SELECTING START SELECT DD MODE IN THE DIALOGUE BOX) TO CREATE A BOOTABLE PEN DRIVE (WARNING: THIS WOULD FORMAT YOUR PEN DRIVE)
NOW YOU SHOULD BOOT YOUR PC FROM THE BOOTABLE USB STICK WHICH YOU HAVE JUST CREATED
THIS WOULD MAKE YOUR PC RUN LINUX OS
TYPE PASSWORD AS linux AND ENTER
Sent from my HD1907 using Tapatalk
Click to expand...
Click to collapse
thanks again for the showing me the right direction. i was talking about unlocking the bootloader in step 1.
i will go through your links and try to study this.
just one more question.
does this method unlocks the bootloader ?
if yes please reply yes i will be thankful to you.
i will follow this step now.
regards

X_BlackBurn_X said:
hello clsA
"
D:\fastboot>adb devices
List of devices attached
LGUS99740047103 device
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot oem device-id
after this it only says waitng for device"
now i am on h91810p as i was instructed. can you please help.
its all happening the same way it was happening when was on h91820h.
fastboot devices cannot be found.
once it reboots in bootloader then it should detect a fastboot device but it doesnot and adb is also lost there.
kindly help.
Click to expand...
Click to collapse
Why does adb show your device as a 997 which is the Sprint variant
Sent from my LG-H910 using XDA Labs

[GUIDE] Simpler Way to Get Rid of T-Mobile USA Branding

For those who only want custom roms - an easier way to convert from T-Mobile USA. You don't need to flash system/product/vendor partitions. No restoring modem to get signal, data will work on first boot after you install a custom rom.
This could be easily done on Linux and Windows too. I don't recommend flashall. Just do it manually. For this discussion, I am converting T-Mobile to Euro:
1. Get T-Mobile MSM package from HERE. Get Euro package (for converting) from HERE
2. Flash T-Mobile MSM (you can't transfer the MSM package via flash drive, as some files will be corrupted and you won't be able to start the package. Just download straight, unzip and execute the exe. file)
3. Boot, enable OEM unlock (you'll have to connect to the internet for a few minutes) and unlock bootloader (get unlock bin from Oneplus)
4. Once unlocked, boot again, connect to PC, enable Developer options, enable ADB. Open terminal and execute adb command:
Code:
adb reboot fastboot
You will get into 'fastbootd' recovery, but that's how it should be. Your fastboot commands will be accepted.
5. Now, unzip the downloaded Euro version, go to that directory, open terminal and execute manually the following commands separately (just copy and paste a single command from the code below) followed by pressing 'enter', i.e. paste the command, press enter, paste the next command, press enter. Watch the terminal to make sure that each command went through:
Code:
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash modem modem.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
6. Once done, don't reboot in system. Instead, reboot into bootloader. From that, follow directions to install a custom rom. If Lineage, for example, flash their recovery first (fastboot flash recovery...), then boot into that recovery. Don't flash their 'copy partitions' files. Instead, just install the latest release via 'adb-sideload' (factory reset before or after flashing is required). Then boot into System normally. Your phone will have normal IMEI/Baseband and it will be listed as IN2013.
This is only for those who want custom roms. No stock OOS updates, which vendor is not needed any way, as all custom roms for Oneplus 8 provide their own vendor.

How to Unlock Oneplus 8 tmobile Bootloader without unlock token​

farhansaeeddnp3021 said:
How to Unlock Oneplus 8 tmobile Bootloader without unlock token​
Click to expand...
Click to collapse
Short answer - Forget it, for good. Here is the long one:
Tmobile branded Oneplus 8's bootloader is tied to a key generated based on the unique numbers, which in turn, are tied to your device's unique IMEI. This is why it is a 2 step process: first, you generate a sequence of 2 long numbers on the phone. Second, you send those numbers together with your IMEI to Oneplus. Only after that, you get the token, which could only work on your phone.
This is why, at Oneplus online store, unbranded Oneplus 8 is $100 more expensive than the branded one. The latter is software crippled, and on other sites, the difference is up to $200. You get what you paid for.

optimumpro said:
Short answer - Forget it, for good. Here is the long one:
Tmobile branded Oneplus 8's bootloader is tied to a key generated based on the unique numbers, which in turn, are tied to your device's unique IMEI. This is why it is a 2 step process: first, you generate a sequence of 2 long numbers on the phone. Second, you send those numbers together with your IMEI to Oneplus. Only after that, you get the token, which could only work on your phone.
This is why, at Oneplus online store, unbranded Oneplus 8 is $100 more expensive than the branded one. The latter is software crippled, and on other sites, the difference is up to $200. You get what you paid for.
Click to expand...
Click to collapse
thanks for replay. recently i unlock oneplus 7t pro Mclarn without unlock token. so that why i was thinking about it.

farhansaeeddnp3021 said:
thanks for replay. recently i unlock oneplus 7t pro Mclarn without unlock token. so that why i was thinking about it.
Click to expand...
Click to collapse
That's because there is a modified MSM tool for Oneplus 7 with a removed device name check. That enables you to flash global firmware on any Oneplus 7 variant. This is not possible on Oneplus 8.

Hi. Im on oxygen os 11.0.4.6IN55CB. do i need to downgrade to TMO android 10 before proceed with this? My device is TMO unlocked and bootloader locked (I don't mind about the bootloader, i can unlock it anytime)

aikattx said:
Hi. Im on oxygen os 11.0.4.6IN55CB. do i need to downgrade to TMO android 10 before proceed with this? My device is TMO unlocked and bootloader locked (I don't mind about the bootloader, i can unlock it anytime)
Click to expand...
Click to collapse
No. You don't. The tool already includes the downgrade software.

Why did you link to and suggest the Euro version of this ROM? The global version is recommended if converting from T-Mobile and should be used instead. Also creates a discrepency from the title of this thread, you did not make a guide on how to convert to global, you made a guide on how to convert to the European version.
to be fair tho shouldn't really cause issues

FoxyDrew said:
Why did you link to and suggest the Euro version of this ROM? The global version is recommended if converting from T-Mobile and should be used instead. Also creates a discrepency from the title of this thread, you did not make a guide on how to convert to global, you made a guide on how to convert to the European version.
to be fair tho shouldn't really cause issues
Click to expand...
Click to collapse
You are right, but as you said, there would be no difference in the outcome, except that your phone will show IN2013 instead of IN2015.

optimumpro said:
You are right, but as you said, there would be no difference in the outcome, except that your phone will show IN2013 instead of IN2015.
Click to expand...
Click to collapse
That's not the ONLY difference, the differences there are will probably be imperceivable in daily use however. Honestly only brought it up because I saw the title of the thread and the a link to the euro ROM and was a tad confused for a sec
Edit: "or Euro" I actually audibly laughed when I saw that, that's great. Great tutorial man haha

FoxyDrew said:
That's not the ONLY difference, the differences there are will probably be imperceivable in daily use however. Honestly only brought it up because I saw the title of the thread and the a link to the euro ROM and was a tad confused for a sec
Edit: "or Euro" I actually audibly laughed when I saw that, that's great. Great tutorial man haha
Click to expand...
Click to collapse
All right. Thanks for a very useful comment. Ha-Ha!

optimumpro said:
All right. Thanks for a very useful comment. Ha-Ha!
Click to expand...
Click to collapse
Ouch you seem salty lol, I could say the same

FoxyDrew said:
Ouch you seem salty lol, I could say the same
Click to expand...
Click to collapse
That's because you seamed to sound sarcastic. "Great guide, ha-ha"

optimumpro said:
That's because you seamed to sound sarcastic. "Great guide, ha-ha"
Click to expand...
Click to collapse
oh no that was genuine lol

FoxyDrew said:
oh no that was genuine lol
Click to expand...
Click to collapse
All right. My apologies. Sometimes it's difficult to figure out intentions on the internet.

Hi and thank you so much for this guide! I'm having a problem with flashing the global rom, it tells me flashing isnt allowed for critical partitions, despite having done both the unlock (fastboot menu confirms it) and fastboot oem unlock_critical.
Has anyone seen this before?

ManlyP0tato said:
Hi and thank you so much for this guide! I'm having a problem with flashing the global rom, it tells me flashing isnt allowed for critical partitions, despite having done both the unlock (fastboot menu confirms it) and fastboot oem unlock_critical.View attachment 5426977 Has anyone seen this before?
Click to expand...
Click to collapse
Step 4: adb reboot fastboot
This has to be done on a live device with adb enabled, connected to PC and typed on PC terminal. As a result, you are not rebooting into fastboot, but in recovery with fastboot commands enabled.

optimumpro said:
Step 4: adb reboot fastboot
This has to be done on a live device with adb enabled, connected to PC and typed on PC terminal. As a result, you are not rebooting into fastboot, but in recovery with fastboot commands enabled.
Click to expand...
Click to collapse
Thanks for your reply!
Is this the difference between fastboot and fastbootd?
Despite using the command and going into fastboot I still can't seem to make it work, even selecting recovery mode in fastboot only brings me back here. I of course installed a fresh MSM version beforehand and unlocked the bootloader.
this is the screen I'm getting, is this fastboot with recovery or only fastboot?
Before reaching fastboot though it takes me to the oneplus language select screen, then gives me the option to wipe, fastboot or recovery, maybe it has something to do with this?
Thanks again for your time.

ManlyP0tato said:
Thanks for your reply!
Is this the difference between fastboot and fastbootd?
Despite using the command and going into fastboot I still can't seem to make it work, even selecting recovery mode in fastboot only brings me back here. I of course installed a fresh MSM version beforehand and unlocked the bootloader. View attachment 5426993 this is the screen I'm getting, is this fastboot with recovery or only fastboot?
View attachment 5426995
Before reaching fastboot though it takes me to the oneplus language select screen, then gives me the option to wipe, fastboot or recovery, maybe it has something to do with this?
Thanks again for your time.
Click to expand...
Click to collapse
Wrong action. You'll never be able to flash critical partitions from fastboot, i.e., the screen in your picture. After executing the adb command in step 4, your phone will enter recovery (not fastboot) and you must stay there. Nowhere my instructions say reboot to fastboot. So, stay in recovery and execute all further commands from your PC.
Edit: Yes, that's the difference between fastboot (your screen shot) and fastbootd, which is Recovery with fastboot commands support.

optimumpro said:
Wrong action. You'll never be able to flash critical partitions from fastboot, i.e., the screen in your picture. After executing the adb command in step 4, your phone will enter recovery (not fastboot) and you must stay there. Nowhere my instructions say reboot to fastboot. So, stay in recovery and execute all further commands from your PC.
Edit: Yes, that's the difference between fastboot (your screen shot) and fastbootd, which is Recovery with fastboot commands support.
Click to expand...
Click to collapse
Ooh! I see I misunderstood that, it works just fine from the recovery screen!
I tried flashing the entire global rom because I don't want a custom rom but I just got a qualcomm crashdump mode . Currently using MSM to fix that. Is it even possible to use the global rom with the Tmobile model? Otherwise I'll just use Lineage.