I'm following this guide:
https://forum.xda-developers.com/t/guide-t220-t225-flash-a-gsi-on-the-a7-lite-without-twrp.4456821/
and keep getting stuck on Step 5 where i have to unpack super.ext4.img.
When I run the command bash$ ./bin/lpunpack super.ext4.img I get the error read failed: Invalid argument
Anyone have any idea how to fix this?
Jroberts225 said:
I'm following this guide:
[GUIDE] [T220/T225] Flash a GSI on the A7 Lite (without TWRP)
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...
forum.xda-developers.com
and keep getting stuck on Step 5 where i have to unpack super.ext4.img.
When I run the command bash$ ./bin/lpunpack super.ext4.img I get the error read failed: Invalid argument
Anyone have any idea how to fix this?
Click to expand...
Click to collapse
Jroberts225 said:
I'm following this guide:
https://forum.xda-developers.com/t/guide-t220-t225-flash-a-gsi-on-the-a7-lite-without-twrp.4456821/
and keep getting stuck on Step 5 where i have to unpack super.ext4.img.
When I run the command bash$ ./bin/lpunpack super.ext4.img I get the error read failed: Invalid argument
Anyone have any idea how to fix this?
Click to expand...
Click to collapse
used linux os?
tom.android said:
used linux os?
Click to expand...
Click to collapse
I’m using Ubuntu 22.04 via WSL 2 on Windows 11
Jroberts225 said:
I’m using Ubuntu 22.04 via WSL 2 on Windows 11
Click to expand...
Click to collapse
CustomAP 2022
The only way to get away from the official firmware. Changes Degoogle (LeOS-TD.2.0 ) A13 GSI Home Launcher For SM-T225 FastbootD ☆☆☆ Tips and Tricks For [ LOS TD Unofficial GSI ] latest 2023-03-24 microG...
forum.xda-developers.com
Jroberts225 said:
I'm following this guide:
https://forum.xda-developers.com/t/guide-t220-t225-flash-a-gsi-on-the-a7-lite-without-twrp.4456821/
and keep getting stuck on Step 5 where i have to unpack super.ext4.img.
When I run the command bash$ ./bin/lpunpack super.ext4.img I get the error read failed: Invalid argument
Anyone have any idea how to fix this?
Click to expand...
Click to collapse
This might help.
Related
Hello
I am trying to flash OS lineage 14.1 in my One Plus X device. I getting the following error.
Comparing TZ version TZ.BF.2.0-2.0.0137 to TZ.BF.2.0-2.0.0134
assert failed: oppo.verify_trustzone ("TZ.BF.2.0-2.0.0137")=="1"
Updater process ended with ERROR 7.
Please help me resolve this error.
Thank you
simply change the 7 to a 4
Lu87ki said:
simply change the 7 to a 4
Click to expand...
Click to collapse
Did the same but this time different error showed up.
You need to update your bootloader. Here's the link for updating bootloader.
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
I've recently installed CherishOS on my N200, however, finding the information to do so was rather difficult so I've decided to compile an easy guide for those of you who want to upgrade. As a warning, I am not responsible if you brick your device, or if it malfunctions.
Install the Android SDK platform tools provided by Google. Do not use third-party tools.
On your N200, enable USB debugging and OEM unlocking.
Unlock the bootloader. (there are threads on this already)
Boot to fastboot - [adb reboot bootloader]
Download CherishOS and the GSI Flasher Tool provided below.
Extract the GSI Flasher Tool to any convenient location on your PC
Extract the CherishOS file, move it to the Flasher Tool folder, and rename it to system.img
Double click on the N200 GSI Installer batch file and start the flashing process.
Voila! Now you have Android 12 on your phone. This method also works with several other GSIs.
Links:
CherishOS - https://sourceforge.net/projects/gs....5-arm64_bgN-slim-Unoffficial.img.xz/download
GSI FastBoot Tool - https://www.mirrored.to/files/1BH90XXY/?hash=7b9499940eefa93ff646c191e5d79ad7&dl=0
Just installed this ROM on the MetroPCS variant and my bluetooth headphones don't play any audio. USB-C headphones work, but I assume wireless headphones don't, an example would be Galaxy Buds+
Edit: USB headphones will cut out seemingly at random, and the noise it makes is extremely similar to how it'd sound if you just unplugged them. I'm honestly new to the whole Android custom rom scene, and I don't know what goes on behind the scenes of rom creation or anything like that. Any help in troubleshooting and/or fixing the issue would be greatly appreciated, it'd kinda suck if I had to go back to stock N200 software, but also I'm not sure how to do that either. I'm sure there's a tutorial on here for it but I didn't check before flashing this. Probably a bad idea.
go to settings > phh treble settings > misc features > force disable a2dp offload
biff_train said:
go to settings > phh treble settings > misc features > force disable a2dp offload
Click to expand...
Click to collapse
That worked, thank you! Any explanation for what that setting means and why it does that?
LavaIceLilac said:
That worked, thank you! Any explanation for what that setting means and why it does that?
Click to expand...
Click to collapse
If my google-fu found this:
A2DP essentially means the audio is transferred to the Bluetooth device and then decoded. With it disabled the audio is decoded on your phone, compressed, and then sent to the device as an audio signal. Having it disabled is more lossy.
Click to expand...
Click to collapse
keeps failing for me at product flash and system flash
As soon as I get my bootloader unlock code I want to try this and will report back. Quick question though: does the native hotspot work on this rom on 5.8ghz? And if used on T-Mobile network, is the data capped for the hotspot?
• Pls help me I am Getting this error while installing Cherish OS in Nord N200
I
nvalid sparse file format at header magic
Sending sparse ‘system’ 1/4 (786352 KB) OKAY [ 18.114s]
Writing ‘system’ FAILED (remote: ‘Partition not found’)
fastboot: error: Command failed
I am getting this error while flashing gsi in oneplus N200 by using ADB
Please Help me
Param_Hacks_YT said:
• Pls help me I am Getting this error while installing Cherish OS in Nord N200
I
nvalid sparse file format at header magic
Sending sparse ‘system’ 1/4 (786352 KB) OKAY [ 18.114s]
Writing ‘system’ FAILED (remote: ‘Partition not found’)
fastboot: error: Command failed
I am getting this error while flashing gsi in oneplus N200 by using ADB
Please Help me
Click to expand...
Click to collapse
I'm not sure, but I think you need to be in fastbootd mode to install a GSI.
Once in fastboot, using this command should get you into fastbootd:
Code:
fastboot reboot fastboot
But I think this is the problem of partitions of Nord N200. Is there any fix for it ?
Your OnePlus Nord N200 is of Tmobile ? Because I think this is the problem of tmobile
Ok now I had fixed all the errors of installing gsi in OnePlus Nord N200. Now only one Error Left to solve, Please help me
THIS ERROR
FAILED (remote: 'Not enough space to resize partition')
GSIs on N200
The process of flashing alone is conventional, shouldn't even need a thread to detail, but still leaving a thread here for search indexing. With an unlocked BL, flash an ARM64 AB GSI within fastbootd, reboot to recovery, format userdata, reboot...
forum.xda-developers.com
You have installed this GSI in Tmobile Varient of OnePlus N200 ?
Param_Hacks_YT said:
You have installed this GSI in Tmobile Varient of OnePlus N200 ?
Click to expand...
Click to collapse
As soon as I get my bootloader unlock token I will be attempting to install this GSI onto the TMO variant. I'll let you know how it goes unless you succeed first!
Param_Hacks_YT said:
Ok now I had fixed all the errors of installing gsi in OnePlus Nord N200. Now only one Error Left to solve, Please help me
THIS ERROR
FAILED (remote: 'Not enough space to resize partition')
Click to expand...
Click to collapse
Did trying this on your TMO variant soft brick it?
edale1 said:
I'm not sure, but I think you need to be in fastbootd mode to install a GSI.
Once in fastboot, using this command should get you into fastbootd:
Code:
fastboot reboot fastboot
Click to expand...
Click to collapse
cannot get into fastbootd
• Ok now I can install the Android 12 GSI in my Nord N200. But please tell me how to Fix the Lagging of Android 12 gsis in Nord N200. Because it sometimes Lags
deleted.
i am getting the partition error because i was flashing gsi in bootloader so i tried to install the gsi in fastbootd mode by typing "adb reboot fastboot" and also i had tried the android 13 gsi in my oneplus N200.
Hello!
I don't think this question needs much information about my phone, so I'll just say:
I live in Europe, Poland. My model is: Rmx2170; I wanted to install a Custom ROM (Evolution X), but it requires android 11.
I was searching for quite a long time and still haven't found any WORKING Android 11, RUI 2.0 Firmware. And I came here to ask:
Does anyone have any of these / Know where I could get it?
Thanks
I found this file there.
Sadly, when installing the ROM on the recovery screen, I get this error:
Code:
Updater process ended with ERROR: 1
Error installing ZIP file '/external_sd/RMX2170_11_C.29.zip'
And with ADB & Sideload, I get this error:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload C:\Users\Jacob\Downloads\RMX2170_11_C.29.zip
adb: failed to read command: No error
Things I did, Recovery I used:
The Recovery Screen I used (the newest version on the page)
(starting from a device with only the recovery screen and no system)
So, first I Formatted Data and Wiped: Dalvik / Art Cache, Data and Cache just to be sure.
Then I tried to install the firmware that I posted above, using the recovery screen, and got this error:
Code:
Updater process ended with ERROR: 1
Error installing ZIP file '/external_sd/RMX2170_11_C.29.zip'
Then I wiped: Dalvik / Art Cache, Data and Cache again and tried to install it via. Sideload:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload C:\Users\Jacob\Downloads\RMX2170_11_C.29.zip
and got this error:
ADB: failed to read command: No error
Then I did the same stuff, but with one difference:
After every wipe, I would boot into the system and wait until it downloads (until I would see the language selection screen)
BUT I got the same errors...
By "wipe" I meant: Formatting data, and then wiping: Dalvik / Art Cache, Data and Cache.
My device:
Model: RMX2170
Last Used ROM: Android 10, RUI 2.0, Realme 7 Pro Firmware, I forgot the exact version.
Custom Recovery Screen (the latest on that site)
Trying to install: This Firmware (RUI 2.0), Android 11 (RMX2170_11_C.29.zip)
Does anyone know what could be causing this/ how to fix it?
JacobBoi_ said:
I found this file there.
Click to expand...
Click to collapse
Before someone smarter replies, try installing C20 (RMX2170PU_11_OTA_c20.zip). I call it a starter for custom 11 installations.
Also don't forget to flash vbmeta.img and patched_boot.img, you can find them on the telegram channel.
deserted said:
Before someone smarter replies, try installing C20 (RMX2170PU_11_OTA_c20.zip). I call it a starter for custom 11 installations.
Also don't forget to flash vbmeta.img and patched_boot.img, you can find them on the telegram channel.
Click to expand...
Click to collapse
Eh, I wanted to have the European version
But you can't have everything in life, I guess.
(I did NOT flash patched_boot.img because it corrupted my stuff)
(Also, I am not sure did I do the vbmeta.img thingie. I forgot, sorry.)
Nonetheless, the RMX2170PU_11_OTA_c20.zip works like a charm.
Thanks!
deserted said:
Before someone smarter replies, try installing C20 (RMX2170PU_11_OTA_c20.zip). I call it a starter for custom 11 installations.
Also don't forget to flash vbmeta.img and patched_boot.img, you can find them on the telegram channel.
Click to expand...
Click to collapse
Where could I find the download link of RMX2170PU_11_OTA_c20.zip?? please thank you
redeemer01 said:
Where could I find the download link of RMX2170PU_11_OTA_c20.zip?? please thank you
Click to expand...
Click to collapse
https://true-mirror-69.gitsauraj.workers.dev/0:/RMX2170PU_11_OTA_c20.zip
Can somebody help me with RUI3 WHERE to download ozip or zip??
Hello everyone!
I am in the process of rooting this device. I need to do this since I need to test / develop AR Apps. So either I buy a new phone or I root this one and try if it works (and by trying that avoiding buying one). After some driver issues - I solved them by using Linux instead of Windows - I ended up with TWRP. In TWRP - Install I was not able to install anything since I got some permission errors. Now I seem to be unable to even install TWRP by using
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
but the device is still recognized while in fastboot.
When I enter recovery I get a long list of errors. Like:
E: [libfs_mgr] Failed to open '/dev/block/platform/bootdevice/by-name/cache': No such file or directory.
Click to expand...
Click to collapse
or
E: [libfs_mgr] Failed to format /cache:No such file or directory
Click to expand...
Click to collapse
Is there anything left I could try to get a working TWRP with permissions?
Thanks for any hints!
Andreas
Basically, you can use mtkclient to unlock your bootloader, instead of going through all of the hassle involved with the mi_unlock tool! I have tested this on my global redmi 9c, running the latest MIUI. I tested this on Linux, but the same should apply running it from Windows.
You can follow the directions here:
Unlock Bootloader on MediaTek Devices using MTKClient
In this comprehensive tutorial, we will show you detailed steps to unlock the bootloader on your MediaTek device using MTKClient.
www.droidwin.com
Also you can make it even easier on yourself and use the current git version of mtkclient, (mtkclient current git clone) which includes mtk_gui. Download the git repo, make sure you have python installed, from inside the directory of the git repo you downloaded run:
Linux
$ pip install -r requirements.txt
or something like this in windows:
C:\gtkclient> python -m pip install -r requirements.txt
That will install all needed requirements to run the app, then you can run mtk_gui by running:
Linux:
$ ./mtk_gui
Windows:
C:\mtkclient> python mtk_gui
From there you will need to WITH PHONE OFF, hold down volume up, then plug in your phone. If all goes well, your phone should be detected and you can click the "Flash Tools" tab, and click "Unlock Bootloader"
PS: I have tested this on linux with a patched kernel, you can do this easily by downloading fireiso, a bootable linux environment with the kernel already patched. Download fireiso, make a bootable USB from it, then boot it up, download mtkclient really quickly, extract it, open a terminal and cd into the directory you extracted it to, run pip install -r requirements.txt, then run ./mtk_gui
PSS: Apparently there is a LiveDVD linked to on mtkclient's github page as well, but its 3.9 GB as opposed to fireiso's <1GB
mtkclient: https://github.com/bkerler/mtkclient
fireiso: https://github.com/amonet-kamakiri/fireiso
I'll be happy to help anyone who has questions, and I would like to hear back from anyone who successfully tests this using Windows, just for posterity.
Thanks folks, and I hope this helps some of you avoid that nasty unlook tool like I did! LOL
Or we can unlock it easier using MTKClient GUI 2.0
That's exactly what I mentioned in the thread if you read the whole thing
hello can i use mtkclient even if im blocked for 7 days in mi flash
aye69 said:
hello can i use mtkclient even if im blocked for 7 days in mi flash
Click to expand...
Click to collapse
no i tried with a mtk device, you will just get dm-verity corruption error but your device still locked
karl615 said:
Basically, you can use mtkclient to unlock your bootloader, instead of going through all of the hassle involved with the mi_unlock tool! I have tested this on my global redmi 9c, running the latest MIUI. I tested this on Linux, but the same should apply running it from Windows.
You can follow the directions here:
Unlock Bootloader on MediaTek Devices using MTKClient
In this comprehensive tutorial, we will show you detailed steps to unlock the bootloader on your MediaTek device using MTKClient.
www.droidwin.com
Also you can make it even easier on yourself and use the current git version of mtkclient, (mtkclient current git clone) which includes mtk_gui. Download the git repo, make sure you have python installed, from inside the directory of the git repo you downloaded run:
Linux
$ pip install -r requirements.txt
or something like this in windows:
C:\gtkclient> python -m pip install -r requirements.txt
That will install all needed requirements to run the app, then you can run mtk_gui by running:
Linux:
$ ./mtk_gui
Windows:
C:\mtkclient> python mtk_gui
From there you will need to WITH PHONE OFF, hold down volume up, then plug in your phone. If all goes well, your phone should be detected and you can click the "Flash Tools" tab, and click "Unlock Bootloader"
PS: I have tested this on linux with a patched kernel, you can do this easily by downloading fireiso, a bootable linux environment with the kernel already patched. Download fireiso, make a bootable USB from it, then boot it up, download mtkclient really quickly, extract it, open a terminal and cd into the directory you extracted it to, run pip install -r requirements.txt, then run ./mtk_gui
PSS: Apparently there is a LiveDVD linked to on mtkclient's github page as well, but its 3.9 GB as opposed to fireiso's <1GB
mtkclient: https://github.com/bkerler/mtkclient
fireiso: https://github.com/amonet-kamakiri/fireiso
Click to expand...
Click to collapse
it doesn't work for xiaomi devices
Yes, actually it does, I've unlocked the bootloader on every single MTK device I've owned, including my Xaiomi Redmi 9c
karl615 said:
Basically, you can use mtkclient to unlock your bootloader, instead of going through all of the hassle involved with the mi_unlock tool! I have tested this on my global redmi 9c, running the latest MIUI. I tested this on Linux, but the same should apply running it from Windows.
You can follow the directions here:
Unlock Bootloader on MediaTek Devices using MTKClient
In this comprehensive tutorial, we will show you detailed steps to unlock the bootloader on your MediaTek device using MTKClient.
www.droidwin.com
Also you can make it even easier on yourself and use the current git version of mtkclient, (mtkclient current git clone) which includes mtk_gui. Download the git repo, make sure you have python installed, from inside the directory of the git repo you downloaded run:
Linux
$ pip install -r requirements.txt
or something like this in windows:
C:\gtkclient> python -m pip install -r requirements.txt
That will install all needed requirements to run the app, then you can run mtk_gui by running:
Linux:
$ ./mtk_gui
Windows:
C:\mtkclient> python mtk_gui
From there you will need to WITH PHONE OFF, hold down volume up, then plug in your phone. If all goes well, your phone should be detected and you can click the "Flash Tools" tab, and click "Unlock Bootloader"
PS: I have tested this on linux with a patched kernel, you can do this easily by downloading fireiso, a bootable linux environment with the kernel already patched. Download fireiso, make a bootable USB from it, then boot it up, download mtkclient really quickly, extract it, open a terminal and cd into the directory you extracted it to, run pip install -r requirements.txt, then run ./mtk_gui
PSS: Apparently there is a LiveDVD linked to on mtkclient's github page as well, but its 3.9 GB as opposed to fireiso's <1GB
mtkclient: https://github.com/bkerler/mtkclient
fireiso: https://github.com/amonet-kamakiri/fireiso
Click to expand...
Click to collapse
How do I find out the proper usage for mtkclient? mtk script....does this allow me to use a .sh script with this parameter?
mdwooten212 said:
How do I find out the proper usage for mtkclient? mtk script....does this allow me to use a .sh script with this parameter?
Click to expand...
Click to collapse
So I have a Xiaomi 11T MTK Dimmensity 1200 and tried this method, all I get now is "dm-verity corruption error" the device is still locked. Can someone help me please?
danieleal said:
So I have a Xiaomi 11T MTK Dimmensity 1200 and tried this method, all I get now is "dm-verity corruption error" the device is still locked. Can someone help me please?
Click to expand...
Click to collapse
Try:
python3 mtk e userdata
mdwooten212 said:
Try:
python3 mtk e userdata
Click to expand...
Click to collapse
It doesn't work in newer firmware, only on 13.0.2 or earlier
danieleal said:
It doesn't work in newer firmware, only on 13.0.2 or earlier
Click to expand...
Click to collapse
There is a dm-verity corruption error. How do I solve it on my 11t device or will unlock tools work?
danieleal said:
So I have a Xiaomi 11T MTK Dimmensity 1200 and tried this method, all I get now is "dm-verity corruption error" the device is still locked. Can someone help me please?
Click to expand...
Click to collapse
did you solve the problem
safaonal said:
did you solve the problem
Click to expand...
Click to collapse
what's ur MIUI version?
safaonal said:
did you solve the problem
Click to expand...
Click to collapse
I think Xiaomi patched the bootloader (but not the brom) in some devices