[DISCUSSION][SOLVED] ROOTING G2 Vision T-mobile

Status
Not open for further replies.
Search This thread

scrapin240

Member
Dec 8, 2009
45
2
Considering the overwhelming demand (they can't keep 'em in stock), I doubt returning the phone and trying to make the market speak will change HTC's mind. I was gung-ho about using this phone to replace my aging G1 (that's screaming with Froyo), but now I'm not so sure.

Also: if the T-Mo reps root their phones, are there any who frequent this board who can offer us some insight? Or do they have special G2s?

ur probably right, but they were talking about their other android phones, not their g2s.
 

ws.itguy

New member
Jun 6, 2010
3
0
Sacramento
Not true. Many ended up returning their Droid X's and I think that's why their "resale" value (if traded in to Verizon) is less than an Eris and definitely less than an Incredible.

The only vote the consumers have is with their wallets. Make a stink about it when you return it to the manager. The noisy assed Sunchips bags are finally being changed due to a small drop in sales :)
 

grankin01

Senior Member
Feb 9, 2008
973
658
Georgetown, KY
Which is the biggest disappointment for me. I love my HTC phone because of it's ability to be hacked. It's what differentiated HTC and other manufactures.

Unacceptable HTC :mad:

Don't give up. Anything electronic can be hacked whether physically or logically. Hell, a toaster oven could be hacked and made to do whatever it is you do with a hacked toaster oven.:rolleyes:

Plus, the "big dogs" are getting their hands on these devices now so it shouldn't be too much longer.:D
 

hansalvato

Senior Member
Feb 7, 2010
103
2
Don't give up. Anything electronic can be hacked whether physically or logically. Hell, a toaster oven could be hacked and made to do whatever it is you do with a hacked toaster oven.:rolleyes:

Plus, the "big dogs" are getting their hands on these devices now so it shouldn't be too much longer.:D

ive modded my toaster with a tegra 2 1 gig of ram 9.7 inch display but most amazing of all it knows when to stop so it doesnt burn my toast :)
 

lbcoder

Senior Member
Jan 21, 2009
2,613
98
Here is the boot and recovery imgs if still needed

http://db.tt/QjykG3F

I'll take a look at that and hopefully something will be interesting to look at.
Thanks.

I would guess that mmc1 is the second, "hidden" partition on the iNAND. According to the data sheet, the iNAND supports split, independently addressable partitions with various levels of programmable read/write protection.

What it looks like we need to be concentrating on are the CSD Register and the EXT_CSD Register. Pages 21-24 in that data sheet lists the parameters of the and what bits in the register control what.

I don't really know what I'm doing and they're are not for Android, but maybe there's some clues in these Linux drivers:

http://tomoyo.sourceforge.jp/cgi-bin/lxr/source/drivers/mmc/core/mmc.c
http://tomoyo.sourceforge.jp/cgi-bin/lxr/source/include/linux/mmc/mmc.h
http://tomoyo.sourceforge.jp/cgi-bin/lxr/source/drivers/mmc/core/mmc_ops.h

Are we sure that sdcard is mmc2 and not mmc1? I haven't seen any mmc2's in anyone's command outputs, and I would suspect that it should be visible in something... if mmc1 *is* the missing space, then that is a very good sign.
 

lbcoder

Senior Member
Jan 21, 2009
2,613
98
Considering the overwhelming demand (they can't keep 'em in stock), I doubt returning the phone and trying to make the market speak will change HTC's mind. I was gung-ho about using this phone to replace my aging G1 (that's screaming with Froyo), but now I'm not so sure.

Also: if the T-Mo reps root their phones, are there any who frequent this board who can offer us some insight? Or do they have special G2s?

Please don't fall for the marketing nonsense about having a hard time keeping them in stock.. it is 100% artificial, exactly the same way as the fruit company does it.
 

jtc442

Senior Member
Oct 4, 2009
517
21
49
Wellington, Colorado
Here is an email directly from HTC a few minutes ago.

"I understand how important it is to know the extent you can customize your device to and I appreciate your interest in software and development. HTC is not aware of any Root Kit or Blocking feature on the G2. It is quite possible such a feature was added by Google or the Carrier. Please be aware that third party roms even on our older devices do void the warranty on a phone and we can not support them. The only thing we would be able to do is direct you to some of the feedback sites and our support forums located at http://www.htc.com/ us/. We can only support the ROM that came on the device or updates provided at carriers request for a device."

Sent from my T-Mobile G2 using XDA App
 

lbcoder

Senior Member
Jan 21, 2009
2,613
98
Here is an email directly from HTC a few minutes ago.

"I understand how important it is to know the extent you can customize your device to and I appreciate your interest in software and development. HTC is not aware of any Root Kit or Blocking feature on the G2. It is quite possible such a feature was added by Google or the Carrier. Please be aware that third party roms even on our older devices do void the warranty on a phone and we can not support them. The only thing we would be able to do is direct you to some of the feedback sites and our support forums located at http://www.htc.com/ us/. We can only support the ROM that came on the device or updates provided at carriers request for a device."

That is a total load of horse crap since tmobile doesn't even have access to the hardware. It is 100% programmed by HTC.
 

vabovyan

New member
Mar 28, 2010
2
0
Timestamps on recovered files

What are the timestamps on recovered files? Are they same as old one or they are more current? If time stamp is current this means it may runs script to recover deleted. I don't have G2 to test.
 

ace42588

Member
Sep 7, 2008
32
1
lbcoder, here is my source for the mmc1 subject. this is from hendusoone's logs

Code:
[    8.499877] mmc0: No card detect facilities available
[    8.500457] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 8
[    8.500610] mmc0: Platform slot type: MMC
[    8.500823] mmc0: 4 bit data mode disabled
[    8.500946] mmc0: 8 bit data mode enabled
[    8.501068] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
[    8.501281] mmc0: Slot eject status = 0
[    8.501434] mmc0: Power save feature enable = 1
[    8.501647] mmc0: DM non-cached buffer at ffa0d000, dma_addr 0x2ac85000
[    8.501770] mmc0: DM cmd busaddr 0x2ac85000, cmdptr busaddr 0x2ac85300
[    8.502716] mmc1: Qualcomm MSM SDCC at 0x00000000a3000000 irq 96,0 dma 8
[    8.502838] mmc1: Platform slot type: N/A
[    8.503051] mmc1: 4 bit data mode enabled
[    8.503173] mmc1: 8 bit data mode disabled
[    8.503295] mmc1: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
[    8.503540] mmc1: Slot eject status = 1
[    8.503662] mmc1: Power save feature enable = 1
[    8.503875] mmc1: DM non-cached buffer at ffa0e000, dma_addr 0x2ac86000
[    8.503997] mmc1: DM cmd busaddr 0x2ac86000, cmdptr busaddr 0x2ac86300
[    8.504760] vision_sdslot_switchvdd: Disabling SD slot power
[    8.505126] mmc2: Qualcomm MSM SDCC at 0x00000000a3100000 irq 100,0 dma 8
[    8.505340] mmc2: Platform slot type: SD
[    8.505462] mmc2: 4 bit data mode enabled
[    8.505676] mmc2: 8 bit data mode disabled
[    8.505798] mmc2: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
[    8.506011] mmc2: Slot eject status = 0
[    8.506134] mmc2: Power save feature enable = 1
[    8.506286] mmc2: DM non-cached buffer at ffa0f000, dma_addr 0x2ac87000
[    8.506500] mmc2: DM cmd busaddr 0x2ac87000, cmdptr busaddr 0x2ac87300
[    8.506622] mmc2: Polling status mode enabled

[ 8.660003] mmcblk0: mmc0:0001 SEM04G 2.10 GiB

whats mmc1?
 

lbcoder

Senior Member
Jan 21, 2009
2,613
98
Anybody have an idea what this means:
Code:
#
#  Create a remote storage service in recovery mode if eMMC booting
#
service rmt_storage /sbin/rmt_storage /dev/block/mmcblk0p13 /dev/block/mmcblk0p14
    user root
    disabled

on property:ro.emmc=1
    start rmt_storage

Sure looks suspicious to me.....
That's from RECOVERY


And this:
Code:
devwait emmc@system
	exec /system/bin/e2fsck_recvy -p emmc@system
	mount ext3 emmc@system /system ro data=ordered
...
service rmt_storage /system/bin/rmt_storage /dev/block/mmcblk0p13 /dev/block/mmcblk0p14
    user root
    disabled
This is from BOOT


WTF is this "rmt_storage" service?

I'm thinking that this might be as simple as killing rmt_storage and setprop ro.emmc=0..... Anybody want to try that?
 

donboyfisher

New member
Sep 1, 2010
4
0
Looking at the dump listed above, the mmc1 has the line:

[ 8.503540] mmc1: Slot eject status = 1

while the mmc0 and mmc2 dont.

If mmc2 was the hidden area, then perhaps its being treated like a removable section of memory and access to it being controlled by simply forcing the value of the variable specifying whether its ejected or not.

If the area registered as being ejected, then the phone may simply make no attempt to access it.
 

ace42588

Member
Sep 7, 2008
32
1
i wouldnt get too caught up with the mmc stuff now that lbcoder found that reference to a rmt storage service. besides, if mmc1 was the hidden area, why is it set as 4 bit while everything else is 8? also, the eject status is just if the hardware can detect a card eject, i dont think its saying whether or not it is ejected.
 

lbcoder

Senior Member
Jan 21, 2009
2,613
98
i wouldnt get too caught up with the mmc stuff now that lbcoder found that reference to a rmt storage service. besides, if mmc1 was the hidden area, why is it set as 4 bit while everything else is 8? also, the eject status is just if the hardware can detect a card eject, i dont think its saying whether or not it is ejected.

Right. One step at a time. rmt_storage could very well be related to that mmc1. Maybe. Or maybe not. The first step is to get a persistent root.... which means that somebody who actually HAS this device has to try out.

Note that it may be necessary to setprop FIRST, and *then* kill the rmt_storage service. Would be nice if this is all it takes.
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Has anyone considered the possibility of a system.img that's being unpacked on boot? The root filesystem on our phones is unpacked from boot.img every time the phone is booted which is why there's trouble with the SGS and people rooting it by placing the su binary in /sbin...

    Back on topic, the root filesystem can be changed at runtime, but reboot, and it all goes away. That's what sounds like is going on with the G2, but I don't have one to mess with.