Database Develop

HTC One - Couldn't Install on USB Storage or SD Card

Hi there!
I received my HTC One two days ago and I am unable to install any PAID apps on the phone. I am able to install free apps without an issue though.
I have searched all over the internet and found two possible solutions, which don't work. These solutions were:
Unmount the SD card. Install app, remount the SD card. This won't work as the HTC One does not have an SD card
In the secure/asec folder, find and delete "smdl2tmp1.asec". Although I found the folder, it was empty and therefore I was unable to delete the file.
I have also completely wiped my phone twice already. I checked the Kernel and Firmware version and it's all up to date. Below are screenshots of the device info.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Finally, I also realized, only after I paid for the device, it's a Dev device. I don't know if this makes any difference though.
The bootloader is unlocked and the device has been rooted. I have full access over the file system.

Make a nandroid and flash another rom to see if that fixes it.

You're using an old custom ROM! Flash any new ROM of your choice from the dev section and it should fix the problem. The issue is within the kernel.
StephanBotha said:
Hi there!
I received my HTC One two days ago and I am unable to install any PAID apps on the phone. I am able to install free apps without an issue though.
I have searched all over the internet and found two possible solutions, which don't work. These solutions were:
Unmount the SD card. Install app, remount the SD card. This won't work as the HTC One does not have an SD card
In the secure/asec folder, find and delete "smdl2tmp1.asec". Although I found the folder, it was empty and therefore I was unable to delete the file.
I have also completely wiped my phone twice already. I checked the Kernel and Firmware version and it's all up to date. Below are screenshots of the device info.
Finally, I also realized, only after I paid for the device, it's a Dev device. I don't know if this makes any difference though.
The bootloader is unlocked and the device has been rooted. I have full access over the file system.
Click to expand...
Click to collapse

Hi,
I'm having a similar problem to the OP. I have a GPE HTC One which is rooted and S-Off. I just updated the software from 4.4 to 4.4.2, at which point the inability to update or install paid apps appeared. As in the original post, I can't find the smdl2tmp1.asec. In fact, my entire mnt/secure folder is empty, as is mnt/asec. I also don't have a .android_secure folder, as has been mentioned in other posts. If I restore to a previous backup running 4.4, everything works fine. The issue is only with installs or updates from the Play Store, because I am able to install the apps from my Titanium backups just fine, but when I do, I get the same error message when I try to update them.
Thanks

roman1984 said:
Hi,
I'm having a similar problem to the OP. I have a GPE HTC One which is rooted and S-Off. I just updated the software from 4.4 to 4.4.2, at which point the inability to update or install paid apps appeared. As in the original post, I can't find the smdl2tmp1.asec. In fact, my entire mnt/secure folder is empty, as is mnt/asec. I also don't have a .android_secure folder, as has been mentioned in other posts. If I restore to a previous backup running 4.4, everything works fine. The issue is only with installs or updates from the Play Store, because I am able to install the apps from my Titanium backups just fine, but when I do, I get the same error message when I try to update them.
Thanks
Click to expand...
Click to collapse
Hi,
I have this exact same issue. Nothing in secure folder etc. From 4.4 to 4.4.2 via OTA.

roman1984 said:
Hi,
I'm having a similar problem to the OP. I have a GPE HTC One which is rooted and S-Off. I just updated the software from 4.4 to 4.4.2, at which point the inability to update or install paid apps appeared. As in the original post, I can't find the smdl2tmp1.asec. In fact, my entire mnt/secure folder is empty, as is mnt/asec. I also don't have a .android_secure folder, as has been mentioned in other posts. If I restore to a previous backup running 4.4, everything works fine. The issue is only with installs or updates from the Play Store, because I am able to install the apps from my Titanium backups just fine, but when I do, I get the same error message when I try to update them.
Thanks
Click to expand...
Click to collapse
The only fix for this is to install Android Revolution ROM. At least, that's the only way I could fix mine :crying:

You should always use stock recovery for OTA updates. This problem is probably due to applying the OTA with a custom recovery.

BenPope said:
You should always use stock recovery for OTA updates. This problem is probably due to applying the OTA with a custom recovery.
Click to expand...
Click to collapse
That's unfortunate, since I like twrp. To reinstall stock recovery, do I just flash the image like I did with twrp?

Yes. You can put TWRP back on after the OTA is on.

BenPope said:
Yes. You can put TWRP back on after the OTA is on.
Click to expand...
Click to collapse
Thanks, that did the trick. Going back and forth between recoveries like that is a little annoying, but fortunately it's relatively quick, so it's not horrible.

roman1984 said:
Thanks, that did the trick. Going back and forth between recoveries like that is a little annoying, but fortunately it's relatively quick, so it's not horrible.
Click to expand...
Click to collapse
Did you have to go back to TWRP and reinstall the GPe ROM? Or did you just have to flash TWRP and it started working again?

DyingBlade said:
Did you have to go back to TWRP and reinstall the GPe ROM? Or did you just have to flash TWRP and it started working again?
Click to expand...
Click to collapse
Once I was able to update using the stock recovery, all I had to do was flash TWRP and everything worked fine (no need to reinstall the GPE ROM since that was already running).

[NAE ROM] Got WIFI and DATA working

resresize piok here is exactly what i did to make Stock rooted NAE Rom working with DATA and WIFI
(I USED ODIN 3 TO FLASH PHILZ RECOVERY TAR)
FULL WIPE
NEED TO BE ON MK2
flash MK2 STOCK ROOTED
FOR SOME REASON IT ONLY WORKS WHEN I FLASH TRI FORCE ROM...
INSTALL TRI FORCE ROM 5.4 WITH CURRENT PHILZ TOUCH RECOVERY
LET IT BOOT
AS SOON AS IT DOES REBOOT INTO RECOVERY
INSTALL NAE ROM...NO WIPE...REBOOT SYSTEM....IT SHOULD GET STUCK AT SPRINT BOOT ANIM....ALL GOOD....NOW....
REBOOT TO DOWNLOAD MODE
FLASH NAE MODEM (FIRMWARE) UNCHECK AUTO REBOOT AND F. RESET
AFTER IT SAYS PASS....REBOOT PHONE USING POWER BUTTON....
SHOULD SAY ANDROID IS UPGRADING ...OPTIMIZING APPS .....ONCE ITS DONE.. UR GOOD
POSTED SCREEN SHOT
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Which bootloader are you on? MF9, MJA, MK2?
Sent from my Nexus 5 using Tapatalk

MK2
optimummind said:
Which bootloader are you on? MF9, MJA, MK2?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
MK2

deeja303y said:
MK2
Click to expand...
Click to collapse
How can I tell which bootloader I have?

You can use an app like Root Checker or Phone Info from the Playstore.

does this knox void?

legasus233 said:
How can I tell which bootloader I have?
Click to expand...
Click to collapse
You can do that from terminal emulator by entering this command getprop ro.bootloader
Sent from my SPH-L720 using Tapatalk

SayWhat10 said:
does this knox void?
Click to expand...
Click to collapse
Flashing the custom recovery will trip KNOX.

This method worked for me on the MF9 bootloader.
Wifi and data (LTE at least) are working.
Only thing is that I'm constantly getting a "Sprint ID stopped working" popup notification.
Update:
Apparently factory reset/wipe data breaks wifi

That's not good

samjam keep us posted. Were you able to get wifi restored?
Data connection still holding?

samjam91 said:
This method worked for me on the MF9 bootloader.
Wifi and data (LTE at least) are working.
Only thing is that I'm constantly getting a "Sprint ID stopped working" popup notification.
Update:
Apparently factory reset/wipe data breaks wifi
Click to expand...
Click to collapse
Turns out wifi wasn't working because my router was on the fritz. I kept getting force closes using the NAE rom from Uknownforce after I restored with TiBu, so I had to flash back to MK2, at least until a newer NAE rom comes out. Still on NAE firmware with MF9 bootloader. Everything is working fine for now.

dumb question
samjam91 said:
Turns out wifi wasn't working because my router was on the fritz. I kept getting force closes using the NAE rom from Uknownforce after I restored with TiBu, so I had to flash back to MK2, at least until a newer NAE rom comes out. Still on NAE firmware with MF9 bootloader. Everything is working fine for now.
Click to expand...
Click to collapse
Anyway I can tell what my current bootloader is ? I am lost and I realize this is a dumb q just lost my wifi is not working i see all these fixes but of course lost ...

kujanme said:
Anyway I can tell what my current bootloader is ? I am lost and I realize this is a dumb q just lost my wifi is not working i see all these fixes but of course lost ...
Click to expand...
Click to collapse
Either in an adb shell or terminal emulator, type this:
Code:
getprop ro.bootloader
It should then return your current bootloader. If it's MJA/MK2/NAE you CANNOT downgrade it, because of KNOX.

[Q] ATT Update to 5.0.1 fails, confirming a solution

It has been over a year since I last flashed a S4A phone, so refreshing my notes and hoping someone can confirm the bits below are correct.
In case another, shorter way to accomplish same exists, kindly suggest it.
Background first.
Phone is SG4 Active, running Android 4.4.2. Baseband I537UCUCNH3, model is Samsung SGH I537, Build KOT49H.I537UCUCNH3
Phone is unlocked and was flashed with Odin one year ago to 4.3 and then ATT updated automatically to current version.
Status today.
When ATT offers download and install the 900 plus MB 5.0.1 update, it fails at 27 percent, reboots phone, repeatedly.
Phone has about 8 GB free space on internal memory and about 10 GB on SD card. As far as I can determine, no special mods have been done to phone and I have uninstalled all user installed apps so it has only ATT, Samsung and Google apps.
Proposed solution.
Found the original I537UCUBML2 bundle *2gb* (Android 4.3) with BL,AP,CSC,CP and I think that since Bootloader already installed, it should be possible to run Odin again and just flash AP,CSC and CP.
Once flashed the system will be back to 4.3 and the OTA updates should work, first to 4.4 and later to 5.0.1.
Can not recall right now just how to do the Odin flash but will use search to figure it out but is my thinking correct or am I missing something important ? For example, don't remember if I have to reboot phone first or if Odin handles it all once the USB cable is connected.
Thank you.

xdafly said:
It has been over a year since I last flashed a S4A phone, so refreshing my notes and hoping someone can confirm the bits below are correct.
In case another, shorter way to accomplish same exists, kindly suggest it.
Background first.
Phone is SG4 Active, running Android 4.4.2. Baseband I537UCUCNH3, model is Samsung SGH I537, Build KOT49H.I537UCUCNH3
Phone is unlocked and was flashed with Odin one year ago to 4.3 and then ATT updated automatically to current version.
Status today.
When ATT offers download and install the 900 plus MB 5.0.1 update, it fails at 27 percent, reboots phone, repeatedly.
Phone has about 8 GB free space on internal memory and about 10 GB on SD card. As far as I can determine, no special mods have been done to phone and I have uninstalled all user installed apps so it has only ATT, Samsung and Google apps.
Proposed solution.
Found the original I537UCUBML2 bundle *2gb* (Android 4.3) with BL,AP,CSC,CP and I think that since Bootloader already installed, it should be possible to run Odin again and just flash AP,CSC and CP.
Once flashed the system will be back to 4.3 and the OTA updates should work, first to 4.4 and later to 5.0.1.
Can not recall right now just how to do the Odin flash but will use search to figure it out but is my thinking correct or am I missing something important ? For example, don't remember if I have to reboot phone first or if Odin handles it all once the USB cable is connected.
Thank you.
Click to expand...
Click to collapse
ML2 won't help you. If you give me about 5-10 minutes I'll link you to the file you need (I'm slow because I'm on mobile and it's a tiny screen for my fat fingers lol)
---------- Post added at 02:43 PM ---------- Previous post was at 02:37 PM ----------
OK here is the file you need. Download and save it to your EXTERNAL SD card (internal storage won't work) and flash the file in stock recovery. You can boot to recovery by shutting the phone off, then holding down power and vol+simultaneously
If you want to be rooted, don't do this, I can point you to a different method

Ok, downloading. Now, in case this "manual method" also fails at 27 percent and just reboots with Install failed, what then ? That was the original reason I proposed to use Odin re-flash the SG4A back to some semblance of original state. Thank you.

xdafly said:
Ok, downloading. Now, in case this "manual method" also fails at 27 percent and just reboots with Install failed, what then ? That was the original reason I proposed to use Odin re-flash the SG4A back to some semblance of original state. Thank you.
Click to expand...
Click to collapse
Use Odin to restore NE3 kit kat instead of ML2. I can link to that too if you need
NE3 kit kat
You have to extract all 4 tar files and flash all 4 with Odin simultaneously

xdafly said:
Ok, downloading. Now, in case this "manual method" also fails at 27 percent and just reboots with Install failed, what then ? That was the original reason I proposed to use Odin re-flash the SG4A back to some semblance of original state. Thank you.
Click to expand...
Click to collapse
The reason your install is failing is because you've modified the stock firmware. When you try to install an AT&T update, manually or automatically there is a script in that update that checks all the files on your phone to ensure that they are the original, unmodified files. If any single one of them is not original or modified, then the update will fail as you have experienced. So if you root your phone you are modifying system files. Even if you unroot, the system files were still modified at one point and the update will fail. I suspect you've done something like this.
The only way you can update to stock OC6 (5.0.1) is to flash your phone back to stock firmware and in your case it should be NE3. As has been explained you will need to flash the NE3 Odin package, but beware this will completely wipe your phone so backup anything you don't want to lose. There is a method for updating your phone without flashing back to stock described in this thread. Also, if you're ever looking for information on rooting and updating your phone it would be a good idea to familiarize yourself with the links in the i537 Firmware Guide.

Use Odin to restore NE3 kit kat instead of ML2.
Click to expand...
Click to collapse
Got it. Downloading (as suspected, the update.zip failed) and will hook up cable and run Odin 3.09 with all 4 files
All important data is backed up to Google so unless I lose some ATT settings, such as the IMEI code or similar, all should be well
Does the phone have to be in recovery mode before starting Odin ? Can't remember now and all Youtube videos show only AP being applied, not all 4 files simultaneously.
Edit, read http://www.samsungodindownload.com/odin-tutorial/
Thank you

BL file to bootloader (BL), CP file to phone (CP), CSC file to CSC, like below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

AT&T 4G/LTE not working after flashing stock boot.img

Hi everyone, proud new owner of a Blu R1 HD here. I've been loving the phone ever since I got it. I flashed TWRP, installed the latest version of systemless root and xposed and was a happy camper. But I stupidly wanted more and started messing around with Magisk and trying to get that to work. I didn't back up my stock boot.img like I was supposed to, so after some failed attempts at installing Magisk (and its new MagiskSU) and some bad attempts at uninstalling SuperSU I just flashed the stock boot.img to the device over via fastboot. I then reflashed the latest versions of SuperSU and Xposed, but for whatever reason, my 4G data won't connect at all. I didn't touch any of the settings and I definitely know it isn't a carrier or plan issue. Does flashing the stock boot.img mess with stuff like this? I'm not all that acquainted with this stuff aside from basic flashing and Rom stuff, so I don't really know what could be going on. Literally everything is working just fine except my data... Any ideas? Thanks in advance!

tiduscrying said:
Hi everyone, proud new owner of a Blu R1 HD here. I've been loving the phone ever since I got it. I flashed TWRP, installed the latest version of systemless root and xposed and was a happy camper. But I stupidly wanted more and started messing around with Magisk and trying to get that to work. I didn't back up my stock boot.img like I was supposed to, so after some failed attempts at installing Magisk (and its new MagiskSU) and some bad attempts at uninstalling SuperSU I just flashed the stock boot.img to the device over via fastboot. I then reflashed the latest versions of SuperSU and Xposed, but for whatever reason, my 4G data won't connect at all. I didn't touch any of the settings and I definitely know it isn't a carrier or plan issue. Does flashing the stock boot.img mess with stuff like this? I'm not all that acquainted with this stuff aside from basic flashing and Rom stuff, so I don't really know what could be going on. Literally everything is working just fine except my data... Any ideas? Thanks in advance!
Click to expand...
Click to collapse
What boot.img did you flash? You didn't back up yours.
Amazon version and oem should have been the same ,(blu only released one version of source) but v7.4.2 and v17 both updated the configuration to include band 12 and volte. So if you are on older version of rom and flashed newer boot , maybe thats the reason.

mrmazak said:
What boot.img did you flash? You didn't back up yours.
Amazon version and oem should have been the same ,(blu only released one version of source) but v7.4.2 and v17 both updated the configuration to include band 12 and volte. So if you are on older version of rom and flashed newer boot , maybe thats the reason.
Click to expand...
Click to collapse
My phone came out of the box with version 6.1, so i was able to flash the modified stock update from here that updates the phone from 6.1 all the way to 7.4.2. I took the boot.img from the vanilla 6.1 prime update and flashed it, so that is probably what the issue is. I assume the next step would be to flash the boot.img from the 7.4.2 version, but I can't seem to find a normal version of the v.7.4.2 update that I can just take the boot.img from (unless I can take it from one of these flashable zips?). If it helps, here is a screenshot of my system info which has all the version numbers and whatnot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: Okay, so I flashed the boot.img from a slightly modified zip of the 7.4.2 update (from here) and thankfully, everything is working fine now. 4G LTE is working swimmingly and I feel like a moron. Lesson learned. Kids, make your backups!

Well, now here is another weird issue. The 4G LTE data is working perfectly fine and speedy as ever, but MMS messages are not being received or sent for whatever reason now. I've already manually entered the correct APN settings and reset them as well to no avail. Any suggestions on this? I've also tried some other SMS apps (such as Pulse) and cleared Messenger's cache and data settings, but that all seems like it did nothing.
Edit: Well, I just flashed the modified 7.4.2 rom that's from the Rom's section of the Blu R1 HD board and MMS is working again. Looks like something other than the boot.img was messed up or something. I did a dirty flash so luckily my roms are in tact.
Edit 2: Sigh, I have no idea what's happening. MMS keeps getting screwey whenever I even start playing around with Xposed (more specifically, Gravity Box). I have no idea why this is happening now all of the sudden. A few days ago before I messed with Magisk, Gravity Box wasn't messing with my MMS messages (at least... I don't think it was...).

[GUIDE] How to Officially Unlock Z2L Z00RD - ZE500KG Bootloader

I'm not responsible for any damage on your phone. Do it at your own risk. Don't come angry or get mad at me, because I'll totally ignore them. I'm just trying to help, if you think this is dangerous for your phone or not worth it, please do back down.
If my thread here is a duplicate, then please feel free to report it so it would be brought down.
I don't own this device, It was my friends device, and I just messed around with it because he bootlooped the phone by doing things without understanding'em. After getting frustrated over and over, suddenly an idea dawned inside my head to do 'what you're about to do' to your phone. This thread here is just to help other ZE500KG users that are as frustrated as I am (was). I didn't find any guide to unlock the ZE500KG here so I decided to do one. If anyone wants to redo this guide, feel free to do it! I'm just here to help even if with very limited knowledge and resources.
First of all, before reading or doing this guide, I'd like to give you a small note, I WON'T BE GIVING LINKS OF THE FILES ITSELF, please search them yourself, you've got google and the threads here (another reason why I'm not giving you links of the files is because my external HDD got corrupted and I lost nearly every file there is for the Z00RD). Plus I did this unlocking like 8-6 months ago, in frustration, so I've forgotten lots of things about the Z00RD.
Now I'd like to explain whats about to happen:
As you guys might know, the only official bootloader unlocking is only available for the Z00ED. What you are about to do is tricking the Z00RD as if it was Z00ED by flashing the Z00ED's stock recovery and flashing stock rom of Z00ED to Z00RD (I hope some users can automatically get the idea of what to do after reading this). After it boots just download the official unlock tool for Z00ED and unlock it. How is this possible? Currently Z00RD (ZE500KG) & Z00ED (ZE500KL) are siblings. They're using the same hardware inside, the only difference is in the camera and modem. So theoretically we can flash ROMs of Z00ED to Z00RD.
Prerequisites:
First of all, please download the respective stock recoveries of Z00ED as per current OS version. Search for them. There is a link somewhere in the forums, just try searching for it. If you're on Lollipop, download the LP stock recovery of Z00ED (ZE500KL) and if you're on Marshmallow download the MM stock recovery Z00ED. Technically this it's just upgrading to latest stock MM ROM.
Download the final stock rom for Z00ED in ASUS's Official Website
Download the official unlock tool for Z00ED that is in the ASUS Official Website too
Optional:
Download stock recovery and stock ROM of ZE500KG and after the unlocking process is finished try reverting back to stock ROM with stock recovery of ZE500KG <- Just incase you are afraid something will go wrong and don't know how to edit build.prop-s to change your device type.
MOST IMPORTANT IS THAT YOU UNDERSTAND & KNOW HOW TO USE ADB & FASTBOOT COMMANDS! I won't be helping you with this, because I'm pretty sure if you're here on XDA, it means you've done some research and pretty much have the knowledge to use the commands.
Okay lets get started:
Move the downloaded stock rom of Z00ED to your phone (I forgot if it has to be renamed and forgot if it has to be in internal or can be put to external) or you could just skip this and later on uise ADB commands to sideload the file.
Boot to fastboot mode / bootloader
Flash the stock recovery via fastboot
Boot to stock recovery that can be done via fastboot command 'fastboot boot' or manually doing it (I forgot the combinations, I'm pretty sure you guys have this covered)
Once it boots to recovery, install the stock rom of Z00ED that has been downloaded (I'd prefer using adb sideload, but it's up to you guys)
You don't have to wipe data, because if you're on MM the data will stay, if you came from LP, it'll be migrated.
Reboot the device and after it wait until it finishes booting (If you're lucky nothing would go wrong in this step)
After it finishes booting, just install the official unlock bootloader app that you've downloaded, open the app and follow the instructions.
Voila device will reboot and you've (somehow) officially unlocked the bootloader of ZE500KG! You're free to flash custom recoveries, custom roms and blablabla without any restriction!
This last step is optional:
If you're planning on sticking with stock ROM, I suggest you to revert back to ZE500KG stock ROM. I don't know if this is a must or optional, but for safety measures I did this to my friends phone.
Notes:
If you've tried rooting this phone via hotbooting a custom kernel (boot.img) that you've found in the threads here (Sorry if I'm not mentioning any names here) and have the fastboot error in every reboot, this will fix it, but if you plan on sticking with stock rom, you won't be able to flash SuperSU in it, because the su binaries will be occupied. On the other hand, MagiskSU works flawlessly.
If somehow this guide doesn't work for you, Try to do other things, or flash other stock recoveries of different stock rom releases of Z00ED. At least you've got the idea on how it works.
If nothing works for you, maybe you're just unlucky, because as usual, ASUS ships different variants of it's phone that may prove to be incompatible with my guide.
There you go! Happy unlocking! Sorry if my post was semi "TL : DR" or I don't reply your posts ASAP, I'm not always online on XDA. Just try your luck and give it a shot! Trial and error is bound to happen when you're dealing with Android phones. Good luck!

Lucky enough my friend sent me some screenies. If this isn't enough, I'll ask him to make a video to see his unlocked status and device type.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

How to Officially Unlock Z2L Z00RD - ZE500KG Bootloader
Need Help
Please Contact

Shafkat said:
How to Officially Unlock Z2L Z00RD - ZE500KG Bootloader
Need Help
Please Contact
Click to expand...
Click to collapse
It's all in the first post friend, just read the guide slowly and enjoy the process.