Posted this as well over on the official Asus site, but I've always found XDA to be full of great answers (& awesome devs) so posting here as well. Okay, so my fault for being impatient to wait for the gradual OTAs but now here's the problem. I rooted the phone and unlocked the bootloader, then installed TWRP for recovery. I backed up my phone. Then I tried to install (flash) new ROMs, starting with some official ones from the ASUS website, then branching out to Lineage, CM, Ressurection, Dirty Unicorns, and uh, something else, don't remember. Anyway, nothing works. I cannot install from SD card, from phone, or from ADB sideload. Nor can I now restore my backup.
ALL ROMs give me errors, I took screenshots of some recent attempts all saying zip signature verification error, lots of other ones indicating the wrong ROM. I researched that error, don't remember exactly what it said, but the workarounds posted were to unzip the ROMs and edit a file, deleting the part that checks for the right version. I can understand if a third party ROM has this problem, but ALL the ROMs - even the ones downloaded directly from Asus?!? No, I think there is another problem here though I could be wrong. Trying to restore my backup gives me either MD5 failed to match or Extracktarfork() Error 255.
So now the system partition is wiped and so nothing will boot at all. The one silver lining is that I CAN still boot into TWRP recovery. Another issue which may or may not be related is that (Just before the system partition got wiped during another attempted ROM flash) I lost the ability to write anything to the external SD card. The contents were readable but I could not write anything to it at all. I would chalk all my ROM problems up to a screwy SD card except that ADB sideloading didn't work either so ... I don't know what to do here. Any help or suggestions would be appreciated.
If you need any additional info, just ask - I probably just forgot to put it in the post. Just in case, I am working with a Asus Zenfone Selfie, ZD551KL, Z00UD, Android WW, 32G internal, 3G RAM. Oh, one last thing, probably just a bum cord but sometimes especially now ADB in windows doesn't see anything & I have to use linux.
Was originally hoping to get the latest Android N installed - Lineage/CM, but at this point I would gladly just go back to the stock ROM if I could finally get it to work. Thank you all again for reading my question & for any help or suggestions you can offer.
EDIT: The more info the better the help, right? I removed the SD card- trying to retrieve my info from it. I can view, just not copy (or write) so using a data recovery program to copy my files off, then I will try to reformat it. Anyway, I tried sideloading and installing from both CM and official Asus zips so I could post the errors - & they have changed a bit. Sideloading remains the same: CM gets to around 50% then stops with the line "Total xfer: 1.00x". The Asus ROM never starts. It gives the error "cannot read ..." but checked it with 7zip and it says there are no errors. On the phone side, obviously nothing on the Asus ROM since it never even starts, but the CM says "assert failed: ....", then gives an ERROR: 7. Copying the files to internal storage & trying to flash them from there, Asus ROM says Zip signature verification failed. Then "Unable to mount storage". CM says assert failed, ERROR: 7, & Unable to mount storage. Hope that helps!
EDIT2: Also tried the suggestion of deleting the asserts part of the ROM, but it says "Invalid zip file format". Any ideas on what the proper zip file format would be? If you open up 7zip as a program there are some options there, what would I need to do differently?
Did you fix your problem cause I fix mine my device can boot to fast boot mode if you
Did you fix your problem cause I fix mine my device can boot to fast boot mode if yours can I will send you the original recovery boot manger then download the latest firmware from the official webpage the go to bootloader and update the file it will work for sure but now have a software touch problems I tried to change theme and enable gloves mode it worked fine for a little time
Same issue..
Hey Lobstercat,
I am having the same problem as you..
I have tried TWRP (format /cache, /dalvik, /system and /data) with an unlock bootloader from an Asus Selfie. I have made a backup of it before trying the above. TWRP was able to restore the UL-Z00T-WW-1.12.40.382 OS fine.
But when install through TWRP, on UL-Z00T-WW-1.13.40.661-user.zip, it gives up on authentication, of which I also turned off with the same result.
In sideload mode it failed with the following message;
sudo adb sideload UL-Z00T-WW-1.13.40.661-user.zip serving: 'UL-Z00T-WW-1.13.40.661-user.zip' (~79%) E: fota_return_code 408
I have also tried "sudo fastboot flash system system.img" it failed, with the message "system.img was too large" this rendered my device unbootable and TWRP cannot restore the backup grrr..
I have the latest fastboot and adb from google went through the same above procedure with the same result, TWRP terminal shows files which I cannot be deleted with rm -rf command
I need to update with the OTA updates to UL-Z00T-WW-1.15 from Asus first before moving over to LOS.
Lobstercat said:
Posted this as well over on the official Asus site, but I've always found XDA to be full of great answers (& awesome devs) so posting here as well. Okay, so my fault for being impatient to wait for the gradual OTAs but now here's the problem. I rooted the phone and unlocked the bootloader, then installed TWRP for recovery. I backed up my phone. Then I tried to install (flash) new ROMs, starting with some official ones from the ASUS website, then branching out to Lineage, CM, Ressurection, Dirty Unicorns, and uh, something else, don't remember. Anyway, nothing works. I cannot install from SD card, from phone, or from ADB sideload. Nor can I now restore my backup.
ALL ROMs give me errors, I took screenshots of some recent attempts all saying zip signature verification error, lots of other ones indicating the wrong ROM. I researched that error, don't remember exactly what it said, but the workarounds posted were to unzip the ROMs and edit a file, deleting the part that checks for the right version. I can understand if a third party ROM has this problem, but ALL the ROMs - even the ones downloaded directly from Asus?!? No, I think there is another problem here though I could be wrong. Trying to restore my backup gives me either MD5 failed to match or Extracktarfork() Error 255.
So now the system partition is wiped and so nothing will boot at all. The one silver lining is that I CAN still boot into TWRP recovery. Another issue which may or may not be related is that (Just before the system partition got wiped during another attempted ROM flash) I lost the ability to write anything to the external SD card. The contents were readable but I could not write anything to it at all. I would chalk all my ROM problems up to a screwy SD card except that ADB sideloading didn't work either so ... I don't know what to do here. Any help or suggestions would be appreciated.
If you need any additional info, just ask - I probably just forgot to put it in the post. Just in case, I am working with a Asus Zenfone Selfie, ZD551KL, Z00UD, Android WW, 32G internal, 3G RAM. Oh, one last thing, probably just a bum cord but sometimes especially now ADB in windows doesn't see anything & I have to use linux.
Was originally hoping to get the latest Android N installed - Lineage/CM, but at this point I would gladly just go back to the stock ROM if I could finally get it to work. Thank you all again for reading my question & for any help or suggestions you can offer.
EDIT: The more info the better the help, right? I removed the SD card- trying to retrieve my info from it. I can view, just not copy (or write) so using a data recovery program to copy my files off, then I will try to reformat it. Anyway, I tried sideloading and installing from both CM and official Asus zips so I could post the errors - & they have changed a bit. Sideloading remains the same: CM gets to around 50% then stops with the line "Total xfer: 1.00x". The Asus ROM never starts. It gives the error "cannot read ..." but checked it with 7zip and it says there are no errors. On the phone side, obviously nothing on the Asus ROM since it never even starts, but the CM says "assert failed: ....", then gives an ERROR: 7. Copying the files to internal storage & trying to flash them from there, Asus ROM says Zip signature verification failed. Then "Unable to mount storage". CM says assert failed, ERROR: 7, & Unable to mount storage. Hope that helps!
EDIT2: Also tried the suggestion of deleting the asserts part of the ROM, but it says "Invalid zip file format". Any ideas on what the proper zip file format would be? If you open up 7zip as a program there are some options there, what would I need to do differently?
Click to expand...
Click to collapse
Resolved..
I was able to sort it out through this link.
https://forum.xda-developers.com/zenfone-2-laser/orig-development/rom-cyanogenmod-13-0-t3317515
"In order to update your firmware to MM one you can either flash ASUS MM rom in stock recovery or flash a package that will update your fw which you can download right here"
Download that link, sideload it with no issues and lineage OS 14 with no issues.
Now running Lineage OS 14. Damn its quick!
Getting failed to mount'/persist'(invalid argument) while flashing custom rom lineage
Lobstercat said:
Posted this as well over on the official Asus site, but I've always found XDA to be full of great answers (& awesome devs) so posting here as well. Okay, so my fault for being impatient to wait for the gradual OTAs but now here's the problem. I rooted the phone and unlocked the bootloader, then installed TWRP for recovery. I backed up my phone. Then I tried to install (flash) new ROMs, starting with some official ones from the ASUS website, then branching out to Lineage, CM, Ressurection, Dirty Unicorns, and uh, something else, don't remember. Anyway, nothing works. I cannot install from SD card, from phone, or from ADB sideload. Nor can I now restore my backup.
ALL ROMs give me errors, I took screenshots of some recent attempts all saying zip signature verification error, lots of other ones indicating the wrong ROM. I researched that error, don't remember exactly what it said, but the workarounds posted were to unzip the ROMs and edit a file, deleting the part that checks for the right version. I can understand if a third party ROM has this problem, but ALL the ROMs - even the ones downloaded directly from Asus?!? No, I think there is another problem here though I could be wrong. Trying to restore my backup gives me either MD5 failed to match or Extracktarfork() Error 255.
So now the system partition is wiped and so nothing will boot at all. The one silver lining is that I CAN still boot into TWRP recovery. Another issue which may or may not be related is that (Just before the system partition got wiped during another attempted ROM flash) I lost the ability to write anything to the external SD card. The contents were readable but I could not write anything to it at all. I would chalk all my ROM problems up to a screwy SD card except that ADB sideloading didn't work either so ... I don't know what to do here. Any help or suggestions would be appreciated.
If you need any additional info, just ask - I probably just forgot to put it in the post. Just in case, I am working with a Asus Zenfone Selfie, ZD551KL, Z00UD, Android WW, 32G internal, 3G RAM. Oh, one last thing, probably just a bum cord but sometimes especially now ADB in windows doesn't see anything & I have to use linux.
Was originally hoping to get the latest Android N installed - Lineage/CM, but at this point I would gladly just go back to the stock ROM if I could finally get it to work. Thank you all again for reading my question & for any help or suggestions you can offer.
EDIT: The more info the better the help, right? I removed the SD card- trying to retrieve my info from it. I can view, just not copy (or write) so using a data recovery program to copy my files off, then I will try to reformat it. Anyway, I tried sideloading and installing from both CM and official Asus zips so I could post the errors - & they have changed a bit. Sideloading remains the same: CM gets to around 50% then stops with the line "Total xfer: 1.00x". The Asus ROM never starts. It gives the error "cannot read ..." but checked it with 7zip and it says there are no errors. On the phone side, obviously nothing on the Asus ROM since it never even starts, but the CM says "assert failed: ....", then gives an ERROR: 7. Copying the files to internal storage & trying to flash them from there, Asus ROM says Zip signature verification failed. Then "Unable to mount storage". CM says assert failed, ERROR: 7, & Unable to mount storage. Hope that helps!
EDIT2: Also tried the suggestion of deleting the asserts part of the ROM, but it says "Invalid zip file format". Any ideas on what the proper zip file format would be? If you open up 7zip as a program there are some options there, what would I need to do differently?
Click to expand...
Click to collapse
I am on latest version of TWRP have done all the process
unlocked bootloader
Rooted my phone
On latest version of TWRP
Official lineage os 14.1
But all time getting failed to mount'/persist'(invalid argument)
Even not able to go back to stock recovery through back2stock.zip process
currently operating my phone through restoring backup
What I need to do please anybody have any solution of this please reply thanks in advance
Jayants susner said:
I am on latest version of TWRP have done all the process
unlocked bootloader
Rooted my phone
On latest version of TWRP
Official lineage os 14.1
But all time getting failed to mount'/persist'(invalid argument)
Even not able to go back to stock recovery through back2stock.zip process
currently operating my phone through restoring backup
What I need to do please anybody have any solution of this please reply thanks in advance
Click to expand...
Click to collapse
Excuses excuses, but bottom line just don't get around to things very fast very often. Did you ever figure it out? It was a long time ago now so I assume you did....
Related
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.
Hi, first post here so please be kind - I really need your help.
SITUATION:
I unlocked the bootloader using the tool provided under the utilities section of ASUS support page. Then, I successfully rooted my phone using one of many exploits contained in KingoRoot. Root Checker app said that root was ok, and I rebooted my phone. Something in the process caused my phone to soft brick, probably KingoRoot messed up the partition table. My phone is now stuck at Asus logo when trying to turn it on.
I can access recovery and fastboot. I also flashed TWRP recovery 2.8.5.0 (no success flashing newer versions) that is capable to put my phone in ADB sideload. I wiped cache, dalvik, data multiple times. Factory reset. Tried to update system using almost every firmware zip that ASUS support page lists (WW) through recovery and through ADB sideload unsuccessfully. Stock recovery is unable to access my SD card (since after the fatal reboot - unable to mount E: ecc, I tried three different cards), while the custom one is able to but gives me error when trying to run zip files. There are a plenty of details that I could give, but my conclusion after 24 hours of forum headaches is that the partition table is messed up.
I came across an utility called Asus Flash Tool that may fix my problem, but it only accepts .raw firmware files and I am unable to find one for my A500KL. There's a folder for it in an old rapidgator link but it's empty now, no luck contacting the original uploader (many others have the same problem). I read through every related thread here on XDA and on many other forums (even in Chinese and Russian), this is my last resort. There's anyone willing to share such .raw image? I read that it can be built out of a functional phone, can someone help me?
Hello,
i bought my Axon this week from Amazon Warehouse.
My problem is, that im not able to update my ROM.
I tried OTA, Install over Recovery (SD-Card), Install over Recovery (ADB Sideload).
All methods failed..
OTA is downloading the update, rebooting and than crashing. Hard to tell why, because i dont see any error logs. Just the information "Update Failed".
Next method i tried was to install over SD-Card. I downloaded the Update from ZTE, moved to my SD and tried to update. But my Smartphone always tells me "Couldn't mount /sdcard".. I tried to Format it with extFAT and FAT32 but both failed.
The last method I tried was using the ADB Sideload. I tried it with the update file, and also with the STOCK-Rom from this site: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547. But also i get an error message.. ADB tellst me "Total xfer 0.00x"...
Have i bougth a bricked Axon? Can I update somehow to the new version?
I have the option to send it back to Amazon, but it was 100€ cheaper, so i would love to fix the problem.
Kind regards,
t4ggno
Recovery stock and SD card seem to be the most reliable method.
Did you check the md5 of the zip? Also update.zip to put on root of the SD card should be the final zip, not the zip that contains another zip.
Also when booting in Android, I assume your SD is recognized, isn't it?
If so, instead of going to recovery then update from SD card, you can try to update from inside Android, from Phone settings, then Update item.
The phone should indicate the current version and the version to be updated to. Then follow the phone indication to update.
Nope, i dont checked MD5. But shouldn't be the problen. I tried many different update files, always same error.
Yes, after booting the SD card is connected and i could use it. Just the recovery mode cant mount the card.
Also the updater recognize my update. But he just boot in the recovery mode and try to update -> Same error: "couldn't mount /sdcard"
Edit 1:
But i can check the MD5 files if necessary. I just need the "correct" MD5 value to compare.
Just a guess:
Is your micro SD card size greater than or equal to 128 GB? Some version has this bug, size less than or equal to 64 GB should work better. To try if this is the case.
t4ggno said:
Hello,
i bought my Axon this week from Amazon Warehouse.
My problem is, that im not able to update my ROM.
I tried OTA, Install over Recovery (SD-Card), Install over Recovery (ADB Sideload).
All methods failed..
OTA is downloading the update, rebooting and than crashing. Hard to tell why, because i dont see any error logs. Just the information "Update Failed".
Next method i tried was to install over SD-Card. I downloaded the Update from ZTE, moved to my SD and tried to update. But my Smartphone always tells me "Couldn't mount /sdcard".. I tried to Format it with extFAT and FAT32 but both failed.
The last method I tried was using the ADB Sideload. I tried it with the update file, and also with the STOCK-Rom from this site: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547. But also i get an error message.. ADB tellst me "Total xfer 0.00x"...
Have i bougth a bricked Axon? Can I update somehow to the new version?
I have the option to send it back to Amazon, but it was 100€ cheaper, so i would love to fix the problem.
Kind regards,
t4ggno
Click to expand...
Click to collapse
Why are you using an SD card though? Put it in the root of the internal storage and it will surely pop up, then try again from Updates, not the recovery (and get the SD off the phone to avoid the phone from detecting the zip there)
Otherwise root and get TWRP and flash Tron1's stuff
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
t4ggno said:
Hello,
i bought my Axon this week from Amazon Warehouse.
My problem is, that im not able to update my ROM.
I tried OTA, Install over Recovery (SD-Card), Install over Recovery (ADB Sideload).
All methods failed..
OTA is downloading the update, rebooting and than crashing. Hard to tell why, because i dont see any error logs. Just the information "Update Failed".
Next method i tried was to install over SD-Card. I downloaded the Update from ZTE, moved to my SD and tried to update. But my Smartphone always tells me "Couldn't mount /sdcard".. I tried to Format it with extFAT and FAT32 but both failed.
The last method I tried was using the ADB Sideload. I tried it with the update file, and also with the STOCK-Rom from this site: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547. But also i get an error message.. ADB tellst me "Total xfer 0.00x"...
Have i bougth a bricked Axon? Can I update somehow to the new version?
I have the option to send it back to Amazon, but it was 100€ cheaper, so i would love to fix the problem.
Kind regards,
t4ggno
Click to expand...
Click to collapse
Also, bricked means totally unusable, so no it isn't bricked lol
dnlilas said:
Just a guess:
Is your micro SD card size greater than or equal to 128 GB? Some version has this bug, size less than or equal to 64 GB should work better. To try if this is the case.
Click to expand...
Click to collapse
Its a 64 GB card Should i try a <= 32 GB card? Could be I have some lying around. Just to be sure its not a special case.
I will test it tomorrow if i found one
Choose an username... said:
Why are you using an SD card though? Put it in the root of the internal storage and it will surely pop up, then try again from Updates, not the recovery (and get the SD off the phone to avoid the phone from detecting the zip there)
Otherwise root and get TWRP and flash Tron1's stuff
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
Also, bricked means totally unusable, so no it isn't bricked lol
Click to expand...
Click to collapse
Hm, last time it only recognize the update file on my SD card. I will try it tomorrow again and will post the result.
TWRP isnt a option, because i dont want to lose my warranty. Also i read that TWRP can be incompatible with Stock-ROM?!
t4ggno said:
Hm, last time it only recognize the update file on my SD card. I will try it tomorrow again and will post the result.
TWRP isnt a option, because i dont want to lose my warranty. Also i read that TWRP can be incompatible with Stock-ROM?!
Click to expand...
Click to collapse
I don't know where you read that, but the closest answer that I can give you is: if you don't install SuperSU, Magisk, or the dm-verity patch, TWRP will get replaced with the stock recovery and you'll have to flash it again (~2 minutes anyways). But it is in no way incompatible. Also you can relock and stuff, but yeah better keep the warranty at least until you're sure that your phone is good.
You unpacked the zip that you downloaded right? to get the update.zip inside? Or did you download it from raysteff's thread? It should work anyways
Another thing: What is your phone's model (G, U, chinese) and what is the update that you're trying to install? I guess it will fail if it is from another model, and if you're trying to jump fron a very old MM build to a very new N build it will probably fail too. Keep that in mind.
First, what is the version of your device?
I'm guessing you are using a chinese device with modified rom. Those units can't install updates unless you first restore to original chinese rom.
Choose an username... said:
I don't know where you read that, but the closest answer that I can give you is: if you don't install SuperSU, Magisk, or the dm-verity patch, TWRP will get replaced with the stock recovery and you'll have to flash it again (~2 minutes anyways). But it is in no way incompatible. Also you can relock and stuff, but yeah better keep the warranty at least until you're sure that your phone is good.
You unpacked the zip that you downloaded right? to get the update.zip inside? Or did you download it from raysteff's thread? It should work anyways
Another thing: What is your phone's model (G, U, chinese) and what is the update that you're trying to install? I guess it will fail if it is from another model, and if you're trying to jump fron a very old MM build to a very new N build it will probably fail too. Keep that in mind.
Click to expand...
Click to collapse
I didnt unpacked the folder. A recovery normally installs zip files?! The zip file isn't packed twice. The zip contains the files directly.
I tried the package A2017G-MM-B11 and A2017G-N-B01 from the link I posted, also i tried the oficiell patch files from the axon website (B10 and Nougat)
otaconremo said:
First, what is the version of your device?
I'm guessing you are using a chinese device with modified rom. Those units can't install updates unless you first restore to original chinese rom.
Click to expand...
Click to collapse
I have a A2017G (that information i found on the back of my phone).
My phone overview tells me:
Modelnumber: ZTE A201G
Build-Number: ZTE A2017GV1.0.0B08
Android-Version: 6.0.1
Security-Patch: 1. December 2016
I can try to install the B09. Probably this patch is required to go to version 10 (and than to nougat)?
Don't know if it applies to your situation, but when the OTA for 7.x came out, there was a bug that would not allow the update to be applied if there was an SD card installed. I know I had to pull my card to get the update to take. Might try running the OTA without the card installed and see if it works.
karlkarloff said:
Don't know if it applies to your situation, but when the OTA for 7.x came out, there was a bug that would not allow the update to be applied if there was an SD card installed. I know I had to pull my card to get the update to take. Might try running the OTA without the card installed and see if it works.
Click to expand...
Click to collapse
I tried it, but doesn't work :/
The update stops at 33% with the error message "Package Mismatch".
t4ggno said:
I didnt unpacked the folder. A recovery normally installs zip files?! The zip file isn't packed twice. The zip contains the files directly.
I can try to install the B09. Probably this patch is required to go to version 10 (and than to nougat)?
Click to expand...
Click to collapse
No, B09 was a patch only for Spain.
The zip you download from the ZTE website has a bunch of numbers as name and has an update.zip inside and a PDF or sth like that. The one you have to flash is the update.zip inside, just sayin'...
If you download the zips from raysteff's thread they are already unpacked.
Try installing an older zip, like B03, then B10
Choose an username... said:
No, B09 was a patch only for Spain.
The zip you download from the ZTE website has a bunch of numbers as name and has an update.zip inside and a PDF or sth like that. The one you have to flash is the update.zip inside, just sayin'...
If you download the zips from raysteff's thread they are already unpacked.
Try installing an older zip, like B03, then B10
Click to expand...
Click to collapse
The big problem still exists -> I cant mount my SD card in recovery mode, so I cant install any patch.
I really want to try B03 as you suggested, but i am unable to install it.
I will search another SD card an try to use it. Probably my SD card has some problems.
Edit: I download my files from these side: http://www.ztemobile.de/support/downloads/?product_id=2100
They dont contain a update.zip. Only many .dat, .bin, .img and .mbn files.
t4ggno said:
The big problem still exists -> I cant mount my SD card in recovery mode, so I cant install any patch.
I really want to try B03 as you suggested, but i am unable to install it.
I will search another SD card an try to use it. Probably my SD card has some problems.
Edit: I download my files from these side: http://www.ztemobile.de/support/downloads/?product_id=2100
They dont contain a update.zip. Only many .dat, .bin, .img and .mbn files.
Click to expand...
Click to collapse
But install it from the internal storage and with thr Updates option on Android itself... You need to put it in the root of the internal storage or it most likely won't find the zip
Choose an username... said:
But install it from the internal storage and with thr Updates option on Android itself... You need to put it in the root of the internal storage or it most likely won't find the zip
Click to expand...
Click to collapse
Thanks! That worked very well. I did a factory reset and moved the update file directly to the root of my internal storage. After that the updater detected my update and I could install the Patch B011. After that i was able to update to Nougat trough OTA. No errors, every worked fine.
otaconremo said:
First, what is the version of your device?
I'm guessing you are using a chinese device with modified rom. Those units can't install updates unless you first restore to original chinese rom.
Click to expand...
Click to collapse
it seems that I got this one with modified rom. is there anyway to get it back to the official chinese rom?
Hello, i decided to open new thread because I nowhere find solution. My problem is that after flashing my moto g2 with omni 6.0.1 it get stuck on warning message (about unlocked bootloader). Now I can only get into bootloader menu, connect phone to PC (it's showing dewice as motorola dadb interface),I can only flash twrp using fastboot (fastboot boot twrp.img) and that's it. I can not flash anything permanently to the phone: any custom recovery, any rom,can't fix it with logofix.It just look like phone doesn't accept any flash. I tried also to change boot and other img but with no succes, always after any operation when I reboot phone it's get to warning message.
My phone is motorola 2G xt1068, 8gb, bootloader ver 48.87. Once I tried to flash it with retail rom from sd card via twrp 3.8.0.1 it shows that previous system was omni-titan 6.0.1 and retaildsdsall can not be flash,always shows error 7.
I wonder if I can flash it with upper version of omni: 7.0.1 to fix the problem with booting the phone.
If You could give me any advise how to solve the problem, I would be very appreciate.
Waitng for your reply Guys.
After a lot of tryes I found that anythig I do on the phone after restart it's getting to the same state, even if I manually deleted folder "Firmware", after reboot it's going back. When I prepared Moto for installing new rom using Philz recovery, all the data stay on it's place ( I mean private data like thumbnails in DCIM folder etc), nothing dissapeared. It's look like it have some copy of the system in internal storage and always after rebooting it's recovering it back, even if the system is flashed by new rom.
Have U any idea what's wrong with this phone?
Additinally I found that a lot of internal memory is busy: over 4500MB and free is only 780MB. Even after wiping everything, also formatting system.Should it be like this?
Edit: 2018-02-15
Ok, if noone could help me let's treat it as a blog.
Digging in google I found spanish site with a lot of custom roms for motorola. Now I'm trying one by one till I found the right one.
It's a pitty that Father's of the omni rom leaving me lonely in that situation, I think that they are the best of source of informations about that rom.
2018.02.19
I tried to install OmniRom 6.0.1 Homemade but on the beginning I had the infothat installation failed with error 7. So I found the solution to change the information in meta-info folder.I did it but when instalation started after "symlinkig" it stopped with error: some symlinks failed, error 7. And again I stucked.I feellike I'm very close of the solution but I need help. I'm using twrp 3.2.1.0 running via fastboot (boot twrp.img).
Hi there,
So I unknowingly did something kinda risky and of course, it backfired. I used the in-system update feature of linage OS to upgrade my version on my Oneplus 6T. Can't exactly remember which one the old version was, but it was at least 4 versions older than the newest nightly one. Afterward, the phone got stuck in a boot loop. Also, in recovery, it can't bind/ mount the system, because there is no file directory. "E:Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory." I tried the following:
- went into recovery, factory reset the device, then flashed new clean lineage os [multiple different versions]. Gets back to boot loop afterward. (note that Fastboot shows no bootloader version or baseband version)
- tried unlocking the bootloader via fastboot flashing unlock. It fails with error code: (remote: Unrecognized command flashing unlock)
- tried copying the contents of slot a to b, in case one was severely outdated as the cause for the soft brick as stated in this guide. Didn't change mentioned issue after flashing os.
- installed Qualcomm USB drivers, to get the PC to detect the phone as a USB device
- after that, tried using the ms-downloader tool to reset and re-flash the phone. It does not get detected and the downloader tool waits for the full 15s before returning the error for no detected device.
- tried unlocking the bootloader itself via fastboot flashing unlock_critical. same error as with normal unlock: (remote: Unrecognized command flashing unlock)
Maybe overwriting the possibly corrupt bootloader would be a good bet, but as mentioned, I cannot unlock the device to make the command for that useable.
Hey, so I am not really knowledgeable enough to help fix this, but I did notice one thing: Why are you using the wiki page from Lineage for the OnePlus 6 (enchilada) instead of the 6t (fajita)?
state_azure said:
Hey, so I am not really knowledgeable enough to help fix this, but I did notice one thing: Why are you using the wiki page from Lineage for the OnePlus 6 (enchilada) instead of the 6t (fajita)?
Click to expand...
Click to collapse
I didn't even notice it was for enchilada, but iirc the file I loaded was only to copy the contents of slot a to slot b. I could search for a fajita version of this. Still, thanks for your reply.
Hi there,
I have the exact same problem. After updating my OP 6T, the cell phone was broken. It's stuck in a reboot loop. Which surprises me, however, because the documentation for this device type recommends that the update be carried out using the system's internal update process. I also noticed that some OTA updates work and some don't. Unfortunately, this is the only way to make use of it very little fun because you never know if the phone is working again when you update. And the security weaknesses show that updates are also important for Lineageos. thanks for the feedback
Zak0r said:
Hi there,
So I unknowingly did something kinda risky and of course, it backfired. I used the in-system update feature of linage OS to upgrade my version on my Oneplus 6T. Can't exactly remember which one the old version was, but it was at least 4 versions older than the newest nightly one. Afterward, the phone got stuck in a boot loop. Also, in recovery, it can't bind/ mount the system, because there is no file directory. "E:Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory." I tried the following:
- went into recovery, factory reset the device, then flashed new clean lineage os [multiple different versions]. Gets back to boot loop afterward. (note that Fastboot shows no bootloader version or baseband version)
- tried unlocking the bootloader via fastboot flashing unlock. It fails with error code: (remote: Unrecognized command flashing unlock)
- tried copying the contents of slot a to b, in case one was severely outdated as the cause for the soft brick as stated in this guide. Didn't change mentioned issue after flashing os.
- installed Qualcomm USB drivers, to get the PC to detect the phone as a USB device
- after that, tried using the ms-downloader tool to reset and re-flash the phone. It does not get detected and the downloader tool waits for the full 15s before returning the error for no detected device.
- tried unlocking the bootloader itself via fastboot flashing unlock_critical. same error as with normal unlock: (remote: Unrecognized command flashing unlock)
Maybe overwriting the possibly corrupt bootloader would be a good bet, but as mentioned, I cannot unlock the device to make the command for that useable.
Click to expand...
Click to collapse
Whatever you do in your device,they will not touch critical partition such as bootloader and many more of it, do u still have twrp or other recovery on your device?
Prinçe çharming ap said:
Whatever you do in your device,they will not touch critical partition such as bootloader and many more of it, do u still have twrp or other recovery on your device?
Click to expand...
Click to collapse
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Zak0r said:
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Click to expand...
Click to collapse
Zak0r said:
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Click to expand...
Click to collapse
Tell me the exact problem you with your phone and maybe i can help
once again,
today got informed via updater that a new update is available. I try do install it, but now i stuck again in recovery. And the only think i can do is a factory reset and everything is lost.
can anybody give an info if it is safe to update the 6T trough OTA? It doesn't look like that.
zero4one said:
once again,
today got informed via updater that a new update is available. I try do install it, but now i stuck again in recovery. And the only think i can do is a factory reset and everything is lost.
can anybody give an info if it is safe to update the 6T trough OTA? It doesn't look like that.
Click to expand...
Click to collapse
Oof, I thought mine only got bricked because I tried to upgrade across 4 versions. It seems as though even normal updates now cause soft bricks, neat.
I tried again today but there seems to be a connection to the error. I had an update pending, which could be installed without any problems. After the restart, I was informed that there was another update, after installing this update there was a total failure again. Could it be that this is somehow related to slot A / B?
zero4one said:
I tried again today but there seems to be a connection to the error. I had an update pending, which could be installed without any problems. After the restart, I was informed that there was another update, after installing this update there was a total failure again. Could it be that this is somehow related to slot A / B?
Click to expand...
Click to collapse
Why don't you try to flash Stock rom on both slots via MSM tool and then just try ota to update to latest build for you specific device
How can i verify if there is an difference between slot a and slot b?
If i flash the stock rom i will be back on oos and that is not what i want i will continue using los, or do we have an idea missmatch there?
thanks for help
zero4one said:
How can i verify if there is an difference between slot a and slot b?
If i flash the stock rom i will be back on oos and that is not what i want i will continue using los, or do we have an idea missmatch there?
thanks for help
Click to expand...
Click to collapse
What do you exactly want ?