Hi guys, i have a big problem. I tried to update my girlfriend's phone (huawei g play mini chc-u01). I read some guides and i downloaded all firmwares from huawei site, unlock bootloader and tried to install updates. But at some point, phone won't boot up ! I made a mistake ! Now the situation is that when i turn on the phone, it shows the honor logo. I tried to flash via fastboot the system, recovery and boot image that i extracted from UPDATE.APP of the firmware taken from huawei site. Also tried to flash twrp recovery and find out a way to unbrick phone, but nothing. I can't find anything that works. An other thing is that in fastboot mode, when i type some erase command, output is remote command not allowed, but flash command seems to work.
How can i restore phone ? Is not there a way to restore it, I can make a aspo or cm based rom from system.img and other stock stuff ? Just split image to see files inside.
The last thing and maybe the core of mistake. I flash via twrp an oem file and then honor logo is appeared.
Thanks at all guys !
Edit: I finally restored phone. it works again flashing its lollipop version firmware.
bob1791 said:
Hi guys, i have a big problem. I tried to update my girlfriend's phone (huawei g play mini chc-u01). I read some guides and i downloaded all firmwares from huawei site, unlock bootloader and tried to install updates. But at some point, phone won't boot up ! I made a mistake ! Now the situation is that when i turn on the phone, it shows the honor logo. I tried to flash via fastboot the system, recovery and boot image that i extracted from UPDATE.APP of the firmware taken from huawei site. Also tried to flash twrp recovery and find out a way to unbrick phone, but nothing. I can't find anything that works. An other thing is that in fastboot mode, when i type some erase command, output is remote command not allowed, but flash command seems to work.
How can i restore phone ? Is not there a way to restore it, I can make a aspo or cm based rom from system.img and other stock stuff ? Just split image to see files inside.
The last thing and maybe the core of mistake. I flash via twrp an oem file and then honor logo is appeared.
Thanks at all guys !
Edit: I finally restored phone. it works again flashing its lollipop version firmware.
Click to expand...
Click to collapse
how did you restore your phone ?
I have a g play mini chc-u01 and I upgraded it directly from android 4.4.2 (c185b067 ) to 6.0 (c185b560 ) but this build has many issues. now I want to downgrade to lollipop but I can't get into the recovery mode. whenever I try to enter the recovery mode, the bootloop happens. I tried to flash the system recovery extracted from UPDATE.APP but it didn't work neither did twrp. so can you show me the steps you made to restore your phone ??
Same Problem here. can you share how you fixed it?
Related
Hi guys!
I am kind of new to Android, but I bought a Lenovo A7600H, updated to 4.4.2 and rooted it.
By "mistake" I deleted at least one apk-file in the system folder. I wanted to update to the newest firmware, but due to the missing files I wasn't able to update. So I tried to flash it with the original factory image, which didn't work with SP flash tool, so I tried to flash with fastboot.
Apparently I applied the "system.img" to the recovery partition with the command "fastboot recovery system.img". Now, when I turn on the tab, it just says "SYSTEM image incorrect! Shutdown after 10,9,8,... seconds".
Is there anything I can do now or is my tab lost forever?
Thanks in advance for any help and sorry for the bad description.
Hi guys, i got my H9 yesterday and because i thought i read enough on this forums i wanted to unlock it then install TWRP and install superSU to gain root access and stick with the stock firmware.
Unlocking went perfectly fine,phone booted to OS, than i flashed twrp 3.1.1-1 as advertised here and made a factory reset. Phone was stuck in bootloop for unknown reason.
I made several wipes and somehow managed to check all boxes in the wipe menu which erased the whole OS.
Now i read here that others have the "no OS" problem too but because i still have all unlocked fastboot and twrp i wanted to ask which method is best to flash back the original FW.
Which stock ROM is safe to install? i have european H9 is STF-L09C432B170 the right one for me?
Which method is the best to install it? Copy the 3 zips to internal stoagre via OTG device and install it out of twrp? I read that there is also a force method where users can push vol up, vol down and power simultaneously and enter the huawei install force mode.
I am quite sad that the phone was stuck in bootloop after twrp install and still dont know what caused it. When i install it from twrp there are 3 zips: update, data full public , hw eu. In which order do they have to e installed and is one of them overwriting the TWRP recovery?
Please give me a short hint/procedure, im quite afraid that i cant get my phone back to work and it is brand new. I dont know what caused the unsolvable bootloop.
Best regards and many thanks
Hi.
Check this:
https://forum.xda-developers.com/showpost.php?p=73334439&postcount=1
This help you.
Regards
thanks for the hint but i cant find a solution for me there.
ut this
i copied the 3 .zip files to internal today but TWRP doenst allow me to write them it fails with "write err errno 9"
then i tried to copy the update.pp in DLOAD folder on micro sd but this is not possible because filesize is over 2gb. i tried to format micro sd with twrp to exfat but it till doesnt work. please give me a little hint what to do im completely desperate about the situation.
Today i installed Huawei Multitool and extracted the .img file out of the update.app files, i was able to flash all 4, system, boot, recovery and cust.
Now the rec. menu is back to stock and everything got installed but the phone still isnt booting. i think it is because i missed the userdata.img which i cant find anywhere.
Other users here have the same problem. Is there a firmware package which includes all 5 .img data?
Best regards
i found the official huawei service full repair firmware with all necessary files for unbrick (system, cust, recovery, userdata, boot) flashed them via fastboot but stil device is "hanging" after the warning message that its unlocked. i think it is because i wiped vendor data in twrp but i cant flash vendor.img in fastboot. it is included in the fw package but cant be transfered to phone via fastboot. it stops at part 1/2 because the filesize allowd is around 470mb max but the extracted file has a size of 670. anyone know what to do?
Best regards
You need to go via the Rebrand way with no rebrand. I had the same problem and was trying to use the multitool without success. The oeminfo can be flashed alternatively if it fails during the HWOTA process.
https://forum.xda-developers.com/honor-9/help/how-flash-oeminfo-t3657499
ok i download all the folders with the .bat file. Then i download C432B150 from the czech site and add it to the update folder. Than i rename the 3 files accoding to the manual and run the .bat file but without rebranding right?
Des this tool any different than the HuaweiMultiTool or fastboot with flash command?
Best regards
I treid out HWOTA, the first step installing twrp is successful than i disattach usb cable as described and enter twrp. Then it says in twrp i have to connect again and press enter but then the bat file stops and doenst go on. i dont come to the point where i can choose rebrand or flash firmware.
Whats wrong here?
edit: i saw in the .sh file that the script executes wait_adb but my phone is not entering adb mode as it seems when in main screen of twrp. is this normal or do i have to set it manually in twrp
best regards
I was able to install the B130 now via 3 button recovery. Now im on B130 but cant update elsewhere. Also the 2 capacitive buttons are not working. Bootloader is locked again. Everything is stock and the phone runs great. When i update with the 3 buton method from external sd, which firmware should i use? i tried B150 full OTA but it aborts after 5% with an error. Do i only need to get a small OTA package now?
How can i put my cap. buttons back to work? Too bad only the 3 button method worked to recover the phone.
Best regards and many thanks.
I did the HWOTA with b120 firmware and then used firmware finder to update to b150.
The bug with capacitive buttons is present till Oreo. I use the home button gestures anyways.
Hope it helps.
ok, thats bad but they worked with the initial revision of b130 and b150 when i downloaded it OTA. Is this something like a fuse like.knox at samsung which happens at custom flashing?
Sent from my GT-I9300 using Tapatalk
the HWOTA method doesnt work, the batch file gets stuck after connecting the phone in twrp back to computer. in script it says wait_adb but it is not recognized somehow.
do u know a solution? anotherone here got that problem too.
im very afraid of that, i read here that everything related to twrp 3.1.1-0 and 3.1.1-1 is problematic a lot of people cant boot after installing twrp and can wipe whtever they want the phone never boots fully
whats the difference in the B130/B120 the phone came from huawei and the version flashed via tools? when i got it everything worked
i have this version.
ok so install twrp have frq and bootloader unlocked and then do backup out of recovery? with your file? can you provide download link? is this then a zip file?
I want to solve the thread and how i solved problem.
The B130 service firmware by huawei could be installed via 3 button method, than i was able to go up to the newest B180 via firmwarefinder and DNS method but with not working cap. buttons and flash etc.
Yesterday i installed TWRP 3.1.1-1(temporary) via HWOTA.zip method (ireplaced the older twrp in recovery folder) and successfully installed B120 and got the buttons etc working again. Then installed root and now system works fine and is rooted. My mistake was to install twrp over B130 or B150 which i downloaded OTA at the first day i got the phone. I tested this yesterday to install TWRP along with B150 and unlocked bootloader, infinite bootloop again. With B120 the TWRP 3.1.1-1 works out of the box without any loops.
The 2 trouble solvers where B130 service firmware and HWOTA with B120.
The external SD had to be inserted in card reader on PC because of the large filesize of the B130.
I would recommend to everyone before starting to play with the H9 to move the B130 folders to phone while it is still accessible. When everything bricks like in my case and u still have twrp than you can go to twrp main screen and connect phone to computer to rename the folder with B130 to "dload" and arrange update.app accordingly on PC or in TWRP file manager.
Can i set this topic to [SOLVED] myself?
Best regards
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
this works flawlessly with 3 button method
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Completely Bricked
Me too need a stock rom of ta 1056. Please help if you could manage to provide a helping hand... ?
I had the same issue like yours, looping in twrp. then i tried to flash it with a so called stock rom from net, guess what it went completely bricked and I donnow what to do. ??
mrabudi said:
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Click to expand...
Click to collapse
It's simple. just get the stock recovery (and boot, optional) to flash it with fastboot and go to recovery and wipe it and you'll be ok.
and also using the twrp on this phone is not a great idea to wipe.
if you wanna wipe. please use "fastboot -w" to wipe the phone while bootloader is unlocked. or stock recovery to wipe.
Because twrp built this recovery with only formatting option was ext4 to /data and /cache. So the phone cannot operate properly. Which leads to fake failed decryption notification.
Data partition must need to be formatted under f2fs format.
And finding rom for this phone is pretty easy. Just find some nb0 file for this phone (any variant of this phone should work) and extract it with "nb0 extractor" and then flash it with SP Flash tool by mediatek.
That's my way. I don't know how will you do. But normally you only need the nb0 file and then flash it with OST LA (Nokia's flash tool based off Intel's SUT L1/L3 tool).
My Nokia 1 TA-1047 stuck at Nokia logo screen
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
cuantonhonhoi said:
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
Click to expand...
Click to collapse
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047. Since it's a universal ROM so any variant of the phone can also work) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to look at line with partition "metadata" and then edit "boundary_check" to false.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
kutiz21 said:
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to hide/delete line with partition "metadata" in scatter.txt and you can flash it perfectly.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
Click to expand...
Click to collapse
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
pabloluih said:
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
Click to expand...
Click to collapse
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
kutiz21 said:
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
Click to expand...
Click to collapse
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
That's weird. If you unlocked the bootloader and install adb/fastboot (must be latest version. Older version will not recognize the phone, download platform-tools from google dev site, don't download adb tools off XDA) + Nokia's driver from emulated CD drive (every time you plug the phone to computer with official rom, you'll see it) properly then it should be able to work.
You need to check the fastboot device driver Device Manager (devmgmt.msc) and see if the driver is properly installed yet.
You can only use "fastboot -w" once the bootloader is unlocked. And booting up the phone. It will say the bootloader is in Orange state.
You need to unlock oem bootloader from developer settings when the stock rom is there. And in fastboot too
Here is how you unlock it:
Enable oem unlock from dev settings
Then reboot to fastboot mode (bootloader)
Do this:
"fastboot oem key "serial number string converted to md5, not imei strings" "
"fastboot oem unlock"
Volume up
Then you are actually unlocked the bootloader.
Unlock from developer settings only will not do the trick. It only allows you to have ability unlock the bootloader in fastboot.
If you stuck on the Encryption unsuccessful screen. Try wipe it with stock recovery or "fastboot -w" (if you properly unlocked the bootloader)
If you think you can't do anything anymore. Just flash the ROM provided you above.
If you need the extracted ROM for SP flash tool and the fastboot driver. I can link it to you.
Most of all drivers will automatically install off Windows Update if you're on Windows 10 (except the fastboot driver, and yes. SP flash tool drivers are also provided by Windows 10 too)
Also. You should update the phone to the latest software update when flashing stock rom too. Because newer builds for this phone is compatible-friendly with GSI rom (Treble ROMs like AOSP Android 9 or 8.1 by phhusson)
Updates on Android 9/10
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
Nokia might harden the security of the device so you can't use Magisk on stock rom.
Just a little disclaimer: I am an ABSOLUTE NOOB at this stuff and I just followed tutorials and guides; no experience whatsoever and I badly need your help
It all started when I wanted to root my phone. So I decided to install a custom recovery on the phone first(CWM to be exact). I flashed the recovery.img file and soft bricked my phone. I managed to fix it easily just by erasing recovery by using adb. Afterwards, recovery was accessible again. Since I couldn't do it that way, I tried downloading the phone's latest firmware from ASUS' website and pulled the boot.img out of it and patched it with Magisk. Flashed it and boom, bricked my phone. I tried fixing it the same way I did with the recovery.img but it didn't work. I even tried erasing it and flashing the original boot.img file I pulled out of the firmware file I got from ASUS' website, but it wouldn't work; it would boot up, show the ASUS logo, then shut off. Please, tell me there's a way through this, and btw the phone's bootloader was unlocked for sure; I used ASUS bootloader unlocker from the website. I have all firmware files already downloaded in case I need 'em.
UPDATE: I flashed a boot.img form an older firmware file from the same website and it kinda worked. It boots now and it seems to be stuck on the Zenfone logo now :/
Hey. I remember that you can boot into adb mode and then do
adb sideload "yourfirmware.zip"
The instruction holds true for earlier zenfones. See if it works here.
I have the same phone, but is dead, no recovery, no fastboot mode, no screen.
What can i do?. My pc just detect QDloader driver help plz.
Try this
msoliveras said:
What can i do?. My pc just detect QDloader driver help plz.
Click to expand...
Click to collapse
You need unbrick with: stock ROM
addrom.com/raw-rom-unbrick-for-asus-zenfone-live-l1-za550kl
QFIL program 1.0.0.2 versión
androidmtk.com/download-qualcomm-flash-image-loader-qfil
And valid version of QDloader driver
gsmusbdrivers.com/download/android-qualcomm-usb-driver
watch this video: youtube.com/watch?v=Ao5FB9mVZCU
Important if you zenfone live l1 is 2/3Gb Ram or is Go version 1Gb Ram to download correct stock ROM
Deceinard said:
Just a little disclaimer: I am an ABSOLUTE NOOB at this stuff and I just followed tutorials and guides; no experience whatsoever and I badly need your help
It all started when I wanted to root my phone. So I decided to install a custom recovery on the phone first(CWM to be exact). I flashed the recovery.img file and soft bricked my phone. I managed to fix it easily just by erasing recovery by using adb. Afterwards, recovery was accessible again. Since I couldn't do it that way, I tried downloading the phone's latest firmware from ASUS' website and pulled the boot.img out of it and patched it with Magisk. Flashed it and boom, bricked my phone. I tried fixing it the same way I did with the recovery.img but it didn't work. I even tried erasing it and flashing the original boot.img file I pulled out of the firmware file I got from ASUS' website, but it wouldn't work; it would boot up, show the ASUS logo, then shut off. Please, tell me there's a way through this, and btw the phone's bootloader was unlocked for sure; I used ASUS bootloader unlocker from the website. I have all firmware files already downloaded in case I need 'em.
UPDATE: I flashed a boot.img form an older firmware file from the same website and it kinda worked. It boots now and it seems to be stuck on the Zenfone logo now :/
Click to expand...
Click to collapse
I had the same problem and qfil didn’t worked. Try mi flash tool( try all versions, because not all work). It was able to flash my phone.(zenfone l1)
I will try to be brief, I've tried to root my Y6- L22 (2018) Huawei, but I think I flash a bad ROM or got mixup with the TWRP command.
I am now trying to flash the original firmware to have a functional phone. I've tried the method with Huawei Update Extractor and flashing the following:
fastboot flash system SYSTEM.img
fastboot flash ramdisk ramdisk.img
fastboot flash kernel kernel.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.IMG
All the process is running smoothly with OKAY everywhere but when I reboot my phone goes to ‘Huawei’(with the lovely and annoying Huawei ring) then it reboot again. I tried different Firmware as I do not have the Built version/regional Number, but none are working.
I've also tried the dload method with the Update.app in the microSD... but getting Software install failed after 5%.
In the meantime I’ve also erase system, and erase cache and install firmware without any success
I would appreciate to have some suggestion or advice from any of you that have faced this issue or know how to get out of this.
Many thanks,
MrKMr said:
I will try to be brief, I've tried to root my Y6- L22 (2018) Huawei, but I think I flash a bad ROM or got mixup with the TWRP command.
I am now trying to flash the original firmware to have a functional phone. I've tried the method with Huawei Update Extractor and flashing the following:
fastboot flash system SYSTEM.img
fastboot flash ramdisk ramdisk.img
fastboot flash kernel kernel.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.IMG
All the process is running smoothly with OKAY everywhere but when I reboot my phone goes to ‘Huawei’(with the lovely and annoying Huawei ring) then it reboot again. I tried different Firmware as I do not have the Built version/regional Number, but none are working.
I've also tried the dload method with the Update.app in the microSD... but getting Software install failed after 5%.
In the meantime I’ve also erase system, and erase cache and install firmware without any success
I would appreciate to have some suggestion or advice from any of you that have faced this issue or know how to get out of this.
Many thanks,
Click to expand...
Click to collapse
07/06/19
Hi All, so I've not had any reply, but I keep trying to fix this Y6 phone.
Just answering to myself in case this can help someone; if you happen to lose the Built Number and phone is not working, you can check if retailer are still selling this phone. If yes, it is likely that they have the same built number and regional code. For mine it is ATU-L22 - 8.0.0.140 (C185).
MrKMr said:
07/06/19
Hi All, so I've not had any reply, but I keep trying to fix this Y6 phone.
Just answering to myself in case this can help someone; if you happen to lose the Built Number and phone is not working, you can check if retailer are still selling this phone. If yes, it is likely that they have the same built number and regional code. For mine it is ATU-L22 - 8.0.0.140 (C185).
Click to expand...
Click to collapse
hi. how did you fixed the bootloop?