How is the proper way of installing GSI images? I have tried TWRP method and Fastboot method, neither of them works. Is it even possible on this device?
Fastboot method gets error @ "fastboot erase system" (remote: Check device console)
BL Unlocked ofc and adb/fastboot is up to date as well drivers
TWRP - i lose all my partitions for some reason and have to MSM back to working state
GSI i tried https://developer.android.com/about/versions/12/gsi-release-notes#downloads
This is my first fully treble supported device and i actually do not know how A and B partitions behave while doing gsi/rom flashing. Perhaps someone can explain it?
ArletPDR said:
How is the proper way of installing GSI images? I have tried TWRP method and Fastboot method, neither of them works. Is it even possible on this device?
Fastboot method gets error @ "fastboot erase system" (remote: Check device console)
BL Unlocked ofc and adb/fastboot is up to date as well drivers
TWRP - i lose all my partitions for some reason and have to MSM back to working state
GSI i tried https://developer.android.com/about/versions/12/gsi-release-notes#downloads
This is my first fully treble supported device and i actually do not know how A and B partitions behave while doing gsi/rom flashing. Perhaps someone can explain it?
Click to expand...
Click to collapse
The 8T is not only an A/B device, it is also a virtual A/B device. I'd be very surprised if you could get a"normal" A/B GSI to boot on an 8T.
Virtual A/B Overview | Android Open Source Project
source.android.com
There is this Dynamic System Updates feature, i have used it earlier to test android 12 GSI
But now I'd ike to delete wherever those GSI's stored, so that i possibly can test other GSI there is
{
"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"
}
ArletPDR said:
There is this Dynamic System Updates feature, i have used it earlier to test android 12 GSI
But now I'd ike to delete wherever those GSI's stored, so that i possibly can test other GSI there is
View attachment 5374671
Click to expand...
Click to collapse
Click discard on the notification of dynamic system updates.
If no notification then the gsi is deleted
I did that in hopes that it clears this dsu dialog up from those that is there now, but no, they are still there and i can use them if i want. it's like they are stored somewhere? (i have no other GSI type file stored on my local storage btw)
ArletPDR said:
I did that in hopes that it clears this dsu dialog up from those that is there now, but no, they are still there and i can use them if i want. it's like they are stored somewhere? (i have no other GSI type file stored on my local storage btw)
Click to expand...
Click to collapse
Do you mean that the installation of the dsu is so fast that it is impossible to download a 3gb GSI in such a short time?
Well, i did not know that it requires internet connection, i always tough it uses file from local storage
ArletPDR said:
Well, i did not know that it requires internet connection, i always tough it uses file from local storage
Click to expand...
Click to collapse
It also occured to me, only takes a few minutes to install dynamic system.
To me though, when I discarded the GSI at that instant there will be a few gigabytes freed and that is a sign of the GSI deleted.
For me it takes a while tho
All the DSU magic happens in this folder
Tried deleting the gsi there?
It was empty before i started dsu installation, also i have no dsu install file on internal storage download folder, that proves the fact that is takes dsu file or filename from internet, because when i rebooted i was greeted with OOS, the same i have primarily installed, with only 4gb on internal storage, and i made screenshots there, but they're gone now.. obviously
LR7875 said:
Tried deleting the gsi there?
Click to expand...
Click to collapse
No i did not, discarding from notification panel did just that
Related
why my pixel always show some unknown file in twrp like this
i cant find my "download" file and zip file that i already put in the phone
{
"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"
}
pls help
I have had the same issue with TWRP. While I cannot find any cause for it, a reboot (or more than one) into recovery seems to eventually result in the actual files being shown. This is even more of an issue if installing the .img and needing to then install a .zip. It can take a couple times. Strange, this has only happened with my wife's Pixel and not my XL but that may just be luck. Did not have this issue with Apha 2, only RC1.
qe7913468250 said:
why my pixel always show some unknown file in twrp like this
i cant find my "download" file and zip file that i already put in the phone
Click to expand...
Click to collapse
It's because the data on your Pixel is encrypted AND TWRP can't decrypt at that time for some reasons. Keep rebooting it until it can successfully decrypt.
quangtran1 said:
It's because the data on your Pixel is encrypted AND TWRP can't decrypt at that time for some reasons. Keep rebooting it until it can successfully decrypt.
Click to expand...
Click to collapse
i have try to reboot for 10 times and it didnt change
what can i do
my twrp is A2 version
qe7913468250 said:
i have try to reboot for 10 times and it didnt change
what can i do
my twrp is A2 version
Click to expand...
Click to collapse
Don't know what to advise you further since it happens to all of us. I would only provide suggestions on issues that I myself came across. I can only relay my experience (Verizon). I use TWRP RC1. It happens to me whether or not I have my device passworded. It happens to me more often when I change boot slot. In other words, if I go to Reboot, change slot, and reboot, I would get that situation. But if, from inside TWRP, I power off the phone, then I can get a successful decryption pretty much 95% of the time. It seems like a programmatic timing issue to me. From my app development experience, sometimes if task B gets executed before task A because of driver issues or timing issues, I'd get undesired results (not unexpected, just undesired).
Are you doing a full reboot or just rebooting Recovery? I find it often have to do a full reboot for it to pick it up sometimes.
cambunch said:
Are you doing a full reboot or just rebooting Recovery? I find it often have to do a full reboot for it to pick it up sometimes.
Click to expand...
Click to collapse
Agreed.
qe7913468250 said:
i have try to reboot for 10 times and it didnt change
what can i do
my twrp is A2 version
Click to expand...
Click to collapse
Try changing your lock screen method (in the os) to something else. I use a pattern and have had no trouble getting twrp to prompt me for it.
try to reboot recovery and system will work, I have encountered same issue.
had this issue the other day when updating to the January build. while in your current rom delete the twrp folder within your internal storage. next time you restart into TWRP, it will prompt you to enter the decryption password
Or use an external USB drive and bypass the entire decryption problem altogether.
use SD card or use OTG cable with pendrive and put file their and select OTG directory from twrp.
The only command prompt that seems to be working is fastboot flash boot twrp.img but when I type fastboot flash recovery the flash fails. I use Minimal ADB and Fastboot command prompt. The latest version too. I downgraded my android 11 to 10 successfully. I have no problems rooting magisk through ADB but why can't TWRP permenantly stick? How can I force it to stick as my main recovery no matter what rom I flash?
Crap. I did not mean to say android 11 on the topic title. Wish I could edit it. I meant to say Android 10. Sorry for the confusion. Any tips of how to retain twrp? Having problems with my unlocked pixel 4a.
This guide shows you how to get TWRP to stick:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
P4a doesn't have a recovery partition anymore, recovery is part of the boot.img. That's why the fastboot cmd fails.
UltimateGamer83 said:
Crap. I did not mean to say android 11 on the topic title. Wish I could edit it. I meant to say Android 10. Sorry for the confusion. Any tips of how to retain twrp? Having problems with my unlocked pixel 4a.
Click to expand...
Click to collapse
You can't flash recovery on this phone. It's part of boot.img. Put the TWRP.img file in your internal storage of your phone. Flash the TWRP temporarily first. Fastboot boot TWRP.img. When TWRP boots, click install, then select install image. Choose your TWRP file and select install Ramdisk. Swipe to flash. TWRP will then be installed permanently. You must also be using a custom kernel with TWRP compression support because the partition is not big enough and must be compressed otherwise you will run into issues like TWRP freezing or touch screen issues.
I tried that and twrp still wont stick even after a OTA update flash. I installed ram disk twrp even after the update. What gives?
I fixed it. My mistake was flashing magisk boot img after the ramdisk installation and two kenel. I just flashed magisk.zip instead and got things working.
UltimateGamer83 said:
I fixed it. My mistake was flashing magisk boot img after the ramdisk installation and two kenel. I just flashed magisk.zip instead and got things working.
Click to expand...
Click to collapse
Yes, if you flash magisk boot img it will replace TWRP. Flashing the zip is the way to go. Glad you got it working.
UltimateGamer83 said:
I did not mean to say android 11 on the topic title. Wish I could edit it. I meant to say Android 10.
Click to expand...
Click to collapse
I've move your thread out of development, for which it doesn't qualify.
And I assumed your consent and edited the thread title.
In order to edit a title, click the "Edit" button of your OP and you'll see the title at the very top, which you're able to edit:
Spoiler: Screenshots
{
"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"
}
Regards
Oswald Boelcke
Senior Moderator
UltimateGamer83 said:
I tried that and twrp still wont stick even after a OTA update flash. I installed ram disk twrp even after the update. What gives?
Click to expand...
Click to collapse
I'm curious....you said you are on Android 10, but then you mentioned above installing an OTA update.....I thought all the currently available OTA updates are only for android 11?
My 10 cents worth. Magisk kills fastboot and adb in MY armor x5 mt6765, in 10_Q, so had no choice but to load boot-debug.img just to 'test'.
Try an android 9 bootloader designed for them 'super' .img's, this is the only way I could LOAD magisk, only to find what I read here.
Also note, in 10_Q, the gsi ability found in dev options dissapears when magisk is flashed, so I cant flash gsi, never mind use fastboot or adb.
Thank you.
Hi,
I have problem How can I roll back to Android 11 from 12 ROM.
I have DFE and root .
Please help me because my work apps don't work on A12.
as far i know there is no android 12 stock rom yet. perharps you are in a custom rom... if that is so.. you just need to flash stock rom with miflash tool and the androdi 11 stock rom version of your device (global, eu, china, etc...) but be careful with the *clean all *save user-data *clean all and lock scripts.... right now some apps detects the bootloader unlocked and maybe that's why your apps doesn't work. you also can try magisk (and magisk hide) to get your apps work again but topjhonwu (creator of magisk) have already drop support of "magisk hide" so is only matter of time for root also stop working
I don't I have rtn PC so I need do it in all in TWRP on phone .
also.. you can check if the rom you want to rollback does not brick ypur device with the "anti-rollback" system that xiaomi create...
use the cmd command "fastboot getvar anti" on fastboot mode, you will get a number (0,1,2,3,4) and check your rom that has the same or higher number....
for example:
if your device shows "anti: 2" you can only flash (trought miflash tool) roms with anti_ver_ : 2,3,4)
on the scripts of your stock rom "clean all *save user-data *clean all and lock you can check the anti rollback version of the rom by using notepad++ and looking something like this
{
"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"
}
astronomy2021 said:
I don't I have rtn PC so I need do it in all in TWRP on phone .
Click to expand...
Click to collapse
again.. if you are in a custom rom.. you can flash android 11, but the fact that your apps wont work because you rooted your device has nothing to do with which version of android you flash... but if your apps detects that the bootloader is unlocked... you can only relocked again using the stock rom with the *clean all and lock script...
google tutorial on youtube.. there are plenty of them and in different languages
You don't understand my apps works on rooted device but not Android 12 I had few ROM like Arrow Os or PE and root and kernel but no problem now I try thee ROM of Android 12 and doesn't work at all.
astronomy2021 said:
You don't understand my apps works on rooted device but not Android 12 I had few ROM like Arrow Os or PE and root and kernel but no problem now I try thee ROM of Android 12 and doesn't work at all.
Click to expand...
Click to collapse
aahh, i get it now.... then just flash arrow os 11... but i think you are gonna loose data
astronomy2021 said:
I don't I have rtn PC so I need do it in all in TWRP on phone .
Click to expand...
Click to collapse
you dont have pc and dont have access to data
now that is a very tough situation
do you have SD card?
Your not encrypted right?
Just wipe super, data (NOT Internal, so media file is safe), cache.
Then flash the ROM + DFE.
You'll be okay and stay decrypted.
But if you're on encrypted internal, you need to format internal in TWRP (lose all data + media)
Also
Magisk isn't dead.
There's Magisk 24 with new root hide solution Zygisk.
.... and big problems with lost root and email certificates... i´m just trying to return to Magisk 23 because of massive problems with version 24 sharing this with some more users ...
Hi, people!
Spoiler: Old message:
Porting our TWRP for A12 (ZUI 14.0.127).
Now it's fully working, exept touchscreen. But with mouse connected via OTG you can to do all neeeded operations.
IMPORTANT! The method of decrypting /userdata is not implemented there (different from A11), so you need to install the DFE-NEO patch to make it work properly with your data.
EDITED: New version v5
Added ability adb/MTP on encrypted /data.
MTP works on demand, pressing Disable MTP-Enable MTP, displays SD card only.
UPDATED Febr. 08:
Built a new full-featured version with data decryption from source. For Android 12 - ZUI 14
Decrypts data by default, if the tablet is not protected.
If it's protected by pin/password, it asks for it and decrypts internal storage.
I haven't tried the pattern, see here: https://twrp.me/faq/openrecoveryscript.html (Specific pattern decrypt note), try it yourself.
Device tree lies here: https://github.com/F1tm0t/twrp_device_lenovo_J716F
Many thanks to:
Yahoo Mike - for useful tips on decryption implementation and general support.LSS4181 - for Q706F device tree, I used it as a basis for mine.Ungeskriptet - for his J716F device tree for A11, it was useful for me.TWRP_J716F_A12_DD. img DD means Data Decryption.
Working: Everything, excluding vibration.
MEGA
PS.
Welcome to collaboration.
I have another variant of TWRP with a malfunctioning touch. The pressure points do not correspond to the position of the buttons. It need to add some calibration files or the right firmware or the right driver for the screentouch. This is too complicated for me I'm just advanced user, no guru.
Please, write me in PM if you can help with this issue.
Nice to see some development for the TB-J716 tablet XD since the developer don't want to release the kernel source/ open source to the public.
Die you add the firmware for touch to TWRP? I have it like this in my TWRP port: https://gitlab.com/ungeskriptet/and...tree/android-11/recovery/root/vendor/firmware
I suggest you extract the firmware yourself from the latest ZUI, the older versions might not work.
Ungeskriptet said:
I suggest you extract the firmware yourself from the latest ZUI, the older versions might not work.
Click to expand...
Click to collapse
Yes, I was trying this.
Thanks for the tip. I have a couple of questions. I'll write you in PM, if you don't mind.
Version with working touch is here:
Файл из Облака Mail.ru
Вам открыли доступ к файлу. Отправлено с помощью Облако Mail.ru.
cloud.mail.ru
and here:
100 MB file on MEGA
mega.nz
Remember, you can't to backup data before using DFE-NEO patch.
Many thanks to Ungeskriptet for helping.
To be continued (I hope)
New version for ZUI 14 with new features:
* added many partitions for backup/restore
* added some partitions for flashing via Install IMG
* A set of partitions is enough to backup/restore an entire OS
Placed here. To see how it works, click here:
Spoiler: Youtube
FFBM mode is my mistake, wrong button pressed, no need
Hello @f1tm0t
The TWRP seems unable to use ADB shell due to ro.adb.secure=1
Could you help to edit that value? I tried many tool to rebuild TWP with new prop but no luck, device bootloop
Thanks
phamthanh said:
Hello @f1tm0t
Click to expand...
Click to collapse
Hello, friend.
My TWRP works with adb/MTP quite excellent.
The following is needed:
decrypt /data
permission in the system to debug from this computer
Spoiler
{
"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 your help, I will redownload and double-check again.
Hi @f1tm0t
I re-download and flashed v3 but the same result
Could you help me to check it
Thanks
phamthanh said:
I re-download and flashed v3
Click to expand...
Click to collapse
I offer version 4: https://mega.nz/file/g4VBnIpC#_4_x0b3V-Z6oSoXDA2xbHSN7hBKXRgjnwfFMLfPcYXA
My version cannot decrypt /data, so you have to install the DFE-NEO patch from TWRP.
After rebooting to OS you must to enable USB debugging, it create adb.key in /data.
And after rebooting to TWRP you can use adb/MTP, because TWRP sees adb.key in not-encrypted /data.
phamthanh said:
The TWRP seems unable to use ADB shell due to ro.adb.secure=1
Click to expand...
Click to collapse
Made new version (in the title), adb works by default. Enjoy!
f1tm0t said:
Made new version (in the title), adb works by default. Enjoy!
Click to expand...
Click to collapse
Many thanks
Updated.
New TWRP with working data decryption, see update in topic.
Can someone post a list of the pixel 7 pro partitions in fastbootd? Im having issues with getting my device working properly cuz some of my partitions are missing and im not sure.. do both slots have to have the product, vendor, vendor dlkm system dlkm etc? im just not sure which partitions need to be on the inactive partition
PochiRaccoon said:
Can someone post a list of the pixel 7 pro partitions in fastbootd? Im having issues with getting my device working properly cuz some of my partitions are missing and im not sure.. do both slots have to have the product, vendor, vendor dlkm system dlkm etc? im just not sure which partitions need to be on the inactive partition
Click to expand...
Click to collapse
I apologize in advanced for not answering your question directly....
But I'm guessing you may be having issues because you attempted to flash the factory image and are bootlooping or not loading the OS; and you had made sure to use the latest version of platform-tools.
I'm guessing this because the latest version of platform-tools (version r34+) has an established notorious bug that doesn't allow it to reboot into fastbootd mode to flash the rest of the partitions that can only be flashed there -- which seems to be the case for you.
If this is your case, you should be able to successfully flash the Full Factory image using the last platform-tools version that did not have said bug -- version r33.0.3. You can find a post to be able to download it below...
Using that version of PT, it should be able to flash all the necessary pertinent partitions and you should be up and running. Be sure to remove the "-w" from the flash-all file or your phone will be completely wiped and returned to stock. I don't imagine you need to flash it to both slots as you only need one slot stable to boot from; but if you wish, you could always reboot back to bootloader, switch slots, and run the flash-all on that slot -- just be sure to not try to boot into the OS from that slot until you've run the flash-all on it; lest your issue indirectly affected it and you may run into some problems.
Good luck and hope this helps...
June 20, 2023 TQ3A.230605.012.A1 Verizon/MVNOs / June 13, 2023 TQ3A.230605.012 Global - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
Is that bug specific to Windows?
I used r34.0.1 on Manjaro Linux without any issues...
I even use "android-sdk-platform-tools-34.0.1-1" from AUR as the provider for adb and fastboot instead of the complete Android Studio...
kodabmx said:
Is that bug specific to Windows?
I used r34.0.1 on Manjaro Linux without any issues...
I even use "android-sdk-platform-tools-34.0.1-1" from AUR as the provider for adb and fastboot instead of the complete Android Studio...
Click to expand...
Click to collapse
It is specific to that all version after 33.0.1. It doesn't allow the phone reboot to FastbootD. There for the partitions that need to flashed in fastbootD cannot occur.
I have personally used it to flash fastbootd images for the Radioactive kernel. No issues encountered using Linux.
I just tested it again:
Code:
adb reboot fastboot
It rebooted to fastbootd as expected. It's a Lineage fastbootd from when I tried Lineage 20. If it's not just a Windows thing, maybe it's how the stock fastbootd interacts.
{
"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"
}
The issue with any adb/fastboot version r33.0.3+ has more to do specifically with the flashing Google's Full Factory images (flash-all) than it is specifically in booting into fastbootd. This also explains why flashing kernels or other specifics still work. For complicated reasons, when running the fastboot "update" command, when needing to flash into the fastbootd mode for flashing certain images/partitions, it fails -- only really following through with the fastboot update protocol than merely just booting into fastbootd.
Most likely, the reason why all the partitions are corrupted/invalid/wrong that's supposed to be flashed in fastbootd for the OP is because of this reason. I'm jumping to that conclusion; but it makes sense.
Also, it is easier to download platform tools directly from Google's developer's site than downloading it as part of a package or taken from Android Studio or other. You can find it here (for Windows, Mac, & Linux): https://developer.android.com/studio/releases/platform-tools