Related
Hi all,
After "successfully" installing TWRP, which already took me lots of time due to strange errors, i can not go into TWRP mode. Only in Standard Recovery.
I followed every tip which i found how to exit the fastboot mode succesfully (pressing Vol+ & Power / Removing USB Cable / Tried TeamSpains Automatic Installer), but nothing worked. Most of the time just a black screen and Blue Led.
The only thing i did not do is typing in "fastboot reboot" because i read that this caused a brick on a few Le Max 2.
Any suggestions how i could finally install TWRP ?
Thanks a lot!
Wow, I'm almost in the same situation, but mine is worse - Neither standart recovery, nor TWRP start.
Can you confirm, that your bootloader is unlocked?
Because in my case, the bootloader was locked and I managed to corrupt the recovery by installing TWRP forcefully, which brought me to the continious boot loop in the recovery with no os loaded at all.
check these commands in fastboot:
fastboot oem unlock (fastboot oem unlock-go worked for me)
After it is unlocked -> fastboot flash recovery bla-bla.img -> fastboot boot bla-bla.img, where bla-bla is your twrp image.
The clue is to use proper version of TWRP from Teamspain or from the thread Official TWRP. You can always use fastboot boot for the first try. And unlock the bootloader first.
Regards Filozof71
Sent from my Le X820 using Tapatalk
RovnyiK said:
Wow, I'm almost in the same situation, but mine is worse - Neither standart recovery, nor TWRP start.
Can you confirm, that your bootloader is unlocked?
Because in my case, the bootloader was locked and I managed to corrupt the recovery by installing TWRP forcefully, which brought me to the continious boot loop in the recovery with no os loaded at all.
check these commands in fastboot:
fastboot oem unlock (fastboot oem unlock-go worked for me)
After it is unlocked -> fastboot flash recovery bla-bla.img -> fastboot boot bla-bla.img, where bla-bla is your twrp image.
Click to expand...
Click to collapse
Yes my device is unlocked. I did it again now with exactly your commands --> after fastboot boot recovery.img --> Black screen and blue LED
Filozof71 said:
The clue is to use proper version of TWRP from Teamspain or from the thread Official TWRP. You can always use fastboot boot for the first try. And unlock the bootloader first.
Regards Filozof71
Sent from my Le X820 using Tapatalk
Click to expand...
Click to collapse
What do you exactly mean with proper version of TWRP? And yes, i am always using fastboot, but it doesnt help. My phone is also unlocked... I havent got any more ideas
Kampfgans said:
What do you exactly mean with proper version of TWRP? And yes, i am always using fastboot, but it doesnt help. My phone is also unlocked... I havent got any more ideas
Click to expand...
Click to collapse
Proper I meant one of this distributions and newest. What is the result of "fastboot devices" command?
regards Filozof71
Is your device 4/64, or 4/32 gb?
Filozof71 said:
Proper I meant one of this distributions and newest. What is the result of "fastboot devices" command?
regards Filozof71
Click to expand...
Click to collapse
Yes, i used the newest official TWRP. Fastboot Devices shows my connected device "blablavla fastboot", so my device is connecting properly
RovnyiK said:
Is your device 4/64, or 4/32 gb?
Click to expand...
Click to collapse
4/32
i was in same situation guys, things which worked for me is official twrp, flash then immediately hold vol up and power button untill you see le eco recovery appearing on the screen which ll be followed by twrp, if u hold the two button and leave them after getting the first vibration, device boots into system and after that twrp is again overwritten and no use going into recovery afterwards...
Kampfgans said:
Yes, i used the newest official TWRP. Fastboot Devices shows my connected device "blablavla fastboot", so my device is connecting properly
Click to expand...
Click to collapse
Hello again. Blue LED means something like inconsistent version with installed system. Try another TWRP. What version did you run before flashing TWRP? Is it x820 or maybe X822 Indian version?
Regards Filozof71
Sent from my Le X820 using Tapatalk
hi
im in the same problem here
cant understand why its not working... spending lots of time on this
what version of twrp you all guys try and its work for you ?
Mpro747 said:
hi
im in the same problem here
cant understand why its not working... spending lots of time on this
what version of twrp you all guys try and its work for you ?
Click to expand...
Click to collapse
TRY the "TWRP_5.8_TeaMSpaiN.img" TWRP using fastboot command, which is work for me, my phone is running eui5.8 previously...
link: h ttp://choimobile.vn/threads/cai-twrp-root-leeco-le-max-2-x820-x821.68026/
If incorrect twrp install, either cannot load into twrp(black screen with unusual led light up), have twrp screeen but freeze, or can load into twrp but no touch at all.
Mpro747 said:
hi
im in the same problem here
cant understand why its not working... spending lots of time on this
what version of twrp you all guys try and its work for you ?
Click to expand...
Click to collapse
Try twrp manager app or the official twrp app. I had problems with teamspain version, appeared not to be working (black screen) but after about 30 seconds it worked. With the latest official version 3.0.2-1-x2 which i installed with twrp manager it boots up immediately
I think as soon as you type fastboot reboot you need to hold power + Volume up button to load the TWRP. Else default recovery gets reinstated.
try to boot into twrp, maybe that will work it described in step 6.4 in this tutorial:
http://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
Hello friends,
I have an OPX and I did some mistakes with it during my attemp to update it to the latest Oxygen 3.1.3.
I had stock rooted 2.1.2 Oxygen OS with Kingroot and TWRP installed. I downloaded the zip of the ROM
for 3.1.3 from Oneplus and tried to flash it. It came up an error so I wiped system cache and data and tried again
but the same errors came up. Then I tried to flash the stock recovery .img file from TWRP to get the stock recovery
and try to flash the ROM from there. When I attempted to flash the stock recovery it asked me about the partition
I wanted to install it and I chose recovery.Installation seemed successfull and I rebooted to recovery.After that I had
no recovery and no system to boot.When I try to boot to recovery I only get the oneplus logo. When I try to boot to
system I get oneplus logo and "Powered by android" at the bottom. Fastboot mode seems ok. So I thought i could flash
everything back with adb BUT no tool or program recognizes correctly in any mode.In device manager of windows 10
the device is listed under "Kedacom Usb device" section with name "Android Bootloader Interface".
Please Help me.
zafiris said:
Hello friends,
I have an OPX and I did some mistakes with it during my attemp to update it to the latest Oxygen 3.1.3.
I had stock rooted 2.1.2 Oxygen OS with Kingroot and TWRP installed. I downloaded the zip of the ROM
for 3.1.3 from Oneplus and tried to flash it. It came up an error so I wiped system cache and data and tried again
but the same errors came up. Then I tried to flash the stock recovery .img file from TWRP to get the stock recovery
and try to flash the ROM from there. When I attempted to flash the stock recovery it asked me about the partition
I wanted to install it and I chose recovery.Installation seemed successfull and I rebooted to recovery.After that I had
no recovery and no system to boot.When I try to boot to recovery I only get the oneplus logo. When I try to boot to
system I get oneplus logo and "Powered by android" at the bottom. Fastboot mode seems ok. So I thought i could flash
everything back with adb BUT no tool or program recognizes correctly in any mode.In device manager of windows 10
the device is listed under "Kedacom Usb device" section with name "Android Bootloader Interface".
Please Help me.
Click to expand...
Click to collapse
Follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and update to 3.1.3 with stock recovery
cva_kabil said:
Follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and update to 3.1.3 with stock recovery
Click to expand...
Click to collapse
I have already tried to do this guide. Windows says the best drivers are already installed for this device and will not install the qualcom ones. Also the program just waits for a device to be connected to start the process of unbricking.Thanks for answering
zafiris said:
I have already tried to do this guide. Windows says the best drivers are already installed for this device and will not install the qualcom ones. Also the program just waits for a device to be connected to start the process of unbricking.Thanks for answering
Click to expand...
Click to collapse
But still u can acess fastboot right? Without any problem?
cva_kabil said:
But still u can acess fastboot right? Without any problem?
Click to expand...
Click to collapse
I think so, yes. When I enter fastboot mode there is the oneplus logo and "fastboot mode" written under it.
zafiris said:
I think so, yes. When I enter fastboot mode there is the oneplus logo and "fastboot mode" written under it.
Click to expand...
Click to collapse
Yes it is fastboot. now connect ur mobile to pc and type "fastboot devices" in adb cmd screen.. if it shows your device info,then u can flash stock recovery and make a fresh start.
cva_kabil said:
Yes it is fastboot. now connect ur mobile to pc and type "fastboot devices" in adb cmd screen.. if it shows your device info,then u can flash stock recovery and make a fresh start.
Click to expand...
Click to collapse
Yes i know. Whenever I type fastboot devices nothing happens. No device gets listed.
I had the same problem, but the Guide to Unbrick worked well.
Now, I cannot flash anything, because Fastboot doesn't recognize my phone. I'm stuck in stock.
cva_kabil said:
Follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and update to 3.1.3 with stock recovery
Click to expand...
Click to collapse
thank you very much this guide finally worked!! It was my mistake.I was booting first on fastboot mode and then plugging in the usb cable
whereas the guide says to keep pressing volume up and then plug it in which is was made it work!
zafiris said:
thank you very much this guide finally worked!! It was my mistake.I was booting first on fastboot mode and then plugging in the usb cable
whereas the guide says to keep pressing volume up and then plug it in which is was made it work!
Click to expand...
Click to collapse
Glad u did ?
The Fastboot installation process goes all fine but device boots into Mi-Recovery by default. Currently Using Miui 9 Dev Rom (7.12.21 | Beta). This happened after I flashed the stock Dev rom after accidentally bricking my phone while unrooting through SuperSu's Full Unroot Option.
Bootloader is unlocked. Help asap plz.
Using The 4Gb 64Gb variant.
Hi,
if you flash Global Developer rom using Fastboot method, you will always flash a stock recovery with it.
There is a great manual how to unlock your device on official CZ and SK webpage created by local admins.
Just go to miuios.cz (translate it to ENG using browser like chrome or others) create an account to be able see the links.
Then on the main page scroll down to Redmi note 4 and check
[NÁVODY] - základné /Bootloader/TWRP/MIUI/ROOT
there is everything you need to unlock device with software you need.
All credits to miuios team.
Crys2perk said:
The Fastboot installation process goes all fine but device boots into Mi-Recovery by default. Currently Using Miui 9 Dev Rom (7.12.21 | Beta). This happened after I flashed the stock Dev rom after accidentally bricking my phone while unrooting through SuperSu's Full Unroot Option.
Bootloader is unlocked. Help asap plz.
Using The 4Gb 64Gb variant.
Click to expand...
Click to collapse
I think is a problem about installation process (I had the same problem with another phone), but you can still access twrp with your computer. Just use this command: Fastboot boot "twrp.img".
Update "twpr.img" with your own twrp´s file name.
Wait untill phone´s reboot (more than 15s.)
Then use it as usual
Good luck
XiaomiRedUser said:
I think is a problem about installation process (I had the same problem with another phone), but you can still access twrp with your computer. Just use this command: Fastboot boot "twrp.img".
Update "twpr.img" with your own twrp´s file name.
Wait untill phone´s reboot (more than 15s.)
Then use it as usual
Good luck
Click to expand...
Click to collapse
I ran into the same problem after unlocking the bootlader:
TWRP would not install -> [Vol+] + [Power] started only the MIUI recovery.
But after some search, I found that you have to:
enter in a terminal "fastboot flash recovery twrp-x.x.x-x-mido.img"
enter after that "fastboot boot twrp-x.x.x-x-mido.img"
My Note 4 then started in TWRP.
EDIT:
Corrected step 2
Crys2perk said:
The Fastboot installation process goes all fine but device boots into Mi-Recovery by default. Currently Using Miui 9 Dev Rom (7.12.21 | Beta). This happened after I flashed the stock Dev rom after accidentally bricking my phone while unrooting through SuperSu's Full Unroot Option.
Bootloader is unlocked. Help asap plz.
Using The 4Gb 64Gb variant.
Click to expand...
Click to collapse
After flashing twrp, directly from terminal boot to twrp and flash super su along with lazyflasher, after that reboot, when rebooted install official twrp app and super su app, and using the twrp app once again install twrp. That shld do.
MyNameIsRage said:
After flashing twrp, directly from terminal boot to twrp and flash super su along with lazyflasher, after that reboot, when rebooted install official twrp app and super su app, and using the twrp app once again install twrp. That shld do.
Click to expand...
Click to collapse
Tried This Still Not Working.
I directly booted from fastboot to TWRP
I Magisk Rooted then , which works fine now.
tinaeire said:
I ran into the same problem after unlocking the bootlader:
TWRP would not install -> [Vol+] + [Power] started only the MIUI recovery.
But after some search, I found that you have to:
enter in a terminal "fastboot flash recovery twrp-x.x.x-x-mido.img"
enter after that "adb reboot recovery"
My Note 4 then started in TWRP.
Click to expand...
Click to collapse
How did you get ADB commands to work in Fastboot? Having the same TWRP problem right now.
dancress said:
How did you get ADB commands to work in Fastboot? Having the same TWRP problem right now.
Click to expand...
Click to collapse
From a terminal from your PC. With a Windows open "cmd.exe".
tinaeire said:
From a terminal from your PC. With a Windows open "cmd.exe".
Click to expand...
Click to collapse
ADB doesn't work in Fastboot... fastboot.exe does. And that can only boot into itself (the bootloader), not the recovery.
Anyway, I solved the problem. Mine is a 4X not a Note 4X. Damn you Xiaomi... they are exactly alike!
dancress said:
ADB doesn't work in Fastboot... fastboot.exe does. And that can only boot into itself (the bootloader), not the recovery.
Anyway, I solved the problem. Mine is a 4X not a Note 4X. Damn you Xiaomi... they are exactly alike!
Click to expand...
Click to collapse
You are right, my mistake.
adb does not work and I mixed it up.
But I did test 'fastboot boot twrp-x.x.x-x-mido.img' in fastboot mode and it worked on my Note 4.
tinaeire said:
I ran into the same problem after unlocking the bootlader:
TWRP would not install -> [Vol+] + [Power] started only the MIUI recovery.
But after some search, I found that you have to:
enter in a terminal "fastboot flash recovery twrp-x.x.x-x-mido.img"
enter after that "fastboot boot twrp-x.x.x-x-mido.img"
Click to expand...
Click to collapse
As others have reported, I had the same issue too. I was able to boot to TWRP with the fastboot boot command above, but it looks like after you boot to the stock ROM (mine was MIUI V9.2.1.0.NCFMIEK as far as I remember), the TWRP recovery gets replaced by the stock one. After flashing LineageOS (official lineage-14.1-20180331-nightly-mido-signed.zip), I can now properly reboot to TWRP with Vol+ & Power.
Thanks for the tip @tinaeire :good:
Why aren't devs mentioning this in the instructions right after the recovery flash command? I'll never understand. I guess it's more MIUI's fault for being so weird about the bootloader.
TWRP boots stable
Press VOLUME-UP and POWER together, when you feel the vibration release the buttons.
-> boots into TWRP
If you hold the two buttons until you see the TWRP logo flash up and release them at that moment -> boots to MIUI.
Did that with phone mentioned below, TWRP 3.2.1, and MIUI Global 9.2 Stable.
I am also facing the same problem, please someone guide me thoroughly how to root my xiaomi redmi note 4 snapdragon global stable version. i have successfully unlocked my phone but i can't start it up in twrp recovery mode. please tell me all the steps and files necessary.
habib_561 said:
I am also facing the same problem, please someone guide me thoroughly how to root my xiaomi redmi note 4 snapdragon global stable version. i have successfully unlocked my phone but i can't start it up in twrp recovery mode. please tell me all the steps and files necessary.
Click to expand...
Click to collapse
Once you flash TWRP via fastboot then use command fastboot boot xxx.img
So, you'll be able to boot to TWRP, next flash magisk for MIUI, install lazyflasher.zip and reboot and check if TWRP sticks.
i have the same issue after flash the twrp and it reboot back to mi recovery instead. However i am using redmi K20.
Found out that the issue is the twrp.img file that you flash must be a correct one that your download for your device.
If it is not the correct file ( my case is using redmi k20 pro instead of redmi k20 twrp.img), i will always failed and stay at mi recovery.
Sir, i have updated my mi note 10 lite to android 11and after restart it works fine. But the problem is that when i reboot to recovery to install root, because i have installed twrp before. Unfortunately, its stuck on fastboot screen.
Can you help me out to solve this problem.
I tried to flash twrp but its not mounting partition, i reboot to recovery again but its go to fastboot mode again
I tried to flash fastboot rom through mi flash tool it errors because anti rollback.(android 10)
Still i am finding Android 11 fastboot images but not found.
You can contact dennis via Instagram that man reply you
Mi note 10 lite User 😭😭 said:
You can contact dennis via Instagram that man reply you
Click to expand...
Click to collapse
Okay i dm you now check please
haadii said:
Sir, i have updated my mi note 10 lite to android 11and after restart it works fine. But the problem is that when i reboot to recovery to install root, because i have installed twrp before. Unfortunately, its stuck on fastboot screen.
Can you help me out to solve this problem.
I tried to flash twrp but its not mounting partition, i reboot to recovery again but its go to fastboot mode again
I tried to flash fastboot rom through mi flash tool it errors because anti rollback.(android 10)
Still i am finding Android 11 fastboot images but not found.
Click to expand...
Click to collapse
extract the official recovery from the global fastboot rom and flash through cmd to recover the boot, then wipe from the recovery and you will return to miui 12.1.1
what i'm trying to figure out is if i can go back to the previous version of android without risking to crash the device.
I ran the fastboot getvar anti command and the result was Anti: 2 but I am not quite clear what that means.
I am a new user at Xiaomi.
leinadagisiaol said:
what i'm trying to figure out is if i can go back to the previous version of android without risking to crash the device.
I ran the fastboot getvar anti command and the result was Anti: 2 but I am not quite clear what that means.
I am a new user at Xiaomi.
Click to expand...
Click to collapse
I tried it. When flashing fastboot images thorough miflash its error in anti roll back check... Or may your device hard brick
Now i am here with a new fu*kin error..
Any solution for this. I don't want to lose data
If stuck in fastboot mode, type "fastboot continue" in adb and it will proceed with boot
ApexPrime said:
If stuck in fastboot mode, type "fastboot continue" in adb and it will proceed with boot
Click to expand...
Click to collapse
No. Its not my problem now
My problem is mentioned above
Bro i think you can access your files from computer in recovery so make a backup and flash official firmware using miflash tool. I don't think there's any other way.
haadii said:
Now i am here with a new fu*kin error..
Any solution for this. I don't want to lose data
Click to expand...
Click to collapse
Before installing custom recovery and installing custom rom, it is recommended to backup.
You installed the recovery well, but in order to install custom ROMs you have to format and restart the recovery, then pass the ROM you want to flash and reboot system.
haadii said:
I tried it. When flashing fastboot images thorough miflash its error in anti roll back check... Or may your device hard brick
Click to expand...
Click to collapse
I managed to go back to miui 11 version 11.0.8
leinadagisiaol said:
I managed to go back to miui 11 version 11.0.8
Click to expand...
Click to collapse
How?? Can you show or tell me the process!! I don't like Android 11
haadii said:
How?? Can you show or tell me the process!! I don't like Android 11
Click to expand...
Click to collapse
Good evening ..
For all those interested in downloading the official ROM version of the Xiaomi mi note 10 Lite, I have news for you, at least for those who want and have not tried.
I tried the method of saving the MiFlash folder on Disk C, in the same way I did with the global ROM of miui 11.0.8 fastboot, to the latter I changed the name of the folder to a shorter one (example Miui11.0.8), then boot in fastboot mode and run my flash running the ROM (Miui11.0.8) and the result obtained is that, I'm back on Android 10 with miui 11.0.8.
I share this information to give security to all those who had doubts about this and did not dare to try.
This data I extracted from various forums and pointed to it to give credit to all those who previously published it.
Remember that the bootloader must be unlocked.
Regards.
Hi everybody
I've got a problem...
Downloaded latest OTA update from "xiaomi.eu", agreed to install, the phone then rebooted in to fastboot mode and does nothing else.
Rebooted the phone with adb command "fastboot continue" and this went well...it rebooted the system.
Now every time i restart the phone it reboots in to fastboot mode and i have to "fastboot continue" again.
I am also not able to enter recovery because the phone always enters fastboot mode.
Reinstalled recovery (Twrp-3.4.2B_toco_by.alex.msk1407.img) via ADB succesfully, but when i "fastboot reboot recovery" it reboots back into fastboot.
I'm also not able to boot into EDL mode.
Any solution?
Thanks
"MI NOTE LITE 8GB/128GB" running "MIUI by xiaomi.eu 12.1.1 | Stable 12.1.1.0(RFNMIXM)
salsaecoentros said:
Hi everybody
I've got a problem...
Downloaded latest OTA update from "xiaomi.eu", agreed to install, the phone then rebooted in to fastboot mode and does nothing else.
Rebooted the phone with adb command "fastboot continue" and this went well...it rebooted the system.
Now every time i restart the phone it reboots in to fastboot mode and i have to "fastboot continue" again.
I am also not able to enter recovery because the phone always enters fastboot mode.
Reinstalled recovery (Twrp-3.4.2B_toco_by.alex.msk1407.img) via ADB succesfully, but when i "fastboot reboot recovery" it reboots back into fastboot.
I'm also not able to boot into EDL mode.
Any solution?
Thanks
"MI NOTE LITE 8GB/128GB" running "MIUI by xiaomi.eu 12.1.1 | Stable 12.1.1.0(RFNMIXM)
Click to expand...
Click to collapse
Just format userdata. In fastboot mode command. Fastboot format userdata
Then flash new stock fastboot images of eu in miflash.
Note,
Backup your data first
Good Day. I have concern but after updating to Android 12. Currently my Mi Note 10 Lite is experiencing stuck in fastboot and mi logo. I already tried flashing using MIFlash 2020 but the error occur is "Erase is not allowed in Lock State".I also used MI PC Suite but it cant read my device (maybe because of lock state also). Even in MI-Unlock (batch_unlock application) it says its locked but when I sign-in it doesnt give permission to unlock (I used yahoo account).
goroshigeno56 said:
Good Day. I have concern but after updating to Android 12. Currently my Mi Note 10 Lite is experiencing stuck in fastboot and mi logo. I already tried flashing using MIFlash 2020 but the error occur is "Erase is not allowed in Lock State".I also used MI PC Suite but it cant read my device (maybe because of lock state also). Even in MI-Unlock (batch_unlock application) it says its locked but when I sign-in it doesnt give permission to unlock (I used yahoo account).
Click to expand...
Click to collapse
did you fix that problem?
can anyone tell me how i can root my n200 stock rom now with android 12 update on it now i cannot get twrp on it or even just boot twrp to flash Magisks with android 11 no issue but now with 12 i can't get it done Thanks for any help
PS shoutout to whomever posted msm tool for global de2117 finally !
The fastboot boot option has been removed from the N200 Android 12 update.
I have extracted the A12 boot.img file with payload-dumper-go from the payload.img and posted it at the N200 Telegram channel while waiting for approval to post at Androidfilehost.
You can then patch it with latest Magisk and fastboot flash it.
Nord N200 Testers
A group for discussing N200 custom software testing. All off topic discussion has been moved to this group: https://t.me/+1qZHIItf9R80MTYx Check pinned messages for important messages and shared/confirmed working files.
t.me
Boot.img for DE2118_11_C.15 T-Mobile/MetroPCS AOSP 12 posted here
scanman0 said:
The fastboot boot option has been removed from the N200 Android 12 update..
Click to expand...
Click to collapse
I'm on Android 12 with the unlocked version and fastboot is still available with either:
adb reboot bootloader
From powered off, press and hold vol down, volume up and power. When the OnePlus logo appears release power but continue holding the other buttons until the fastboot screen appears.
yeswap said:
I'm on Android 12 with the unlocked version and fastboot is still available with either:
adb reboot bootloader
From powered off, press and hold vol down, volume up and power. When the OnePlus logo appears release power but continue holding the other buttons until the fastboot screen appears.
Click to expand...
Click to collapse
I have C.16 stock unlocked boot elsewhere
mingkee said:
I have C.16 stock unlocked boot elsewhere
Click to expand...
Click to collapse
What is C.16? T-Mobile version? With the factory SIM unlocked Android 12 my build number ends in C.15.
When would someone need to flash your boot image and what advantages would it have over the stock boot?
yeswap said:
What is C.16? T-Mobile version? With the factory SIM unlocked Android 12 my build number ends in C.15.
When would someone need to flash your boot image and what advantages would it have over the stock boot?
Click to expand...
Click to collapse
It's stock unlocked C16 boot I got yesterday (neither T-Mobile nor Metro version)
As soon as I received the OTA, I grabbed boot and uploaded it
yeswap said:
I'm on Android 12 with the unlocked version and fastboot is still available with either:
adb reboot bootloader
From powered off, press and hold vol down, volume up and power. When the OnePlus logo appears release power but continue holding the other buttons until the fastboot screen appears.
Click to expand...
Click to collapse
scanman0 means you can no longer run "fastboot boot" from the computer to send a boot image without flashing, you have to flash with "fastboot flash boot" to test a new boot image on your phone
towardsdawn said:
scanman0 means you can no longer run "fastboot boot" from the computer to send a boot image without flashing, you have to flash with "fastboot flash boot" to test a new boot image on your phone
Click to expand...
Click to collapse
Thanks
towardsdawn said:
scanman0 means you can no longer run "fastboot boot" from the computer to send a boot image without flashing, you have to flash with "fastboot flash boot" to test a new boot image on your phone
Click to expand...
Click to collapse
Does that mean I can flash without unlocking the bootloader?
NeonWhitey said:
Does that mean I can flash without unlocking the bootloader?
Click to expand...
Click to collapse
No, unlocking bootloader gives you access to boot sector and allows you to flash boot images. Unlocking bootloader on Android 11 on this device also let you run "fastboot boot" which let you run boot images without flashing but with upgrade to Android 12 that is no longer the case.
towardsdawn said:
No, unlocking bootloader gives you access to boot sector and allows you to flash boot images. Unlocking bootloader on Android 11 on this device also let you run "fastboot boot" which let you run boot images without flashing but with upgrade to Android 12 that is no longer the case.
Click to expand...
Click to collapse
How would i go about doing it on android 12 because the firmware version I'm on has a major bug.
NeonWhitey said:
How would i go about doing it on android 12 because the firmware version I'm on has a major bug.
Click to expand...
Click to collapse
Follow this guide, if you have T-Mobile version and need a SIM unlock, you only need to run the one line ADB command to remove qti.uim you don't need the full debloat script.
You don't need to unlock bootloader if you just want to factory reset the device. If you have T-mobile use MSM tool, otherwise you can try your luck with this guide