Develop Bugs

Root help please

So I finally got my G2/Vision, I want to perm-root my G2. But I fail so much, I can't even put Visionary into my G2.... I downloaded Astro, but I need to place Visionary r14 in my SD, but I can't find a place to put it.
When I look in my SD through windows, it shows me a LOST.DIR, .Trashes, .Spotlight-V100, .fseventsd, .android_secure, Android, etc. etc. But I still can't find the spot to place Visionary, Help?

place it in that folder

ilikepu said:
place it in that folder
Click to expand...
Click to collapse
Haha, I figured I'd just dl it off the internet through my G2. It worked. Configured it.

Word to the wise, stay away from visionary. Use rage.

ddgarcia05 said:
Word to the wise, stay away from visionary. Use rage.
Click to expand...
Click to collapse
Whats the difference? And... What happens if I already used Visionary?

If you used Visionary and it worked for you, then that's great.
I also try and steer folks away from Visionary myself. Quite a few seem to end up with a lot of problems after using Visionary. The "rage" method of rooting is a lot more reliable, it's just that it looks a lot more "scary" to newcomers because there are commands you have to type in and run on your PC and phone. But if you read up on it, and ask questions if you don't understand, then follow the instructions carefully, you'll be fine - and even if rage goes wrong then you won't end up with a semi-brick, you just won't get root (until you fix the problem).

Ohhhh, Ok. Yeah I couldn't get Visionary to work until several tries. Took me a while. I was supprised I hadn't bricked my phone already. But now I'm pretty satisfied with CM 6.1 w/ MattedBlues theme. Sucks though I couldn't get it to work with Virtuous. I really like Sense alot more than the stock Rom (I consider CM 6 to be pretty stock)

Hope this helps!!!
steviewevie said:
If you used Visionary and it worked for you, then that's great.
I also try and steer folks away from Visionary myself. Quite a few seem to end up with a lot of problems after using Visionary. The "rage" method of rooting is a lot more reliable, it's just that it looks a lot more "scary" to newcomers because there are commands you have to type in and run on your PC and phone. But if you read up on it, and ask questions if you don't understand, then follow the instructions carefully, you'll be fine - and even if rage goes wrong then you won't end up with a semi-brick, you just won't get root (until you fix the problem).
Click to expand...
Click to collapse
+1 on the reliable and +1 on the scary!!!!
I am very new to Android,...I've only had my G2 for about 2 months...I ran Visionary temp root without issues (r10). When I tried to install in r14 to perm root, I encountered a myriad of errors, and decided not to root.
But I just couldn't give up on it....two weeks ago I got food poisoning, which rendered me useless and home bound, I decided to attempt it. I decided to use the rage method, but found that the instructions assumes that you know something about rooting. There are alot of people on this forum that are willing to help (steviewevie was one of them) to get you your through what ever hurdle you encounter.
Personally I found the rooting process very rewarding as I now have less of a vague idea of what is happening in my phone (ie not as lost as before).
Some of the basics:
- Install adb on your pc (not that scary), and read a bot on it...understand what some of the basic commands are trying to do. (see the rooting guide for those commands)
- set your path on your PC to point to the correct directory from where you are pushing (There are a few forums here that will guide you setup by step on how to do this)
-Follow the instructions to the T, and you should be ok.
Click here to go to the thread that these guys helped me while I going through the process. Post #4 makes reference to the path on your pc.
NOTE:This Path should point to the location where you have your adb tools and location of the files you are trying to push to your phone.
Post #17 goes step by step on what you need to do, and how the lines on the terminal should look like.
This is really not that difficult once you get your bearings, and for me it was a lot of fun...actually a little bored with the phone after having done this.

Put (SOLVED) in your thread title please.
Sent from my HTC Vision using XDA App

You all seem to suggest to not use visionary but use rage but from what I saw yesterday we had 2 "bricks" from people rooting with rage, compared to none from visionary

Lennyuk said:
You all seem to suggest to not use visionary but use rage but from what I saw yesterday we had 2 "bricks" from people rooting with rage, compared to none from visionary
Click to expand...
Click to collapse
Ouch! Really? So no method is any "safer" yet then? Was planning on return to stock then Rage today. I take it I can't update my radio without full radio s-off? Or can i"?
Sent from my HTC Vision using XDA App

ddotpatel said:
Ouch! Really? So no method is any "safer" yet then? Was planning on return to stock then Rage today. I take it I can't update my radio without full radio s-off? Or can i"?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
If you know how to read, you can safely root using rage. Just read over the instructions a couple times first.

If you know what your doing both methods are as safe as each other. From what I can see there is a larger margin of error using Rage, however its entirely in your own hands, so as long as you make sure you input it all correctly it should be fine.
Both "bricks" yesterday were recoverable, and both times the user was sure they followed it all correctly, it just seems that their rom corrupted during the process so ended up stuck on a bootloop.

blackknightavalon said:
If you know how to read, you can safely root using rage. Just read over the instructions a couple times first.
Click to expand...
Click to collapse
Lennyuk said:
If you know what your doing both methods are as safe as each other. ...
Click to expand...
Click to collapse
So we not talking about the random occurance of file corruption then?
Thank you both (i'll add the to your thanks meters when I have some available). Just need to find how to fully reverse the rage method if needed.

Lennyuk said:
If you know what your doing both methods are as safe as each other. From what I can see there is a larger margin of error using Rage, however its entirely in your own hands, so as long as you make sure you input it all correctly it should be fine.
Both "bricks" yesterday were recoverable, and both times the user was sure they followed it all correctly, it just seems that their rom corrupted during the process so ended up stuck on a bootloop.
Click to expand...
Click to collapse
Are you sure the corruption didn't stem from an earlier unsuccessful attempt to root with Visionary ?
I've yet to see a thread where someone has done something bad to their phone via rage, all it does is fire up a ton of process to use an exploit which gets you root. That can't corrupt your phone on its own.
Do you have some links ?

ddotpatel said:
So we not talking about the random occurance of file corruption then?
Thank you both (i'll add the to your thanks meters when I have some available). Just need to find how to fully reverse the rage method if needed.
Click to expand...
Click to collapse
Here you go.

How to put cyanogen with visionary?

Hi, I'm sorta a noob with rooting so bare with me. First, what version of visionary should I use to root my device? Will it work after the ota update? What are the chances of visionary bricking my phone or doing anything that would make my phone unusable? Will it put SU on my phone? And now for the main question, how will I get cyanogen on my g2? Thanks for any help!
Sent from my T-Mobile G2 using XDA App

As far as i know visionary is not gonna brick your phone ,in regard to changing your rom you also need to s/off your phone, and to do that you need to setup ADB on your computer i suggest you read this posts first ,you will find all the answers you are after
http://forum.xda-developers.com/showthread.php?t=857390
http://forum.xda-developers.com/showthread.php?t=855764
http://forum.xda-developers.com/showthread.php?t=835777
http://forum.xda-developers.com/showthread.php?t=532719
After you root and s-off your phone you need to setup rom manager so you will get clockworkmod recovery and you can boot in to that and flash a new rom or kernel through there.
and i am not sure about the question you had about the update.
yes you will get su after rooting.

Hwoarang747 said:
Hi, I'm sorta a noob with rooting so bare with me. First, what version of visionary should I use to root my device? Will it work after the ota update? What are the chances of visionary bricking my phone or doing anything that would make my phone unusable? Will it put SU on my phone? And now for the main question, how will I get cyanogen on my g2? Thanks for any help!
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Ok, first there are already many threads on this subject, so next time you should try a search first,
for example: http://forum.xda-developers.com/showthread.php?t=850141
http://forum.xda-developers.com/showthread.php?t=882546
Next the following links will help walk you thru rooting your phone using visionary r14. I have not had any problems with it, many people have rooted this way. If something goes wrong it is usually operator error. This method is for after the OTA. All needed files and links are in the video instructions.
Visionary has bricked phones before when not properly used, the videos show how to use it properly, use all the same settings in the videos.
This is the visionary method, but works perfectly when done correctly..
No adb needed.
Follow the videos to a "T", remove visionary and superusers from you phone if you already have them installed from a previous temp root before following the videos, start fresh, follow the videos starting with temp root then onto perm root then onto flashing a rom. Do everything just like the videos start to finish and you should have no problems.
Temp root first:
http://theunlockr.com/2010/10/20/how-to-root-the-t-mobile-g2-htc-vision-visionary-method/
Then perm root
http://theunlockr.com/2010/11/30/how-to-gain-permanent-root-and-s-off-on-the-t-mobile-g2-htc-vision/
Then flash a rom
http://theunlockr.com/2010/11/30/how-to-load-a-custom-rom-on-the-t-mobile-g2-htc-vision/
Remember don't assume you know how to temp root properly, follow all three videos start to finish and you should have no problems
Also the video "Load a custom rom" will give you a link to flash your first rom. There are a couple of choices to choose from.
Good Luck.
Editlease see post #32 in this thread for a testimony from someone who just followed the videos and rooted his phone.

Thanks soooo much!!! I have another question, how will I be able to get gingerbread after rooting? Or should I wait? Do I need to wipe my phhone? And what if I just want vanilla android with su and cyanogen?
Sent from my T-Mobile G2 using XDA App

Hwoarang747 said:
Thanks soooo much!!! I have another question, how will I be able to get gingerbread after rooting? Or should I wait? Do I need to wipe my phhone? And what if I just want vanilla android with su and cyanogen?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Everyones still waiting on gingerbread, but it looks like Cyanogen is in the lead for releasing it.
Any time you flash a new rom you need to wipe data/cache in recovery. Updates to the same rom a wipe is not needed.
As far as what you want in a rom, my suggestion is to start flashing diffrent roms and give them a try. I thought I didnt like sense but I am currently running a sense rom (Virtuous). So you dont know till you try.

1) Don't use Visionary. People have had brick after brick when using it. Use the rage method.
2) There's a beta version of CM7.0.0 out. The devs are still working out the bugs in it.
Sent from a Western Union telegram.

blackknightavalon said:
1) Don't use Visionary. People have had brick after brick when using it. Use the rage method.
2) There's a beta version of CM7.0.0 out. The devs are still working out the bugs in it.
Sent from a Western Union telegram.
Click to expand...
Click to collapse
1)Show me one brick from someone following the videos I posted and Ill take the links down. Yes a lot of people have bricked using visionary, but thats because they assumed they knew what they were doing when in fact they did not. Visionary causes bricks when not properly used, the videos shows how to use it properly. You must follow all the steps from start to finish including the temp root settings they use in the videos.
2)and yes there is a beta version of gingerbread out CM7 but Cyanogen did not officially release this version, and there are so many bugs in it I hardly think a noob needs to flash CM 7.0.0.

What exactly its the range method?
Sent from my T-Mobile G2 using XDA App

Hwoarang747 said:
What exactly its the range method?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Its Rage method and heres a link to the thread:
http://forum.xda-developers.com/showthread.php?t=834228&highlight=rage
I recommend you read this thread and make informed desicions, if you know how to use ADB, then this is another method. But if you dont the method I posted above is your other option, it doesn't require the use of ADB.
As far as ADB goes this is something I highly recommend learning, but we all know some people just dont get it. It took me a lot of reading and watching videos to understand ADB. Now that I know how to use ADB its pretty simple, but I remember when I first started with rooting ADB was like reading greek. But I really cant stress enough the importance of learning ADB.

Hahah sorry, i was using swype. And yeah, so what do you recomend, cause i really dont wanna brick my phone for its fairly new.

Oh, and another thing, if i root with visionary or rage, that only gives me root access. But if i flash a rom then i will also have cyanogen? And i was reading, since i wanna oc, whats this kernel stuff? Please forgive my noobish ways

Hwoarang747 said:
Hahah sorry, i was using swype. And yeah, so what do you recomend, cause i really dont wanna brick my phone for its fairly new.
Click to expand...
Click to collapse
I used the videos to root my G2, there have been a lot of bricks using Visionary but I have yet to see anyone say they followed the videos to the "T" and it bricked there phone. As for the Rage method, there have been almost no reports of bricks from this method, but I have seen a few bootloops (stuck on the HTC screen). It requires using ADB, so if your ok with ADB use the Rage method, if not, you'll have to weigh the risks based on your own ability. My suggestion, watch the videos, all of them and if its something within your skill range go for it.

Hwoarang747 said:
Oh, and another thing, if i root with visionary or rage, that only gives me root access. But if i flash a rom then i will also have cyanogen? And i was reading, since i wanna oc, whats this kernel stuff? Please forgive my noobish ways
Click to expand...
Click to collapse
Ok, get rooted first then you can worry about kernels, I believe Cyanogen 6.1.1 already comes with an overclocked kernel up to 1.42GHz. So all you have to do is flash CM 6.1.1 his latest release, then down load a cpu controlling app from the market like setcpu(which I use) or cputuner(free) and set the parameters you want your cpu to run at.

Thanks, but a boot loop is fixable right?
Sent from my T-Mobile G2 using XDA App

It usualy is you can boot in to recovery and wipe and flash another kernal or rom. Just have a look at the links that I posted ,you will get all the answers.
Sent from my HTC Vision using XDA App

Hwoarang747 said:
Thanks, but a boot loop is fixable right?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Not always hopefully if this happens you have gotten far enough along to put a recovery on your phone, or sometime you can stock recovery factory reset but if those options arn't there guess what you would have to have AndriodSDk installed on your computer with ADB, but you would have to do everything in fastboot mode which is giving commands from your computer to you phone. So it wouldn't be adb because you have to be booted into Andriod to use it, it would be fastboot and run commands similar to ADB, so for this purpose you would have to know how to use ADB. And even then no guarantees. So if you are looking for a guarantee you wont brick your phone there are none, and I wont give you one, these methods have been proven to work if you follow them exactly, mess up and you have a brick.
I know most people dont have $500+ laying around and I know I dont but for me the rewards far outweighed the risk. I just got a pm from another member that followed the videos and guess what he is rooted, he did it today. I asked him to post in this thread with his success story, so hopefully he will.
Here is a quote from him from my PM "it worked! i got so frustrated with adb, i gave it a shot and success!"
Edit: He just posted success his user name is robot_agenda and his post is #32 in this thread.

wait so what did he give a shot? the gfree method?

Hwoarang747 said:
wait so what did he give a shot? the gfree method?
Click to expand...
Click to collapse
He rooted his phone with visionary following the videos I posted.

and also, have you heard of the issue with visionary where the phone boots into recovery when being charged?

Hwoarang747 said:
and also, have you heard of the issue with visionary where the phone boots into recovery when being charged?
Click to expand...
Click to collapse
That has nothing to do with visionary, thats has to do with ClockworkMod recovery, if your phone is powered off and you plug it in to charge it boots into recovery, if you want root you have to deal with this issue untill they fix the bug in clockworkmod recovery. Also the phone shuts off fine unless its pluged in. Everyone with a htc vision phone who is rooted has this issue. as for me I charge my phone while it on so it doesn't bother me.
heres a link to the problem:
http://forum.xda-developers.com/showthread.php?t=884516

[Q] Running into problem following root guide

Hello. The guide I'm following is found at http://forum.xda-developers.com/showthread.php?t=2221039. I'm following it character for character short of where the thread has corrections to some errors.
My end goal is getting CM7.2 on this thing and having a rooted phone. My question is basically "What do I do when I'm experiencing the following?"
When I get to:
•fastboot flash zip firmware.zip under step 7 I end up with a FAILED (remote: 41 model id check fail)
Everything prior to this point is going exactly as it should as far as I can tell. There are no other errors of any kind. When I continue through the process after this failure I end up at:
•adb shell /tmp/gfree -f under step 8
This is where the second failure occurs which I imagine is due to the firmware issue. It ends up with a bunch of lines showing things happening and then comes to:
Attempting to power cycle eMMC... Failed.
Module failed to power cycle eMMC.
These are the only issues I'm having with this guide and can't seem to figure it out. Unfortunately I can't ask on that thread because I'm under the 10 post mark as I've tried to read instead of ask questions. At this point I'm just stuck though. As of now I'm trying to flash CM7.2 using CWM as the rooted stock rom is done in that guide. So far I'm having no luck though. I'm glad I'm using this as a test dummy before getting a newer phone and attempting anything on it. Any help that can be provided is greatly appreciated. I'd love to get this sorted out.

bhd1223 said:
•adb shell /tmp/gfree -f under step 8
This is where the second failure occurs which I imagine is due to the firmware issue. It ends up with a bunch of lines showing things happening and then comes to:
Attempting to power cycle eMMC... Failed.
Module failed to power cycle eMMC.
Click to expand...
Click to collapse
From what I have read gfree works for Android 2.2.1 and you do realize if you the hboot version is correct you can just unlock at htcdev.com and flash the rom. Thats what werked for me.

lamebmx said:
From what I have read gfree works for Android 2.2.1 and you do realize if you the hboot version is correct you can just unlock at htcdev.com and flash the rom. Thats what werked for me.
Click to expand...
Click to collapse
Thanks. Actually, just after I posted that I tried to load CM 7.2 in the same way that it directed to load the rooted stock ROM in the guide. This was after using the HTC Dev Unlock. Then I discovered I needed to have 4.0+ to stream video from an app I was using. The night after that I ended up going with an Unofficial CM 10.1 port for Ace devices and making it think it was an Inspire 4G again (http://forum.xda-developers.com/showthread.php?t=2093845).
A little wonky at random times, probably hardware related, but works really well and allows me access to things I wouldn't otherwise have. I was really concerned about running non-final release or "stable" labeled ROMs which has had me holding off on getting a newer phone. After running this build for a few days which is based off a nightly, I see no reason to worry. It seems a simple process to do all this stuff although I'm sure the actually programming is more difficult.
Basically, the only thing I'm left without is S-Off. From further reading I've done this doesn't even really matter anymore. I can load custom ROMs, I can gain su access, I can do anything I want to the phone as far as I can tell. I'm happy with it is unless there is some secret of awesomeness I'm unaware of that I've yet to tap.

bhd1223 said:
Basically, the only thing I'm left without is S-Off. From further reading I've done this doesn't even really matter anymore. I can load custom ROMs, I can gain su access, I can do anything I want to the phone as far as I can tell. I'm happy with it is unless there is some secret of awesomeness I'm unaware of that I've yet to tap.
Click to expand...
Click to collapse
I just got S-OFF with this guide:
http://forum.xda-developers.com/showthread.php?t=2367322
using the proper PD98IMG.zip from this thread:
http://forum.xda-developers.com/showthread.php?t=2193681
FYI it downgrades you in the process and I have not got my phone to boot yet, but im 99% sure its cuz i have not done the upgraded RUU from the first thread (JB probably does not like GB radio etc) but unlocked and S-OFF leaves it where you should be able to fix it.

lamebmx said:
I just got S-OFF with this guide:
http://forum.xda-developers.com/showthread.php?t=2367322
using the proper PD98IMG.zip from this thread:
http://forum.xda-developers.com/showthread.php?t=2193681
FYI it downgrades you in the process and I have not got my phone to boot yet, but im 99% sure its cuz i have not done the upgraded RUU from the first thread (JB probably does not like GB radio etc) but unlocked and S-OFF leaves it where you should be able to fix it.
Click to expand...
Click to collapse
Thanks lamebmx. I was having a boot issue as well when I first installed CM7.2. Then I learned that each ROM needs to have it's own boot image flashed to the boot partition. After that no issues. When I did 10.1 I used the boot image from that as well and haven't had any issue with booting. You may have done that already but it can't hurt to re-flash if you already did, or do it if you haven't.

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

LG G4 Root?

Hello XDA community,
I recently traded in my old iPhone for this new LG G4, and am so glad to be converted from iOS to Android! Anyways, one of the main reasons I switched is because root access would enable me to maximize the potential of my phone. The only problem is...I have looked vastly throughout XDA and other Android developer havens for root guides and have gotten so confused as to where to start. Can somebody direct me to the right place, or even better, guide me through the process?
Thanks!
(I am using the Verizon G4 (VS986) with Android 5.1.)

DId you have a good look through this thread?
http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
It seems daunting but the first things you can do prior to the flashing are
-Get the software you need installed and tested
-Learn how to put your phone into download mode
-test to make sure your phone can communicate with your computer the way it should
-Download all the files you need (stock kdz and matching rooted image version)
Take the time to read each step, and if you have any questions, ask before you proceed, not after you have completed the step.
Good luck! The group here is very helpful so do not hesitate to ask.

goofball2k said:
It seems daunting but the first things you can do prior to the flashing are
Click to expand...
Click to collapse
I will definitely look into that thread! Quick question, what exactly is flashing? I know it has to do with modifying the operating system..but I honestly do not understand the purpose and benefit. Could you explain that to me?

Flashing is basically copying OS onto your phone and installing it.

Okay. So in this root you copy an OS with root permission?

cl_miller said:
Okay. So in this root you copy an OS with root permission?
Click to expand...
Click to collapse
Yes. With this method, you are basically putting a portion of the OS on that is already rooted. That is why it is important to make sure you have the correct versions.

Done?
I followed all of the steps provided in the link you shared, and believe that my device is now rooted! At least, I think and hope. How can I be sure? And if it was successful, what should I do next to make use of my root access?
Thanks again

You should see the SuperSU app. Open it, it may/should prompt you to update.
Otherwise, download root checker from the play store

Done! Now, are there any resources for what I can do next?