Related
Hi guys!
I have use this Zenfone 5 LTE variant (ASUS_T00P or A500KL variant) for about a year unrooted until recently the phone failed/bricked due to unknown reason.
The last stable version that I used before the phone failed was KitKat 4.4.2 (UL-ASUS_T00P-WW-11.4.6.94-user).
After a visit to Asus service center, they re-flashed my phone with Lollipop 5.0 (LRX21M.WW_Phone-12.4.5.58-20151013 044030443_201501281349).
When I tried to root the phone with the common Zenfone 5 Lollipop Rootkit available on the Internet, it failed due to some restriction in writing some flash part inside the phone.
Again, one more weird thing with this phone is when I tried the power button+volume up button, it won't bring me to fastboot mode.
Instead, the button combo will bring up a yellow text saying that my phone now is in CSC mode.
In recovery mode, I couldn't find the "apply update from adb" menu too.
Even in the .zip firmware file downloaded from Asus site, I couldn't find the fastboot.img and recovery.img
So, herein lies my questions.
1. What will happen to the failed root process? Will it corrupt my current Lollipop file system in near future?
2. Does anyone know what is CSC mode?
3. Can anyone confirm whether I can root this phone or not with the current setup? I really need to root this phone ASAP as I want to try to recover all my lost photos inside the internal storage with help from other software.
4. Can I still sideload from adb incase the phone brick again since I don't want to visit and pay Asus technician just to re-flash my firmware. I totally can do that myself provided they gave me the option in the 1st place.
p/s: anyhow, I wouldn't recommend this phone to anyone due to above reason.
I have the same issues with this model. I hope someone will be able to help us.
Same problem to me can't do anything .
CSC mode - locked bootloader.
UnlockBootloader in oficial site Asus (section Utilites)
http://www.asus.com/Phone/ZenFone_5_A500KL/HelpDesk_Download/
TWRP recovery for a500kl too.
As far as I know the very first version of Lollipop on this device, WW 12.4.5.22, is rootable. I had no luck with the latest versions of firmware, so you probably won´t be able to root your current one. If you get back to this version using the downgrade version on the Asus website, you can use Kingroot to root the device. After you install Kingroot, reboot the phone, otherwise it will not be able to root it for some reason. I bought this phone because my lumia 710 decided to give up on life and it´s mainboard died. I needed some not very expensive phone with pretty good specs and big enough RAM for a low amount of money and so far it´s been working flawlessly
Did you manage to root? I have the same version on lollipop and have managed to root it and install TWRP.
Kibet said:
Did you manage to root? I have the same version on lollipop and have managed to root it and install TWRP.
Click to expand...
Click to collapse
How did you do it?
Follow this thread if you have any questions ask.
http://forum.xda-developers.com/zenfone-5/help/installing-custom-recovery-zenfone-5-t3365120
Ok thanks
I'm trying to flash CM 12.1 to my ZE551KL. I have the most recent nightly and the gapps zips. I tried to flash the ROM and kept getting a signature not verified error that I forget the exact wording of. I researched a bit and concluded that I need to unlock the boot loader. So here's where the problem starts. Asus makes a boot loader that will work on my phone but requires firmware 1.16.40.763. My phone won't update past 1.15 something. And that's odd to me since I just got it yesterday.
I tried to use the Asus boot unlocker anyway but nothing happened because my phone won't update to firmware 1.16.40.763. I saw a firmware update to 1.16.40.763 on the Asus website for the Z00T. I have the Z00TD. Will the Z00T firmware brick my phone or work on my phone? My thought it that if it works I can run the boot unlocker that requires 1.16.40.763 and then with the boot loader unlocked I should stop receiving the signature invalid error when I try to flash CM12.1. Does that sound about right? This is my first time flashing CM myself.
Thank you for your help and thoughts.
You should only flash a ROM that's made specifically for your device.
It's actually a good thing for you that it did not flash.
http://wiki.cyanogenmod.org/w/Unofficial_Ports#Asus - Zenfone 2 Laser is not in the cyanogenmod list.
David McDavid said:
I'm trying to flash CM 12.1 to my ZE551KL. I have the most recent nightly and the gapps zips. I tried to flash the ROM and kept getting a signature not verified error that I forget the exact wording of. I researched a bit and concluded that I need to unlock the boot loader. So here's where the problem starts. Asus makes a boot loader that will work on my phone but requires firmware 1.16.40.763. My phone won't update past 1.15 something. And that's odd to me since I just got it yesterday.
I tried to use the Asus boot unlocker anyway but nothing happened because my phone won't update to firmware 1.16.40.763. I saw a firmware update to 1.16.40.763 on the Asus website for the Z00T. I have the Z00TD. Will the Z00T firmware brick my phone or work on my phone? My thought it that if it works I can run the boot unlocker that requires 1.16.40.763 and then with the boot loader unlocked I should stop receiving the signature invalid error when I try to flash CM12.1. Does that sound about right? This is my first time flashing CM myself.
Thank you for your help and thoughts.
Click to expand...
Click to collapse
Where did you download the CM-12 ROM? Are you sure it's for the ZE551KL?
I'm on the same firmware and the bootloader unlock apk does work, though it leaves no indication after the phone restarts. My guess is that you're phone is bootloader unlocked just fine, but you're trying to flash a rom that wasn't built for ZE551KL (Z00TD).
I'm assuming all of you have already rooted your device and was wondering if you can point me to the files needed so that I can root my Z00TD (ZE551KL)..just got this phone yesterday and switched from a lgg3. Have been looking everywhere and can't seem to find the files needed for thiss specific device..thanks
tmjm28 said:
I'm assuming all of you have already rooted your device and was wondering if you can point me to the files needed so that I can root my Z00TD (ZE551KL)..just got this phone yesterday and switched from a lgg3. Have been looking everywhere and can't seem to find the files needed for thiss specific device..thanks
Click to expand...
Click to collapse
HampTheToker wrote up a nice tutorial fro the ZE551KL:
http://forum.xda-developers.com/showpost.php?p=65264766&postcount=7
First of all, I wanted to apologize if I'm posting at a wrong section but please do move this thread if necessary.
Second, I know some of you have already read a bunch of problems regarding to this model of zenfone 5 but I'm still hoping that one day someone can help us A500KL users. I've spent sleepless nights browsing the internet for solutions. I've been through different websites like taiwanese, chinese, russian and many more but still can't seem to find any guides or solution to my problem.
The thing is, one day after booting my phone and making it to home screen a few seconds later it's restarting on it's own. restarted and same thing happened over and over again. I didn't mind losing my files so i went to recovery to do a factory reset hoping it will resolve the problem. But the moment I press enter, a bunch of errors saying E:failed to mount...... (invalid argument) showed up. It failed wiping to factory reset. i tried wiping cache but still gets a bunch of those error. I know little about flashing so I came to a place where they said that i have to download the stock firmware from asus website with the same version and same SKU. so i did that and stored the stock rom on my external SD card (can't save in internal since I can't boot to homescreen anymore. Just ending up in Asus logo loading forever.) but still no luck. I Searched some more and found a guide about flashing using AFT. I tried but still no luck, says it needs a .raw firmware. unfortunately anywhere i go there is no .raw firmware for my phone. so I explore some more and came across about bootloader. but recently i found out that my bootloader is locked. Neither can I flash using sideload.
My phone is not rooted, no custom recovery installed, no option to install update from ADB and can't install from recovery. BUT still able to go to recovery, boot until asus logo, when charging battery icon still shows. still vibrates when powered.
I really hope someone out there can help me with my current problem. I still think this can be done cause i don't think theres a problem with the hardware. Been searching for days and I really need to recover my phone. Oh and not to mention there are 2 more of this phone on my relatives and all of them have the same problem. So please help us A500KL users. Sorry for the long message, I'm just so desperate to recover my phone. God Bless
hi bro
well firstly bootloader unlock is NOT needed for sideloading stock firmware.i'm giving you the link to one of my tutorials,follow the procedure carefully.note one thing that do NOT download the firmware whose link is given in tutorial,instead use kitkat firmware of your phone(download from asus support page)....use only kitkat firmware pls.coz my experience says that flashing lollipop directly gives errors.http://forum.xda-developers.com/zenfone-5/help/bootlooped-bricked-returning-to-stock-t3358662
[email protected] said:
hi bro
well firstly bootloader unlock is NOT needed for sideloading stock firmware.i'm giving you the link to one of my tutorials,follow the procedure carefully.note one thing that do NOT download the firmware whose link is given in tutorial,instead use kitkat firmware of your phone(download from asus support page)....use only kitkat firmware pls.coz my experience says that flashing lollipop directly gives errors.http://forum.xda-developers.com/zenfone-5/help/bootlooped-bricked-returning-to-stock-t3358662
Click to expand...
Click to collapse
That method only work for A500/501 cg models. Not A500KL .It will not work. I already came across this problem. There is NO RAW FIRMWARE FOR ZENFONE 5 LTE
ChristopherXI said:
That method only work for A500/501 cg models. Not A500KL .It will not work. I already came across this problem. There is NO RAW FIRMWARE FOR ZENFONE 5 LTE
Click to expand...
Click to collapse
but when did i say that you need raw firmware??
what we are doing is flashing fastboot,recovery and then sideloading the zip firmware which is available on asus website...
[email protected] said:
hi bro
well firstly bootloader unlock is NOT needed for sideloading stock firmware.i'm giving you the link to one of my tutorials,follow the procedure carefully.note one thing that do NOT download the firmware whose link is given in tutorial,instead use kitkat firmware of your phone(download from asus support page)....use only kitkat firmware pls.coz my experience says that flashing lollipop directly gives errors.http://forum.xda-developers.com/zenfone-5/help/bootlooped-bricked-returning-to-stock-t3358662
Click to expand...
Click to collapse
Hello bro.. your tutorial is well said but unfortunately Zenfone 5 LTE is different. Yes i do have a firmware downloaded at the official asus website and it doesn't contain any recovery.img and fastboot.img there's only boot.img inside. and yes its only kitkat. its WW 11.4.6.94
Lastly, zenfone 5 LTE doesn't have "apply update from ADB" option in recovery by default so sideloading is not really possible. I can only depend on fastboot with locked bootloader. so yeah that makes things difficult.
[email protected] said:
but when did i say that you need raw firmware??
what we are doing is flashing fastboot,recovery and then sideloading the zip firmware which is available on asus website...
Click to expand...
Click to collapse
You din't get what i mean.... His system partition is MESSED UP. The partition also contains fastboot and recovery partition. Flashing fastboot and recovery WILL FAIL. He will have to find AND RAW FIRMWARE NOT A ZIP FIRMWARE FROM ASUS.
I already searched for Raw firmware for zenfone 5 lte. There is no raw firmware for that model. Using that guide requires the raw firmware. In the process that tool will use the RAW firnware to fix the partition table.
Hopes that clears everything up
Hi Bazerald,
My 18-month old A500KL has exactly the same problem as you had described - startup never get pass the Asus logo screen, got a bunch of "E: failed to mount ....." error messages in Recovery. I was told by the Asus Service Centre technician that the problem was caused by a broken ROM and to revive the phone, a replacement of the mother board was required and they were charging megabuck for the job. I ended up taking my phone back without fixing and here I am browsing in this forum hoping to find an alternative solution.
Since I know everything else on my A500KL is still working except the internal ROM, what I am hoping to do is to find if there is a way to load the stock firmware onto an external SD card and boot up the phone from there, in other words, I would like to swap the internal and external memory. I can find a few discussions on this topic for the Samsung Galaxy, but I have yet to find a viable solution for our A500KL.
Any member has any suggestion on this idea?
ChristopherXI said:
You din't get what i mean.... His system partition is MESSED UP. The partition also contains fastboot and recovery partition. Flashing fastboot and recovery WILL FAIL. He will have to find AND RAW FIRMWARE NOT A ZIP FIRMWARE FROM ASUS.
I already searched for Raw firmware for zenfone 5 lte. There is no raw firmware for that model. Using that guide requires the raw firmware. In the process that tool will use the RAW firnware to fix the partition table.
Hopes that clears everything up
Click to expand...
Click to collapse
hi friend
i'm really sorry,i just somehow missed the line saying that he has system error..
thanks for noting
Toki Yoki said:
Since I know everything else on my A500KL is still working except the internal ROM, what I am hoping to do is to find if there is a way to load the stock firmware onto an external SD card and boot up the phone from there, in other words, I would like to swap the internal and external memory. I can find a few discussions on this topic for the Samsung Galaxy, but I have yet to find a viable solution for our A500KL.
Any member has any suggestion on this idea?
Click to expand...
Click to collapse
I agree, I was hoping for the same thing here since xda is very popular for fixing tons of problems. I guess we'll just have to wait for THE ONE who can help us.. since A500KL doesn't seem have a raw firmware I'll be very happy if anyone can spend a time and make a raw firmware for us (if it's possible). Recovering the 3 A500KL here will be very rewarding.
Also, I'm trying to not depend too much on the raw firmawre cause the main reason is the messed up partition. Still searching for a way to fix it manually and getting some ideas on how it is done on other phones.
Unless you guys found a RAW firmware for the LTE model. It's preety much hopeless. Sorry........
does anyone know if repartitioning the messed up partition of A500KL manually is possible?
I got the same problem a few months ago. I searched through the Internet and found that many many people having such problem, I concluded that it is the quality of the chips (usually 15 months of usage), not software problem alone (the phone just died suddenly, I did nothing at all!!). This was the first time I had hardware failure in phones (in the past 20 years!). I WILL NEVER BUY ASUS phone again.
Ok guys, give me a sec and i'll find the firmware. Theres one on the website thats a revert firmware that will fix it. I had the same issue with mine. This firmware will revert it back to Kitkat. Yes.. Its DOES have the stock Recovery,Boot.img and System.img files.
This is the firmware your looking for Version WW_11.4.6.94 (Downgrade Version)
http://www.asus.com/us/support/Download/39/1/0/6/8/
ONLY FLASH THAT VERSION! Only Version WW_11.4.6.94 (Downgrade Version) (WorldWide) Version..
Only the Downgrade Versions have the complete files needed to repair a bad flash or root attempt.
Follow the directions Vaib posted on the previous page, but use the firmware file above.
Should fix the software,recovery and partition issue. Also, the bootloader unlock provided by Asus is hit and miss.
I've used it to root,but alot of the files are interlinked. So you run the risk of another app not working when trying to debloat the rom. As of now there is no Alternate non Stock Rom for the A500KL. Note: After flashing the WW firmware you phone will be recognized as an Asus "T00P". This is normal and doesnt cause any issues.
If all else fails, go here for more info on the A500KL. http://www.asus-zenfone.com/search/label/Zenfone 5 LTE
Good Luck. Happy Flashing
TabascoTX said:
Ok guys, give me a sec and i'll find the firmware. Theres one on the website thats a revert firmware that will fix it. I had the same issue with mine. This firmware will revert it back to Kitkat. Yes.. Its DOES have the stock Recovery,Boot.img and System.img files.
This is the firmware your looking for Version WW_11.4.6.94 (Downgrade Version)
http://www.asus.com/us/support/Download/39/1/0/6/8/
ONLY FLASH THAT VERSION! Only Version WW_11.4.6.94 (Downgrade Version) (WorldWide) Version..
Only the Downgrade Versions have the complete files needed to repair a bad flash or root attempt.
Follow the directions Vaib posted on the previous page, but use the firmware file above.
Should fix the software,recovery and partition issue. Also, the bootloader unlock provided by Asus is hit and miss.
I've used it to root,but alot of the files are interlinked. So you run the risk of another app not working when trying to debloat the rom. As of now there is no Alternate non Stock Rom for the A500KL. Note: After flashing the WW firmware you phone will be recognized as an Asus "T00P". This is normal and doesnt cause any issues.
If all else fails, go here for more info on the A500KL. http://www.asus-zenfone.com/search/label/Zenfone 5 LTE
Good Luck. Happy Flashing
Click to expand...
Click to collapse
Tabasco , WW_11.4.6.94 (Downgrade Version) did not have recovery.img and fastboot.img inside as well.
kenooi1984 said:
Tabasco , WW_11.4.6.94 (Downgrade Version) did not have recovery.img and fastboot.img inside as well.
Click to expand...
Click to collapse
It should have, unless i accidentally linked to the wrong one. Let me see what happened.
The downgrade version should have recovery and fast-boot. It kicks it from L to KK. Since the fast-boot and recovery aren't compatible from L to KK, it should flash it. When i boot looped mine trying to a flash an alternate recovery i re-flashed using the downgrade version to fix it. I guess possibility that it could be in another WW Version, but im pretty sure i remember flashing the first WW Downgrade. I'm going to look at WW_11.4.6.71 and see if it in there.
OK, WW_11.4.6.71 has a script to install recovery. So the recovery.img is in the firmware somewhere. Try WW_11.4.6.71 instead and see if that fixes it for you.
TabascoTX said:
It should have, unless i accidentally linked to the wrong one. Let me see what happened.
The downgrade version should have recovery and fast-boot. It kicks it from L to KK. Since the fast-boot and recovery aren't compatible from L to KK, it should flash it. When i boot looped mine trying to a flash an alternate recovery i re-flashed using the downgrade version to fix it. I guess possibility that it could be in another WW Version, but im pretty sure i remember flashing the first WW Downgrade. I'm going to look at WW_11.4.6.71 and see if it in there.
Click to expand...
Click to collapse
thanks for tried to check , i downloaded WW-11.4.6.107 it did not have it either.
due to my super slow internet speed ,it took me abt 3 hours to downloaded 1 firmware....... i wish to download all to check but...... poor me..
kenooi1984 said:
thanks for tried to check , i downloaded WW-11.4.6.107 it did not have it either.
due to my super slow internet speed ,it took me abt 3 hours to downloaded 1 firmware....... i wish to download all to check but...... poor me..
Click to expand...
Click to collapse
OK, WW_11.4.6.71 has a script to install recovery. So the recovery.img is in the firmware somewhere. Try WW_11.4.6.71 instead and see if that fixes it for you.
The recovery isnt exactly named recovery.img, there's a script that refers to installing the recovery from another location. So i'd try flashing the downgrade version after getting the phone into fastboot. And unfortunately it can be difficult to tell if the phone is actually in fastboot.
TabascoTX said:
OK, WW_11.4.6.71 has a script to install recovery. So the recovery.img is in the firmware somewhere. Try WW_11.4.6.71 instead and see if that fixes it for you.
Click to expand...
Click to collapse
ok thanks , will try it later on.
Wow.
You people really didn't read the comments section throughly.
Trying normal or downgrade firmware will not work.
This procedure requires a RAW firmware.
And using the offline update tool provided by @dgadelha.
If any of you found a RAW firmware for the A500KL model.
You can easily adapt the script from his Offline update tool.
It will repartition the device.
AGAIN. trying normal firmware is not going to fix the problem
@Bazerald (i think that your a500kl is WW) Try: with stock recovery try wipe the phone (data, cache), flash the firmware downloadable from asus site UL-ASUS_T00P-WW-11.4.6.94-user, (not the downgrade version), if not success, try UL-ASUS_T00P-WW-12.4.5.22
Hi A7 users,
Let's start this off be saying, bare with me English is not my primary language.....
OK now, the reason for this Thread is to find a definite solution for current users and future users who have run into boot issues cuz they were trying to :
A- Go back to Un-rooted and lock bootloader state.
B- Started Playing with root tools and make a huge mistake
C- Started playing with twrp not knowing what they were doing
D- All the above + started flashing images files and got worts.
E- Any other type of situation.
I Know we make mistakes and we learn from them and well here today we are going to try or rather say Find a permanent /define solution to all this issues with your help, so PLEASE ONLY POST IF YOU HAVE RUN INTO ANY OF THIS ISSUES AND HOW YOU GOT INTO THE ENCHILADA ( MESS ) .
If you have the solution to your previous boot problems send me a PM and I'll keep this Thread updated for everyone to see with your solution and of course credit to the user/s.
NOTE : Please mention which Axon 7 you are using e.g. :
- A2017 (Chinese Variant)
- A2017U (USA Variant)
-A2017G (UK/Europe/International Variant)
reserve 1
reserve 2
reserve 3
reserve solution 4
reserve solution 5
Anyone this issues please post you issue, how to got into the problem, device model and if you got it fix let us know.
https://www.youtube.com/shared?ci=05LD4Ja-h3k
You'd think with all the other posts about problems there'd be something here by now.
Always thank those who are helpful...and just ignore those who aren't.
Mine happened when I wiped Internal storage from twrp. This caused the phone to only see 4gb of internal storage. Came to xda and it was suggested to flash back original boot.img. once that was done 4gb issue was fixed and the radio was gone.
I did indeed try every solution offered (thanks again for all the effort, DrakenFX and others). But, I've come to the conclusion that this is not going to get fixed until XTE releases US images. For other people's sake I hope I am wrong, but I myself decided to proceed with the exchange where I bought it, as I was right at the end of my 14 days (newegg doesn't seem to give the 30 days that xte does). I may be out of an Axon 7 for a while, so for now I am on my amazon ads, Blu R1 HD (with ads defeated
Is there a guide to go back to stock for the A2017G?
i'm on B02 with root and the bootloader still locked.
Like to go back to stock now that ZTE is working on an update to give the A2017G an unlocked bootloader.
Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A03");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!
aPexalpha said:
Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A03");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!
Click to expand...
Click to collapse
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++
I am was rooting my axon a2017 on b10 chinnese version without any backup after rooting got password screen after boot then i was do factory reset and format data and all looking good but after that i saw that i dont have google play app so i installed macro gapps 6.0 after flashing phone stuck on axon screen (after zte logo) for long time i been wait up to 30 minutes and nothing was done..also i have the message on twrp about the modification(dont understand why i have this message all the time) i saw in xda forum that need to install supersu so i search on internet and was flash super su 2.65 and then when i am was boot device go to zte logo screen and then turning off when i connect the device as mtp device named as a2017u (whats worng with it??? I was flashed b10 root boot.img)
I regret about this root and want to back all to stock without any problems need help from someone
I need stock b10 boot.img if someone can upload
Many thanks!
---------- Post added at 04:23 AM ---------- Previous post was at 04:11 AM ----------
DrakenFX said:
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++
Click to expand...
Click to collapse
Its will help me too i think
Dear All,
ZTE Axon 7 A2017 (Chinese version) Stuck on Bootloader mode.
Device after power on will Stuck on ZTE logo even power button press longer also will Off and came back to square one and the only way to power off is via selection on bootloader page via volume button which consists of Recovery mode, Power Off, Bootloader and some other mode which I can't recall.
History of this issue. Please bear with long story.
Manage to install MM ROM with B13 via sd card installation via update software in phone setting. follow by Unlocked bootloader and Install TWRP 3.1.1.0 then try few different ROM until one day when I use Xiaomi flashtool my PC crash half way through during flashing resulting in device with Pure Chinese ROM and TWRP also got corrupted, when I said corrupted because I install TWRP 3.1.1.0 but when I go to Recovery mode it shows TWRP 3.0 something. with this corrupted TWRP when I try to install ROM it will show loading but end result is NIL meaning same ROM nothing change.
Until this stage I never did a TWRP backup because all this while the ROM is Not my type of ROM from this junction when I boot back to TWRP and I did Advance Wipe most of it except external sd card thinking that I may be able to install fresh TWRP but my Recovery TWRP is residing in phone storage resulting in No more TWRP recovery software. next thing I did was I connect phone to PC and ran adb fastboot tool to detect device and managed to detect device in recovery mode and I make decision to Locked back the bootloader and did just that and Locked bootloader is Succes and it also Erased everything during the process.
To cut short the story after Locked back bootloader only Bootloader mode is accessible and when I connect to PC and enable Recovery mode (Black screen) and EDL mode (Black screen) from Windows PC Device Manager COM port able to see Qualcomm 9008 for this 2 mode.
I must admit after few days of trying to resolve this Stuck Bootloader issue I almost give up.
Then I remember this Woodo magic by jcadduno which recommends XM flashtool version 2016.08.30.0 but unable to flash after trying few version Xiaomi flashtool and the very latest and I mean from Xiaomi Flashtool webpage http://xiaomiflashtool.com/
version 20170425 that break the ice and finally able to load A2017U ROM because this US ROM my phone No Network detected.
From here onwards I unlocked bootloader and install back TWRP (Installation of TWRP via Axon7toolkit) because of Network issue since I got TWRP I install back A2017 ROM but still Not satisfied because Chinese ROM certain Apps having issue because of Google services and I chance upon this Conversion A2017 to A2017U ROM (Hybrid ROM caused ROM is US and Modem from Chinese Modem)
that I'm stay put right now and my phone now is A2017U model.
I hope this experience can help others with similar Stuck bootloader and those who wish to convert A2017 to A2017U ROM.
below is the link that I described Woodo magic.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Straight forward Axon7toolkit, please don't use Chrome browser cause Chrome will Automatically Delete it after complete download for my case I used Microsoft Edge.
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
below is the link to Hybrid ROM for A2017U
https://androidfilehost.com/?fid=457095661767154458 by Michael Warner After flash install No verity patch for the bootloader.
Cheers.
I am stuck in a position where I can restore my nandroid backups but get Error 7
when trying to reinstall any Rom on a2017u I was able to fix the unlocked bootloop
by the EDL method. The Rom's are the same as the backups. I think I tried to role back to B29 Causing the bootloop) and have had problems ever since.
Should I try flashing A2017Uv1.1.0B32_Bootstack_by_DrakenFX since the Rooms are all B32?
The B15 and B19 Nandroid's still Restore fine.
Hello all,
i don't get onto forums very often but i thought this was a nice one to add to. i've rooted a few motorolas, a few ztes, a cat; i've also bricked those ztes, cat & a few samsungs. i'm dealing with two Axon7U's; one is factory MM-b29, the other is N-b35.
while screwing around with TWRP, i bricked the b35 (the b29 has been bricked for a month at this time) after i had it almost perfected. by perfected i mean a custom recovery & root user access fully acquired. with DrakenFX's {YOURS; thanks so much. i'm learning to get along with linux} extensive files created to save people from themselves i was able to unbrick the b35. albeit its CELLULAR DATA became unhinged; that's something i could've lived with except it was a loaner and had NO CAMERA! it's camera (along with the ability to push both volume buttons at once for say EDL mode...) was damaged having been beaten across a steering wheel several times. so with my newfound unbricking superpowers i decided to take another crack at the b29. managed to get it unbricked but couldn't get it setup with both TWRP & SuperSU without losing one, the other or, both. at times it didn't even boot up. i was doing pretty much everything cited above for reasons 'why'. best way to learn is by trial & error (if one can afford it).
the b29 is rooted right at this moment; i'm working on it as soon as i leave this posting. i used Axon7_EDL_Tool. i used Axon7root. i used MiFlash. i used Fastboot. I used ADB App Controller software too. back & forth i fought for three days mostly due to downloading glitches and i prevailed. i manipulated a stock OTA full system update.zip by happenstance and it Auto_Updated over itself. in other words it already had the same ROM installed. i don't know what it tested to realize it needed to update to what it already had. it didn't have CELLULAR DATA either. just like the b35, it broke somehow while flashing TWRP or SuperSU. funny thing is it still wanted to update that same ROM after it did. while perusing the system update setting(s) i noticed it had downloaded N-b15 and it wanted to update b29 AGAIN! i opted for the Nougat update. it did alright and appears to have fixed it's CELLULAR DATA too. i haven't looked at it since but i'm confident i can gain root user access with a minimal amount of effort.
The main problem i've had with dealing with bricked devices is the age of the file downloads. most of them are simply GONE!, expired links and whatnot. if i'd had a clear path say from a custom recovery and rooted boot image of my factory version or the path that leads to it, i'd have been fixed up long ago. i've found partial 'paths' if you will that almost get me there but no quite all the way. flashing images & zips through fastboot are different from their counterparts entered through TWRP or Emergency Download Mode which of course are both different too. three different ways to get into one's phone makes it almost impossible to keep them perfected.
i'm not sure i did what i'm supposed to regarding this thread. Thank you DrakenFX for your time & knowledge; you've saved my old Axon7!
Hello all update;
b35 Nougat phone is retired. b29 managed to update itself to b35 7.1.1. however, its CELLULAR DATA is still broken. i haven't managed to figure out how or where it's broken so i cannot fix it.
what i'm trying to do now is flash Magisk instead of SuperSU and using a TWRP version 3.0.3-1. heck i've used all of TWRP's versions in my efforts to reacquire CELLULAR DATA.
crazy part is the phone knows its CELLULAR DATA carrier and freely displays all of its hookup info. this is very frustrating.
Hello,
In a late-night act of utter stupidity, when over-tired, I re-flashed the boot recovery with TWRP and bricked my M3. It obviously can't now enter boot recovery.
I've used TWRP and successfully re-flashed custom roms on my original Mate, and changed regions. (Not in any way an expert, I know how to follow instructions.)
I was trying to convert my Chinese (I was living there) ROM to UK. It's tricky nowadays.
This was a stupid error when tired. Any way back?
I read somewhere that people with the right hardware can do it, but finding someone. I'm in Leeds, UK.
The pad does (did) what I need, and I'm not in a position to buy a new one. If it's dead, it's dead; and I can move on.
Cheers in advance for any input.
SOLVED
See my last post on this thread.
After using Multi Tool V8 to enquire into the machine I switched off and rebooted.
It came back with a "Wipe cache" and "Reset to factory settings" Huawei screen, so I did both and - It booted!
It had spectacularly failed to do anything but boot-loop since coming out of a very dead battery yesterday.
1) Boot recovery, OTA recovery, and dload recovery from SD were all unavailable after the original overwriting of the bootloader.
2) After being dead for months, all recovery options booted from power button plus vol- Vol+ and Vol+/- - but still bootlooping.
Then, suddenly it booted into wipe cache/factory reset screen.
Android 7, EMUI 5.1.3
I have no idea why.
Now fully working. (Including restarting)
I fell in a similar situation after having flashed a magisk module .. unfortunately my nandroid backup didn't restore my devices, but I was able to enter in twrp recovery.. so,..
if you can boot in twrp recovery, not all hopes are lost..
first of all, you must download a stock firmware for your device (i suggest to download trough huawei firmware finder: https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/amp/)
You must download a fullota version of stock firmware
then, you can flash this firmware (3 zip files) trough hurupdater via twrp recovery: https://forum.xda-developers.com/ho...lash-official-firmware-recovery-t3769279/amp/
in order to not overwrite twrp recovery, put the twrp.img file in the same folder and rename it to recovery.img
you can find more info in this topic (follow the instructions, in particular those on how to use hurupdater): https://forum.xda-developers.com/me...ting-btv-dl09-to-unapproved-firmware-t3817541
in order to find a firmware suitable to your device, try to find info on it: you have a mediapad m3 European? American? asian? just wifi or also 4G-LTE (whit a sim and phone functions)? lite or normal version? 10 inches or 8.4?
everyone of these devices have different codenames and suitable firmwares
I found exact firmware for my devices with the procedure described here:
https://forum.xda-developers.com/showpost.php?p=77241673&postcount=3
.. but, if you flashed a wrong firmware, i really don't know if it might help you..
anyway, i wish the info above could help you.
qllkevuoi said:
I fell in a similar situation after having flashed a magisk module .. unfortunately my nandroid backup didn't restore my devices, but I was able to enter in twrp recovery.. so,..
if you can boot in twrp recovery, not all hopes are lost..
first of all, you must download a stock firmware for your device (i suggest to download trough huawei firmware finder: https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/amp/)
You must download a fullota version of stock firmware
then, you can flash this firmware (3 zip files) trough hurupdater via twrp recovery: https://forum.xda-developers.com/ho...lash-official-firmware-recovery-t3769279/amp/
in order to not overwrite twrp recovery, put the twrp.img file in the same folder and rename it to recovery.img
you can find more info in this topic (follow the instructions, in particular those on how to use hurupdater): https://forum.xda-developers.com/me...ting-btv-dl09-to-unapproved-firmware-t3817541
in order to find a firmware suitable to your device, try to find info on it: you have a mediapad m3 European? American? asian? just wifi or also 4G-LTE (whit a sim and phone functions)? lite or normal version? 10 inches or 8.4?
everyone of these devices have different codenames and suitable firmwares
I found exact firmware for my devices with the procedure described here:
https://forum.xda-developers.com/showpost.php?p=77241673&postcount=3
.. but, if you flashed a wrong firmware, i really don't know if it might help you..
anyway, i wish the info above could help you.
Click to expand...
Click to collapse
Thanks for the reply, and sorry for the delay. New child has somewhat taken over our lives!
I'll take a look at the tablet again when I have time, probably next month.
Update - Bootloader working after battery drain: Now what?
[Edit] Post redundant as it started working - see OP.
NwotNot said:
Thanks for the reply, and sorry for the delay. New child has somewhat taken over our lives!
I'll take a look at the tablet again when I have time, probably next month.
Click to expand...
Click to collapse
Well...
After being without power for so long I turned the tablet on and it booted!
However, it then went into OTA and updated - rebooted - and locked the damned bootloader.
1) It's showing as rooted.
2) Boot loader is locked.
3) Fastboot & rescue mode comes up.
4) Recovery (OTA) still comes up but "Fails" this time.
I don't recall how I unlocked it last time. I don't ever rememebr an unlock code.
Status:
Fastboot reports it exists.
ADB reports "Null" not found. (ADB drivers installed).
Firmware version: CPN-AL00C233B078
Device name: CPN-AL00
Serial Number: Showing
IMEI: Showing
Bootloader state: LOCK
I have an old TWRP backup - don't know how to use it.
Solutions?
a) Any kind devs prepared to work with me and find the boot unlocker code for this 5-year old tablet?
b) Any other solutions now we know what's what?
I'm self employed without income in this pandemic and can't really afford to buy a new tablet. If I have to, it won't be Huawei.
(There's a T3 10.6" at £89, but I'm not biting - I need to sort out a budget tablet with at least the oomph of the M3.)
Any help much appreciated. :good:
David.