yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Accessories] stuntdouble:
Yeah I agree it shouldnt happen. Just saying I think it is. Pretty sure there are guidelines and safety features that are applied to all power supplies to make them safe for use in the home, at least there are in the EU, and it seems these ones are in violation of those guidelines, even though they have the CE approved label. If you are smelling something burning/melting its obviously faulty and needs to be replaced.
[Eee Pad Transformer Accessories] bbilko:
Well I tried comet for the warrenty and was directed to the asus support line, which is closed today.

How dull.
[Eee Pad Transformer Accessories] elacris:
Is using the Desire charger just as slow at using a normal (5V) USB hub?
[Eee Pad Transformer Accessories] Geekbabe:
I'm no engineer but aren't there safeguards built into a charger/battery that is operating normally? ie: put TF on charger overnight, battery draws power till full then stops charging?

I use my TF all day, at night it goes on the charger, at no time does my charger get "hot" to the touch.
[Eee Pad Transformer Accessories] bbilko:
Information of PSU model with a known fault here:

http://xdaforums.com/showthread.php?t=1081435
[GT540 Optimus General] ali_alashery:
plz .......

i need arabic font of c7 (v2.3.3 or v2.3.4 ) to install it on v2.2 foryo ???

can anybody help me ???

thanx in advance ........
[GT540 Optimus General] lavero.burgos:
you have to pull the fonts from CM7 and push them to CM6 is very simple

In CM7:

cd C:\<sdk>\platform-tools
adb devices
adb remount
adb pull /system/fonts fonts

* This will pull all the .apk's located /system/fonts and save them into a folder that it will create in C:\Android-SDK\platform-tools named fonts

* If you already on CM6 and dont want to flash to CM7 just for the fonts then download Font_stock.zip from here:

http://www.mediafire.com/?4hfnalbconhxo

* I personally like Confortaa fonts which i use in all my soft-modded roms

In CM6:

adb push fonts /system/fonts

* This will push all the .apk's located in C:\Android-SDK\platform-tools\fonts folder to /system/fonts

Hope it helps, let me know how it went ( PM me )

For more information about How-to use adb tools, How-to's in general, tutorials, FAQ please clic on FAQ | LG GT540 Reference Thread located in my signature

Veronica
[Android Software/Hacking General [Developers Only]] mmoalem:
hi there all - my phone is the ZTE blade with SS5 rom.

i currently use the inbuilt call recording feature (pressing 'menu' once call connected, press record on the pop-up menu)

recording are currently saved on the root of the sdcard with a file name voicerecordingXXXXX.amr (Xs are digits)

I would like the file name to include time stamp caller number and if possible save it to a dedicated folder on the card rather than root but i cant find a way of changing the settings. can anyone help please?
[Xoom Q&A, Help & Troubleshooting] floridatank:
My battery usage lately has gone from being able to go at least a day and a half to less than a day. Is there any way to make it last longer or to see what is eating the battery.
[Xoom Q&A, Help & Troubleshooting] SteveEdson:
Have a look in Settings > Applications > Battery Use

it will tell you what is using the battery.
[myTouch 4G Android Development] jdkoren:
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.
[myTouch 4G Android Development] dacquesta1:
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.
[myTouch 4G Android Development] syl0n:
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?
[myTouch 4G Android Development] TeeJay3800:
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://xdaforums.com/showthread.php?t=858021. Follow that and you'll be fine.
[myTouch 4G Android Development] Towle:
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
[myTouch 4G Android Development] clem2595:
So thats a no on auto rooting. for me.
[myTouch 4G Android Development] Towle:
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
[myTouch 4G Android Development] TeeJay3800:
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?
[myTouch 4G Android Development] Onefast:
I didn't use gfree, just root.sh, and I've flashed 4 radios no problem...
[myTouch 4G Android Development] dacquesta1:
No issue flashing radios here. Never a single issue flashing roms radios recoveries anything.
[myTouch 4G Android Development] eliasadrian:
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.
[myTouch 4G Android Development] TeeJay3800:
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. :p
[myTouch 4G Android Development] Towle:
Sorry very bad wording on my part.

I guess I should have said radio s-off

Sent from my MyTouch4G running RoyalGinger 2.0
[myTouch 4G Android Development] dacquesta1:
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
[myTouch 4G Android Development] TeeJay3800:
Do I have the fastboot commands correct here?
[myTouch 4G Android Development] Jclintcox:
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
[myTouch 4G Android Development] dacquesta1:
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.
[myTouch 4G Android Development] dcwiker05:
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
[myTouch 4G Android Development] kimbernator:
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.
[myTouch 4G Android Development] dcwiker05:
I get an error fastboot flashing a new recovery in EBL too :(
[myTouch 4G Android Development] kimbernator:
We don't have a fix for that. Although I think you can format or remove partitions from the sd card through fastboot and re-make them... But i wouldn't be the one to ask about using fastboot. I've never use that or ADB.
[myTouch 4G Android Development] syl0n:
What I don't get it why is there partitions on the SD card?
[myTouch 4G Android Development] kimbernator:
Not sd card... my bad - the internal memory. wherever the recovery, cache, system, etc. partitions are.
[myTouch 4G Android Development] xdviper:
Dude, we can't adjust the partitions in the internal memory. We can only format them. I haven't been able to get in touch with most of the guys from the G2 irc channel because of work but I'll try getting more info.

If you guys can't do anything please join the irc channel #G2ROOT and let them know. Please, so we could find out what's going on.
[myTouch 4G Android Development] Kline:
My two phones (mine, wife's) are both gfree rooted. The Visionary method absolutely would not work on my wife's phone and I ended up having to swap it for a replacement. It worked after that. Then gfree came out and I did that on top of everything. Always been eng hboot and haven't had a problem yet with either phone (and we got our phones almost at release).
[myTouch 4G Android Development] xdviper:
Can you please post your emmc serial number? I have a thread on the general section, I'd post the commands now but I'm on my phone. But please, so we can determine if the bad ones have a certain chip that has a tendency to just randomly die.

Thanks
[myTouch 4G Android Development] mrmako777:
I assume this is only affecting you guys running custom roms? I'm running stock rooted with gfree and haven't had any issues
[myTouch 4G Android Development] KronicAnarchy:
Ok so if I rooted via gfree originally and haven't had any problems should I then unroot and re-root via visionalry method. I've flashed numerous ROMS etc. but no radios......yet, and I've never had an issue. Granted I've had some ROMS get stuck on splash screen but nandroid always brought me back. I mean when do these problems occur. Just randomly on reboots or..... only when flashing???
[myTouch 4G Android Development] neidlinger:
Hasn't effected me in the least. I've rooted SEVERAL MyTouch4Gs. I've used the Root.sh method, the ./gfree method and the Cyangoen method. All of them have worked flawlessly. And i flash ROMs more that most people take showers. Just this morning i went from eViL Sense 3.0 (1.0.3) > 1.0.6 > Cyangoen CM7N > 1.0.6. without problems.

People are wanting to blame the Recovery image and they are wanting to blame the rooting methods. I do not think the problems lies in either one. I see the problem laying in "Clockwork ROM Manager". I always wipe my OS via the recovery image, i always flash via the recovery image and i've never had a problem. I see tons of threads where people mention that they "flash via clockwork" then the problems begin. 99% if all the phones that clockwork is designed to work with are EXT3 ROMS. And most of all of the popular ones are EXT4. and it always happens when someone goes to EXT3 > EXT4 or EXT4 > EXT3. It feels/seems as if the Clockwork ROM Manager is reading the partitions correctly and screwing things up.

I be if people would realize that the App in of it's self is a waste and not needed and just used the Recovery Image these problems would go down. People want to use shortcuts and not every shortcut is the best option of their needs.
[myTouch 4G Android Development] syl0n:
how did you install clockwork recovery originally? did you use ROM manager? CM7 suggests you use ROM manager to install recovery.
[myTouch 4G Android Development] mike21pr:
well, ive had over a dozen android devices and pretty much any smartphone os so im no stranger to hacking and flashing roms. i indeed flash every rom using the recovery image and not rom manager and it still happened to me.... the ext3-ext4 thing makes sense though...

*rooted with gfree btw
[myTouch 4G Android Development] neidlinger:
originally? I did it standing in the T-mobile store even before i took the phone home. So i did it via the Clockwork ROM Manager application. But as soon as i got to work i loaded the Engineering hBoot and re-flashed just the image via hBoot. and updated them from that point forward via the hBoot screen.
[myTouch 4G Android Development] acsi007:
neidlinger, I flashed cwm 3024 thru rommanager after rooting gfree via the second main grankin01 thread, then flashed hboot085.

the only thing i've done is wiped the caches specified in the royalginger 1.6 thread, excatly as it spells it out there, and then flashed RG 1.6 itself. So far no problems.

I'm getting my moxy on now, and think I'm ready to start flashing more roms (evil d new one, orange 2.0, maybe royal ginger 2.1 when it comes out in a day)

so with more wiping and flashing, there's now the threat of a brick with failed -pu and the cant mount cache E: errors.

I do have 2 backups of the part7 file made by gfree, and 2 copies of the pd15img, but i'm in the "measure twice and cut once" mode right now-- i dont want to brick now that i will be much more flash active...

1. I never reflashed cwm3024 from hboot, just from rommanager as i said before, and that was before flashing royal ginger 1.6/ Should I be reflashing cwm3024 from hboot or adb now as a precautionary measure to ensure there wasnt some partition corruption i'm not yet aware of?

2. if so, which method? i.e.

http://xdaforums.com/showthread.php?t=852905

3. is it worth it at all to undo gfree and try root.sh re-root, just to avoid the fatal errors.

4. grankin01 has a reversal of gfree listed towards the bottom of the gfree root thread. Is that necessary when one uses the pd15img restore?

thanks
[myTouch 4G Android Development] neidlinger:
Good idea but one is all you need and once it's south from the looks of things it's south for good.

You can flash it from within the ROM it's just done a little differently.

You would just download the 3.0.2.4 image directly from Koush's website store it on the ROOT of your SDcard and type

adb shell
su
flash_image recovery /sdcard/recovery.img

that will flash it as well.

meh, you can use either one i just prefer doing it from the hBoot, but it's really a Coke v. Pepsi deal. Which ever you want to do... do it....

Their are thousands of people who have followed the ./gfree method and it work perfectly and will still continue to work. if you personally feel better unrooting then going back and doing the root.sh method then by all means go for it. Peace of Mind is worth alot ya know..

If you do not restore the file that you pull off the SDcard, flashing the PD15IMG will not restore s back to on. It will leave it off.
[myTouch 4G Android Development] irrelephant:
+1

I always do it from recovery, Rom manager is just there for me to use as a shortcut to get there!
[myTouch 4G Android Development] acsi007:
1. going on the assumption in granking's gfree thread, 'check this out even if' that gfree may bork a recovery, i think i need to reflash the recovery. i see the adb instructions you referenced- but can i do it thru hboot? and if so, what do i name the recovery-- img or rename it zip? (if renamed zip, do you actually have to zip it, or just rename the extension of the img)

2. "If you do not restore the file that you pull off the SDcard, flashing the PD15IMG will not restore s back to on. It will leave it off."

so rebooting to hboot with the pd15img on your sd card, WITHOUT undoing gfree first, WILL return you to s=on IF you simply include the part7 on the zip root? Or to get s=on, you really have to follow the undo gfree instructions in the grankin thread, and then do the pd15img.

3. im wondering if koush has some message boards that discuss this gfree/rom manager/cwm problem where some combination of these tools are resulting in failed -pu or cant mount cache bricks. maybe there's some cwm3.0.2.5beta floating around? or essentially koush should but this all back on gfree wrecking some parition allocation while rooting, because cwm3024 by itself is not involved at all in these errors.
[myTouch 4G Android Development] neidlinger:
1) Download the attached file and store just the .img to your folder from which you preform all of your ADB commands

2) plug the phone into the computer

3) boot the phone into HBoot

adb reboot bootloader

4) from the ADB commands change the drive to the folder where you stored the recovery image.

5) type these commands

fastboot flash recovery recovery.img

the screen should say something to the degree of

sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s

I think you are misunderstanding me, or i'm wording it wrong. If you do not revert the ./gfree root you will leave s-on after you've flashed the PD15IMG via the hBoot screen. If you want s-on you must undo the ./gfree.

I have no clue. With all the developers pumping out ROMs for this phone almost daily, and none of them having problems, it must be something we are doing on our end that we are overlooking. ... thats just my 2 cents
[myTouch 4G Android Development] syl0n:
Can you please explain to me what these backups are and how to make them?
[myTouch 4G Android Development] acsi007:
neidlinger, thanks.

just to clarify- so i should use adb to reflash cwm3024. and there's no way to use the "install zip" command from hboot to install a recovery? (i.e., can i zip the img and just flash it the same way i would flash a rom?)

or is the point that "install zip" from hboot would flash a revovery on the wrong partition, and that this command is only used to install roms and radios?

(no wait, radios are done by renaming the radio to pd15img, right?)
[myTouch 4G Android Development] kimbernator:
Flashing recovery through rom manager hasn't shown to cause any issues. Considering 99% of people use rom manager to get cwm, that is an accepted constant when we check for the cause of these issues. The only constant we have found for people who have this issue is that they used Gfree, and there have been possible explanations for why this could be. There is little to no refuting that the rooting method directly affects these errors.

There are some threads in the general forum asking for the serial number for the chip that supposedly dies, causing these errors. It could simply be that a batch of these phones came with factory defects in these chips and the danger lies beneath a few prerequisites. First, getting a defective chip, and second using gfree to root it.
[myTouch 4G Android Development] acsi007:
I'd like to think this is true, for peace of mind. Yet I see 4 of 5 senior devs here always say "better to do it thru hboot directly" for this kind of stuff...
[myTouch 4G Android Development] neidlinger:
I am by no means a dev. I'd love to be one but as of now i am not.

I always clean, flash, restore, backup with Clockwork Recovery Image. I do not do anything via Clockwork ROM Manager. I have a friend of mine who works for T-Mobile in New Mexico, and works in the Android department who warned me against such applications, when i got into Android to begin with. I was always told to do it the long way.

I just like how ./gfree has ALWAYS worked and alot of people have done it. Then all of a sudden we get some people popping their heads in here @ XDA, And i've yet to see 6 similar threads @ Android Central (by far the most popular Android specific forum). It could be a bad batch of eMMC, and i'm not contesting that. But to me, and in my eyes, its easy to blame something that we have no control over.
[myTouch 4G Android Development] kimbernator:
Im Not saying I use it to backup etc just using it to flash recovery images is pretty reliable
[myTouch 4G Android Development] _ice_:
The guy who said these problems occur because of ext3 and ext4 rom flashing. I totally agree with this because I have noticed these issues occurred while switching between ext3 and ext4 roms. Say if you flashed a ext 3 rom, you wipe everything but the partition still stays intact and cwm thinks its supposed to flash a ext 3 rom but rather you're flashing an ext 4 rom. That's when things break. And sometimes does not flash properly.

We should all get koush to take a look at this issue.
[myTouch 4G Android Development] Kline:
I no longer have the bad phone that root.sh/Visionary failed on. It was returned during the swap to get my wife's current (working) phone.
[myTouch 4G Android Development] acsi007:
I did this, and all I got was another # on my laptop in the shell. Doesn that mean it did it? There was no confirmation that anything flashed, and neither on the phone. USB debugging was ON, USB storage was OFF.

EDIT: UPDATE - didnt have flash_image installed I found out ( I though it would have it in royal glacier 1.6) so instead I used the second method here (fastboot)

http://xdaforums.com/showthread.php?t=919834

which was horribly easy.
[myTouch 4G Android Development] guhl99:
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):

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:

cat /proc/kmsg | grep mmc0

or

dmesg | grep mmc0

If you see output like (not necessarily in this order) :

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
[myTouch 4G Android Development] kimbernator:
So i put this in term. emulator and got SEMO4G

I assume that means i don't need to worry about this affliction then?
[myTouch 4G Android Development] acsi007:
guhl99 - here's my shell dialog output-

i have the M4G2DE emmc chip in question, unfortunately:

C:\adb>adb shell

# cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name

cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name

M4G2DE

#

then the following-- am I to infer that I don't have the problem then??

C:\adb>adb shell

~ # dmesg | grep mmc0

dmesg | grep mmc0

<3>[ 8.610168] mmc0: No card detect facilities available

<6>[ 8.610656] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 8

<6>[ 8.610870] mmc0: Platform slot type: MMC

<6>[ 8.610961] mmc0: 4 bit data mode disabled

<6>[ 8.611083] mmc0: 8 bit data mode enabled

<6>[ 8.611297] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz

<6>[ 8.611419] mmc0: Slot eject status = 0

<6>[ 8.611602] mmc0: Power save feature enable = 1

<6>[ 8.611724] mmc0: DM non-cached buffer at ffa0d000, dma_addr 0x0bc9a000

<6>[ 8.611938] mmc0: DM cmd busaddr 0x0bc9a000, cmdptr busaddr 0x0bc9a300

<6>[ 8.769500] mmc0: new high speed MMC card at address 0001

<6>[ 8.770690] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB

~ #

Oh, and for the record, I rooted gfree 0.2 "./gfree -f" after temp visionary11, then finished again vis11, using grankin01's "check this out even if" thread. no anomalies so far after flashing my one and only flash - royal ginger 1.6

Thanks
[myTouch 4G Android Development] tilt4life2:
I did this and I have the M4G2DE chip. Damn! Should i stop flashing? What should I do? :(
[myTouch 4G Android Development] kimbernator:
I've added this to the OP.
[myTouch 4G Android Development] cmdmilitia13:
Thanks for the good info..I have the good chip : ) should we still worry bout this affectin us @ some point in time?

Mytouch 4g-white

Permrooted s-off

Root Method-gfree

CWR-3.0.2.4

Rom-Royalginger v2.1

Kernel-Ckisgen~smartass~v1.2
[myTouch 4G Android Development] kimbernator:
It seems as if people with the good chip SHOULD be safe - I have it and I've flashed like 3 roms today alone.