Hello,
yesterday I read about the Generic LineageOS ROM that will work on all Project Treble compatible devices, if I understood it right. So it should also work on the Huawei MediaPad M5 since it supports Project Treble, right?
Does anyone have tried it out? And what's about Root?
I plan to buy the MediaPad M5, cuz my Pixel C is broken, but I want to have Root and a Vanilla Android ROM like LineageOS.
@Marcopoloy13 I would like to test it but as there is no firmware / ota package for the device available yet it's a bit risky. For installation you need to overwrite the recovery with TWRP but if installation fails I do not see a way back to stock. I am new to Huawei devices, probably you know wheter if at least erecovery is working you are able to return to stock?
@AndDiSa No, sadly I have no experience with Huawei devices, too. So I thing we have to wait till someone have the stock firmware?
What's about Root? Is already a rooting method working?
@Marcopoloy13 well, all rooting methods supported by Treble devices should work. I know that @phhusson has already prepared several roms based on Treble which provide root access, but first step is to get TWRP working or to have at least a save way to return to stock in case something goes wrong ...
AndDiSa said:
@Marcopoloy13 well, all rooting methods supported by Treble devices should work. I know that @phhusson has already prepared several roms based on Treble which provide root access, but first step is to get TWRP working or to have at least a save way to return to stock in case something goes wrong ...
Click to expand...
Click to collapse
FWIW, since this is yet another kirin 960, I'm fairly confident it should work, but that would make for a costly brick if it doesn't.
Could you send me your vendor/etc/selinux/nonplat_sepolicy.cil (this doesn't require root) so that I can run some early checks on it?
If GSI works, there is a way to get root/make a full dump, with two users:
User A (the most intripiduous one) installs the GSI, gets root with it, dumps all partition (except system because, well, that's the GSI)
With magisk manager, root the "ramdisk" dump.
Then user B flashes the rooted "ramdisk" partition, he gets root on stock ROM, and he can dump stock system.img
You don't need TWRP to flash a GSI, you just need fastboot, which should work natively on the device.
If the device is running Android 8.0, an Android 8.0 GSI has more chances to work than Android 8.1 GSI.
@phhusson I'll send you the vendor/etc/selinux/nonplat_sepolicy.cil when I am coming home, and to answer your question : yes, the device is running Android 8.0, so chances are not too bad, I think ...
AndDiSa said:
@phhusson I'll send you the vendor/etc/selinux/nonplat_sepolicy.cil when I am coming home, and to answer your question : yes, the device is running Android 8.0, so chances are not too bad, I think ...
Click to expand...
Click to collapse
Got it thanks, it passed the test on 8.1 AOSP.
It is not a guarantee of anything, but it's a bit safer than without the test
phhusson said:
Got it thanks, it passed the test on 8.1 AOSP.
It is not a guarantee of anything, but it's a bit safer than without the test
Click to expand...
Click to collapse
One question: do you know whether /system/etc/recovery-resource.dat contains the recovery image? I know that stock Android generally on boot is overwriting the recovery so I was wondering whether this file is/contains the recovery image ?
AndDiSa said:
One question: do you know whether /system/etc/recovery-resource.dat contains the recovery image? I know that stock Android generally on boot is overwriting the recovery so I was wondering whether this file is/contains the recovery image ?
Click to expand...
Click to collapse
Short answer is no.
Longer answer is that it is a part of recovery. in /system there is recovery-resource.dat and recovery-from-boot.p (or something like that, and recovery is made as a delta of boot.img (which you don't have access without root), and then applying recovery-from-boot.p and recovery-resource.dat on top of boot.img
phhusson said:
Short answer is no.
Longer answer is that it is a part of recovery. in /system there is recovery-resource.dat and recovery-from-boot.p (or something like that, and recovery is made as a delta of boot.img (which you don't have access without root), and then applying recovery-from-boot.p and recovery-resource.dat on top of boot.img
Click to expand...
Click to collapse
Well ... there is no recovery-from-boot.p and there is no extra partition for the recovery kernel but there is a recovery-ramdisk partition. I suppose recovery-resource.dat contains the recovery-ramdisk data, but it's only a feeling.
Edit: Hmmm ... probably not, looks more like a container of images.
I'm interessted too in the m5 but i want aosp or any custom rom. I don't like the emui one. But back to treble. Has anyone tested if it haves treble or any document what says it ? About the system img i think the one from other huaweis will not work correctly a lot of things like dpi and screen size is totaly different.
Anyone knows the codename of m5 ?
rcstar6696 said:
I'm interessted too in the m5 but i want aosp or any custom rom. I don't like the emui one. But back to treble. Has anyone tested if it haves treble or any document what says it ? About the system img i think the one from other huaweis will not work correctly a lot of things like dpi and screen size is totaly different.
Anyone knows the codename of m5 ?
Click to expand...
Click to collapse
The M5 definitely is Treble enabled. The code name for the SHT-W09, e.g. the 8.4 WiFi version is schubert.
AndDiSa said:
The M5 definitely is Treble enabled. The code name for the SHT-W09, e.g. the 8.4 WiFi version is schubert.
Click to expand...
Click to collapse
Okay thanks if we get safe way to restore stock firmware i would try to build twrp and a rom for it ( buidling for z2 and z2 tablet from sony currently) but rom building should be easy at all with treble
Twrp could be a bit harder but i think its possible to make it without kernel source. If kernel source is out it should be easy to do twrp
rcstar6696 said:
Okay thanks if we get safe way to restore stock firmware i would try to build twrp and a rom for it ( buidling for z2 and z2 tablet from sony currently) but rom building should be easy at all with treble
Twrp could be a bit harder but i think its possible to make it without kernel source. If kernel source is out it should be easy to do twrp
Click to expand...
Click to collapse
There is already kind of 'generic' TWRP for the Kirin 960 available. Either this works already or otherwise it should be easy to adapt. Biggest problem currently is the missing firmware package so that you can return to stock in case you need to ..
AndDiSa said:
There is already kind of 'generic' TWRP for the Kirin 960 available. Either this works already or otherwise it should be easy to adapt. Biggest problem currently is the missing firmware package so that you can return to stock in case you need to ..
Click to expand...
Click to collapse
Yes basicly you are right but the problem is the srenn size i think twrp is messed up if you flash the phone one. Another problem could be the display driver at all not sure if the m5 uses same driver as the rest
AndDiSa said:
There is already kind of 'generic' TWRP for the Kirin 960 available. Either this works already or otherwise it should be easy to adapt. Biggest problem currently is the missing firmware package so that you can return to stock in case you need to ..
Click to expand...
Click to collapse
Can't erecovery do that?
phhusson said:
Can't erecovery do that?
Click to expand...
Click to collapse
What do you mean ? Dump the firmware ?
rcstar6696 said:
What do you mean ? Dump the firmware ?
Click to expand...
Click to collapse
No, download and restore to a working stock firmware
@phhusson the functionality of erecovery is new to me. Can you expain how it works? Or can you give me a hint where I can get additional information about this. The only thnig I know is that erecovery is a second recovery which will / can be started when the system is messed up, but will it work on a modified system, too? Will it download the firmware if needed?
AndDiSa said:
@phhusson the functionality of erecovery is new to me. Can you expain how it works? Or can you give me a hint where I can get additional information about this. The only thnig I know is that erecovery is a second recovery which will / can be started when the system is messed up, but will it work on a modified system, too? Will it download the firmware if needed?
Click to expand...
Click to collapse
I don't know a lot about it, and I've never actually tested it.
What I know is that it has its own kernel/ramdisk/vendor/whatever, so as long as you don't flash any erecovery_* partition, you should be safe
I also know it is capable of connecting to WiFi
So considering all of this, I think that it is capable to download restore a fully functional firmware...
Perhaps you should try running eRecovery without doing flashing anything to see how it goes?
Related
Hello guys!
Recently, i've got this phone mentioned above. It is a great phone, everything is okay, but i do not like EMUI a lot, i prefer AOSP to EMUI.
Are there any custom ROMs (CM, AOSP, etc) to this phone?
I've looked around on 4pda.ru about this, i found a recovery, but thats it, nothing more.
There you go, i installed this TWRP 3.0.2.0, and it works like a charm.
1: Unlock your bootloader. IT IS INDISPENSABLE! If you brick your device locked, you lost.
2: Go into fastboot (Easiest: Turn off your device, and Hold down POWER DOWN + POWER WHILE you attach the USB from the computer. The phone will go instantly into fastboot mode, it works for me)
3: Type: fastboot flash recovery twrp.img
4: The phone now should download the recovery. Pull the battery out, and restart in recovery.
Download
The file is from 4PDA.ru, i have to reupload it, because 4PDA's sign up is a PAIN. A friend of mine helped me, and it took like 2 hours.
Altough, i do not know why you need the recovery other than backing up, since there are no custom rom avaiable for this phone. (Can anyone maybe port to it?)
I think, that porting Allwiev E4 Lite custom roms would be the best option, but I have weak knowledge about roms porting :crying:
There are no custom roms yet for this device.
For first you may trie to install nova launcher? It gives some feeling near to aosp.
Loller 123 said:
I think, that porting Allwiev E4 Lite custom roms would be the best option, but I have weak knowledge about roms porting :crying:
Click to expand...
Click to collapse
No. The best option is to port the ROM with the same chipset (MT6735).
My best result is a Doogee X5 Pro
Runner85sx said:
There are no custom roms yet for this device.
For first you may trie to install nova launcher? It gives some feeling near to aosp.
Click to expand...
Click to collapse
Thanks. I'll probably try it.
snikerfreak said:
No. The best option is to port the ROM with the same chipset (MT6735).
My best result is a Doogee X5 Pro
Click to expand...
Click to collapse
This is THE SAME chipset...
Loller 123 said:
This is THE SAME chipset...
Click to expand...
Click to collapse
Maybe I did read a wrong article. Could you please link a cyanogenmod to that device?
snikerfreak said:
Maybe I did read a wrong article. Could you please link a cyanogenmod to that device?
Click to expand...
Click to collapse
IDK, if there is cm for allview, but I'm trying to port IOS rom.
snikerfreak said:
There you go, i installed this TWRP 3.0.2.0, and it works like a charm.
1: Unlock your bootloader. IT IS INDISPENSABLE! If you brick your device locked, you lost.
2: Go into fastboot (Easiest: Turn off your device, and Hold down POWER DOWN + POWER WHILE you attach the USB from the computer. The phone will go instantly into fastboot mode, it works for me)
3: Type: fastboot flash recovery twrp.img
4: The phone now should download the recovery. Pull the battery out, and restart in recovery.
Download
The file is from 4PDA.ru, i have to reupload it, because 4PDA's sign up is a PAIN. A friend of mine helped me, and it took like 2 hours.
Altough, i do not know why you need the recovery other than backing up, since there are no custom rom avaiable for this phone. (Can anyone maybe port to it?)
Click to expand...
Click to collapse
@snikerfreak did you find any rom for this device.
My son instaled TWRP and wiped everything trying to flash an honor 5A rom, installation failed so now phone is dead.
Do you know where to get a firmware? Can't find anything right!
All attempts to find firmware for my Dual Sim Huawei Y6 II Compact (LYO-L21) failed so I want to ask a BIG support to anyone in this thread with a TWRP recovery installed. By inexperience my teenager son wiped every partition on the phone and now we are unable to boot. It would be of great help if some one could share a twpr backup (including all partitions) to be used not only for me but for anyone as a flashable firmware.
I'm aware it would take some time, skills and dedication.
Here is how to perform it:
Backup your current phone firts with all your personal data
Do a Factory Reset
Do a second backup to be shared as a stock rom or standard firmware
Restore personal backup
Upload firmware (stock rom) backup to the cloud and share donwload link here
Is there anyone wanting to provide this?
I'll be very grateful for that
Thanks
zumnao said:
All attempts to find firmware for my Dual Sim Huawei Y6 II Compact (LYO-L21) failed so I want to ask a BIG support to anyone in this thread with a TWRP recovery installed. By inexperience my teenager son wiped every partition on the phone and now we are unable to boot. It would be of great help if some one could share a twpr backup (including all partitions) to be used not only for me but for anyone as a flashable firmware.
I'm aware it would take some time, skills and dedication.
Here is how to perform it:
Backup your current phone firts with all your personal data
Do a Factory Reset
Do a second backup to be shared as a stock rom or standard firmware
Restore personal backup
Upload firmware (stock rom) backup to the cloud and share donwload link here
Is there anyone wanting to provide this?
I'll be very grateful for that
Thanks
Click to expand...
Click to collapse
OK I did the trick myself on a new phone I've got
Upload is done.
I've decided to create a new thread for it
Please check for the link here https://forum.xda-developers.com/general/rooting-roms/huawei-y6ii-compact-lyo-l21-dual-sim-t3577874
snikerfreak said:
Hello guys!
Recently, i've got this phone mentioned above. It is a great phone, everything is okay, but i do not like EMUI a lot, i prefer AOSP to EMUI.
Are there any custom ROMs (CM, AOSP, etc) to this phone?
I've looked around on 4pda.ru about this, i found a recovery, but thats it, nothing more.
Click to expand...
Click to collapse
Are there any custom ROMs?
Russian have custom ROMs in 4pda forum. It is Resurrection Remix OS 7.1.1 (unstable beta) and CyanogenMod 14.1_Android 7.1.1 (beta, camera not working). They stop work with RR_OS, but CM 14.1 is still porting.
You can help em.
links:
RR_Os port - 4pda.ru/forum/index.php?showtopic=792704&st=560#entry60137872
CM 14.1 port - 4pda.ru/forum/index.php?showtopic=792704&st=780#entry60547208
Also u can install ota-updates from custom recovery. Just del some strings in updater-script file into update.app \META-INF\com\google\android\ and repack its like .zip (w/o compression)
4xample strings:
assert(file_getprop(" -- it is checks firmware version and region
assert(apply_patch_check(" --- it is checks the hash sums of files the updates
UPDATED 2/19/2018
Almost enough here to start attempting debug builds... any other builders/devs out there working on this device? Hopefully some of this will be useful.
Minimal Omni device tree for TWRP (full lineage branch in progress as of 2/19/2018)
https://github.com/mightysween/android_device_motorola_payton
Proprietary blobs/vendor (initial push 2/19/2018):
https://github.com/mightysween/android_vendor_motorola_payton
Partition names/locations/mounts...maybe a few missing still:
https://docs.google.com/document/d/1EkPOkc8uUStKIjRGC2-4jkcXpxmj8v3piGPqZi9ctQM/edit?usp=drivesdk
7.1 KERNEL SOURCE:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/7.1.1-nougat-release-payton
8.0 KERNEL SOURCE:
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-OPW27.57-40
So what's the deal with the A/B partitions? I've seen that there are some lineage OS commits to handle the A/B partitions. Would it be possible to load an OS to the A partition and put the recovery on the B partition. I'm not familiar enough to know how much control of the boot process we can have with boot time commands. Does the bootloader have a boot to recovery option?
There doesn't seem to be a recovery partition in the list that you provided. I wonder what the fastboot commands look like... just thinking out loud on the internet. I don't have the phone yet, but I did have a look at Best Buy, so that practically makes me an expert. I have a N5X, so I'm lining up the successor for after its sudden, but inevitable betrayal.
gee one said:
So what's the deal with the A/B partitions? I've seen that there are some lineage OS commits to handle the A/B partitions. Would it be possible to load an OS to the A partition and put the recovery on the B partition. I'm not familiar enough to know how much control of the boot process we can have with boot time commands. Does the bootloader have a boot to recovery option?
There doesn't seem to be a recovery partition in the list that you provided. I wonder what the fastboot commands look like... just thinking out loud on the internet. I don't have the phone yet, but I did have a look at Best Buy, so that practically makes me an expert. I have a N5X, so I'm lining up the successor for after its sudden, but inevitable betrayal.
Click to expand...
Click to collapse
There is no traditional recovery partition...handled by boot. A/B is mainly to allow 'seamless' updates (as in OTA that downloads to the other partition for instant reboot). Bit more to it... if you want to read more, check out the Pixel forums.
Well... progress is being made. Wish there were others (there must be!) working on this.
I have the stock kernel, a VERY basic device tree, and cobbled-together vendor... syncing repos and will try to compile TWRP over the weekend. I do not expect it to work
Dealing with this right now on brunch...runs fine up until this point, appreciate any thoughts:
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/mightysween/android/omni/out/target/product/payton/obj/SHARED_LIBRARIES/libcryptfs_hw_intermediates/export_includes', needed by '/home/mightysween/android/omni/out/target/product/payton/obj/SHARED_LIBRARIES/libcryptfslollipop_intermediates/import_includes', missing and no known rule to make it
build/core/ninja.mk:157: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
Click to expand...
Click to collapse
Do I really need the lollipop libs???? Especially if I just want to compile TWRP and not full omni. Ahhhhhhh....so much fun
OK, got TWRP to compile
Need to do some testing in the emulator and double and triple check all sources and configs before even thinking about trying to boot it on the actual device.
But just troubleshooting at this point, so looking good for TWRP in coming days!
UPDATE: oops, totally compiled it with the wrong kernel. Haha... working through some defconfig issues, but hopefully nothing too crazy.
mightysween said:
OK, got TWRP to compile
Need to do some testing in the emulator and double and triple check all sources and configs before even thinking about trying to boot it on the actual device.
But just troubleshooting at this point, so looking good for TWRP in coming days!
Click to expand...
Click to collapse
I hope you can do it! Is the first step to get backups and ROMs. I don´t have the phone yet, but later the normal version that is sell in México and want to flash the Android One version (previously anyone get it working).
I'm returning my Amazon version of this phone and getting Project Fi version. I am willing to help in testing.
Well, my boot.img compiles fine... but will not boot to recovery. Given the fact that it is mostly guesswork on the device tree, I am not shocked.
Pushed my working tree to GitHub and will keep working on it...
https://github.com/mightysween/android_device_motorola_payton
Been looking at Pixel 2 TWRP Alpha... holy cow. So much more to it with this partitioning scheme.
mightysween said:
Well, my boot.img compiles fine... but will not boot to recovery. Given the fact that it is mostly guesswork on the device tree, I am not shocked.
Pushed my working tree to GitHub and will keep working on it...
https://github.com/mightysween/android_device_motorola_payton
Been looking at Pixel 2 TWRP Alpha... holy cow. So much more to it with this partitioning scheme.
Click to expand...
Click to collapse
Have not even peeked into the Pixel 2 forums. I'm afraid this seems to be another ballgame entirely. Do the new Pixel owners even have root passing safety net while allowing these security updates new android phones now get? Gah this is a mess
SR3TLAW said:
Have not even peeked into the Pixel 2 forums. I'm afraid this seems to be another ballgame entirely. Do the new Pixel owners even have root passing safety net while allowing these security updates new android phones now get? Gah this is a mess
Click to expand...
Click to collapse
TWRP has been worked on for Pixel2 by several people, including expert Dees Troy, and is still a heavy alpha. I feel pretty good about booting compiled boot images and not bricking on x4 (as far as I have gotten)
I have been compiling my own stuff for many years, and yes -- this new stuff is foreign. But, we will all learn and in a few weeks/months, there will be plenty of action on this device
mightysween said:
TWRP has been worked on for Pixel2 by several people, including expert Dees Troy, and is still a heavy alpha. I feel pretty good about booting compiled boot images and not bricking on x4 (as far as I have gotten)
I have been compiling my own stuff for many years, and yes -- this new stuff is foreign. But, we will all learn and in a few weeks/months, there will be plenty of action on this device
Click to expand...
Click to collapse
try using fixes from https://github.com/TeamWin/android_device_xiaomi_tissot tree. similar android one device!!
i.snehal.kiran said:
try using fixes from https://github.com/TeamWin/android_device_xiaomi_tissot tree. similar android one device!!
Click to expand...
Click to collapse
Thanks, picked up 3 changes from here already... will test them out soon!
So, I have checked out several XDA threads on this Xiaomi device (tissot) and I think it is going to help quite a bit with the A/B issues.
I am still, unfortunately stuck on getting TWRP to boot. Boot.img compiles fine and I can extract it and see TWRP has replaced stock recovery in the ramdisk, but it will not boot into recovery.
Ideally, we need a way to boot a TWRP image without flashing anything... easier said than done with devices that have recovery baked into the boot image. But once that works, we can extract just the ramdisk from my build and write a script to patch it into the stock boot image from the temporary TWRP running on the device.
Progress! New TWRP thread coming soon...
BTW, there is still a long way to go here... this was just a rudimentary test to get TWRP to boot. Need to start totally fresh with partitions before there is any attempt to actually use it!
Also -- my build environment is a total cluster after weeks of messing around. I need to wipe it and start over. That alone will take me a few days, and TWRP might take a few weeks more.
Incredible! Looking forward to having a custom recovery!
mightysween said:
Progress! New TWRP thread coming soon...
BTW, there is still a long way to go here... this was just a rudimentary test to get TWRP to boot. Need to start totally fresh with partitions before there is any attempt to actually use it!
Also -- my build environment is a total cluster after weeks of messing around. I need to wipe it and start over. That alone will take me a few days, and TWRP might take a few weeks more.
Click to expand...
Click to collapse
I hope later we can flash the Android One firmware on the retail Moto X4, I supose that OTA update will not work but at least we will have the lastest updates if someone make a flashable version
f3r.and0 said:
I hope later we can flash the Android One firmware on the retail Moto X4, I supose that OTA update will not work but at least we will have the lastest updates if someone make a flashable version
Click to expand...
Click to collapse
At the very least, we have the ability to create "nandroid" style backup from A1 device. Theoretically, that could allow anyone to install it...
But yes, in the long run, hopefully the actual firmware is released
mightysween said:
At the very least, we have the ability to create "nandroid" style backup from A1 device. Theoretically, that could allow anyone to install it...
But yes, in the long run, hopefully the actual firmware is released
Click to expand...
Click to collapse
Doesn't the nandroid (or for that matter Flashfire) backup contain personally unique identifiers?
DiDGR8 said:
Doesn't the nandroid (or for that matter Flashfire) backup contain personally unique identifiers?
Click to expand...
Click to collapse
Yes, technically... obviously would need to start with a fresh system and limit to non-data partitions.
No one needs to restore someone else's apps... just their boot/oem/system_image
mightysween said:
Yes, technically... obviously would need to start with a fresh system and limit to non-data partitions.
No one needs to restore someone else's apps... just their boot/oem/system_image
Click to expand...
Click to collapse
This just came to my mind, since this phone has 2 partitions for boot etc. --
Code:
mmcblk0p44: boot_a SIZE:65536 blocks
mmcblk0p45: boot_b
can't we make backup of boot_b ? it will be same as boot_a but unmodified i think ? i mean, use magisk/cf-autoroot/whatever to gain root on boot_a. and make backup of boot_b. so in case if we want to receive update, just restore back boot_b.img to boot_a slot and update through ota ? that way we can practically make full backup which is unmodified. ofc this is until we have fastboot image available and working TWRP.
also it seems all x4's are having same kernel according to this thread. although their build time is different.
I might have found a quick and dirty Method to Port TWRP to the newest 7.2 shield experience. It's not guaranteed, but it's a chance im going to try. But as I didn't upgraded my own shield yet, I need some files from someone who has rooted his shield already.
1. Is an recovery.img
2. The build.prop
If I can get hands on these files I might be able to bring up a testing version asap
Enough. Seriously.....
Keep it clean, and on-topic... The rules are there for a reason. Don't remember them? HERE you go.
Adromir said:
I might have found a quick and dirty Method to Port TWRP to the newest 7.2 shield experience. It's not guaranteed, but it's a chance im going to try. But as I didn't upgraded my own shield yet, I need some files from someone who has rooted his shield already.
1. Is an recovery.img
2. The build.prop
If I can get hands on these files I might be able to bring up a testing version asap
Click to expand...
Click to collapse
If you want the files
Then can you please update your Sheild tv to the latest firmware for us 7.2.2
An back up the recovery.img
An back up your build.prob
Because I can't help you! I refuse!
Thx again have a great day
i hope you can port the twrp to nvidia sheild tv thx
Foster_e (Shield TV 2015 16GB) - 7.2.2 (30.7.130.7)
recovery.img + build.prop
https://drive.google.com/open?id=18E_u8as1E9dstmRtRwPb97hALdmsrdsc
The recovery is dumped directly from
Code:
/dev/block/platform/sdhci-tegra.3/by-name/SOS -> /dev/block/mmcblk0p16
No offense but quick and dirty does not do it on the new kernel.
You can port as much as you like and it might work for the older models but certainly not for the 2017 model.
And if you have no clue how to get the required files by simply exctracting the firmware files that you can download then I wonder how you will be able to actually modify the recovery image.
People with quite some experience tried and failed, so unless you compile TWRP from source he proper way it won't work (at least not on the 2017).
And even if compiled correctly there is no garantee it will be usable with the secure boot restrictions still in place.
You need a fully rooted device to fully use TWRP and you can not root the 7.2 in the simple way anymore.
Fully rooted the normal TWRP will work just fine.
Downunder35m said:
No offense but quick and dirty does not do it on the new kernel.
You can port as much as you like and it might work for the older models but certainly not for the 2017 model.
And if you have no clue how to get the required files by simply exctracting the firmware files that you can download then I wonder how you will be able to actually modify the recovery image.
People with quite some experience tried and failed, so unless you compile TWRP from source he proper way it won't work (at least not on the 2017).
And even if compiled correctly there is no garantee it will be usable with the secure boot restrictions still in place.
You need a fully rooted device to fully use TWRP and you can not root the 7.2 in the simple way anymore.
Fully rooted the normal TWRP will work just fine.
Click to expand...
Click to collapse
So if I understand you correctly the only way that a recent version of TWRP would work on 7.21 and above are if you have a "rooted" developer image? I have stayed with 7.1 (rooted with a flashed TWRP recovery) My expectation is that Ill stay with it until a stable version is released.
Odd thing is every OTA notification I get refuses to install. It just boots to TWRP without updating. I even opted in for the 7.2.2 beta updates and the shield refuses to update. Kinda thankful as others seem to have so many issues, just not worth it until 7.3 is released perhaps?
Any decent update is worth applying.
But if you ask if it is worth it for those really needing full root access then the answer is no.
The cummunity behind the shield might not be as big as behing Samsung devices but I am sure something will be figured out sooner or later.
@Downunder35m : As I mentioned in a deleted Post, I know how to get these Files from the recovery images. But they are Still 7.2.1 and as 7.2.2 already I didn't see a point in starting with already Outdated Files.
What kind of Things have you been trying already? My Approach was, that maybe TWRP hangs itself, because it can't find the Vendor and system Partition. After unpacking the recovery.img i found out, that the partitions still get mounted, but not over over the fstab anymore but single commands in some init scripts. So my Idea was to patch the kernel of the recovery image with a proper fstab and then use that to build a twrp around it, with the modified boot image. But sadly the resulting TWRP exceeded the Partitionsize. But i didn't set up the Source Tree to compile correctly, because I assumed that with such a breaking approach nvidia did at least moved onward to Android 8.1 ..
A real life job sadly limits my time far more than what I would like.
So maybe my failures are of use to you...
Lets start with the basics:
(All for the 2017 model!)
Firstly, the bootloader has changed and now enforces basically everything Google has on offer.
This means you can not just boot into a custom recovery because the bootloader does not accept it as genuine.
Lets say you get around this problem by, dor example, compiling TWRP from source and with the not yet realesed NVidia 7.2 sources.
There might be other ways but right now I think we can't get around compiling it from scratch.
Once you are able to somehow properly boot into TWRP there is more problems:
A lot if not all special rights and permissions are now handled almost exclusively by the DTB, or to be precise the DTS, which is compiled during boot.
By default TWRP does not make any use of the DTB but instead relies only on the FSTAB configuration.
And since TWRP is not an authorised service, task or app the bootloader won't provide the required rights.
The system partition stays invisible, the vendor part locked and since TWRP is required to copy or store at least some things somewhere this is detected as a possible intrusion.
As that the bootloader now marks the entire system as compromised - the dreaded corrupted system message appears and the system fails to boot.
You could tweak the init files, get the complete FSTAB info from the plat - and nonplat_file_contexts and even fiddle with the rest.
Then you get this happy feeling of a booting TWRP, pull a backup and think all is fine.
That it until you try to reboot and nothing works anymore.
The backup is useless as firstly you can not write it back and secondly it will be encrypted or otherwise corrupt.
To be able to use TWRP ADBD must be able to run in root mode, this is not possible by default on a user or release build, which NVidia now provides as a "developer" firmware.
A bootloader set to enforce all SeLinux and DM-Verity funtions will not allow any vital modifications to any vital part of the system.
In theory you must first at least free the bootloader (we can not do that) or destroy the safety, like by using a modified DTB.
Then you must make sure that you modifiy the prop files so full ADB and ADBD rights are available where they are needed.
After that TRWP will run just fine but it creates a cricle that first needs to be broken somehow
No root rights means no TWRP, no TWRP means no mods to the system.
Magisk currently fails to help us as it does not make use of DTB features at this stage.
And if you ask me then messing with the DTB can backfire badly.
Unlike normal firmwares we won't get a DTB partition included in the boot image or kernel image.
So once the dTB is stuffed too much it will be hard to impossible to install a genuine or custom firmware.
Once Pie comes out this will be worse.
Here the DTB too will be protected and generated/checked during boot.
Unless NVidia wakes up and removes these restrictions from the developer firmwares we will be locked out until someone finds a way to restore full root rights.
Right now I am hopin they will still release the full sources one day.
With a massive effors one could then just compile a normal userdebug firmware and all is fine once more.
Any luck yet? I upgraded one of my Shield TV to 7.2.2 from 7.2.1 dev root and want to install Magisk....
Thanks!
Here you go TWRP recovery for Shield TV 2017 running 7.2.3
UPDATE: Boots but not working correctly so removed links
leezaal said:
Here you go TWRP recovery for Shield TV 2017 running 7.2.3
https://www.androidfilehost.com/?fid=6006931924117905072
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
Here you go TWRP recovery for Shield TV 2017 running 7.2.3
https://www.androidfilehost.com/?fid=6006931924117905072
Click to expand...
Click to collapse
Every time i open recovery it works, but after trying to reboot it bootloops at nvidia. I flash-all and it works again until i enter recovery (then botloops again on reboot). Am i missing something? (shield 2017 7.2.3 dev edition)
Here's twrp 3.3.1-0 for Shield TV. It seems to work properly on my shield pro running 7.2.3, I was able to flash magisk with it, but I don't have the 2017 model to test on. Please let me know how it works and report any errors in as detailed a manner as possible. As ever, this is experimental and you flash at your own risk :good:
https://drive.google.com/file/d/1BCfXg9pUpFm_3sPXp_nEwBlkNU9nelkg/view?usp=sharing
rootfan said:
Here's twrp 3.3.1-0 for Shield TV. It seems to work properly on my shield pro running 7.2.3, I was able to flash magisk with it, but I don't have the 2017 model to test on. Please let me know how it works and report any errors in as detailed a manner as possible. As ever, this is experimental and you flash at your own risk :good:
https://drive.google.com/file/d/1REnehReTaA5BamUBDe8XmBMyZG6zQkFB/view?usp=sharing
Click to expand...
Click to collapse
there is always the bug for 4k screen display?
rootfan said:
Here's twrp 3.3.1-0 for Shield TV. It seems to work properly on my shield pro running 7.2.3, I was able to flash magisk with it, but I don't have the 2017 model to test on. Please let me know how it works and report any errors in as detailed a manner as possible. As ever, this is experimental and you flash at your own risk :good:
https://drive.google.com/file/d/1REnehReTaA5BamUBDe8XmBMyZG6zQkFB/view?usp=sharing
Click to expand...
Click to collapse
Many thanks i renamed this to recovery.img and renamed magisk boot img to boot.img reflashed both as part of the whole 7.2.3 dev OS shield tv 2017 image.
booted into TWRP via adb from my pc it loads up fine on my LG 43" 4k tv no problem rebooted and got back into 7.2.3 also without any issues
UPDATE: TWRP will not let me wipe system / data or anything else or mount any partitions in order to wipe before trying to install anything making this sadly kinda useless right now
twrp seems complicated to be functional lately, the same on my mi max 3, but orange Fox might be better on Shield
leezaal said:
UPDATE: TWRP will not let me wipe system / data or anything else or mount any partitions in order to wipe before trying to install anything making this sadly kinda useless right now
Click to expand...
Click to collapse
Well that makes sense because I was overwriting the emmc fstab with the sata one. I've updated my original post with a link to a new twrp that should have this problem fixed. If you're still having issues please click on the menu button to the right of the home button in twrp and tell me what the log says. Do this when first booting into twrp before doing anything else. It should say something like the following with no mounting complaints if everything is working right.
Shield Debug: Hardware variant is darcy
Shield Debug: Using emmc fstab
Shield Debug: Found required fstab
rootfan said:
Well that makes sense because I was overwriting the emmc fstab with the sata one. I've updated my original post with a link to a new twrp that should have this problem fixed. If you're still having issues please click on the menu button to the right of the home button in twrp and tell me what the log says. Do this when first booting into twrp before doing anything else. It should say something like the following with no mounting complaints if everything is working right.
Shield Debug: Hardware variant is darcy
Shield Debug: Using emmc fstab
Shield Debug: Found required fstab
Click to expand...
Click to collapse
Thanks for the great feedback will DL the updated TWRP and give it a go will report back shortly
UPDATE: 100% working ! Amazing work all partitions mount etc no problem FULLY working TWRP on my 4k TV too
I can't restore android in my tab s7 T-875 4G to old version
please help me
Almgrm2008 said:
I can't restore android in my tab s7 T-875 4G to old version
please help me
Click to expand...
Click to collapse
You won't be able to downgrade the normal way (via Odin) if you have upgraded to BUC1 or later.
Samsung incremented rollback protection at that point.
EDIT: The actual version number varies depending on model. It's the March security update, which I think for S7 (non-plus) would be BUC6.
LSS4181 said:
You won't be able to downgrade the normal way (via Odin) if you have upgraded to BUC1 or later.
Samsung incremented rollback protection at that point.
EDIT: The actual version number varies depending on model. It's the March security update, which I think for S7 (non-plus) would be BUC6.
Click to expand...
Click to collapse
Is it possible that there is no way to go back to an older version
Almgrm2008 said:
Is it possible that there is no way to go back to an older version
Click to expand...
Click to collapse
If you're not rooted, well, there really is no way back without voiding your warranty.
If you're rooted (warranty already voided), you might be able to dd the individual partitions inside super (after extracting them using lpunpack), if you use Ian's TWRP. I only did this for getting GSI to work, and I did not test if it's possible to boot an earlier stock image this way post-increment.
LSS4181 said:
If you're not rooted, well, there really is no way back without voiding your warranty.
If you're rooted (warranty already voided), you might be able to dd the individual partitions inside super (after extracting them using lpunpack), if you use Ian's TWRP. I only did this for getting GSI to work, and I did not test if it's possible to boot an earlier stock image this way post-increment.
Click to expand...
Click to collapse
Where can I find the Ian TWRP file for my device?
Almgrm2008 said:
Where can I find the Ian TWRP file for my device?
Click to expand...
Click to collapse
You may have to check the thread. Actually it's mainly for the S7 Plus (T976B).
From what I remember, back then there were few testers for the non-Plus S7 (T875) so the progress was limited at that time.
At present, it was reported to be working on T875, but the display were corrupted so you can only use the adb shell. I don't know how to make nandroid backups entirely from command line but for flashing the individual partitions via dd, the adb shell should be enough.
LSS4181 said:
You may have to check the thread. Actually it's mainly for the S7 Plus (T976B).
From what I remember, back then there were few testers for the non-Plus S7 (T875) so the progress was limited at that time.
At present, it was reported to be working on T875, but the display were corrupted so you can only use the adb shell. I don't know how to make nandroid backups entirely from command line but for flashing the individual partitions via dd, the adb shell should be enough.
Click to expand...
Click to collapse
Did you explain to me how?
Almgrm2008 said:
Did you explain to me how?
Click to expand...
Click to collapse
For TWRP I think you can just ask in the Telegram group (in Ian's TWRP thread).
I don't recommend flashing the stock Android 10 using the dd method, as I cannot assess what would be needed to get old Android 10 system working in your current state. In case there are some other rollback protections aside from the bootloader (I don't know), you risk bricking your device for good.
I've a thread in the guide section on how to flash GSI (credits to everyone who helped me getting everything working), and you can find how to use dd to flash system and vendor there. Again, it's only for GSI and I don't really think it's a good idea to flash older stock FW this way.
Will a previous version of Android backup TWRP work to restore on Target tab S6 currently running Android 12 4.1
but why do you want to down grade is there any performance problem i want to know because I am running the older version and I was considering to update .
Hi
Is there anyone here who could explain the P20 lite boot process (for stock) and exactly what modifications are needed for a custom ROM to boot properly? Specifically, how are the kernel and recovery_ramdisk partitions used, and at what points do other partitions get mounted, etc, as well as what is needed if one wants to deviate in some way from the standard sequence.
Any help would be much appreciated!
Thank you,
aribk
aribk said:
Is there anyone here who could explain the P20 lite boot process (for stock)
Click to expand...
Click to collapse
All the stages of the boot process are probably the same as with Android, the interface probably doesn't play any role there. IMO ).
aribk said:
exactly what modifications are needed for a custom ROM to boot properly?
Click to expand...
Click to collapse
it depends on the type of custom ROM (ported, sGSI, GSI etc.). and on the user's requirements.
OK.
Well, at some point last year someone (maybe you?) mentioned that it was important not to format the data partition on this device. Is that correct? And if so, why?
aribk said:
maybe you?
Click to expand...
Click to collapse
I mentioned that doing 'data format' (running stock EMUI 9, not custom ROM) with incompatible (not modified) TWRP 3.4.0 and above can brick our device.
It is also not recommended to do Factory reset in TWRP on Huawei devices, it can cause permanent problems.