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.
Related
I have found threads where this was asked too but it didn't get solved or it did but for a specific device.
I have a OPX with OOS 3.1.4
In command prompt typed "fastboot oem device-info" it gives me this info "device unlocked true" typed "fastboot flash recovery recovery.img" i named my recovery file "recovery" obviously. i get info
target reported max download size of 536870912 bytes
sending 'recovery' (14758 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.313s]
finished. total time: 0.844s
but when i reboot to my recovery it is still the stock OP recovery.
medick_ said:
I have found threads where this was asked too but it didn't get solved or it did but for a specific device.
I have a OPX with OOS 3.1.4
In command prompt typed "fastboot oem device-info" it gives me this info "device unlocked true" typed "fastboot flash recovery recovery.img" i named my recovery file "recovery" obviously. i get info
target reported max download size of 536870912 bytes
sending 'recovery' (14758 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.313s]
finished. total time: 0.844s
but when i reboot to my recovery it is still the stock OP recovery.
Click to expand...
Click to collapse
after flashing by "fastboot flash recovery recovery.img", boot into recovery directly by giving this cmd "fastboot boot recovery.img" this time it should overwrite your stock op recovery. try this and report back.
I'm assuming your trying to immediately boot into recovery after flashing because it will overwrite it. You can try the command "fastboot erase recovery" before flashing twrp. After flashing recovery completely turn off the phone. Then hold down volume down and proceed powering on into recovery. Sorry for the step by step if your not a noob just have to make sure we cover step by step. The above post is the proper way to boot after flashing try it first.
cva_kabil said:
after flashing by "fastboot flash recovery recovery.img", boot into recovery directly by giving this cmd "fastboot boot recovery.img" this time it should overwrite your stock op recovery. try this and report back.
Click to expand...
Click to collapse
Thanks for the reply
This is the the info i get:
downloading 'boot.img'...
OKAY [ 0.531s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.578s
And it stays in fastboot mode (guessing cause the dtb wasn't found)
medick_ said:
Thanks for the reply
This is the the info i get:
downloading 'boot.img'...
OKAY [ 0.531s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.578s
And it stays in fastboot mode (guessing cause the dtb wasn't found)
Click to expand...
Click to collapse
Which recovery u tried?
Exodusche said:
I'm assuming your trying to immediately boot into recovery after flashing because it will overwrite it. You can try the command "fastboot erase recovery" before flashing twrp. After flashing recovery completely turn off the phone. Then hold down volume down and proceed powering on into recovery. Sorry for the step by step if your not a noob just have to make sure we cover step by step. The above post is the proper way to boot after flashing try it first.
Click to expand...
Click to collapse
When i boot it stays stuck on the OP logo so I want to try other methods before ereasing my recovery. Cause I think this will give me another problem. Of course if you have more knowledge about this problem and say that it works then i will try it
cva_kabil said:
Which recovery u tried?
Click to expand...
Click to collapse
this one https://dl.twrp.me/onyx/twrp-3.0.2-0-onyx.img.html
medick_ said:
this one https://dl.twrp.me/onyx/twrp-3.0.2-0-onyx.img.html
Click to expand...
Click to collapse
The one u flashed ll not work in oos 3.x.x as u r in new bootloader,
Try flashing this one.. this ll work https://www.androidfilehost.com/?fid=457095661767115910
cva_kabil said:
The one u flashed ll not work in oos 3.x.x as u r in new bootloader,
Try flashing this one.. this ll work https://www.androidfilehost.com/?fid=457095661767115910
Click to expand...
Click to collapse
thanks mate this twrp worked. Is there a way to see if the recovery version is compatible or not? Just for should i get another phone or when i update too nougat
medick_ said:
thanks mate this twrp worked. Is there a way to see if the recovery version is compatible or not?
Click to expand...
Click to collapse
Not exactly,but as of now there is no official twrp for onyx new bootloader.. Luckily we hv smart dev like @Nachiket.Namjoshi Thank for dem.. And not sure about other devices,but u can update to nougat using this unofficial recovery,all AOSP,CM based Nougat roms are compatible with this..
cva_kabil said:
The one u flashed ll not work in oos 3.x.x as u r in new bootloader,
Try flashing this one.. this ll work https://www.androidfilehost.com/?fid=457095661767115910
Click to expand...
Click to collapse
how do you edit the thread title so it's [solved] ?
medick_ said:
how do you edit the thread title so it's [solved] ?
Click to expand...
Click to collapse
Found Go to edit, then advanced edit :good:
cva_kabil said:
Found Go to edit, then advanced edit :good:
Click to expand...
Click to collapse
i know who to contact when i have another problem ;p Thanks a lot
medick_ said:
i know who to contact when i have another problem ;p Thanks a lot
Click to expand...
Click to collapse
Lol happy to help
cva_kabil said:
Lol happy to help
Click to expand...
Click to collapse
hahahah unbelievable phone won't boot after installing superSU any advice
medick_ said:
hahahah unbelievable phone won't boot after installing superSU any advice
Click to expand...
Click to collapse
Welcome back use this one https://www.androidfilehost.com/?fid=24591000424944601
cva_kabil said:
Welcome back use this one https://www.androidfilehost.com/?fid=24591000424944601
Click to expand...
Click to collapse
quick question how do i place this in my internal storage since it won't boot
medick_ said:
quick question how do i place this in my internal storage since it won't boot
Click to expand...
Click to collapse
Connect ur device with usb cable to pc while u r in twrp screen...
cva_kabil said:
Connect ur device with usb cable to pc while u r in twrp screen...
Click to expand...
Click to collapse
thanks, i had to boot recovery with out usb cable else it wouldnt find my phone. I tried deleting the supersu before i came for help but it wouldnt find my phone
SOLVED & THREAD CLOSED
Hi,
Last week I got my phone stuck in a bootloop which led to me making a lot of mistakes, I flashed a boot.img as a kernel, I deleted my entire software, and I lost a lot of files. I currently have my phone in an error mode, it says I have to update the system again. I have access to fastboot but I do not have access to twrp (flashing the recovery doesn't work).
Can anyone help me with this problem?
pim8181 said:
Hi,
Last week I got my phone stuck in a bootloop which led to me making a lot of mistakes, I flashed a boot.img as a kernel, I deleted my entire software, and I lost a lot of files. I currently have my phone in an error mode, it says I have to update the system again. I have access to fastboot but I do not have access to twrp (flashing the recovery doesn't work).
Can anyone help me with this problem?
Click to expand...
Click to collapse
Is a really fastboot mode or error mode?
If it is fastboot what you see, Phone unlocked and FRP unlock?
kilroystyx said:
Is a really fastboot mode or error mode?
If it is fastboot what you see, Phone unlocked and FRP unlock?
Click to expand...
Click to collapse
I can get in both fastboot and error mode, I think fastboot is the most useful. It says PHONE Unlocked and FRP unlocked.
pim8181 said:
I can get in both fastboot and error mode, I think fastboot is the most useful. It says PHONE Unlocked and FRP unlocked.
Click to expand...
Click to collapse
-Do you know exactly which files or partitions did you mess?
-What is your region code and build number?
If you don’t know run this command is fastboot mode => fastboot oem get-build-number
-Do you have a TWRP backup from your device?
kilroystyx said:
-Do you know exactly which files or partitions did you mess?
-What is your region code and build number?
If you don’t know run this command is fastboot mode => fastboot oem get-build-number
-Do you have a TWRP backup from your device?
Click to expand...
Click to collapse
I don't know for sure which parts I messed up, but I do know these thing: I don't have an OS installed, and my kernel is a boot.img.
I don't know my region number for sure, but according to this post: https://forum.xda-developers.com/8-lite/how-to/huawei-regional-codes-t3740473 it should be C432.
My build number is ANE-LX1 8.0.0.126 (C432) and I should have a TWRP backup on my sd card from the moment my phone was only bootlooping.
pim8181 said:
I don't know for sure which parts I messed up, but I do know these thing: I don't have an OS installed, and my kernel is a boot.img.
I don't know my region number for sure, but according to this post: https://forum.xda-developers.com/8-lite/how-to/huawei-regional-codes-t3740473 it should be C432.
My build number is ANE-LX1 8.0.0.126 (C432) and I should have a TWRP backup on my sd card from the moment my phone was only bootlooping.
Click to expand...
Click to collapse
Do you have currently TWRP installed?
-Boot in the TWRP recovery and restore your backup.
-If your backup don't have all partitions let me know and I'll send you what is missing.
If you currently don't have TWRP installed?
-Go to fastboot mode and flash this TWRP
If boot then should be ok.
If remains bootlooping then you can wipe cache and reboot
If remains bootlooping you can test flash B126 with HuRUpdater
kilroystyx said:
Do you have currently TWRP installed?
-Boot in the TWRP recovery and restore your backup.
-If your backup don't have all partitions let me know and I'll send you what is missing.
If you currently don't have TWRP installed?
-Go to fastboot mode and flash this TWRP
If boot then should be ok.
If remains bootlooping then you can wipe cache and reboot
If remains bootlooping you can test flash B126 with HuRUpdater
Click to expand...
Click to collapse
I can't install TWRP, I currently install it by flashing the file as a recovery_ramdisk.
After it is flashed I execute the command fastboot reboot and hold volume up whilst disconnecting my phone from my PC.
Do you have any tips?
pim8181 said:
I can't install TWRP, I currently install it by flashing the file as a recovery_ramdisk.
After it is flashed I execute the command fastboot reboot and hold volume up whilst disconnecting my phone from my PC.
Do you have any tips?
Click to expand...
Click to collapse
No, you are doing right. Can you post the output from fastboot during the installation?
kilroystyx said:
No, you are doing right. Can you post the output from fastboot during the installation?
Click to expand...
Click to collapse
Code:
fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
gives:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.689s]
writing 'recovery_ramdisk'...
OKAY [ 0.122s]
finished. total time: 0.811s
Since I can't boot in TWRP by holding down the volume up button when rebooting I tried to use the boot command:
Code:
fastboot boot TWRP_3.2.1-0_ANE-LX1_Full_01.img
downloading 'boot.img'...
OKAY [ 0.690s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.695s
pim8181 said:
Code:
fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
gives:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.689s]
writing 'recovery_ramdisk'...
OKAY [ 0.122s]
finished. total time: 0.811s
Since I can't boot in TWRP by holding down the volume up button when rebooting I tried to use the boot command:
Code:
fastboot boot TWRP_3.2.1-0_ANE-LX1_Full_01.img
downloading 'boot.img'...
OKAY [ 0.690s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.695s
Click to expand...
Click to collapse
I don't believe that fastboot boot can work...
That is strange...
Can you flash TWRP one more time?
After successful flash don't use the command fastboot reboot
Unplug the USB cable and press ON/OFF and VOL+ and stay pressings until you see TWRP screen.
kilroystyx said:
I don't believe that fastboot boot can work...
That is strange...
Can you flash TWRP one more time?
After successful flash don't use the command fastboot reboot
Unplug the USB cable and press ON/OFF and VOL+ and stay pressings until you see TWRP screen.
Click to expand...
Click to collapse
It didn't work , maybe I can flash the stock system image from fastboot?
pim8181 said:
It didn't work , maybe I can flash the stock system image from fastboot?
Click to expand...
Click to collapse
Yes, system, cust, recovery_ramdisk.... all partions that might be mess by you.
kilroystyx said:
Yes, system, cust, recovery_ramdisk.... all partions that might be mess by you.
Click to expand...
Click to collapse
I don't know how to get these ones can you explain it to me?
pim8181 said:
I don't know how to get these ones can you explain it to me?
Click to expand...
Click to collapse
Check this thread, this applies to recovery_ramdisk but for all other partitions is the same.
kilroystyx said:
Check this thread, this applies to recovery_ramdisk but for all other partitions is the same.
Click to expand...
Click to collapse
It worked, many thanks for your help!
For those that have issues with the programme, I had to uncheck the verify header checksum button in the settings file in order for it to work properly.
kilroystyx said:
Do you have currently TWRP installed?
-Boot in the TWRP recovery and restore your backup.
-If your backup don't have all partitions let me know and I'll send you what is missing.
If you currently don't have TWRP installed?
-Go to fastboot mode and flash this TWRP
If boot then should be ok.
If remains bootlooping then you can wipe cache and reboot
If remains bootlooping you can test flash B126 with HuRUpdater
Click to expand...
Click to collapse
I guess I spoke too soon, I can get my phone in TWRP but it continues to bootloop.
pim8181 said:
I guess I spoke too soon, I can get my phone in TWRP but it continues to bootloop.
Click to expand...
Click to collapse
Did you do wipes?
If didn't work use your TWRP backup or use HuRUpdater
kilroystyx said:
Did you do wipes?
If didn't work use your TWRP backup or use HuRUpdater
Click to expand...
Click to collapse
My TWRP is completely lost and the tool doesn't seem to work, I wiped data cache and dalvik.
When you flash a rom aren't you just supposed to flash the rom itself, when I bricked my phone by installing Xposed I just reflashed the rom it's sytem image and a boot image. How should I do it?
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.
Apologies if I should have searched harder. My understanding is that touch screen issues like this happen when the firmware you flash isn't quite compatible with your device. I've triple checked the stuff I downloaded, and I'm not seeing how it could be that. Maybe I did something else stupid? This is my first time rooting anything.
Product/Variant (as seen in bootloader): sofia XT2041-4 64GB PVT
The boot.img I downloaded: lolinet's firmware/moto/sofia/official/RETUS/ (the august 31 one. Currently trying with the earlier one, but the download is taking forever)
Magisk version: 7.5.1
I only have a linux laptop, so the rescue and smart assistant appears to be off the table
Here's what I did:
Downloaded the boot.img from lolinet
patched it using magisk
flashed it using fastboot
How I flashed it:
Code:
~/Downloads$ fastboot flash boot magisk_patched.img
target reported max download size of 805261312 bytes
sending 'boot_b' (12136 KB)...
OKAY [ 0.376s]
writing 'boot_b'...
OKAY [ 0.069s]
finished. total time: 0.446s
I booted up after this, and I couldn't use the touchscreen. Then I noticed the boot_b thing, so I did the following to do both partitions (although I have no idea if this is what you're supposed to do):
Code:
~/Downloads$ fastboot flash boot_a magisk_patched.img
target reported max download size of 805261312 bytes
sending 'boot_a' (12136 KB)...
OKAY [ 0.350s]
writing 'boot_a'...
OKAY [ 0.076s]
finished. total time: 0.425s
~/Downloads$ fastboot flash boot_b magisk_patched.img
target reported max download size of 805261312 bytes
sending 'boot_b' (12136 KB)...
OKAY [ 0.370s]
writing 'boot_b'...
OKAY [ 0.214s]
finished. total time: 0.584s
No dice..
Next, I tried to just use the unpatched boot.img to restore things.
Code:
~/Downloads$ fastboot flash boot_a XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/boot.img
target reported max download size of 805259264 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 1.908s]
writing 'boot_a'...
OKAY [ 0.696s]
finished. total time: 2.604s
~/Downloads$ fastboot flash boot_b XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/boot.img
target reported max download size of 805259264 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.949s]
writing 'boot_b'...
OKAY [ 0.525s]
finished. total time: 2.474s
once again, no dice..this time I didn't even get to the lockscreen. Just stuck on the moto logo
Any idea what I've done wrong? Would really appreciate some help with this.
Update: I tried with the other boot.img from lolinet, doesn't get to lockscreen. Then I tried a factory reset with twrp, and flashing the earlier boot.img and I got to the setup screen, but still no touch.
Update 2: I managed to get omnirom flashed, and that's working so far! I am still curious to know why the touch screen issues popped up..will be useful next time I want to flash stock
check the forums for the g7 play, I've found topics about that kind of issue.
There's a few touchscreen vendors used for the same device, and they use different drivers basically.
Got a link by any chance? The ones I've seen are twrp related or because of the wrong firmware.
Any idea how to figure out which set is right for my phone?
Here is solution: get full ROM through LMSA and flash components through bootloader and fastbootd
* boot, recovery, dtbo, vbmeta, super flashed in fastbootd (adb reboot fastboot)
* All other actions done in bootloader (adb reboot bootloader)
mingkee said:
Here is solution: get full ROM through LMSA and flash components through bootloader and fastbootd
* boot, recovery, dtbo, vbmeta, super flashed in fastbootd (adb reboot fastboot)
* All other actions done in bootloader (adb reboot bootloader)
Click to expand...
Click to collapse
Can this be done without fastbootd? i stupidly flashed twrp (which doesnt work). so I dont have stock recovery to get into fastbootd. Can this be done using regular fastboot?
Or any way to flash a stock rom using just fastboot? the rom i have does not have 'flash all' so im not sure what to do from here.
If you get the recovery image from lolinet, you can boot that (or flash recovery) and then enter fastbootd
cnoevl21 said:
Can this be done without fastbootd? i stupidly flashed twrp (which doesnt work). so I dont have stock recovery to get into fastbootd. Can this be done using regular fastboot?
Or any way to flash a stock rom using just fastboot? the rom i have does not have 'flash all' so im not sure what to do from here.
Click to expand...
Click to collapse
Solution:
Flash everything ***except*** those flashed in fastbootd
fastboot reboot bootloader
fastboot reboot fastboot
The last resort: use LMSA rescue, but your phone will be wiped
mingkee said:
Solution:
Flash everything ***except*** those flashed in fastbootd
fastboot reboot bootloader
fastboot reboot fastboot
The last resort: use LMSA rescue, but your phone will be wiped
Click to expand...
Click to collapse
when you say flash everything. is it just flashing the .img files? or literally everything?
Sorry, ive never had to manually flash before.
---------- Post added at 09:17 PM ---------- Previous post was at 09:15 PM ----------
nero075 said:
If you get the recovery image from lolinet, you can boot that (or flash recovery) and then enter fastbootd
Click to expand...
Click to collapse
ill have to try this. thanks. Ive tried to just boot the boot.img and it hasnt done anything. so ill do this to try and get into fastbootd.
nero075 said:
If you get the recovery image from lolinet, you can boot that (or flash recovery) and then enter fastbootd
Click to expand...
Click to collapse
Ok. ive gotten into fastbootd but have no idea what to do now. I assumed it was like flashing with regular fastboot. but when i type commands like fastboot flash boot boot.img i get a failed result no such file or directory
Hello friend,
Did you ever resolve your issue with the touchscreen?
I've just down the same thing using Magisk. Everything was fine until I flashed the magisk.patched.img. The device booted up but the touchscreen doesn’t work no matter what.
Please let me know of your solution.
Thank you kindly.
PamelaGirl said:
Hello friend,
Did you ever resolve your issue with the touchscreen?
I've just down the same thing using Magisk. Everything was fine until I flashed the magisk.patched.img. The device booted up but the touchscreen doesn’t work no matter what.
Please let me know of your solution.
Thank you kindly.
Click to expand...
Click to collapse
hey did you fix it or something? i got the same problem, and idk what to do, can you help?
I never solved it.
In the end I was able to get a Moto G8 Plus that I was able to unlock the bootloader and root using Magisk.
PamelaGirl said:
I never solved it.
In the end I was able to get a Moto G8 Plus that I was able to unlock the bootloader and root using Magisk.
Click to expand...
Click to collapse
sadly the phone i tried to root is the only phone that i have
I understand the frustration my friend. I tried and tried but it just doesn’t work with Moto G Power.
PamelaGirl said:
I understand the frustration my friend. I tried and tried but it just doesn’t work with Moto G Power.
Click to expand...
Click to collapse
i think i got how to do it, u need to use LENOVO MOTOROLA SMART ASSISTANT and it works i think, i am going to try it, there is a tutorial in this forum, sadly only works if u have windows, but i manage to go to a place that has windows pc https://forum.xda-developers.com/t/moto-g-power-flashing-guide.4159301/
klninja said:
i think i got how to do it, u need to use LENOVO MOTOROLA SMART ASSISTANT and it works i think, i am going to try it, there is a tutorial in this forum, sadly only works if u have windows, but i manage to go to a place that has windows pc https://forum.xda-developers.com/t/moto-g-power-flashing-guide.4159301/
Click to expand...
Click to collapse
That’s a good find. Please report back with your success so I stand corrected.
PamelaGirl said:
That’s a good find. Please report back with your success so I stand corrected.
Click to expand...
Click to collapse
a person already did this
That’s good news!
Now its your turn.
PamelaGirl said:
That’s good news!
Now its your turn.
Click to expand...
Click to collapse
i would like to ask a question, when ur g8 wasnt working did the phone charge or not? cus mine dont show how much battery i have
Sorry I honestly cannot recall. I was so frustrated at that time, blinded to get the root to work that I did not notice.
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