Related
Hello,
Recently I flashed a CWM file on my android 'Lava Iris X1 Grand'. Now my phone is stuck in a bootloop. For some reason i cant enter recovery mode even before my phone was stuck in a bootloop. I am not sure whether my phone has USB debugging enabled or not. I have even rooted my android with KingRoot. I have downloaded your Minimal Adb and Fastboot but it cant find my device.
Overall problem:
1) Phone Stuck in Bootloop
2)USB debugging enabled ? Not sure
3) Can't enter recovery mode
4) ADB wont find my device
Note : When I used Minimal Adb and Fastboot, when i type Fastboot devices some numbers appear but when I used the command 'adb devices' my device is not shown. I have a backup at my phone through the Flashify app but since recovery mode cant show I cant recover it.
Please help me out here. I don't know what else to do.
Thank You in advance
Fixed
Sorry posted in wrong section
My phone is fixed now using SP Flash Tool
I'm running into issues with my Compact X. Current situation:
- Omni 8.1 rom installed, but doesn't boot. Stuck on Sony logo.
- TRWP 3.3
- Rooted
- When in fastboot mode (vol up + connect usb cable) the device manager shows: Android Device > Sony Fastboot Interface.
- Windows 10 running in "Test mode"
- adb & fastboot v1.4.3
ADB does not recognize my device when the device is in fastboot mode. When it's in recovery mode the command 'adb devices' shows me the device listed. I can then reboot in fastboot mode, but then the device isn't listed anymore. I'm not sure what happened because a couple of hours ago I installed TWRP using fastboot.
I'm trying to get this thing up and running again, but not being able to flash anything via fastboot complicates things. Any idea's what could be the culprit?
Download official Android drivers by Google and force Install them (search: Force Install Windows drivers" anywhere preferably YouTube
Some random said:
Download official Android drivers by Google and force Install them (search: Force Install Windows drivers" anywhere preferably YouTube
Click to expand...
Click to collapse
Thank you for your reply. As far as I know the official drivers were already installed. Because at first my device did show up listed when using the command 'adb devices' and I successfully flashed TWRP recovery. But to be sure I repeated the process:
- Connected my phone in fastboot mode (vol up + connect usb cable). The blue led lights up.
- Go to the device manager, right click on 'Android ADB interface' device and manually install the driver via 'Have disk'.
- The driver installs with no errors.
But still my phone is not listed and I cannot flash anything.
When the phone is in recovery mode it is listed using the 'adb devices' command. But when I'm trying to flash something I get the message <waiting for device> .
Ok, I restored my computer to a point before I started messing with my phone. After installing the official drivers my phone is still not listed (adb devices), but this time flashing did work. I managed to flash the AOSP 8.1 image. My phone is up and running again!
I'm trying to root a pixel (sailfish). I'm able to find the device in adb, but when I go into bootloader, the device isn't there. I'm mostly trying things on my Mac, which I used to successfully root a Nexus 7, but I also had the same issue on a Raspberry Pi. What's more is that I have a Verizon Pixel, which is detected in bootloader (but I can't root it since it's Verizon), and the problematic Pixel in bootloader isn't even registering as a connected USB device when I use the command, "system_profiler SPUSBDataType". Anyone have any advice?
@macduffk
Try
Code:
adb reboot bootloader
fastboot devices
jwoegerbauer said:
@macduffk
Try
Code:
adb reboot bootloader
fastboot devices
Click to expand...
Click to collapse
I’ve tried that. It doesn’t show anything.
I have spent months trying to figure out how to get TWRP flashed on my Pixel Phones (I have 2 of them). I have searched & read many links on this forum and can't find any firm details/directions on how to get TWRP on a pixel. From https://android.gadgethacks.com/how-to/install-twrp-custom-recovery-your-pixel-pixel-xl-0175163/ it appears I should of installed TWRP on the factory image first, but I went to Lineage a couple years ago on Android 9 & this was not an option back then.
Both phones have the two latest version of Lineage OS, Both Devices are UNLOCKED, Both have Developer Options Enabled, and on my Windows PC I have the latest version of SDK tools & drivers installed.
Plugging into the PC is done with a a tested/good USB cable plugged into a USB 2 Port. Here is what I am seeing with LinageOS running:
adb devices shows List of Devices Attached
FA77LO302202 device
After executing - adb reboot bootloader
adb devices -> shows an empty list, hence doing a -> fastboot devices shows no devices.
Going to Recovery Mode in Bootloader list of devices shows:
FA76F0303478 unauthorized
In Recovery Mode -> Advanced -> Enable ADB list of devices shows:
FA76F0303478 recovery
I can Apply Update in Recovery Mode via Sideload, but that does not help me get TWRP flashed.
With no devices showing in the main bootloader via adb I can't get the phone into autoboot mode. Per the link at android.gadgethacks.com in order to put the Factory Image back on the phone, https://developers.google.com/android/images, I need to get the phone into autoboot mode.
Anyone have any ideas????
Come-on guys & gals. I'm sure someone can help me at XDA get my devices to fastboot.
So, I recently tried to root my Redmi 5 phone and install Lineage OS into it. This is my first time doing it, so I believe I may not have understood the words I had been reading well. Due to this, I'll try to be as descriptive as possible with the actions I had taken that led to my device being stuck.
I had followed this guide, for the most part: https://www.getdroidtips.com/lineage-os-17-xiaomi-redmi-5/
As per the guide, I performed the following actions:
Enabled the developer options
Registered my device to my Mi account
Enabled USB debugging, OEM unlocking
Rebooted in fastboot mode using the ADB tools through CMD (adb reboot bootloader)
While in fastboot mode, I used the Mi Unlock tool to unlock my device.
As per my understanding, these steps would unlock the bootloader. I rebooted my device, set it up (the phone behaves as if freshly booted) and checked the settings menu after enabling developer options again. It shows the bootloader is already unlocked and that Mi Account status is also unlocked. I enabled the USB debugging options again and carried on with the guide.
I then downloaded the rosy TWRP file (version 3.5, I think).
I even downloaded GApps and Lineage 18.1 OS
I tried to copy the above files into my Redmi 5 internal storage
The Lineage and GApps file failed to copy, but I was able to copy the TWRP file
One thing to note here, I am not sure if my USB cable is faulty or if my phone's micro USB port is faulty or if my laptop's USB ports are faulty. When the phone is connected to my PC, it is extremely lousy. If I shake the cable even a bit, it disconnects and reconnects. When I try to use the file explorer to copy the files from my laptop to the android phone, it usually fails for large files or large quantities of small files. I believe this was the reason behind the failure. Nonetheless, I decided to do the TWRP part first.
The guide said to reboot in recovery mode and that would take me to TWRP recovery mode. Well, it did not! It took me to a menu that had the following options:
Reboot
Reboot to System
Back to Main Menu
Wipe Data
Wipe All Data
Back to Main Menu
Connect to MIAssistant
I assumed I had entered recovery mode incorrectly, so I followed the link in the guide on how to enter recovery mode. It suggested using the ADB tools.
I used the command: adb reboot recovery
It did the same thing that I had done. So, I assumed that that is the recovery mode, but I am unable to enter TWRP recovery mode. There was another link that would show me how to do this.
I followed that link and downloaded the files that was mentioned. However, the guide tells little to nothing on what to do with these files. The only file that was used was the rosy twrp file.
I enabled the USB debugging mode on my phone.
Opened CMD from the folder with ADB
Entered the command: adb reboot bootloader
Phone enters fastboot mode
Entered the command: fastboot devices
I can see that a device is connected
Entered the command: fastboot flash recovery rosy-3-5.img (I renamed it for convenience, I believe that was allowed because every website had different name for their file)
I then rebooted into recovery mode by first rebooting it normally: fastboot reboot
Then entering the command: adb reboot recovery
It still showed the same old recovery menu. Nothing had changed. I looked around the internet and found that I could boot with the TWRP image by entering the command: fastboot boot rosy-3-5.img
This opened the screen that I was expecting, but it did not open the chinese menu at all. It directly went to the screen that had options such as Install, Wipe, etc.,
I rebooted normally and then tried to transfer the GApps file and Lineage file into my phone. As usual, it was failing. I tried to use the adb push command and it still failed but with an error saying "permissions denied"
At this point, I looked up how to get root permissions and I learnt that I had to root my device. I looked up how to root with Magisk and SuperSU. The guides all required me to boot in TWRP recovery and then install the files from my phone. Unable to transfer the files to my phone, I uploaded the files to my google drive, and manually downloaded into my phone. I boot up rosy (TWRP recovery, or so I think) using ADB tools. Unfortunately, it does not recognize any of the files in my internal storage. Everything is empty.
Defeated by this, I decided to let it go. I had a factory reset Redmi 5 at the time. I then watched a video that showed how to root with Magisk, but wasn't specific to Redmi 5, it was a generic video for android devices.
I installed the magisk manager apk into my android phone.
Then I copied the boot.img file from the Lineage folder into my android device. Despite the OS being 600 MB large, the boot.img file was only 11 MB.
Anyway, I patched the boot.img file using magisk manager.
It created a file called magisk-patched_1pTOD.img (I'm a bit unsure of the name, but it was similar to that).
The video said that I should copy this file into my laptop and then reboot my phone into fastboot.
Once in fastboot, I had to enter the command: fastboot flash boot magisk-patched_1pTOD.img
I believed that this would root my device and grant me root access. I don't know what my actions were actually supposed to do, but my device is unusable for all intents and purposes. I rebooted the device and it shows the Mi logo for a brief moment and there's no light. An empty dark screen, it's not even a black screen. It's like the display fails to work. I can switch into recovery mode and into fastboot mode but normal reboot did the same.
Thinking that I bricked my phone, I tried to unbrick it.
I downloaded the fastboot rom for Redmi 5 rosy and then installed the Mi Flash tool along with the drivers for it.
I then selected the correct ROM folder (it kept showing up as can't find flash script until I was in the right folder for it)
Rebooted my phone into fastboot mode
Hit refresh on the Mi Flash tool
It showed my device
I chose Clean All option
I hit flash
It goes up till 97%-ish and then fails with an error saying "flash system error".
However, I noticed that now, I can see that the Mi Logo doesn't disappear now. I can still go into recovery mode and fastboot mode, but normal reboot takes me to the permanent Mi Logo Screen. I cannot even shut it down. It auto reboots to the Mi Logo Screen if I do so.
I connected my device to my laptop and then opened the ADB tools.
I entered the following command to see if it's recognized by adb:
adb devices
It did not. I then switched to fastboot mode manually by pressing the Vol Down and Power buttons.
Then entered the following to see if it is recognized in fastboot mode:
fastboot devices
It showed my device there. So I used the following command to reboot and see if it is recognized in fastboot again:
fastboot reboot
While it shows the Mi Logo screen, I typed the command:
fastboot devices
It still shows my device.
I concluded that my device is in an infinite fastboot loop. I cannot boot it up normally. I cannot flash the Redmi 5 ROM into it either. I cannot use my phone.
If anybody has actually gone through this entire mess that I made, and has figured out what went wrong or at least how to fix it, please help me.
Message me on telegram @benzoylperoxide
Hope I could help you with this situation.
If you got data, download fastboot rom based on nought and fastboot rom 9.5.30
Download latest miflash tool from miglobe website.
Install proper drivers from miunlock tool zip file.
And Hope for the best.
Ping me tommorow at anytime.
Good night Bro
incertam7 said:
So, I recently tried to root my Redmi 5 phone and install Lineage OS into it. This is my first time doing it, so I believe I may not have understood the words I had been reading well. Due to this, I'll try to be as descriptive as possible with the actions I had taken that led to my device being stuck.
I had followed this guide, for the most part: https://www.getdroidtips.com/lineage-os-17-xiaomi-redmi-5/
As per the guide, I performed the following actions:
Enabled the developer options
Registered my device to my Mi account
Enabled USB debugging, OEM unlocking
Rebooted in fastboot mode using the ADB tools through CMD (adb reboot bootloader)
While in fastboot mode, I used the Mi Unlock tool to unlock my device.
As per my understanding, these steps would unlock the bootloader. I rebooted my device, set it up (the phone behaves as if freshly booted) and checked the settings menu after enabling developer options again. It shows the bootloader is already unlocked and that Mi Account status is also unlocked. I enabled the USB debugging options again and carried on with the guide.
I then downloaded the rosy TWRP file (version 3.5, I think).
I even downloaded GApps and Lineage 18.1 OS
I tried to copy the above files into my Redmi 5 internal storage
The Lineage and GApps file failed to copy, but I was able to copy the TWRP file
One thing to note here, I am not sure if my USB cable is faulty or if my phone's micro USB port is faulty or if my laptop's USB ports are faulty. When the phone is connected to my PC, it is extremely lousy. If I shake the cable even a bit, it disconnects and reconnects. When I try to use the file explorer to copy the files from my laptop to the android phone, it usually fails for large files or large quantities of small files. I believe this was the reason behind the failure. Nonetheless, I decided to do the TWRP part first.
The guide said to reboot in recovery mode and that would take me to TWRP recovery mode. Well, it did not! It took me to a menu that had the following options:
Reboot
Reboot to System
Back to Main Menu
Wipe Data
Wipe All Data
Back to Main Menu
Connect to MIAssistant
I assumed I had entered recovery mode incorrectly, so I followed the link in the guide on how to enter recovery mode. It suggested using the ADB tools.
I used the command: adb reboot recovery
It did the same thing that I had done. So, I assumed that that is the recovery mode, but I am unable to enter TWRP recovery mode. There was another link that would show me how to do this.
I followed that link and downloaded the files that was mentioned. However, the guide tells little to nothing on what to do with these files. The only file that was used was the rosy twrp file.
I enabled the USB debugging mode on my phone.
Opened CMD from the folder with ADB
Entered the command: adb reboot bootloader
Phone enters fastboot mode
Entered the command: fastboot devices
I can see that a device is connected
Entered the command: fastboot flash recovery rosy-3-5.img (I renamed it for convenience, I believe that was allowed because every website had different name for their file)
I then rebooted into recovery mode by first rebooting it normally: fastboot reboot
Then entering the command: adb reboot recovery
It still showed the same old recovery menu. Nothing had changed. I looked around the internet and found that I could boot with the TWRP image by entering the command: fastboot boot rosy-3-5.img
This opened the screen that I was expecting, but it did not open the chinese menu at all. It directly went to the screen that had options such as Install, Wipe, etc.,
I rebooted normally and then tried to transfer the GApps file and Lineage file into my phone. As usual, it was failing. I tried to use the adb push command and it still failed but with an error saying "permissions denied"
At this point, I looked up how to get root permissions and I learnt that I had to root my device. I looked up how to root with Magisk and SuperSU. The guides all required me to boot in TWRP recovery and then install the files from my phone. Unable to transfer the files to my phone, I uploaded the files to my google drive, and manually downloaded into my phone. I boot up rosy (TWRP recovery, or so I think) using ADB tools. Unfortunately, it does not recognize any of the files in my internal storage. Everything is empty.
Defeated by this, I decided to let it go. I had a factory reset Redmi 5 at the time. I then watched a video that showed how to root with Magisk, but wasn't specific to Redmi 5, it was a generic video for android devices.
I installed the magisk manager apk into my android phone.
Then I copied the boot.img file from the Lineage folder into my android device. Despite the OS being 600 MB large, the boot.img file was only 11 MB.
Anyway, I patched the boot.img file using magisk manager.
It created a file called magisk-patched_1pTOD.img (I'm a bit unsure of the name, but it was similar to that).
The video said that I should copy this file into my laptop and then reboot my phone into fastboot.
Once in fastboot, I had to enter the command: fastboot flash boot magisk-patched_1pTOD.img
I believed that this would root my device and grant me root access. I don't know what my actions were actually supposed to do, but my device is unusable for all intents and purposes. I rebooted the device and it shows the Mi logo for a brief moment and there's no light. An empty dark screen, it's not even a black screen. It's like the display fails to work. I can switch into recovery mode and into fastboot mode but normal reboot did the same.
Thinking that I bricked my phone, I tried to unbrick it.
I downloaded the fastboot rom for Redmi 5 rosy and then installed the Mi Flash tool along with the drivers for it.
I then selected the correct ROM folder (it kept showing up as can't find flash script until I was in the right folder for it)
Rebooted my phone into fastboot mode
Hit refresh on the Mi Flash tool
It showed my device
I chose Clean All option
I hit flash
It goes up till 97%-ish and then fails with an error saying "flash system error".
However, I noticed that now, I can see that the Mi Logo doesn't disappear now. I can still go into recovery mode and fastboot mode, but normal reboot takes me to the permanent Mi Logo Screen. I cannot even shut it down. It auto reboots to the Mi Logo Screen if I do so.
I connected my device to my laptop and then opened the ADB tools.
I entered the following command to see if it's recognized by adb:
adb devices
It did not. I then switched to fastboot mode manually by pressing the Vol Down and Power buttons.
Then entered the following to see if it is recognized in fastboot mode:
fastboot devices
It showed my device there. So I used the following command to reboot and see if it is recognized in fastboot again:
fastboot reboot
While it shows the Mi Logo screen, I typed the command:
fastboot devices
It still shows my device.
I concluded that my device is in an infinite fastboot loop. I cannot boot it up normally. I cannot flash the Redmi 5 ROM into it either. I cannot use my phone.
If anybody has actually gone through this entire mess that I made, and has figured out what went wrong or at least how to fix it, please help me.
Click to expand...
Click to collapse
Flash system error in MiFlash? Probably the stock rom you downloaded and extracted is corrupted.
Please try flashing MIUI 9 for your Redmi 5.
Yeah, users have had issues with twrp being replaced by stock rom.
For TWRP,
fastboot flash revovery (recovery name.img)
Fastboot boot (recovery name .img)
After that flash your custom rom after wiping system,boot, vendor, data and cache, Internal format might be needed if it's encrypted.
Then, after custom rom is flashed, flash gapps and then twrp zip in TWRP, yeah you saw it right, flash twrp zip in TWRP. This way, twrp won't get replaced.
You can give directly flashing TWRP and flashing custom rom the way I told, Flashing Miui isn't important if your goal is to flash custom rom.
Hi! I would like to mod my AC2003 upgraded to oxygenos 12.1 (android 12) version AC2003_11_F.13
Could you please tell me the steps to proceed? I can't find a guide that answers all my questions ... Do I need to unlock the bootloader first? Then the recovery and the rom? I would be oriented towards the pixel experience, can it be a good choice? Does it support 2 sims? How to do with the root for the bank's applications? Many questions, and nowhere to start ... Thanks in advance
Copy all important phone data, it will be wiped!
- Download adb platform tools here
- Download adb drivers here
- Enable developer settings -> Enable OEM unlock.
- Reboot into Fastbot mode: Turn off the phone, hold down vol+ and vol-, then power on the phone.
- Connect the phone to the computer, run "fastboot devices". If not recognized, ensure driver is installed in the device manager, install from downloaded adb drivers.
- Run "fastboot oem unlock", accept in the phone prompt, the phone will be wiped!
- Boot again in fastboot, flash the recovery: "fastboot flash recovery recovery_file".
- Unplug the USB, I found the recovery to not work properly if the usb was already plugged in before booting.
- Boot into recovery mode: Hold Vol+ and turn on the phone.
- Go to Update... Install from ADB, connect the USB.
- In the computer, run "adb sideload rom_file"
- I'd recommend issuing a factory reset after this, just in case.
- NEVER run "fastboot oem lock" with modded system, it'll brick your phone! (Can be fixed, but just don't do it)
- Enjoy
Ex. for Pixel rom:
- Recovery file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.img
- ROM file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.zip
I wasn't happy with custom roms. Too many bugs. So I also post how to return to factory:
- Download fastboot ROM from here, unzip file.
- Boot the phone into fastboot mode, connect the USB, run "flash-all.bat", it'll take a while, it'll reboot afterwards
- You're now with stock system. You can upgrade to OOS11/12 using the zips from here, also check F.13, copying them to the phone, going to the updater and selecting "Local update".
- Better do OOS10->OOS11->OOS12, just in case! I'd stay with OOS 11.1.11.11, OOS12 is a battery drainer!
- Ensure to make a factory reset when done with updating.
- Now you're stock, you can also relock the bootloader by booting into fastboot and running "fastboot oem lock".
Be aware that you will miss some camera features with any custom rom... Full camera features are only available with the stock rom..
Thats why I moved back to stock rom and debloated all unuseable stuff...
But a custom rom offers many other opportunities that the stock rom doesn't have...
dabyd64 said:
Copy all important phone data, it will be wiped!
- Download adb platform tools here
- Download adb drivers here
- Enable developer settings -> Enable OEM unlock.
- Reboot into Fastbot mode: Turn off the phone, hold down vol+ and vol-, then power on the phone.
- Connect the phone to the computer, run "fastboot devices". If not recognized, ensure driver is installed in the device manager, install from downloaded adb drivers.
- Run "fastboot oem unlock", accept in the phone prompt, the phone will be wiped!
- Boot again in fastboot, flash the recovery: "fastboot flash recovery recovery_file".
- Unplug the USB, I found the recovery to not work properly if the usb was already plugged in before booting.
- Boot into recovery mode: Hold Vol+ and turn on the phone.
- Go to Update... Install from ADB, connect the USB.
- In the computer, run "adb sideload rom_file"
- I'd recommend issuing a factory reset after this, just in case.
- NEVER run "fastboot oem lock" with modded system, it'll brick your phone! (Can be fixed, but just don't do it)
- Enjoy
Ex. for Pixel rom:
- Recovery file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.img
- ROM file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.zip
I wan't happy with custom roms. Too many bugs. So I also post how to return to factory:
- Download fastboot ROM from here, unzip file.
- Boot the phone into fastboot mode, connect the USB, run "flash-all.bat, it'll take a while, it'll reboot afterwards
- You're now with stock system. You can upgrade to OOS11/12 using the zips from here, also check F.13, copying them to the phone, going to the updater and selecting "Local update".
- Better do OOS10->OOS11->OOS12, just in case! I'd stay with OOS 11.1.11.11, OOS12 is a battery drainer!
- Ensure to make a factory reset when done with updating.
- Now you're stock, you can also relock the bootloader by booting into fastboot and running "fastboot oem lock".
Click to expand...
Click to collapse
Wow! You wrote the bible for the beginner ... I don't know how to thank you for your patience, now I have a great starting point
I've a problem, fastboot can't see my device... I've installed the oneplus drivers, but windows continues to use Microsoft's drivers. I tried to update the drivers from the device manager indicating as drivers those installed in the Oneplus folder, but windows keeps telling me not to find drivers compatible with an x64 system in that folder. I also tried to disable the digital signature check, without success. This is on both windows 11 and windows 10 PCs. I've also enabled debug usb...
There's no problem using Windows drivers.
Isn't the phone recognized as fastboot device?
Attach device manager screenshot.
dabyd64 said:
There's no problem using Windows drivers.
Isn't the phone recognized as fastboot device?
Attach device manager screenshot.
Click to expand...
Click to collapse
It seems you're not in fastboot Mode?
Do you see this screen?
dabyd64 said:
It seems you're not in fastboot Mode?
Do you see this screen?
Click to expand...
Click to collapse
The cable was the problem...Now i've tried with it's original cable and yes, i can see it! Thank you so much...
dabyd64 said:
Copy all important phone data, it will be wiped!
- Download adb platform tools here
- Download adb drivers here
- Enable developer settings -> Enable OEM unlock.
- Reboot into Fastbot mode: Turn off the phone, hold down vol+ and vol-, then power on the phone.
- Connect the phone to the computer, run "fastboot devices". If not recognized, ensure driver is installed in the device manager, install from downloaded adb drivers.
- Run "fastboot oem unlock", accept in the phone prompt, the phone will be wiped!
- Boot again in fastboot, flash the recovery: "fastboot flash recovery recovery_file".
- Unplug the USB, I found the recovery to not work properly if the usb was already plugged in before booting.
- Boot into recovery mode: Hold Vol+ and turn on the phone.
- Go to Update... Install from ADB, connect the USB.
- In the computer, run "adb sideload rom_file"
- I'd recommend issuing a factory reset after this, just in case.
- NEVER run "fastboot oem lock" with modded system, it'll brick your phone! (Can be fixed, but just don't do it)
- Enjoy
Ex. for Pixel rom:
- Recovery file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.img
- ROM file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.zip
I wasn't happy with custom roms. Too many bugs. So I also post how to return to factory:
- Download fastboot ROM from here, unzip file.
- Boot the phone into fastboot mode, connect the USB, run "flash-all.bat", it'll take a while, it'll reboot afterwards
- You're now with stock system. You can upgrade to OOS11/12 using the zips from here, also check F.13, copying them to the phone, going to the updater and selecting "Local update".
- Better do OOS10->OOS11->OOS12, just in case! I'd stay with OOS 11.1.11.11, OOS12 is a battery drainer!
- Ensure to make a factory reset when done with updating.
- Now you're stock, you can also relock the bootloader by booting into fastboot and running "fastboot oem lock".
Click to expand...
Click to collapse
After flash recovery, when i go to the recovery mode, i see this mex:
"The current image (boot/recovery) have been destroted and can not boot. Please flash the correct image or contact customer service to fix"
Fortunately i have solved with msm....
It's a known thing that you can flash on any custom ROM only if you're on oxygenOS 10 or 11 version. Respectively, if you are on android 12, then you first need to flash with unbrick tool (msmtool) anroid 10 (EU/Global/India) or android 11 (India).
gorro8 said:
It's a known thing that you can flash on any custom ROM only if you're on oxygenOS 10 or 11 version. Respectively, if you are on android 12, then you first need to flash with unbrick tool (msmtool) anroid 10 (EU/Global/India) or android 11 (India).
Click to expand...
Click to collapse
Hi,
I am on OS12 stock currently.
At which stage of the guide posted above I need to use the unbrick tool ?
Many thanks
Hi bro.
If you want to flash any custom ROM, then you need to go to unbrick tools thread, download drivers and MSM tool firmware and step by step flash it.
After that flash custom rom you need also with it instruction in the thread.