Every time I wanna flash Rom files with fastboot or adb side load
System partition failed to flash
even I have tried fastboot enhanced tool but it states all .img file is not logical even .img for stock rom.
Before using MSM tool I haven't faced this kinds of problems but once my device stuck in qualcom crush dump mode and I have to use MSM tool to unbrick my device and after that I think my partition type have changed and I can not flash any kind of rom. Every time I got the following error:
Invalid sparse file format at header magic
Sending sparse 'system_b' 1/5 (773795 KB) OKAY [ 17.926s]
Writing 'system_b' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
My bootloader is unlocked
I have searched a lot and didn't got any solution and there are many users they are also facing the same problem but didn't got any solutions.
Does anyone know how to fix this problem?
Use adb reboot fastboot instead of adb reboot bootloader
御坂19041号 said:
Use adb reboot fastboot instead of adb reboot bootloader
Click to expand...
Click to collapse
Fastboot working fine here no issue with fastboot.
nowshadalve1 said:
Every time I wanna flash Rom files with fastboot or adb side load
System partition failed to flash
even I have tried fastboot enhanced tool but it states all .img file is not logical even .img for stock rom.
Before using MSM tool I haven't faced this kinds of problems but once my device stuck in qualcom crush dump mode and I have to use MSM tool to unbrick my device and after that I think my partition type have changed and I can not flash any kind of rom. Every time I got the following error:
Invalid sparse file format at header magic
Sending sparse 'system_b' 1/5 (773795 KB) OKAY [ 17.926s]
Writing 'system_b' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
My bootloader is unlocked
I have searched a lot and didn't got any solution and there are many users they are also facing the same problem but didn't got any solutions.
Does anyone know how to fix this problem?
Click to expand...
Click to collapse
maybe on the wrong version or wrong recovery
dfm000 said:
maybe on the wrong version or wrong recovery
Click to expand...
Click to collapse
I have tried to flash fastboot stock rom also.....
Everytime says partition not found or volume full.
Look at the screenshot
nowshadalve1 said:
I have tried to flash fastboot stock rom also.....
Everytime says partition not found or volume full.
Click to expand...
Click to collapse
which oxygen os version you are on
dfm000 said:
which oxygen os version you are on
Click to expand...
Click to collapse
It's oos 11.2.7.7
After using MSM tool this problem appears before I can flash custom rom without any issue.
nowshadalve1 said:
It's oos 11.2.7.7
After using MSM tool this problem appears before I can flash custom rom withoutwh
Click to expand...
Click to collapse
which rom you trying to install
nowshadalve1 said:
It's oos 11.2.7.7
After using MSM tool this problem appears before I can flash custom rom without any issue.
Click to expand...
Click to collapse
use msm tool again to start fresh. update to version 11.2.8.8 from settings after that. use the recovery included with the rom provider. all should work well
dfm000 said:
use msm tool again to start fresh. update to version 11.2.8.8 from settings after that. use the recovery included with the rom provider. all should work well
Click to expand...
Click to collapse
I have tried this process so many times but still not working.
I can't fastboot any system Img any fix?
Every time I wanna flash Rom img files with fastboot System partition failed to flash Invalid sparse file format at header magic Sending sparse 'system_b' 1/5 (773795 KB) OKAY [ 17.926s] Writing 'system_b' FAILED (remote: 'Partition not...
forum.xda-developers.com
Check the link he also facing same problem...
nowshadalve1 said:
I have tried this process so many times but still not working.
I can't fastboot any system Img any fix?
Every time I wanna flash Rom img files with fastboot System partition failed to flash Invalid sparse file format at header magic Sending sparse 'system_b' 1/5 (773795 KB) OKAY [ 17.926s] Writing 'system_b' FAILED (remote: 'Partition not...
forum.xda-developers.com
Check the link he also facing same problem...
Click to expand...
Click to collapse
https://t.me/OnePlus9ROfficial ask here
Finally I got the solution :
1. update the oos to 11.2.8.8 from system updater.
2. Then unlock the bootloader. -> fastboot flashing unlock
3. Then flash custom recovery -> fastboot flash recovery recovery.img
4.Then enable adb sideload.
5. Then flash rom using-> adb sideload rom.zip
( After 47% it will show an error msg but don't worry)
6. Then back to recovery and formate user data.(most important otherwise you will stuck in bootloop and have to use msm tool)
7. Then reboot to system.
Done.
Who will face this problem on future follow the steps.
Thanks to https://t.me/OnePlus9ROfficial
And also thanks you bro @dfm000
im unable to enter fastboot mode after updating to OOS 12... anyone facing this issue?
gohaaron said:
im unable to enter fastboot mode after updating to OOS 12... anyone facing this issue?
Click to expand...
Click to collapse
Yes I was facing this issue also...you have to rollback to oos 11.
nowshadalve1 said:
Yes I was facing this issue also...you have to rollback to oos 11.
Click to expand...
Click to collapse
i have... so r u saying i need to root from OOS 11? my phone got bricked just now i had to use Msmtool to reflash back to OOS 11... but ive updated back to 12
Yes currently you need to root from oos 11. I don't weather you can root your device from oos 12 or not.
Ask here: https://t.me/OnePlus9ROfficial
And using MSM tool there is no big deal with Android 12. You will flash your device in edl mode so everything will be fine.
nowshadalve1 said:
Yes currently you need to root from oos 11. I don't weather you can root your device from oos 12 or not.
Ask here: https://t.me/OnePlus9ROfficial
And using MSM tool there is no big deal with Android 12. You will flash your device in edl mode so everything will be fine.
Click to expand...
Click to collapse
ok ive joined thanks
gohaaron said:
ok ive joined thanks
Click to expand...
Click to collapse
If you wanna rollback from 12 to 11 can follow this article:
Steps to Downgrade or Rollback Oneplus 8, 8 pro, 8T & 9R from Stable OxygenOS 12 to OxygenOS 11
Oneplus user are not happy about changes done on OxygenOS 12 for Oneplus 8, 8 pro, 8T & 9R. Now users want to downgrade to Stable.
techibee.in
nowshadalve1 said:
If you wanna rollback from 12 to 11 can follow this article:
Steps to Downgrade or Rollback Oneplus 8, 8 pro, 8T & 9R from Stable OxygenOS 12 to OxygenOS 11
Oneplus user are not happy about changes done on OxygenOS 12 for Oneplus 8, 8 pro, 8T & 9R. Now users want to downgrade to Stable.
techibee.in
Click to expand...
Click to collapse
yes i follow him too... but i saw him enter fastboot with OOS 12
Related
Hey guys, I do not think this is a re-post of the other TWRP problems on Blackview 6000s. I have tried to install TWRP on my device many times. When I reboot into the custom recovery, a android with a danger sign appears. Instead of the TWRP screen. So what is the problem? (Android Noob here, please don't throw big developer words ).
Have tried
1. Changing USB ports / Using different computers
2. Flash_tool.exe
3. Flashing though adb/fastboot (is it the same?)
4. Different versions of TWRP.
5. Enabled USB debugging, OEM unlock & Install from Unknown Sources
Error Messages:
1. Running this -> adb reboot bootloader
error :no devices/emulators found (device was detected in "fastboot devices")
2. Running this -> fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (9318 KB)...
OKAY [ 0.892s]
writing 'recovery'...
OKAY [ 0.250s]
finished. total time: 1.142s
(However, TWRP is not installed?)
Problem is solved, if u need help pm me
Hi,
Its good phone? Worth to buy it?
off160 said:
Hi,
Its good phone? Worth to buy it?
Click to expand...
Click to collapse
Yes, it is. It is a damm good phone. Pm me for more details.
Managed to solve issue. flashed wrong TWRP file lol
ROM for the bv6000s MT6737T?
DoctStrange said:
Managed to solve issue. flashed wrong TWRP file lol
Click to expand...
Click to collapse
Hi did you manage to find a ROM for the phone?
Hello
Might I know what ROM you are using, and where you got the TWRP? I managed to flash TWRP once on the device, and then install SuperSU when it had a previous ROM.
But I flashed it with blackview's latest ROM I found on their website. Since then, when I flash TWRP, the phone won't boot anymore
I'm using TWRP3.0.0, which is the latest one I found with a scatter file.
How-to get a GSI running on your HTC U11 life Android One
Bootloader must be Unlocked
Stock Update to 8.1 must be installed
The Kernel must be Stock without any changes (no Magisk)
Make a Backup thats not Stored on Your Device
Remove the Google Account from the Device and Factory Reset the Device using the Recovery How-to
Download the correct GSI (arm64 a/b)
Flash the system.img using fastboot in Download Mode:
Code:
fastboot flash system_<slot> system.img
where <slot> is a or b depending on your active partition
Reboot the Device and Enjoy
Bugs with phh treble GSI (most others are based on this):
Mobile data doesnt work
Notification LED doesnt work
Audio Output only over speaker (known bug in this GSI for several devices)
List of compatible Roms
If you want to go back to Stock, just download the latest Full Firmware File here in post #2 and Restore the Device using SD Card method like written in post #1 of the same thread.
Updated, added the Guide
I try to flash GSI treble on HTC U11 Life but it doesn't work...
fastboot flash system_a /Users/thibautmaringer/Downloads/PixelExperienceP-arm64-ab.img
Sending sparse 'system_a' 1/3 (1048572 KB) OKAY [ 36.946s]
Writing sparse 'system_a' 1/3 (bootloader) HOSD CL#1033709
(bootloader) [email protected]
(bootloader) [email protected]%
FAILED ()
Finished. Total time: 111.730s
I don't understand...
this is the way to go when, i won't say if, HTC goes down and support will end for our phones.
maybe a bit more difficult than to just flash an image as we've always done, but not much more.
if HTC doesn't present a 9.0 before Xmas i will definitely install AOSP instead with no google at all.
titimar16 said:
I try to flash GSI treble on HTC U11 Life but it doesn't work...
fastboot flash system_a /Users/thibautmaringer/Downloads/PixelExperienceP-arm64-ab.img
Sending sparse 'system_a' 1/3 (1048572 KB) OKAY [ 36.946s]
Writing sparse 'system_a' 1/3 (bootloader) HOSD CL#1033709
(bootloader) [email protected]
(bootloader) [email protected]%
FAILED ()
Finished. Total time: 111.730s
I don't understand...
Click to expand...
Click to collapse
You should place the system.img (gsi) in the same folder where your adb and fastboot installation is. And you can see on the display of your device the progress of writing from 0% to 100% maybe you can have a look at it next time you flash something to see if it flashes at all.
saturday_night said:
You should place the system.img (gsi) in the same folder where your adb and fastboot installation is. And you can see on the display of your device the progress of writing from 0% to 100% maybe you can have a look at it next time you flash something to see if it flashes at all.
Click to expand...
Click to collapse
I tried that but it stuck on "system_a O%" then my cmd says "failed()"
./fastboot flash system_a system.img
Sending sparse 'system_a' 1/2 (1048572 KB) OKAY [ 35.131s]
Writing sparse 'system_a' 1/2 (bootloader) HOSD CL#1033709
(bootloader) [email protected]
(bootloader) [email protected]%
FAILED ()
Finished. Total time: 115.146s
I think that we can't flash GSI like that with the HTC U11 Life
titimar16 said:
I tried that but it stuck on "system_a O%" then my cmd says "failed()"
./fastboot flash system_a system.img
Sending sparse 'system_a' 1/2 (1048572 KB) OKAY [ 35.131s]
Writing sparse 'system_a' 1/2 (bootloader) HOSD CL#1033709
(bootloader) [email protected]
(bootloader) [email protected]%
FAILED ()
Finished. Total time: 115.146s
I think that we can't flash GSI like that with the HTC U11 Life
Click to expand...
Click to collapse
It works that way, already did it three times with three different systems. What file are you using? Do you even have the android one version of the u11 life or the Sense version?
saturday_night said:
It works that way, already did it three times with three different systems. What file are you using? Do you even have the android one version of the u11 life or the Sense version?
Click to expand...
Click to collapse
2 GSI: pixelexperience and phh-treble because I want to install Android P on my phone. I have the one version. So I'm on stock Android 8.1.
The files:
https://github.com/phhusson/treble_experimentations/releases/tag/v104 (ab arm64)
https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294 (ab arm64 v9.0.0.r1)
titimar16 said:
2 GSI: pixelexperience and phh-treble because I want to install Android P on my phone. I have the one version. So I'm on stock Android 8.1.
The files:
https://github.com/phhusson/treble_experimentations/releases/tag/v104 (ab arm64)
https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294 (ab arm64 v9.0.0.r1)
Click to expand...
Click to collapse
Android 9 GSIs are in an very early development stage and if you would read their threads you would know this. I dont even try it until phh treble has its first stable release.
saturday_night said:
Android 9 GSIs are in an very early development stage and if you would read their threads you would know this. I dont even try it until phh treble has its first stable release.
Click to expand...
Click to collapse
Okay, Thank you. And what have you tried ?
titimar16 said:
Okay, Thank you. And what have you tried ?
Click to expand...
Click to collapse
Android 8.1 GSIs
Today i tested for the first time an Android 9 GSI, phh treble got an update yesterday with a lot of bug fixes and it looks pretty good so far. Sadly we have the same bugs as with Android 8.1 GSIs. Its the first time phh treble gsi android 9 has GApps + Root integrated. I think those bugs we have are related to a faulty treble integration by HTC and cant be fixed by a dev of a GSI but its running good so far.
saturday_night said:
Today i tested for the first time an Android 9 GSI, phh treble got an update yesterday with a lot of bug fixes and it looks pretty good so far. Sadly we have the same bugs as with Android 8.1 GSIs and one additional bug. Its not possible to connect to hidden wifi networks, as long as the networks ssid is visible there is no problem to connect to it. Its the first time phh treble gsi android 9 has GApps + Root integrated. I think those bugs we have are related to a faulty treble integration by HTC and cant be fixed by a dev of a GSI but its running good so far.
Click to expand...
Click to collapse
Hi. Sorry but for me it doesn't work again. I did all the steps:
1) unlock bootloader
2) I'm on stock 2.13.401.1
3) I flashed using fastboot flash system_a system.img (from phh-treble 9 GSI with su and gapps)
4) it says again
Code:
fastboot flash system_a /Users/thibautmaringer/Downloads/system.img
Sending sparse 'system_a' 1/2 (1048572 KB) OKAY [ 32.109s]
Writing sparse 'system_a' 1/2 (bootloader) HOSD CL#1033709
(bootloader) [email protected]
(bootloader) [email protected]%
FAILED ()
Finished. Total time: 109.315s
and on my phone it says "flash success 2/2 start flashing" but nothing happened.
So can you explain how you did that well because for me it doesn't work.
titimar16 said:
Hi. Sorry but for me it doesn't work again. I did all the steps:
1) unlock bootloader
2) I'm on stock 2.13.401.1
3) I flashed using fastboot flash system_a system.img (from phh-treble 9 GSI with su and gapps)
4) it says again
Code:
fastboot flash system_a /Users/thibautmaringer/Downloads/system.img
Sending sparse 'system_a' 1/2 (1048572 KB) OKAY [ 32.109s]
Writing sparse 'system_a' 1/2 (bootloader) HOSD CL#1033709
(bootloader) [email protected]
(bootloader) [email protected]%
FAILED ()
Finished. Total time: 109.315s
and on my phone it says "flash success 2/2 start flashing" but nothing happened.
So can you explain how you did that well because for me it doesn't work.
Click to expand...
Click to collapse
Hmm, there are just two things where i could imagin that it causes a problem for you. First if you try to flash stuff from bootloader and not from download mode. Second would be a problematic usb connnection during the flash process. I have no other ideas sorry.
saturday_night said:
Hmm, there are just two things where i could imagin that it causes a problem for you. First if you try to flash stuff from bootloader and not from download mode. Second would be a problematic usb connnection during the flash process. I have no other ideas sorry.
Click to expand...
Click to collapse
Do you have
Code:
secure boot: PRODUCTION
? Because my usb connection is good and I flash files in "htc download mode"
Maybe can you explain precisely how you flash the GSI ?
titimar16 said:
Do you have
Code:
secure boot: PRODUCTION
? Because my usb connection is good and I flash files in "htc download mode"
Maybe can you explain precisely how you flash the GSI ?
Click to expand...
Click to collapse
1. I remove my Google Account from the Stock System
2. Reboot to bootloader - reboot to recovery and factory reset the device
3. reboot to bootloader and identify the active partition
4. reboot to download mode
5. flash Stock boot.img (because i was rooted before)
6. flash GSI system.img
If you need it more in detail just read the first posts in these two threads: https://forum.xda-developers.com/u11-life/how-to/collection-htc-u11-life-android-one-t3768265 https://forum.xda-developers.com/u11-life/how-to/treble-gsi-running-android-one-8-1-t3823015
And yes i have secure boot production and device state unlocked
saturday_night said:
1. I remove my Google Account from the Stock System
2. Reboot to bootloader - reboot to recovery and factory reset the device
3. reboot to bootloader and identify the active partition
4. reboot to download mode
5. flash Stock boot.img (because i was rooted before)
6. flash GSI system.img
If you need it more in detail just read the first posts in these two threads: https://forum.xda-developers.com/u11-life/how-to/collection-htc-u11-life-android-one-t3768265 https://forum.xda-developers.com/u11-life/how-to/treble-gsi-running-android-one-8-1-t3823015
And yes i have secure boot production and device state unlocked
Click to expand...
Click to collapse
What's your GSI file and android version ? (I mean the entire like 2.12.401....)
titimar16 said:
What's your GSI file and android version ? (I mean the entire like 2.12.401....)
Click to expand...
Click to collapse
I used the Stock boot.img from 2.12.401.17 and phh treble GSI arm64 a/b gapps su... exactly this file https://github.com/phhusson/treble_...download/v105/system-arm64-ab-gapps-su.img.xz
saturday_night said:
1. I remove my Google Account from the Stock System
2. Reboot to bootloader - reboot to recovery and factory reset the device
3. reboot to bootloader and identify the active partition
4. reboot to download mode
5. flash Stock boot.img (because i was rooted before)
6. flash GSI system.img
If you need it more in detail just read the first posts in these two threads: https://forum.xda-developers.com/u11-life/how-to/collection-htc-u11-life-android-one-t3768265 https://forum.xda-developers.com/u11-life/how-to/treble-gsi-running-android-one-8-1-t3823015
And yes i have secure boot production and device state unlocked
Click to expand...
Click to collapse
saturday_night said:
I used the Stock boot.img from 2.12.401.17 and phh treble GSI arm64 a/b gapps su... exactly this file https://github.com/phhusson/treble_...download/v105/system-arm64-ab-gapps-su.img.xz
Click to expand...
Click to collapse
And did you change something about CID of MID ?
titimar16 said:
And did you change something about CID of MID ?
Click to expand...
Click to collapse
No, dont change anything, that can cause a lot of problems
Hello Everyone!
I unlocked and installed TWRP on my P20 lite, but now I want to be able to install the updates of Huawei again (especially when Android P is about to release).
So how do I uninstall TWRP and if it's possbile lock my phone again?
(am not that amazing with Smartphone software, so just saying...)
Greets Louis
LouisJ444 said:
Hello Everyone!
I unlocked and installed TWRP on my P20 lite, but now I want to be able to install the updates of Huawei again (especially when Android P is about to release).
So how do I uninstall TWRP and if it's possbile lock my phone again?
(am not that amazing with Smartphone software, so just saying...)
Greets Louis
Click to expand...
Click to collapse
Maybe this thread somehow can helps you:
https://forum.xda-developers.com/huawei-p20-lite/help/req-stock-recovery-p20-lite-t3803027
Don't need lock bootloader to install or receive via OTA official updates.
Lock the bootloader is not possible (maybe it is, but is a pay service).
You can relock instead of lock, but don't do it if your device is not completely stock.
Within the little experience that I have with this team I have investigated the following, when flasheas the official roms by twrp the boatloader is blocked again and the twrp is erased
kilroystyx said:
Maybe this thread somehow can helps you:
https://forum.xda-developers.com/huawei-p20-lite/help/req-stock-recovery-p20-lite-t3803027
Don't need lock bootloader to install or receive via OTA official updates.
Lock the bootloader is not possible (maybe it is, but is a pay service).
You can relock instead of lock, but don't do it if your device is not completely stock.
Click to expand...
Click to collapse
I still don't really understand how it works:
I downloaded the huawei extractor and extracted the files in a folder on my computer.
I got a update.zip file from my phone and extracted it on my computer.
But when I try to open the update.app file I get an error message saying:
https://i.gyazo.com/abce07c696fb31f15b95c832e3baa899.png
(if it doesn't work: ERECOVERY_VBMET.img: Invalid header crc - Expected: 42613 Got 18415)
LouisJ444 said:
I still don't really understand how it works:
I downloaded the huawei extractor and extracted the files in a folder on my computer.
I got a update.zip file from my phone and extracted it on my computer.
But when I try to open the update.app file I get an error message saying:
https://i.gyazo.com/abce07c696fb31f15b95c832e3baa899.png
(if it doesn't work: ERECOVERY_VBMET.img: Invalid header crc - Expected: 42613 Got 18415)
Click to expand...
Click to collapse
Remove the verification on the settings, check pic enclosed.
Mannuok said:
Within the little experience that I have with this team I have investigated the following, when flasheas the official roms by twrp the boatloader is blocked again and the twrp is erased
Click to expand...
Click to collapse
Your are partially correct.
Flashing official firmware with TWRP, have to be done with HuRUpdater, during installation the TWRP is replaced by stock recovery, then is your decision keep it or not.
About lock bootloader, mine is unlocked since day one and every time that I install new firmware it keep it unlocked. My experience so far is installing ANE-LX1 firmware in my ANE-LX1 device, probably with other firmware like ANE-AL00 or ANE-TL00 it can be different.
kilroystyx said:
Remove the verification on the settings, check pic enclosed.
Click to expand...
Click to collapse
So I can't seem to do "adb reboot bootloader" It will just go to the system.
And when I manually go into the bootloader and try to flash it, I get this error
Before this I tried to flash an other recovery on it which I found on a guide, but after I did that TWRP did get removed but I can't get on the recovery anymore and updating doesn't work either.
LouisJ444 said:
So I can't seem to do "adb reboot bootloader" It will just go to the system.
And when I manually go into the bootloader and try to flash it, I get this error
Before this I tried to flash an other recovery on it which I found on a guide, but after I did that TWRP did get removed but I can't get on the recovery anymore and updating doesn't work either.
Click to expand...
Click to collapse
In the Fastboot&Rescue Mode screen did you see phone unlocked and FRP unlock ?
Can you share all commands that you are using, can be text like you see bellow:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.861s]
writing 'recovery_ramdisk'...
OKAY [ 0.109s]
finished. total time: 0.970s
Are you trying to use command recovery instead of recovery_ramdisk?
kilroystyx said:
In the Fastboot&Rescue Mode screen did you see phone unlocked and FRP unlock ?
Can you share all commands that you are using, can be text like you see bellow:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.861s]
writing 'recovery_ramdisk'...
OKAY [ 0.109s]
finished. total time: 0.970s
Are you trying to use command recovery instead of recovery_ramdisk?
Click to expand...
Click to collapse
1. It says: Phone Unlocked
FRP Unlock
2. When I was in this screen I do:
- cd C:\Users\Louis\Desktop\platform-tools
- fastboot flash recovery RECOVERY_RAMDIS.img
then it gives the error
3. When I try to do it normally, I do:
- cd C:\Users\Louis\Desktop\platform-tools
- adb reboot bootloader
LouisJ444 said:
1. It says: Phone Unlocked
FRP Unlock
2. When I was in this screen I do:
- cd C:\Users\Louis\Desktop\platform-tools
- fastboot flash recovery RECOVERY_RAMDIS.img
then it gives the error
3. When I try to do it normally, I do:
- cd C:\Users\Louis\Desktop\platform-tools
- adb reboot bootloader
Click to expand...
Click to collapse
You have to use recovery_ramdisk because this is the name of the partition in this Android version.
I assume that you didn't change the name of the stock recovery extracted, for your case the right command is:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
kilroystyx said:
You have to use recovery_ramdisk because this is the name of the partition in this Android version.
I assume that you didn't change the name of the stock recovery extracted, for your case the right command is:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
Click to expand...
Click to collapse
Thanks, that seemed to work!
kilroystyx said:
Your are partially correct.
Flashing official firmware with TWRP, have to be done with HuRUpdater, during installation the TWRP is replaced by stock recovery, then is your decision keep it or not.
About lock bootloader, mine is unlocked since day one and every time that I install new firmware it keep it unlocked. My experience so far is installing ANE-LX1 firmware in my ANE-LX1 device, probably with other firmware like ANE-AL00 or ANE-TL00 it can be different.
Click to expand...
Click to collapse
Where I get the original romes of Huawei???
Mannuok said:
Where I get the original romes of Huawei???
Click to expand...
Click to collapse
web version:
http://pro-teammt.ru/firmware-database/?firmware_model=&firmware_page=0
android version:
https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder
some tips:
https://forum.xda-developers.com/hu...om-official-emui-8-0-huawei-p20-lite-t3773999
kilroystyx said:
Your are partially correct.
Flashing official firmware with TWRP, have to be done with HuRUpdater, during installation the TWRP is replaced by stock recovery, then is your decision keep it or not.
About lock bootloader, mine is unlocked since day one and every time that I install new firmware it keep it unlocked. My experience so far is installing ANE-LX1 firmware in my ANE-LX1 device, probably with other firmware like ANE-AL00 or ANE-TL00 it can be different.
Click to expand...
Click to collapse
ANE LX3 no funciona asi,
Mannuok said:
ANE LX3 no funciona asi,
Click to expand...
Click to collapse
what do you mean by that?
kilroystyx said:
Maybe this thread somehow can helps you:
https://forum.xda-developers.com/huawei-p20-lite/help/req-stock-recovery-p20-lite-t3803027
Don't need lock bootloader to install or receive via OTA official updates.
Lock the bootloader is not possible (maybe it is, but is a pay service).
You can relock instead of lock, but don't do it if your device is not completely stock.
Click to expand...
Click to collapse
Hi all,
Getting a "lock" state is possible indeed. I believe you @kilroystyx had seen it as well on @Merlin_99 's thread:
https://forum.xda-developers.com/huawei-p20-lite/how-to/root-how-to-install-update-t3841557
This will erase all data, except from sdcards of course
Cheers,
AS
Mannuok said:
ANE LX3 no funciona asi,
Click to expand...
Click to collapse
ars_chelsea said:
Hi all,
Getting a "lock" state is possible indeed. I believe you @kilroystyx had seen it as well on @Merlin_99 's thread:
https://forum.xda-developers.com/huawei-p20-lite/how-to/root-how-to-install-update-t3841557
This will erase all data, except from sdcards of course
Cheers,
AS
Click to expand...
Click to collapse
You are right, first post was on the August 20th, at that time I didn't knew that was possible lock bootloader, only after Merlin_99 create that thread on September 12th.
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/huawei-p20-pro/how-to/guide-erecovery-hisuite-failing-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
benkiller47 said:
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/huawei-p20-pro/how-to/guide-erecovery-hisuite-failing-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
Click to expand...
Click to collapse
First, in TWRP, advance wipe everything! Now, you need a pc, connect the phone to PC with a USB, on pc, download any ROM you want (and gapps if you want) now transfer the files to your phone and then flash them, izi,
Thumbs up if I was useful.
DankMemz said:
First, in TWRP, advance wipe everything! Now, you need a pc, connect the phone to PC with a USB, on pc, download any ROM you want (and gapps if you want) now transfer the files to your phone and then flash them, izi,
Thumbs up if I was useful.
Click to expand...
Click to collapse
Hi thank you for your help , unfortunatly at the end of the ROM installation , my phone reboot back to fastboot mode , no matter wich ROM i boot in it
also good to precise i have a Huawei p20 pro
benkiller47 said:
Hi thank you for your help , unfortunatly at the end of the ROM installation , my phone reboot back to fastboot mode , no matter wich ROM i boot in it
also good to precise i have a Huawei p20 pro
Click to expand...
Click to collapse
Try reinstalling stock firmware trough download mode...
Try reinstalling the twrp image. Helped me once
It's pretty standard hardware as far as phones go. No weird under display fingerprint reader or anything. Anyone try a GSI ROM? It might "just work" or "almost just work but you need to run a few commands to fix something".
triggerlord said:
It's pretty standard hardware as far as phones go. No weird under display fingerprint reader or anything. Anyone try a GSI ROM? It might "just work" or "almost just work but you need to run a few commands to fix something".
Click to expand...
Click to collapse
I'm looking at an android 11 based GSI rom right now. The main problem is that I can't get TWRP to work properly. TWRP boots, but I have no touch functionality and thus cannot interact with it, and an OTG connected mouse doesn't work either. Do you know how to fix this?
thebestofall007 said:
I'm looking at an android 11 based GSI rom right now. The main problem is that I can't get TWRP to work properly.
Click to expand...
Click to collapse
Just saying, you don't need TWRP to flash GSIs.
AndyYan said:
Just saying, you don't need TWRP to flash GSIs.
Click to expand...
Click to collapse
How do you do that?
thebestofall007 said:
How do you do that?
Click to expand...
Click to collapse
fastboot flash system <name-of-image>
triggerlord said:
fastboot flash system <name-of-image>
Click to expand...
Click to collapse
Oh OK.
thebestofall007 said:
Oh OK.
Click to expand...
Click to collapse
If you do try one I'd recommend trying the latest build of PHH's AOSP. You'll want to use one of these images.
triggerlord said:
If you do try one I'd recommend trying the latest build of PHH's AOSP. You'll want to use one of these images.
Click to expand...
Click to collapse
I tried flashing the "system-roar-arm64-ab-vanilla" image and I get an error in the end: "FAILED (remote: Operation not permitted)" I did extract the img file from the archive.
thebestofall007 said:
I tried flashing the "system-roar-arm64-ab-vanilla" image and I get an error in the end: "FAILED (remote: Operation not permitted)"
Click to expand...
Click to collapse
Did you unlock the bootloader? Did you erase user data first?
triggerlord said:
Did you unlock the bootloader? Did you erase user data first?
Click to expand...
Click to collapse
I unlocked the bootloader but I didn't erase user data.
thebestofall007 said:
I unlocked the bootloader but I didn't erase user data.
Click to expand...
Click to collapse
Ah if that doesn't work try "system_a" instead. Anyway you always have to erase the data partition or it could cause problems.
triggerlord said:
Ah if that doesn't work try "system_a" instead. Anyway you always have to erase the data partition or it could cause problems.
Click to expand...
Click to collapse
It's still doing it. It's already using system_a. Here is my terminal output:
[email protected]:~/Desktop/moto g power$ sudo fastboot flash system '/home/lou/Downloads/system-roar-arm64-ab-vanilla.img'
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/4 (458752 KB)...
OKAY [ 20.605s]
writing 'system_a' 1/4...
OKAY [ 2.573s]
sending sparse 'system_a' 2/4 (458752 KB)...
OKAY [ 21.022s]
writing 'system_a' 2/4...
FAILED (remote: Operation not permitted)
finished. total time: 46.437s
I don't think it can write to the "system" partition, if that has anything to do with it.
What's funny is that I was able to flash a magisk patched boot image file to the boot partition to root my phone with no problem. So it can't be a locked bootloader. I don't know...
thebestofall007 said:
What's funny is that I was able to flash a magisk patched boot image file to the boot partition to root my phone with no problem. So it can't be a locked bootloader. I don't know...
Click to expand...
Click to collapse
Does your device use fastbootd ?
Check with
Code:
fastboot getvar is-userspace
sd_shadow said:
Does your device use fastbootd ?
Check with
Code:
fastboot getvar is-userspace
Click to expand...
Click to collapse
Yes it does use fastbootd actually. I can boot to fastbootd from the recovery and it says fastbootd on top of the screen when I boot to it. I can flash files in both fastbootd and bootloader modes, HOWEVER, I get different errors with each one when I flash the GSI image. When I flash with fastbootd, I get the terminal output I posted earlier, but in bootloader mode I get "(bootloader) Preflash validation failed".
thebestofall007 said:
Yes it does use fastbootd actually. I can boot to fastbootd from the recovery and it says fastbootd on top of the screen when I boot to it. I can flash files in both fastbootd and bootloader modes, HOWEVER, I get different errors with each one when I flash the GSI image. When I flash with fastbootd, I get the terminal output I posted earlier, but in bootloader mode I get "(bootloader) Preflash validation failed".
Click to expand...
Click to collapse
You know it might be comparing your GSI signature to the stock ROM. You might have to erase system first. Worst comes to worst you can just use the Lenovo Smart Assistant to flash the stock ROM back.
triggerlord said:
You know it might be comparing your GSI signature to the stock ROM. You might have to erase system first. Worst comes to worst you can just use the Lenovo Smart Assistant to flash the stock ROM back.
Click to expand...
Click to collapse
I erased system with fastboot erase system. Same errors unfortunately. I'm wondering if the system is part of the "super" partition and fastboot cannot write to it. I was also wondering if I can do fastboot within twrp, which CAN write to system.
I found a little info on the android development site that details what might be happening. It has to do with the writing to dynamic partitions giving an error. Here it is.
thebestofall007 said:
I erased system with fastboot erase system. Same errors unfortunately. I'm wondering if the system is part of the "super" partition and fastboot cannot write to it. I was also wondering if I can do fastboot within twrp, which CAN write to system.
Click to expand...
Click to collapse
TWRP can natively flash GSIs. You just have to change the image type from flashable zip to img.
thebestofall007 said:
I found a little info on the android development site that details what might be happening. It has to do with the writing to dynamic partitions giving an error. Here it is.
Click to expand...
Click to collapse
I wouldn't recommend using the force argument.. That might change the logical partition to a physical one and the LSA might fail to flash the stock ROM. Worst case that might brick it.