Develop Bugs

Can't flash system.img (TWRP/FASTBOOT)

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.

fastboot flash system: partition not found

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

[ROM] AOSP 11.0 - SODP [11.0.0_r38]

{
"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:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What's AOSP?
AOSP is Android as Google publish without any modifications. .
What's working :
Boots
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
LED
GPS
ROM Updated : 7th July 2020
Changelog :
Kernel upstreamed to 4.14.232
Imported stock sensors stack as SODP needs to be worked on right now.
Used lineage as base
June 21 Security Patch.
Instructions to install up ROM :
Flash latest available Stock ROM(47.2.A.10.107) and boot into it once.
Reboot to Fastboot and flash this TWRP recovery ( recovery.img)
fastboot flash recovery recovery.img
Download the latest OEM Image from HERE, Extract and Flash it.
fastboot flash oem SW_binaries_for_Xperia_Android_11_4.14_v5b_yoshino.img
Flash the userdata image (Will wipe all the userdata).
fastboot flash userdata userdata.img
Boot into twrp and wipe
system
cache
dalvik cache
DO NOT WIPE DATA from twrp, you will have issues with internal storage.
TWRP is not yet able to decrypt the internal storage, so please use adb sideload to flash the rom.
Advanced > Enable adb sideload
adb sideload ***rom zip file***
Install Magisk/Gapps(Optional).
Reboot
Downloads :
G8142 : https://sourceforge.net/projects/xz...1-20210706-UNOFFICIAL-maple_dsds.zip/download
G8141 : https://sourceforge.net/projects/xz...e-18.1-20210706-UNOFFICIAL-maple.zip/download
Source Code: https://github.com/xperiadev

Questions :
Q) How to flash Gapps?
A) Flash this TWRP in fastboot mode (fastboot flash recovery <path to recovery>.img
Boot to the recovery, This recovery is not yet compatible with encryption so use adb sideload ( Advanced >> Adb sideload).
on your PC open cmd/terminal and type adb sideload <opengapps>.zip
Q) How to flash Magisk?
A) Adb sideload.

I really like your amazing work! I hope that one day you will also bring the pixel experience to android 11

thanks matee for your work

Hal3 support? (does gcam work?)

Thank you a lot Shujat!
P.s. read in "notes"
Flashing user data is not mandatory...do you mean erase them? Otherwise i don't get what this means
Ok, my mistake, reread all and found what i needed

Bymn.38 said:
Hal3 support? (does gcam work?)
Click to expand...
Click to collapse
Camera2api support?
Yes its full, test out which gcam mod works best on maple and share it with us too

Shujath said:
Camera2api support?
Yes its full, test out which gcam mod works best on maple and share it with us too
[/ALINTI]
I did the steps right
but remained black screen (shaking)
Click to expand...
Click to collapse

Can you please write the steps down what all you did?

Shujath said:
Can you please write the steps down what all you did?
Click to expand...
Click to collapse
latest stock software(newflasher)
fastboot flash oem
fastboot flash boot
fastboot flash system(
erasing 'system'...
OKAY [ 0.149s]
sending sparse 'system' (517140 KB)...
OKAY [ 11.929s]
writing 'system'...
OKAY [ 0.004s]
sending sparse 'system' (516144 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 13.004s)
fastboot flash userdata
fastboot flash twrp and adb sideload gapps and magisk

Let's face it people, these phones are pretty much toast. they may very well work with some carriers but they will be getting few and far between. When 5G becomes more prevalent 4G will become almost useless just as 3G became. Web content will be so data heavy 4G won't be able to keep up. So I bid adieu to Sony as I have moved on to a Pixel 5. I mean, that's what we're trying to turn our phones into, right? Carrier and manufacturer bloatware free? It was fun messing with these phones but, just too much hassle in the end. Good luck to all that press on.

Bymn.38 said:
latest stock software(newflasher)
fastboot flash oem
fastboot flash boot
fastboot flash system(
erasing 'system'...
OKAY [ 0.149s]
sending sparse 'system' (517140 KB)...
OKAY [ 11.929s]
writing 'system'...
OKAY [ 0.004s]
sending sparse 'system' (516144 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 13.004s)
fastboot flash userdata
fastboot flash twrp and adb sideload gapps and magisk
Click to expand...
Click to collapse
System image did not get flashed correctly
Re download the file and try again

Shujath said:
System image did not get flashed correctly
Re download the file and try again
Click to expand...
Click to collapse
didn't happen with cmd
I have been successful with flashtool
thanks for the rom

Bymn.38 said:
didn't happen with cmd
I have been successful with flashtool
thanks for the rom
Click to expand...
Click to collapse
so were you able to boot ?

sim kart görmüyor mu?

Bymn.38 said:
sim kart görmüyor mu?
Click to expand...
Click to collapse
Did you boot into stock ROM once?

[QUOTE = "Shujath, gönderi: 84193105, üye: 6427265"]
Stok ROM'a bir kez önyükleme yaptınız mı?
[/ ALINTI]
Evet
bazen okumak
my device G8141 ? not dual

Bymn.38 said:
[QUOTE = "Shujath, gönderi: 84193105, üye: 6427265"]
Stok ROM'a bir kez önyükleme yaptınız mı?
[/ ALINTI]
Evet
bazen okumak
my device G8141 ? not dual
Click to expand...
Click to collapse
Download Single SIM ROM from Here

thanks for ur hard work!love u,bro

Shujath said:
Download Single SIM ROM from
Click to expand...
Click to collapse
better now but
wifi is breaking
writes factory data reset and turns off won't turn on

How to disable dm-verity?

{
"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 found this in twrp official web site. I guess this is the reason that every time i try to install twrp and after that, my device get bootloop.
So how can i disable dm-verity?
(Sorry, my English may bad because we don't use that in our country)

Here is the file you need to flash it

zuhaibsarwar said:
Here is the file you need to flash it
Click to expand...
Click to collapse
Thanks you, but one more thing i need to ask
I tried many times to install LineageOS 18.1 with zip file (by twrp of course). I found out that my phone is a/b device, so i search on youtube "install custom rom on a/b devices" and follow step by step. But nothing happend, twrp still warn "no OS installed" and bootloop everytime
Please, if you know something i really want to use Lineage

cl3izv said:
I found this in twrp official web site. I guess this is the reason that every time i try to install twrp and after that, my device get bootloop.
So how can i disable dm-verity?
(Sorry, my English may bad because we don't use that in our country)
Click to expand...
Click to collapse
Everytime you install any custom ROM you always need to change slot .if you flash on a then switch to b and if flash on b switch to a

zuhaibsarwar said:
Everytime you install any custom ROM you always need to change slot .if you flash on a then switch to b and if flash on b switch to
Click to expand...
Click to collapse
i read your cmt about twrp, but yes, i use that twrp 3.4.0 file too but i got some problem
After fastboot boot twrp-3.4.0-0-PL2_sprout.img
Sending 'boot.img' (42412 KB) OKAY [ 1.206s]
Booting OKAY [ 5.049s]
Finished. Total time: 6.466s
Im stuck on android one screen
But when i return to download mode, i type:
fastboot flash recovery twrp-3.4.0-0-PL2_sprout.img (alway getting error)
fastboot boot twrp-3.4.0-0-PL2_sprout.img
I can go to twrp screen normally
Do you got any idea?

cl3izv said:
i read your cmt about twrp, but yes, i use that twrp 3.4.0 file too but i got some problem
After fastboot boot twrp-3.4.0-0-PL2_sprout.img
Sending 'boot.img' (42412 KB) OKAY [ 1.206s]
Booting OKAY [ 5.049s]
Finished. Total time: 6.466s
Im stuck on android one screen
But when i return to download mode, i type:
fastboot flash recovery twrp-3.4.0-0-PL2_sprout.img (alway getting error)
fastboot boot twrp-3.4.0-0-PL2_sprout.img
I can go to twrp screen normally
Do you got any idea?
Click to expand...
Click to collapse
Fastboot flash boot twrp.img
Fastboot reboot
It will take to TWRP now flash the lineage 18.1 and after flashing it successful with no errors change slot to b or a depends on which you flash lineage 18.1 and you will successful boot in lineage 18.1
If still failed i will try to make a full video of whole procedure by tomorrow morning
cl3izv said:
i read your cmt about twrp, but yes, i use that twrp 3.4.0 file too but i got some problem
After fastboot boot twrp-3.4.0-0-PL2_sprout.img
Sending 'boot.img' (42412 KB) OKAY [ 1.206s]
Booting OKAY [ 5.049s]
Finished. Total time: 6.466s
Im stuck on android one screen
But when i return to download mode, i type:
fastboot flash recovery twrp-3.4.0-0-PL2_sprout.img (alway getting error)
fastboot boot twrp-3.4.0-0-PL2_sprout.img
I can go to twrp screen normally
Do you got any idea?
Click to expand...
Click to collapse
cl3izv said:
i read your cmt about twrp, but yes, i use that twrp 3.4.0 file too but i got some problem
After fastboot boot twrp-3.4.0-0-PL2_sprout.img
Sending 'boot.img' (42412 KB) OKAY [ 1.206s]
Booting OKAY [ 5.049s]
Finished. Total time: 6.466s
Im stuck on android one screen
But when i return to download mode, i type:
fastboot flash recovery twrp-3.4.0-0-PL2_sprout.img (alway getting error)
fastboot boot twrp-3.4.0-0-PL2_sprout.img
I can go to twrp screen normally
Do you got any idea?
Click to expand...
Click to collapse
Fastboot flash boot twrp.img
Fastboot reboot
It will take to TWRP now flash the lineage 18.1 and after flashing it successful with no errors change slot to b or a depends on which you flash lineage 18.1 and you will successful boot in lineage 18.1
If still failed i will try to make a full video of whole procedure by tomorrow morning
Don't flash dm verification file here np needed just install twrp boot tp twrp flash lineage and change boot slot and boom enjoy 18.1

Lol my comment messed up

cl3izv said:
i read your cmt about twrp, but yes, i use that twrp 3.4.0 file too but i got some problem
After fastboot boot twrp-3.4.0-0-PL2_sprout.img
Sending 'boot.img' (42412 KB) OKAY [ 1.206s]
Booting OKAY [ 5.049s]
Finished. Total time: 6.466s
Im stuck on android one screen
But when i return to download mode, i type:
fastboot flash recovery twrp-3.4.0-0-PL2_sprout.img (alway getting error)
fastboot boot twrp-3.4.0-0-PL2_sprout.img
I can go to twrp screen normally
Do you got any idea?
Click to expand...
Click to collapse
I have another idea.i tried it before . don't install twrp simple go impulsion lineage and download lineage boot.img I mean lineage recovery .if you have SD card copy lineage on SD and after installing lineage recovery with these commands with adb
Fastboot flash boot lineage recovery.img
Fastboot reboot
And now in lineage recovery go to update and select lineage file and flash it after flashing in done simple reboot to lineage

Download latest recovery image of lineage os
LineageOS Downloads
download.lineageos.org

i will try, but also need your video, thank you

here the commands while i was flashing twrp on my mobile
C:\Users\480\OneDrive\Desktop\platform-tools>fastboot flash boot abc.img
Sending 'boot_b' (42412 KB) OKAY [ 4.609s]
Writing 'boot_b' OKAY [ 0.344s]
Finished. Total time: 12.000s
C:\Users\480\OneDrive\Desktop\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.031s
C:\Users\480\OneDrive\Desktop\platform-tools>

zuhaibsarwar said:
here the commands while i was flashing twrp on my mobile
C:\Users\480\OneDrive\Desktop\platform-tools>fastboot flash boot abc.img
Sending 'boot_b' (42412 KB) OKAY [ 4.609s]
Writing 'boot_b' OKAY [ 0.344s]
Finished. Total time: 12.000s
C:\Users\480\OneDrive\Desktop\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.031s
C:\Users\480\OneDrive\Desktop\platform-tools>
Click to expand...
Click to collapse
when i flash stock rom, it's andoird 8.1 and i don't update to android 10
fastboot flash boot abc.img
Sending 'boot_a' (42412 KB) OKAY [ 4.609s]
Writing 'boot_a' OKAY [ 0.344s]
Finished. Total time: 6s
fastboot reboot
Then it's stuck on logo
But when i flash stock again and update to android 10, it's like what i said

I don't know why my device is harder than any other or i have wrong on any step but it doesn't like any tutorial video on youtube

wait i gotta make video now

cl3izv said:
I don't know why my device is harder than any other or i have wrong on any step but it doesn't like any tutorial video on youtube
Click to expand...
Click to collapse
in this i used pixel experienced recover and pixel experienced rom andriod 11 . same procedure for lineage 18.1

zuhaibsarwar said:
in this i used pixel experienced recover and pixel experienced rom andriod 11 . same procedure for lineage 18.1
Click to expand...
Click to collapse
here is CMD PROCESSSING
C:\Users\480\OneDrive\Desktop\platform-tools>fastboot flash boot C:\Users\480\OneDrive\Desktop\boot.img
Sending 'boot_a' (37309 KB) OKAY [ 1.205s]
Writing 'boot_a' OKAY [ 0.300s]
Finished. Total time: 2.035s
C:\Users\480\OneDrive\Desktop\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.011s

thank you, i will try it when i'm home

cl3izv said:
I don't know why my device is harder than any other or i have wrong on any step but it doesn't like any tutorial video
Click to expand...
Click to collapse
cl3izv said:
thank you, i will try it when i'm home
Click to expand...
Click to collapse
welcome and okay

WAO dude, i really did it, it working Very helpful, thank you
and how about twrp and gapps? should i install Disable Force encryption again?

cl3izv said:
WAO dude, i really did it, it working Very helpful, thank you
and how about twrp and gapps? should i install Disable Force encryption again?
Click to expand...
Click to collapse
dont try to install twrp .i tried to install twrp permanently many times but always failed always bootloop . dont flash disable force . flash gapps using lineage recovery only and you can flash magisk too

Question Is it ok to skip an update using the android flash tool

So basically I haven't updated since android 13 came out. Last month I saw that the monthly patch had arrived but the android flash tool didn't seem to have it. I haven't been bothered enoguh to check again since then but I now see that they builds aren't separated like they used to be and there's only a Android 13 option. I am currently on TP1A.220624.021, and Andrioid Flash Tool is offering TP1A.221005.002.

Divine Bicycle said:
So basically I haven't updated since android 13 came out. Last month I saw that the monthly patch had arrived but the android flash tool didn't seem to have it. I haven't been bothered enoguh to check again since then but I now see that they builds aren't separated like they used to be and there's only a Android 13 option. I am currently on TP1A.220624.021, and Andrioid Flash Tool is offering TP1A.221005.002.
Click to expand...
Click to collapse
Yeah, it's fine to just update to the latest. As a reminder, make sure you have the A13 bootloader flashed to both slots before doing anything, if you haven't already,

Lughnasadh said:
Yeah, it's fine to just update to the latest. As a reminder, make sure you have the A13 bootloader flashed to both slots before doing anything, if you haven't already,
Click to expand...
Click to collapse
Ok, as for having both slots flashed, in not entirely sure if they are haha. I had a few issues updating to Android 13 as listed here, so I'm assuming they are both flashed.

Divine Bicycle said:
Ok, as for having both slots flashed, in not entirely sure if they are haha. I had a few issues updating to Android 13 as listed here, so I'm assuming they are both flashed.
Click to expand...
Click to collapse
Reading through that thread it doesn't sound like you did as Android Flash Tool doesn't flash to both slots, even when force flash partitions is selected.
Follow the guide in the link below to flash the A13 bootloader to the opposite slot.
🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...
forum.xda-developers.com

Lughnasadh said:
Reading through that thread it doesn't sound like you did as Android Flash Tool doesn't flash to both slots, even when force flash partitions is selected.
Follow the guide in the link below to flash the A13 bootloader to the opposite slot.
🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...
forum.xda-developers.com
Click to expand...
Click to collapse
Sorry for the *very* late response. When I was trying using ADB and ```flash-all.bat```, I think the bootloader flashed successfully. However I will try the instructions at the bottom of the page you linked to check the bootloader version.

Ok, so I've just checked. The bootloader is the same version on both slots:
Microsoft Windows [Version 10.0.19044.2130]
(c) Microsoft Corporation. All rights reserved.
C:\Users\$USER\Downloads\platform-tools_r33.0.2-windows\platform-tools>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
C:\Users\$USER\Downloads\platform-tools_r33.0.2-windows\platform-tools>fastboot devices
1C101FDEE009NE fastboot
C:\Users\$USER\Downloads\platform-tools_r33.0.2-windows\platform-tools>fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.002s
C:\Users\$USER\Downloads\platform-tools_r33.0.2-windows\platform-tools>fastboot getvar version-bootloader
version-bootloader: slider-1.2-8739948
Finished. Total time: 0.005s
C:\Users\$USER\Downloads\platform-tools_r33.0.2-windows\platform-tools>fastboot --set-active=b
Setting current slot to 'b' OKAY [ 0.111s]
Finished. Total time: 0.116s
C:\Users\$USER\Downloads\platform-tools_r33.0.2-windows\platform-tools>fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.002s
C:\Users\$USER\Downloads\platform-tools_r33.0.2-windows\platform-tools>adb reboot bootloader
C:\Users\$USER\Downloads\platform-tools_r33.0.2-windows\platform-tools>fastboot getvar bersion-bootlaoder
getvar:bersion-bootlaoder FAILED (remote: 'variable (bersion-bootlaoder) not found')
Finished. Total time: 0.008s
C:\Users\$USER\Downloads\platform-tools_r33.0.2-windows\platform-tools>fastboot getvar bersion-bootloader
getvar:bersion-bootloader FAILED (remote: 'variable (bersion-bootloader) not found')
Finished. Total time: 0.011s
C:\Users\$USER\Downloads\platform-tools_r33.0.2-windows\platform-tools>fastboot getvar version-bootloader
version-bootloader: slider-1.2-8739948
Finished. Total time: 0.003s
C:\Users\$USER\Downloads\platform-tools_r33.0.2-windows\platform-tools>fastboot --set-active a
fastboot: usage: unknown command a
C:\Users\$USER\Downloads\platform-tools_r33.0.2-windows\platform-tools>fastboot --set-active=a
Setting current slot to 'a' OKAY [ 0.125s]
Finished. Total time: 0.133s
C:\Users\$USER\Downloads\platform-tools_r33.0.2-windows\platform-tools>fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.002s
C:\Users\$USER\Downloads\platform-tools_r33.0.2-windows\platform-tools>fastboot continue
Resuming boot OKAY [ 0.036s]
Finished. Total time: 0.051s
C:\Users\$USER\Downloads\platform-tools_r33.0.2-windows\platform-tools>
Click to expand...
Click to collapse
If you ignore my typos, then you can see that both slots are on bootloader version 'slider-1.2-8739948'. What steps should I take to update to the latest system version now? Just update through the Android Flash Tool?

Divine Bicycle said:
Ok, so I've just checked. The bootloader is the same version on both slots:
If you ignore my typos, then you can see that both slots are on bootloader version 'slider-1.2-8739948'. What steps should I take to update to the latest system version now? Just update through the Android Flash Tool?
Click to expand...
Click to collapse
Updating via Android Flash Tool is fine. You can also use the Pixel Flasher.

{
"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"
}
Thank you for that advice, I am now up to date and using Kirisakura's kernel.