I wanted to try brand new Nougat ROMs. So, I flashed twrp using Mi4i Toolkit and took backup of my MIUI8.
I tried many ROMs and decided to return to my MIUI8 nandroid backup.
But when I tried to restore the nandroid backup, It went successful but after restoring, Phone started rebooting in each 4-5 minutes. Searched and found that many people were facing this issue and they stayed on custom ROMs just because of this issue. So. I thought to create a new thread so this major problem can be easily solved.
How I got it fixed that,
REBOOT ISSUE
Download Full stock MIUI ROM pack here : http://en.miui.com/download-263.html
1. Boot into TWRP
2. Wipe Dalvik/ART, Cache, Data (Internal Storage not required to wipe)
3. Flash ROM zip.
4. If It gets failed, No need to worry.
5. Go to advanced options in TWRP and select "Fix Contexts".
6. Try flashing Again.
7. It is successful now. Boot device and Perform a full reset ( again deleting Internal storage is not needed.)
8. Here you go, No reboots now, You get brand new performance of MIUI ROM flawlessly
Hit thanks if it works for you or ask me in replies.
Fastboot Not Detecting
It has been noticed even after installing Minimal ADB and Fastboot drivers properly and performing all adb commands flawlessly, some computers can't detect devices in fastboot mode. Here's the solution.
1. Download Minimal ADB and Fastboot here : https://forum.xda-developers.com/showthread.php?t=2317790
2. Install and extract in a folder
3. Open command prompt in the folder.
4. connect your device in fastboot mode. (By holding power and vol- key, you can enter in fastboot mode)
5. Type
Code:
fastboot devices
and press enter
6. If it detects , then you've no problem.
7. If it doesn't detect go to device manager on your PC ( Press Windows+X, M on win10)
8.It might be detecting your device with some name, look for it.
9. Once you find, choose to uninstall its driver
10. Now click on action in menu bar and "Scan for hardware changes"
11. It now detects your device. If It doesn't, Uninstall and Install ADB drivers again and repeat above steps.
12.
Code:
fastboot devices
now should be showing your device.
MI4i Stock Recovery
Found stock recovery on MIUI forum for MI4i but there's a problem with that. It shows option to wipe External SD (which isn't supported for MI4i), So I doubt this could be pulled from the same MI4i.
So, I backed up Genuine MI4i Stock Recovery from my MI4i with flashify.
Steps:
1. Boot into fastboot mode.
2. Connect with PC and open command prompt in the same folder of fastboot and ADB
3. Put this file https://docs.google.com/uc?id=0B98eukQ9ePc-NnljcmxjWWJvUHc in same folder
4. Type
Code:
fastboot flash recovery mi4istockrecovery
press enter
5. Cheers! You're now on stock recovery.
6. Boot into recovery mode to verify.
Hit thanks if helped
madhurajkumar said:
7. If you are unable to flash stock recovery, bootloader maybe locked, unlock the bootloader and then try again.
Click to expand...
Click to collapse
The bootloader never locks for the Mi4i ? why'd you add a step for this ?
sharan.nyn said:
The bootloader never locks for the Mi4i why'd you add a step for this ?
Click to expand...
Click to collapse
Read it somewhere, so thought to add. Edited
madhurajkumar said:
I wanted to try brand new Nougat ROMs. So, I flashed twrp using Mi4i Toolkit and took backup of my MIUI8.
I tried many ROMs and decided to return to my MIUI8 nandroid backup.
But when I tried to restore the nandroid backup, It went successful but after restoring, Phone started rebooting in each 4-5 minutes. Searched and found that many people were facing this issue and they stayed on custom ROMs just because of this issue. So. I thought to create a new thread so this major problem can be easily solved.
How I got it fixed that,
REBOOT ISSUE
Download Full stock MIUI ROM pack here : http://en.miui.com/download-263.html
1. Boot into TWRP
2. Wipe Dalvik/ART, Cache, Data (Internal Storage not required to wipe)
3. Flash ROM zip.
4. If It gets failed, No need to worry.
5. Go to advanced options in TWRP and select "Fix Contexts".
6. Try flashing Again.
7. It is successful now. Boot device and Perform a full reset ( again deleting Internal storage is not needed.)
8. Here you go, No reboots now, You get brand new performance of MIUI ROM flawlessly
Hit thanks if it works for you or ask me in replies.
Fastboot Not Detecting
It has been noticed even after installing Minimal ADB and Fastboot drivers properly and performing all adb commands flawlessly, some computers can't detect devices in fastboot mode. Here's the solution.
1. Download Minimal ADB and Fastboot here : https://forum.xda-developers.com/showthread.php?t=2317790
2. Install and extract in a folder
3. Open command prompt in the folder.
4. connect your device in fastboot mode. (By holding power and vol- key, you can enter in fastboot mode)
5. Type
and press enter
6. If it detects , then you've no problem.
7. If it doesn't detect go to device manager on your PC ( Press Windows+X, M on win10)
8.It might be detecting your device with some name, look for it.
9. Once you find, choose to uninstall its driver
10. Now click on action in menu bar and "Scan for hardware changes"
11. It now detects your device. If It doesn't, Uninstall and Install ADB drivers again and repeat above steps.
12.now should be showing your device.
MI4i Stock Recovery
Found stock recovery on MIUI forum for MI4i but there's a problem with that. It shows option to wipe External SD (which isn't supported for MI4i), So I doubt this could be pulled from the same MI4i.
So, I backed up Genuine MI4i Stock Recovery from my MI4i with flashify.
Steps:
1. Boot into fastboot mode.
2. Connect with PC and open command prompt in the same folder of fastboot and ADB
3. Put this file https://docs.google.com/uc?id=0B98eukQ9ePc-NnljcmxjWWJvUHc in same folder
4. Type
press enter
5. Cheers! You're now on stock recovery.
6. Boot into recovery mode to verify.
Hit thanks if helped
Click to expand...
Click to collapse
can you help us about hardbricked Mi4i? what should we do a proper guide can make a huge support to me
There is no led, only access to fastboot mode but when i tried to flash stock rom via miflash the whole completed in just 2 sec and phone doesn't boot up completely and stuck again
aa_vi said:
can you help us about hardbricked Mi4i? what should we do a proper guide can make a huge support to me
There is no led, only access to fastboot mode but when i tried to flash stock rom via miflash the whole completed in just 2 sec and phone doesn't boot up completely and stuck again
Click to expand...
Click to collapse
If you can boot into fastboot mode,
Flash twrp from your pc using Minimal adb and fastboot.
If you face issues and need help about this, Ask me
i flashed a fastboot mode rom through cmd everything goes perfect there is no issue in the whole process but after reboot it does not reboot only show mi logo and turn off then the display of device fluctuate again and again i never experience this issue
suggest something
aa_vi said:
i flashed a fastboot mode rom through cmd everything goes perfect there is no issue in the whole process but after reboot it does not reboot only show mi logo and turn off then the display of device fluctuate again and again i never experience this issue
suggest something
Click to expand...
Click to collapse
Which ROM?
This issue is called Bootloop.
1.Flash twrp through cmd
2. Wipe everything ( except the internal storage, as it's not needed )
3. Try repeating the same.
If you again face the issue, try downloading flashable zip of the same ROM and try flashing via twrp.
madhurajkumar said:
Which ROM?
This issue is called Bootloop.
1.Flash twrp through cmd
2. Wipe everything ( except the internal storage, as it's not needed )
3. Try repeating the same.
If you again face the issue, try downloading flashable zip of the same ROM and try flashing via twrp.
Click to expand...
Click to collapse
Thanks! it worked but there is a little bit problem the internal. memory of device is reducing to 2.57 gb instead of 12.xx gb what the hell is this the partion of memory is reduced to this much
aa_vi said:
Thanks! it worked but there is a little bit problem the internal. memory of device is reducing to 2.57 gb instead of 12.xx gb what the hell is this the partion of memory is reduced to this much
Click to expand...
Click to collapse
Partition Issues there.
Boot into twrp
Go to wipe
Select System
Tap on "Repair or Change File System"
Confirm the action
Repeat the same for data and cache partitions ONE BY ONE ( you can select one partition once)
Now after formatting all the partitions,
Wipe all partitions
Flash the ROM zip through TWRP
Reboot
madhurajkumar said:
Partition Issues there.
Boot into twrp
Go to wipe
Select System
Tap on "Repair or Change File System"
Confirm the action
Repeat the same for data and cache partitions ONE BY ONE ( you can select one partition once)
Now after formatting all the partitions,
Wipe all partitions
Flash the ROM zip through TWRP
Reboot
Click to expand...
Click to collapse
when we select system it show a warning in that is says some roms and kernels didn't support this and at bottom some options are shown
EXT2
EXT3
EXT4
FAT
exFAT
F2FS
which option supports the process?
aa_vi said:
when we select system it show a warning in that is says some roms and kernels didn't support this and at bottom some options are shown
EXT2
EXT3
EXT4
FAT
exFAT
F2FS
which option supports the process?
Click to expand...
Click to collapse
Try Ext4
Help
help my xiaomi mi4i cannot solved it ,
target reported max download size of 268435456 bytes
sending 'recovery' (32768 KB)...
OKAY [ 1.030s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 1.404s
dstyo said:
help my xiaomi mi4i cannot solved it ,
target reported max download size of 268435456 bytes
sending 'recovery' (32768 KB)...
OKAY [ 1.030s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 1.404s
Click to expand...
Click to collapse
What is your miui version currently? And which twrp you use that has 32mb? 3.1.1.1 only 24mb if im not mistaken
yumm91 said:
What is your miui version currently? And which twrp you use that has 32mb? 3.1.1.1 only 24mb if im not mistaken
Click to expand...
Click to collapse
i'm not used twrp , but i install mi4istockrecovery still failed. my miui version is 7 , now my phone stuck in mi logo if i restarted my phone then always started fastboot mode , i still confused
dstyo said:
i'm not used twrp , but i install mi4istockrecovery still failed. my miui version is 7 , now my phone stuck in mi logo if i restarted my phone then always started fastboot mode , i still confused
Click to expand...
Click to collapse
I would suggest you to first install TWRP, then flash the stock ROM from TWRP and then flash mi4i stock recovery in fastboot mode. ( As I faced similar issue and got it solved this way. )
dstyo said:
i'm not used twrp , but i install mi4istockrecovery still failed. my miui version is 7 , now my phone stuck in mi logo if i restarted my phone then always started fastboot mode , i still confused
Click to expand...
Click to collapse
The easiest way to do this is by dowloading fastboot ROM for your miui version. Once you extract the files, there will be a recovery.img inside.
Then u can flash the recovery via fastboot flash recovery recovery.img to return the recovery to stock.
Done.
Help needed
I hae this same problem my MI4i is stuck in fastboot mode it's not even going off. Device's bootloader is locked so can't flash twrp
aamir93 said:
I hae this same problem my MI4i is stuck in fastboot mode it's not even going off. Device's bootloader is locked so can't flash twrp
Click to expand...
Click to collapse
Try to boot into twrp by using this command
rename downloaded twrp img file to twrp.img
connect in fastboot mode and in Minimal ADB ad Fastboot cmd, type
Code:
fastboot boot twrp.img
wich rom ?
aa_vi said:
Thanks! it worked but there is a little bit problem the internal. memory of device is reducing to 2.57 gb instead of 12.xx gb what the hell is this the partion of memory is reduced to this much
Click to expand...
Click to collapse
I try rom global stable and china dev but just stay bootlop in miui boot
Mi4i twrp flash without data loss
madhurajkumar said:
If you can boot into fastboot mode,
Flash twrp from your pc using Minimal adb and fastboot.
If you face issues and need help about this, Ask me
Click to expand...
Click to collapse
Mi4i device stuck at mi logo (Came to know this is called Bootloop, Note that not flashed or installed anything on device automatically this issue happened) .As non technical person i need help from you guys to get my device alive. I need to save all my data in the mobile so Googled some topics and came to know that for this i have to flash TWRP in fastboot mode where we can able to save the data . Can anybody help me on this?
Really appreciate your support ....!!!!
So I was trying to install a custom ROM (first time ) did unlock my bootloader and when wiped using twrp and then rebooted to twrp for flashing the ROM it said that system has been destroyed when I tried to reboot to recovery then also it was of no use.I tried to flash fastboot roms via miflash tool. The new versions couldnt find scripts o don't know why so I tried the old ones but the flash got completed in 1 second so it was useless.further more I think that I have anti rollback v2 in my phone and that's why I'm not able to go anywhere..
Is there any fix please help
Try to manual flash using fastboot
Fastboot flash system system.img
Fastboot flash recovery recovery.img
Then flash EU rom
LovingDracula04 said:
So I was trying to install a custom ROM (first time ) did unlock my bootloader and when wiped using twrp and then rebooted to twrp for flashing the ROM it said that system has been destroyed when I tried to reboot to recovery then also it was of no use.I tried to flash fastboot roms via miflash tool. The new versions couldnt find scripts o don't know why so I tried the old ones but the flash got completed in 1 second so it was useless.further more I think that I have anti rollback v2 in my phone and that's why I'm not able to go anywhere..
Is there any fix please help
Click to expand...
Click to collapse
The same thing happened to me when I tried to install and use TWRP.
To fix this, I used the MiFlash tool and flashed the fastboot ROM which you can download from here.
LovingDracula04 said:
So I was trying to install a custom ROM (first time ) did unlock my bootloader and when wiped using twrp and then rebooted to twrp for flashing the ROM it said that system has been destroyed when I tried to reboot to recovery then also it was of no use.I tried to flash fastboot roms via miflash tool. The new versions couldnt find scripts o don't know why so I tried the old ones but the flash got completed in 1 second so it was useless.further more I think that I have anti rollback v2 in my phone and that's why I'm not able to go anywhere..
Is there any fix please help
Click to expand...
Click to collapse
I had the same issue, but my phone went to fastboot from there I flashed it, the process was simple :
1. Download the fastboot rom and extract it (I guess two times, the first extraction extracts a file, open that with some extraction tool and uzip again, there you will see the fw with certain folders and images etc ).
2. Download the adb/fastboot zip file I"ll attach that here, extract it to the same folder where your fw files are. (fw = firmware).
3. You will find 3 bat files, flash all, flash all and lock, flash except storage, choose flash all (execute it).
4. Once done, reboot to recovery (stock), do a data wipe again.
This worked for me, hope it does for you too.
try unlock bootloader via internet
format data once via twrp
Hi guys
I just successfully flashed my K8+(2018) to oreo from nougat and kept my working fastboot. Im gonna tell you how but first........
I Duhjoker am in no way responsible for anything that may befall your device by trying any technique or by following this guide. Do this at your own risk.
What you will need::::::::
Lg K8+(2018) LM-X210ULM
K8+Oreo-rooted-boot.img =====second post
K8+Oreo-twrp-recovery.img====second post
LGUP dual mode
Lg firmware extractor ??? This is for those portting a recovery and boot.img for a different cv1 device
Oreo firmware for your K8+(2018) X210ULM
and/or
Nougat firmware for your K8+(2018) X210ULM
Magisk manager
Patience
Ok so go to settings and tap general then about phone then software and tap the build number 7 times and to make yourself a developer. Exit about phone and open your newly opened developers settings turn off auto updates and enable oem unlocking and debugging.
Now this guide assumes your cv1 device is on nougat. If you are already on oreo and have no ARB number and want to upgrade your oreo rom to include a working fastboot mode then you will need to first downgrade your cv1 device to the earliest version of nougat firmware you can find and repeat the steps above.
To unlock the bootloader go to your adb folder open up a command line and type
adb reboot bootloader
When it boots to a mostly black screen with a tiny lil paragraph describing fastboot and giving some instruction type
fastboot flashing unlock
Or
fastboot oem unlocck
From there your done for now with fastboot. Lets go ahead and type fastboot reboot.
A developer here who was trying to unbrick his lg phone ended up hacking the program LGUP and found out a way to download to different partitions of the phones memory. The option called partition dl will allow us to flash a rom to the phone with out flashing the aboot partition which holds our working fastboot mode. You could even change your phone from a aristo 2 to a fortune 2 or k8 or any number of combinations as long as you do not ever flash aboot.
Warning! Warning! Warning! Warning! Warning!
Just a reminder. If you flash the aboot of anothet cv1 device to your phone it will immediately go dead and will be bricked under Qualcomm HSUSB 9008 mode which at this point in time there is no fix for.
Now you will need LGUP dual mode and since we are using a cv1 device go over to tecknights Aristo 2 page grab LGUP dual mode from there and thank him for all his hard work.
While your there if you want root you will need to go ahead and grab his twrp 4 cv1 devices with oreo kernel from his tutorial on flashing a prerooted oreo rom and port it over to the K8+ or not or i may have it posted here. Either way you will need it soon.
Now download the LG firmware extractor and pull the boot.bin from the oreo rom you are using to upgrade your device to and rename it to boot.img then put it in a dedicated folder in external storage.
Download the latest version of magisk manager put it on your external storage sd card with your oreo boot image.
Now lets flash our K8+(2018) X210ULM to Android 8.1 OREO.
Plug your phone into your windows pc and start LGUP dual mode Dev. When it loads your device hit select and the fladhing screen will appear with several more options than the LGUP your probably used to working with. Click the circle next to
Partition DL
Now go and choose the rom you want to flash and check every partition except aboot. Then hit ok. When it gets done it will reboot into Oreo and you will still have your boitloader is unlocked screen warning upon boot.
If not you did something wrong. Reflash nougat read the directions again and reflash the oreo rom with every partition except aboot. Remember do not flash aboot. If you do you will lose your working fastboot.
You now have a cv1 device that not only has fastboot mode but it can also flash.
Now for root go to settings and set up your developers options and this time you will notice that the oem unlock switch is greyed out in the unlock position.
Now install magisk manager and choose the install by picking a file and patching it. When it gets done you will find it in internal storage Download folder. Now hook plug your phone back into the pc and place your TWRP 4 CV1 DEVICES w OREO KERNEL and magisk patched image into the adb folder and rename them recovery.img and boot.img and open up a commandline there.
Now type
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
Upon booting go to magisk and let it setup up the enviroment and reboot then before rebooting to twrp go ahead and go to settings and Downloads in magisk and install TWRP helper. Then go do not reboot but go up to modules and hit the reboot to recovery option. It should now reboot to twrp where you can now mount your partitions then make a back up then check those mounts again and reboot to system.
Thats it. Your done.
Extra:::
This can be done with any cv1 device that does not have an ARB value on before you start flashing. You upgrade an Aristo 2 to Oreo as well as a Fortune 2. The only stipulation is that you choose firmware with an ARB value of 0 and start with a device with a firmware that has an ARB value of 0.
Ive heard that one could possibly change an Aristo 2 to a Fortune 2 and a Fortune 2 to a K8+ or vice versa but im not brave enough to try.
Please be sure to thank Tecknight for his work with the CV1 and you dont have thank me but it would nice if some one did.
Maybe i said i would post my recovery and rooted boot images. Maybe i didnt. Well i did i say i might. So any way these are my images. One magisk rooted-boot.image for the Lg LM-210ULM ONLY. This image is only to be used with K8+ running oreo. Do not use with nougat.
IF YOU TRY TO USE THIS IMAGE WITH ANOTHER CV1 IT WILL BOOTLOOP.
We also have a TWRP image for K8+ Lg LM-X210ULM android 8.1 Oreo. while this image should work for any android 8.1 cv1 device, its for android 8.1 only and could cause a bootloop if used for a 7.1.2 nougat device.
The recovery i ported over myself from teknights oreo version for cv1 devices. Why did i not just use his since most cv1 devices can use the same recovery? Well when i first started rooting this device i did but had some issues with my device feeezing at the K8+ screen. Also i had to set the system.img to ext4 or no mounting and i had to set firmware to vfat as well. Data was changed to ext4 since every time twrp was started i would have to wipe a reformat it.
Never had a problem where i had to change any thing in the recovery.fstab before but once those changes were made i had no more boot loops, mounting or formatting issues and it works without fail now.
Im including the no verity opt encrypt flash zip too. Dont forget to flash the first time you boot twrp or you might have a bad day.
Edit:::: since i pulled these images using flashify after flashing the no verity zip and also flashing the twrp storage helper you may not need to use flash zip or module yourself but i dont think it would hurt.
Good find!
Do not try to flash another device to your cv1. I have tried this as an experiment and netted a device in hsusb 9008 mode. Only flash rom images for your device or buhbye felicia.
Hi,
First of all, yes, I have checked the other threads that talk about reverting to stock and I am still stuck.
So I installed Kang OS which is Android 11, and now I want to revert to stock. I have tried downloading multiple different versions of the fastboot ROM from the page https://androidfilehost.com/?w=files&flid=294300 and run the flash all batch file and every time I am either getting stuck in a boot loop or getting the Verity Crash Dump Screen. I have managed to reach the fastboot screen, and I am waiting on the fastboot screen, for someone to show me some way.
Thanks in Advance.
If you used a pin then your storage is encrypted and the rom you are trying to flash can't use it, that's why you're most likely stuck at boot.
I ran into the same issue and posted about it in the same thread. I think we will need a new version of TWRP as 3.4.0-0 would not accept my pin which had not changed.
To fix your issue, sadly, you'll need to wipe your storage:
Boot the phone into fastboot mode
Attach your USB cable to the phone/PC
Download and unzip the file I've attached (ADB/Fastboot)
Launch an elevated command window in the folder you extracted the attached zip to
Try the command fastboot devices and ensure that it reports the device correctly, if not then you need to install the latest OnePlus drivers
Type the following in the command window : fastboot -w (This will wipe the storage)
Try your rom again (TWRP should remain as the recovery if you had flashed it already, if not then copy the latest TWRP img file to the same folder as the ADB/Fastboot tools, use fastboot and type boot twrpfilename.img this will make the phone boot into TWRP recovery, you can then copy over the TWRP zip and flash it to recovery using the booted version of TWRP)
Once you've done the above you shouldn't really need to use the fastboot scripts as the latest rom should just flash from TWRP.
Get msm download tool for guacamole which is the codename of the op7p. I know the shorts with the global version I am unsure if this works with T-Mobile or others?
MSM is a bit of a severe fix when they've already confirmed they can still get fastboot, MSM is for completely bricked phones that can't access anything. Wiping the storage and going to fastboot will allow them to just flash recovery then flash the stock rom. Way easier.
Boot into twrp. Then format data. Phone will boot then.
What's this?This is a stock oxygen os fastboot Rom for OnePlus9 adapted from https://forum.xda-developers.com/t/...xygenos-a-04-a-07-for-mt2110-devices.4404719/ .I really appreciate @Valdem for his flashing script for OnePlus 9RT.And I modified his script according to OnePlus 9 partitions and changed some flashing order in script.
Note that this is only for the device which is unlocked bootloader.And internal storge may be cleaned if you downgrade from higher oxygen rom or come from other rom like custom rom.
The ROM's image is extracted from oos11.2.10.10BA and oos12(LE2113_C47) ota package.Note that the ROM is only for ONEPLUS9(LEMONADE).
For full package oxygen os:
Flashing instructions:
- On your PC, install bootloader drivers for OP9 and check if device is recognized in Bootloader and Fastbootd modes.
- On your PC, download the Fastboot ROM zip from the download link below.
- On your PC, unzip downloaded file
- On your PC, navigate to its now-uncompressed folder
- Reboot your OnePlus 9 to bootloader mode.
- Connect the OP9 to your PC
- On your PC open command line window in the uncompressed folder,
- double click flash-all.bat
- wait till PC shows "pause" on terminal.
-Whether to format data is depend on which rom you stayed before. If upgrade from older oxygen os or on the same version oxygen os,no need to format data.Otherwise format data and reboot phone.
For firmware package:
Firmware package is used for whom wants to install custom ROM.And flashing firmware package by using this instead of MSM can streamline the procedure.After the PC shows "pause"on termianl,firmware package has been installed completely.Then following the custom rom install procedure-flash boot boot.img.If not boot into recovery,replace phone into bootloader mode,flashing dtbo and vendor_boot partitions will work.
The using procedure is same as full package.
NOTE:Before using this fastboot ROM and Firmware,you must have a compatible boot.img which can flashing images in fastbootd mode.Oherwise,install the "boot.img","dtbo.img"and"vendor_boot.img"by using "fastboot flash boot boot.img","fastboot flash dtbo dtbo.img"and"fastboot flash vendor_boot vendor_boot.img"in phone's bootloader mode.If phone don't boot into recovery or fastbootd mode,flashing firmware(If target is OOS11,then flashing oos11.2.10.10 firmware;If target is OOS12,then flashing firmware OOS12C47).After this,reflashing boot,dtbo and vendor_boot.
Download link:
Oxygen os 11.2.10.10:OOS11.2.10.10(FULL PACKAGE)
Oxygen os 12(LE2113_C47):OOS12(LE2113_C47)(FULL PACKAGE)
Firmware package:
Oxygen os 11.2.10.10 firmware:OOS11.2.10.10firmware package
Oxygen os 12(LE2113_C47) firmware:OOS12(LE2113_C47)firmware package
in A12, which recovery do you use.
bec. twrp does not survive an Android 12 upgrade.
TWRP no compatible with A12
jmadiaga said:
in A12, which recovery do you use.
bec. twrp does not survive an Android 12 upgrade.
TWRP no compatible with A12
Click to expand...
Click to collapse
This script uses fastboot, not recovery. Custom ROMs typically post the recovery image to use for flashing them in the thread if you're asking about that.
Any one success in flashing OOS11.2.10.10 or OOS12(C47) by using this script?
cbrown666 said:
Any one success in flashing OOS11.2.10.10 or OOS12(C47) by using this script?
Click to expand...
Click to collapse
Fastboot scripts are the quickest path to bricking and having to use MSM in my experience so I'm not trying it. If you do, make sure you switch to slot A first because for some reason, slot B really doesn't like to cooperate on this device.