Related
Hello,
i have a Pixel XL which i have just purchased second hand. The previous owner flashed the Android P beta and i wanted to restore to the last Oreo.
Started skipsoft tool and chose to restore to stock, device found and flash starts but always fails to finish with the following status. The stock Rom i am trying to flash was downloaded from official sources. Any ideas what to try?
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: 8996-012001-1711291800
Baseband Version.....: 8996-130091-1802061512
Serial Number........: HT69T0XXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.047s]
checking version-baseband...
OKAY [ 0.045s]
sending 'boot_b' (30177 KB)...
OKAY [ 0.748s]
writing 'boot_b'...
OKAY [ 0.608s]
erasing 'system_b'...
OKAY [ 1.091s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 12.765s]
writing 'system_b' 1/4...
OKAY [ 3.989s]
sending sparse 'system_b' 2/4 (524284 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 32.709s
Make sure your SDK (ADB, fastboot) is up to date.
Is the phone in working condition?
Is the bootloader unlocked?
jiggly cable dude,replace cable before flashing again cause u could brick it.Device fine!
Well that data partition could be corrupt. I would suggest wiping date then try to reflash the factory image. If the data won't wipe you might have a bad emmc
dosada said:
Hello,
i have a Pixel XL which i have just purchased second hand. The previous owner flashed the Android P beta and i wanted to restore to the last Oreo.
Started skipsoft tool and chose to restore to stock, device found and flash starts but always fails to finish with the following status. The stock Rom i am trying to flash was downloaded from official sources. Any ideas what to try?
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: 8996-012001-1711291800
Baseband Version.....: 8996-130091-1802061512
Serial Number........: HT69T0XXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.047s]
checking version-baseband...
OKAY [ 0.045s]
sending 'boot_b' (30177 KB)...
OKAY [ 0.748s]
writing 'boot_b'...
OKAY [ 0.608s]
erasing 'system_b'...
OKAY [ 1.091s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 12.765s]
writing 'system_b' 1/4...
OKAY [ 3.989s]
sending sparse 'system_b' 2/4 (524284 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 32.709s
Click to expand...
Click to collapse
DR3W5K1 said:
Well that data partition could be corrupt. I would suggest wiping date then try to reflash the factory image. If the data won't wipe you might have a bad emmc
Click to expand...
Click to collapse
Is the device 128gb? If so refer to this post by me.
https://forum.xda-developers.com/showpost.php?p=76710445&postcount=23
i would go to developers.google.com and download and flash-all the the latest rom. if that doesn't work fastboot boot twrp.img and goto Wipe -Format Data .
DR3W5K1 said:
Make sure your SDK (ADB, fastboot) is up to date.
Is the phone in working condition?
Click to expand...
Click to collapse
I'm going to second this. I could not flash back to June 8.1 factory from the P beta without updating my ADB and Fastboot to the latest google provides.
I had the latest "Minimal ADB and Fastboot" from XDA and that was not working at all - lots of errors thrown.
dosada said:
Hello,
i have a Pixel XL which i have just purchased second hand. The previous owner flashed the Android P beta and i wanted to restore to the last Oreo.
Started skipsoft tool and chose to restore to stock, device found and flash starts but always fails to finish with the following status. The stock Rom i am trying to flash was downloaded from official sources. Any ideas what to try?
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: 8996-012001-1711291800
Baseband Version.....: 8996-130091-1802061512
Serial Number........: HT69T0XXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.047s]
checking version-baseband...
OKAY [ 0.045s]
sending 'boot_b' (30177 KB)...
OKAY [ 0.748s]
writing 'boot_b'...
OKAY [ 0.608s]
erasing 'system_b'...
OKAY [ 1.091s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 12.765s]
writing 'system_b' 1/4...
OKAY [ 3.989s]
sending sparse 'system_b' 2/4 (524284 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 32.709s
Click to expand...
Click to collapse
I had a similar issue and it started with release of May image and no matter what i did with cable changes like mentioned or using a different pc or using a different usb port or updating to latest fastboot/adb ... switching slots.. i could not flash the full image with -w removed.. i went back and reverted to April full image ... I have not yet tried June but my guess is it will be similiar result with failing on that exact spot as you mentioned. Same exact error.
---------- Post added at 08:40 PM ---------- Previous post was at 08:00 PM ----------
firefly777 said:
I had a similar issue and it started with release of May image and no matter what i did with cable changes like mentioned or using a different pc or using a different usb port or updating to latest fastboot/adb ... switching slots.. i could not flash the full image with -w removed.. i went back and reverted to April full image ... I have not yet tried June but my guess is it will be similiar result with failing on that exact spot as you mentioned. Same exact error.
Click to expand...
Click to collapse
Here's what i did to get past this error so maybe worth a try.. as i mentioned above i reverted to April i flashed slot B with full image ... no data wipes in any of this btw.. so i removed -w from flash-all
i let it do its thing and reboot
i switched to slot A and again did the april flash all no data wipes (remove -w)
then i tried the june full image again no data wipes (remove -w) and voila it finally worked.. so try that to see if it works for you.
no data wipe needed.
flash april full image (remove -w) to both slot b and slot a
keep it on slot a
flash june full image (remove -w)
so up to now i had always flashed only to active slot and not both but with this trick it worked for June as well but first start with April. hope that works for you too bud
My Pixel 3 XL completely stock not unlocked just started displaying the following message:
"Your device is corrupt. It can't be trusted and may not work properly"
"Visit this link on another device g.co/ABH"
Spoke to Google and they asked me to perform a factory reset, I have done so with no luck.
Currently on latest November update.
Is the phone a dud and do I need to claim on warranty or is there any solution to this? Thanks
Demolition49 said:
My Pixel 3 XL completely stock not unlocked just started displaying the following message:
"Your device is corrupt. It can't be trusted and may not work properly"
"Visit this link on another device g.co/ABH"
Spoke to Google and they asked me to perform a factory reset, I have done so with no luck.
Currently on latest November update.
Is the phone a dud and do I need to claim on warranty or is there any solution to this? Thanks
Click to expand...
Click to collapse
you're probably gonna get told this anyway but "use search function"
This has been addressed several times,
Download platform tools make sure your adb is in order download the november factory image and run the flash-all.bat script, this will bring your phone back to life, but with no data,
Demolition49 said:
My Pixel 3 XL completely stock not unlocked just started displaying the following message:
"Your device is corrupt. It can't be trusted and may not work properly"
"Visit this link on another device g.co/ABH"
Spoke to Google and they asked me to perform a factory reset, I have done so with no luck.
Currently on latest November update.
Is the phone a dud and do I need to claim on warranty or is there any solution to this? Thanks
Click to expand...
Click to collapse
You sure it not already unlocked?
Sent from my crosshatch using XDA Labs
I've had this on my P2XL before. Came about totally randomly. Phone started running extremely slow one day, so I rebooted it to see if it would clear out whatever was causing the issue. It wouldn't boot up and gave the same error. I was able to recover from it and save all my data by flashing factory image without wiping (remove -w in the flash-all script). Unfortunately it looks like you already factory reset so all data would be gone already.
Thanks I will flash it and hopefully it will sort it.
Sorry I did search but saw articles about pixel 2 not the 3.
Demolition49 said:
My Pixel 3 XL completely stock not unlocked just started displaying the following message:
"Your device is corrupt. It can't be trusted and may not work properly"
"Visit this link on another device g.co/ABH"
Spoke to Google and they asked me to perform a factory reset, I have done so with no luck.
Currently on latest November update.
Is the phone a dud and do I need to claim on warranty or is there any solution to this? Thanks
Click to expand...
Click to collapse
Did you get the Nov update OTA, or flash it yourself? I'm stock and still on the Sep update. Thought I saw that updates are rolling out, so just curious.
masri1987 said:
you're probably gonna get told this anyway but "use search function"
This has been addressed several times,
Download platform tools make sure your adb is in order download the november factory image and run the flash-all.bat script, this will bring your phone back to life, but with no data,
Click to expand...
Click to collapse
samnada said:
Did you get the Nov update OTA, or flash it yourself? I'm stock and still on the Sep update. Thought I saw that updates are rolling out, so just curious.
Click to expand...
Click to collapse
I got the OTA quite a few days ago, didn't flash it myself. Hopefully you'll get yours soon.
Demolition49 said:
I got the OTA quite a few days ago, didn't flash it myself. Hopefully you'll get yours soon.
Click to expand...
Click to collapse
Thanks
If it caused your problem I'll be happy to wait.
just download sdk platform tools and factory image and run flash all.bat. My data also got corrupt last night after downloading greenify
samnada said:
Thanks
If it caused your problem I'll be happy to wait.
Click to expand...
Click to collapse
I can confirm the update didnt cause any issue, it happened before that
i tryed to sideload OTA but it didnt work so the device needed a full factory wipe and it has fixed the issue.
Demolition49 said:
I can confirm the update didnt cause any issue, it happened before that
i tryed to sideload OTA but it didnt work so the device needed a full factory wipe and it has fixed the issue.
Click to expand...
Click to collapse
Thanks for the follow-up. I actually just got the OTA Nov update this morning and all is well. Glad yours got fixed also.
Alright, I got the device is corrupt error as well because of force of habit i mistakenly installed twrp.....
So I was trying to avoid wiping the data, and removed -w from the flash-all.bat. But I got the error again. Step two I used the flash-all.bat with -w to wipe.
The following are my results. The error "FAILED (Error reading sparse file)" appears at the end.
Code:
Sending 'bootloader_a' (8489 KB) OKAY [ 0.420s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b1c1-0.1-5004167
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.535s]
Finished. Total time: 1.137s
rebooting into bootloader OKAY [ 0.050s]
Finished. Total time: 0.052s
Sending 'radio_a' (71148 KB) OKAY [ 3.579s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g845-00023-180917-B-5014671
(bootloader) Flashing partition modem_a
OKAY [ 0.425s]
Finished. Total time: 4.187s
rebooting into bootloader OKAY [ 0.050s]
Finished. Total time: 0.051s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: b1c1-0.1-5004167
Baseband Version.....: g845-00023-180917-B-5014671
Serial Number........: 8A2Y0E0CS
--------------------------------------------
Checking product OKAY [ 0.060s]
Checking version-bootloader OKAY [ 0.059s]
Checking version-baseband OKAY [ 0.059s]
extracting boot.img (64 MB) to disk... took 0.245s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.024s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
extracting product.img (194 MB) to disk... took 0.691s
archive does not contain 'product.sig'
archive does not contain 'product-services.img'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (2158 MB) to disk... took 10.997s
archive does not contain 'system.sig'
extracting system_other.img (418 MB) to disk... took 2.277s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (445 MB) to disk... took 2.150s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
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_a' (65536 KB) OKAY [ 1.586s]
Writing 'boot_a' OKAY [ 0.318s]
Sending 'dtbo_a' (8192 KB) OKAY [ 0.271s]
Writing 'dtbo_a' OKAY [ 0.100s]
Sending 'product_a' (199620 KB) OKAY [ 5.847s]
Writing 'product_a' OKAY [ 0.919s]
Sending sparse 'system_a' 1/9 (262140 KB) OKAY [ 10.910s]
Writing sparse 'system_a' 1/9 OKAY [ 0.363s]
Sending sparse 'system_a' 2/9 (262140 KB) OKAY [ 9.863s]
Writing sparse 'system_a' 2/9 OKAY [ 0.364s]
Sending sparse 'system_a' 3/9 (262140 KB) OKAY [ 12.823s]
Writing sparse 'system_a' 3/9 OKAY [ 0.366s]
Sending sparse 'system_a' 4/9 (262140 KB) OKAY [ 10.361s]
Writing sparse 'system_a' 4/9 OKAY [ 0.322s]
Sending sparse 'system_a' 5/9 (262140 KB) OKAY [ 9.411s]
Writing sparse 'system_a' 5/9 OKAY [ 0.364s]
Sending sparse 'system_a' 6/9 (262140 KB) OKAY [ 10.273s]
Writing sparse 'system_a' 6/9 OKAY [ 0.366s]
Sending sparse 'system_a' 7/9 (262140 KB) OKAY [ 10.251s]
Writing sparse 'system_a' 7/9 OKAY [ 0.365s]
Sending sparse 'system_a' 8/9 (258820 KB) OKAY [ 16.452s]
Writing sparse 'system_a' 8/9 OKAY [ 0.365s]
Sending sparse 'system_a' 9/9 (116824 KB) OKAY [ 5.003s]
Writing sparse 'system_a' 9/9 OKAY [ 0.870s]
Sending sparse 'system_b' 1/2 (262140 KB) OKAY [ 16.649s]
Writing sparse 'system_b' 1/2 OKAY [ 0.365s]
Sending sparse 'system_b' 2/2 (166548 KB) OKAY [ 10.722s]
Writing sparse 'system_b' 2/2 OKAY [ 1.139s]
Sending 'vbmeta_a' (4 KB) OKAY [ 0.120s]
Writing 'vbmeta_a' OKAY [ 0.066s]
Sending sparse 'vendor_a' 1/2 (262140 KB) OKAY [ 16.260s]
Writing sparse 'vendor_a' 1/2 OKAY [ 0.366s]
Sending sparse 'vendor_a' 2/2 (193888 KB) FAILED (Error reading sparse file)
Finished. Total time: 198.246s
Press any key to exit...
I've had the phone for all of less than 12 hours.... are you friggin kidding me? Any help??
raleighirishman said:
Alright, I got the device is corrupt error as well because of force of habit i mistakenly installed twrp.....
So I was trying to avoid wiping the data, and removed -w from the flash-all.bat. But I got the error again. Step two I used the flash-all.bat with -w to wipe.
The following are my results. The error "FAILED (Error reading sparse file)" appears at the end.
I've had the phone for all of less than 12 hours.... are you friggin kidding me? Any help??
Click to expand...
Click to collapse
Update your sdk tools.
c_86 said:
Update your sdk tools.
Click to expand...
Click to collapse
Alright it is a new laptop but I was pretty sure it was up-to-date.... although given the error I could be wrong. If any problems persist I'll be back.
Thanks for the heads up!
---------- Post added at 04:08 AM ---------- Previous post was at 04:05 AM ----------
c_86 said:
Update your sdk tools.
Click to expand...
Click to collapse
Yeah, I did have the newest version. Tried it again, and the same result. So currently researching anything I can while sitting in fastboot mode.
raleighirishman said:
Alright it is a new laptop but I was pretty sure it was up-to-date.... although given the error I could be wrong. If any problems persist I'll be back.
Thanks for the heads up!
---------- Post added at 04:08 AM ---------- Previous post was at 04:05 AM ----------
Yeah, I did have the newest version. Tried it again, and the same result. So currently researching anything I can while sitting in fastboot mode.
Click to expand...
Click to collapse
Flash the boot.img to both slots. boot_a and boot_b.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Flash the boot.img to both slots. boot_a and boot_b.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Alright, so I began to flash the boot image to each of the slots. But it keeps failing at vendor_a each time. It couldn't be the file, is it my device at this point??
--------
Welp I saw it all over the place that people seemed to just use their friends pc and it worked. So I said screw it. Put down the laptop, went to the desktop. Sure as anything. It flashed the phone no problem and fixed the boot loop. I don't get why, the cable is the same, the files are the exact same... but it worked!
raleighirishman said:
Alright, so I began to flash the boot image to each of the slots. But it keeps failing at vendor_a each time. It couldn't be the file, is it my device at this point??
--------
Welp I saw it all over the place that people seemed to just use their friends pc and it worked. So I said screw it. Put down the laptop, went to the desktop. Sure as anything. It flashed the phone no problem and fixed the boot loop. I don't get why, the cable is the same, the files are the exact same... but it worked!
Click to expand...
Click to collapse
Are you using usb c to usb c cable? I had the same problem and error when I was. If you are switch to a usb a to usb c and try it all again, it worked once I switched cables.
Scratch that just read your edit at the bottom that you used the same cable lol.
I got the same probleme, how did you reset your pixel? I have pixel 3 xl 32gb and i tried to go on recovery mode and idn't work, its go on the page what its say : Your device is corrupt. Its can't be trusted and may not work propely. Visit this link on another device: go.co/ahb
Hope have some help
I have flashed the phone but the error has come back after a few weeks of use... I'm starting to feel like this could be a hardware issue. I am still getting the phone freezing every so often and it doesn't even reboot correctly I have to hold power and volume down to turn the phone on. Something definitely isn't right.
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?
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
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