Related
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ones who are on stock recovery and just want to update their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
I created this thread to help the CM13(Official or Sultan's)//any custom rom using new BL,users who want to update their BL without flashing the OOS through the tedious way just to update BL and users who are stuck on bootlogo due to old BL with roms using new BL.
Here I will guide you through the required steps to update our bootloader "In easiest and fastest way without wiping and restoring anything".
So what are we waiting for ,lets start .
Prerequisites
you will need two files for this process,nothing else.
1 . First one is BLUpdater zip --->Here.
2. Second is TWRP compiled from latest sources use either This or the one from Here<--use v41 or use Sultan's from Here OR if you are Martin's fan like me and want to use his MutiRom TWRP goHere.
PS:I am assuming you have Unlocked Bootloader and have either
official/blu_spark/sultan's/ Multirom TWRP installed,in a working condition on OOS2.x BL(if not what are you doing here).
Note: make sure oem unlocking is checked in developer options in your current rom,else updating the BL may cause it to get locked ,and you will have to unlock it again and flash the recovery manually through fastboot itself.
Now the steps
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
NOTE:If you chose to use Sultan's recovery.zip then just flash it normally.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Now voila you should have updated your firmware/BL.Congrats.
You can now install any rom that supports the new BL.Older roms won't boot on the new MM BL.So check the rom thread before installing the rom and later on quacking here about your device being stuck at bootlogo.
Notes
i)Neither I nor XDA will be responsible if your OPX bricks or explodes or ditches you and flies to space.
ii)We are not touching system partition so last installed ROM will be intact.
iii)This guide will leave you into bootable rom only if you have a rom installed that works on latest firmware.
iv)This can also be used to restore all your OPX partitions back to OOS3.x partition state,if you messed any.
v)In case you are using latest nightly (cm13) and face bootloop - go Here
psst:If you are not diggin the new BL,and wanna downgrade again ,back to old BL,check this post.
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
matwaking said:
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ons who are on stock recovery and just want to their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
So I created this thread just to shorten the process provided by Joshwin.I also created this thread to help the official CM13 users who have problem with latest nightlies due to new bootloader or are stuck in bootlogo.
...
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
Click to expand...
Click to collapse
Booomshkalaka!!!
Great guide, can't test (already have new bootloader and too lazy to switch back but look very good.
Thx to all
Kurt
Kurt Krummbein said:
Booomshkalaka!!!
Click to expand...
Click to collapse
Lol .
Thanks mate.
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
jonrodz said:
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
Click to expand...
Click to collapse
Will work with any twrp,no requirement of official one.
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
jonrodz said:
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
Click to expand...
Click to collapse
No it wont,right now almost all the custom roms need to update to support new firmware.Only latest cm13 nightlies are booting now,also aosp compiled by olddroid for new BL(shh its only for testers right now)
also maybe the MIUI8 port ,just posted in the forums.
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
jerikooo said:
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
Click to expand...
Click to collapse
no update the BL using the steps above ,then flash the latest nightly.That way it would be good.
Or you can flash nightly first then update BL.Choice is yours.I recommend updating the BL first.
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Duplicate post.Deleted
ccaappton said:
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Click to expand...
Click to collapse
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
matwaking said:
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
Click to expand...
Click to collapse
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
ccaappton said:
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
Click to expand...
Click to collapse
Well no fix without any problems hehehe,.Haapy 4 u.
Click that button if you think my posts are useful
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Manelit said:
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Click to expand...
Click to collapse
taking you wanna flash ashwins cm14 right. You just wanna follow the instructions in first post and then flash the cm14.No need to install the whole Oos zip.
This way you should have updated BL and working cm14.
Just flash the cm14 after booting into new TWRP
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
slaav said:
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
Click to expand...
Click to collapse
Press that sweet sweet button mate
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Click to expand...
Click to collapse
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
walsash said:
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
Click to expand...
Click to collapse
u can flash bluespark twrp via fasboot
Sent from my ONE E1003 using XDA-Developers mobile app
This is for people who have received their phone with a pre-installed Vendor ROM (MIUI Global Stable 8.0.8.0) and wants to switch to the Unofficial EU ROM. In my opinion, the EU ROM is currently the best ROM without any Chinese bloatware or popups until Xiaomi decides to release an actual Global ROM.
For those who are already on a China Stable ROM, there is already an excellent guide to install TWRP, ROOT, compiled by @underlines. This is only intended for switching from a Vendor ROM as I wasn't able to switch from a Vendor ROM to an official build using the previous guide. You need to be on an official build to be able to use TWRP and flash the EU ROM.
EDIT : The reason why I have mentioned to flash an official build at first is because, TWRP can be unresponsive with some Vendor ROMS. You'll be able to boot TWRP but touch would be frozen. I've tried with both versions of TWRP and it wouldn't work with the Vendor ROM installed on my device. TWRP over the Vendor ROM may work for some users.. For some builds like the one which came installed on my phone, it may not work. If TWRP works for you without being on an official build, you can skip the part where you have to flash an official ROM.
1. You need to have an unlocked bootloader. Please follow instructions on the other guide on how to do this.
2. You need the older version of MiFlash found on this link. Thanks to @Thorin78 for this link.
3. Download and extract fastboot Stable or Dev ROM and extract ROM folder to the C:\ Drive. This is because MiFlash may show a "cannot find file" error if you have a lot of subfolders. To avoid this, its best if the folder is C:\ROM Folder.
4.In the older version of MiFlash, click advanced and change the fastboot script location to the flash_all.bat in your unzipped rom folder.
5.Connect your phone in fastboot mode, click "Refresh" in MiFlash. Once your phone is detected, click "Flash" and it should now successfully flash the official ROM of your choice.
If you wish to be on a Xiaomi Official Stable or Dev ROM, Stop here! If you wish to continue installing the EU ROM proceed with the steps below.
6. Now that you have successfully flashed Official Stable or Dev ROM, use Minimal ADB and flash TWRP RC2 using the instructions in the other guide.
7. Once you are in TWRP, Swipe right to allow System Modifications and copy the forced encryption disabler using MTP. Flash this file to ensure that there are no bootloops.
8. After this step, go to WIPE, Format Storage, type "yes" and then Reboot Recovery. Copy SuperSU and EU ROM to storage and flash. Phone may take a few minutes to boot up and you will successfully boot the EU ROM.
For everything else, please follow the guide posted by underlines.
TWRP EU RC2 works with the China Dev ROM as well. Once you Swipe to Right to allow modifications, don't forget to flash the latest dm-verity and forced encryption disabler script from here. This is to prevent the device going into a bootloop.
These are the steps I followed and I am on EU ROM. Hope this helps people who wish to switch to the EU ROM from the Vendor ROM.
The link to miflash takes you DL minimal adb?
jazz452 said:
The link to miflash takes you DL minimal adb?
Click to expand...
Click to collapse
Corrected. Thanks for letting me know! Cheers!
satishp said:
Corrected. Thanks for letting me know! Cheers!
Click to expand...
Click to collapse
I managed to flash with latest miflash using your guide my bootloader was already unlocked check using:
boot your phone into fastboot and COMMAND PROMPT " fastboot oem device-info "
most are probably unlocked with vendor rom but not all.
Don't try to unlock with this method just check to save sometime.
guide: http://xiaomitips.com/guide/how-to-check-if-redmi-note-3-bootloader-is-locked-or-unlocked/
jazz452 said:
I managed to flash with latest miflash using your guide my bootloader was already unlocked check using:
boot your phone into fastboot and COMMAND PROMPT " fastboot oem device-info "
most are probably unlocked with vendor rom but not all.
Don't try to unlock with this method just check to save sometime.
guide: http://xiaomitips.com/guide/how-to-check-if-redmi-note-3-bootloader-is-locked-or-unlocked/
Click to expand...
Click to collapse
I guess it also depends on the Vendor ROM and customization which comes installed on your device. Not all Vendor ROMs for this device are the same. I tried everything under the sun with the latest miflash. It would detect device and even give a "success" output but the ROM was never actually flashed. The phone would still be on the Vendor ROM. Its as if some Vendor ROMs have some form of write protection baked in.
I could only get it working with the older miflash.
I'm not saying it was easy, the hard thing was making the unpack ING of the file. Sort of did it twice never had that problem before.
Why is it required to flash the official rom before flashing the EU rom?
nkatz565 said:
Why is it required to flash the official rom before flashing the EU rom?
Click to expand...
Click to collapse
This for people who don't want TWRP, root and dm-verify, just genuine Xiaomi rom with OTA updates and remove vendor rom.
QQ.
I did the following on my Mix and wondering if I am missing anything. I should say that everything "appears" to be working perfectly on the EU rom.
My Mix came with 8.0.8.0 Global (Vendor ROM) and I wanted to move onto the Xiaomi.eu rom. I loosely followed the above guide and did the following steps:
Applied for Unlock
Unlocked the device via MiUnlock
Used Minimal ADB and booted the device into FastBoot
Confirmed device was Bootloader unlocked
Flashed TWRP (latest non-eu build)
Booted to recovery
DID NOT swipe to edit system partition, left that read only
Flashed the latest Weekly Xiaomi.eu build
Wiped Dalvik/Cache
Booted phone
Performed a Factory reset.
All seemed a little too easy and I didnt need to go to an "Official" china ROM first. But I do have a few questions...
Should I have swiped Yes to enter Read/Write mode for the system partition and run a dm-verify? (I am not interested in Rooting the device at this stage)
Should I have performed a System clear in TWRP before installing Xiaomi.eu ontop of the Vendor ROM?
geubes said:
QQ.
I did the following on my Mix and wondering if I am missing anything. I should say that everything "appears" to be working perfectly on the EU rom.
My Mix came with 8.0.8.0 Global (Vendor ROM) and I wanted to move onto the Xiaomi.eu rom. I loosely followed the above guide and did the following steps:
Applied for Unlock
Unlocked the device via MiUnlock
Used Minimal ADB and booted the device into FastBoot
Confirmed device was Bootloader unlocked
Flashed TWRP (latest non-eu build)
Booted to recovery
DID NOT swipe to edit system partition, left that read only
Flashed the latest Weekly Xiaomi.eu build
Wiped Dalvik/Cache
Booted phone
Performed a Factory reset.
All seemed a little too easy and I didnt need to go to an "Official" china ROM first. But I do have a few questions...
Should I have swiped Yes to enter Read/Write mode for the system partition and run a dm-verify? (I am not interested in Rooting the device at this stage)
Should I have performed a System clear in TWRP before installing Xiaomi.eu ontop of the Vendor ROM?
Click to expand...
Click to collapse
Wouldn't worry about it the vendor ROMs aren't poison, not sure about dm-verify if you kept read only. I would of swiped then flashed dm-verify but didn't mean I know what I'm doing.
nkatz565 said:
Why is it required to flash the official rom before flashing the EU rom?
Click to expand...
Click to collapse
This is because some Vendor ROMS have some compatibility issues with TWRP. Touch screen wouldn't work on TWRP. I tried both TWRP versions and couldn't get touch to work.
Finally, I flashed the China Dev ROM and then used TWRP RC2 and touch functionality worked.
As some users below have pointed out that they could get to EU without flashing the one of the official builds, I guess it depends on the amount or type of vendor customizations applied on your device.
Which version do you own? I was wondering if this would work with the 6GB as well.
dbesada said:
Which version do you own? I was wondering if this would work with the 6GB as well.
Click to expand...
Click to collapse
This works with both versions. The ROM is compatible with both variants as the size of memory and storage doesn't affect compatibility.
I have the 6\256 variant.
satishp said:
This works with both versions. The ROM is compatible with both variants as the size of memory and storage doesn't affect compatibility.
I have the 6\256 variant.
Click to expand...
Click to collapse
Thank you. It worked. I fastboot twrp then factory reset the device and flashed the eu rom. All good. My bootloader was unlocked by the vendor.
Can someone please give me some advice? Just got the phone a couple hours ago. I took a picture of the info page. Based on the screenshot am I on the vendor ROM or official? I'm thinking I'm on Vendor because it has GAPPS already included.
If I'm on Vendor ROM and want to get to rooted EU Rom I can follow directions in the OP right?
How do I know is if my bootloader is already unlocked? Many thanks
SantinoInc said:
Can someone please give me some advice? Just got the phone a couple hours ago. I took a picture of the info page. Based on the screenshot am I on the vendor ROM or official? I'm thinking I'm on Vendor because it has GAPPS already included.
If I'm on Vendor ROM and want to get to rooted EU Rom I can follow directions in the OP right?
How do I know is if my bootloader is already unlocked? Many thanks
Click to expand...
Click to collapse
Vendor (there is no Global ROM for Mix). You should unlock your bootloader (check if it's already unlocked using "fastboot oem device-info"), flash TWRP, wipe and flash EU
Razorbacktrack5535 said:
Vendor (there is no Global ROM for Mix). You should unlock your bootloader (check if it's already unlocked using "fastboot oem device-info"), flash TWRP, wipe and flash EU
Click to expand...
Click to collapse
Do I have to do Power + Vol Down (that's bootloader mode right) in order to input the ADB code you gave me?
SantinoInc said:
Do I have to do Power + Vol Down (that's bootloader mode right) in order to input the ADB code you gave me?
Click to expand...
Click to collapse
Yes, you have to use Fastboot Mode
Razorbacktrack5535 said:
Yes, you have to use Fastboot Mode
Click to expand...
Click to collapse
I'm not unlocked right? Hope they approve my unlock request soon
SantinoInc said:
I'm not unlocked right? Hope they approve my unlock request soon
Click to expand...
Click to collapse
Yes, you have to wait
I'm not responsible for any damage to your device. For more info check Xiaomi.eu (source)
Bootloader needs to be unlocked: http://en.miui.com/unlock/
Install TWRP via Fastboot mode
Code:
fastboot flash recovery twrp.img
fastboot boot twrp.img
https://androidfilehost.com/?fid=4349826312261761273
Ps: It worked for me.
Optional: (I haven't tried this yet)
For ROOT install Magisk (may cause lags and fingerprint issue) in TWRP, reboot one more time after install to get rid of system lags.
https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip
https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
If you decide to install Xiaomi eu roms: Go with the stable version of miui11. Code name of the rom is "Imi" K30 pro (it is also for pocof2pro)
https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv11/
ROMs for devices with locked bootloader:
Unlock your bootloader here, this will erase your data. Make a backup. http://en.miui.com/unlock/
Install TWRP via Fastboot mode, then install ROM
Code:
fastboot flash recovery twrp.img
fastboot boot twrp.img
TWRP Recovery Zip or TWRP.ME (link above)
FORMAT / Wipe your data,cache,Internal storage,dalvik DONT WIPE SYSTEM OR YOU WILL BRICK YOUR DEVICE!!!
Copy ROM to the internal storage
Install ROM
Reboot
done
Installation via TWRP:
- Download zip to internal storage
- Updater - Menu (...) - Reboot to Recovery.
- Install - Select zip
- Reboot
- Done
Cheers
More info:
[ROM][LMI][10] Xiaomi.eu Weekly | Stable MIUI 12 for Redmi K30 Pro/Zoom/Poco F2 Pro thread
New at making tutorials
I'm new at this so please bear with me ?
Redmi k30 pro, k30 pro zoom and Poco f2 pro all flash with lmi. The k30 pro zoom is lmipro but uses the same as the other 2 models.
Is there a reason you recommend version 17.1 of Magisk?
The current version is 20.4: https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
No reason ?
cgdams said:
Is there a reason you recommend version 17.1 of Magisk?
The current version is 20.4: https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
Click to expand...
Click to collapse
I did not see there was a newer version. Thanks ?
Hi you mean never delete system or persist, You just have to do the right data format and nothing else, and install Xiaomi EU, I know that you must also wipe the system and vendor advice from the MIUI MIX guys I don't know you get confused so
---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------
Hi you mean never delete system or persist, You just have to do the right data format and nothing else, and install Xiaomi EU, I know that you must also wipe the system and vendor advice from the MIUI MIX guys I don't know you get confused so
Cool
rosy09 said:
Hi you mean never delete system or persist, You just have to do the right data format and nothing else, and install Xiaomi EU, I know that you must also wipe the system and vendor advice from the MIUI MIX guys I don't know you get confused so
---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------
Hi you mean never delete system or persist, You just have to do the right data format and nothing else, and install Xiaomi EU, I know that you must also wipe the system and vendor advice from the MIUI MIX guys I don't know you get confused so
Click to expand...
Click to collapse
Could you then write how to do the right data format? I'll add it to the post. Thanks for clearing that ?
Is this TWRP chinese version? Any links for english version of TWRP?
Twrp version
spicediablo said:
Is this TWRP chinese version? Any links for english version of TWRP?
Click to expand...
Click to collapse
Right now it is the only version I know of. You can find more info in the xiaomi eu web page.
don't really wanna install some unofficial twrp. Probably gonna wait till the official twrp website hosts the recovery for this device.
Does anyone know when or if teamwin is gonna release an official twrp?
Teamwin
herpsnderpsn said:
don't really wanna install some unofficial twrp. Probably gonna wait till the official twrp website hosts the recovery for this device.
Does anyone know when or if teamwin is gonna release an official twrp?
Click to expand...
Click to collapse
I have just asked through their webpage. I'll let you know as soon as they write back.
spicediablo said:
Is this TWRP chinese version? Any links for english version of TWRP?
Click to expand...
Click to collapse
just change language to english
Any drivers?
Great work!
I suggest to move this thread to "Xiaomi Poco F2 Pro (Redmi K30 Pro) ROMs, Kernels, Recoveries, & Other Development".
And maybe use a naming convention and a template for the first post also add sourcecode.
Noob
GoldeneyeS2 said:
Great work!
I suggest to move this thread to "Xiaomi Poco F2 Pro (Redmi K30 Pro) ROMs, Kernels, Recoveries, & Other Development".
And maybe use a naming convention and a template for the first post also add sourcecode.
Click to expand...
Click to collapse
Hello ?,
I'm a noob at this. I just posted this because it took so long to have a thread that I wanted to show that there was some development on the device. There is a better thread in the forum about the same recovery and rom. Is there a way to delete this thread?
urez2beat said:
just change language to english
Click to expand...
Click to collapse
Does Twrp fit? Good Poco F2? cyanogenmods.org/twrp-poco-f2-pro/[/url]
Someone tried ?
leelossyferi said:
Does Twrp fit? Good Poco F2? cyanogenmods.org/twrp-poco-f2-pro/[/url]
Someone tried ?
Click to expand...
Click to collapse
Yes, works fine
Actually I'm finding alot of problems with this TWRP and I just hope TEAMWIN puts out an official version
urez2beat said:
Actually I'm finding alot of problems with this TWRP and I just hope TEAMWIN puts out an official version
Click to expand...
Click to collapse
Yeah me too, had trouble flashing the updated gpu drivers via using the Chinese twrp.
XDRdaniel said:
Yes, works fine
Click to expand...
Click to collapse
Yep. Though on consecutive reboots it just goes back to stock recovery unless I fastboot boot recovery.img again.
I haven't installed lazy flasher etc though.
Hello,
I would like to upgrade my Redmi Note 7 lavender.
The MIUI 12.1 by Xiaomi.eu 20.7.9 beta version is currently installed.
The smartphone mounts the OrangeFox R10.1_3.
I should restore the stock recovery, but I don't know how and where to find the recovery.img file.
Expanding the ROM I found only the boot.img file.
Can someone help me?
Thank you.
nigol
nigol said:
Hello,
I would like to upgrade my Redmi Note 7 lavender.
The MIUI 12.1 by Xiaomi.eu 20.7.9 beta version is currently installed.
The smartphone mounts the OrangeFox R10.1_3.
I should restore the stock recovery, but I don't know how and where to find the recovery.img file.
Expanding the ROM I found only the boot.img file.
Can someone help me?
Thank you.
nigol
Click to expand...
Click to collapse
If you install stock MIUI and reboot to system, MIUI overwrites the custom recovery with the stock one.
darhma said:
If you install stock MIUI and reboot to system, MIUI overwrites the custom recovery with the stock one.
Click to expand...
Click to collapse
Thanks for the reply.
But I don't want to reinstall MIUI because I would lose many current configurations that have already cost me a lot of time, I just wanted to know how to recover the recovery.img file relating to the MIUI version currently installed in order to use the command
"fastboot flash recovery recovery.img"
without having to reinstall anything.
Thanks anyway, but the problem remains.
nigol
nigol said:
Thanks for the reply.
But I don't want to reinstall MIUI because I would lose many current configurations that have already cost me a lot of time, I just wanted to know how to recover the recovery.img file relating to the MIUI version currently installed in order to use the command
"fastboot flash recovery recovery.img"
without having to reinstall anything.
Thanks anyway, but the problem remains.
nigol
Click to expand...
Click to collapse
I think that you need a custom recovery to update xiaomi.eu, why do you need the stock recovery? I found this (is about redmi note 9 but should be valid also for rn7) https://xiaomi.eu/community/threads/recovery-in-xiaomi-eu-fastboot-rom.56358/
nigol said:
... I should restore the stock recovery, but I don't know how and where to find the recovery.img file ...
Click to expand...
Click to collapse
Download a MIUI fastboot ROM, and extract it. You should find a recovery.img in it.
DarthJabba9 said:
Download a MIUI fastboot ROM, and extract it. You should find a recovery.img in it.
Click to expand...
Click to collapse
Thanks, everything OK!
Update successfully installed!
nigol
Links to Official MIUI Roms & Flash Tool
Latest MIUI Official ROMs
Xiaomi Flash Tool
Hello,
I tried to root my 9T(model M2010JI9SG) following this guide:
I used twrp from this link:
Xiaomi Mi 9T / Redmi K20
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
version 3.5.2_9-0
after I flashed twrp, I got into fastboot mode, which I can't leave.
I tried doing volume up +power, volume down+ power, and all the buttons as well, nothing worked, every time it goes back to fastboot,
I tried to redo everything, still didn't fix, and tried to flash stock via mi tool, didn't work too.
Please help me fix that,
Thanks!!!
Shahaf said:
Hello,
I tried to root my 9T(model M2010JI9SG) following this guide:
I used twrp from this link:
Xiaomi Mi 9T / Redmi K20
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
version 3.5.2_9-0
after I flashed twrp, I got into fastboot mode, which I can't leave.
I tried doing volume up +power, volume down+ power, and all the buttons as well, nothing worked, every time it goes back to fastboot,
I tried to redo everything, still didn't fix, and tried to flash stock via mi tool, didn't work too.
Please help me fix that,
Thanks!!!
Click to expand...
Click to collapse
OMG
You should first of all know your phone model
"Redmi 9T" reads as different name than "Mi 9T", isn't it?
Hence you MUST NEVER flash TWRP for Redmi K20/Mi 9T (guide clearly says it is for that phone, check the big picture in your post) to your Redmi 9T
oh damn, I can fix that somehow?
Shahaf said:
oh damn, I can fix that somehow?
Click to expand...
Click to collapse
Check on twrp.me is there TWRP for your Redmi 9T
Or download the so called Fastboot/TGZ ROM for your M2010JI9SG, extract recovery.img (stock Recovery) and flash it back over the wrong TWRP
For more details search on XDA for Redmi 9T subforum (this one is for Mi 9T), there should be users and freaks who can better help you for the same phone
zgfg said:
Check on twrp.me is there TWRP for your Redmi 9T
Or download the so called Fastboot/TGZ ROM for your M2010JI9SG, extract recovery.img (stock Recovery) and flash it back over the wrong TWRP
For more details search on XDA for Redmi 9T subforum (this one is for Mi 9T), there should be users and freaks who can better help you for the same phone
Click to expand...
Click to collapse
Thank you, I will check with them!
Shahaf said:
Thank you, I will check with them!
Click to expand...
Click to collapse
Here you can find firmwares for lime:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
You should (?) know what was your installed firmware, download the same Fastboot/tgz and extract (TGZ=Tar+GZIP) your original stock recovery.img, and flash it from Fastboot (just like you flashed the wrong TWRP)
You could also use MiFlash tool to flash the whole firmware, but it must be not needed
zgfg said:
Here you can find firmwares for lime:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
You should (?) know what was your installed firmware, download the same Fastboot/tgz and extract (TGZ=Tar+GZIP) your original stock recovery.img, and flash it from Fastboot (just like you flashed the wrong TWRP)
You could also use MiFlash tool to flash the whole firmware, but it must be not needed
Click to expand...
Click to collapse
It worked!!! now my device is working, now in order to root, which twrp should I use?
Shahaf said:
It worked!!! now my device is working, now in order to root, which twrp should I use?
Click to expand...
Click to collapse
You don't need TWRP. Extract boot.img (like you extracted recovery.img). Install Magisk apk and use the method Install (Magisk), then Select and patch your boot.img (do not tick Recovery option)
Find the patched img in Download folder, transfer to PC and flash from Fastboot - this time to boot partition, not to recovery partition
If anything goes wrong, flash back the stock boot img
Btw, on that Redmi 9T, do you have A12 (or A11 or what) and is it MTK chipset?
Generally, use Magisk Stable v23 from TJW:
Magisk/README.MD at master · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
But if A12 or MTK and if it ain't work, you can try Magisk Alpha ('pilot' builds for the new Magisk to be soon? released)
zgfg said:
You don't need TWRP. Extract boot.img (like you extracted recovery.img). Install Magisk apk and use the method Install (Magisk), then Select and patch your boot.img (do not tick Recovery option)
Find the patched img in Download folder, transfer to PC and flash from Fastboot - this time to boot partition, not to recovery partition
If anything goes wrong, flash back the stock boot img
Btw, on that Redmi 9T, do you have A12 (or A11 or what) and is it MTK chipset?
Generally, use Magisk Stable v23 from TJW:
Magisk/README.MD at master · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
But if A12 or MTK and if it ain't work, you can try Magisk Alpha ('pilot' builds for the new Magisk to be soon? released)
Click to expand...
Click to collapse
I tried to do it, after I patched boot.img I transfered it to my PC and did fastboot boot boot_patched.img
it did ok on sending, but then failed on booting(unknown command), any fix for that?
Flash (not boot) a healthy un-patched stock "boot.img" that is signed with your ROM version to the device and see if that works.
Shahaf said:
I tried to do it, after I patched boot.img I transfered it to my PC and did fastboot boot boot_patched.img
it did ok on sending, but then failed on booting(unknown command), any fix for that?
Click to expand...
Click to collapse
fastboot boot xxx.img boots one time to the xxx.img
For flashing (permanently) to boot you need to use:
fastboot flash boot xxx.img
Before flashing the 'stock' or patched boot img, pls double check: compare your firmware name in Settings / My device against the fastbboot/tgz package you downloaded and extracted the boot.img from
Recovery images might be the same for several firmwares, but boot.img is more critical. If extracted from the wrong firmware, it will not be your real stock boot.img and will not boot
You can use this app (now when your phone boots) to download and look for the proper firmware:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
Shahaf said:
It worked!!! now my device is working, now in order to root, which twrp should I use?
Click to expand...
Click to collapse
I would trust to the following thread on Xiaomi.eu forum, to find the suitable TWRP for your device.
Post #1, link to AFH, then scroll to lime (if that's the code name for your Redmi 9T):
[TWRP][RECOVERY] List of relevant recovery in one place
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/ I have compiled a list of relevant recovery in one place, i think it will be useful. Updates are monitored each day. Welcome, friends! How to install TWRP https://xiaomi.eu/community/threads/installing-a-custom-recovery.67841/
xiaomi.eu
Based on experience with my 9T I would pick
twrp-3.5.2_10-3-lime-brigudav.img
I.e., Xoaomi.eu provides weekly and stable firmwares that are usually well ahead of the official firmwares (on my Mi 9T, daily driver and businesses phone I was 9 months on their weeklies until I switched to their Stable two months ago)
The point is that Xiaomi.eu firmwares for most phones (I just checked, Redmi 9T is on the list) require TWRP to flash
That means if people recommend the TWRP as there, it nust be the right one
Once you have TWRP you can back up your boot partition. You will get boot.emmc.win and that will be your exact stock boot.img
You can still use the Patch and Flash method to install Magisk (as described you earlier), by patching that boot.emmc.win
zgfg said:
I would trust to the following thread on Xiaomi.eu forum, to find the suitable TWRP for your device.
Post #1, link to AFH, then scroll to lime (if that's the code name for your Redmi 9T):
[TWRP][RECOVERY] List of relevant recovery in one place
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/ I have compiled a list of relevant recovery in one place, i think it will be useful. Updates are monitored each day. Welcome, friends! How to install TWRP https://xiaomi.eu/community/threads/installing-a-custom-recovery.67841/
xiaomi.eu
Based on experience with my 9T I would pick
twrp-3.5.2_10-3-lime-brigudav.img
I.e., Xoaomi.eu provides weekly and stable firmwares that are usually well ahead of the official firmwares (on my Mi 9T, daily driver and businesses phone I was 9 months on their weeklies until I switched to their Stable two months ago)
The point is that Xiaomi.eu firmwares for most phones (I just checked, Redmi 9T is on the list) require TWRP to flash
That means if people recommend the TWRP as there, it nust be the right one
Once you have TWRP you can back up your boot partition. You will get boot.emmc.win and that will be your exact stock boot.img
You can still use the Patch and Flash method to install Magisk (as described you earlier), by patching that boot.emmc.win
Click to expand...
Click to collapse
it worked! thank you