Related
Hello! Some day i want to downgrade my Marshmallow to Lollipop. I installed stock ROM to my Honor 5X but in older android - Lollipop 5.1. And I get bricked it. On start on screen i can see first-step logo honor after it i can see second-step honor's logo and here i wait 30 minutes and nothing 45 minutes and nothing. Worse is this I can't back to my stock Marshmallow, when I'm installing my previous ROM - MM i get the same brick on second-step logo. I installed a few more ROMs and nothing. My bootloader is unlocked but when i try to flash cust/system by fastboot appear an error. FAILED (remote: Command not allowed). I think i tried everything, thank for help me.
PS. Sorry for bad English :/
EDIT.1 I tried to use this method from Thread: http://forum.xda-developers.com/honor-5x/help/ive-bricked-honor-5x-t3324225. But the same problem at fastboot.
cust and system won't get flashed on 5X, try force updating it with an UPDATE.APP package for your device.
Put it inside dload folder in root of the Sdcard, and press all three buttons (Vol UP + Vol DOWN + Power) after switching off your phone, to start updating.
Sent from my PLK-L01 using Tapatalk
Thank you. But i tried to get ROM back by UPDATE.APP and when i want to go back to Marshmallow i get second-step honor logo and nothing after it. When i want to get Lollipop i have error "Software can't be installed" - something like that. I heard something about "Transition package" or "Downgrade Package" ? Maybe it can be work. But i can't find those packages for honor 5x KIW-L21.
Bayont said:
Thank you. But i tried to get ROM back by UPDATE.APP and when i want to go back to Marshmallow i get second-step honor logo and nothing after it. When i want to get Lollipop i have error "Software can't be installed" - something like that. I heard something about "Transition package" or "Downgrade Package" ? Maybe it can be work. But i can't find those packages for honor 5x KIW-L21.
Click to expand...
Click to collapse
If the Marshmallow update went through a bit, then you'll need transition package, so take on some pain to find it. It should be out there somewhere.
Sent from my PLK-L01 using Tapatalk
That's maybe becouse i don't remove ROOT and Xposed before installing ROM, how to unroot by TWRP?
Bayont said:
That's maybe becouse i don't remove ROOT and Xposed before installing ROM, how to unroot by TWRP?
Click to expand...
Click to collapse
If you use the this version of TWRP > https://www.androidfilehost.com/?fid=24588212152305793
you can flash system.img and cust.img extracted from your Update.APP with HuaweiUpdateExtractor
fastboot boot twrp.img
then copy the files to the phone
then choose Install / Install Image / system.img or cust.img or recovery.img boot.img ..you choose
Also just saying your have a L21 does not help
is it KIW-L21 C432 or KIW-L21 C185
Now i backed to B130 and i have loop with message Optimizing system... this process going to 100% and phone reboot. And it looping.
Bayont said:
Now i backed to B130 and i have loop with message Optimizing system... this process going to 100% and phone reboot. And it looping.
Click to expand...
Click to collapse
your post tells us nothing about what you did, are we suppose to guess ?
if you successfully flashed System.img - boot .img - cust.img and recovery.img you can now use the dload / Update.app
clsA said:
if you successfully flashed System.img - boot .img - cust.img and recovery.img you can now use the dload / Update.app
Click to expand...
Click to collapse
Done but without any effect, the same problem, stuck at second-step honor logo ;/
Any ideas?
Bayont said:
Any ideas?
Click to expand...
Click to collapse
Well considering I still don't know what you have done. Its hard to guess the next step
Sent from my SM-N920T using Tapatalk
Ok, one more time. When i'm installing any ROM B130 or B330, stock or official doesn't matter, the same problem. After installing rom by UPDATE.APP my phone booting and booting and booting and nothing. When i'm installing rom images by TWRP - boot, cust, system It's the same problem Booting, booting and nothing. When i tried to flash rom by fastboot i have error: FAILED (remote: Command not allowed). I would like to try this: http://forum.xda-developers.com/honor-5x/help/how-restore-cust-partition-t3356769 But i don't know how to access to adb shell: when i type "adb shell" in cmd where i have adb it say to me: error: device '(null)' not found. I don't know what to do more.
How much time honor 5x system is installing?
How i can check my honor is KIW-L21 C432 or KIW-L21 C185?
Bayont said:
How i can check my honor is KIW-L21 C432 or KIW-L21 C185?
Click to expand...
Click to collapse
If you tried to install the wrong Update.app the updater would get to 5% and stop and eventually just reboot. Did you actually watch the update go to 100% and reboot ?
I think i found source of my problem. When i want to downgrade my system was B340.
I read something about downgrade. Without Transition Package I can't downgrade my system I can install only the same (B340) or higher.
This making brick when i'm installing B330 or B140.
Now i'm trying to install OTA B340 and i have another problem,
when i have B330 and installing B340 by small OTA 124MB I have stuck on 5% of installing. It becouse:
EDIT 2 : If you come from B330, don't try to flash the small B340 update as local update has simply been disabled by theHuawei/Honor devs !
Worse, with B340 you won't be able to downgrade to any lower version : at least not easily... INFO FROM: HERE
Click to expand...
Click to collapse
But when i'm installing B130 by TWRP and upgrading to B340 by big upgrade (1,36GB) it's stucking on 0% and i get info: DO NOT UNPLUG....
I think that becouse my version isn't B130 only B140. I'm checking it by DC-UNLOCKER. Output from it:
Code:
Found Phone : KIW-L21
Model : Huawei phone in fastboot mode
Serial NR. : My Serial
Firmware : KIW-L21C432B140
FB LockState: LOCKED
widevine LockState: UNLOCKED
Bootloader Lock State: UNLOCKED
Root State: ROOT
Bootloader WidevineKey: WidevineKey_VALID
System State: Bootloader in UNLOCKED state
Bootloader Version: 001.001.000
Battery state: battery is present
Maybe I should Restore backup from diffrent KIW-L21 by TWRP?
Bayont said:
I think i found source of my problem. When i want to downgrade my system was B340.
I read something about downgrade. Without Transition Package I can't downgrade my system I can install only the same (B340) or higher.
This making brick when i'm installing B330 or B140.
Now i'm trying to install OTA B340 and i have another problem,
when i have B330 and installing B340 by small OTA 124MB I have stuck on 5% of installing. It becouse:
But when i'm installing B130 by TWRP and upgrading to B340 by big upgrade (1,36GB) it's stucking on 0% and i get info: DO NOT UNPLUG....
I think that becouse my version isn't B130 only B140. I'm checking it by DC-UNLOCKER. Output from it:
Code:
Found Phone : KIW-L21
Model : Huawei phone in fastboot mode
Serial NR. : My Serial
Firmware : KIW-L21C432B140
FB LockState: LOCKED
widevine LockState: UNLOCKED
Bootloader Lock State: UNLOCKED
Root State: ROOT
Bootloader WidevineKey: WidevineKey_VALID
System State: Bootloader in UNLOCKED state
Bootloader Version: 001.001.000
Battery state: battery is present
Maybe I should Restore backup from diffrent KIW-L21 by TWRP?
Click to expand...
Click to collapse
Normally restoring a TWRP backup is no different than flashing System.img and boot.img
your bootloop is firmware related ... you need the full B340 package
Yes, you written in Honor 5x Repo:
Waiting for full B340 to appear on Honor support site.
Click to expand...
Click to collapse
At the moment there isn't any full B340 ROM for download. And any OTA B340 doesn't work for me, yes? For example:
B140 -> B340
http://update.hicloud.com:8180/TDS/d...ull/update.zip
changelog
http://update.hicloud.com:8180/TDS/d.../changelog.xml
Click to expand...
Click to collapse
Bayont said:
Yes, you written in Honor 5x Repo:
At the moment there isn't any full B340 ROM for download. And any OTA B340 doesn't work for me, yes? For example:
Click to expand...
Click to collapse
Then you just have to wait
I don't publish the updates I just post them
Sent from my SM-N920T using Tapatalk
I can't back to Stock Lolipop by editing some files or install B340 from B140 by OTA
Hi
I don't know where to publish this thread cause there is no Zenfone 3 Zoom Section
So I will write it here till the moderators make the section
This thread is method for changing the stock ROM from Chinese version to worldwide version
NOTE : You can't flash ww ROM from TWRP even if you change the Updater script , also it can't be flashed from ASUS flashtool. [ I attached photos for it ]
Required things :
1- Unlocked Bootloader | you can Download the unlock app from herehttps://ln.sync.com/dl/be16e9f30/h5hsy3iq-ruag2n8n-v293cg8a-wi29bypk
2- adb & fastboot drivers | download it from here
3- WW ROM | from here
** You have to make a backup for your data cause your device will be wiped .
Steps :
1- Unlock the bootloader .
2- Install the adb & fastboot drivers on your PC
3- extract the ROM file [ will have a lot of files , you only need System.img and boot.img]
4- copy System.img and boot.img to adb&fastboot folder
5- open command Prompt
6- put your devices in fastboot mode [ restart your device then press the Vol.Up button and choose fastboot]
7- enter these commands in cmd :
fastboot flash boot boot.img
fastboot flash system system.img
fastboot format userdata
fastboot reboot
8- enjoy your new ww rom
** if you want to flash twrp then >>
1- install it from here
2- enter fastboot mode
3- in cmd , write this command
fastboot flash recovery twrp.img
DONE
photos attached for
battery Status after installing WW ROM
difference between the WB in WW ROM and CN ROM
The errors shown when flashing WW ROM from TWRP or asus flashtool
Nice guide
awesome
I know this isn't the thread for it... but there is no forum for the ZenFone 3 Zoom.
I have US model and I've unlocked the bootloader, installed TWRP, rooted.
I want to install rom update that was just released last week. It obviously doesn't flash in TWRP. I also can't unzip it without corruption errors. Redownloaded the ROM multiple times from ASUS.
I assume to update stock rom with an unlocked Bootloader we'll need stock recovery??
DriveEuro said:
I have US model and I've unlocked the bootloader, installed TWRP, rooted.
I want to install rom update that was just released last week.
Click to expand...
Click to collapse
How did you do the rooting? No issues so far? Is there a guide somewhere you followed?
calus said:
How did you do the rooting? No issues so far? Is there a guide somewhere you followed?
Click to expand...
Click to collapse
Use the bootloader unlock.
Install TWRP.
Install SuperSU zip file.
DriveEuro said:
Use the bootloader unlock.
Install TWRP.
Install SuperSU zip file.
Click to expand...
Click to collapse
And where was that twrp install originally from? I haven't found an image for this model specifically.
Also, does this bootloader unlock still allow the pushed OS updates from ASUS? Want to make sure I can get Nougat when it comes out!
Hey guys,
I need some help. I installed the apk to unlock the bootloader and my phone was fine, but after flashing twrp and installing the zip for supersu via twrp, my phone has been stuck on the boot screen. Now it says "The dm verity is not started in enforcing mode and may not work properly" when booting up. I can get back into twrp, and I've tried wiping the dalvik/art cache, system, data, and cache, but my phone still won't boot up. It's stuck on the ASUS boot screen, and I have no idea what to do now. Any help would be greatly appreciated!
magicmanfk said:
And where was that twrp install originally from? I haven't found an image for this model specifically.
Click to expand...
Click to collapse
https://www.asus.com/zentalk/tw/thread-222337-1-1.html
Use google translate.
---------- Post added at 05:34 AM ---------- Previous post was at 05:33 AM ----------
magicmanfk said:
Also, does this bootloader unlock still allow the pushed OS updates from ASUS? Want to make sure I can get Nougat when it comes out!
Click to expand...
Click to collapse
No. The last update WW_V11.41.87.2 is not available for my OTA. I can download the zip though and flash. I haven't actually attempted to do this yet. I plan to flash it today. Not sure if I'll be able to do it through twrp, or if I'll have to flash back the stock recovery first.
So does this change the bands available with it? I have the WW ROM but want the additional bands the US ROM has.
why I only have system.new.dat where can i get the system.img? thank you
How did you get on with flashing the update... did you have to revert to stock recovery and if so which did you use? Thanks for your help with this.
Can I ask where/how you got the stock ROM? I'd like to make sure that these are updated/available somewhere for people on this device to use as needed, and ASUS seems to only have the updates on their website.
Is it possible to relock bootloader after converting to WW?
I'm interested in this phone. Do you know if this one is going to be shipped later this year with Snapdragon 630?. I hear something similar in a YouTube video.
JERRYZKT said:
Is it possible to relock bootloader after converting to WW?
Click to expand...
Click to collapse
Once the bootloader is unlocked it can't be relocked.
I cant find the images in the folder - are they named differently?
Already I convert CN to WW successfully. Thanks for your post . But , I want to update Nougat WW rom. Please help me boss..... I am student and ZenFone 3 Zoom is my favorite phone. Please do something for me .......
???
How can I update Nougat on ZenFone 3 Zoom.....??? Please help me .......
Hi,
sorry if i'm the 100th person to ask this question but how can i go back to the stock ROM with OTA?
I currently have a flavor of LinageOS with the Turbo Z kernel installed on my phone but it's just to buggy for me. I want to have root access on my phone for various reasons though.
I tried to just download different (6.0/7.0) stock ROM files but i can't install them with TWRP. I know that 7.1.x was released but i can not find the ROM for it.
What is the easiest way to just go back to a stock ROM? I know my way around the console but i don't want to brick my phone. I made backups of my files and also with TWRP so data loss is not an issue.
https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
First things first.
On which bootloader are you, MM or are you on Nougat. If your device has been flashed with the 7(N) bootloader, you cannot flash the 6.0 stock, you will have to stay of 7.
Use the fastboot flash / erase commands, as in this thread:
https://forum.xda-developers.com/showpost.php?p=73119650&postcount=1
If at any stage your phone get bricked, ie, black screen after reboot, no charging, etc. Use these instructions. They saved me in the last week from returning my device for a replacement(and paying $350.00):
https://forum.xda-developers.com/showpost.php?p=71874880&postcount=1
lollyjay said:
https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
Click to expand...
Click to collapse
Does this work for the EU version too? I'm not sure if the baseband thingy is compatible. I'll need a EU ROM otherwise but i can't find any for Android 7 :/
bert269 said:
On which bootloader are you, MM or are you on Nougat. If your device has been flashed with the 7(N) bootloader, you cannot flash the 6.0 stock, you will have to stay of 7.
Click to expand...
Click to collapse
I've already updated to Android 7 so i guess i've to use a stock Nougat ROM.
Read my last post on page 15 of this thread
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-root-moto-z-supersu-t3551113/page15
Where can I find the stock recovery for XT1650-03 RETEU without downloading an entire ROM zip file?
I have stock 7.0.0 with TWRP and Magisk 13.3.
I want to install the stock recovery so that I can install the 7.1.1 OTA which is available on my device, after which I will flash TWRP and root again. Will this work?
Byte_76 said:
Where can I find the stock recovery for XT1650-03 RETEU without downloading an entire ROM zip file?
I have stock 7.0.0 with TWRP and Magisk 13.3.
I want to install the stock recovery so that I can install the 7.1.1 OTA which is available on my device, after which I will flash TWRP and root again. Will this work?
Click to expand...
Click to collapse
If you didn't take a backup of your stock boot and recovery before, then i think you'll have to go the long way by flashing the whole rom.
If you manage to install the 7.1.1 OTA after that, boot once into TWRP, backup stock recovery & boot and save it on your sdcard/pc. Then you can start flashing TWRP permantly, root, etc
Someone correct me, if I'm wrong.
Byte_76 said:
Where can I find the stock recovery for XT1650-03 RETEU without downloading an entire ROM zip file?
I have stock 7.0.0 with TWRP and Magisk 13.3.
I want to install the stock recovery so that I can install the 7.1.1 OTA which is available on my device, after which I will flash TWRP and root again. Will this work?
Click to expand...
Click to collapse
What is your build number?
lollyjay said:
What is your build number?
Click to expand...
Click to collapse
The current build number is NPLS25.86-30-12
Byte_76 said:
The current build number is NPLS25.86-30-12
Click to expand...
Click to collapse
Here is my recovery.img for NPLS25.86-30-12
https://drive.google.com/file/d/0B3gcDbDvV4MkOHhPd0lBVE9IMzg/view?usp=drivesdk
It should work for reteu also if not you can just reflash twrp:cyclops:
lollyjay said:
Here is my recovery.img for NPLS25.86-30-12
https://drive.google.com/file/d/0B3gcDbDvV4MkOHhPd0lBVE9IMzg/view?usp=drivesdk
It should work for reteu also if not you can just reflash twrp:cyclops:
Click to expand...
Click to collapse
Thank you!
---------- Post added at 12:31 AM ---------- Previous post was at 12:15 AM ----------
lollyjay said:
Here is my recovery.img for NPLS25.86-30-12
https://drive.google.com/file/d/0B3gcDbDvV4MkOHhPd0lBVE9IMzg/view?usp=drivesdk
It should work for reteu also if not you can just reflash twrp:cyclops:
Click to expand...
Click to collapse
Your recovery works on my Moto Z.
I now have stock 7.0.0 rooted with Magisk 13.3, stock recovery and unlocked bootloader.
If I proceed with the 7.1.1 OTA, will it work?
Byte_76 said:
Thank you!
---------- Post added at 12:31 AM ---------- Previous post was at 12:15 AM ----------
Your recovery works on my Moto Z.
I now have stock 7.0.0 rooted with Magisk 13.3, stock recovery and unlocked bootloader.
If I proceed with the 7.1.1 OTA, will it work?
Click to expand...
Click to collapse
You must have fully stock. I would suggest that you uninstall Magisk
lollyjay said:
You must have fully stock. I would suggest that you uninstall Magisk
Click to expand...
Click to collapse
The reason that I installed Magisk is because after unlocking the bootloader with the stock rom, it would not boot anymore. Installing a custom kernel or Magisk solves that issue.
Byte_76 said:
The reason that I installed Magisk is because after unlocking the bootloader with the stock rom, it would not boot anymore. Installing a custom kernel or Magisk solves that issue.
Click to expand...
Click to collapse
I still would suggest that you uninstall Magisk because the OTA would not work.
lollyjay said:
I still would suggest that you uninstall Magisk because the OTA would not work.
Click to expand...
Click to collapse
Okay I uninstalled Magisk which initiated an immediate reboot and resulted in a bootloop just after the bootloader message.
I think the issue occurs because the Data partition gets encrypted when root is uninstalled and decrpyption fails because of a bad key due to the unlocked bootloader.
To recover, I used TWRP to wipe/format the Data partition and then flashed the no_verity zip file from the thread below which disables encryption. I then ran "fastboot continue" after which my phone booted back into Android:
https://forum.xda-developers.com/moto-z/help/bricked-moto-z-unlocking-bootlader-t3634701
My phone status was then: Stock Android 7.0.0, no_verity patch (no encryption), stock recovery, unlocked bootloader.
So my phone is about as close to stock as I can get it with unlocked bootloader.
I finally attempted to install the 7.1.1 OTA again. It reboots and indicates that it is installing and then pops up with a message that says "Error".
Pressing the power and up button brings up the recovery screen with the error log (with info that I don't understand) and from there I can reboot into system again where I get another message indicating that the update failed and no changes were made.
I'm hesitant to install RETBR or other non-RETEU roms (Because although they might work, there probably are some differences such as LTE bands etc. and they are not actually correct for my phone) so I'm not sure how else to get to 7.1.1 unless the wifi issue is resolved with the image that Erfanoabdi uploaded in another thread or Lenovo releases an official 7.1.1 firmware package for the RETEU model.
Byte_76 said:
.....
To recover, I used TWRP to wipe/format the Data partition and then flashed the no_verity zip file from the thread below which disables encryption.........
Click to expand...
Click to collapse
You still have a modified ROM as you flashed "no_verity patch"
The best for you would be to search for your version of ROM and FASTBOOT FLASH everything back.
Then see if the 7.1.1 OTA wants to stick.
bert269 said:
You still have a modified ROM as you flashed "no_verity patch"
The best for you would be to search for your version of ROM and FASTBOOT FLASH everything back.
Then see if the 7.1.1 OTA wants to stick.
Click to expand...
Click to collapse
So far I have been unable to find the official RETEU firmware from Adnroid 7.0.0 and I'm hesitant to flash the firmware for another region because it isn't technically correct for my phone and there are likely small differences that might become an issue at a later stage. (Maybe the LTE bands are different etc...)
Byte_76 said:
So far I have been unable to find the official RETEU firmware from Adnroid 7.0.0 and I'm hesitant to flash the firmware for another region because it isn't technically correct for my phone and there are likely small differences that might become an issue at a later stage. (Maybe the LTE bands are different etc...)
Click to expand...
Click to collapse
The LTE band on RETEU is 20 and stays 20 with RETBR. No change and everything works. No issues with LTE.
As I mentioned before, the RETBR version is the only working 7.0 backup for RETEU devices. After flashing RETBR , the softwarechannel changed automatically into RETEU. With this, i took the OTA 7.1.1.
Btw. the 7.1.1 OTA doesn't even change the boot loader Nr.( 0x9107). That means, if you mess up with 7.1.1 you can safely downgrade to 7.0 by flashing RETBR (and take a fresh 7.1.1 OTA again)
Did that twice without issues.(for security reason i always skip the two lines with "bootloader" and "gpt" at the top of the flash commands)
bullfinch110 said:
The LTE band on RETEU is 20 and stays 20 with RETBR. No change and everything works. No issues with LTE.
As I mentioned before, the RETBR version is the only working 7.0 backup for RETEU devices. After flashing RETBR , the softwarechannel changed automatically into RETEU. With this, i took the OTA 7.1.1.
Btw. the 7.1.1 OTA doesn't even change the boot loader Nr.( 0x9107). That means, if you mess up with 7.1.1 you can safely downgrade to 7.0 by flashing RETBR (and take a fresh 7.1.1 OTA again)
Did that twice without issues.(for security reason i always skip the two lines with "bootloader" and "gpt" at the top of the flash commands)
Click to expand...
Click to collapse
Thank you for the clarification. I will take your advice and flash the RETBR firmware.
---------- Post added at 08:40 PM ---------- Previous post was at 08:01 PM ----------
bullfinch110 said:
The LTE band on RETEU is 20 and stays 20 with RETBR. No change and everything works. No issues with LTE.
As I mentioned before, the RETBR version is the only working 7.0 backup for RETEU devices. After flashing RETBR , the softwarechannel changed automatically into RETEU. With this, i took the OTA 7.1.1.
Btw. the 7.1.1 OTA doesn't even change the boot loader Nr.( 0x9107). That means, if you mess up with 7.1.1 you can safely downgrade to 7.0 by flashing RETBR (and take a fresh 7.1.1 OTA again)
Did that twice without issues.(for security reason i always skip the two lines with "bootloader" and "gpt" at the top of the flash commands)
Click to expand...
Click to collapse
I cannot get RSDLite to detect my phone in fastboot mode so I guess I'm going to have to run the fastboot commands manually.
What do you mean about skipping the bootloader and gpt commands? If I skip those, I keep my stock "unlocked bootloader" and "gpt" but then the phone probably won't boot again because that is very much like what I have now except that I flashed the no_verity patch when my phone would not boot.
What exactly are you avoiding by skipping those two lines? Should I skip them too?
---------- Post added at 08:46 PM ---------- Previous post was at 08:40 PM ----------
Byte_76 said:
Thank you for the clarification. I will take your advice and flash the RETBR firmware.
---------- Post added at 08:40 PM ---------- Previous post was at 08:01 PM ----------
I cannot get RSDLite to detect my phone in fastboot mode so I guess I'm going to have to run the fastboot commands manually.
What do you mean about skipping the bootloader and gpt commands? If I skip those, I keep my stock "unlocked bootloader" and "gpt" but then the phone probably won't boot again because that is very much like what I have now except that I flashed the no_verity patch when my phone would not boot.
What exactly are you avoiding by skipping those two lines? Should I skip them too?
Click to expand...
Click to collapse
Are these the commands that I should run?
fastboot flash partition gpt.bin
fastboot flash motoboot boot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Byte_76 said:
Thank you for the clarification. I will take your advice and flash the RETBR firmware.
---------- Post added at 08:40 PM ---------- Previous post was at 08:01 PM ----------
I cannot get RSDLite to detect my phone in fastboot mode so I guess I'm going to have to run the fastboot commands manually.
What do you mean about skipping the bootloader and gpt commands? If I skip those, I keep my stock "unlocked bootloader" and "gpt" but then the phone probably won't boot again because that is very much like what I have now except that I flashed the no_verity patch when my phone would not boot.
What exactly are you avoiding by skipping those two lines? Should I skip them too?
Click to expand...
Click to collapse
It's out of my knowledge if your verity patch influences either bootloader or gpt partition. So i would recommend to flash those two commands in order to "repair" them. If you'll get an error message, skip them and proceed with the rest.
I always prefer RSD method instead of manually flashing by fastboot commands.
Have you installed the latest version of RSD-lite 6.2.4? Have you installed the latest moto drivers?
If you have extracted the RETBR. zip, search for "flashall.xml" file. Open it with a texteditor and you'll find the correct flashing commands.
So I unlocked bootloader and FRP. Installed magis. It was working, but when i tried to install xposed, it went into a bootloop. Now I'm stuck at eRecovery screen with nothing working. I've done factory reset 10-15 times. Clicking 'Download latest version and recovery' is also not giving anything. Can go to fastboot mode. Went there, saw FRP was locked. Thinking I'll redo the process, I relocked the bootloader. But now the commands aren't working as neither 'allow oem unlock' nor 'usb debugging' is enabled. I can't enable them as phone won't boot up. Any solutions? Please help.
Model ANE-AL00
Arseon said:
So I unlocked bootloader and FRP. Installed magis. It was working, but when i tried to install xposed, it went into a bootloop. Now I'm stuck at eRecovery screen with nothing working. I've done factory reset 10-15 times. Clicking 'Download latest version and recovery' is also not giving anything. Can go to fastboot mode. Went there, saw FRP was locked. Thinking I'll redo the process, I relocked the bootloader. But now the commands aren't working as neither 'allow oem unlock' nor 'usb debugging' is enabled. I can't enable them as phone won't boot up. Any solutions? Please help.
Model ANE-AL00
Click to expand...
Click to collapse
Go to TWRP and restore your system backup.
kilroystyx said:
Go to TWRP and restore your system backup.
Click to expand...
Click to collapse
But I didn't install a custom recovery. So no TWRP
Arseon said:
But I didn't install a custom recovery. So no TWRP
Click to expand...
Click to collapse
So, then try flash same system partition via fastboot.
I tried flashing original firmware using DC-Pheonix. But phone is still in bootloop
What your build ?
If this phone with OREO or with NOUGAT / Android 8.x or 7.x ?
Possibly didn't work because the rom was of a different built. I've an ANE-AL00 8.0.0.131. Any solutions for this fix? Thanks.
Arseon said:
Possibly didn't work because the rom was of a different built. I've an ANE-AL00 8.0.0.131. Any solutions for this fix? Thanks.
Click to expand...
Click to collapse
You should try at least flash the system from fullota, the firrmware can be found with Firmware Finder for Huawei
http://pro-teammt.ru/firmware-database/?firmware_model=ANE-AL00C00B131&firmware_page=0
kilroystyx said:
You should try at least flash the system from fullota, the firrmware can be found with Firmware Finder for Huawei
http://pro-teammt.ru/firmware-database/?firmware_model=ANE-AL00C00B131&firmware_page=0
Click to expand...
Click to collapse
Yes. I flashed same file only. But not booting up. In DC, it says file writing complete when in fastboot mode. But in upgrade mode, it fails at 5/31 PACKAGE_TYPE.
I'm using update.app from update.zip. Is that what I should be using? Should I use the other zip files(cn, public etc.)? Please help.
Arseon said:
Yes. I flashed same file only. But not booting up. In DC, it says file writing complete when in fastboot mode. But in upgrade mode, it fails at 5/31 PACKAGE_TYPE.
I'm using update.app from update.zip. Is that what I should be using? Should I use the other zip files(cn, public etc.)? Please help.
Click to expand...
Click to collapse
It seems like you are doing well, but have you read the instructions carefully? They recommend when something fail.
https://www.dc-unlocker.com/huawei-phone-flashing-in-fastboot
@Arseon
you write "ANE-AL00 8.0.0.131" - this is not the "full" build : what's your Cxxx ?
on FirmwareFinder i see (example)ANE-AL00C00B133 ( C00 = Country '00'; B133 = Build Counter )
you need the correctly build from your phone !!!
you can boot to bootloader ?
your bootloader is unlockt ?
your FRP is unlock ?
you have download your build FULL-Update ?
you have with UpdateExtractor from Update.app (inside Update.zip)
- ramdisk.img
- recovery_ramdisk.img
- system.img
extracted ? The Extractor do automatic for all *.img a *.img.header.
you have copy this 6 files to your ADB-Folder ?
If this all "YES" then boot to bootloader and
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
reboot phone, phone start to eRecovery and Low-Level format "data" and boot to system.
phone start as "new" phone (initial settings)
good : phone work
no good : all data is lost
AND very important : do not relock the bootloader !
ONLY if bootloader 'unlockt' you can self-repair !
JamesBott said:
@Arseon
you write "ANE-AL00 8.0.0.131" - this is not the "full" build : what's your Cxxx ?
on FirmwareFinder i see (example)ANE-AL00C00B133 ( C00 = Country '00'; B133 = Build Counter )
you need the correctly build from your phone !!!
Click to expand...
Click to collapse
Mine is ANE-AL00 8.0.0.131(C675). I used ANE-AL00C00B131 (http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2370/g1789/v138744/f1/full/filelist.xml ) to flash
JamesBott said:
you can boot to bootloader ?
your bootloader is unlockt ?
your FRP is unlock ?
Click to expand...
Click to collapse
Sadly no. Both bootloader and frp are locked.
JamesBott said:
you have download your build FULL-Update ?
you have with UpdateExtractor from Update.app (inside Update.zip)
- ramdisk.img
- recovery_ramdisk.img
- system.img
extracted ? The Extractor do automatic for all *.img a *.img.header.
you have copy this 6 files to your ADB-Folder ?
If this all "YES" then boot to bootloader and
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
reboot phone, phone start to eRecovery and Low-Level format "data" and boot to system.
phone start as "new" phone (initial settings)
good : phone work
no good : all data is lost
Click to expand...
Click to collapse
Since bootloader and frp locked, adb commands are not working. Hence I'm using DCPheonix to flash the file. But without luck. It's still botting to eRecovery only
your phone is C675, you flash C00 : no correct
now is inside your phone a 'mix'
i think, you can no self-repair - sorry
@Arseon, my opinion your system partition is a mess due to xposed installation fail.
The solution for this case is restore system partition, it worked for me in the past.
In some cases we can get lucky install a clean system partition even if it is from other region code, because the main differences between regions are located in the other partitions
But what I learning is that system from C00 region don’t follow this standard because at least is missing google apps.
With DCPheonix did with get lucky and flash all files or just the first 4 and stop in the PACKAGE_TYPE?
same situation
I am in the same situation, can only boot to erecovery. I tried boot fastboot flash 4 files (because i have bootloader and frp unlocked) and dc-unlocker without luck. In both cases pass the flash but phone still not boot, only erecovery. I can get twrp works now following this guide: https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692 but i dont have backups because i do a factory reset and the internal storage is empty. What can i do in twrp? I flash the correctly firmware for my phone ANE-LX3 8.0.0.104(C605), with this file ANE-LX3C605B130 (8.0.0.130) from here: http://pro-teammt.ru/firmware-database/?firmware_model=ANE-LX3&firmware_page=0 . Any other suggestion?
Edit: I can solve my problem. When I connect my phone in fastboot mode to dc-unlocker it give me an info:
Found Phone : ANE-LX3
Model : Huawei phone in fastboot mode
IMEI : 867903xxxxxxxxxxxx
Serial NR. : KPS7N18xxxxxxxxx
Firmware : ANE-LX3 8.0.0.104(C605
IMEI1:867903032092188
MEID:00000000000000
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 3829mv
and with the firmware info I download that version exactly (ANE-LX3 8.0.0.104(C605, found on easy-firmware web page, paid), flash with dc-phoenix, and i got it, the device boots again. Hope it help to anyone, thks. This thing cost me 28 usd, too expensive for unroot a device lol
alvavaca said:
I am in the same situation, can only boot to erecovery. I tried boot fastboot flash 4 files (because i have bootloader and frp unlocked) and dc-unlocker without luck. In both cases pass the flash but phone still not boot, only erecovery. I can get twrp works now following this guide: https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692 but i dont have backups because i do a factory reset and the internal storage is empty. What can i do in twrp? I flash the correctly firmware for my phone ANE-LX3 8.0.0.104(C605), with this file ANE-LX3C605B130 (8.0.0.130) from here: http://pro-teammt.ru/firmware-database/?firmware_model=ANE-LX3&firmware_page=0 . Any other suggestion?
Click to expand...
Click to collapse
This thread can help you a lot => HuRUpdater
kilroystyx said:
This thread can help you a lot => HuRUpdater
Click to expand...
Click to collapse
Thks for your help, I can solve my problem. When I connect my phone in fastboot mode to dc-unlocker it give me an info:
Found Phone : ANE-LX3
Model : Huawei phone in fastboot mode
IMEI : 867903xxxxxxxxxxxx
Serial NR. : KPS7N18xxxxxxxxx
Firmware : ANE-LX3 8.0.0.104(C605
IMEI1:867903032092188
MEID:00000000000000
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 3829mv
and with the firmware info I download that version exactly (ANE-LX3 8.0.0.104(C605, found on easy-firmware web page, paid), flash with dc-phoenix, and i got it, the device boots again. Hope it help to anyone, thks. This thing cost me 28 usd, too expensive for unroot a device lol
---------- Post added at 02:08 PM ---------- Previous post was at 02:01 PM ----------
Arseon said:
I tried flashing original firmware using DC-Pheonix. But phone is still in bootloop
Click to expand...
Click to collapse
In pretty sure you are flashing the wrong firmware, try to push your version with dc-unlocker in fastboot and download the excatly matching firmware. Good luck
well, i have all of this+one more tougher stuff..
Well, I tried to install a custom ROM on my P20 Lite (ane-lx1) via TWRP aand when I failed I ended up into a bootloop, but the thing that got me a headache after a full day of forum research is that when I attempted to install the custom ROM the TWRP wanted a .img file, not a .zip file, so I rebooted after I alreday wiped out everything, I made a backup into the phone, BUT I cant access it because.. the TWRP freezes every time at the TeamWin logo.....the only thing that is accessible now its the fastboot&rescue mode and I'm out of juice and desperated...the bootloader is enabled...i think i preety much killed my phoen and my brain trying to get an android stock experience...i really have to get some sleep,well..thank you for your attention, if you have any suggestions that would pick me up from this mess I would be very greatfull, i'll see what i had left to do as soon as i'm able to...for now, have a good night/day/afternoon, whatever side of the world you're from
Edit:
I left the phone all night into bootloobing and after it got FULLY discharged, I dont know exactly how but the TWRP hasn't popped out, instead after this I was able to get into eRecovery and now it is downloading the 146(C432) version. I guess that I got lucky
Hi folks, I've had a Huawei P20 Lite lying around here for a while. It is a demo device.
I was able to successfully unlock the bootloader with using the Testpoint method.
Now I need help to change the country code from "demo" to "eu" and I also need the right firmware. Is there a free way to change the country code?
I hope you can help me with that ? Thanks in advance.
cvpcvp said:
Hi folks, I've had a Huawei P20 Lite lying around here for a while. It is a demo device.
I was able to successfully unlock the bootloader with using the Testpoint method.
Now I need help to change the country code from "demo" to "eu" and I also need the right firmware. Is there a free way to change the country code?
I hope you can help me with that ? Thanks in advance.
Click to expand...
Click to collapse
Hi, look here
If you are running EMUI 9.1, flash C432 oeminfo and use variant with HuRupdater https://forum.xda-developers.com/t/...0-0-046-070f-emui-8-0-0.4324543/post-85538623
https://forum.xda-developers.com/t/...0-0-046-070f-emui-8-0-0.4324543/post-85538725
Thanks in advance. Somehow I can no longer get into the / system or the smartphone can no longer boot. When running HuRupdater I also get an error message that / System cannot be mounted. It only boots TWRP
I was able to import the oeminfo beforehand. There weren't any problems.
cvpcvp said:
Thanks in advance. Somehow I can no longer get into the / system or the smartphone can no longer boot. When running HuRupdater I also get an error message that / System cannot be mounted. It only boots TWRP
I was able to import the oeminfo beforehand. There weren't any problems.
Click to expand...
Click to collapse
Can you write down exactly what you did?
What is your version of EMUI?
In fastboot mode run commands:
fastboot oem get-build-number
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
I guess I've stupidly used the wrong command line a number of times to get twrp to run.
fastboot flash system, boot or recovery twrp....
At least it worked with the country ID change ... if only a small consolation for the first
fastboot oem get-build-number
(bootloader) :ANE-LX1 8.0.0.112(C432)
fastboot getvar vendorcountry
vendorcountry: hw/eu
fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :ANE-LX1 8.0.0.112(C432)
cvpcvp said:
ANE-LX1 8.0.0.112(C432)
Click to expand...
Click to collapse
your firmware is incomplete, it must be 8.0.0.143, if I'm not mistaken. Try again Huru method & factory reset in Stock recovery (not in TWRP!).
Or, download Service ROM Link , unpack , there's dload folder in "Software" . Copy dload folder (without unpacking it) to the OTG flash, turn off the phone and press and hold both volume buttons + Power ( this method will lock the BL again).
Thanks for the files. But i get an
Softwaere install failed
Incompatibility with current version.
Please download the correct update package.
EDIT: cant find the firmware version: ANE-L01C185B112 / ANE-LX1 8.0.0.112(C432)
EDIT2: same fail with 8.0.0.178(C432)
cvpcvp said:
Softwaere install failed
Incompatibility with current version
Click to expand...
Click to collapse
Probably due to incomplete firmware .112 , ( it was stupidity on my part to suggest Service ROM in this case, sorry. Maybe I was too sleepy...).
1. Try again Hurupdater method, it should work (don't forget to press Volume down)
2. Reboot into eRecovery, if possible, and select Download latest version and recovery
cvpcvp said:
cant find the firmware version: ANE-L01C185B112
Click to expand...
Click to collapse
Flash only C432 regional variant!
-Alf- said:
Probably due to incomplete firmware .112 , ( it was stupidity on my part to suggest Service ROM in this case, sorry. Maybe I was too sleepy...).
1. Try again Hurupdater method, it should work (don't forget to press Volume down)
2. Reboot into eRecovery, if possible, and select Download latest version and recovery
Click to expand...
Click to collapse
Can you explain me, how i can Boot into twrp without Flash twrp in recovery ramdisk?
cvpcvp said:
without Flash twrp in recovery ramdisk?
Click to expand...
Click to collapse
And what stopping you from doing it?
-Alf- said:
And what stopping you from doing it?
Click to expand...
Click to collapse
Okay, idon't think that's relevant anymore anyway
I found the problem. It was the TWRP version. I took the latest one (twrp-3.5.2_9-0-anne.img) and it couldn't mount the /system partition. Now I took a version from this forum (twrp-3.2.1-0.img), which seems to be specially adapted for the Huawei devices. Unfortunately, it doesn't support OTG, but that wasn't a problem because I moved the files it to the internal memory.
Only with this twrp version could HuRUpdater.zip be executed correctly and all other files just like that. Here, too, I was first asked to press the vol-down button.
After the smartphone finally boots properly, I flash the firmware via dload to lock the bootloader again and do over the Recovery Wipe data / factory reset + cach partition.
Now I'm on version 8.0.0.046(0CXB). Unfortunately the device cannot find a new firmware version and nothing can be updated via HiSuit.
Can you tell me which step I have to take now to get the latest Android version for the device?
Thank you very much so far for your help
cvpcvp said:
Now I'm on version 8.0.0.046(0CXB)
Click to expand...
Click to collapse
Unfortunately, you have incomplete FW there again, I think you're doing something wrong. And until the correct FW is there, you won't be able to receive OTA update or update via dload.
If you have followed instructions to the letter , it must work.
Use this TWRP . ( I don't know why you used TWRP 3.5.2.9, in the guide there is a link to 3.2.1-pretoriano80.). 3.5.2.9 isn't fully compatible with our device.
Try this way out:
- Flash TWRP
- Wipe - format data
- Reboot back to TWRP
- Wipe - Advanced wipe - wipe Dalvik/ART, cache, data, system
- Go back and flash HuRu
Note: the installation of the first file (write radio image...) must take longer, 2-3 minutes, this is proof that the installation is proceeding properly.
Btw, have you tried update via eRecovery & Wi-Fi?
Did it exactly like that. And then the 9.1.0.370 (C432) from the same thread loaded (dload / ANE-L01_hw_eu).
Now i have the firmware: ANE-LGRP2-OVS 9.1.0.370 in the device information.
Unfortunately, there is no further update, but I also don't know whether the current one is already the most recent?
What I also notice is that Dual-Sim settings are available in the menus. The IMEI2 is only provided with 000000000000000. I know that my device "only" supports single SIM.
Can I fix that too? Then everything should be fine as far as possible
cvpcvp said:
ANE-LGRP2-OVS
Click to expand...
Click to collapse
Wrong again .
cvpcvp said:
What I also notice is that Dual-Sim settings are available in the menus. The IMEI2 is only provided with 000000000000000. I know that my device "only" supports single SIM.
Click to expand...
Click to collapse
Oh, it's all clear now
Because this oeminfo is for dual SIM. Oeminfo for single SIM can be found for example here:
https://forum.xda-developers.com/t/c432-single-sim-oeminfo.3873312/
Also update_all_hw.zip file is for ANE-L21, you need ANE-L01, unfortunately, I don't have files for single SIM.
cvpcvp said:
Can I fix that too?
Click to expand...
Click to collapse
Maybe...You have to downgrade to Oreo via HuRupdater using downloaded files, then install TWRP over eRecovery and install stock Recovery.
Download https://androidhost.ru/2zMw and create dload folder .
In TWRP install new oeminfo.img , then go back to the main TWRP's menu, select Reboot > Power off. Use three buttons kombo to flash service ROM.
To be honest, I've never tried a variation like this, so I'm not responsible for this procedure, but it should work. The question is, is it worth it ...
-Alf- said:
Wrong again .
Click to expand...
Click to collapse
Which step is missing now exactly? I followed the steps from you. I also used the files from the other thread that you linked. The single-sim / dual-sim problem is not important either. The main thing is that it works that way too
cvpcvp said:
The single-sim / dual-sim problem is not important either.
Click to expand...
Click to collapse
Are you sure? In my opinion, this is your main problem...
Hello, it's been a while. I sat down again and went through everything. The dual SIM files fold onto a single SIM smartphone. I was finally able to install the update via eRecovery after flashing via TWRP. Then two updates were pulled or installed via Android OS. Now I'm on 9.1.0.132 (C432E5R1P7).