Develop Bugs

[Q] Only Root Galaxy Nexus without erasing any data

HI,
I've using my Galaxy Nexus (GSM) for a long time, but i want to get Root access, i've been reading a lot and it seems if i use Galaxy Nexus Toolkit it will delete all my data, there's any way to root it without losing any data?
Thanks a lot! :good: :fingers-crossed:

milerx said:
HI,
I've using my Galaxy Nexus (GSM) for a long time, but i want to get Root access, i've been reading a lot and it seems if i use Galaxy Nexus Toolkit it will delete all my data, there's any way to root it without losing any data?
Thanks a lot! :good: :fingers-crossed:
Click to expand...
Click to collapse
no.
you have to unlock your bootloader (no matter which method you use, also, dont use a toolkit, use the sticky at the top of the forum) which wipes your data. period.

Zepius said:
you have to unlock your bootloader (no matter which method you use, also, dont use a toolkit, use the sticky at the top of the forum) which wipes your data. period.
Click to expand...
Click to collapse
I did a root of my Galaxy Nexus, when I flashed the new 4.1. It did work fine. When the phone did the small update to 4.1.2, can it be true that it rolled back the root? My phone don't seem to be rooted anymore.
Isn't it possible to get root permissions again, without loosing data?

IsonNick said:
I did a root of my Galaxy Nexus, when I flashed the new 4.1. It did work fine. When the phone did the small update to 4.1.2, can it be true that it rolled back the root? My phone don't seem to be rooted anymore.
Isn't it possible to get root permissions again, without loosing data?
Click to expand...
Click to collapse
if your bootloader is unlocked, reflash the supersu.zip
otherwise, you have to unlock the bootloader and it will wipe your device.

Zepius said:
if your bootloader is unlocked, reflash the supersu.zip
Click to expand...
Click to collapse
It should be. Anyway to see that?
(sorry for noob questions)

IsonNick said:
It should be. Anyway to see that?
(sorry for noob questions)
Click to expand...
Click to collapse
if you enter fastboot, it will says "lock status: unlocked"
or you can see if when you first start up your phone if there's a little lock that is unlocked.

Zepius said:
or you can see if when you first start up your phone if there's a little lock that is unlocked.
Click to expand...
Click to collapse
Hep hep! The lock is unlocked. Perfect.
When I receive the 4.2 update (my phone is yakju), I will root again. Thank you for your help, I appreciate it a lot.

Similar thing happened to me. I was messing around with different ROM's for some time but in the end went back to the stock ROM. My phone now shows unlocked and using the stock recovery (as described here http://forums.androidcentral.com/google-samsung-galaxy-nexus/243004-recovery-mode.html).
The stock recovery offers 4 options: reboot, apply update from ADB or USB, wipe.
How do I "reflash the supersu.zip" from here? I want to avoid wiping as everything is set up as I like it now, and because it isn't rooted I can't back it up, catch 22 thing

madsere said:
Similar thing happened to me. I was messing around with different ROM's for some time but in the end went back to the stock ROM. My phone now shows unlocked and using the stock recovery (as described here http://forums.androidcentral.com/google-samsung-galaxy-nexus/243004-recovery-mode.html).
The stock recovery offers 4 options: reboot, apply update from ADB or USB, wipe.
How do I "reflash the supersu.zip" from here? I want to avoid wiping as everything is set up as I like it now, and because it isn't rooted I can't back it up, catch 22 thing
Click to expand...
Click to collapse
Why did you bump a 4 months old thread?
Obviously, you need a custom recovery to flash a non-Google zip...
Sent from my Nexus

bk201doesntexist said:
Why did you bump a 4 months old thread?
Obviously, you need a custom recovery to flash a non-Google zip...
Sent from my Nexus
Click to expand...
Click to collapse
I'm sorry, I didn't know there was a rule against that. I searched Google for the problem and this thread came up closest.
Well sorry if I am not a genius like you who know everything already. I thought that forums like this was for asking questions.
It would be nice if instead of just being mean and nasty you'd offer some constructive suggestions, such as would installing a custom recovery wipe the phone? The distinction between the boot loader and the custom recovery isn't clear to me.

madsere said:
I'm sorry, I didn't know there was a rule against that. I searched Google for the problem and this thread came up closest.
Well sorry if I am not a genius like you who know everything already. I thought that forums like this was for asking questions.
It would be nice if instead of just being mean and nasty you'd offer some constructive suggestions, such as would installing a custom recovery wipe the phone? The distinction between the boot loader and the custom recovery isn't clear to me.
Click to expand...
Click to collapse
Yeah?
Then it would be nice if you read the stickies.
Sent from my Nexus

madsere said:
I'm sorry, I didn't know there was a rule against that. I searched Google for the problem and this thread came up closest.
Well sorry if I am not a genius like you who know everything already. I thought that forums like this was for asking questions.
It would be nice if instead of just being mean and nasty you'd offer some constructive suggestions, such as would installing a custom recovery wipe the phone? The distinction between the boot loader and the custom recovery isn't clear to me.
Click to expand...
Click to collapse
Sarcastic, aren't we? Look, XDA is first and foremost a developer site for developers to develop. Answering and asking questions about that development is only incidental. Members are expected to have read the rules of XDA and to follow them. That includes not bumping old threads, but it also includes an expectation that you will read the information readily available to you. Seeing the same common questions get asked daily, when there are good guides made specifically for this purpose, gets very old very fast. The constructive suggestion is to search and read. Guides abound both in the stickies and elsewhere, and the fact that you haven't found answers to your fairly common questions tells me that you either haven't made an effort to look, or you just don't understand and therefore probably shouldn't be messing with your phone.

I was able to root my gnex without wiping the data!
I dont know how it happened, but it happened, I was surprised too because I was really frustrated couldn't root it even after 10-15 tries ( I am a big time noob) and suddenly I unlocked the boot loader and rooted the phone without any loss of data, actually I was rooting because I had the VM100U something memory issue and my phone was terribly slow! I was surprised becasue i was expecting to copy all my files and crap one by one but now I have no issues

[Q] noob - 2.20?

How do I know if my phone is 2.20?
I can't seem to find anywhere in my "about" section anything that has these numbers... or even 1.85...
*edit* Found it! I'm on 3.18. Now with that being said, I have been searching and searching on how to root for 3.18. I have found several threads where a user will ask if it's do able yet and they get flamed with "it's been asked a thousand times, search!' or "look in the forums"... Well I am a complete noob and I can't find it... please point me in the right direction??????

Your first wrong decision was to put this thread in the general section.
Now I'll give you some clues what to do, and you shouldn't ask anything else as it will be really easy for you to google it and find out all the details:
1) Unlock your phone at htcdev.com (careful, it will wipe out all your data and there's no another way to do it);
2) Flash a clockworkmod recovery for One X via fastboot flash recovery filename.img;
3) Flash a supersu package via recovery;
4) Enjoy your root privileges.
I underlined keywords to look for in google.

Adiost said:
Your first wrong decision was to put this thread in the general section.
Now I'll give you some clues what to do, and you shouldn't ask anything else as it will be really easy for you to google it and find out all the details:
1) Unlock your phone at htcdev.com (careful, it will wipe out all your data and there's no another way to do it);
2) Flash a clockworkmod recovery for One X via fastboot flash recovery filename.img;
3) Flash a supersu package via recovery;
4) Enjoy your root privileges.
I underlined keywords to look for in google.
Click to expand...
Click to collapse
Thank you x1000!!! I got so overwhelmed very quickly with all the "experts" out there and I could not find the right material. The two techniques I tried failed and I didn't want to brick my phone because I didn't know what I was doing...
Thank you again!!!!

bugzeem6s said:
Thank you x1000!!! I got so overwhelmed very quickly with all the "experts" out there and I could not find the right material. The two techniques I tried failed and I didn't want to brick my phone because I didn't know what I was doing...
Thank you again!!!!
Click to expand...
Click to collapse
It's pretty hard to brick a hox, There is almost always a solution, read carefully but don't worry too much

I'm really starting to think this isn't meant to be... When I go to install Android SDK on my computer it says to extract the file straight to C:\ and then I "should" have a folder named C:\Android, well, I don't. Kept re trying and re trying, nothing.... Then I go to ask a question and I get the infamous I cannot page because I have less than 10 posts... Think I am going to give it up... Oh well...
windows 8...

bugzeem6s said:
I'm really starting to think this isn't meant to be... When I go to install Android SDK on my computer it says to extract the file straight to C:\ and then I "should" have a folder named C:\Android, well, I don't. Kept re trying and re trying, nothing.... Then I go to ask a question and I get the infamous I cannot page because I have less than 10 posts... Think I am going to give it up... Oh well...
windows 8...
Click to expand...
Click to collapse
I was pretty certain uderlining fastboot.
http://www.4shared.com/zip/j9DPgqkY/FastbootADB.html
This is all the tools you'll ever need on your PC. There are two of them, including fastboot.exe. No need to install the whole Android SDK.

error code 160 MID not allowed
i also got error code 141 could not generate result

another thing... my phone is 4 days old...

bugzeem6s said:
another thing... my phone is 4 days old...
Click to expand...
Click to collapse
https://www.google.de/url?sa=t&rct=...=0H-OBcV12hM_MACsirhxXQ&bvm=bv.50500085,d.ZWU
use this tutorial man..you could try to search on your own...it helps often you know?
http://forum.xda-developers.com/showthread.php?t=1583801 or this here

Try searching for the all in one toolkit for Hox.
Does the trick without the headache.
Sent from my HTC One X using xda app-developers app

I've tried the all in one, i've tried many tutorials, i've searched and searched and searched and searched... Nothing but circles... I'm thinking it's the phone...

did both of the windows 8 tutorial and... NOTHING!!! so d**n pissed right now!!

http://forum.xda-developers.com/showthread.php?t=2069904
[HOW TO] Unlock bootloader, Root, Flash Custom ROM, Flash Kernel And More!
Don't forget to enable USB debugging in your current ROM or else fastboot will not work. And install HTC drivers, but I assume you already did that.
Sent from my HTC One X using xda app-developers app

please delete this thread

bugzeem6s said:
please delete this thread
Click to expand...
Click to collapse
Did you succeed?
Sent from my HTC One X using xda app-developers app

nope. not wasting anymore time on it... error after error.

[Q] HELP!! Have I bricked my new device!? SO WORRIED!!

Hey guys,
I'm kinda new to the HTC/Android world, found this community a damn good place to find support.. But now I've hit a road block.
Basically, I've been eager to root from day 1 of getting my first htc handset, I came across from jailbreak and loved the fact of customizability with Android.
So I had the Google play edition(I think, all geared towards Google) running Kit Kat 4.4.4. Love it, big Google user so this all tied together lovely.
Here is the Situation.
I found a video on youtube, cannot provide URL as I'm in work at the moment, but it was root guide from scratch. Fresh windows OS, seemingly a phone fresh out the box.. you get the idea.
I used the Hasoon2000 tool to root the device. Installed ADB etc on my pc, signed up as a a dev, got the Key for device, sent in and received my .bin file. I got up to actually rooting my device, well pleased and happy. Using TWRP via Hasoon2000.
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Queried this on another forum, decided to continue to be patient... but no replies, in the mean time I restored my apps and have a fiddle, see what the root function can do for myself.
I installed "Freedom 1.0.6" and a program called "Market Share"- Hate iAP, some games are ridiculously priced for the smallest of things, I just wanted to sandbox plague inc. ;(
Now the device is stuck in a boot loop, phone starts up, see the home screen for a bout 40 seconds/ one minute.. Some times I unlock the device and it goes back to flash screen then.. others I boot an app and its slides away once more.
This happened close to 15x before I left for work this morning and I imagine its just going to repeat this and run the battery - I tried to stop this loop by going into TWRP and possibly choosing to boot system this way may of stopped it.. but when I was on the boot screen with those options.. It said Tampered at top of screen and S-On- which has scared me quite a bit..
What the hell has happened!?
I'm desperate to know and don't want to have this damn thing bricked! Please help.. try explain like I'm 5, as said I'm new to a lot of this! >.<

first off, if the screen comes on, its not bricked.
esenfur said:
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Click to expand...
Click to collapse
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.

redpoint73 said:
first off, if the screen comes on, its not bricked.
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
Click to expand...
Click to collapse
Thank you for fast response.
Official OTA - being that the phone its self said "Update the OS" - I just accepted this, hit download and began install as a reboot- didnt spot implications. As said, noob, followed a tut. If it highlighted DO NOT UPDATE or.. IF U WANT UPDATE NOW FOLLOW THIS- Great, but nothing of the sort?
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Or do you have any links to tutorials I could possibly follow?
Side note- when this loop started I deleted

esenfur said:
Or do you have any links to tutorials I could possibly follow?
Click to expand...
Click to collapse
This is really your main issue. By following a YouTube video and using a Toolkit, you've failed to actually learn anything or gain any real understanding or knowledge. Do yourself a favor and ditch the tutorials and videos (and toolkit for that matter) and do it the old fashioned way . . . by reading. Videos and step-by-step guides do you no good when things go south (as you've now discovered). And with the prior proper knowledge (usually not gained by following tutorials) this whole mess probably would have never happened in the first place.
A cardinal rule of Android phone modding: DO NOT accept/download/install OTAs (official OS updates) on a modded device unless you know what you are doing, and what the result will be. If in any doubt, simply DO NOT do it.
esenfur said:
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Click to expand...
Click to collapse
.exe file is Windows specific. You are looking for a zip file, and it typically starts with "OTA". Don't remember where its saved to, so you will have to search for it. If you can't keep the phone running long enough to do so, mount the memory on your computer and search that way.
Deleting the OTA file worked for me on a past device, although one M8 user in the same position said deleting the file didn't get him out of the loop. Flashing your ROM again, or wiping the internal memory (backup any important personal data first) might be options for you.

redpoint73 said:
you've failed to actually learn anything or gain any real understanding or knowledge.
Click to expand...
Click to collapse
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
redpoint73 said:
Videos and step-by-step guides do you no good when things go south (as you've now discovered).
Click to expand...
Click to collapse
agreed.. theres FAR much more I need to learn.. its scary haha.
redpoint73 said:
DO NOT accept/download/install OTAs (official OS updates)
Click to expand...
Click to collapse
taken on board. I know with my jailbreaks in past it has been a pain, assumed Android would be alot more stable to over write- due to functionality of OS and unlocked features.
I was being generic when I said .exe- basically the installer..
I returned from work to see phone stopped looping.. i could stop the install and deleted the file ASAP.. but now what.. Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?

I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.

Try to re-flash the ROM, with stok ROM, using TWRP and clean install. It should work.

hack14u said:
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Click to expand...
Click to collapse
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8

esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
First of all once the bootloader is unlocked you don't have to relock it to get OTA.
As I undersand you have done the following:
1) Unlock using HTCDev-Method
2) flashed a custom revocery (TWRP in your case)
3) flashed a supersu too!?
To install the OTA means loosing root acces. Thus you have to re-root it after the OTA is done. The other problem ist that STOCK OTAs don't work with a custom recovery. Meaning you would have to flash a stock recovery first, install the OTA second (as long as you didn't change anything an just root), and re-root third.
Let's have a look which stock recovery you would need:
1) reboot to bootloader
2) connect the phone to you PC and open cmd in you adb/fastboot folder
3) enter "fastboot getvar all"
4) paste this information here (but DELETE the IMEI and SERIAL NUMBER before posting!!)
As soon as we know which stock recovery you need we will go on.

esenfur said:
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
Click to expand...
Click to collapse
I'm not saying there is anything "wrong" with the toolkit, per se. For the most part, it does what its intended to do.
But it also shortcuts the learning process, and facilitates folks rooting the phone without gaining the proper knowledge. This is a dangerous thing.
This is just my opinion. But I strongly believe it. If you can't accomplish these things without a toolkit, you shouldn't be rooting your phone in the first place.
Others use the toolkits, and love them. They are more than entitled to have their own opinion. But when things go south, the toolkits aren't going to help; and those folks don't have the proper knowledge and they come running here. So you tell me what is the "best" way to root the phone?
esenfur said:
I was being generic when I said .exe- basically the installer..
Click to expand...
Click to collapse
I already figured this was probably the case. But I found it better to provide the exact information on what file to delete; rather than leaving it open to the possibility of you and/or others being misinformed.
esenfur said:
Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
Click to expand...
Click to collapse
Sounds like you still have TWRP installed, so just flash SU or SuperSU to gain root.
After that, you can use Titanium Backup or similar app to find the update process and freeze it, to stop the update notifications.
Don't remember the exact process (this is where searching and reading comes in for you) but its something like "drm..." or "updater".

I have this situation before,what i do is find the right stock recovery and flash..after ota done flash back custom recovery..?

esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
At this point after seeing this, I would suggest you take some time and start reading. All of your answers are here in the forums. Knowledge is power and within the pages of this site you will find everything you need.
To take the OTA find a stock recovery, to flash ROM's find the one you like and flash via your favorite recovery.

ZE500CL Rooting and other related stuff

It seems that few ever talk about the ZE500CL variant of the zenfone 2. I've read a whole lot of posts on rooting, unlocking the bootloader, and installing TWRP, but most do not even mention this variant.
I started this thread to collect some information about this device. I would like to know from those who have this device, what has worked for you so far, and what hasn't? I'm especially interested in finding out the 3 things mentioned above.

I've only recently bought the device, and I only rooted it (though I did first get one bootloop already). The method that worked for me is described in this thread: http://forum.xda-developers.com/zenfone2/general/root-ze500cl-z00d-t3116531
The OP of the thread linked above also said that the second method on this thread: http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 works as well.
Btw, make sure the drivers are installed, else the computer won't be able to recognize the device when it is in bootloader mode.

Installing Xposed works as well using the ADB method mentioned in the thread linked below:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476

I can add any info you find to the device index in the general section for the 500CL.

Djalaal said:
I've only recently bought the device, and I only rooted it (though I did first get one bootloop already). The method that worked for me is described in this thread: http://forum.xda-developers.com/zenfone2/general/root-ze500cl-z00d-t3116531
The OP of the thread linked above also said that the second method on this thread: http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 works as well.
Btw, make sure the drivers are installed, else the computer won't be able to recognize the device when it is in bootloader mode.
Click to expand...
Click to collapse
How did you fix/handle the bootloop?
Do you know if it is possible to update the phone after rooting it?

cmendonc2 said:
I can add any info you find to the device index in the general section for the 500CL.
Click to expand...
Click to collapse
Sure, that post is much more likely to be noticed than this one. Although I might not find out much. I'm a lot less daring without custom recovery. Hence this thread.
crisbal said:
How did you fix/handle the bootloop?
Do you know if it is possible to update the phone after rooting it?
Click to expand...
Click to collapse
Well, seeing that I do not have a custom recovery (bootloader is still locked), I had to do it the hard way, reflash stock rom. Good news is, apparently your userdata (installed apps+settings and internal memory) is not wiped in the process.
First, you gotta download the rom. Get it from http://forum.xda-developers.com/zenfone2/general/index-asus-zenfone-2-wip-t3149748. Although I got mine here: http://www.asus-zenfone.com/2015/03/asus-zenfone-2-stock-rom-ze500cl-ze550ml-ze551ml.html, which is the old version.
Second, go into recovery mode (from bootloader mode), and use adb sideload ("apply update from ADB") to flash the .zip downloaded before. This is described under "Flashing Zenfone 2 via ADB" on this thread: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Btw, the bootloop was caused by a mistake I made, not the rooting process.

any news update in our bootloader? hope someone could work for that..

How to get rid off couldn't add widget?

crisbal said:
Do you know if it is possible to update the phone after rooting it?
Click to expand...
Click to collapse
After more than a week of feeling unsure to update mine to WW_12.16.5.118, updating it today after finish uninstalling SuperSU. This is what I have done.
1 - uninstall SuperSU from SuperSU setting - reboot.
2 - update firmware.
3 - re-root using Temporary_CWM method as describe here
Chinaphonearena said:
Method 2: Root through temporary CWM
This is a temporary CWM with the primary purpose of injecting SuperSU onto your Asus Zenfone 2. It doesn't permanently replace recovery. This process looks long, but really is bam 1,2,3 done. Just laid out step by step for the newbie.
link removed due to post count limitation
Unzip the package
Copy SuperSU.zip to the base of your SD card
Enable USB debugging (Settings > Phone info > Tap build 7x > Back button > Developer options > USB debugging)
If you don't already have ADB drivers installed, you may need to [post count restriction] and install them (most PCs have them already, but trying installing these if you're having trouble getting your PC to issue commands to the phone via USB)
With your phone on, attach it to PC via USB
Run 'cai_dat_CWM.bat' from the CWM package
In the black command window that opens, type ACCEPT
Type T4
Phone will reboot into fastboot and you'll see commands being issued from the PC cmd window copying the temporary recovery
You may see some funked up images on your display for a bit. Remove the USB cable and within 30 seconds should then see it booted into CWM
Select install update
Navigate to SuperSU.zip and install
Bam, done.
Click to expand...
Click to collapse
4 - Success!!! now my phone are rooted and all rooted apps installed previously are working.
Note: Previously (before updating FOTA) I also root my ZE500CL using Temporary_CWM since One Click root method aren't working for me.

Recover from bootfreeze while fully stock
Well, after getting a bootfreeze being on a fully (old version) stock ze500cl (Z00D), I figured out something useful. How to recover from a bootfreeze with locked bootloader, non rooted stock rom, without loosing what was saved on your internal storage.
Given that you have not messed with system files (since you aren't rooted), I'm assuming you got either corrupted userdata files or your internal storage is so full, the phone fails to even boot. I had the latter. If system files are the problem, this method might (or probably?) not work. The trick is to use tethered TWRP for backing up your internal storage.
1: Download CWM_Zenfone_2_Intel.zip here: https://www.mediafire.com/folder/w70w7r1a65840/Zenfone_2 (gotten from source 1)
2: Download Recovery.zip here: https://drive.google.com/folderview...T0xRMVRkcTg3MHdlc1o0cVFBc3RPeTQ&usp=drive_web (gotten from source 2)
3: Extract the zip from Step 1.
4: Go to the FB_RecoveryLauncher folder you have extracted, and replace the recovery.zip there with the one downloaded in Step 2.
5: Boot into your stock recovery and connect your phone to the computer. Make sure you have adb and the phone's drivers installed (gotten from source 3).
6. Run the cai_dat_CWM.bat script and you should boot into temporary TWRP recovery after a minute or so.
7. Use TWRP to copy your sdcard folder (internal storage) into your ext_sdcard folder (external storage/microsd) for the sake of backing it up.
8a. In the case of having too full internal storage, simply delete some things in there, and you should be able to boot it again.
8b. Not tested, but in case of corrupted userdata, a factory reset is probably necessary, and will solve the bootfreeze issue.
source 1: http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 (method 2)
source 2: http://forum.xda-developers.com/zenfone2/development/alpha-tethered-twrp-asus-zenfone-2-t3123532
source 3: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
@cmendonc2 , if you want, you can add this to your index.

Djalaal said:
It seems that few ever talk about the ZE500CL variant of the zenfone 2. I've read a whole lot of posts on rooting, unlocking the bootloader, and installing TWRP, but most do not even mention this variant.
I started this thread to collect some information about this device. I would like to know from those who have this device, what has worked for you so far, and what hasn't? I'm especially interested in finding out the 3 things mentioned above.
Click to expand...
Click to collapse
Thank you so much for providing this thread. Found it after hours of scouring the internet in search of help after somehow getting my phone locked in boot-loop. There isn't much support for the ZE500CL, but I will be posting on some blogs while I begin work on mine, and I will reference others to this thread and the few others I've found. Thanks again! :good:

Xanathide said:
Thank you so much for providing this thread. Found it after hours of scouring the internet in search of help after somehow getting my phone locked in boot-loop. There isn't much support for the ZE500CL, but I will be posting on some blogs while I begin work on mine, and I will reference others to this thread and the few others I've found. Thanks again! :good:
Click to expand...
Click to collapse
Sorry, was out of town for 3 months. Glad to be of help. You know where the thanks button is .
I should note that the this phone is now the daily driver of both my parents so I stopped tinkering with it, although I left one of them rooted (and the other not lol). So don't expect more updates from me sadly.

Djalaal said:
Sorry, was out of town for 3 months. Glad to be of help. You know where the thanks button is .
I should note that the this phone is now the daily driver of both my parents so I stopped tinkering with it, although I left one of them rooted (and the other not lol). So don't expect more updates from me sadly.
Click to expand...
Click to collapse
That's quite alright, I've had my fun with Z00D, got myself a LG V10 to break now

I dont ask for directions...
This is my first time asking questions as I have always been able to reverse-engineer (R-E) or as the hacker in swordfish would say "the code just comes to me". Ive been around computers since my dad took me to work at UT and commands were issued with punch out cards....I've been a long time android self taught enthusiast turned professional. ITT Alum etc. I research, I surf, I R-E, and I try every possible option etc...only this has me stumped. And this is the first android that has stumped me. I double checked everything but I keep getting this error in BBQLinux: I followed all pre-update instructions to the T.
fw: ATT_12.16.10.92
adb sideload
This package is not for ATT (WW)
E: Error in /sideload/package.zip
(Status 7)
yes I did with root cmd line, yes cd to zip file location, yes I verified correct fw, even tried different fw zips ZE500CL downloaded officially and from here.
I greatly appreciate any help and I do apologize for "asking for directions"
Computer John dba Austin Computer Techs

cuervo233 said:
This is my first time asking questions as I have always been able to reverse-engineer (R-E) or as the hacker in swordfish would say "the code just comes to me". Ive been around computers since my dad took me to work at UT and commands were issued with punch out cards....I've been a long time android self taught enthusiast turned professional. ITT Alum etc. I research, I surf, I R-E, and I try every possible option etc...only this has me stumped. And this is the first android that has stumped me. I double checked everything but I keep getting this error in BBQLinux: I followed all pre-update instructions to the T.
fw: ATT_12.16.10.92
adb sideload
This package is not for ATT (WW)
E: Error in /sideload/package.zip
(Status 7)
yes I did with root cmd line, yes cd to zip file location, yes I verified correct fw, even tried different fw zips ZE500CL downloaded officially and from here.
I greatly appreciate any help and I do apologize for "asking for directions"
Computer John dba Austin Computer Techs
Click to expand...
Click to collapse
?? Is that att ota youre trying to sideload? Att doesn't have fw, ze500cl does. But just unlock your bootloader, flash twrp, then install whatever, cm, aicp, custom stock or straight stock. http://forum.xda-developers.com/showthread.php?p=64991762
Sent from my MotoG3 using Tapatalk

Cool, I didn't read anywhere about unlocking BL first otherwise Ida made that "turn at the first light". We will ULO thru Asus and continue on our journey. These little Asus trinkets are little buggers being Intel based. Only line of Android devices that have ever stumped me. I am much obliged, fellow XDA brethren. Much obliged.
After pondering a little I came to this conclusion:
UL BL is basically the first step one should take when doing any kind of flashing of internal partitions be it a boot.img, recovery.img, FW etc... at least for the higher end devices. I don't recall having to do that for my sm-n900t recently. Does it only apply for flashing back to stock and not custom roms? Although I didn't have to UL BL first when I heim-dall/Odin flashed my note3 back to stock rom after being boot-looped. Cause once I did that I was able to try out a majority of custom roms available for it whether flashed thru HD/fastboot, Odin, via twrp update zip, or adb sideload. Hmmm, I might understand once I think it thru and look at all the different variables.
Good day gentlemen.
Be vewy vewy quiet, I'm hunting androids...
:good:

@cuervo233 Yes most devices you have to unlock the bootloader first. But there are some devices that already come unlocked. And then there are even some that have bootloaders that cannot be unlocked due to carrier restrictions. In order to get custom recovery to boot you must unlock the bootloader or it must come unlocked. With a custom recovery you can Flash the stock zip file from the Asus website or a custom ROM have fun
Sent from my MotoG3 using Tapatalk

Thank you. I was able to ULBL, flash TWRP, flash to ww 118, root, and now its time to explore the neat wonderful world of custom ROMs. This was by far the hardest yet. Next in line is the cricket Stylo which was also giving me hell, but now I dont think I should have any problem getting it done. I'll keep ya'll posted.:good:

Lg stylo should have way more development, have fun brother. Remember tmobile phones( cricket, walmart family mobile, and metro pcs) you can easily unlock the bootloader . att on the other hand usually has locked down bl.
Sent from my MotoG3 using Tapatalk

Help please. NEW to 2013 N7

Hello all. I am new to the N7. I look forward to trying out some of the awesome development in this forum. Before I begin I need to ask some things. I have spent ALL DAY today reading forums and researching this device b4 I begin. But to be honest, I can not spend days reading every post out there and still be a dad here. So I am trying to stream line this some. I am not a newbie in rooting / roming. Sorry if I have not seen a topic like this b4 posting. There are just so many in this forum now to go through. I will delete this one once helped if nessary. Also THANK YOU VERY MUCH in advance for any help I get here.
1. I have a Verizon note 2, Verizon PERMANENTLY locked the bootloaders on their phones so development has stoped/ slowed drastically. I know the N7 has a locked bootloader that can be unlocked. Is this still true on a stock 5.1.1 lollipop version? or Is there a step to reflash to an older rom I should do first?
2. I see the wugs toolkit out there and a nexus toolkit. Is there any reason to use one over the other? Are either of these working on my STOCK 5.1.1 rom still?
3. Can someone please run down the steps to achieve UNLOCK, ROOT, AND CUSTOM RECOVERY? I seen how wugs does all that in it's program. So if that is the way than a good link to use Please.
Once again. Thanks in advance for your help here. Please also feel free to add in here anything I need to be aware of b4 I begin making my N7 a beast of a tablet. I can not wait to try out some of the awesome roms and mods I have seen so far.
:thumbup::beer::thumbup::beer::thumbup::beer::thumbup::beer:
To root or not to root? That is the question.

1. It's unlockable
2. No need for a toolkit just use fastboot, unless you don't want to know what you're doing. It's in the platform-tools folder of the android sdk. There are many guides on xda about how to use it. Don't forget to install googles usb driver.
3. Very easy. Boot the tablet to the bootloader by holding volume down and power while turned off.
Plug into the computer and open a command prompt in whatever folder you have fastboot and type fastboot oem unlock and hit enter. Follow the steps on the tablet.
For recovery download the recovery .img you want and put it in the fastboot folder. Type fastboot flash recovery whatevername.img
To root just download the su zip from here and flash it through recovery.

You need to be careful you don't have a new Nexus 7 version which doesn't allow the mounting of any of the partitions in a custom recovery. I have one of these new Nexus 7s and no matter what I do I can't get the recovery to work, there's a thread about it.
Sent from my SM-G925F using Tapatalk

Batfink33 said:
You need to be careful you don't have a new Nexus 7 version which doesn't allow the mounting of any of the partitions in a custom recovery. I have one of these new Nexus 7s and no matter what I do I can't get the recovery to work, there's a thread about it.
Sent from my SM-G925F using Tapatalk
Click to expand...
Click to collapse
Ok so how do I locate n answer to this issue. The serial number in the bootloader info? Or something else?
Thanks for the two answers so far!
:thumbup::thumbup::thumbup::thumbup:
To root or not to root? That is the question.

robrooter said:
Ok so how do I locate n answer to this issue. The serial number in the bootloader info? Or something else?
Thanks for the two answers so far!
[emoji106][emoji106][emoji106][emoji106]
To root or not to root? That is the question.
Click to expand...
Click to collapse
Here's the thread on the issue. I bought my N7 yesterday and I'm affected by this. I can't resolve it and am stuck on stock at the moment which is annoying as I bought it to mess about with Roms and kernels. I'm not sure how you identify which tablets are affected but it seems the later manufactured ones are.
http://forum.xda-developers.com/showthread.php?t=3064562