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
Related
[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/#
So I finally got my G2/Vision, I want to perm-root my G2. But I fail so much, I can't even put Visionary into my G2.... I downloaded Astro, but I need to place Visionary r14 in my SD, but I can't find a place to put it.
When I look in my SD through windows, it shows me a LOST.DIR, .Trashes, .Spotlight-V100, .fseventsd, .android_secure, Android, etc. etc. But I still can't find the spot to place Visionary, Help?
place it in that folder
ilikepu said:
place it in that folder
Click to expand...
Click to collapse
Haha, I figured I'd just dl it off the internet through my G2. It worked. Configured it.
Word to the wise, stay away from visionary. Use rage.
ddgarcia05 said:
Word to the wise, stay away from visionary. Use rage.
Click to expand...
Click to collapse
Whats the difference? And... What happens if I already used Visionary?
If you used Visionary and it worked for you, then that's great.
I also try and steer folks away from Visionary myself. Quite a few seem to end up with a lot of problems after using Visionary. The "rage" method of rooting is a lot more reliable, it's just that it looks a lot more "scary" to newcomers because there are commands you have to type in and run on your PC and phone. But if you read up on it, and ask questions if you don't understand, then follow the instructions carefully, you'll be fine - and even if rage goes wrong then you won't end up with a semi-brick, you just won't get root (until you fix the problem).
Ohhhh, Ok. Yeah I couldn't get Visionary to work until several tries. Took me a while. I was supprised I hadn't bricked my phone already. But now I'm pretty satisfied with CM 6.1 w/ MattedBlues theme. Sucks though I couldn't get it to work with Virtuous. I really like Sense alot more than the stock Rom (I consider CM 6 to be pretty stock)
Hope this helps!!!
steviewevie said:
If you used Visionary and it worked for you, then that's great.
I also try and steer folks away from Visionary myself. Quite a few seem to end up with a lot of problems after using Visionary. The "rage" method of rooting is a lot more reliable, it's just that it looks a lot more "scary" to newcomers because there are commands you have to type in and run on your PC and phone. But if you read up on it, and ask questions if you don't understand, then follow the instructions carefully, you'll be fine - and even if rage goes wrong then you won't end up with a semi-brick, you just won't get root (until you fix the problem).
Click to expand...
Click to collapse
+1 on the reliable and +1 on the scary!!!!
I am very new to Android,...I've only had my G2 for about 2 months...I ran Visionary temp root without issues (r10). When I tried to install in r14 to perm root, I encountered a myriad of errors, and decided not to root.
But I just couldn't give up on it....two weeks ago I got food poisoning, which rendered me useless and home bound, I decided to attempt it. I decided to use the rage method, but found that the instructions assumes that you know something about rooting. There are alot of people on this forum that are willing to help (steviewevie was one of them) to get you your through what ever hurdle you encounter.
Personally I found the rooting process very rewarding as I now have less of a vague idea of what is happening in my phone (ie not as lost as before).
Some of the basics:
- Install adb on your pc (not that scary), and read a bot on it...understand what some of the basic commands are trying to do. (see the rooting guide for those commands)
- set your path on your PC to point to the correct directory from where you are pushing (There are a few forums here that will guide you setup by step on how to do this)
-Follow the instructions to the T, and you should be ok.
Click here to go to the thread that these guys helped me while I going through the process. Post #4 makes reference to the path on your pc.
NOTE:This Path should point to the location where you have your adb tools and location of the files you are trying to push to your phone.
Post #17 goes step by step on what you need to do, and how the lines on the terminal should look like.
This is really not that difficult once you get your bearings, and for me it was a lot of fun...actually a little bored with the phone after having done this.
Put (SOLVED) in your thread title please.
Sent from my HTC Vision using XDA App
You all seem to suggest to not use visionary but use rage but from what I saw yesterday we had 2 "bricks" from people rooting with rage, compared to none from visionary
Lennyuk said:
You all seem to suggest to not use visionary but use rage but from what I saw yesterday we had 2 "bricks" from people rooting with rage, compared to none from visionary
Click to expand...
Click to collapse
Ouch! Really? So no method is any "safer" yet then? Was planning on return to stock then Rage today. I take it I can't update my radio without full radio s-off? Or can i"?
Sent from my HTC Vision using XDA App
ddotpatel said:
Ouch! Really? So no method is any "safer" yet then? Was planning on return to stock then Rage today. I take it I can't update my radio without full radio s-off? Or can i"?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
If you know how to read, you can safely root using rage. Just read over the instructions a couple times first.
If you know what your doing both methods are as safe as each other. From what I can see there is a larger margin of error using Rage, however its entirely in your own hands, so as long as you make sure you input it all correctly it should be fine.
Both "bricks" yesterday were recoverable, and both times the user was sure they followed it all correctly, it just seems that their rom corrupted during the process so ended up stuck on a bootloop.
blackknightavalon said:
If you know how to read, you can safely root using rage. Just read over the instructions a couple times first.
Click to expand...
Click to collapse
Lennyuk said:
If you know what your doing both methods are as safe as each other. ...
Click to expand...
Click to collapse
So we not talking about the random occurance of file corruption then?
Thank you both (i'll add the to your thanks meters when I have some available). Just need to find how to fully reverse the rage method if needed.
Lennyuk said:
If you know what your doing both methods are as safe as each other. From what I can see there is a larger margin of error using Rage, however its entirely in your own hands, so as long as you make sure you input it all correctly it should be fine.
Both "bricks" yesterday were recoverable, and both times the user was sure they followed it all correctly, it just seems that their rom corrupted during the process so ended up stuck on a bootloop.
Click to expand...
Click to collapse
Are you sure the corruption didn't stem from an earlier unsuccessful attempt to root with Visionary ?
I've yet to see a thread where someone has done something bad to their phone via rage, all it does is fire up a ton of process to use an exploit which gets you root. That can't corrupt your phone on its own.
Do you have some links ?
ddotpatel said:
So we not talking about the random occurance of file corruption then?
Thank you both (i'll add the to your thanks meters when I have some available). Just need to find how to fully reverse the rage method if needed.
Click to expand...
Click to collapse
Here you go.
Hi, I'm sorta a noob with rooting so bare with me. First, what version of visionary should I use to root my device? Will it work after the ota update? What are the chances of visionary bricking my phone or doing anything that would make my phone unusable? Will it put SU on my phone? And now for the main question, how will I get cyanogen on my g2? Thanks for any help!
Sent from my T-Mobile G2 using XDA App
As far as i know visionary is not gonna brick your phone ,in regard to changing your rom you also need to s/off your phone, and to do that you need to setup ADB on your computer i suggest you read this posts first ,you will find all the answers you are after
http://forum.xda-developers.com/showthread.php?t=857390
http://forum.xda-developers.com/showthread.php?t=855764
http://forum.xda-developers.com/showthread.php?t=835777
http://forum.xda-developers.com/showthread.php?t=532719
After you root and s-off your phone you need to setup rom manager so you will get clockworkmod recovery and you can boot in to that and flash a new rom or kernel through there.
and i am not sure about the question you had about the update.
yes you will get su after rooting.
Hwoarang747 said:
Hi, I'm sorta a noob with rooting so bare with me. First, what version of visionary should I use to root my device? Will it work after the ota update? What are the chances of visionary bricking my phone or doing anything that would make my phone unusable? Will it put SU on my phone? And now for the main question, how will I get cyanogen on my g2? Thanks for any help!
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Ok, first there are already many threads on this subject, so next time you should try a search first,
for example: http://forum.xda-developers.com/showthread.php?t=850141
http://forum.xda-developers.com/showthread.php?t=882546
Next the following links will help walk you thru rooting your phone using visionary r14. I have not had any problems with it, many people have rooted this way. If something goes wrong it is usually operator error. This method is for after the OTA. All needed files and links are in the video instructions.
Visionary has bricked phones before when not properly used, the videos show how to use it properly, use all the same settings in the videos.
This is the visionary method, but works perfectly when done correctly..
No adb needed.
Follow the videos to a "T", remove visionary and superusers from you phone if you already have them installed from a previous temp root before following the videos, start fresh, follow the videos starting with temp root then onto perm root then onto flashing a rom. Do everything just like the videos start to finish and you should have no problems.
Temp root first:
http://theunlockr.com/2010/10/20/how-to-root-the-t-mobile-g2-htc-vision-visionary-method/
Then perm root
http://theunlockr.com/2010/11/30/how-to-gain-permanent-root-and-s-off-on-the-t-mobile-g2-htc-vision/
Then flash a rom
http://theunlockr.com/2010/11/30/how-to-load-a-custom-rom-on-the-t-mobile-g2-htc-vision/
Remember don't assume you know how to temp root properly, follow all three videos start to finish and you should have no problems
Also the video "Load a custom rom" will give you a link to flash your first rom. There are a couple of choices to choose from.
Good Luck.
Editlease see post #32 in this thread for a testimony from someone who just followed the videos and rooted his phone.
Thanks soooo much!!! I have another question, how will I be able to get gingerbread after rooting? Or should I wait? Do I need to wipe my phhone? And what if I just want vanilla android with su and cyanogen?
Sent from my T-Mobile G2 using XDA App
Hwoarang747 said:
Thanks soooo much!!! I have another question, how will I be able to get gingerbread after rooting? Or should I wait? Do I need to wipe my phhone? And what if I just want vanilla android with su and cyanogen?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Everyones still waiting on gingerbread, but it looks like Cyanogen is in the lead for releasing it.
Any time you flash a new rom you need to wipe data/cache in recovery. Updates to the same rom a wipe is not needed.
As far as what you want in a rom, my suggestion is to start flashing diffrent roms and give them a try. I thought I didnt like sense but I am currently running a sense rom (Virtuous). So you dont know till you try.
1) Don't use Visionary. People have had brick after brick when using it. Use the rage method.
2) There's a beta version of CM7.0.0 out. The devs are still working out the bugs in it.
Sent from a Western Union telegram.
blackknightavalon said:
1) Don't use Visionary. People have had brick after brick when using it. Use the rage method.
2) There's a beta version of CM7.0.0 out. The devs are still working out the bugs in it.
Sent from a Western Union telegram.
Click to expand...
Click to collapse
1)Show me one brick from someone following the videos I posted and Ill take the links down. Yes a lot of people have bricked using visionary, but thats because they assumed they knew what they were doing when in fact they did not. Visionary causes bricks when not properly used, the videos shows how to use it properly. You must follow all the steps from start to finish including the temp root settings they use in the videos.
2)and yes there is a beta version of gingerbread out CM7 but Cyanogen did not officially release this version, and there are so many bugs in it I hardly think a noob needs to flash CM 7.0.0.
What exactly its the range method?
Sent from my T-Mobile G2 using XDA App
Hwoarang747 said:
What exactly its the range method?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Its Rage method and heres a link to the thread:
http://forum.xda-developers.com/showthread.php?t=834228&highlight=rage
I recommend you read this thread and make informed desicions, if you know how to use ADB, then this is another method. But if you dont the method I posted above is your other option, it doesn't require the use of ADB.
As far as ADB goes this is something I highly recommend learning, but we all know some people just dont get it. It took me a lot of reading and watching videos to understand ADB. Now that I know how to use ADB its pretty simple, but I remember when I first started with rooting ADB was like reading greek. But I really cant stress enough the importance of learning ADB.
Hahah sorry, i was using swype. And yeah, so what do you recomend, cause i really dont wanna brick my phone for its fairly new.
Oh, and another thing, if i root with visionary or rage, that only gives me root access. But if i flash a rom then i will also have cyanogen? And i was reading, since i wanna oc, whats this kernel stuff? Please forgive my noobish ways
Hwoarang747 said:
Hahah sorry, i was using swype. And yeah, so what do you recomend, cause i really dont wanna brick my phone for its fairly new.
Click to expand...
Click to collapse
I used the videos to root my G2, there have been a lot of bricks using Visionary but I have yet to see anyone say they followed the videos to the "T" and it bricked there phone. As for the Rage method, there have been almost no reports of bricks from this method, but I have seen a few bootloops (stuck on the HTC screen). It requires using ADB, so if your ok with ADB use the Rage method, if not, you'll have to weigh the risks based on your own ability. My suggestion, watch the videos, all of them and if its something within your skill range go for it.
Hwoarang747 said:
Oh, and another thing, if i root with visionary or rage, that only gives me root access. But if i flash a rom then i will also have cyanogen? And i was reading, since i wanna oc, whats this kernel stuff? Please forgive my noobish ways
Click to expand...
Click to collapse
Ok, get rooted first then you can worry about kernels, I believe Cyanogen 6.1.1 already comes with an overclocked kernel up to 1.42GHz. So all you have to do is flash CM 6.1.1 his latest release, then down load a cpu controlling app from the market like setcpu(which I use) or cputuner(free) and set the parameters you want your cpu to run at.
Thanks, but a boot loop is fixable right?
Sent from my T-Mobile G2 using XDA App
It usualy is you can boot in to recovery and wipe and flash another kernal or rom. Just have a look at the links that I posted ,you will get all the answers.
Sent from my HTC Vision using XDA App
Hwoarang747 said:
Thanks, but a boot loop is fixable right?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Not always hopefully if this happens you have gotten far enough along to put a recovery on your phone, or sometime you can stock recovery factory reset but if those options arn't there guess what you would have to have AndriodSDk installed on your computer with ADB, but you would have to do everything in fastboot mode which is giving commands from your computer to you phone. So it wouldn't be adb because you have to be booted into Andriod to use it, it would be fastboot and run commands similar to ADB, so for this purpose you would have to know how to use ADB. And even then no guarantees. So if you are looking for a guarantee you wont brick your phone there are none, and I wont give you one, these methods have been proven to work if you follow them exactly, mess up and you have a brick.
I know most people dont have $500+ laying around and I know I dont but for me the rewards far outweighed the risk. I just got a pm from another member that followed the videos and guess what he is rooted, he did it today. I asked him to post in this thread with his success story, so hopefully he will.
Here is a quote from him from my PM "it worked! i got so frustrated with adb, i gave it a shot and success!"
Edit: He just posted success his user name is robot_agenda and his post is #32 in this thread.
wait so what did he give a shot? the gfree method?
Hwoarang747 said:
wait so what did he give a shot? the gfree method?
Click to expand...
Click to collapse
He rooted his phone with visionary following the videos I posted.
and also, have you heard of the issue with visionary where the phone boots into recovery when being charged?
Hwoarang747 said:
and also, have you heard of the issue with visionary where the phone boots into recovery when being charged?
Click to expand...
Click to collapse
That has nothing to do with visionary, thats has to do with ClockworkMod recovery, if your phone is powered off and you plug it in to charge it boots into recovery, if you want root you have to deal with this issue untill they fix the bug in clockworkmod recovery. Also the phone shuts off fine unless its pluged in. Everyone with a htc vision phone who is rooted has this issue. as for me I charge my phone while it on so it doesn't bother me.
heres a link to the problem:
http://forum.xda-developers.com/showthread.php?t=884516
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..
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.