Related
Hello, I've spent several hours searching a solution for this problem, both on this forum as well as others. But still unable to find one I try my luck here.
This is the case:
U8800 bought in Sweden a couple of weeks ago. Installed SuperBoot r1 and CWM 4.0.0.5 Perfect Recovery from XDA forums. Installed Oxygen 2.2.2 r4, worked fine until yesterday. When it got stock at the screen lock. Pulled battery and then it was stuck in a boot loop showing only the IDEOS-logo. Tried to get into recovery with Vol+ and power. But still only gets to IDEOS-logo and then reboot after about 10 seconds.
I'm able to get into bootloader (pink-screen) by Vol+, Vol- and Power. Have tried to replace boot.img and recovery.img with others (original backup, CWM 5.0.2.3) in both Ubuntu 11.10 and Win 7). But still unable to reach recovery. And next time I start bootloader and check it's still the same boot.img and recovery.img as it was before I replaced them.
Seems like I'm unable to write to image folder somehow. It looks good when I disconnect it from the computer. Have tried "safe removal" in both Ubuntu and Windows, no difference. Also tried to rename the files to boot_backup.img and recovery_backup.img and then put the new files in there. But next time I start bootloader they are once again restored to how they were before (same file size as before) and the renamed files doesn't exists any more.
Have also tried to install B136 stock ROM via bootloader, looked good at first but when it was finished it said "Installation failed" (or something similar)...
Read somewhere modding the build.prop could cause boot loops, but I haven't touched that and therefore doesn't have any backup of it either.
Any ideas?
Yep, it looks like your bootloader may be corrupt...Do the following:
Boot the phone in Bootloader (pink screen) by pressing Vol+, Vol- and Power and connect the USB cable. Copy all the files you can find on that partition (this will be your backup) and format the partition with FAT32 file system, create a folder named "image" and copy the following files on there.
EMMCBOOT - http://www.mediafire.com/?lb6ifvgk72iru4a
AMSS.MBN - http://www.mediafire.com/?d6r45q6p5gew59v
Recovery.img - http://www.mediafire.com/?57njygc8oianjac
Boot.img - http://www.mediafire.com/?6d5i0714a7o9z97
Once you've done this, take the battery out and boot into Recovery and flash a new Rom (VOL+ and Power.)
Let me know how this goes...
Thank you very much for your help!
However when I try to format the partition windows says it couldn't complete the format. Tried both to right click > format and disk management > format. FAT32/std fast format as well as regular/slow. Neither work. If I do a regular format it goes at normal rate up to 100% and then says the disk isn't formatted...
I don't know if I dare to remove the partition and make a new in disk management, feels like I would screw something else up then?
Any tips?
Have tried to format in Ubuntu 11.10 as well, with the standard tool it didn't complain, but it didn't format it either. Installed GParted and tried that, it did seem to work and said it had successfully formatted it. But yet the image-folder still remains on the boot partition...
Run a systemcheck with the disk management in Ubuntu and it said the file system was OK.
I'm almost out of ideas now...
I don't think you're actually formatting the drive as the "image" folder should be gone once the format is done.
Try using a windows PC, I know that Gparted and Ubuntu can be a bit tricky sometimes...
Also, you've definitely installed the drivers for the cable?
On Windows 7 the drivers are being automatically installed, so maybe you should try that...
I've tried Windows 7 several times (the only Windows I use). It's very weird the files just wont go away. I have taken Shift+Del on the image folder several times and they are removed just as any other files on the computer. Then the next time I connect it the very same files (58 MB) are back! When I do a format the computer shows the disk empty, but when the error window comes up the files are back... In ubuntu GParted shows the partition empty, but after a re-scan the 58 MB are back...
Can try to see if I can make a screen recording to see if I'm doing it wrong somehow.
Thanks for your support!
I have a short screencast on screenr illustrating the problem, but unable to post a link I'll try to describe it.
screenr(dot)com(slash)WMls
Pastasallad said:
I have a short screencast on screenr illustrating the problem, but unable to post a link I'll try to describe it.
screenr(dot)com(slash)WMls
Click to expand...
Click to collapse
Seen your screencast...it's a bit unclear. Sent you a PM, hopefully we'll be able to sort this out.
Same problem here h ttp//forum.xda-developers.com/showthread.php?t=1318647
The bootloader seemed to be beyond rescue. Nothing seemed to help, tried several drivers and computers. But the partition seemed locket somehow, couldn't replace the files. Tried to flash in stock ROM 136 and 138. Both failed unless you removed the cust update file. Then it succeeded, but still bootloop when it restarted.
So the phone is now returned for service.
Thanks katu2006 for all the help!
I installed latest CWMR. Created a backup to my external SD. Formatted /system, /data, /cache. Flashed CM11 Nightly, cm-11-20131216-NIGHTLY-xt907.zip . Booted fine, ran fine. Went to add my Wifi SSID and when I toggled the Wifi, it toggled back off/on/off/on/off ect... for a few seconds then stayed off. Rebooted. Same thing. Cleared cache and dalvik, same thing. Cleared data/factory reset, same thing.
Decided to restore my backup so did full format (/system, /data, /cache), then restore. System booted into my old stock install which I backed up, same Wifi issue. It acts like it is trying to initialize the service but fails and retries about 6 times, then stays in the OFF position.
So then I decided to try a full factory restore with RSD-Lite and the zip containing 4.1.2. Completed with 0 errors, rebooted, completed initial setup, same Wifi issue present.
Has anyone else encountered this? And If so, do you have any suggestions on how I can restore my Wifi to working order?
Can anyone direct me to some ways I can dig deeper to diagnose this? Is there a tool that looks at the Wifi device and logs errors that may be helpful? I will post a logcat as soon as I can get it.
Unholyfire said:
I installed latest CWMR. Created a backup to my external SD. Formatted /system, /data, /cache. Flashed CM11 Nightly, cm-11-20131216-NIGHTLY-xt907.zip . Booted fine, ran fine. Went to add my Wifi SSID and when I toggled the Wifi, it toggled back off/on/off/on/off ect... for a few seconds then stayed off. Rebooted. Same thing. Cleared cache and dalvik, same thing. Cleared data/factory reset, same thing.
Decided to restore my backup so did full format (/system, /data, /cache), then restore. System booted into my old stock install which I backed up, same Wifi issue. It acts like it is trying to initialize the service but fails and retries about 6 times, then stays in the OFF position.
So then I decided to try a full factory restore with RSD-Lite and the zip containing 4.1.2. Completed with 0 errors, rebooted, completed initial setup, same Wifi issue present.
Has anyone else encountered this? And If so, do you have any suggestions on how I can restore my Wifi to working order?
Can anyone direct me to some ways I can dig deeper to diagnose this? Is there a tool that looks at the Wifi device and logs errors that may be helpful? I will post a logcat as soon as I can get it.
Click to expand...
Click to collapse
After the restore did you test wifi on stock?
Otherwise, seems it is a kernel issue with cm. At lease behaving like one. Bad rom download?
---------- Post added at 03:11 PM ---------- Previous post was at 03:07 PM ----------
Did you wipe data b4 you restored???
Not doing so can cause wifi to break.
It is not commonly known but it happened to me.
Yes after I restored from my backup, I tested wifi and it did the toggle back and forth thing but never came on.
Honestly, I would like to assume I wiped data (/system /data /cache I normally wipe when doing anything like this), but I can't say for sure.
If I didn't, and broke the wifi, is there any way to fix it? Is this a hardware break?
When it happened to you, did you have to replace the mainboard?
Unholyfire said:
Yes after I restored from my backup, I tested wifi and it did the toggle back and forth thing but never came on.
Honestly, I would like to assume I wiped data (/system /data /cache I normally wipe when doing anything like this), but I can't say for sure.
If I didn't, and broke the wifi, is there any way to fix it? Is this a hardware break?
When it happened to you, did you have to replace the mainboard?
Click to expand...
Click to collapse
No no.
Rsd restore is the fix. Just be sure to wipe data before. I have an easy version. See my stickys.
Yea already tried, but now I think I have a messed up partition. Fails with some odd error in flashing /boot.
Unholyfire said:
Yea already tried, but now I think I have a messed up partition. Fails with some odd error in flashing /boot.
Click to expand...
Click to collapse
No way.
Post the details.
When using RSD after full format of all partitions:
Downgraded security version
update tz version failed
preflash validation failed for tz
Tried another VRZ as well: VZW_XT907_4.1.2-9.8.1Q-66_1FF.xml
Same method. Wipe all, RSD, reboot, no Wifi still. Just toggles back and forth then stops on OFF.
Trying to recreate the partition error I saw still. Will post that when I can.
Unholyfire said:
When using RSD after full format of all partitions:
Downgraded security version
update tz version failed
preflash validation failed for tz
Tried another VRZ as well: VZW_XT907_4.1.2-9.8.1Q-66_1FF.xml
Same method. Wipe all, RSD, reboot, no Wifi still. Just toggles back and forth then stops on OFF.
Trying to recreate the partition error I saw still. Will post that when I can.
Click to expand...
Click to collapse
Why do you not flash ...94? You are unlocked.
---------- Post added at 01:28 PM ---------- Previous post was at 01:15 PM ----------
Use my restore ...mod7...xml in my restore thread. You do not format anything.
I will try that one right now.
But here is the error regarding the partitions:
I:Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host
Also now seeing:
warning: wipe_block_device: Wipe via secure discard suppressed due to bug in EMMC firmware
Both of these errors are shown after I format /system /data /cache in CWM then go to "show log".
Did I somehow add/remove a non-compatible partition to my EMMC? Does anyone have a reference layout of what partitions SHOULD be on a standard on this device?
Update: I ran your mod7 RSD. Still no Wifi. Same behavior.
Unholyfire said:
I will try that one right now.
But here is the error regarding the partitions:
I:Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host
Also now seeing:
warning: wipe_block_device: Wipe via secure discard suppressed due to bug in EMMC firmware
Both of these errors are shown after I format /system /data /cache in CWM then go to "show log".
Did I somehow add/remove a non-compatible partition to my EMMC? Does anyone have a reference layout of what partitions SHOULD be on a standard on this device?
Update: I ran your mod7 RSD. Still no Wifi. Same behavior.
Click to expand...
Click to collapse
You wiped Data?
Mod 7 ran from rsd & did all the ~22 steps & rebooted?
Did you bootup from there & had no wifi?
Then some HW problem must exist.
I do not understand why you did all that formatting.
Just discovered another person has the exact same issue after attempted install of the CM11 12-16 nightly.
LogCat from when I try to enable Wifi:
[ 12-26 13:48:02.733 713: 2770 E/WifiStateMachine ]
Failed to load driver!
[ 12-26 13:48:02.733 713: 849 E/WifiStateMachine ]
DriverFailedState
EDIT: Some more LogCat:
[ 12-26 13:58:21.178 295: 295 I/AudioFlinger ]
loadHwModule() Loaded r_submix audio interface from Wifi Display audio HAL (audio) handle 3
[ 12-26 13:58:27.254 705: 850 E/WifiStateMachine ]
Failed to disable IPv6: java.lang.IllegalStateException: command '1 interface ipv6 wlan0 disable' failed with '400 1 Failed to change IPv6 state (No such file or directory)'
[ 12-26 13:58:27.314 705: 729 I/WifiService ]
WifiService starting up with Wi-Fi enabled
[ 12-26 13:58:27.314 705: 729 D/WifiService ]
setWifiEnabled: true pid=705, uid=1000
[ 12-26 13:58:32.250 705: 1086 I/WifiService ]
WifiService trying to set country code to us with persist set to true
[ 12-26 13:58:36.114 1216: 1332 W/WifiNormalizer ]
No specific device detected. Offset set to -7.
[ 12-26 13:58:42.541 1540: 1786 W/Settings ]
Setting wifi_sleep_policy has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.
[ 12-26 13:58:27.825 705: 872 E/WifiStateMachine ]
Failed to load driver!
[ 12-26 13:58:27.825 705: 850 E/WifiStateMachine ]
DriverFailedState
Edit: Double post... oops.
Unholyfire said:
Edit: Double post... oops.
Click to expand...
Click to collapse
All this means nothing.
Did wifi work in the conditions of my previous post?
aviwdoowks said:
All this means nothing.
Did wifi work in the conditions of my previous post?
Click to expand...
Click to collapse
Nope. Still has not worked since it first stopped working after installing the CM11 12-16 nightly.
Tried the Mod7 RSD in your links. Same thing, wifi will not turn on. Same errors in logcat.
Unholyfire said:
Nope. Still has not worked since it first stopped working after installing the CM11 12-16 nightly.
Tried the Mod7 RSD in your links. Samea thing, wifi will not turn on. Same errors in logcat.
Click to expand...
Click to collapse
Are we on the same page?
Forget cm. I am talking about wiping data from cwmr, (do not go to mounts...) then booting to stock right after you run the rsd lite restore.
Yes that's what I did. I only mentioned cm to reference that's where all the trouble started. Anyway, I found someone else that also has the exact same problem after doing exactly what I did. They are also searching for a solution. Happened to both of us after installing cm11 nightly 12-16 in the same way. So if it's bad hardware, it went bad because of that nightly install.
hi.
i had same problem with wifi after experiments with CWM.
look into /persist folder on your device. have a WCNSS_qcom_wlan_nv.bin file?
when i restore this file my wi-fi began work normally.
sorry for poor english:cyclops:
mwg: said:
hi.
i had same problem with wifi after experiments with CWM.
look into /persist folder on your device. have a WCNSS_qcom_wlan_nv.bin file?
when i restore this file my wi-fi began work normally.
sorry for poor english:cyclops:
Click to expand...
Click to collapse
Any chance you could get me a clean copy of that file?
Also, what other files belong in that folder? Mine is empty.
here is 2 archives - my backup of /persist folder and /etc/firmware/wlan/prima (there some additional files and links to /persist)
hope it help you
mwg: said:
here is 2 archives - my backup of /persist folder and /etc/firmware/wlan/prima (there some additional files and links to /persist)
hope it help you
Click to expand...
Click to collapse
After you replaced those files, did you just reboot and it works, or did you have to clear /data - /cache - /dalvik? Any of thos combinations?
Thank you so much by the way for grabbing those files for me so quick!
Hello guys
Some time ago i flashed DotOS 2.5 with the according bootstack and oki's twrp,and used inbuild party zip to create vendor.
Before i did this,i was sitting on RDX rom 7.1 and i had no any complains.
When i wiped my partitions for setting up dotos,i also mounted persist partition.
After the flash installation of dotos was done,and booted in the system...my battery drops 20% in 3 minutes,and when i put it on charger, it charged 10% in like 4 seconds.
I complained about this in the schwifty group and on xda...and at this moment i still think its software related.
After searching and searching i cam acros a forum on xda that tells the work of any partition
ive read this:
PERSIST - contains data which shouldn't be changed after the device is shipped, e.g. DRM related files, sensor reg file (sns.reg) and calibration data of chips; wifi, bluetooth, camera etc.
Some package installers such as OpenGapps also make use of this partition to read configuration file.
I have the idea,because i mounted persist partition and allowed twrp to change system files....these calibration issues popped up on my device.
Now i want to try to put back stock persist partition....but is that possible? I dont have any backup,and also dont know how to replce this partition.
Is there somewehere a persist partition to download? Or maybe someone can share it that didnt touched ther persist partition?
Broken black screen - TWRP working but encrypted, & file transfer not enabled default
Hi all, novice here
OnePlus 5
OxygenOS (OnePlus5Oxygen_23_OTA_040_all_1811051816_c6670cf.zip) I think.
rooted
twrp-3.2.3-0-20180822-codeworkx-cheeseburger.img
I dropped my phone and I think a car ran over it. Screen is black and touchscreen not functional. At first the screen was fragmented and I could see parts of my home screen, but now it is totally black. So I think the phone itself is functional.
I can boot to TWRP and use ADB. I can navigate through the internal files system. I wish to copy the files to my PC. If I navigate to /sdcard, the folders have names like "wvTioi91z2FNnyelsUoraA" which I assume means they are encrypted. I can researched for 4 days and tried multiple methods. I have tried commands like mount, twrp decrypt 14789 for my lock pattern, to no avail.
I have tried a program called [email protected] to simulate touchscreen movements after booting to the system, but I'm flying blind.
I guess I want to know if this is all futile. I want to get my data off before I send it to OnePlus to get fixed because they will likely wipe it.
If I could somehow swipe down from the top when booted to the system and select MTP mode or whatever, I should be fine. But this is not working. Can I flash a different TWRP without losing data while removing encryption? I am not sure if I have USB debug mode on or off.
Any advice would be highly appreciated.
I had the same problem. But twrp decrypt <lockpattern> was the solution for me.
No idea why it do not work for you.
If you can get it into fastmode you could theoretically flash or just boot any recover you want without wiping anything.
Qnorsten said:
I had the same problem. But twrp decrypt <lockpattern> was the solution for me.
No idea why it do not work for you.
If you can get it into fastmode you could theoretically flash or just boot any recover you want without wiping anything.
Click to expand...
Click to collapse
Thanks. I think Android is having trouble matching the passwords.
Attempting to decrypt data partition via command line.
Iecrypting FBE for user 0
password filename is '/data/system/gatekeeper.pattern.key'
get_ce_key_directory_path 0: /data/misc/vold/user_keys/ce/0
Skipping non-key .Skipping non-key ..get_ce_key_paths adding: /data/misc/vold/user_keys/ce/0/current
Trying user CE key /data/misc/vold/user_keys/ce/0/currentOpenssl error: 0Failed to find working ce key for user 0Couldn't read key for 0e4crypt_unlock_user_key returned fail
I have another OnePlus 5 with Pie installed. After this error, I copied gatekeeper.pattern.key and then all of the contents in /data/system from my other OnePlus 5 to my broken OnePlus 5. It did not work.
I'm trying to make all of the encrypted passwords match somehow.
I have a Samsung Galaxy Tab 10.1" SM-P580 and started working to root it so I could install more apps using a micro SD card. It was a long time ago with Android 7 or so and a while back I thought I would upgrade so I tried upgrading it to Android 11 and Lineage 18.1 and bare bones Google apps. This has been only partially successfully as the system runs but I cannot install any apps at all and have been unable to make any further progress. So I am looking to go back to the drawing board here. What recommendations do you have with regard to what to use that will allow me to install more apps? Thank you very much!
JR1979 said:
I have a Samsung Galaxy Tab 10.1" SM-P580 and started working to root it so I could install more apps using a micro SD card. It was a long time ago with Android 7 or so and a while back I thought I would upgrade so I tried upgrading it to Android 11 and Lineage 18.1 and bare bones Google apps. This has been only partially successfully as the system runs but I cannot install any apps at all and have been unable to make any further progress. So I am looking to go back to the drawing board here. What recommendations do you have with regard to what to use that will allow me to install more apps? Thank you very much!
Click to expand...
Click to collapse
I assume you got the basic stuff out of the way - unlocked bootloader, installed TWRP, etc.
Did you install a Gapps package?
If you prefer something more vanilla, without the LineageOS customizations, you can try an Android GSI, which is like turning your device into a Pixel tablet. Check out my guide here.
JR1979 said:
I have a Samsung Galaxy Tab 10.1" SM-P580 and started working to root it so I could install more apps using a micro SD card. It was a long time ago with Android 7 or so and a while back I thought I would upgrade so I tried upgrading it to Android 11 and Lineage 18.1 and bare bones Google apps. This has been only partially successfully as the system runs but I cannot install any apps at all and have been unable to make any further progress. So I am looking to go back to the drawing board here. What recommendations do you have with regard to what to use that will allow me to install more apps? Thank you very much!
Click to expand...
Click to collapse
There are differences between Android 7,8,9 and now, especially eg.the use of sd-cards and permissions for users in general. Maybe you have to check such things as "Allow Installing apps from unknown ressources" in Settings, or you ckeck magisk modules that could help.
abagm said:
There are differences between Android 7,8,9 and now, especially eg.the use of sd-cards and permissions for users in general. Maybe you have to check such things as "Allow Installing apps from unknown ressources" in Settings, or you ckeck magisk modules that could help.
Click to expand...
Click to collapse
Thanks for the input. I have it upgraded to Android 11. Yhe unknown resources shouldn't matter AFAIK, in this case, as I am only trying to install via Play Store. I was trying to work with Magisk - I have it installed. I was going to try the ExSD module but I haven't been able to add it.
V0latyle said:
I assume you got the basic stuff out of the way - unlocked bootloader, installed TWRP, etc.
Did you install a Gapps package?
If you prefer something more vanilla, without the LineageOS customizations, you can try an Android GSI, which is like turning your device into a Pixel tablet. Check out my guide here.
Click to expand...
Click to collapse
Thank you. I will look into that. I will look into what the differences are between that and LineageOS. Question: will the pen/stylus work under this configuration? Thank you again.
JR1979 said:
Thank you. I will look into that. I will look into what the differences are between that and LineageOS. Question: will the pen/stylus work under this configuration? Thank you again.
Click to expand...
Click to collapse
In theory, yes - because GSIs are meant to be used with the stock kernel, and the system image doesn't have to have any specific hardware support.
LineageOS is built from AOSP, with added tweaks and customizations. I used it for a while, but grew tired of the Magisk issues I was having (PHH builds have built in SuperSU) so I just went straight vanilla with GMS.
So I looked at your guide and decided to give it a shot. With Multidisabler, when I tried pushing that to the tablet with sideload, it failed. I have also been unable to move system.img to the tablet. I'm at a loss. I know I am missing something here but just can't figure out what I am doing wrong. I just want to get this tablet up and running with Android and being able to use the 400GB SD card.
Thanks.
JR1979 said:
So I looked at your guide and decided to give it a shot. With Multidisabler, when I tried pushing that to the tablet with sideload, it failed. I have also been unable to move system.img to the tablet. I'm at a loss. I know I am missing something here but just can't figure out what I am doing wrong. I just want to get this tablet up and running with Android and being able to use the 400GB SD card.
Thanks.
Click to expand...
Click to collapse
Does MTP work for you in TWRP? ADB sideload is only for installing zips from your computer; the correct command to send files to device storage is adb push. Still, if you're able to get storage access over USB in TWRP just move the files that way because it's simpler.
I'm honestly not sure if the multidisabler is necessary when using custom firmware or GSIs. I think most likely not.
V0latyle said:
Does MTP work for you in TWRP? ADB sideload is only for installing zips from your computer; the correct command to send files to device storage is adb push. Still, if you're able to get storage access over USB in TWRP just move the files that way because it's simpler.
I'm honestly not sure if the multidisabler is necessary when using custom firmware or GSIs. I think most likely not.
Click to expand...
Click to collapse
Sorry - I just saw this response from you. So MTP is enabled but my laptop was unable to see the tablet. I connected the SD card to my laptop and placed the system.img file on it and then dropped the SD card back into the tablet. I was able to see it in the File Manager. As you said to, I wiped /system and flashed the system.img file. It showed "[IMAGE FLASH COMPLETED]". But when I went to reboot from the main TWRP menu, it said there was no OS installed and asked if I was sure if I wanted to reboot. So I took a gamble and selected Reboot and System again. And I guess I lost on the gamble. It now just loops on the "Samsung Galaxy Tab A with S Pen" splash screen. Well, game over... for tonight.
JR1979 said:
Sorry - I just saw this response from you. So MTP is enabled but my laptop was unable to see the tablet. I connected the SD card to my laptop and placed the system.img file on it and then dropped the SD card back into the tablet. I was able to see it in the File Manager. As you said to, I wiped /system and flashed the system.img file. It showed "[IMAGE FLASH COMPLETED]". But when I went to reboot from the main TWRP menu, it said there was no OS installed and asked if I was sure if I wanted to reboot. So I took a gamble and selected Reboot and System again. And I guess I lost on the gamble. It now just loops on the "Samsung Galaxy Tab A with S Pen" splash screen. Well, game over... for tonight.
Click to expand...
Click to collapse
Don't worry about the No OS warning, I get the same thing on my Tab A after installing a GSI.
You formatted data, yes?
You did NOT wipe /boot or /product I hope?
Something I noticed with the LineageOS GSIs is that the securized ones bootlooped, and I had to flash one of the pre-rooted builds. Can you link the image you tried to flash?
As a test to ensure a GSI runs properly, download one of the Android Developer Preview GSIs and try installing that. Let me know how it goes.
I didn't wipe /boot or /product.
I did format data.
I used the system.img from the aosp_arm64-exp-T2B2.221216.006-9443277-e508d63f.zip file on this page, from the Android Developer Preview GSIs: https://developer.android.com/topic/generic-system-image/releases
I'm guessing I didn't select the right build ?
Thanks again!
JR1979 said:
I didn't wipe /boot or /product.
I did format data.
I used the system.img from the aosp_arm64-exp-T2B2.221216.006-9443277-e508d63f.zip file on this page, from the Android Developer Preview GSIs: https://developer.android.com/topic/generic-system-image/releases
I'm guessing I didn't select the right build ?
Thanks again!
Click to expand...
Click to collapse
I also just tried the system.img from gsi_gms_arm64-exp-T2B2.221216.006-9443277-12a8e193.zip file. I get the same results - the splash screen loop.
JR1979 said:
I also just tried the system.img from gsi_gms_arm64-exp-T2B2.221216.006-9443277-12a8e193.zip file. I get the same results - the splash screen loop.
Click to expand...
Click to collapse
And so I tried the system.img files from the 2 zip files that are in the Android 13 (stable) folder:
aosp_arm64-exp-TP1A.220624.014-8819323-996da050.zip
gsi_gms_arm64-exp-TP1A.220624.014-8819323-8a77fef1.zip
Neither of these work. I still get the splash screen boot loop.
One thing I noticed is when I wipe system, it shows:
========================================
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Failed to mount '/system_root' (Invalid argument)
Formatting system using mke2fs...
Done.
Updating partition details...
...done
=========================================
It's almost tablet frisbee time.