Database Develop

new phone need CMW help

Hi all.
just bought a galaxy note for my gf,
running
2.3.6
N7000XXLA4
2.6.35.7-n700ZSLA2-CL899610 [email protected] #2 ???? (no clue)
Gingerbread.ZSLA2
by looking at the forums, it looks complicated compare to my HtC....i just download the rom n put it in my phone n boot cmw.
i tried booting into recovery on this Note, it shows an Android, and (downloading...)
this u need..KIES???ODIN????...
nver had a Samsung Before so...please be nice, and i did search, but some terms i dont get it..so thats y im posting.
my q is, how do i know if my phone is rooted or not,
n how to install cmw?
n whats "CF-Root"???
i want to Upgrade to 4.0.3/4
depending which one is safer.
and i need DioPen Chinese IME.
cuz i need to tpye chinese..and like to use stock n not market.
thanks all

ching1206 said:
n how to install cmw?
n whats "CF-Root"???
i want to Upgrade to 4.0.3/4 depending which one is safer.
and i need DioPen Chinese IME.
cuz i need to tpye chinese..and like to use stock n not market.
thanks all
Click to expand...
Click to collapse
First to check if you have root, you can use the root validator application.
1. If no then you can check this thread for rooting procedures and requirements.
2. CF root is a close to stock kernel with minimal requirements for superuser.
3. Still we have not got the emmc bug removed in stock so a stock ICS kernel is definitely not safe. All CM9 kernels and Kernels like SpeedMod, Notecore have the bug disabled, so they are SAFE.
I don't know chinese related things so i guess i won't be able to give you an answer for your last question.

Akilesh said:
First to check if you have root, you can use the root validator application.
1. If no then you can check this thread for rooting procedures and requirements.
2. CF root is a close to stock kernel with minimal requirements for superuser.
3. Still we have not got the emmc bug removed in stock so a stock ICS kernel is definitely not safe. All CM9 kernels and Kernels like SpeedMod, Notecore have the bug disabled, so they are SAFE.
I don't know chinese related things so i guess i won't be able to give you an answer for your last question.
Click to expand...
Click to collapse
im on LA4 which is not rootable...right?
so i need to downgrade??!
how i do that?

use KIES for download stock firmware samsung ;When connect your smartphone or Tab, Kies you automatically warn of the presence of a
new firmware update improves your smartphone or Tab with the latest available firmware....
{
"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"
}
You do not need to root or unroot the device to update the firmware.
Please ensure that KIES is closed and not running in the system tray! Kies doesn't like Odin, it's like the big brother who's always jealous that his little brother is getting to flash all the phones so he starts to flash block.
Regarding change logs. Samsung thinks firmware should be like a box of chocolates, you never know what you’re gonna get and that all a big part of the surprise user experience program so they don't publish any change logs.
Odin is a tool unofficial,.
The installation of an original firmware via odin does not invalidate the warranty.
The installation of a firmware via odin does not entail the loss of the data inside the phone.
It is recommended in every case to make backups.
Get Odin v3.04 from here: Download here ; https://androidfirmwares.net/Tools/Download/8
Just extract the Odin folder.
You will also need to install the Samsung USB drivers for the device if you haven't installed KIES. Get them from here: https://androidfirmwares.net/Tools/Download/9
Just install like any Windows program.....
Root permissions or root privileges are obtained by performing a process called routing and grant the user the ability to take advantage of specific parts of the operating system, in our case of Android, which would not otherwise be accessible.
Thanks to this process so we can use applications that leverage, more profoundly, the operating system and offer customizations and features in more than a telephone that does not have enabled root permissions. Superuser is an application that is usually included in mod ROM (for example CyanogenMod) is basically manages root permissions by opening a pop-up whenever a application request is made, in such a way as to decide if grants or less allowed to, and lists all the applications for which we have given access to root permissions.
The recovery of an Android phone is a particular feature that you can activate before the boot (i.e. , before the start) of the operating system and allows you to perform a number of specific operations, including: hard reset and firmware upgrade. Let's start by saying that the root is not a "thing" as the jailbreak and not a task to perform. On linux platform is the root administrator user who has the highest privileges in the system (such as the Windows Administrator user to understand each other). The root then you do not get, but instead get its permissions. The root permissions allow you to do anything with your system. Limited only by your imagination. We can access the system files, delete them, edit them, replace them.(root explorer), Change the frequency of the processor , Back up applications (including system) even with their data. Or remove the applications already installed, on the device.(titanium backup), partialroot that is permitted without the recovery and icon superuser with root explorer can not to heave reading/writing in to system / app .
The recovery of an Android phone is a particular feature that you can activate before the boot (i.e. , before the start) of the operating system and allows you to perform a number of specific operations, including: hard reset and firmware upgrade.
The original recovery or stock recovery is the one which is pre-installed on our Android phone at the time of purchase.
The custom recovery is a particular feature that in addition to the operations of the recovery original, allows you to install custom rom firmware (modified) as the CyanogenMod and install various hacks.
READ THIS GUIDE FOR ROOT AND RECOVERY; http://forum.xda-developers.com/showthread.php?t=1424997

You can flash a stock pre-rooted ROM using PC-ODIN from here . This will give you root as well as CWM-recovery.

Akilesh said:
You can flash a stock pre-rooted ROM using PC-ODIN from here . This will give you root as well as CWM-recovery.
Click to expand...
Click to collapse
eh..jusst download Odin, use those 4.0.3 n im done?

You are currently running Gingerbread so you cannot use the ICS files for root.
You have two options
1. Flash a directly rootable stock firmware from here and use this to root the phone.
2. Or flash the pre-rooted one from here.

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

M7 OTA : OTA_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651. 10-6.23.651.7_R_release

Just got the notification for OTA update for m7 .
File name: OTA_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10-6.23.651.7_R_release_452237.zip
Size: 189.61 mb
{
"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"
}
Sprint Website
Download link
I rooted my phone yesterday and dont want to go back to stock for the update. Can someone please help me with a flashable zip which I can use.
cheers

tangojoker said:
Just got the notification for OTA update for m7 .
I rooted my phone yesterday and dont want to go back to stock for the update. Can someone please help me with a flashable zip which I can use.
cheers
Click to expand...
Click to collapse
From my understanding, you should be able to take the OTA, but you need to make sure everything is as stock as possible first. Follow these steps:
0. BACKUP with a nandroid backup
1. Uninstall any apps that changed the /system partition (like xposed).
2. Unroot from the SuperSU app.
3. Flash the stock recovery (easiest way is to flash the latest full firmware).
4. If you are s-on, you may have to relock the bootloader first (I'm s-off, so I'm not sure).
5. Take the OTA.
6. If you are s-on, unlock the bootloader if you locked in step 4.
7. Flash TWRP.
8. Allow TWRP to root the phone (it will ask you if you want to root when you exit the recovery).
You can get the full firmware from this thread. If you wait though, someone might release a flashable stock rooted ROM, but the phone is old, so that may not happen.

Won't this wipe everything?

jy04 said:
Won't this wipe everything?
Click to expand...
Click to collapse
I don't believe so. The OTA typically leaves the /data partition alone. Of course, as always, everything you do to your phone is at your own risk.

coal686 said:
From my understanding, you should be able to take the OTA, but you need to make sure everything is as stock as possible first. Follow these steps:
0. BACKUP with a nandroid backup
1. Uninstall any apps that changed the /system partition (like xposed).
2. Unroot from the SuperSU app.
3. Flash the stock recovery (easiest way is to flash the latest full firmware).
4. If you are s-on, you may have to relock the bootloader first (I'm s-off, so I'm not sure).
5. Take the OTA.
6. If you are s-on, unlock the bootloader if you locked in step 4.
7. Flash TWRP.
8. Allow TWRP to root the phone (it will ask you if you want to root when you exit the recovery).
You can get the full firmware from this thread. If you wait though, someone might release a flashable stock rooted ROM, but the phone is old, so that may not happen.
Click to expand...
Click to collapse
If anyone does take the OTA and wants to send me a TWRP backup, I'd be more then willing to post a stock rooted flashable Rom.
Just throwing it out there, in case there's anyone interested, willing, and able.
Sent from my HTC6535LVW using Tapatalk

This is the second Stagefright patch/update.
There is an issue with the idea of flashing the latest full firmware, as it is not posted on the forum, the latest RUU post is the firmware before the first Stagefright update, I didn't realize this so I flashed stock recovery as that's how I took the first Stagefright patch, the problem with this is in the OTA update installation it identifies your build before installing so you will receive an error: "Package expects build fingerprint of blah blah/499067.10:user" but it will show as "499067.7:user" and abort installation as that is the fingerprint of the most recent firmware available on the forum, and not the most recent as of the first stagefright update. Someone needs to upload or find updated full firmware or maybe just stock recovery before the installation is possible.

So 6.23.651. 10 is not patched for "stagefright"?

Joshlul said:
This is the second Stagefright patch/update.
There is an issue with the idea of flashing the latest full firmware, as it is not posted on the forum, the latest RUU post is the firmware before the first Stagefright update, I didn't realize this so I flashed stock recovery as that's how I took the first Stagefright patch, the problem with this is in the OTA update installation it identifies your build before installing so you will receive an error: "Package expects build fingerprint of blah blah/499067.10:user" but it will show as "499067.7:user" and abort installation as that is the fingerprint of the most recent firmware available on the forum, and not the most recent as of the first stagefright update. Someone needs to upload or find updated full firmware or maybe just stock recovery before the installation is possible.
Click to expand...
Click to collapse
Just updating the firmware to the previous version won't be enough to allow the update to work.
Most OTA updates, unless they are a full Rom update or RUU, contain patch files.
Those patch files will check the MD5 of every single system file before patching each one.
So even if your firmware is current or your build.prop is edited, to pretend like you have the last version, it will still fail when checking the system files it intends on patching.
There is no way to trick an OTA to work.
You have to have the proper system files, for them to patch at all or properly.
So don't waste your time on that...you need the previous stock Rom for the latest OTA to ever apply properly, or at all.
Good luck!!
Sent from my HTC6535LVW using Tapatalk

links broken can anyone post the OTA update zip like ,i'm rooted with twrp recovery with s-on

santod040 said:
If anyone does take the OTA and wants to send me a TWRP backup, I'd be more then willing to post a stock rooted flashable Rom.
Just throwing it out there, in case there's anyone interested, willing, and able.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I created a TWRP backup using the following procedure:
1. Relocked my bootloader
2. Took the RUU (RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10.exe)
3. Unlocked my bootloader
4. Booted into fastboot
5. I tried to run: fastboot boot twrp-2.8.7.0-m7wls.img but that didn't work
6. fastboot flash recovery twrp-2.8.7.0-m7wls.img
7. I booted to recovery.
8. I selected read only
9. Created a backup leaving out the cache.
I'm not sure where to send it or where to post it (1.73GB)

chrishonson said:
I created a TWRP backup using the following procedure:
1. Relocked my bootloader
2. Took the RUU (RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10.exe)
3. Unlocked my bootloader
4. Booted into fastboot
5. I tried to run: fastboot boot twrp-2.8.7.0-m7wls.img but that didn't work
6. fastboot flash recovery twrp-2.8.7.0-m7wls.img
7. I booted to recovery.
8. I selected read only
9. Created a backup leaving out the cache.
I'm not sure where to send it or where to post it (1.73GB)
Click to expand...
Click to collapse
Could upload to Dropbox, Google Drive, Mega, whatever host you prefer.
Then send me a link via PM, or post it here and mention me.
If using Dropbox, a public link could cause too much traffic on your account, if posted publicly.
Feel free to shoot me a PM if you need further guidance on it.
Thanks for your effort, it should benefit a few folks.
Sent from my HTC6535LVW using Tapatalk

I can't post links yet so pm me if anyone wants the link.
The funny thing about this rom is that TWRP didn't root it like i expected it would. It installed SuperSU but "There is no SU binary installed, and SuperSU cannnot install it..."
Maybe I'm missing something.

santod040 said:
Could upload to Dropbox, Google Drive, Mega, whatever host you prefer.
Then send me a link via PM, or post it here and mention me.
If using Dropbox, a public link could cause too much traffic on your account, if posted publicly.
Feel free to shoot me a PM if you need further guidance on it.
Thanks for your effort, it should benefit a few folks.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
having a similar issue. relocked and RUU'd using last release. For some reason my OTA fails. I found some other guidance that said to extract the stock recovery from the OTA and flash it then run the OTA again, but for some reason I can't extract recovery from firmware. If anyone can post it, I'd like give that method a try. Thanks!

yeah so twrp-2.8.7 wasn't able to flash super su binary in a way that would stick. twrp-2.8.6 worked fine. I think may have seen this issue elsewhere.

Stock Nexus 6 (Verizon) will not update!

Hi guys,
As I wrote in the title, my Verizon Nexus 6 will not update. When I get a notification for the software update, I see that it downloads and is ready to restart the phone so it will install the update...
but when I do, it will display the android icon with the word "error" above it. No error number or details about why it did not work.
{
"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"
}
Things I tried already are:
formatting the phone (both through the settings menu as well as the stock bootloader)
deleting data and cache in Google Services Framework (via settings/apps/all apps)
I have more than enough space in my storage; more than 2/3rds of my storage is free space, so I really am having trouble wrapping my head around why this software update is failing to install. And since all the threads and help things I find are for rooted phones, I am having trouble finding something that would offer an answer. I was hoping to keep this phone stock as long as possible, which is an oddity for me because I usually want to root my phone immediately. I guess I just really like this phone as stock. And other than this update that fails to load, the phone has no other issues, other than a few emojis that fail to show, but I feel like that's from the software not being able to update for the 6 months that I've been trying to update it.
Any help with this would be greatly appreciated! Thank you!!

Is your device unlocked? Have you tried to sideload the update?
If your device is unlocked you can use NRT to update without loosing any data.

PickelledEggs said:
Hi guys,
As I wrote in the title, my Verizon Nexus 6 will not update. When I get a notification for the software update, I see that it downloads and is ready to restart the phone so it will install the update...
but when I do, it will display the android icon with the word "error" above it. No error number or details about why it did not work.
Things I tried already are:
formatting the phone (both through the settings menu as well as the stock bootloader)
deleting data and cache in Google Services Framework (via settings/apps/all apps)
I have more than enough space in my storage; more than 2/3rds of my storage is free space, so I really am having trouble wrapping my head around why this software update is failing to install. And since all the threads and help things I find are for rooted phones, I am having trouble finding something that would offer an answer. I was hoping to keep this phone stock as long as possible, which is an oddity for me because I usually want to root my phone immediately. I guess I just really like this phone as stock. And other than this update that fails to load, the phone has no other issues, other than a few emojis that fail to show, but I feel like that's from the software not being able to update for the 6 months that I've been trying to update it.
Any help with this would be greatly appreciated! Thank you!!
Click to expand...
Click to collapse
You might try clearing the cache partition in recovery and reboot. Maybe the next OTA will be install without issues.

lol!
if you made any kind of changes, chances are that any ota will not work. but that's alright, all you have to do is flash the factory image. it would've been updated already if you did that instead of writing out your post. you can grab it here https://developers.google.com/android/nexus/images

simms22 said:
lol!
if you made any kind of changes, chances are that any ota will not work. but that's alright, all you have to do is flash the factory image. it would've been updated already if you did that instead of writing out your post. you can grab it here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I don't think you read my post at all... I didn't make any changes. My phone is fully stock. No root at all. No unlock. No modifications whatsoever The ota Software update just will not work.
gee2012 said:
You might try clearing the cache partition in recovery and reboot. Maybe the next OTA will be install without issues.
Click to expand...
Click to collapse
I tried going in to recovery mode, but when I do, it gives me the same android error icon, but instead of "error" it says "no command"

Timza said:
Is your device unlocked? Have you tried to sideload the update?
If your device is unlocked you can use NRT to update without loosing any data.
Click to expand...
Click to collapse
Nope. Not unlocked. No modification whatsoever

PickelledEggs said:
Nope. Not unlocked. No modification whatsoever
Click to expand...
Click to collapse
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.

PickelledEggs said:
Nope. Not unlocked. No modification whatsoever
Click to expand...
Click to collapse
Best is to enable OEM UNLOCKING and usb debugging in developer options, reboot into fastboot and unlock the bootloader and after the reboot flash the latest MMB29S firmware as @simms22 allready stated. Flash the img`s seperately in fastboot, all i would flash personaly is the system and boot img.

Timza said:
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
Click to expand...
Click to collapse
gee2012 said:
Best is to enable OEM UNLOCKING and usb debugging in developer options, reboot into recovery and unlock the bootloader and after the reboot flash the latest MMB29S firmware as @simms22 allready stated. Flash the img`s seperately in fastboot, all i would flash personaly is the system and boot img.
Click to expand...
Click to collapse
Oh ok, I must have misinterpereted what SImmz was saying, then. I got in to recovery mode and wiped cache finally, so I will see if that works, otherwise I'll try your guys' other suggestions

PickelledEggs said:
Oh ok, I must have misinterpereted what SImmz was saying, then. I got in to recovery mode and wiped cache finally, so I will see if that works, otherwise I'll try your guys' other suggestions
Click to expand...
Click to collapse
I had this issue with my Nexus 7 (stock) - wiped the cache partition in recovery, and waited for OTA to appear again - and it worked.

BTW, you don't need root to make certain changes(I don't know what changes, but I know many don't get ota because of). or google just made it to sensitive.

Timza said:
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
Click to expand...
Click to collapse
You can only sideload OTA`s in stock recovery afaik, not complete images.

gee2012 said:
You can only sideload OTA`s in stock recovery afaik, not complete images.
Click to expand...
Click to collapse
Ah, my mistake. I (wrongly) assumed OTAs were included on that download page.

is using nexus root tool kit let you flash with su 2.5.2 or it using the lastest 2.66? or that makes no difference when flashing stock image?

MikePancake6 said:
is using nexus root tool kit let you flash with su 2.5.2 or it using the lastest 2.66? or that makes no difference when flashing stock image?
Click to expand...
Click to collapse
The latest version of NRT (v2.1.4) uses SuperSU 2.6.6.

Timza said:
The latest version of NRT (v2.1.4) uses SuperSU 2.6.6.
Click to expand...
Click to collapse
is there any way to use 2.5.2, or flashing a custom rom will system root or will it be systemless root anyhow?

MikePancake6 said:
is there any way to use 2.5.2, or flashing a custom rom will system root or will it be systemless root anyhow?
Click to expand...
Click to collapse
After you flash with TWRP (a step with NRT). When you opt to reboot system, you will get a message asking if you would like to install SuperSU. If you swipe to install you will have a "system root". If you opt to not install, you will have a systemless root.
Personally, I have a "system root", and it seems to be working fine, whereas before, I was having an issue with the systemless root.

Timza said:
After you flash with TWRP (a step with NRT). When you opt to reboot system, you will get a message asking if you would like to install SuperSU. If you swipe to install you will have a "system root". If you opt to not install, you will have a systemless root.
Personally, I have a "system root", and it seems to be working fine, whereas before, I was having an issue with the systemless root.
Click to expand...
Click to collapse
ok, thank you for all the help. i already unlocked the bootloader using the tool kit.
tonight i will root it and try a custom rom. maybe chrome or pure nexus project, those seem to be stock with extra options and rro customize.

Thanks guys. I just got around to sideloading the update last night and it's working like a dream.
I'll probably root it soon now. I've been feeling the itch recently... Lol
This (so far) is probably my favorite stock phone though. I might keep it stock for a bit longer
Sent from my Nexus 6 using Tapatalk

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