Related
Good morning
I have:
LG G Pad 8.3 with LG's custom interface OS
Android version 4.4.2
Kernel version 3.4.0
Build number KOT49I.V50020b
Software version V50020b
Here is an image of the software information:
http://s30.postimg.org/taiyvu2k1/201...8_14_31_41.png
I have already:
The LG drivers installed and updated -
Rooted the G Pad with towelroot's tr.apk (many thanks to the guy who made that method!)
Root checker and SuperSU installed and verifying the device is rooted
Google USB drivers (after rooting, the device refused to be recognized through the USB - installing the Google USB drivers seemed to fix that, although occasionally it dissappears again and I have to unplug/replug the USB cable)
Google ADT Bundle (adt-bundle-windows-x86_64-20140624 - although to be honest, my knowledge of using this program is limited)
Flashify (and Rashr - uncertain which is best to use, although both look good)
My goal:
Install TWRP
Use TWRP to install Cyanogen Mod
I'm using Windows 7 64-bit. My G Pad has a micro SD card, which it can also write to (thanks to the G Pad being rooted). I'm a competent Windows and Android user, but by no means a hacker. If I want to upgrade or fix something, I read read read and try try try. But installing a new OS on my tablet is a new experience and I don't want to turn my tablet into a permanent brick! I have done all my homework, and think I know all the concepts, and generally the procedure. Now I just need the specific files and procedure for my G Pad.
My questions are:
1) Which TWRP recovery/boot image should I use to flash my device? (I tried a version, and briefly turned my G Pad into a brick! Fortunately I tried some power+volume combinations that I discovered, and that seemed to return to the original system.) My best options I have found seem to be:
http://forum.xda-developers.com/show....php?t=2551499
plus using step 3 here (a loki-exploitable ABOOT and TWRP)
http://forum.xda-developers.com/show....php?t=2698267
...or only:
http://teamw.in/project/twrp2/213
2) Do I need to use an aboot/loki file first? (Apparently 4.4.2 doesn't have a loki exploit? I'm a little unclear about this tbh.)
3) Can/should I use ROM Toolbox or ROM Manager?
4) If you try to flash a TWRP, and it doesn't work, does/can the device just return to the standard OS? (This is what seems to have happened with my G Pad.)
5) Should I wait until the community has more experience TWRP-ing and modding the G Pad Kit Kat 4.4.2, V50020b device? (There seem to be a lot of posts with people installing TWRP and installing another OS.)
Many thanks in advance. And while I am decent with computers and technology in general, I humbly ask to speak/explain it to me including steps you probably already know are obvious(!) - I don't want to miss anything, and it is probably not obvious for me, as this is more or less my first time! If I can make this question clearer, or can provide better information, I will update this comment. Again, many thanks in advance!
Sorry - no questions in this forum?
Looking at a post by an admin, it looks like there shouldn't be any questions here. I've put this post in the troubleshooting Q&A forum section...
i have the same device firmware... I have root access, but cannot install TWRP!
Any ideas?
look at this instructions, they worked fine for me
http://forum.xda-developers.com/showpost.php?p=53612227&postcount=3
notice step 8 that states to disconnect the tablet
Thanks
don_ernesto said:
look at this instructions, they worked fine for me
http://forum.xda-developers.com/showpost.php?p=53612227&postcount=3
notice step 8 that states to disconnect the tablet
Click to expand...
Click to collapse
Thanks for the link and information. I'll look at that carefully later. I want to be very careful (and know as much about what I'm doing as possible first) when I do this.
hmm... I believe I have the same build and software version as yours. I could recall a thread in the forums to flash the TWRP for the Korean version of the ROM, which actually worked fine for me. I have a SEA region tablet. If you still have issues, ill have a look when I get home.
jarod004 said:
hmm... I believe I have the same build and software version as yours. I could recall a thread in the forums to flash the TWRP for the Korean version of the ROM, which actually worked fine for me. I have a SEA region tablet. If you still have issues, ill have a look when I get home.
Click to expand...
Click to collapse
Thank you very much, I'd appreciate the link, and any extra info you could give. I don't know if I'll have time to try it this weekend, but I'm collecting all the pages and info I can over the next few days, and I'm looking for a free time in my schedule to try this thing.
Now I have 20d : /
Apparently LG saw fit to update last night, and now I have 20d!
Does this change anything?
Cause I was all ready to try to load TWRP with 20b on my tablet. Now it's 20d and I don't know if that messes everything up.
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.
Can I flash a new bootloader using recovery (twrp)? (flashed plenty of ROMs and Kernels wasn't sure if the steps are the same for a bootloader)
So if I plug my rooted Nexus 7(2013) in to any usb cable on any computer, it is just not detected(assuming usb port is dead at this point, only charges), Cannot even get adbd wifi to start and listen on port 5555 went through every possible scenario.( basically tried everything you can will throw at me, (MTP/PTP, usb debugging on/off, new cables, new computers, remove every possible android driver and re-install)
I saw one post where someone seemed to have a similar issue but was able to update the bootloader and his problem was solved!
Now I am not sure how he did it since I can't seem to find any good info on updating the bootloader directly from say TWRP I have no other access into the device remotely or via USB
kernelsandirs said:
Can I flash a new bootloader using recovery (twrp)? (flashed plenty of ROMs and Kernels wasn't sure if the steps are the same for a bootloader)
So if I plug my rooted Nexus 7(2013) in to any usb cable on any computer, it is just not detected(assuming usb port is dead at this point, only charges), Cannot even get adbd wifi to start and listen on port 5555 went through every possible scenario.( basically tried everything you can will throw at me, (MTP/PTP, usb debugging on/off, new cables, new computers, remove every possible android driver and re-install)
I saw one post where someone seemed to have a similar issue but was able to update the bootloader and his problem was solved!
Now I am not sure how he did it since I can't seem to find any good info on updating the bootloader directly from say TWRP I have no other access into the device remotely or via USB
Click to expand...
Click to collapse
Yeah it's possible, I did it for the Nexus 4 before. Usually the bootloader update files are found within the OTA zip updates. Usually the bootloader is composed of multiple files, not just one. You can take those files and put them in a flashable zip and make sure the script flash the files to the correct partition of the device, all the info are in the updater-script file in the zip.
It look like this is the last OTA update for the N7 that have the bootloader files: http://android.clients.google.com/p....signed-razor-KTU84L-from-KOT49H.df43279b.zip
So you can use make a flashable zip for those bootloader files or I can do it later.
I guess a smarter person would be able to dump these partitions from their device, maybe just by using "dd" command while in recovery's ADB.
I previously flashed a pre-rooted 4.4.4 OTA Stock ROM which is what I have been running ever since.
I really don't know if, or why the bootloader would affect my ability to use the USB port or not, but I guess I just had some hope based on one other post that seemed to work with.
I am not sure how to make a flashable zip from an existing ROM image, only flashable zips I made came from Titanium backup producing the flashable files for me
eksasol said:
Yeah it's possible, I did it for the Nexus 4 before. Usually the bootloader update files are found within the OTA zip updates. Usually the bootloader is composed of multiple files, not just one. You can take those files and put them in a flashable zip and make sure the script is flash it to the correct partition of the device, all these infos are usually found in the official OTA zip. The problem is not all OTA zip have bootloader files, just the one that specifically update it.
It look like this is the last OTA update for the N7 that have the bootloader files: http://android.clients.google.com/p....signed-razor-KTU84L-from-KOT49H.df43279b.zip
So you can use make a flashable zip for those bootloader files or I can do it later.
The next one will be for Android 5, so we'll look forward to that also. I guess a smarter person would be able to dump these partitions from their device or something.
Click to expand...
Click to collapse
So your computer doesn't recognize the tablet when it's at the bootloader? Can you even get into bootloader? Tried different cables? Different USB ports?
I can get to TWRP, but no usb not recognized there, cannot use the mount feature in TWRP, tried all items in pretty much every post I could find that were related, inlcuding the items you suggest yes.
Maybe something with the stock rooted ROM has gone wacky, Been very good to this tablet as far as babying the usb port, as I have had other devices have broken ports as my kids would yank cables etc.
So really the only thing I have not done since this trouble started was just do a factory reset and re-flash the ROM, just afraid that is something goes wrong durring flash I will be out of luck restoring anything since I cannot get to the filesystem to put new ROMS etc unless I download them to SD before I begin the process while I have access to the OS and wifi.
nhizzat said:
So your computer doesn't recognize the tablet when it's at the bootloader? Can you even get into bootloader? Tried different cables? Different USB ports?
Click to expand...
Click to collapse
[snip]
Thanks @eksasol I think I may just let this sucker chill until the stock rooted Lollipop ROM, I was already on 4.02 I just thought there was a newer one, I think the Lollipop version has a 4.04 bootloader.
I greatly appreciate your time on this.
So I would assume that if the flash fails for any reason I will be the proud new owner of a nexus 9 shortly after
@eksasol do you have a flashable 4.04 bootloader or know a guide to making a bootloader flashable, I did use your 4.02 and it worked great, but for the Lollipop version I need 4.04 but can only find .img that needs fastboot, which I do not have access to since USB does not seem to work still.
kernelsandirs said:
@eksasol do you have a flashable 4.04 bootloader or know a guide to making a bootloader flashable, I did use your 4.02 and it worked great, but for the Lollipop version I need 4.04 but can only find .img that needs fastboot, which I do not have access to since USB does not seem to work still.
Click to expand...
Click to collapse
You will need to wait until the OTA zip for KitKat to Lollipop become available, it will include the proper 4.04 bootloader files needed for flashing.
OK cool, guess I am just impatient
@eksasol any chance you can throw a flashable 4.04 bootloader together, i see several others looking for one that are in the same boat as me, i looked around for a tutorial on making one but did not find any so far. Anyway if you get a chance or have some info on making one i would be grateful.
Here is the Android 5.0 bootloader version 4.04. For Nexus 7 WiFi only (Flo, Razor), again it will check to see if it's the correct device before proceeding with flashing. Go to this link: http://forum.xda-developers.com/nexus-7-2013/general/flashable-factory-image-zips-android-5-t2939599
kernelsandirs said:
@eksasol any chance you can throw a flashable 4.04 bootloader together, i see several others looking for one that are in the same boat as me, i looked around for a tutorial on making one but did not find any so far. Anyway if you get a chance or have some info on making one i would be grateful.
Click to expand...
Click to collapse
You didn't have to remind me every single day.
Thanks for this. I'm alright with adb and fastboot (i.e. I can follow directions) but I'm running the Windows 10 tech preview and it absolutely does not support either. Drivers are fine, it just won't do it. Won't happen at all. Then I throw it all on a flash, take it to work (Win7 Pro), and it works just as easy as you like, so it's not (likely) user incompetence... I woulda waited but figured someone else might have asked. So, much appreciated!
dragontology said:
Thanks for this. I'm alright with adb and fastboot (i.e. I can follow directions) but I'm running the Windows 10 tech preview and it absolutely does not support either. Drivers are fine, it just won't do it. Won't happen at all. Then I throw it all on a flash, take it to work (Win7 Pro), and it works just as easy as you like, so it's not (likely) user incompetence... I woulda waited but figured someone else might have asked. So, much appreciated!
Click to expand...
Click to collapse
They decided to skip 9?
I posted the full device's image in flashable zip formats here:
http://forum.xda-developers.com/nex...shable-factory-image-zips-android-5-t2939599/
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
Hi all,
I have a zenfone 2 that I have just rooted....so now what?
Basically I wanted to optimise my phone so I am able to disable annoying notifications which are greyed out (although since rooting and checking this it still greyed out) I want to remove bloatware and I would actually like to customise my own android system, starting from a 'vanilla' base where I can build it up myself.
I have also read that I need to install a android recovery programme on asap after rooting.
So sorry about this but I really do need 'stupid' instructions as using hi tech words will just baffle me. lol
I have played around with computers in the past and learned about them so this is the phone stage now!
Thanks in advance and for your patience with this newbie!
Kerry
Yankeegal said:
Hi all,
I have a zenfone 2 that I have just rooted....so now what?
Basically I wanted to optimise my phone so I am able to disable annoying notifications which are greyed out (although since rooting and checking this it still greyed out) I want to remove bloatware and I would actually like to customise my own android system, starting from a 'vanilla' base where I can build it up myself.
I have also read that I need to install a android recovery programme on asap after rooting.
So sorry about this but I really do need 'stupid' instructions as using hi tech words will just baffle me. lol
I have played around with computers in the past and learned about them so this is the phone stage now!
Thanks in advance and for your patience with this newbie!
Kerry
Click to expand...
Click to collapse
Hi Kerry,
First thing you should now do after rooting your device would be flashing a custom recovery that is specific to your device (make sure your devices boot loader is unlocked first). This will allow you to make a backup of everything just in case anything were to go wrong, flash custom ROMs and useful zips. You can pick your favorite custom recovery such as Team Win Recovery Projects custom recovery (TWRP), Clock Work Mods custom recovery (CWM) or Philz Touch recovery based off of CWM although personally I would recommended twrp.
There are multiple ways to do this: Using the TWRP/CWM recovery installer from the play store or the more complicated way of flashing it from your computer. If you were to choose to install TWRP from their app on the play store (grant it root permission) you can select your device from the supported device section within the app, pick the latest recovery, hit the install button and let the app work its magic. If all works correctly you can now reboot to recovery and you will see TWRP is installed. Now you should create a backup to be on the safe side and you're good to go!
To best optimize your device I would recommend installing a custom ROM (look up custom ROMs for the Zenfone 2) and install the zip through recovery. (make sure to pick the right ROM for your device and version otherwise you may soft brick your smartphone) Now with a custom ROM you can better optimize your device and fully customize it to your liking. Make sure to look up custom ROM installation instructions for your device for better detail.
As far as removing system apps/bloatware you can use a "root app delete" tool from the play store but be careful what you remove as some applications are required!
Make sure to take your time and be careful when attempting any of these things and be careful what you modify! Just remember that no question is a stupid question as we all have to start somewhere!
Hope I was able to help you even if it was just a little, good look and have fun!
Rooted Droid Thanks you so much!!! First of all thanks for being so patient with me and secondly thanks for the useful (and easy to read) information.
I will go and install a back up on my phone from the ones you have suggested.
Hopefully you will be around over the next few days if I have more questions. Not planning on doing this all at once but rather taking the time and doing it right.
Thanks so much again!! :good::good::good:
Ooops sorry....how do I do this please?? ---> (make sure your devices boot loader is unlocked first)
Yankeegal said:
Rooted Droid Thanks you so much!!! First of all thanks for being so patient with me and secondly thanks for the useful (and easy to read) information.
I will go and install a back up on my phone from the ones you have suggested.
Hopefully you will be around over the next few days if I have more questions. Not planning on doing this all at once but rather taking the time and doing it right.
Thanks so much again!! :good::good::good:
Click to expand...
Click to collapse
Not a problem! I'm always happy to spread some knowledge and appreciate when people do the same to me! I also went ahead and checked the TWRP app and the Zenfone 2 is supported so it looks like your good to go. And yes absolutely, there's no rush so take all the time you may need and everything will go smoothly! I'm always around and will try my best to answer questions.
---------- Post added at 08:02 AM ---------- Previous post was at 07:41 AM ----------
Yankeegal said:
Ooops sorry....how do I do this please?? ---> (make sure your devices boot loader is unlocked first)
Click to expand...
Click to collapse
Check this site out:
http://myzen.asus.com/2015/10/13/official-bootloader-unlock-for-zenfone-2-is-now-available/
All devices have a different method for unlocking bootloader (some don't even have locked bootloaders) but this is an official bootloader unlocking method for the Zenfone 2 from Asus itself. I suggest following its directions and you should be able to unlock it this way.
Ok I followed the link but now I am confused. I have version ww_2.20.40.63_201......
Apparently I need a later version. What started off with just adding an APP means me doing other things before I even get to that point (hence the confusion! lol)
I never updated the phone via OTA as I was told it would invalidate my warranty and also I have killed a phone before using that so can you walk me through please...if you have the time....or could I just check if I have it unlocked already??
I haven't even gotten to the part where I create a backup...tee hee
Yankeegal said:
Ok I followed the link but now I am confused. I have version ww_2.20.40.63_201......
Apparently I need a later version. What started off with just adding an APP means me doing other things before I even get to that point (hence the confusion! lol)
I never updated the phone via OTA as I was told it would invalidate my warranty and also I have killed a phone before using that so can you walk me through please...if you have the time....or could I just check if I have it unlocked already??
I haven't even gotten to the part where I create a backup...tee hee
Click to expand...
Click to collapse
Hi sorry for the late reply, I'm in Canada so it was 2am when I was last talking to you so I went to bed haha. Anyway as far as unlocking the Zenfone 2's bootloader I wouldn't have experience unfortunately as I'm using a Nexus 5. The easiest way to go about this now would be to go to your device specific forum and find a way to unlock it there.
The following way to unlock the bootloader requires you have ADB installed on your PC. This is a guide for installation on Windows :
http://www.android.gs/install-android-sdk-adb-windows/
And here is a thread specific to unlocking the Zenfone 2 using adb:
http://www.xda-developers.com/asus-zenfone-2-bootloader-unlocked-without-asus/
BTW as you mentioned "updating may invalidate your warranty" things like rooting, installing a custom OS, unlocking the bootloader, installing a custom recovery and other things like that all (in most cases) void your warranty.
Sorry I can't personally help with the bootloader as I've not personally unlocked it on a Zenfone. Still feel free to ask any questions if you need to. Good luck!