CODES;
I am NOT responsible for bricked devices, destroyed SD cards or any
damage that may happen to your device.
Requirements;
Unlocked bootloader
WARNING;Don't use nippon gsi they aren't working,I recommend using phh gsi by phusson lineage os by Andyyan and PE 12 by ponces
INSTRUCTIONS;
Power + volume down button
fastboot reboot fastboot
fastboot delete-logical-partition product
fastboot flash system (name gsi.img)
fastboot reboot recovery
in recovery select wipe data
Reboot to system
bugs:
No bugs
Pixel Experience Plus 12.1 v413.1;
Release Pixel Experience 12.1 v414 · ponces/treble_build_pe
Sync with June sources of PE Sync with AOSP 12.1 v414 (thanks @phhusson)
github.com
If brightness slider is broken:
Go to phh treble settings,misc settings enable "use alternative brightness scale", "use linear screen brightness slider" and "allow setting brightness to the lowest possible",reboot the device
Id bluetooth audio is broken:
Go to phh treble settings,misc settings, "Force enable a2dp off-load" and "Bluetooth workarounds" select mediatek option and reboot the device
ENJOY
Reserved
didnt work, followed all the steps, got a dm-verity corruption error
tried disabling vbmeta after erasing the system partition / before flashing the gsi using stock miui's vbmeta image
didnt work as well, got stuck on a bootloop
@zuhaibsarwar The [Development] prefix is only for threads created to share one's own development. Since this isn't the case for this thread, I've changed the prefix to [How To Guide] which is more appropriate for this thread.
Regards,
shadowstep
Forum Moderator
Did it worked for anyone
muhsin_Sultan said:
didnt work, followed all the steps, got a dm-verity corruption error
tried disabling vbmeta after erasing the system partition / before flashing the gsi using stock miui's vbmeta image
didnt work as well, got stuck on a bootloop
Click to expand...
Click to collapse
muhsin_Sultan said:
didnt work, followed all the steps, got a dm-verity corruption error
tried disabling vbmeta after erasing the system partition / before flashing the gsi using stock miui's vbmeta image
didnt work as well, got stuck on a bootloop
Click to expand...
Click to collapse
skip this line ( fastboot erase system ) and try
What's the performance is like in gsi
muneeb rizwan said:
What's the performance is like in gsi
Click to expand...
Click to collapse
I haven't tested this GSI 100%
muneeb rizwan said:
Did it worked for anyone
Click to expand...
Click to collapse
For me it's works before 4 weeks
zuhaibsarwar said:
For me it's works before 4 weeks
Click to expand...
Click to collapse
what do you mean by before 4 weeks
and other than performance is it stable
muneeb rizwan said:
and other than performance is it stable
Click to expand...
Click to collapse
Yeah it's stable
muneeb rizwan said:
what do you mean by before 4 weeks
Click to expand...
Click to collapse
what do you mean by this
muneeb rizwan said:
what do you mean by this
Click to expand...
Click to collapse
This GSI is used for 2 days only before 4 week's
zuhaibsarwar said:
This GSI is used for 2 days only before 4 week's
Click to expand...
Click to collapse
any other gsi you tried
muneeb rizwan said:
any other gsi you tried
Click to expand...
Click to collapse
Nippon gsi but failed . Since I hard brick my device before now i stopped installing GSI
Mi service center replaced box packed Redmi note 11 pro against old hard brick Redmi note 11 pro . So i stop testing stuff
zuhaibsarwar said:
Mi service center replaced box packed Redmi note 11 pro against old hard brick Redmi note 11 pro . So i stop testing stuff
Click to expand...
Click to collapse
can you tell me ho you hard bricked it
muneeb rizwan said:
can you tell me ho you hard bricked it
Click to expand...
Click to collapse
You wanna hard brick your device too ?
After enjoying GSI. Install originally firmware while installing original firmware interrupt the flashing while removing the usb data and restart the mobile phone by pressing volume up + volume down and power at same time
muhsin_Sultan said:
didnt work, followed all the steps, got a dm-verity corruption error
tried disabling vbmeta after erasing the system partition / before flashing the gsi using stock miui's vbmeta image
did
Click to expand...
Click to collapse
it works for me without no errors
C:\Users\HACKER\Desktop\platform-tools_r33.0.2-windows\platform-tools>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.005s]
< waiting for any device >
Finished. Total time: 31.417s
C:\Users\HACKER\Desktop\platform-tools_r33.0.2-windows\platform-tools>fastboot delete-logical-partition product
Deleting 'product' OKAY [ 0.034s]
Finished. Total time: 0.047s
C:\Users\HACKER\Desktop\platform-tools_r33.0.2-windows\platform-tools>fastboot flash system C:\Users\HACKER\Desktop\PixelExperience_Plus_arm64-ab-12.1-20220613-UNOFFICIAL.img_2
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.011s]
Sending sparse 'system_a' 1/14 (262108 KB) OKAY [ 23.304s]
Writing 'system_a' OKAY [ 1.305s]
Sending sparse 'system_a' 2/14 (262120 KB) OKAY [ 20.560s]
Writing 'system_a' OKAY [ 1.192s]
Sending sparse 'system_a' 3/14 (262112 KB) OKAY [ 19.624s]
Writing 'system_a' OKAY [ 1.106s]
Sending sparse 'system_a' 4/14 (262116 KB) OKAY [ 19.489s]
Writing 'system_a' OKAY [ 1.209s]
Sending sparse 'system_a' 5/14 (262128 KB) OKAY [ 19.921s]
Writing 'system_a' OKAY [ 1.176s]
Sending sparse 'system_a' 6/14 (262124 KB) OKAY [ 22.930s]
Writing 'system_a' OKAY [ 1.213s]
Sending sparse 'system_a' 7/14 (262124 KB) OKAY [ 20.192s]
Writing 'system_a' OKAY [ 1.192s]
Sending sparse 'system_a' 8/14 (262124 KB) OKAY [ 20.209s]
Writing 'system_a' OKAY [ 1.140s]
Sending sparse 'system_a' 9/14 (262124 KB) OKAY [ 20.017s]
Writing 'system_a' OKAY [ 1.168s]
Sending sparse 'system_a' 10/14 (262124 KB) OKAY [ 19.848s]
Writing 'system_a' OKAY [ 1.206s]
Sending sparse 'system_a' 11/14 (262120 KB) OKAY [ 20.352s]
Writing 'system_a' OKAY [ 1.207s]
Sending sparse 'system_a' 12/14 (262084 KB) OKAY [ 19.608s]
Writing 'system_a' OKAY [ 1.203s]
Sending sparse 'system_a' 13/14 (262128 KB) OKAY [ 20.083s]
Writing 'system_a' OKAY [ 1.185s]
Sending sparse 'system_a' 14/14 (201896 KB) OKAY [ 15.774s]
Writing 'system_a' OKAY [ 1.071s]
Finished. Total time: 411.459s
C:\Users\HACKER\Desktop\platform-tools_r33.0.2-windows\platform-tools>fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.082s
Related
The new update is allegedly out. But for me there is no update.
Has anyone a zip or some infos about it?
It's out only for preview program members.
I don't read too well
Out now for everyone now, currently updating now
out now but wont update, just loops for me
ricflairandy said:
out now but wont update, just loops for me
Click to expand...
Click to collapse
Same here, downloads the update, reboots, says its installing, doesn't finish, reboot, back to square one prompting to install.
So happy that it's not just me. I am also having the issue do you think the problem is with the rooted ROMs
jonsharky said:
So happy that it's not just me. I am also having the issue do you think the problem is with the rooted ROMs
Click to expand...
Click to collapse
I don't think so... Just restored with latest factory image, wiping everything and still doesn't work! I have a 2015 16GB model.
On the official shield forums it's been confirmed that the ota update won't work for rooted devices. The flash will be up on developer.nvidia.com in about a week.
JohnRossJennings said:
On the official shield forums it's been confirmed that the ota update won't work for rooted devices. The flash will be up on developer.nvidia.com in about a week.
Click to expand...
Click to collapse
My shield isn't rooted but im getting the same looping problem. I noticed recently though that on boot up my shield says the device is corrupt etc etc as though it has been rooted, but I've not modified anything.maybe this looping update caused that?
Will I need to wait and try and flash a factory image when it comes out?
Sent from my Pixel C using Tapatalk
You can NOT use OTA Updates if you are rooted. END!
The only way back is to factory reset the Shield. In the case of the Pro. This usually means a 2h wait.
Perhaps a quick reset might be enough? Though I have never attempted it before. But simply restoring a Recovery Image won't overwrite the /system Partition, clearing out the remnants of root. Thus allowing you to then update.
adam_purkis said:
My shield isn't rooted but im getting the same looping problem. I noticed recently though that on boot up my shield says the device is corrupt etc etc as though it has been rooted, but I've not modified anything.maybe this looping update caused that?
Will I need to wait and try and flash a factory image when it comes out?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Hi , i am new , having 2015 model
i getting a boot looping when updating and now stay at Nvida Logo page , can you or members here help me how to flash back 5.1 ?
sorry to trouble you.
thank you
Also, the update will definitely not take with TWRP. Looks like I have to wait until the developer release.
chow9229 said:
Hi , i am new , having 2015 model
i getting a boot looping when updating and now stay at Nvida Logo page , can you or members here help me how to flash back 5.1 ?
sorry to trouble you.
thank you
Click to expand...
Click to collapse
Hi, sorry can't give you detailed instructions right now. You'll find the info but a word of advice: Flash manually command by command in fastboot, DO NOT use the flash-all.bat and if you had 5.1 previously then there is no need to flash the bootloader (blob file). You need to be careful with that file, most hard bricks are caused by corrupted bootloader. Pay attention when downloading the Nvidia recovery image, make sure you get the one for your specific device model.
Cheers.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
lavero.burgos said:
Hi, sorry can't give you detailed instructions right now. You'll find the info but a word of advice: Flash manually command by command in fastboot, DO NOT use the flash-all.bat and if you had 5.1 previously then there is no need to flash the bootloader (blob file). You need to be careful with that file, most hard bricks are caused by corrupted bootloader. Pay attention when downloading the Nvidia recovery image, make sure you get the one for your specific device model.
Cheers.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
Click to expand...
Click to collapse
Hi , here my flash details
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 67108864 bytes
sending 'recovery' (13698 KB)...
OKAY [ 0.374s]
writing 'recovery'...
OKAY [ 0.580s]
finished. total time: 0.958s
C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 67108864 bytes
sending 'boot' (10288 KB)...
OKAY [ 0.254s]
writing 'boot'...
OKAY [ 0.453s]
finished. total time: 0.712s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 67108864 bytes
erasing 'system'...
OKAY [ 0.347s]
sending sparse 'system' 1/31 (62437 KB)...
OKAY [ 1.594s]
writing 'system' 1/31...
OKAY [ 2.723s]
sending sparse 'system' 2/31 (62993 KB)...
OKAY [ 1.622s]
writing 'system' 2/31...
OKAY [ 2.720s]
sending sparse 'system' 3/31 (65443 KB)...
OKAY [ 1.810s]
writing 'system' 3/31...
OKAY [ 3.066s]
sending sparse 'system' 4/31 (65512 KB)...
OKAY [ 1.651s]
writing 'system' 4/31...
OKAY [ 2.788s]
sending sparse 'system' 5/31 (65532 KB)...
OKAY [ 1.671s]
writing 'system' 5/31...
OKAY [ 2.674s]
sending sparse 'system' 6/31 (63893 KB)...
OKAY [ 1.635s]
writing 'system' 6/31...
OKAY [ 2.673s]
sending sparse 'system' 7/31 (58260 KB)...
OKAY [ 1.475s]
writing 'system' 7/31...
OKAY [ 2.320s]
sending sparse 'system' 8/31 (59088 KB)...
OKAY [ 1.502s]
writing 'system' 8/31...
OKAY [ 2.355s]
sending sparse 'system' 9/31 (65533 KB)...
OKAY [ 1.680s]
writing 'system' 9/31...
OKAY [ 2.747s]
sending sparse 'system' 10/31 (64176 KB)...
OKAY [ 1.622s]
writing 'system' 10/31...
OKAY [ 2.494s]
sending sparse 'system' 11/31 (58956 KB)...
OKAY [ 1.504s]
writing 'system' 11/31...
OKAY [ 2.454s]
sending sparse 'system' 12/31 (65532 KB)...
OKAY [ 1.652s]
writing 'system' 12/31...
OKAY [ 2.736s]
sending sparse 'system' 13/31 (60898 KB)...
OKAY [ 1.555s]
writing 'system' 13/31...
OKAY [ 2.704s]
sending sparse 'system' 14/31 (62455 KB)...
OKAY [ 1.627s]
writing 'system' 14/31...
OKAY [ 2.751s]
sending sparse 'system' 15/31 (65532 KB)...
OKAY [ 1.707s]
writing 'system' 15/31...
OKAY [ 2.698s]
sending sparse 'system' 16/31 (65532 KB)...
OKAY [ 1.667s]
writing 'system' 16/31...
OKAY [ 2.690s]
sending sparse 'system' 17/31 (61848 KB)...
OKAY [ 1.551s]
writing 'system' 17/31...
OKAY [ 2.666s]
sending sparse 'system' 18/31 (61428 KB)...
OKAY [ 1.498s]
writing 'system' 18/31...
OKAY [ 2.491s]
sending sparse 'system' 19/31 (65532 KB)...
OKAY [ 1.650s]
writing 'system' 19/31...
OKAY [ 2.736s]
sending sparse 'system' 20/31 (65533 KB)...
OKAY [ 1.677s]
writing 'system' 20/31...
OKAY [ 2.791s]
sending sparse 'system' 21/31 (63217 KB)...
OKAY [ 1.610s]
writing 'system' 21/31...
OKAY [ 2.736s]
sending sparse 'system' 22/31 (65533 KB)...
OKAY [ 1.671s]
writing 'system' 22/31...
OKAY [ 2.857s]
sending sparse 'system' 23/31 (65053 KB)...
OKAY [ 1.714s]
writing 'system' 23/31...
OKAY [ 2.962s]
sending sparse 'system' 24/31 (65534 KB)...
OKAY [ 1.746s]
writing 'system' 24/31...
OKAY [ 3.063s]
sending sparse 'system' 25/31 (63170 KB)...
OKAY [ 1.623s]
writing 'system' 25/31...
OKAY [ 2.748s]
sending sparse 'system' 26/31 (60468 KB)...
OKAY [ 1.535s]
writing 'system' 26/31...
OKAY [ 2.602s]
sending sparse 'system' 27/31 (64617 KB)...
OKAY [ 1.618s]
writing 'system' 27/31...
OKAY [ 2.686s]
sending sparse 'system' 28/31 (65532 KB)...
OKAY [ 1.626s]
writing 'system' 28/31...
OKAY [ 2.682s]
sending sparse 'system' 29/31 (65532 KB)...
OKAY [ 1.644s]
writing 'system' 29/31...
OKAY [ 2.773s]
sending sparse 'system' 30/31 (65532 KB)...
OKAY [ 1.653s]
writing 'system' 30/31...
OKAY [ 2.734s]
sending sparse 'system' 31/31 (16061 KB)...
OKAY [ 0.496s]
writing 'system' 31/31...
OKAY [ 0.808s]
finished. total time: 131.663s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata.img
target reported max download size of 67108864 bytes
erasing 'userdata'...
OKAY [ 1.750s]
sending sparse 'userdata' 1/3 (65532 KB)...
OKAY [ 1.644s]
writing 'userdata' 1/3...
OKAY [ 2.672s]
sending sparse 'userdata' 2/3 (65532 KB)...
OKAY [ 1.617s]
writing 'userdata' 2/3...
OKAY [ 2.620s]
sending sparse 'userdata' 3/3 (5158 KB)...
OKAY [ 0.182s]
writing 'userdata' 3/3...
OKAY [ 0.386s]
finished. total time: 10.884s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash staging blob
target reported max download size of 67108864 bytes
sending 'staging' (3443 KB)...
OKAY [ 0.100s]
writing 'staging'...
OKAY [ 0.175s]
finished. total time: 0.278s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem dtbname
...
(bootloader) tegra210-foster-e-p2530-0930-e02-00.dtb
OKAY [ 0.006s]
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dtb tegra210-foster-e-p2530-0930-e02-00.dtb
error: cannot load 'tegra210-foster-e-p2530-0930-e02-00.dtb'
So i stuck at DTB flash, then i just fast reboot and it back alive, but it back factory default my SSD 500GB storage all gone.
I need to be reformat, remount as storage again and reinstall applications again. I also upgraded to 5.2 too.
just don't know why this update have problem, previously 3 updates (since june 2016) all no issue,
moreover this 5.2 update is the smallest files (140+MB) size compare to the other 3 updates.
can someone explain why? hopefully the next update it would not happen again.
I rather prefer big size file update then this.
BTW i wish to thanks everyone here share and help.
Thank You
I unrooted and still couldn't update. Factory reset did nothing.
adam_purkis said:
My shield isn't rooted but im getting the same looping problem. I noticed recently though that on boot up my shield says the device is corrupt etc etc as though it has been rooted, but I've not modified anything.maybe this looping update caused that?
Will I need to wait and try and flash a factory image when it comes out?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Did you unlock bootloader? If so that is why you are getting the device is corrupt message...
chow9229 said:
just don't know why this update have problem, previously 3 updates (since june 2016) all no issue,
moreover this 5.2 update is the smallest files (140+MB) size compare to the other 3 updates.
can someone explain why? hopefully the next update it would not happen again.
I rather prefer big size file update then this.
BTW i wish to thanks everyone here share and help.
Thank You
Click to expand...
Click to collapse
This update was different, it is a progressive update and it is the first time nvidia do that.
Enviado desde mi Redmi Note 4 mediante Tapatalk
AndroidUser00110001 said:
Did you unlock bootloader? If so that is why you are getting the device is corrupt message...
Click to expand...
Click to collapse
Nope didn't unlock anything it's fully stock and only bought it about 3 weeks ago.
If I flash the factory rom when they release it do you think that will help?
Sent from my D6503 using Tapatalk
adam_purkis said:
Nope didn't unlock anything it's fully stock and only bought it about 3 weeks ago.
If I flash the factory rom when they release it do you think that will help?
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Yes, most likely but are you able to boot into 5.1 system and use your shield normally?.
Hello, does anyone have a complete ROM running, where all the little stuff is working without gapps?
Ideally im searching for Lineage but any AOSP, or anything without Gapps is welcome here.
Thanks for any hint.
Havoc rom working fine
thanks for the reply. so battery life, notch, wifi, etc. all working and no single google app is preinstalled?
is it a GSI (treble) or a rom specifically for a2 lite?
As far as I know there are no custom roms for our device beside GSI's at the moment.
i thought so but what i read from lineageOS´s GSI i presumed they all have serious difficulties with custom notch position and special drivers for each telephone. so i couldnt imagine havoc working just fine with a2 lite. There also isnt a thread for havoc here right? at least i didnt find it at the custom rom section. but if thedoop says its working just fine ill give it a try as daily driver. as long as i have gapps from custom rom i wouldnt even take the phone out of the fridge
After you tried Havoc please report about your experiences with it.
Code:
fastboot flash system Havoc-OS-v2.0-20181016-GSI-ARM64-AB-Official.img
target reported max download size of 534773760 bytes
sending sparse 'system' 1/3 (522236 KB)...
OKAY [ 12.138s]
writing 'system' 1/3...
OKAY [ 2.515s]
sending sparse 'system' 2/3 (522236 KB)...
OKAY [ 12.431s]
writing 'system' 2/3...
OKAY [ 2.446s]
sending sparse 'system' 3/3 (424660 KB)...
OKAY [ 9.869s]
writing 'system' 3/3...
OKAY [ 1.994s]
finished. total time: 41.409s
bootloop.
nothing fancy stock full flash, twrp intall, fastboot havoc. i think ill wait for official lineageOS...
tutankpusch said:
Code:
fastboot flash system Havoc-OS-v2.0-20181016-GSI-ARM64-AB-Official.img
target reported max download size of 534773760 bytes
sending sparse 'system' 1/3 (522236 KB)...
OKAY [ 12.138s]
writing 'system' 1/3...
OKAY [ 2.515s]
sending sparse 'system' 2/3 (522236 KB)...
OKAY [ 12.431s]
writing 'system' 2/3...
OKAY [ 2.446s]
sending sparse 'system' 3/3 (424660 KB)...
OKAY [ 9.869s]
writing 'system' 3/3...
OKAY [ 1.994s]
finished. total time: 41.409s
bootloop.
nothing fancy stock full flash, twrp intall, fastboot havoc. i think ill wait for official lineageOS...
Click to expand...
Click to collapse
TWRP is having issues with custom ROMs. If you use fastboot to flash then the stock recovery to factory reset, HavocOS works fine.
rosiepie said:
TWRP is having issues with custom ROMs. If you use fastboot to flash then the stock recovery to factory reset, HavocOS works fine.
Click to expand...
Click to collapse
Let me try. If I succeeded. I shall share complete guide along with download links.
abidalishakir.khan said:
Let me try. If I succeeded. I shall share complete guide along with download links.
Click to expand...
Click to collapse
I do have difficulties flashing ROMS. Once I did flash successfully, but after installing Magisk, it bootloops, and I also stumbled upon the Encrypted Password thing in TWRP.
i tried today without twrp, so just flash-all stock, then fastboot havoc.
bootloop.
(this file: https://sourceforge.net/projects/ha...0181016-GSI-ARM64-AB-Official.img.xz/download)
Hey All,
I wanted to start a thread on compiling AOSP from scratch. I have done a bit of work with the folks over in the unofficial Lineage build (thank you @gee one!).
If you want to recreate my work, I posted helper scripts to include the necessary changes as well as a guide on how to compile there. Those scripts were adapted from lineageOS.
You can download a compiled img files or the recovery-image.zip here (get the vendor image here, and get the bootloader and radio images here). The recovery-image.zip should be able to be flashed in TWRP, or you can execute the following commands in the bootloader for the img files:
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot -w (to wipe cache and data)
This is currently based off of build PQ3B.190801.002, last updated 2019-08-30
This ROM is compatible with MicroG, OpenGapps, F-Droid Privileged App, and Magisk
MicroG - Install via NanoDroid: https://nanolx.org/nanolx/nanodroid (Install first NanoDroid-Patcher then NanoDroig-MicroG)
OpenGapps - https://opengapps.org/
Magisk: https://forum.xda-developers.com/apps/magisk
F-Droid Privileged App: https://f-droid.org/en/packages/org.fdroid.fdroid.privileged.ota/
KNOWN ISSUES:
- AT&T does not have "Enhanced 4G LTE" mode, and WiFi Calling doesn't seem to work. I imagine this is a proprietary blob missing.
- eSIM isn't functional. I have a test build for it if you want to try, but it will crash without MicroG or Google Play. When I get confirmation it works I'll add it.
- There are probably other proprietary files I can add so that I can unlock normally stock ROM features, feel free to post and let me know. I am happy to even provide test builds, so if it does work, I will add it to the normal ROM.
NOTICES:
- This is untested in Sprint and Verizon. I removed a bunch of their proprietary files, so if you install and it doesn't work, install this version and see if it works. Please also let me know the results!
- If you do not install the AOSP Vendor above, you get a "device is corrupted" error. This is intentional. Secure boot is still on, so you cannot use the factory vendor image.
- The compiled ROMs will stay as close to AOSP as possible, with the exception of adding proprietary files that unlock stock ROM features. I do this so maintaining the ROM is easy, and I really only make this ROM for myself. I don't mind posting the compiled ROMs here, and I do hope folks find it useful. However, I am not adding non-stock/AOSP features (i.e. Lineage/OmniROM/bootlegger/etc. features). If I did, I have to add and maintain them. I really have neither the time nor the inclination to do that. The only way to change my mind is if I was paid to do it, but I already have a well paying day job, so the paycheck would have to be very well worth my while (which is why I don't have a donote button, I really don't want to feel like I'm obligated to do this).
I was trying to be "smart" and use vendor.img from stock ROM. It failed miserably.
Boot to TWRP first, did factory wipe, reboot to bootloader and flashed ROM:
======================================
AOSP>fastboot flash boot boot.img && fastboot flash dtbo dtbo.img && fastboot flash vbmeta vbmeta.img && fastboot flash system system.img && fastboot flash vendor vendor.img && fastboot -w
Sending 'boot_b' (65536 KB) OKAY [ 1.641s]
Writing 'boot_b' OKAY [ 0.328s]
Finished. Total time: 2.453s
Sending 'dtbo_b' (8192 KB) OKAY [ 0.281s]
Writing 'dtbo_b' OKAY [ 0.094s]
Finished. Total time: 0.656s
Sending 'vbmeta_b' (4 KB) OKAY [ 0.109s]
Writing 'vbmeta_b' OKAY [ 0.063s]
Finished. Total time: 0.438s
Sending sparse 'system_b' 1/5 (262140 KB) OKAY [ 6.508s]
Writing 'system_b' OKAY [ 0.047s]
Sending sparse 'system_b' 2/5 (262140 KB) OKAY [ 6.531s]
Writing 'system_b' OKAY [ 0.063s]
Sending sparse 'system_b' 3/5 (262140 KB) OKAY [ 6.455s]
Writing 'system_b' OKAY [ 0.063s]
Sending sparse 'system_b' 4/5 (262140 KB) OKAY [ 6.584s]
Writing 'system_b' OKAY [ 0.359s]
Sending sparse 'system_b' 5/5 (155532 KB) OKAY [ 3.968s]
Writing 'system_b' OKAY [ 1.172s]
Finished. Total time: 39.903s
Sending sparse 'vendor_b' 1/3 (262140 KB) OKAY [ 6.527s]
Writing 'vendor_b' OKAY [ 0.373s]
Sending sparse 'vendor_b' 2/3 (262096 KB) OKAY [ 6.515s]
Writing 'vendor_b' OKAY [ 0.375s]
Sending sparse 'vendor_b' 3/3 (12276 KB) OKAY [ 1.297s]
Writing 'vendor_b' OKAY [ 0.125s]
Finished. Total time: 19.118s
Erasing 'userdata' OKAY [ 4.506s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.188s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 5.147s
======================================
White screen with Google logo popped up for few sec and phone rebooted with following message:
Your device is corrupt. It can't be trusted and may not work properly.
In second attempt flashed stock ROM first, boot, enabled ADB, disabled automatic updates, boot to bootloader, then TWRP, did factory wipe, flash ROM and ends up with the same result.
Compiling my own vendor image using provided instructions doesn't look like something I'm eager to do.
Pogo said:
I was trying to be "smart" and use vendor.img from stock ROM. It failed miserably.
Boot to TWRP first, did factory wipe, reboot to bootloader and flashed ROM:
======================================
AOSP>fastboot flash boot boot.img && fastboot flash dtbo dtbo.img && fastboot flash vbmeta vbmeta.img && fastboot flash system system.img && fastboot flash vendor vendor.img && fastboot -w
Sending 'boot_b' (65536 KB) OKAY [ 1.641s]
Writing 'boot_b' OKAY [ 0.328s]
Finished. Total time: 2.453s
Sending 'dtbo_b' (8192 KB) OKAY [ 0.281s]
Writing 'dtbo_b' OKAY [ 0.094s]
Finished. Total time: 0.656s
Sending 'vbmeta_b' (4 KB) OKAY [ 0.109s]
Writing 'vbmeta_b' OKAY [ 0.063s]
Finished. Total time: 0.438s
Sending sparse 'system_b' 1/5 (262140 KB) OKAY [ 6.508s]
Writing 'system_b' OKAY [ 0.047s]
Sending sparse 'system_b' 2/5 (262140 KB) OKAY [ 6.531s]
Writing 'system_b' OKAY [ 0.063s]
Sending sparse 'system_b' 3/5 (262140 KB) OKAY [ 6.455s]
Writing 'system_b' OKAY [ 0.063s]
Sending sparse 'system_b' 4/5 (262140 KB) OKAY [ 6.584s]
Writing 'system_b' OKAY [ 0.359s]
Sending sparse 'system_b' 5/5 (155532 KB) OKAY [ 3.968s]
Writing 'system_b' OKAY [ 1.172s]
Finished. Total time: 39.903s
Sending sparse 'vendor_b' 1/3 (262140 KB) OKAY [ 6.527s]
Writing 'vendor_b' OKAY [ 0.373s]
Sending sparse 'vendor_b' 2/3 (262096 KB) OKAY [ 6.515s]
Writing 'vendor_b' OKAY [ 0.375s]
Sending sparse 'vendor_b' 3/3 (12276 KB) OKAY [ 1.297s]
Writing 'vendor_b' OKAY [ 0.125s]
Finished. Total time: 19.118s
Erasing 'userdata' OKAY [ 4.506s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.188s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 5.147s
======================================
White screen with Google logo popped up for few sec and phone rebooted with following message:
Your device is corrupt. It can't be trusted and may not work properly.
In second attempt flashed stock ROM first, boot, enabled ADB, disabled automatic updates, boot to bootloader, then TWRP, did factory wipe, flash ROM and ends up with the same result.
Compiling my own vendor image using provided instructions doesn't look like something I'm eager to do.
Click to expand...
Click to collapse
You should be able to use the vendor image off of the google website (AOSP drivers, not factory image), all you are doing is unpacking it and then agreeing to the terms of use. You can't use other ones because it trips secure boot. I hesitate to upload it because you have to agree to terms of use when you unpack it.
EDIT: I confirmed, the SHA-512 of the vendor.img off of the google website (AOSP, not stock) is exactly the same as the one I flashed (I.e. the compilation process does nothing to it). You do have to use the AOSP one, or else you trip secure boot.
Pogo said:
I was trying to be "smart" and use vendor.img from stock ROM. It failed miserably.
Boot to TWRP first, did factory wipe, reboot to bootloader and flashed ROM:
======================================
AOSP>fastboot flash boot boot.img && fastboot flash dtbo dtbo.img && fastboot flash vbmeta vbmeta.img && fastboot flash system system.img && fastboot flash vendor vendor.img && fastboot -w
Sending 'boot_b' (65536 KB) OKAY [ 1.641s]
Writing 'boot_b' OKAY [ 0.328s]
Finished. Total time: 2.453s
Sending 'dtbo_b' (8192 KB) OKAY [ 0.281s]
Writing 'dtbo_b' OKAY [ 0.094s]
Finished. Total time: 0.656s
Sending 'vbmeta_b' (4 KB) OKAY [ 0.109s]
Writing 'vbmeta_b' OKAY [ 0.063s]
Finished. Total time: 0.438s
Sending sparse 'system_b' 1/5 (262140 KB) OKAY [ 6.508s]
Writing 'system_b' OKAY [ 0.047s]
Sending sparse 'system_b' 2/5 (262140 KB) OKAY [ 6.531s]
Writing 'system_b' OKAY [ 0.063s]
Sending sparse 'system_b' 3/5 (262140 KB) OKAY [ 6.455s]
Writing 'system_b' OKAY [ 0.063s]
Sending sparse 'system_b' 4/5 (262140 KB) OKAY [ 6.584s]
Writing 'system_b' OKAY [ 0.359s]
Sending sparse 'system_b' 5/5 (155532 KB) OKAY [ 3.968s]
Writing 'system_b' OKAY [ 1.172s]
Finished. Total time: 39.903s
Sending sparse 'vendor_b' 1/3 (262140 KB) OKAY [ 6.527s]
Writing 'vendor_b' OKAY [ 0.373s]
Sending sparse 'vendor_b' 2/3 (262096 KB) OKAY [ 6.515s]
Writing 'vendor_b' OKAY [ 0.375s]
Sending sparse 'vendor_b' 3/3 (12276 KB) OKAY [ 1.297s]
Writing 'vendor_b' OKAY [ 0.125s]
Finished. Total time: 19.118s
Erasing 'userdata' OKAY [ 4.506s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.188s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 5.147s
======================================
White screen with Google logo popped up for few sec and phone rebooted with following message:
Your device is corrupt. It can't be trusted and may not work properly.
In second attempt flashed stock ROM first, boot, enabled ADB, disabled automatic updates, boot to bootloader, then TWRP, did factory wipe, flash ROM and ends up with the same result.
Compiling my own vendor image using provided instructions doesn't look like something I'm eager to do.
Click to expand...
Click to collapse
How are you getting the "device is corrupt message". I think that only shows up when your bootloader is locked. Are you sure it's not the orange message " device can't be verified"? You should only get orange or yellow messages. The red message means something is wrong- missing keys or bad/no signature.
I might be a little confused- I've been building and flashing so many variations, I can't keep them straight anymore.
gee one said:
How are you getting the "device is corrupt message". I think that only shows up when your bootloader is locked. Are you sure it's not the orange message " device can't be verified"? You should only get orange or yellow messages. The red message means something is wrong- missing keys or bad/no signature.
I might be a little confused- I've been building and flashing so many variations, I can't keep them straight anymore.
Click to expand...
Click to collapse
I compiled AOSP with the AOSP vendor.IMG, not the factory vendor.img . he is using the factory one, and that triggers the "device is corrupt" error he is getting. It's secure boot detecting the difference in vendor images
kop316 said:
I compiled AOSP with the AOSP vendor.IMG, not the factory vendor.img . he is using the factory one, and that triggers the "device is corrupt" error he is getting. It's secure boot detecting the difference in vendor images
Click to expand...
Click to collapse
If you build it with the stock image as a prebuilt vendor image, the hash and info should be included in the vbmeta.img. The BoardConfigPartial.mk file has
Code:
BOARD_PREBUILT_VENDORIMAGE := vendor/google_devices/sargo/proprietary/vendor.img
which should add whatever vendor image you put in there to the vbmeta data.
However, if I recall correctly, building aosp with the aosp vendor images doesn't enable all the features. I think wifi calling and camera are broken on stock aosp.
There is a great tool for bringing the extra proprietary files into aosp. https://github.com/GrapheneOS/android-prepare-vendor
This will create a drop in replacement for the vendor/google_devices tree. I believe it also replaces the qcom tree as well.
Here is stock aosp built with help from the android-prepare-vendor scripts.
https://brownbagdinner.com/sargo-aosp-prepare-vendor_d6c76ce9.tar
This probably isn't gapps friendly, although there is a --full flag that will pull in more files that could help with gapps.
I don't think that you have to flash system_other.img, but it will probably speed up your first boot.
You can use "fastboot getvar current-slot" to see what slot you are on, and then flash system_other.img to, you know, the other slot with "fastboot flash system_<type in the other slot here> system_other.img"
You might have to wipe data if you are coming from a different rom, and you might have to reflash the stock vendor if you are going to a custom rom that is expecting the stock vendor.
gee one said:
If you build it with the stock image as a prebuilt vendor image, the hash and info should be included in the vbmeta.img. The BoardConfigPartial.mk file has
Code:
BOARD_PREBUILT_VENDORIMAGE := vendor/google_devices/sargo/proprietary/vendor.img
which should add whatever vendor image you put in there to the vbmeta data.
However, if I recall correctly, building aosp with the aosp vendor images doesn't enable all the features. I think wifi calling and camera are broken on stock aosp.
There is a great tool for bringing the extra proprietary files into aosp. https://github.com/GrapheneOS/android-prepare-vendor
This will create a drop in replacement for the vendor/google_devices tree. I believe it also replaces the qcom tree as well.
Here is stock aosp built with help from the android-prepare-vendor scripts.
https://brownbagdinner.com/sargo-aosp-prepare-vendor_d6c76ce9.tar
This probably isn't gapps friendly, although there is a --full flag that will pull in more files that could help with gapps.
I don't think that you have to flash system_other.img, but it will probably speed up your first boot.
You can use "fastboot getvar current-slot" to see what slot you are on, and then flash system_other.img to, you know, the other slot with "fastboot flash system_<type in the other slot here> system_other.img"
You might have to wipe data if you are coming from a different rom, and you might have to reflash the stock vendor if you are going to a custom rom that is expecting the stock vendor.
Click to expand...
Click to collapse
One of my next steps was to try the Graphene OS scripts to see how they work.
I am actually able to use WiFi calling and enhanced LTE on T mobile with the AOSP vendor image, and the camera works fine. If you are compiling AOSP yourself, you can also just swap out the vendor.IMG to the factory one.and recompile, it will do like you said.
I am trying also not to include every single.proprietary thing that is included, just what is needed for desired functionality. Several of them adds functionality for Google Play, and that can be added with openGapps.
kop316 said:
You should be able to use the vendor image off of the google website (AOSP drivers, not factory image), all you are doing is unpacking it and then agreeing to the terms of use. You can't use other ones because it trips secure boot. I hesitate to upload it because you have to agree to terms of use when you unpack it.
EDIT: I confirmed, the SHA-512 of the vendor.img off of the google website (AOSP, not stock) is exactly the same as the one I flashed (I.e. the compilation process does nothing to it). You do have to use the AOSP one, or else you trip secure boot.
Click to expand...
Click to collapse
You are right. Once I extracted vendor.img from AOSP it booted!
I'm looking around, playing, installing... So far so good
Magisk and EdXposed are working ,Google camera is working after installing microG as well as my banking app, Netflix and all other apps I use.
Pogo said:
You are right. Once I extracted vendor.img from AOSP it booted!
I'm looking around, playing, installing... So far so good
Magisk and EdXposed are working ,Google camera is working after installing microG as well as my banking app, Netflix and all other apps I use.
Click to expand...
Click to collapse
Glad to hear It! I didn't add the part to allow signature spoofing....I'm surprised MicroG works. That was something I was going to try.
kop316 said:
Glad to hear It! I didn't add the part to allow signature spoofing....I'm surprised MicroG works. That was something I was going to try.
Click to expand...
Click to collapse
Signature Spoofing require FakeGApps2.apk which is Exposed module. However FakeGApps2 is throwing lots of NullPointerExceptions in EdXposed. If you add signature spoofing into ROM, this module won't be needed.
Pogo said:
Signature Spoofing require FakeGApps2.apk which is Exposed module. However FakeGApps2 is throwing lots of NullPointerExceptions in ExXposed. If you add signature spoofing into ROM, this module won't be needed.
Click to expand...
Click to collapse
OK. I haven't tried Exposed in a long time.
My mobile provider has LTE. Mobile network in Status bar shows 4G+ (ok, no big deal).
In Mobile Network -> Advanced -> Preferred Network type, it also say 4G+ (again no big deal). However when I click to 'Preferred Network type' the available options are 3G and 2G. No 4G+, no LTE option.
The mobile speed is fine, it's definitely as fast as any other ROM.
Any chance to add eSIM into AOSP? I nave tried to install eSIM app from my backup, the app is there, but it won't show in the options (Settings->Mobile network->Advanced->Carrier)
Pogo said:
My mobile provider has LTE. Mobile network in Status bar shows 4G+ (ok, no big deal).
In Mobile Network -> Advanced -> Preferred Network type, it also say 4G+ (again no big deal). However when I click to 'Preferred Network type' the available options are 3G and 2G. No 4G+, no LTE option.
The mobile speed is fine, it's definitely as fast as any other ROM.
Any chance to add eSIM into AOSP? I nave tried to install eSIM app from my backup, the app is there, but it won't show in the options (Settings->Mobile network->Advanced->Carrier)
Click to expand...
Click to collapse
I'm aware of the first issue, I have a feeling there's an app I need to add that I haven't yet.
I recall Gee One saying you need Gapps for the eSIM to work? I know AOSP is aware of it (if you go into reset -> network, it will ask to also wipe your eSIM).
kop316 said:
I'm aware of the first issue, I have a feeling there's an app I need to add that I haven't yet.
I recall Gee One saying you need Gapps for the eSIM to work? I know AOSP is aware of it (if you go into reset -> network, it will ask to also wipe your eSIM).
Click to expand...
Click to collapse
Esim looks for gcs/google services otherwise it will force close.
Oops, hit send too soon. Lineage has LTE as an option. I can't remember if I've ever seen it on aosp. I think yes, because WiFi calls are HD. I'll check when I'm home later.
gee one said:
Oops, hit send too soon. Lineage has LTE as an option. I can't remember if I've ever seen it on aosp. I think yes, because WiFi calls are HD. I'll check when I'm home later.
Click to expand...
Click to collapse
The AOSP one I compiled doesn't have that option. I was wondering if I didn't include a proprietary file to allow that. But it does give me enhanced 4G LTE mode (VoLTE) and it gives my WiFi calling, so I haven't made too hard of an effort to look.
If you know what it is I am missing that'd be great!
gee one said:
Esim looks for gcs/google services otherwise it will force close.
Click to expand...
Click to collapse
I have microG installed and eSIM Manager (pulled from Stock ROM) and it's not crashing.
However, I cannot start it. My guess is that some menu option is missing or has to be enabled in Settings.
If I search for eSIM in Settings it point to 'Carrier', but nothing happen when click on this.
If I try to start some of the eSIM Manager activities I'm getting "permission denied". Don't know if this help.
kop316 said:
The AOSP one I compiled doesn't have that option. I was wondering if I didn't include a proprietary file to allow that. But it does give me enhanced 4G LTE mode (VoLTE) and it gives my WiFi calling, so I haven't made too hard of an effort to look.
If you know what it is I am missing that'd be great!
Click to expand...
Click to collapse
Yup, that sound right. The menu has a toggle for 4G LTE mode, but the network type only allows for 3G/2G.
This is for aosp.
Pogo said:
I have microG installed and eSIM Manager (pulled from Stock ROM) and it's not crashing.
However, I cannot start it. My guess is that some menu option is missing or has to be enabled in Settings.
If I search for eSIM in Settings it point to 'Carrier', but nothing happen when click on this.
If I try to start some of the eSIM Manager activities I'm getting "permission denied". Don't know if this help.
Click to expand...
Click to collapse
https://mega.nz/#F!95wmSAJA!xE1eWAA68AsJax6C90pFxg
See if that get's it to work. I am not confident it will work without Google Play, but maybe?
kop316 said:
https://mega.nz/#F!95wmSAJA!xE1eWAA68AsJax6C90pFxg
See if that get's it to work. I am not confident it will work without Google Play, but maybe?
Click to expand...
Click to collapse
Should I just flash these 3 img files or there are more steps involved?
When flashing the full November image to my BL unlocked Google 3XL, I get the following errors during the flash;
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
Sending 'boot_b' (65536 KB) OKAY [ 1.978s]
Writing 'boot_b' OKAY [ 0.516s]
Sending 'dtbo_b' (8192 KB) OKAY [ 0.313s]
Writing 'dtbo_b' OKAY [ 0.085s]
Sending sparse 'product_b' 1/8 (262140 KB) OKAY [ 7.364s]
Writing sparse 'product_b' 1/8 FAILED (remote: 'Partition should be flashed in fastbootd')
Finished. Total time: 73.905s
Press any key to exit...
Any assistance is appreciated thanks!
Maybe try and d/l the latest tools since they are new as of Oct 2019: https://developer.android.com/studio/releases/platform-tools
cmh714 said:
Maybe try and d/l the latest tools since they are new as of Oct 2019: https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
And changing USB Cables
cmh714 said:
Maybe try and d/l the latest tools since they are new as of Oct 2019: https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
That did it!
Thank you thank you thank you!
I didn't think of that since it wasn't long ago that I updated these files!
parakleet said:
And changing USB Cables
Click to expand...
Click to collapse
Thank you for that good suggestion!
It turned out I needed to update the ADB tools!
Hello lads, after trying trying to install multiple android 13 custom roms I have issue booting my phone. Keep getting this annoying "no command" screen after it tries to reboot few times. Could anyone help me with this one ? I know that issue should be very easy resolvable. My daily driver used to be stock most recent (not beta) firmware.
naujokellis said:
Hello lads, after trying trying to install multiple android 13 custom roms I have issue booting my phone. Keep getting this annoying "no command" screen after it tries to reboot few times. Could anyone help me with this one ? I know that issue should be very easy resolvable. My daily driver used to be stock most recent (not beta) firmware.
Click to expand...
Click to collapse
Did you erase your boot image by chance? Reflash /boot and /init_boot
Ok, i will do. I havent deleted it for sure, but i did flashed bootloader to all slots, would that could effect booting up ? as i have some errors during installation of custom ROM, but installation finished with successful message.
BTW with original firmware it booted up without a problem. And I still used stock firmware for another day after playing with bootloader or boot files.
Bootloader Version...: slider-1.2-9152140
Baseband Version.....: g5123b-107485-221101-B-9242015
Serial Number........: 1A281FDEE007L3
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Setting current slot to 'b' OKAY [ 0.089s]
extracting boot.img (64 MB) to disk... took 0.286s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.350s]
Writing 'boot_b' OKAY [ 0.079s]
extracting dtbo.img (16 MB) to disk... took 0.069s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.566s]
Writing 'dtbo_b' OKAY [ 0.022s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.002s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system_b' OKAY [ 0.002s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Sending 'super' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.020s]
Resizing 'product_b' OKAY [ 0.003s]
Resizing 'system_b' OKAY [ 0.002s]
Resizing 'system_a' OKAY [ 0.003s]
Resizing 'vendor_b' OKAY [ 0.002s]
Resizing 'vendor_a' OKAY [ 0.002s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (2234 MB) to disk... took 12.826s
Invalid sparse file format at header magic
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.005s]
Sending sparse 'product_b' 1/9 (261666 KB) OKAY [ 9.032s]
Writing 'product_b' OKAY [ 0.457s]
Sending sparse 'product_b' 2/9 (261399 KB) OKAY [ 9.334s]
Writing 'product_b' OKAY [ 0.495s]
Sending sparse 'product_b' 3/9 (260861 KB) OKAY [ 9.410s]
Writing 'product_b' OKAY [ 0.473s]
Sending sparse 'product_b' 4/9 (261912 KB) OKAY [ 9.286s]
Writing 'product_b' OKAY [ 0.471s]
Sending sparse 'product_b' 5/9 (262080 KB) OKAY [ 9.405s]
Writing 'product_b' OKAY [ 0.462s]
Sending sparse 'product_b' 6/9 (261344 KB) OKAY [ 9.402s]
Writing 'product_b' OKAY [ 0.550s]
Sending sparse 'product_b' 7/9 (261391 KB) OKAY [ 9.325s]
Writing 'product_b' OKAY [ 0.498s]
Sending sparse 'product_b' 8/9 (256403 KB) OKAY [ 9.318s]
Writing 'product_b' OKAY [ 0.633s]
Sending sparse 'product_b' 9/9 (183972 KB) OKAY [ 6.660s]
Writing 'product_b' OKAY [ 0.356s]
archive does not contain 'product_services.img'
extracting system.img (967 MB) to disk... took 4.577s
Invalid sparse file format at header magic
archive does not contain 'system.sig'
Resizing 'system_b' OKAY [ 0.007s]
Sending sparse 'system_b' 1/4 (262108 KB) OKAY [ 9.344s]
Writing 'system_b' OKAY [ 0.451s]
Sending sparse 'system_b' 2/4 (254041 KB) OKAY [ 9.211s]
Writing 'system_b' OKAY [ 1.016s]
Sending sparse 'system_b' 3/4 (261996 KB) OKAY [ 9.528s]
Writing 'system_b' OKAY [ 0.433s]
Sending sparse 'system_b' 4/4 (200872 KB) OKAY [ 7.233s]
Writing 'system_b' OKAY [ 0.374s]
extracting system_other.img (20 MB) to disk... took 0.141s
archive does not contain 'system.sig'
Resizing 'system_a' OKAY [ 0.007s]
Sending 'system_a' (21248 KB) OKAY [ 0.766s]
Writing 'system_a' OKAY [ 0.092s]
extracting vendor.img (534 MB) to disk... took 2.574s
Invalid sparse file format at header magic
archive does not contain 'vendor.sig'
Resizing 'vendor_b' OKAY [ 0.006s]
Sending sparse 'vendor_b' 1/3 (259740 KB) OKAY [ 9.475s]
Writing 'vendor_b' OKAY [ 0.467s]
Sending sparse 'vendor_b' 2/3 (262132 KB) OKAY [ 9.323s]
Writing 'vendor_b' OKAY [ 0.483s]
Sending sparse 'vendor_b' 3/3 (21572 KB) OKAY [ 0.764s]
Writing 'vendor_b' OKAY [ 0.100s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 0.163s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.004s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Rebooting OKAY [ 0.000s]
Finished. Total time: 189.359s
naujokellis said:
Hello lads, after trying trying to install multiple android 13 custom roms I have issue booting my phone. Keep getting this annoying "no command" screen after it tries to reboot few times. Could anyone help me with this one ? I know that issue should be very easy resolvable. My daily driver used to be stock most recent (not beta) firmware.
Click to expand...
Click to collapse
Sounds like the stock android recovery. If you see the above, just hold power and volume up to enter recovery.
jamescable said:
Sounds like the stock android recovery. If you see the above, just hold power and volume up to enter recover
Click to expand...
Click to collapse
OK, this is the screen I am getting, but I am looking for solution why any custom rom does not run on my phone. I know that installing stock firmware would fix issue, but i do not want to use stock firmware. I will try to install stock firmware and reinstall custom ROM later, but i do not think that would fix issue I am having.
naujokellis said:
OK, this is the screen I am getting, but I am looking for solution why any custom rom does not run on my phone. I know that installing stock firmware would fix issue, but i do not want to use stock firmware. I will try to install stock firmware and reinstall custom ROM later, but i do not think that would fix issue I am having.
Click to expand...
Click to collapse
It may help others to help you if you describe in detail (e.g. exact steps and commands used, etc.) your method of installation and any other pertinent details, such as version of Platform Tools used, etc..
naujokellis said:
OK, this is the screen I am getting, but I am looking for solution why any custom rom does not run on my phone. I know that installing stock firmware would fix issue, but i do not want to use stock firmware. I will try to install stock firmware and reinstall custom ROM later, but i do not think that would fix issue I am having.
Click to expand...
Click to collapse
Use android recovery to wipe data and see if that works
jamescable said:
Use android recovery to wipe data and see if that works
Click to expand...
Click to collapse
did that multiple times before installing every custom ROM
Lughnasadh said:
It may help others to help you if you describe in detail (e.g. exact steps and commands used, etc.) your method of installation and any other pertinent details, such as version of Platform Tools used, etc..
Click to expand...
Click to collapse
Im using Linux Mint 21.1
Android Debug Bridge version 1.0.41
Version 28.0.2-debian
Installed as /usr/lib/android-sdk/platform-tools/adb
commands used before reinstalling stock firmware:this and this thread
after reinstalling latest stock firmware (canceling beta version) only used guides how to install custom rom using fastboot mode. ( fastboot update rom.zip )
I have a questio tho, do i need to root my phone with magisk before being able to install custom rom ? I feel like I am missing something, thats why it does not work
naujokellis said:
Im using Linux Mint 21.1
Android Debug Bridge version 1.0.41
Version 28.0.2-debian
Installed as /usr/lib/android-sdk/platform-tools/adb
commands used before reinstalling stock firmware:this and this thread
after reinstalling latest stock firmware (canceling beta version) only used guides how to install custom rom using fastboot mode. ( fastboot update rom.zip )
Click to expand...
Click to collapse
That could be the issue, idk. I have always used windows. I know some people have issues with Mac and Linux so...
jamescable said:
That could be the issue, idk. I have always used windows. I know some people have issues with Mac and Linux so...
Click to expand...
Click to collapse
That would be insane, as I would have had issues before, linux is my daily driver
naujokellis said:
That would be insane, as I would have had issues before, linux is my daily driver
Click to expand...
Click to collapse
Then idk. I have been flashing Roms since Motorola droid 1 android froyo days and have heard of numerous people having some weird issue with Linux one time or another
naujokellis said:
Version 28.0.2-debian
Click to expand...
Click to collapse
Is that Platform Tools version 28.0.2? If so, that's like 4 years old. The latest Platform Tools version is 33.0.3.
Lughnasadh said:
Is that Platform Tools version 28.0.2? If so, that's like 4 years old. The latest Platform Tools version is 33.0.3.
Click to expand...
Click to collapse
OK, i will double check on that and I will update platform tools