Hi xda!
I can't flash system with TWRP or Fastboot
Fastboot:
Code:
C:\Users\manager\Desktop\coils\Nexus>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.741s]
sending sparse 'system' 1/4 (516666 KB)...
OKAY [ 17.776s]
writing 'system' 1/4...
FAILED (remote: size too large)
finished. total time: 18.557s
TWRP:
{
"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"
}
I try fastboot erase system
I try repair partition in TWRP
I try change filesystem to ext2 and back to ext4
I try in TWRP
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/system
and
Code:
make_ext4fs /dev/block/mmcblk0p41
Can any body help me with this problem?
Your fastboot is old. Get the latest one from the SDK.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
Your fastboot is old. Get the latest one from the SDK.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I have the latest version, I use this fastboot early and everything was fine
bzz11g said:
I have the latest version, I use this fastboot early and everything was fine
Click to expand...
Click to collapse
Obviously not. The error you are getting is due to an out of date fastboot.
Sent from my Nexus 5X using Tapatalk
piousinquisitor said:
obviously not. The error you are getting is due to an out of date fastboot.
Sent from my nexus 5x using tapatalk
Click to expand...
Click to collapse
IT'S LATEST VERSION
Code:
Microsoft Windows [Version 6.1.7601]
(c) Корпорация Майкрософт (Microsoft Corp.), 2009. Все права защищены.
C:\Users\manager\Desktop\Nexus>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.532s]
sending sparse 'system' 1/4 (516666 KB)...
OKAY [ 17.605s]
writing 'system' 1/4...
FAILED (remote: size too large)
finished. total time: 18.178s
C:\Users\manager\Desktop\Nexus>fastboot --version
fastboot version 8f855a3d9b35-android
C:\Users\manager\Desktop\Nexus>
When i had this problem, i had a bad download. Go redownload the image you are attempting to flash, make sure to check MD5. And where are you getting your fastboot drivers from?
I try redownload firmware and verifi сhecksum, all is good, but I continue to watch same error, can any body help?
bzz11g said:
I try redownload firmware and verifi сhecksum, all is good, but I continue to watch same error, can any body help?
Click to expand...
Click to collapse
Have you updated your platform tools? This new 7.0 system.img takes a while to flash and updating that helped me.
Sent from my Nexus 5X using Tapatalk
Try with:
fastboot flash -S 512M system system.img
i had this error with the nexus 5, fixed by flashing with -s 512m.
Make sure to download the latest platform-tools, pal
That'll fugure out your problem for sure. The do the fastboot and you're just gonna be fine. No reason to go around bushes. Follow the Root 5x thread.
SlimSnoopOS said:
Have you updated your platform tools? This new 7.0 system.img takes a while to flash and updating that helped me.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I try system.img from 7.0 and 6.0.1 and always get the same error
AtField said:
Try with:
fastboot flash -S 512M system system.img
i had this error with the nexus 5, fixed by flashing with -s 512m.
Click to expand...
Click to collapse
yes i try it in first time, without results...
2 All,
please look at the screenshot in first message with TWRP log, I think problem in system partition, other img (vendor, userdata, cache etc.) installed without problems
may be some body know how I can repair system partition across ADB Shell?
bzz11g said:
I try system.img from 7.0 and 6.0.1 and always get the same error
yes i try it in first time, without results...
2 All,
please look at the screenshot in first message with TWRP log, I think problem in system partition, other img (vendor, userdata, cache etc.) installed without problems
may be some body know how I can repair system partition across ADB Shell?
Click to expand...
Click to collapse
You tried with the added -S 512M ?
Because in the first screenshot i dont see that part of the command.
Anyway, if you already tried with -s 512m I'm sorry but I cant help you.
AtField said:
You tried with the added -S 512M ?
Because in the first screenshot i dont see that part of the command.
Anyway, if you already tried with -s 512m I'm sorry but I cant help you.
Click to expand...
Click to collapse
yes, i try this key's
if you look in log
Code:
target reported max download size of 536870912 bytes
it already 512 Mb
536870912 bytes / 1024 = 524288 kB / 1024 = 512 Mb
@bzz11g Issue the following command (after updating your fastboot, lol) and try again.
Code:
fastboot format system
note that there is a difference between erase and format.
Have you tried using the flash-all script?
If nothing else works use the TOT method to fix your phone.
@PiousInquisitor thank you for your note, I already try it..
I try install full stock with flash-all.bat and NRT, and always see the same error
Yesterday I can flash system.img with ADB shell and DD command:
Code:
ADB shell dd if=/sdcard/system.img of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/system
and everything went well, but I still in bootloop and see Google logo..
Can anybody make TWRP backup of system 6.0.1 for me?
bzz11g said:
@PiousInquisitor thank you for your note, I already try it..
I try install full stock with flash-all.bat and NRT, and always see the same error
Yesterday I can flash system.img with ADB shell and DD command:
Code:
ADB shell dd if=/sdcard/system.img of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/system
and everything went well, but I still in bootloop and see Google logo..
Can anybody make TWRP backup of system 6.0.1 for me?
Click to expand...
Click to collapse
You can't flash system.img that way. It isn't a standard .img file.
I don't know what is wrong with your setup, but if you want you can try fastboot from here
http://forum.xda-developers.com/nexus-5x/general/psa-fix-adb-doesnt-winxp-t3403955
I know for sure it has no problems flashing the NRD90M system.img as I did it a few days ago.
If that doesn't work, then the problem is not with fastboot or the usb dll that uses.
sfhub said:
You can't flash system.img that way. It isn't a standard .img file.
Click to expand...
Click to collapse
I know, I want try to restore System with TWRP
sfhub said:
I don't know what is wrong with your setup, but if you want you can try fastboot from here
http://forum.xda-developers.com/nexus-5x/general/psa-fix-adb-doesnt-winxp-t3403955
Click to expand...
Click to collapse
I try it now, thank you
@sfhub
Code:
C:\Users\manager\Desktop\platform-tools-v23.1>fastboot devices
0106fb608bc03dee fastboot
C:\Users\manager\Desktop\platform-tools-v23.1>fastboot -S 512M flash system syst
em.img
erasing 'system'...
OKAY [ 0.556s]
sending sparse 'system' (516666 KB)...
OKAY [ 17.587s]
writing 'system'...
FAILED (remote: size too large)
finished. total time: 18.170s
bzz11g said:
@sfhub
Code:
C:\Users\manager\Desktop\platform-tools-v23.1>fastboot devices
0106fb608bc03dee fastboot
C:\Users\manager\Desktop\platform-tools-v23.1>fastboot -S 512M flash system syst
em.img
erasing 'system'...
OKAY [ 0.556s]
sending sparse 'system' (516666 KB)...
OKAY [ 17.587s]
writing 'system'...
FAILED (remote: size too large)
finished. total time: 18.170s
Click to expand...
Click to collapse
So it isn't related to fastboot.
Are any of your partitions on the remote device full? cache or userdata?
If you can boot into stock recovery, you might want to try the FULL OTA from the nexus factory image site which you can try installing over adb sideload.
---------- Post added at 11:44 AM ---------- Previous post was at 11:42 AM ----------
bzz11g said:
I know, I want try to restore System with TWRP
Click to expand...
Click to collapse
Is that system.img from a factory image or is it from twrp backup?
If it is from factory image, I am not sure if TWRP does what is necessary to restore it either.
---------- Post added at 11:55 AM ---------- Previous post was at 11:44 AM ----------
You didn't mention you were at Qualcomm loader.
You need to use LGUP and the TOT file in the other thread.
I got the same error message a while back - I solved it by re-installing SDK on my computer. I know you have previously said that you have the most recent version of SDK, and I thought I did as well. But I went ahead and uninstalled everything related to SDK on my computer and reinstalled a fresh version. Once I tried flashing system.img after that, it worked perfectly. I'd suggest that you try the same.
Related
I rooted my Moto Z Play but I think I screwed up since I can´t no longer flash anything.
The TWRP is working fine (i guess) but when I try to install a ROM I get the following message:
"Failed to mount '/firmware' (invalid argument)"
I tried everything but can´t get it working properly.
Prior to this error I think I tried a diferent version of PAC-MAN and ended up with this situation.
Any sugestions?
Thanx in advance!
gocks said:
I rooted my Moto Z Play but I think I screwed up since I can´t no longer flash anything.
The TWRP is working fine (i guess) but when I try to install a ROM I get the following message:
"Failed to mount '/firmware' (invalid argument)"
I tried everything but can´t get it working properly.
Prior to this error I think I tried a diferent version of PAC-MAN and ended up with this situation.
Any sugestions?
Thanx in advance!
Click to expand...
Click to collapse
As far as I know no one has built PAC ROM for moto z play. My guess is TWRP just saved you from bricking your phone. Better make sure you're trying to flash a ROM build for MZP.
dandrumheller said:
As far as I know no one has built PAC ROM for moto z play. My guess is TWRP just saved you from bricking your phone. Better make sure you're trying to flash a ROM build for MZP.
Click to expand...
Click to collapse
C´mon guys, give me a break, I´m not a tech savy or something like that, just a regular lawyer.
Since I didn´t break my MZP what do I have to do to get it working again??
gocks said:
C´mon guys, give me a break, I´m not a tech savy or something like that, just a regular lawyer.
Since I didn´t break my MZP what do I have to do to get it working again??
Click to expand...
Click to collapse
Flash the correct ROM, in the updater script it checks your phone version prior to flashing the ROM.
Go to the development threads and find yourself moto z play specific ROM and flash
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Flash the correct ROM, in the updater script it checks your phone version prior to flashing the ROM.
Go to the development threads and find yourself moto z play specific ROM and flash
Sent from my XT1635-02 using
Click to expand...
Click to collapse
I´ve already tried the specific ROM from 3 diferent sources but the problem persists. I´ve tried the custon one and other ROMs but the same erros keeps showing.
gocks said:
I´ve already tried the specific ROM from 3 diferent sources but the problem persists. I´ve tried the custon one and other ROMs but the same erros keeps showing.
Click to expand...
Click to collapse
Does the phone boot to the stock ROM?
You may want flash the specific firmware for your phone.
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Does the phone boot to the stock ROM?
You may want flash the specific firmware for your phone.
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It does not boot to the stock ROM.
Just flashed the Nagout that you uploaded on another thread. It install but when I do the swipe after flashing the same error appears and the phone don´t boot. The error always appear after the "Updating partition details...." message.
After the installation I got this message:
Moto Z Play Nougat Installed
script suceeded: result was [Moto z P`lay Nougat Installed]
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
Then I wiped the cache/dalvik and this occurs:
Formating Cache using make_ext4gs....
Updating partition details....
Failed to mount '/firmware' (invalid argument)
....done
Wiping Dalvil Cache Directories...
Cleaned: /data/dalvik-cache...
--Dalvik Cache Directories Wipe Complete!
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
And when I reboot the system twrp ask to install a su wich I don´t install, the system reboot and after the message warning that my device is unlocked it goes to a dark screen and nothing happens.
AP Fastboot Flash Mode (Secure), is that correct?
Thanks again.
gocks said:
It does not boot to the stock ROM.
Just flashed the Nagout that you uploaded on another thread. It install but when I do the swipe after flashing the same error appears and the phone don´t boot. The error always appear after the "Updating partition details...." message.
After the installation I got this message:
Moto Z Play Nougat Installed
script suceeded: result was [Moto z P`lay Nougat Installed]
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
Then I wiped the cache/dalvik and this occurs:
Formating Cache using make_ext4gs....
Updating partition details....
Failed to mount '/firmware' (invalid argument)
....done
Wiping Dalvil Cache Directories...
Cleaned: /data/dalvik-cache...
--Dalvik Cache Directories Wipe Complete!
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
And when I reboot the system twrp ask to install a su wich I don´t install, the system reboot and after the message warning that my device is unlocked it goes to a dark screen and nothing happens.
AP Fastboot Flash Mode (Secure), is that correct?
Thanks again.
Click to expand...
Click to collapse
Download your firmware and flash in fastboot. Flash only the 10 sparsechunks,recovery, OEM.img and boot.img and erase user data.
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Download your firmware and flash in fastboot. Flash only the 10 sparsechunks,recovery, OEM.img and boot.img and erase user data.
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Dont know how to flash oem.img. It´s just fastboot oem unlock? If it is it gave me back invalid boot state.
Are the others commands and the order something like that:
fastboot flash system system.img_sparechunk.0 till 10
fastboot flash recovery recovery.img
IDK what´s the OEM.img command
fastboot flash boot boot.img
fastboot erase userdata
Thank you so much again!
gocks said:
Dont know how to flash oem.img. It´s just fastboot oem unlock? If it is it gave me back invalid boot state.
Are the others commands and the order something like that:
fastboot flash system system.img_sparechunk.0 till 10
fastboot flash recovery recovery.img
IDK what´s the OEM.img command
fastboot flash boot boot.img
fastboot erase userdata
Thank you so much again!
Click to expand...
Click to collapse
This is the commands
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Repeat all 10 sparsechunks
fastboot flash oem oem.img
Fastboot erase userdata
Fastboot reboot
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
This is the commands
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Repeat all 10 sparsechunks
fastboot flash oem oem.img
Fastboot erase userdata
Fastboot reboot
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Did exactly what you told me and this happened:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.371s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.683s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10820 KB)...
OKAY [ 0.235s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.235s]
finished. total time: 0.501s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257307 KB)...
OKAY [ 5.493s]
writing 'system'...
OKAY [ 3.985s]
finished. total time: 9.478s
The othes lines seems to be ok, but the phone continue stucked on the "Your device has been unlock...." and don´t reboot.
Downloaded another custom ROM (ADDISON_RETBR_6.0.1_MPNS24.104-44-7)
Unzipped into Minimal ADB and Fastboot folder
Openned Fastboot
Loaded bootloader and connected USB
>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.376s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.704s
>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.375s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.296s]
finished. total time: 0.672s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 5.505s]
writing 'system'...
OKAY [ 3.971s]
finished. total time: 9.477s
>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 2.245s]
writing 'oem'...
OKAY [ 1.439s]
finished. total time: 3.688s
>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.151s]
finished. total time: 0.154s
>fastboot reboot
rebooting...
And nothing happens again after the reboot.
When I try to boot to recovery it gives me a "no command" screen with a "no command" message and just it.
Flashed the recovey.img from twrp and it is working ok.
My bootloader:
AP Fastboot Flash Mode (Secure) => in red
BL: C0.14 (sha-9325e5f, 2016-07-11 16:32:03)
Baseband: <not found>
Product/Variant: addison XT1635-02 32GB P7
Serial number: xxxxxxxxx
CPU: xxxxxx
eMNC: xxxxxx
DRAW: xxxxxxxxx
Console: [NULL]: null
Battery: OK
flashing_unlocked
Software status: Modified
Transfer Mode: USB Connected
Trying now ROM XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_
Any clue? Thanx again.
gocks said:
Downloaded another custom ROM (ADDISON_RETBR_6.0.1_MPNS24.104-44-7)
Unzipped into Minimal ADB and Fastboot folder
Openned Fastboot
Loaded bootloader and connected USB
>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.376s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.704s
>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.375s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.296s]
finished. total time: 0.672s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 5.505s]
writing 'system'...
OKAY [ 3.971s]
finished. total time: 9.477s
>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 2.245s]
writing 'oem'...
OKAY [ 1.439s]
finished. total time: 3.688s
>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.151s]
finished. total time: 0.154s
>fastboot reboot
rebooting...
And nothing happens again after the reboot.
When I try to boot to recovery it gives me a "no command" screen with a "no command" message and just it.
Flashed the recovey.img from twrp and it is working ok.
My bootloader:
AP Fastboot Flash Mode (Secure) => in red
BL: C0.14 (sha-9325e5f, 2016-07-11 16:32:03)
Baseband: <not found>
Product/Variant: addison XT1635-02 32GB P7
Serial number: xxxxxxxxx
CPU: xxxxxx
eMNC: xxxxxx
DRAW: xxxxxxxxx
Console: [NULL]: null
Battery: OK
flashing_unlocked
Software status: Modified
Transfer Mode: USB Connected
Trying now ROM XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_
Any clue? Thanx again.
Click to expand...
Click to collapse
You flashed all the sparsechunks from 0 to 10?
The stock recovery has a dead Andy robot, so that flashed.
Did you flash the boot.img?
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
You flashed all the sparsechunks from 0 to 10?
The stock recovery has a dead Andy robot, so that flashed.
Did you flash the boot.img?
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yep, exactly the way you told me to do.
ADDISON_RETBR_6.0.1_MPNS24.104-44-7 has a corrupted file, but it didn´t work with the ADDISON_RETBR_MPNS24.104-44-10_cid50_ too.
Will try another one. And thanx again.
gocks said:
Yep, exactly the way you told me to do.
ADDISON_RETBR_6.0.1_MPNS24.104-44-7 has a corrupted file, but it didn´t work with the ADDISON_RETBR_MPNS24.104-44-10_cid50_ too.
Will try another one. And thanx again.
Click to expand...
Click to collapse
Obviously the pacman rom screwed up your partition, normally every rom will check if you're flashing a rom to a specific device.
I don't think flashing any other firmware will help cause it's all the same from one carrier to another.
I think you may need to flash the entire firmware package but it MUST BE YOUR SPECIFIC FIRMWARE PACKAGE otherwise you'll really be bricked.
I'm pulling at straws
flashallthetime said:
Obviously the pacman rom screwed up your partition, normally every rom will check if you're flashing a rom to a specific device.
I don't think flashing any other firmware will help cause it's all the same from one carrier to another.
I think you may need to flash the entire firmware package but it MUST BE YOUR SPECIFIC FIRMWARE PACKAGE otherwise you'll really be bricked.
I'm pulling at straws
Click to expand...
Click to collapse
Don´t say the word brick, please!!!
What I have to do to know what is my specific firmware?
gocks said:
Don´t say the word brick, please!!!
What I have to do to know what is my specific firmware?
Click to expand...
Click to collapse
Which carrier are you with?
And don't sue me if things get worse
flashallthetime said:
Which carrier are you with?
And don't sue me if things get worse
Click to expand...
Click to collapse
Vivo, its a brazilian one.
Relax, if my phone bricks I wont sue you because my wife will kill me first!
I flashed TWRP recovery.img and found that I have diferent kinds of partitions, is it corret?
/data is f2fs
/cach /system /persist ext4
/efs1 emmc
/external_sd and usb-otg vfat
gocks said:
I flashed TWRP recovery.img and found that I have diferent kinds of partitions, is it corret?
/data is f2fs
/cach /system /persist ext4
/efs1 emmc
/external_sd and usb-otg vfat
Click to expand...
Click to collapse
Yes and it seems like you can't right to the system and or data partitions. There's more partitions but they're locked or hidden
Try to format your data in TWRP
and wipe system
Hi, that's my first customisation:
1. Device unlocked:
{
"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"
}
2. TWRP flashed + *zip ready on /sdcard1
3. Install Zip fails
The checksums of all zips are ok, verified on my notebook.
I also can't wipe. And the standard Android 7.1 is recovering itself, if I boot-up.
Please advise, thanks!
1. Try unchecking signature verification in TWRP
2. Most likely, you will have to downgrade to CM13.1 first with that mounting error
3. I recommend using the standard LOS zip, it seems you have one with microG embedded
SECURE BOOT - enabled — Am I root?
kabu83 said:
1. Try unchecking signature verification in TWRP
2. Most likely, you will have to downgrade to CM13.1 first with that mounting error
3. I recommend using the standard LOS zip, it seems you have one with microG embedded
Click to expand...
Click to collapse
Thanks, I did all that and much more, trying to install CM 13.1, crDroid, OrangeFox, SuperSu => nothing installs!
Now I wonder: Am I root at all? I thought so, since I installed TWRP on a naked device?!
The bootloader shows: DEVICE STATE - unlocked
The Problem is, that TWRP cannot mount /system in the first place.
Have you tried downgrading following these steps: https://forum.xda-developers.com/showpost.php?p=72261104
TWRP cannot mount /system
kabu83 said:
The Problem is, that TWRP cannot mount /system in the first place.
Have you tried downgrading following these steps: https://forum.xda-developers.com/showpost.php?p=72261104
Click to expand...
Click to collapse
Now, that my holidays are over, I want this Crackling to crack!
Here my efforts to crack it via Fastboot:
Since the vintage Cyanogen fails as well as the state of the art Linage, I suspect that the payload might not be the cause for the failure?!
Code:
# fastboot flash system lineage-16.0-20190826-microG-crackling.zip
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 271225615 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2794255 is not a multiple of the block size 4096
erasing 'system'...
OKAY [ 0.841s]
sending sparse 'system' 1/3 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 271225615 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 271225615 is not a multiple of the block size 4096
OKAY [ 8.258s]
writing 'system' 1/3...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 16.173s
# fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 1.042s]
finished. total time: 1.043s
# fastboot flash system SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 619158578 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 350727218 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 82295858 is not a multiple of the block size 4096
erasing 'system'...
OKAY [ 0.831s]
sending sparse 'system' 1/4 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 619158578 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 619158578 is not a multiple of the block size 4096
OKAY [ 8.290s]
writing 'system' 1/4...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 14.176s
# fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.205s]
finished. total time: 0.205s
# fastboot flash recovery twrp-3.3.1-0-crackling.img
target reported max download size of 268435456 bytes
sending 'recovery' (16984 KB)...
OKAY [ 0.563s]
writing 'recovery'...
OKAY [ 1.188s]
finished. total time: 1.751s
# fastboot boot twrp-3.3.1-0-crackling.img
downloading 'boot.img'...
OKAY [ 0.535s]
booting...
OKAY [ 0.672s]
finished. total time: 1.208s
Boot to recovery (TWRP), then touch the bottom right menu button, what does it say in the terminal log? (Similar to the 2nd screenshot you posted.)
Bootloader vs BIOS
kabu83 said:
Boot to recovery (TWRP), then touch the bottom right menu button, what does it say in the terminal log? (Similar to the 2nd screenshot you posted.)
Click to expand...
Click to collapse
At the time of the Cyanogen/Linage installation I had no TWRP installed! Would it help to repeat the process?
In general, I assumed the Bootloader to function similar to the BIOS at a PC? That makes me wonder, why an Android installation-process via Fastboot can't just reformat the entire drive and do a fresh partitioning? (instead of complaining about 'chunks' and 'block-sizes')
Thanks for all your assistance, most appreciated! :good:
[email protected] said:
At the time of the Cyanogen/Linage installation I had no TWRP installed! Would it help to repeat the process?
In general, I assumed the Bootloader to function similar to the BIOS at a PC? That makes me wonder, why an Android installation-process via Fastboot can't just reformat the entire drive and do a fresh partitioning? (instead of complaining about 'chunks' and 'block-sizes')
Thanks for all your assistance, most appreciated! :good:
Click to expand...
Click to collapse
I would recommend installing TWRP, Version 3.2.1-0.
Then boot to recovery and check, if TWRP can mount the system Partition.
What OS do you have currentyl installed?
/system is empty
kabu83 said:
I would recommend installing TWRP, Version 3.2.1-0.
Then boot to recovery and check, if TWRP can mount the system Partition.
What OS do you have currently installed?
Click to expand...
Click to collapse
As mentioned, I prefer a clean install. Thus formatted /system with ext4 via Fastboot (it's default). It should be possible to mount an empty /system -- isn't it?
A clean install is needed anyway. It seems just easier to install the OS via TWRP and for future nightly updates anyway.
Heureka!
kabu83 said:
I would recommend installing TWRP, Version 3.2.1-0.
Click to expand...
Click to collapse
With TWRP 3.2.1-0 I managed to install SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip :good:
(I failed though to install "lineage-16.0-20190826-microG-crackling.zip" before.)
What's next? Replacing Cyanogen Bootloader with TWRP 3.2.1-0 again?
Then trying a pure Lineage and later Gapps seperately?
[email protected] said:
With TWRP 3.2.1-0 I managed to install SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip :good:
(I failed though to install "lineage-16.0-20190826-microG-crackling.zip" before.)
What's next? Replacing Cyanogen Bootloader with TWRP 3.2.1-0 again?
Then trying a pure Lineage and later Gapps seperately?
Click to expand...
Click to collapse
Can you boot into CM 13 now?
Has it replaced TWRP as recovery?
Bingo!
kabu83 said:
Can you boot into CM 13 now?
Has it replaced TWRP as recovery?
Click to expand...
Click to collapse
I've got Cyanogen Fastboot, Lineage Bootloader, and Lineage Crackling 190801.002 up and running… :good:
With CM 13 installed, TWRP directly installed "lineage-16.0-20190826-microG-crackling.zip" from SD-card.
Thanks again for your advice, it appears that the Android System which Google offers as update to CM13, indeed prevented the alternative OS installation somehow.
[email protected] said:
I've got Cyanogen Fastboot, Lineage Bootloader, and Lineage Crackling 190801.002 up and running… :good:
With CM 13 installed, TWRP directly installed "lineage-16.0-20190826-microG-crackling.zip" from SD-card.
Thanks again for your advice, it appears that the Android System which Google offers as update to CM13, indeed prevented the alternative OS installation somehow.
Click to expand...
Click to collapse
Happy to help. So you are all set now?
Hi all,
I've seemed to have bricked my Pixel C. I tried flashing the stock ROM after installing LineageOS.
I wiped everything using fastboot (recovery, data, system, bootloader, cache, etc) and now I am just stuck with fastboot.
When I try and use
Code:
fastboot boot twrp.img
, I get the following:
Code:
creating boot image...
creating boot image - 12974080 bytes
Sending 'boot.img' (12670 KB) OKAY [ 0.320s]
Booting FAILED (remote: 'image verification failed')
fastboot: error: Command failed
If I try and flash recovery using
Code:
fastboot flash recovery twrp.img
, I get the following:
Code:
Sending 'recovery' (12668 KB) OKAY [ 0.347s]
Writing 'recovery' FAILED (remote: 'unsupported command')
fastboot: error: Command failed
I did have this error before, but I had TWRP and used fwtool to fix it. But I have no OS, no recovery and I am getting these issues with fastboot.
I have tried various cables, my drivers are up to date and my software is up to date. I have also tried flashing the stock image from Google but that just does the following:
Code:
Sending 'bootloader' (16384 KB) OKAY [ 0.445s]
Writing 'bootloader' FAILED (remote: 'unsupported command')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.016s
--------------------------------------------
Bootloader Version...: ***********************************************************
Baseband Version.....: N/A
Serial Number........: unknown variable
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.010s]
Checking 'version-bootloader' FAILED
Device version-bootloader is '***********************************************************'.
Update requires 'Google_Smaug.7900.139.0'.
fastboot: error: requirements not met!
Press any key to exit...
Is this tablet totally bricked or can anyone help me out?
Thanks
Vartom said:
I fixed such a lock by flashing a chip with a bootloader. To do this, I had to peel off the screen and buy a programmer on Ali. Risky operation.
Click to expand...
Click to collapse
Hi, can you give more details on how you proceeded
Have you tried this?
https://download.dirtyunicorns.com/?device=dragon
Google smaug vendor image
Gesendet von meinem Nexus 6P mit Tapatalk
Doesn't work. It's not the image that's the issue anyway, its the command being unrecognized:
Code:
Sending 'bootloader' (16384 KB) OKAY [ 0.438s]
Writing 'bootloader' FAILED (remote: 'unsupported command')
fastboot: error: Command failed
Bricked.
I solved same problem but I was able to boot system and used this in adb:
Code:
fwtool vbnv write dev_boot_fastboot_full_cap 1
You must somehow boot recovery and flash system. Without recovery you are screwed.
matonka007 said:
Bricked.
I solved same problem but I was able to boot system and used this in adb:
Code:
fwtool vbnv write dev_boot_fastboot_full_cap 1
You must somehow boot recovery and flash system. Without recovery you are screwed.
Click to expand...
Click to collapse
Yeah. I have been searching for hours but it seems impossible without recovery.
Tried this?
https://forum.xda-developers.com/pixel-c/help/bootloader-reports-unlocked-unable-to-t3483513
Gesendet von meinem Nexus 6P mit Tapatalk
---------- Post added at 06:13 PM ---------- Previous post was at 06:11 PM ----------
And this?
https://forum.xda-developers.com/pixel-c/help/flash-factory-image-t3599367/amp/
Gesendet von meinem Nexus 6P mit Tapatalk
Yes but with no joy.
Fastboot doesn't work at all so I cannot even boot to recovery. Therefore, I am unable to use ADB to fix fastboot
Sad, maybee this?
https://forum.xda-developers.com/pixel-c/help/flashing-to-stock-android-npd90g-twrp-t3424863
Gesendet von meinem Nexus 6P mit Tapatalk
Doesn't work. But AGAIN... I cannot access recovery for ADB
Sorry no more ideas
Gesendet von meinem Nexus 6P mit Tapatalk
Are you sure that your BL is unlocked? Try to lock it and unlock it again.
Code:
FAILED (remote: 'image verification failed')
This error looks like it can not boot unsigned image. But I do not know why.
Bootloader is definitely unlocked. I have tried locking and unlocking multiple times
JustDarren said:
Hi all,
If I try and flash recovery using
Code:
fastboot flash recovery twrp.img
, I get the following:
Code:
Sending 'recovery' (12668 KB) OKAY [ 0.347s]
Writing 'recovery' FAILED (remote: 'unsupported command')
fastboot: error: Command failed
[/code]
Click to expand...
Click to collapse
This is a longshot, but I was getting very similar errors trying to do anything. All this happened on a Windows 10 Laptop using the Google Drivers. I tried it again on a Mac Book Pro running Catalina and it worked just fine with latest platform tools.
Perhaps you want to try a Linux or Mac if you have access to one, or try a Linux live edition on your current machine, something like this:
https://ubuntu.com/tutorials/try-ubuntu-before-you-install#1-getting-started
Just worth a shot. Still an awesome tablet to lose just yet. Hope it is not too late for you.
TheInitialCommand said:
This is a longshot, but I was getting very similar errors trying to do anything. All this happened on a Windows 10 Laptop using the Google Drivers. I tried it again on a Mac Book Pro running Catalina and it worked just fine with latest platform tools.
Perhaps you want to try a Linux or Mac if you have access to one, or try a Linux live edition on your current machine, something like this:
https://ubuntu.com/tutorials/try-ubuntu-before-you-install#1-getting-started
Just worth a shot. Still an awesome tablet to lose just yet. Hope it is not too late for you.
Click to expand...
Click to collapse
Thanks for the suggestion. I'll give it a go and let you know what happens
Good luck!
TheInitialCommand said:
Good luck!
Click to expand...
Click to collapse
No joy. Still getting unknown command. Even tried manually erasing and formatting the partitions with no luck. Thanks for the suggestion though.
Really bummed out because I still love this tablet. Shame I bricked it ?
JustDarren said:
No joy. Still getting unknown command. Even tried manually erasing and formatting the partitions with no luck. Thanks for the suggestion though.
Really bummed out because I still love this tablet. Shame I bricked it
Click to expand...
Click to collapse
I have similar problem ..
you need to extract the rom zip file, inside you have img files ...
a) you need tablet in fastboot mode . i have made the process in linux. also i have downloaded this rom
ryu-opm8.190605.005-factory-25b457f3.zip downloaded from google.
b) Tablet needs to be unlocked .. for that you need to do fastboot oem unlock .. and after you return to fastboot mode.
And here you have my steps ..
All made in linux but if you use windows remove the command "sudo" it ahould work
1) sudo fastboot flash bootloader bootloader-dragon-google_smaug.7900.139.0.img
2) sudo fastboot reboot bootloader
3) sudo fastboot flash boot boot.img
4) sudo fastboot flash cache cache.img
5) sudo fastboot flash recovery recovery.img
6) sudo fastboot flash system system.img
7) sudo fastboot flash vendor vendor.img
8) restart the tabler pressing button.
Check if these works for you ..
bye
Thanks for your reply but as o have said many times, fastboot is unresponsive and returns "Command not found". This isn't an error on my part with inputting the commands but I think moreso, corrupt storage
Did you try to use fusée gelée like on the nintendo switch, i think it will may solve your problem.
rhmanoa said:
Did you try to use fusée gelée like on the nintendo switch, i think it will may solve your problem.
Click to expand...
Click to collapse
I don't think that will work. Unless you have a guide for using it on android devices other than the switch.
Hi All,
used my OP7T for a week before deciding to unlock. That went fine, but when I tried to flash a GSI (no custom ROMs available yet), it says partition not found?? Tried system and system_a.
Code:
[email protected]:~/Downloads/Android$ fastboot flash system system-quack-arm64-ab-vanilla.img
Sending sparse 'system' 1/3 (786428 KB) OKAY [ 24.933s]
Writing sparse 'system' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.950s
[email protected]:~/Downloads/Android$ fastboot flash system_a Havoc-OS-3.0_ARM64-AB.img
Sending sparse 'system_a' 1/3 (786428 KB) OKAY [ 24.953s]
Writing sparse 'system_a' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.965s
[email protected]:~/Downloads/Android$
Hey,
I have the same issue, did you ever find a solution?
You must unlock first
You don't say
In the meantime I found the actual solution, here it is for the record : reboot from fastboot to fastbootd using "fastboot reboot fastboot"
And then the commands will work
natinusala said:
You don't say
In the meantime I found the actual solution, here it is for the record : reboot from fastboot to fastbootd using "fastboot reboot fastboot"
And then the commands will work
Click to expand...
Click to collapse
Got: "fastboot: usage: unknown reboot target fastboot"
bump
SecondSon1 said:
Got: "fastboot: usage: unknown reboot target fastboot"
Click to expand...
Click to collapse
been messing all night with fastboot trying to get it to boot to fastbootd
i keep getting this same error and so my phone is currently bricked as i cannot install the
system.img or anything that follows. also tried booting to fastbootd by doing
fastboot reboot recovery but it cannot find reboot target recovery either.
this is what i did
dosnoventa said:
been messing all night with fastboot trying to get it to boot to fastbootd
i keep getting this same error and so my phone is currently bricked as i cannot install the
system.img or anything that follows. also tried booting to fastbootd by doing
fastboot reboot recovery but it cannot find reboot target recovery either.
Click to expand...
Click to collapse
i got it working
Please help
sathara said:
i got it working
Click to expand...
Click to collapse
I'm getting
remote: Failed operation not permitted
and
remote: value to large for defined data type please help
i had the same problem. solved it by flashing msm extended recovery to both slots. that recovery has option to enter fastbootd
altojd said:
i had the same problem. solved it by flashing msm extended recovery to both slots. that recovery has option to enter fastbootd
Click to expand...
Click to collapse
Can you share that recovery image?
I couldn't find it in the Rom files.
For my 600th post on XDA, I offer this info in hopes it will help.
This one is T-mobile. Don't know if it will help ort harm but it works for me.
I don't have both hands right now; yoiu'll have to search for yourself on how to enter "EDL" mode and possibly an MSM (or is it MDM?) version of stock flashable file for your model and carrier, else maybe try the T-Mobile one at your own risk: Unbrick Tool for T-Mobile
GOOD LUCK
Hi guys,
When I type ' fastboot reboot fastboot ' in windows command prompt, I got the help menu of fastboot, anyone got a solution ?
My phone (Redmi 9 Note Pro) is bricked because I can't flash a system.img
Booting into fastboot using volumedown + power isn't working.
OKAY [ 17.778s]
writing 'system'...
FAILED (remote: Partition not found)
josdehaes said:
Hi All,
used my OP7T for a week before deciding to unlock. That went fine, but when I tried to flash a GSI (no custom ROMs available yet), it says partition not found?? Tried system and system_a.
Code:
[email protected]:~/Downloads/Android$ fastboot flash system system-quack-arm64-ab-vanilla.img
Sending sparse 'system' 1/3 (786428 KB) OKAY [ 24.933s]
Writing sparse 'system' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.950s
[email protected]:~/Downloads/Android$ fastboot flash system_a Havoc-OS-3.0_ARM64-AB.img
Sending sparse 'system_a' 1/3 (786428 KB) OKAY [ 24.953s]
Writing sparse 'system_a' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.965s
[email protected]:~/Downloads/Android$
Click to expand...
Click to collapse
Did you find a solution ?
Download latest fastboot drivers.
From OS:
adb reboot fastboot
Or from bootloader
fastboot reboot fastboot
With devices launched on Android 10 there is a new interface called fastbootd, this is where you flash the system.
Lethien said:
Did you find a solution ?
Click to expand...
Click to collapse
clearly. there is a difference between "old" fastboot (bootloader) and fastbootd (userspace fastboot to support dynamic partitions). You need to be in fastbootd to do most stuff nowadays.
{
"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"
}
My problem is bit different, can anybody help through this --- System partitioned doesn't exist !!!! while Gsi flashing on Realme 7 RMX2151
So when you see people posting in their tutorial;
fastboot reboot fastboot
NOW we type in;
fastboot reboot fastbootd?
No, same command, but you need stock recovery for this to work (twrp prevents fastbootd entry)
I tried for days to get to work but for TMobile follow guide on here and if it doesn't work even after you install drivers and all then use a different PC bc I have 7t and 8t OnePlus and my 8t unlocked works on my gf PC and her 7t TMobile works on mine figured that out the hard way but it's truthfully a solution when everything won't work
Levi0630 said:
I tried for days to get to work but for TMobile follow guide on here and if it doesn't work even after you install drivers and all then use a different PC bc I have 7t and 8t OnePlus and my 8t unlocked works on my gf PC and her 7t TMobile works on mine figured that out the hard way but it's truthfully a solution when everything won't work
Click to expand...
Click to collapse
Convert TMobile op7t to global using msmtool
Hey all, hoping to get some help recovering my Pixel 2 XL.
I was testing Ubuntu Touch and was annoyed that I didn't have enough root space, so I tried to adjust the partitions and have ended up here.
Whats happening:
Phone only boots in bootloader / `fastboot` mode
When trying to boot into recovery it just takes me back to bootloader
When I try to start the phone it goes right back to bootloader
What works:
`fastboot devices` shows my phone connected
What I've tried:
Flashing recovery via fastboot
`fastboot flash system twrp-3.7.0_9-0-taimen.img`
Sending 'system' (40960 KB) OKAY [ 1.055s]
Writing 'system' FAILED (remote: 'No such partition.')
`fastboot flash recovery twrp-3.7.0_9-0-taimen.img`
Warning: skip copying recovery image avb footer (recovery partition size: 0, recovery image size: 41943040).
Sending 'recovery' (40960 KB) OKAY [ 1.051s]
Writing 'recovery' FAILED (remote: 'No such partition.')
`fastboot flash boot_a twrp-3.7.0_9-0-taimen.img`
Warning: skip copying boot_a image avb footer (boot_a partition size: 0, boot_a image size: 41943040).
Sending 'boot_a' (40960 KB) OKAY [ 1.060s]
Writing 'boot_a' OKAY [ 0.364s]
`fastboot flash boot_b twrp-3.7.0_9-0-taimen.img`
Warning: skip copying boot_b image avb footer (boot_b partition size: 0, boot_b image size: 41943040).
Sending 'boot_b' (40960 KB) OKAY [ 0.989s]
Writing 'boot_b' OKAY [ 0.360s]
All of the above (successful or not) end up just taking me back to `bootloader` when I try to boot `recovery`
I've basically tried any command I can find on any image I've been able to get my hands on with no success
Everything I've found around restoring the factory partition table needs `adb`, so I'm stuck right now with.
Would love any suggestions, thanks.
klimbot said:
Hey all, hoping to get some help recovering my Pixel 2 XL.
I was testing Ubuntu Touch and was annoyed that I didn't have enough root space, so I tried to adjust the partitions and have ended up here.
Whats happening:
Phone only boots in bootloader / `fastboot` mode
When trying to boot into recovery it just takes me back to bootloader
When I try to start the phone it goes right back to bootloader
What works:
`fastboot devices` shows my phone connected
What I've tried:
Flashing recovery via fastboot
`fastboot flash system twrp-3.7.0_9-0-taimen.img`
Sending 'system' (40960 KB) OKAY [ 1.055s]
Writing 'system' FAILED (remote: 'No such partition.')
`fastboot flash recovery twrp-3.7.0_9-0-taimen.img`
Warning: skip copying recovery image avb footer (recovery partition size: 0, recovery image size: 41943040).
Sending 'recovery' (40960 KB) OKAY [ 1.051s]
Writing 'recovery' FAILED (remote: 'No such partition.')
`fastboot flash boot_a twrp-3.7.0_9-0-taimen.img`
Warning: skip copying boot_a image avb footer (boot_a partition size: 0, boot_a image size: 41943040).
Sending 'boot_a' (40960 KB) OKAY [ 1.060s]
Writing 'boot_a' OKAY [ 0.364s]
`fastboot flash boot_b twrp-3.7.0_9-0-taimen.img`
Warning: skip copying boot_b image avb footer (boot_b partition size: 0, boot_b image size: 41943040).
Sending 'boot_b' (40960 KB) OKAY [ 0.989s]
Writing 'boot_b' OKAY [ 0.360s]
All of the above (successful or not) end up just taking me back to `bootloader` when I try to boot `recovery`
I've basically tried any command I can find on any image I've been able to get my hands on with no success
Everything I've found around restoring the factory partition table needs `adb`, so I'm stuck right now with.
Would love any suggestions, thanks.
Click to expand...
Click to collapse
Assuming your bootloader is unlocked, try flashing the stock firmware again using Android Flash Tool. Select "Force Flash Partitions".
Lughnasadh said:
Assuming your bootloader is unlocked, try flashing the stock firmware again using Android Flash Tool. Select "Force Flash Partitions".
Click to expand...
Click to collapse
Thanks for the suggestion, but not working :-(
Flash Failed: Fastboot command (erase:userdata) failed. 'Check device console'
{
"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"
}
I've tried all the options in there, but no luck
Maybe just run flash-all in the factory image? (I'm not really sure if that is what the flash tool does).
Check your USB connection. This phone usually fails if you use a USB C port on the computer.
Also, did you try fastboot boot twrp.img?
runekock said:
Maybe just run flash-all in the factory image? (I'm not really sure if that is what the flash tool does).
Check your USB connection. This phone usually fails if you use a USB C port on the computer.
Click to expand...
Click to collapse
I'm using the USB connection that I have used the entire time to successfully flash images before I stuffed up the partitions, so I'm confident it's not that. I am on a Mac so only have USB-C available unfortunately.
runekock said:
Also, did you try fastboot boot twrp.img?
Click to expand...
Click to collapse
Yep have tried flashing both boot and recovery with no luck.
I think I need to fix the partitions somehow, if that's even possible from where I am
I was thinking of the fastboot "boot" command that can boot twrp without flashing it
runekock said:
I was thinking of the fastboot "boot" command that can boot twrp without flashing it
Click to expand...
Click to collapse
I got in to TWRP!! Not sure why but `fastboot reboot recovery` got me to TWRP... progress! Thanks for your help @runekock
Now I guess I just need to work out how to restore the partition table
Got it going again!! So once I got from fastboot in to recovery, I was able to follow these instructions to remake the partition table:
[GUIDE] System partition too small? Installing Android 12, GApps & large GSIs on Pixel 2 XL!
SPECIAL THANKS TO @Lunarixus on XDA I wouldn't have figured out how to maneuver the pixel 2 XL partition table without him. WARNING! This tutorial only applies to Taimen (2XL). There's already another tutorial for Walleye, click here for link...
forum.xda-developers.com
Good to hear. Your persistence was rewarded!