Database Info

Error 70 when trying to install GAPPS

Hi people
Yesterday I updated my phone to CyanogenMod(CM)13.0 which went fine. However when I rebooted the phone a popup came up the entire time telling me that google play services stopped working. In an attempt to fix it, I accidently removed google play services, causing a bunch of trouble at the moment.
I went to the CM Wiki and first I downloaded the "nano" variant of the GAPPS, trying to fix everything in the end. I put the file on my phone and tried to install it via recovery. This message came up however:
Insufficiënt storage space available in system partition. You may want to use a smaller GAPPS package or consider removing some apps using GAPPS-config ( bla bla) Error code 70.
As far as I can see, it is able to mount /system and /data, but the partition does not seem to have enough space left, at least so it says.
After that I tried the same with the "pico" variant, which also gave the same result. Pretty strange for a package that small.
So after taking a backup of important files I tried to wipe data/factory reset (was going to reinstall everything), to which I got an error "data wipe failed", which is correct since I can still boot in CM13 after that.
So I'm a bit in trouble here. I cannot seem to wipe my phone entirely, nor am I able to reinstall GAPPS due to this error 70.
Could this be a permissions problem somehow?
Things I have done so far to check what the problem could be:
- I've checked the space left on the /system partition which is 501 MB. Should be enough I guess?
- I've checked the /system partition for errors via adb shell while the phone was in recovery mode, which came out clean.
Below a picture of output of "mount", "df -h" and "uname -a" for extra information.
{
"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"
}
Thanks

Was the phone dirty flashed from an older cm13 rom or was it dirty flashed over a non-cm13 rom?

What do you mean with dirty flashed?
i got this Phone from a friend and the Original stock rom was installed. I installed Cyanogenmod together with gapps and everything went fine back then.

Dirty flashing is referred to as the installation of a new rom without wiping the previous rom prior to installation of the new rom.
If the stock rom was LP or kk and cm13 is installed via dirty flash, it is likely, based on my on experience, that the phone will hang at the boot screen.

audit13 said:
Dirty flashing is referred to as the installation of a new rom without wiping the previous rom prior to installation of the new rom.
If the stock rom was LP or kk and cm13 is installed via dirty flash, it is likely, based on my on experience, that the phone will hang at the boot screen.
Click to expand...
Click to collapse
The Phone is working perfectly on its own, except for the google-applications.
That is the reason I only need GApps, to repair the initial problem.
Would it be a solution to format /data and /system and start all over? Although i'm worried that I will still not be able to install GApps due to error 70...

I agree that it may be simpler to start over by flashing a stock Mm rom, erasing userdata in fastboot, flash userdata.img in fastboot, make sure it boots, install twrp, install cm13, no then gapps.

Which recovery do you use? TWRP or CWM?
Which build date of open gapps have you tried? The latest one?

audit13 said:
I agree that it may be simpler to start over by flashing a stock Mm rom, erasing userdata in fastboot, flash userdata.img in fastboot, make sure it boots, install twrp, install cm13, no then gapps.
Click to expand...
Click to collapse
It started installing after I initiated the flash-all command. This is the output. i downloaded the correct image and searched the net to know how I had to work with fastboot and such.
W/ ( 6228): Zip: unable to truncate file to 1044902952: File too large
failed to extract 'system.img': I/O Error
Press any key to exit...
The full log:
D:\temp\Hammerhead>flash-all.bat
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.314s]
writing 'bootloader'...
OKAY [ 0.536s]
finished. total time: 0.852s
rebooting into bootloader...
OKAY [ 0.107s]
finished. total time: 0.110s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.733s]
writing 'radio'...
OKAY [ 3.121s]
finished. total time: 4.858s
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.046s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
W/ ( 6228): Zip: unable to truncate file to 1044902952: File too large
failed to extract 'system.img': I/O Error
Press any key to exit...
So, again something about the file being to large. I locked and unlocked the lock state of my phone to make sure it would remove data, to get more space. I guess it did not really work.
Anything else I can do?

Here's the output when I flash mmb29s t0 my 16 GB Nexus 5:
D:\Downloads\Nexus 5\Nexus 5 Stock 6.01\hammerhead-mmb29s-factory-6bfcdfa4\hamme
rhead-mmb29s>flash-all
sending 'bootloader' (3120 KB)...
OKAY [ 0.306s]
writing 'bootloader'...
OKAY [ 0.542s]
finished. total time: 0.849s
rebooting into bootloader...
OKAY [ 0.126s]
finished. total time: 0.126s
sending 'radio' (45425 KB)...
OKAY [ 1.640s]
writing 'radio'...
OKAY [ 3.122s]
finished. total time: 4.762s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.125s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12k
Baseband Version.....: M8974A-2.0.50.2.28
Serial Number........: 050db890002e8xxx
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (9154 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.774s]
sending 'recovery' (10012 KB)...
OKAY [ 0.565s]
writing 'recovery'...
OKAY [ 0.824s]
sending 'system' (1020413 KB)...
OKAY [ 32.200s]
writing 'system'...
OKAY [ 68.826s]
erasing 'userdata'...
OKAY [ 8.696s]
erasing 'cache'...
OKAY [ 0.630s]
rebooting...
finished. total time: 113.718s
Press any key to exit...
I noticed your commands do not include the phone's installed baseband, bootoader, or serial number. Were these edited out before you posted the results?

audit13 said:
Here's the output when I flash mmb29s t0 my 16 GB Nexus 5:
D:\Downloads\Nexus 5\Nexus 5 Stock 6.01\hammerhead-mmb29s-factory-6bfcdfa4\hamme
rhead-mmb29s>flash-all
sending 'bootloader' (3120 KB)...
OKAY [ 0.306s]
writing 'bootloader'...
OKAY [ 0.542s]
finished. total time: 0.849s
rebooting into bootloader...
OKAY [ 0.126s]
finished. total time: 0.126s
sending 'radio' (45425 KB)...
OKAY [ 1.640s]
writing 'radio'...
OKAY [ 3.122s]
finished. total time: 4.762s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.125s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12k
Baseband Version.....: M8974A-2.0.50.2.28
Serial Number........: 050db890002e8xxx
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (9154 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.774s]
sending 'recovery' (10012 KB)...
OKAY [ 0.565s]
writing 'recovery'...
OKAY [ 0.824s]
sending 'system' (1020413 KB)...
OKAY [ 32.200s]
writing 'system'...
OKAY [ 68.826s]
erasing 'userdata'...
OKAY [ 8.696s]
erasing 'cache'...
OKAY [ 0.630s]
rebooting...
finished. total time: 113.718s
Press any key to exit...
I noticed your commands do not include the phone's installed baseband, bootoader, or serial number. Were these edited out before you posted the results?
Click to expand...
Click to collapse
Non, they were not edited out. They just did not show up.
Ok, I got the Android stock rom installed on the phone, but now something else is wrong. here is what i did:
Code:
D:\temp\Hammerhead>fastboot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.632s]
sending 'system' (1020413 KB)...
OKAY [ 33.134s]
writing 'system'...
OKAY [ 68.970s]
finished. total time: 102.738s
D:\temp\Hammerhead>fastboot flash data data.img
error: cannot load 'data.img'
D:\temp\Hammerhead>fastboot flash data userdata.img
target reported max download size of 1073741824 bytes
sending 'data' (137318 KB)...
OKAY [ 4.556s]
writing 'data'...
FAILED (remote: partition table doesn't exist)
finished. total time: 4.745s
D:\temp\Hammerhead>fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.489s]
sending 'cache' (13348 KB)...
OKAY [ 0.647s]
writing 'cache'...
OKAY [ 1.074s]
finished. total time: 2.215s
D:\temp\Hammerhead>fastboot flash boot boot.img
target reported max download size of 1073741824 bytes
sending 'boot' (9156 KB)...
OKAY [ 0.481s]
writing 'boot'...
OKAY [ 0.774s]
finished. total time: 1.260s
I first erased the partitions "system", "data" and "cache". After that I flashed "system", "userdata", "cache", and lastly "boot"
The phone booted into the rom, I entered my PIN, after which it complained my data was corrupt. It makes sense because of this:
"D:\temp\Hammerhead>fastboot flash data userdata.img
target reported max download size of 1073741824 bytes
sending 'data' (137318 KB)...
OKAY [ 4.556s]
writing 'data'...
FAILED (remote: partition table doesn't exist)
finished. total time: 4.745s"
It prolly needs the data partition to write stuff to.
Somehow the partition table of data seems to be gone.
So, the plot thickens! Is there a way I can recreate this partition table, or am I supposed to do something else?

fastboot flash userdata userdata.img
btw, nothing is wrong with your partition table, there is simply no partition on the phone called data. Data is part of userdata partition.

The commands are:
fastboot erase userdata
fastboot flash userdata userdata.img
The img file has to be extracted from the mmb29s zip file.

Damn, stupid I didn't see that.
I'll try again tonight and see how that goes.

GTCG said:
Damn, stupid I didn't see that.
I'll try again tonight and see how that goes.
Click to expand...
Click to collapse
Ok, I got it working again. Back on stock rom atm. Thanks for help everyone!

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] [Build 2] Elephone U Pro 09/05 Pixel Experience | Android 9.0 | Stable

{
"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"
}
Code:
#include
/*
* 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!
*/
Pixel Experience is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. Pixel Experience does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for Pixel Experience is available on the Pixel Experience Github repo. And if you would like to contribute to Pixel Experience , please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Attention! Your bootloader should be unlocked!
Treble unofficial builds of Pixel Experience (Android 9.0) for the Elephone U Pro​
Code:
Changelog:
Fixed NFC
Fixed MTP
Fixed Camera
Fixed and optimized camera speed and quality
Working:
It is boots and hardware accelerated!
MTP
WiFi
Fast charging
Offline charging
GPS
AGPS
Vibration
Audio
Auto brightness
Doze
RAM and ROM
Rotation
All sensors
Flashlight (Statusbar and Camera)
Bluetooth
Camera rear/front (Video and Photos)
Hdr in camera app
External SD
RIL for SMS/Calls/Internet/Lte on 1 and 2 SIM
Audio over Bluetooth ((a2dp)Music and etc)
Enforcing SELinux
Fingerprint Scanner
FM Radio
NFC (Payments, pairing)
And other
In progress:
Tell me
Download Pixel Experience:
Build 2:
https://drive.google.com/open?id=1EsiIQuFsIqzUvlo9i3nW68VJy7ij4Yqf
How to install Pixel Experience on your U Pro:
Reboot device in bootloader by next command in ADB shell.
adb shell reboot bootloader
When device will be at Bootloader mode write next commands:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot --set-active=a
Reboot to recovery (on green droid press power and vol up buttons shortly), make wipe data factory reset.
Reboot device.
Sources:
Pixel Experience is open source project
Thanks to:
CyanogenMod team
Pixel Experience team
Appendix:
If you want to mirror the files or port the ROM to another device, I encourage you to do so! Only please respect my work and give proper credits. Thank you!
XDA:DevDB Information
Pixel Experience P, ROM for all devices (see above for details)
Contributors
Deepflex
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Created 2018-09-08
Last Updated 2018-09-16​

Nice rom, thanks.

New version released.
Now ROM is stable. All fixed. About other bugs tell me here

Look forward to this. Is there a telegram group to test?

Hello!
I am having issues when installing like described above.
After step flash system.img and trying to flash vendor.img I get no response from phone only a reboot into bootloader let me proceed
same with step fastboot --set-active=a
Once done the phone does not boot into the ROM
Later I got the tip from Skeleton just to flash system.img
I did so - but then I do not have WIFI at all
any help here?
thank you

Finally I could make itto work
but Hotspot is not working

Locked bootloader
Quite a newbie here:
So, If my bootloader is locked, I need to follow this guide https://forum.xda-developers.com/android/general/guide-elephone-pro-how-to-lock-unlock-t3799667 and unlock it first, right?
Thanks for your work, Deepflex.

I am getting this code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.480s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.515s
C:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system_b'...
FAILED (remote: unknown command)
finished. total time: 0.004s
C:\adb>fastboot flash vendor vendor.img
target reported max download size of 536870912 bytes
sending 'vendor' (521614 KB)...
OKAY [ 13.037s]
writing 'vendor'...
FAILED (remote: unknown command)
finished. total time: 13.045s
C:\adb>fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote: unknown command)
finished. total time: 0.006s
Looks like partitions problem. Bootloader unlocked using this https://forum.xda-developers.com/android/general/guide-elephone-pro-how-to-lock-unlock-t3799667. Version now is 20180917.

DaGo68 said:
I am getting this code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.480s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.515s
C:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system_b'...
FAILED (remote: unknown command)
finished. total time: 0.004s
C:\adb>fastboot flash vendor vendor.img
target reported max download size of 536870912 bytes
sending 'vendor' (521614 KB)...
OKAY [ 13.037s]
writing 'vendor'...
FAILED (remote: unknown command)
finished. total time: 13.045s
C:\adb>fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote: unknown command)
finished. total time: 0.006s
Looks like partitions problem. Bootloader unlocked using this https://forum.xda-developers.com/android/general/guide-elephone-pro-how-to-lock-unlock-t3799667. Version now is 20180917.
Click to expand...
Click to collapse
Did you manage to get a rom on it? Even i get same errors like you. Im stuck only in fastboot mode with no os. I also unlocked the bootloader using the link you provided but in vain.
---------- Post added at 11:44 PM ---------- Previous post was at 11:35 PM ----------
Deepflex said:
New version released.
Now ROM is stable. All fixed. About other bugs tell me here
Click to expand...
Click to collapse
I am getting this code like xda user(DaGo68):
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.480s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.515s
C:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system_b'...
FAILED (remote: unknown command)
finished. total time: 0.004s
C:\adb>fastboot flash vendor vendor.img
target reported max download size of 536870912 bytes
sending 'vendor' (521614 KB)...
OKAY [ 13.037s]
writing 'vendor'...
FAILED (remote: unknown command)
finished. total time: 13.045s
C:\adb>fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote: unknown command)
finished. total time: 0.006s
Looks like partitions problem. Bootloader unlocked using this https://forum.xda-developers.com/android/general/guide-elephone-pro-how-to-lock-unlock-t3799667. Version now is 20180917.
Any help to be able to boot a custom rom by getting fastboot flashing commands to work or stock rom at this point?

Dr23890 said:
Did you manage to get a rom on it? Even i get same errors like you. Im stuck only in fastboot mode with no os. I also unlocked the bootloader using the link you provided but in vain.
---------- Post added at 11:44 PM ---------- Previous post was at 11:35 PM ----------
I am getting this code like xda user(DaGo68):
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.480s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.515s
C:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system_b'...
FAILED (remote: unknown command)
finished. total time: 0.004s
C:\adb>fastboot flash vendor vendor.img
target reported max download size of 536870912 bytes
sending 'vendor' (521614 KB)...
OKAY [ 13.037s]
writing 'vendor'...
FAILED (remote: unknown command)
finished. total time: 13.045s
C:\adb>fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote: unknown command)
finished. total time: 0.006s
Looks like partitions problem. Bootloader unlocked using this https://forum.xda-developers.com/android/general/guide-elephone-pro-how-to-lock-unlock-t3799667. Version now is 20180917.
Any help to be able to boot a custom rom by getting fastboot flashing commands to work or stock rom at this point?
Click to expand...
Click to collapse
I am about to go back to full ROM 20180227. I hope I'd be able to do this via QFIL tool. Then I'll unlock bootloader and follow with TWRP and Android 9 ROM. Can someone confirm this is a good idea?

DaGo68 said:
I am about to go back to full ROM 20180227. I hope I'd be able to do this via QFIL tool. Then I'll unlock bootloader and follow with TWRP and Android 9 ROM. Can someone confirm this is a good idea?
Click to expand...
Click to collapse
I tried flashing the different variants of stock roms which successfully flashed via Qfil but was unable to boot in the rom. So far, my U Pro boots only to fastboot mode. When plugged in for charge, it goes in fastboot mode..
Any solution for this? :crying:

Dr23890 said:
I tried flashing the different variants of stock roms which successfully flashed via Qfil but was unable to boot in the rom. So far, my U Pro boots only to fastboot mode. When plugged in for charge, it goes in fastboot mode..
Any solution for this? :crying:
Click to expand...
Click to collapse
No, I have solution for this. I am looking for flashable zip or better QFIL version of this ROM. But I am afraid we will not get one.

Hello, I installed Eragon V10 first. superimposed on it I entered with the commands to overwrite only the files. on my cell phone it worked. in the step of the vendor it takes around 7 minutes without response. but it is normal. then the CMD responds. on the issue of wi-fi not working should be because you are not with the original ROM recovery. I tried to do root with the magisk and it worked out more or less. only that disabled the wi-fi. When I come back to the original recovery it returns everything to what is left without root access. Hope this helps.

Deepflex said:
New version released.
Now ROM is stable. All fixed. About other bugs tell me here
Click to expand...
Click to collapse
Hi, I installed this version of Android and I'm really enjoying it, but I've already tried several ways to do root and I can not make it work 100% the same in Eragon. so I realized the problem is that this ROM is encrypted at the root. When I install twrp as boot it asks for password. I have already checked and it is not the same as the user's password. do you have any news of how to do root and install magisk by twrp in this ROM?

Has this topic been discontinued?

Wi-Fi Mac 02:00:00:00:00
I was able to force the unlock of the rom that prevented the twrp from exploring the memory. being the twrp unlocked I installed the last version of the magisk but the problem that is happening now is that the wifi is not active. address mac 02: 00: 00: 00: 00. I researched the subject and made several attempts with the tips that I found but nothing solved.

this rom was giving me a lot of headache. I arrived until I had problems with the partitions. I preferred to go back to eragon v10.

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.

Development Paranoid Android Topaz Beta 1 - Pixel 7a

{
"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"
}
We are very excited to announce Paranoid Android Topaz, based on Android 13.
On the first launch, you’ll notice a clean setup with beautiful wallpapers from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhance the overall user experience. You can find all of the Paranoid Android wallpapers and many more in the Abstruct app from the PlayStore.
Our builds are based on the Code Linaro Organization Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features, performance, and stability. We are dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.
Notice
We kindly ask all of you that are in a position to donate anything, to help and support us so we can provide better and faster build releases, as well as increase the download speed of our servers, all looking for your enjoyment.
You can donate on the link below:
Donate
Device-specific issues
* You tell us
Requirements
Make sure you've latest platform tools for Android.
Download
You can always get our builds from our website Paranoid Android website
Note: Custom kernels are NOT supported and GMS is included!
Changelogs
Keep an eye on our Twitter account, @paranoidaospa, as we will be posting about new features getting included in the release builds, as well as links to betas for those devices that will get them. For more detailed information please have a look at the second post of this thread of each build changelog on the website.
Paranoid Android Topaz released
Instructions
- Unlock your bootloader, and in bootloader mode follow the next command
Bash:
fastboot update aospa-topaz-beta-*-image.zip
- After the reboot, factory reset the device (only required for the first time you flash Paranoid Android)
Kernel source.
Important / Useful links
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Download Channel (Telegram)
Paranoid Android Community (Telegram)
Cheers and #StayParanoid!

I think face unlock doesn't work, does it?

Saswata Chakraborty said:
I think face unlock doesn't work, does it?
Click to expand...
Click to collapse
It does work.

Ok Lets go.. We have AOSPA the holy grail of Custom Roms... Going by how smooth the UI and UX is on AOSPA on other devices, i bet its silky smooth in Pixel 7A

aniketh12 said:
Ok Lets go.. We have AOSPA the holy grail of Custom Roms... Going by how smooth the UI and UX is on AOSPA on other devices, i bet its silky smooth in Pixel 7A
Click to expand...
Click to collapse
It definitely feels atleast as smooth as the stock ROM. maybe even smoother.

IDK what I'm doing wrong here, but I have the following error:
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Setting current slot to 'a' OKAY [ 0.071s]
fastboot: error: ANDROID_PRODUCT_OUT not set
Click to expand...
Click to collapse

treblechet said:
IDK what I'm doing wrong here, but I have the following error:
Click to expand...
Click to collapse
That's caused by some issues with the latest platform tools.
Download Platform Tools for Android SDK Manager
Download Android SDK Platform-tools 29.0.0 , 29.0.0 , 30.0.0 , 30.0.0 , 31.0.0 , 31.0.0 , 31.0.0 , 33.0.0 , 33.0.0 , 33.0.0 , 34.0.0 ,
androidsdkmanager.azurewebsites.net
Try using version 33 from here.

V3NK4135H said:
That's caused by some issues with the latest platform tools.
Download Platform Tools for Android SDK Manager
Download Android SDK Platform-tools 29.0.0 , 29.0.0 , 30.0.0 , 30.0.0 , 31.0.0 , 31.0.0 , 31.0.0 , 33.0.0 , 33.0.0 , 33.0.0 , 34.0.0 ,
androidsdkmanager.azurewebsites.net
Try using version 33 from here.
Click to expand...
Click to collapse
Ok, now this time around I would get further, it would yield
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Setting current slot to 'a' OKAY [ 0.066s]
extracting boot.img (64 MB) to disk... took 0.192s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.249s]
Writing 'boot_a' OKAY [ 0.096s]
extracting init_boot.img (8 MB) to disk... took 0.038s
archive does not contain 'init_boot.sig'
Sending 'init_boot_a' (8192 KB) OKAY [ 0.031s]
Writing 'init_boot_a' OKAY [ 0.021s]
extracting dtbo.img (16 MB) to disk... took 0.038s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (16384 KB) OKAY [ 0.062s]
Writing 'dtbo_a' OKAY [ 0.027s]
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.004s]
Writing 'pvmfw_a' OKAY [ 0.005s]
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' (8 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.003s]
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.003s]
extracting vendor_boot.img (64 MB) to disk... took 0.175s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_a' (65536 KB) OKAY [ 0.250s]
Writing 'vendor_boot_a' OKAY [ 0.094s]
extracting vendor_kernel_boot.img (64 MB) to disk... took 0.154s
archive does not contain 'vendor_kernel_boot.sig'
Sending 'vendor_kernel_boot_a' (65536 KB) OKAY [ 0.248s]
Writing 'vendor_kernel_boot_a' OKAY [ 0.096s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
Click to expand...
Click to collapse
It would then go to the recovery menu and the terminal would hang here, I would wipe and reboot, and the stock OS would come up. I ended up using the other file that was linked (the non-image one) and flashed that as well, which worked.

treblechet said:
Ok, now this time around I would get further, it would yield
It would then go to the recovery menu and the terminal would hang here, I would wipe and reboot, and the stock OS would come up. I ended up using the other file that was linked (the non-image one) and flashed that as well, which worked.
Click to expand...
Click to collapse
Well I'll look into the issues with the fastboot method. It did work fine for me and the testers but maybe something is missing. I'll check it. Thanks for the response.

A couple of things that I noticed right off the bat:
- the date and the time are slightly unaligned vertically in the notification drawer
- there is no option for changing app shapes in the default launcher
I don't know if the latter is a bug or just a lack of a feature, but since it was originally present in stock firmware I would assume it would be present in Topaz as well

fastboot and recovery mode both dont work for me.
can u please check it again?

BunkerBert said:
fastboot and recovery mode both dont work for me.
can u please check it again?
Click to expand...
Click to collapse
If its the Same build as 2 days ago the Fastboot Image should work. Tested it without problems.

treblechet said:
A couple of things that I noticed right off the bat:
- the date and the time are slightly unaligned vertically in the notification drawer
- there is no option for changing app shapes in the default launcher
I don't know if the latter is a bug or just a lack of a feature, but since it was originally present in stock firmware I would assume it would be present in Topaz as well
Click to expand...
Click to collapse
Try GrapheneOS. I am using it and yet to find a bug.

Is it possible to get a build of this ROM without gapps? I'd be also okay with building it myself, but wanted to see if it's possible at all before potentially wasting time.

Is it possible to install this ROM without ROOT?
I need ROOT so I can use Financial Apps like Wallet. When I root my phone I cant use the phone for making payments at a convenience store.

you can use the pixel flasher and patch the boot.img.
result is a prerooted boot.img which you can flash

Yea wallet is not working, and some security applications I can't download because of the incompliance. Phone is not rooted tho. Why wouldn't wallet work?
All in all, amazing butter smooth rom! I love it so far

i think you dont pass the safetynet check with custom roms.
there is a magisk modul to fix that -> https://github.com/kdrag0n/safetynet-fix
but for this you need root (magisk)