Related
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction/About
This is just stock ww 6.5.27 deodexed rom, packed as ext4 system.img meant to be flash via fastboot, nothing fancy here.
Click to expand...
Click to collapse
Features:
Based on stock ww 6.5.27.
Deodexed.
Zipaligned.
Init.d sysinit.
Zipalign and sqlite init.d script added.
Dalvik optimization in build.prop.
Busybox 1.22.0 applet installed in /system/xbin.
Adblocking hosts file.
Xposed framework fix. Can install/update xposed without bootloop/stuck on booting.
Accessing sdcard fix for thirdparty apps. Can read/write/modify data on sdcard.
Updated asus standalone app from playstore ie camera, calendar, messaging etc.
Debloated by removing app that can be install from playstore eg gmail, youtube, google plus, google music, google book, google magazine, google game, google hangouts, omlet chat etc. If u want them u can just install from playstore.
Probably other things i forgot to list here...
Click to expand...
Click to collapse
What Works:
Everything in stock rom should work.
Click to expand...
Click to collapse
Bugs:
Fc after first boot, just turn off/reboot again and everything should be fine.
Click to expand...
Click to collapse
Installation Instructions:
U need to already have updated to 6.5.27 stock rom either full flash or update ota.
Because zenfone 4 got no custom recovery yet so this is meant to be flash from pc/laptop so u need to have pc/laptop.
Backup your data eg contact, sms, calendar, photos etc.
U need to install Intel android driver.
U need to have adb and fastboot tool, can download from my link below. Just extract the archive, ADB_FASTBOOT.7z somehere in root of drive eg in C or D.
Extract the rom, u will get system.img around 1gb in size. Put it in the same folder as adb and fastboot above.
Boot phone into droidboot mode by pressing volume up+power button together.
Connect phone via usb cable.
Open the adb and fastboot tool folder and double click on OPEN.CMD. Windows terminal will open.
Type in the terminal to erase cache
Code:
fastboot erase cache
and press enter.
Type in the terminal to erase data
Code:
fastboot erase data
and press enter.
Type in the terminal to erase system
Code:
fastboot erase system
and press enter.
Now to flash system, type in the terminal
Code:
fastboot flash system system.img
and press enter. Flashing system would take around 10minutes.
After success flash system, if u want root need to flash supersu. Download and put ASUS_ZENFONE_ROOT.zip in the adb and fastboot folder and type in terminal
Code:
fastboot flash update ASUS_ZENFONE_ROOT.zip
and press enter. Phone will reboot automatically and will flash the root zip, then it will reboot again into system. First boot would take longer to generate dalvik etc.
Click to expand...
Click to collapse
Download:
Click to expand...
Click to collapse
Thanks To/Credits:
God
Linus Torvalds and whole linux kernel team and contributors.
Google
Asus.
shakalaca
and many, many other people whose their tool/app/guide i've used to make this...
Click to expand...
Click to collapse
Thank you for this rom but i have hard bricked my phone flashing this rom would get to normal :crying:
what did u do anyway?
if u follow the instruction it should boot, and even its not booting then can always reflash to stock rom. this rom will only modify system partition.
boot, recovery, fastboot and all other partition wont be touched and can always recover back to stock rom.
great job sir... I will try
syaeful said:
great job sir... I will try
Click to expand...
Click to collapse
Edit :
Succes Deodexed.. Thank you very much sir
Is anyone know to swap the storage of this phone ???
Sent from my ASUS_T00I using XDA Premium 4 mobile app
anyone wanna root the newly released kk update can root using the root zip in first post
Hoping for a kitkat custom ROM soon! :victory:
updated to ww 6.5.27.
mdfzhi said:
updated to ww 6.5.27.
Click to expand...
Click to collapse
Can I use the root package in the 1st post with this update?
ong14 said:
Can I use the root package in the 1st post with this update?
Click to expand...
Click to collapse
yes.
mdfzhi said:
yes.
Click to expand...
Click to collapse
Thank you.
I'll get my zf4 tomorrow.
Can't wait to try your mod.
This was great..been for a while finding exploit for rooting this phone on kitkat..your deodexed one was great..nice job...hope this phone community will grow big...
Cheers.
Bro..where's link..I'm sutfing on xda app..
Nvm..opnened in browser..
Just downloaded root things..tomorrow will try this deodex..
Greet from Malaysia
actually i'm not really into roms, more into kernels. thats why the rom is just deodex and few changes only, no new added features. hated smali editing.
been waiting far too long for asus to unlock zenfone 4 bootloader so that i could compile kernel myself.
mdfzhi said:
actually i'm not really into roms, more into kernels. thats why the rom is just deodex and few changes only, no new added features. hated smali editing.
been waiting far too long for asus to unlock zenfone 4 bootloader so that i could compile kernel myself.
Click to expand...
Click to collapse
Thank you for your contributing in zf4.
I have one question;
How can I revert back to stock firmware?
Can I flash a full stock f/w directly via droid boot menu [sd download]?
Not sure about sd download option in droidboot, never use it before but what i always did to get to full stock is by downloading full rom zip from asus server, extract it to get another zip, copy it into internal memory via usb cable and when removing usb cable will get notification to update.
mdfzhi said:
Not sure about sd download option in droidboot, never use it before but what i always did to get to full stock is by downloading full rom zip from asus server, extract it to get another zip, copy it into internal memory via usb cable and when removing usb cable will get notification to update.
Click to expand...
Click to collapse
Thank you for quick reply.
I'll try your mod tomorrow. (My zf4 have 2 batteries of 1200mAh, and still charging one of them.)
Owh...yeah..nany news on asus for unlocking bootloader.
?
Thanks a lot .. U saved me from a soft brick ...
No news yet about the bootloader, no reply from Asus
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- A / B slot support
- EdXposed customized Magisk
- Stock boot backup
- Automation
Install guide:
- First, you should unlock your device
- Then enable USB debugging in Settings
- Install Java runtime environment in your Windows computer: http://java.com
- Double-click the MagiskInstaller_hotdog_20191111.jar then follow the prompts
(If double-click not work, you should use this command
Code:
java -jar MagiskInstaller_hotdog_20191111.jar
Tips:
- Any system version (include H2OS/OxygenOS) can use this tool
- Built-in Magisk version is EdXposed customized 20.1(20101), you can replace magiskboot,magiskinit,util_function.sh to your Magisk version in jar file /assets (do NOT replace boot_patcher.sh, it will brick your device to Qualcomm CrashDump Mode)
- OnePlus 7T should also be usable (I haven't tested it, because I don't have OnePlus 7T device)
- Thanks to @mauronofrio for his unofficial twrp.
- To use EdXposed, follow the official website and install modules: http://edxp.meowcat.org/
Download:
Google Drive
at last .. hope its work in global
fahadalkhalaf said:
at last .. hope its work in global
Click to expand...
Click to collapse
should works
its work perfect.y ..
now i have superSu root ..
many thanks
@mlgmxyysd Links to social media removed from OP. Please refer to Telegram and Whatsapp Channels - Going Forward
mlgmxyysd said:
[a great post]
Click to expand...
Click to collapse
Hi, thanks for posting your guide. I have a few questions if it's okay.
1. Where is the stock boot image backed up to?
2. If I needed to undo everything this guide achieves (e.g. for warranty or selling), would I...
A. Uninstall all Magisk modules that I may have installed, then remove Magisk using Magisk Manager, then uninstall Magisk Manager
B. Restore the backed up boot image. (I'm not sure how to do that but can probably find out how to do it using adb)
C. Relock the bootloader.
3. Can I let Magisk Manager update Magisk and update Magisk Manager? The tip about how I can replace Magisk files and the risk of bricking make me think that maybe I can't.
4. Because you're thanking @mauronofrio for his unofficial twrp, does that mean this replaces the stock recovery with that twrp?
Thank you!
mlgmxyysd said:
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- A / B slot support
- EdXposed customized Magisk
- Stock boot backup
- Automation
Install guide:
- First, you should unlock your device
- Then enable USB debugging in Settings
- Install Java runtime environment in your Windows computer: http://java.com
- Double-click the MagiskInstaller_hotdog_20191111.jar then follow the prompts
(If double-click not work, you should use this command
Code:
java -jar MagiskInstaller_hotdog_20191111.jar
Tips:
- Any system version (include H2OS/OxygenOS) can use this tool
- Built-in Magisk version is EdXposed customized 20.1(20101), you can replace magiskboot,magiskinit,util_function.sh to your Magisk version in jar file /assets (do NOT replace boot_patcher.sh, it will brick your device to Qualcomm CrashDump Mode)
- OnePlus 7T should also be usable (I haven't tested it, because I don't have OnePlus 7T device)
- Thanks to @mauronofrio for his unofficial twrp.
- To use EdXposed, follow the official website and install modules: http://edxp.meowcat.org/
Download:
Google Drive
Click to expand...
Click to collapse
Sir, I stuck at Flashing boot_b partition
And that time the phone have boot in to twrp
ricky886 said:
Sir, I stuck at Flashing boot_b partition
And that time the phone have boot in to twrp
Click to expand...
Click to collapse
Some devices are unable to run the ADB shell commands in recovery for unknown reasons
Anyone get EdXposed working after installing this Magisk?
cucumbersmell said:
Anyone get EdXposed working after installing this Magisk?
Click to expand...
Click to collapse
+1
Also does the safetynet passes along with EdXposed?
Ok thank God the Lord has given me a changed frame of mind cause I was about to slam my laptop and computer. I must be missing something. I have Java installed and downloaded the magisk jar and for the life of me I can't get it to work not by double clicking not by running as administrator nothing I can't get Java to pop up so I can put in the command. And I tried using the other method with adb and fastboot. I keep getting error that directory doesn't exist. I think I'm stuck with boring stock at least I got unlocked LOL oh well. Any help would be appreciated. Thanks
mlgmxyysd said:
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- A / B slot support
- EdXposed customized Magisk
- Stock boot backup
- Automation
Install guide:
- First, you should unlock your device
- Then enable USB debugging in Settings
- Install Java runtime environment in your Windows computer: http://java.com
- Double-click the MagiskInstaller_hotdog_20191111.jar then follow the prompts
(If double-click not work, you should use this command
Code:
java -jar MagiskInstaller_hotdog_20191111.jar
Tips:
- Any system version (include H2OS/OxygenOS) can use this tool
- Built-in Magisk version is EdXposed customized 20.1(20101), you can replace magiskboot,magiskinit,util_function.sh to your Magisk version in jar file /assets (do NOT replace boot_patcher.sh, it will brick your device to Qualcomm CrashDump Mode)
- OnePlus 7T should also be usable (I haven't tested it, because I don't have OnePlus 7T device)
- Thanks to @mauronofrio for his unofficial twrp.
- To use EdXposed, follow the official website and install modules: http://edxp.meowcat.org/
Download:
Google Drive
Click to expand...
Click to collapse
Is it working for McLaren edition too?
Root?
Will this root my 7tpro?
And is the process reversible?
stuck
So I run it and I get stuck at Patching boot for slot a...
so has anyone done a one plus 7t pro with this method ?
garny68 said:
so has anyone done a one plus 7t pro with this method ?
Click to expand...
Click to collapse
This method is for 7T pro.
Read carefully please
i cant even get it to open , double click the jar and nothing so i type command and get
C:\Users\garny>operable program or batch file.java -jar MagiskInstaller_hotdog_20191111.jar
'operable' is not recognized as an internal or external command,
operable program or batch file.
garny68 said:
i cant even get it to open , double click the jar and nothing so i type command and get
C:\Users\garny>operable program or batch file.java -jar MagiskInstaller_hotdog_20191111.jar
'operable' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Some users above also reporting errors with this method
So
https://forum.xda-developers.com/showpost.php?p=80894389&postcount=133
If you're on 10.0.4 try this patched boot IMG
thanks but im on 10.0.3
garny68 said:
thanks but im on 10.0.3
Click to expand...
Click to collapse
https://forum.xda-developers.com/7t...-3-patched-boot-image-oneplus-7t-pro-t3986351
Here
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- TWRP boots.
- Decryption is working.
- Vibration
- System, Vendor and Product partitions mount is working but you can't modify them.
- You can flash magisk, miui roms, kernels, firmwares, etc.
Not working:
- Partition formatting (upstream)
- ADB sideload (upstream)
Install guide:
To boot (Reccomended):
Code:
fastboot boot <twrp.img>
To install (NOT reccomended):
Code:
fastboot flash recovery <twrp.img>
Download:
Now build is checking "ro.boot.hwversion". If it is begined with "1" then use Mi 10 Pro cmi profile, otherwise it will use Mi 10 umi profile.
Please report ro.boot.hwversion if possible. You can get it from getprop command.
Mega Drive Link
Source code:
Device Tree
Recovery Source
Thanks:
@mauronofrio @bigbiff and more open source TWRP devs.
Mi 10 Pro (cmi) thread:
https://forum.xda-developers.com/xi...xperimental-unofficial-twrp-mi-10-10-t4106385
USB OTG ?
Hi,
very important for me: is USB OTG working to read ROM from it ?
thank you !
Tested : USB OTG not working.
fastboot reboot recovery.img hangs the phone.
Solved using another twrp for the moment.
adario73 said:
Hi,
very important for me: is USB OTG working to read ROM from it ?
thank you !
Click to expand...
Click to collapse
It should work but I could not test it for you...
Great. Here we start development section.
tested:
can not mount system and vendor.
if you choose : reboot - recovery ( in this TWRP), the device will hang on fastboot.
k1n9n0th1n9 said:
tested:
can not mount system and vendor.
if you choose : reboot - recovery ( in this TWRP), the device will hang on fastboot.
Click to expand...
Click to collapse
Could you fetch a copy of log at /cache/recovery/log.gz for me?
You can only mount them with read only flag. It's super partition's limit.
Will mi 10 get twrp and other custom roms stuff??
---------- Post added at 12:58 PM ---------- Previous post was at 12:57 PM ----------
No custom development till 5 months??!!
Hi guys, new build (rev. 2) has been uploaded. Tested fastboot flash recovery is working.
The way to fix it is just appending recovery dtbo from official recovery. OTG might still not working. Source code has been updated.
cc @k1n9n0th1n9 @adario73
simonsmh said:
Hi guys, new build (rev. 2) has been uploaded. Tested fastboot flash recovery is working.
The way to fix it is just appending recovery dtbo from official recovery. OTG might still not working. Source code has been updated.
cc @k1n9n0th1n9 @adario73
Click to expand...
Click to collapse
can not select partitions system and vendor to mount
k1n9n0th1n9 said:
can not select partitions system and vendor to mount
Click to expand...
Click to collapse
Even with read-only flag? You could only mount system and vendor as read-only.
Do not try to Chmod 755 cause phone won't boot! even after ROM installed and rooted, do not do that with any file manager cause will stop the phone from booting!
head_djmusic said:
Do not try to Chmod 755 cause phone won't boot! even after ROM installed and rooted, do not do that with any file manager cause will stop the phone from booting!
Click to expand...
Click to collapse
Just don't do that if you are unfamiliar with AVB. You could disable this security feature by reflash vbmeta.img with disable verity and disable verification flag with fastboot. You can find more infomation on Google.
k1n9n0th1n9 said:
can not select partitions system and vendor to mount
Click to expand...
Click to collapse
Hi guys, new build (rev. 3) has been uploaded for fixing mount issue, please test when you have free time.
simonsmh said:
Hi guys, new build (rev. 3) has been uploaded for fixing mount issue, please test when you have free time.
Click to expand...
Click to collapse
Decryption works fine.
First I chose [Mount]: System was not checked, Vendor had a checkmark. Then I unticked Vendor and tried to mount it again. But both aren't able to get mountet within rev.3.
Backing up System isnt working too.
recover log is attached.
nocturnoz said:
Decryption works fine.
First I chose [Mount]: System was not checked, Vendor had a checkmark. Then I unticked Vendor and tried to mount it again. But both aren't able to get mountet within rev.3.
Backing up System isnt working too.
recover log is attached.
Click to expand...
Click to collapse
It's pretty weird since I didn't have this issue on my side, could you try it at command line?
Code:
mount /dev/block/mapper/system /system_root
Then check the result it printed and see if it mounts under /system_root
I also remembered that I flashed the miui rom for testing twrp, and after that I could mount both system and vendor. Could you have a try?
-----
Could you grab a logcat for me?
Code:
adb logcat > logcat.log
nocturnoz said:
Decryption works fine.
First I chose [Mount]: System was not checked, Vendor had a checkmark. Then I unticked Vendor and tried to mount it again. But both aren't able to get mountet within rev.3.
Backing up System isnt working too.
recover log is attached.
Click to expand...
Click to collapse
same
simonsmh said:
It's pretty weird since I didn't have this issue on my side, could you try it at command line?
Code:
[B]1.: mount /dev/block/mapper/system /system_root[/B]
Then check the result it printed and see if it mounts under /system_root
I also remembered that I flashed the miui rom for testing twrp, and after that I could mount both system and vendor. 2. Could you have a try?
-----
Could you grab a logcat for me?
Code:
[B]3. adb logcat > logcat.log[/B]
Click to expand...
Click to collapse
1.: mount: '/dev/block/mapper/system/system_root' not in fstab
2.: I'm running MIUI.EU 12 20.5.24 (weekly)
3.: ADB Sideload isn't working in TRWP.
nocturnoz said:
It's pretty weird since I didn't have this issue on my side, could you try it at command line?
Then check the result it printed and see if it mounts under /system_root
I also remembered that I flashed the miui rom for testing twrp, and after that I could mount both system and vendor. 2. Could you have a try?
-----
Could you grab a logcat for me?
1.: mount: '/dev/block/mapper/system/system_root' not in fstab
2.: I'm running MIUI.EU 12 20.5.24 (weekly)
3.: ADB Sideload isn't working in TRWP.
Click to expand...
Click to collapse
1. There is a space in it.
2. I will have a try with eu at weekends.
3. Since you can decrypt your data, I suggest you put it in your /sdcard instead. I will try to fix sideload soon.
Still it would be very helpful if you could grab a logcat for me.
simonsmh said:
1. There is a space in it.
2. I will have a try with eu at weekends.
3.Since you can decrypt your data, I suggest you put it in your /sdcard instead. I will try to fix sideload soon.
Still it would be very helpful if you could grab a logcat for me.
Click to expand...
Click to collapse
1. mount /dev... gave an error that -t is required
1a.
Code:
mount -t /dev/blck/mapper/system /system_root
mount: '/dev/blck/dm-2' -> '/system_root': Device or resource busy
2. TWRP Backup is possible until vendor backup. Then I'll get Error 255.
3. How do I do that? :/
4. When I'm on my ROM MIUI 12, then I'll connect the phone via USB and launch the ADB logcat commmand? Or where do I have to get the logcat from?
nocturnoz said:
1. mount /dev... gave an error that -t is required
1a.
Code:
mount -t /dev/blck/mapper/system /system_root
mount: '/dev/blck/dm-2' -> '/system_root': Device or resource busy
2. TWRP Backup is possible until vendor backup. Then I'll get Error 255.
3. How do I do that? :/
4. When I'm on my ROM MIUI 12, then I'll connect the phone via USB and launch the ADB logcat commmand? Or where do I have to get the logcat from?
Click to expand...
Click to collapse
Hi,
I mean logcat of TWRP, you can grab it on TWRP boot. ADB sideload is confirmed not working for now.
Could you try my latest build (rev.4) first? I rebased upstream source to see if it would fix system mounting issue for you.
These are instructions to flash LineageOS 18.1 GSI builds on our SM-T500. The same instructions should work for any other GSI rom out there.
Some instructions here, like flashing an empty product.img and resizing system partition, are not necessary if you want to flash a rom that fits in system and bundles gapps with it.
Prerequisites:
* SM-T500 with BUJ1 FW
* Unlocked bootloader
* Verified Boot disabled
* TWRP installed
* fastboot and adb installed on your computer.
Step 1: boot to fastboot.
Boot in TWRP and press "reboot" -> "fastboot". Wait until the tablet reboots and, after a few seconds, check that you can see your device with
Code:
fastboot devices
Now flash product.img and system.img and resize system image to the entire available size of the super partition:
Code:
fastboot flash product product.img
fastboot erase system
fastboot flash system lineage-18.1-20211214-UNOFFICIAL-treble_arm64_bvS-vndklite.img
fastboot resize-logical-partition system 3940000000
fastboot reboot recovery
Step 2: back in recovery
We need to resize the logical system partition to take up all the space we asigned to it. That's only mandatory if you want to flash gapps later on. If your rom comes with gapps bundled you don't need to do this.
Code:
adb shell
mount /dev/block/bootdevice/by-name/system /system_root
umount /system_root
e2fsck -f /dev/block/bootdevice/by-name/system
resize2fs /dev/block/bootdevice/by-name/system 961915
Step 3: finish it
Now you need to go to "wipe" -> "format data" and confirm. After that you can flash gapps if you want. You must use MindTheGapps arm64 version.
If you choose to flash gapps you'll need to follow https://github.com/phhusson/treble_experimentations/wiki/Frequently-Asked-Questions-(FAQ)#how-to-bypass-certified-device-after-first-boot
Some stuff won't work out of the box (brightness, MTP, bluetooth or wired audio). Please see the next post to learn how to workaround these issues.
Known issues (and workarounds)
1. MTP doesn't work
You need to flash SM-T500-GSI-kernel.zip from TWRP. Do it only once unless you reverted back to stock boot.img.
2. The rom I've flashed (mostly PixelExperience) reboots after a few seconds/minutes
You need to flash SM-T500-GSI-kernel.zip from TWRP. Do it only once unless you reverted back to stock boot.img.
3. Brightness doesn't work
You need to flash SM-T500-GSI-brightness-fix.zip from TWRP. You need to repeat this again after flashing a new system.img with the same or different rom.
4. Audio doesn't work via bluetooth/jack headphones.
Follow the AUDIO FIX section of https://forum.xda-developers.com/t/...s-nairo-and-some-post-install-tweaks.4364963/, as suggested by @wesleyvanneck12345678
* kernel sources: https://github.com/pazos/android_kernel_samsung_gta4lwifi/
FAQ
Q: Which GSI variant should I choose?
A: arm64 ab. Use the vndklite variant if you want to flash gapps or fix the brightness.
Q: Do I need to format data after flashing a different ROM?
A: YES
Q: Do I need to format data after flashing a different version of the same ROM?
A: Most likely YES, but you can try without formatting and see if it boots.
Q: Do gapps survive rom changes (diffent versions of the same rom or different roms)?
A: NOPE. You need to flash them again.
Q: Do GSI roms work with Magisk?
A: They should if they're based on PHH builds and are up-to-date.
Q: How to bypass SafetyNet?
A: I don't know, I don't care.
Reserved
Thank you very much for this guide, this really opens things up for thre A7 as far as custom roms go. I do like the OneUI 3.1 on this tablet, however I find I don't use much of the OneUI specific features. An AOSP/Lineage build should be lighter on resources and storage.
I do have a question, when you do "fastboot flash product product.img", where exactly do you get the poroduct.img from? Is this somewhere in the stock firmware or do I find it elsewhere?
Thanks again!
Whoops, sorry. I forgot to attach it here. It is already attached in https://forum.xda-developers.com/t/...xy-tab-a7-10-4-sm-t500.4371123/#post-86050459, so you can pick it up from there if you're in a hurry. If not I will add it to OP.
All done! I'm now running the LineageOS 18.1 version you mentioned in the directions. So far so good, however after flashing both the brightness fix and the GSI kernel, I am still unable to control brightness and I do not have MTP. Just to clarify, I install both of these zips via the TWRP menu, correct?
One other thing that I've noticed is that the tablet does not sleep when closing the Samsung Book cover like it does in the stock OneUI. I wonder if a magisk or LSposed module could helo us out here?
paziusss said:
These are instructions to flash LineageOS 18.1 GSI builds on our SM-T500. The same instructions should work for any other GSI rom out there.
Some instructions here, like flashing an empty product.img and resizing system partition, are not necessary if you want to flash a rom that fits in system and bundles gapps with it.
Prerequisites:
* SM-T500 with BUJ1 FW
* Unlocked bootloader
* Verified Boot disabled
* TWRP installed
* fastboot and adb installed on your computer.
Step 1: boot to fastboot.
Boot in TWRP and press "reboot" -> "fastboot". Wait until the tablet reboots and, after a few seconds, check that you can see your device with
Code:
fastboot devices
Now flash product.img and system.img and resize system image to the entire available size of the super partition:
Code:
fastboot flash product product.img
fastboot erase system
fastboot flash system lineage-18.1-20211214-UNOFFICIAL-treble_arm64_bvS-vndklite.img
fastboot resize-logical-partition system 3940000000
fastboot reboot recovery
Step 2: back in recovery
We need to resize the logical system partition to take up all the space we asigned to it. That's only mandatory if you want to flash gapps later on. If your rom comes with gapps bundled you don't need to do this.
Code:
adb shell
mount /dev/block/dm-0 /system_root
umount /system_root
e2fsck -f /dev/block/dm-0
resize2fs /dev/block/dm-0 961915
Step 3: finish it
Now you need to go to "wipe" -> "format data" and confirm. After that you can flash gapps if you want. You must use MindTheGapps arm64 version.
If you choose to flash gapps you'll need to follow https://github.com/phhusson/treble_experimentations/wiki/Frequently-Asked-Questions-(FAQ)#how-to-bypass-certified-device-after-first-boot
Some stuff won't work out of the box (brightness, MTP, bluetooth or wired audio). Please see the next post to learn how to workaround these issues.
Click to expand...
Click to collapse
paziusss said:
These are instructions to flash LineageOS 18.1 GSI builds on our SM-T500. The same instructions should work for any other GSI rom out there.
Some instructions here, like flashing an empty product.img and resizing system partition, are not necessary if you want to flash a rom that fits in system and bundles gapps with it.
Prerequisites:
* SM-T500 with BUJ1 FW
* Unlocked bootloader
* Verified Boot disabled
* TWRP installed
* fastboot and adb installed on your computer.
Step 1: boot to fastboot.
Boot in TWRP and press "reboot" -> "fastboot". Wait until the tablet reboots and, after a few seconds, check that you can see your device with
Code:
fastboot devices
Now flash product.img and system.img and resize system image to the entire available size of the super partition:
Code:
fastboot flash product product.img
fastboot erase system
fastboot flash system lineage-18.1-20211214-UNOFFICIAL-treble_arm64_bvS-vndklite.img
fastboot resize-logical-partition system 3940000000
fastboot reboot recovery
Step 2: back in recovery
We need to resize the logical system partition to take up all the space we asigned to it. That's only mandatory if you want to flash gapps later on. If your rom comes with gapps bundled you don't need to do this.
Code:
adb shell
mount /dev/block/dm-0 /system_root
umount /system_root
e2fsck -f /dev/block/dm-0
resize2fs /dev/block/dm-0 961915
Step 3: finish it
Now you need to go to "wipe" -> "format data" and confirm. After that you can flash gapps if you want. You must use MindTheGapps arm64 version.
If you choose to flash gapps you'll need to follow https://github.com/phhusson/treble_experimentations/wiki/Frequently-Asked-Questions-(FAQ)#how-to-bypass-certified-device-after-first-boot
Some stuff won't work out of the box (brightness, MTP, bluetooth or wired audio). Please see the next post to learn how to workaround these issues.
Click to expand...
Click to collapse
I've tried this from both a Win11 and a Mint 20.2 box and get the same errors. The resize-logical-partition cmd unknown command and the fastboot reboot recovery says unknown target.
USE TWRP 3.6 from
[RECOVERY][UNOFFICIAL]TWRP 3.6.0 for 2020 Galaxy Tab A7 10.4[SM-T500]
/* * Disclaimer * * Your warranty is now void. * * We're not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com
You need a recent version of fastboot too. Get one
NeilR2 said:
All done! I'm now running the LineageOS 18.1 version you mentioned in the directions. So far so good, however after flashing both the brightness fix and the GSI kernel, I am still unable to control brightness and I do not have MTP. Just to clarify, I install both of these zips via the TWRP menu, correct?
One other thing that I've noticed is that the tablet does not sleep when closing the Samsung Book cover like it does in the stock OneUI. I wonder if a magisk or LSposed module could helo us out here?
Click to expand...
Click to collapse
MTP is disabled by default. You need to plug the tablet to your computer, go to the "slightly" hidden notification and select transfer files instead of the default "charge only".
Agree with the brightness thing. I will upload a new version when I have a minute. It should be placed in rw-system.sh, not in phh-on-boot.sh.
Thanks for the feedback on the sleepcover stuff. I think lineage has a package that does that job, maybe it isn't included on this build. No idea if you can handle it using magisk or hoking into zygote process, I guess not.
I've finally succeeded in flashing LOS 19 and doing all of the resizing bit. Final step is getting gapps flashed. The recommendation I saw was to use MindTheGapps. The closest one I could find was MindTheGapps-11.0.0-arm64-20210920_084011.zip and it didn't work. It said is was for LOS 18 "or higher". Is there one for LOS 19?
I would like to point out that my system_root partition is /dev/block/dm-1 and not /dev/block/dm-0... I have wondered if this was due to differing recoveries however I am using your latest recovery and it is the same for me... so I would suggest that others do:
Bash:
adb shell
cat /tmp/recovery.log
That will show which one system_root is located at then you can continue with the resize.. otherwise it will give an error saying there arent enough blocks...
ragarcia87 said:
I would like to point out that my system_root partition is /dev/block/dm-1 and not /dev/block/dm-0
Click to expand...
Click to collapse
Thanks!! Never thought about it . Fixed!
Would porting ubports be possible for this device?
paziusss said:
Known issues (and workarounds)
1. MTP doesn't work
You need to flash SM-T500-GSI-kernel.zip from TWRP. Do it only once unless you reverted back to stock boot.img.
2. The rom I've flashed (mostly PixelExperience) reboots after a few seconds/minutes
You need to flash SM-T500-GSI-kernel.zip from TWRP. Do it only once unless you reverted back to stock boot.img.
3. Brightness doesn't work
You need to flash SM-T500-GSI-brightness-fix.zip from TWRP. You need to repeat this again after flashing a new system.img with the same or different rom.
4. Audio doesn't work via bluetooth/jack headphones.
Follow the AUDIO FIX section of https://forum.xda-developers.com/t/...s-nairo-and-some-post-install-tweaks.4364963/, as suggested by @wesleyvanneck12345678
* kernel sources: https://github.com/pazos/android_kernel_samsung_gta4lwifi/
Click to expand...
Click to collapse
I flashed both the kernel and brightness zips but brightness slider still does nothing.
Juppy99 said:
Would porting ubports be possible for this device?
Click to expand...
Click to collapse
Someone please corrent me if I am wrong, but I think the stock kernel needs to have Halium patches applied to it for UbPorts to work. I am not sure what exactly is involved in doing this, but I believe that it is possible. Though that does not mean it will not have bugs without major work being done beyond patching the kernel.
lewmur said:
I flashed both the kernel and brightness zips but brightness slider still does nothing.
Click to expand...
Click to collapse
paziusss said:
For now you can get it working with just 3 commands, until you reboot your device:
Click to expand...
Click to collapse
paziusss said:
adb shell
su
echo 100 > /sys/class/backlight/panel0-backlight/brightness
Click to expand...
Click to collapse
This from the TWRP thread works, the zip didn't. I use Tasker to run the script every boot.
paziusss said:
d confirm. After that you can flash gapps if you want. You must use MindTheGapps arm64 version.
If you choose to flash gapps you'll need to follow https://github.com/phhusson/treble_experimentations/wiki/Frequently-Asked-Questions-(FAQ)#how-to-bypass-certified-device-after-first-boot
Some stuff won't work out of the box (brightness, MTP, bluetooth or wired audio). Please see the next post to learn how to workaround these issues.
Click to expand...
Click to collapse
The get info apk in that link doesn't work in LOS 19. Does anyone know of one that will? Or of another way to get the GFW id?
this is cool, thanks op.....worked a doddle on arch linux, after I followed your instructions for installing TWRP using heimdall
thanks again, u da man! hope you have a happy and prosperous 2022
Tirofog said:
This from the TWRP thread works, the zip didn't. I use Tasker to run the script every boot.
Click to expand...
Click to collapse
Sorry, could you explain better how you set up tasker for that? I can't seem to manage to do it. I 've read somewhere that tasker might have problems with sudo commands... thank you!
TWRP Disclaimer
Code:
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
After many months struggling with the source code, TWRP finally comes to the Surface Duo! Do not flash this boot image! TWRP will NOT boot directly into the system! Again: this is a tethered boot and should not be flashed/replacing the boot image installed on your device.
Special thanks to: @none24 Captain Throwback (TWRP team)
Requirements for Booting:- Unlocked Bootloader
- Latest Platform Tools
- TWRP image
How to Boot:With device connected to your PC and turned ON:
adb devices
adb reboot bootloader
fastboot boot boot_TWRP.img
And with that, you're booted into TWRP!
What is working:ADB Shell
ADB Push
MTP
Mouse Navigation
You tell me!
What is not working:Touch Screen
ADB Sideload
You tell me!
Firmwares Tested:
2021.1019.24 GEN
2022.215.137 GEN
2022.418.56 GEN
2022.817.13 GEN (Android 12L)
Changelog:Changelog 0.1.1
Updated TWRP for Android 12L November Update (2022.817.13)
If you still are currently on android 11, please remain using version 0.1.0 of TWRP!
Changelog 0.1.0
Data can now be Decrypted, but with no passcode set
Updated Kernel and other binaries to the June update (2022.418.25)
Spoiler: Changelog History
Version 0.0.4
Data can now be mounted, but only after a factory reset
ADB push and Zip flashing is confirmed working (See Post #19)
Firmwares Tested:
2022.215.137
Version 0.0.3
System, Vendor, and Product directories can be mounted as read-only
MTP enabled, but can't receive data
TWRP Crypto Scripts added
Firmwares Tested:
2021.1019.24 GEN
2022.115.10 GEN
Version 0.0.2
Root directory found, but cannot find system_root, vendor, and product directories
Internal Storage can now me mounted
ADB push to sdcard tested and works
Version 0.0.1
Initial Release
Download via Google Drive
*cracks knuckles* let's see..
JengaMasterG said:
TWRP Disclaimer
Code:
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
After many months struggling with the source code, TWRP finally comes to the Surface Duo! Do not flash this boot image! It is not tested to boot directly into the system! Again: this is a tethered boot and should not be flashed/replacing the boot image installed on your device.
Requirements for Booting:- Unlocked Bootloader
- Latest Platform Tools
- TWRP image
How to Boot:With device connected to your PC and turned ON:
adb devices
adb reboot bootloader
fastboot boot boot_TWRP.img
And with that, you're booted into TWRP!
What is working:ADB Shell
You tell me!
What is not working:Touch Screen
ADB Sideload
You tell me!
Versions Tested:
2022.115.10 GEN
Click to expand...
Click to collapse
Hey where's the actual file?
LocBox said:
Hey where's the actual file?
Click to expand...
Click to collapse
It would help if XDA told me it didn't upload it lol. I added a link to GDrive. It should be available now!
TWRP Update-------------------------------------
Version 0.0.2
Root directory found, but cannot find system_root, vendor, and product directories
Internal Storage can now me mounted
ADB push to sdcard tested and works
JengaMasterG said:
Download via Google Drive
Click to expand...
Click to collapse
JengaMasterG said:
Thank You!!!
TWRP Disclaimer
Code:
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
After many months struggling with the source code, TWRP finally comes to the Surface Duo! Do not flash this boot image! It is not tested to boot directly into the system! Again: this is a tethered boot and should not be flashed/replacing the boot image installed on your device.
Requirements for Booting:- Unlocked Bootloader
- Latest Platform Tools
- TWRP image
How to Boot:With device connected to your PC and turned ON:
adb devices
adb reboot bootloader
fastboot boot boot_TWRP.img
And with that, you're booted into TWRP!
What is working:ADB Shell
ADB Push
USB OTG
You tell me!
What is not working:Touch Screen
ADB Sideload
MTP Storage Mode
You tell me!
Firmwares Tested:
2021.1019.24 GEN
2022.115.10 GEN
Changelog:Version 0.0.2
Root directory found, but cannot find system_root, vendor, and product directories
Internal Storage can now me mounted
ADB push to sdcard tested and works
Spoiler: Changelog History
Version 0.0.1
Initial Release
Download via Google Drive
Click to expand...
Click to collapse
how can i get past the System read only screen?
Also, now with this being achieved the likely ROMs to use would be the Treble A/Bs over in the Treble ROM section on XDA. CHAOS should run for example
LocBox said:
how can i get past the System read only screen?
Click to expand...
Click to collapse
You will need to plug a mouse into the USB C port for now. The touch isn’t working and I’m researching how to get that fixed.
LocBox said:
Also, now with this being achieved the likely ROMs to use would be the Treble A/Bs over in the Treble ROM section on XDA. CHAOS should run for example
Click to expand...
Click to collapse
Probably! The prebuilt kernel is available and we can create custom ROMs already. We just need a fully working twrp. If you know anyone who has experience in this let me know!
well ill be damned somebody did it. now if we could only get some custom roms
I appreciate you!
Has there been anymore progress ? and if not how can we help?
none24 said:
Has there been anymore progress ? and if not how can we help?
Click to expand...
Click to collapse
I'm still trying to get touch working and resolve the issue with decrypting the data partition. If you know someone with TWRP experience or have made TWRP before you are welcome to help compile it!
JengaMasterG said:
I'm still trying to get touch working and resolve the issue with decrypting the data partition. If you know someone with TWRP experience or have made TWRP before you are welcome to help compile it!
Click to expand...
Click to collapse
i've had experience decrypting it using Linux but ive never compiled it. If u think thats helpful I can reinstall linux and get my hands dirty-- just tell me what exactly you need me to do or figure out.
I also put out a help thread in android general.
none24 said:
i've had experience decrypting it using Linux but ive never compiled it. If u think thats helpful I can reinstall linux and get my hands dirty-- just tell me what exactly you need me to do or figure out.
I also put out a help thread in android general.
Click to expand...
Click to collapse
I'll try android general. I'm on the Zulip chat for official TWRP support and they're not exactly helpful or free to assist.
If you have experience decrypting that would be a major step forward! Basically data is mapped correctly in the fstab, but TWRP can't decrypt it. I noticed too that none of the files needed to be copied during the build process doesn't copy for some reason so the decrypting script can't find the rc file it needs to modify
JengaMasterG said:
I'll try android general. I'm on the Zulip chat for official TWRP support and they're not exactly helpful or free to assist.
If you have experience decrypting that would be a major step forward! Basically data is mapped correctly in the fstab, but TWRP can't decrypt it. I noticed too that none of the files needed to be copied during the build process doesn't copy for some reason so the decrypting script can't find the rc file it needs to modify
Click to expand...
Click to collapse
and you've tried no-verity-opt-encrypt ?
Whats strange for me is TWRP asks for a password to decrypt data. I've tried everything to my knowledge to get passed it but i cant.
I also cant load any zips to flash the no-verity-opt-encrypt.zip
If you have discord or telegram I can stay in touch quicker
none24 said:
and you've tried no-verity-opt-encrypt ?
Whats strange for me is TWRP asks for a password to decrypt data. I've tried everything to my knowledge to get passed it but i cant.
I also cant load any zips to flash the no-verity-opt-encrypt.zip
If you have discord or telegram I can stay in touch quicker
Click to expand...
Click to collapse
I haven't tried that. I can send you my discord. I'm normally on that
A 0.0.3 is in the works. I will update this post and the main post when it's ready.
A quick changelog:
MTP is on, but nothing can be transferred
System and Vendor directories can be mounted as read-only
Added Decryption TWRP modules (Data (SDCard) can't be mounted or decrypted yet)
Device Tree supports OrangeFox Recovery, currently an ALPHA build (another thread to come later)
EDIT: Main Post updated with Changelog. 0.0.3 image has been uploaded to GDrive
TWRP UPDATE-------------------------------------------------------
Version 0.0.4Data can now be mounted, but only after a factory reset
ADB push and Zip flashing is confirmed working (See Magisk Attachment)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for the continued work on this!
I have had it sitting in my drawer until an easier way to root came about.
Has anyone who used this to root with magisk had an OTA fail?