Related
Hi, guys!
Here's updated version of TWRP
Features:
Supports USB OTG, so you can use USB flash drive as external storage for backups, zip installations.
Added feature to make backup of internal storage.
Combined with stock EMUI 3.1 recovery. In case of power-on by holding power + vol+ or rebooting into recovery by command or any 3rd part application: will boot in TWRP. In case of local update, OTA-update, "force update" (3buttons method) or factory reset from menu: will boot into EMUI recovery.
Off-mode charger updated from EMUI 3.1 (for 4.4.2)
custom.bin and cust symlinks are saved/restored (if they were exist) in case of Wipe/Format Data. So there is not gonna be "cust" issues after factory reset in TWRP.
Excluded SuperSu from build.
Included support of crypted data.
Screen lock replaced with screen off at power button.
Requirements:
Unlocked bootloader
Android 4.4.2 - 5.1.1
Known bugs:
Because internal storage is not a separate block device and just a subfolder of "userdata" partition, before you can make backup/restore of internal storage, first you should do Mount -> Data. Otherwise you will get error, saying that TWRP can't mount "storage". So don't bother if you'll see this error.
Installation:
Reboot in fastboot mode
Flash image via fastboot
Code:
fastboot flash recovery TWRP_MT2-3.0.0-0.img
fastboot reboot
From TWRP: Press "Install" and select zip-archive
Download: TWRP_MT2-3.0.0-0.img
For TWRP: TWRP_MT2-3.0.0-0.zip
Older version: TWRP_MT2-2.8.1.0.img
Kostyan_nsk said:
Hi, guys!
I've built TWRP for MT2-C00 by request, so I would like to share it with you.
It works also on L05 because it's on the same SoC.
Download: TWRP_MT2-2.8.1.0.img
Requirements:
Unlocked bootloader
Android 4.4.2
Installation:
Reboot in fastboot mode
Flash image via fastboot
Code:
fastboot flash recovery TWRP_MT2-2.8.1.0.img
fastboot reboot
Known issues: I don't know because I'don't have a device and didn't test it by myself.
Click to expand...
Click to collapse
Thank you very much !
I have flashed this onto my MT2-L05 using flashify from the Playstore ( because i'm lazy, lol ) and can confirm that it appears to work perfectly on 4.4.2 b606 EMUI 3.0 rom.
I had no problem booting into TWRP or making a backup. I will attempt to restore my data later to make sure it's working 100% as it should. Excellent work and thanks again !
How did you root your phone ?? I have same model on EMUI 3.0
That is good that the two devices are on the same SoC however I have a relatively important question to ask. Do both the L05 and C00 models contain the same partition layouts? For example, lets say, hypothetically speaking, that the boot partition for device one was mmcblk0p20, then would device two be equal to that and following through with the other partitions as well? Most newer model phones these days will use the "by name" scheme which is in lamen terms just a mere variable that directs to the actual value stored to that variable in which always points to the correct location as it should. So my next question would be, does the device tree include these "by names" variables?
Merely asking this so as to clear the air with less in experience users as to prevent any future complications as well as a better understanding.
Modding.MyMind said:
So my next question would be, does the device tree include these "by names" variables?
Merely asking this so as to clear the air with less in experience users as to prevent any future complications as well as a better understanding.
Click to expand...
Click to collapse
Yes, partitions are mounted via "by-name".
Kostyan_nsk said:
Yes, partitions are mounted via "by-name".
Click to expand...
Click to collapse
Outstanding! One more question. Are the partition sizes for both devices identical? If not, then it would not be safe to use this TWRP build for both devices but presumably only for the C00 model given that it was initially built based on it's structure. Appreciate your timely response
Modding.MyMind said:
Outstanding! One more question. Are the partition sizes for both devices identical? If not, then it would not be safe to use this TWRP build for both devices but presumably only for the C00 model given that it was initially built based on it's structure. Appreciate your timely response
Click to expand...
Click to collapse
I can confirm that the this recovery works perfectly on MT2-L05.
I have used it to back up and restore system, boot and data partitions and it's worked flawlessly every time.
modding.mymind said:
outstanding! One more question. Are the partition sizes for both devices identical? If not, then it would not be safe to use this twrp build for both devices but presumably only for the c00 model given that it was initially built based on it's structure. Appreciate your timely response
Click to expand...
Click to collapse
The only place where size of partitions is defined is BoardConfig.mk, owners of L05 can compare them with their own.
BOARD_BOOTIMAGE_PARTITION_SIZE := 16777216
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 16777216
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 1610612736
BOARD_USERDATAIMAGE_PARTITION_SIZE := 12790530048
Click to expand...
Click to collapse
But I didn't notice that these variables somehow related to TWRP. For example, there is not defined size of 'cust' partition, but TWRP makes backup of it or some other partition placed in twrp.fstab successfully.
TWRP has its own methods of determinig size of partitions, so do you have any proves that it could be unsafe to use for L05 if partition's sizes are not identical?
I'm just curios what your suggestions are based on?
4L0M said:
I can confirm that the this recovery works perfectly on MT2-L05.
I have used it to back up and restore system, boot and data partitions and it's worked flawlessly every time.
Click to expand...
Click to collapse
I'm sure it does and I appreciate the reply back. Glad to here it actually. I merely asked because in any given device tree used to build from source, twrp in this case, you must determine the used partitions and their sizes and allocate that information towards the boardconfig.mk file. I own a K2_CL as well and there are also three other models to that variant. All of which are on the same SoC, but not only are their partition layouts different but so are their partition sizes. Having said that, it could cause problems should the improper TWRP be used in this case. For example, if you were to use TWRP to say, wipe your data partition and reformat it, but the sizes for the data partition were different from each other then you would literally be resizing your partition where it be smaller or larger than before. Even more so, say it were to enlarge it, then by doing so, it could presumably crash the phone since any given device is given but only so much space unless it were to be intentionally manipulated which is far outside of this discussion.
Modding.MyMind said:
I'm sure it does and I appreciate the reply back. Glad to here it actually. I merely asked because in any given device tree used to build from source, twrp in this case, you must determine the used partitions and their sizes and allocate that information towards the boardconfig.mk file. I own a K2_CL as well and there are also three other models to that variant. All of which are on the same SoC, but not only are their partition layouts different but so are their partition sizes. Having said that, it could cause problems should the improper TWRP be used in this case. For example, if you were to use TWRP to say, wipe your data partition and reformat it, but the sizes for the data partition were different from each other then you would literally be resizing your partition where it be smaller or larger than before. Even more so, say it were to enlarge it, then by doing so, it could presumably crash the phone since any given device is given but only so much space unless it were to be intentionally manipulated which is far outside of this discussion.
Click to expand...
Click to collapse
Take a look at TWPartition::Wipe_EXT4() function
Kostyan_nsk said:
Take a look at TWPartition::Wipe_EXT4() function
Click to expand...
Click to collapse
Just got off of work. Decided to take a look at partitions.cpp and I am seeingng what you are pointing out. Will take a closer look at.
Meanwhile, decided to to look elsewhere and realized in some ways I should correct myself. Ultimately depends if the devices kernel supports "by-names" or not, which the K2 variants unfortunately do not. Though can easily be added.
In addition, the sizes in BoardConfig.mk are used by the compiler to ensure that the boot.img, recovery.img, etc that it produces are not too large for the partition on your device.
Been a fun learning and refreshing discussion . Enjoyed it lol.
didn't work on my phone
well, i tried this recovery on my device. Its MTL2-L05 and it didn't work. Tried to reboot into recovery but the phone just restarted after an attempt to boot into recovery.
mawais15 said:
well, i tried this recovery on my device. Its MTL2-L05 and it didn't work. Tried to reboot into recovery but the phone just restarted after an attempt to boot into recovery.
Click to expand...
Click to collapse
The reason being, you haven't unlocked your bootloader I reckon. The recovery works perfectly on MT2-L05, on firmware b606 4.4.2
4L0M said:
The reason being, you haven't unlocked your bootloader I reckon. The recovery works perfectly on MT2-L05, on firmware b608 4.4.2
Click to expand...
Click to collapse
My Android version is also 4.2.2. So this makes sense why it's not working. Is there a way to upgrade my o's to 4.4.2?
mawais15 said:
My Android version is also 4.2.2. So this makes sense why it's not working. Is there a way to upgrade my o's to 4.4.2?
Click to expand...
Click to collapse
What is the exact wording on your phone in Settings-About Phone-Build Number?
mawais15 said:
My Android version is also 4.2.2. So this makes sense why it's not working. Is there a way to upgrade my o's to 4.4.2?
Click to expand...
Click to collapse
Read requirments carefully in the first post.
Won't work on 4.2.2
4L0M said:
What is the exact wording on your phone in Settings-About Phone-Build Number?
Click to expand...
Click to collapse
Screenshot attached plz
Kostyan_nsk said:
Read requirments carefully in the first post.
Won't work on 4.2.2
Click to expand...
Click to collapse
is there any way i can upgrade it to 4.2.2 or any other method to root my version??
mawais15 said:
is there any way i can upgrade it to 4.2.2 or any other method to root my version??
Click to expand...
Click to collapse
You mean downgrade TWRP? As to allow it to work while on 4.2.2? Assuming the partition layout isn't different from the android OS's on your device then you can literally just unpack your stock recovery image "take note of the configurations used to rebuild it" then unpack this TWRP build and swap out the kernel binary from the TWRP build with the one from your stock recovery image. Then using the build configurations you should have taken note of, simply rebuild the custom recovery image and flash it to your recovery partition. This will resolve your issues as an unethical but temporary solution.
Modding.MyMind said:
You mean downgrade TWRP? As to allow it to work while on 4.2.2? Assuming the partition layout isn't different from the android OS's on your device then you can literally just unpack your stock recovery image "take note of the configurations used to rebuild it" then unpack this TWRP build and swap out the kernel binary from the TWRP build with the one from your stock recovery image. Then using the build configurations you should have taken note of, simply rebuild the custom recovery image and flash it to your recovery partition. This will resolve your issues as an unethical but temporary solution.
Click to expand...
Click to collapse
I wish i were that good at development stuff to understand your post but sure thanks for trying to help
The problem is i don't know where to get my stock recovery image first. which is the first step in your suggestions..
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.
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?
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
morpheus______ said:
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
Click to expand...
Click to collapse
Hello! Thx for posting this info. I have a few of questions. Can you post a simple set of instructions on how to apply this root? I have never rooted a Nubia device before but I want to root this. Will the flashing of the boot image require the bootloader unlock? Might you know if the viper4Android is working from the modules install in magisk? Thx in advance for any info you may be able to provide!
RngrYogi said:
Hello! Thx for posting this info. I have a few of questions. Can you post a simple set of instructions on how to apply this root? I have never rooted a Nubia device before but I want to root this. Will the flashing of the boot image require the bootloader unlock? Might you know if the viper4Android is working from the modules install in magisk? Thx in advance for any info you may be able to provide!
Click to expand...
Click to collapse
Also using your method would it require a user data wipe?
RngrYogi said:
Also using your method would it require a user data wipe?
Click to expand...
Click to collapse
yes, of course. it's like any standard boot loader unlocked. Which is why you do it first thing when you get the device.
Edit: I didn't see the question how to apply it -
just OEM unlock the device, and then
adb reboot bootloader
(wait for it too boot to boot loader)
fastboot flashing unlock
(accept unlocking voiding warranty, etc by pressing volume down and power)
fastboot flash boot <the boot.img>
Note that they don't recognize "fastboot boot" , which is my favorite way of rooting since it leaves the original image intact - and thus flashing is irreversible unless you get the stock OTA at a later time and flash it over. But this will not bring back the warranty and warnings.
morpheus______ said:
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
Click to expand...
Click to collapse
greetings bro thanks for sharing the vbmeta.img file? didn't you use it?
few questions:
1. were did you find the stock firmware to pull the clean boot.img? Can you link it, I would like to have a backup if anything goes wrong
2. Is the patched boot.img for the North American Version?
So to lpedrot: Didn't need a vbmeta.
To superrama: Since it's the kernel, the CN/US/etc versions don't matter. That's handled at a much higher level of Android build, which is user mode. So same boot.img can be used anywhere (which btw is true in all cases - boot.img s only have kernel + Ramdisk anyway)
1. I found the original by looking for NX679 OTA . It was a rather large OTA payload.bin, which I used my imjtool to unpack the boot.img from. Don't have the link handy now, but I can probably dig up the payload.bin and put it in a link since I have it stored somewhere.
morpheus______ said:
So to lpedrot: Didn't need a vbmeta.
To superrama: Since it's the kernel, the CN/US/etc versions don't matter. That's handled at a much higher level of Android build, which is user mode. So same boot.img can be used anywhere (which btw is true in all cases - boot.img s only have kernel + Ramdisk anyway)
1. I found the original by looking for NX679 OTA . It was a rather large OTA payload.bin, which I used my imjtool to unpack the boot.img from. Don't have the link handy now, but I can probably dig up the payload.bin and put it in a link since I have it stored somewhere.
Click to expand...
Click to collapse
nice, thanks for the quick reply
morpheus______ said:
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
Click to expand...
Click to collapse
On which rom you use it? Aparently its taken out from a Ianuary rom, latest being v2.32 afaik
Just whichever random firmware image I found. But you're overlooking one major thing which is - the kernel barely, if at all, changes between firmware versions . You can use this book image with any other firmware image of any date, earlier or later, and there's no reason why it wouldn't work. The Android OTA images are user mode, this is just the kernel + Ramdisk - and so are largely independent of each other. Only exception would be if there's some kernel vulnerability in that particular version of the kernel, which as far as we know now - there isn't.
Hi, thanks for the guide. I did the steps to unlock bootloader and do flash your provided boot.img.
They both worked successfully but not sure if the boot img did anything.
I have the chinese phone and I want to convert it to global. Going to the settings and choosing the local update file provided by the official website doesn't work.
Any tips?
LeonFresh said:
Hi, thanks for the guide. I did the steps to unlock bootloader and do flash your provided boot.img.
They both worked successfully but not sure if the boot img did anything.
I have the chinese phone and I want to convert it to global. Going to the settings and choosing the local update file provided by the official website doesn't work.
Any tips?
Click to expand...
Click to collapse
”we” have a telegram channel for RM7 users, join since most of them don't use XDA anymore and you'll get faster help here
D1stRU3T0R said:
”we” have a telegram channel for RM7 users, join since most of them don't use XDA anymore and you'll get faster help here
Click to expand...
Click to collapse
Rooting != Image locale change. To do an image locale change you need to get the device image for whichever locale you want (if you can find it) and then apply the usual Magisk method.
D1stRU3T0R said:
”we” have a telegram channel for RM7 users, join since most of them don't use XDA anymore and you'll get faster help here
Click to expand...
Click to collapse
Hi I just joined the TG but got banned any chance of unbanning me?
User is Indiana_Gems on TG I'm looking to change my RM7 CN to global
morpheus______ said:
Rooting != Image locale change. To do an image locale change you need to get the device image for whichever locale you want (if you can find it) and then apply the usual Magisk method.
Click to expand...
Click to collapse
Thanks, I thought the two was related. I can't find any of the img files, which is why I'm stuck I guess. For older versions of the phone like Red Magic 5 they exist.
If they don't exist, is there a process to make one? Or do I have to wait
LeonFresh said:
Thanks, I thought the two was related. I can't find any of the img files, which is why I'm stuck I guess. For older versions of the phone like Red Magic 5 they exist.
If they don't exist, is there a process to make one? Or do I have to wait
Click to expand...
Click to collapse
There is a long and painful process to make one, and it's not guaranteed to work. I'll explain:
If a given vendor (in our case, Nubia, but this applies to others as well) adheres to Google's specification their /system partition should effectively be identical to that of all other Android devices (of same version). The vendor is supposed to put the BSP or ODM specific files in /system_ext, /vendor, /product and /odm.
The language, in this case, is just a locale setting, and several other "overlay" files (which supersede those in /system) laid out in the vendor/odm/product partitions. The problem here is that all these partitions will A) differ by vendor B) be read/only and DM-verity enabled.
Thus, it would take going over the vendor's overlay files and locale settings, and changing every one. Impractical.
You're better off just going in the language settings and setting en_US, and working from there. Even on non-rooted device, you can always adb install any app you want.
morpheus______ said:
There is a long and painful process to make one, and it's not guaranteed to work. I'll explain:
If a given vendor (in our case, Nubia, but this applies to others as well) adheres to Google's specification their /system partition should effectively be identical to that of all other Android devices (of same version). The vendor is supposed to put the BSP or ODM specific files in /system_ext, /vendor, /product and /odm.
The language, in this case, is just a locale setting, and several other "overlay" files (which supersede those in /system) laid out in the vendor/odm/product partitions. The problem here is that all these partitions will A) differ by vendor B) be read/only and DM-verity enabled.
Thus, it would take going over the vendor's overlay files and locale settings, and changing every one. Impractical.
You're better off just going in the language settings and setting en_US, and working from there. Even on non-rooted device, you can always adb install any app you want.
Click to expand...
Click to collapse
morpheus______ said:
There is a long and painful process to make one, and it's not guaranteed to work. I'll explain:
If a given vendor (in our case, Nubia, but this applies to others as well) adheres to Google's specification their /system partition should effectively be identical to that of all other Android devices (of same version). The vendor is supposed to put the BSP or ODM specific files in /system_ext, /vendor, /product and /odm.
The language, in this case, is just a locale setting, and several other "overlay" files (which supersede those in /system) laid out in the vendor/odm/product partitions. The problem here is that all these partitions will A) differ by vendor B) be read/only and DM-verity enabled.
Thus, it would take going over the vendor's overlay files and locale settings, and changing every one. Impractical.
You're better off just going in the language settings and setting en_US, and working from there. Even on non-rooted device, you can always adb install any app you want.
Click to expand...
Click to collapse
Thanks for the details!
Is it impractical in terms of technical perspective , or is it just tedious to do? And do you think it will be released in future?
The reason I want to switch is that there are bugs mostly related to the google assistant. It resetting my settings like on default voice assistant app. It doesn't have ok google detection, sometimes doesn't open at all.
If that can be fixed maybe I can stay on CN rom, but honestly there's a lot of random bugs, it not only resets default apps for assistant but other apps too like fluid navigation gestures (FNG) app.
LeonFresh said:
Thanks for the details!
Is it impractical in terms of technical perspective , or is it just tedious to do? And do you think it will be released in future?
The reason I want to switch is that there are bugs mostly related to the google assistant. It resetting my settings like on default voice assistant app. It doesn't have ok google detection, sometimes doesn't open at all.
If that can be fixed maybe I can stay on CN rom, but honestly there's a lot of random bugs, it not only resets default apps for assistant but other apps too like fluid navigation gestures (FNG) app.
Click to expand...
Click to collapse
Hello. Have you found a solution to the problem? I also do not flash, says the version for the firmware is not suitable.
Morrovoker said:
Hello. Have you found a solution to the problem? I also do not flash, says the version for the firmware is not suitable.
Click to expand...
Click to collapse
Not yet, I guess we just have to wait
LeonFresh said:
Not yet, I guess we just have to wait
Click to expand...
Click to collapse
any news yet i wanna switch from global to cn lol