Related
TWRP3.2.30-Universal version uploaded
https://drive.google.com/open?id=16BueY8230PzL-5ngkMiNZGxpIYBoK4EL
TWRP3.2.20-Universal version uploaded
https://drive.google.com/open?id=1Qr35EfIy76c6lkQZaKBzRS_PuBhUfjMX
TWRP3.2.10-Universal version uploaded
Rebased on TWRP3.2.1-0
https://drive.google.com/open?id=1Tcc5pk-7MOz5IRwqgH-zfKj-t7pnSMi5
TWRP3.2.0-0-Universal version uploaded
Changelog:
Backup / Restore every possible partition
Supports both Android 5.x and 6.0+ partitioning schemes
Oreo ready..........
https://drive.google.com/open?id=1uJAc84Qgw4k1NW3W3BjcVtwc37y--xz8
TWRP3.1.1-0-Universal version uploaded
Changelog:
Uses 7.5.11 Android 5.02 kernel
Backup / Restore every possible partition
Supports both Android 5.x and 6.0+ partitioning schemes
https://drive.google.com/open?id=0BwdRTuyj12_yVWZqUnd6MEN0QVk
Note: This version saves to a folder named as the serial number of the device which is different to the previous version. Old backups will not work unless they are copied into the new folder.
TWRP3.0.2-2 has had a makeover also:
Rebased on 7.3.16 Kernel
Removed F2FS support to prevent "mishaps"
Added ability to backup & restore Preloader partition
https://drive.google.com/open?id=0BwdRTuyj12_yU19qQWNra1o3alk
Hi, great work. Can you make twrp 3.0 for our beloved xrmn2? It's has been released: http://www.xda-developers.com/twrp-3-0-0-has-arrived/
If you don't like the extensive partition listings in the original, I have altered the fstab files and repacked so you see only the necessary partitions for each function. Other than that, it is the same.
Now only one version with all the partitions you need and none that will get you into trouble
Thank you for sharing!
jajk said:
TWRP3.0 is here. All credit to Jeminni.
Unpacked, examined and tested to be fully functional and free from malware by me. This is totally unaltered - just mirrored here for convenience.
Click to expand...
Click to collapse
Hi, great work...thanks alot, just keep peaking !
Can we get informed by you what kind of malware plant in this, does it method by flashing any zip using it or by restore/backup process?
Anyway, u're whispering somethin' th
at we cant wait ur MM builds desperately...
@Adam Hui Maybe you misunderstood, I checked that there is no malware in the original by unpacking it and looking at the code. I also tested every function does not break the phone and works correctly. I am assuring other users that maybe cannot examine the contents that it is clean.
My modified version only rationalizes how partitions are presented in Recovery. Try the original and you will understand the need to alter the partitions displayed.
MIUI based on MM is in beta testing for ReNo2 already (I am not one of the beta testers)
Be careful what you wish for as MM brings everyone one step closer to a closed platform like Apple. I would be happy on 5.1.1
jajk said:
[MENTION=4666525]
Be careful what you wish for as MM brings everyone one step closer to a closed platform like Apple. I would be happy on 5.1.1
Click to expand...
Click to collapse
Hey man, pls washout that greyed info.
Do u mean there'll be a locked bootloader in miui MM ?
U should inform us if u knew it at first time !
Hi, Is there a MultiROM / dualboot feature included in this release?
Thank you to jemimi for the dev work and thank you in advance for any reply.
@MiSteven No dualboot in this one and I haven't seen one for our phone (not that I have been looking)
New version 3.0.0-3
jajk said:
New version 3.0.0-3
Click to expand...
Click to collapse
Is this update of jemmini's TWRP_3_ReNo2.zip from 4pda.ru?
@sanceliken2000 No it is original.
jajk said:
@sanceliken2000 No it is original.
Click to expand...
Click to collapse
Thanks for the answer. Could you please tell me if i could flash it directly with twrp 3 jemminis' in order not to do the procedure with fastboot?
@sanceliken2000 Just flash it in your existing TWRP (it is a flashable zip)
Interface look good, old backups need to be re-backup! Thx~
addro said:
Interface look good, old backups need to be re-backup! Thx~
Click to expand...
Click to collapse
If you have backup made by jemmini's TWRP3 it is not necessary to re-back. The new one understands that backup.
@faorekh It surely is. I look for compatible donors since we have no official build for our device.
The only thing that changes from previous TWRP backups is the folder name where it is stored. If needed, rename the old folder to /TWRP/BACKUPS/Redmi_Note_2 and TWRP will see it or just move the old backups into the new folder when it is created on first new backup.
There is the signature "Lenovo/full_aio_otfp/aio_otfp" inside recovery. Is this recovery port from recovery-twrp-3.0.0-3-k3.img of Lenovo K3 Note?
This version works great for my rmn2 prime.
Sent from my 2014817 using Tapatalk
I flashed this recovery yesterday through my twrp 2.8.7.
After updating to TWRP 3.0.0-3 I got messages like this:
Code:
This package is for "hermes" devices; this is a "".
[COLOR="Red"]Updater process ended with ERROR: 7
Error installing zip file '/external_sd/!Flash/twrp287.zip'[/COLOR]
After that I used the fix in this thread to make my old recovery flashable again. Now everything works fine again, but you may want to look into that, so others won't have to get similar headaches as me.
Little note: I spent 3 hours trying to make this work under OSX El Capitan, but it seems like OSX can't create flashable zips. I used a windows partition to zip the files and everything worked fine.
I'm using the official version of TWRP flashed to my device.
If I set the device encryption with a password then TWRP is unable to mount the encrypted file system - It fails with 'Incorrect Password'
If I change to use a PIN then TWRP successfully mounts and decrypts the file system.
Is this a known issue, or is there any work round to enable to use of a password rather than a PIN?
Anyone?
iam-q said:
I'm using the official version of TWRP flashed to my device.
If I set the device encryption with a password then TWRP is unable to mount the encrypted file system - It fails with 'Incorrect Password'
If I change to use a PIN then TWRP successfully mounts and decrypts the file system.
Is this a known issue, or is there any work round to enable to use of a password rather than a PIN?
Click to expand...
Click to collapse
iam-q said:
Anyone?
Click to expand...
Click to collapse
Known TWRP issue across multiple device types. Google is your friend.
Alas google hints at a problem with some versions and some phones - there is no actual word from the developer(s) and if you care to check the github site you will find a mass of bugs raised with no replies and missing information. Most of the issues others have raised relate to nothing working at all or patten unlock not working.
iam-q said:
Alas google hints at a problem with some versions and some phones - there is no actual word from the developer(s) and if you care to check the github site you will find a mass of bugs raised with no replies and missing information. Most of the issues others have raised relate to nothing working at all or patten unlock not working.
Click to expand...
Click to collapse
Yes - given the number if independent reports it is reasonable to suspect there is an issue that either can not be replicated or is noting addressed
Hi,
This last days I have stranges things with my phone, and it is the first time that happened.
When I reboot after install magisk modules or adaway file host, my phone cannot be unlocked.
I type the pin code for unlock my sim card, and after the pin code for unlock the phone.
At this moment I have a black screen and I must retype my code ever and ever.
Nothing to do, just reinstall all the rom. Unable to use a clean backup, this is the same problem.
If anybody knows this issue and can save my life, you're welcome.
Thanks a lot, cordialement
I found the issue.
I can install magisk and reboot normally.
But when I install modules everything is locked.
If anyone have infos?
Lethalben said:
I found the issue.
I can install magisk and reboot normally.
But when I install modules everything is locked.
If anyone have infos?
Click to expand...
Click to collapse
Hello, I am updating my mom's phone and saw your post.
Unfortunately that bug has been around for a few months, I have a quick temporary fix for you but unfortunately the bug will return, if you can live without a screen lock that may be you only solution for now.
Lock Screen ( delete the lock)
Boot to Recovery
Go to Recovery File Manager
Navigate to the /data/system folder
locate and delete the file called : locksettings.db
Now you no longer have a screen lock and you can easily get into the phone.
FYI : If you want the lock again , simply create a new key or pattern
This issue could be anything such as corrupted permissions, It seems that it pops up after installing audio mods and substratum. But I don't think it is caused by either one.
If your phone gets hot while experiencing this issue flash the thermalfix 7 file, located on the thermals thread https://forum.xda-developers.com/showpost.php?p=78717015&postcount=18
This morning I've formated my phone to be sure is not an error from me. I will try your solution if it happens again.
Thanks for your response my friend!
Is it possible f2fs formating data partition is the issue?
Lethalben said:
Is it possible f2fs formating data partition is the issue?
Click to expand...
Click to collapse
It's very likely that this is the origin of the problem. It happens to me too, and have F2FS formated data too.
Forsaken75 said:
It's very likely that this is the origin of the problem. It happens to me too, and have F2FS formated data too.
Click to expand...
Click to collapse
I'm go back to ext4 and everything is OK.
I saw a magisk module who's made for stop this issue.
If there is a magisk module for that I think the problem is f2fs!
Lethalben said:
Is it possible f2fs formating data partition is the issue?
Click to expand...
Click to collapse
I don't think so because I only use Ext4
Well, I think I finally found the true origin of this problem: Magisk Hide interferes with newer Webview implementations, as explained here:
https://www.didgeridoohan.com/magisk/MagiskIssues#
I also found several workarounds:
1) Disable Magisk Hide. I need some banking apps, so for me this is not an option.
2) Use Chrome Beta and select its engine as default Webview in Developer Options. Chrome Beta signature is not buggy, so it works as it should. This is the solution that I've chosen, by the way.
3) Ask our developers @codeworks @mosimchah and the others if they could include this commit that fixes invalid signatures in their future releases:
https://github.com/LineageOS/android_vendor_cm/commit/a3a76f5d1cc233ad8024ffdc74bb3a786e1605c3
Hi all:
Have you managed to solve the screen lock problem? I did not achieve it and I followed all the instructions you mentioned.
A greeting.
txiscoman said:
Hi all:
Have you managed to solve the screen lock problem? I did not achieve it and I followed all the instructions you mentioned.
A greeting.
Click to expand...
Click to collapse
It's some app compatibility issue with Android Pie/Webview for sure. In my case was my banking app, changing to Chrome beta fixed the problem (app still crashes from time to time, but I'm not having the damned screen lock problem anymore)
You can try using Webview component alone from Play Store (I notice that in my case it's working too) or do some research to find out which app is causing the issue and uninstall it (if you can live without it, of course)
Deleted
So, as has probably been spotted in various places, Google dropped an Android Q GSI here recently.
One thing it requires (which breaks because Huawei, of course) is AVB support. Looks like init is unable to find the vbmeta image to verify and so it throws it's hands up with a "screw you, I'm going home".
Fortunately, this is relatively easy to work around - I have it booting on a Mate 9 that's been upgraded to EMUI 9, and I wouldn't be surprised if others have the same issue.
In any case, if this might be the reason why you're not booting, copy the attached file into /system/lib64 using TWRP or something.
There's other things broken on it - but that'll get it booting at least.
EDIT:
Link to patched Q GSI (GMS arm64 QPP2.190228.021):
https://drive.google.com/open?id=1dnEKJbjoiGhHuL6BLM8qXXyBFOKkE1bD
The only thing changed from the Google distributed image is the replacement of /system/lib64/libfs_mgr.so.
I will give that a try..
What are you doing for the selinux deniels?
Great, where did you install twrp as ramdisk partition in emui 9 doesn't exist anymore?
THE MAXIMUM POWER said:
Great, where did you install twrp as ramdisk partition in emui 9 doesn't exist anymore?
Click to expand...
Click to collapse
You still have the recovery partition, which can be used to flash twrp??
What works/doesn't work for you?
MishaalRahman said:
What works/doesn't work for you?
Click to expand...
Click to collapse
In the bit of playing I did, wifi to unsecured networks works, secured does nothing. Most of the apps included seem to work - but I didn't get too far into playing with it.
Can't say anything about cellular, as the device I loaded it on has a dud modem. It does read imei 1 successfully, though, so it might work on another device.
deepsrd said:
I will give that a try..
What are you doing for the selinux deniels?
Click to expand...
Click to collapse
Nothing yet. Just made sure the lib I posted was in the right place with proper permissions.
Doesn't seem to work on the Huawei Mate 10 Pro.
MishaalRahman said:
Doesn't seem to work on the Huawei Mate 10 Pro.
Click to expand...
Click to collapse
Hmm. I've heard mixed reports.
I've only tried it on the one device - MHA-AL00, EMUI 9.0.1.150 base. I figured it might be relevant to other people since there were a fair number of people on the main website post commenting on problems with AVB, which led me to that workaround.
I installed it with twrp over adb:
adb push libfs_mgr.so /tmp
adb shell
mkdir /system_root
mount -t ext4 /dev/block/bootdevice/by-name/system /system_root
cat /tmp/libfs_mgr.so > /system_root/system/lib64/libfs_mgr.so
reboot
On reboot, after a long wait (seems to take a minute to get to boot animation, that's Huawei for you), it came up to the welcome screen.
Edit - changed cp / chmod / chcon to cat, as it doesn't replace the file, keeping it's previous permissions & security label.
I think it will be better if you make a Q IMG that include the fixes
THE MAXIMUM POWER said:
I think it will be better if you make a Q IMG that include the fixes
Click to expand...
Click to collapse
Check the first post, I've added a link to the patched image.
irony_delerium said:
Check the first post, I've added a link to the patched image.
Click to expand...
Click to collapse
And now it actually booted on the Mate 10 Pro. Nice!
Does it work on devices other than huawei?
AsusZenFone3Deluxe said:
Does it work on devices other than huawei?
Click to expand...
Click to collapse
There's no reason for it not to. All that the patch I applied does is make it so that Android doesn't go looking for vbmeta information, so if that's the reason it fails to boot elsewhere this might allow it to work. If the image from Google already works, or it otherwise gets to the Android boot animation, this build won't do anything for you.
It booted on my MediaPad M5 but with no wifi, it stuck at "saved" but never mind, i just wanted to see the Q 2 beta, your fix might work as well with other unbootable roms like Pixel experience.
I really appreciate your work
THE MAXIMUM POWER said:
It booted on my MediaPad M5 but with no wifi, it stuck at "saved" but never mind, i just wanted to see the Q 2 beta, your fix might work as well with other unbootable roms like Pixel experience.
I really appreciate your work
Click to expand...
Click to collapse
Yeah, I've only been able to connect to unsecured networks. Pretty sure that's HAL changes in Q to blame.
irony_delerium said:
Yeah, I've only been able to connect to unsecured networks. Pretty sure that's HAL changes in Q to blame.
Click to expand...
Click to collapse
Ohh, thank you for the hint, btw any way to install your mod through fastboot mode as MediaPad M5 doesn't have a good TWRP?
Thank you in advance
THE MAXIMUM POWER said:
Ohh, thank you for the hint, btw any way to install your mod through fastboot mode as MediaPad M5 doesn't have a good TWRP?
Thank you in advance
Click to expand...
Click to collapse
I don't know about using it on Pie builds - init on Q is dynamically linked, on Pie it's a static binary, so you'd have to patch /init to make that change. Whether it would help or not, I don't know.
MishaalRahman said:
And now it actually booted on the Mate 10 Pro. Nice!
Click to expand...
Click to collapse
Did you have to do any other than what's instructed? Id like to take it for a spin.
Also, unrelated, what's with some of our "avatars" are green while others yellow?
I'm pretty sure @fullofhell was looking for an actual bootable build, and not just hear say.
culiacanazo said:
Did you have to do any other than what's instructed? Id like to take it for a spin.
Also, unrelated, what's with some of our "avatars" are green while others yellow?
I'm pretty sure @fullofhell was looking for an actual bootable build, and not just hear say.
Click to expand...
Click to collapse
Haha yeah Bro i tried this yesterday thanks tho
Hi everyone
I have created an python script to automate patching of the super partition in A/B devices
can be found here: (https://github.com/ChromiumOS-Guy/SuperPatcherGSI)
important to mention that both Windows / Linux versions only work for 64-bit,
I have attached how a full log of the SuperPatcherGSI script looks like when it successfully makes a patched super.img
also I'm a new user in the XDA forums so please tell me if this post needs to be moved to somewhere else,
feel free to ask any question I will try to answer to the best of my abilities
Enjoy and Thanks.
@ChromiumOS-Guy , you are great and your script works smoothly.
Just installed LineageOS 20 after having MIUI 13.
Somehow, after flashing, my phone lost the MAC address and bluetooth (IMEIs are fine).
Do you think it can be due to LineageOS or for the flashing process?
Welcome to XDA!
Hello good tool i like it but im getting error on repack could you help ?
snx413 said:
Hello good tool i like it but im getting error on repack could you help ?
Click to expand...
Click to collapse
I can try to
newboihere said:
@ChromiumOS-Guy , you are great and your script works smoothly.
Just installed LineageOS 20 after having MIUI 13.
Somehow, after flashing, my phone lost the MAC address and bluetooth (IMEIs are fine).
Do you think it can be due to LineageOS or for the flashing process?
Welcome to XDA!
Click to expand...
Click to collapse
Thanks!,
never happened to me though, try changing LineageOS to 19 had only bad things happen with 20 (my own experience though may not be the same)
if it still doesn't work maybe the firmware you flashed corrupted your nvdata ?
if this is the case you can use SP flash to take a backup of current nvram /nvdata / nvcfg / protect1 / protect2
and try to restore MAC address and bluetooth with SP writer or Modem Meta (don't forget engineering rom)
sorry for reply time i took a break from phone roming (working on making custom PCBs)
edit:
also know that fastbootb(fastboot dynamic) works for flashing dynamic images with phones with fastboot support, this tool is for phones without fastboot like Samsung with download mode ,though it should work all the same just letting you know (if Samsung do have fastboot then i don't know about it)