Hi everyone!
I bought a MI 9 SE for my dad, it was a Chinese version with an unlocked bootloader and global rom installed.
After trying to use Google Pay, I figured it needs a locked bootloader. So I locked it using "fastboot oem lock".
After that, the phone is bricked
I didn't have an account bound to it, so can't use the official unlock.
Can access fastboot and recovery.
Tried flashing using recovery, sideloading.
It refuses to install a chinese rom, only a global one can be installed.
Obviously, I get the "This MIUI version can't be installed on this device".
I know there's the EDL path, but that requires an authorized account
Is there any other way around this?
Is there a way to force install a chinese rom over the global rom?
I would really appreciate any help or advice. I've spent a few days reading the forums, tried a lot of utilities but with zero luck.
Did you try the original chinese ROM, the first release? The same with global?
elpaablo said:
Did you try the original chinese ROM, the first release? The same with global?
Click to expand...
Click to collapse
I have tried the last few MIUI versions, but didn't try the original release versions. That's a good point! Will try today, and get back with the results :good:
If you locked the bootloader on a non-official ROM, you could have messed the AVB (Android Verified Boot) partition.
Disabling vbmeta could be helpful.
Download vbmeta.img from https://drive.google.com/open?id=1-Np8xHPfVlJwUJLURntIklmkCyVqU5jH and place it in the same folder of your fastboot tools.
Open a cmd window (don't use Windows Power Shell) and type command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you get the command executed properly, then type
fastboot reboot
and pray if device will restart on old ROM, set a MiAccount and unlock bootloader again using MiFlash, then flash any Official ROM and relock bootloader, if needed.
You can also get GPay working on unlocked bootloader, using Magisk, in case.
Flounderist said:
If you locked the bootloader on a non-official ROM, you could have messed the AVB (Android Verified Boot) partition.
Disabling vbmeta could be helpful.
Download vbmeta.img from and place it in the same folder of your fastboot tools.
Open a cmd window (don't use Windows Power Shell) and type command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you get the command executed properly, then type
fastboot reboot
and pray if device will restart on old ROM, set a MiAccount and unlock bootloader again using MiFlash, then flash any Official ROM and relock bootloader, if needed.
You can also get GPay working on unlocked bootloader, using Magisk, in case.
Click to expand...
Click to collapse
{
"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"
}
It didn't work, says 'Flashing is not allowed in Lock State'
elpaablo said:
Did you try the original chinese ROM, the first release? The same with global?
Click to expand...
Click to collapse
The same error both times, seems it refuses to install older versions of MIUI
savandriy said:
The same error both times, seems it refuses to install older versions of MIUI
Click to expand...
Click to collapse
Oh, you don't use miflash tools?
savandriy said:
It didn't work, says 'Flashing is not allowed in Lock State'
Click to expand...
Click to collapse
Try with
fastboot format userdata
and
fastboot reboot
If you use telegram, join the conversation here @GrusFamily
Reboot in fastboot ans use Flashtool
Flash any ron in fastboot format from here https://mirom.ezbox.idv.tw/en/phone/grus/
With flashtool, all partition will be format and phone is like out of the box
Flounderist said:
If you use telegram, join the conversation here @GrusFamily
Click to expand...
Click to collapse
What the hell, I have a family? What's this about?
Grus said:
What the hell, I have a family? What's this about?
Click to expand...
Click to collapse
Hahaha sorry mate. It's the link of a telegram group and it matched with your nickname.
Grus is the device name for Mi 9 SE :laugh:
That's so incredibly strange. Guess I'll have to check that phone out.
Flounderist said:
Try with
fastboot format userdata
and
fastboot reboot
If you use telegram, join the conversation here @GrusFamily
Click to expand...
Click to collapse
Sadly, it just hangs forever on the "Sending 'userdata' (4400 KB)" part ...
pikouchou said:
Reboot in fastboot ans use Flashtool
Flash any ron in fastboot format from here https://mirom.ezbox.idv.tw/en/phone/grus/
With flashtool, all partition will be format and phone is like out of the box
Click to expand...
Click to collapse
Can you please link to the Flashtool or a tutorial? Do you mean XiaomiADB?
savandriy said:
Can you please link to the Flashtool or a tutorial? Do you mean XiaomiADB?
Click to expand...
Click to collapse
Here is the link:
https://www.xiaomiflash.com/download/
You need to download a fastboot ROM and to unzip it TWICE to get the flashable files.
Then launch flashtool while device is connected in fastboot mode.
Locate files using flashtool interface and try to flash it.
If you won't succeed, EDL flash is your last resort.
https://mirom.ezbox.idv.tw/en/phone/grus/roms-cn-stable/
Try the first chinese version (10.2.3).
Flounderist said:
Here is the link:
https://www.xiaomiflash.com/download/
You need to download a fastboot ROM and to unzip it TWICE to get the flashable files.
Then launch flashtool while device is connected in fastboot mode.
Locate files using flashtool interface and try to flash it.
If you won't succeed, EDL flash is your last resort.
Click to expand...
Click to collapse
It says there's a device mismatch, but this is the Chinese MIUI 10.2.3 for MI 9 SE
I guess EDL it is then
Try global too. I would try all Chinese and global versions, just to be sure. Because, you know, edl isn't free.
savandriy said:
It says there's a device mismatch, but this is the Chinese MIUI 10.2.3 for MI 9 SE
I guess EDL it is then
Click to expand...
Click to collapse
If you get device mismatch error you should:
- check if your device is actually a Mi9 SE
- check if you downloaded a fastboot ROM for Mi 9SE
- check if you are using the latest MIUI driver and MiFlash.
Probably your device had a fake-MIUI ROM installed with some messed device fingerprint, hence MiFlash does not recognize it as Grus.
If you are 100% sure your device is a Mi 9SE, and you downloaded the correct ROM (I would recommend latest China Stable), you can try editing the flash-all.bat file.
Here is a tutorial (you probably will need to translate it): https://www.miui.it/forum/index.php...lazione-delle-rom-fastboot-con-miflash.15301/
Good luck!
You can flash him only with testpoint and auth account
Related
I am getting this error everytime I try to flash twrp using the fastboot commands. I used the proper flashing commands on my Redmi Note 5 pro. Bootloader is also unlocked. Adb and minimal drivers are installed as well. Please help.
target reported max download size of 536870912 bytes
sending 'recovery' (35404 KB)...
FAILED (remote: Requested download size is more than max allowed )
vib$$$ said:
I am getting this error everytime I try to flash twrp using the fastboot commands. I used the proper flashing commands on my Redmi Note 5 pro. Bootloader is also unlocked. Adb and minimal drivers are installed as well. Please help.
target reported max download size of 536870912 bytes
sending 'recovery' (35404 KB)...
FAILED (remote: Requested download size is more than max allowed )
Click to expand...
Click to collapse
Try official recovery it worked
kash2freedom said:
Try official recovery it worked
Click to expand...
Click to collapse
it is the official one
vib$$$ said:
it is the official one
Click to expand...
Click to collapse
Did you turn on OEM unlock in developer option before flashing TWRP? and I used this tool to flash TWRP from MIUI fastboot, you can also try this but make sure you have proper adb driver install and the tool detect your device is fastboot mood
Link of the tool - https://androidfilehost.com/?fid=746010030569969698
1. After connected with fastboot with the tool will look like this
{
"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"
}
2. And then click the "Recovery Flash button" and follow the second pic, do tick the "and boot it" option like in the second picture
Shahitto said:
Did you turn on OEM unlock in developer option before flashing TWRP? and I used this tool to flash TWRP from MIUI fastboot, you can also try this but make sure you have proper adb driver install and the tool detect your device is fastboot mood
Link of the tool - https://androidfilehost.com/?fid=746010030569969698
1. After connected with fastboot with the tool will look like this View attachment 44940562. And then click the "Recovery Flash button" and follow the second pic, do tick the "and boot it" option like in the second pictureView attachment 4494060
Click to expand...
Click to collapse
Yes. My bootloader is unlocked. So oem is also ticked. I'll try using this software. Do you have the proper steps for it?
type fastboot devices and see if it shows a device
maybe try using anothar usb port on laptop
if fastboot devices is not showing anything, its coz adb and fastboot drivers are not installed properly, are u using a windows 10 laptop??? they tend to give some problems while installing drivers.. google up and u will find ways
I had the same issue. Its coz windows 10 driver issues. I tried the same method in a windows 7 pc and it worked.
Shahitto said:
Did you turn on OEM unlock in developer option before flashing TWRP? and I used this tool to flash TWRP from MIUI fastboot, you can also try this but make sure you have proper adb driver install and the tool detect your device is fastboot mood
Link of the tool - https://androidfilehost.com/?fid=746010030569969698
1. After connected with fastboot with the tool will look like this View attachment 44940562. And then click the "Recovery Flash button" and follow the second pic, do tick the "and boot it" option like in the second pictureView attachment 4494060
Click to expand...
Click to collapse
is it for redmi note 5 pro
vib$$$ said:
is it for redmi note 5 pro
Click to expand...
Click to collapse
i used this toolkit and it does not recognise my device in fastboot mode. it recognises that the device is in fastboot. but shows no device found. When i tried installing the adb files. it showed 0 files copied. maybe thats why it is. any solution to the 0 files copied thing
vib$$$ said:
i used this toolkit and it does not recognise my device in fastboot mode. it recognises that the device is in fastboot. but shows no device found. When i tried installing the adb files. it showed 0 files copied. maybe thats why it is. any solution to the 0 files copied thing
Click to expand...
Click to collapse
It's OK not to show device name in the toolkit if the toolkit only shows fastboot as green color that means you device has been recognized and you don't have to install adb driver again so now you just need to click on the button Recovery Flash and a new box will appear and then check my second Pic file and find the twrp file and flash it, it's very simple
And I have done this method for my Redmi Note 5 AI(China)
Same thing happened with me. I can't even flash anything via fastboot. I updated from 8.4.25 to 8.5.2 global beta on my Redmi Note 5 Pro and this happened.
Also, I noticed that if I try to flash anything from MiFlash, the phone would disconnect itself even if I would flash from CMD.
After disconnecting from itself, the screen stays on fastboot and immediately a text appears "Press any key to shut down" on the top left corner.
Now I'm on Miui 9.2.4.0 Global Stable flashed through EDL mode still the fastboot is broken
confused what the heck happened! Tried reinstalling all drivers but no luck.
p.s In the image I was just testing the flashing state using userdata.img and twrp files
vib$$$ said:
I am getting this error everytime I try to flash twrp using the fastboot commands. I used the proper flashing commands on my Redmi Note 5 pro. Bootloader is also unlocked. Adb and minimal drivers are installed as well. Please help.
target reported max download size of 536870912 bytes
sending 'recovery' (35404 KB)...
FAILED (remote: Requested download size is more than max allowed )
Click to expand...
Click to collapse
I Also faced these issues Many time in Adb
Here is the solution
Copy the boot img. Of your phone's rom
(If u r on Official nought then use that's boot img.
If on any other rom use the img. Of other rom )
And paste it to Adb folder where U pasted twrp
Then use command
That will work 100%
Easiest solution is to go with linux!
You can make this even form freshly created ubuntu live USB drive. Just go in terminal, install adb and fastboot and voila, no need for "drivers", here You work in "native" environment!
Then, agin in terminal go with:
sudo fastboot flash recovery recovery.img
or for ROM flashing, when You are in recovery, activate sideload option an again in terminal go with:
sudo adb sideload rom.zip
That's it!
Works every time!
nikhil jain984 said:
I Also faced these issues Many time in Adb
Here is the solution
Copy the boot img. Of your phone's rom
(If u r on Official nought then use that's boot img.
If on any other rom use the img. Of other rom )
And paste it to Adb folder where U pasted twrp
Then use command
That will work 100%
Click to expand...
Click to collapse
How do I get the boot image ? I have the recovery and the fastboot file of 9.2.4. where do I find the boot.img? also My device is currently on 9.2.7 so will it work if i used the boot.img of 9.2.4. Both are NOUGHAT
nikhil jain984 said:
I Also faced these issues Many time in Adb
Here is the solution
Copy the boot img. Of your phone's rom
(If u r on Official nought then use that's boot img.
If on any other rom use the img. Of other rom )
And paste it to Adb folder where U pasted twrp
Then use command
That will work 100%
Click to expand...
Click to collapse
That's what I've been doing bud... :/ No luck.
---------- Post added at 03:19 AM ---------- Previous post was at 02:58 AM ----------
vib$$$ said:
How do I get the boot image ? I have the recovery and the fastboot file of 9.2.4. where do I find the boot.img? also My device is currently on 9.2.7 so will it work if i used the boot.img of 9.2.4. Both are NOUGHAT
Click to expand...
Click to collapse
Use this link.
https://drive.google.com/file/d/18QNEWcwgoMP1HPth8VxiI0DgCVe3My8L/view?usp=drivesdk
vib$$$ said:
How do I get the boot image ? I have the recovery and the fastboot file of 9.2.4. where do I find the boot.img? also My device is currently on 9.2.7 so will it work if i used the boot.img of 9.2.4. Both are NOUGHAT
Click to expand...
Click to collapse
U can try but in My case the 9.2.7 boot image worked
gavi7566 said:
That's what I've been doing bud... :/ No luck.
---------- Post added at 03:19 AM ---------- Previous post was at 02:58 AM ----------
Use this link.
https://drive.google.com/file/d/18QNEWcwgoMP1HPth8VxiI0DgCVe3My8L/view?usp=drivesdk
Click to expand...
Click to collapse
This is the boot image of which Rom?
vib$$$ said:
This is the boot image of which Rom?
Click to expand...
Click to collapse
9.2.7.0
I had same problem , Yesterday i fixed it somehow .
S_Arya said:
I had same problem , Yesterday i fixed it somehow .
Click to expand...
Click to collapse
How??
Hi, I have a problem in my phone. Please help me install a system that has been modified by developers
You have started a new system that is not working, please watch the video
https://drive.google.com/file/d/1sQz-FjEPEKduXM6zE9JT8kEcrqKgxlHG/view?usp=sharing
https://drive.google.com/file/d/1W1m12WVzDWT7Vk2N6vcvGNglKmHT1i_8/view?usp=sharing
Try edl
" fastboot oem edl"
with mi flash 2016.4 is working fine,
ht0 said:
Try edl
" fastboot oem edl"
with mi flash 2016.4 is working fine,
Click to expand...
Click to collapse
{
"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"
}
if you didn't unlocked bootloader you can't go on try "fastboot oem unlock"
"fastboot oem unlock go"
or firstly try normal flash using "flash_all.bat"
---------- Post added at 11:28 PM ---------- Previous post was at 11:26 PM ----------
essam_alasmi said:
Click to expand...
Click to collapse
must do it on edl
if you don't know please Google it
ht0 said:
if you didn't unlocked bootloader you can't go on try "fastboot oem unlock"
"fastboot oem unlock go"
or firstly try normal flash using "flash_all.bat"
---------- Post added at 11:28 PM ---------- Previous post was at 11:26 PM ----------
must do it on edl
if you don't know please Google it
Click to expand...
Click to collapse
not work
not work
Click to expand...
Click to collapse
By the picture from MiFlash tool I see that you are trying to flash a rom while in fastboot and you can´t with locked bootloader and in your image from fastboot command is unclear if device was previously detected.
First of all start the process from the beginning.
- With device on and connected to pc type:
Code:
adb devices
and keep waiting a prompt from device screen to "always allow USB connection" within both.
- If device is detected properly, then send it to fastboot with
Code:
adb reboot bootloader
- Now repeat the operation to see if device is detected again but now in fastboot with
Code:
fastboot devices
- Now you have to ensure if your device is really Daisy (Mi A2 Lite) or Sakura (Redmi 6 Pro) for that while in fastboot type
Code:
fastboot getvar all
you will see a long list of information, the first lines will tell you about.
- If all is ok and your device is Daisy just now you can try to unlock bootloader with
Code:
fastboot oem unlock
if your device is not Daisy you won´t to unlock it this way.
- If all continues well just now you can send device to EDL mode with fastboot oem edl
- Now flash what you want through MiFlash tool.
bro
did you trying on fastboot or edl?;
if edl should work/not sure..?
but on fastboot if you try flash_all_except_torage.bat" should work
SubwayChamp said:
By the picture from MiFlash tool I see that you are trying to flash a rom while in fastboot and you can´t with locked bootloader and in your image from fastboot command is unclear if device was previously detected.
First of all start the process from the beginning.
- With device on and connected to pc type:
Code:
adb devices
and keep waiting a prompt from device screen to "always allow USB connection" within both.
- If device is detected properly, then send it to fastboot with
Code:
adb reboot bootloader
- Now repeat the operation to see if device is detected again but now in fastboot with
Code:
fastboot devices
- Now you have to ensure if your device is really Daisy (Mi A2 Lite) or Sakura (Redmi 6 Pro) for that while in fastboot type
Code:
fastboot getvar all
you will see a long list of information, the first lines will tell you about.
- If all is ok and your device is Daisy just now you can try to unlock bootloader with
Code:
fastboot oem unlock
if your device is not Daisy you won´t to unlock it this way.
- If all continues well just now you can send device to EDL mode with fastboot oem edl
- Now flash what you want through MiFlash tool.
Click to expand...
Click to collapse
is not done.. Will continue with Xiaomi Thank you
ht0 said:
bro
did you trying on fastboot or edl?;
if edl should work/not sure..?
but on fastboot if you try flash_all_except_torage.bat" should work
Click to expand...
Click to collapse
Thank you my friend did not work but I will communicate with Xiaomi
essam_alasmi said:
By the picture from MiFlash tool I see that you are trying to flash a rom while in fastboot and you can´t with locked bootloader and in your image from fastboot command is unclear if device was previously detected.
First of all start the process from the beginning.
- With device on and connected to pc type: and keep waiting a prompt from device screen to "always allow USB connection" within both.
- If device is detected properly, then send it to fastboot with
- Now repeat the operation to see if device is detected again but now in fastboot with
- Now you have to ensure if your device is really Daisy (Mi A2 Lite) or Sakura (Redmi 6 Pro) for that while in fastboot type you will see a long list of information, the first lines will tell you about.
- If all is ok and your device is Daisy just now you can try to unlock bootloader with
is not done.. Thank you bro we Eamil xiaomi
Click to expand...
Click to collapse
It looks like you didn't enable OEM unlock in developer options
SubwayChamp said:
It looks like you didn't enable OEM unlock in developer options
Click to expand...
Click to collapse
Problem I can not enter the system Also the phone was working without problems when installed the system again can not work appears on the screen of Android One I am to communicate with Xiaomi The solution will be sent to an update right For Fastboot V10.0.16.0.PDLMIXM Because my phone was on protection mod Thank you for help
Hi, I tried the solution is not resolved yet The phone hung a logo Android one
hi plz help the phone no work
Unfortunately, I tried to solve the problem, but unfortunately it did not work, and I am waiting for the release of the new update, maybe the problem will be solved with the phone
essam_alasmi said:
Unfortunately, I tried to solve the problem, but unfortunately it did not work, and I am waiting for the release of the new update, maybe the problem will be solved with the phone
Click to expand...
Click to collapse
Reboot into fastboot and type fastboot oem edl and try flash from PC again
czeckpage_FUZE said:
Reboot into fastboot and type fastboot oem edl and try flash from PC again
Click to expand...
Click to collapse
did not work it seems Error
I am waiting for an update From Xiaomi
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
What did you do to try to patch it? Why are you in adb? Does fastboot work?
craznazn said:
What did you do to try to patch it? Why are you in adb? Does fastboot work?
Click to expand...
Click to collapse
Patched the boot.img using magisk and then flashed it. After patching, it totally cant boot and can only boot to bootloader.
tried alot of version of MSMtool and it will always fail with param preload error...
Then tried manually recover via extracting the payload using python then using adbtools to wipe and flash but it will also fail because some img files are unable to flash over to the phone...
Any other solutions?
U not able to flash boot the stock boot.img?
i am able to flash the stock boot.img to the phone but some critical img files will come out with
FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
You need to be in fastbootd,
Code:
fastboot reboot fastboot
craznazn said:
You need to be in fastbootd,
Code:
fastboot reboot fastbootd
Click to expand...
Click to collapse
Nope not working too...
{
"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"
}
danjcxie said:
Nope not working too...
View attachment 5281163
Click to expand...
Click to collapse
Sorry, fastboot reboot fastboot (without the d)
@danjcxie
To be honest, I would download the rom and boot with the recovery image instead, I'll upload the image collection...
Will post a link here once it's up.
Actually, just noticed there isn't a recovery image, so boot to the default boot.img using fastboot, then see if the storage shows on your computer, copy the latest default rom over to the main storage folder then then go into Settings > System > System Updates and use the cog to do a local update using the rom zip.
That should re-install everything back to default, you might get lucky and still have all your data
My collection is for the Europe build FYI:
OP9P_Image_Collection_BA_11.2.3.3.zip | by djsubterrain for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
MD5 : 00227014483b4913a2624fac6f492434
So you would reboot the phone into fastboot mode by holding vol up during boot
Once you are in fastboot mode connect the phone to your computer
Test that the computer can see it properly using fastboot devices
You should see a number returned, if so then your computer is recognising the phone, if you don't then try installing the latest drivers from here
If fastboot can see the device properly then copy the default boot.img to the same folder as your fastboot.exe and type the following :
fastboot boot boot.img
You should see a message saying it's transferring it to the phone, then it should boot the phone using it, it's slower than a normal boot but, if everything else on the phone is ok, then you should see it booted and it should accept your lock method
Once you get into the phone using that boot.img, try connecting the phone to your computer and see if it's recognised, if it is then copy over the latest stock rom to your main storage folder, then go to Settings > System > System Updates and use the cog to do a local update using the rom zip
I'm guessing it should let you because it will see a difference between your boot image and the one from the rom.
MSM tool for LE2125 - 11.2.2.2.LE15AA
User Type of Others for login MSM Tool for LE2125 - 11.2.2.2.LE15AA Drivers Mirrors: (provided by @djsubterrain) MSM Tool : https://sourceforge.net/projects/djsubterrain/files/OnePlus 9 Pro/OP9P_MSM_Tool.zip/download MD5 ...
forum.xda-developers.com
New problem... After i did fastboot reboot fastboot, it shows low battery whole day and is unable to charge totally... it has been charging the whole day now and totally cant turn on at all.
it keeps showing the lightning sign in the centre of the circle keeps blinking and dies off
danjcxie said:
New problem... After i did fastboot reboot fastboot, it shows low battery whole day and is unable to charge totally... it has been charging the whole day now and totally cant turn on at all.
it keeps showing the lightning sign in the centre of the circle keeps blinking and dies off
View attachment 5281971
Click to expand...
Click to collapse
Turn it off and try charging it
Also "fastboot reboot fastboot" isn't a valid command, there is an adb command "adb reboot bootloader" but that can only be run from within your rom from when you are in recovery with the phone connected
See here :
Fastboot Commands: A Beginner’s Guide
With this guide of ours, you'll be able to learn all the fastboot commands and their syntax. We've also posted some hidden commands which you never knew.
android.tutorials.how
#To reboot your device
fastboot reboot
#To reboot your device to fastboot mode
fastboot reboot-bootloader
Click to expand...
Click to collapse
djsubterrain said:
Turn it off and try charging it
Click to expand...
Click to collapse
Yup tried. Everytime you just plug in the charging cable, it will just auto boot up and show the charging sign
danjcxie said:
Yup tried. Everytime you just plug in the charging cable, it will just auto boot up and show the charging sign
Click to expand...
Click to collapse
Yeah that symbol isn't what I get, I get a blue lightning sign with the percentage underneath. Are you running OxygenOS or ColorOS?
I think it might be time for you to contact OnePlus support
djsubterrain said:
Turn it off and try charging it
Also "fastboot reboot fastboot" isn't a valid command, there is an adb command "adb reboot bootloader" but that can only be run from within your rom from when you are in recovery with the phone connected
See here :
Fastboot Commands: A Beginner’s Guide
With this guide of ours, you'll be able to learn all the fastboot commands and their syntax. We've also posted some hidden commands which you never knew.
android.tutorials.how
Click to expand...
Click to collapse
Wtf are you talking about. fastboot reboot fastboot is literally the only way to get into fastbootd if you can't get to recovery or boot normally.
Regarding battery, that I'm not sure, hopefully someone can help
craznazn said:
OP
Wtf are you talking about. fastboot reboot fastboot is literally the only way to get into fastbootd if you can't get to recovery or boot normally.
Regarding battery, that I'm not sure, hopefully someone can help
Click to expand...
Click to collapse
OK, firstly, who the hell do you think you're talking to?
Secondly, did you look at the link I posted?
djsubterrain said:
OK, firstly, who the hell do you think you're talking to?
Secondly, did you look at the link I posted?
Click to expand...
Click to collapse
Who the hell are you? Why the hell are you linking "tutorials.how"?
fastboot/fastboot.cpp - platform/system/core - Git at Google
android.googlesource.com
Lines 2178, source tells you to reboot fastbootd by reboot fastboot.
Show me it's not a valid command, go on
craznazn said:
Who the hell are you? Why the hell are you linking "tutorials.how"?
fastboot/fastboot.cpp - platform/system/core - Git at Google
android.googlesource.com
Lines 2178, source tells you to reboot fastbootd by reboot fastboot.
Show me it's not a valid command, go on
Click to expand...
Click to collapse
Go ahead and help the guy solve his problem.
Just remember it's fastboot, not fastbootd.
Now, how do you block people on here again?
danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
use the MSM Tool with the latest drivers
QDLoader HS-USB Driver_64bit_Setup
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
This just worked for me minutes ago
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
i downloaded Indian Variant LE2121 while my phone is LE2120 ant it worked
Hello,
Fist, I will say it, I am a total newbie in rooting. So, I followed one of the excellent guides here. Little by little, I begin to understand the process. So I have succeeded to root my pixel 6 pro using magisk.
Then, Android 13 has come. I think, pretty sure, that the bootloader need to be locked again to update. At least, I tried, I removed magisk and so the root, but the update fails.
Then I have reset the phone. Now I try to lock again the bootloader. However, withadb reboot bootloader, I cannot see the phone. fastboot devices shows nothing.
fastboot flashing lock stay on <waiting for any device>
Then I tried adb reboot fastboot. Here, the phone is found when I type fastboot devices. However fastboot flashing lock displays:
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
Click to expand...
Click to collapse
So, my questions:
1.) do I really need to lock the bootloader to update to android 13 ?
2.) what did I do as mistake ? I want to understand, especially if one day I need to sell the phone, I want to be able to lock again the bootloader. Is fastboot flashing lock the right command ?
Ralendil said:
Hello,
Fist, I will say it, I am a total newbie in rooting. So, I followed one of the excellent guides here. Little by little, I begin to understand the process. So I have succeeded to root my pixel 6 pro using magisk.
Then, Android 13 has come. I think, pretty sure, that the bootloader need to be locked again to update. At least, I tried, I removed magisk and so the root, but the update fails.
Then I have reset the phone. Now I try to lock again the bootloader. However, withadb reboot bootloader, I cannot see the phone. fastboot devices shows nothing.
fastboot flashing lock stay on <waiting for any device>
Then I tried adb reboot fastboot. Here, the phone is found when I type fastboot devices. However fastboot flashing lock displays:
So, my questions:
1.) do I really need to lock the bootloader to update to android 13 ?
2.) what did I do as mistake ? I want to understand, especially if one day I need to sell the phone, I want to be able to lock again the bootloader. Is fastboot flashing lock the right command ?
Click to expand...
Click to collapse
You don't need to do all of that to upgrade to android 13. You can read how to upgrade to android 13 here: https://forum.xda-developers.com/t/...-6-pro-bootloader-central-repository.4352027/
as well as here: https://forum.xda-developers.com/t/pixel-6-pro-easy-step-by-step-unlock-root-update.4361847/
it is a long thread with a lot of information, so I'll just give you an adlibbed version of how to upgrade
I read that you have removed root. You can re-root after upgrading. Make sure your bootloader is unlocked first.
First make sure you have the latest sdk platform tools version here: https://developer.android.com/studio/releases/platform-tools
Download the android 13 factory image here: https://developers.google.com/android/images
Extract the platform tools and the factory image, and make sure the flash-all.bat file is in the same location as adb.exe and fastboot.exe
If you want to keep your data, do this. If you don't want to lose your data and don't mind wiping your phone, skip this step and just run flash-all.bat in fastboot.
Edit the flash-all.bat file and remove the -w flag from the
Code:
fastboot update -w image-raven-tp1a.220624.021.zip
command. So it'll just be
Code:
fastboot update image-raven-tp1a.220624.021.zip
Save it, edit again just to double check that -w flag is gone. If it is, reboot your phone back into fastboot and run flash-all.bat.
It'll upgrade and do everything for you. You're on Android 13 now and your data is still intact.
Once your phone is booted, you can patch the boot image from the factory image you downloaded with Magisk and flash it in fastboot again by doing fastboot flash boot --slot=all (drag and drop patched boot.img here) OR type in the file name magisk_patched-xxxxxxxxxx.img. Then you will have root.
If you want to go back to complete factory with a locked bootloader, run Android Flash Tool from Google here: https://flash.android.com/welcome?continue=/back-to-public
Make sure "Wipe Device", "Lock Bootloader", and "Force Flash All Partitions" are checked.
You could always try the Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own). It's possible you could also take advantage of it's new option to flash only the 13 bootloader to both slots, and then will update the current slot to 13 completely.
Lughnasadh said:
FYI: Even though Android Flash Tool does not flash the whole image to both slots, they have added an option to flash the A13 bootloader to the inactive slot. This may be the easiest option to use when updating to A13 from A12.
Just to be clear, when updating to A13 from A12 a prompt will show up asking whether you want to also flash the bootloader to the inactive slot as well. It doesn't show up in the regular tick boxes.
{
"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"
}
Click to expand...
Click to collapse
FYI, you most definitely didn't need to re-lock the bootloader. Also, a pro tip for rooters. Once you unlock a device's bootloader, never ever re-lock it except in very rare circumstances. This didn't count as rare before you consult us.
I would have loved that it would be a solution.
It would allow me only to install android 12... and locking the bootloader make me affraid… I think I will never be able to unlock it cause I can’t use bootloader (see under)
For now, I try to make bootloader drivers working.
Every time I reboot to bootloader, the phone is not recognized by the computer and no adb/fastboot command can be used. So, I cannot use the flash-all.bat script.
Also, now when I use adb reboot fastboot the fastboot screen appears, then bootloader is loaded immediately...
I can’t believe I will spend several hours to be able to install that… I am stuck.
I tried to uninstall several drivers and reinstall drivers, but no changes... or yes a change. Now it is worst, Pixel 6 pro isn’t listed in device manager, and adb bootloader driver has disapear replaced by an adb driver line. Anyways, bootloader driver was never activated.
Edit: I should add that the update through the phone doesn’t work.
Don’t know why... the interface for google android flash tool changed... and now I was able to choose the version and I could flash the two slot with a13 bootloader.
Thanks for the idea...
Even if… I would love to understand why I did not succeed to install it...
Final edit: Android 13 has been successfully installed
Now, time to root it
yo guys, i have a little trouble with twrp, it is flashing in slot b and dont boot, or flashing in slot a and dont boot the system, tried 3 other twrp & ofox, maybe you'll know whats wrong?
sewerfract said:
yo guys, i have a little trouble with twrp, it is flashing in slot b and dont boot, or flashing in slot a and dont boot the system, tried 3 other twrp & ofox, maybe you'll know whats wrong?
Click to expand...
Click to collapse
Last version
https://dl.akr-developers.com/?dir=skkk/TWRP/A12/v6.0_A12
Installation
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
NOSS8 said:
fastboot boot twrp.img
Click to expand...
Click to collapse
if fastboot boot would work i would not writing here
sewerfract said:
if fastboot boot would work i would not writing here
Click to expand...
Click to collapse
You have not specified it.
So you have installed a TWRP with fastboot and now the Fastboot mode no longer works?
And specify what phone you have.
NOSS8 said:
You have not specified it.
So you have installed a TWRP with fastboot and now the Fastboot mode no longer works?
And specify what phone you have.
Click to expand...
Click to collapse
fastboot still working, no problems with it. twrp just didnt flash with fastboot boot twrp.img, i can send vids how it looks.
poco f3 alioth global
sewerfract said:
fastboot still working, no problems with it. twrp just didnt flash with fastboot boot twrp.img, i can send vids how it looks.
poco f3 alioth global
Click to expand...
Click to collapse
With this one?
https://dl.akr-developers.com/?file=skkk/TWRP/A12/v6.0_A12/[BOOT]3.6.2_12-RedmiK40-POCOF3-Mi11X_v6.0_A12-alioth-skkk_b3647986.zip
NOSS8 said:
With this one?
https://dl.akr-developers.com/?file=skkk/TWRP/A12/v6.0_A12/[BOOT]3.6.2_12-RedmiK40-POCOF3-Mi11X_v6.0_A12-alioth-skkk_b3647986.zip
Click to expand...
Click to collapse
yeah, that first twrp i ever tried to flash
sewerfract said:
yeah, that first twrp i ever tried to flash
Click to expand...
Click to collapse
the bootloader is unlocked?
If so post a screenshot of the fastboot command.
NOSS8 said:
the bootloader is unlocked?
If so post a screenshot of the fastboot command.
Click to expand...
Click to collapse
of course unlocked.
{
"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"
}
sewerfract said:
yo guys, i have a little trouble with twrp, it is flashing in slot b and dont boot, or flashing in slot a and dont boot the system, tried 3 other twrp & ofox, maybe you'll know whats wrong?
Click to expand...
Click to collapse
You need to provide full details of what you are doing. Are you flashing a ROM? Did you format the data partition after flashing the ROM? etc. etc.
sewerfract said:
of course unlocked.
Click to expand...
Click to collapse
try with power shell
DarthJabba9 said:
You need to provide full details of what you are doing. Are you flashing a ROM? Did you format the data partition after flashing the ROM? etc. etc.
Click to expand...
Click to collapse
Okay. I flash stock fastboot miui 13.0.5, next i want flash a twrp with "fastboot boot twrp.img" command, but as i wrote above, it didn't flash, my phone just turned off and after turning it on it start miui, "fastboot reboot recovery" command sent me in stock miui recovery. Today I tried flash twrp with "fastboot flash boot_a twrp.img" command, it flashed, but after i do this system stop booting, worked only twrp and fastboot mode. I also tried "fastboot flash boot_b" command but like "fastboot boot" it didn't flash twrp
Download Platform tool
command is
NOSS8 said:
Download Platform tool
command is
View attachment 5728813
Click to expand...
Click to collapse
i try it tomorrow, thanks
sewerfract said:
Okay. I flash stock fastboot miui 13.0.5, next i want flash a twrp with "fastboot boot twrp.img" command, but as i wrote above, it didn't flash, my phone just turned off and after turning it on it start miui, "fastboot reboot recovery" command sent me in stock miui recovery. Today I tried flash twrp with "fastboot flash boot_a twrp.img" command, it flashed, but after i do this system stop booting, worked only twrp and fastboot mode. I also tried "fastboot flash boot_b" command but like "fastboot boot" it didn't flash twrp
Click to expand...
Click to collapse
Try this:
Code:
fastboot devices
fastboot flash boot twrp.img
fastboot reboot recovery
sewerfract said:
i try it tomorrow, thanks
Click to expand...
Click to collapse
You are using ADB.exe instead of Fastboot.exe.
NOSS8 said:
You are using ADB.exe instead of Fastboot.exe.
Click to expand...
Click to collapse
always using it
sewerfract said:
always using it
Click to expand...
Click to collapse
It is a Fastboot command,that s all.