Database Users

Post Your Current or Last Boot Issues here (READ BEFORE POSTING PLEASE)

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.

Asus Zenfone 5 LTE (T00P - A500KL) - Help with soft brick, need .raw firmware

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?

Asus Zenfone Selfie ZD551KL cannot flash any ROMs or restore recovery. TWRP installed

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....

Bootloop after uninstalling Xposed + Firmware upgrade encountered issue

Hello,
I'm really desperate right now and would highly appreciate your help.
The background is the following:
several months ago I've flashed Cyanogenmod 13 on my Note 3 (N9005) using TWRP (via Odin). The system has been working perfectly. In addition, I was using Xposed (Version 89) without any problems. However I decided to uninstall Xposed today using its uninstaller, but I only got a error message ( I don't remember its content, it was saying something like ' can't rename... /lib'.
Well, I then tried uninstalling via recovery which resulted in a bootloop.
I watched some YT-videos explaining how to bypass Xposed in TWRP, so I went to download mode and tried installing the TWRP with stock_kernel_twrp_1120-signed-for_Odin (the file I used the first time). This step failed. After restarting my phone it's saying: 'Firmware upgrade encountered issue. Please select recovery mode in Kies & try again'.
I don't know what to do now. I simply want to install a working TWRP to save all my files and recover from the bootloop. What matters the most to me is to recover all data on the phone (videos, pictures, files etc. which unfortunately I haven't backed up).
I'm able to access download mode (home/power/volume down) but I don't know what to do to get a recovery/TWRP.
I'm not doing anything right to avoid further harm and wait for your advice. I'd be most grateful if you could help me.
Thanks in advance!
Exupery

exupery09 said:
Hello,
I'm really desperate right now and would highly appreciate your help.
The background is the following:
several months ago I've flashed Cyanogenmod 13 on my Note 3 (N9005) using TWRP (via Odin). The system has been working perfectly. In addition, I was using Xposed (Version 89) without any problems. However I decided to uninstall Xposed today using its uninstaller, but I only got a error message ( I don't remember its content, it was saying something like ' can't rename... /lib'.
Well, I then tried uninstalling via recovery which resulted in a bootloop.
I watched some YT-videos explaining how to bypass Xposed in TWRP, so I went to download mode and tried installing the TWRP with stock_kernel_twrp_1120-signed-for_Odin (the file I used the first time). This step failed. After restarting my phone it's saying: 'Firmware upgrade encountered issue. Please select recovery mode in Kies & try again'.
I don't know what to do now. I simply want to install a working TWRP to save all my files and recover from the bootloop. What matters the most to me is to recover all data on the phone (videos, pictures, files etc. which unfortunately I haven't backed up).
I'm able to access download mode (home/power/volume down) but I don't know what to do to get a recovery/TWRP.
I'm not doing anything right to avoid further harm and wait for your advice. I'd be most grateful if you could help me.
Thanks in advance!
Exupery
Click to expand...
Click to collapse
Flash TWRP 2.8.7.0 via ODIN.
if this works, then backup everything from recovery immediately.
here is the link (if you need).
https://forum.xda-developers.com/ga...ecovery-twrp-materialized-dark-light-t3153589
Now Flash a new kernel. look over here at xda for your need.
then reboot and check. pls have patience if it took long while first boot.
and pls tell if it works.

dark_phoenix said:
Flash TWRP 2.8.7.0 via ODIN.
if this works, then backup everything from recovery immediately.
here is the link (if you need).
https://forum.xda-developers.com/ga...ecovery-twrp-materialized-dark-light-t3153589
Now Flash a new kernel. look over here at xda for your need.
then reboot and check. pls have patience if it took long while first boot.
and pls tell if it works.
Click to expand...
Click to collapse
Thank you very much for your help.
I've just flashed twrp-2.8.7.0-hlte-4.4.img.tar successfully, but when trying to access recovery (volume up/home/power) it's stuck in the Samsung logo saying:
'RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery"
What to do now?
I've found different kernels:
https://forum.xda-developers.com/ga...nt/kernel-idlekernel-leankernel-fork-t3241582
and
https://forum.xda-developers.com/galaxy-note-3/development/temasek-kernel-t3395437
Which should I choose for N9005/Cyanogenmod 13? I have no idea due to lacking knowledge.
[Hlte][Purify][25.02.17][CM13.0]. sounds appropriate to me? Could you please give me an advice? Thank you!

Ok, flashing both twrp-2.8.7.0-ha3g.tar and then twrp-2.8.7.0-hlte-4.4.img.tar resulted in the herein before mentioned problem (stuck on Samsung logo).
I now flashed successfully n9005-cwm-recovery-6.0.4.4 and it's backed up everything.
I then tried uninstalling xposed via recovery with the uninstaller.zip on sdcard, but got this error message:
mv: can't rename '/system/lib/libart.so.o
rig': No such file or directory
E: Error in /data/media/0/Android/data/de.robv.android.xposed.installer/cache/downloads/framework/xposed-uninstaller-20180117-arm.zip
Any ideas how to fix it? Or do you recommend wiping everything and flashing a new ROM (e.g. MagMa NX ROM)?

exupery09 said:
Ok, flashing both twrp-2.8.7.0-ha3g.tar and then twrp-2.8.7.0-hlte-4.4.img.tar resulted in the herein before mentioned problem (stuck on Samsung logo).
I now flashed successfully n9005-cwm-recovery-6.0.4.4 and it's backed up everything.
I then tried uninstalling xposed via recovery with the uninstaller.zip on sdcard, but got this error message:
mv: can't rename '/system/lib/libart.so.o
rig': No such file or directory
E: Error in /data/media/0/Android/data/de.robv.android.xposed.installer/cache/downloads/framework/xposed-uninstaller-20180117-arm.zip
Any ideas how to fix it? Or do you recommend wiping everything and flashing a new ROM (e.g. MagMa NX ROM)?
Click to expand...
Click to collapse
ok.
you backed up your necessary data ?
if YES then go ahead and wipe everything and flash a new rom, which ever you want.
you know what. i am a huge fan of this dev.
here is this his work. awesome rom. give it a go.
https://forum.xda-developers.com/galaxy-note-3/development/rom-aspireteam-c9-pro-v2-0-t3610152
or this one if you don't want touchwiz .
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
---------- Post added at 10:43 AM ---------- Previous post was at 10:27 AM ----------
exupery09 said:
Thank you very much for your help.
I've just flashed twrp-2.8.7.0-hlte-4.4.img.tar successfully, but when trying to access recovery (volume up/home/power) it's stuck in the Samsung logo saying:
'RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery"
What to do now?
I've found different kernels:
https://forum.xda-developers.com/ga...nt/kernel-idlekernel-leankernel-fork-t3241582
and
https://forum.xda-developers.com/galaxy-note-3/development/temasek-kernel-t3395437
Which should I choose for N9005/Cyanogenmod 13? I have no idea due to lacking knowledge.
[Hlte][Purify][25.02.17][CM13.0]. sounds appropriate to me? Could you please give me an advice? Thank you!
Click to expand...
Click to collapse
FOR THIS ONE ....
i think you need to pull battery out just after successfully flashing TWRP 2.8.7.0
when ODIN flashes recovery and says passed. pull out battery immediately. don't let the phone boot/start. wait 10-20 seconds. re-insert battery and try now booting in TWRP.

Please Help With MY SM-T380 (Samsung Galaxy Tab A 8.0 2017)...I'm STUCK. :(

I can boot into Samsung recovery and can boot into Download mode. I have tried factory resetting the tablet. I have tried reflashing the stock image with Odin 3.09 in Download but everything I try just fails. It comes up with a message in stock Samsung Recovery that says:
#REboot Recovery Cause is [[check_boot_mode]RebootRecoveryWith Key]
#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
dm-verity verification failed. . .
E: Failed to clear BCB message: failed to open /dev/block/bootdevic
e/by-name/misc: No such file or directory
Could someone please help me figure out what I need to do. I am familiar with Odin for the most part. I would be FOREVER GRATEFUL! Thank you! :victory:

TWRP to save the day!
obtain stock rom and after flashing with Odin 3b patched also flash twrp and then and using either an external storage sd card or USB otg cable and a flash drive restore them twrp backup available elsewhere on the site , try use samfirm or whatever and go to android file host and search t380 and sort thru it but everything you need is there

mrstuffandthings said:
TWRP to save the day!
obtain stock rom and after flashing with Odin 3b patched also flash twrp and then and using either an external storage sd card or USB otg cable and a flash drive restore them twrp backup available elsewhere on the site , try use samfirm or whatever and go to android file host and search t380 and sort thru it but everything you need is there
Click to expand...
Click to collapse
mine also has the same problem, another problem is my OEM is locked. So I cannot install twrp.

Hello there, I`ve bought a vietnamese Samsung Galaxy Tab A 8.0 2019.
Can I flash the european Rom on it?
Is there maybe twrp to flash and perhaps Custom Rom's?
I wanna use it as a german model.

I am not an informed authority whatsoever but I did have quite a few close calls with my same device and I repeatedly managed to get it going. That must hurt to hear without a clear step by step specific with links instructions I know but let me not mislead you either. What good is that?! Well I can refer you to some of the resources I had luck with , it’s been a few years since too so I will go look and see if I have anything concrete , off the top of my head I want to say thanks to magisk the bootloader never did get unlocked , and I only ran the boot.img thru the app and then had my tarp ready to flash right after, be persistent I must have mangled and recovered over two dozen times here and there and again ambiguous encouragement empty as it is I can say from my experience that more than a few things that worked ended up being very simple but minor factors such as unchecking the auto reboot and flashing the twrp right after , another saving grace came in the form of a few die hard twrp flushable zips that enabled simple functions while in twrp bc I remember I would get as far as twrp and then loose the bootable os until I had reflashed the correct boot from inside twrp and I recall dmverity can be mitigated with a zip flashed inside twrp , now that sounds great but only just the right twrp would allow for this flashing feature at all so again hit and miss , I’ll go look at some of those files and review before I make any specific suggestions which would drive me nuts but if your lucky I was actually just noticing I still had an old custom rom that I had cooked up with one of those command line rom kitchens, so standby for real info but for now off hand …
Androidfilehost.com was a killer source of roms and where I found the working twrp
Back then samfirm was already depreciated but still worked and it was the fastest around but
Samsung firmware download - find All Official Android & Samsung Updates | updato.com
Are you looking for the official Samsung software to download? At updato.com, you'll find the latest Android device updates. Check on your own!
updato.com
Jonny boy , again knowing I don’t really know I want to say your good to go as I flashed all manner of rom from all over but I do remember something about I think the us version that seemed XAR less appealing I think bc it was a little more locked down but you would do well of course to refer to that list of the country codes for the roms obv, and as far as twrp I found mine on that android file host but on that same site was an identical looking version that once inside couldn’t flash or mount things properly , see what the trick was , was once armed with a twrp flashable zip i would wipe everything and include the dmverity disabled and whatever else , the patched boot.img And so if your careful even if you flash the wrong twrp first you can inside still flash that other one and reboot to it , my custom rom is nothing to get interested in all it were was a trimmed down stock , tho I did manage later to get some neat custom boot animations , I’ll check out my old files and return sooner this time
WARNING : I JUST COPY PASTED THIS FROM A SEARCH FOR sm-t380 on androidfilehose but it seems someone has been busy since i...
god mode?
Search Results for "sm-t380" | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
please lmk how things gel, or not
hope i was not all nonsense