Official Xiaomi MIUI 7
Xiaomi Mi 5
Recovery ROM and Fastboot ROM
Introduction
This topic will just gather all available MIUI ROM Versions (Fastboot and Recovery) for the Xiaomi Mi 5. I will keep it up to date, as good as possible.
The same information you can get from the official MIUI forum, but as the forum is big, it' s nice to have a short summary here. Please be aware that for the moment there is only the China stable ROM. Included languages are some Chinese + English.
Stable ROM
Waiting for global.
Developer ROM
Waiting for global.
Developer ROM Naming:
It's all about the date. like MIUI6.3.17 is 2016/03/17
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. P You are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Why this disclaimer
People often fail to read and do stupid stuff. The disclaimer is just here to remind you of this. Mistakes happen, mistakes happen fast. Think before you act.
There is a good amount of guides online on how to flash a Fastboot ROM on a MIUI. But there is something new for locked phones. The old recovery is gone , it got replaced! So be careful, know what you are doing before you do it.
Hope this is helpful to you guys.
will flashing one of these lock the bootloader again? anyone knows?
gajrut said:
will flashing one of these lock the bootloader again? anyone knows?
Click to expand...
Click to collapse
It's up to you.
I unlocked my phone on the first day of use, did loads of updates through stock recovery and mi-flash, and none of it locked my bootloader.
Assuming you do it right: Recovery ROM's won't lock it again
I tested it and so far: Going from 7.2.3 to 7.2.4 to 7.2.5 to 7.2.6 did not lock my phone again.
But if you want to you can use the flash_all_lock.bat or flash_all_lock.sh to lock the bootloader.
Picture of an extracted Fastboot-ROM:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These scripst are identical to the flash_all.bat / flash_all.sh up to the following lines:
Additional lines in flash_all_lock:
Code:
...
fastboot %* erase devinfo
...
fastboot %* oem lock
....
So as long as you don't flash using flash_all_lock, you should be fine. And your bootloader should stay unlocked.
But things might change, I only tried it with all available firmware versions, no guarantee for the future. I don't know about that.
Bootloader comes unlocked?
Me_Ashish_ said:
Bootloader comes unlocked?
Click to expand...
Click to collapse
No, the bootloader is locked.
Have a look at this: http://forum.xda-developers.com/mi-5/how-to/unlocking-xiaomi-mi-5-bootloader-t3336243
TheUltrametricSpace said:
It's up to you.
I unlocked my phone on the first day of use, did loads of updates through stock recovery and mi-flash, and none of it locked my bootloader.
Assuming you do it right: Recovery ROM's won't lock it again
I tested it and so far: Going from 7.2.3 to 7.2.4 to 7.2.5 to 7.2.6 did not lock my phone again.
But if you want to you can use the flash_all_lock.bat or flash_all_lock.sh to lock the bootloader.
Picture of an extracted Fastboot-ROM:
These scripst are identical to the flash_all.bat / flash_all.sh up to the following lines:
Additional lines in flash_all_lock:
Code:
...
fastboot %* erase devinfo
...
fastboot %* oem lock
....
So as long as you don't flash using flash_all_lock, you should be fine. And your bootloader should stay unlocked.
But things might change, I only tried it with all available firmware versions, no guarantee for the future. I don't know about that.
Click to expand...
Click to collapse
I tried flashing 7.2.5 & 7.2.6 using mi flash (flash_all_except_storage.bat) tool. MiFlash says success but I think it bootloop. I've waited about half an hour for it to boot. It's just showing mi logo and running three dots at the bottom. How long more should I wait? Any thoughts?
gajrut said:
I tried flashing 7.2.5 & 7.2.6 using mi flash (flash_all_except_storage.bat) tool. MiFlash says success but I think it bootloop. I've waited about half an hour for it to boot. It's just showing mi logo and running three dots at the bottom. How long more should I wait? Any thoughts?
Click to expand...
Click to collapse
I've no idea.
updated. Added developer and latest stable
TheUltrametricSpace said:
updated. Added developer and latest stable
Click to expand...
Click to collapse
Thanks......
fixed the bootloop issue :good:
TheUltrametricSpace said:
Hope this is helpful to you guys.
Click to expand...
Click to collapse
sure will... nothing like being able to slap different ROM's on the device of this calibre.
being in India, we are yet to see the Mi5 here up for sale just yet.
all the previous claimed release dates has whoooooshed by
Can we flash the developer china MIUI or global MIUI from updater, without unlocking bootloader.
updated to 7.2.8; the new developer 6.3.24 will follow as soon it's out.
Hi, i want to flash my Mi5 with fastboot mode
I have downloaded the updated MiFlash (http://bigota.d.miui.com/tools/MiPhone20151028.exe)
and the ROM.
My phone already entered fastboot mode, but it's not detected on MiFlash.
I've attached the screenshot at http://en.miui.com/thread-249284-1-1.html
What's wrong or what is missing?
thank you in advance
Guys you can't post roms that have the Mi-store built in.
zelendel said:
Guys you can't post roms that have the Mi-store built in.
Click to expand...
Click to collapse
Is this up to date?
I read on en.miui.com that Xiaomi takes copyright stuff serious now, but dunno.
Ok stop and think about that for a mine. They take copy rights seriously? They rip off the design of IOS for the software and every other oem on the hardware.
And yes. It is up to date. The Mi-store is a known warez market. It is only in the China based versions of their roms.
zelendel said:
Ok stop and think about that for a mine. They take copy rights seriously? They rip off the design of IOS for the software and every other oem on the hardware.
And yes. It is up to date. The Mi-store is a known warez market. It is only in the China based versions of their roms.
Click to expand...
Click to collapse
Why do you lurk here to post negative remarks everywhere?
kickassdave said:
Why do you lurk here to post negative remarks everywhere?
Click to expand...
Click to collapse
I'm sorry if you find the truth negative. I was just explaining the reasoning behind our stance.
zelendel said:
Ok stop and think about that for a mine. They take copy rights seriously? They rip off the design of IOS for the software and every other oem on the hardware.
And yes. It is up to date. The Mi-store is a known warez market. It is only in the China based versions of their roms.
Click to expand...
Click to collapse
Cut it, and be reasonable!
All companies copy. (So does Apple.)
And the worst evil are phones that ship with a Webbrowser (according to your logic). As web-browser allow to download childporn and other highly highly illegal stuff.
So the question is: Are Web browser banned as they may give access to some stuff or is the user in charge?
Is it in the ends, the users fault if he broke any kind of law?
It's important to keep people aware of it, but don't overreact! Keep it reasonable.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As anyone who has unlocked the bootloader on their 5X knows, this message appears at startup. I've flashed the PureNexus ROM and then the EX Kernel but neither of these removes the message. It's not a huge deal since everything is working as it's supposed to. Just not sure what can be done to remove that message.
I believe there is nothing we can do, short of getting our hands on an engineering bootloader.
I was wrong, see post #6 below!
Unlocking the BL is the only way to root, right?
km8j said:
Unlocking the BL is the only way to root, right?
Click to expand...
Click to collapse
Dude...
sn0warmy said:
Dude...
Click to expand...
Click to collapse
Thanks for the help
Sent from my Nexus 5X using Tapatalk
It might be possible to replace the images with this tool:
http://forum.xda-developers.com/nex...-change-bootlogo-images-imgdata-tool-t3240052
solara1973 said:
It might be possible to replace the images with this tool:
http://forum.xda-developers.com/nex...-change-bootlogo-images-imgdata-tool-t3240052
Click to expand...
Click to collapse
Judging by the screenshots, It looks like you're right - The delay would still be there but happy to stand corrected here!
Useful note from the thread:
ddggttff3 said:
Just tested, and yes you can visually remove the warnings, but note flashing a custom imgdata file will cause the bootloader to boot to the red error screen instead of the yellow one, so you will want to update the images for all of the warning messages to remove it.
Click to expand...
Click to collapse
Warning message is an Eye Sore!, my offer
That caution warning is a complete downer.... I would be willing to pay 250 dollar bounty to a deve who can either:
1. remove the warning as a stand alone solve or ,
2. force the Google screen to run in its place for that time period.
3. Packed as a zip to flashed in recovery or an img. for fastboot flash...
Think in time, as more of the phones get out in public, it will help the community who wants the unlock but not the eye sore warning...
So far my exploring has scored a big zero to solve the issue...
I'm putting it out there for whoever wants to give it a go. It will be good for the community.
Cheers, CG
I've been thinking about this, but my android-fu isn't too strong. I still need to do a bunch of research.
There are three warning messages - yellow, orange, and red. I think you get the yellow one when the bootloader is unlocked and the red one when the verity checksums do not match the actual rom (I.e., something has been modified).
I think one way would get rid of the messages would be to relock the bootloader and also update the checksums so that they do match. I might be missing something here, but the issue with locking the bootloader, is that we won't be able to flash any new recoveries. I think this can be worked around by flashing the new recovery as a zip file, not an image. My marshmallow-fu isn't great in this area, so I'm not sure what has changed recently that prevents this.
The red warning might be harder and I need to do more research into the checksum process and how the rom is verified. I suspect this has to do with the dm-verity bits.
Edit: OK, I did 20 mins of "research" - http://source.android.com/security/verifiedboot/verified-boot.html#overview
We will get the orange warning if the bootloader is unlocked.
If the bootloader is locked, we will get the yellow warning whenever the signatures don't match the OEM key, but do match the public keys (user, not OEM) used to sign the images.
The red warning can be avoided by signing the images and including the public key.
As noted above, the images can be changed to reduce the eyesore. In a more ideal world, we would just get the yellow warning.
I really hope one day we can get rid of that eye sore
mdrt4me said:
2. force the Google screen to run in its place for that time period.
3. Packed as a zip to flashed in recovery or an img. for fastboot flash...
Click to expand...
Click to collapse
stu5797 said:
I really hope one day we can get rid of that eye sore
Click to expand...
Click to collapse
I've made a couple of replacements that you might like to flash.
See the first post in that thread for more background information.
PhoenixTank said:
I've made a couple of replacements that you might like to flash.
See the first post in that thread for more background information.
Click to expand...
Click to collapse
This worked perfectly using the fastboot flashing method. That ugly message is now gone. Thanks!
Works perfect!
Just flashed via fastboot!
Annoying screen is gone!
THANKS
PhoenixTank said:
I've made a couple of replacements that you might like to flash.
See the first post in that thread for more background information.
Click to expand...
Click to collapse
Used subtle zip, flashed with TWRP. Worked like a champ.:good:
I already love this mod. It could be 100% perfect if it had the exact unlock pad underneath google just like the boot screen, though. Still amazing work!
Witek_M said:
Used subtle zip, flashed with TWRP. Worked like a champ.:good:
Click to expand...
Click to collapse
Glad to know the zip works! Since I haven't said it here, be sure to grab the stock.zip from the first post of bitdomo's thread (linked above). Important for any "uh-oh" moments or updates.
stu5797 said:
I already love this mod. It could be 100% perfect if it had the exact unlock pad underneath google just like the boot screen, though. Still amazing work!
Click to expand...
Click to collapse
That shouldn't be too hard, thanks for the feedback. I could rush out a quick version, but posting up images just before I sleep doesn't fill me with ease.
No promises but hopefully I'll have time tomorrow
Created another version of subtle with an unlocked padlock. Check the main thread above for them.
If someone wanted the visible option with a padlock, please let me know.
You should start your own thread in the Mod section! People will really love this but its too hard to find! THANK YOU AGAIN!
^^ Agreed!
PhoenixTank said:
I've made a couple of replacements that you might like to flash.
See the first post in that thread for more background information.
Click to expand...
Click to collapse
I noticed these are for BHZ10i, that's a model number right? Mine is mhc19j, can this be used for my phone as well? or how to disable the warning for my Nexus 5X?
---------- Post added at 05:24 PM ---------- Previous post was at 04:25 PM ----------
rollex said:
I noticed these are for BHZ10i, that's a model number right? Mine is mhc19j, can this be used for my phone as well? or how to disable the warning for my Nexus 5X?
Click to expand...
Click to collapse
Okay, figured out that this is bootloader version, right? mine says BHZ10m, so I ask again, will this work with my Nexus 5X? (bought today, brand new)
Imgdata tool works flawlessly
The Imgdata Tool mentioned earlier works flawlessly to customize your boot screens: http://forum.xda-developers.com/nex...-change-bootlogo-images-imgdata-tool-t3240052
You need to have a little knowledge of graphics but with Photoshop or Gimp it's just a matter of choosing your image and resizing (or making a text based image, or just a black image that will be a blank screen). Watch the file size as instructed. If you haven't done any advanced image manipulation, it's a great learning opportunity.
This is the Pixel 2 XL's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Cant wait to try it
Toejam1998 said:
Cant wait to try it
Click to expand...
Click to collapse
Tell me if it's work for you
I'll wait for a few others as well
Finally i got a solution for Nexus and Pixel Factory Image flash, now it works perfectly
does this do the critical unlock as well?
razgriz1234 said:
does this do the critical unlock as well?
Click to expand...
Click to collapse
I have integrated "fastboot flashing unlock_critical" for pixel 2 xl only, i have not tested it but it should work
mauronofrio said:
I have integrated "fastboot flashing unlock_critical" for pixel 2 xl only, i have not tested it but it should work
Click to expand...
Click to collapse
ok cool thanks for the quick reply
razgriz1234 said:
ok cool thanks for the quick reply
Click to expand...
Click to collapse
I saw now that i forgot to unlock the flash factory image option for all 4 Pixel, i have released an update to solve that, tell me if it works
This saved my ass last night got bootloop from hell nothing would flash at all run this and boom back in business so like to say thanks for the tool :good:
jaythenut said:
This saved my ass last night got bootloop from hell nothing would flash at all run this and boom back in business so like to say thanks for the tool :good:
Click to expand...
Click to collapse
I'm happy this tool helped you:good:
Do you flash a factory image with this tool?
mauronofrio said:
I'm happy this tool helped you:good:
Do you flash a factory image with this tool?
Click to expand...
Click to collapse
Yes mate
jaythenut said:
Yes mate
Click to expand...
Click to collapse
People like to see feedback and in this thread this is the first
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
almahix said:
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
Click to expand...
Click to collapse
I think way early on it was established we can't have it unencrypted once the OS install it's completed, unless something changed or I got it wrong. Lol
almahix said:
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
Click to expand...
Click to collapse
You can uncrypt your phone but if you.flash a stock rom, the kernel at first boot will automatically encrypt your memory again. There are 2 different encryption, one by code and one with standard image key. At this moment the twrp will automatically uncrypt the system key but you need to manually write the code (if is setted). The tool will uncrypt both method, the flash of stock rom will re-uncrypt with system key but not with code key
mauronofrio said:
You can uncrypt your phone but if you.flash a stock rom, the kernel at first boot will automatically encrypt your memory again. There are 2 different encryption, one by code and one with standard image key. At this moment the twrp will automatically uncrypt the system key but you need to manually write the code (if is setted). The tool will uncrypt both method, the flash of stock rom will re-uncrypt with system key but not with code key
Click to expand...
Click to collapse
Grazie.
Just got my Pixel 2XL the other day and am excited to root and start modding. I have been monitoring this thread just to see what issues people are running into but it looks like not many people are even doing this surprisingly. I mean that's why I bought this Google phone, so I don't have to deal with locked bootloaders that these carriers put in them to discourage rooting. I know this phone is also locked but it's not for the purpose of keeping people from rooting them. I just think that it's so odd that this thread has very little activity.
dricacho said:
I just think that it's so odd that this thread has very little activity.
Click to expand...
Click to collapse
I think it too, but i don't know why.
dricacho said:
Just got my Pixel 2XL the other day and am excited to root and start modding. I have been monitoring this thread just to see what issues people are running into but it looks like not many people are even doing this surprisingly. I mean that's why I bought this Google phone, so I don't have to deal with locked bootloaders that these carriers put in them to discourage rooting. I know this phone is also locked but it's not for the purpose of keeping people from rooting them. I just think that it's so odd that this thread has very little activity.
Click to expand...
Click to collapse
mauronofrio said:
I think it too, but i don't know why.
Click to expand...
Click to collapse
The device is very expensive, has dual partitions, has gotten a lot of bad press, and not near as Dev friendly as some others. Having said that, there are about 5 custom roms, root, exposed, substratum, and various launcher and active edge mods. So it's not like we're hurting too bad ??
Through googling, there are a few tutorial in going through how to get this rooted. But does anyone has any success?
Do I have to apply to unlock the OEM unlocker first through online before getting started?
How To Root Xiaomi Poco F3 with Magisk (No TWRP Required) - NaldoTech
If you like to customize your Xiaomi Poco F3 and have complete control over its firmware, then the first thing you should do is root it. You can root the
www.naldotech.com
https://www.getdroidtips.com/root-poco-f3/
Mahoro.san said:
Do I have to apply to unlock the OEM unlocker first through online before getting started?
Click to expand...
Click to collapse
Yes, your F3 bootloader has to be unlocked. Keep in mind that doing so will NOT void device warranty, but phone contents will be erased. So take a backup of personal or important files before proceeding.
Thank you Leo,
Just started the unlock process and it requires 168hr (7days) of wait time , guess I can still uses my op5 phone for sometime until the wait.
Pretty annoying way of wait but at least its not unattainable.
fastleo63 said:
Yes, your F3 bootloader has to be unlocked. Keep in mind that doing so will NOT void device warranty, but phone contents will be erased. So take a backup of personal or important files before proceeding.
Click to expand...
Click to collapse
Hey. Are you sure it won't void warranty ? E.g.article
Bootloader Unlocking does not Void Warranty of Xiaomi and Redmi Devices - Gizmochina
Xiaomi smartphones are popular in the developer community, thanks to the company’s policy regarding warranty against unlocking of bootloader. But the brand has now updated its policy. Thankfully, bootloader unlocks still does not void warranty of Xiaomi and Redmi devices but with some caveats...
www.gizmochina.com
It says about unlock policy :
... "This policy is applicable to Xiaomi phones in India under both the Mi and Redmi sub-brand. Other regions could possibly have variations to this policy. And before you ask, POCO is excluded from the scope of this article and this policy entirely as it operates as an independent unit and has its own separate policy."
Do you have the source of the information that unlocking POCO from anywhere in the world is officialy not voiding warranty?
I don't know exactly if the above apply in your country.
Here in Italy Xiaomi/POCO said clearly that bootloader unlock and device rooting DOES NOT void warranty.
If further operations will lead to a phone crash/brick, so warranty will be void, and device will be repaired at a cost.
If in doubt, I suggest to ask directly to your local POCO office.
I've got not local poco office jn my country (Poland) . When asked reseller they said - every software modification results in warranty loss. I don't trust their judgment entirely. Anybody know who I may ask about that?
Eventually we all know we relock bootloade, but if they want to they can see if that was the case.
I'm really struggling about unlock + root. I'm not sure if phone has a any defect.
I'll do it for sure in time (I really need V4A). I would have more morales if it was not loosing warranty
osemoka said:
...I really need V4A...
Click to expand...
Click to collapse
Be aware that installing V4A on Android R devices like our F3 isn't as simple as it was with previous versions.
For example, the driver needs Selinux set to permissive to work correctly (a little risky practice).
For the moment I decided to give up, and installed a similar alternative (Wavelet).
Well. On my poco f1 with android q it was problematic but I found workaround not setting Linux to permissive I think. I just had to restart v4a and Spotify often before to make it work ^^. I am desperate to have it. I can't use in-ear headphones without auditory ear protection. They hurt my ears. Wavelet does not have that. Is it a way to achieve the effect? It's a bit off topic already so I will just ask elsewhere...
Mahoro.san said:
Thank you Leo,
Just started the unlock process and it requires 168hr (7days) of wait time , guess I can still uses my op5 phone for sometime until the wait.
Pretty annoying way of wait but at least its not unattainable.
Click to expand...
Click to collapse
Hey mate I'm new on this kind of thing but can you share to me how do you unlock your bootloader?
jfmark0718 said:
Hey mate I'm new on this kind of thing but can you share to me how do you unlock your bootloader?
Click to expand...
Click to collapse
Apply for unlocking Mi devices
en.miui.com
Mahoro.san said:
Do I have to apply to unlock the OEM unlocker first through online before getting started?
Click to expand...
Click to collapse
Yes. Before flashing the patched boot.img you must unlock the bootloader of your F3.
What is this?There is option in dev opt that unlocks bootloader.I never unlocked my old phones by manufacturer.
djuroue1 said:
What is this?There is option in dev opt that unlocks bootloader.I never unlocked my old phones by manufacturer.
Click to expand...
Click to collapse
It does not unlock bootloader, it only allows you to do it in fadtboot if you toggle it. With Xiaomi you need as well their blessing with a code to be able to unlock bootloader as far as I know (no real life experience with Xiaomi yet, still waiting for my F3)
Today I managed to set up Magisk Root without TWRP!
Installation
The Magic Mask for Android
topjohnwu.github.io
"Patching Images"
The first time the F3 was stuck in bootloop so please save the original Boot.img on the PC to flash it via Fastboot if something goes wrong.
Bootloader unlock is mandatory, is only unlocked after 1 week and deletes all data.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does unlocking the bootloader disable the ota rom update ? If that's the case do you have to manually flash the rom through fast boot everytime for updating?
Mahoro.san said:
Does unlocking the bootloader disable the ota rom update ? If that's the case do you have to manually flash the rom through fast boot everytime for updating?
Click to expand...
Click to collapse
Afaik unlocking bootloader does not, rooting does disable ota.
And yes. Only way to flash/update roms is via fastboot untill twrp release.
I found some instructions on how to preserve Magisk root on A/B devices like our F3:
https://topjohnwu.github.io/Magisk/ota.html
I need some advice because the Magisk uninstall process described up there involves original boot.img restoring.
But how can it be possible? The original boot.img is only on my PC, and not on the phone...
Hello, is it possible and how to have magisk after unlocking and flashing a rom with fastboot ?
lejeanlouisF said:
Hello, is it possible and how to have magisk after unlocking and flashing a rom with fastboot ?
Click to expand...
Click to collapse
Yes, it's absolutely possible.
Link: Installation | Magisk
The above operations must be repeated every time you'll flash a new ROM.
I have flashed it but failed safety check .
And can't get the adaway work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Supported Models:
Galaxy S21 FE G990E
Download & Guide:
1. Unlock your bootloader.
2. Download S21 FE: r9s.
3. Reboot to download mode
4. Put the TWRP TAR for your device with Odin in the AP slot, vbmeta_disabled_R.tar in USERDATA slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.- Type: multidisabler again. will see - Finished. when done.- Go back to Wipe > Format Data > type yes.- Reboot to recovery.7. Flash magisk apk in twrp.
8. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree
Changelog:
26.03.2022 - Initial Release.
Hey, glad to see something on development, thanks for that !
I hope someone will work soon on Snapdragon variants
Doghan13 said:
Hey, glad to see something on development, thanks for that !
I hope someone will work soon on Snapdragon variants
Click to expand...
Click to collapse
contact me on telegram @ afaneh92 for testing
@afaneh92 I don't know if I am totally dumb or if Telegram (app version) don't permit to PM somebody who don't appear in contacts, but even in XDA channel, I dont find your name. Mediafire link in XDA forum PM isn't possible and easier ?
Mine is Doghan13 on Telegram and I would be honored to give a try to your TWRP.
Doghan13 said:
@afaneh92 I don't know if I am totally dumb or if Telegram (app version) don't permit to PM somebody who don't appear in contacts, but even in XDA channel, I dont find your name. Mediafire link in XDA forum PM isn't possible and easier ?
Mine is Doghan13 on Telegram and I would be honored to give a try to your TWRP.
Click to expand...
Click to collapse
Wrong name or id.
Just join my telegram group and ask.
Glad to see our beloved S21FE growing
Thanks for the time you spent on this
It was a great necessity for all future developments
Can I install it without wiping data?
I'm coming from galaxy s3 and I feel like I'm a noob in new android world order
mahpooya said:
Glad to see our beloved S21FE growing
Thanks for the time you spent on this
It was a great necessity for all future developments
Can I install it without wiping data?
I'm coming from galaxy s3 and I feel like I'm a noob in new android world order
Click to expand...
Click to collapse
Wipe is mandatory
afaneh92 said:
Wipe is mandatory
Click to expand...
Click to collapse
hello sir. i am looking to unlock my bootloader for at&t variant
please let me know
Ahlebiak1 said:
hello sir. i am looking to unlock my bootloader for at&t variant
please let me know
Click to expand...
Click to collapse
Not supported yet
Anyone tried to flash the SM-G990B with this?
Supported models says only 990E but from a hardware point of view they are exactly the same. I would try it myself but I'm on vacation with a ****ty connection, if it fails downloading stock and re-flashing would take me weeks
Discorly said:
Anyone tried to flash the SM-G990B with this?
Supported models says only 990E but from a hardware point of view they are exactly the same. I would try it myself but I'm on vacation with a ****ty connection, if it fails downloading stock and re-flashing would take me weeks
Click to expand...
Click to collapse
Um... SM-G990B is Snapdragon sir. You should be looking at this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-s21-fe-5g-snapdragon.4439941/
ShaDisNX255 said:
Um... SM-G990B is Snapdragon sir. You should be looking at this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-s21-fe-5g-snapdragon.4439941/
Click to expand...
Click to collapse
What the hell?
I blindly trusted this info: https://www.phonemore.com/specs/samsung/galaxy-s21-fe/sm-g990bds-128gb/ which says exynos
I downloaded cpu-z to make sure and it sure says snapdragon, wtf? I though snapdragon was US/China and this is a brand new swedish phone
Discorly said:
I though snapdragon was US/China and this is a brand new swedish phone
Click to expand...
Click to collapse
Lol I also thought this was the case but apparently not
Discorly said:
I blindly trusted this info: https://www.phonemore.com/specs/samsung/galaxy-s21-fe/sm-g990bds-128gb/ which says exynos
Click to expand...
Click to collapse
I guess that goes to show you that you shouldn't always trust sketchy websites (phonemore) lol. Matter of fact I think most if not all websites contain errors (including gsmarena) so it's always good to keep an open mind.
ShaDisNX255 said:
Lol I also thought this was the case but apparently not
I guess that goes to show you that you shouldn't always trust sketchy websites (phonemore) lol. Matter of fact I think most if not all websites contain errors (including gsmarena) so it's always good to keep an open mind.
Click to expand...
Click to collapse
My mind is blown. Thank you so much, this could've ended in disaster lol
not working bro , odin shows failure
grewal_saurabh said:
not working bro , odin shows failure
Click to expand...
Click to collapse
Post you errors and dont spam the thread asking for frp its not supported by me
the link isnt working
del
Where is Magisk APK?
Now that the entire kernel source is released, is anyone working on building a custom recovery and rom for this device? I was looking at building orange fox recovery for it but I couldn't find how to make it with android 13 decryption support.
gwenmillett said:
Now that the entire kernel source is released, is anyone working on building a custom recovery and rom for this device? I was looking at building orange fox recovery for it but I couldn't find how to make it with android 13 decryption support.
Click to expand...
Click to collapse
You build, I'll try.. I'm decrypted with r/w permissions already. Used dfe neo and RO2RW by leegar, termux method and flashed super.img with fastboot.. Seeing as how we don't have recovery yet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
JWnSC said:
You build, I'll try.. I'm decrypted with r/w permissions already. Used dfe neo and RO2RW by leegar, termux method and flashed super.img with fastboot.. Seeing as how we don't have recovery yetView attachment 5889613
Click to expand...
Click to collapse
May be you can try this https://github.com/BigfootACA/device_nubia_nx729j/releases
vadizzi said:
May be you can try this https://github.com/BigfootACA/device_nubia_nx729j/releases
Click to expand...
Click to collapse
Tried "fastboot boot twrp.img" blackscreen after logo...
Edit: my mistake it worked
i wroted this and it works but very strange. i use fastboot flash recovery ...img; recovery_a ...img and recovery_b ...img. I havent much enthusiasm on twrp so i droped it. You can flash it if worth offcourse
vadizzi said:
i wroted this and it works but very strange. i use fastboot flash recovery ...img; recovery_a ...img and recovery_b ...img. I havent much enthusiasm on twrp so i droped it. You can flash it if worth offcourse
Click to expand...
Click to collapse
Ohh ok. This phone is a little different from my last one op9p..recovery was inside ramdisk..so usually I would boot twrp.img and flash recovery to ramdisk..
I tried fastboot boot twrp.img..it switched to slot b..so I had to set active back to slot a..my mistake
I'll try your method and report back. Thanks!
vadizzi said:
i wroted this and it works but very strange. i use fastboot flash recovery ...img; recovery_a ...img and recovery_b ...img. I havent much enthusiasm on twrp so i droped it. You can flash it if worth offcourse
Click to expand...
Click to collapse
Yeah it worked! Default language is Chinese
It's reading internal storage( decrypted ofc).. Little laggy but usable.. Do you need logs or anything? I'll mess with it a little bit later today.
JWnSC said:
It's reading internal storage( decrypted ofc).. Little laggy but usable.. Do you need logs or anything? I'll mess with it a little bit later today.
Click to expand...
Click to collapse
no i just show it to you. Developer needs i think
vadizzi said:
no i just show it to you. Developer needs i think
Click to expand...
Click to collapse
Thanks! If he post in development section more users can post logs, test, ect ..I didn't even know this existed for our device. Does he have telegram group or something?
JWnSC said:
Thanks! If he post in development section more users can post logs, test, ect ..I didn't even know this existed for our device. Does he have telegram group or something?
Click to expand...
Click to collapse
I've just been browsing github and don't know any information
JWnSC said:
It's reading internal storage( decrypted ofc).. Little laggy but usable.. Do you need logs or anything? I'll mess with it a little bit later today.
Click to expand...
Click to collapse
Hello. Installed your TWRP, but the internal memory is not displayed and there is no active OTG. Did you do something wrong ?
batargin said:
Hello. Installed your TWRP, but the internal memory is not displayed and there is no active OTG. Did you do something wrong ?
Click to expand...
Click to collapse
This isn't my twrp.. I'm already decrypted, so I just test it. I could read internal storage on mine. Your probably still encrypted, so it wouldn't work for you.
JWnSC said:
This isn't my twrp.. I'm already decrypted, so I just test it. I could read internal storage on mine. Your probably still encrypted, so it wouldn't work for you.
Click to expand...
Click to collapse
I realized that you are testing, and I just have no one to turn to for help but you. How can I decrypt it? I just got the device today.
6.49 GB file on MEGA
mega.nz
MIUI 14 Rom you can try it we need some help to install.
ibestmoder said:
6.49 GB file on MEGA
mega.nz
MIUI 14 Rom you can try it we need some help to install.
Click to expand...
Click to collapse
Extract the file to a directory then put your phone in bootloader, connect your phone then go to the directory you extract and click on 8pro****.bat (*** for some chinese character). Your phone will then boot after it is done. However this is not a free rom you can run it for 30 minutes and you will have hard time to get back to stock rom since this rom modify the stock rom partitions.
[email protected] said:
Extract the file to a directory then put your phone in bootloader, connect your phone the go to the directory you extract and click on 8pro****.bat (*** for some chinese character). Your phone will then boot after it is done. However this is not a free rom you can run it for 30 minutes and you will have hard time to get back to stock rom since this rom modify the stock rom partitios.
Click to expand...
Click to collapse
I going to buy it from the maker he going do some changing to English with full support
Have someone tried that miui 14 rom? Are there any screenshots or something about what happens after 30 minutes? Might be possible to just remove that restrictions, but unless there's an easy way to revert back to stock (EDL or something), don't think it makes sense to flash it. Better wait for someone to build a proper CAF/CLO ROM (i.e. Paranoid Android)
aaa.bbb111222 said:
Have someone tried that miui 14 rom? Are there any screenshots or something about what happens after 30 minutes? Might be possible to just remove that restrictions, but unless there's an easy way to revert back to stock (EDL or something), don't think it makes sense to flash it. Better wait for someone to build a proper CAF/CLO ROM (i.e. Paranoid Android)
Click to expand...
Click to collapse
Rom is from chinese dev made out chinese 2.26. you need to pay 4 dollars to unlock it. I im Private with hem going to fix the rom for us
ibestmoder said:
Rom is from chinese dev made out chinese 2.26. you need to pay 4 dollars to unlock it. I im Private with hem going to fix the rom for us
Click to expand...
Click to collapse
It's MIUI, there's nothing that could fix that
That's not the point tho. Gonna assume no one yet tried flashing it (so the potential drawbacks not including 30 minutes lifetime are unknown. Should be always possible to remove that from ROM anyway). And we still don't have any way to unbrick, ZTE doesn't want to give us the flash tool for bs reasons.