Why should I use a GSI ? Mojito already have custom ROMs ¯\_(ツ)_/¯Yes. But this thread exists due to the following reasons:
You don't wanna fear about devs stop shipping updates.
You don't wanna re-flash your custom recovery / kernel after each update.
Unlike some ROMs, no clean flashes necessary after you update.
You don't wanna be a flashoholic / beta tester of a ROM maintainer.
GSIs are like Linux Distros. Flexible, hasslefree & minimal.
All GSIs support signature spoofing out of the box.
Differences between GSIs & ROMs:
ROM updates modify all the partitions (boot, recovery, kernel, system, vendor, etc). A GSI update is just a system partition that updates "only" the system, that runs upon stock firmware.
ROMs might pass safetynet out of the box. But for GSIs, you must root & use magisk modules to achieve that.
You can't flash gapps on vanilla GSIs, as you do on vanilla ROMs. You must use bgS/bgN GSI variants.
For now, GSIs have to be installed via fastbootd, as recoveries still yet to support logical partitions. So you need computer available when you update or change them.
AOSP GSI project is being alive for almost many years now. I've been daily driving his project on this device for almost two years. Everyone claim GSIs are buggy & not daily drivable, which is a complete false claim. There are no compromises with GSIs when compared to ROMs.
PREREQUISITES
USB Drivers (guide to install)
Platform Tools (guide to setup)
Stock ROM (fastboot)
MicroG (for vanilla)
vbmeta.img (from google)
TWRP (thanks to Nebrassy)
Magisk (thanks to topjohnwu)
SafetyNet Fix (thanks to kdrag0n)
Recommended GSIs :
TrebleDroid (thanks to phhusson)
Pixel Experience (thanks to ponces)
LineageOS (thanks to AndyYan)
More to test from here
INSTALLATIONNOTE: I'm assuming you've already unlocked bootloader, backed up your data & know all the technical consequences of flashing & modding.
Download / extract all prerequisites in one place.
From stock firmware, edit flash_all_except_data_storage.bat/sh & modify last line to fastboot reboot fastboot
Enter fastboot mode {vol_down+power}, connect to PC & flash firmware using above edited script. When device enters fastbootd, from terminal/cmd execute :
fastboot erase userdata
fastboot flash vbmeta vbmeta.img
fastboot flash system <gsi-file.img> (ignore INVALID SPARSE warning)
fastboot reboot & make sure your GSI boots up. Power off & return to fastboot again.
fastboot boot <twrp-file.img>, head to Advanced & run flash current TWRP to make recovery persistent across reboots.
Finally Magisk (for root, safetynet fix, additional modding, etc).
BUG_1: Don't touch the screen while booting to avoid touch issues after you boot (this bug occurs only on custom kernels).
BUG_2: Don't set up password on startup wizard. Instead, set it up later & then disable Android Setup app if it exists. Else it'll crash fingerprint settings.
UPDATE / DIRTY FLASH HOW ?
fastboot reboot fastboot
fastboot flash system <new-gsi.img> & reboot twice
All phh based GSIs are dirty flashable (unless you switch between vanilla & gapps). If any GSI doesn't boot up, you can always reflash the older GSI & restore the previous state without any data wipes.
POST CONFIGURATION
Enable the following Settings > Phh Treble Settings:
Qualcomm features / Use alternate camera profile & audio policy
Misc features / Disable audio effects
IMS features / Force the presense of 4G calling & Install IMS Apk for Qualcomm vendor from notification panel.
Setup magisk, hide the app, enable Zygisk & Enforce Denylist.
Use SafetyNet-Fix module to pass safetynet. Still won't pass? Try Pixel-Props (redfin) that ensures fingerprinting.
microG module if you chose vanilla variant (Safetynet works. Most of the banking apps work except gpay).
NOTE: Flash custom kernels only through your custom recovery. Flashing through kernel managers (FKM, SPKM, etc) is not suggested.
MAGISK NOT WORKING ?In this case, the GSI you selected isn't securized (comes with su bydefault). Through TWRP, do
mount -o rw /dev/block/mapper/system_a /system_root from terminal
Code:
rm /system_root/system/xbin/su
rm /system_root/system/bin/phh-su
rm /system_root/system/etc/init/su.rc
Or instead, you can use recovery's file manager to delete the above files. Then reboot.
EXTRASMy Recommendations for great experience:
SPKM to set GPU > GPU Governor > Performance (fixes UI lags)
Lawnchair / Quickswitch for launcher customization with gesture navigation support.
Lineage Dialer for built-in call recording (push into /product/priv-app/Dialer/Dialer.apk).
ANXCam for MIUI camera's post processing.
GCam for google camera's post processing.
Aurora Store / Droid for microg users.
Kiwi Browser for chrome extensions support.
Migrate to backup / restore user apps & data, incase you lose your setup.
Thanks for reading all the way through here.
I have been using GSIs on my old Huawei P10 lite for almost 3 years, and it was a very good experience.
Now with mojito I find myself lazy always using Roms -_- '
Thanks for the guide!
Hami_Do said:
I have been using GSIs on my old Huawei P10 lite for almost 3 years, and it was a very good experience.
Now with mojito I find myself lazy always using Roms -_- '
Thanks for the guide!
Click to expand...
Click to collapse
The only official dev for this device, who's actually from core development of a reputed project (PE), is Zid. There aren't any, as I do not find others to be helping from core (except couple of kernel devs).
ROMs have no complete guarantees for future updates. Although you can use other project GSIs such as crD by Nazim, LOS by Andy, phhusson's the one who's consistently providing regular monthly updates with built-in OTA.
Can I install MIUI gsi roms like this?
Furkantaner said:
Can I install MIUI gsi roms like this?
Click to expand...
Click to collapse
You can install any AOSP GSIs with this guide. Not sure of other skins, as they're proprietary.
And why would you need MIUI GSI? Mojito stock "is" MIUI.
Furkantaner said:
Can I install MIUI gsi roms like this?
Click to expand...
Click to collapse
Miui and its similar sGsi ( semi gsi ) such as OneUi , Color os .. and other AOSPs based ported with Erfan tool aren't real gsi.
They miss patches from Phh and Andy.
The recommanded gsis with full patches (minimum issues) are from Phh (aosp), AndyYan (LOS 18.1/19.1), Ponces (PE) and many others you can check them here for example :
Treble-Enabled Device Development A/AB ROMS
Treble-Enabled Device Development A/AB ROMS
forum.xda-developers.com
There are also more by Nazim and eremitein, you can check them in telegram groups.
can i use this method from aosp?
and what stock rom version should i use?
AlsoKouki said:
can i use this method from aosp?
and what stock rom version should i use?
Click to expand...
Click to collapse
Any version would work. Open stock ROM link in main post & make sure it's fastboot, not recovery.
As for AOSP, you can use any of them from this list (except A13).
in the last line i should change it to "fastboot %* reboot fastboot" or "fastboot reboot fastboot" ?
AlsoKouki said:
in the last line i should change it to "fastboot %* reboot fastboot" or "fastboot reboot fastboot" ?
Click to expand...
Click to collapse
Both work & imply the same btw. That line I've wrote just to make device go to fastboot instead of stock miui.
Adding fingerprint force closes settings.
Youtube fc aswell.
MPK99 said:
Both work & imply the same btw. That line I've wrote just to make device go to fastboot instead of stock miui.
Click to expand...
Click to collapse
i already execute the "flash_all_except_data_storage.bat" but nothing happen should i execute it with mi flash tool?
Samir2298 said:
Adding fingerprint force closes settings.
Youtube fc aswell.
Click to expand...
Click to collapse
No issues here. The procedure I've laid out is exact to that of my device. Some more info from your side might help, such as what you did from the start.
AlsoKouki said:
i already execute the "flash_all_except_data_storage.bat" but nothing happen should i execute it with mi flash tool?
Click to expand...
Click to collapse
I bet it's usb drivers issue. There's guide link in main post.
You should know the issue if you flashed a fastboot rom before.
MPK99 said:
I bet it's usb drivers issue. There's guide link in main post.
You should know the issue if you flashed a fastboot rom before.
Click to expand...
Click to collapse
{
"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"
}
nah its already installed and its detected in fastboot
i tried move the firmware to plarform-tools/ after i execute it this happen
MPK99 said:
No issues here. The procedure I've laid out is exact to that of my device. Some more info from your side might help, such as what you did from the start.
Click to expand...
Click to collapse
Followed exactly as in OP.
I did remove some apps tho from product app/priavpp and system app/privapp, so maybe that caused an issue? Is there anything related to fingerprint in those folders?
AlsoKouki said:
tried move the firmware to plarform-tools/ after i execute it this happen
Click to expand...
Click to collapse
This is redmi Note 10 forum mate. So I had stock ROM link of mojito/sunny. Your device (3rd screenshot) closely states it's Rainbow (Wiko).
Although this is a GSI guide, I suggest you to flash your own device's stock rom.
Still, it won't be enough caz I don't have overlay patch of your device.
Samir2298 said:
I did remove some apps tho from product app/priavpp and system app/privapp, so maybe that caused an issue? Is there anything related to fingerprint in those folders?
Click to expand...
Click to collapse
Probably. Try removing only one or two apps that are disablable from settings.. For overlay just 20kB is needed.
You can reflash system image from fastbootd & boot up without wiping again.
MPK99 said:
Probably. Try removing only one or two apps that are disablable from settings.. For overlay just 20kB is needed.
You can reflash system image from fastbootd & boot up without wiping again.
Click to expand...
Click to collapse
Alright, thanks! I'll try reflash.
Sorry for off-topic, does microg support whatsapp google drive backup/restore? I searched google but all answers are years old.
MPK99 said:
This is redmi Note 10 forum mate. So I had stock ROM link of mojito/sunny. Your device (3rd screenshot) closely states it's Rainbow (Wiko).
Although this is a GSI guide, I suggest you to flash your own device's stock rom.
Still, it won't be enough caz I don't have overlay patch of your device.
Click to expand...
Click to collapse
ahh sorry its because the spoofing feature from the rom,i forgot to disable that, will disable it and try again
Related
EXPERIMENTAL AND MOST LIKELY BROKEN
{
"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"
}
Code:
/*
* 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.
*/
Android "Q" is the upcoming ninth major version of the Android operating system. It was first announced by Google on March 2019, and the first developer preview was released on the same day. The second developer preview is expected to be released at the next Google I/O developer conference.
[more stable] Pixel: Ported from Pixel 2 firmware (walleye)
Generic: Ported from Google GSI with gapps
GET UPDATES FROM: https://t.me/androidqgsi
Requirements :
Treblized device with 8.1 or P vendor
Global Bugs :
VoLTE
Device specific Bugs :
...
Instructions :
for A-Only :
Install img into system partition
Flash permissiver_v2.zip or make your boot partition selinux permissive
Flash FixZygote.zip
Reboot
for AB :
Install img into system partition
Flash permissiver_v2.zip or make your boot partition selinux permissive
Reboot
Downloads :
Q Developer Preview
Notes :
Fix gapps: install google play services with "adb install"
if images didn't worked properly post your logs(logcat and console-ramoops) on telegram group i'll come for help : @androidqgsi
Logcat without PC: take /data/local/tmp/logs/log
Enable adb before boot using this command in TWRP:
Linux/mac :
Code:
adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys
Win :
Code:
adb push C:\Users\<userName>\.android\adbkey.pub /data/misc/adb/adb_keys
Donate:
My paypal: https://www.paypal.me/erfanoabdi
Tested on:
give me logs if didn't worked, or donate me a device
Tested by myself:
Moto Z (A-only)
Moto X4 (AB)
Thanks
ENJOY!
[DEV-ONLY] Bug Fixing
NVM
Ah actually this is ridiculous to have bug fixing post here, and i hate my port, real P GSI shouldn't done like this. but anyway this is ported from closed source P and i can point in most popular fixable bugs here...
by looking into logs(adb logcat -b all) if we see :
1) library "libxxxxxxxxx.so" not found
fix of this error is very simple as you guys all know we just need to put needed lib from system image of base rom in https://github.com/erfanoabdi/P_sem...GSI_Patches/Vendor/P Blobs/POST-sGSI_1/vendor
and zip up "POST sGSI 1" with new libs
Feel free to make pull request new libs in github
2) cannot locate symbol :
for example LG RIL error was like this:
Code:
CANNOT LINK EXECUTABLE "/vendor/bin/hw/rild": cannot locate symbol "_ZN7android8hardware5radio4V1_08toStringENS2_22CdmaSmsWriteArgsStatusE" referenced by "/vendor/lib64/[email protected]"...
a) here we need to find where is unknown symbol located in 8.1 system image
so in terminal goto system/ and :
Code:
grep -r "_ZN7android8hardware5radio4V1_08toStringENS2_22CdmaSmsWriteArgsStatusE"
output in this case is :
Code:
Binary file lib/[email protected] matches
Binary file lib64/[email protected] matches
(here you may get long list of blobs, only find and grab needed ones)
b) now just copy libs to vendor and rename them
in this case i renamed [email protected] to [email protected]
***important rule keep string name same as original file only replace one letter (a->W)***
c) and sed renamed lib (in my case) :
Code:
sed -i "s/[email protected]/[email protected]/" "P_semiGSI/POST_sGSI_Patches/Vendor/P\ Blobs/POST-sGSI_1/vendor/lib/[email protected]"
sed -i "s/[email protected]/[email protected]/" "P_semiGSI/POST_sGSI_Patches/Vendor/P\ Blobs/POST-sGSI_1/vendor/lib64/[email protected]"
we're almost done here
d) now open POST-sGSI_2 and sed "referenced by" lib from error line in log
like this : https://github.com/erfanoabdi/P_sem...ETA-INF/com/google/android/update-binary#L154
e) and zip up "POST sGSI 1/2" with new libs
Feel free to make pull request new libs/hax in github
3) more...
NVM
WIKI : https://github.com/erfanoabdi/P_semiGSI/wiki
i hope we get a full GSI eventually one P is released, been waiting a while for this. at least now its semi done, it should be easier to create a full GSI for kirin (aka my H9) and MTK devices.
Hi, will it support Honor9?
I'm waiting for kirin chipset supported gsi
Dumpling- Needs mokee vendor
waiting support kirin960 and more?
Sent from my Honor V9 using XDA Labs
Jamie_oppo said:
Do you need to be a on a treble rom before flashing this?
Ive got a 5t (dumpling) and flashed the open beta which gave treble. Then flashed a normal custom rom. I tried all the zip at this point and no luck decrypted.
Click to expand...
Click to collapse
Same phone here, I flashed the rom, but it reboots every time to the bootloader...
ChristiaanP said:
Same phone here, I flashed the rom, but it reboots every time to the bootloader...
Click to expand...
Click to collapse
were u on a treble rom? Or normal non treble custom rom
Edit: apparently ob 11 vendor image is broken and mokee one boots.
Jamie_oppo said:
were u on a treble rom? Or normal non treble custom rom
Edit: apparently ob 11 vendor image is broken and mokee one boots
Click to expand...
Click to collapse
I was on OB 11
Awesome... btw Currently booting phones
Mi 5 (gemini)
Redmi 4 Prime (markw)
Redmi 4x (santoni)
Redmi 3s/3x/Prime (land)
Zuk Z2 Plus (z2_plus)
Redmi Note 4 sd (mido) (Tested on PE and Lineage-ex vendors)
Lenovo P2 (kunato)
Redmi Note 5 Pro (whyred) (With mokee vendor)
Mi 6 (sagit) LG V30 (h930)
Redmi 5 Plus (vince) (Tested with cardinal-aosp vendor)
Exynos S9+ (Unstable as **** as its not QCOM)
Redmi 4A (rolex) (crDroid Treble)
OnePlus 5/T (Only one user has reported it to work with proof though)(Mokee trees)
Bugs for land or all devices!
- half volte is working (only outgoing call and volume for jio left to fix)
- app opening time is extra
None volte users r really lucky
Also jio4gvoice app is not working
Update for DP5
THE MEGAPOST OF NOTES FOR THE P GSI HERE
Wiki page: https://github.com/erfanoabdi/P_semiGSI/wiki/OnePlus-5T and https://github.com/erfanoabdi/P_semiGSI/wiki/OnePlus-5 (Thanks to timocapa)
OnePlus 5/5T users, you MUST be decrypted in order to boot this GSI. This means flashing the noverity zip and formatting data. The link to the zip which I used to get it working is here: https://drive.google.com/file/d/1BtZKnNc2ooe9lcDd0JJ8eHzylA0StSm2/view The recovery I am using is the latest codeworkx recovery here: https://sourceforge.net/projects/ch....1-0-20180414-codeworkx-dumpling.img/download for dumpling and https://sourceforge.net/projects/ch...-20180414-codeworkx-cheeseburger.img/download for cheeseburger.
Some things to take into consideration before I followed these steps: I was using OB11 as my daily driver since it's release and I have always been encrypted.
This is exactly how I managed to get it booting on my 5T:
1) format data to remove encryption (I'm on OOS OB11 before doing this)
2) reboot recovery
3) factory reset
4) flash Mokee ROM (latest nightly)
5) flash noverity zip
6) reboot into OS
7) get past set up and reboot into TWRP
8) factory reset
9) install P GSI
10) mount vendor
11) install all the latest POST zips in the order of 1 to 3
12) reboot into OS
OPTIONAL: After you have booted into Android P and the lockscreen shows. You can reboot back into TWRP and install the latest BETA version of Mqgisk
Click to expand...
Click to collapse
Alternative instructions if you are getting kicked back into the recovery with the display log saying "RescueParty", do all of the above but replace step 11 with the steps below (Thanks to @jelousdogs for his method):
11) Flash POST Zip 1,2 (Dont flash zip 3 Yet)
12) Reboot to system (You will see the rom booting and reboot to recovery suddenly)
13) Flash POST zip 3 in recovery and reboot to system
If this STILL does not work, try this: After completing all of these steps, mount vendor partition in TWRP, then use the TWRP File Manager. Copy the build.prop file from the vendor partition to your internal storage (/sdcard) and move it to your PC via MTP in recovery. Add "persist.sys.disable_rescue=true" (without quotes) to the bottom of the build.prop file you have just copied to your PC. Save and transfer it back to your internal storage. Copy the build.prop from your internal storage to /vendor, replacing the original file. Press on the build.prop file in your /vendor partition and press "chmod". Remove all of the "0000" numbers in the text box and type "0600", then confirm the chmod. Reboot to the OS.
Click to expand...
Click to collapse
DIRTY FLASHING DP5 FROM DP4 (Thanks to timocapa):
1) reboot into TWRP and flash the DP5 GSI.
2) reboot into the OS.
Simple as that.
Click to expand...
Click to collapse
Notes:
- If you get kicked into recovery after trying to boot the GSI, look at TWRP's display log where flashable zip text are printed out and see if "init_user0_failed". This means you are encrypted and the GSI is having trouble with it. You must be decrypted as said above.
- Yes, this includes the new gesture pill nav bar. SETTINGS > SYSTEM > GESTURES > SWIPE UP ON HOME BUTTON (Your stock launcher must be working, i.e. not Force Closing, in order for this to work because the new overview app switcher is part of the stock Pixel Launcher).
- Weird software issues like apps not opening, random FCs, settings going blank? Try a factory reset in TWRP and reboot to see if it has fixed any problems!
Click to expand...
Click to collapse
Known bugs confirmed by a number of 5/t users:
- Potato quality camera, you can use GCam to remedy the problem but expect blue dots in HDRmode (OnePlus problem)
- Front facing camera can only be used in OOS camera (wait for official sources)
Click to expand...
Click to collapse
To get rid of the three persistent notifications:
1) install GMS update (https://www.apkmirror.com/apk/googl...2-8-72-100400-202717283-android-apk-download/)
2) Tap on the blue finishing setup notification and connect to wifi, then force close the pixel setup so it re-appears again
3) Go to settings > accounts > sign into google
4) Tap on the blue notification again and you should be able to go further than "pixel is finishing setup" page.
5) Force stop play store to remove the play store persistent notification
Click to expand...
Click to collapse
Hope this helps other OP5/5T users out there who are having trouble booting this.
Can someone tell me if boot this rom on mi mix2s It is able for treble rom i tryied to flash but doesnt boot.
Reserved for review
Boots
Could someone please tell me if this is a Pixel experience in terms of new nav gestures+copy/paste in multitasking overview?
unrealmac said:
Could someone please tell me if this is a Pixel experience in terms of new nav gestures+copy/paste in multitasking overview?
Click to expand...
Click to collapse
No
ZeroInfinity said:
OnePlus 5/5T users, you MUST be decrypted in order to boot this GSI. This means flashing the noverity zip and formatting data. The link to the zip which I used to get it working is here: https://drive.google.com/file/d/1BtZKnNc2ooe9lcDd0JJ8eHzylA0StSm2/view The recovery I am using is the latest codeworkx recovery here: https://sourceforge.net/projects/ch....1-0-20180414-codeworkx-dumpling.img/download for dumpling and https://sourceforge.net/projects/ch...-20180414-codeworkx-cheeseburger.img/download for cheeseburger.
This is exactly how I managed to get it booting on my 5T:
1) format data to remove encryption (I'm on OOS OB11 before doing this)
2) reboot recovery
3) factory reset
4) flash Mokee ROM (latest nightly July 15th is what I used)
5) flash noverity zip
6) reboot into OS
7) get past set up and reboot into TWRP
8) factory reset
9) install P GSI
10) mount vendor
11) install all the latest POST zips in the order of 1 to 3
12) install in-call audio fix
13) reboot into OS
OPTIONAL: After you have booted into Android P and the lockscreen shows. You can reboot back into TWRP and install magisk. I recommend this version as it was the only one working for me: https://drive.google.com/open?id=10LV_j43YUmmHNe0PjE_GNo9kkb-1gAnD
Notes:
- If you get kicked into recovery after trying to boot the GSI, look at TWRP's display log where flashable zip text are printed out and see if "init_user0_failed". This means you are encrypted and the GSI is having trouble with it. You must be decrypted as said above.
- If you get kicked into recovery and TWRP's display log shows something about RescueParty, flash the POST 3 zip again and rebooting. You might want to try this 2-3 times if it did not work the first time.
- Yes, this includes the new gesture pill nav bar. SETTINGS > SYSTEM > GESTURES > SWIPE UP ON HOME BUTTON
Bugs that I have encountered personally but may not affect you, need confirmation:
- MTP isn't working, even with the workaround.
- ADB is detected but when doing "adb devices", it will stay on the "connected" status so you can't issue any adb commands via PC.
- Fingerprint not even detected, no option to enrol in security settings.
To get rid of the three persistent notifications:
1) force stop pixel setup in app settings
2) install GMS update (https://apkdot.com/apk/google-llc/g...s-12-8-66-100400-200774163-beta-041/download)
3) when the blue notification appears again, open it and connect to wifi
4) force stop pixel setup again
5) the next time the notification appears, it should allow you to finally finish the setup
Hope this helps other OP5/5T users out there who are having trouble booting this.
Click to expand...
Click to collapse
Thanks! It worked!
{
"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"
}
Here is complete guide to install android p dp5 on redmi 3s..
do every step carefully as messing up could brick your device
quick note ANDROID P WORTH READING THIS LONG ENGNEERING PAPER LIKE ARTICLE SO BE PATIENT
use trebal twrp link-https://forum.xda-developers.com/xiaomi-redmi-3s/development/recovery-unofficial-twrp-xiaomi-redmi-t3701841
step 1 ) choosing a base rom.
as project trebal can install android p on vender of oreo roms we need a campatable oreo rom (trebal supported)
i will suggest to go with lineage os
step 2) clean flash lineage os without gapps
step 3) without rebooting into system wipe all partitions except vender and internal storage
step 4) Download and extract the dp5.zip https://androidfilehost.com/?fid=5862345805528058112
copy img file in internal storage
step 5) install the gsi image as system image
[click on install image , select .img file, flash as system image]
check if vender and system partition is mounted properly
if error code 7 is shown unmount and mount vender
step 6) install postgsi 1 2 3 resspectively
pgsi 1-https://androidfilehost.com/?fid=5862345805528063582
pgsi 2-https://androidfilehost.com/?fid=5862345805528063581
pgsi 3-https://androidfilehost.com/?fid=5862345805528058103
step 7) install lag ,gcam fix
lag fix-https://drive.google.com/file/d/1r2oxwvaCCWEUw_iYIH_g25cescD-h0U4/view
gcam fix-https://drive.google.com/file/d/1YNxEuldCgIQzxOqp8_4Mwd--rf2uSy_1/view
volte fix and fingerprint fix not tested
volte fix-https://drive.google.com/file/d/1NFBU1KErlZgz-rg9NZdIHkWwalsW3phh/view
fp fix-https://drive.google.com/file/d/1nyO8c0Jpk445pbsGtYUN7Yaj8mCoUc08/view
before booting system format data to remove the encryption otherwise it will ask for password
step 8) boot into system
step 9) enabling MTP
after booting into android p
go to build no tap 5 times and enable dev options
in dev option select [default usb configration] to file transfer
step 10) fixig lag
go to dev options and decrease [window animation scale] to 0.5 for all 3
step 11) copy play services apk into the internal storage
play-https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-12-8-74-release/google-play-services-12-8-74-100400-204998136-android-apk-download/
install using file maneger...
step 12) logging in
open play store and log in to google account
step 13) setting up assistant
you have to initealise the assistant right now otherwise it wont work in future
open [google app] and set up assistant
step 14) rooting the device for cam2api
reboot to twrp and flash the magiks 16.7 only
link- https://www.mobileheadlines.net/download-magisk-16-7-beta/
reboot into system
install migiks maneger.apk link-https://******************/
install cam2api ebalbler in magics maneger
link-https://drive.google.com/open?id=1Xn9hSKGBAzgOA4wAYIo73iRykj5TUQb5
step 15) install gcam by urikil
link -https://drive.google.com/file/d/1VVrO0Lf3TN1te2fIaAA10OpBsfssMJV6/view?usp=sharing
open camera under [settings] [advance settings] [model] select [pixel 2]
if you are reading till this then you are a nerd and you definitely need something to control your addiction
luckyly google has you covered by digital wellbeing program
step 16) enroll for digital wellbeing
link-https://www.android.com/versions/pie-9-0/digital-wellbeing-beta/
sign up and you will get conformation mail in 7-8 hrs
finally you are in fully stable android p dev preview 5
CREDITS:
1)Lineage os team
2) erfanoabdi for huge contribution in this progect
Nice guide but
Post in general section pls
[email protected]$ said:
Nice guide but
Post in general section pls
Click to expand...
Click to collapse
Agree it's helpful. And I already report it. cc @engloa
Actually u can flash vendor.img directly then sGSI or sGSI first doesn't matter, for vendor.img just extract it from treble rom that u choose, after that u will need to decompress it from brotli ".br" extension..., Here's the link for brotli official software https://github.com/google/brotli/releases
Type from cmd "brotli -d vendor.new.dat.br" then you will get ".dat" extension, to convert it to ".img" use this script https://github.com/xpirt/sdat2img just run "./sdat2img.py vendor.transfer.list vendor.new.dat vendor.img" or from windows "python sdat2img.py vendor.transfer.list vendor.new.dat vendor.img"
If after u reboot then stuck at "asking password for decrypt or whatever i forgot it exactly" just go to fastboot then type "fastboot -w" this will wipe your data and cache off course internal too ? ... But this will let u to boot to home screen, FBE_Disabler.zip from erfan will not work for us because our device using fde not fbe
And about fingerprint there's no need to flash any patch because fingerprint already work for goodix or fpc, the problem is your saved fingerprint will disappeare if u reboot your phone ... Only goodix has this problem not fpc... At least on mine goodix ?
Lagfix.zip i guess it's optional, because from my experience it's already smooth even without lagfix patch
For camera actually it already work even u just flash vendor.img sGSI and post 123, but the cam will take a minute to open... The bug just like our dev bringup custom rom nougat before, if u see the log u can see mm-qcamera-daemon crashes..., That's all from my experience on my country volte is not available so i don't have experience to explain ?
ndzaky said:
Agree it's helpful. And I already report it. cc @engloa
Click to expand...
Click to collapse
Moved :good:
Sorry guys for this I wasn't aware of that
I truely apologize for posting at wrong place
actully my main moto was to make this guide as simple as possible so i dont added extraction of vender image,
and added those steps which are more familier to end user so users wont freak out...
actully i installed gsi images before thats why it wasnt nessesary at this time so i forget to add that
thanks for reporting i will note that
actully i added lagfix so that if anyone use future images like pr1 they dont face any issue it is not nessesary for dp5 but listed to be future proff
actully i own 2gb+16gb version so couldn't verify that but listed for prime users just in case.......
and talking about volte i accidentaly damaged my bands while thermal repesting opration
so can't confirm that to lol....
at last thanks for taking interest and giving time for this post .....................have a great day
zainifame said:
Actually u can flash vendor.img directly then sGSI or sGSI first doesn't matter, for vendor.img just extract it from treble rom that u choose, after that u will need to decompress it from brotli ".br" extension..., Here's the link for brotli official software https://github.com/google/brotli/releases
Type from cmd "brotli -d vendor.new.dat.br" then you will get ".dat" extension, to convert it to ".img" use this script https://github.com/xpirt/sdat2img just run "./sdat2img.py vendor.transfer.list vendor.new.dat vendor.img" or from windows "python sdat2img.py vendor.transfer.list vendor.new.dat vendor.img"
If after u reboot then stuck at "asking password for decrypt or whatever i forgot it exactly" just go to fastboot then type "fastboot -w" this will wipe your data and cache off course internal too ... But this will let u to boot to home screen, FBE_Disabler.zip from erfan will not work for us because our device using fde not fbe
And about fingerprint there's no need to flash any patch because fingerprint already work for goodix or fpc, the problem is your saved fingerprint will disappeare if u reboot your phone ... Only goodix has this problem not fpc... At least on mine goodix
Lagfix.zip i guess it's optional, because from my experience it's already smooth even without lagfix patch
For camera actually it already work even u just flash vendor.img sGSI and post 123, but the cam will take a minute to open... The bug just like our dev bringup custom rom nougat before, if u see the log u can see mm-qcamera-daemon crashes..., That's all from my experience on my country volte is not available so i don't have experience to explain
Click to expand...
Click to collapse
GUYS as i am on strictly bed rest now i have lot of time to test new mods on android p
if you have any ideas let me know
i will definately try those..........
Guys flashed everything successfully but i didn't found navigation keys there, not even home key ?
Kuchayhilal said:
Guys flashed everything successfully but i didn't found navigation keys there, not even home key ?
Click to expand...
Click to collapse
Strange ......try enabling gesture key
Kuchayhilal said:
Guys flashed everything successfully but i didn't found navigation keys there, not even home key ?
Click to expand...
Click to collapse
Strange ......try enabling gesture key
Kuchayhilal said:
Guys flashed everything successfully but i didn't found navigation keys there, not even home key ?
Click to expand...
Click to collapse
Is VoLTE working for you?
paarkhi said:
Is VoLTE working for you?
Click to expand...
Click to collapse
Yes, i flashed that VoLTE fix.
Kuchayhilal said:
Yes, i flashed that VoLTE fix.
Click to expand...
Click to collapse
Any major bugs? it's for a friend....
paarkhi said:
Any major bugs? it's for a friend....
Click to expand...
Click to collapse
I just used it for few hours, everything was working after flashing all the bug fixes.
Only problem was with on screen navigation keys, they aren't their.
Is this and the final Android Pie stable release the same?
Nevermind, I see it's not.
Kuchayhilal said:
I just used it for few hours, everything was working after flashing all the bug fixes.
Only problem was with on screen navigation keys, they aren't their.
Click to expand...
Click to collapse
Flash without volte fix,navi bar working for me..just try
I have tried the guide step by step carefully but with the final Android P image instead of DP5 and it's not booting.
Has someone been able to boot it? I'm stuck at the MI logo.
epraes said:
I have tried the guide step by step carefully but with the final Android P image instead of DP5 and it's not booting.
Has someone been able to boot it? I'm stuck at the MI logo.
Click to expand...
Click to collapse
I was able to boot final Android P Image but volte was not working so i revert back to MIUI.
Did all exactly as mentioned. Stuck at boot logo.
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
As we all know - the tablet does not support treble. And we do not have a separate /vendor partition, i'm using /cache as /vendor.
Instructions
1. flash my twrp from link above - this is latest twrp with system_image support, it need to restore system treble images
2. download system image from https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Known Issues
1. rotate sensor working, but strange - on rotate tablet show black screen for a moment and then back to normal in right state
2. SM-T580 only: gps
Links
Treble images
SM-T585:
1. 20180827: initial treble: https://drive.google.com/file/d/1uX5JYqLCTMPpT5Zx2Wvi0U-Ms49S0YrW/view?usp=sharing
2. 20180904: camera recording in oreo images, both sdcards in pie images: https://drive.google.com/file/d/1cTEXJb9n5oZad0O3DXT5nlEhnlBDP6QB/view?usp=sharing
3, 20180906: remove shim for mediaserver - only for pie!!!: https://drive.google.com/file/d/1C0MfHt0SNYL4hD-BtOj3i7O_qBBPD25t/view?usp=sharing
SM-T580:
1. 20180828: initial treble: https://drive.google.com/file/d/1sgB1xQjRWyGM1OfF73Yhl5vRNunP04iK/view?usp=sharing
2. 20180904: camera recording in oreo images, both sdcards in pie images: https://drive.google.com/file/d/13WL9_Q_WoStf0WVHbmoYaL2CHbCluzNO/view?usp=sharing
3, 20180906: remove shim for mediaserver - only for pie!!!: https://drive.google.com/file/d/15dN2DugPBjhi_m0SOy4qYwVmR03nyY69/view?usp=sharing
Root
Use Magisk, it's should work. If during install Magisk give error about missed /vendor, run my prepare script and the install Magisk: https://drive.google.com/file/d/10JnOtyF5Y_4q1OE3FOZYPDcR7TK1jRhA/view?usp=sharing
GApps - Pie only!!!
Right now on T580\T585 pie images with gapps dnw, it's stuck on the start wizard, what is strange.
Solution: flash image without gapps and then flash gapps. It's working. I'm playing right now with aosp 9.0 and gapps.
We have 32bit recovery and right now standalone gapps think about arm and 6.0.1 version, what is wrong. I took gapps from https://forum.xda-developers.com/android/development/gapps-unofficial-opengapps-builds-t3828141 and fix script inside to arm64 and right sdk version, this is gapps with my fix, what should work on T580\T585: https://drive.google.com/file/d/1kkHUPSznfibcER0DV89GhDdepEjqjCl9/view?usp=sharing
How install gapps:
1. install treble image, then pie system image
2. boot to system
3. restart to twrp and install gapps
4. boot to system, go to play market and login
For now working only this sequence
Recovery
SM-t585:
1. twrp-3.2.3-0: https://drive.google.com/file/d/16D-sFDt41n-wxNu1A0q01oRRKiZ-AsfF/view?usp=sharing
SM-T580:
1. this is original twrp (from https://dl.twrp.me/gtaxlwifi/twrp-3.2.3-0-gtaxlwifi.img.html), I just added system_image support and repack: https://drive.google.com/file/d/10LgZ1rabkgVSyIyd38BxIxNr22_9PJY5/view?usp=sharing
All firmware say about wrong vendor version. This is normal, just press OK.
System images:A only and 64Bits
Checked firmwares
Almost all oreo roms from treble's thread working.
Even new Android 9.0 Pie roms working, but it has issue with sdcard, it will require additional checks from me.
Installation
1. (optional): "Wipe\Format Data": type yes and press ok
{
"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"
}
2. wipe data: "Wipe\Advanced Wipe" and select "Dalvik/ARP Cache" / "Data" / "Internal Storage" / "System" / "Cache"
3. install treble: "Install", then navigate to lineage-15.1-20180827-treble.zip and "Swipe to confirm Flash"
4. install system: "Install", then press "Install Image" then navigate to system images, then select "System Image" and "Swipe to confirm Flash"
5. reboot
let's experiment together!
Valera1978 said:
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
As we all know - the tablet does not support treble. And we do not have a separate /vendor partition, i'm using /cache as /vendor.
Instructions
1. go to the current twrp and full wipe
2. flash my twrp - this is latest twrp with system_image support, it need to restore system treble images (twrp-3.2.3-0-gtaxlltexx.img): https://drive.google.com/file/d/16D-sFDt41n-wxNu1A0q01oRRKiZ-AsfF/view?usp=sharing
3. flash zip with vendor data and boot image (lineage-15.1-20180827-treble.zip): https://drive.google.com/file/d/1uX5JYqLCTMPpT5Zx2Wvi0U-Ms49S0YrW/view?usp=sharing
4. now you device is ready to flash any treble system image from: https://forum.xda-developers.com/project-treble/trebleenabled-device-development - download img, copy to sdcard and then flash as system image in twrp
5. if you wanna check another rom, just make 1-4 again
Known Issues
1. video-recording
2. rotate sensor working, but strange - on rotate tablet show black screen for a moment and then back to normal in right state
All firmware say about wrong vendor version. This is normal, just press OK.
System A only
Checked firmwares
Almost all oreo roms from treble's thread working.
Even new Android 9.0 Pie roms working, but it has issue with sdcard, it will require additional checks from me.
let's experiment together!
Click to expand...
Click to collapse
You are amazing dude thanks so much for releasing this to us. Keep up the great work.
Wow, can you Do the same for the WiFi Version SM-T580?
This is by far the best news for our device. I am wondering if when we'll get official Oreo, Samsung will provide us with a treble rom as well.
Thanks Valera for you support.
I get "No OS installed"
Wow. Good job, my friend! I already want to try it on T580 wifi version. I remember that the roms of t585 work in the wifi version, can you flash this without problems?
Many cravings
Thank you!
paulo boë said:
I get "No OS installed"
Click to expand...
Click to collapse
just ignore this error. look like twrp not quite correctly handle the situation with restore via system_image and think that there is no system.
alanloax said:
Wow. Good job, my friend! I already want to try it on T580 wifi version. I remember that the roms of t585 work in the wifi version, can you flash this without problems?
Many cravings
Thank you!
Click to expand...
Click to collapse
I can build version for t580, the kernel and almost all stuff is not a problem, question only in the gps. In the t585 it's connect to the ril, but t580 using own gps chip. I don't know, where I can get 64bit binary for it. In case of t585 i'm using proprietary bin\libs from a5'17. Need to check, can I use 32bit gps in 64bit system.
And may be can be a problems (not sure now) - all treble's images created for phones. tablet with lte is close to phone, but not a witi version. but in any way - it's need to check.
Valera1978 said:
I can build version for t580, the kernel and almost all stuff is not a problem, question only in the gps. In the t585 it's connect to the ril, but t580 using own gps chip. I don't know, where I can get 64bit binary for it. In case of t585 i'm using proprietary bin\libs from a5'17. Need to check, can I use 32bit gps in 64bit system.
And may be can be a problems (not sure now) - all treble's images created for phones. tablet with lte is close to phone, but not a witi version. but in any way - it's need to check.
Click to expand...
Click to collapse
Oh I understand. Luckily I use little the gps. At least to try haha.
Thank you very much again for contributing to these devices, very good work!
Valera1978 said:
just ignore this error. look like twrp not quite correctly handle the situation with restore via system_image and think that there is no system.
Click to expand...
Click to collapse
And still it reboots over and over. The Galaxy Tab logo, then 6 7 secs black screen and the the Galaxy tab logo again.
paulo boë said:
And still it reboots over and over. The Galaxy Tab logo, then 6 7 secs black screen and the the Galaxy tab logo again.
Click to expand...
Click to collapse
Did you flashed anything other than rom? Magisk, gapps?
EugenStanis said:
Did you flashed anything other than rom? Magisk, gapps?
Click to expand...
Click to collapse
Nope, but I kinda forgot to mention that I use it on the T580
Hey, very good job. Please make a 580 version, GPS doesn't matter. You said it was experimental.
paulo boë said:
Nope, but I kinda forgot to mention that I use it on the T580
Click to expand...
Click to collapse
It's cannt work on T580 right now, because treble require changes in DTB. Without DTB changes system cann't mount /cache as /vendor and you will get boot before animation.
Will try build T580 today.
Please someone check version for T580
Valera1978 said:
Please someone check version for T580
Click to expand...
Click to collapse
And the twrp for t580? Cuz when I flash I get "this is for wifi this is lte"
Also can you post some screenshots with a link to the treble rom that works?
paulo boë said:
And the twrp for t580? Cuz when I flash I get "this is for wifi this is lte"
Click to expand...
Click to collapse
are your right now on twrp for lte? In this case in the gtaxlwifi-20180828-treble.zip - go to "\META-INF\com\google\android\updater-script" and remove first line with assert
Or you can use my twrp repack for t580: https://drive.google.com/file/d/10LgZ1rabkgVSyIyd38BxIxNr22_9PJY5/view?usp=sharing
this is original 3.23 version, I added only system-image
Valera1978 said:
are your right now on twrp for lte? In this case in the gtaxlwifi-20180828-treble.zip - go to "\META-INF\com\google\android\updater-script" and remove first line with assert
Or you can use my twrp repack for t580: https://drive.google.com/file/d/10LgZ1rabkgVSyIyd38BxIxNr22_9PJY5/view?usp=sharing
this is original 3.23 version, I added only system-image
Click to expand...
Click to collapse
I flashed it. Tried to flash a img, but still reboots back into galaxy logo
paulo boë said:
I flashed it. Tried to flash a img, but still reboots back into galaxy logo
Click to expand...
Click to collapse
can you send me /data/tombstones and /proc/last_kmsg?
SM-T285YD
Hi,
I have twrp for SM-T285YD but I cannot find any rom for my SM-T285YD. So can I flash this rom in my SM-T285YD.
If not then tell me what I need to do to get it working in my SM-T285YD and also I have the twrp but tell me how can make my twrp treble supported twrp....
Best regards....
Thanks to TheAtt1la
{
"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"
}
Download:
Xdroid-13_arm64-bgN-slim-lite-UNOFFICIAL.img.xz ( Gapps with Read Only System )
Xdroid-13_arm64-bgN-lite-UNOFFICIAL.img.xz (Gapps with Read/Write System)
Installation: for A11 GSI Based Only
-TWRP's Fastboot or CustomAP for Odin.
-Check this first before CustomAP making with SM-T225
stat -c '%n %s' *.img
stat -c '%n %s' *.raw
A11 super-group fixed(odm+product+vendor)size = 1,737,162,752
super.raw 6094323712
odm.img 4349952
product.img 1091608576
vendor.img 641204224
Reclaim working spaces:
Delete system/system_ext/apex/com.android.vndk.all (except vndk 30) about 200M
Phh Treble Setting Hiding. (Termux from fdroid) After enable dubble tap for wake etc.,
( Must Have Magisk)
Code:
su
pm disable me.phh.treble.app/.TopLevelSettingsActivity
*For Enable again:
su
pm enable me.phh.treble.app/.TopLevelSettingsActivity
Update new xdroid GSI: (dirty update)
*Disable All Magisk modules.
fastboot flash system newGSI.img
(reboot system with not wipe)
* i don't like to use HOME_CSC with CustomAP. (Broken Knox Guard status happened to me.)
Calling
Camera
tigr: trCamera_V7_FINAL.apk
Download trCamera_V7_FINAL.apk by tigr.
www.celsoazevedo.com
Features:*Home Launcher & UI
works well with this Tablet
Extended Pixel Launcher.
https://github.com/saitamasahil/Pixel-Launcher-Extended
Overlay for Auto-Screen Brightness: broken
* you can install "Velis Auto Brightness" from play store.
Bluetooth Connection: works on all wired, unwired headphone and external Speaker.
* Not required PHH Treble Setting.
* Do not mod system sound. ( Will broken Bluetooth connection )
* Wavelet EQ is recommended.
exFAT micro-sdcard supported
Face unlock : broken
Offline-charging : supported
Screen Casting : supported
DSU Side loader : supported with no Magisk.
What happened when we had made uncompleted or unsupported " New Super image" and flash it with Odin ?
- During Odin process then terminate itself , didn't write super image file to the partition, flashing stop , uncompleted
- at download mode screen of your Tab A7 lite
>press power + vol down to reboot device immediatly screen shutdow to black screen changes to press and hold
>Vol up + Vol down then insert USB cable which the other side had connected with computer usb port before.
Device will go into download mode again. waitting for Odin .
"This event happened when i have tried to mod and dump Super image inside A11 hope it help for bugs fixing on A12 with CustomAP. no luck now.
Rom is pretty good! But I have a small issue that i can't install magisk, I have build custom AP from a12 AP file.
If Anyone knows a solution please help.
I have also tried custom AP from a11 AP file on which I was able to install magisk and root but USB debugging wasn't working.
yshiv666 said:
Rom is pretty good! But I have a small issue that i can't install magisk, I have build custom AP from a12 AP file.
If Anyone knows a solution please help.
I have also tried custom AP from a11 AP file on which I was able to install magisk and root but USB debugging wasn't working.
Click to expand...
Click to collapse
Did you used slim variant ? What Based Android.? What you mean USB debugging not works?
tom.android said:
Did you used slim variant ? What Based Android.?
Click to expand...
Click to collapse
I have used this version Xdroid-13_arm64-bgN-lite-UNOFFICIAL.img. I can try slim variant.
yshiv666 said:
I have used this version Xdroid-13_arm64-bgN-lite-UNOFFICIAL.img. I can try slim variant.
Click to expand...
Click to collapse
CustomAP Based A11 works /but CustomAP Based A12 not works..? I mean install magisk.
No not try slim cause it Read only system.
Using debugging from dev to enable MTP works only on A12.
tom.android said:
CustomAP Based A11 works /but CustomAP Based A12 not works..?
No not try slim cause it Read only system.
Click to expand...
Click to collapse
I have Build Xdroid-13_arm64-bgN-lite-UNOFFICIAL.img one with A12 and one with A11 AP file. Both were working.
BUT Both have different issue
on A12
-Magisk broken(Warning:- you don't have enough space to install this app),
- USB debugging working
And
on A11
-Magisk working
-USB debugging Broken
yshiv666 said:
I have Build Xdroid-13_arm64-bgN-lite-UNOFFICIAL.img one with A12 and one with A11 AP file. Both were working.
BUT Both have different issue
on A12
-Magisk broken(Warning:- you don't have enough space to install this app),
- USB debugging working
And
on A11
-Magisk working
-USB debugging Broken
Click to expand...
Click to collapse
That right. You are good at making CustomAP.
Cause this GSI now in a beginning state. ( not fully support Stock A12)
MTP for GSIs is works on Stock A12 ONLY.
No A13 GSI now supported our A12 Stock Tab A7 Lite.
tom.android said:
That right. You are good at making CustomAP.
Cause this GSI now in a beginning state. ( not fully support Stock A12)
MTP for GSIs is works on Stock A12 ONLY.
Click to expand...
Click to collapse
I hope this issue gets fixed in future updates. Because This gsi has almost everything to use as a daily driver.
yshiv666 said:
I hope this issue gets fixed in future updates. Because This gsi has almost everything to use as a daily driver.
Click to expand...
Click to collapse
On A11 Based is very good . Quick & Stable the best I had tested.
yshiv666 said:
Rom is pretty good! But I have a small issue that i can't install magisk, I have build custom AP from a12 AP file.
If Anyone knows a solution please help.
I have also tried custom AP from a11 AP file on which I was able to install magisk and root but USB debugging wasn't working.
Click to expand...
Click to collapse
You try to flash magisk from Twrp
Difficul said:
You try to flash magisk from Twrp
Click to expand...
Click to collapse
Nope! A12 support TWRP?
Difficul said:
You try to flash magisk from Twrp
Click to expand...
Click to collapse
Can't install or update any apps , error not enough space. ( read only bug A12)
yshiv666 said:
I have Build Xdroid-13_arm64-bgN-lite-UNOFFICIAL.img one with A12 and one with A11 AP file. Both were working.
BUT Both have different issue
on A12
-Magisk broken(Warning:- you don't have enough space to install this app),
- USB debugging working
And
on A11
-Magisk working
-USB debugging Broken
Click to expand...
Click to collapse
Hmm. Thanks for the report because both are very important for me. I was building that GSI as of this post. Canceling. Sticking with A12 VGB with CherishOS A12 for a long time until issues get fixed.
yshiv666 said:
Nope! A12 support TWRP?
Click to expand...
Click to collapse
sorry
tom.android said:
Can't install or update any apps , error not enough space. ( read only bug A12)
Click to expand...
Click to collapse
I think it's because of the partition problem, usually the Bl upgrade will reduce the free partition
Difficul said:
I think it's because of the partition problem, usually the Bl upgrade will reduce the free partition
Click to expand...
Click to collapse
If it's about partition locked / not enough spaces uses this
[MAGISK][TWRP][ARM32/64][A8+]Universal Read Only to Read Write for android (RO2RW) | Auto converting SUPER "system partitions" to read/write mode
Read Only to Read Write for android (RO2RW) Update 03.01.2023 : Stable Beta v 3.7.2.1 The first truly working script, original and unique in its logic for all devices with a SUPER partition Universal auto RO2RW | EROFS-2-RW | F2FS-2-RW by...
forum.xda-developers.com
But I don't thinks so.
next step by step Tutorial>Read Only to Read Write for android (RO2RW)
( SM-T22x Based on Android 12 )
How does the script work in Magisk?
- You need to install the archive via Magisk manager as a module. The script will tell you if you need to restart the device. Next, you need to launch the terminal and give it root rights with the command "su", Then enter the command "RO2RW" and the script will run, it will prepare an image of RW-super.img according to your choice and optionally backup the original super bak-super.img. These files will occupy the internal storage, so in order to get the space back you need to move them to a PC so that the modified image can be flashed via fastboot. Or you can simply flash it via TWRP as img super if the images are for recovery. Or
*After you got new super.img then you can uses CustomAP Making to flash with odin.
" Tested but not works"
tom.android said:
next step by step Tutorial>Read Only to Read Write for android (RO2RW)
( SM-T22x Based on Android 12 )
How does the script work in Magisk?
- You need to install the archive via Magisk manager as a module. The script will tell you if you need to restart the device. Next, you need to launch the terminal and give it root rights with the command "su", Then enter the command "RO2RW" and the script will run, it will prepare an image of RW-super.img according to your choice and optionally backup the original super bak-super.img. These files will occupy the internal storage, so in order to get the space back you need to move them to a PC so that the modified image can be flashed via fastboot. Or you can simply flash it via TWRP as img super if the images are for recovery. Or
*After you got new super.img then you can uses CustomAP Making to flash with odin.
Click to expand...
Click to collapse
Did this worked on xdroid installed on top of stock a12 like apps can now be installed and not tell that is not enough space or sepolicy denaial ?
{
"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"
}
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:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
Supported Models:
Galaxy S23 Ultra S918B/S918N/S9180.
Download & Guide:
1. Unlock your bootloader.
2. Downloads for S23 Ultra: AFH: dm3q twrp
3. Reboot to download mode
4. Uncheck auto reboot in Odin and flash TWRP in AP slot and vbmeta_disabled_R.tar in USERDATA slot.
5. Hold volume down and power until the screen goes black then immediately switch to holding volume up and power to reboot into TWRP.
6. Go to wipe, format data, and type "yes" to confirm.
7. Reboot to TWRP
8. Flash boot_repack.zip (To fix stock recovery restoration)
9. Flash magisk canary (Optional)
10. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Decryption will only work if no password/PIN/pattern is set in Android.
- No erofs r/w support yet.
Thanks:
TWRP team
@BlackMesa123 for helping me to add encryption support
@dr.ketan for supporting meDonators
Sources:
Kernel tree
Device tree
Changelog:
GitHub History
mine
afaneh92 said:
Bugs:
- Encryption not fully working.
- No erofs r/w support yet.
Click to expand...
Click to collapse
Data decrypt support should be mandatory for this device expecially with the newer A13 EROFS partitions, please consider adding it.
BlackMesa123 said:
Data decrypt support should be mandatory for this device expecially with the newer A13 EROFS partitions, please consider adding it.
Click to expand...
Click to collapse
I tried on S20+ and S22 ultra it was harder than A series. But will try again when the device delivered, I may ask for your help. Thanks.
afaneh92 said:
I tried on S20+ and S22 ultra it was harder than A series. But will try again when the device delivered, I may ask for your help. Thanks.
Click to expand...
Click to collapse
Implementing crypto support is not that hard as it seems, in the S23 family it should even be easier since you can just implement the official TeamWin QSEE scripts in your device tree. I imagine the big deal on S20/S22 is due to those device having an Exynos SoC with TEEgris TZ, but even in that case it should be easy to handle. What I'm more afraid of is that this device probably has Knox SDP in vold so decrypt with PIN/password set won't work, but it's better than nothing atm.
BlackMesa123 said:
Implementing crypto support is not that hard as it seems, in the S23 family it should even be easier since you can just implement the official TeamWin QSEE scripts in your device tree. I imagine the big deal on S20/S22 is due to those device having an Exynos SoC with TEEgris TZ, but even in that case it should be easy to handle. What I'm more afraid of is that this device probably has Knox SDP in vold so decrypt with PIN/password set won't work, but it's better than nothing atm.
Click to expand...
Click to collapse
I was referring to snapdragon, and never worked. I used your implementation and device wasn't able to decrypt data. S22 was harder since data wasn't able to mount. I will wait for device, thanks again.
afaneh92 said:
I was referring to snapdragon, and never worked. I used your implementation and device wasn't able to decrypt data. S22 was harder since data wasn't able to mount. I will wait for device, thanks again.
Click to expand...
Click to collapse
We can surely work it out to fix it
@afaneh92 it looks like S23 vold has no crap A11 code leftovers which does break decrypt with PIN/password on TWRP, I compared the vold bin with my A52s' one and certain stuff is clearly missing. So it might just work out of the box once support for it gets added
BlackMesa123 said:
@afaneh92 it looks like S23 vold has no crap A11 code leftovers which does break decrypt with PIN/password on TWRP, I compared the vold bin with my A52s' one and certain stuff is clearly missing. So it might just work out of the box once support for it gets added
Click to expand...
Click to collapse
I hope so.
Nice work!
I followed the steps above, and when trying to reboot to system I get back to to twrp. Help please?
I just want to ask if anyone has tried installing viper4android yet and does it work? If it's like the s22 ultra and doesn't work. I might sound crazy but I wouldn't buy it. Music is more important to me then spen and camera although admittedly they are good to. It's mind blowing to think 1200 dollar won't sound as good as my Poco f3 or even my lg tribute 10 years ago.
lcd047 said:
I followed the steps above, and when trying to reboot to system I get back to to twrp. Help please?
Click to expand...
Click to collapse
I have exactly the same:
- after following all steps one by one there is only a reboot into TWRP itself possible
I compared the steps from this thread with the steps which are successfully working on my Galaxy Tab S8 Ultra ( https://forum.xda-developers.com/t/...-for-galaxy-tab-s8-series-snapdragon.4455491/ ) and I see a difference at step 7:
7. Flash custom kernel and magisk apk in twrp.
Click to expand...
Click to collapse
I do not see any "custom kernel" to download in this thread (at least for now) so I think this is the missing part. Or it only works correct in combination with "dr.ketans rom" (which I do not want to use for now).
@afaneh92: Thank you very much for your work (on "root" and also with "twrp")!
Edit: I just read the installation pdf from "dr. ketans rom". There is written in red letters:
DON'T run multidisabler from TWRP termial/zip or any system-rw script after flashing ROM else device won't boot.
Click to expand...
Click to collapse
So maybe the not booting system is related to the work which the "multidisabler" should do.
I will be happy if there will be some light regarding the non booting system after flashing TWRP.
Maybe I will give "dr. ketans rom" a try and have an eye on this thread how the things go on.
________________________________________
@Techguy777: This is very offtopic but I am with you that "Viper4Android" is a very important part also of my daily used tools. I just have found a (for me) good running workaround.
Search the fDroid store for the app "RootlessJamesDSP". Depending on which parts of "Viper4Android" you care about, the app is an extremely good working replacement. In my example, the "Convolver" with the impulse response files are important and that works wonderfully with the players I use.
hurray said:
I will go back for now to (rooted) stock ROM and Recovery and will have a look how this thread will go on.
Click to expand...
Click to collapse
Sadly flashing "dr.ketans rom" (or the "unroot" one, for that matter) doesn't fix the problem for me. Ironically everything was working fine with "dr.ketans rom" alone, but I just had to try disabling encryption. Well I suppose better is the enemy of good.
lcd047 said:
Sadly flashing "dr.ketans rom" (or the "unroot" one, for that matter) doesn't fix the problem for me. Ironically everything was working fine with "dr.ketans rom" alone, but I just had to try disabling encryption. Well I suppose better is the enemy of good.
Click to expand...
Click to collapse
I just flashed the orginal FW from samfw.com and my S23 Ultra is booting correctly into the system. Now I will try the current "S918B_WA6_DrKetan_ROM_T02". It seems that TWRP is build in into the ROM. If this works I will try a backup & restore of user data (this is the most important part from TWRP for me).
hurray said:
I just flashed the orginal FW from samfw.com and my S23 Ultra is booting correctly into the system. Now I will try the current "S918B_WA6_DrKetan_ROM_T02". It seems that TWRP is build in into the ROM. If this works I will try a backup & restore of user data (this is the most important part from TWRP for me).
Click to expand...
Click to collapse
After flashing my ROM + Format dara (Read changelog) TWRP backup/restore data should work as expected. And for that purpose mentioned in OP
dr.ketan said:
After flashing my ROM + Format dara (Read changelog) TWRP backup/restore data should work as expected. And for that purpose mentioned in OP
Click to expand...
Click to collapse
Yup, flashing the full ROM works. Many thanks, and keep up the amazing work!
dr.ketan said:
After flashing my ROM + Format dara (Read changelog) TWRP backup/restore data should work as expected. And for that purpose mentioned in OP
Click to expand...
Click to collapse
You have convinced me of your ROM. After flashing I had to reformat "data" but afterwards the system booted correctly.
The ROM works very well so far and the additional functions via "ROM Tools S23" are also good (especially that they can be selectively enabled and disabled).
Backup and recovery of user data has also worked flawlessly.
So now I can start with the actual setup of all apps.
Thanks a lot for your work!
hurray said:
You have convinced me of your ROM. After flashing I had to reformat "data" but afterwards the system booted correctly.
The ROM works very well so far and the additional functions via "ROM Tools S23" are also good (especially that they can be selectively enabled and disabled).
Backup and recovery of user data has also worked flawlessly.
So now I can start with the actual setup of all apps.
Thanks a lot for your work!
Click to expand...
Click to collapse
I have seen many users don't want "custom" roms, but my ROM will have complete stock look + single click all critical fix. It won't force users to use customised look. Also it have more options to make modifications in ui but everything will be by user's will.