Related
LG V30 Recovery UnBrick Zips
So as some of you are aware, I released a h932 rom that soft bricked a few devices. well in the process of that I (with @runningnak3d help) figured out a way to unbrick those devices. As long as you have TWRP or download mode with ADB then you can unbrick. These zips here are NOT meant to be flashed to just flash. These zips are for those people that have a non 9008 brick only! DO NOT FLASH THESE ZIPS OR RUN THESE COMMANDS FOR ANY REASON EXCEPT FOR A NON 9008 BRICK! DO NOT FLASH OR RUN THIS COMMANDS BECAUSE YOU HAVE A BOOTLOOP! ONLY FOLLOW THIS THREAD FOR NON 9008 BRICKS! PLEASE BE SMART!
Now on to the good stuff.......
Only download and flash the zip made for your original device model. Do NOT flash whatever your converted too. for example i have a ls998 converted to us998. I would flash the ls998 THEN convert to us998 later on...
NOTE: After flashing the unbrick zip for your model youll need to have a rom zip on your sdcard or internal storage. You'll need to flash that rom zip (aosp or stock) in order to boot
Recovery Zips
H932_Dump.zip [Download]
See Post 2 [Post 2] for what to do if you do NOT have TWRP
See Post 3 [Post 3] if you want to contribute to this thread and backup your device models EMMC for others to be able to recover. ( NO PERSONAL DATA WILL BE USED )
Don´t forget to hit the thanks-button if you like this zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...
#RESERVED1
For those of you that dont have TWRP but have download mode and ADB, you have a second option of just manually running the commands to unbrick.
Step 1 - Make sure you have ADB installed on your computer
Step 2 - Download the zip for your orginal device model
Step 3 - Extract the zip and place all the files into a folder called dump
Step 4 - ADB push the folder to your device ( adb push <file path to dump> /sdcard/ )
Step 5 - Open the update-binary file inside the extracted zip inside META-INF/com/google/android
Step 6 - Run all the make_ext4fs commands in adb shell (adb shell make_ext4fs <partition name>
Step 7 - Run all the write_raw_image commands in adb shell ( NOTE : remove $INSTALLER in your commands and replace write_raw_image with dd ) ( EXAMPLE : adb shell dd if=/sdcard/<partition name> of=/dev/block/bootdevice/by-name/<partition name> )
Step 8 - Once this is done you'll need to reboot and profit.
If any questions about this guide please feel free to tag me and ask and i will help you
thank you
#RESERVED2
Make sure you have enough space on internal storage before flashing the backup zip. You'll likely need 10GB+. this new zip now checks free storage on internal and aborts if not enough. it also now creates a flashable restore zip so now youll have the restore zip internal storage/dump/backup.zip and you can flash this zip when you get a non 9008 brick
Dumps can be done with aosp or custom roms but please try to backup only stock roms if possible. Thanks Everyone!
EDIT: NEW ZIP HAS BEEN ATTACHED.
#RESERVED3
#RESERVED4
I'll be releasing the flashable zip to dump your partitions later today!
Added a flashable backup zip. please flash in twrp and then upload Backup.zip from internal storage Dump folder somewhere and send link here. ill make a restore zip so we can make the v30 almost unbrickable :good:
LG V30 bricked
Hi!
I need your help please, if there is any help... (I hope this is the right thread for my topic)
I got my LG V30 a few days ago (on 8.April 2019, EU version, H930). I schwitched it on and made the initial setup (wifi, region, ...). And the "normal" system update. (I think, it was sec.update from 1.1.2019).
After 2 days I wanted to root the phone. My mistake ....
The steps in short:
1. adb and fastboot installed (on my laptop with Windows 10). I copied SR5-SuperSU-v2.82-SR5-20171001224502.zip into the root of the phone (no sd card in the phone).
2. with adb and fastboot (and LG develpoer account + imiei & co) I managed to unlock with my unlock.bin
3. phone restarted. Since then I see an additional start screen "Lock the bootloader." for 1-2 sec at every start/restart. After this the boot process continues with the standard screen : LG V30 ThinQ powered by Andriod
4. restarting the phone with volume up + power buttons did not funtcion (I gave 4-5 times a try). It never ever succeed for me on this phone. Maybe this is an important point...
5. restarting into the new feature of the phone worked out only with adb reboot bootloader
6. I flashed TWRP in Win10's cmd with fastboot flash recovery recovery.img (I renamed TWRP-3.2.3-7-DataIMG.img to recovery.img)
7. restarting the phone with volume up + power buttons still did not funtcion (I gave it a try 4-5 times)
8. I found this hint : fastboot boot recovery.img. It did the job, TWRP was started (Version 3.2.3-7 DataIMG).
9. I made a backup in TWRP, copied the BACKUP directrory to my laptop. (maybe the only smart thing of me...)
10. TWRP started with fastboot boot recovery.img again
11. in TWRP -> intsall -> SR5-SuperSU-v2.82-SR5-20171001224502.zip selected and the 'restart' option checked.
12. I have seen, that SuRoot....zip was succesful installed (without any errors) and the phone rebooted automatically (it was connected via USB cable to the laptop, but it should not be the problem)
13. since then nothing happens, but the boot screen: for short time the screen with bootlocker text, then only the black screen with LG v30 ThinQ powered by Andriod
I can not boot in to TWRP with volume up + power buttons. This never worked for me. I tried it 20-30 times... :crying:
With volume up + power buttons I can restart, but only the screen with bootlocker text, then only the black screen with LG v30 ThinQ powered by Andriod appiers.
My laptop does not recognise the phone on USB.
Before I destroy the phone with a hammer, any hints?
sicci75 said:
Hi!
I need your help please, if there is any help... (I hope this is the right thread for my topic)
I got my LG V30 a few days ago (on 8.April 2019, EU version, H930). I schwitched it on and made the initial setup (wifi, region, ...). And the "normal" system update. (I think, it was sec.update from 1.1.2019).
After 2 days I wanted to root the phone. My mistake ....
The steps in short:
1. adb and fastboot installed (on my laptop with Windows 10). I copied SR5-SuperSU-v2.82-SR5-20171001224502.zip into the root of the phone (no sd card in the phone).
2. with adb and fastboot (and LG develpoer account + imiei & co) I managed to unlock with my unlock.bin
3. phone restarted. Since then I see an additional start screen "Lock the bootloader." for 1-2 sec at every start/restart. After this the boot process continues with the standard screen : LG V30 ThinQ powered by Andriod
4. restarting the phone with volume up + power buttons did not funtcion (I gave 4-5 times a try). It never ever succeed for me on this phone. Maybe this is an important point...
5. restarting into the new feature of the phone worked out only with adb reboot bootloader
6. I flashed TWRP in Win10's cmd with fastboot flash recovery recovery.img (I renamed TWRP-3.2.3-7-DataIMG.img to recovery.img)
7. restarting the phone with volume up + power buttons still did not funtcion (I gave it a try 4-5 times)
8. I found this hint : fastboot boot recovery.img. It did the job, TWRP was started (Version 3.2.3-7 DataIMG).
9. I made a backup in TWRP, copied the BACKUP directrory to my laptop. (maybe the only smart thing of me...)
10. TWRP started with fastboot boot recovery.img again
11. in TWRP -> intsall -> SR5-SuperSU-v2.82-SR5-20171001224502.zip selected and the 'restart' option checked.
12. I have seen, that SuRoot....zip was succesful installed (without any errors) and the phone rebooted automatically (it was connected via USB cable to the laptop, but it should not be the problem)
13. since then nothing happens, but the boot screen: for short time the screen with bootlocker text, then only the black screen with LG v30 ThinQ powered by Andriod
I can not boot in to TWRP with volume up + power buttons. This never worked for me. I tried it 20-30 times... :crying:
With volume up + power buttons I can restart, but only the screen with bootlocker text, then only the black screen with LG v30 ThinQ powered by Andriod appiers.
My laptop does not recognise the phone on USB.
Before I destroy the phone with a hammer, any hints?
Click to expand...
Click to collapse
Your mistake was not following any of the rooting Instructions in this V30 forum. If you did, you know we don't use SuperSu, we use Magisk. That's probably what messed up your phone.
I understand you obtained an "official" bootloader unlock code from LG for your H930 -- which is not necessary now for almost a year with the WTF exploit -- but you still need to follow the rooting instructions guide.
The unlocked bootloader warning screen is normal. Ignore it, it's just a harmless annoyance. You would have learned that if you read the instructions.
Try manually going into Download mode (power off completely, then hold volume up button while plugging in USB cable) -- if you can, then reflashing most recent full stock H930 KDZ via Dev Patched LGUP in "Refurbish" mode. Dev Patched LGUP is attached to post #1 of that thread.
If/when you recover, your bootloader should still be unlocked, but you'll have install TWRP again and this time use Magisk. Read the WTF instructions, but you can skip the bootloader part, as you've already done that. You can start with Section 6. Read those instructions on a web browser, not an app.
ChazzMatt said:
Try manually going into Download mode (power off completely, then hold volume up button while plugging in USB cable) -- if you can, then reflashing most recent full stock H930 KDZ via Dev Patched LGUP in "Refurbish" mode. Dev Patched LGUP is attached to post #1 of that thread.
Click to expand...
Click to collapse
Thank you for your quick reply!
I'm learning this forum threads, intstuctions and flashing... And I am now preparing for the unbricking.
After installing LGUP, what dev zip files do I need?
LGUP+V30DLL_PATCHED.zip
LGUP_common_DLL_V30_ALLVARIANTS.zip
LGUP_common_OREO.zip
I can take this kdz: H93021w_00_OPEN_EU_OP_0121.kdz, right?
sicci75 said:
Thank you for your quick reply!
I'm learning this forum threads, intstuctions and flashing... And I am now preparing for the unbricking.
After installing LGUP, what dev zip files do I need?
LGUP+V30DLL_PATCHED.zip
LGUP_common_DLL_V30_ALLVARIANTS.zip
LGUP_common_OREO.zip
I can take this kdz: H93021w_00_OPEN_EU_OP_0121.kdz, right?
Click to expand...
Click to collapse
Are you able to get into Download mode?
You want the "patched" version, but be sure to read the installation instructions.
Yes, you can use that KDZ.
If for some reason your bootloader is not still unlocked, you can run your code again.
ChazzMatt said:
Are you able to get into Download mode?
Click to expand...
Click to collapse
Yessss!!After reading very focused the guidelines you mentioned, it was everything fine.
Thank you!
sicci75 said:
Yessss!!After reading very focused the guidelines you mentioned, it was everything fine.
Thank you!
Click to expand...
Click to collapse
Glad to help.
Sent via open market LG US998 V30/V30+
So just uploaded a new zip in post 3. this new zip now checks for free space and will abort if theres not enough to create the backup and flashable restore zip. need at least 10GB in Internal Storage. the zip will now create automatically a flashable restore zip :good: i designed this around the v30 but in theory it should be able to work on all qualcomm devices and maybe even some other SoCs as well. but this has not been tested on other devices. ive fully tested this on my ls998 and everything works great! Enjoy!
john, did i ever tell you, that i like your work and efforts? good man! :good:
Lg v30 h932 brick
Hello, I need your help.
My LG V30 H932 phone is left as a BRICK after installing an erroneous kdz, it does not enter download mode or emergency mode, is there any way to revive it?
JohnFawkes said:
#RESERVED1
For those of you that dont have TWRP but have download mode and ADB, you have a second option of just manually running the commands to unbrick.
Step 1 - Make sure you have ADB installed on your computer
Step 2 - Download the zip for your orginal device model
Step 3 - Extract the zip and place all the files into a folder called dump
Step 4 - ADB push the folder to your device ( adb push <file path to dump> /sdcard/ )
Step 5 - Open the update-binary file inside the extracted zip inside META-INF/com/google/android
Step 6 - Run all the make_ext4fs commands in adb shell (adb shell make_ext4fs <partition name>
Step 7 - Run all the write_raw_image commands in adb shell ( NOTE : remove $INSTALLER in your commands and replace write_raw_image with dd ) ( EXAMPLE : adb shell dd if=/sdcard/<partition name> of=/dev/block/bootdevice/by-name/<partition name> )
Step 8 - Once this is done you'll need to reboot and profit.
If any questions about this guide please feel free to tag me and ask and i will help you
thank you
Click to expand...
Click to collapse
---------- Post added at 03:26 AM ---------- Previous post was at 03:23 AM ----------
My LG V30 H932 phone is left as a BRICK after installing an erroneous kdz, it does not enter download mode or emergency mode, is there any way to revive it?
It was a big mistake and I don't know what to do, my phone does nothing, totally dead
JohnFawkes said:
#RESERVED1
For those of you that dont have TWRP but have download mode and ADB, you have a second option of just manually running the commands to unbrick.
Step 1 - Make sure you have ADB installed on your computer
Step 2 - Download the zip for your orginal device model
Step 3 - Extract the zip and place all the files into a folder called dump
Step 4 - ADB push the folder to your device ( adb push <file path to dump> /sdcard/ )
Step 5 - Open the update-binary file inside the extracted zip inside META-INF/com/google/android
Step 6 - Run all the make_ext4fs commands in adb shell (adb shell make_ext4fs <partition name>
Step 7 - Run all the write_raw_image commands in adb shell ( NOTE : remove $INSTALLER in your commands and replace write_raw_image with dd ) ( EXAMPLE : adb shell dd if=/sdcard/<partition name> of=/dev/block/bootdevice/by-name/<partition name> )
Step 8 - Once this is done you'll need to reboot and profit.
If any questions about this guide please feel free to tag me and ask and i will help you
thank you
Click to expand...
Click to collapse
---------- Post added at 04:04 AM ---------- Previous post was at 03:26 AM ----------
Hello, I need your help.
My LG V30 H932 phone is left as a BRICK after installing an erroneous kdz, it does not enter download mode or emergency mode, is there any way to revive it?!!!
JohnFawkes said:
LG V30 Recovery UnBrick Zips
So as some of you are aware, I released a h932 rom that soft bricked a few devices. well in the process of that I (with @runningnak3d help) figured out a way to unbrick those devices. As long as you have TWRP or download mode with ADB then you can unbrick. These zips here are NOT meant to be flashed to just flash. These zips are for those people that have a non 9008 brick only! DO NOT FLASH THESE ZIPS OR RUN THESE COMMANDS FOR ANY REASON EXCEPT FOR A NON 9008 BRICK! DO NOT FLASH OR RUN THIS COMMANDS BECAUSE YOU HAVE A BOOTLOOP! ONLY FOLLOW THIS THREAD FOR NON 9008 BRICKS! PLEASE BE SMART!
Now on to the good stuff.......
Only download and flash the zip made for your original device model. Do NOT flash whatever your converted too. for example i have a ls998 converted to us998. I would flash the ls998 THEN convert to us998 later on...
NOTE: After flashing the unbrick zip for your model youll need to have a rom zip on your sdcard or internal storage. You'll need to flash that rom zip (aosp or stock) in order to boot
Recovery Zips
H932_Dump.zip [Download]
See Post 2 [Post 2] for what to do if you do NOT have TWRP
See Post 3 [Post 3] if you want to contribute to this thread and backup your device models EMMC for others to be able to recover. ( NO PERSONAL DATA WILL BE USED )
Don´t forget to hit the thanks-button if you like this zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...
Click to expand...
Click to collapse
robertojha said:
Hello, I need your help.
My LG V30 H932 phone is left as a BRICK after installing an erroneous kdz, it does not enter download mode or emergency mode, is there any way to revive it?
Click to expand...
Click to collapse
You tried to cross flashed another variant stock KDZ over your T-Mobile H932? Not sure why you would do that, but normally that results in 9008 brick which needs remote viewer Octoplus help to recover.
Lg v30 h932 brick
I was following a guide and installed a kdz different from the original of my phone, and now I have no download mode or emergency mode, it's totally a brick,...
ChazzMatt said:
You tried to cross flashed another variant stock KDZ over your T-Mobile H932? Not sure why you would do that, but normally that results in 9008 brick which needs remote viewer Octoplus help to recover.
Click to expand...
Click to collapse
ChazzMatt said:
You tried to cross flashed another variant stock KDZ over your T-Mobile H932? Not sure why you would do that, but normally that results in 9008 brick which needs remote viewer Octoplus help to recover.
Click to expand...
Click to collapse
From what I know, there is no fire hose for the H932.
Sent from my LG-H932 using XDA Labs
---------- Post added at 02:40 PM ---------- Previous post was at 02:37 PM ----------
robertojha said:
I was following a guide and installed a kdz different from the original of my phone, and now I have no download mode or emergency mode, it's totally a brick,...
Click to expand...
Click to collapse
I don't think think there is any guide that says to do this. If there was, @ChazzMatt would have gotten it shut down.
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
From what I know, there is no fire hose for the H932.
Click to expand...
Click to collapse
Ah, yeah you're right.
---------- Post added at 03:33 PM ---------- Previous post was at 02:43 PM ----------
BROKEN1981 said:
I don't think think there is any guide that says to do this. If there was, @ChazzMatt would have gotten it shut down.
Click to expand...
Click to collapse
The T-Mobile root guide does say flash the LAF partition of the H933. But only the LAF partition. Some people do not pay attention and flash the entire H933 kdz over the T-Mobile H932 and brick their phone.
Just had a guy in the Frankenstein thread who said he followed instructions. I didn't believe, told him so, and asked him to tell me step-by-step what he did... Turns out rather than flash US998 Nougat, then Master Reset, then Oreo of choice -- he flashed 20f (Oreo), Master Reset, 20g Oreo.
I asked him why he did that. He said US998 20f was Nougat. That's like saying a banana is an apple. "10" is Nougat, "20" is Oreo. Plus, in my instructions I have specific download links to all requisite firmware, which he ignored.
He said he downloaded KDZ from LG-Firmwares website who told him US998 20f was Nougat -- which they didn't. But even if they did, who cares? You're following MY instructions, so use my download links. Once he downloaded actual Nougat from my download link -- hey that worked!
Also use the Dev Patched LGUP which I recommend. Some guy over the telegram thread said he was following my instructions, but used Uppercut. Of course that's going to fail. None of my instruction mention Uppercut and never will because it doesn't work on Oreo or later and conflicts with Dev Patched LGUP. I always include the specific version of Dev Patched LGUP you should be using. (The Dev for Uppercut is amazing, but it just doesn't work on our phones past Nougat. If it's NOT in the Instructions, don't use it.)
This isn't a recipe where you can substitute your own ingredients.
You need to read carefully and pay attention.
I'm happy to help -- but while some people's problems are quite preventable, once occurred may not be fixable.
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile Stock 10.0.8 to Rooted Global Firmware.
Please take the time to read every step carefully. It'll explain a little bit as to the why behind some of the steps. PM me if I've missed anything.
This has been revamped as some of the steps are no longer required. Devices coming from 10.0.6 and below might have to try a different set of steps. Click here for the post with the old instructions
Requirements:
ADB setup and working
Global Fastboot ZIP Grab the latest version (10.0.8 as of 3/20)
For Root:
Magisk Canery apk
Modded-Boot.img From here or make your own pulling your own boot.img and using magisk to create a modded boot.img file
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
This group of instructions are going to walk you through on how to unlock your bootloader. This is the first general step in converting your device into a global device.
1. Either follow the rules via T-Mobile (paid off and 40 days on the network) or visit this thread and get the hook up from our friend (send him some cash, for real I did this and it worked hopefully he keeps up with this for a while!). This will allow you to use the Unlock App to permanently unlock your phone.
2. Open the "Unlock" app that's preinstalled on your phone and click on Permanent Unlock. If you have completed Step One correctly, it'll congratulate you and ask you to reboot your phone.
3. Reboot your phone and Enable Developer Settings. Check out the OEM Unlock button is now able to be switched off. Switch it off.
4. Be sure to also tick USB Debugging.
5. You'll now need to submit a request for an unlock_code.bin (could also be labeled unlock_token.bin) file from OnePlus via this link. It takes a week. Seriously almost down to the second. There's no avoiding this. I've read several people try (myself included) all met with the same fate. Wait. 7 whole days. You'll get an email from OnePlus containing the unlock_code.bin file. Download this file and save it to your ADB folder.
5a. Open CMD (with admin rights) and navigate to your ADB folder. I've heard users try to use Powershell and while it works mostly, ymmv. I stick with CMD and haven't had any issues.
Mine would be--
Code:
cd c:\adb\
6. Reboot your phone into fastboot--
Code:
adb reboot bootloader
Code:
fastboot flash cust-unlock unlock_code.bin
Code:
fastboot oem unlock
This will unlock your bootloader and wipe your device
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
Now that you've unlocked your bootloader, lets get to flashing the Global Rom--
7. Extract the contents of the Global Fastboot Rom zip folder directly into your ADB folder.
a. If you did this correctly your ADB folder will be filled with a bunch of new .img files. Like boot.img8. Open CMD (with admin rights) and navigate to your ADB folder. I've heard users try to use Powershell and while it works mostly, ymmv. I stick with CMD and haven't had any issues.
Mine would be--
Code:
cd c:\adb\
This will also wipe your data, be sure to save anything that you need prior to running the following command.
Code:
flash-all.bat
9. If you've never flashed via fastboot before, this is going to spit a bunch of information to you that might look like garbage. Your phone will boot a few different times including into FastbootD (link for explanation) But it's telling you what it's flashing and how fast it's doing it. There's a common looking error that happens every time you do this. It says "Invalid sparce file format at header magic". This is normal, just ignore it and keep waiting. Once everything settles, the device will reboot by itself. If it doesn't, like bootloops to the bootloader, start over and go back to Step 8 and try again.
10. You've now fully converted to the Global Firmware. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.8(as of the time of this post).
You're done! Continue on if you want to root your device...
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
If you're interested in root:
11. Boot the device from the modded-boot.img file to give your self temp root. Once this is done, boot the device.
Code:
adb reboot bootloader
fastboot boot modded-boot.img
12. Install Magisk Manager Canary from here
13. Check in the middle of the screen for "advanced options" and make sure Preserve force encryption and preserve avb 2.0/dm-verify are checked.
14. Now look under the first Magisk check and make sure that it's telling you there's an update to "Magisk" and run through that update via direct install.
15. Once that finishes it'll have you reboot the phone.
16. You've now fully converted to the Global Firmware and Rooted. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.8(as of the time of this post)
=-=-=-=-=-=-=-=-=-=-=-=
Shoutouts will go here soon.
nolimit78 said:
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. This will be a living first post as I'm currently not able to successfully get rooted. The idea of this thread is going from 100% T-Mobile Stock to Rooted Global Firmware. Once I can replicate and get root stable on my phone I will finalize this post. I will also add in shout outs to where I pulled this information from, both thread post and user, as it was through our group that I was able to piece this together. All this will be updated and make to look nice later.
The reason we flash to Indian and then Global is because if you don't, wifi/data and camera will be broken. I can't explain why it works, it just does.
Ok. Now to the good stuff. Please take the time to read every step carefully. It'll explain a little bit as to some of the why behind the steps. PM me if I've missed anything.
Requirements:
ADB setup and working
Global OTA ZIP (download from here)
Indian Fastboot ROM(download from here)
1. Unlock your bootloader. Either follow the rules via T-Mobile (paid off and 40 days on the network) or visit this thread and get the hook up from our friend (send him some cash, for real I did this and it worked hopefully he keeps up with this for a while!).
2. Move the Global Rom.zip file to the root of your OnePlus7T. It'll save you time later. Do this now or there's a later step where I give you the chance.
2. Open the "Unlock" app that's preinstalled on your phone and click on Permanent Unlock. If you have completed Step One correctly, it'll congratulate you and ask you to reboot your phone.
3. Reboot your phone and Enable Developer Settings. Check out the OEM Unlock button is now able to be switched off. Switch it off.
4. Be sure to also tick USB Debugging.
4. You'll now need to submit a request for an unlock_code.bin file from OnePlus via this link. It takes a week. Seriously almost down to the second. There's no avoiding this. I've read several people try (myself included) all met with the same fate. Wait. 7 whole days. You'll get an email from OnePlus containing the unlock_code.bin file. Download this file and save it to your ADB folder.
5. Reboot your phone into fastboot adb reboot bootloader
6. Extract the Indian Fastboot Rom folder directly into your ADB folder.
a. If you did this correctly your ADB folder will be filled with a bunch of new .img files. Like boot.img
7. Open CMD (with admin rights) and navigate to your ADB folder.
Mine would be-- cd c:\adb\
8. flash-all.bat
9. It will also ask you to wipe data. This is your call. If you followed Step 2, this will wipe out this file and you'll need to replace it once your phone has converted.
9. If you've never flashed via fastboot before, this is going to spit a bunch of information to you that might look like garbage. But it's telling you what it's flashing and how fast it's doing it. There's a common looking error that happens every time you do this. It says []. This is normal, just ignore it. Once everything settles, the device will reboot by itself. If it doesn't, start over and go back to Step 5 and try again.
10. Once the device boots up, you should now be on the Indian build for the OnePlus 7T.
11. You should have already moved the Global OTA to the root of the OnePlus 7t. If you haven't, do so now.
12. Go to settings > system updates and look for the gear on the top right-hand corner. If it's not there, something didn't flash right. Go Back to Step 2 and try again. Click on it and select Local Upgrade
13. Select the Global OTA file and it'll start to flash from within the update app.
14. Once that finishes it'll have you reboot the phone.
15. You've now fully converted to the Global Firmware. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.6(as of the time of this post, I'll try to update this as I can)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--==
This is where we should be able to root. Once I can verify getting this setup and replicate it I will continue with the tutorial. Hopefully, everyone who reads this will find it helpful.
Click to expand...
Click to collapse
I'm having a issue when inflash globel my phone stays on Indian firmware
Are we 100% sure that WiFi/Data/Camera will be broken if you just go straight to Global? Because just this morning I flashed from TMO 10.0.4 to Global 10.0.6 using the fastboot flashable ROM with perfect VoLTE/WiFi/Camera...
Also fully rooted!
Edit: Updated to 10.0.7, kept root via Magisk Manager install to inactive slot.
Reserved for old instructions. Going from 10.0.7 and up the instructions were changed and certain steps weren't needed, like flashing Indian before Global.
Keeping these here just in case someone purchases a phone with older firmware and doesn't want to wait updating to the latest version.
Requirements:
ADB setup and working
Global OTA ZIP (grab the 10.0.6 from here)
Updated 10.0.7 OTA Build from hereas well
Indian Fastboot ROM(grab the latest from here)
Pre-Rooted 10.0.6 boot.img file here
Magisk Canery apk
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
This group of instructions are going to walk you through on how to unlock your bootloader. This is the first general step in converting your device into a global device.
1. Either follow the rules via T-Mobile (paid off and 40 days on the network) or visit this thread and get the hook up from our friend (send him some cash, for real I did this and it worked hopefully he keeps up with this for a while!). This will allow you to use the Unlock App to permanently unlock your phone.
2. Open the "Unlock" app that's preinstalled on your phone and click on Permanent Unlock. If you have completed Step One correctly, it'll congratulate you and ask you to reboot your phone.
3. Reboot your phone and Enable Developer Settings. Check out the OEM Unlock button is now able to be switched off. Switch it off.
4. Be sure to also tick USB Debugging.
5. You'll now need to submit a request for an unlock_code.bin file from OnePlus via this link. It takes a week. Seriously almost down to the second. There's no avoiding this. I've read several people try (myself included) all met with the same fate. Wait. 7 whole days. You'll get an email from OnePlus containing the unlock_code.bin file. Download this file and save it to your ADB folder.
6. Reboot your phone into fastboot--
Code:
adb reboot bootloader
Code:
fastboot oem unlock
This will unlock your bootloader and wipe your device
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
Now that you've unlocked your bootloader, lets get to flashing the Global Rom--
7. Extract the contents of the Indian Fastboot Rom zip folder directly into your ADB folder.
a. If you did this correctly your ADB folder will be filled with a bunch of new .img files. Like boot.img8. Open CMD (with admin rights) and navigate to your ADB folder. I've heard users try to use Powershell and while it works mostly, ymmv. I stick with CMD and haven't had any issues.
Mine would be--
Code:
cd c:\adb\
This will also wipe your data, be sure to save anything that you need prior to running the following command.
Code:
flash-all.bat
10. If you've never flashed via fastboot before, this is going to spit a bunch of information to you that might look like garbage. Your phone will boot a few different times including into FastbootD (link for explanation) But it's telling you what it's flashing and how fast it's doing it. There's a common looking error that happens every time you do this. It says "Invalid sparce file format at header magic". This is normal, just ignore it and keep waiting. Once everything settles, the device will reboot by itself. If it doesn't, like bootloops to the bootloader, start over and go back to Step 5 and try again.
11. Once the device boots up, you should now be on the Indian build for the OnePlus 7T.
12. Be sure to copy the Global OTA to the root storage of your OnePlus 7T. If you haven't, do so now.
13. Reboot the phone and boot the Modded-boot.img file from the bootloader
Code:
adb reboot bootloader
fastboot boot modded-boot.img
14. Once the phone boots up, you should now have temp root. Go to settings > system updates and look for the gear on the top right-hand corner. If it's not there, something didn't flash right. Go Back to Step 2 and try again. Click on it and select Local Upgrade
15. Select the Global OTA file and it'll start to flash from within the update app. Let this finish before proceeding.
16. Install Magisk Manager Canary from here
17. Check in the middle of the screen for "advanced options" and make sure Preserve force encryption and preserve avb 2.0/dm-verify are checked.
18. Now look under the first Magisk check and make sure that it's telling you there's an update to "Magisk" and run through that update via direct install.
19. Once that finishes it'll have you reboot the phone.
20. You've now fully converted to the Global Firmware and Rooted. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.6(as of the time of this post, I'll try to update this as I can)
If you'd like to update to 10.0.7:
1. Download and move the OTA file for 10.0.7 to the root of your OP7T
2. Go to Settings > System > System Updates and look for the gear in the top right.
3. Select Local upgrade and select the update file for 10.0.7.
4. Let it run through and finish, don't reboot.
5. Open Magisk Manager
6. Update and select direct install to inactive boot partition to update.
7. Once this finishes, reboot and you're now on 10.0.7 rooted.
=-=-=-=-=-=-=-=-=-=-=-=
nolimit78 said:
Yup, tried to be slick by going straight to Global and ran into this problem. Data worked for me but Camera was super unstable and Wifi was the only solid no that I got. Required more research to discover that this issue is avoided by flashing the indian rom first.
Tell me more about this. What steps did you take to do this? I'm thinking that once you flash the global ROM to reboot, and then use the a image-new.img that boots a temp-magisk to then use magisk canary to install magisk on the inactive slot (should be a right?)
Click to expand...
Click to collapse
Hmm I'll watch and see if my Camera is unstable but it seems fine so far.
To root I flashed (not booted) a 10.0.6 Magisk patched boot img (fastboot flash boot patched_boot.img) that someone posted in the "how to patch boot with Magisk" thread and installed Magisk Manager Canary.
I used Oxygen Updater to local update to 10.0.7 (it says 10.3.0 because of a typo from OnePlus, see another thread. It says 10.0.7 in settings) but make sure to download the full 2gb update not the 200 something mb incremental one because it will fail.
Then when the update is done, don't hit reboot, go to Magisk Manager, make sure you're set to the Canary channel (unless you patched the boot img yourself with something else) and install and choose inactive slot. Then you can hit reboot in Magisk.
Perfect, means I was thinking correctly with an extra unneeded reboot. Updated info in OP.
Just now noticed this thread so I'll crosspost my applicable results from the MSM thread https://forum.xda-developers.com/showpost.php?p=81227253&postcount=113
I want to share my experience in case it might help someone else as I was quite confused for a while over the past few weeks trying to get off tmobile slow updates.
I can also confirm jumping straight from tmobile 10.0.4 to global 10.0.6 works. I didn't have the 10.0.7/10.3.0 downloaded and I have slow internet so I can't say if that would work but I have upgraded to it since via oxygen updater.
Basic steps how I got there is, assuming you know how to do stuff like enable dev mode and usb debugging
-sim unlock https://forum.xda-developers.com/oneplus-7t/how-to/t-mobile-free-op7t-sim-unlocking-t4014053
-request bootloader unlock token and wait 7 days https://www.oneplus.com/unlock_token
-unlock bootloader
-get fastboot rom https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
-use all in one tool to flash flashboot rom https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
I told the AIO tool I had a oneplus 7 (7T not an option) and did "flash factory images", and chose wipe and reboot to be safe and just waited until the phone came back to factory setup screen
that's it. oxygen updater incremental update failed for 10.0.7/10.3.0 but full worked fine, I've never used oxygen updater until now so idk if that is fairly normal or not. VoLTE works, WiFi calling, etc all seem to be working as far as I can tell (although it seems the global doesn't have the quick select option to disable wifi calling like the tmobile rom did).
I've also now installed Magisk Canary, patched boot img and have certified play store now and google pay is fully functional and I have used camera for mobile banking deposit. Still no issues with wifi, camera, anything
Once converted to Global oos, will it support Dual SIM?
ysfk7 said:
Once converted to Global oos, will it support Dual SIM?
Click to expand...
Click to collapse
Yes it will support dual SIM as long as you have the dual SIM tray.
rgreen83 said:
Just now noticed this thread so I'll crosspost my applicable results from the MSM thread https://forum.xda-developers.com/showpost.php?p=81227253&postcount=113
I want to share my experience in case it might help someone else as I was quite confused for a while over the past few weeks trying to get off tmobile slow updates.
I can also confirm jumping straight from tmobile 10.0.4 to global 10.0.6 works. I didn't have the 10.0.7/10.3.0 downloaded and I have slow internet so I can't say if that would work but I have upgraded to it since via oxygen updater.
Basic steps how I got there is, assuming you know how to do stuff like enable dev mode and usb debugging
-sim unlock https://forum.xda-developers.com/one...cking-t4014053
-request bootloader unlock token and wait 7 days https://www.oneplus.com/unlock_token
-unlock bootloader
-get fastboot rom https://forum.xda-developers.com/one...us-7t-t3979213
-use all in one tool to flash flashboot rom https://forum.xda-developers.com/and...ctory-t3358711
I told the AIO tool I had a oneplus 7 (7T not an option) and did "flash factory images", and chose wipe and reboot to be safe and just waited until the phone came back to factory setup screen
that's it. oxygen updater incremental update failed for 10.0.7/10.3.0 but full worked fine, I've never used oxygen updater until now so idk if that is fairly normal or not. VoLTE works, WiFi calling, etc all seem to be working as far as I can tell (although it seems the global doesn't have the quick select option to disable wifi calling like the tmobile rom did).
I've also now installed Magisk Canary, patched boot img and have certified play store now and google pay is fully functional and I have used camera for mobile banking deposit. Still no issues with wifi, camera, anything
Click to expand...
Click to collapse
FYI link to fastboot rom is broken.
Crappyvate said:
FYI link to fastboot rom is broken.
Click to expand...
Click to collapse
Sorry bout that, crosspost fail
Crappyvate said:
FYI link to fastboot rom is broken.
Click to expand...
Click to collapse
I clicked on it and it worked, but I didn't check through mobile. Can you show me what happens when you try?
There is no link to request unlock file from OnePlus. Also will regular global OTA updates work? Or will I have to manually update every time?
Will this work for McLaren 5g?
I just followed the instructions in post#7 and was able to do this successfully as well (direct Tmobile->Global, without the Indian version flash in between). Note that the phone will reboot sometime in the middle of the flash, do NOT manually go into the phone and reboot yet again, just wait for it to complete.
Is waiting around for OnePlus to send you an unlock token really necessary to unlock the bootloader? I ask this because it's not necessary on the OP7 with the use of the MSM Tool (https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947) Would this tool work on the OP7T or does it need its own?
tkoreaper said:
Is waiting around for OnePlus to send you an unlock token really necessary to unlock the bootloader? I ask this because it's not necessary on the OP7 with the use of the MSM Tool (https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947) Would this tool work on the OP7T or does it need its own?
Click to expand...
Click to collapse
Yes, unfortunately the loophole that let this work on the 6T and 7 was corrected for the 7T+
cm0002 said:
Yes, unfortunately the loophole that let this work on the 6T and 7 was corrected for the 7T+
Click to expand...
Click to collapse
i guess thats why i can unlock the bootloader and convert the Tmo 6T without asking the unlock_code.bin from oneplus. thank you kindly for the info
I got the unlock bin today I just flashed via fastboot received message the bootloader is unlocked, but the device status still states locked?
nolimit78 said:
...
4. Reboot your phone and Enable Developer Settings. Check out the OEM Unlock button is now able to be switched off. Switch it off.
...
Click to expand...
Click to collapse
So OEM Unlock button suppose to be OFF or ON?
Hi, everyone. A very desperate owner over here...So, I am having no response from my Redmi Note 8 Pro. I unlocked bootloader, flashed the "lk" and "preloader" files to prevent hard brick. Then I flashed recovery.img from LR Team. I formatted the data and flashed the latest version of MIUI 11 for Europe (miui_BEGONIAEEAGlobal_V11.0.2.0.QGGEUXM_a13b9653ba_10.0). Everything went without problems. I went back (didn't restart) to recovery, and I chose the "install root" option and flashed Magisk. After that, I restarted the phone. But then the problems started with the phone bootlooping. So, I thought, I'm gonna do all these steps without the "Install root" to see if anything changes. So I flashed "lk" and "preloader" (just to be sure), and I flashed the recovery. After that phone doesn't even bootloop. It just vibrates vey shortly if I hold volume+ and power. No panic just yet, I go to SP Flash Tool, load the firmware scatter file and I press "download". But the tool gives me an error "status-brom_cmd_send_da_fail (0xC0060003)". I have tried different usb ports, changed the usb cable, different button combinations, changed between MTK_AllInOne_DA. bin and DA_PL.bin but without success. So I'm asking you all is there some step that I am missing? Because I have been all over XDA these last couple of days and no solution is working for me.
*******************Update 03/13/20********************
So I have managed to unbrick my RN8P. It was dead, without fastboot or any other way to connect. Except for SP Flash Tool. But I had no success to connect my phone in a way that would allow to flash the stock firmware. The SPF Tool kept giving me the "status-brom_cmd_send_da_fail (0xC0060003)" error. So, with my final effort I tried the steps that are explained in this thread https://forum.xda-developers.com/redmi-note-8-pro/help/redmi-note-8-pro-bricked-t3976289/page4 (the last post on the page) . First I downloaded Miflash Pro from here https://androidfilehost.com/?fid=4349826312261688231 . It's in Italian, but don't worry, you just need to use a few functions within the program.
1. Once you have installed Miflash, open it.
2. Switch over to the 'Flash MTK' tab.
2. Load your firmware (I used this page to download mine https://c.mi.com/oc/miuidownload/detail?device=1900375 - European Version)
3. Choose Download Agent ( for example C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\MTK_AllInOne_DA_mt6785_mt6765.bin, your path coud be different)
4. Load scatter file (my example - C:\Users\your_username\Downloads\begoniav11030eea\images, it should be in the 'images' folder)
5. Click on 'Download'.
6. Connect your bricked phone
7. Now this step might work for you without pressing any buttons, as that was the case with me. But you could try pressing Volume - or Voulume + while connecting with the computer.
That's it. The flashing took about 5 minutes, but my phone was resurrected. BEAR IN MIND that before this hard brick happened, I did flash the files that were leaked a few weeks ago that permitted the use of SP Flash Tool without an authorised Mi account- the 'preloader' and 'lk' file. But I did flash an android 10 based firmware on top of it. As suggested by some senior members on this thread, by flashing an Android 10 ROM, I overwrote the 'preloader' and 'lk' files, therefore losing the option to flash with SP Flash Tool without an authorised account. But, the bottom line is, this method worked for me. So maybe it might work for you. And if you have a hard bricked Redmi Note 8 Pro, that doesn't have a previously flashed 'preloader' and 'lk' files, please, do try this method. If it works, then great, we just might have resolved some issues with hard bricking of this device.
Preloader only works o Pie, and if you flashed miui Android 10 the preloader partition was over wrote...
Excuse my bad English
djzero86 said:
Preloader only works o Pie, and if you flashed miui Android 10 the preloader partition was over wrote...
Excuse my bad English
Click to expand...
Click to collapse
From what I understood, you have to be on android 9 when flashing preloader. After that one can flash other ROM versions. Or am I wrong?
avdo06 said:
From what I understood, you have to be on android 9 when flashing preloader. After that one can flash other ROM versions. Or am I wrong?
Click to expand...
Click to collapse
Nope, if you flash a rom that contain those partitions it will be over writed.
Read carefully the instructions, the dev remark this point clearly in the mega post
In the past, I would edit the updater script to remove whichever partition updates I didn't want, such as boot.
Does that work with MIUI 11? I guess I could try it out, only flash the system partition and see what happens. Anyone else try?
OP, did you flash both preloader, lk and lk2 before rebooting?
Try this:
I was in a similar situation. I unbricked my phone by downloading the SP flash tools with the DA file specifically for the MT6785 (The note 8 pro's chip). here's the link to download it: https[colon]//easyfirmwares[dot]com/index.php?a=downloads&b=file&id=603
Just extract and follow the directions to unbrick your device on the megathread. Hopefully this helps.
* Also, this won't work if you don't have the preloader and lk images flashed, as said in the megthread. *
edit: Replace [colon] with " : " and [dot] with " . "
I pulled my phone back from the dead. I read in a thread somewhere that this guy had the same situation as me. He downloaded miflash pro (black icon). So I did the same. There is a tab inside miflash for sp flash tool. When I connected my phone it immediately started flashing. The phone rebooted with the firmware I chose ( which is 11.0.3.0 PGGEUXM). Since this thread is from last year (when I have more time I'll post the link here), I think that it MIGHT work for bricked RN8P's that don't have the preloader/lk files flashed. But it's just a thought. Anyway, like I said, my phone was dead, wasn't reacting to anything, I had no fastboot and SP Flash Tool that I had downloaded from the official website kept giving me errors each time I connected with USB. It could be that particular versions of SP Flash had some misunderstandings with my PCs (tried two PCs and three versions of the SP tool). I was so desperate and I had already ordered a Redmi Note 8T from Amazon. But then I read this post and it worked! :silly: :laugh:
i need an auth. mi account to flash my firmware back. can anyone help me please?
avdo06 said:
Hi, everyone. A very desperate owner over here...So, I am having no response from my Redmi Note 8 Pro. I unlocked bootloader, flashed the "lk" and "preloader" files to prevent hard brick. Then I flashed recovery.img from LR Team. I formatted the data and flashed the latest version of MIUI 11 for Europe (miui_BEGONIAEEAGlobal_V11.0.2.0.QGGEUXM_a13b9653ba_10.0). Everything went without problems. I went back (didn't restart) to recovery, and I chose the "install root" option and flashed Magisk. After that, I restarted the phone. But then the problems started with the phone bootlooping. So, I thought, I'm gonna do all these steps without the "Install root" to see if anything changes. So I flashed "lk" and "preloader" (just to be sure), and I flashed the recovery. After that phone doesn't even bootloop. It just vibrates vey shortly if I hold volume+ and power. No panic just yet, I go to SP Flash Tool, load the firmware scatter file and I press "download". But the tool gives me an error "status-brom_cmd_send_da_fail (0xC0060003)". I have tried different usb ports, changed the usb cable, different button combinations, changed between MTK_AllInOne_DA. bin and DA_PL.bin but without success. So I'm asking you all is there some step that I am missing? Because I have been all over XDA these last couple of days and no solution is working for me.
*******************Update 03/13/20********************
So I have managed to unbrick my RN8P. It was dead, without fastboot or any other way to connect. Except for SP Flash Tool. But I had no success to connect my phone in a way that would allow to flash the stock firmware. The SPF Tool kept giving me the "status-brom_cmd_send_da_fail (0xC0060003)" error. So, with my final effort I tried the steps that are explained in this thread https://forum.xda-developers.com/redmi-note-8-pro/help/redmi-note-8-pro-bricked-t3976289/page4 (the last post on the page) . First I downloaded Miflash Pro from here https://androidfilehost.com/?fid=4349826312261688231 . It's in Italian, but don't worry, you just need to use a few functions within the program.
1. Once you have installed Miflash, open it.
2. Switch over to the 'Flash MTK' tab.
2. Load your firmware (I used this page to download mine https://c.mi.com/oc/miuidownload/detail?device=1900375 - European Version)
3. Choose Download Agent ( for example C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\MTK_AllInOne_DA_mt6785_mt6765.bin, your path coud be different)
4. Load scatter file (my example - C:\Users\your_username\Downloads\begoniav11030eea\images, it should be in the 'images' folder)
5. Click on 'Download'.
6. Connect your bricked phone
7. Now this step might work for you without pressing any buttons, as that was the case with me. But you could try pressing Volume - or Voulume + while connecting with the computer.
That's it. The flashing took about 5 minutes, but my phone was resurrected. BEAR IN MIND that before this hard brick happened, I did flash the files that were leaked a few weeks ago that permitted the use of SP Flash Tool without an authorised Mi account- the 'preloader' and 'lk' file. But I did flash an android 10 based firmware on top of it. As suggested by some senior members on this thread, by flashing an Android 10 ROM, I overwrote the 'preloader' and 'lk' files, therefore losing the option to flash with SP Flash Tool without an authorised account. But, the bottom line is, this method worked for me. So maybe it might work for you. And if you have a hard bricked Redmi Note 8 Pro, that doesn't have a previously flashed 'preloader' and 'lk' files, please, do try this method. If it works, then great, we just might have resolved some issues with hard bricking of this device.
Click to expand...
Click to collapse
I can access my fastboot but how do i flash stock rom ? Prior to this i was able to flash global version but got brick when i install twrp
If i flash a different rom it just says anti rollback
By the way my unit is china variant any response will be apperciated
I have eea 11.0.2.0 android 10 and the twrp is diferent than android 9...
Test with this version of twrp..... https://forum.xda-developers.com/showpost.php?p=82062075&postcount=7
avdo06 said:
Hi, everyone. A very desperate owner over here...So, I am having no response from my Redmi Note 8 Pro. I unlocked bootloader, flashed the "lk" and "preloader" files to prevent hard brick. Then I flashed recovery.img from LR Team. I formatted the data and flashed the latest version of MIUI 11 for Europe (miui_BEGONIAEEAGlobal_V11.0.2.0.QGGEUXM_a13b9653ba_10.0). Everything went without problems. I went back (didn't restart) to recovery, and I chose the "install root" option and flashed Magisk. After that, I restarted the phone. But then the problems started with the phone bootlooping. So, I thought, I'm gonna do all these steps without the "Install root" to see if anything changes. So I flashed "lk" and "preloader" (just to be sure), and I flashed the recovery. After that phone doesn't even bootloop. It just vibrates vey shortly if I hold volume+ and power. No panic just yet, I go to SP Flash Tool, load the firmware scatter file and I press "download". But the tool gives me an error "status-brom_cmd_send_da_fail (0xC0060003)". I have tried different usb ports, changed the usb cable, different button combinations, changed between MTK_AllInOne_DA. bin and DA_PL.bin but without success. So I'm asking you all is there some step that I am missing? Because I have been all over XDA these last couple of days and no solution is working for me.
*******************Update 03/13/20********************
So I have managed to unbrick my RN8P. It was dead, without fastboot or any other way to connect. Except for SP Flash Tool. But I had no success to connect my phone in a way that would allow to flash the stock firmware. The SPF Tool kept giving me the "status-brom_cmd_send_da_fail (0xC0060003)" error. So, with my final effort I tried the steps that are explained in this thread https://forum.xda-developers.com/redmi-note-8-pro/help/redmi-note-8-pro-bricked-t3976289/page4 (the last post on the page) . First I downloaded Miflash Pro from here https://androidfilehost.com/?fid=4349826312261688231 . It's in Italian, but don't worry, you just need to use a few functions within the program.
1. Once you have installed Miflash, open it.
2. Switch over to the 'Flash MTK' tab.
2. Load your firmware (I used this page to download mine https://c.mi.com/oc/miuidownload/detail?device=1900375 - European Version)
3. Choose Download Agent ( for example C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\MTK_AllInOne_DA_mt6785_mt6765.bin, your path coud be different)
4. Load scatter file (my example - C:\Users\your_username\Downloads\begoniav11030eea\images, it should be in the 'images' folder)
5. Click on 'Download'.
6. Connect your bricked phone
7. Now this step might work for you without pressing any buttons, as that was the case with me. But you could try pressing Volume - or Voulume + while connecting with the computer.
That's it. The flashing took about 5 minutes, but my phone was resurrected. BEAR IN MIND that before this hard brick happened, I did flash the files that were leaked a few weeks ago that permitted the use of SP Flash Tool without an authorised Mi account- the 'preloader' and 'lk' file. But I did flash an android 10 based firmware on top of it. As suggested by some senior members on this thread, by flashing an Android 10 ROM, I overwrote the 'preloader' and 'lk' files, therefore losing the option to flash with SP Flash Tool without an authorised account. But, the bottom line is, this method worked for me. So maybe it might work for you. And if you have a hard bricked Redmi Note 8 Pro, that doesn't have a previously flashed 'preloader' and 'lk' files, please, do try this method. If it works, then great, we just might have resolved some issues with hard bricking of this device.
Click to expand...
Click to collapse
Brother i hace muy phone bricked now i downloaded mi pro Italian versión, i havent fastboot only blackscreen pc cant read phone only on edl, i disconnected battery and still not getting fastboot, so mmy question is where to find that miui android 10 tgz ROM ? For install and try ? I got same error Brome and auth permission , i payed 25$ and i got scamed, i cant find that android 10 ROM that you mentioned
I do as you say but it's not work
Sorry, I'm confused with Step 4:
Where do I find the scatter file? Is it in a subfolder of the firmware I downloaded ? I have a scatter file but each and everytime I get Error: Status_scatter_file_invalid (bC0030001). I have googled all over, change the path of my firmware to a real simple path (c:\firmware). I have the same problem with stand-alone sp flash tools. - For that I tried 5 different versions. Any advice appreciated
avdo06 said:
Hi, everyone. A very desperate owner over here...So, I am having no response from my Redmi Note 8 Pro. I unlocked bootloader, flashed the "lk" and "preloader" files to prevent hard brick. Then I flashed recovery.img from LR Team. I formatted the data and flashed the latest version of MIUI 11 for Europe (miui_BEGONIAEEAGlobal_V11.0.2.0.QGGEUXM_a13b9653ba_10.0). Everything went without problems. I went back (didn't restart) to recovery, and I chose the "install root" option and flashed Magisk. After that, I restarted the phone. But then the problems started with the phone bootlooping. So, I thought, I'm gonna do all these steps without the "Install root" to see if anything changes. So I flashed "lk" and "preloader" (just to be sure), and I flashed the recovery. After that phone doesn't even bootloop. It just vibrates vey shortly if I hold volume+ and power. No panic just yet, I go to SP Flash Tool, load the firmware scatter file and I press "download". But the tool gives me an error "status-brom_cmd_send_da_fail (0xC0060003)". I have tried different usb ports, changed the usb cable, different button combinations, changed between MTK_AllInOne_DA. bin and DA_PL.bin but without success. So I'm asking you all is there some step that I am missing? Because I have been all over XDA these last couple of days and no solution is working for me.
*******************Update 03/13/20********************
So I have managed to unbrick my RN8P. It was dead, without fastboot or any other way to connect. Except for SP Flash Tool. But I had no success to connect my phone in a way that would allow to flash the stock firmware. The SPF Tool kept giving me the "status-brom_cmd_send_da_fail (0xC0060003)" error. So, with my final effort I tried the steps that are explained in this thread https://forum.xda-developers.com/redmi-note-8-pro/help/redmi-note-8-pro-bricked-t3976289/page4 (the last post on the page) . First I downloaded Miflash Pro from here https://androidfilehost.com/?fid=4349826312261688231 . It's in Italian, but don't worry, you just need to use a few functions within the program.
1. Once you have installed Miflash, open it.
2. Switch over to the 'Flash MTK' tab.
2. Load your firmware (I used this page to download mine https://c.mi.com/oc/miuidownload/detail?device=1900375 - European Version)
3. Choose Download Agent ( for example C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\MTK_AllInOne_DA_mt6785_mt6765.bin, your path coud be different)
4. Load scatter file (my example - C:\Users\your_username\Downloads\begoniav11030eea\images, it should be in the 'images' folder)
5. Click on 'Download'.
6. Connect your bricked phone
7. Now this step might work for you without pressing any buttons, as that was the case with me. But you could try pressing Volume - or Voulume + while connecting with the computer.
That's it. The flashing took about 5 minutes, but my phone was resurrected. BEAR IN MIND that before this hard brick happened, I did flash the files that were leaked a few weeks ago that permitted the use of SP Flash Tool without an authorised Mi account- the 'preloader' and 'lk' file. But I did flash an android 10 based firmware on top of it. As suggested by some senior members on this thread, by flashing an Android 10 ROM, I overwrote the 'preloader' and 'lk' files, therefore losing the option to flash with SP Flash Tool without an authorised account. But, the bottom line is, this method worked for me. So maybe it might work for you. And if you have a hard bricked Redmi Note 8 Pro, that doesn't have a previously flashed 'preloader' and 'lk' files, please, do try this method. If it works, then great, we just might have resolved some issues with hard bricking of this device.
Click to expand...
Click to collapse
poster74 said:
Sorry, I'm confused with Step 4:
Where do I find the scatter file? Is it in a subfolder of the firmware I downloaded ? I have a scatter file but each and everytime I get Error: Status_scatter_file_invalid (bC0030001). I have googled all over, change the path of my firmware to a real simple path (c:\firmware). I have the same problem with stand-alone sp flash tools. - For that I tried 5 different versions. Any advice appreciated
Click to expand...
Click to collapse
The scatter file is inside the firmware. You need to extract the tar.gz image, then it should be in the 'images' folder.
Thanks, I managed to get abit further, but not much.
My phone is bricked I think. Can't go into recovery nor fastboot. powering it on, I just get the standard 'Redmi, by Xiaomi' splashscreen for about 3 seconds, in the bottom left, I get a small line 'se blown:sucess'. I think it should read efuse or qfuse but because of rounded corners, cant see full message. After 3 seconds it reboots, goes blank for 5 seconds and then back to Redmi Screen..
I have noticed, having it plugged into PC, when it reboots (i.e. goes blank) the meditek vcom driver pops up in Device Manager and I get the Windows sound of a device being connected. Then it disappears after a second or two
So I can now successfully load my firmware and scatter file. and if I hit the Download button in SPFT just as the its rebooting, detects the phone and the port comes up in bottom left of SPFT. But after 2 minutes it just times out with an error. Its like it detects it for a second and thats it.
Any ideas?
avdo06 said:
The scatter file is inside the firmware. You need to extract the tar.gz image, then it should be in the 'images' folder.
Click to expand...
Click to collapse
poster74 said:
Thanks, I managed to get abit further, but not much.
My phone is bricked I think. Can't go into recovery nor fastboot. powering it on, I just get the standard 'Redmi, by Xiaomi' splashscreen for about 3 seconds, in the bottom left, I get a small line 'se blown:sucess'. I think it should read efuse or qfuse but because of rounded corners, cant see full message. After 3 seconds it reboots, goes blank for 5 seconds and then back to Redmi Screen..
I have noticed, having it plugged into PC, when it reboots (i.e. goes blank) the meditek vcom driver pops up in Device Manager and I get the Windows sound of a device being connected. Then it disappears after a second or two
So I can now successfully load my firmware and scatter file. and if I hit the Download button in SPFT just as the its rebooting, detects the phone and the port comes up in bottom left of SPFT. But after 2 minutes it just times out with an error. Its like it detects it for a second and thats it.
Any ideas?
Click to expand...
Click to collapse
Looks like it's not hardbricked anymore, that's great. You should check out other threads on the RN8 Pro about what to do next.
It works flawlessly AND i had preventive loader (Android 9, Global 11.0.6)
However, note following points;
1. if you get your battery drained it wont charge in preloader mode. so you have to flash the original preloader/lk files as well else, you can uncheck preloader, lk1 and lk2.
2. For future, DONT EVER LET YOUR PHONE BATTERY EVER DRAIN TO ZERO, else possibly you might have to flash whole rom again. (you can try simply restoring preloader)
hi i have a redmi note 8 pro bricked, wrong twrp install, i tried this but it says i don't have any authorized account, what can i do?
dont work!for me
avdo06 said:
Hi, everyone. A very desperate owner over here...So, I am having no response from my Redmi Note 8 Pro. I unlocked bootloader, flashed the "lk" and "preloader" files to prevent hard brick. Then I flashed recovery.img from LR Team. I formatted the data and flashed the latest version of MIUI 11 for Europe (miui_BEGONIAEEAGlobal_V11.0.2.0.QGGEUXM_a13b9653ba_10.0). Everything went without problems. I went back (didn't restart) to recovery, and I chose the "install root" option and flashed Magisk. After that, I restarted the phone. But then the problems started with the phone bootlooping. So, I thought, I'm gonna do all these steps without the "Install root" to see if anything changes. So I flashed "lk" and "preloader" (just to be sure), and I flashed the recovery. After that phone doesn't even bootloop. It just vibrates vey shortly if I hold volume+ and power. No panic just yet, I go to SP Flash Tool, load the firmware scatter file and I press "download". But the tool gives me an error "status-brom_cmd_send_da_fail (0xC0060003)". I have tried different usb ports, changed the usb cable, different button combinations, changed between MTK_AllInOne_DA. bin and DA_PL.bin but without success. So I'm asking you all is there some step that I am missing? Because I have been all over XDA these last couple of days and no solution is working for me.
*******************Update 03/13/20********************
So I have managed to unbrick my RN8P. It was dead, without fastboot or any other way to connect. Except for SP Flash Tool. But I had no success to connect my phone in a way that would allow to flash the stock firmware. The SPF Tool kept giving me the "status-brom_cmd_send_da_fail (0xC0060003)" error. So, with my final effort I tried the steps that are explained in this thread https://forum.xda-developers.com/redmi-note-8-pro/help/redmi-note-8-pro-bricked-t3976289/page4 (the last post on the page) . First I downloaded Miflash Pro from here https://androidfilehost.com/?fid=4349826312261688231 . It's in Italian, but don't worry, you just need to use a few functions within the program.
1. Once you have installed Miflash, open it.
2. Switch over to the 'Flash MTK' tab.
2. Load your firmware (I used this page to download mine https://c.mi.com/oc/miuidownload/detail?device=1900375 - European Version)
3. Choose Download Agent ( for example C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\MTK_AllInOne_DA_mt6785_mt6765.bin, your path coud be different)
4. Load scatter file (my example - C:\Users\your_username\Downloads\begoniav11030eea\images, it should be in the 'images' folder)
5. Click on 'Download'.
6. Connect your bricked phone
7. Now this step might work for you without pressing any buttons, as that was the case with me. But you could try pressing Volume - or Voulume + while connecting with the computer.
That's it. The flashing took about 5 minutes, but my phone was resurrected. BEAR IN MIND that before this hard brick happened, I did flash the files that were leaked a few weeks ago that permitted the use of SP Flash Tool without an authorised Mi account- the 'preloader' and 'lk' file. But I did flash an android 10 based firmware on top of it. As suggested by some senior members on this thread, by flashing an Android 10 ROM, I overwrote the 'preloader' and 'lk' files, therefore losing the option to flash with SP Flash Tool without an authorised account. But, the bottom line is, this method worked for me. So maybe it might work for you. And if you have a hard bricked Redmi Note 8 Pro, that doesn't have a previously flashed 'preloader' and 'lk' files, please, do try this method. If it works, then great, we just might have resolved some issues with hard bricking of this device.
Click to expand...
Click to collapse
i do this step and when press volume + and connect my mi account authotised but after it take error such
STATUS_BROM_CMD_STARTCM_FAIL(0XC0060001) ...
...in devices manager in laptop(windows 10) when press and connect phone show mediatek usb port... but flash do not start!!!
tanx for you giud and response
hello
zumboy said:
hi i have a redmi note 8 pro bricked, wrong twrp install, i tried this but it says i don't have any authorized account, what can i do?
Click to expand...
Click to collapse
do you resolve that problem?? i got the same (same wrong twrp install) & i think our only chance to resolve this is with authorised account
Preamble:
After a bit of research, I've found a simple way to - at least - obtain root privileges on the basic version of Redmi Note 9 (Mediatek - Helio G85).
The procedure has been tested on a Redmi Note 9 Global NFC 4/128 (Model: M2003J15SG) with MIUI Global 11.0.5.
The attached files comprise:
Original Boot Image from MIUI Global 11.0.5 (provided as a courtesy, download your own copy from MIUI Website if you wish)
Patched Boot Image from Magisk on MIUI Global 11.0.5 (again, the file provided as a courtesy; you can generate your own file, on your device.)
VBMETA Patched Image: essential to the process, this file has not been created by me. Courtesy of user Neko-kun from MI.cn Forum. I can only confirm that the file works as expected; please, if you have the required expertise, inspect the file and report your findings.
Warning:
This procedure depends on having previously unlocked the bootloader. Doing so you have read, understood and accepted all the information regarding security and potential stability issues given by XIAOMI before completing the procedure.
Also, this means you have understood and accepted potential warranty issues arising from such procedure, and you understand the risks associated with a rooted device.
I'm not responsible for any damage, loss of personal data, brick or loss of usability arising from following this procedure and/or from any user error committed by doing so.
As a result, your warranty may be void, according to laws in effect in your state.
This procedure is only valid for Redmi Note 9 (not the Pro version, not the 9S version) with MEDIATEK chipset
Note:
Always make a back-up of your data! This procedure will re-initialize the device.
Requirements:
A valid MI Account, associated with the phone, used to certification in the bootloader unlocking procedure. (via official MI UNLOCK)
Unlocked Bootloader (new devices usually have a 7-day waiting period)
A personal computer with FASTBOOT installed, basic knowledge of FASTBOOT commands, drivers correctly installed on your system of choice. (for windows users, a valid solution is "Minimal ABD and Fastboot".)
Resources:
Magisk Manager
Boot Image / Magisk Patched Boot Image / VBMeta Image - link or see attached files
Procedure:
Download the attached files (or generate the first two on your own device, using Magisk Manager).
Copy the prepared files inside the fastboot directory (so you don't have to worry about file path in the following steps)
Reboot the phone into Fastboot Mode (hold Power+Volume Down until fastboot screen)
Connect the phone to the computer, open fastboot terminal and issue the following commands. BE PATIENT AND DOUBLE CHECK EVERYTHING BEFORE CONFIRMING! Text between round brackets are comments, it must not be copied.
Code:
fastboot devices (check your phone is the only device shown)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (this disables system changes)
fastboot erase userdata (this will clear user data!)
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
The following first reboot will take a while. After completing the initial configuration, install the latest Magisk Manager (at the time of writing, v. 7.5.1) and continue with the configuration following the in-app prompt.
Phone will reboot at the end of the procedure. Launch once again Magisk Manager, select the "Beta Channel" for updates and enable Magisk Hide.
Reload Magisk Manager, check for Safety Net: you should have the green light.
Enjoy your root privileges. (aka, get rid of the bloatware )
Known BUGs / LIMITATIONS:
Can't modify /system partition
Need to temporary set SELinux to permissive in order to remove system apps. Please refer to this post.
Removing "Bloatware"
Probably one the main reasons for obtaining root privileges is to get rid of some default apps which come bundled with the official MIUI.
Given the current situation for this device, using classic methods (such as Titanium Backup / System App Remover / etc.) is not possible and - most probably - attempting in doing so will result in a soft-brick.
Instead, there is a particularly useful Magisk Module that can be used for this scope: Debloater.
You can read more about it here on XDA; the installation procedure will vary just a bit since there is currently no TWRP support for the Helio G85 Redmi Note 9.
Installing Debloater
Launch Magisk Manager and select "Download" from the menu
Use the search function to locate the package "Busybox for Android NDK"
Install the package, and chose to skip the reboot at the end of the procedure.
Use the search function to locate the package "Debloater Terminal Emulator"
Install the package and this time proceed with the reboot
When the reboot is complete, install any terminal emulator app from PlayStore (like Termux)
Open the terminal and issue:
Code:
su
(confirm the request for superuser access) and then
Code:
debloat
Now you can use Debloat to remove all the unwanted applications that come bundled with the ROM.
Please refer to the video included in the post mentioned above to learn more about Debloat and how to use it.
One Question
Can i know this work for Redmi Note 9 global non NFC?
The download link in the first post does not work any longer ... Gives a 404. Please re-upload and don't use XDA's upload space. Thanks!
dfahren said:
The download link in the first post does not work any longer ... Gives a 404. Please re-upload and don't use XDA's upload space. Thanks!
Click to expand...
Click to collapse
Sorry for the inconvenience, there is still the MEGA link from the first post up and working.
Here it is: https://mega.nz/file/ucFDXIaY#FrUllKuUASoStlSvrcMYABsbYv6ie-WHR4zOqJMdP4E
[email protected] said:
Can i know this work for Redmi Note 9 global non NFC?
Click to expand...
Click to collapse
It should work, since there is no significant difference between the two models regarding the rooting procedure. But I have no way of testing it because I don't have that phone version on hand.
N3OMOD said:
It should work, since there is no significant difference between the two models regarding the rooting procedure. But I have no way of testing it because I don't have that phone version on hand.
Click to expand...
Click to collapse
Hi there,
I can confirm the aforementioned procedure to root one's phone does work. I own a Redmi Note 9, Code: merlinnfc, Version: 11.0.5.0 (QJOEUXM). As you can see it's the European variant.
However, I didn't use the Zip archive the OP provided since it is meant for the global variant and (as of now) I don't see any necessity to reflash my phone to the global firmware.
I strongly recommend everybody to have Magisk Manager generate patched boot.img files and NOT use the original author's boot.img file! This holds true especially for those guys like me who own, say, an indian, chinese or european variant or run a different firmware version like, e.g., 11.0.3.0.
What's also important to mention is that there is no special "patched" vbmeta file. That guy "neko-kun" simply used the one contained in the original full firmare downloadable from Xiaomi's servers. Here you also have to make sure you use the one that matches the installed firmware version on your phone. Do not flash any other or you might get a brick!
If anybody of you guys has managed to get AFWall up and running and apply iptable rules without error, please drop me a line.
Thanks and good speed to everybody!
dfahren said:
Hi there,
I can confirm the aforementioned procedure to root one's phone does work. I own a Redmi Note 9, Code: merlinnfc, Version: 11.0.5.0 (QJOEUXM). As you can see it's the European variant.
Click to expand...
Click to collapse
Thank you for the feedback! That is the same version (hardware and ROM) I used to test the procedure before writing the article.
dfahren said:
However, I didn't use the Zip archive the OP provided since it is meant for the global variant and (as of now) I don't see any necessity to reflash my phone to the global firmware.
I strongly recommend everybody to have Magisk Manager generate patched boot.img files and NOT use the original author's boot.img file! This holds true especially for those guys like me who own, say, an indian, chinese or european variant or run a different firmware version like, e.g., 11.0.3.0.
Click to expand...
Click to collapse
Indeed, as I mentioned in the first post, those files are provided only as a courtesy for those who may have the same device with the same firmware: I strongly encourage everyone to make their own using Magisk Manager.
dfahren said:
What's also important to mention is that there is no special "patched" vbmeta file. That guy "neko-kun" simply used the one contained in the original full firmare downloadable from Xiaomi's servers. Here you also have to make sure you use the one that matches the installed firmware version on your phone. Do not flash any other or you might get a brick!
Click to expand...
Click to collapse
Thanks for the clarification about the vbmeta file. I will update the post to clarify this aspect.: good:
The original explanation from the user was a bit difficult to understand, hence the warning about the possibility of a "patched" file. (I didn't want to create any trouble for anyone).
Also, a little comforting for anyone who might incur in a (soft)brick: I have seen some people flashing only the "boot.img" and ending up in an infinite bootloop (black screen with "redmi" logo).
Should that happen, you can always enter the fastboot mode (keeping pressed the power+vol down for a bit longer than usual) and re-flash the original "boot.img" extracted from the official ROM image available on MIUI site.
dfahren said:
If anybody of you guys has managed to get AFWall up and running and apply iptable rules without error, please drop me a line.
Thanks and good speed to everybody!
Click to expand...
Click to collapse
Will let you know as soon as I have some time to test it.
(sidenote for those interested: for now I can confirm that AdAway is working fine)
Followed the steps, worked flawlessly on my Redmi Note 9 (Merlin) 3gb ram 64gb storage purchased in Europe, running Global 11.0.5.
Thank you so very much!
I had successfully done this in the past but messed something up with xposed later, I won't xposed it this time and just enjoy my root-ness.
N3OMOD said:
Thanks for the clarification about the vbmeta file. I will update the post to clarify this aspect.: good:
The original explanation from the user was a bit difficult to understand, hence the warning about the possibility of a "patched" file. (I didn't want to create any trouble for anyone).
...
Also, a little comforting for anyone who might incur in a (soft)brick: I have seen some people flashing only the "boot.img" and ending up in an infinite bootloop (black screen with "redmi" logo).
Should that happen, you can always enter the fastboot mode (keeping pressed the power+vol down for a bit longer than usual) and re-flash the original "boot.img" extracted from the official ROM image available on MIUI site.
...
(sidenote for those interested: for now I can confirm that AdAway is working fine)
Click to expand...
Click to collapse
The original explanation from user "neko-kun" seemed to me an automatic translation hence the rather weird language.
I can testify to the statement that you can reflash the original boot.img file should you enter a bootloop (which I got).
AdAway is also working for me as does AFWall+ (I needed to leave logging of blocked packets as it is -> off)
N3OMOD said:
Thank you for the feedback! That is the same version (hardware and ROM) I used to test the procedure before writing the article.
Indeed, as I mentioned in the first post, those files are provided only as a courtesy for those who may have the same device with the same firmware: I strongly encourage everyone to make their own using Magisk Manager.
Thanks for the clarification about the vbmeta file. I will update the post to clarify this aspect.: good:
The original explanation from the user was a bit difficult to understand, hence the warning about the possibility of a "patched" file. (I didn't want to create any trouble for anyone).
Also, a little comforting for anyone who might incur in a (soft)brick: I have seen some people flashing only the "boot.img" and ending up in an infinite bootloop (black screen with "redmi" logo).
Should that happen, you can always enter the fastboot mode (keeping pressed the power+vol down for a bit longer than usual) and re-flash the original "boot.img" extracted from the official ROM image available on MIUI site.
Will let you know as soon as I have some time to test it.
(sidenote for those interested: for now I can confirm that AdAway is working fine)
Click to expand...
Click to collapse
i'm having an infinite bootloop and keep pressing power + vol down didn't help , what should i do ?
@noodlelicious
That's very unfortunate. I know this situation only too well. First of all what type of Redmi Note 9 do you have. Please post the "Product Model" number you can find on your phone and package. Mine, for example, is M2003J15SG. Which version of MIUI did you run? Is it MIUI 11 or the newer MIUI 12? Do you run some regional flavor of MIUI such as European, Russian, Indonesian, Indian or China?
Second, did you flash the correct vbmeta file? I mean this is an IMG file that must match the flavor? The original poster supplied a vbmeta IMG file for the global variant that might (I'm really not sure) not fit to your specific flavor.
Ok, how do you get rid of the boot loop? I manged to stop the loop by pressing Volume down continuously for about a minute. After that my phone reboots into fastboot mode. Please DO NOT press the power button, this is unnecessary.
When in fastboot mode reflash your original boot.img according to the steps above.
I hope that helps you a bit.
Best wishes,
Didi
dfahren said:
@noodlelicious
That's very unfortunate. I know this situation only too well. First of all what type of Redmi Note 9 do you have. Please post the "Product Model" number you can find on your phone and package. Mine, for example, is M2003J15SG. Which version of MIUI did you run? Is it MIUI 11 or the newer MIUI 12? Do you run some regional flavor of MIUI such as European, Russian, Indonesian, Indian or China?
Second, did you flash the correct vbmeta file? I mean this is an IMG file that must match the flavor? The original poster supplied a vbmeta IMG file for the global variant that might (I'm really not sure) not fit to your specific flavor.
Ok, how do you get rid of the boot loop? I manged to stop the loop by pressing Volume down continuously for about a minute. After that my phone reboots into fastboot mode. Please DO NOT press the power button, this is unnecessary.
When in fastboot mode reflash your original boot.img according to the steps above.
I hope that helps you a bit.
Best wishes,
Didi
Click to expand...
Click to collapse
Thank you so much for replying my problems.
First, i'm using M2003J15SS
I'm running on latest miui 11 indonesian.
I'm flashing the vbmeta on first post , i skip all the comment section and straight install all the things there.
I already put a rubber band on my vol down since 7 hours ago and still got no fastboot.
What else can i do ?
What about entering recovery?
noodlelicious said:
Thank you so much for replying my problems.
First, i'm using M2003J15SS
I'm running on latest miui 11 indonesian.
I'm flashing the vbmeta on first post , i skip all the comment section and straight install all the things there.
I already put a rubber band on my vol down since 7 hours ago and still got no fastboot.
What else can i do ?
Click to expand...
Click to collapse
Try to enter stock recovery, if you can, select mi assitant. After that connect trough adb and run "adb reboot bootloader", that should do the trick.
If phone isnt booting none of main enviroments (system, recovery or fastboot/bootloader) battery drainage may restablish normal boot order. Just remember that if in any case it boots to recovery, use adb command to reboot to bootloader.
Tested on RN9 Global non-NFC (M2003J15SS) with MIUI 12 Global
Hi, just to inform. The following was tested in Redmi Note 9 Global non-NFC (M2003J15SS) with MIUI 12 Global.
- Patched boot image from MIUI12 Global (Android 10) works fine if dm-verity and forced encryption are disable at the time of making the boot image with magisk.
- vbmeta file provided by OP also works (I think any file would work if it's flashed with "--disable-verity --disable-verification" option. This option is essential to avoid bootloop after flashing any non-stock (or patched) image to any partition:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
The vbmeta file I used was extracted (and possibly) edited from a previous version of MIUI (MIUI11), and applied over MIUI12 ROM, that's why I think any file could be used.
Hi .. Is there a way to write to system / app. I need to be able to pass an application to system. Thank you.
Does netflix still work in HD after having the BL unlocked and further rooted?
How to patch vbmeta
---------- Post added at 05:50 PM ---------- Previous post was at 05:14 PM ----------
N3OMOD said:
Preamble:
After a bit of research, I've found a simple way to - at least - obtain root privileges on the basic version of Redmi Note 9 (Mediatek - Helio G85).
The procedure has been tested on a Redmi Note 9 Global NFC 4/128 (Model: M2003J15SG) with MIUI Global 11.0.5.
The attached files comprise:
Original Boot Image from MIUI Global 11.0.5 (provided as a courtesy, download your own copy from MIUI Website if you wish)
Patched Boot Image from Magisk on MIUI Global 11.0.5 (again, the file provided as a courtesy; you can generate your own file, on your device.)
VBMETA Patched Image: essential to the process, this file has not been created by me. Courtesy of user Neko-kun from MI.cn Forum. I can only confirm that the file works as expected; please, if you have the required expertise, inspect the file and report your findings.
Warning:
This procedure depends on having previously unlocked the bootloader. Doing so you have read, understood and accepted all the information regarding security and potential stability issues given by XIAOMI before completing the procedure.
Also, this means you have understood and accepted potential warranty issues arising from such procedure, and you understand the risks associated with a rooted device.
I'm not responsible for any damage, loss of personal data, brick or loss of usability arising from following this procedure and/or from any user error committed by doing so.
As a result, your warranty may be void, according to laws in effect in your state.
This procedure is only valid for Redmi Note 9 (not the Pro version, not the 9S version) with MEDIATEK chipset
Note:
Always make a back-up of your data! This procedure will re-initialize the device.
Requirements:
A valid MI Account, associated with the phone, used to certification in the bootloader unlocking procedure. (via official MI UNLOCK)
Unlocked Bootloader (new devices usually have a 7-day waiting period)
A personal computer with FASTBOOT installed, basic knowledge of FASTBOOT commands, drivers correctly installed on your system of choice. (for windows users, a valid solution is "Minimal ABD and Fastboot".)
Resources:
Magisk Manager
Boot Image / Magisk Patched Boot Image / VBMeta Image - link or see attached files
Procedure:
Download the attached files (or generate the first two on your own device, using Magisk Manager).
Copy the prepared files inside the fastboot directory (so you don't have to worry about file path in the following steps)
Reboot the phone into Fastboot Mode (hold Power+Volume Down until fastboot screen)
Connect the phone to the computer, open fastboot terminal and issue the following commands. BE PATIENT AND DOUBLE CHECK EVERYTHING BEFORE CONFIRMING! Text between round brackets are comments, it must not be copied.
Code:
fastboot devices (check your phone is the only device shown)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (this disables system changes)
fastboot erase userdata (this will clear user data!)
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
The following first reboot will take a while. After completing the initial configuration, install the latest Magisk Manager (at the time of writing, v. 7.5.1) and continue with the configuration following the in-app prompt.
Phone will reboot at the end of the procedure. Launch once again Magisk Manager, select the "Beta Channel" for updates and enable Magisk Hide.
Reload Magisk Manager, check for Safety Net: you should have the green light.
Enjoy your root privileges. (aka, get rid of the bloatware )
Known BUGs / LIMITATIONS:
Can't modify /system partition
Need to temporary set SELinux to permissive in order to remove system apps. Please refer to this post.
Click to expand...
Click to collapse
can i use original vbmeta in rom files for this command
"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (this disables system changes)"
Because my phone is redmi note 9 (m2003j15ss) updated to 12.03.0(QJOMIXM) miui version
If not with the original, how do I patch this file?
can this be used to root the EU model: MZB9410EU ?
farvehar09 said:
---------- Post added at 05:50 PM ---------- Previous post was at 05:14 PM ----------
can i use original vbmeta in rom files for this command
"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (this disables system changes)"
Because my phone is redmi note 9 (m2003j15ss) updated to 12.03.0(QJOMIXM) miui version
If not with the original, how do I patch this file?
Click to expand...
Click to collapse
Yes u can, i use the original vbmeta from miui_MERLINIDGlobal_V12.0.1.0.QJOIDXM_709d727d58_10.0.zip (ID variant)
Hey,
I'm currently on ArrowOS latest build, and I wanted to go back to stock but I can't flash the stock rom for my phone aliothin or Mi 11x. TWRP updater process ends with Error 1 and then Error 7: kInstallDeviceOpenError. I'm using vasishasht's TWRP. Can someone guide me on what I should do?
Dhruv.m said:
Hey,
I'm currently on ArrowOS latest build, and I wanted to go back to stock but I can't flash the stock rom for my phone aliothin or Mi 11x. TWRP updater process ends with Error 1 and then Error 7: kInstallDeviceOpenError. I'm using vasishasht's TWRP. Can someone guide me on what I should do?
Click to expand...
Click to collapse
You have to use miflashtool to flash the stock.
Read this guide, there is a lot of useful information, including what might solve your problem.
How to flash ROM and TWRP on POCO F3 / k40 / mi11x. And an explanation. A very important guide
Mandatory instructions for beginners (and not only beginners) to install ROM and other on poco f3 Prerequisite, unlocking the bootloader For questions, if something is not clear, please write to "Conversations", I will try to correct it in a post...
forum.xda-developers.com
Okay, actually I was trying to flash the Recovery ROM through TWRP, I'll do fastboot and let you know what happens!
Thank you
RollDload said:
You have to use miflashtool to flash the stock.
Read this guide, there is a lot of useful information, including what might solve your problem.
How to flash ROM and TWRP on POCO F3 / k40 / mi11x. And an explanation. A very important guide
Mandatory instructions for beginners (and not only beginners) to install ROM and other on poco f3 Prerequisite, unlocking the bootloader For questions, if something is not clear, please write to "Conversations", I will try to correct it in a post...
forum.xda-developers.com
Click to expand...
Click to collapse
I was unable to flash with XiaoMiFlashTool as it triggered the Anti Rollback, but the images i tried to flash were the latest MIUI fastboot files available (They haven't updated for aliothin since June 26).
How do I proceed?
Dhruv.m said:
I was unable to flash with XiaoMiFlashTool as it triggered the Anti Rollback, but the images i tried to flash were the latest MIUI fastboot files available (They haven't updated for aliothin since June 26).
How do I proceed?
Click to expand...
Click to collapse
It has happened to others before, try to do what this guide says and try again ...
Alioth ARB Anti Rollback error in MiFlash
EDIT: i'm really not sure about the correctness of this now. I'll leave the thread up as a sort of guide, but you'll need to do your own checks on ARB. Sorry, i read a couple of threads and thought i had it clear, but now i am not so sure...
forum.xda-developers.com
RollDload said:
It has happened to others before, try to do what this guide says and try again ...
Alioth ARB Anti Rollback error in MiFlash
EDIT: i'm really not sure about the correctness of this now. I'll leave the thread up as a sort of guide, but you'll need to do your own checks on ARB. Sorry, i read a couple of threads and thought i had it clear, but now i am not so sure...
forum.xda-developers.com
Click to expand...
Click to collapse
How do I check the value of anti? In the aliothin files it calls some .TXT file instead of the normal
Dhruv.m said:
How do I check the value of anti? In the aliothin files it calls some .TXT file instead of the normal
Click to expand...
Click to collapse
On the phone, check the anti by connecting it to the PC in fastboot mode and typing this command on cmd
Code:
fastboot getvar anti
which rom are you trying to install?
RollDload said:
On the phone, check the anti by connecting it to the PC in fastboot mode and typing this command on cmd
Code:
fastboot getvar anti
which rom are you trying to install?
Click to expand...
Click to collapse
I'm trying to return to stock MIUI
I know I was on 12.5.2 before I went to Arrow OS
Dhruv.m said:
How do I check the value of anti? In the aliothin files it calls some .TXT file instead of the normal
Click to expand...
Click to collapse
These are the actions you need to do:
1) Extract the fastboot rom;
2) Rename the "flash_all.bat" file to "flash_all.txt";
3) Open it and delete everything selected here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4) Save and rename it again .bat;
5) try to flash again with miflash.
Code:
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *alioth" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *alioth" || exit /B 1
::check anti_version
if exist %~dp0images\anti_version.txt (for /f "delims==" %%a in (%~dp0images\anti_version.txt) do (set CURRENT_ANTI_VER=%%a))
if [%CURRENT_ANTI_VER%] EQU [] set CURRENT_ANTI_VER=0
for /f "tokens=2 delims=: " %%i in ('fastboot %* getvar anti 2^>^&1 ^| findstr /r /c:"anti:"') do (set version=%%i)
if [%version%] EQU [] set version=0
set anticheck="antirollback check pass"
What does this mean by the way?
RollDload said:
These are the actions you need to do:
1) Extract the fastboot rom;
2) Rename the "flash_all.bat" file to "flash_all.txt";
3) Open it and delete everything selected here
View attachment 5405679
4) Save and rename it again .bat;
5) try to flash again with miflash.
Click to expand...
Click to collapse
thank you i'll try it in a bit, by the way my phone's anti is 1 - does this mean that any MIUI ROM can be flashed?
Dhruv.m said:
thank you i'll try it in a bit, by the way my phone's anti is 1 - does this mean that any MIUI ROM can be flashed?
Click to expand...
Click to collapse
The one above is the arb control which compares the anti in the phone with the anti in the rom.
I don't want to give you bad information, but I downloaded and checked all 12.0 and 12.5 stock EEA roms (my region) and they are all anti = 1 so I think we can flash them all. that miflash error should be a program bug. Let me know if it works
RollDload said:
The one above is the arb control which compares the anti in the phone with the anti in the rom.
I don't want to give you bad information, but I downloaded and checked all 12.0 and 12.5 stock EEA roms (my region) and they are all anti = 1 so I think we can flash them all. that miflash error should be a program bug. Let me know if it works
Click to expand...
Click to collapse
Thank you very much, can you tell me how you checked your ROM so I can check for my region and my device?
Dhruv.m said:
Thank you very much, can you tell me how you checked your ROM so I can check for my region and my device?
Click to expand...
Click to collapse
for the device I wrote it above, I think the anti value of the rom is inside the "anti_version.txt" file which is inside the images folder of the rom itself. Try looking there ...
RollDload said:
for the device I wrote it above, I think the anti value of the rom is inside the "anti_version.txt" file which is inside the images folder of the rom itself. Try looking there ...
Click to expand...
Click to collapse
The file has just a number, 1
Dhruv.m said:
The file has just a number, 1
Click to expand...
Click to collapse
It's the same one I found in all EEA roms,
ALSO just to confirm before I do it, is this safe to do? Does it involve any risks of bricking? I just got my device 12 days ago and I really do NOT want to brick it and be perfectly safe?
Dhruv.m said:
ALSO just to confirm before I do it, is this safe to do? Does it involve any risks of bricking? I just got my device 12 days ago and I really do NOT want to brick it and be perfectly safe?
Click to expand...
Click to collapse
Nothing serious should happen, since you are restoring the rom you had before flashing the castom, the important thing is that you remember to select the check on "clean all" at the bottom right of the miflash program, because if you leave the check on "clean and lock" blocks the bootloader and then you risk the brick.
RollDload said:
Nothing serious should happen, since you are restoring the rom you had before flashing the castom, the important thing is that you remember to select the check on "clean all" at the bottom right of the miflash program, because if you leave the check on "clean and lock" blocks the bootloader and then you risk the brick.
Click to expand...
Click to collapse
True, but I am just asking because this modifies quite a bit of files and I hope it doesn't mess anything up.
Dhruv.m said:
True, but I am just asking because this modifies quite a bit of files and I hope it doesn't mess anything up.
Click to expand...
Click to collapse
If you follow the instructions step by step, you should be fine.
1) Extract the rom;
2) Edit the .bat file as I told you above, delete only the selected one and nothing else.
3) enable usb debug on the phone developer settings;
4) open miflash as administrator and select the rom you need to flash;
5) select "clean all" at the bottom right;
6) restart the phone in fastboot and connect it to the pc;
7) wait for miflash to recognize the phone and make sure that "clean all" is checked;
8) press flash and wait for it to finish without touching anything.
9) it may be that miflash gives some other error, you wait for it to finish, unplug the phone and restart it if it did not boot by itself.
10) remember that the first start can take several minutes on the miui screen, wait without doing anything, if everything went well you should see the configuration screen.