Related
Dear all,
Here is a tutorial to unlock meizu E3 without any malicious software.
The idea is to edit frp partition and make the fastboot flashing unlock pass the security check.
Please note below might damage your phone so do it as your own risk, i do not responsible to any damage made.
Detail step:
(1)get root access
(2)install terminal emulater app
(3)dump frp partition
(4)modify frp by hex editor at offset 7fff8 and 7fff to 1 (not sure 7fff8 or 7ffff take the effect, so i edit both) as frp1
(5)write frp1 back to frp partition
(6)reboot boot loader
(7)fastboot flashing unlock
(8)press up-vol or down-vol (not sure, i stop here, feedback welcome)
(9)done
This is generic enough for MTK and Qcom soc, success story other than sdm636 and mt6755 are welcome.
Other phone unlock tutorial:
Meizu M3note bootloader unlock
Regards,
99degree
An unofficial twrp for MeizuE3 is available below for people unlocked bootloader and would like to play with custom rom.
twrp custome ver 3.3.1:
http://s000.tinyupload.com/?file_id=01088261345935635855
-ramdisk is from twrp.me model whyred
-kernel is self compile, based on LA.UM.8.2.r1-05700-sdm660.0
-with lcd and touchpad driver patched
BTW, this twrp support encrypted data partition, so it is working parallel with flyme8 well.
An official MeizuE3 recovery img is also provided here for people would like to boot and restore flyme back.
https://gofile.io/?c=pFRTJy
A vlog for booting MeizuE3 with LineageOS 17.1 up to splash screen is available at youtube:
It is based on below LOS custom system build from rcstar6696 and kvsjxd, credit him:
https://forum.xda-developers.com/mi-a2/development/10-x-lineage-17-0-jasminesprout-t3966643
and with his another wayne vendor:
https://forum.xda-developers.com/mi-a2/xiaomi-6x-wayne/rom-lineageos-17-0-t3989193
Found in other thread* that mentioned about persist partition might be wiped by LOS17 or other custom rom and cause Wlan mac missing etc. I suspect this is also true for unstable wifi too. So if there is anybody have an original persist partition dump please upload and share. [20200303]The issue is fixed by two thing. /persist/wlan_mac.bin modification. Recompile kernel to include 3 more modules (fw-api, qca-wifi-host-cmn, qcacld-3.0).
https://forum.xda-developers.com/showpost.php?p=80217431&postcount=2
Hi there,
MeizuE3 boots up LOS17.1 with WIFI, detail is at below youtube video. Check it out!
Custom ROM from rcstar6696 and ItsMeShouko, creadit them.
https://forum.xda-developers.com/mi-a2/development/10-x-lineage-17-0-jasminesprout-t3966643
Or my modified ROM based on above jasmine sprout ROM.
https://forum.xda-developers.com/android/development/meizu-e3-lineageos-17-1-rom-porting-t4055605
Thx,
99degree
Edit 25/10/2020: OK its been a while guys, if you want to try a ROM I'd highly recommend following LineageOS's wiki for instructions. Then if u want to try other ROMs keep an eye out in these forums, ill have a build up every now and then. See ya around guys
==========================================================================================
Rather than having random comments in random parts of the forum here is a thread for everything 64 bit on G7 Play.
CURRENT STATUS
WE DID IT!!!! CHECK SyberHexen's ANDROIDFILEHOST FOR DOWNLOAD!
OLD POST ARCHIVED BELOW
And here is what is available so far:
A nice selection of ROMs for the other G7's, but they dont actually boot on the Play, although should do something in theory
postmarketOS is aarch64, but that is mobile linux, and no phone interface works (x.org doesnt work with the current drivers)
Here is what I've tried:
crDroid from ocean:
I got it to install by: repartitioning device using ocean gpt.bin
Then flashing stock rom from channel
Booting TWRP
Flashing ROM, with modified zip accepting channel
Doesnt boot
Also tried a flash using ocean firmware completely, doesn't boot, but got the logos and bootloader works lol
If anyone has any tips or progress drop it here, eta kids go away. Read the status above if you want the up-to-date answer
00p513 said:
Rather than having random comments in random parts of the forum here is a thread for everything 64 bit on G7 Play.
CURRENT STATUS
NO 64-BIT ANDROID ROM AVAILABLE
And here is what is available so far:
A nice selection of ROMs for the other G7's, but they dont actually boot on the Play, although should do something in theory
postmarketOS is aarch64, but that is mobile linux, and no phone interface works (x.org doesnt work with the current drivers)
Here is what I've tried:
crDroid from ocean:
I got it to install by: repartitioning device using ocean gpt.bin
Then flashing stock rom from channel
Booting TWRP
Flashing ROM, with modified zip accepting channel
Doesnt boot
Also tried a flash using ocean firmware completely, doesn't boot, but got the logos and bootloader works lol
If anyone has any tips or progress drop it here, eta kids go away. Read the status above if you want the up-to-date answer
Click to expand...
Click to collapse
You have to compile the kernel from source and use a 64bit gsi and flash a 64 bit vendor partition I'm pretty sure everythi
---------- Post added at 04:44 AM ---------- Previous post was at 04:42 AM ----------
00p513 said:
Rather than having random comments in random parts of the forum here is a thread for everything 64 bit on G7 Play.
CURRENT STATUS
NO 64-BIT ANDROID ROM AVAILABLE
And here is what is available so far:
A nice selection of ROMs for the other G7's, but they dont actually boot on the Play, although should do something in theory
postmarketOS is aarch64, but that is mobile linux, and no phone interface works (x.org doesnt work with the current drivers)
Here is what I've tried:
crDroid from ocean:
I got it to install by: repartitioning device using ocean gpt.bin
Then flashing stock rom from channel
Booting TWRP
Flashing ROM, with modified zip accepting channel
Doesnt boot
Also tried a flash using ocean firmware completely, doesn't boot, but got the logos and bootloader works lol
If anyone has any tips or progress drop it here, eta kids go away. Read the status above if you want the up-to-date answer
Click to expand...
Click to collapse
You have to compile the kernel from source and use a 64bit gsi and flash a 64 bit vendor partition I'm pretty sure everything else will work fine. I'm working on getting a new dev environment set up I'll give it a shot... This phone is reeeeealy under developed. Proly cause the g6 play is a way better phone and much cheaper to boot
mrsurge said:
You have to compile the kernel from source and use a 64bit gsi and flash a 64 bit vendor partition I'm pretty sure everythi
---------- Post added at 04:44 AM ---------- Previous post was at 04:42 AM ----------
You have to compile the kernel from source and use a 64bit gsi and flash a 64 bit vendor partition I'm pretty sure everything else will work fine. I'm working on getting a new dev environment set up I'll give it a shot... This phone is reeeeealy under developed. Proly cause the g6 play is a way better phone and much cheaper to boot
Click to expand...
Click to collapse
We have a 64-bit kernel and 64-bit Lineage OS testing builds but porting 64-bit vendor partition for it to flash in g7 play hasn't been achieved yet.
kD said:
We have a 64-bit kernel and 64-bit Lineage OS testing builds but porting 64-bit vendor partition for it to flash in g7 play hasn't been achieved yet.
Click to expand...
Click to collapse
I think maybe you can just pick out driver binaries from 64 bit /vendor and use all the configs scripts and frameworks from the original vendor
Try backing up/vendor pieceing the drivers from another device of the same model but diff carrier and a combo as such would work. If not mistaken the. Vendor from the Verizon g6 play worked for sprint except data and wifi or radio in general didn't work.. that's a start right there
I think the modem is going to be the same architecture no matter what so you wouldn't have to worry to much about that
64bit Test
Okay so this sh*t probably totally won't boot up at all, but if someone is feeling brave, you can test this out.
1. From your active slot, with root access, you'll need to dd these images to the correct partitions. It's easiest to do this from the internal sdcard using termux. Use the following as a template. These commands assume you're installing it to slot b.
Code:
su
dd if=/sdcard/boot64.img of=/dev/block/by-name/boot_b
dd if=/sdcard/dtbo64.img of=/dev/block/by-name/dtbo_b
dd if=/sdcard/vendor64.img of=/dev/block/by-name/vendor_b
dd if=/sdcard/oem64.img of=/dev/block/by-name/oem_b
2. Reboot into fastboot, swap active slots, and wipe userdata + DDR. Then flash an arm64 AB GSI. I'd recommend trying Phh's AOSP Vanilla to maximize the chances of success.
To swap slots and wipe user data...
Code:
fastboot --set-active=_b
fastboot erase userdata
fastboot erase DDR
3. Reboot system, and tell me what happens.
**Do NOT attempt to use TWRP with this. You'll probably have to reflash stock firmware to the slot you tampered with to get everything back to normal afterwards.**
Link: 64bit Folder
This is not source built, and it's very much a hack job, so I'm really not expecting anything to work. I did get Ubuntu installed this morning, so I will attempt to build from source in the near future.
Please don't use this if you don't know what a "brick" is or how to recover from one
PS: it probably wont work cause vendor is twice the size xD
The G7 play is coming so far little by little it was like yesterday we never thought we would have twrp and magisk and now in fact we do on a GSI
([emoji88]Havoc GSI[emoji88])
00p513 said:
PS: it probably wont work cause vendor is twice the size xD
Click to expand...
Click to collapse
You are correct. She's way too hefty. It's ~164mb too large. I tried resizing last night, but I can only shrink it to 433mb. I can probably remove the modem files and replace them with the ones from stock. I think it's where most of the extra weight is from. The 64bit libs are about 1.5x bigger, but I don't think that accounts for all of it. The Muppets have a tree for sdm632, so all I need to do is look at it, and delete everything in vendor that's not in there. It should help but I'm not sure if it'll be enough. I could repartition it, but I'm not a fan of resizing partitions because I'm very fearful of bricks.
Spaceminer said:
You are correct. She's way too hefty. It's ~164mb too large. I tried resizing last night, but I can only shrink it to 433mb. I can probably remove the modem files and replace them with the ones from stock. I think it's where most of the extra weight is from. The 64bit libs are about 1.5x bigger, but I don't think that accounts for all of it. The Muppets have a tree for sdm632, so all I need to do is look at it, and delete everything in vendor that's not in there. It should help but I'm not sure if it'll be enough. I could repartition it, but I'm not a fan of resizing partitions because I'm very fearful of bricks.
Click to expand...
Click to collapse
I can get a bit more space with an ocean gpt.bin btw. i suppose we could see how those files work i guess and make a bigger vendor?
00p513 said:
I can get a bit more space with an ocean gpt.bin btw. i suppose we could see how those files work i guess and make a bigger vendor?
Click to expand...
Click to collapse
Have you flashed the gpt.bin from ocean before? If so I'll definitely try using that with the slightly smaller vendor I made. I'm thinking most things from Ocean should work natively. The only difference is screen size by a few pixels, ram, and battery capacity. Otherwise they're essentially the same.
Spaceminer said:
Have you flashed the gpt.bin from ocean before? If so I'll definitely try using that with the slightly smaller vendor I made. I'm thinking most things from Ocean should work natively. The only difference is screen size by a few pixels, ram, and battery capacity. Otherwise they're essentially the same.
Click to expand...
Click to collapse
yeah i use channel firmware extracted, then i use motoflash2sh to generate a bashscript from the flashfile. I then replace gpt .bin and remove it from the md5 checks at the beginning of the script. run the script and im repartitioned!
00p513 said:
yeah i use channel firmware extracted, then i use motoflash2sh to generate a bashscript from the flashfile. I then replace gpt .bin and remove it from the md5 checks at the beginning of the script. run the script and im repartitioned!
Click to expand...
Click to collapse
That's awesome! I'll try working with this.
Spaceminer said:
That's awesome! I'll try working with this.
Click to expand...
Click to collapse
ill send a repartition kit later. just unzip and run the script
00p513 said:
ill send a repartition kit later. just unzip and run the script
Click to expand...
Click to collapse
I already found it. So I'd just remove 61863ba7dac0c512d610ffa6406a50f8 and it'll flash correct?
Code:
md5sum --check <<EOF || exit 1
[B]61863ba7dac0c512d610ffa6406a50f8[/B] *gpt.bin
Spaceminer said:
I already found it. So I'd just remove 61863ba7dac0c512d610ffa6406a50f8 and it'll flash correct?
Code:
md5sum --check <<EOF || exit 1
[B]61863ba7dac0c512d610ffa6406a50f8[/B] *gpt.bin
Click to expand...
Click to collapse
that whole line needs deleting. That is just to stop it failing on md5 verification ,as it is a dfiferent file
Spaceminer said:
I already found it. So I'd just remove 61863ba7dac0c512d610ffa6406a50f8 and it'll flash correct?
Code:
md5sum --check <<EOF || exit 1
[B]61863ba7dac0c512d610ffa6406a50f8[/B] *gpt.bin
Click to expand...
Click to collapse
Did it work? Any update on the vendor image?
00p513 said:
Did it work? Any update on the vendor image?
Click to expand...
Click to collapse
I haven't tried it yet. I got side tracked compiling twrp. I'm 3 errors away from success. Something about unknown compiler flags.
As an FYI, I'm out of a computer for the next several months, possibly up to a year. I'm going through a nasty divorce at the moment, and that's all I'm going to say about that. I'll get back into the game as soon as I can, but for now, you should not expect me to put out anything new for quite awhile. I can and will help people as much as possible during this time. But my ability to do so is going to be hindered without an PC.
I'm sorry to hear that. My divorce lasts since two years.
However, that's not why I registered. I received a Moto G7 Play for app security testing just a few days ago and found this forum when trying to install GSI to the phone. Everything works fine, but I'm interested to upgrade the OS to 64bit. Therefore, I'd like to try out the work already present in this thread. Unfortunately, I have neither found the repartition kit nor gained enough information about gpt.bin file format yet in order to repartition the flash memory of the G7 Play.
I'd really appreciate if anybody could either post or send me the repartition kit or supply information about the partition table format, because I failed to google for that kind of information.
[edit] Ok, I found out how to change partition size to the size of ocean. I flashed the following images:
* Partition table from ocean
* Everything else except system_a from channel
* system_a from phh (binder64)
Everything worked just fine.
Then I proceeded to flash the files posted in this thread earlier. The vendor64.img fits into the new partition layout just fine. After flashing all 4 files, I proceeded to flash phh 64bit version. Then I rebooted, but the boot failed:
First, the device showed up some very long hexadecimal number (maybe some UUID?) on a black screen, where it had shown "bad key" before when everything went right.
Afterwards, it ran into fastboot:
Start Up Failed:
Your device didn't start up successfully.
Use Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
Failed to verify hab image boot_a
Error: failed to load kernel!
No bootable A/B slot
Failed to boot Linux,falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
Click to expand...
Click to collapse
So, I'm back on binder64 again.
Please, could you provide any help for fixing the images, or at least the information how you have built the 64bit images?
Ok so heres the full story (It's short):
So my V20 bricked itself for no reason (I was on stock for a few days unrooted no unlock nothing)
and while going through xda I stumbled upon this:https://forum.xda-developers.com/on...eble-lineageos-15-1-treble-oneplus-3-t3830455
Treble on the oneplus 3 and 3t. Why this one you might ask
well it is because our V20 and the Oneplus are similar.
So here is what somebody who is willing to help with a h990ds or H990 (It wont brick your device don't worry)needs to do:
1.First install this modded twrp here is the Link (Made from Pheonix591's twrp): https://drive.google.com/file/d/1pBrjWnKqRFFsQ-By_ElE3pW3LbWsg9sx/view?usp=sharing
2. Boot into the TWRP and go to advanced options then select terminal
Now type Treble and wait for a few seconds (This command is taken from the trebel port for oneplus 3 @simonsh)
Next reboot to whatever rom you are using(If it doesn't boot or bootloops something went wrong retry from step 2)
After it boots successfully go back to twrp and check in wipe and advanced wipe for Vendor
Now here is the problem the partition is only about 100 megabytes which we cant really use for treble it is too small.
So I am pinging a person who might be able to help us :
@runningnak3d I need your help in making the partition larger as it is again only about 100megabytes
Edit: So Runningnak3d has stopped developing for the V20 :crying: and I had just remembered that @x86cpu might be able to help so pinging him, we want as much people as possible.
Uhh so seems like my wifi is not properly working I will upload the twrp
Mysteriouslog6 said:
Ok so heres the full story (It's short):
So my V20 bricked itself for no reason (I was on stock for a few days unrooted no unlock nothing)
and while going through xda I stumbled upon this:https://forum.xda-developers.com/on...eble-lineageos-15-1-treble-oneplus-3-t3830455
Treble on the oneplus 3 and 3t. Why this one you might ask
well it is because our V20 and the Oneplus are similar.
So here is what somebody who is willing to help with a h990ds or H990 (It wont brick your device don't worry)needs to do:
1.First install this modded twrp here is the Link (Made from Pheonix591's twrp):
2. Boot into the TWRP and go to advanced options then select terminal
Now type Treble and wait for a few seconds (This command is taken from the trebel port for oneplus 3 @simonsh)
Next reboot to whatever rom you are using(If it doesn't boot or bootloops something went wrong retry from step 2)
After it boots successfully go back to twrp and check in wipe and advanced wipe for Vendor
Now here is the problem the partition is only about 100 megabytes which we cant really use for treble it is too small.
So I am pinging a person who might be able to help us :
@runningnak3d I need your help in making the partition larger as it is again only about 100megabytes
Click to expand...
Click to collapse
Running naked moved on and stopped developing for the V20 a long time ago.
Sent from my LG-H910 using XDA Labs
cnjax said:
Running naked moved on and stopped developing for the V20 a long time ago.
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
That's really sad I was hoping someone can help me with the partition problem, what about @x86cpu ?
Mysteriouslog6 said:
Ok so heres the full story (It's short):
So my V20 bricked itself for no reason (I was on stock for a few days unrooted no unlock nothing)
and while going through xda I stumbled upon this:https://forum.xda-developers.com/on...eble-lineageos-15-1-treble-oneplus-3-t3830455
Treble on the oneplus 3 and 3t. Why this one you might ask
well it is because our V20 and the Oneplus are similar.
So here is what somebody who is willing to help with a h990ds or H990 (It wont brick your device don't worry)needs to do:
1.First install this modded twrp here is the Link (Made from Pheonix591's twrp): https://drive.google.com/file/d/1pBrjWnKqRFFsQ-By_ElE3pW3LbWsg9sx/view?usp=sharing
2. Boot into the TWRP and go to advanced options then select terminal
Now type Treble and wait for a few seconds (This command is taken from the trebel port for oneplus 3 @simonsh)
Next reboot to whatever rom you are using(If it doesn't boot or bootloops something went wrong retry from step 2)
After it boots successfully go back to twrp and check in wipe and advanced wipe for Vendor
Now here is the problem the partition is only about 100 megabytes which we cant really use for treble it is too small.
So I am pinging a person who might be able to help us :
@runningnak3d I need your help in making the partition larger as it is again only about 100megabytes
Edit: So Runningnak3d has stopped developing for the V20 :crying: and I had just remembered that @x86cpu might be able to help so pinging him, we want as much people as possible.
Click to expand...
Click to collapse
Mind if I help I recently acquired a vs995 for cheap so for know at least im back. I experimented with trebe on the g5 and was able to build a treblized los 15.1 but the problem was no gsi would boot here's what I used to build it.
https://review.lineageos.org/c/LineageOS/android_device_lge_h850/+/222974
https://review.lineageos.org/c/LineageOS/android_device_lge_msm8996-common/+/221553
https://review.lineageos.org/c/LineageOS/android_kernel_lge_msm8996/+/222018
I then added this to BoardConfigCommon.mk:
# Treble
BOARD_PROPERTY_OVERRIDES_SPLIT_ENABLED := true
BOARD_VNDK_RUNTIME_DISABLE := true
BOARD_VNDK_VERSION := current
PRODUCT_FULL_TREBLE_OVERRIDE := true
I would also like to mention that a few years ago @King_lilrowrow said he was working on/achieved treble on the G5 I'd contact him as well for help.
What is 'treble' / 'treblizing'... Curious what it does.
kaluna00 said:
What is 'treble' / 'treblizing'... Curious what it does.
Click to expand...
Click to collapse
The command does this (From @simonsh thread)
Code:
/sbin/sgdisk --typecode=5:8300 /dev/block/sdf
/sbin/sgdisk --change-name=5:vendor /dev/block/sdf
It basically makes the sdf block the vendor partition (Works as nothing has interfered with the working of the phone so the partition is unused but it is too small need help with that)
kaluna00 said:
What is 'treble' / 'treblizing'... Curious what it does.
Click to expand...
Click to collapse
So treble aka project treble is something google implemented with android 8 that splits system/vendor to / system and /vendor basically it gives vendor files which are device-specific code and drivers used to interact with the phone's hardware there own separate partition. Now since /system without vendor is mostly free of device-specific code it means that the phones os can be upgraded with messing with building and modifying the device-specific code, this is were GSIs (generic system images) come in, flashing a gsi essentially means we can modify and upgrade our OS like a custom rom but instead of spending hours working on a custom rom we can just build a system image which is very fast and easy and it can do just as much as a custom rom as far as enhancing the user experience goes.
That's the best I can explain it here is an article explaining it more and as far as trebilizing goes it's just a term used when someone gets treble working on an old device that doesn't support it from the factory.
ROMSG said:
Mind if I help I recently acquired a vs995 for cheap so for know at least im back. I experimented with trebe on the g5 and was able to build a treblized los 15.1 but the problem was no gsi would boot here's what I used to build it.
https://review.lineageos.org/c/LineageOS/android_device_lge_h850/+/222974
https://review.lineageos.org/c/LineageOS/android_device_lge_msm8996-common/+/221553
https://review.lineageos.org/c/LineageOS/android_kernel_lge_msm8996/+/222018
I then added this to BoardConfigCommon.mk:
# Treble
BOARD_PROPERTY_OVERRIDES_SPLIT_ENABLED := true
BOARD_VNDK_RUNTIME_DISABLE := true
BOARD_VNDK_VERSION := current
PRODUCT_FULL_TREBLE_OVERRIDE := true
I would also like to mention that a few years ago @King_lilrowrow said he was working on/achieved treble on the G5 I'd contact him as well for help.
Click to expand...
Click to collapse
Thanks for wanting to help I will send a link for the vs995 with a custom twrp. Also isn't the BoardConfigCommon.MK in the source for lineage os I will try building it with the modifications
Mysteriouslog6 said:
Thanks for wanting to help I will send a link for the vs995 with a custom twrp. Also isn't the BoardConfigCommon.MK in the source for lineage os I will try building it with the modifications
Click to expand...
Click to collapse
Thanks, BoardConfigCommon.mk is a device tree file and specific to any rom. Here this Commit outlines one of the issues @x86cpu had with getting treble working.
@ROMSG
Thanks a bunch for the explanation. I appreciate you breaking it down I like that. I'll do some homework and check out that link after work. Take care!
Mysteriouslog6 said:
Thanks for wanting to help I will send a link for the vs995 with a custom twrp. Also isn't the BoardConfigCommon.MK in the source for lineage os I will try building it with the modifications
Click to expand...
Click to collapse
Any update on the vs995 custom twrp?
ROMSG said:
Any update on the vs995 custom twrp?
Click to expand...
Click to collapse
Sorry for the late reply I will send it tomorrow itself (Will have to somehow see if the TWRP boots or not)
Heres the link:
twrp-treble-vs995.img
drive.google.com
ROMSG said:
Any update on the vs995 custom twrp?
Click to expand...
Click to collapse
I have sent the TWRP just check the latest post
Mysteriouslog6 said:
I have sent the TWRP just check the latest post
Click to expand...
Click to collapse
Just saw it thanks
Mysteriouslog6 said:
Ok so heres the full story (It's short):
So my V20 bricked itself for no reason (I was on stock for a few days unrooted no unlock nothing)
and while going through xda I stumbled upon this:https://forum.xda-developers.com/on...eble-lineageos-15-1-treble-oneplus-3-t3830455
Treble on the oneplus 3 and 3t. Why this one you might ask
well it is because our V20 and the Oneplus are similar.
So here is what somebody who is willing to help with a h990ds or H990 (It wont brick your device don't worry)needs to do:
1.First install this modded twrp here is the Link (Made from Pheonix591's twrp): https://drive.google.com/file/d/1pBrjWnKqRFFsQ-By_ElE3pW3LbWsg9sx/view?usp=sharing
2. Boot into the TWRP and go to advanced options then select terminal
Now type Treble and wait for a few seconds (This command is taken from the trebel port for oneplus 3 @simonsh)
Next reboot to whatever rom you are using(If it doesn't boot or bootloops something went wrong retry from step 2)
After it boots successfully go back to twrp and check in wipe and advanced wipe for Vendor
Now here is the problem the partition is only about 100 megabytes which we cant really use for treble it is too small.
So I am pinging a person who might be able to help us :
@runningnak3d I need your help in making the partition larger as it is again only about 100megabytes
Edit: So Runningnak3d has stopped developing for the V20 :crying: and I had just remembered that @x86cpu might be able to help so pinging him, we want as much people as possible.
Click to expand...
Click to collapse
Hello, since Android 12 beta has released recently, i get to know that we can use the GSI image to update “any” (in terms of project treble supported) device to a newer android version without the need of building the rom per device.
So that i started to explore on a few xda threads trying to get Treble on LG V20. After digging into it, i updated my TWRP to the latest image (official TWRP 3.5.2_9 H990 which is the Official TWRP build commit based on Pheonix591's twrp build), then i saw that the /vendor shows up on mount, but not on either Wipe or Backup, which Phoenix591’s reddit post stated that this means there’s no vendor partition on it.
I followed this thread, since my TWRP is not modded (as the link in your comment does not work) I typed two sgdisk commands which the Treble command does, after a reboot, i saw a Vendor partition in Backup showed 0mb, Vendor partition DOES NOT appears on Wipe.
Next, as what i saw from @x86cpu ’s comment, he said he repartitioned and created the /vendor partition of 512mb by resizing the /system partition, unfortunately i am new to partitioning the Android device, i haven’t figured out how i can do that.
I tried to do sgdisk —print /dev/block/mmcblk0, it showed a single 64gb MBR FAT32 Partition instead of showing the system partition, it seems to be showing the micro sd card instead of the system volume, so i tried to unplug the sd card and reboot, now /dev/block/mmcblk0 is not found. I also tried to list info of /dev/block/sdf which we have wrote the partition name “vendor” to the 5th parnum of /sdf, it shows that the partition is only 4kb.
Since i have a H990N (Hong Kong version of the H990) i used the Dirty Santa patch to get TWRP installed on the device, that means the device’s bootloader is NOT fully unlocked, so the device might have difference between official unlocked device like the VS995.
Is there anything i could try ?
kwankiu said:
Hello, since Android 12 beta has released recently, i get to know that we can use the GSI image to update “any” (in terms of project treble supported) device to a newer android version without the need of building the rom per device.
So that i started to explore on a few xda threads trying to get Treble on LG V20. After digging into it, i updated my TWRP to the latest image (official TWRP 3.5.2_9 H990 which is the Official TWRP build commit based on Pheonix591's twrp build), then i saw that the /vendor shows up on mount, but not on either Wipe or Backup, which Phoenix591’s reddit post stated that this means there’s no vendor partition on it.
I followed this thread, since my TWRP is not modded (as the link in your comment does not work) I typed two sgdisk commands which the Treble command does, after a reboot, i saw a Vendor partition in Backup showed 0mb, Vendor partition DOES NOT appears on Wipe.
Next, as what i saw from @x86cpu ’s comment, he said he repartitioned and created the /vendor partition of 512mb by resizing the /system partition, unfortunately i am new to partitioning the Android device, i haven’t figured out how i can do that.
I tried to do sgdisk —print /dev/block/mmcblk0, it showed a single 64gb MBR FAT32 Partition instead of showing the system partition, it seems to be showing the micro sd card instead of the system volume, so i tried to unplug the sd card and reboot, now /dev/block/mmcblk0 is not found. I also tried to list info of /dev/block/sdf which we have wrote the partition name “vendor” to the 5th parnum of /sdf, it shows that the partition is only 4kb.
Since i have a H990N (Hong Kong version of the H990) i used the Dirty Santa patch to get TWRP installed on the device, that means the device’s bootloader is NOT fully unlocked, so the device might have difference between official unlocked device like the VS995.
Is there anything i could try ?
Click to expand...
Click to collapse
So in regards to partitioning you have to build a ROM with that partiton table in place for it too work and I have gotten treble to work (this was on myt h830) however no gsi will boot. I had to use this tool to add vender in order to flash my treble rom. I used the 800MB option in order for vender to show up.
Here are some 15.1 device tress I made for tbe VS995. I used the changes from x86cpu
GitHub - ROMSG/Treble-android_device_lge_msm8996-common
Contribute to ROMSG/Treble-android_device_lge_msm8996-common development by creating an account on GitHub.
github.com
GitHub - ROMSG/android_device_lge_vs995
Contribute to ROMSG/android_device_lge_vs995 development by creating an account on GitHub.
github.com
GitHub - ROMSG/Treble_android_device_lge_v20-common
Contribute to ROMSG/Treble_android_device_lge_v20-common development by creating an account on GitHub.
github.com
ROMSG said:
So in regards to partitioning you have to build a ROM with that partiton table in place for it too work and I have gotten treble to work (this was on myt h830) however no gsi will boot. I had to use this tool to add vender in order to flash my treble rom. I used the 800MB option in order for vender to show up.
Here are some 15.1 device tress I made for tbe VS995. I used the changes from x86cpu
GitHub - ROMSG/Treble-android_device_lge_msm8996-common
Contribute to ROMSG/Treble-android_device_lge_msm8996-common development by creating an account on GitHub.
github.com
GitHub - ROMSG/android_device_lge_vs995
Contribute to ROMSG/android_device_lge_vs995 development by creating an account on GitHub.
github.com
GitHub - ROMSG/Treble_android_device_lge_v20-common
Contribute to ROMSG/Treble_android_device_lge_v20-common development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Thanks for your reply ! I used the tool in your comment, at first i tried take use /system space to resize a 512mb /vendor partition unfortunately this makes the /system partition only at 5gb which result in Error:7 while flashing new ROMs, so i removed the partition and did it again by adding a 512mb /vendor using space AFTER /data, i checked the partition by fdisk -l /dev/block/sda the /vendor partition is created successfully with 512gb partition size, but no “/vendor” Partition was shown on the Wipe page of TWRP (while the partition was shown in Backup and Mount), not sure whether this affect us on going Treble or not, but wiping /vendor should be possible via terminal commands.
ROMSG said:
So in regards to partitioning you have to build a ROM with that partiton table in place for it too work and I have gotten treble to work (this was on myt h830) however no gsi will boot. I had to use this tool to add vender in order to flash my treble rom. I used the 800MB option in order for vender to show up.
Here are some 15.1 device tress I made for tbe VS995. I used the changes from x86cpu
GitHub - ROMSG/Treble-android_device_lge_msm8996-common
Contribute to ROMSG/Treble-android_device_lge_msm8996-common development by creating an account on GitHub.
github.com
GitHub - ROMSG/android_device_lge_vs995
Contribute to ROMSG/android_device_lge_vs995 development by creating an account on GitHub.
github.com
GitHub - ROMSG/Treble_android_device_lge_v20-common
Contribute to ROMSG/Treble_android_device_lge_v20-common development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
One more thing, I actually misunderstood the partition yesterday that i said it was 0mb, in fact, the backup page shows 0mb is a normal behaviour as the vendor partition is empty, i didnt check how big is the partition size, but I believe it should be 100mb after running the command “Treble”. Anyways, thanks for pointing out the tools which makes it 512mb now !
My goal in this post is simple: I would like to ask anyone if they have a copy of the source code for the China Telecom variant for HTC Desire 709d (cp5dwg), or if they could contact HTC effectively, directly for this source. The only source available for this device on HTCdev is for a variant in India and would never boot on my device(tested over and over and over again). If anyone could possibly offer a copy of a custom recovery I'd be also appreciated. Note that this model uses a Spreadtrum SoC instead of a Qualcomm one.
If someone is to contact HTC for this here is some possibly relevant information for accurate search:
KERNEL VERSION: 3.4.5-gec07fd6
OTHER KERNEL INFO: SMP PREEMPT
ROM VERSION: 1.80.1401.11
Thanks.
can you tell me what spreadtrum chipset it is? and can you give me a stock recovery image?
notnoelchannel said:
can you tell me what spreadtrum chipset it is? and can you give me a stock recovery image?
Click to expand...
Click to collapse
from CPU Info (got from f-droid since aida64 cant install on android 4.1) it shows "Spreadtrum SC8830."
Recovery image (boot2.img) attached in post. It's from software version 1.80.1401.9
*this device seems to use the old board files method instead of device trees, according to this india source i have.
MightyPandora8 said:
from CPU Info (got from f-droid since aida64 cant install on android 4.1) it shows "Spreadtrum SC8830."
Recovery image (boot2.img) attached in post. It's from software version 1.80.1401.9
*this device seems to use the old board files method instead of device trees, according to this india source i have.
Click to expand...
Click to collapse
hmm i looked into this and i found recovery fstab:
Code:
# mount point fstype device
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p48
/data ext4 /dev/block/mmcblk0p50
/cache ext4 /dev/block/mmcblk0p49
/misc emmc /dev/block/mmcblk0p25
/boot emmc /dev/block/mmcblk0p23
/recovery emmc /dev/block/mmcblk0p24
/sprd_fix_nv_w emmc /dev/block/mmcblk0p28
/sprd_fix_nv_t emmc /dev/block/mmcblk0p30
/sprd_runtime_nv_w emmc /dev/block/mmcblk0p32
/sprd_runtime_nv_t emmc /dev/block/mmcblk0p33
This might be useful in the future
Recovery fstab is the same as the Walton Primo EF4+ phone, so if it had any lineage rom i could port it (not possible though)
Anyway, i ported TWRP 3.2.0, can you try to flash it?
Download below attachments
you ported twrp for my device in 20 minutes???
you ported twrp for my device in 20 minutes???
oh my goodness
notnoelchannel said:
hmm i looked into this and i found recovery fstab:
Code:
# mount point fstype device
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p48
/data ext4 /dev/block/mmcblk0p50
/cache ext4 /dev/block/mmcblk0p49
/misc emmc /dev/block/mmcblk0p25
/boot emmc /dev/block/mmcblk0p23
/recovery emmc /dev/block/mmcblk0p24
/sprd_fix_nv_w emmc /dev/block/mmcblk0p28
/sprd_fix_nv_t emmc /dev/block/mmcblk0p30
/sprd_runtime_nv_w emmc /dev/block/mmcblk0p32
/sprd_runtime_nv_t emmc /dev/block/mmcblk0p33
This might be useful in the future
Recovery fstab is the same as the Walton Primo EF4+ phone, so if it had any lineage rom i could port it (not possible though)
Anyway, i ported TWRP 3.2.0, can you try to flash it?
Download below attachments
Click to expand...
Click to collapse
No. My phone bootlooped in recovery
like it's ENDLESS. it keeps trying to boot into recovery as long as there's adequate power to go into the phone's hardware
i had to pull the battery to stop it from continuing to reboot
MightyPandora8 said:
you ported twrp for my device in 20 minutes???
Click to expand...
Click to collapse
yeah but it has a chance that it will not boot:
MightyPandora8 said:
No. My phone bootlooped in recovery
like it's ENDLESS. it keeps trying to boot into recovery as long as there's adequate power to go into the phone's hardware
Click to expand...
Click to collapse
i can try to port CWM recovery from an other device, maybe it'll boot
I recommend also not flashing it to the recovery partition if you have fastboot then type:
fastboot boot <recovery image here>
notnoelchannel said:
I recommend also not flashing it to the recovery partition if you have fastboot then type:
fastboot boot <recovery image here>
Click to expand...
Click to collapse
uhh it doesnt seem like my phone likes full boot.img to be sent via fastboot boot.
only works when sending a single kernel...
also, i asked for the kernel source - is all this useful for my india code to work on my china telecom device?
MightyPandora8 said:
uhh it doesnt seem like my phone likes full boot.img to be sent via fastboot boot.
only works when sending a single kernel...
also, i asked for the kernel source - is all this useful for my india code to work on my china telecom device?
Click to expand...
Click to collapse
i don't have the kernel source for your device, you have to email to HTC and request the kernel source of your device, give them your model number, processor, and variant. it would violate GPL if they don't release the kernel source.
notnoelchannel said:
i don't have the kernel source for your device, you have to email to HTC and request the kernel source of your device, give them your model number, processor, and variant. it would violate GPL if they don't release the kernel source.
Click to expand...
Click to collapse
the big problem here is the email address. I can't find anywhere with a proper email address that you send an email to it youre sending directly to the HQ and would be taken directly to relevant departments like [email protected]. all i find is some indirect tech support forms thats not going to help at all. no htc global contact/site at all either.
i doubt that the source is gone forever - for i have a samsung, which is also a CT variant from 8-9 years ago and samsung is still able to put it up on their site. htc, as the number one in android back in those good old days, shouldn't be unable to do so like samsung did. but if it's htc's policy in obsoletion then... well.
Hi, I just registered today to ask this question. Through somewhat simple means using the tools I had available, I was able to readback the stock rom from a TCL 20 XE 5087Z branded under Boost Mobile. I have successfully rooted via magisk and have confirmed that it is indeed the correct stock firmware through a bit of an accident, I forgot to patch vbmeta when flashing magisk_patched_boot.img, so in a panic, I flashed back all the roms I had read back from the device except userdata, and miraculously the device worked! Now the problem I run into is all the bloatware the carrier has installed on the phone. My main reason for rooting my device was I wanted the ability to prevent apps from being killed by the "Smart" manager on the device, because it seems that important apps keep getting killed by the built-in software. I ended up determining that the ram manager on the phone was killing apps based on the amount of ram available. Now that the phone is rooted, you would think I would have no problem getting rid of all the bloatware, except that whenever I forcefully uninstall the ram manager (com.tct.onetouchbooster), the app is still available on my apps menu and clicking on it with pretty much no delay opens the app right up as if the data had just been cleared. Now I have no idea what is causing this, probably another app, but I was wondering if maybe an easier alternative would be to get a generic android image for the device without bloatware that I can install just what I need. Now I say easier, but I find little documentation on how to do this, better yet if it will work. I have limited knowledge of how the android system works, mainly I just understand that /boot contains the bootloader, /system contains the os, and /userdata contains all the extra data apart from the stock image. If someone would enlighten me, would it actually be easier to build a generic image? Are there tools to do this? I understand that firmware is very touchy and that there is no "Generic" image in the sense, but having my stock rom available, would I be able to somehow generate a generic image based on the rom contents? If this would be way harder, how would I go about removing bloatware? I would not want to have to reset my phone each time I uninstall the wrong application, is there a non-data-damaging way to go about removing bloatware? If it ends up not being bloatware that is causing it and some hidden property somewhere in the stock rom config, how hard would it be to find that? Any help would be appreciated, and I am open to any comments and criticism. Please let me know how I might go about this, thanks in advance!
The stock firmware for this device can be found here: https://drive.google.com/file/d/1Q5IDP8V7PvuH2_1z63IFe23O2DF0cXZR/view?usp=sharing
The phone was bought from Walmart with prepaid Boost Mobile and it is a TCL 20 XE 5087Z with a MT6765 processor.
The password for the file is: xda5087Z-MT6765
Is the phone Project Treble enabled? If not don't waste your time.
A GSI is related to Project Treble, which means that the image can be installed on any Project Treble-supported device, regardless of the manufacturer, because it does not contain any hardware-specific components. The advantage is that a GSI can theoretically be used on any Project Treble-supported device.
xXx yYy said:
Is the phone Project Treble enabled? If not don't waste your time.
A GSI is related to Project Treble, which means that the image can be installed on any Project Treble-supported device, regardless of the manufacturer, because it does not contain any hardware-specific components. The advantage is that a GSI can theoretically be used on any Project Treble-supported device.
Click to expand...
Click to collapse
I downloaded the treble info app from the play store and indeed it is available with treble, the system image i need is system-arm64-ab.img.xz, would you mind pointing me in the right direction for how to install this? I'm assuming this just gets installed in the /system partition but let me know if I'm wrong. Thanks!
Can't help you, never did this.
You may look inside here:
[GUIDE] How to build a Project Treble GSI ROM from source? [31/08]
Hello guys, in this guide I'll try to simplify building Treble GSI process. As you read this guide now I'll assume you already have a previous knowledge about How to build android from source, so I won't cover some points with too many basic...
forum.xda-developers.com
Yes, only flash system.img. I recommend Android 10 (Android 11+ introduced restricted permissions)
[DISCONTINUED][GSI][10] LineageOS 17.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 16.0 GSIs I've been making since March 2019. If you clicked in here, I bet you know what LineageOS is already, but just to fill the blank: LineageOS is a free, community built...
forum.xda-developers.com
alecxs said:
Yes, only flash system.img. I recommend Android 10 (Android 11+ introduced restricted permissions)
[DISCONTINUED][GSI][10] LineageOS 17.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 16.0 GSIs I've been making since March 2019. If you clicked in here, I bet you know what LineageOS is already, but just to fill the blank: LineageOS is a free, community built...
forum.xda-developers.com
Click to expand...
Click to collapse
DO NOT DO THIS!!!! The TCL 20 XE is NOT compatible with Android 10 (it only supports something 30, which corresponds to Android 11), and the device will bootloop. I have made this mistake but I can not reach fastboot as the option is not in the recovery, therefore I need to run "adb reboot fastboot" within Android. MTKClient should fix this if you can find a stock super.img file for the 5087z.
note "adb reboot fastboot" is for fastbootd which is in recovery, while "adb reboot bootloader" is for fastboot (you can always enter from Volume button, regardless of destroyed boot/system partition)
boot-loop is probably caused by dm-verity, you forgot vbmeta?
alecxs said:
note "adb reboot fastboot" is for fastbootd which is in recovery, while "adb reboot bootloader" is for fastboot (you can always enter from Volume button, regardless of destroyed boot/system partition)
boot-loop is probably caused by dm-verity, you forgot vbmeta?
Click to expand...
Click to collapse
Fastbootd doesn't have an option in the recovery on my model, I've seen other TCL 20 XE phones have it though (I have the Boost Mobile varient like the thread maker), however Fastbootd let's me boot into recovery. I was only able to flash the stock ROM with MTKClient, which mikedcoombs thankfully provided (I just needed the super partition). For vbmeta, I just have an empty vbmeta that I flashed when I first rooted the phone. I don't think it is dm-verity, because LineageOS 20 as an GSI worked except for the Wi-Fi.