Related
Hello, I've followed the official build instructions (sorry, I'm not allowed to post any links) to build AOSP Oreo 8.1 for my XA2 Ultra (H2313_userdata/discovery/android-8.1.0_r35 branch). I set up my own Docker container to build the sources, which successfully finished after about 2 hours. After flashing the boot.img, system.img, vendor.img, userdata.img and SW_binaries_for_Xperia_Android_8.1.6.4_r1_v14_nile.img with fastboot (without any errors) I'm not able to boot the phone. I'm stuck at the white screen with the black Sony logo on it. It is also not possible to connect the phone to an adb logcat. I am able to re-enter the fastboot mode and can boot to AOSP recovery, which is quite useless I think. I flashed the images multiple times but that didn't help. The bootloader is unlocked. I could verify that with the service menu (*#*#7378423#*#*) few steps earlier. I also downloaded the Android sources again and successfully built it again. If that's of interest I had problems with the up to date version of the android-tools (fastboot) so I used version 6.0.1_p79 from my Gentoo repositories.
What should be my next steps?
PS: I wasn't able to build android-9.0.0_r1 but the the vendors software binaries for AOSP Pie (Android 9.0) aren't available anyways. Right now I'm trying to build AOSP Oreo 8.04
PPS: Linux is fine. If Windows is needed, that would be rather bad.
EDIT: Whether builds for aosp_h3213-userdebug nor aosp_h3213-eng are able to boot.
For some reason I had to flash Oreo 8.0 with the Sony Flashtool (Emma). After flashing my userdebug builds with fastboot again it is now working and booting AOSP. Huuray! Thanks anyway
You need to flash the latest oem image
Phone: OnePlus 7 Pro
Build number: Oxygen OS 10.0.3 GM21BA
Anndroid Version: 10
Model: GM1913
Hi all,
I received yesterday my Oneplus 7 Pro. My objective is to install nethunter fully rooted.
After looking the requirements in the offensive security website i noticed i need 3 things
TWRP
Magisk
DM-Verify
I started with TWRP watching different tutorials and comparing them but they are similar.
- Installed sdk platform tools and Minimal adb/fastboot ( tried both ways )
-unlocked the bootloader and enabled usb debug mode.
- Once i do " fastboot boot twrp.img " everything seems " okay " in the terminal, but the phone becomes stuck in fastboot mode logo image, it never actually boots into the twrp.
In a different tutorial, i replaced the "fastboot boot twrp.img" with " fastboot flash boot twrp.img ". This broke my phone i couldn't start the android or go the recovery mode, i couldn't leave fastboot mode unless to restart or to turn off the phone. I fixed this by " fastboot flash boot boot.img " that i had available in the platform tools folder.
I tried different twrp images:
TWRP 3.3.1-74 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-70 Unified Unofficial Pie by mauronofrio
twrp-3.3.1-4-guacamole.img
Nothing seems to work, i don't know what else to try or what am i doing wrong.
I've been 8 hours around this so any help would be deeply appreciated.
Kind regards,
C666PO said:
Phone: OnePlus 7 Pro
Build number: Oxygen OS 10.0.3 GM21BA
Anndroid Version: 10
Model: GM1913
Hi all,
I received yesterday my Oneplus 7 Pro. My objective is to install nethunter fully rooted.
After looking the requirements in the offensive security website i noticed i need 3 things
TWRP
Magisk
DM-Verify
I started with TWRP watching different tutorials and comparing them but they are similar.
- Installed sdk platform tools and Minimal adb/fastboot ( tried both ways )
-unlocked the bootloader and enabled usb debug mode.
- Once i do " fastboot boot twrp.img " everything seems " okay " in the terminal, but the phone becomes stuck in fastboot mode logo image, it never actually boots into the twrp.
In a different tutorial, i replaced the "fastboot boot twrp.img" with " fastboot flash boot twrp.img ". This broke my phone i couldn't start the android or go the recovery mode, i couldn't leave fastboot mode unless to restart or to turn off the phone. I fixed this by " fastboot flash boot boot.img " that i had available in the platform tools folder.
I tried different twrp images:
TWRP 3.3.1-74 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-70 Unified Unofficial Pie by mauronofrio
twrp-3.3.1-4-guacamole.img
Nothing seems to work, i don't know what else to try or what am i doing wrong.
I've been 8 hours around this so any help would be deeply appreciated.
Kind regards,
Click to expand...
Click to collapse
I have an almost identical problem to you.
except: my device is GM1910, I had a stock hydrogen OS, which has been converted to oxygen OS.
so far, I have tried twrp-3.3.1-0, 3.3.1-2, 3.3.1-3, 3.3.1-4, on oxygen OS version 10.0.2.GM21AA, 10.0.3.GM21AA, and 10.3.0.GM21AA, all would stuck at the fastboot mode logo screen
Rolling back to a lower version of oxygen OS, including version 9.5.1 and 9.5.7 causes my OP7P in bootloader mode no longer recognized by "fastboot devices", or even by "dmseg" as a usb device.
I received a suggestion of trying the latest TWRP 3.3.1-74 build, which I intend to try later tonight, but got not so optimistic about, seeing that you've experimented with TWRP 3.3.1-74 Unified Unofficial Pie by mauronofrio
One observation I do like to make, is that android 9 is considered as Pie while android 10 was developed from android Q.
since your device is already android 10 at version 10.0.3, should you still use the Pie TWRP build?
OblixioN said:
One observation I do like to make, is that android 9 is considered as Pie while android 10 was developed from android Q.
since your device is already android 10 at version 10.0.3, should you still use the Pie TWRP build?
Click to expand...
Click to collapse
Hi OblixioN,
I tried the image with the Q at the end: TWRP 3.3.1-74 Unified Unofficial Q by mauronofrio and it worked. I had no idea what the Q or Pie meant so your information just solved my problem. I assume it will work for you.
Huge thanks!
Thanks - worked for me as well!
Unfortunately I formated before getting to this solution, so rather unnecessary for me, but what I did was getting the unofficial twrp for guacamole here:
h-t-t-p-s://androidfilehost.com/?fid=4349826312261707787
(from this post: https://forum.xda-developers.com/oneplus-7-pro/development/recovery-unofficial-twrp-recovery-t3931322)
Then I booted to fastboot at ran
Code:
fastboot set_active a
fastboot boot .\twrp-3.3.1-75-guacamole-unified-Q-mauronofrio.img
fastboot set_active b
fastboot boot .\twrp-3.3.1-75-guacamole-unified-Q-mauronofrio.img
Now I could boot into twrp, it found all the internal data storage, and I could sideload
Code:
adb sideload .\twrp-installer-3.3.1-4-guacamole.zip
adb sideload .\Magisk-v20.3.zip
C666PO said:
I had no idea what the Q or Pie meant so your information just solved my problem.
Click to expand...
Click to collapse
It means if you are on Android Q, you need to use the TWRP version that supports Android Q.
Hey, I seem to have the same problem but how do u get it unstuck from the Fastboot Mode so I can try another version of TWRP?
OrionGiant said:
Hey, I seem to have the same problem but how do u get it unstuck from the Fastboot Mode so I can try another version of TWRP?
Click to expand...
Click to collapse
hey there.
So, first of, You restart it by pressing and holding volume up, down and power at the same time for 10+ seconds.
And second, try updating Oxygen OS to its latest version. It works for me now, just unpacked a new OnePlus 7 Pro, didn't work on Android 9, works on Android 10 latest update.
OrionGiant said:
Hey, I seem to have the same problem but how do u get it unstuck from the Fastboot Mode so I can try another version of TWRP?
Click to expand...
Click to collapse
While in fastboot , " fastboot boot twrp.img
Hi!
I'm on the latest official OxygenOS 11 and am having the exact same issue you hade above.
Tried everything mentioned above and the phone is still boot looping :'(
Any more tips?
SABMAN said:
Hi!
I'm on the latest official OxygenOS 11 and am having the exact same issue you hade above.
Tried everything mentioned above and the phone is still boot looping :'(
Any more tips?
Click to expand...
Click to collapse
I tried installing a new kernal and after that mine would go directly to bootloader, no matter what I did it went directly to bootload, thankfully fastboot was still active but using boot cmd into anything would fail,, ,I started my msm tool, and rebooted into edl and as soon as a com port became active on the MSM panel I hit start, and it took off running and did it's thing,
I think my issue had two reasons!
1. The boot.img file i used was from the earlier Oxygen update not the version i had just installed.
2. The phone encryption (but i doubt this!)
Anyway since nothing helped i erased the phone and restored it Now it's working again!
Hello folks.
In my months-long quest to avoid turning an ASUS TF201 tablet into e-waste ...
I've searched, searched again, searched some more, and while I've found answers (none of which have worked), a lot of them seem to be dated, or depend on files that are no longer available for download, so I turn to you for suggestions.
Current state:
The tablet will not boot Android.
TWRP works fine.
The problem(s):
I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails.
I have tried Chrombi-KK, following the directions step by step, but a few strange things occur:
1. When flashing through TWRP (.zip images sitting on an SD card), everything completes with no errors, but on reboot, the tablet displays its ASUS logo, but does not boot into Android. I let it sit there for three hours today, and it just sat there, displaying the logo.
2. When trying to flash from ADB (TWRP update for example), it sits there endlessly at "< waiting for any device >". This is odd, because ADB's "reboot" commands works fine.
Now, I'm at a loss. The hardware seems fine, but I'm stuck ... and this is after months of trying, giving up, trying again etc.
Is this a lost cause?
Any help at all would be much appreciated. I've tried so many things, so many online "solutions," to no avail. So I turn to the experts as my Hail Mary pass before sending this to the eco centre.
Thanks for reading, and hopefully ... just maybe ... someone will have the magical set of instructions to get this thing working again.
The only command to verify whether an ADB / Fastboot connection got successfully established is
Code:
adb devices OR fastboot devices
The command
Code:
adb reboot
simply in Android's system file called build.prop (re-)sets flag ro.bootmode to normal what is read by bootloader when Android boots up.
jwoegerbauer said:
The only command to verify whether an ADB / Fastboot connection got successfully established is
Code:
adb devices OR fastboot devices
The command
Code:
adb reboot
simply in Android's system file called build.prop (re-)sets flag ro.bootmode to normal what is read by bootloader when Android boots up.
Click to expand...
Click to collapse
As it turns out, I had already stumbled upon your your "ADB-FASTBOOT-Installer" during a trip down one of the many rabbit holes trying to get this tablet working again.
adb devices returns:
List of devices attached0123456789ABCDEF recovery
adb reboot restarts the tablet, which I assume means the ASUS tablet driver is working.
I can't seem to do anything else with adb, however, such as push a new TWRP version, etc. This may be a key point, as it seems likely the version I have of TWRP may be too old to support upgrade using something like Chrombi-KK.
Is this a likely theory?
I would re-flash phone's Stock ROM to get rid off of all mofications applied so far to check for phone is working as expected.
NotTheLips said:
Hello folks.
In my months-long quest to avoid turning an ASUS TF201 tablet into e-waste ...
I've searched, searched again, searched some more, and while I've found answers (none of which have worked), a lot of them seem to be dated, or depend on files that are no longer available for download, so I turn to you for suggestions.
Current state:
The tablet will not boot Android.
TWRP works fine.
The problem(s):
I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails.
I have tried Chrombi-KK, following the directions step by step, but a few strange things occur:
1. When flashing through TWRP (.zip images sitting on an SD card), everything completes with no errors, but on reboot, the tablet displays its ASUS logo, but does not boot into Android. I let it sit there for three hours today, and it just sat there, displaying the logo.
2. When trying to flash from ADB (TWRP update for example), it sits there endlessly at "< waiting for any device >". This is odd, because ADB's "reboot" commands works fine.
Now, I'm at a loss. The hardware seems fine, but I'm stuck ... and this is after months of trying, giving up, trying again etc.
Is this a lost cause?
Any help at all would be much appreciated. I've tried so many things, so many online "solutions," to no avail. So I turn to the experts as my Hail Mary pass before sending this to the eco centre.
Thanks for reading, and hopefully ... just maybe ... someone will have the magical set of instructions to get this thing working again.
Click to expand...
Click to collapse
ok, so good thing is twrp boots, now again if you have box with wich the tablet come try to get correct model number and search for official frimware to flash through adb using flashall.cmd
again, if official rom is not installing don't worry flash THIS custom rom using TWRP make sure to wipe all before flashing.
jwoegerbauer said:
I would re-flash phone's Stock ROM to get rid off of all mofications applied so far to check for phone is working as expected.
Click to expand...
Click to collapse
As I mentioned: "I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails."
This is exactly what I'm trying to find a solution on how to do.
[email protected] said:
ok, so good thing is twrp boots, now again if you have box with wich the tablet come try to get correct model number and search for official frimware to flash through adb using flashall.cmd
again, if official rom is not installing don't worry flash THIS custom rom using TWRP make sure to wipe all before flashing.
Click to expand...
Click to collapse
Yes, thank goodness it's not completely bricked, haha.
I think the version of TWRP that's on there may be too old, and I'm having trouble pushing a newer version through ADB ... so this is the current hurdle I'm trying to overcome.
Might you happen to have a link to the ASUS TF201 drivers known to work in Windows 10, so I can rule that out? If I can't get ADB to push a newer TWRP version from Windows, I may give it a go in Linux too ... but I'm trying not to open up new avenues of complexity, so I've restricted all my efforts to Windows as that's where most of the online help I can find tends to take place.
Thanks!
Edit: Unfortunately, the download link to [ROM][N 7.1] KatKiss Nougat [TF201] no longer works:
404 Not Found
This has been another constant obstacle, i.e., recommended files to download are no longer available.
NotTheLips said:
As I mentioned: "I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails."
This is exactly what I'm trying to find a solution on how to do.
Click to expand...
Click to collapse
Nobody needs TWRP to re-flash a device's Stock ROM.
It's typically done via ADB Sideload method.
NotTheLips said:
Yes, thank goodness it's not completely bricked, haha.
I think the version of TWRP that's on there may be too old, and I'm having trouble pushing a newer version through ADB ... so this is the current hurdle I'm trying to overcome.
Might you happen to have a link to the ASUS TF201 drivers known to work in Windows 10, so I can rule that out? If I can't get ADB to push a newer TWRP version from Windows, I may give it a go in Linux too ... but I'm trying not to open up new avenues of complexity, so I've restricted all my efforts to Windows as that's where most of the online help I can find tends to take place.
Thanks!
Edit: Unfortunately, the download link to [ROM][N 7.1] KatKiss Nougat [TF201] no longer works:
404 Not Found
This has been another constant obstacle, i.e., recommended files to download are no longer available.
Click to expand...
Click to collapse
how you tried to flash stock rom, i mean do you boot into fastboot after booting into twrp or not?
jwoegerbauer said:
Nobody needs TWRP to re-flash a device's Stock ROM.
It's typically done via ADB Sideload method.
Click to expand...
Click to collapse
As I mentioned before, "2. When trying to flash from ADB (TWRP update for example), it sits there endlessly at "< waiting for any device >". This is odd, because ADB's "reboot" commands works fine."
[email protected] said:
how you tried to flash stock rom, i mean do you boot into fastboot after booting into twrp or not?
Click to expand...
Click to collapse
I've tried two methods.
The first is to try to flash it from TWRP, but this fails with an error. The stock ROM appears to be checking for dependencies, and it fails this check.
The second is to use ADB (fastboot) while the tablet is sitting in TRWP. It stalls at "< waiting for any device >".
So this the problem. Neither of those two methods work for the stock ROM.
With a third party ROM, TWRP appears to flash the device successfully (no errors or stalls). When I reboot the device, it will not boot Android, and gets stuck at the ASUS boot logo indefinitely.
I'm not sure what do next to get past these two problems.
NotTheLips said:
I've tried two methods.
The first is to try to flash it from TWRP, but this fails with an error. The stock ROM appears to be checking for dependencies, and it fails this check.
The second is to use ADB (fastboot) while the tablet is sitting in TRWP. It stalls at "< waiting for any device >".
So this the problem. Neither of those two methods work for the stock ROM.
With a third party ROM, TWRP appears to flash the device successfully (no errors or stalls). When I reboot the device, it will not boot Android, and gets stuck at the ASUS boot logo indefinitely.
I'm not sure what do next to get past these two problems.
Click to expand...
Click to collapse
here is the problem, ok so follow the steps carefully,
boot into twrp
then connect your phone to your pc
type "adb devices",
if some thing like 1234567890 -recovery shows up proceed else start-over,
after successfully detected by adb typed "adb reboot bootloader"
then after booting into fastboot mode type "fastboot device"
if something shows up proceed else tell me
make sure you have installed adb and fastboot properly,
after all this run the cmd file in stock rom, to automatically flash it.
[email protected] said:
here is the problem, ok so follow the steps carefully,
boot into twrp
then connect your phone to your pc
type "adb devices",
if some thing like 1234567890 -recovery shows up proceed else start-over,
after successfully detected by adb typed "adb reboot bootloader"
then after booting into fastboot mode type "fastboot device"
if something shows up proceed else tell me
make sure you have installed adb and fastboot properly,
after all this run the cmd file in stock rom, to automatically flash it.
Click to expand...
Click to collapse
Here's what happened:
C:\Windows\system32>adb devicesList of devices attached0123456789ABCDEF recoveryC:\Windows\system32>adb reboot bootloaderC:\Windows\system32>fastboot device< waiting for any device >It sits at < waiting for any device > indefinitely, until I reboot the device.
NotTheLips said:
Here's what happened:
C:\Windows\system32>adb devicesList of devices attached0123456789ABCDEF recoveryC:\Windows\system32>adb reboot bootloaderC:\Windows\system32>fastboot device< waiting for any device >It sits at < waiting for any device > indefinitely, until I reboot the device.
Click to expand...
Click to collapse
the problem is your pc does not have adb and fastboot properly installed
try this one https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
also, use this official driver https://www.asus.com/SupportOnly/Eee_Pad_Transformer_Prime_TF201/HelpDesk_Download/
if your pc is 64 bit use win764bit version
NotTheLips said:
Here's what happened:
C:\Windows\system32>adb devicesList of devices attached0123456789ABCDEF recoveryC:\Windows\system32>adb reboot bootloaderC:\Windows\system32>fastboot device< waiting for any device >It sits at < waiting for any device > indefinitely, until I reboot the device.
Click to expand...
Click to collapse
This "waiting for device" problem happens when the USB device node is not accessible to your current user. The USB id is different in Fastboot mode, so you can easily have permission to it in ADB but not in Fastboot.
Each manufacturer implements Fastboot differently. So, if not already done yet, download and install the suitable "Android USB Driver" provided by ASUS. Then Fastboot should work.
BTW: Your device actually stucks in recovery mode.
Is OEM Unlock got enabled in Android settings? If not, Fastboot never will work.
Ive tried installing the DSU by phone through developer options and when i restart the phone it just says DSU ready restart phone. Ive tried the adb way and got it to download and restarted my phone now there was no notification at all but the DSU was still not installed. Can anyone explain to me what im doing wrong.
ThatNiggaDurk666 said:
Ive tried installing the DSU by phone through developer options and when i restart the phone it just says DSU ready restart phone. Ive tried the adb way and got it to download and restarted my phone now there was no notification at all but the DSU was still not installed. Can anyone explain to me what im doing wrong.
Click to expand...
Click to collapse
I figured this out today...
Unlock your bootloader and use stock boot image(no magisk)
official aosp gsi(from dsu loader ui) and phh based gsis(with commands from official dsu page) work best.
Also check settings_dynamic_system option to true under feature flags within developer settings(on userdebug ROM) or do the setprop command found on androids official dsu page.
another note about the commands from official dsu page, the provided du command in android system may not support the -b flag, i ended up using "wc -c" to get byte size of system_raw.img in place of "du -b".
make sure your not using any sparse system images, convert those with simg2img, I also rename the gsi from lineage-19-x-x.img to system_raw.img then gzip -c system_raw.img >system_raw.gz make sure the system file name matches what is in the adb install commands, and the image name getting gzipped.
it is possible to run the commands from dsu page within rooted android device(i use adb root since magisk patched boot image only boots the host sustem with new userdata_gsi image)
mrbox23 said:
I figured this out today...
Unlock your bootloader and use stock boot image(no magisk)
official aosp gsi(from dsu loader ui) and phh based gsis(with commands from official dsu page) work best.
Also check settings_dynamic_system option to true under feature flags within developer settings(on userdebug ROM) or do the setprop command found on androids official dsu page.
another note about the commands from official dsu page, the provided du command in android system may not support the -b flag, i ended up using "wc -c" to get byte size of system_raw.img in place of "du -b".
make sure your not using any sparse system images, convert those with simg2img, I also rename the gsi from lineage-19-x-x.img to system_raw.img then gzip -c system_raw.img >system_raw.gz make sure the system file name matches what is in the adb install commands, and the image name getting gzipped.
it is possible to run the commands from dsu page within rooted android device(i use adb root since magisk patched boot image only boots the host sustem with nei just got the 1+ nord n200 5g ive tried everything including msm download tool my problem is when holding volume up and volume down and power it brings up fastboot mode but the moment i let one go it goes off and brings back the corrupt error and then same thign if you try to just hold it and i think its cause my pc to not register the phone is connected please someone help im lost at this point
Click to expand...
Click to collapse
i just got the 1+ nord n200 5g ive tried the dsu loader and it brick my device ive tried everything i could including msm download tool my problem is when holding volume up and volume down and power it brings up fastboot mode but the moment i let one go it goes off and brings back the corrupt error and then same thign if you try to just hold it and i think its cause my pc to not register the phone is connected please someone help im lost at this point
ThatNiggaDurk666 said:
i just got the 1+ nord n200 5g ive tried the dsu loader and it brick my device ive tried everything i could including msm download tool my problem is when holding volume up and volume down and power it brings up fastboot mode but the moment i let one go it goes off and brings back the corrupt error and then same thign if you try to just hold it and i think its cause my pc to not register the phone is connected please someone help im lost at this point
Click to expand...
Click to collapse
theres no screen for edl mode. launch msm tool, click start, connect phone, as soon as it finds device, it starts. make sure you have qualcom drivers
Xperia 5 J8210
Hi there, so as a newbie, I've got myself into a right mess!
I wanted to enable Ethernet over USB but Android 9 that came with the phone doesn't support. I couldn't immediately see any standard custom roms (should have looked harder!) so I unlocked the boatloader, compiled AOSP from scratch following the instructions on developer.sony.com. Flashed the resulting images across and it resulted in the phone not booting. I've managed to install TWRP but I'm unable to install any custom ROMs such as Lineage and PixelOS. When I go to install in TWRP it always immediately fails with "Error installing zip file '....unofficial.zip'. When I put TWRP into ADB mode and use adb sideload the transfer fails immediately.
This seems to be the same for any zip file I care to install. Any suggestions, I've a feeling something underlying is wrong, not least the opening statement on the custom rims along the lines of "Make sure you come from Official Android 11.0 from Sony".
Oh boy... help would be most appreciated.
Many thanks.
Do you use an SD card? There seems to be an issue with transferring files through MTP (at least on my device), whether it's from the system or the recovery, that renders seemingly good files unusable for flashing.
If you have an SD card or your phone supports USB OTG, I would suggest transferring the file from your PC to the external storage, then plugging it into the phone and flashing from there.
Thanks. I think there is something more fundamental: if I follow the instructions here to install PixelOS based on Android 11:
[ROM][11][UNOFFICIAL] PixelExperience 11 for Sony Xperia 5[AOSP]
PixelExperience 11 for Sony Xperia 5 [Bahamut] What is this? PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation) Our mission is to offer the maximum possible...
forum.xda-developers.com
I can't even get the recovery to work, it just says your device is corrupted it can't be trusted and will not boot. To get to this stage, I:
1. Downloaded software binaries for AOSP Android 11.9 - Kernel 4.14 Kumano
2. Installed in fastboot via fastboot flash oem_a SW_binaries...._kumano.img and fastboot flash oem_b SW_binaries...._kumano.img
3. Dowloaded and extracted pe-recovery.zip and PixelExperience_bahamut-11.0-20211229-1823-UNOFFICIAL.zip
4. Extracted pe_recovery and installed in fastboot via:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash --disable-verity --disable-verfication flash vbmeta vbmeta.img
Unplugged USB booted into recovery mode via power and volume down only to briefly see Sony logo and then corruption message.
Given I can't get this to work, can you suggest any other things I need to do to at least get the PixelOS custom recovery to work?
Many thanks.
SoundAdikt said:
Thanks. I think there is something more fundamental: if I follow the instructions here to install PixelOS based on Android 11:
[ROM][11][UNOFFICIAL] PixelExperience 11 for Sony Xperia 5[AOSP]
PixelExperience 11 for Sony Xperia 5 [Bahamut] What is this? PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation) Our mission is to offer the maximum possible...
forum.xda-developers.com
I can't even get the recovery to work, it just says your device is corrupted it can't be trusted and will not boot. To get to this stage, I:
1. Downloaded software binaries for AOSP Android 11.9 - Kernel 4.14 Kumano
2. Installed in fastboot via fastboot flash oem_a SW_binaries...._kumano.img and fastboot flash oem_b SW_binaries...._kumano.img
3. Dowloaded and extracted pe-recovery.zip and PixelExperience_bahamut-11.0-20211229-1823-UNOFFICIAL.zip
4. Extracted pe_recovery and installed in fastboot via:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash --disable-verity --disable-verfication flash vbmeta vbmeta.img
Unplugged USB booted into recovery mode via power and volume down only to briefly see Sony logo and then corruption message.
Given I can't get this to work, can you suggest any other things I need to do to at least get the PixelOS custom recovery to work?
Many thanks.
Click to expand...
Click to collapse
why are you using sony binaries for that rom?
didn't you read the instructions?