Develop Bugs

Huawei P6 Stuck on Logo. Final Fixer!

Hello. I'll Make Huawei Stuck on Logo fixer to my friend. and i want to share it to everybody! Okay Lets start!
Follow The Instructions :
Download Adb&Fastboot here. and installed the adb&fastboot.
- http://tabletrepublic.com/forum/downloads.php?do=file&id=312
Download HiSuite for Huawei and update it.
- http://consumer.huawei.com/minisite/HiSuite_en/
Download recovery.img here .
- https://www.androidfilehost.com/?fid=23329332407584772
# after you downloaded the recovery.img paste it on adb&fastboot folder.
# Connect your phone to the computer using the supplied USB cable.
# Press and hold the Power and Volume Down button.
# PHONE will be recognized as ABD device. it appears on the side of your desktop.
# Leave the Power and Volume Down button.
# And now go to Adb&fastboot folder , and hold Shift+Right click then Choose "Open command window here"
# and then when cmd appears type this command .
"fastboot devices" without quote ("")
when you see like this ????/??,,? <>?????? it means device is detected .
you can continue . next step type this .
Type: fastboot reboot bootloader
Type fastboot flash recovery recovery.img
after you type the last command , when you see the finish word without FAILED.
Fastboot will flash the image and give you a success/failure notification. If successful, you're all set.
Finally, press and hold the Power button. PHONE will boot now :laugh:
and then your phone fix now , and dont stuck on logo! ENJOY! :angel: :angel: :angel:
Btw if you failed flashing recovery please tell me.
PRESS THANKS IF HELPS!

U flash recovery without unlock bootloader!!!??

Help999 said:
Hello. I'll Make Huawei Stuck on Logo fixer to my friend. and i want to share it to everybody! Okay Lets start!
Follow The Instructions :
Download Adb&Fastboot here. and installed the adb&fastboot.
- http://tabletrepublic.com/forum/downloads.php?do=file&id=312
Download HiSuite for Huawei and update it.
- http://consumer.huawei.com/minisite/HiSuite_en/
Download recovery.img here .
- https://www.androidfilehost.com/?fid=23329332407584772
# after you downloaded the recovery.img paste it on adb&fastboot folder.
# Connect your phone to the computer using the supplied USB cable.
# Press and hold the Power and Volume Down button.
# PHONE will be recognized as ABD device. it appears on the side of your desktop.
# Leave the Power and Volume Down button.
# And now go to Adb&fastboot folder , and hold Shift+Right click then Choose "Open command window here"
# and then when cmd appears type this command .
"fastboot devices" without quote ("")
when you see like this ????/??,,? <>?????? it means device is detected .
you can continue . next step type this .
Type: fastboot reboot bootloader
Type fastboot flash recovery recovery.img
after you type the last command , when you see the finish word without FAILED.
Fastboot will flash the image and give you a success/failure notification. If successful, you're all set.
Finally, press and hold the Power button. PHONE will boot now :laugh:
and then your phone fix now , and dont stuck on logo! ENJOY! :angel: :angel: :angel:
Btw if you failed flashing recovery please tell me.
PRESS THANKS IF HELPS!
Click to expand...
Click to collapse
I try for me but i got this ERROR :
D:\--- MOBILE\Android\android\platform-tools>fastboot flash recovery recovery.im
g
< waiting for device >
target reported max download size of 838860800 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.476s]
writing 'recovery'...
FAILED (remote: flash failure, ErrNo:2)
finished. total time: 0.486s
D:\--- MOBILE\Android\android\platform-tools>fastboot flash boot boot.img
D:\--- MOBILE\Android\android\platform-tools>fastboot flash boot boot.img
target reported max download size of 838860800 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.243s]
writing 'boot'...
FAILED (remote: flash failure, ErrNo:2)
finished. total time: 0.252s
Click to expand...
Click to collapse

after you downloaded the recovery.img paste it on adb&fastboot folder.
Click to expand...
Click to collapse
i think he means c:\adb
because there is no such folder named adb&fastboot
Type: fastboot reboot bootloader
Type fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Correction:Type: fastboot reboot-bootloader
Tried this, FAILED <remote: verify failure : Errno. 8>
{
"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"
}

amir_zohaib said:
i think he means c:\adb
because there is no such folder named adb&fastboot
Correction:Type: fastboot reboot-bootloader
Tried this, FAILED <remote: verify failure : Errno. 8>
Click to expand...
Click to collapse
are you on windows 8?

danielpsx said:
are you on windows 8?
Click to expand...
Click to collapse
No, windows 7 ,64 bit.
i think it has something to do with timing

Any news on this?

I also have this problem, is there a fix?
C:\adb>fastboot flash recovery recovery_original_flashable.img
target reported max download size of 838860800 bytes
sending 'recovery' (7804 KB)...
OKAY [ 0.334s]
writing 'recovery'...
(bootloader) OKAY
FAILED (remote: verify failure, ErrNo:8)
finished. total time: 1.519s

any updates i have the same problem
same problem on widnows 10 64bit
benjamin1 said:
I also have this problem, is there a fix?
C:\adb>fastboot flash recovery recovery_original_flashable.img
target reported max download size of 838860800 bytes
sending 'recovery' (7804 KB)...
OKAY [ 0.334s]
writing 'recovery'...
(bootloader) OKAY
FAILED (remote: verify failure, ErrNo:8)
finished. total time: 1.519s
Click to expand...
Click to collapse

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.

Lenovo P2 stuck in "Fast boot" menu. Bricked?

I have a Lenovo P2, unrooted, on stock Android, with a 256mb micro SD card. It hasn't been unlocked/flashed/rooted in any way apart from Developer Options to allow ADB.
A couple of days ago the phone started to lag and lock up, and then rebooted into "AP Fastboot Flash Mode (Secure)" menu. The only options are Start/Barcodes/Power Off.
The Start and Power Off/On options simply reboot back to the same screen after a couple of seconds. It won't boot back into Android with any combination of volume up/down/power buttons, or offer me any other options such as recovery or clear cache etc.
I've tried rebooting with/without the SD card - it makes no difference.
The phone still appears to be recognised by ADB when I connect it to a laptop - it appears in 'fastboot devices' - but I still can't get it to exit fastboot and boot back into Android with any ADB command.
I've tried downloading Reiboot and "15 second adb" toolkits which claim to exit fastboot mode, but without success.
I'm assuming the bootloader is corrupted.
Can anyone please point me towards any possible action for fixing it, or is it bricked?
Many thanks.
{
"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"
}

The thing you are on now is the bootloader...
What you did is probably soft bricked the phone.
What did you perform with adb?

If your rom is not booting you might need to reinstall it.

Keno_I said:
The thing you are on now is the bootloader...
What you did is probably soft bricked the phone.
What did you perform with adb?
Click to expand...
Click to collapse
Here's what I've tried with ADB - the phone seems to be connected as evidenced by "fastboot devices", but I don't know what to do now. "Fastboot reboot" just brings me back to the same Fastboot screen in my original post, as does holding down vol+/vol-/power for several seconds.
I successfully unlocked/flashed a ZTE San Francisco Blade back in the day, so I don't mind trying to flash this P2 if that's the answer and you can point me towards a noob-friendly guide, please.

Reinstall the stock rom from fastboot

@Kenora_I
To try and reinstall stock, I'm following the instructions here --> https://forum.xda-developers.com/t/lenovo-p2-fastboot-files-of-every-stock-firmware.3649914/
and have downloaded all the firmware files linked on that page, ie https://www.androidfilehost.com/?w=files&flid=205781
Do I need to unlock the bootloader first?
Well, when I tried to "fastboot oem unlock", I got
fastboot oem unlock
...
FAILED (remote: oem unlock error: partition tampered
I then tried the Flash commands given, and got this error;
Fastboot flash system systemchunk0.img
target reported max download size of 536870912 bytes
sending 'system' (260121 KB)...
OKAY [ 9.303s]
writing 'system'...
FAILED (remote: Not official valid sparse image)
finished. total time: 9.379s
I got this with every set of firmware files on the download link. Am I trying to use the wrong firmware images?
Thanks for any tips and suggestions.

bigajm said:
@Kenora_I
To try and reinstall stock, I'm following the instructions here --> https://forum.xda-developers.com/t/lenovo-p2-fastboot-files-of-every-stock-firmware.3649914/
and have downloaded all the firmware files linked on that page, ie https://www.androidfilehost.com/?w=files&flid=205781
Do I need to unlock the bootloader first?
Well, when I tried to "fastboot oem unlock", I got
fastboot oem unlock
...
FAILED (remote: oem unlock error: partition tampered
I then tried the Flash commands given, and got this error;
Fastboot flash system systemchunk0.img
target reported max download size of 536870912 bytes
sending 'system' (260121 KB)...
OKAY [ 9.303s]
writing 'system'...
FAILED (remote: Not official valid sparse image)
finished. total time: 9.379s
I got this with every set of firmware files on the download link. Am I trying to use the wrong firmware images?
Thanks for any tips and suggestions.
Click to expand...
Click to collapse
You have to find and flash a valid flash image, try with the same version you were installed on

Can someone provide me with a twrp restore file? I tried to flash the stock rom but the bat file that came with it tampered with some files and I can't even boot into the stock rom

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

[SOLVED] Need some help - can't access anything but fastboot - broken partition table

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!