Related
Hello y'all,
I've noticed that on the Pixel 2 and on many other A/B devices, there is a twrp zip available that can be flashed after flashing the twrp image to boot and booting into recovery and flashing the stock boot image (like we do on the Essential) which patches the ramdisk in the stock boot.img to add twrp to it so that twrp can be permanently installed on the device.
If I could make something like this myself, I would have a long time ago, but unfortunately, it's over my head. Just curious why something like this has never been made for the Essential. Also, but much less important, TWRP 3.2.3-0 is about to be released (code is on GitHub), yet the latest available to us is version 3.2.1-1.
I know one of you smart devs could make the zip to install twrp to the ramdisk (and possibly build the latest version of twrp also) probably in almost no time at all. I love my Essential, but having to connect it to a PC just to get into TWRP is very irritating.
When one of you guys have the time, could you give it a try? I'd be happy to test whatever you come up with.
Much thanks!
starcms said:
Hello y'all,
I've noticed that on the Pixel 2 and on many other A/B devices, there is a twrp zip available that can be flashed after flashing the twrp image to boot and booting into recovery and flashing the stock boot image (like we do on the Essential) which patches the ramdisk in the stock boot.img to add twrp to it so that twrp can be permanently installed on the device.
If I could make something like this myself, I would have a long time ago, but unfortunately, it's over my head. Just curious why something like this has never been made for the Essential. Also, but much less important, TWRP 3.2.3-0 is about to be released (code is on GitHub), yet the latest available to us is version 3.2.1-1.
I know one of you smart devs could make the zip to install twrp to the ramdisk (and possibly build the latest version of twrp also) probably in almost no time at all. I love my Essential, but having to connect it to a PC just to get into TWRP is very irritating.
When one of you guys have the time, could you give it a try? I'd be happy to test whatever you come up with.
Much thanks!
Click to expand...
Click to collapse
It's definitely possible but I don't know how many Devs would want to take this up. I'm all for the idea, I really miss having TWRP permanently, but you kinda get used to the whole PC flashing thang.
I don't know how different the Pixel 2 is in comparison to the Essential phone, but they both share A/B partitions, so it wouldn't be too outlandish if someone were able to port something like this over to our Mata's down the road.
?
starcms said:
Hello y'all,
I've noticed that on the Pixel 2 and on many other A/B devices, there is a twrp zip available that can be flashed after flashing the twrp image to boot and booting into recovery and flashing the stock boot image (like we do on the Essential) which patches the ramdisk in the stock boot.img to add twrp to it so that twrp can be permanently installed on the device.
If I could make something like this myself, I would have a long time ago, but unfortunately, it's over my head. Just curious why something like this has never been made for the Essential. Also, but much less important, TWRP 3.2.3-0 is about to be released (code is on GitHub), yet the latest available to us is version 3.2.1-1.
I know one of you smart devs could make the zip to install twrp to the ramdisk (and possibly build the latest version of twrp also) probably in almost no time at all. I love my Essential, but having to connect it to a PC just to get into TWRP is very irritating.
When one of you guys have the time, could you give it a try? I'd be happy to test whatever you come up with.
Much thanks!
Click to expand...
Click to collapse
MoistPicklez said:
It's definitely possible but I don't know how many Devs would want to take this up. I'm all for the idea, I really miss having TWRP permanently, but you kinda get used to the whole PC flashing thang.
I don't know how different the Pixel 2 is in comparison to the Essential phone, but they both share A/B partitions, so it wouldn't be too outlandish if someone were able to port something like this over to our Mata's down the road.
?
Click to expand...
Click to collapse
The problem lies in the way our touch driver is implemented. For lack of a better explanation, what good would it do to need to carry a type c mouse around to use twrp if touch doesn't work. Many many people have tried and failed getting touch to work on Oreo source, let alone P. That is why twrp resides on a nougat kernel meant for LOS. Someone I know even rewrote the driver in c, no go. It's gonna be tough sledding.
Does it have to be touch though? Could it be more old school clockworkmod recovery where you use the buttons or really like default recovery. I don't know enough about it but just a thought. You definitely get use to just downloading and flashing in twrp and it would be cool to find that with the PH-1.
Atleaset there is a way to use TWRP on the fly.
1) Root the phone the first time using the PC.
2) Copy the TWRP and boot.img(rooted) files to the Phone.
3) While booted and rooted, use apps like Rashr - Flash Tool or Flashify available on the playstore to flash TWRP and boot to it.
4) Once you are done using TWRP, flash the boot.img and boot to the phone.
Gundabolu SC said:
Atleaset there is a way to use TWRP on the fly.
1) Root the phone the first time using the PC.
2) Copy the TWRP and boot.img(rooted) files to the Phone.
3) While booted and rooted, use apps like Rashr - Flash Tool or Flashify available on the playstore to flash TWRP and boot to it.
4) Once you are done using TWRP, flash the boot.img and boot to the phone.
Click to expand...
Click to collapse
Been waiting for someone to share this for 6 months.. thanks lol
aer0zer0 said:
The problem lies in the way our touch driver is implemented. For lack of a better explanation, what good would it do to need to carry a type c mouse around to use twrp if touch doesn't work. Many many people have tried and failed getting touch to work on Oreo source, let alone P. That is why twrp resides on a nougat kernel meant for LOS. Someone I know even rewrote the driver in c, no go. It's gonna be tough sledding.
Click to expand...
Click to collapse
Thanks for the explanation. Now I understand why it hasn't been done before.
But why the issue with touch in TWRP with an Oreo kernel in the first place? What's so special/different/difficult about the touch driver that the Essential uses? And why does it work fine with TWRP with a Nougat kernel? No other devices (to my knowledge) have this issue.
Edit: I wonder if since TWRP worked with the touch driver from the Nougat kernel, if it could work with the P kernel? Maybe whatever was changed in Oreo that prevented it from working has been fixed?
starcms said:
Thanks for the explanation. Now I understand why it hasn't been done before.
But why the issue with touch in TWRP with an Oreo kernel in the first place? What's so special/different/difficult about the touch driver that the Essential uses? And why does it work fine with TWRP with a Nougat kernel? No other devices (to my knowledge) have this issue.
Click to expand...
Click to collapse
Hbtp_daemon (touchscreen) doesn't work in twrp on 8.x and newer sources.
Hbtp_daemon runs in userspace iirc, which is the problem. So an entire driver needs to be hogged together in order to get twrp to work. same process that worked on N doesn't work now.
aer0zer0 said:
Hbtp_daemon (touchscreen) doesn't work in twrp on 8.x and newer sources.
Hbtp_daemon runs in userspace iirc, which is the problem. So an entire driver needs to be hogged together in order to get twrp to work. same process that worked on N doesn't work now.
Click to expand...
Click to collapse
Not possible to use the driver in userspace after TWRP decrypts the device (userspace) using the default password (after any patterns or pins are removed from the lockscreen)?
Edit: And what the heck is the driver doing in userspace anyway? Shouldn't it be in /vendor? If the driver is in userspace, then how can the touchscreen work after a factory reset?
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
galakanokis said:
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
Click to expand...
Click to collapse
It doesn't after you lets say flash magisk and gapps they create a script in /system/addon....and when updatting lineage it runs the scripts in the addon folder which is how gapps and magisk get installed to the new updated system and boot.....first magisk and gapps have to be flashed in twrp....after that u shudnt need it on dirty flashes
galakanokis said:
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
Click to expand...
Click to collapse
@aer0zer0
This seems like the easiest solution to getting TWRP working on the Oreo and P boot images and being able to keep it permanently installed in ramdisk. Make TWRP use the volume up/down keys for scrolling and the power key to select. If the touchscreen is soooo difficult to get working, forget it. If someone really wants to use the touchscreen, they can use the existing TWRP version built on the Nougat boot image.
galakanokis said:
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
Click to expand...
Click to collapse
What can you do in Lineage recovery if you can't flash zips? Can you make backups? What else can you do? If you have it installed, could you attach a pic (assuming you have another phone/camera)?
Has anyone looked in the stock P kernel? I was poking around and noticed some twrp residual files. This was straight from the images zip from essential. I didn't touch it.Wth are they in there for? Could they have a better twrp on the back burner for kernel development purposes for Essential? It was in the ramdisk, ill look again tomorrow when I unpack the boot.img. it would make sense to have it in ramdisk, pixel 2 has it like that. Ill post screenshots after work. But, the conversation looks good folks, you are on to something. We could always bust out some phillz recovery, or clockwork mod.
starcms said:
What can you do in Lineage recovery if you can't flash zips? Can you make backups? What else can you do? If you have it installed, could you attach a pic (assuming you have another phone/camera)?
Click to expand...
Click to collapse
I would say it is more stock-ish as far as recoverys go. It's a stock LOS recovery. You can factory reset, flash or sideload update.zips or signed zips no regular custom ROM zips or magisk. It is meant to run on LOS, it only runs on LOS actually and not made for the flashaholics out there. It's a good start though.
Sorry, out right now and no other phone/camera handy.
Gundabolu SC said:
Atleaset there is a way to use TWRP on the fly.
1) Root the phone the first time using the PC.
2) Copy the TWRP and boot.img(rooted) files to the Phone.
3) While booted and rooted, use apps like Rashr - Flash Tool or Flashify available on the playstore to flash TWRP and boot to it.
4) Once you are done using TWRP, flash the boot.img and boot to the phone.
Click to expand...
Click to collapse
Just wanted to mention this works perfectly, tried it last night was able to get into TWRP and then back into my P Beta 3 with root, no issues. Thanks for this!
One could also theoretically copy a copy of the twrp boot. Img to the ex kernel manager backup file, and while booted into the system, hit restore kernel and since its in the boot partition it will flash it then reboot into recovery. Then from there flash your normal kernel and boot back to system/android.. i backup all my kernels after rooting them so after flashing otas, i can just flash my prerooted kernel and reboot without having to flash magisk
Edit. This works, i just did it, but u must make it reboot to bootloader to then tell it to reboot recovery. I dont know if flashify is the same
MoistPicklez said:
Just wanted to mention this works perfectly, tried it last night was able to get into TWRP and then back into my P Beta 3 with root, no issues. Thanks for this!
Click to expand...
Click to collapse
Hey, I'm just curious, before I try it, anyway when using flashify and selecting flash zip - does a recovery other than stock need to be present?
dirtyreturn said:
Hey, I'm just curious, before I try it, anyway when using flashify and selecting flash zip - does a recovery other than stock need to be present?
Click to expand...
Click to collapse
Not sure what you mean by that but to be honest all I did was take the TWRP11.img, and flashed it to boot (kernel) using Rashr, Flashify didn't load up oddly, then reboot to bootloader, select Recovery and bam, there was TWRP. Then to get back I just flashed my boot.img, and Magisk and all my modules and everything were all good to go. No issues at all. ?
Edit: as long as you have TWRP.img, your boot.img, and Magisk, you can easily get to TWRP and back, just make sure you have the img's you need and boom we all got TWRP on the fly.
Wish I had tried this sooner.
MoistPicklez said:
Not sure what you mean by that but to be honest all I did was take the TWRP11.img, and flashed it to boot (kernel) using Rashr, Flashify didn't load up oddly, then reboot to bootloader, select Recovery and bam, there was TWRP. Then to get back I just flashed my boot.img, and Magisk and all my modules and everything were all good to go. No issues at all. ?
Edit: as long as you have TWRP.img, your boot.img, and Magisk, you can easily get to TWRP and back, just make sure you have the img's you need and boom we all got TWRP on the fly.
Wish I had tried this sooner.
Click to expand...
Click to collapse
Hey, Rashr doesn't support this device(phone). I get a reboot to recovery option and if I tap cancel the app just closes. Did the app identify what it needed to?
In Flashify there are 3 options ,Flash - kernel,boot, and zip. What I'm curious about is , when choosing just the zip option - would twrp first need to be flashed to the boot partition?
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:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you 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 us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption works
- Otg works
- Flash Rom works
- F2FS support
- Fastboot boot command support
Not working:
- Fastbootd
- Adb sideload
- Backup restore and image flash (system-vendor-product)
- Android 11 fully support
Download:
TWRP 3.4.0-14 Unofficial by mauronofrio
TWRP 3.4.0-13 Unofficial by mauronofrio
To Flash the TWRP:
Code:
fastboot flash recovery twrp-3.3.1-xx-xxxxxx-mauronofrio.img
Then reboot in TWRP manually or using a fastboot command.
Code:
fastboot boot twrp-3.3.1-xx-xxxxxx-mauronofrio.img
or
Code:
fastboot oem reboot-recovery
REMEMBER: is important that from fastboot you directly go in TWRP mode or the TWRP will be overwritten.
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/Teamwin/android_bootable_recovery
https://github.com/mauronofrio/android_device_xiaomi_toco
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
- Thanks to @bigbiff and @Captain_Throwback for the hard work on this android 10 TWRP
Thanks to all testers on the Telegram Group
Created 2020-05-29
Oooo finally... Gonna test this out when I get home later.
Just to check, what happens if i flash and i get bootloop? How do I recover? By flashing the entire MIUI rom from official site?
Okay Im sure im being a noob... But err...
I wasnt able to mount data...
I tried to mount and install MAGISK via USB-OTG mounting and i get permission denied for system and vendor (and also Data unable to mount)
EDIT2: Oh cool... despite the errors Magisk got installed! Nice!
Hello, will there be more development for this terminal? and the note 10 lite thread? Thank you
Did anyone boot it?
hello, work boot it?
fastboot boot twrp.XXXX.img
StanGumn said:
hello, work boot it?
fastboot boot twrp.XXXX.img
Click to expand...
Click to collapse
Yes
iron maiden said:
Hello, will there be more development for this terminal? and the note 10 lite thread? Thank you
Click to expand...
Click to collapse
Let us hope so.
I would like to apologize in advance as I am a noob when it comes to the recent changes made by Google to android. So on a lot of the recent devices launched with android 10, an essential step before flashing Magisk is to disable the vbmeta partition by flashing the "vbmeta.img" using a fastboot command with the --disable-verify and --disable-verification argument. My question is that is the "vbmeta.img" modified by developers or is this the same identical file found in the stock firmware files?
I do apologize if this is the wrong thread but there's not many resources online or even on xda for this device.
Why its in mi note 10 general section? Isnt right to do separately section for mi note 10 lite since there is nothing in common just name.
Reanimax said:
Why its in mi note 10 general section? Isnt right to do separately section for mi note 10 lite since there is nothing in common just name.
Click to expand...
Click to collapse
ask to xda to make a dedicated section and i will ask to move this thread
mauronofrio said:
ask to xda to make a dedicated section and i will ask to move this thread
Click to expand...
Click to collapse
Yes. You right about it.
Kediraksith said:
Oooo finally... Gonna test this out when I get home later.
Just to check, what happens if i flash and i get bootloop? How do I recover? By flashing the entire MIUI rom from official site?
Okay Im sure im being a noob... But err...
I wasnt able to mount data...
I tried to mount and install MAGISK via USB-OTG mounting and i get permission denied for system and vendor (and also Data unable to mount)
EDIT2: Oh cool... despite the errors Magisk got installed! Nice!
Click to expand...
Click to collapse
Nowadays you have to unmount Data and mount vendor (just in case for Vendor) before flashing Magisk. Mounting data does not let Magisk install via TWRP. Follow the this process, same install process with the Mi Note 10, and assuming the Mi note 10 Lite. The reason why is because of encryption.
Update: 5/16/2020
1) Flash lastest TWRP unofficial 3.31-4 mauronofrio using Command prompt using the - fastboot flash recovery [XXXX].img. Note: it's easier to just rename the recover image to "twrp"
2) Then - fastboot boot [XXXX].img to reboot into TWRP recovery.
3) In my experience for thr Mi Note 10 that is, the reboot to RECOVERY did not happened, so instead i pressed - volume up and power button at the same time for thr phone to reboot until you see the boot splash screen, hold the two buttons for another 3 seconds ... and then let go of power button and then TWRP recovery will show up.
4) Ok...so first things first... flash the VBMETA PATCHER like the OP says on first page --> that way you don't lose TWRP after flashing the Rom and MAGISK. After install, reboot to RECOVERY. ***This is only if OP asks to flash VBMETA PATCHER, otherwise skip to Step 5***
5) Now....go to FORMAT DATA (Warning: DON'T use advanced wipe)... Instead, go to the FORMAT DATA, type in yes and press ok. Then go back to main menu, and reboot to RECOVERY again.
6) Now you can access your internel memory when connecting to USB... You can import the two neccesary files --> Xiaomi.EU and MAGISK 20.4. Now Flash the Rom and when flash MAGISK, make sure you unmount DATA and mount VENDOR to avoid flash error. After unticking DATA, you can now install Magisk.
7) Now you can go to REBOOT, and press SYSTEM, and the phone will boot to Xiaomi EU 11 or 12, etc. just follow this process and enjoy your ROM. ?
Note: When updating, flash EU rom and Magisk, dont forget to unmount Data when flashing Magisk. You can probably disable decryption because that is why you can't mount Data when flashing Magisk. **Just don't ask me about it because I normally don't flash Disable Decyption often.
Wmateria said:
Nowadays you have to unmount Data and mount vendor (just in case for Vendor) before flashing Magisk. Mounting data does not let Magisk install via TWRP. Follow the this process, same install process with the Mi Note 10, and assuming the Mi note 10 Lite. The reason why is because of encryption.
1) Flash lastest TWRP unofficial 3.31-4 mauronofrio using Command prompt using the - fastboot flash recovery [XXXX].img. Note: it's easier to just rename the recover image to "twrp"
2) Then - fastboot boot [XXXX].img to reboot into TWRP recovery.
3) In my experience for thr Mi Note 10 that is, the reboot to RECOVERY did not happened, so instead i pressed - volume up and power button at the same time for thr phone to reboot until you see the boot splash screen, hold the two buttons for another 3 seconds ... and then let go of power button and then TWRP recovery will show up.
4) Ok...so first things first... flash the VBMETA PATCHER like the OP says on first page --> that way you don't lose TWRP after flashing the Rom and MAGISK. After install, reboot to RECOVERY.
5) Now....go to FORMAT DATA (Warning: DON'T use advanced wipe)... Instead, go to the FORMAT DATA, type in yes and press ok. Then go back to main menu, and reboot to RECOVERY again.
6) Now you can access your internel memory when connecting to USB... You can import the two neccesary files --> Xiaomi.EU and MAGISK 20.4. Now Flash the Rom and when flash MAGISK, make sure you unmount DATA and mount VENDOR to avoid flash error. After unticking DATA, you can now install Magisk.
7) Now you can go to REBOOT, and press SYSTEM, and the phone will boot to Xiaomi EU 11 or 12, etc. just follow this process and enjoy your ROM.
Note: When updating, flash EU rom and Magisk, dont forget to unmount Data when flashing Magisk. You can probably disable decryption because that is why you can't mount Data when flashing Magisk. **Just don't ask me about it because I normally don't flash Disable Decyption often.
Click to expand...
Click to collapse
this post is gold! Coming back to xiaomi and twrp after 2 years with a huawei, hope to go smooth again with root magisk etc!
cerme said:
this post is gold! Coming back to xiaomi and twrp after 2 years with a huawei, hope to go smooth again with root magisk etc!
Click to expand...
Click to collapse
The root and flash process is basically the same process as the Mi 9T/K20, Mi Max 3, Mi Note 10 since decryption is now a common thing with Android 10... except for the VBmeta.zip, which is new and necessary to flash, as long as you follow the directions..you'll be fine.
Wmateria said:
The root and flash process is basically basically the same process as the Mi 9T/K20, Mi Max 3, Mi Note 10 since decryption is now a common thing with Android 10... except for the VBmeta.zip, which is new and necessary to flash, as long as you follow the directions..you'll be fine.
Click to expand...
Click to collapse
I understand. Last experience ti flash etc was on a mi5, so I have a little bit of rust with that. I do think that following instructions i shouldn't face major difficulties
cerme said:
I understand. Last experience ti flash etc was on a mi5, so I have a little bit of rust with that. I do think that following instructions i shouldn't face major difficulties
Click to expand...
Click to collapse
Same here, i was on the Mi 9T before, I didnt understood the whole new flashing process and carefully updating from EU Rom to AOSP Roms and back, I think i was messing with with thwe wipe and change partition feature (f2fs to ext 4 with an EU Rom) - then the Mi 9T bricked big time. Never recovered after that, luckily got it refunded for it but not many may have that second chance. After learning how to flash propeely and root, ect. I try to help out here when needed and ask too. I just got my Mi Note 10 2 weeks ago and rooted a week ago. So if anything, am willing to help out and repeat the following flash process or any changes in the future and feedback on future Roms.
Was thinking about which rom to use... does xiaomi.eu is stille faster with providing updates? what about the situation with OTA with that.
Now I have the phone with global rom, I want at least flash the EEA rom. But I also know that at some point i want to root, install magisk and get nice features. Still don't want to update manually everytime for an update...
will be watching this thread with much interest..
I recently bought this device (Global version) for use here in Australia.
my first time owning a Xiaomi - quite happy with it so far.
would be nice to have the themeing stuff work properly - I have used MIUI based ROMs back a LOoonggg time ago, in the days of the Nexus S and Galaxy Nexus etc.
used to have a new ROM flashed every couple of days lol, back then. But recent years I've stopped all that, no cool ROMs no snazzy kernels TWRP no nothing not even root lol, very boring!
anyway thanks for posting I hope to try this sometime soon
Hello is there any Eu rom for Mi note 10 lite?
Alisiddiqui75 said:
Hello is there any Eu rom for Mi note 10 lite?
Click to expand...
Click to collapse
yes, there is the EEA ROM you can find on miui website. You can flash it after unlocking bootloader with miFlash
Alisiddiqui75 said:
Hello is there any Eu rom for Mi note 10 lite?
Click to expand...
Click to collapse
I'm not sure if you mean the official ROM or xiaomi.eu.
The link to the official EEA(EU) ROM:
Recovery: https://bigota.d.miui.com/V11.0.7.0.QFNEUXM/miui_TOCOEEAGlobal_V11.0.7.0.QFNEUXM_7926bf9c02_10.0.zip
Fastboot: https://bigota.d.miui.com/V11.0.7.0...EUXM_20200508.0000.00_10.0_eea_4eb1c694c9.tgz
I have yesterday seen a xiaomi.eu Stable build for toco which is based on Global Stable ROM:
https://sourceforge.net/projects/xi...e10LITE_V11.0.4.0.QFNMIXM_v11-10.zip/download
I can not promise that it's working.
Hi
I fixed my oneplus 5 using MSMdownload tool. It put my phone on Android 7.1.1 with July 1st, 2017 security Patch and Oxygen OS 4.5.8, I have exhausted all the option to upgrade it to latest Android but it won't update. Every time I check for update it will show that it is up to date. I have also tried "local Upgrade" option but it shows installation failed.
Any work around this would be highly appreciated
Thanks
Aman
@lucider14 Just curious why you used the MSMDownloadTool from OxygenOS 4.5.8 and not the one for OxygenOS 9.0.11? You most likely won't see OTAs for Android 7 as it is now 4 Android Versions behind as of this week. Android 9.0.11 was the last official fully released OTA, OxygenOS 10.0.0 Hotfix is last official OTA OnePlus has released into the wild.
My phone waa bricked so had to use it. Please let me know if there is any workaround for this to update.
@lucider14 The workarounds I would try are:
Opt 1: Upgrade via zip file in Stock Recovery
Step 1: Download latest OTA from https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Step 2: Copy zip file to root of Phone storage
Step 3: Reboot into Recovery
Step 4: Install
Opt 2: Use Newer MSMDownloadTool:
Step 1: Download newest tool from here https://forum.xda-developers.com/oneplus-5/how-to/op5-collection-unbrick-tools-t3898870
Step 2: Reboot phone into EDL
Step 3: Run newer MSMDownloadTool
card13;83478941 [user=11104643 said:
@lucider14[/user] The workarounds I would try are:
Opt 1: Upgrade via zip file in Stock Recovery
Step 1: Download latest OTA from https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Step 2: Copy zip file to root of Phone storage
Step 3: Reboot into Recovery
Step 4: Install
Opt 2: Use Newer MSMDownloadTool:
Step 1: Download newest tool from here https://forum.xda-developers.com/oneplus-5/how-to/op5-collection-unbrick-tools-t3898870
Step 2: Reboot phone into EDL
Step 3: Run newer MSMDownloadTool
Click to expand...
Click to collapse
@lucider14 OOS 4.5.8 is pre-treble. You can't jump directly to Android 9 or 10. One of the OOS updates before Android 9 set up treble on our phones. I don remember exactly which one. You're best to use Opt 2 above, it will be easier.
Cheers!?
lucider14 said:
Hi
I fixed my oneplus 5 using MSMdownload tool. It put my phone on Android 7.1.1 with July 1st, 2017 security Patch and Oxygen OS 4.5.8, I have exhausted all the option to upgrade it to latest Android but it won't update. Every time I check for update it will show that it is up to date. I have also tried "local Upgrade" option but it shows installation failed.
Any work around this would be highly appreciated
Thanks
Aman
Click to expand...
Click to collapse
First,flash it 9.0.11 build and then OxygenOS 10.0.0 Hotfix..
And with https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
I've had a similar problem and I thought I broke my phone, got pretty scared can't buy a new phone but need a newer android for my apps to work.
I came from freedom OS on android 7 so I never had the project treble on my phone and tried to flash new factory images, as a result, no newer TWRP recovery worked and I was unable to boot into anything other than the bootloader. I had the same error with Error 7, from what I can understand this is from a screwed up or non-existing "vendor" partition which says stuff like "this is a OnePlus 5" for newer factory images to install (factory image told me I didn't have a OP5), this never existed in android 7 or OOS 4.X.X. ScRuFFy7 is correct, the vender partition was created in OOS 5.1.4 (or OTA 037) and only when android is booting up, this took like 10 mins on mine. Once this vendor partition is correctly created you can flash newer TWRP recovery (I flashed 3.4.0) and newer factory images, like OOS 9.0.11 then to version 10. The built-in updater and stock recovery can update to the newer versions with the flashable zip files. For whatever reason OnePlus don't size the partitions in their zips so they make small changes from one version to the next so skipping specfic versions throws up errors in the future.
Screw it, I should document what I did in case I mess up my phone in the future and maybe be helpful to someone else in need, especially in this messed up and depressing time of the plague. But anyway this is what I did to get my phone back, I should point out I have no idea what I'm doing. Meaning I'm a N00b.
NOTE: this process Wipes all the data from the phone, so I hope you have backups right now.
Will need ADB, you can install This on windows, it's super easy and works thanks to mauronofrio. You can get the all in one tool too from here it's pretty handy and can format and decrypt from the bootloader, from mauronofrio? I think? This guy is pretty good. I got all old firmware from Here thanks to Some_Random_Username for the life line since OnePlus won't provide the old Zips anymore.
1) Boot to TWRP recovery if you have it installed (VOL DOWN + POWER). If not Boot to Bootloader (VOL UP + POWER) and flash TWRP Recovery. You can use TWRP 3.1.1 This one works on OOS 4.X firmware without giving me a Black Screen.
1a) To Flash the Recovery you can use the all in one tool to flash it or open up command prompt and use the Fastboot Flash [insert recovery file name here .img] command to flash it, you can find the FastBoot Flashing Method in the middle of this page for instructions.
2) Format Data. The Format Data button in TWRP recovery not the swipe to factory reset, because we're going back to scratch.
3) Flash OTA_006 (OOS 4.5.2) original firmware from the link above (says ota_006 in the middle of the loong file name)
4) Boot into android and use System Update in settings and stock recovery it just flashed to flash OTA_020 (OOS 4.5.15) by clicking on the cogwheel in the corner and choosing Local Update. [probably skippable I just wanted to make sure it works]
5) Boot into android again and install OTA_27 (OOS 5.0) with System Update again.
6) If it doesn't boot, go to Bootloader and flash TWRP. Once in the recovery and you go to install and if you find all the folders have random numbers and letters for names then the storage in encrypted.
7) Format to get rid of encryption (random name folders) then reboot to Recovery and Flash OTA_27 again and let it start fresh on OOS 5.0 to make sure it's still booting and working.
8) Once booted Flash OTA_037 (OOS 5.1.4) wait for vendor partition to be created (took 10 mins on my OP5), reboot to TWRP and format if folders are encrypted and reflash OTA_037 if needed.
Once booted into android this is the point where you should have the Vendor Partition already created by the factory image, you can go back into TWRP (flash TWRP if needed) and under Mount be able to see, mount/unmount a Vendor partition without errors. This should solve the Error 7 problem with factory images. A newer version of TWRP Recovery should work now, I installed 3.4.0 from mauronofrio Here. 3.4.0 works with android 10.0 so I was glad.
9) Boot android again and flash OTA_038 (OOS 5.1.5) just to make sure with stock recovery. [Probably skippable but I was a Paranoid Android at this point, just to make sure it still works]
10) Boot to android again and install OTA_042 (OOS 9.0.0) with System Update to keep making sure it works. [Again, I was Paranoid. Probably Skippable]
11) Boot to android again and install OTA_054 (OOS9.0.11) as last Android 9 update to have things set up ok.
12) Boot into Android again and install the latest android 10 from OnePlus (OTA_068) with System Update and the Stock Recovery, this is Android 10.0.0 and OOS 10.0.0. Things should work fine at this point but I doubt the check for update will get new oneplus updates. As of Sep 25, 2020 it is up to date. Technically.
I should add something else I discovered after. I found a flashable zip file from one of the lineage OS posts of a oneplus5_vendor_5.1.5.zip Here. You might be able to just use that to create the Vendor partition then just Flash one of the OOS 5.X Firmwares and go from there, I've not tried it so I'm not 100% sure but it's a possibility?
Hope this is helpful to someone at some point in time. for troubleshooting at least. Honestly really glad I have a working phone right now.
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
What is the reason for installing TWRP, I rooted it but if I restart the smartphone, TWRP and Root are lost, deleted and the main menu recovery of redmi note 7 MIUI 12.5.3 returns
how to solve it?
It helps to ask your question in the proper section. Please search before posting.
Xiaomi Redmi Note 7
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
Which method did you use and did it follow the instructions?
ze7zez said:
Xiaomi Redmi Note 7
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
Which method did you use and did it follow the instructions?
Click to expand...
Click to collapse
minimal abd fastboot and smartphone in fastboot I downloaded the latest version of TWRP for Redmi Note 7
my PC recognized the smartphone normally I activated USB debugging and file transfer on the redmi note 7
installed normally but I only used it while not restarting the smartphone
Hello.
I need help, please.
I have a Redmi Note 7 and I tried to install android 13 on it using TWRP, however, I made a mistake and using TWRP I ended up formatting the entire smartphone. I can no longer use Mi-Recovery 3.0 or enter TWRP, because when I click volume up and power nothing happens and the cell phone just starts because I managed to install its original android using Mi flash.
How can I restore or install recovery mode with mi-recovery 3.0 and thus be able to install the newest versions of android?
I also wanted to know if I can install android 13 or others that were not official for my device without TWRP, mi-recovery mode, or another that depends on the commands described above, which are not working.
Thanks for the help.