Related
So I flashed Euphoria OS in my Zenfone 2 ZE551ML 16GB variant but now I wanna go back to stock rom. So I downloaded a full stock rom version WW-2.19.40.22. I booted into TWRP recovery, wiped data and all and then flashed the stock rom and then this assert failed get prop error appears. I can't flash the stock rom and I'm stuck with Euphoria. Any info on how I can get back to stock rom?
hello i think your devices is unlock you can use a system.img to revert back to stock if you came from custom rom
fastboot erase data
fastboot erase cache
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
then reboot if you stuck on asus logo re flash again the system.img and your done..
---
second option is flash stock recovery and boot.img and use adb sideload for flashing stock rom good luck
knoneNull said:
hello i think your devices is unlock you can use a system.img to revert back to stock if you came from custom rom
fastboot erase data
fastboot erase cache
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
then reboot if you stuck on asus logo re flash again the system.img and your done..
---
second option is flash stock recovery and boot.img and use adb sideload for flashing stock rom good luck
Click to expand...
Click to collapse
I'm unable to use the adb sideload method. My device disconnects when I activate sideload on it but it reconnects when I cancel it.
caveat13 said:
I'm unable to use the adb sideload method. My device disconnects when I activate sideload on it but it reconnects when I cancel it.
Click to expand...
Click to collapse
try to charge it first , then try again, if not work i think the best is send to service center or try to message shakalaca may be he can help you
Hi All,
I am facing issues with flashing any custom recovery on my oneplus 3 device running on open beta 30.
Everytime I flash a recovery, it says finished without an error but throw me back to stock recovery, After searching some available option I can across several links and tried following suggestions so far:
1) used "Fastboot boot recovery.img": Error "FAILED (remote: bootimage header fields are invalid)"
Thought the downloaded recovery file is corrupted, downloaded it from official site and other locations, all with same hash value and same problem
2) Searched an option to disable "update cm recovery", unable to location this setting on my device
3) Tried to flash recovery then poweroff and then reboot to recovery using power button and volume down key, did not worked.
recoveries I have tried:
blu_spark TWRP and original TWRP
device-info:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Have console: false
(bootloader) Selinux type: <none>
(bootloader) Boot_mode: normal
(bootloader) Kmemleak_detect: false
(bootloader) force_training: false
Anyone faced similar issue or found a way to fix this ?
Note: Device not rooted, bootloader unlocked.
You could try "fastboot format userdata" in fastboot mode. Backup your data first. I think it was something with encryption. Same case with my friend.
oopstairs said:
You could try "fastboot format userdata" in fastboot mode. Backup your data first. I think it was something with encryption. Same case with my friend.
Click to expand...
Click to collapse
Encryption is for the data partition not the recovery one. Are you using correct adb drivers? Works all fine here.
Puddi_Puddin said:
Encryption is for the data partition not the recovery one. Are you using correct adb drivers? Works all fine here.
Click to expand...
Click to collapse
Yes, I have verified ADB and fastboot on another device, its working fine.
I did tried two different systems for OP3 device, Ubuntu and windows. Same result in both cases, no success.
anandpandey said:
Yes, I have verified ADB and fastboot on another device, its working fine.
I did tried two different systems for OP3 device, Ubuntu and windows. Same result in both cases, no success.
Click to expand...
Click to collapse
Which recovery are you trying to flash?
Puddi_Puddin said:
Which recovery are you trying to flash?
Click to expand...
Click to collapse
recoveries I have tried:
blu_spark TWRP and official TWRP
Try:
fastboot flash recovery recovery.img
cmnaka said:
Try:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Thanks, that was the first thing i tried.
anandpandey said:
Thanks, that was the first thing i tried.
Click to expand...
Click to collapse
Did you try flashing SuperSU immediately after flashing TWRP and before booting into system?
When I flashed TWRP alone, I could boot back into TWRP but after booting into system, the next boot to recovery will take me to the stock one. I solved it by flashing SuperSu immediately after flashing TWRP.
tnsmani said:
Did you try flashing SuperSU immediately after flashing TWRP and before booting into system?
When I flashed TWRP alone, I could boot back into TWRP but after booting into system, the next boot to recovery will take me to the stock one. I solved it by flashing SuperSu immediately after flashing TWRP.
Click to expand...
Click to collapse
The problem with this approach is that I cound never reach to TWRP so to flash SuperSu or Magisk.
Soon after I flash TWRP, the repory enters into a loop.
Still not able to flash a custom rom, any other suggested options ?
This is a nonsense answer but can try , Rename to twrp or anything else other than recovery.img ( may be stock confused with same name )
anandpandey said:
Still not able to flash a custom rom, any other suggested options ?
Click to expand...
Click to collapse
Told you already to flash SuperSu. Don't use TWRP to flash SuperSu. Use adb.
If I were you, I would wipe system, data, Dalvik and cache and flash the ROM first, all using adb. Then boot into the ROM. Then using adb, flash blu_spark's TWRP v 8.61 and immediately thereafter flash SuperSu v 2.79 SR5, again using adb. Then boot into TWRP and then into system.
I after getting the beta31 I ran out of dash charger and also could not get the recovery oos
so I went back to 5.0.1 and did not go back to giving the cherzer dash. I got now I put the beta 31 and firmware of beta 30
Our old twrp have been great compared to nothing but it isn't exactly fully working and freezes a lot on splash screen.
Thanks to @Stricted and @deadman96385 we now have a more functional twrp.
Support for A/B slots.
ADB working.
No need to flash full firmware. Just flash the vbmeta_patch.img and boot twrp.
!!BOOTLOADER MUST BE UNLOCKED!!
YOUR DATA WILL BE WIPED!!
Code:
fastboot flash vbmeta vbmeta_patch.img
fastboot boot twrp-3.3.1-test3.img
Now that we booted to TWRP it's time to format data.
Go to wipe -> format data -> type yes.
"Permanent" install of TWRP (optional):
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot and go to advanced settings.
Use the option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings so that it won't reboot to recovery instead of system..
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
This must be done every time you update your boot.img.
-------------------------------------------------------------------------------------------------------------------------------------------------------
# ROOT:
-----------
# First time:
# Method 1: Root, forced encryption disabled. Full access to data from twrp:
Flash Magisk and Disable_Dm-Verity_ForceEncrypt.zip.
# Method 2: Root only. Device still encrypted and won't be able to decrypt / mount data in twrp.
Magisk modules through Magisk manager still works:
Flash only Magisk.
----------------------------------------------------------------------------------------------------
# Fastboot flash update without loosing root or data:
----------------------------------------------------------------------------------------
# Already rooted with encryption disabled:
Extract the firmware zip to your adb/fastboot folder.
You already have the patched vbmeta flashed so just remove the stock vbmeta.img from the folder after extraction to avoid flashing it by mistake.
Flash full firmware without wipe. (Use cmds from below. Save as .bat to make it more simple.)
Boot twrp and then install it, fix recovery bootloop.
Reboot recovery, flash Magisk and Disable_Dm-Verity_ForceEncrypt.zip.
Boot system.
Code:
echo off
echo - UPDATE AND PRESERV ROOT -
fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.img
fastboot flash ldfw_a ldfw.img
fastboot flash ldfw_b ldfw.img
fastboot flash keystorage_a keystorage.img
fastboot flash keystorage_b keystorage.img
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash modem_a modem.bin
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.10
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot flash vendor_a vendor.img
fastboot reboot bootloader
pause 10
fastboot boot twrp-3.3.1-test3.img
echo TWRP is booting..
echo - install recovery ramdisk, fix bootloop, flash magisk & dm-verity zip.
echo - alternatively flash only magisk and Disable_Dm-Verity_ForceEncrypt.zip if you want to keep stock recovery.
pause
# Already rooted with device still encrypted:
Flash firmware update, except vbmeta.
Boot twrp and flash Magisk with adb sideload.
(alternative method: boot twrp and flash magisk patched boot.img)
Download TWRP: https://images.stricted.net/test/troika/twrp-3.3.1-test3.img
Download Magisk: https://github.com/topjohnwu/Magisk/releases
Download vbmeta_patch.img & Disable_Dm-Verity_ForceEncrypt.zip attached below.
PLEASE, DON't QUOTE THE WHOLE OP.
Great guide @tys0n and thank you to @Stricted and @deadman96385 for his work !
tys0n said:
Code:
fastboot flash vbmeta vbmeta_patch.img
fastboot boot twrp-3.3.1-test3.img
Click to expand...
Click to collapse
My Vision is already unlocked and rooted by the old TWRP method. Should I just do this step so I can update to the new TWRP, and then I can follow "encryption disabled" steps to update to a new firmware?
I suppose I can't enable encryption anymore without resetting data.
daekdroom said:
My Vision is already unlocked and rooted by the old TWRP method. Should I just do this step so I can update to the new TWRP, and then I can follow "encryption disabled" steps to update to a new firmware?
I suppose I can't enable encryption anymore without resetting data.
Click to expand...
Click to collapse
You're right. You can't switch between encrypted / non encrypted without a reset.
This update method have been working for me with the old twrp as well, but this new build is much better and more stable that I see no reason not to switch to the new one.
Actually, I think it may be better to first fastboot flash the new firmware (except vbmeta) so that you have a "clean" boot.img to start with if you're planning to use the install recovery ramdisk. At least if you have the old one installed already.
That's how I switched and I've had no problems.
Worked to my, Thnx
Good afternoon,
I'm trying to "patch" the TWRP as you indicate at the beginning of the first post.
When you say:
"For permanent install, use the" flash recovery ramdisk "option in twrp advanced settings"
What file do I have to flash?
Regards
gonzo1963 said:
Good afternoon,
I'm trying to "patch" the TWRP as you indicate at the beginning of the first post.
When you say:
"For permanent install, use the" flash recovery ramdisk "option in twrp advanced settings"
What file do I have to flash?
Regards
Click to expand...
Click to collapse
Sorry, I could have been more clear about this step in the description.
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot, go to advanced settings.
There's an option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings.
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
tys0n said:
Sorry, I could have been more clear about this step in the description.
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot, go to advanced settings.
There's an option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings.
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
Click to expand...
Click to collapse
Good evening,
One last question:
Currently I have permanently installed the TWRP.
Is it also necessary to do these last steps that you have added?
Regards
Enviado desde mi unknown mediante Tapatalk
gonzo1963 said:
Good evening,
One last question:
Currently I have permanently installed the TWRP.
Is it also necessary to do these last steps that you have added?
Regards
Enviado desde mi unknown mediante Tapatalk
Click to expand...
Click to collapse
Good afternoon,
Any answer?
Regards
Enviado desde mi unknown mediante Tapatalk
Bootloop
Dude, my phone was encrypted and unrooted. I flashed vbmeta then booted into twrp. Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop, then I flashed Magisk then I flashed the Disable DM Verity. Now I'm stuck in a recovery loop. The phone turns on, then android one screen, then reboots then goes to twrp...
What did I do wrong / miss?
"Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop."
Agter this restart the phone in recovery mode and then continue as explained.
Sorry in bad english
First of all, @tys0n thank you very much for your work. I got this phone for work, but since an unrooted Android device is almost useless to me, this is very much appreciated. Just a few annotations from my side, maybe they help someone.
1. Permanent TWRP install didn't work for me. TWRP was installed sucessfully but just like the dude above me, it would not boot to system, even after appying the bootloop fix. I had to reflash to fix this, so better be careful here!
2. I didnt want to lose encryption, so i chose method 2 for rooting. This works fine, but still I had to wipe data in the first place. Otherwise it would again not boot to system, but at least this time it told me that wiping would possibly fix this. However, after wiping encryption IS active. Maybe I did something wrong here but I don't know... Chosing method 1 seems to be the more straightforward option here.
3. Despite these issues, flashing updates seems to work just fine as described described in the OP, preserving data and root. I have only tried this once, from QSA30.62-24-6 to QSA30.62-33, which is currently the most recent patchlevel for RETEU devices. I even got the "successfully updated" notification afterwards, as if it was an OTA update
Preceptor said:
Dude, my phone was encrypted and unrooted. I flashed vbmeta then booted into twrp. Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop, then I flashed Magisk then I flashed the Disable DM Verity. Now I'm stuck in a recovery loop. The phone turns on, then android one screen, then reboots then goes to twrp...
What did I do wrong / miss?
Click to expand...
Click to collapse
same here !
sennator said:
First of all, @tys0n thank you very much for your work. I got this phone for work, but since an unrooted Android device is almost useless to me, this is very much appreciated. Just a few annotations from my side, maybe they help someone.
1. Permanent TWRP install didn't work for me. TWRP was installed sucessfully but just like the dude above me, it would not boot to system, even after appying the bootloop fix. I had to reflash to fix this, so better be careful here!
2. I didnt want to lose encryption, so i chose method 2 for rooting. This works fine, but still I had to wipe data in the first place. Otherwise it would again not boot to system, but at least this time it told me that wiping would possibly fix this. However, after wiping encryption IS active. Maybe I did something wrong here but I don't know... Chosing method 1 seems to be the more straightforward option here.
3. Despite these issues, flashing updates seems to work just fine as described described in the OP, preserving data and root. I have only tried this once, from QSA30.62-24-6 to QSA30.62-33, which is currently the most recent patchlevel for RETEU devices. I even got the "successfully updated" notification afterwards, as if it was an OTA update
Click to expand...
Click to collapse
Hi. Yes, you're right. After flashing the patched vbmeta we need to format data. I've made it more clear in OP now.
Thanks for pointing it out.
kArLiN_dRaKE_MX said:
same here !
Click to expand...
Click to collapse
Format data in twrp
It doesn't work for me (XT1970-1).
I did the process according to information method 2.
the system boots normally.
however magisk is not 'GREEN' like two pieces of information.
How is it going without ROOT, how do I put ROOT?
have another process after this information?
Thank you.
It worked.
I performed the process again.
and everything went well.
Thanks to everyone involved. :good:
gambiarraweb1 said:
It doesn't work for me (XT1970-1).
I did the process according to information method 2.
the system boots normally.
however magisk is not 'GREEN' like two pieces of information.
How is it going without ROOT, how do I put ROOT?
have another process after this information?
Thank you.
Click to expand...
Click to collapse
Just a quick question, when I have TWRP and root I can't pass the SafetyNet check, right?
Hello all. When I click on Internal storage, there are folders with names like "a16sgyx462" and so on, so I am not able to install TWRP permanently. Can somebody help me with this?
simije97 said:
Hello all. When I click on Internal storage, there are folders with names like "a16sgyx462" and so on, so I am not able to install TWRP permanently. Can somebody help me with this?
Click to expand...
Click to collapse
You probably have Data encrypted. You need to execute Format Data in TWRP.
Has anyone used the official TWRP version? I've been thinking of transitioning from the older, unofficial, TWRP to that, but I haven't found any comment about it at all.
Hi, I was on 11.0.11 and after flashing 11.0.12 from TWRP
miui_GINKGOGlobal_V11.0.12.0.PCOMIXM_912960e1fc_9.0.zip
I can't flash TWRP
twrp-3.4.0-1-ginkgo.img
in fastboot mode even though there isn't an error
Code:
fastboot flash recovery twrp-3.4.0-1-ginkgo.img
Sending 'recovery' (65536 KB) OKAY [ 1.564s]
Writing 'recovery' OKAY [ 0.277s]
Finished. Total time: 1.868s
if I try to boot into recovery TWRP isn't there, it's on stock recovery. My bootloader is unlocked if it isn't obvious.
If I do
fastboot reboot recovery
after flashing TWRP, it doesn't boot into TWRP but instead into normal phone mode, not recovery.
If I do
fastboot reboot recovery
after flashing TWRP and then keep pressing the recovery key combo (PWR+VOLUP) it doesn't boot any recovery, it just keeps rebooting
-
Hacker?pcs said:
Hi, I was on 11.0.11 and after flashing 11.0.12 from TWRP
miui_GINKGOGlobal_V11.0.12.0.PCOMIXM_912960e1fc_9.0.zip
I can't flash TWRP
twrp-3.4.0-1-ginkgo.img
in fastboot mode even though there isn't an error
Code:
fastboot flash recovery twrp-3.4.0-1-ginkgo.img
Sending 'recovery' (65536 KB) OKAY [ 1.564s]
Writing 'recovery' OKAY [ 0.277s]
Finished. Total time: 1.868s
if I try to boot into recovery TWRP isn't there, it's on stock recovery. My bootloader is unlocked if it isn't obvious.
If I do
fastboot reboot recovery
after flashing TWRP, it doesn't boot into TWRP but instead into normal phone mode, not recovery.
If I do
fastboot reboot recovery
after flashing TWRP and then keep pressing the recovery key combo (PWR+VOLUP) it doesn't boot any recovery, it just keeps rebooting
Click to expand...
Click to collapse
Download twrp fastboot mode.
Download TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150-fastboot.zip - Redmi Note 8
Download TWRP TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150-fastboot.zip - Redmi Note 8 - in MiFirm ✅ - Xiaomi MIUI Firmware - ROM - TWRP download free and max speed - The biggest Xiaomi Mi download
mifirm.net
J. Harry Potter said:
Download twrp fastboot mode.
Download TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150-fastboot.zip - Redmi Note 8
Download TWRP TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150-fastboot.zip - Redmi Note 8 - in MiFirm ✅ - Xiaomi MIUI Firmware - ROM - TWRP download free and max speed - The biggest Xiaomi Mi download
mifirm.net
Click to expand...
Click to collapse
Doesn't work,
fastboot boot recovery-TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150.img
bring me to a different screen, the one that says "Redmi by Xiaomi" instead of the one with the little thing with the communist hat tinkering with Android but it's fastboot again, no TWRP.
Flashing it to recovery is the same as the official, rebooting to normal phone mode and if I do adb reboot recovery it gets me to stock recovery, not TWRP
Hacker?pcs said:
Doesn't work,
fastboot boot recovery-TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150.img
bring me to a different screen, the one that says "Redmi by Xiaomi" instead of the one with the little thing with the communist hat tinkering with Android but it's fastboot again, no TWRP.
Flashing it to recovery is the same as the official, rebooting to normal phone mode and if I do adb reboot recovery it gets me to stock recovery, not TWRP
Click to expand...
Click to collapse
Then ig.......try after reseting your device or clean flash latest miui with mi flash tool.(your bootloader needs to be unlocked)
Hacker?pcs said:
Doesn't work,
fastboot boot recovery-TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150.img
bring me to a different screen, the one that says "Redmi by Xiaomi" instead of the one with the little thing with the communist hat tinkering with Android but it's fastboot again, no TWRP.
Flashing it to recovery is the same as the official, rebooting to normal phone mode and if I do adb reboot recovery it gets me to stock recovery, not TWRP
Click to expand...
Click to collapse
By the way this is a different method. this should have worked. what did you do ?
J. Harry Potter said:
Then ig.......try after reseting your device or clean flash latest miui with mi flash tool.(your bootloader needs to be unlocked)
Click to expand...
Click to collapse
My bootloader is unlocked, I'm with Magisk since I bought the device, I usually to update download the recovery rom
Miui Updates
Redmi Note 8 Global Stable V11.0.12.0 OTA Apply for V11.0.11.0 https://bigota.d.miui.com/V11.0.12.0.PCOMIXM/miui-blockota-ginkgo_global-V11.0.11.0.PCOMIXM-V11.0.12.0.PCOMIXM-a0ac2f3c57-9.0.zip Recovery ROM...
t.me
and flash it then flash Magisk then TWRP to recovery, sometimes I forget though TWRP and then flash it from fastboot. I forgot it now but now it doesn't flash via fastboot for some reason
J. Harry Potter said:
By the way this is a different method. this should have worked. what did you do ?
Click to expand...
Click to collapse
As I've said, it acts like the official TWRP, it either reboots to fastboot or to normal phone mode.
Hacker?pcs said:
My bootloader is unlocked, I'm with Magisk since I bough the device, I usually to update download the recovery rom
Miui Updates
Redmi Note 8 Global Stable V11.0.12.0 OTA Apply for V11.0.11.0 https://bigota.d.miui.com/V11.0.12.0.PCOMIXM/miui-blockota-ginkgo_global-V11.0.11.0.PCOMIXM-V11.0.12.0.PCOMIXM-a0ac2f3c57-9.0.zip Recovery ROM...
t.me
and flash it then flash Magisk then TWRP to recovery, sometimes I forget though TWRP and then flash it from fastboot. I forgot it now but now it doesn't flash via fastboot for some reason
As I've said, it acts like the official TWRP, it either reboots to fastboot or to normal phone mode.
Click to expand...
Click to collapse
i don't know how you flashed that twrp. Just open EN_Recovery-twrp-oneclick-EN then press enter. and then boot your phone to fastboot mode and connect to pc. then in pc type 2 and then i hope it will work
J. Harry Potter said:
i don't know how you flashed that twrp. Just open EN_Recovery-twrp-oneclick-EN then press enter. and then boot your phone to fastboot mode and connect to pc. then in pc type 2 and then i hope it will work
Click to expand...
Click to collapse
I've flashed it with the fastboot I have from Android SDK, didn't run the script. I've checked it out and saw that it flashes the misc.bin file too, I've tried flashing it but now I'm stuck on fastboot... ffs
I've downloaded the official Fastboot rom
ginkgo_global_images_V11.0.12.0.PCOMIXM_20201119.0000.00_9.0_global_37804edbcb.tgz
but I can't flash its misc.bin, it says Volume full...
fastboot continue
says "system has been destroyed"
I really don't want to wipe data and start fresh with Mi Flash tool ffs
Hacker?pcs said:
I've flashed it with the fastboot I have from Android SDK, didn't run the script. I've checked it out and saw that it flashes the misc.bin file too, I've tried flashing it but now I'm stuck on fastboot... ffs
I've downloaded the official Fastboot rom
ginkgo_global_images_V11.0.12.0.PCOMIXM_20201119.0000.00_9.0_global_37804edbcb.tgz
but I can't flash its misc.bin, it says Volume full...
never heard of volume full problem. place the fastboot rom in desktop menu. and install necessary drivers that need to flash via mi flash tool
Click to expand...
Click to collapse
J. Harry Potter said:
never heard of volume full problem. place the fastboot rom in desktop menu. and install necessary drivers that need to flash via mi flash tool
Click to expand...
Click to collapse
Well the misc.bin from your link is 8KB, the misc.img from fastboot rom tgz is 8MB
It sucks because mi flash tool erases data...
EDIT
THANK GOD,
fastboot erase misc
fixes the destroyed problem and lets me boot.
I figured it out from the bat script in the tgz fastboot rom, it doesn't flash the contained 4MB misc.img, it just has "fastboot %* erase misc" near the end
Problem that I can't flash TWRP again so I can't root :/
Hacker?pcs said:
Well the misc.bin from your link is 8KB, the misc.img from fastboot rom tgz is 8MB
It sucks because mi flash tool erases data...
EDIT
THANK GOD,
fastboot erase misc
fixes the destroyed problem and lets me boot.
I figured it out from the bat script in the tgz fastboot rom, it doesn't flash it, it just has "fastboot %* erase misc" near the end
Problem that I can't flash TWRP again so I can't root :/
Click to expand...
Click to collapse
so now you can boot.
if you have a pc just store your data in pc and then flash miui. then ig it will clear all the bugs u r facing and then you can try to flash twrp
J. Harry Potter said:
so now you can boot.
if you have a pc just store your data in pc and then flash miui. then ig it will clear all the bugs u r facing and then you can try to flash twrp
Click to expand...
Click to collapse
Yeah seems to the only way, something blocks the custom TWRP recovery and a clean slate may be the only way
Hacker?pcs said:
Yeah seems to the only way, something blocks the custom TWRP recovery and a clean slate may be the only way
Click to expand...
Click to collapse
don't forget to flash VBMETA after so the custom recovery (twrp or orangefox) persist
I tried installing a custom ROM on my p20 lite, but ended up bricking my phone instead at some point, and now I can't figure out how to restore it to stock EMUI 9.1.
When I boot my phone, it always goes to the TWRP recovery but gets stuck on the TWRP logo. It still accepts adb commands though. Fastboot works too.
The bootloader is unlocked, and there's no FRP lock.
I've tried flashing the images extracted from Huawei P20 Lite ANE-LX1 ANE-L01 hw eu HLRCF Anne-L01 9.1.0.274(C782E5R1P7T8) Firmware EMUI9.1.0 05015ARN [androidhost.ru].zip UPDATE.APP as shown in this video but my phone is still stuck on the TWRP logo.
I think erecovery has been overwritten because I can't get to it and I get the error seen below in the images (no system error) when I try the power button + vol up + vol down and just vol up + vol down.
Code:
C:\platform tools adb>fastboot devices
9WV4C18706040848 fastboot
C:\platform tools adb>fastboot oem get-build-number
(bootloader) :ANE-LGRP2-OVS 9.1.0.274
OKAY [ 0.000s]
Finished. Total time: 0.016s
Is my phone ****ed or is there still hope?
XRealXX said:
I tried installing a custom ROM on my p20 lite, but ended up bricking my phone instead at some point, and now I can't figure out how to restore it to stock EMUI 9.1.
When I boot my phone, it always goes to the TWRP recovery but gets stuck on the TWRP logo. It still accepts adb commands though. Fastboot works too.
The bootloader is unlocked, and there's no FRP lock.
I've tried flashing the images extracted from Huawei P20 Lite ANE-LX1 ANE-L01 hw eu HLRCF Anne-L01 9.1.0.274(C782E5R1P7T8) Firmware EMUI9.1.0 05015ARN [androidhost.ru].zip UPDATE.APP as shown in this video but my phone is still stuck on the TWRP logo.
I think erecovery has been overwritten because I can't get to it and I get the error seen below in the images (no system error) when I try the power button + vol up + vol down and just vol up + vol down.
Code:
C:\platform tools adb>fastboot devices
9WV4C18706040848 fastboot
C:\platform tools adb>fastboot oem get-build-number
(bootloader) :ANE-LGRP2-OVS 9.1.0.274
OKAY [ 0.000s]
Finished. Total time: 0.016s
Is my phone ****ed or is there still hope?
Click to expand...
Click to collapse
I don't understand why you installed C782 firmware when you have C432??
XRealXX said:
UPDATE.APP
Click to expand...
Click to collapse
New know-how?
XRealXX said:
I think erecovery has been overwritten
Click to expand...
Click to collapse
I think both Recovery has been overwritten...
First flash stock recovery_ramdisk, then try to flash service ROM via dload, for region C432, of course. And please FOLLOW INSTRUCTIONS on how to install correctly full Stock (can be found in ReleaseDoc folder).
Or, flash TWRP again, enter TWRP and flash eRecovery image (for sure). Reboot into eRecovery and use option "Download latest etc." .
Files:
Stock Recovery:
https://mega.nz/file/M0FHlYhb#4yWz8Onr3D1NATel4mZSK4SNdd5B3p6dnPg6oXPGWl8
Stock eRecovery:
https://mega.nz/file/58tnXIKB#KiNi1LXdvZ6hFQAKknULA6fTaOW4-3dstDDdngzBdco
Service ROM for hw-eu
I don't understand why you installed C782 firmware when you have C432??
Click to expand...
Click to collapse
I don't get these version number names... fastboot oem get-build-number command says that the version number is: ANE-LGRP2-OVS 9.1.0.274. How is it C432 then? I don't understand it.
The zip file I downloaded has .274 in it "Huawei P20 Lite ANE-LX1 ANE-L01 hw eu HLRCF Anne-L01 9.1.0.274(C782E5R1P7T8) Firmware EMUI9.1.0 05015ARN [androidhost.ru].zip". So shouldn't it be the version I need? How do I know that this is actually C782? Sorry, I'm not very experienced with this stuff.
New know-how?
Click to expand...
Click to collapse
What I meant by this is that I extracted the UPDATE.APP file from update_sd.zip. I opened the UPDATE.APP file via the Huawei Update Extractor program and extracted the files shown in this video and flashed those files as shown in the video too: From the UPDATE.APP I extracted: RECOVERY_RAMDIS.img, RECOVERY_RAMDIS.img.header, SYSTEM.img, SYSTEM.img.header.
I then flashed RECOVERY_RAMDIS.img via fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
SYSTEM.img with fastboot flash system SYSTEM.img
Everything went fine, but when I tried to enter the erecovery, it still only went to twrp. When I tried to go to the forcible upgarde mode (power button + vol up + vol down), I got this error message:
Spoiler: Image
I think both Recovery has been overwritten...
First flash stock recovery_ramdisk, then try to flash service ROM via dload, for region C432, of course. And please FOLLOW INSTRUCTIONS on how to install correctly full Stock (can be found in ReleaseDoc folder).
Or, flash TWRP again, enter TWRP and flash eRecovery image (for sure). Reboot into eRecovery and use option "Download latest etc." .
Files:
Stock Recovery:
https://mega.nz/file/M0FHlYhb#4yWz8Onr3D1NATel4mZSK4SNdd5B3p6dnPg6oXPGWl8
Stock eRecovery:
https://mega.nz/file/58tnXIKB#KiNi1LXdvZ6hFQAKknULA6fTaOW4-3dstDDdngzBdco
Service ROM for hw-eu
Click to expand...
Click to collapse
Okay, so I tried flashing stock recovery_ramdisk that you linked in your comment this way:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-9.1.img
I copied the dload folder to the root of the SD Card, as instructed in the ReleaseDoc folder.
Held down power button + vol up + vol down, I still got this error screen:
Spoiler: That error screen I showed previously in this comment
I tried flashing the ERECOVERY_RAMDISK-ANE-9.1.img instead:
Code:
fastboot flash recovery_ramdisk ERECOVERY_RAMDISK-ANE-9.1.img
but that didn't help either, and I still got that error screen shown above.
I tried flashing a different TWRP recovery
Code:
fastboot flash recovery_ramdisk twrp.img
before I posted this thread on the forum but my phone still only booted to the twrp that was on it before that gets stuck on the TWRP logo (holding down power button + vol up or just vol up yields the same result).
Spoiler: The stuck TWRP
So, what now? Thank you for your patience.
XRealXX said:
How is it C432 then?
Click to expand...
Click to collapse
It's your info:
"My Huawei P20 lite (ANE-LX1, hw/eu)"
hw/eu = C432 region.
C782 is an unlocked UK version, not a hw/eu. Keep in mind, the only trusted source for downloading service ROMs is the website in my link above.
XRealXX said:
I tried flashing the ERECOVERY_RAMDISK-ANE-9.1.img instead:
Code:
fastboot flash recovery_ramdisk ERECOVERY_RAMDISK-ANE-9.1.img
but that didn't help either, and I still got that error screen shown above.
Click to expand...
Click to collapse
Read carefully:
-Alf- said:
enter TWRP and flash eRecovery image (for sure). Reboot into eRecovery and use option "Download latest etc." .
Click to expand...
Click to collapse
As for TWRP, try to install 3.2.1 pretoriano80 or 3.4.0-0-emui9_eR
https://forum.xda-developers.com/t/recommended-and-tested-twrp-recovery.4199099/post-84056933
Do factory reset via fastboot:
fastboot erase userdata
As for TWRP, try to install 3.2.1 pretoriano80 or 3.4.0-0-emui9_eR
https://forum.xda-developers.com/t/recommended-and-tested-twrp-recovery.4199099/post-84056933
Click to expand...
Click to collapse
I tried flashing the two TWRP recoveries you mentioned (3.2.1 pretoriano80 and 3.4.0-0-emui9_eR) via fastboot flash recovery_ramdisk twrp_image_name_here.img but my phone still keeps booting into GAGUGA Edition TWRP.
-Alf- said:
Do factory reset via fastboot:
fastboot erase userdata
Click to expand...
Click to collapse
Okay. I'll try that.
-Alf- said:
Do factory reset via fastboot:
fastboot erase userdata
Click to expand...
Click to collapse
So I tried that and it failed:
Code:
C:\platform tools adb>fastboot erase userdata
< waiting for any device >
Erasing 'userdata' FAILED (Status read failed (Too many links))
fastboot: error: Command failed
C:\platform tools adb>fastboot erase userdata
(bootloader) success to erase cryypt info in oeminfo
Erasing 'userdata' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
C:\platform tools adb>fastboot devices
9WV4C18706040848 fastboot
But now the GAGUGA Edition TWRP works! Thank you!
Now that the GAGUGA TWRP recovery works, what should I do? I don't wanna mess it up again.
XRealXX said:
Now that the GAGUGA TWRP recovery works, what should I do? I don't wanna mess it up again.
Click to expand...
Click to collapse
-Alf- said:
enter TWRP and flash eRecovery image (for sure). Reboot into eRecovery and use option "Download latest etc."
Click to expand...
Click to collapse
Btw, the firmware you have downloaded and flashed, is for Single SIM devices.
-Alf- said:
Btw, the firmware you have downloaded and flashed, is for Single SIM devices.
Click to expand...
Click to collapse
Oh... My phone is dual sim.
-Alf- said:
Btw, the firmware you have downloaded and flashed, is for Single SIM devices.
Click to expand...
Click to collapse
Okay, I'll try flashing the erecovery file. Ty
Thanks to you -Alf-, my phone is no longer e-waste! After flashing the eRecovery image in TWRP to eRecovery and rebooting my phone, it automatically started to install the software in my dload folder on my sd card. And it worked. Thank you again!
To recap everything for people in the future who might need this and find it via google or some other search engine, the fix was to run this command in fastboot (it does a factory reset):
Code:
fastboot erase userdata
Then the phone will automatically install the firmware that's in the dload folder in the root of your sd card (the firmware I used is the Service ROM -Alf- linked Alternatively, you can try installing the latest firmware via WiFi in eRecovery.
Luckily those devices seem to be fairly indestructible, as long as the Bootloader is open and FRP is disabled.