[USB-BRICK] All you need to know about USB-Bricks
Fix here: http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/ or http://forum.xda-developers.com/showthread.php?t=691639
What is this thread for?
The main goal of this thread is to inform all Desire owners of the USB-Brick.
Especially the ones considering rooting / flashing ROM's.
And of course the people who have already bricked their phone...
There's many threads about rooting and current development on the matter,
but a thread that summarizes the issue was lacking in my opinion.
Index
What is this brick you're talking about?
How to recognize a USB-Brick?
When does this bricking occur?
Any numbers on this bricking?
I want to root and/or flash ROM's, what should I do?
I can wait, but for what?
I'm USB-Bricked what should I do?
Fix for SD Card and (maybe) Cellular Radio
Proxity Sensor Bug, never heard of it?
I'd like to return my device and want to flash an official ROM, how can I do that?
Disclaimer
This thread is useful, how can I help?
Sunday 30 May
Tuesday 1 June
Thursday 3 June Paranoid Rooting.
[*]What is this brick you're talking about?
The brick known as USB-Brick will mess up the USB Connectivity with the Desire.
How to recognize a USB-Brick?
Symptoms:
Unable to connect your phone using USB when booted into Android.
Unable to connect your phone using USB in Custom/Pushed Recovery.
FM Radio Malfunction.
Bluetooth Malfunction.
Wall charging doesn't start immediately.
Radio Malfunction. (Fix below)
SD Card Malfunction. (Fix below)
[*]When does this bricking occur?
Unfortunately it happens randomly. Some people experience it at their attempt at rooting,
others after 10 times of successful flashing. And there's people out there who have flashed
their device a 100 times and they're still fine.
Some people have blamed flaky USB Connections (through Cables and Hubs), others thought it was Apps2SD.
But it also occurs with all possible precautions and without Apps2SD, so noone really knows...
[*]Any numbers on this bricking?
On MoDaCo some guy named 'afiorillo' started gathering info from all flashing users.
This thread can be found here: http://android.modaco.com/content/h...-usb-disabling-bricking-issue-data-gathering/
'eVil D:' also started a poll in http://android.modaco.com/content/h...-or-legends-lets-get-a-count-55-and-counting/
but this thread is outdated.
This is the current poll: http://android.modaco.com/content/h...-or-legends-lets-get-a-count-66-and-counting/
[*]I want to root and/or flash ROM's, what should I do?
You can now, since the fix is out, make sure you backup the misc partition /dev/mtd/mtd0 in case it gets corrupted, it's very easy to flash the
original image back.
I'd suggest you use PaulOBrien's r5 rooting method. r5 added a nohup, which should prevent recovery from ending because of a flaky USB connection during flashing.
http://android.modaco.com/content/h...e-now-with-hboot-0-80-and-os-to-1-21-support/
ahmgsk released a different custom recovery http://forum.xda-developers.com/showthread.php?t=689778
This recovery supports wiping of ext partitions which is usefull for people using Apps2SD.
The method behind both recoveries is the same, so that might be because fewer people are willing to take the risk.
ahmgsk flashes over 30 times a day and his phone is fine. But this is no guarantee.
'ieftm' on XDA mentioned this command for linux
sudo ./adb-linux shell sh -c "nohup /sbin/recovery &"
See here: http://forum.xda-developers.com/showpost.php?p=6624079&postcount=81
And ahmgsk has updated his recovery script with this line.
[*]I can wait, but for what?
You can still wait for a safer recovery (one that doesn't corrupt the misc partition)
[*]I'm USB-Bricked what should I do?
Get it fixed, follow this link: http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
You have two options here; fix what you can and wait for a fix or you send your device back. If you chose the latter, they will most likely replace your mainboard.
You might want to revert to a non-rooted official ROM even though this won't fix your problem.
[*]Fix for SD Card and (maybe) Cellular Radio
Boot into fastboot. Open a terminal. Navigate to folder where fastboot binary is located (Android SDK or whatever you used for rooting your phone)
fastboot oem enableqxdm 0
Source: http://forum.xda-developers.com/showpost.php?p=6634033&postcount=115
[*]Now I have cellular reception, but in calls I lose the connection after a few seconds?
This is called the 'Proximity Sensor Bug'.
It's unknown if it's related to the USB-Brick or the ROM you were flashing.
[*]Proxity Sensor Bug, never heard of it?
It seems that due to this bug cellular connection is lost whenever the screen turns off.
But there's no fix for this issue. And only a small subset of the USB-Brickers
has this problem.
[*]I'd like to return my device and want to flash an official ROM, how can I do that?
You can find many official ROM's here: http://forum.xda-developers.com/showthread.php?t=677513
Check this thread: http://android.modaco.com/content/htc-desire-desire-modaco-com/307683/howto-unroot-your-htc-desire/
Be wary that you can't downgrade your bootloader.
[*]Todo
Proper formatting for the forum.
[*]Disclaimer
This summary is a result of me gathering information from both XDA-developers forum and MoDaCo forum + IRC for several days.
If you believe that something is wrong or missing, feel free to PM me so I can correct/add it.
[*]This thread is useful, how can I help?
If you're also into this issue, you'd do me (and many others) a favour by using this thread to keep us updated with interesting links to other topics, tweets or quotes from IRC.
Keep it short and simple.
[*]Sunday 30 May
ahmgsk updated his recovery with ieftm's recovery command line.
http://forum.xda-developers.com/showpost.php?p=6634416&postcount=3
[*]Tuesday 1 June
Integrated the fix into the whole story.
[*]Thursday 3 June - Paranoid Rooting
Since there's still no new recovery that prevents USB-Bricks from happening, I've added a few simple steps to the original rooting process to make it even easier when you brick your device the first time.
[-] Perform step 1 of the rooting guide.
[-] Boot your device as your normally would
[-] Check SD and USB functionality, if all is well, continue at [a]
[-] If you're already bricked, which is highly unlikely, continue at
Do the USB-Brick Fix, and save the working misc.img somewhere safe and skip [a]
[a] Backup your mtd0 / misc partition while it's still good, to do this, open a shell, become root by typing 'su' and then '/mount /sdcard' type: 'cat /dev/mtd/mtd0 > /sdcard/mtd0.img' to copy the contents of this partition into /sdcard/mtd0.img and save the proper misc.img somewhere safe.
[-] Continue with step2 of the rooting process and flash the rootedupdate.zip, or any other custom Rom.
[-] Happy flashing.
Very useful guide.
Thanks
-------------------------------------
Sent via the XDA Tapatalk App
Recovery Getting update
nothing major ->
just addition of ->
'ieftm' on XDA mentioned this command for linux
sudo ./adb-linux shell sh -c "nohup /sbin/recovery &"
Click to expand...
Click to collapse
Just rooted and i was about to flash froyo until i read this, it's not worth the risk i think i am just going to unroot and wait for a fix or the official update
oawalker said:
Just rooted and i was about to flash froyo until i read this, it's not worth the risk i think i am just going to unroot and wait for a fix or the official update
Click to expand...
Click to collapse
If you are rooted there is no point in un-rooting! You can't do any damage unless you are in recovery and flashing. Stick with your current rom and sit tight for a new recovery
There's no reason to unroot if you've successfully rooted. The only risk comes when actively flashing the device - i.e. you've already gotten past the part where you could have broken it. There's no reason to go back - just sit tight where you are until it's fixed.
Edit:\\ Wow, nice timing, sock. Great minds think alike.
as my firend say in upper case
very usefull guide,m8
10ks
pls continue with exelent job
Hi, I have a noob question: How do you restore the phone to an official rom after the brick if you need the device to be connected to a PC to run the.exe? (I m asking because I can hardly resist trying froyo, and if I can return my phone after the brick, I ll take the risk.)
bee55 said:
Hi, I have a noob question: How do you restore the phone to an official rom after the brick if you need the device connected to a PC to run the.exe? (I m asking because I can hardly resist trying froyo, and if I can return my phone after the brick, I ll take the risk.)
Click to expand...
Click to collapse
Details are in the first post here by Rudolfje.
[*]I'd like to return my device and want to flash an official ROM, how can I do that?
You can find many official ROM's here: http://forum.xda-developers.com/showthread.php?t=677513
Check this thread: http://android.modaco.com/content/ht...ur-htc-desire/
Be wary that you can't downgrade your bootloader.
Click to expand...
Click to collapse
You can connect in fastboot mode, where USB still works, and flash one of the official RUUs. This will completely restore the phone software-wise, but will not restore USB-related device function.
I'm going to bow out here for now and let you carry on Prof. lol. There is no point in us both answering the same questions, and I have to get my house in order for the mrs coming over
OK, thanks for the reply. I just wasn't sure if you can still establish some kind of USB connection after the brick. I m off to flash froyo then .
socktug said:
I'm going to bow out here for now and let you carry on Prof. lol. There is no point in us both answering the same questions, and I have to get my house in order for the mrs coming over
Click to expand...
Click to collapse
Hah, my fault. Have a good one.
Good luck, FroYo flasher!
recovery just got v1.1 -> now u can start recovery via pc
then remove usb
still recovery works
ahmgsk said:
recovery just got v1.1 -> now u can start recovery via pc
then remove usb
still recovery works
Click to expand...
Click to collapse
This sounds ideal, nice work, AHMGSK you are prolific with your work on the desire, the desire comunity would be far less interesting without you so thanks
Does usb-bricking only happens with Desire? or n1 is also prone to that?
The Desire and the Legend. The N1 has an easy unlock, there's no worries.
Lots of people are now attributing this bricking issue down to using a usb hub.... I heard up to 85 percent of people bricked are using hubs.
Any thing that might help is a step forward,
JD
JupiterDroid said:
.... I heard up to 85 percent of people bricked are using hubs.,
JD
Click to expand...
Click to collapse
really, is this true? can we ask anyone here who is bricked to confirm this - if you are usb-bricked just post a quick ' yes bricked using hub ' or not !
For numbers, check out this thread\post: http://android.modaco.com/content/htc-desire-desire-modaco-com/309615/all-users-usb-disabling-bricking-issue-data-gathering/#
Related
I've been getting a lot of requests from people, simply asking how I went about Rooting and Flashing new ROMs to my lovely G2 Vision. Well, I'm gonna make a guide with step by step instructions on how to do so. This Guide will teach you how to Root, Unroot, S-OFF (security off, to enable development), and how to Flash a new ROM to your G2.
NOTE!: I am NOT a developer, and i will only accept thanks for putting this information together, I did not create these instructions. Thank the individual developers/posters for their information!
WARNING!!: These procedures are not only dangerous if you don't follow them to the point, but also void the warranty on your phone!! Following these steps incorrectly can brick or otherwise damage your phone!! XDA-DEVELOPERS as well as MYSELF accept NO RESPONSIBILITY to what happens to your phone!!
Just in case you didn't get the message.. WE AREN'T RESPONSIBLE. HACK AT YOUR OWN RISK!!
I will do my best to help anyone along their way, but you've been warned. We aren't here to take the blame for a mistake, we're here to help you do what you're seeking to do.
Got it? Let's proceed, shall we?
First off? The Rooting!
ROOTING: Allowing the phone and it's softwares to have access to the "Root", or complete control, of the phone itself.
This procedure includes two major steps. Temporary Root and Permanent Root. The rooting process for the Temp Root will revoke itself after a reboot. The Perm Root method will not. The rooting process is not complete until the Perm Root process has been finished and the Root is still active after a reboot!
Temp Root the G2:
1. On your phone, go to Settings > Applications > Development > and make sure USB Debugging is ON (it MUST be ON) and make sure Fastboot is checked OFF (it MUST be OFF).
2. Visionary was removed from the Market, please download it from Here instead. Save it to your phone's memory card, then simply open it on your phone with any file manager app. (like Linda File Manager for free from the Market, for example) Find the visionary .apk file in the file manager and click it and follow the prompts to install it.
3. Install Visionary from Modaco.
4. Once installed, open Visionary and check ON Temp Root After Reboot, and check ON System R/W After Root. Then click TempRoot Now, and wait for it to finish. DO NOT CLICK ATTEMPT PERMROOT NOW! We'll get to that momentarily.
5. Once it is done, you have temp root and can use rooted apps without rebooting, OR continue to the next procedure to gain persistent root access.
Perm Root & S-OFF the G2:
An explanation of what S-OFF is and why you might want it - S Off means security off for your HBoot mode (aka Bootloader). The bootloader is what allows you to flash updates and write to the file system of your phone. By turning the Security OFF, we can flash any updates/ROMs we want without the phone checking to see if it is an official update or not.
Let's continue.
1. Download the rooting files: Right here.
2. Extract the files somewhere to your computer.
3. Plug your phone in via USB cable and mount the SD card so we can transfer files to it.
4. Copy the .ko and .img files from inside the extracted folder from step 2 to the root of your sd card on your phone (NOT in any folders, just on the SD card itself).
5. Unplug the phone.
6. Go to the Market on your phone and download/install Android Terminal Emulator (free).
7. Open the Terminal Emulator app and type the following with hitting enter at the end of each line (to get the touch screen keyboard to come up hit the menu button then toggle soft keyboard):
Code:
su
cd /sdcard
insmod /sdcard/wpthis.ko
*After typing the last line, you should see an error saying failed:
(function not implemented). If you DO see that, you have done it correctly
and can continue.
8. Now, type the following line in the terminal emulator hitting enter at the end of the line.
Code:
dd if=/sdcard/hboot-eng.img of=/dev/block/mmcblk0p18
[the last part is mmcblk(zero)p(one)(eight)]
9. After you have typed the dd line for your specific phone, it should say something was written etc. Now, type the following into the command prompt with hitting enter at the end of each line:
Code:
sync
10. After that is done, reboot the phone. When it boots back up, turn it off and back on holding down Volume Down and Power until the HBoot screen comes up. Confirm it says S-OFF at the top. If so, you have S-OFF.
11. Now, to get permanent root, turn the phone back on to get to the normal home screen.
12. Open Visionary and Uncheck TempRoot on Boot and click Temproot Now.
13. Then select Attempt Perm Root Now and the phone should reboot.
14. Once the phone reboots, open Terminal Emulator on the phone and type su and hit enter. If you get the # symbol, you have permanent root access and S-OFF!
Next? The ROM Flashing!
Alright, guys. If you've made it this far, You're golden. Grade A directions taker, In my opinion. Let's get to the last step, yeah?
Getting Recovery:
1. Once you have done the above to procedures, open the Market on your phone and search for ROM Manager (Free).
2. Install it.
3. Open the ROM Manager app and click Menu, then Settings and turn ON Delete Recovery.
4. Click Back and then select Flash Recovery.
5. Choose your phone model and then let it flash the recovery.
6. Click Reboot Recovery and you should be put into the custom recovery image screen. If so, you are all set.
Now, to Flash a Custom ROM:
1. Head over to theunlockr.com's ROM page here and choose your preferred ROM. Download it and save it to your computer.
2. Once it is saved, plug in your phone via USB cable and mount the SD card so we can save files to the sd card.
3. Copy the ROM's .zip file over to the root of the sd card (NOT in any folders on the sd card, just on the root of the card) (do NOT extract it, leave it as a .zip).
4. In the custom recovery screen, Backup/Restore and backup your current ROM.
5. Then select Wipe Data.
6. Then select Apply .zip from sd card and choose the ROM you downloaded earlier.
7. Once it is done flashing, click reboot system. Once it reboots, you are all set!
Congrats! You've flashed a new ROM to your G2! Hopefully..
There are some known issues out there, that prevent mostly the Rooting process. I'll touch on one of them real quickly.
The main issue I experienced was that I accepted and flashed the update that T-Mobile released to prevent Rooting. I've found an article on how to downgrade your firmware to pre-OTA, so that you can Root. Try this if you have severe issues trying to complete the Rooting process. Thanks to Apache14 for this info!
http://forum.xda-developers.com/showthread.php?t=831398
There's now also a process to UNROOT your phone! Here's the link. Thanks to David Cogen from theunlockr for all this information!!
http://theunlockr.com/2010/12/01/how-to-unroot-the-t-mobile-g2-htc-vision/
Thanks for reading, XDA friendlies, and Happy Rooting!!
Thnx for the link to the unroot man
Sent from my HTC Vision
No problem!
Sent from my HTC G2 using XDA App
Thanks for the effort. But I'm not sure what this is achieving other than duplicating the existing rooting guides in the dev forum.
Also this isn't a very up-to-date guide, it only seems to use one version of "wpthis.ko" and it isn't clear if this is for pre-OTA or post-OTA G2s. And it doesn't cover the DZ either, so it's not a "Vision" guide, just a G2 one.
The existing wpthis.ko was found by scotty not really to work properly anyway, and the newer gfree method of rooting (fully documented in the Wiki) is more reliable (though still does not work with all kernels). And you know Visionary hasn't been updated for months now, right ?
Sorry if this seems like I'm just trashing your guide, but I don't see how posting old information is going to help people ?
steviewevie said:
Thanks for the effort. But I'm not sure what this is achieving other than duplicating the existing rooting guides in the dev forum.
Also this isn't a very up-to-date guide, it only seems to use one version of "wpthis.ko" and it isn't clear if this is for pre-OTA or post-OTA G2s. And it doesn't cover the DZ either, so it's not a "Vision" guide, just a G2 one.
The existing wpthis.ko was found by scotty not really to work properly anyway, and the newer gfree method of rooting (fully documented in the Wiki) is more reliable (though still does not work with all kernels). And you know Visionary hasn't been updated for months now, right ?
Sorry if this seems like I'm just trashing your guide, but I don't see how posting old information is going to help people ?
Click to expand...
Click to collapse
It may be old, but I had yet to see a collective guide on xda developers' website about rooting, s-off, and flashing the 'G2' vision. In which I clearly stated this was for the G2. Not the Desire Z. This is the only method I knew about, and this guide was for a few select friends, and whomever else felt the need to use it. Its okay if you don't agree this post was helpful. But come on. This was the surefire way I used to root my G2, so I'm spreading the knowledge. Let not hate.
So visionary still works right?
Just checking before I go threw with this.
ijoshv2 said:
It may be old, but I had yet to see a collective guide on xda developers' website about rooting, s-off, and flashing the 'G2' vision. In which I clearly stated this was for the G2. Not the Desire Z. This is the only method I knew about, and this guide was for a few select friends, and whomever else felt the need to use it. Its okay if you don't agree this post was helpful. But come on. This was the surefire way I used to root my G2, so I'm spreading the knowledge. Let not hate.
Click to expand...
Click to collapse
Exactly, it's old. If you're writing a new guide, why use very old, out-of-date info, when you could easily provide the latest info (e.g. from the Wiki).
Yes, it's a collective guide, but one with old info in, so I don't see how that's helpful.
Your guide uses wpthis.ko, but makes no reference to G2s that might be running the original shipped ROM, or the OTA update. So this will only work on some of those phones.
Your article talks about something that T-Mobile did "to prevent rooting". I don't know where you got that information from, but it's not correct. T-Mobile did nothing to prevent rooting, because the OTA came out before root was fully achieved. It's just that the way of disabling NAND write protection needed to be done differently on the OTA (more as an accident than anything that T-Mobile did).
You refer to Visionary as a "sure-fire" way of rooting. Are you sure ? Have you seen how many phones have ended up stuck in a boot loop after using Visionary ?
Also, I find it kind of weird/interesting how your guide points people to another website to choose their list of custom ROMs. Why not point them to the dev forum on this site ?
Sorry but your guide is full of mistakes and out of date. You haven't even posted it in the right forum, this is the Q&A forum.
It worked for me. Bottom line, That's because i did it step by step and actually followed directions.
Old or not, IT WORKS.
If you want to make something better, then do so. Otherwise, silence your lout. Thank you.
Thank you for this write up. I was having problems getting my root to stick even though it was showing s-off but I followed your steps
10. After that is done, reboot the phone. When it boots back up, turn it off and back on holding down Volume Down and Power until the HBoot screen comes up. Confirm it says S-OFF at the top. If so, you have S-OFF.
11. Now, to get permanent root, turn the phone back on to get to the normal home screen.
12. Open Visionary and Uncheck TempRoot on Boot and click Temproot Now.
13. Then select Attempt Perm Root Now and the phone should reboot.
14. Once the phone reboots, open Terminal Emulator on the phone and type su and hit enter. If you get the # symbol, you have permanent root access and S-OFF
AND IT WORKS!!!!
You're welcome, fellow G2 owner.
Why don't you join my group, for those who love their G2? just check my groups in my profile, hopefully we can get a good set of owners together. You never kno what a mass of similar thinking people could accomplish!
Plus, i'm going to start posting some cool guide on how to further customize / enhance your device! Good stuff to kno.
Can i use this tutorial for HTC Desire Z?
Dimitri1992 said:
Can i use this tutorial for HTC Desire Z?
Click to expand...
Click to collapse
This tutorial was create for THE G2. I would NOT recommend you trying this method. Go around and search google for a tutorial MADE FOR YOUR PHONE. Although the phones are almost exactly alike, they don't necessarily mean they are exactly the same.
Find a different method.
Need help
This is not working for me. I temprooted my phone using visionary but when i try to use terminal to permroot, whenever i type "su" it say permission denied. Please help. I've been trying to do this all night and have been unsuccessful.
steviewevie said:
Exactly, it's old. If you're writing a new guide, why use very old, out-of-date info, when you could easily provide the latest info (e.g. from the Wiki).
Yes, it's a collective guide, but one with old info in, so I don't see how that's helpful.
Your guide uses wpthis.ko, but makes no reference to G2s that might be running the original shipped ROM, or the OTA update. So this will only work on some of those phones.
Your article talks about something that T-Mobile did "to prevent rooting". I don't know where you got that information from, but it's not correct. T-Mobile did nothing to prevent rooting, because the OTA came out before root was fully achieved. It's just that the way of disabling NAND write protection needed to be done differently on the OTA (more as an accident than anything that T-Mobile did).
You refer to Visionary as a "sure-fire" way of rooting. Are you sure ? Have you seen how many phones have ended up stuck in a boot loop after using Visionary ?
Also, I find it kind of weird/interesting how your guide points people to another website to choose their list of custom ROMs. Why not point them to the dev forum on this site ?
Sorry but your guide is full of mistakes and out of date. You haven't even posted it in the right forum, this is the Q&A forum.
Click to expand...
Click to collapse
Hmm...It is true that it is out of date but for me it works fine. I didn't use the wiki way cause it was to confusing for me and Unfrogivens method was working fine on me. Not saying this method is better or anything and I know this method is unsafe "if" you do not fallow what it says. Like always people try Gfree method 1st before trying this one...(Only for G2)
Sent from my HTC Desire Z/G2 Using XDA Premium App
lainvalenajr said:
Hmm...It is true that it is out of date but for me it works fine. I didn't use the wiki way cause it was to confusing for me and Unfrogivens method was working fine on me. Not saying this method is better or anything and I know this method is unsafe "if" you do not fallow what it says. Like always people try Gfree method 1st before trying this one...(Only for G2)
Sent from my HTC Desire Z/G2 Using XDA Premium App
Click to expand...
Click to collapse
When I rooted my DZ, I combined all referrences and guides
It was very hard at the beginning to understand the instruction, but after read and tried, it become easier to understand.. and I finally could root my DZ...
Cheers
Hello
Hello all totally new to android and was trying to root my g2. I followed instructions thourghly ( so i thought at least) and the s is still on after i exit the emulator and reboot. The last part about typing sync threw me off, how many times am i supposed to type sync while hitting enter after each line? Which lines, im sure overanaylzing something but didnt seem to work and tried multiple times. Thanks for your time..
To senior Mytouch 4gers:
Let's just start recommending the root.sh/visionary method to beginners and people who haven't rooted yet. It might not be the rooting method that causes issues but so far it looks like it plays a role in it. only gfree rooters have had this issue so far, so let's stay on the safe side, huh? just link this thread: http://forum.xda-developers.com/showthread.php?t=834225 and we can notify people later on about whether or not they should use gfree, as it's easy to use even after the root.sh method.
UPDATE:
It turns out that the rooting method may have little to no effect on this issue. Please read the bottom past the "update" title
Most of my data here will be pulled from http://forum.xda-developers.com/showthread.php?t=1074922 and similar threads.
Many of you probably have already read about this, but it has been becoming more and more common for people to get errors in recovery saying that certain partitions cannot be mounted, usually data and/or cache. The issue is that they cannot be re-formatted in recovery because the recovery partition is messed up as well.
Some people escape this using PD15IMG, but about 50% hit another error - Fail-PU in hboot when trying to use this. The only recovery here is available if you have the engineering hboot (Which at this point i would highly recommend you flash). without it, the phone is effectively bricked (I know, i know, not really bricked if you can get to hboot, but it's to the point that there is no recovery and the phone is unusable.)
We have narrowed it down to this: these errors only happen to people who used the gfree method to root. one (convincing) theory was posted in the previously linked thread by xdviper:
xdviper said:
Alright well I've been reading logs from G2_Root channel from April 26th and so on, and it looks like the G2 has two different types of the emmc chip. Gfree powers off this chip and then initializes the chip again in order to get around the write protection. I remember before we had root access on the G2 (before I traded for a mytouch) I would lurk around the irc channel and read progress. I remember having to get the chip to power on in order to get around the write protection.
Now it looks like while the phone is being used, or booting up and or trying tto read or write from emmc the chip suddenly dies. This is what causes us to get force closes, freezes and not being able to get past the splash screen and also explains the recovery not being able to mount partitions.
We're going to need people to join in the G2 channel preferably ones who still have their defective phones to get some data off it.
Again, this is a very vague summary of what I've been able to read off the irc logs.
Why the G2? Because we're using the same gfree method to root our phones and with our phones dying it makes sense.
I think, they have already ruled out recovery and the Eng hboot to be culprit but this is just too early in the game to determine.
Here's a thread from the G2 side, if anyone still has this problem with their cache not being to mount please check out post #13.
I'll look.around more and see what I find from the G2 side.
http://forum.xda-developers.com/showthread.php?t=1039504
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
In addition to (Hopefully) discovering the issue, we believe we have something you can do to lower your chances of being afflicted by this issue. IF you use the gfree method, reflash recovery a couple times, and hopefully it will work correctly. If you are not in need of a sim unlock, carrier unlock, whatever gfree does, use the visionary method with root.sh. At this point there are no documented cases of these issues happening with users that used that method.
Root.sh method:
http://forum.xda-developers.com/showthread.php?t=834225
Thanks for reading, have fun and be safe!
Mod: I feel it would be beneficial if this thread was stickied.
UPDATE
It turns out that the rooting method may have little to no effect having this issue, in a quote from Guhl99:
guhl99 said:
Hi !
After analyzing this issue a lot and also discussing this with scotty2 on #G2ROOT yesterday I would like to say that we can see no way how gfree could be causing this issue that effects the G2/DZ/DHD/MT4G.
We see that it seems to effect people that used gfree to radio S-OFF and root the phone but this is very likely only an statistical effect as gfree is the most used rooting method now.
The only thing that we know fur sure (or at least with a very very high probability) is that only emmc chips with the name M4G2DE are effected. You can find the name of your emmc chip by using the following command (in a terminal or adb shell):
Code:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
To be sure that you really are effected by the emmc issue (and not other partition corruption issues that show similar symptoms) you have to look at the kernel messages when booted to clockworkmod recovery. Do to this boot the phone into recovery and then (in and adb shell) issue the following command:
Code:
cat /proc/kmsg | grep mmc0
or
Code:
dmesg | grep mmc0
If you see output like (not necessarily in this order) :
Code:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
then you are effected by this issue.
Basically the emmc chip does not initialize any more after the first attempt to access it in write mode.
Based on our current knowledge this is a hardware issue and can not be cured. We will keep investigating this issue and welcome everybody to discuss it on #G2ROOT.
Have fun - Guhl
Click to expand...
Click to collapse
I looks like M4G2DE is the bad one and SEMO4G is the good one. We don't have any cases of other ones, but please post yours if it is different. Keep in mind we still aren't 100% sure about this being the cause, but it's very probable, as a logcat on booting in to recovery shows this chip dying. Also be aware that this is a hardware issue, no software can fix this. you have the bad one or you don't.
Also, it would be nice if when you post you would list these things:
1. what method of rooting you used
2. which version of hboot do you have
3. which emmc chip serial do you have
4. have you encountered this issue before
Let's not throw away the idea that the rooting method still plays a big role in this issue! please post any information you have about the partition errors and FAIL-PU errors! All information is welcomed!
If we're still not sure why it's happening, then how do we know reflashing recovery a couple times will fix it? The cause is still unknown, right? Cuz I've gfree'd several Glaciers and haven't encountered this problem.
i personally do not trust auto-rooting. I did the visionary and root.sh way of rooting and have engineering bootloader and have not had a single issue.
Wow lucky I read this. I need to SIM unlock my phone. Should I wait till this issue has been figured out? I am afraid I might brick my MyTouch 4G. I am not with T-Mobile and also not in the US, bought the phone off ebay, so can't really call them to get unlock code. Do i have any other options?
dacquesta1 said:
i personally do not trust auto-rooting. I did the visionary and root.sh way of rooting and have engineering bootloader and have not had a single issue.
Click to expand...
Click to collapse
Same here. Root.sh all the way.
Here is the method I used. Very similar to grankin's linked to in the OP, but slightly more simple: http://forum.xda-developers.com/showthread.php?t=858021. Follow that and you'll be fine.
Good to know! I rooted via the root sh method and have been considering doing gfree, not now!
Sent from my MyTouch4G running RoyalGinger 2.0
dacquesta1 said:
i personally do not trust auto-rooting. I did the visionary and root.sh way of rooting and have engineering bootloader and have not had a single issue.
Click to expand...
Click to collapse
So thats a no on auto rooting. for me.
clem2595 said:
So thats a no on auto rooting. for me.
Click to expand...
Click to collapse
Unless you need SIM unlock I would highly recommend the root . sh method. Go to theunlockr.com there is a very simple video guide in the "how to's" section.
Sent from my MyTouch4G running RoyalGinger 2.0
Towle said:
Unless you need SIM unlock or are planning on flashing radios I would highly recommend the root . sh method. Go to theunlockr.com there is a very simple video guide in the "how to's" section.
Click to expand...
Click to collapse
I know that the root.sh method isn't "true" S-OFF and that the radio's security flag is still technically "on", but does that mean you aren't able to flash new radios after rooting that way?
I didn't use gfree, just root.sh, and I've flashed 4 radios no problem...
Sent from my HTC Vision using XDA App
No issue flashing radios here. Never a single issue flashing roms radios recoveries anything.
Sent from my HTC Panache using XDA Premium App
TeeJay3800 said:
I know that the root.sh method isn't "true" S-OFF and that the radio's security flag is still technically "on", but does that mean you aren't able to flash new radios after rooting that way?
Click to expand...
Click to collapse
I've flashed a couple radios and I rooted the visionary/root.sh method. If I'm not supposed to be able to, I guess I got lucky.
Sent from my HTC Glacier using XDA App
It's still not clear whether you're "supposed" to be able to flash radios or not, but it seems to be working for everyone that has rooted with root.sh. I'll just blame you guys if I brick my phone.
Sorry very bad wording on my part.
I guess I should have said radio s-off
Onefast said:
I didn't use gfree, just root.sh, and I've flashed 4 radios no problem...
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Sent from my MyTouch4G running RoyalGinger 2.0
rooting the visionary method gives radio s=off...mine has been like that since i rooted and i have flashed all four radios and countless ROMs
dacquesta1 said:
rooting the visionary method gives radio s=off...mine has been like that since i rooted and i have flashed all four radios and countless ROMs
Click to expand...
Click to collapse
Do I have the fastboot commands correct here?
I also used the unlocker how to and worked great. Uses visonary and root. sh
Reply via MT4G Royal Ginger 2.0 on the #1 android forum app- XDA
TeeJay3800 said:
Do I have the fastboot commands correct here?
Click to expand...
Click to collapse
truthfully i do not know. i don't use command lines to flash anything. i just put radio images on the root of my sd card and go into the bootloader and flash it there and i flash roms from recovery...never any issues.
I have gotten this error for the second time on the same device...the first time I recovered by flashing a 2.x.x.x CWM in EBL and the formating cache in the old recovery, reflashing CWM 3.0.2.4 in EBL and I was all set after restoring a NANDroid. BUt the second I got the error I have tired everything so far and nothing gets it to go away, I cant even flash the old CWM in EBL I get an error in adb
Hey to all of you that are saying we don't really know the solution, im aware of that. The reflashing of recovery is merely the most we can do at this point. it won't save you, but it's a theory that can't hurt to try.
Sent from my HTC Glacier using XDA App
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.
I have a problem in Mobile (htc ADR6350), or what is called (HTC Incredible 2) almost
When you turn it on and then up to the slogan (HTC) and then restart frequently.
I'm doing tried scanning manufacturers (FACTORY RESET) or repair (recovery) of (HBOOT)
But as soon as you press the power button to select one of them the restart and so
Knowing There is a full backup
I hope you help me resolve this problem .... appreciate your cooperation and apologize for the bad translation.
system info:
vivo_w XB ENG S-OFF RL
HBOOT-0.96.200 (PG3210***)
RADIO-1.09.01.0722
OS Ver.-1.34.605.4
yshai1 said:
I have a problem in Mobile (htc ADR6350), or what is called (HTC Incredible 2) almost
When you turn it on and then up to the slogan (HTC) and then restart frequently.
I'm doing tried scanning manufacturers (FACTORY RESET) or repair (recovery) of (HBOOT)
But as soon as you press the power button to select one of them the restart and so
Knowing There is a full backup
I hope you help me resolve this problem .... appreciate your cooperation and apologize for the bad translation.
system info:
vivo_w XB ENG S-OFF RL
HBOOT-0.96.200 (PG3210***)
RADIO-1.09.01.0722
OS Ver.-1.34.605.4
Click to expand...
Click to collapse
Let me be the first to say this.
What?
Sent from my ADR6350 using xda app-developers app
FordNate said:
Let me be the first to say this.
What? [/QUOT
Okay, I agreed ... but, let's try to be helpful to OP whose native language is obviously not English.
I believed s/he is trying to say the device is doing an endless boot-looping and cannot get into Recovery - looking for help from us here.
OP, what carrier or home system (CDMA or GSM) are you using the phone on? Did it worked before? What were you doing with the device before this happened - trying to flash a new/different ROM, kernel or radio, etc. ??
You will need to learn and use ADB, read the sticky in this Forum and/or get someone familiar to help you with it. In the unlikely situation of being on Verizonwireless CDMA system, you can flash the RUU file and restore it to stock (unrooted) and start over - after getting it activated again & restore all the factory settings.
Click to expand...
Click to collapse
thanks Letitride,,,,help my
Letitride said:
FordNate said:
Let me be the first to say this.
What? [/QUOT
Okay, I agreed ... but, let's try to be helpful to OP whose native language is obviously not English.
I believed s/he is trying to say the device is doing an endless boot-looping and cannot get into Recovery - looking for help from us here.
OP, what carrier or home system (CDMA or GSM) are you using the phone on? Did it worked before? What were you doing with the device before this happened - trying to flash a new/different ROM, kernel or radio, etc. ??
You will need to learn and use ADB, read the sticky in this Forum and/or get someone familiar to help you with it. In the unlikely situation of being on Verizonwireless CDMA system, you can flash the RUU file and restore it to stock (unrooted) and start over - after getting it activated again & restore all the factory settings.
Click to expand...
Click to collapse
thanks Letitride
* yes....the device is doing an endless boot-looping.
* using carrier or home system (CDMA).
* What do you mean (ADB)?
* How do (flash the RUU file and restore it to stock (unrooted) and start over - after getting it activated again & restore all the factory settings.)
and Where did it get them?
please help my
Click to expand...
Click to collapse
yshai1 said:
Letitride said:
thanks Letitride
* yes....the device is doing an endless boot-looping.
* using carrier or home system (CDMA).
* What do you mean (ADB)?
* How do (flash the RUU file and restore it to stock (unrooted) and start over - after getting it activated again & restore all the factory settings.)
and Where did it get them?
Click to expand...
Click to collapse
It sounded like you are a complete newcomer to all this and you are going to need extra help to avoid bricking your device completely into a useless paperweight.
ADB is Android Debug Bridge, see the "Wiki" section above here on XDA and read about it, you can also google for details & how to.
Please answer, was your DI2 working before? Is (was) it activated on Verizonwireless? Was it working before this endless boot-looping?
To give you a very general idea of what is involved here, and it isn't simple but most of us learned it, sometimes - the hard way !! So be careful, very careful on what you are about to do !! If you are not confident or comfortable, don't even attempt to try & do it.
http://forum.xda-developers.com/showthread.php?t=2357721
http://forum.xda-developers.com/showthread.php?t=1876073
Do you have the HTC device drivers loaded & working on your PC? Does it recognize the DI2 when it is connected?
The links to the RUU might be broken but please answer the questions above and I will try to offer some suggestions on how best to proceed.
If all of these are "foreign" to you and you are completely lost, you need expert help instead of trying a DIY (Do It Yourself) ...
Click to expand...
Click to collapse
thanks mr. Letitride,,,,help my
Letitride said:
yshai1 said:
It sounded like you are a complete newcomer to all this and you are going to need extra help to avoid bricking your device completely into a useless paperweight.
ADB is Android Debug Bridge, see the "Wiki" section above here on XDA and read about it, you can also google for details & how to.
Please answer, was your DI2 working before? Is (was) it activated on Verizonwireless? Was it working before this endless boot-looping?
To give you a very general idea of what is involved here, and it isn't simple but most of us learned it, sometimes - the hard way !! So be careful, very careful on what you are about to do !! If you are not confident or comfortable, don't even attempt to try & do it.
http://forum.xda-developers.com/showthread.php?t=2357721
http://forum.xda-developers.com/showthread.php?t=1876073
Do you have the HTC device drivers loaded & working on your PC? Does it recognize the DI2 when it is connected?
The links to the RUU might be broken but please answer the questions above and I will try to offer some suggestions on how best to proceed.
If all of these are "foreign" to you and you are completely lost, you need expert help instead of trying a DIY (Do It Yourself) ...
Click to expand...
Click to collapse
I apologize for the delay ... Because of the circumstances
These answers your questions:
was your DI2 working before?
yes
Is (was) it activated on Verizonwireless?
yes
Was it working before this endless boot-looping?
yes
Do you have the HTC device drivers loaded & working on your PC?
yes
Does it recognize the DI2 when it is connected?
yes
Click to expand...
Click to collapse
yshai1 said:
... was your DI2 working before? yes
Is (was) it activated on Verizonwireless? yes
Was it working before this endless boot-looping? yes
Do you have the HTC device drivers loaded & working on your PC? yes
Does it recognize the DI2 when it is connected? yes
Click to expand...
Click to collapse
Here is a dropbox link to the OEM/stock RUU file released from VZW that I've saved & restored to dropbox from my collection - https://dl.dropboxusercontent.com/u....01.1111_NV_VZW1.92_release_225831_signed.exe
Please download this to your PC (linked file will be removed after 72 hours) - and prepare your DI2 by making sure it's 75% to 100% charged first. Make backup copies of your mSD card to a safe location, just in case.
Next, power on your DI2 and connect it to your PC via the micro-USB cable, then run or launch this RUU file. Read the warnings and click thru to run it - it will flash & restore your phone to factory fresh, stock condition and result in your DI2 being UN-rooted again. However, it will not change or affect SIM unlocking (if it was already done) - and, the process should take about 10 minutes or so, and when it is finished, power down & reboot the smartphone - and it should take you to the initial Startup/Setup Screen menu - follow it and get it activated again, including downloading the latest PRL from OTA.
When it is finished, you will need to follow the steps & guides to root it, install a custom recovery and SU, etc. Then, you can install your choice of custom ROM and/or kernet, etc.
The above approach is more fool-proof than using ADB to flash a different bootloader and to try to restore it to working conditions etc. with the tradeoff of losing root, which can be easily reversed again.
Let me know if you decided to go ahead and the results/outcome, etc.
Option #2 - If, however, you do not want to lose root and you can boot your device into Custom Recovery (CWM - not stock recovery) - use this link here - http://forum.xda-developers.com/showthread.php?t=1599767
Follow it & download the "Stock" PG32IMG from CS, copy it to your mSD card, boot into Recovery & flash the zip file - it SHOULD get your device backup and running again (it might NOT, I haven't done this in a while) and as long as you don't need to mess with the bootloader again (which might be corrupted or damaged, etc.) - you are good to go. Once it's up & running, you can restore & setup your APPS again - and/or install other custom ROM of your own choice, at your own risk, of course. But, make a CWM Backup first before doing so in between.
Good Luck & Regards !
i am havig troble with my HTc ADR350
my phone keep shutting down how do i resolve this?
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