The OEMinfo file follows a simple structure.
Out of curiosity i've built a script to unpack / replace content in the OEMinfo for Huawei P Series OEMINFO roms.
The tool is not final (and might never be) although it might help in understanding what information is carried in this partition.
I started this tool to simplify region changes [and ROM-Hopping].
To switch to a foreign upgrade (186 to 432 etc.) download your own OEMINFO with TWRP, alter the 0x12 region element, write it back.
After this the upgrade.app is accepted.
Again: if ANYONE is willing to contribute on attributes [IDs] please do so.
This script is only tested on Windows Python 2.7. due to path and other issues. Please feel free to adopt if this tool fails for you.
Running in n00b mode is not recommended
usage:
--------------
oeminfo_decode_v2.py a <action> -i <inputfile> -r <replace_inputfile> -o <outputfile> -t <type 0x00>'
I interesed in this, updates are welcome
Thanks for the work
rysmario said:
The OEMinfo file follows a simple structure.
Out of curiosity i've built a script to unpack unpack / replace content in the OEMinfo for P9 [plus].
The tool is not final yet although it might help in understanding what information is carried in this partition.
Click to expand...
Click to collapse
How is work????
rysmario said:
The OEMinfo file follows a simple structure.
Out of curiosity i've built a script to unpack / replace content in the OEMinfo for Huawei P Series OEMINFO roms.
The tool is not final (and might never be) although it might help in understanding what information is carried in this partition.
I started this tool to simplify region changes [and ROM-Hopping].
To switch to a foreign upgrade (186 to 432 etc.) download your own OEMINFO with TWRP, alter the 0x12 region element, write it back.
After this the upgrade.app is accepted.
Again: if ANYONE is willing to contribute on attributes [IDs] please do so.
This script is only tested on WINDOWS [due to possible path issues]
Running in n00b mode is not recommended(!)
usage:
--------------
oeminfo_decode_v2.py a <action> -i <inputfile> -r <replace_inputfile> -o <outputfile> -t <type 0x00>'
Click to expand...
Click to collapse
I've python 3.5 on windows, but i not undestant how is work your oeminfo_decode_v2.py
Your may put example for command line here???
DRUGER said:
I've python 3.5 on windows, but i not undestant how is work your oeminfo_decode_v2.py
Your may put example for command line here???
Click to expand...
Click to collapse
Code:
python oeminfo_decode_v2.py
oeminfo_decode_v2.py -a <action> -i <inputfile> -r <replace_inputfile> -o <outputfile> -t <type 0x00>
python oeminfo_decode_v2.py -i p9p\oeminfo_cn
hdr:eek:EM_INFO age:00000023 id:0008
hdr:eek:EM_INFO age:00000001 id:0012 Region
hdr:eek:EM_INFO age:00000005 id:0042
hdr:eek:EM_INFO age:00000009 id:0043
.
.
hdr:eek:EM_INFO age:00000074 id:006b CN or CDMA info 0x6b
hdr:eek:EM_INFO age:00000002 id:015f Logo Boot
hdr:eek:EM_INFO age:00000002 id:0160 Logo Battery Empty
hdr:eek:EM_INFO age:00000002 id:0161 Logo Battery Charge
rysmario said:
Code:
python oeminfo_decode_v2.py
oeminfo_decode_v2.py -a <action> -i <inputfile> -r <replace_inputfile> -o <outputfile> -t <type 0x00>
python oeminfo_decode_v2.py -i p9p\oeminfo_cn
hdr:eek:EM_INFO age:00000023 id:0008
hdr:eek:EM_INFO age:00000001 id:0012 Region
hdr:eek:EM_INFO age:00000005 id:0042
hdr:eek:EM_INFO age:00000009 id:0043
.
.
hdr:eek:EM_INFO age:00000074 id:006b CN or CDMA info 0x6b
hdr:eek:EM_INFO age:00000002 id:015f Logo Boot
hdr:eek:EM_INFO age:00000002 id:0160 Logo Battery Empty
hdr:eek:EM_INFO age:00000002 id:0161 Logo Battery Charge
Click to expand...
Click to collapse
D:\FORFONE>python oeminfo_decode_v2.py -i oeminfo
File "oeminfo_decode_v2.py", line 102
print "hdr:%s age:%08x id:%04x %s " % (header, age, id, element(id) )
^
SyntaxError: invalid syntax
D:\FORFONE>
Dont work V2
BadWolfYe said:
Dont work V2
Click to expand...
Click to collapse
Wokr with python-2.7.12, test 100%
D:\FORFONE>python oeminfo_decode_v2.py -i oeminfo
hdr: OEM_INFO age:00000003 id:0008
hdr: OEM_INFO age:00000001 id:0012 Region
hdr: OEM_INFO age:00000003 id:0042
hdr: OEM_INFO age:00000005 id:0043
hdr: OEM_INFO age:00000001 id:0044 rescue Version
hdr: OEM_INFO age:00000001 id:004a 16 byte string 0 terminated
hdr: OEM_INFO age:00000001 id:004e Rom Version
hdr: OEM_INFO age:00000001 id:0053
hdr: OEM_INFO age:00000001 id:0057
hdr: OEM_INFO age:00000001 id:005a
hdr: OEM_INFO age:00000001 id:005b Hardware Version / Customizeable
hdr: OEM_INFO age:00000001 id:005d
hdr: OEM_INFO age:00000001 id:0061 Hardware Version
hdr: OEM_INFO age:00000009 id:0062 PRF?
hdr: OEM_INFO age:00000001 id:0063
hdr: OEM_INFO age:00000003 id:0065 Rom Version / Customizeable
hdr: OEM_INFO age:00000009 id:0066
hdr: OEM_INFO age:00000077 id:0069
hdr: OEM_INFO age:0000001b id:006a CN or CDMA info 0x6a
hdr: OEM_INFO age:00000083 id:006b CN or CDMA info 0x6b
hdr: OEM_INFO age:00000001 id:015f Logo Boot
hdr: OEM_INFO age:00000003 id:0160 Logo Battery Empty
hdr: OEM_INFO age:00000003 id:0161 Logo Battery Charge
hdr: OEM_INFO age:00000002 id:0008
hdr: OEM_INFO age:00000002 id:0042
hdr: OEM_INFO age:00000006 id:0043
hdr: OEM_INFO age:00000002 id:0044 rescue Version
hdr: OEM_INFO age:00000008 id:0062 PRF?
hdr: OEM_INFO age:00000004 id:0065 Rom Version / Customizeable
hdr: OEM_INFO age:0000000a id:0066
hdr: OEM_INFO age:00000076 id:0069
hdr: OEM_INFO age:0000001c id:006a CN or CDMA info 0x6a
hdr: OEM_INFO age:00000084 id:006b CN or CDMA info 0x6b
hdr: OEM_INFO age:00000002 id:015f Logo Boot
hdr: OEM_INFO age:00000002 id:0160 Logo Battery Empty
hdr: OEM_INFO age:00000002 id:0161 Logo Battery Charge
D:\FORFONE>
can you show us how to repack the file?
Hi, I'm very nOOb when it comes to programming, in fact, I don't really know anything.
It is possible that you can create an Oeminfo for me for Vodafone Spain?
I'm currently on Fri-l09b381c432.
If that's not possible, I won't bother you anymore, thank you very much.
P.s. The versión of oeminfo is l09c02
BadWolfYe said:
Dont work V2
Click to expand...
Click to collapse
Hola compadre mañico, no se si te va a llegar, algo me pasa con los mensajes privados, pero por intentarlo.
Has podido hacerte con un nuevo oeminfo?, yo necesito el de Vodafone que sería la C02, pero no hay tutia.
Y con este sistema no me entero, pues no tengo ni zorra de programación.
Espero puedas ayudarme, saludos.
I have refactored this to python3 and added as much pep8 as i could be bothered to, as well as fix paths on linux and added a few new field types. Enjoy!
Mistaken comment deleted
Is there any way to repack the unpacked oeminfo from a folder?
---------- Post added at 02:06 AM ---------- Previous post was at 02:03 AM ----------
Also how would you use the altering function as OP used as an example?
hackintosh5 said:
I have refactored this to python3 and added as much pep8 as i could be bothered to, as well as fix paths on linux and added a few new field types. Enjoy!
Click to expand...
Click to collapse
I would really appreciate it if you could give an example of how the repacking works.
After being frustrated at the lack of ability to find a functional European oeminfo for a CMR-W09 (MediaPad m5).
I decided to update the script to function properly and added a detailed usage example here:
GitHub - EtoTen/oeminfo-huawei: Unpack and repack Huawei oeminfo
Unpack and repack Huawei oeminfo. Contribute to EtoTen/oeminfo-huawei development by creating an account on GitHub.
github.com
I then used it to modify a CMR-W09 to the hw/eu / c432 region in order to receive updates.
lunarhonour said:
After being frustrated at the lack of ability to find a functional European oeminfo for a CMR-W09 (MediaPad m5).
I decided to update the script to function properly and added a detailed usage example here:
GitHub - EtoTen/oeminfo-huawei: Unpack and repack Huawei oeminfo
Unpack and repack Huawei oeminfo. Contribute to EtoTen/oeminfo-huawei development by creating an account on GitHub.
github.com
I then used it to modify a CMR-W09 to the hw/eu / c432 region in order to receive updates.
Click to expand...
Click to collapse
This is cool work. I think this can have a separate thread to discuss and help everyone.
I am stunned that the thing is still available in use and even extended!
hackintosh5, lunarhonour, balamu96m
Many thanks for your work and keeping it up!
hi , can anyone explain how to modify OEMinfo file that i extracted from huawei? i have a file and want to change model in it, ho to use this script to do that?
Related
I modify firmware for devices with chipset AllWinner H3. My problem is that when I modify system.fex I get bootloop.
I use alwinner-kitchen (by Miniand) for pack/unpack (system.fex): mkuserimg.sh -s SRC_DIR OUTPUT_FILE ext4 MOUNT_POINT 1024M.
After experimenting, I found that when I rebuild system.fex, I get bootloop.
If I only unpack and pack the image with the firmware, when I load the firmware to the device it works.
I have suggested that I need in another kitchen, for build system.fex.
PS Sorry for my English.
I root my coolpad 3320A and added a custom boot animation and now it won't load past the animation is just shuts off. I can access the System Recovery menu but I need the stock rom to get it working again. Can someone help me please?
I'm bricked.
Softbricked my Coolpad Rogue 3320a with SuperSU.
My only options to fix are:
1. Finding someone with a 3320a who is willing to dump their working system.img and upload it for me, so I can download it and fastboot flash the working system.img, to overwrite my corrupted system.
2. Waiting for stock rom to be released.
3. Smashing it with a Hammer.
Someone please be kind/Knowledgeable enough to help.
I'm also in need of a stock rom for this phone!
I ordered a new one from Amazon yesterday,will upload some dumps if someone can help me through the process. Still waiting on mail though.
Update: Phone arrived 5 minutes ago!!!.
Uploading System.img (easily relflashable with fastboot)
ZepyhrHD said:
I root my coolpad 3320A and added a custom boot animation and now it won't load past the animation is just shuts off. I can access the System Recovery menu but I need the stock rom to get it working again. Can someone help me please?
Click to expand...
Click to collapse
You MAY be able to fix this without the entire stock ROM,you should be able to connect it to a pc via fastboot cable,and reflash whatever IMG you corrupted via adb/fastboot in CMD... Once I get the new phone in the mail,I will post a download link here in this thread. (May also include some instructions on the process for future rogue users)
Here ya go XDA,maybe this will help some of you.
(Might upload other partitions later,but not today)
Download System.IMG here:
http://ow.ly/Gx8t3042SMg
Instructions Included (Requires a basic understanding of adb)
Hi everyone.
Stock +KingRoot'ed Partition Dump as well as the OTA UPDATE zip available here:
https://www.androidfilehost.com/?w=files&flid=126528
(this is rooted w/KingRoot, if you want to tinker you may need to grab the stock install-recovery.sh (as trying to install update fails for this file among other things, just a side-effect of using KingRoot to root.
Another thing to work out for that could brick you - Kingroot does a chattr +ia on install-recovery.sh - If you try to install the update and immutable attributes are present the update will fail and you may be left with a boot loop.
Since there's no custom recovery, and I couldn't get this thing to goto fastboot (didn't try very hard though), may be out of luck if you get bricked...
I strongly recommend NOT taking/using the OTA, but I have provided it here since I know some people may want to inspect/manually install it. If you do want updated apps I'd pull them from the update manually...
I returned this phone after I did the dump, so I'll be of no further use with it... but I hope this helps.
-tronik
Guide please
Can you please guide me how to reflash stock image? My coolpad rogue is stuck at ''Download package'' And whenever I press the c=volume down button to ''cancel'' it restarts phone and goes right back to it
I'm having toubles flashing the system.img. I tried doing this:
fastboot flash system system.img
I get this error: target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
and just hangs there and does nothing more
I had tried to redownload the file and re flashing but keep getting this error. If anyone is on please assist me on how to fix this if possible. I don't know if its the phone or fastboot that is having troubles.
*UPDATE* It sent its just takes a few minutes to send the system:cowboy
BIG BIG thanks to ApatheticEuphoria for the system.img i got my phone unbricked and working again
Phone
AustinGarrick1818 said:
I'm having toubles flashing the system.img. I tried doing this:
fastboot flash system system.img
I get this error: target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
and just hangs there and does nothing more
I had tried to redownload the file and re flashing but keep getting this error. If anyone is on please assist me on how to fix this if possible. I don't know if its the phone or fastboot that is having troubles.
*UPDATE* It sent its just takes a few minutes to send the system:cowboy
BIG BIG thanks to ApatheticEuphoria for the system.img i got my phone unbricked and working again
Click to expand...
Click to collapse
How did you get yours to work? -VON
coolpad road 3320A sistema arruinado
Alguien que me pueda ayudar ise root en mi telefono, y luego actualize el software y se me arruino solo enciende en modo recovery ayudemme a ver si ago algo mal al poner la imagen por medio de fastboot ya que solo me aparece asi
Microsoft Windows [Versión 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.
C:\Program Files\Minimal ADB and Fastboot>fastboot devices
4348a67b fastboot
C:\Program Files\Minimal ADB and Fastboot>fastboot flash system system.img
error: cannot load 'system.img'
C:\Program Files\Minimal ADB and Fastboot>fastboot update system.img
W/ ( 1276): Unable to open 'system.img': No such file or directory
error: failed to open zip file 'system.img': I/O Error
bigguccivon said:
How did you get yours to work? -VON
Click to expand...
Click to collapse
Just download the system.img file and reboot to fastboot mode (it will show on screen information mode or similar) and run:
fastboot erase system
fastboot flash system system.img
jose1914 said:
Alguien que me pueda ayudar ise root en mi telefono, y luego actualize el software y se me arruino solo enciende en modo recovery ayudemme a ver si ago algo mal al poner la imagen por medio de fastboot ya que solo me aparece asi
Microsoft Windows [Versión 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.
C:\Program Files\Minimal ADB and Fastboot>fastboot devices
4348a67b fastboot
C:\Program Files\Minimal ADB and Fastboot>fastboot flash system system.img
error: cannot load 'system.img'
C:\Program Files\Minimal ADB and Fastboot>fastboot update system.img
W/ ( 1276): Unable to open 'system.img': No such file or directory
error: failed to open zip file 'system.img': I/O Error
Click to expand...
Click to collapse
Or do you have the system.img avalable ??
Many of 6GB RAM Nokia X6 has an issue, that you can't flash system partition properly - after 1st sparse flashed, fastboot will prompt "error flashing partition".
This guide introduces a workaround for this issue.
4GB RAM Nokia X6 / 6.1 Plus needn't to follow this guide.
And 6GB RAM Nokia 7 Plus needn't to follow this guide.
Or if your 6GB RAM Nokia X6 can flash stock firmware properly, you needn't to read this guide any further.
Click to expand...
Click to collapse
I still don't clear the pattern of 6GB RAM Nokia X6 that can't flash partitions.
Prerequisites:
- Bootloader must be completely unlocked
- You have fully unpacked firmware
- Use OST LA 6.0.4 or NOST v0.4 by @stollD
Here's how:
1. Make a copy of DRG-2XXX-0-00XX-B0X.mlf at the same directory, in this example, I made a copy of "DRG-221F-0-00CN-B03.mlf".
2. Use Notepad++ or any code editor that supports unix to open "DRG-221F-0-00CN-B03 - Copy.mlf".
3. Navigate to these codes.
Code:
[Package Info 31]
PACKAGE_NAME = "system_a"
BOOT_NAME = "system_a"
OPTION = 0x40000
IMAGE_FILE = "DRG-0-221F-00CN-system.img"
[Package Info 32]
PACKAGE_NAME = "system_b"
BOOT_NAME = "system_b"
OPTION = 0x40000
IMAGE_FILE = "DRG-0-221F-00CN-system_other.img"
And modify them to:
Code:
[Package Info 31]
PACKAGE_NAME = "system_a"
BOOT_NAME = "system_a"
OPTION = 0x4
IMAGE_FILE = ""
[Package Info 32]
PACKAGE_NAME = "system_b"
BOOT_NAME = "system_b"
OPTION = 0x4
IMAGE_FILE = ""
Save it.
4. Use OST LA or NOST to flash this - you'll definitely encounter C6DA error, but don't worry about that.
5. Download TWRP for Nokia 7 Plus that doesn't require flash from here (TBA) and execute these commands under OST LA installation directory:
NOTE: YOU MUST USE fastboot-android.exe included in OST LA - DO NOT USE fastboot.exe provided by Google.
Click to expand...
Click to collapse
Code:
.\fastboot-android format userdata
.\fastboot-android reboot-bootloader
.\fastboot-android boot D:\Nokia7plusv3.2.1.0-noflash.img
After your phone booted to TWRP, you may find the touch screen doesn't work, don't worry - we only need to use adb commands.
6. Execute following commands:
[QUOTE]
You can use adb.exe from both OST LA or platform tools.
[/QUOTE]
[CODE]
.\adb push D:\DRG-221F-0-00CN-B03.nb0_unpacked\systeminfo.img /data/systeminfo.img
.\adb push D:\DRG-221F-0-00CN-B03.nb0_unpacked\DRG-0-221F-00CN-system.img /data/system_a.img
.\adb push D:\DRG-221F-0-00CN-B03.nb0_unpacked\DRG-0-221F-00CN-system_other.img /data/system_b.img
.\adb shell
simg2img /data/system_a.img /data/system_a.img.ext4
simg2img /data/system_b.img /data/system_b.img.ext4
dd if=/data/systeminfo.img of=/dev/block/bootdevice/by-name/systeminfo_a
dd if=/data/systeminfo.img of=/dev/block/bootdevice/by-name/systeminfo_b
dd if=/data/system_a.img.ext4 of=/dev/block/bootdevice/by-name/system_a
dd if=/data/system_b.img.ext4 of=/dev/block/bootdevice/by-name/system_b
rm /data/systeminfo.img
rm /data/system_a.img
rm /data/system_b.img
reboot
That's all for the whole 6GB RAM Nokia X6 stock firmware flashing guide.
If you're a developer, 6GB RAM Nokia X6 is definitely unsuitable for developing.
Thanks for the guide, it will be very useful for me. I'm trying to flash this phone for a long time and I just can't unbrick it.
A few issues I've come over while following it:
OST_LA and NOST didn't want to flash DRG-221F-0-00CN-B03 ("you need to update your software" or something like that), so I had to unpack DRG-229D-0-00WW-B01.
I couldn't find Nokia7plusv3.2.1.0-noflash.img anywhere, so I used Twrp_N6.1plus_global_Aug.
When I try to use simg2img in adb shell, I get the following error:
Code:
~ # simg2img /data/system_a.img /data/system_a.img.ext4
error: file_write: write: Out of memory
Cannot write output file
---
Update: I've flashed 250A and it works like a charm! Just had to edit the .mlf according to this guide.
Hi @hikari_calyx,
have you tried flashing Nokia X6 6GB version to 6.1 Plus International Version (Android One)?
Anything I need to consider?
Hey I bought the Nokia x6 TA-1099 6gb Chinese variant it came with the global ROM 00WW_3_38A I believe it was flashed by the seller. When I got the phone I saw there was an OTA to update the pie to v3.45B I want to know if it's safe to update via OTA because it's meant for 6.1plus
:good: thanks
twrp fails
when iam flashing twrp it is showing that no such partiton is found recovery b
Recently purchased an iplay 7t after reading the xda review. This is replacing an LG v400 tablet that I had rooted. I updated the iplay to build T701_V1.20_20191112, enabled developer options, enabled oem unlock bootloader, found the corresponding firmware pac, installed magisk and used it to patch boot.img. So far so good.
I entered fastboot, then I attempted to flash the modified boot.img and was told:
Code:
target didn't report max-download-size
sending 'boot' (18584 KB)...
OKAY [ 0.593s]
writing 'boot'...
FAILED (remote: Flashing Lock Flag is locked. Please unlock it first!)
finished. total time: 0.608s
I tried various options to unlock the bootloader:
Code:
> fastboot getvar unlocked
unlocked:
finished. total time: -0.000s
> fastboot oem unlock
...
FAILED (remote: unknown cmd.)
finished. total time: -0.000s
> fastboot oem unlock-go
...
FAILED (remote: unknown cmd.)
finished. total time: 0.002s
> fastboot flashing get_unlock_ability
...
FAILED (remote: Not implement.)
finished. total time: -0.000s
> fastboot flashing unlock
...
FAILED (remote: Not implemet.)
finished. total time: -0.000s
> fastboot flashing unlock_critical
...
FAILED (remote: Not implement.)
finished. total time: 0.016s
> fastboot flashing unlock_bootloader
fastboot: usage: unknown 'flashing' command unlock_bootloader
> fastboot flashing unlock_bootloader_nonce
fastboot: usage: unknown 'flashing' command unlock_bootloader_nonce
Okay ... fine. I fired up SPD Research tool and attempted to use it to flash the modified boot.img. It transfers the image and then times out.
As a sanity check I used SPD Research tool to flash the original boot.img and that worked fine.
I'll note the modified image is smaller than the original, however padding the modified image with zeros to the same size didn't seem to help. Using SPD Research tool to flash the padded image still timed out.
I am looking to open a request up on the Alldocube support site (currently their registration form is giving me an error), in the meantime ... suggestions? Has anyone successfully flashed a modified boot.img on this device / rooted this device?
in the "developer option" on your phone, you should enable the "allow unlock bootloader" option.
DR.Doyle said:
in the "developer option" on your phone, you should enable the "allow unlock bootloader" option.
Click to expand...
Click to collapse
Yes ... I have that enabled.
Okay I was able to unlock the bootloader by using the procedure documented for the Qin 2 Pro. With the bootloader unlocked on reboot the device notes:
Code:
INFO: LOCK FLAG IS : UNLOCKED!!!
followed by:
Code:
WARNING: LOCK FLAG IS : UNLOCKED, SKIP VERIFY!!!
Using fastboot I can now reflash the stock vbmeta and the stock recovery without any problems and the stock recovery boots fine.
Also if I re-sign the stock recovery, then I can't flash it (fastboot flash hangs) until I've flashed a modified vbmeta containing the new public key for the re-signed recovery. Meaning flashing vbmeta is "working".
All this seems like I'm on the right track.
However attempting to boot into the re-signed stock recovery results in:
Code:
INFO: LOCK FLAG IS : UNLOCKED!!!
followed by the device hanging (without displaying the WARNING message) so there is still something that's unhappy.
Any thoughts on how to get to the point that I can flash a useable re-signed stock recovery? If I can get that to work, then I should be in good shape to install magisk.
jwehle said:
Okay I was able to unlock the bootloader by using the procedure documented for the Qin 2 Pro. With the bootloader unlocked on reboot the device notes:
Code:
INFO: LOCK FLAG IS : UNLOCKED!!!
followed by:
Code:
WARNING: LOCK FLAG IS : UNLOCKED, SKIP VERIFY!!!
Using fastboot I can now reflash the stock vbmeta and the stock recovery without any problems and the stock recovery boots fine.
Also if I re-sign the stock recovery, then I can't flash it (fastboot flash hangs) until I've flashed a modified vbmeta containing the new public key for the re-signed recovery. Meaning flashing vbmeta is "working".
All this seems like I'm on the right track.
However attempting to boot into the re-signed stock recovery results in:
Code:
INFO: LOCK FLAG IS : UNLOCKED!!!
followed by the device hanging (without displaying the WARNING message) so there is still something that's unhappy.
Any thoughts on how to get to the point that I can flash a useable re-signed stock recovery? If I can get that to work, then I should be in good shape to install magisk.
Click to expand...
Click to collapse
Dear jwehle:
good job, i have also modify the pac firmware file which based on chinese vesion firmware:T701-1101-vbmetapri-vennofbe-systemnore-recpri01.pac
What's modified:
1.resgin the vbmeta img
2.delete fbe Force encryption in vendor partitions
3.delete the script in system.img to prevent factory recovery restore
4.modify recovery.img to a magisk build-in recovery
please use SPD_Research_Tool to flash the pac,change the android os language from chinese to english ,install magiskmanager app ,and the use adb command (adb reboot recovery)to let tablet reboot to recovery.
after tablet reboot to android os again ,open magiskmanager app,you can see the magisk can get root authority .
how to change language from chinese to english,please see attach png file.
Considering that the Android os you are using is in English version(including Google services),according to the modification points above, you can try to use the vbmeta and recovery (built in magisk) modified by your own signature , and then delete the fbe Force encryption、 recovery restoration in the system and vendor images , then use the SPD_Research_Tool to package the imgs into a pac image, flash the pac image, install the magiskmanager app, and use the adb command to restart the machine into recovery mode, so you can use magisk to get root permissions.
twrp egg:https://mega.nz/#!YZ9VDZbT!1ptlOI6g3FS_ES-cLGhLy9ybGtdHQ8vzVHaasAXglXo
and last thanks PeterCxy on xda 、the other masters sifu on 4pda agian.
wangyiling said:
Dear jwehle:
good job, i have also modify the pac firmware file which based on chinese vesion firmware:T701-1101-vbmetapri-vennofbe-systemnore-recpri01.pac
What's modified:
1.resgin the vbmeta img
2.delete fbe Force encryption in vendor partitions
3.delete the script in system.img to prevent factory recovery restore
4.modify recovery.img to a magisk build-in recovery.
Click to expand...
Click to collapse
Thanks for supplying the modified PAC and for explaining the changes.
Your PAC seemed to work fine and now that I have a better understanding
of things I should be able build my own PAC when I have a chance.
Your time and effort in explaining things is appreciated.
What's the significance of removing the encryption for the vendor partitions?
jwehle said:
What's the significance of removing the encryption for the vendor partitions?
Click to expand...
Click to collapse
the vendor img in my pac，just use ext4 format.i have use simg2img convert the oringin vendor img to ext4 format,and modify the fstab file in vendor/etc folder.
fstab.sp9832e_1h10：
Code:
/dev/block/platform/soc/soc:ap-ahb/20600000.sdio/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inline_xattr,inline_data wait,check,[COLOR="DarkOrange"]fileencryption[/COLOR]=aes-256-xts,reservedsize=128M
/dev/block/platform/soc/soc:ap-ahb/20600000.sdio/by-name/userdata /data ext4 noatime,nosuid,nodev,nomblk_io_submit,noauto_da_alloc wait,check,[COLOR="darkorange"]fileencryption[/COLOR]=aes-256-xts
---------->
Code:
/dev/block/platform/soc/soc:ap-ahb/20600000.sdio/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inline_xattr,inline_data wait,check,[COLOR="darkorange"]encryptable[/COLOR]=aes-256-xts,reservedsize=128M
/dev/block/platform/soc/soc:ap-ahb/20600000.sdio/by-name/userdata /data ext4 noatime,nosuid,nodev,nomblk_io_submit,noauto_da_alloc wait,check,[COLOR="darkorange"]encryptable[/COLOR]=aes-256-xts
wangyiling said:
the vendor img in my pac，just use ext4 format.i have use simg2img convert the oringin vendor img to ext4 format,and modify the fstab file in vendor/etc folder.
Click to expand...
Click to collapse
Actually, I was more curious as to why it was necessary / desirable to remove the encryption from the vendor partitions.
jwehle said:
Actually, I was more curious as to why it was necessary / desirable to remove the encryption from the vendor partitions.
Click to expand...
Click to collapse
Just for twrp to read the data partition, convenient for personal use。
It looks like the issue on this tablet is similar to what the magisk documentation mentions regarding the new Samsung tablets. Meaning after the bootloader is unlocked when rooting you should flash newly signed versions of the following:
Code:
vbmeta
boot
recovery
What was happening is when the system started normally it saw that recovery image had been modified so it checked if the boot image was the factory standard image. Since I hadn't touched the boot image the OS went ahead and attempted to replace the recovery image I flashed with a standard recovery image generated on the fly from the factory standard boot image. This caused a soft-brick when I rebooted into recovery since that recovery image wasn't signed using the public key specified by my replacement vbmeta.
By also flashing a newly signed boot image because the signature is different from what's it knows about the system no longer attempts to use it to refresh the recovery image.
Here's an outline of what I did to successfully root the device:
Use the Qin 2 Pro instructions / tools to unlock the boot loader.
Flash the appropriate factory standard firmware to establish a know starting point. I used iplay7t(T701)-Android9.0-ALLDOCUBE-191112 from the Alldocube web site.
Use SPD Rsearch Tool to extract vbmeta-sign.img, boot.img, and recovery.img.
Use avbtool (with the below patch) to extract the public keys from vbmeta-sign.img like so:
Code:
avbtool info_image --image vbmeta-sign.img.
Use make (with the below makefile) to sign vbmeta, boot, and recovery using a new key.
Flashed vbmeta, boot, and recovery.
Booted into recovery, saw that it worked, and did a factory reset.
Used magisk to patch recovery.img in the normal fashion, signed the patched recovery using the new key, and flashed the patched recovery.
Proceed to finish installing magisk in the normal fashion.
Notes:
rsa4096_vbmeta.pem is the private key mentioned in the Qin 2 Pro article.
The dhtbsign-vbmeta command is basically the dhtb signing python script from Qin 2 Pro article.
Here's the trival patch for avbtool to dump the public keys.
Code:
--- avbtool 2020-02-22 22:11:55.107787032 -0500
+++ avbtool.dumpkeys 2020-02-22 22:15:36.046283077 -0500
@@ -1657,6 +1657,10 @@ class AvbChainPartitionDescriptor(AvbDes
Arguments:
o: The object to write the output to.
"""
+ kfd = open(self.partition_name, "w");
+ kfd.write(self.public_key);
+ kfd.close();
+
o.write(' Chain Partition descriptor:\n')
o.write(' Partition Name: {}\n'.format(self.partition_name))
o.write(' Rollback Index Location: {}\n'.format(
Here's the makefile I used for signing the images.
Code:
all: boot-sign.img recovery-sign.img vbmeta-sign.img
vbmeta-sign.img: Makefile avb4096_pkmd.bin keys/*
avbtool make_vbmeta_image --output vbmeta.img --padding_size 16384 \
--key ../rsa4096_vbmeta.pem --algorithm SHA256_RSA4096 --flag 0 \
--chain_partition boot:1:avb4096_pkmd.bin \
--chain_partition system:3:keys/system \
--chain_partition vendor:4:keys/vendor \
--chain_partition product:10:keys/product \
--chain_partition dtbo:9:keys/dtbo \
--chain_partition recovery:2:avb4096_pkmd.bin \
--chain_partition l_modem:5:keys/l_modem \
--chain_partition l_ldsp:6:keys/l_ldsp \
--chain_partition l_gdsp:7:keys/l_gdsp \
--chain_partition pm_sys:8:keys/pm_sys \
--chain_partition dtb:11:keys/dtb
dhtbsign-vbmeta vbmeta.img vbmeta-sign.img
@rm -f vbmeta.img
avb4096_pkmd.bin: avb4096.pem
avbtool extract_public_key --key avb4096.pem --output avb4096_pkmd.bin
avb4096.pem:
openssl genrsa -out avb4096.pem 4096
boot-sign.img: boot.img avb4096.pem
cp boot.img boot-sign.img
avbtool add_hash_footer --image boot-sign.img \
--partition_name boot --partition_size 36700160 \
--key avb4096.pem --algorithm SHA256_RSA4096
recovery-sign.img: recovery.img avb4096.pem
cp recovery.img recovery-sign.img
avbtool add_hash_footer --image recovery-sign.img \
--partition_name recovery --partition_size 36700160 \
--key avb4096.pem --algorithm SHA256_RSA4096
@ jwehle，Very grateful for your detailed sharing
Did you have any trouble getting the tablet to populate the fastboot devices list?
I have USB drivers installed and can view the tablet's internal storage when it's not in fastboot mode. She's plugged directly into the mobo and I've tried two cables.
When in fastboot mode, it comes up in the Windows Device Manager as fastboot Gadget and drivers are apparently not available. I've tried using Zadig to feed it a driver of some kind, but still nothing.
MissAyako said:
Did you have any trouble getting the tablet to populate the fastboot devices list?
I have USB drivers installed and can view the tablet's internal storage when it's not in fastboot mode. She's plugged directly into the mobo and I've tried two cables.
When in fastboot mode, it comes up in the Windows Device Manager as fastboot Gadget and drivers are apparently not available. I've tried using Zadig to feed it a driver of some kind, but still nothing.
Click to expand...
Click to collapse
Seems the issue was with Windows. I thought I would be able to get the unlock token with Windows and then use WSL to do the rest of the signing, but apparently not.
Luckily I had an old laptop lying around. I threw Linux Mint on it and it worked just fine.
It didn't seem to work just using a live USB; I had to install Linux to the hard disk, but YMMV.
jwehle said:
It looks like the issue on this tablet is similar to what the magisk documentation mentions regarding the new Samsung tablets. Meaning after the bootloader is unlocked when rooting you should flash newly signed versions of the following:
Click to expand...
Click to collapse
This was wonderful, thank you! I've added some of my own notes below as an experience of what I encountered when attempting this process myself (spoiler'd because it is a lot).
I do not have enough post count to add links, but titles to the relevant articles has been added.
Follow steps in Article "Guide: How to Unlock Xiaomi Qin 2 (Pro) and Install Custom ROMs" from step 1 to (and including) step 10 (Unlocking section).
Notes:
- A Linux PC is necessary.
- You'll have to mark the "fastboot" file from the "Android_device_unlock.rar" archive as executable (chmod +x).
- Run the "fastboot" file as root.
- Getting the "SPD Research Tool" to pick up the tablet and not let the tablet try to move to either the charging
screen or the bootlogo is difficult, but do-able. Press and hold Power+Vol_Up and release when Windows does its
USB device detected chime.
- Flashing takes a few minutes (I think around 300 seconds).
- The SPD Research Tool extracts the PAC file contents into a folder. Grab the system images from there.
- The "avbtool" is available to be cloned via git from Google's repo
- The avbtool is a python script that is patched with three lines of code at line 1776:
Code:
kfd = open(self.partition_name, "w");
kfd.write(self.public_key);
kfd.close();
- When you use the patched avbtool on the vbmeta-sign.img file you copied (avbtool info_image --image vbmeta-sign.img)
it will produce several partitions with relative public keys that need to be stored in separate files for the next step.
The contents of the files are simply the public key and the partition name as the file name. Store the files in a folder named "keys".
- When creating the makefile, ensure that proper indentation is used. The code segment below is properly formatted (hopefully). If you get make errors, remove and re-indent the lines.
- If your "rsa4096_vbmeta.pem" keyfile is not placed alongside the makefile, ensure the --key flag points to this file.
- The makefile exists in the same directory as the system images.
- I had to insert local paths to the avbtool, as it was not installed to the system PATH.
- The dhtbsign-vbmeta.py command is located below. Make sure to mark this as executable as well.
Everything else is rather straightforward.
# makefile
Code:
all: boot-sign.img recovery-sign.img vbmeta-sign.img
vbmeta-sign.img: makefile avb4096_pkmd.bin keys/*
avbtool make_vbmeta_image --output vbmeta.img --padding_size 16384 \
--key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096 --flag 0 \
--chain_partition boot:1:avb4096_pkmd.bin \
--chain_partition system:3:keys/system \
--chain_partition vendor:4:keys/vendor \
--chain_partition product:10:keys/product \
--chain_partition dtbo:9:keys/dtbo \
--chain_partition recovery:2:avb4096_pkmd.bin \
--chain_partition l_modem:5:keys/l_modem \
--chain_partition l_ldsp:6:keys/l_ldsp \
--chain_partition l_gdsp:7:keys/l_gdsp \
--chain_partition pm_sys:8:keys/pm_sys \
--chain_partition dtb:11:keys/dtb
./dhtbsign-vbmeta.py vbmeta.img vbmeta-sign.img
@rm -f vbmeta.img
avb4096_pkmd.bin: avb4096.pem
avbtool extract_public_key --key avb4096.pem --output avb4096_pkmd.bin
avb4096.pem:
openssl genrsa -out avb4096.pem 4096
boot-sign.img: boot.img avb4096.pem
cp boot.img boot-sign.img
avbtool add_hash_footer --image boot-sign.img \
--partition_name boot --partition_size 36700160 \
--key avb4096.pem --algorithm SHA256_RSA4096
recovery-sign.img: recovery.img avb4096.pem
cp recovery.img recovery-sign.img
# dhtbsign-vbmeta.py file (from "How I Unlocked Xiaomi Qin 2 Pro and Installed Phh GSI")
Code:
#!/usr/bin/env python
import hashlib
import sys
f = open(sys.argv[1], "rb")
b = f.read()
sha = hashlib.sha256(b).digest()
f.close()
f = open("vbmeta_signed.img", "wb")
f.write(b)
f.seek(1048576 - 512)
f.write(b'\x44\x48\x54\x42\x01\x00\x00\x00')
f.write(sha)
f.write(b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x40\x00\x00')
f.seek(1048576 - 1)
f.write(b'\x00')
f.close()
wuxianlin has build a twrp device for T701.
i think this will be a help .
Help me
Sir help pliz same problem my device ,same chipset , Symphony i95 ,pliz sir modify my pac file pliz....
wangyiling said:
Dear jwehle:
good job, i have also modify the pac firmware file which based on chinese vesion firmware:T701-1101-vbmetapri-vennofbe-systemnore-recpri01.pac
What's modified:
1.resgin the vbmeta img
2.delete fbe Force encryption in vendor partitions
3.delete the script in system.img to prevent factory recovery restore
4.modify recovery.img to a magisk build-in recovery
please use SPD_Research_Tool to flash the pac,change the android os language from chinese to english ,install magiskmanager app ,and the use adb command (adb reboot recovery)to let tablet reboot to recovery.
after tablet reboot to android os again ,open magiskmanager app,you can see the magisk can get root authority .
how to change language from chinese to english,please see attach png file.
Considering that the Android os you are using is in English version(including Google services),according to the modification points above, you can try to use the vbmeta and recovery (built in magisk) modified by your own signature , and then delete the fbe Force encryption、 recovery restoration in the system and vendor images , then use the SPD_Research_Tool to package the imgs into a pac image, flash the pac image, install the magiskmanager app, and use the adb command to restart the machine into recovery mode, so you can use magisk to get root permissions.
twrp egg:https://mega.nz/#!YZ9VDZbT!1ptlOI6g3FS_ES-cLGhLy9ybGtdHQ8vzVHaasAXglXo
and last thanks PeterCxy on xda 、the other masters sifu on 4pda agian.
Click to expand...
Click to collapse
can i just flash the pac without unlocking the bootloader.
thanks in advances
hidroela said:
can i just flash the pac without unlocking the bootloader.
thanks in advances
Click to expand...
Click to collapse
yes,just falsh pac
wangyiling said:
yes,just falsh pac
Click to expand...
Click to collapse
i did unlocked the bootloader and flash the pac and follow the instructions for magisk to work, but after a third reboot Root was gone.
i don't know what I am missing.
Hi everyone, this is a short guide on how to flash a GSI on the A7 Lite (without TWRP).
Its a nice little tablet for the price but it doesn't have a very powerful SOC and for me the One UI is barely usable on this device. The launcher and the whole system UI feel extremely laggy, but apps generally run fine.
I tried phhusson's custom Android 12 GSI and the device was almost resurrected. Much much less UI lag and the battery life is the same as stock ROM. The only thing i found not working is MTP but i don't need it.
Since i saw a couple users here asking about GSIs i decided to make a very simple guide.
As always do this at your own risk. You may brick your device. You will void your warranty.
Follow the guide only if you know what your are doing. Read each step carefully and avoid copy pasting stuff randomly.
I won't go deep into details as i believe you should have some basic knowledge if you decide to do this.
The procedure sould work for both T220 and T225 (i tested it on a T220).
I did this on Windows using WSL for some of the steps.
Sources
Thanks to @kkoo and @Brepro1 for the useful info
- https://forum.xda-developers.com/t/...sing-odin-without-twrp-phh-lineageos.4114435/
- https://forum.xda-developers.com/t/...r-img-and-flashing-our-modifications.4196625/
Requirements
- Unlocked bootloader
If you haven't done this already follow the steps in parts 1-2 from:
[TUTORIAL] How To Unlock & Root Tab A7 Lite T220/T225, & Install LSPosed, Magisk, Mods
While some of these instructions are copied from other sources, I combined all the different things I learned, because no one guide was sufficient, and all needed additional info, so I expanded it all to one place. Part I is partly from...
forum.xda-developers.com
- Latest official ROM
I used T220XXU1AVE1 for EUX region
Samsung Galaxy Tab A7 Lite Firmware Download SM-T220 Free Download
Samsung Galaxy Tab A7 Lite Firmware Download SM-T220 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
- Download your preferred GSI
I used AOSP 12.1 v414 with gapps from phhusson
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
- Clean vbmeta.img from Google
https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
Tools
- lz4
Releases · lz4/lz4
Extremely Fast Compression algorithm. Contribute to lz4/lz4 development by creating an account on GitHub.
github.com
- simg2img
[DEV][Tools] simg2img for Windows
Hello, although I'm working in Linux (VM too) I rewrote the SIMG2IMG so far for Windows (PE32, x86) Usage: simg2img.exe -i -o Optional: -d for debugging messages, listing all chunks of the image...
forum.xda-developers.com
- lpunpack and lpmake
[GUIDE] OTA Tools LPUnpack
Please see this URL https://android.googlesource.com/platform/build.git/+/eec4a7cba4face3370acb6293ab357879920b467 and this for more information. Hi everyone. I'm surprised I havent seen a thread about ota tools yet and lpunpack. This zip file...
forum.xda-developers.com
- tar-md5-script-tool
Use the attached tar-md5-script-tool.zip
Steps
1. Extract official ROM files (BL, AP, CP, CSC)
2. Extract AP .tar.md5
3. Decompress the extracted super.img.lz4
Code:
lz4 -d super.img.lz4 super.img
4. Convert the sparse super.img
Code:
simg2img super.img super.ext4.img
5. Unpack super.ext4.img
Code:
lpunpack super.ext4.img
I got 4 partitions in my image (should be the same for all T220/T225 ROMs):
- odm.img
- product.img
- system.img
- vendor.img
6. Replace system.img with your GSI (rename it to system.img)
7. Get the size of all partitions and the size of the original super.ext4.img (not the sparse super.img)
Code:
stat -c '%n %s' IMG_FILE.img
8. Repack super.img
Code:
lpmake --metadata-size 65536 \
--super-name super \
--metadata-slots 2 \
--device super:ORIGINAL_SUPER_IMG_SIZE \
--group main:SUM_OF_ALL_PARTITIONS_SIZES \
--partition odm:readonly:ODM_PARTITION_SIZE:main \
--image odm=./odm.img \
--partition product:readonly:PRODUCT_PARTITION_SIZE:main \
--image product=./product.img \
--partition system:readonly:SYSTEM_PARTITION_SIZE:main \
--image system=./system.img \
--partition vendor:readonly:VENDOR_PARTITION_SIZE:main \
--image vendor=./vendor.img \
--sparse \
--output ./super_new.img
Replace ORIGINAL_SUPER_IMG_SIZE, SUM_OF_ALL_PARTITIONS_SIZES, ODM_PARTITION_SIZE, PRODUCT_PARTITION_SIZE, SYSTEM_PARTITION_SIZE, VENDOR_PARTITION_SIZE with the values you obtained in step 7.
Read lpmake docs for a more detailed expalation of the args used above:
partition_tools - platform/system/extras - Git at Google
9. Compress the repacked super_new.img
Code:
lz4 -B6 --content-size super_new.img super_new.img.lz4
10. Compress the clean vmbeta.img
Code:
lz4 -B6 --content-size vbmeta.img vbmeta.img.lz4
11. Extract tar-md5-script-tool.zip
12. Put all the *.img.lz4 files extracted from AP .tar.gz in tar-md5-script-tool dir
13. Replace super.img.lz4 and vbmeta.img.lz4 in tar-md5-script-tool dir with your repacked and compressed super_new.img.lz4 (rename it to super.img.lz4) and the clean compressed vbmeta.img.lz4
14. Run batch.bat in tar-md5-script-tool dir
You will find the new AP .tar.md5 in the temp-folder subdir
15. Flash your custom AP .tar.md5 with Odin along with BL, CP, CSC from original ROM
16. Reboot into recovery and do a factory reset
17. Done
Can you share screenshot as I think treble projects are only stable on SD chipset.
Abish4i said:
Can you share screenshot as I think treble projects are only stable on SD chipset.
Click to expand...
Click to collapse
System lang is italian but should be easy to understand.
I found only a couple bugs so far in phhusson's GSI:
- in the launcher dragging apps from drawer to homescreen doesn't always work (just use another launcher)
- crashed once while searching in settings app
I use the tablet only for media consumption and some retrogaming, so there are probably other bugs i haven't noticed.
This is a generic guide, it won't include a "known issues" section since it largely depends on what GSI you choose.
I haven't tested this on the LTE version so i can't say for sure if mobile network works or not.
Unfortunately i don't have the time to make a custom ROM, test it and keep it updated here on the forum but maybe if there is enough interest someone will do it.
I hope other users will try to flash a GSI and share their experience here so we can gather some info on working/broken stuff, especially on the LTE model since i can't test that.
Hello,
I'm sorry but what am I missing here?
I'm a little fustrated cause after hours and hours of headaches I got to the second to last step which involves tar-md5-script-tool
I simply put all the .img.lz4 files from AP and replace super & vbmeta files which the ones that I converted and try to run the batch.bat as instructed.
However nothing happens and this is what the program spits out.
On the tar tool xda forum it says that it convers .img files, not .img.lz4 . Are we supposed to extract all the .img files from inside the .lz4 files?
I appreciate the guide but there are a lot of missing details I had to fill in and figure out myself, like the fact that from step 4 to step 8 you need to use WSL or a Linux distro (using simg2img for Windows messes things up so please use the one from otatools inside a linux bash)
Also for people that are not familiar with linux you need to type "./" in front of directed commands ( in this case ./simg2img ./lpunpack ./lpmake)
I'm not a developer or a programmer, maybe you wrote this guide for people more inclined to that, but for me this was pretty hard.
Noob here, but I'm running the "simg2img super.img super.ext4.img" and nothing happens for 5 min and when I'm aborting I'm getting a "Error reading sparse file header".
Any suggestions?
DanneSwe said:
Noob here, but I'm running the "simg2img super.img super.ext4.img" and nothing happens for 5 min and when I'm aborting I'm getting a "Error reading sparse file header".
Any suggestions?
Click to expand...
Click to collapse
Are you using the Windows version of simg2img? If yes, use the one from otatools inside Windows Subsystem for Linux
ReubenMCSM said:
Are you using the Windows version of simg2img? If yes, use the one from otatools inside Windows Subsystem for Linux
Click to expand...
Click to collapse
I can confirm simg2img doesn't seem to work on Windows, i used WSL.
@ReubenMCSM i will update the guide with more details in the future but i don't have much time right now.
For you specific issue, try to use the attached tar-md5-script-tool.
Great thanks!
What's the process with tar-md5-script-tool? Just moving the super.img to the folder and running the batch.bat didn't work the output file in the temp folder is 11 kb. Tried to change super.img to super.tar but no change.
Thanks for the tool, but unfortunately the output is the same, like the problem @DanneSwe has
It looks like the batch.bat script from the tar md5 tool linked in the guide is a bit different from the one i used. I will update the guide.
Try again with the version i attached in the post above.
- Extract the AP tar md5 from official rom
- Copy all .img.lz4 files in the tar-md5-script-tool folder
- Replace super.img.lz4 and vbmeta.img.lz4 (step 13)
- Launch batch.bat, output should look like this
- You will find AP_TAR_MD5_CUSTOM_FILE_ODIN.tar.md5 in temp-folder
It finally worked! I redid everything and also moved my folder to drive C instead of drive D, maybe this made the difference
ReubenMCSM said:
It finally worked! I redid everything and also moved my folder to drive C instead of drive D, maybe this made the difference
Click to expand...
Click to collapse
What GSI did you pick and could you upload the files you flashed?
I got simg2img to work by using
.\simg2img -i super.img -o super.ext4.img
packed img filename: super.img
output img filename: super.ext4.img
Wrote "super.ext4.img"
The lpunpack and lpmake step isnt working for me ive been at this for days, no luck.
Can someone please help me out by uploading custom AP .tar.md5(file with GSI, the modded one) along with BL, CP, CSC from original ROM to google drive?
thanks!
ramz.pa said:
The lpunpack and lpmake step isnt working for me ive been at this for days, no luck.
Can someone please help me out by uploading custom AP .tar.md5(file with GSI, the modded one) along with BL, CP, CSC from original ROM to google drive?
thanks!
Click to expand...
Click to collapse
I had the same issue. :/
Can someone help me with the T225 LTE model by compiling the AP please? Because for some reason the tar-md5-script tool isnt working for me
Thanks.
Successfully flashed GSI with magisk on my T220 following the OP's procedure. MTP is not working as the OP said. However, I can use my flash drive so I don't really miss MTP.
I chose "system-squeak-arm64-ab-vndklite-gapps-secure.img.xz" for GSI. "Treble Info" app can tell you what image would be compatible with your device.
If you want to use a different launcher like Nova instead of the default one, change the "Smallest width" setting from 600 to 598 in Developer options to hide the annoying taskbar.
AOSP-Mods and "Project Themer - Android 12+" work fine for me.
Here is my build for my device SM-T220 (SM-T220_EUX_T220XXU1AVE1):
GSI: system-squeak-arm64-ab-vndklite-gapps-secure.img.xz
Custom AP: https://www.filehosting.org/file/details/7045394/AP_TAR_MD5_CUSTOM_FILE_ODIN.tar.md5
Custom AP with Magisk patch: https://www.filehosting.org/file/details/7045714/magisk_patched-25101_cauJQ.tar
You can extract BL and Home_CSC from SM-T220_EUX_T220XXU1AVE1.
Notes: My device is actually SM-T220 XAR, but I have been updating it with SM-T220 EUX firmware versions without any issue.
Pleasance said:
Can someone help me with the T225 LTE model by compiling the AP please? Because for some reason the tar-md5-script tool isnt working for me
Thanks.
Click to expand...
Click to collapse
Here is the custom AP based on the following. Since I don't have SM-T225 device, can't verify it. However, I compiled the AP the same way I did for my SM-T220.
- SM-T225_EUX_T225XXU1AUJ1
- GSI: system-squeak-arm64-ab-vndklite-gapps-secure.img.xz
https://www.filehosting.org/file/details/7046296/AP_TAR_MD5_CUSTOM_FILE_ODIN.tar.md5
xpdragon said:
Here is the custom AP based on the following. Since I don't have SM-T225 device, can't verify it. However, I compiled the AP the same way I did for my SM-T220.
- SM-T225_EUX_T225XXU1AUJ1
- GSI: system-squeak-arm64-ab-vndklite-gapps-secure.img.xz
https://www.filehosting.org/file/details/7046296/AP_TAR_MD5_CUSTOM_FILE_ODIN.tar.md5
Click to expand...
Click to collapse
Thank you so much for compiling the AP for me bro but when i try to flash it with odin i get this error
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> preloader.img.lz4
<ID:0/004> FAIL!
For your information the current OS build on my tablet is INS with the baseband version of T225XXU1AVB2 and security patch of 1 Feb 2022 hope this helps you.
DanneSwe said:
What GSI did you pick and could you upload the files you flashed?
I got simg2img to work by using
.\simg2img -i super.img -o super.ext4.img
packed img filename: super.img
output img filename: super.ext4.img
Wrote "super.ext4.img"
Click to expand...
Click to collapse
GSI-12_SM-T220_EUX_T220XXU1AVE1_fac.zip
drive.google.com
Use this ONLY on SM-T220 (without SIM card) and on EUX version.
Pleasance said:
Thank you so much for compiling the AP for me bro but when i try to flash it with odin i get this error
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> preloader.img.lz4
<ID:0/004> FAIL!
For your information the current OS build on my tablet is INS with the baseband version of T225XXU1AVB2 and security patch of 1 Feb 2022 hope this helps you.
Click to expand...
Click to collapse
Here is GSI build for SM-T225_INS_T225XXU1AVB2
https://www.filehosting.org/file/details/7129248/GSI-12_SM-T225_INS_T225XXU1AVB2.zip