Related
Dear Android Hackers!
Please consider helping if you have some spare time and good will.
The device is Samsung Galaxy Player 4.2 (mine is North America version from the US)
Product code: YP-GI1
Android: Gingerbread 2.3.6
Kernel: 2.6.35.7
There is no special section in XDA for this device, so we (the owners of such devices and others who are trying to help) were discussing the matters of rooting here: http://forum.xda-developers.com/showthread.php?t=1715461&page=999
We have tried all the publicly available exploit-based rooting methods, none works, the device release date is April 2012, and there is no Android Gingerbread Local Privilege Escalation exploit released after that date if I am not wrong, and all the old ones are patched as it comes out...
Disclaimer: I'm not a developer, and everything I know I've learned in the last month, so please not laugh if I'm telling something stupid
So, as I understand the options are:
1.
Solution: Find a new exploit, get root, install SuperSU, profit
Problem: There is no publicly available exploit that I'm aware of
2.
Solution: Create an update.zip package with SuperSU and BusyBox, install it in the Recovery Mode
Problem: We need a genuine Samsung signing key to bypass the signature checking
3.
Solution: Get the stock rom, inject SuperSU and BusyBox, flash using Heimdall or Odin
Problem: There is no stock rom available, where do you people get them ha?
4.
Solution: Port CWM to our device, install it, then install and update.zip with SuperSU and BusyBox
Problem: I don't know how to create a CWM rom for my device
So, can anybody help with anything please? THANK YOU!
Up.. Anybody?
There hasn't been a leak of the firmware?
If there's no exploit for you to use, it's going to be hard.
And there probably aren't many people working on GB root exploits.
If you can get the kernel or system partition firmware file it would be easy to do.
Wish I had more help for you.
Did it ship with this version, or did it take an update?
If it took an update you might have hope. PM me if it did, I prolly won't see this thread again.
D
.
dsb9938 said:
There hasn't been a leak of the firmware?
If there's no exploit for you to use, it's going to be hard.
And there probably aren't many people working on GB root exploits.
If you can get the kernel or system partition firmware file it would be easy to do.
Wish I had more help for you.
Did it ship with this version, or did it take an update?
If it took an update you might have hope. PM me if it did, I prolly won't see this thread again.
D
.
Click to expand...
Click to collapse
Thanks for your interest.
No, there were no updates, it is the stock firmware.
The source code of the kernel is available at Samsung's site. And I have dumped the contents of the /system partition (except for several config files, see below):
Code:
$ /data/local/tar -czf /sdcard/external_sd/system.tar.gz /system
tar: removing leading '/' from member names
tar: can't open '/system/etc/bluetooth/audio.conf': Permission denied
tar: can't open '/system/etc/bluetooth/auto_pairing.conf': Permission denied
tar: can't open '/system/etc/bluetooth/input.conf': Permission denied
tar: can't open '/system/etc/bluetooth/main.conf': Permission denied
tar: can't open '/system/etc/dbus.conf': Permission denied
tar: error exit delayed from previous errors
So here is the /system:
http://depositfiles.com/files/e0odb9gvt
password: XDA-DEV
P.S.
Also PM'ed you this post
dsb9938 said:
There hasn't been a leak of the firmware?
If there's no exploit for you to use, it's going to be hard.
And there probably aren't many people working on GB root exploits.
If you can get the kernel or system partition firmware file it would be easy to do.
Wish I had more help for you.
Did it ship with this version, or did it take an update?
If it took an update you might have hope. PM me if it did, I prolly won't see this thread again.
D
.
Click to expand...
Click to collapse
any way you could help?
You will need two devices. There are a few different approaches, but all will require two devices to get everything.
First option:
Dump all /system partition contents. This can be tough without busybox, and without root it will likely be incomplete. (Edit: Looks like you have this.)
Assuming the 4.2 uses ext4 - use http://forum.xda-developers.com/showthread.php?t=1081239 to rebuild an Odin-flashable image from the dump. Without root access, the dump will likely be incomplete but at least hopefully bootable. (Based on the posts above, my guess is that Bluetooth will be busted.)
Once booted, use dd to dump the stock kernel image
Use initramfs repacking tools (these vary by device...) to change default.prop of the stock kernel so that it is debuggable and insecure (ADB sessions have root)
Flash this image into another device to get a full and complete /system dump (including the ones you couldn't dump above).
Second option:
Copy individual files from the initramfs of a running system including scripts
Get kernel source
Build a kernel using the manually dumped initramfs (basically, everything in / that isn't a mount point)
Flash this kernel to get a clean /system dump
Root-inject the /system dump (see above) and flash that on another device to get the stock kernel
It sucks that US devices never seem to have stock firmware images available on release like international devices do.
I can't help you beyond this, everything else is device-specific.
I'm not too experienced with this, but if you you can compile the system.img you might be able to root it. Pm me if you need more specifics, I remember a friend doing this with his motorola charm.
Edit: Heres a nand upload, you should be able to get it from here. Just extract it with yaffs2
http://forum.xda-developers.com/showthread.php?p=30320175&postcount=53
flapflip22 said:
I'm not too experienced with this, but if you you can compile the system.img you might be able to root it. Pm me if you need more specifics, I remember a friend doing this with his motorola charm.
Edit: Heres a nand upload, you should be able to get it from here. Just extract it with yaffs2
http://forum.xda-developers.com/showthread.php?p=30320175&postcount=53
Click to expand...
Click to collapse
No recent device uses raw NAND, and thus yaffs2 doesn't apply.
The problem is getting clean kernel and system dumps without root access - the best you'll do usually is a partial system dump that is hopefully bootable, can be root-injected, and then flashed to a device to get clean kernel dumps. With the kernel dump, you can build an insecure kernel, flash it to a second device, and get the factory image.
In the case of Player 4.2 - there is a POSSIBILITY an insecure international device kernel will boot well enough to get a clean system dump. I know Player 5.0 initramfs was identical, and the only difference between international and USA kernels was the touchkey map. So an international kernel would boot on USA devices but would have broken touchkeys.
Have you checked for rom on sammobile.com. If anyone can provide original firmware are those guys. You can also request it on their forum.
Sent from my HTC One S using xda app-developers app
Entropy512 said:
No recent device uses raw NAND, and thus yaffs2 doesn't apply.
The problem is getting clean kernel and system dumps without root access - the best you'll do usually is a partial system dump that is hopefully bootable, can be root-injected, and then flashed to a device to get clean kernel dumps. With the kernel dump, you can build an insecure kernel, flash it to a second device, and get the factory image.
In the case of Player 4.2 - there is a POSSIBILITY an insecure international device kernel will boot well enough to get a clean system dump. I know Player 5.0 initramfs was identical, and the only difference between international and USA kernels was the touchkey map. So an international kernel would boot on USA devices but would have broken touchkeys.
Click to expand...
Click to collapse
can u explain this a bit more? what are touch keys exactly? sorry ima noob but we are still cant find anything. if you could post your ideas on the thread http://forum.xda-developers.com/showthread.php?t=1715461 that would be helpful thanks!
Entropy512 said:
You will need two devices. There are a few different approaches, but all will require two devices to get everything.
First option:
Dump all /system partition contents. This can be tough without busybox, and without root it will likely be incomplete. (Edit: Looks like you have this.)
Assuming the 4.2 uses ext4 - use http://forum.xda-developers.com/showthread.php?t=1081239 to rebuild an Odin-flashable image from the dump. Without root access, the dump will likely be incomplete but at least hopefully bootable. (Based on the posts above, my guess is that Bluetooth will be busted.)
Once booted, use dd to dump the stock kernel image
Use initramfs repacking tools (these vary by device...) to change default.prop of the stock kernel so that it is debuggable and insecure (ADB sessions have root)
Flash this image into another device to get a full and complete /system dump (including the ones you couldn't dump above).
Second option:
Copy individual files from the initramfs of a running system including scripts
Get kernel source
Build a kernel using the manually dumped initramfs (basically, everything in / that isn't a mount point)
Flash this kernel to get a clean /system dump
Root-inject the /system dump (see above) and flash that on another device to get the stock kernel
It sucks that US devices never seem to have stock firmware images available on release like international devices do.
I can't help you beyond this, everything else is device-specific.
Click to expand...
Click to collapse
I tought of the 2nd option but I miss actually the init.rc, init.hugo.rc and init and recovery files. Someone that tried to help me said that he can't do it. Maybe alice you can make a dump of this for me so I can build an insecure kernel. (hopefully)
good nice.....
Sorry, I was offline the last 3 days.
Entropy512, thank you very much for detailed description of the available options.
Assuming the 4.2 uses ext4 - use http://forum.xda-developers.com/show....php?t=1081239 to rebuild an Odin-flashable image from the dump. Without root access, the dump will likely be incomplete but at least hopefully bootable. (Based on the posts above, my guess is that Bluetooth will be busted.)
Once booted, use dd to dump the stock kernel image
Click to expand...
Click to collapse
I don't understand this part. Wouldn't I just rewrite the stock image when flashing the dumped one? And what is the point of flashing the dumped image without modifications? (or you just didn't write about the needed modifications, e.g. injecting the su binary there?). And should I deodex the /system/app/ and /system/framework directories before creating the new image or no modifications are needed? And if it's preferable to deodex, how do I do that in Linux? Thank you!!
Added:
Meanwhile, I've created a system.img with injected su and superuser.apk, not deodexed, here - http://forum.xda-developers.com/showpost.php?p=31345895&postcount=418
1. Search google and xda...
2. Sign zip with signapk or some other signing tool...
3. Try sams firmware or extract your rom... search for how to in guide in my signature(create custom rom)
4. Search if someone have already ported it on your device or use build.clockworkmod.com
Sent from my GT-S7500 using xda premium
Dear my friends,
i knwo, this is the "normal" Mate 9 thread, but there is no Pro forum and in the Porsche forum is ... boooring
So, to me, i own a porsche design (LON-L29C721), i already have got TWRP and root on it, thx to Rayglobe, but its TWRP without encryption support, and root just with phh´s avaliable!
here is now my question:
Is there any newer TWRP for LON models out there? Cause i really want to use a TWRP with encryption support to get root with magisk!
And, if i´m already here, question to ALL Mate Users:
- How can i turn off the charging led ... it´s horrible (root available)
- Light Flow isnt working right, any other app what works with emui5?
- any app or mod out there, to get increasing ringtones?
THX mates,
cheers Markus
Same here and busybox is not installing. Any help?
MultiCulti said:
Dear my friends,
i knwo, this is the "normal" Mate 9 thread, but there is no Pro forum and in the Porsche forum is ... boooring
So, to me, i own a porsche design (LON-L29C721), i already have got TWRP and root on it, thx to Rayglobe, but its TWRP without encryption support, and root just with phh´s avaliable!
here is now my question:
Is there any newer TWRP for LON models out there? Cause i really want to use a TWRP with encryption support to get root with magisk!
And, if i´m already here, question to ALL Mate Users:
- How can i turn off the charging led ... it´s horrible (root available)
- Light Flow isnt working right, any other app what works with emui5?
- any app or mod out there, to get increasing ringtones?
THX mates,
cheers Markus
Click to expand...
Click to collapse
Same here and busybox is not installing. Any help?
Edit: OH. I think I helped you already. Didn't notice this post was from april
Anyhow, you should be able to use the TWRP for regular Mate 9, then install Magisk using that.
If any of you Pro owners want to test, here's a newer TWRP: https://mega.nz/#!45kwBJaY!4e1uRfrqOME7gHzuICHxX9L8BF6fCY1qbzzEkz8i4zs
It uses /cache for TWRP settings so they're actually kept between reboots, and you can select /cache as Storage to flash from, which should save some trouble since you have no ext sd. (Unless you decrypted, which makes /data readable).
The Copy Log button saves to /cache/recovery.log as well.
It's built using, mostly, Tkkg1994's sources and only removed /external_sdcard entry in recovery fstab, and altered partition sizes in BoardConfig.mk to match raimondo's source.
If it doesn't work and you can't get back to recovery, use fastboot to flash back older twrp.
ante()
I see this is a month old but I just came across it having issues with my mate 9 rooted at the moment... So I stumbled across this twrp to test and I will try it both on this 9 pro and I also will try it on my pd .
Since rooting I can only use puffin browser because any others the minute I launch my Kirin 960 throttles to minimums and it's like horrible ... In case anyone else out there has run into this I'm all ears... I've tried everything even terminal su command stop bcl stop perkd and nothing budges it so frustrating....
MultiCulti said:
Dear my friends,
i knwo, this is the "normal" Mate 9 thread, but there is no Pro forum and in the Porsche forum is ... boooring
So, to me, i own a porsche design (LON-L29C721), i already have got TWRP and root on it, thx to Rayglobe, but its TWRP without encryption support, and root just with phh´s avaliable!
here is now my question:
Is there any newer TWRP for LON models out there? Cause i really want to use a TWRP with encryption support to get root with magisk!
And, if i´m already here, question to ALL Mate Users:
- How can i turn off the charging led ... it´s horrible (root available)
- Light Flow isnt working right, any other app what works with emui5?
- any app or mod out there, to get increasing ringtones?
THX mates,
cheers Markus
Click to expand...
Click to collapse
Hello, could you please send me the oeminfo backup from your lon l29c721
Thanks
Androwar said:
Hello, could you please send me the oeminfo backup from your lon l29c721
Thanks
Click to expand...
Click to collapse
+1 for L29C721 OEMINFO.
anyone can share oeminfo?
This is a flashable zip that enables init.d scripts to run depending on the root method you have installed.
To uninstall, just flash the zip again and it'll restore everything to how it was before
If magisk:
Boot scripts will be installed that will run all exectuable scripts in init.d as post-fs-data except any that end in '-ls' which will be run as late start. Also note that if you're trying to create the init.d folder, the original directory when using magisk is actually /sbin/.core/mirror/system/etc. It goes without saying that this could break safetynet (honestly though, just copy your script to /sbin/.core/img/.core/service.d or post-fs-data.d instead and set permissions to 0755 rather than creating an init.d directory - using the in-house magisk solution is always the better option. Magisk users have almost no reason to create an init.d directory)
The rest of this is for non-magisk/supersu installs
Otherwise: the boot img and part of the system will be modified to enable init.d support.
What it does:
Search for sysinit in any rc file. If found and seclabel is intact and equal to target seclabel for my init rc script, then that seclabel will be set to permissive in sepolicy if needbe instead of using my solution
If sysinit with seclabel isn't found, a custom rc file and system/bin/script file will be installed and sepolicy will be patched accordingly to add init.d support. Init.d scripts will be run the same way as with magisk installs above
Adds magiskpolicy to sbin. It's more up to date and complete than setools so why not?
If there is an error on unpacking your boot image, check the binary inclusion section here to see if your device needs one: https://github.com/osm0sis/AnyKernel3#-binary-inclusion
If it does, place it in addon/AnyKernel3/tools/arm (or x86 - whichever your architecture is - probably arm)
I am not responsible for any oddities that happen to your device because of this, use common sense. For example, if you know your device has a weird boot img, check first.
BACKUP BOOT AND SYSTEM PARTITIONS BEFORE FLASHING
Compatibility: Any device magisk is compatible with
Confirmed working (boot img method):
Nexus 5x
Verizon LG G2
Oneplus 3/3T
Oneplus 5T
Nexus 9
Redmi Note
Zuk Edge
Axon 7 (A2017U)
Nexus 5
SM-N900T
SM-T350
LeEco Pro 3
Confirm your device works and I'll add it to the list!
Special thanks to: @osm0sis, @CosmicDan, @Ricky Divjakovski, @JustArchi
Source: https://github.com/Zackptg5/Init.d-Injector
Download
Good stuff :good:
Good idea with the removal of other/old init.d capabilities. It's annoying that so many ROM's/kernels claim to have init.d but they're fake or hacky (well, I guess the sepolicy injection is pretty hacky too lol). You might also want to consider looking for install-recovery hijack method of init.d and disabling that too - shouldn't be too hard, just check if the file exists in known locations and grep for init.d. The harder part though is what to actually *do* if found - probably best to comment-out the line that contains "run-parts" and/or "init.d" rather than erase the whole file.
CosmicDan said:
Good stuff :good:
Good idea with the removal of other/old init.d capabilities. It's annoying that so many ROM's/kernels claim to have init.d but they're fake or hacky (well, I guess the sepolicy injection is pretty hacky too lol). You might also want to consider looking for install-recovery hijack method of init.d and disabling that too - shouldn't be too hard, just check if the file exists in known locations and grep for init.d. The harder part though is what to actually *do* if found - probably best to comment-out the line that contains "run-parts" and/or "init.d" rather than erase the whole file.
Click to expand...
Click to collapse
Good idea, I'll look into that. Thanks!
Will try this soon on Honor 8 Pro and report back.
Quick update to v1.1
Just bought a used nexus 9 and found that the boot partition layout for it and other nvidia tegra devices is different from typical android devices. So I added support for nvidia tegra devices
So github screwed with my EOL again and converted a few of the files to windows eol which broke everything. I just fixed it and reuploaded v1.1 with the fixes so just redownload it and flash away. Thanks to @dmgZero for finding the issue
Just updated to v1.2. I added support for pixels and nexus5x/6p avb-signing. I haven't been able to test it out myself as my bullhead doesn't even need signing to work so any feedback would be great. Also updated the OP on how to modify this for any weird boot imgs you may have
Edit: No point in spamming the thread with another post: updated to v1.3. Just adds capability to remove any init.d stuff present from install-recovery.sh. Thanks to @CosmicDan for pointing it out
Works fine on Redmi Note (a MediaTek Helio X20 device) running MIUI 9 (Android 6.0).
One tiny detail, maybe just do an mkdir /system/etc/init.d after the patch succeeds, if it doesn't already exist. I could imagine that some other zips could check for the existence of this folder for a simple way to determine if init.d is supported.
CosmicDan said:
Works fine on Redmi Note (a MediaTek Helio X20 device) running MIUI 9 (Android 6.0).
One tiny detail, maybe just do an mkdir /system/etc/init.d after the patch succeeds, if it doesn't already exist. I could imagine that some other zips could check for the existence of this folder for a simple way to determine if init.d is supported.
Click to expand...
Click to collapse
Sweet, I already have that in the sysinit script but it would make more sense to move that to the installer so I'll put that into the next version. Thanks!
Is that supposed to work systemlessly?
You should probably add Samsung to the weird/hexed/Satan kernels. Tried flashing your zip and recovery came back with Invalid Partition upon failure, my device is a Galaxy Note 5 running RR 7.1.2. I do love the idea and your work though bro. Thanks.
Metabolic12 said:
You should probably add Samsung to the weird/hexed/Satan kernels. Tried flashing your zip and recovery came back with Invalid Partition upon failure, my device is a Galaxy Note 5 running RR 7.1.2. I do love the idea and your work though bro. Thanks.
Click to expand...
Click to collapse
I tried to originally but it was basically impossible to detect all bootimg types and they need extract binaries which if I included them all, would make the zip over 70mb. I updated the op a few days ago with instructions on how to add support for weird boot imgs (it's basically adding a few files to the zip)
I completely understand, I wasn't gonna ask you to include my kernel regardless that's rather selfish, and I did follow your guide in the OP to get it to work. I was just suggesting maybe add Samsung kernels next to LG in your OP. Great work bro, thank you.
Zackptg5 said:
I tried to originally but it was basically impossible to detect all bootimg types and they need extract binaries which if I included them all, would make the zip over 70mb. I updated the op a few days ago with instructions on how to add support for weird boot imgs (it's basically adding a few files to the zip)
Click to expand...
Click to collapse
---------- Post added at 02:58 AM ---------- Previous post was at 02:51 AM ----------
I'm a retard, I read the OP wrong earlier. Disregard the adding Samsung part ha.
Zackptg5 said:
I tried to originally but it was basically impossible to detect all bootimg types and they need extract binaries which if I included them all, would make the zip over 70mb. I updated the op a few days ago with instructions on how to add support for weird boot imgs (it's basically adding a few files to the zip)
Click to expand...
Click to collapse
sscheib01 said:
Is that supposed to work systemlessly?
Click to expand...
Click to collapse
The boot img is not part of the system partition so that's systemless. However, it installs an addon.d script and modifies the sysinit and install_recovery files if present which are on the system. It won't break safetynet if that's what you're wondering
Zackptg5 said:
The boot img is not part of the system partition so that's systemless. However, it installs an addon.d script and modifies the sysinit and install_recovery files if present which are on the system. It won't break safetynet if that's what you're wondering
Click to expand...
Click to collapse
I thought *any* System modification trips the Safety net?
I use the Universal Safetynet Bypass module for Magisk so it doesn't bother me, but curious.
Sent from my Redmi Note 4 using Tapatalk
CosmicDan said:
I thought *any* System modification trips the Safety net?
I use the Universal Safetynet Bypass module for Magisk so it doesn't bother me, but curious.
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
That's what I thought initially too but I've found lots of system modifications doesn't break safetynet such as editing the hosts file. Modifications to the zygote such as xposed framework for sure break safetynet but I'm not sure exactly which system modifications would. Other than testing them myself, I'm not really sure what would break it. I've found that you can completely alter parts of the system like with arise sound systems which adds a whole slew of libs and other modifications and safetynet still won't break (I found through my work there that having the system mounted as rw via a boot script will trigger safetynet but you can even go so far as to mount it as rw, make your changes, and then remount it as ro before boot completes and safetynet will still pass). It's weird man
Zackptg5 said:
That's what I thought initially too but I've found lots of system modifications doesn't break safetynet such as editing the hosts file. Modifications to the zygote such as xposed framework for sure break safetynet but I'm not sure exactly which system modifications would. Other than testing them myself, I'm not really sure what would break it. I've found that you can completely alter parts of the system like with arise sound systems which adds a whole slew of libs and other modifications and safetynet still won't break (I found through my work there that having the system mounted as rw via a boot script will trigger safetynet but you can even go so far as to mount it as rw, make your changes, and then remount it as ro before boot completes and safetynet will still pass). It's weird man
Click to expand...
Click to collapse
Kind of makes sense actually.
Hosts is in etc right, nothing in there is executable. So I imagine any changes to etc won't trip it because nothing in there would mess with device security. Sound mods... Well yeah they ADD libs but they don't replace any do they? They just add sound filters through the mixer configs in etc.
So I guess it makes sense. Sysinit is just added to xbin or whatever and I guess that doesn't trip it. But if you replaced, say, dex2oat with a proxy script to intercept oat generation, then it would definitely trip it.
Sent from my Redmi Note 4 using Tapatalk
Is it really needed??
I want to flash Dolby Atmos for Redmi Note 4, but init.d support is needed as mentioned by developer.
I tried Dolby Atmos without it sound is loud and great
I can't understand, why init.d is still needed?
Can anyone explain here?
amit.tiger12 said:
Is it really needed??
I want to flash Dolby Atmos for Redmi Note 4, but init.d support is needed as mentioned by developer.
I tried Dolby Atmos without it sound is loud and great
I can't understand, why init.d is still needed?
Can anyone explain here?
Click to expand...
Click to collapse
If it's working, then you don't need it or already have it. Init.d support is needed for Dolby if you are not using magisk or supersu and you have selinux set to enforcing
Zackptg5 said:
If it's working, then you don't need it or already have it. Init.d support is needed for Dolby if you are not using magisk or supersu and you have selinux set to enforcing
Click to expand...
Click to collapse
That's with respect to Dolby, what does it provide as a general point of view? What is it's significance?
Explain if you've enough time or just throw a link, it will help out.
Good day everybody,
A few questions about upgrading my pixel 3 from 9 to 10. To preface I have an unlocked bootloader and am rooted on the June 2019 version of android. I would like to update to android 10 and am wondering if one of my modifications to the build.prop would still work. I use the following modification for enabling hotspot:
net.tethering.noprovisioning=true
Can anybody confirm that this still works on Android 10?
Also, huge noob question - Where is the guide for updating from 9 -> 10 with root/unlock, and do I lose my data in the process? I can't seem to find anything but how to sideload monthly updates.
Thank you in advance for any help
To edit /system or /vendor you need to use magisk and do it systemlessly. A10 no longer allows you to directly modify these partitions. There is some discussion about exactly what you want to change under the guides section in the Pixel 3xl forum. For the second one, there is a guide somewhere in the guides section in this forum. You will need to do a full wipe with a version change. Look into different ways to back up your stuff before you switch. For apps and app data I did a twrp backup before switching then used titanium backup once on A10 to extract the app/data and restore it. For other stuff you might need to do it manually.
Follow this method for the Magisk based tethering modification:
https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-native-tethering-rooted-pixel-3-t3858662
(Works on Pixel 3)
Hi,
just got a HTC U11 Life phone running already Android 10.
I read and serached the forum for quite a while now and I couldn't figure out how to root the phone
According to this there is no working TWRP, but then again I find comments from people who say got TWRP working (here for instance).
In this HowTo Collection there are instructions, but I can't find the referenced patched image
Now I'm wondering if the problem is that my phone is already on Android 10 or did I just miss some important things?
Help appreciated!
Greetings from Greece, is there anything new? with htc u11 life running already Android 10
there is twrp recovery and root for device ?
Οne more question please, the device with android 10 has sense home ui ?
thank you very much and sorry for my bad English.
[A10][TWRP]WWE Google One edition
Hello guys, after so time as i start working on proper twrp for my HTC u11 life, which working on android one 10, it's finally done ✅ Os - 4.73.401.2 It's completely possible to make backup/flash *System *System_Image *Vendor *Vendor_Image *Boot...
forum.xda-developers.com
Root by flashing boot.img by magisk/lygisk.
@Trymitius great news bro ,thank you very much.
Btw your device probably (dont know for sure, cuz didn't test yet) need to be unencrypted. I've provide correct path in fstab for FBE but as i mentioned before it wasn't tested. Just in case, if you need to decrypt your devices, simply edit fstab.qcom + fstab.htc which you can find in /vendor/etc and change "filencryption=" to "encryptable" at system mounting line.
Just be careful, after that you'll need to reboot your device and wipe data or userdata partition. If you going to have any issues about/system partition you can fix it by editing fstab.qcom + fstab.htc and change "ro" --》》 "rw" at /system line.
thanks trymitius but I haven't bought the device yet. I believe in a few days it will be in my hands
sorry for my bad English.