Develop Bugs

[USB-BRICK] All you need to know about USB-Bricks

[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/#

[Q] {Q} ClockworkMod

now im coming from many other android related phones but what i remember most that may help....ima test this but i remember ClockworkMod Recovery being used for MT3GS.......we go into our stock recovery; click update.zip (which was the clockwork recovery) and it would boot up a recovery mode that way; has anyone attempted this?
....Just a thought towards root or atleast custom recovery

s0xpan said:
now im coming from many other android related phones but what i remember most that may help....ima test this but i remember ClockworkMod Recovery being used for MT3GS.......we go into our stock recovery; click update.zip (which was the clockwork recovery) and it would boot up a recovery mode that way; has anyone attempted this?
....Just a thought towards root or atleast custom recovery
Click to expand...
Click to collapse
The way I understand is the locked or bug in NAND will not allow for a recover. It removes all SU permissions on reboot.

Big Dawg 23 said:
The way I understand is the locked or bug in NAND will not allow for a recover. It removes all SU permissions on reboot.
Click to expand...
Click to collapse
i feel as if if we can get into fastboot and do modifications that way (thanks Modaco) why cant we go even further to be that a means of rooting; with appropriate scripts? why is it people are like *sigh* i have no root but i have temp root.......nand locked but i can do **** with android actually open; what if there was a way to initiate visionary on run.....before actual loading the os like the steps as
power on > visionary/turn into custom recov or custom boot like magldr is supposed to be> os?

This thread can't be serious.
Sent from my T-Mobile G2 using Tapatalk

unforgiven512 said:
This thread can't be serious.
Sent from my T-Mobile G2 using Tapatalk
Click to expand...
Click to collapse
so it cant be serious because i have an idea? that can help speed up the development for your phone? thanks guy

s0xpan said:
i feel as if if we can get into fastboot and do modifications that way (thanks Modaco) why cant we go even further to be that a means of rooting; with appropriate scripts? why is it people are like *sigh* i have no root but i have temp root.......nand locked but i can do **** with android actually open; what if there was a way to initiate visionary on run.....before actual loading the os like the steps as
power on > visionary/turn into custom recov or custom boot like magldr is supposed to be> os?
Click to expand...
Click to collapse
Have you contributed anything to the G2 root effort? Some of the best Android hackers are working to root this phone; in fact many of the same ones who came up with the method you posted in your first post.

im actually attempting but with any type of movement requires a brainstorming; so i was literally brainstorming outloud......i cant help if my ideas have been thought of you kno

There's a thinktank thread, it was posted there, it won't work.
Sent from my HDfied HTC Desire

Not trying to be rude, but present some facts. Try it out. Show us the code. Explain your findings. And present your idea in a clean, intelligent, organized manner. That means capital letters. That means punctuation. That means use the space bar.
I agree with, I'd say, ~90% of the other users here. All the useless crap in this forum is doing absolutely nothing towards getting actual development accomplished.
Mods: Please lock and/or delete this thread. Also, I apologize for wasting an entry in the SQL database. =P
Sent from my T-Mobile G2 using Tapatalk

well i have an idea; ima pursue it the clockwork mod has been proven to not work so ima attempt ; ima get this working even though i dont have contact with too many devs working on this phone

s0xpan said:
well i have an idea; ima pursue it the clockwork mod has been proven to not work so ima attempt ; ima get this working even though i dont have contact with too many devs working on this phone
Click to expand...
Click to collapse
Haha good luck. People keep posting about what should be done yet have no idea what actually goes on to do any of this stuff. It isn't as simple as "making" it, you have to know HOW to make it. Please go to the think tank thread.

thinktank thread is good but the WIKI is even better. I just wish it was updated more often -- but anyway this thing has everything short of #g2root irc
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Intro
READ THIS REALLY F*CKING CAREFULLY --- it is great reading. If you have ideas after reading it (i said read it dont glance it dont masturbate on it just read it as if it was your last will and testament) and then speak up.

Look not to rain on ur parade buddy but in order to do that on the mts you first had to install the enginering img to the phone that allows unsigned packages. Now since we have a copy of the eng img for the g2 (we as in the devs not me) and the phone will not let you downgrade to it so therefore the mts way of loading a custom recovery won't work. I traded in my mts to get my g2.

androidcues said:
thinktank thread is good but the WIKI is even better. I just wish it was updated more often -- but anyway this thing has everything short of #g2root irc
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Intro
READ THIS REALLY F*CKING CAREFULLY --- it is great reading. If you have ideas after reading it (i said read it dont glance it dont masturbate on it just read it as if it was your last will and testament) and then speak up.
Click to expand...
Click to collapse
Wow, I didn't even know this existed. Thanks mate!
As for OP, post this in the thinktank thread. Why did you bother making your own thread? You only had an idea, which is what the other thread is for. If you had tried it out and had success, then it may be a different story.

Don't post stuff here unless you get permission

[PATCH] Working Superuser/su for newer Sense ROMs

Anyone following the RUU threads already knows about this and it's starting to get more attention now. The latest official build of Superuser does not work with newer Sense ROMs (such as Vision 1.72+, anything released recently). HTC has started utilizing a relatively new feature of sqlite; a journaling mode called WAL (write-ahead logging). It's actually smart. WAL journaling should improve sqlite throughput, which represents a large amount of Android's IO and benefits applications across the board. The downside is it broke Superuser because it's actually special in its' use of sqlite.
WAL journaling, as built with these new Sense ROMs, is using exclusive locking. Why is this important for Superuser? It's the one situation where you have an application running within Android's process space and one outside of it, both accessing the same sqlite database. When su runs, it opens the sqlite database to check whether you have allowed access for said command to run. If not, a call is made to the Android application, which fires up and prompts you for an answer. Problem is, su has the database open with an exclusive lock (i.e. nothing else can touch it), so Superuser (the Android app) fails to open the database and cannot run. It'll either force close or do nothing.
To fix this, I have modified Superuser and su. Both changes have been submitted to ChainsDD for review. You can look at his git repository's pull requests to see the changes I'm proposing. I'm basically changing the journal mode being used by su one that is non-exclusive and Superuser to close its' database when sitting idle. I couldn't change Superuser's journal mode no matter what I did; it seems to be set deeper in the stack than I can access.
Here are the links to my pull requests on Github if you want to review the code:
https://github.com/ChainsDD/android_packages_apps_Superuser/pull/14
https://github.com/ChainsDD/android_system_extras/pull/1
Anyway, the end result is I have a working Superuser. Here are the caveats:
This is not an official build, so it's signed with my key, not ChainsDD. He has merged my patches into his Github repository so they should be making their way into a release soon.
I've artificially incremented the version number to 9.9.9, to make sure if you install my version, it'll "win" over any other installed version. Also, this prevents the Market from nagging you for updates.
I don't recommend using this version unless you must. In other words, you are on one of the Sense ROMs which is broken. Use an official build otherwise.
If you ran the RUU and have trashed your custom recovery (Clockwork), this isn't going to help you root the device again. Superuser is a tool for managing root access, not obtaining it.
If you are running Virtuous, you DO NOT need this.
Download Patched Superuser Flashable Zip​

great work rmk! but i still prefer to stick with your virtuous.

I'm trying to work around the no root available for 1.72 problem with my stock HTC Z rom updated to 1.72 OTA, but with Rage method temp-root I'm stuck with a frozen terminal after the 'Force Close' step, starting the terminal the 3rd time in the process. I've replaced the gfree_temp_root package's su file with the one provided here, used the APK provided here (pre-installed the apk too before the attempt). It's unfortunately stuck with a frozen black terminal window. Probably the Rage thingy doesn't work with the new 1.72 update, or am I using these files correctly at all?
(guide http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29 )

ChainsDD merged my patches into his repositories today so they should make it into an official release soon.

Nice! Is ChainsDD going to be changing Journal Mode himself?

thanks for this, confirmed working on DHD.

Just for a correct understanding:
I need to have root like described here to use SU right?
Or is it now possible to get the new Update via OTA and get root with this method and its a solution for rooting 1.72?
Thanks!

Dacoco said:
Just for a correct understanding:
I need to have root like described here to use SU right?
Click to expand...
Click to collapse
That's a DHD thread and this is the DZ/G2 forum. So you're either in the wrong forum, or looking at the wrong procedure (which could brick your phone).

Soo.... Us stock 1.72 people can root??

MacaronyMax said:
Soo.... Us stock 1.72 people can root??
Click to expand...
Click to collapse
There has been more than one report that rage doesn't work either, on the 1.72 ROMs.
Also, there's the issue of S-OFF that needs addressing, whether that can be re-done at 1.72.

I dont understand, or I miss some information. The 1,72 ROM is not patched yet (or what?).. Then. If I install 1,72 I will loose root. So in what cases I will need this patch?

denich said:
I dont understand, or I miss some information. The 1,72 ROM is not patched yet (or what?).. Then. If I install 1,72 I will loose root. So in what cases I will need this patch?
Click to expand...
Click to collapse
Check this thread - http://forum.xda-developers.com/showthread.php?t=886023
The patched su/Superuser is just part of the solution.

steviewevie said:
That's a DHD thread and this is the DZ/G2 forum. So you're either in the wrong forum, or looking at the wrong procedure (which could brick your phone).
Click to expand...
Click to collapse
Oh! You're right. I just followed some links. Okay thanks.

steviewevie said:
Check this thread - http://forum.xda-developers.com/showthread.php?t=886023
The patched su/Superuser is just part of the solution.
Click to expand...
Click to collapse
According to this- there is now root method to 1.72.. I don't understand, why this patch is needed if rooting 1,72 is not availeble?

denich said:
According to this- there is now root method to 1.72.. I don't understand, why this patch is needed if rooting 1,72 is not availeble?
Click to expand...
Click to collapse
Cause the Virtuous 0.8.X is build from the Egypt 1.72.X Release, if I understood it right

b1oh4zard said:
Cause the Virtuous 0.8.X is build from the Egypt 1.72.X Release, if I understood it right
Click to expand...
Click to collapse
Is the Egypt RUU rootable?
That could solve our problems!

&partialy working for me.. still creating read-only -wal and -shm files
here is an another solution: http://saraev.ca/su/
it is modified to "chmod" own databases - have a look at README file included
don't forget to grant permissions to superuser itself
EDIT: this is a dirty workaround, I hope someone can make it better...

seo said:
&partialy working for me.. still creating read-only -wal and -shm files
here is an another solution: http://saraev.ca/su/
it is modified to "chmod" own databases - have a look at README file included
don't forget to grant permissions to superuser itself
EDIT: this is a dirty workaround, I hope someone can make it better...
Click to expand...
Click to collapse
The one in your link is a dirty workaround for sure, it modifies baksmali code. Mine is working as intended. The wal and shm files are only present when you're actually sitting in the Superuser app. I'll modify the code some more to close the DB anytime it's not being read or written from. As it stands it's already rare to trigger a case where a request would fail.

rmk40 said:
The one in your link is a dirty workaround for sure, it modifies baksmali code. Mine is working as intended. The wal and shm files are only present when you're actually sitting in the Superuser app. I'll modify the code some more to close the DB anytime it's not being read or written from. As it stands it's already rare to trigger a case where a request would fail.
Click to expand...
Click to collapse
yeah i know that..

Hi,
This patch works only on Desire Z or I can install in my Desire HD?
Regards,

PSA: Rooting methods and recently discovered dangers

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

Confused

I just recently bought a G2 and updated its software...But I'm clueless where to start/how to root the phone. I looked through some stickies, but I got lost right away. Can anyone help or show me something a lot easier to follow? Thanks

Word to the wise, if the rooting process seemed too hard to do do not do it and stay stock, lot less risk of your phone bricking.

monkeytuner said:
I just recently bought a G2 and updated its software...But I'm clueless where to start/how to root the phone. I looked through some stickies, but I got lost right away. Can anyone help or show me something a lot easier to follow? Thanks
Click to expand...
Click to collapse
Just follow the guide in the wiki step by step, and remember to double check your typing before issuing ang commands
Sent from my T-Mobile G2 using XDA App

monkeytuner said:
I just recently bought a G2 and updated its software...But I'm clueless where to start/how to root the phone. I looked through some stickies, but I got lost right away. Can anyone help or show me something a lot easier to follow? Thanks
Click to expand...
Click to collapse
What software did you upgrade? You may have to downgrade to root, pay attention to software versions.
Sent from my shiny metal G2 w/ meXdroid V3

PaganAng3l said:
What software did you upgrade? You may have to downgrade to root, pay attention to software versions.
Sent from my shiny metal G2 w/ meXdroid V3
Click to expand...
Click to collapse
I'm on 2.2
Build number 1.22.531
Kerner 2.6.32.17
Hboot-0.82

Just follow the steps on the wiki like a member said. I had no experience whatsoever but managed to learn a little adb and successfully rooted my phone. Use the rage gfree method. It is simple with the least chance of bricking
Sent from my HTC Vision using XDA App

The Wiki guide is right here, if you haven't found it yet:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Just read up as much as you can before you start, and follow the instruction very carefully, and you will be fine.
The Gingerbread (Android 2.3) OTA that is currenlty being deployed is not currently rootable (and requires downgrading first to root), but you should be okay since you are still on the T-Mobile 2.2 ROM still.

What about doing this on Macs?

monkeytuner said:
What about doing this on Macs?
Click to expand...
Click to collapse
It should work on a Mac. Just dual boot into a Linux distribution.

Could someone post the Windows USB Drivers for the Vision?
The link is dead, and i couldn't find anything after I searched for it.
Can somebody also post T-Mobile G2 and HTC Desire Z: recovery-clockwork-3.0.2.4-vision.img (md5sum cbc776e7941ebf030e9fa39473d5b6f1)
? The link won't load, I'l borrow my friends windows to do this. Thanks so much!
Edit:
http://theunlockr.com/2010/11/30/how-to-gain-permanent-root-and-s-off-on-the-t-mobile-g2-htc-vision/
Will this method work after doing a temp root? It seems a lot easier

As far as the usb drivers go, I used pda.net from the market. If after you install pda.net it still sees your phone as usb mass storage only, then unplug your phone, remove the current driver and plug it back in. It should ask you if you want to set up your new hardware and show it as an android device
Sent from my shiny metal G2 w/ meXdroid V3

monkeytuner said:
Could someone post the Windows USB Drivers for the Vision?
The link is dead, and i couldn't find anything after I searched for it.
Can somebody also post T-Mobile G2 and HTC Desire Z: recovery-clockwork-3.0.2.4-vision.img (md5sum cbc776e7941ebf030e9fa39473d5b6f1)
? The link won't load, I'l borrow my friends windows to do this. Thanks so much!
Click to expand...
Click to collapse
Just download HTC Sync, it comes with the drivers:
http://www.htc.com/www/supportdownloadlist.aspx?p_id=325&act=sd&cat=all
There is a similar post about the Clockworkmod download. Might just be down temporarily. Try again later.
http://forum.xda-developers.com/showthread.php?t=1097465

Will the visionary method work too?

monkeytuner said:
Will the visionary method work too?
Click to expand...
Click to collapse
NO. And yes. Confused? Here is a link to the method myself and many others have used: http://forum.xda-developers.com/showthread.php?t=928160
This is an "easy" method using Visionary to temp root ONLY and then G-free for perm root. Do not be tempted to check "perm-root now" on Visionary since there is a high brick risk. Anyhow, this method runs scripts so much less chance for typo errors... just follow the simple directions to the letter and you will be rooted in no time. Works like a dream.

That was easy! hah, this was a lot easier than what the wiki told me to do. Thank you so much

edit:i restored to my back up (phew ), but why does the CM screen keep on repeating after I try installing 7.03?
i rooted everything fine, but after installing CM 7, the boot logo keeps on repeating, and the home screen won't pop up. is there a fix for this? :/

No prob.
Did you do a full wipe before flashing CM7? Even if you did, I'd recommend a "Superwipe". This is a zip you flash from recovery like anything else, and it really gets to everything on your phone's memory. I don't have the direct link but you can download it here:
http://forum.xda-developers.com/showthread.php?t=991254
It's down the page a bit, in the "attached files". The one on the top called SuperWipeG2+. Also, the ROM on that page is a nice one if you're looking for stuff other than CM. (Though CM is a good place to start)

I didn't do a complete wipe, I just did something else instead. I figured it out before checking this up, but thank you a lot for the help. +Thanks