Database Info

Marshall London - Root, recovery and system images. - KB-1501 - Megathread

The Marshall London is no longer supported by Zound Industries and has been discontinued. Anything further will have to be done by developers and that seems unlikely. This thread and the files linked in this thread will remain online for those who have a Marshall London phone and need to restore and/or root their device.
---
Why this thread?
I have finally made enough progress with the Marshall London to where I feel comfortable enough posting a thread for this device. I doubt this device will ever get its own section considering how niche and relatively unknown it is... Aside from a couple of questions about root for this device, there's basically next to zero support on XDA (or anywhere else)... and I hope to change that. Hopefully people will be able to find this thread.
Some notes:
Extra special thanks to Dees_Troy for getting a working TWRP recovery for me to test out and use. Also extra thanks to autoprime. This basically wouldn't have happened without either of you two putting up with me on IRC.
Also thanks to Zound Industries for providing the stock fastboot flashable images for those who would be unable to take OTAs, as I wasn't able to for some reason.
I'm not a developer, just the one who managed to find the awesome folks to help me with all of this.
What is the Marshall London?
The Marshall London is a phone designed by Zound Industries with design elements licensed from Marshall. There was an emphasis put on sound quality and to be able to use the phone as a multi function media device. Two headphone jacks, front facing speakers that actually sound pretty good and are loud, Cirrus Logic Wolfson DAC, the ability to control volume levels for each headphone jack independently, the ability to use both headphone jacks as stereo INPUTS and to do 4 track recording on the device... It's a nifty little device hampered by poor performance from the Snapdragon 410 SOC in it. The phone is actually pretty awesome... and most of the issues go away once you make some tweaks.
Unfortunately, likely due to out of the box performance issues and cost... the phone never really took off. Even just using the phone as a high quality mp3 player resulted in issues (mostly lag) until I was able to find a way to pare down the system to only what I needed. My aim is to give people access to the tools they will need to be able to do this for themselves as well... but also to help people fix their device should something have been done that necessitates a return to stock.
Some reviews about the device to digest:
https://www.engadget.com/2015/09/12/marshall-london-review/
https://www.digitaltrends.com/cell-phone-reviews/marshall-london-review/
http://www.androidauthority.com/marshall-london-review-659269/
https://www.theverge.com/2015/7/16/8976561/marshall-london-smartphone-images
One of the best things about the device is its near completely stock Android software. Aside from visual tweaks (wallpapers, icons, word clock) the software is largely as you would find it from Google. As far as I know, the only real proprietary aspect of the phone is the audio DAC and "M-Button."
Specs:
Snapdragon 410 SOC in 64 Bit Mode (MSM8916)
2GB Ram
16GB Storage/NAND
Nano Sim Slot
MicroSD Slot that supports 128+GB cards
1280x720 Screen at 320 DPI
Cirrus Logic Wolfson DAC Hub
Dual Front Facing Speakers
Dual Headphones/Input Jacks
Programmable Shortcut "M-Button"
Volume Wheel
Removable Battery
8MP Rear Camera, 1080p Video recording mode
1.9MP Front/Selfie Camera, 720p Video recording mode
So yes, low average specs, even for when it was announced in 2015.
Where is it available?
Europe, mostly. It appears (in internal software memos) the device was tentatively planned for release in the US as an AT&T exclusive and it just never happened. If you're in the States like I am, you will have to import it or buy it used. Some ... ahem ... opportunistic people thought the relative scarcity of the product meant they could just buy one and try to resell it for double. You can easily import order (on eBay or Amazon) this device, brand new, for about $400 USD. I got mine from a store in Italy called E-Commerce World/Ghz Wireless and it arrived in 5 days. They were nice enough to include an EU to US power adapter in the package. Wherever you do find one, don't pay more than $500 for it. Marshall still has it for sale on their own site.
Where is it compatible?
Europe, mostly.
https://www.frequencycheck.com/models/vq2a7/marshall-london-4g-lte
https://www.marshallheadphones.com/mh_us_en/faq-london
GSM: 850, 900, 1800, 1900MHz
WCDMA Bands: 1/2/4/5/8
LTE Bands: 1/3/4/7/17/38/40
You might have some luck in the US with AT&T (bands 2, 4, 12, 17 for LTE) and AT&T based MVNOs or T-Mobile (bands 2, 4 and 12 for LTE) but I wouldn't count on it. Trying the phone in Colorado on an AT&T MVNO left me with only 2G service. I am unsure if additional bands are supported by the hardware but locked/limited in software. Hopefully this thread will spur some development and we can find out.
http://www.androidguys.com/2016/07/12/reference-guide-to-us-carrier-bands-and-networks/
Accessories?
Sadly, next to none. There's a nice leather flip case with a red velvet interior that was made for the phone (you don't slip it in, but rather another battery cover is stitched into the wallet itself)... but good luck finding one. Headphones, like the one that was boxed in with the phone itself, are available separately through Marshall's site.
What then?
Due to the lack of support, ANYWHERE, for this device, I enlisted the help of some folks to try to remedy that.
Here's what I know about the device:
It is not bootloader locked.
Fastboot is 100% standard. It shows up as a Google device and all commands are supported.
It is rootable. (I used Kingoroot initially, not recommended because it brought the system down to its knees with its bundled crapware)
A working custom recovery now exists for the device. As a result, this means you can root it from within recovery instead of relying on shady root tools.
This also means you can now use XPosed.
Goals for this device:
Stock images for flashing device back to 100% stock :good:
Rooted images for flashing (though may break OTA) :good:
100% working TWRP Recovery for backing up, flashing other roms, rooting the device with Magisk. (Magisk, since it modifies boot.img, also may break OTA) It will be mentioned several times, because it's that important, DO NOT use the TWRP built-in root/SuperSU installer. There is a reason the instructions say to use Magisk instead. :good:
Enough resources to allow for people to start developing custom roms for this device should anyone feel inclined. :good:
All goals met. :highfive:
Known issues:
Changing the DPI with build.prop editors won't work.
Changing the DPI using ADB (adb shell wm density ### && adb reboot) works but will break all Marshall apps: The onscreen buttons render right but cannot be activated. This means that if you want to use the device for music, you'll have to replace the stock music app (and freeze it to keep it from hijacking audio playback) for another one if you change the DPI to show more on the screen. I find 260 or 280 to be a reasonably good DPI value for both size and density of information. Default is 320.
This device cannot be rooted using the internal tool in TWRP Recovery. It will cause the device to hang on boot. Use Magisk instead.

To flash these images, you will need to use Fastboot. If you don't already have Fastboot installed, you can install Minimal ADB and Fastboot from this thread: https://forum.xda-developers.com/showthread.php?t=2317790
System Images
These are raw, stock, flashable in Fastboot only images. If you already have a custom recovery installed, then you can use that to flash these images instead. Bear in mind that flashing recovery.img while in recovery will replace your custom recovery with stock recovery.
The device ships with version R313.
persist.img : https://www.androidfilehost.com/?fid=745425885120742754
persist.img : md5 : 682275ff830598fa42a05250002cc02f
splash.img : https://www.androidfilehost.com/?fid=961840155545573563
splash.img : md5 : 1d56e5e62f27baf837084165694db52c
boot.img : https://www.androidfilehost.com/?fid=961840155545573562
boot.img : md5 : fe044e9ca9ccf7bdc4819500cfbffcda
recovery.img : https://www.androidfilehost.com/?fid=889764386195907755
recovery.img : md5 : 6b3b9e3b171a8f1151a60ae14e410b93
system.img : https://www.androidfilehost.com/?fid=745425885120740418
system.img : md5 : 4f6fef214ed162d921c85c5369f3454d
Version R403:
persist.img : https://www.androidfilehost.com/?fid=673368273298965596
persist.img : md5 : 10f983ad12dcf8452527bef513951ea5
splash.img : https://www.androidfilehost.com/?fid=817550096634777452
splash.img : md5 : 1d56e5e62f27baf837084165694db52c
boot.img : https://www.androidfilehost.com/?fid=745425885120740107
boot.img : md5 : e1d7f8875afb3a4a00602890a5b94ee7
recovery.img : https://www.androidfilehost.com/?fid=745425885120740108
recovery.img : md5 : 1d4da69e929119e85c68117fadc0484f
system.img : https://www.androidfilehost.com/?fid=817550096634777453
system.img : md5 : 7078ca8cd3ba8b7ba4e5baa94112e570
Version R412 is currently the latest version for the device:
persist.img : https://www.androidfilehost.com/?fid=817550096634780185
persist.img : md5 : 40e0e812ea0645fcd46c3136dc8f85a9
splash.img : https://www.androidfilehost.com/?fid=817550096634777468
splash.img : md5 : 1d56e5e62f27baf837084165694db52c
boot.img : https://www.androidfilehost.com/?fid=889764386195907458
boot.img : md5 : dac5a75fa41ddfe9da9186ea475ed707
recovery.img : https://www.androidfilehost.com/?fid=889764386195907459
recovery.img : md5 : 71aed500e670b7a81d6a7a43b7ae9ed0
system.img : https://www.androidfilehost.com/?fid=817550096634777469
system.img : md5 : a5b5001f9417ccc7e237661a01b2da38
How to flash:
1) Download all of the files for the version you want to flash.
2) Power off the device completely.
3) Enter fastboot mode by holding down the M-Button top of the phone and then holding down power until "FASTBOOT MODE" screen shows up.
4) Connect your phone to your computer. (This assumes you already have Fastboot and ADB installed and generally know how these tools work)
5) Use fastboot to flash each of the images to the correct partition: eg,
Code:
fastboot flash persist KB15_3_R403_160608_persist.img
fastboot flash splash KB15_3_R403_160608_splash.img
fastboot flash boot KB15_3_R403_160608_boot.img
fastboot flash recovery KB15_3_R403_160608_recovery.img
fastboot flash system KB15_3_R403_160608_system.img
6) Reboot.
First boot after flashing the system images will take some time as "Android is upgrading..." If you flashed version R412, you will be on the latest version. The older versions are provided for those who may have preferred them.
Custom Recovery
Before you install this recovery, it is very important to know that you MUST NOT let TWRP install SuperSU.
Download the latest TWRP from here: https://twrp.me/devices/marshalllondon.html
Older/Test build:
TWRP v3.1.1-0 : https://www.androidfilehost.com/?fid=745425885120740158
TWRP v3.1.1-0 : md5 : 05e61cbeb1afbc479d85f260acf52d3e
1) Download the TWRP image linked above.
2) Power off the device completely.
3) Enter fastboot mode by holding down the M-Button top of the phone and then holding down power until "FASTBOOT MODE" screen shows up.
4) Connect your phone to your computer. (This assumes you already have Fastboot and ADB installed and generally know how these tools work)
5) Use fastboot to flash:
Code:
fastboot flash recovery Marshall_London_TWRP_3_1_1-0.img
6) When fastboot is done, DO NOT reboot. Doing a fastboot reboot or fastboot reboot-bootloader will cause the system to overwrite TWRP with stock recovery. Pop the battery out instead.
7) Feel free to boot into recovery at this point to root or make backups. (Volume Wheel + Power for 4 seconds after you feel the power on buzz)
Rooting
Whatever you do, DO NOT allow TWRP to install SuperSU/Superuser/Root. Your device will fail to boot.
You must use Magisk. Magisk is systemless root and does not result in files being installed in /system, preventing the hang on boot.
Note: The versions that work for me are Magisk 13.3 and MagiskManager 5.1.1. If the latest don't work for you, download these older versions and try those instead.
Magisk 13.3: https://github.com/topjohnwu/Magisk/releases/download/v13.3/Magisk-v13.3.zip
Magisk Manager 5.1.1: https://github.com/topjohnwu/Magisk/releases/download/manager-v5.1.1/MagiskManager-v5.1.1.apk
Click to expand...
Click to collapse
1) Download both the Flashable ZIP and Magisk Manager APK.
2) Put both the ZIP and APK on a MicroSD card.
3) Turn off the phone, put the MicroSD card in.
4) Boot into TWRP Recovery by holding volume wheel down and power button down for about 4 seconds after you feel the power on vibration. Release the buttons.
5) TWRP Splash screen should pop up. Swipe to allow write.
6) Press "Install", "Select Storage", "Micro SDCard", "OK", scroll down to find Magisk-13.3.zip, press the file name and them Swipe to confirm Flash.
7) Reboot.
8) Once booted, you will need to use a file browser app, like Explorer by Speed Software, to find MagiskManager.apk on your MicroSD and install it. (Why? Cause it was removed from the Play Store.) This will require that Unknown Sources is enabled under Settings/Security.
---
Edit for 2021:
I have revived my London for some projects and ran into some issues trying to use modern methods/versions for the device.
I wanted to upgrade what I could and using Magisk v23 on the boot.img bootloops the device. I tried some lower Magisk versions and was met with the same result... so instead of fiddling with it I went back to my known working config on my second London and ripped the files to fix my first device.
As such, it is HIGHLY advised that you stick with v13.3 (known working version on both of my devices) for the image and v5.1.1 for Manager.
The necessary files for this config have been mirrored here:
Modified Marshall London R412 Boot Img with Magisk v13.3 (no recovery) applied:
https://www.androidfilehost.com/?fid=14943124697586343614
MD5: 23426a4a1d82f9a7465ba9a7cdf30e1f
Magisk Manager v5.1.1:
https://www.androidfilehost.com/?fid=14943124697586343616
MD5: 790c9d412e7afbd76566ee47f24cd3b8
To flash:
From a power-off state, hold M-Button and Power until "FASTBOOT MODE" shows up on the screen.
Connect phone to PC
"fastboot flash boot MLondon_Magisk_Boot.img"
You *MUST* be on Lollipop version R412 for this boot image.
This now means that if you are on version R412, all you need to do is flash the modified boot.img file to root your device instead of flashing recovery and applying the Magisk.zip inside TWRP. I do not have fastboot flashable files for the last firmware version for the Marshall London (titled "Tom Petty").
The alternative, of course, is to use TWRP and go through the steps listed above, but honestly, I've found TWRP to be largely unnecessary when you already have a Magisk patched boot image. This all is just being put here to preserve a working config.

Success!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

New notes for the "Tom Petty" final system update:
All of the above steps will work for flashing Magisk and getting root. No changes at all.
If you are having trouble booting after installing Magisk, reflash boot.img and use an older version. v13.3 worked best for me.

Thanks!
I own a london and I just want to thank you for putting this all together. I love the device, and use it as an audio player. I was also lucky enough to find one that came with the leather flip case.
There's an update availiable, and I'm assuming that it would prevent me from attempting the above modifications. Am I correct to hold off on "KB15_3_R412_170324"?

caltemus said:
I own a london and I just want to thank you for putting this all together. I love the device, and use it as an audio player. I was also lucky enough to find one that came with the leather flip case.
There's an update availiable, and I'm assuming that it would prevent me from attempting the above modifications. Am I correct to hold off on "KB15_3_R412_170324"?
Click to expand...
Click to collapse
The R412 update will not prevent you from being able to flash in Fastboot. They, thankfully, have not locked down the device. Some people had better luck with an older version and held off on updates but you now are able to revert to an older version if you feel like an update you took introduced issues. (eg, Lag)
If you need to up or downgrade, just use Fastboot to flash system.img and boot.img and reboot. I've been able to 'dirty flash' between system versions without having to wipe data.

Hello !
I am looking forward to root my Marshall London but I'm pretty new to android programmation & stuff
Is TWRP installed by default or do I need to install it myself ? Because when I hold the volume wheel and the power button, I get on "Android system recovery" and not TWRP.
If I have to install TWRP by myself, can someone send me a link for a tutorial or something ?
That's been more than a year I'm trying to root my phone, that'd be very kind of you if you can help me.
Lastly, I'd like to apologize if I made some mistakes as English isn't my native langage.
Thanks for anyone that is willing to help me !
Update : I have sucessfully rooted my London, any ideas where I can find custom ROMs for it ?

Can the 410 be over clocked and is anyone doing that?
Also, anyone installing apps on the microSD successfully?
Thanks!
Sent from my XT1095 using Tapatalk

Sancora said:
Update : I have sucessfully rooted my London, any ideas where I can find custom ROMs for it ?
Click to expand...
Click to collapse
There aren't any. This thread is the first to provide anything for this device.
eKeith said:
Can the 410 be over clocked and is anyone doing that?
Click to expand...
Click to collapse
Not without a custom kernel. There isn't one due to the lack of kernel source from Zound.

Thanks for the sharing. Your posting is very useful.

This is great, i did try to get hold of initial rom from the support, because with every update my phone broke more and more, but according to them they did not save old roms.
But for some reason i cant flash the files, only get "error: cannot load 'KB15_3_R403_160608_persist.img'" and the same for the other files.
Did forget that there is usually problem with long names, fixed by renaming.

The links to the system images doesn't seem to work they only say "no mirrors found"

Thanks!
Is it possible to build a own kernel for the phone?
I also tried to get the source from Zound Industries a few months ago with no luck.
I'm interested in creating a port to Ubuntu touch but I think a source for the kernel is required to do this.
This is something I would like to try to learn how it all works.

please new uploading brothers firmware version R412
i cant flashing system.img KB15_3_R412_170324_system error !!!!!!!!
please brothers can you help my please
this error
C:\adb> fastboot flash system C:\adb\KB15_3_R403_160608_system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 1.100s]
sending sparse 'system' (259594 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 11.399s

stuck on magisk manager
Hello and thank you for the great guide. I managed to do all the steps, but it seems my Marshall London is still not rooted. Am I supposed to open magisk manager and press install? If so it is not working, I get error: Unable to unpack boot image.
Thankful for all the help I can get.

Woah, seems like a nice thread to play with! Time to DIY repair my London?!
One question - how's yout GPS, guys? Been through 5 Latvia devices with nonexistent GPS performance. Please advise what can be done to solve this.

Hello,
i have marshall london with restart on logo
tried flash , wipe data
flashed ok but same condition
how to fix it ??
Code:
C:\Users\Syed Mobile\Desktop\marshall london>fastboot flash persist 1.img
target reported max download size of 268435456 bytes
sending 'persist' (4708 KB)...
OKAY [ 0.141s]
writing 'persist'...
OKAY [ 0.531s]
finished. total time: 0.688s
C:\Users\Syed Mobile\Desktop\marshall london>fastboot flash splash 2.img
target reported max download size of 268435456 bytes
sending 'splash' (2700 KB)...
OKAY [ 0.094s]
writing 'splash'...
OKAY [ 0.109s]
finished. total time: 0.203s
C:\Users\Syed Mobile\Desktop\marshall london>fastboot flash boot 3.img
target reported max download size of 268435456 bytes
sending 'boot' (24994 KB)...
OKAY [ 0.797s]
writing 'boot'...
OKAY [ 2.188s]
finished. total time: 2.985s
C:\Users\Syed Mobile\Desktop\marshall london>fastboot flash recovery 4.img
target reported max download size of 268435456 bytes
sending 'recovery' (25692 KB)...
OKAY [ 0.828s]
writing 'recovery'...
OKAY [ 0.422s]
finished. total time: 1.250s
C:\Users\Syed Mobile\Desktop\marshall london>fastboot flash system 5.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 1.531s]
sending sparse 'system' (259594 KB)...
OKAY [ 15.721s]
writing 'system'...
OKAY [ 17.299s]
sending sparse 'system' (261941 KB)...
OKAY [ 15.720s]
writing 'system'...
OKAY [ 20.596s]
sending sparse 'system' (259218 KB)...
OKAY [ 15.144s]
writing 'system'...
OKAY [ 21.081s]
sending sparse 'system' (251451 KB)...
OKAY [ 14.486s]
writing 'system'...
OKAY [ 19.768s]
sending sparse 'system' (257536 KB)...
OKAY [ 15.064s]
writing 'system'...
OKAY [ 19.924s]
sending sparse 'system' (258042 KB)...
OKAY [ 15.220s]
writing 'system'...
OKAY [ 21.252s]
sending sparse 'system' (206561 KB)...
OKAY [ 11.783s]
writing 'system'...
OKAY [ 16.252s]
finished. total time: 240.857s
C:\Users\Syed Mobile\Desktop\marshall london>fastboot reboot
rebooting...
finished. total time: 0.000s
C:\Users\Syed Mobile\Desktop\marshall london>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 6.251s]
finished. total time: 6.266s
C:\Users\Syed Mobile\Desktop\marshall london>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.125s]
finished. total time: 0.141s
C:\Users\Syed Mobile\Desktop\marshall london>fastboot reboot
rebooting...
finished. total time: 0.000s
C:\Users\Syed Mobile\Desktop\marshall london>
sorry ,
I did it wrong
i flashed it with lower version R313
let me download new version and post result here......

Hello,
flashed with latest version also , but same
restarting on logo...........
Code:
C:\Users\Syed Mobile\Downloads>fastboot flash persist KB15_3_R412_170324_persist
.img
target reported max download size of 268435456 bytes
sending 'persist' (4708 KB)...
OKAY [ 0.156s]
writing 'persist'...
OKAY [ 0.109s]
finished. total time: 0.266s
C:\Users\Syed Mobile\Downloads>fastboot flash splash KB15_3_R412_170324_splash.i
mg
target reported max download size of 268435456 bytes
sending 'splash' (2700 KB)...
OKAY [ 0.078s]
writing 'splash'...
OKAY [ 0.391s]
finished. total time: 0.469s
C:\Users\Syed Mobile\Downloads>fastboot flash boot KB15_3_R412_170324_boot.img
target reported max download size of 268435456 bytes
sending 'boot' (24940 KB)...
OKAY [ 0.797s]
writing 'boot'...
OKAY [ 2.031s]
finished. total time: 2.829s
C:\Users\Syed Mobile\Downloads>fastboot flash recovery KB15_3_R412_170324_recove
ry.img
target reported max download size of 268435456 bytes
sending 'recovery' (25636 KB)...
OKAY [ 0.984s]
writing 'recovery'...
OKAY [ 3.033s]
finished. total time: 4.705s
C:\Users\Syed Mobile\Downloads>
Code:
C:\Users\Syed Mobile\Downloads>fastboot flash system KB15_3_R412_170324_system.i
mg
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 1.486s]
sending sparse 'system' (259594 KB)...
OKAY [ 15.912s]
writing 'system'...
OKAY [ 18.228s]
sending sparse 'system' (257537 KB)...
OKAY [ 16.395s]
writing 'system'...
OKAY [ 20.591s]
sending sparse 'system' (262070 KB)...
OKAY [ 14.659s]
writing 'system'...
OKAY [ 20.581s]
sending sparse 'system' (253004 KB)...
OKAY [ 13.408s]
writing 'system'...
OKAY [ 19.851s]
sending sparse 'system' (257537 KB)...
OKAY [ 13.347s]
writing 'system'...
OKAY [ 20.599s]
sending sparse 'system' (258041 KB)...
OKAY [ 13.892s]
writing 'system'...
OKAY [ 19.853s]
sending sparse 'system' (250899 KB)...
OKAY [ 13.236s]
writing 'system'...
OKAY [ 20.315s]
finished. total time: 242.416s
C:\Users\Syed Mobile\Downloads>fastboot reboot
rebooting...
finished. total time: 0.016s
C:\Users\Syed Mobile\Downloads>

syed tuqeer said:
Hello,
flashed with latest version also , but same
restarting on logo...........
Click to expand...
Click to collapse
Try flashing the earliest version first and see if you can take updates within the phone itself. You may need to shorten filenames and ensure that none of the files you flash have spaces in the filename.

..

[ROM][11][OnePlus8] PixelExperience [AOSP]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for OnePlus8[instantnoodle]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 11
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
Nothing yet
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Device Specified Telegram Group
Our blog​
Android OS version: 11.0.0_r27
Security patch level: January 2021
Build author/Device Maintainer: Chandra
Device Source code: https://github.com/PixelExperience-Devices
Kernel Source code: https://github.com/PixelExperience-Devices/kernel_oneplus_sm8250
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
​

Changelog :
02-10-2020
- Initial Official Release

Reserved

Add here:
https://forum.xda-developers.com/oneplus-8/oneplus-8--8-pro-cross-device-development
Wysłane z mojego IN2013 przy użyciu Tapatalka

thank you sir！excited！

N I C E
Araa01 said:
Add here:
https://forum.xda-developers.com/oneplus-8/oneplus-8--8-pro-cross-device-development
Wysłane z mojego IN2013 przy użyciu Tapatalka
Click to expand...
Click to collapse
He can ask a mod to move the thread if this ROM is tested on both devices. If not it's better to keep it here.
And @chandra1.jd be careful using DevDB on xda, there will be some changes soon :
https://www.xda-developers.com/big-changes-to-xda-forums-are-coming-soon/

Wow!

It's exciting to see some custom rom development its been lacking thus far
why does it have to be done that way thru adb? maybe twrp flashable to come because i doubt I'll try to install it that way. I'm excited by the prospect of the rom very much but I'll let a few guinea pigs go first and keep tabs on this. Is the lack of custom rom development because developers are waiting for android 11 or what? One of the main reasons I decided on OP8 was because i thought the forum would be very active and its been kinda disappointing thus far. Does anyone know when theres gonna be the official android 11 update not this open beta bull****? also when an official twrp recovery?

sizzlemane727 said:
why does it have to be done that way thru adb? maybe twrp flashable to come because i doubt I'll try to install it that way. I'm excited by the prospect of the rom very much but I'll let a few guinea pigs go first and keep tabs on this. Is the lack of custom rom development because developers are waiting for android 11 or what? One of the main reasons I decided on OP8 was because i thought the forum would be very active and its been kinda disappointing thus far. Does anyone know when theres gonna be the official android 11 update not this open beta bull****? also when an official twrp recovery?
Click to expand...
Click to collapse
First of all, it has to be flashed through Fastboot because TWRP for Android 10 isn't really finished yet, devs have a hard time finding ways to comply with Android 10 new system, that's why there are a lot of those Fastboot ROMs.
Second of all, those "Guinea Pigs" are users that allows OP to release the official OOS build you're eager to have. You just wait for it to come and you call users who report bugs "Guinea Pigs"... Remember that those who install Open Betas are the ones that make this phone not a crappyy pile of bugs bad glitches, and represent the "active community" you're complaining of rn. Get off you high horse man...
Finally, the "lack of development" is indeed partially because devs are waiting for Android 11, and it has always been like that for every newly released OP phone. Once they age a bit that's when the amazing community comes together to build, to TEST, and finally release ROMs.

Looking good, however just like other roms RIL is broke on the t-mobile variant. Just hoping lol.

esjames said:
Looking good, however just like other roms RIL is broke on the t-mobile variant. Just hoping lol.
Click to expand...
Click to collapse
Actually t-mobile works on quartz it's just very laggy, I hope they get it working on this ROM I like this one!

Rom on EU variant works well. Sometimes get screen turning on from lock randomly but with kernel that is built into rom or smurfkernel so far so good. Thanks!

Someone, can tell me what type of camera app use the rom, stock or gcam? Because i prefer there is the stock camera app

Nice, for anyone who flashed the rom, have any of you flashed Magisk? And tried Google pay?

shaneg79 said:
Actually t-mobile works on quartz it's just very laggy, I hope they get it working on this ROM I like this one!
Click to expand...
Click to collapse
Oh nice, I did not know that! I tried a while back with the same. I hope it works soon here cause I love PE roms.
Thanks.

SUPERUSER said:
Nice, for anyone who flashed the rom, have any of you flashed Magisk? And tried Google pay?
Click to expand...
Click to collapse
Should work as long as you setup magisk.

5G Icon
When I'm On 5G It Shows G For Gsm It does not have a 5g icon like I have 2 apps indicating I'm on 5G NR any fix for that

I am not sure what I am doing wrong; I've made two attempts and flashed stock rom twice to reset to a clean table but both times I end up at an error flashing system.img
Not sure if checksum is correct after extracting it from the payload.bin or if its generating a hash on the go at this stage.
But this is what I have:
Code:
system.img
CRC32: 9D934E13
MD5: 062954A86F7D33A9FB846B3B67E266D6
SHA-1: A9D6E3A607B84346C8D53D000299FC0C372518ED
[COLOR=Green]C:\Users\Administrator\Downloads\2\PixelExperience_Plus_instantnoodle-10.0-20200926-0438-UNOFFICIAL>fastboot flash recovery recovery.img
Sending 'recovery' (98304 KB) OKAY [ 2.429s]
Writing 'recovery' OKAY [ 0.377s]
Finished. Total time: 2.828s
C:\Users\Administrator\Downloads\2\PixelExperience_Plus_instantnoodle-10.0-20200926-0438-UNOFFICIAL>fastboot flash boot boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.413s]
Writing 'boot_b' OKAY [ 0.328s]
Finished. Total time: 2.765s
C:\Users\Administrator\Downloads\2\PixelExperience_Plus_instantnoodle-10.0-20200926-0438-UNOFFICIAL>fastboot flash dtbo dtbo.img
Sending 'dtbo' (24576 KB) OKAY [ 0.599s]
Writing 'dtbo' OKAY [ 0.091s]
Finished. Total time: 0.705s
C:\Users\Administrator\Downloads\2\PixelExperience_Plus_instantnoodle-10.0-20200926-0438-UNOFFICIAL>fastboot --disable-verity flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.024s
C:\Users\Administrator\Downloads\2\PixelExperience_Plus_instantnoodle-10.0-20200926-0438-UNOFFICIAL>fastboot --disable-verity flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta_system' OKAY [ 0.003s]
Finished. Total time: 0.026s[/COLOR]
[COLOR=Green]C:\Users\Administrator\Downloads\2\PixelExperience_Plus_instantnoodle-10.0-20200926-0438-UNOFFICIAL>fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/2 (781483 KB) OKAY [ 18.047s]
Writing 'system'[/COLOR] [COLOR=Red]FAILED (remote: 'Partition not found')
fastboot: error: Command failed
[/COLOR][COLOR=Green]
C:\Users\Administrator\Downloads\2\PixelExperience_Plus_instantnoodle-10.0-20200926-0438-UNOFFICIAL>[/COLOR]

SUPERUSER said:
I am not sure what I am doing wrong; I've made two attempts and flashed stock rom twice to reset to a clean table but both times I end up at an error flashing system.img
Not sure if checksum is correct after extracting it from the payload.bin or if its generating a hash on the go at this stage.
But this is what I have:
Code:
system.img
CRC32: 9D934E13
MD5: 062954A86F7D33A9FB846B3B67E266D6
SHA-1: A9D6E3A607B84346C8D53D000299FC0C372518ED
[COLOR=Green]C:\Users\Administrator\Downloads\2\PixelExperience_Plus_instantnoodle-10.0-20200926-0438-UNOFFICIAL>fastboot flash recovery recovery.img
Sending 'recovery' (98304 KB) OKAY [ 2.429s]
Writing 'recovery' OKAY [ 0.377s]
Finished. Total time: 2.828s
C:\Users\Administrator\Downloads\2\PixelExperience_Plus_instantnoodle-10.0-20200926-0438-UNOFFICIAL>fastboot flash boot boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.413s]
Writing 'boot_b' OKAY [ 0.328s]
Finished. Total time: 2.765s
C:\Users\Administrator\Downloads\2\PixelExperience_Plus_instantnoodle-10.0-20200926-0438-UNOFFICIAL>fastboot flash dtbo dtbo.img
Sending 'dtbo' (24576 KB) OKAY [ 0.599s]
Writing 'dtbo' OKAY [ 0.091s]
Finished. Total time: 0.705s
C:\Users\Administrator\Downloads\2\PixelExperience_Plus_instantnoodle-10.0-20200926-0438-UNOFFICIAL>fastboot --disable-verity flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.024s
C:\Users\Administrator\Downloads\2\PixelExperience_Plus_instantnoodle-10.0-20200926-0438-UNOFFICIAL>fastboot --disable-verity flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta_system' OKAY [ 0.003s]
Finished. Total time: 0.026s[/COLOR]
[COLOR=Green]C:\Users\Administrator\Downloads\2\PixelExperience_Plus_instantnoodle-10.0-20200926-0438-UNOFFICIAL>fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/2 (781483 KB) OKAY [ 18.047s]
Writing 'system'[/COLOR] [COLOR=Red]FAILED (remote: 'Partition not found')
fastboot: error: Command failed
[/COLOR][COLOR=Green]
C:\Users\Administrator\Downloads\2\PixelExperience_Plus_instantnoodle-10.0-20200926-0438-UNOFFICIAL>[/COLOR]
Click to expand...
Click to collapse
did you enter fastboot to make it fastbootd to write system?

[REQUEST]
Plz add OTA support in this rom (I know that this a UNOFFICIAL ROM but plz if the OP is comfortable making updates for PE for OP8 then Plz add OTA support in it).

Development [ROM][OFFICIAL] LOS-Modded 19.1 [DISCONTINUED]

Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS Modded is a free, community built, aftermarket firmware distribution of Android 12 (S), which is designed to increase performance and reliability over stock Android for your device.
LineageOS Modded is based on the Android Open Source Project and LineageOS with extra contributions from many people within the Android community.
All the source code for LineageOS Modded is available in the LineageOS Modded Github repo.
Flashing Instructions:-
1. Download the OTA zip, copy partitions zip and boot image
2.
Code:
fastboot -w
3.
Code:
fastboot flash boot Lineage-Rec-Boot.img
4. Select ADB Sideload mode in Lineage Recovery
4.
Code:
adb sideload copy-partitions-20210323_1922.zip
5. Reboot back into Recovery and Select Sideload again
6.
Code:
adb sideload LineageOS-Modded-19.1-Osaka-V2-OTA.zip
7. Enjoy!
Bugs :
Permissive
3G only on Sprint/Boost
You tell me!!!
* Drop a comment down below if you need any help, you can also Join https://t.me/electimonrel on telegram if you need any help.
Downloads:
https://1pwn.ixmoe.com/android/osaka/Lineage-Rec-Boot.img
https://1pwn.ixmoe.com/android/osaka/LineageOS-Modded-19.1-Osaka-V2-OTA.zip
https://1pwn.ixmoe.com/android/copy-partitions-20210323_1922.zip
Contributors
@Electimon, @Androbots
Source Code: https://github.com/moto-sm4350
Version Information
Status: Stable
1/23/2022: lineage_osaka-img-eng.electimon-Jan-Week3 pushed
6/13/2022: Pushed new update, 19.1 and fixed GPS!
7/6/2022: Device tree is now available to support additional development

Electimon said:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS Modded is a free, community built, aftermarket firmware distribution of Android 12 (S), which is designed to increase performance and reliability over stock Android for your device.
LineageOS Modded is based on the Android Open Source Project and LineageOS with extra contributions from many people within the Android community.
All the source code for LineageOS Modded is available in the LineageOS Modded Github repo.
Make sure to wipe userdata, ensure you have at least taken one stock OTA!
Flashing Instructions:-
1. Download the zip
2.
Code:
fastboot -w
3.
Code:
fastboot update *Images*.zip
4. Reboot and enjoy!
Bugs :
Permissive
5G on Sprint/Boost
You tell me!!!
* Drop a comment down below if you need any help, you can also Join https://t.me/electimonrel on telegram if you need any help.
Downloads (LINEAGE LABELED):
https://2pwn.tk/android/osaka/weeklies/
Contributors
@Electimon, @Androbots
Source Code: https://github.com/moto-sm4350/kernel_motorola_osaka
Version Information
Status: Beta, Weekly builds, Important fixes will be released regardless of the week.
1/23/2022: lineage_osaka-img-eng.electimon-Jan-Week3 pushed
Click to expand...
Click to collapse
Great work

Thank you for this, you definitely made this device worth keeping

Is there anything you know of that doesn't work like calling/texting, any big deal breakers?

ShayBox said:
Is there anything you know of that doesn't work like calling/texting, any big deal breakers?
Click to expand...
Click to collapse
Nothing that I know about

Wait... this says osaka not denver, is this even for the this forums device? (Moto G Stylus 5G)
Spoiler
--------------------------------------------
getvar:version-bootloader FAILED (Status read failed (No such device))
getvar:version-baseband FAILED (Write to device failed (No such device))
getvar:serialno FAILED (Write to device failed (No such device))
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
getvarroduct FAILED (Write to device failed (No such device))
Checking 'product' FAILED
Could not getvar for 'product' (Write to device failed (No such device))
fastboot: error: requirements not met!
EDIT: The phone doesn't stay in the bootloader long enough to flash, it reboots every 30 seconds or so
EDIT2: Needs windows, linux just keeps resetting it, however now it gets to the rebooting to fastbootd step, it reboots into fastbootd (wrong product name, says osaka not denver), but fastboot update fails to recognise fastboot.
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
EDIT3: Apparently re-running the fastboot update in the now fastbootd bootloader successfully flashes it, woo.
So I'm guessing just normal magisk to root?

Osaka=Denver. Denver=Osaka.
5g isn't working on some variants. Check telegram for more information on this build.

Some more bugs to add, no sound (even alarms) and can't receive calls and texts for me, boost.

ShayBox said:
Some more bugs to add, no sound (even alarms) and can't receive calls and texts for me, boost.
Click to expand...
Click to collapse
Can you send a logcat

Just curious -- what's the reasoning for needing to have updated via OTA at least once?

xStealth said:
Just curious -- what's the reasoning for needing to have updated via OTA at least once?
Click to expand...
Click to collapse
From the factory Slot B partitions aren't filled so if you accidentally switch to it the SoC cannot have the secondary bootloader and you have yourself a brick

1. Newly bought Stylus 5g phone xt 2131 and tried to load lineage (Week 1, 2, 3)
2. bootloader unlocked
3. OTA update done (slot b filled)
4. fastboot -w
5. fastboot update lineage_osaka-img-eng.electimon-Jan-Week1.zip
6. reboot
Just getting a boot loop every time I restart it goes back to fastboot
I can get to fastbootd and have tried update their too.
Unable to load lineage
Any thoughts what i am doing wrong?

Where exactly does it bootloop, do you get to see the lineage fastbootd screen?

i have had similar issues

If you are running the fastboot update command it is normal it goes to fastbootd, watch the cmd for progress.

it says okay for all items.
finished. then reboots and brings me back to regular fastboot.

Can you show me a picture of the CMD window after it's completed? Thanks

extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Setting current slot to 'b' OKAY [ 0.247s]
extracting boot.img (96 MB) to disk... took 0.329s
archive does not contain 'boot.sig'
Sending 'boot_b' (98304 KB) OKAY [ 3.934s]
Writing 'boot_b' OKAY [ 1.373s]
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.009s]
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.001s]
Writing 'vbmeta_system_b' OKAY [ 0.005s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
Sending 'super' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.010s]
Resizing 'product_b' OKAY [ 0.005s]
Resizing 'system_b' OKAY [ 0.005s]
Resizing 'system_a' OKAY [ 0.006s]
Resizing 'vendor_b' OKAY [ 0.007s]
Resizing 'vendor_a' OKAY [ 0.006s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1347 MB) to disk... took 6.063s
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.018s]
Sending sparse 'product_b' 1/6 (262140 KB) OKAY [ 7.520s]
Writing 'product_b' OKAY [ 1.008s]
Sending sparse 'product_b' 2/6 (262140 KB) OKAY [ 7.528s]
Writing 'product_b' OKAY [ 0.984s]
Sending sparse 'product_b' 3/6 (262140 KB) OKAY [ 7.791s]
Writing 'product_b' OKAY [ 0.992s]
Sending sparse 'product_b' 4/6 (262140 KB) OKAY [ 7.725s]
Writing 'product_b' OKAY [ 0.995s]
Sending sparse 'product_b' 5/6 (262140 KB) OKAY [ 7.701s]
Writing 'product_b' OKAY [ 0.972s]
Sending sparse 'product_b' 6/6 (68820 KB) OKAY [ 2.047s]
Writing 'product_b' OKAY [ 0.358s]
archive does not contain 'product_services.img'
extracting system.img (894 MB) to disk... took 4.050s
archive does not contain 'system.sig'
Resizing 'system_b' OKAY [ 0.007s]
Sending sparse 'system_b' 1/4 (262140 KB) OKAY [ 7.921s]
Writing 'system_b' OKAY [ 1.010s]
Sending sparse 'system_b' 2/4 (262140 KB) OKAY [ 8.117s]
Writing 'system_b' OKAY [ 0.987s]
Sending sparse 'system_b' 3/4 (262140 KB) OKAY [ 8.095s]
Writing 'system_b' OKAY [ 0.992s]
Sending sparse 'system_b' 4/4 (129776 KB) OKAY [ 3.833s]
Writing 'system_b' OKAY [ 0.583s]
extracting system_other.img (0 MB) to disk... took 0.000s
archive does not contain 'system.sig'
Resizing 'system_a' OKAY [ 0.004s]
Sending 'system_a' (60 KB) OKAY [ 0.002s]
Writing 'system_a' OKAY [ 0.054s]
extracting vendor.img (756 MB) to disk... took 3.165s
archive does not contain 'vendor.sig'
Resizing 'vendor_b' OKAY [ 0.007s]
Sending sparse 'vendor_b' 1/3 (262140 KB) OKAY [ 7.768s]
Writing 'vendor_b' OKAY [ 1.002s]
Sending sparse 'vendor_b' 2/3 (262140 KB) OKAY [ 7.655s]
Writing 'vendor_b' OKAY [ 0.969s]
Sending sparse 'vendor_b' 3/3 (250144 KB) OKAY [ 7.864s]
Writing 'vendor_b' OKAY [ 0.952s]
archive does not contain 'vendor_other.img'
Rebooting OKAY [ 0.000s]
Finished. Total time: 142.573s

Hm, if you have the stock package handy (if not its available on lolinet) try running this command using vbmeta.img from stock
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

ran command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 7 Pro Support Thread.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the support thread of PixelFlasher
(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).
Note: This thread is meant for issues and problems faced in Google Pixel 7 Pro devices, generic issues that are device agnostic should be discussed in the main thread.
For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.
Troubleshooting:
If you need support or assistance, the best way to get is by generating a support file from within PixelFlasher.
You can hit that big Support button on the main screen, or select it from the Help menu.
The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.

Placeholder

Got Pixel 7 and Pixel 7 Pro (wife and me) on launch day. Both of us coming from 4 and 4 XL. Crazy how far things have come and continue to go. Love this community, and I'm sure I'm gonna love this tool too. Thanks OP!!

Great to see GUI Tool! Kudos

As soon as BB has my P7P in stock, I will then be taking this for a spin!! Thanks for making it compatible with P7P!!

Used the pre-release version without any issues. Thank you so much for this amazing tool! Let me know if you want to see any logs or anything of the process. This was also the first time I used the tool to have it actually wipe data and that worked as well, and I appreciate the double checking before the data is wiped. Good to know if you accidentally have it on wipe all data that it will prompt you before you make a mistake.

skaforey said:
Used the pre-release version without any issues. Thank you so much for this amazing tool! Let me know if you want to see any logs or anything of the process. This was also the first time I used the tool to have it actually wipe data and that worked as well, and I appreciate the double checking before the data is wiped. Good to know if you accidentally have it on wipe all data that it will prompt you before you make a mistake.
Click to expand...
Click to collapse
Thanks for the feedback, no need for files considering that it worked fine.
It helps to get the confirmation as I don't have a Pixel 7 / 7P device.

I managed to kill my Pixel. I went with the keep data option. Everything was good until it got to this
Sending sparse 'product_a' 11/11 (248408 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
rebooting to bootloader ...
Rebooting into bootloader FAILED (remote: 'Couldn't download data')
fastboot: error: Command failed
After this it went into a bootloop. I got out of bootloop and tried it again. This time i got these errors and no it won't boot. When connected to my computer it shows up as usb3. Tried to send commands to it and nothing, tried holding power button, power + up volume, power + down volume and nothing.
Resizing 'vendor_a' OKAY [ 0.003s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (2811 MB) to disk... took 24.746s
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.007s]
Sending sparse 'product_b' 1/11 (262116 KB) OKAY [ 6.766s]
Writing 'product_b' OKAY [ 0.354s]
Sending sparse 'product_b' 2/11 (262120 KB) OKAY [ 6.874s]
Writing 'product_b' OKAY [ 0.371s]
Sending sparse 'product_b' 3/11 (262128 KB) OKAY [ 6.851s]
Writing 'product_b' OKAY [ 0.358s]
Sending sparse 'product_b' 4/11 (262124 KB) OKAY [ 6.893s]
Writing 'product_b' OKAY [ 0.405s]
Sending sparse 'product_b' 5/11 (262116 KB) OKAY [ 6.719s]
Writing 'product_b' OKAY [ 0.365s]
Sending sparse 'product_b' 6/11 (262128 KB) OKAY [ 6.869s]
Writing 'product_b' OKAY [ 0.403s]
Sending sparse 'product_b' 7/11 (262128 KB) OKAY [ 6.899s]
Writing 'product_b' OKAY [ 0.359s]
Sending sparse 'product_b' 8/11 (262128 KB) OKAY [ 6.896s]
Writing 'product_b' OKAY [ 0.398s]
Sending sparse 'product_b' 9/11 (262140 KB) OKAY [ 6.909s]
Writing 'product_b' OKAY [ 0.362s]
Sending sparse 'product_b' 10/11 (262096 KB) OKAY [ 6.926s]
Writing 'product_b' OKAY [ 0.385s]
Sending sparse 'product_b' 11/11 (248408 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
rebooting to bootloader ...
Rebooting into bootloader FAILED (remote: 'Couldn't download data')
fastboot: error: Command failed
Sleeping 5-10 seconds ...

losticloud said:
I managed to kill my Pixel. I went with the keep data option. Everything was good until it got to this
Sending sparse 'product_a' 11/11 (248408 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
rebooting to bootloader ...
Rebooting into bootloader FAILED (remote: 'Couldn't download data')
fastboot: error: Command failed
After this it went into a bootloop. I got out of bootloop and tried it again. This time i got these errors and no it won't boot. When connected to my computer it shows up as usb3. Tried to send commands to it and nothing, tried holding power button, power + up volume, power + down volume and nothing.
Resizing 'vendor_a' OKAY [ 0.003s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (2811 MB) to disk... took 24.746s
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.007s]
Sending sparse 'product_b' 1/11 (262116 KB) OKAY [ 6.766s]
Writing 'product_b' OKAY [ 0.354s]
Sending sparse 'product_b' 2/11 (262120 KB) OKAY [ 6.874s]
Writing 'product_b' OKAY [ 0.371s]
Sending sparse 'product_b' 3/11 (262128 KB) OKAY [ 6.851s]
Writing 'product_b' OKAY [ 0.358s]
Sending sparse 'product_b' 4/11 (262124 KB) OKAY [ 6.893s]
Writing 'product_b' OKAY [ 0.405s]
Sending sparse 'product_b' 5/11 (262116 KB) OKAY [ 6.719s]
Writing 'product_b' OKAY [ 0.365s]
Sending sparse 'product_b' 6/11 (262128 KB) OKAY [ 6.869s]
Writing 'product_b' OKAY [ 0.403s]
Sending sparse 'product_b' 7/11 (262128 KB) OKAY [ 6.899s]
Writing 'product_b' OKAY [ 0.359s]
Sending sparse 'product_b' 8/11 (262128 KB) OKAY [ 6.896s]
Writing 'product_b' OKAY [ 0.398s]
Sending sparse 'product_b' 9/11 (262140 KB) OKAY [ 6.909s]
Writing 'product_b' OKAY [ 0.362s]
Sending sparse 'product_b' 10/11 (262096 KB) OKAY [ 6.926s]
Writing 'product_b' OKAY [ 0.385s]
Sending sparse 'product_b' 11/11 (248408 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
rebooting to bootloader ...
Rebooting into bootloader FAILED (remote: 'Couldn't download data')
fastboot: error: Command failed
Sleeping 5-10 seconds ...
Click to expand...
Click to collapse
This sounds like a flaky communication problem.
1- Support.zip file from PF's help menu greatly helps
2- Make sure you are only using SDK 33.0.3 anything older will not work
3- Make sure your connection to the PC is solid, and the fatsboot drivers are good
4- USB 2 connections are more reliable
When you scan for devices in PF, does it detect the phone? in any mode?
if yes, what mode is that?
I'm going to step out for a little while, but don't worry, your phone is not dead, it can be revived and I'll do my best to support you along the way when I'm back.

badabing2003 said:
This sounds like a flaky communication problem.
1- Support.zip file from PF's help menu greatly helps
2- Make sure you are only using SDK 33.0.3 anything older will not work
3- Make sure your connection to the PC is solid, and the fatsboot drivers are good
4- USB 2 connections are more reliable
When you scan for devices in PF, does it detect the phone? in any mode?
if yes, what mode is that?
I'm going to step out for a little while, but don't worry, your phone is not dead, it can be revived and I'll do my best to support you along the way when I'm back.
Click to expand...
Click to collapse
1. do you want me to post it here or PM to you?
2. I downloaded 33.0.3 before starting
3. drivers are good
4. I tried usb 2 connection but doesn't do anything. If i use the usb c cable that it came with it shows up as port com3
I tried scanning with PF and it doesn't detect the device at, I used both usb c and usb 2 cable.
If you can help great, if not I can always do RMA since i just got device. Thank you in advance
If you can help great, if not I can start RMA process. Thank you

Is this method keeping L1 and Safetynet?

K1nsey6 said:
Is this method keeping L1 and Safetynet?
Click to expand...
Click to collapse
Yes, the pixel no longer shows up. it also stopped booting, it's just dark.
Doing some searching i think its stuck in EDL mode and there's no recovery i have to return it or exchange it.

losticloud said:
Yes, the pixel no longer shows up. it also stopped booting, it's just dark.
Doing some searching i think its stuck in EDL mode and there's no recovery i have to return it or exchange it.
Click to expand...
Click to collapse
Holding down Power/Vol Up for 20 seconds isnt rebooting?

K1nsey6 said:
Holding down Power/Vol Up for 20 seconds isnt rebooting?
Click to expand...
Click to collapse
Nope, doesn't even vibrate.

badabing2003 said:
This sounds like a flaky communication problem.
...
4- USB 2 connections are more reliable
....
Click to expand...
Click to collapse
God is that still a thing?!?!?!
LOL, I remember when I first started rooting on my Pixel 2 XL, SOOOO many people were having issues using the USB-C connection, but once they used the legacy USB-A, things would suddenly work!
USB-C connections on a computer/laptop were still rather new-ish, so I figured that was the reason. I can't believe how many years later that this advice would still be relevant!

I started RMA I’ll try this again in a few weeks when I get new one.

losticloud said:
I started RMA I’ll try this again in a few weeks when I get new one.
Click to expand...
Click to collapse
Sorry to hear that you have to go through RMA, the logs help in trying to see if there are any hints on what might have happened, they are sanitized, ie any sensitive information is redacted, so you can safely post it here.
Have you tried Google's Android flash tool, I know if the phone isn't detected it can't help, but maybe they can detect EDL mode.

badabing2003 said:
Sorry to hear that you have to go through RMA, the logs help in trying to see if there are any hints on what might have happened, they are sanitized, ie any sensitive information is redacted, so you can safely post it here.
Have you tried Google's Android flash tool, I know if the phone isn't detected it can't help, but maybe they can detect EDL mode.
Click to expand...
Click to collapse
I did try but the phone wasn't detected. Files are attached.

losticloud said:
I did try but the phone wasn't detected. Files are attached.
Click to expand...
Click to collapse
Thanks,
It's interesting that you started with slot a, ran into the problem writing product 11/11
I'm assuming that the phone could no longer boot to slot a,
Because the next thing I see is the phone in bootloader mode with slot b being active, not sure why it would be in bootloader mode as slot b should have been intact, nothing was written to slot b yet.
I wonder if out of factory phones have both slots the same image.
Then you trying flashing again, again the exact same step of flashing product 11/11 it failed.
However unlike the first time, the phone was placed in bootloader mode on slot b.
I wonder if you were manually putting the phone into bootloader mode or it was eventually ending up in that state?
You tried yet another time, again on slot b, and again it failed on the exact same step.
After that we have no data, I suppose at that point you couldn't even put the phone in bootloader mode.
When you get your new device, I would strongly suggest that you inspect the USB cable, and also make sure the USB port is connected to the PC without a hub or anything, and preferably USB 2.
I know at this day and age it sounds silly, but the signs are failure in communication, or hardware problem.
If you search Google for similar problems, you'd find lots of cases where most of those are related to either the drivers, the cable or the USB port, here's one as an example.
Let us know how your phone goes, and best wishes.

New Release:
Oct 15, 2022 v4.3.0 release
New: You can now download and install alpha and delta Magisk versions in addition to the official stable, beta, canary and debug versions.
Bug fix: Generating support.zip file was modifying the main db file unnecessarily.
Bug fix: When patching with Magisk Manager the version of Magisk Manager was not being displayed in the boot images table.
Bug fix: MacOS downloaded Magisk had space in the file path, which was causing failed installation.

Question Android 14 Beta 1 factory image flash fails with error

# Phone Config
Pixel 7 Pro, running Android 14 DP2, Magisk 26.1.
I downloaded the 14 Beta 1 factory image today from the official site, and verified that the checksum matches.
Extracted the zip into my existing platform-tools folder (on Windows), removed the -w flag from the flash-all.bat and ran it. (After connecting the phone in bootloader mode to the computer via USB cable.)
Everything runs fine, until the very end, where it failed to flash the vendor img. Here's the full log -
Code:
Sending 'bootloader_a' (13927 KB) OKAY [ 0.109s]
Writing 'bootloader_a' (bootloader) Flashing pack version cloudripper-14.0-9701414
(bootloader) flashing platform gs201
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition partition:0
(bootloader) Validating partition partition:1
(bootloader) Validating partition partition:2
(bootloader) Validating partition partition:3
(bootloader) Validating partition bl1_a
(bootloader) Validating partition pbl_a
(bootloader) Validating partition bl2_a
(bootloader) Validating partition abl_a
(bootloader) Validating partition bl31_a
(bootloader) Validating partition tzsw_a
(bootloader) Validating partition gsa_a
(bootloader) Validating partition ldfw_a
(bootloader) Flashing partition ufs
(bootloader) Flashing partition ufs
(bootloader) Flashing partition partition:0
(bootloader) Flashing partition partition:1
(bootloader) Flashing partition partition:2
(bootloader) Flashing partition partition:3
(bootloader) Flashing partition bl1_a
(bootloader) Flashing partition pbl_a
(bootloader) Flashing partition bl2_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition bl31_a
(bootloader) Flashing partition tzsw_a
(bootloader) Flashing partition gsa_a
(bootloader) Flashing partition ldfw_a
(bootloader) Loading sideload ufsfwupdate
OKAY [ 0.262s]
Finished. Total time: 0.380s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.003s
< waiting for any device >
Sending 'radio_a' (111960 KB) OKAY [ 0.917s]
Writing 'radio_a' (bootloader) Flashing pack version g5300q-230217-230224-M-9650069
(bootloader) Flashing partition modem_a
OKAY [ 0.571s]
Finished. Total time: 1.496s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.004s
< waiting for any device >
--------------------------------------------
Bootloader Version...: cloudripper-14.0-9701414
Baseband Version.....: g5300q-230217-230224-B-9650069
Serial Number........: REDACTING
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'a' OKAY [ 0.080s]
extracting boot.img (64 MB) to disk... took 0.196s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.535s]
Writing 'boot_a' OKAY [ 0.231s]
extracting init_boot.img (8 MB) to disk... took 0.022s
archive does not contain 'init_boot.sig'
Sending 'init_boot_a' (8192 KB) OKAY [ 0.068s]
Writing 'init_boot_a' OKAY [ 0.015s]
extracting dtbo.img (16 MB) to disk... took 0.029s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (16384 KB) OKAY [ 0.139s]
Writing 'dtbo_a' OKAY [ 0.019s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.003s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_a' (1024 KB) OKAY [ 0.009s]
Writing 'pvmfw_a' OKAY [ 0.003s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (12 KB) OKAY [ 0.000s]
Writing 'vbmeta_a' OKAY [ 0.003s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system_a' OKAY [ 0.001s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_vendor_a' OKAY [ 0.002s]
extracting vendor_boot.img (64 MB) to disk... took 0.186s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_a' (65536 KB) OKAY [ 0.554s]
Writing 'vendor_boot_a' OKAY [ 0.075s]
extracting vendor_kernel_boot.img (64 MB) to disk... took 0.128s
archive does not contain 'vendor_kernel_boot.sig'
Sending 'vendor_kernel_boot_a' (65536 KB) OKAY [ 0.554s]
Writing 'vendor_kernel_boot_a' OKAY [ 0.080s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
Sending 'super' (5 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 1.039s]
Resizing 'product_a' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.002s]
Resizing 'system_dlkm_a' OKAY [ 0.002s]
Resizing 'system_ext_a' OKAY [ 0.003s]
Resizing 'system_b' OKAY [ 0.002s]
Resizing 'vendor_a' OKAY [ 0.003s]
Resizing 'vendor_dlkm_a' OKAY [ 0.003s]
Resizing 'vendor_b' OKAY [ 0.002s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (2925 MB) to disk... took 11.503s
archive does not contain 'product.sig'
Resizing 'product_a' OKAY [ 0.008s]
Sending sparse 'product_a' 1/12 (262112 KB) OKAY [ 0.996s]
Writing 'product_a' OKAY [ 0.753s]
Sending sparse 'product_a' 2/12 (262124 KB) OKAY [ 0.982s]
Writing 'product_a' OKAY [ 0.944s]
Sending sparse 'product_a' 3/12 (262128 KB) OKAY [ 0.966s]
Writing 'product_a' OKAY [ 1.011s]
Sending sparse 'product_a' 4/12 (262120 KB) OKAY [ 0.968s]
Writing 'product_a' OKAY [ 0.936s]
Sending sparse 'product_a' 5/12 (262124 KB) OKAY [ 0.979s]
Writing 'product_a' OKAY [ 1.052s]
Sending sparse 'product_a' 6/12 (262128 KB) OKAY [ 0.970s]
Writing 'product_a' OKAY [ 0.933s]
Sending sparse 'product_a' 7/12 (262124 KB) OKAY [ 0.984s]
Writing 'product_a' OKAY [ 1.052s]
Sending sparse 'product_a' 8/12 (262124 KB) OKAY [ 0.966s]
Writing 'product_a' OKAY [ 0.999s]
Sending sparse 'product_a' 9/12 (262128 KB) OKAY [ 0.971s]
Writing 'product_a' OKAY [ 1.063s]
Sending sparse 'product_a' 10/12 (262124 KB) OKAY [ 0.977s]
Writing 'product_a' OKAY [ 0.968s]
Sending sparse 'product_a' 11/12 (262092 KB) OKAY [ 0.968s]
Writing 'product_a' OKAY [ 0.819s]
Sending sparse 'product_a' 12/12 (102712 KB) OKAY [ 0.394s]
Writing 'product_a' OKAY [ 0.161s]
extracting system.img (899 MB) to disk... took 3.753s
archive does not contain 'system.sig'
Resizing 'system_a' OKAY [ 0.042s]
Sending sparse 'system_a' 1/4 (262116 KB) OKAY [ 1.028s]
Writing 'system_a' OKAY [ 0.526s]
Sending sparse 'system_a' 2/4 (262116 KB) OKAY [ 0.994s]
Writing 'system_a' OKAY [ 0.965s]
Sending sparse 'system_a' 3/4 (262140 KB) OKAY [ 0.972s]
Writing 'system_a' OKAY [ 1.174s]
Sending sparse 'system_a' 4/4 (131716 KB) OKAY [ 0.496s]
Writing 'system_a' OKAY [ 0.556s]
extracting system_dlkm.img (0 MB) to disk... took 0.001s
archive does not contain 'system_dlkm.sig'
Resizing 'system_dlkm_a' OKAY [ 0.006s]
Sending 'system_dlkm_a' (340 KB) OKAY [ 0.003s]
Writing 'system_dlkm_a' OKAY [ 0.045s]
extracting system_ext.img (256 MB) to disk... took 1.042s
archive does not contain 'system_ext.sig'
Resizing 'system_ext_a' OKAY [ 0.008s]
Sending sparse 'system_ext_a' 1/1 (262068 KB) OKAY [ 1.016s]
Writing 'system_ext_a' OKAY [ 0.939s]
extracting system_other.img (16 MB) to disk... took 0.086s
archive does not contain 'system.sig'
Resizing 'system_b' OKAY [ 0.011s]
Sending 'system_b' (17264 KB) OKAY [ 0.064s]
Writing 'system_b' OKAY [ 0.093s]
extracting vendor.img (699 MB) to disk... took 2.624s
archive does not contain 'vendor.sig'
Resizing 'vendor_a' OKAY [ 0.007s]
Sending sparse 'vendor_a' 1/3 (262120 KB) OKAY [ 0.996s]
Writing 'vendor_a' OKAY [ 1.194s]
Sending sparse 'vendor_a' 2/3 (262116 KB) OKAY [ 0.992s]
Writing 'vendor_a' OKAY [ 0.504s]
Sending sparse 'vendor_a' 3/3 (189388 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
Press any key to exit...
I noticed that the platform-tools was an old version (33.0.3). So, I downloaded the latest 34.0.0 RC2 from the Android developer site and reran the falsh-all.bat. This time, the flash fails with a different error (I'm not pasting the bootloader / radio part of the log here, as they were fine.) -
Code:
--------------------------------------------
Bootloader Version...: cloudripper-14.0-9701414
Baseband Version.....: g5300q-230217-230224-B-9650069
Serial Number........: REDACTING
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'a' OKAY [ 0.077s]
extracting boot.img (64 MB) to disk... took 0.186s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.529s]
Writing 'boot_a' OKAY [ 0.075s]
extracting init_boot.img (8 MB) to disk... took 0.020s
archive does not contain 'init_boot.sig'
Sending 'init_boot_a' (8192 KB) OKAY [ 0.069s]
Writing 'init_boot_a' OKAY [ 0.017s]
extracting dtbo.img (16 MB) to disk... took 0.028s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (16384 KB) OKAY [ 0.134s]
Writing 'dtbo_a' OKAY [ 0.019s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.004s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_a' (1024 KB) OKAY [ 0.009s]
Writing 'pvmfw_a' OKAY [ 0.003s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (12 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.001s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system_a' OKAY [ 0.002s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_vendor_a' OKAY [ 0.002s]
extracting vendor_boot.img (64 MB) to disk... took 0.173s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_a' (65536 KB) OKAY [ 0.542s]
Writing 'vendor_boot_a' OKAY [ 0.075s]
extracting vendor_kernel_boot.img (64 MB) to disk... took 0.122s
archive does not contain 'vendor_kernel_boot.sig'
Sending 'vendor_kernel_boot_a' (65536 KB) OKAY [ 0.553s]
Writing 'vendor_kernel_boot_a' OKAY [ 0.074s]
extracting super_empty.img (0 MB) to disk... took 0.001s
extracting product.img (2925 MB) to disk... took 10.295s
[liblp] Partition product_a will resize from 0 bytes to 3067695104 bytes
extracting system.img (899 MB) to disk... took 3.202s
[liblp] Partition system_a will resize from 0 bytes to 943325184 bytes
extracting system_dlkm.img (0 MB) to disk... took 0.001s
[liblp] Partition system_dlkm_a will resize from 0 bytes to 348160 bytes
extracting system_ext.img (256 MB) to disk... took 0.948s
[liblp] Partition system_ext_a will resize from 0 bytes to 269307904 bytes
extracting system_other.img (16 MB) to disk... took 0.074s
[liblp] Partition system_b will resize from 0 bytes to 17678336 bytes
extracting vendor.img (699 MB) to disk... took 7.555s
[liblp] Partition vendor_a will resize from 0 bytes to 733212672 bytes
extracting vendor_dlkm.img (42 MB) to disk... took 0.115s
[liblp] Partition vendor_dlkm_a will resize from 0 bytes to 44281856 bytes
archive does not contain 'vendor_other.img'
Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)
fastboot: error: Command failed
Press any key to exit...
Platform tools 34.0.0 RC2 throws this same error when trying to flash 14 DP2 too. Platform tools 33.0.3 flashes 14 DP2 fine.
Anyone else has faced this issue and knows a fix?

People have been having issues with Platform Tools 34 since its release. The only fix I know is to uninstall 34 and revert to installing 33.03. I haven't had any problems flashing the latest stable build on 33.03 and it looks like people have had success with flashing the latest Android 14 beta with it as well.

synesthete said:
People have been having issues with Platform Tools 34 since its release. The only fix I know is to uninstall 34 and revert to installing 33.03. I haven't had any problems flashing the latest stable build on 33.03 and it looks like people have had success with flashing the latest Android 14 beta with it as well.
Click to expand...
Click to collapse
I get the platform tools from here. The download is just a portable zip, not an installer needing any uninstall / install. I deleted the 34 RC2 download and went back to my previous 33.0.3 download. But through that too, I'm getting this error for 14B1 -
Code:
Sending sparse 'vendor_a' 3/3 (189388 KB) FAILED (Write to device failed (Unknown error))
14DP2 flashes fine with 33.0.3.

I got this also as did others in the Android 14 thread. I don't know what Google are on. First the platform tools bug which still isn't fixed and now this. I get and fully expect to run into issues within the OS itself, but not even being able to flash the build?
I'll laugh/cry if this also affects the non-pro and even the Pixel 6, but even without that just a single device failing flash seems like a complete amature mistake to have made.
We are all just going to have to avoid the build and hope someone at Google cares enough to fix it, or wee just wait until beta 2 next month I guess, and rely on having to use using OTA updates until then.

Dave_247 said:
I got this also as did others in the Android 14 thread.
Click to expand...
Click to collapse
Can you please give me a link to that thread?

Just use android flash tool to install this a14 beta
Working properly

cultofluna said:
Just use android flash tool to install this a14 beta
Working properly
Click to expand...
Click to collapse
I haven't used that before. Does that provide an option to flash without wipe or does that mandatorily wipe the device while flashing?

bagarwa said:
I haven't used that before. Does that provide an option to flash without wipe or does that mandatorily wipe the device while flashing?
Click to expand...
Click to collapse
Yes you can choose any option you want ..
With or without wipe/ or disable verity/ verification

cultofluna said:
Yes you can choose any option you want ..
With or without wipe/ or disable verity/ verification
Click to expand...
Click to collapse
I only used Android Flash Tool once, but I don't believe it could disable verity & verification...
Did you by chance mean badabing2003's PixelFlasher? I know for sure that that program does this, and it most likely can flash Android 14 as well...

cultofluna said:
Yes you can choose any option you want ..
With or without wipe/ or disable verity/ verification
Click to expand...
Click to collapse
I tried the flashing tool now, but that too kept failing, this time at flashing product 11/12.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But I finally managed to finish the flash on my local. I used a different USB C to C cable (previously I was using A to C) on a different port of the laptop. The file transfer from PC to phone (the "Sending sparse..." parts) were much slower this time (~6 seconds for each part, compared to less than 1 second before). But the flash finally successfully finished. And now I've booted into 14B1.

simplepinoi177 said:
I only used Android Flash Tool once, but I don't believe it could disable verity & verification...
Did you by chance mean badabing2003's PixelFlasher? I know for sure that that program does this, and it most likely can flash Android 14 as well...
Click to expand...
Click to collapse
You can disable verity/ verification with android flash tool
And i don't mean Pixel flasher

bagarwa said:
I tried the flashing tool now, but that too kept failing, this time at flashing product 11/12.
But I finally managed to finish the flash on my local. I used a different USB C to C cable (previously I was using A to C) on a different port of the laptop. The file transfer from PC to phone (the "Sending sparse..." parts) were much slower this time (~6 seconds for each part, compared to less than 1 second before). But the flash finally successfully finished. And now I've booted into 14B1.
Click to expand...
Click to collapse
Interesting, I always get 6 seconds using my C-to-C cable too.

bagarwa said:
Can you please give me a link to that thread?
Click to expand...
Click to collapse
Here's the thread. It was started folowingf the devloper preview versions of 14 but has not sahifted to the beta versions.
June 7, 2023 - Beta 3 UPB3.230519.008 Global - Android 14 "Upside Down Cake" - Pixel 7 Pro [Cheetah]
Android 14 Beta program for the Pixel 7 Pro [Cheetah] Download links in the middle of the OP. Welcome to the Android 14 Developer Preview! This first release is for developers only, to help with early development, testing, and feedback...
forum.xda-developers.com

cultofluna said:
Just use android flash tool to install this a14 beta
Working properly
Click to expand...
Click to collapse
bagarwa said:
I tried the flashing tool now, but that too kept failing, this time at flashing product 11/12.
View attachment 5887309
But I finally managed to finish the flash on my local. I used a different USB C to C cable (previously I was using A to C) on a different port of the laptop. The file transfer from PC to phone (the "Sending sparse..." parts) were much slower this time (~6 seconds for each part, compared to less than 1 second before). But the flash finally successfully finished. And now I've booted into 14B1.
Click to expand...
Click to collapse
I was getting the same error so I gave up and manually flashed the developer preview 2 then did a OTA update to get to Beta 1. There has to be something wrong with the build itself to be having this many issues for so many people.