yashsingh1/xdaforums huggingface dataset:
[G2 and Desire Z Android Development] xile6:
Im just throwing this out there because I dont jnow much about all this. But once u gotten temp roit r u powering off the phone and rebooting to find the stuff in /system gone? Mybay if u temp root then pull the battery it my stick?

Im just thing that maybe a comman is sent to clear the system on shutdown? But like u said idk much about this an im kinnda half sleep right now
[G2 and Desire Z Android Development] Bavilo:
So where do these .zips come from? They surely aren't system dumps...they must have come from some T-Mo sources...

Also, do you guys have an irc channel set up for this? Would be a lot faster than xda...
[G2 and Desire Z Android Development] tubaking182:
Zips come from HTC at first, but later update.zip will come from tmo, I think that recovery reads tmo sig, and bootloader readts htc sig as I tried the shipped rom and it flashed from bootloader and not from recovery. I still think that finding a way to flash a custom recovery(once we have one) will be the way to go, even if we have to keep it as an update.zip for a while on sdcard until we flash the engspl we already have.

Once in a rooted recovery we should be able to make an update.zip for the engspl we have and apply through rooted recovery and move on from there with fully installed recovery and ROMs
[G2 and Desire Z Android Development] Bavilo:
So how did that limestar guy manage to flash the g2 rom on his desire z?

I must be missing something here...

If you are able to flash while in bootloader, and the update is signed from htc, why can't you flash hboot while in the bootloader?

Not having a G2 to try this on makes this a bit hard to understand....
[G2 and Desire Z Android Development] Bumble-Bee:
We can flash HBOOT in bootloader ..... only if it singed tho.

Root and System RW will come.

Can someone confirm that the computer doesnt detect the phone in FASTBOOT mode ? (boot into bootloder and select fastboot on screen)

As that test image may be singed still :-S if not we are out of luck.

----------------------------------------------------------------------------

Its quite possible as the Desire Z and G2 are praticaly the same HW, the roms are interchangeable and are singed the same. Unlikely that HTC did this but possible

-----------------------------------------------------------------------------​
[G2 and Desire Z Android Development] joackie27:
hendusoone used rageagainstthecage to gain temporary root on the G2

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

rageagainstthecage was also used to root Froyo on the Evo

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

Maybe you guys can tweak something from the Evo guide above to apply to the G2?
[G2 and Desire Z Android Development] Bavilo:
I'm pretty sure that the updates, that are floating around, are signed. So we just need to find a way to flash them like usual. What exactly isn't working when trying to apply the updates?
[G2 and Desire Z Android Development] rp1783:
The computer will not recognize the phone in fastboot.
[G2 and Desire Z Android Development] Bumble-Bee:
The EVO root uses a mathod of unlocking NAND where they have singed HTC images to start with.

No real help here
[G2 and Desire Z Android Development] Bumble-Bee:
OK bugger . . . . . .
[G2 and Desire Z Android Development] hendusoone:
I was able to get my computer to recognize the phone in fastboot. When installing the drivers, I had to manually select them, using "Have Disk" - I pointed it at the ADB driver, and from there, it installed and auto-detected the rest. That was yesterday... not at that computer now, and don't have dev tools on this one, so can't really test further for now.
[G2 and Desire Z Android Development] Bumble-Bee:
well if we can get fatboot to connect ....

anyone who can run

fastboot getvar all

post the results back :D

P.s.

I would do all this but i havent got a G2
[G2 and Desire Z Android Development] gariak:
INFOversion: 0.5

INFOversion-bootloader: 0.82.0000

INFOversion-baseband: 26.02.01.15_M2

INFOversion-cpld: None

INFOversion-microp: 0425

INFOversion-main: 1.19.531.1

INFOserialno: XXXXXXX

INFOimei: XXXXXX

INFOproduct: vision

INFOplatform: HBOOT-7230

INFOmodelid: PC1010000

INFOcidnum: T-MOB010

INFObattery-status: good

INFObattery-voltage: 4057mV

INFOpartition-layout: Generic

INFOsecurity: on

INFObuild-mode: SHIP

INFOboot-mode: FASTBOOT

INFOcommitno-bootloader: dirty-fafe9aa3

INFOhbootpreupdate: 11

INFOgencheckpt: 0

all: Done!
[G2 and Desire Z Android Development] Bumble-Bee:
wohhh awsome :D

now ill see if that leek HBOOT is any different
[G2 and Desire Z Android Development] tubaking182:
It seems we are going in circles, if we had a set of testers and posted what each step would be then we would be there, we have already stated repeatedly that if phone can be seen in fastboot we can flash an s-off spl and now we find out that fastboot worked for one person but he didn't test the hboot? Guys come on organize your thoughts and post then have testers trying different things and posting back what happened.
[G2 and Desire Z Android Development] joackie27:
The leak HBOOT has 0.76.2000 as it's version
[G2 and Desire Z Android Development] Bumble-Bee:
Right seeing as fastboot is working we can try flash the leaked hboot (if its singed it will flash).

It May be dangerous

anyone wants to help join #g2root on freenode irc
[G2 and Desire Z Android Development] Bumble-Bee:
From IRC

so nope that hboot is no good .....
[G2 and Desire Z Android Development] wrxtc714:
my question has been answered while I was writing my post

I should just hop on irc

see you guys there
[G2 and Desire Z Android Development] bfletcher6147:
Just wanted to say thanks to all of you guys in here. Im not a developer or coder (Just an Android fan. i dont understand all of the code posted) but love coming here and observing. Maybe pick up on a thing or too. G2 will probably be the first phone i root. This is exciting. Sometimes it makes me rethink my career choice. You guys are AWESOME!:D
[G2 and Desire Z Android Development] Jorsher:
I think updating the original post with methods that have been tried and why they failed would be helpful.
[G2 and Desire Z Android Development] wrxtc714:
Where did everyone go

All the posting just kinda died

where did everyone go
[G2 and Desire Z Android Development] unforgiven512:
I don't know about everyone else, but I'm at Walmart =D
[G2 and Desire Z Android Development] JoshHart:
Nevermind...
[G2 and Desire Z Android Development] sccpmusc26:
Without wireless tether I'm going to die!
[G2 and Desire Z Android Development] rp1783:
We'll get root.....give it time. The device hasn't even been properly released yet.
[G2 and Desire Z Android Development] sccpmusc26:
disregard please
[G2 and Desire Z Android Development] philosophics:
I really can't believe you just said that.

Can we please keep this on subject?

Thank you in advance...
[G2 and Desire Z Android Development] Bumble-Bee:
Has anyone tried this mathod to flash the test ralease ?

1) create goldcard

2) get the PC10img.zip the **test keys ralease**

3) Reboot into bootloader

4) fastboot reboot RUU

5) fatboot flash PC10img.zip

This will not flash HBOOT but if we can get a test key recovery on we may be able to use a fake-flash style recovery to root ?
[G2 and Desire Z Android Development] xspeed9190:
Fyi ...we got emails yesterday from upper management....g2 went on sale yesterday at 2 pm est
[G2 and Desire Z Android Development] thrice43:
What is the command to reboot into ruu from fastboot? I have gold card ready, and I have test key rom ready to go.
[G2 and Desire Z Android Development] themadbogart:
just did this:

goldcard,

reboot into RUU

flashimage flash recovery recovery.img (from PC10IMG - test.zip)

flashimage flash zip PC10IMG-test.zip

all failed sig checks. (did last step twice)
[G2 and Desire Z Android Development] sino8r:
Guys keep the sales talk in the general section, please.

Btw, the goldcard won't work. I tried it a couple ways already. We need a moddified eng. build or recovery at this point. I'm officiallly out of ideas besides that.
[G2 and Desire Z Android Development] Ryanmo5:
Its not relevant to this thread and is off topic so keep sales talk in general, stay on topic people.
[G2 and Desire Z Android Development] wrxtc714:
New File system info

I'm not sure if anyone has posted this yet

but to see where the recovery and boot .img actually are

open terminal:

cat /proc/emmc (enter)

this will show you where we actually need to write the recovery and boot to

not the mtdblocks that all of the other phones use

I beleive most people have tried flashing to mtd instead of emmc

if we flash the files to the right places then they may take.

there is a special partition that holds a recovery that is reflashed on shut down to remove any changes done. I'm not sure if flashing the recovery here will do it or if we need to find the location of the hidden recovery source and replace that one

I'll post a screenshot as soon as I connect to my other computer with DDMS

but for now anyone interested just type the commands above and view the results.

I am currently working on a custom recovery based on Amon's source since he is not responding to me about him making one for us himself.
[G2 and Desire Z Android Development] joackie27:
It's good that you're already working on the custom recovery. I think Amon_RA is attending the Android BBQ that is why he's not responding to your inquiries.
[G2 and Desire Z Android Development] tubaking182:
wasn't there another phone that reflashed itself on reboot? we could see how they overcame it. for some reason i think there was a phone but honestly can't remember.

as for recovery, what about flashing via /cache/recovery/command that way when the command runs it may flash recovery
[G2 and Desire Z Android Development] connoisseur:
Wait a minute flash on reboot? Does the 3 finger salute count as a proper reboot? Would that bypass the flashing?
[G2 and Desire Z Android Development] teferi:
it doesn't flash recovery on boot, the reference to that in init.rc is just cruft from the generic android image pre-customization - the script it references isn't even there on the G2.

Also, the set of commands that recovery takes is very small (you can look at it in recovery.git from AOSP), and it verifies signatures on anything you tell it to flash, whether from the menu or from the command file.
[G2 and Desire Z Android Development] soba5150:
There are a lot of files in system/bin that end in recvy I'm wondering if those are checking the changes or if they can be flashed with ones from the engineering version
[G2 and Desire Z Android Development] ChiefzReloaded:
U say the hboot is s-off? i can almost bet that means the recovery with it uses test keys or the whole thing wouldnt work... PPl are worried about s-off and we're just getting that finished for the slide... What i think u need to be doing is looking at a test key rec like the slide so that u can use an update.zip recovery at least to get in and flash a rooted rom... then u would have perm root just not s-off.... yet... ;) when i get one we will work on it!! Has anyone tried to symlink files after the temp root shell and using a modified mtd0.img to make the phone accept a downgrade?... Just a thought but thats how Eugene and I managed the first slide root via adb race condition.... Then nbetcher and I again with a temp root shell exploit aka exploid... Someone let me know how far u have looked into this... I have the exp to do this but have no way to get a handset in my hands so im at a loss... would love a G2 and love to get this poppin for ya guys but wish in one hand.... piss in the other? Anyways.... Im still willing to lend support and ideas as well as walk through steps with ppl that want to... Let me know... CR
[G2 and Desire Z Android Development] wrxtc714:
Chiefzreloaded all right

now we are seeing the people we need here

I very briefly tried a few symlinks

but I think I will look into more based on your recommendations.

You wouldn't happen to be in so cali would you?

I'd have no problem handing over my g2 to you for testing.
[G2 and Desire Z Android Development] Nainus Dextrous:
I would like to humbly offer my assistance-I already have my G2 and two more on the way. While I may not be a dev, I can follow instructions and report back. So to all who could contribute to this cause but don't have the hardware, feel free to hit me up and let me know what I can do with mine to help this along.

Thanks for all your hard work.
[G2 and Desire Z Android Development] ChiefzReloaded:
I was, I moved to Oregon... I just sent back a desire and 2 slides to ppl who sent them to me to work on lol... I am impressed at the trust ppl have then again am not a thief by any means, one of the worst things u can be imho... Anyway, no im nt in Cali anymore, middle of OR... tiny town... otherwise i would meet up w/you to work on it... I gt screwed on my pre order and thats why I cant get one... Not eligable for upgrade, no lines available for new line and def no 500 bucks... So im trying to find someone who needs a line yet nt the G2 so I can pay for it, get the handset and then give them a mytouch or slide or something so they still have a phone on that line... Anyways, back to topic... I have some ideas, i think we need to look at the slide s-off method, which none of u know about yet ;) and also, that chinese rom, for the test key rec... CR
[G2 and Desire Z Android Development] ChiefzReloaded:
U have one and 2 on the way?!... Can i hit u in the mouth pleeeeez.... Jealous* Okay sorry... I cant even get 1 myself damnit!! ;P Just kidding man, congrats.... I will let ppl know what i come up with, just gonna be hard cause i have never even seen 1 yet so im thinking blind... CR
[G2 and Desire Z Android Development] unforgiven512:
CR: if you'd like to work one-on-one with me, I'll set up a root sshd for you on my G2... Hack away, sir.
[G2 and Desire Z Android Development] PsychoI3oy:
if anyone gets (or think they have) a custom or otherwise test-keys checking recovery, here's something to try flashing

http://blargification.com/phone/update-cm-6.1.0-RC0-vision-signed.zip

it's named cm but is completely unofficial and unsupported and may not even boot. .md5sum file is in the same dir

and no, it won't flash in the stock recovery
[G2 and Desire Z Android Development] ace42588:
For the sake of not drowning the thread in reposts and red herrings:

If the phrase "I don't know if anyone has tried this..." appears in your post, stop. Read the thread. Reconsider your post. Your post should no longer have that phrase and wont waste space.

If the phrase "I don't know, but..." appears in your post, stop. Find out. The interwebz is amazingly useful for learning things. Reconsider your post. Your post should no long have that phrase and you will sound knowledgable and educated.

Please know this: files that have signatures CANNOT be modified. It changes the signature. You can take, break, and make anything you want using these files, but then the signature has to be spoofed. Also, flashing different anything typically requires a higher version number. Changing said version number will typically break the signature.

If you don't have any idea how an exploit is supposed to work, please don't suggest it. Look it up. If it sounds applicable to the G2, proceed to share.

Again, the most critical step at the moment is finding a method of write access that works.

EDIT: If you feel the need to reply to this post, please do so in a PM
[G2 and Desire Z Android Development] philosophics:
what's funny about your post is the fact that it's right after psychoI3oy's.

I don't think we need a crash course on posting, as long as we stay on topic. The way I see it is you can say whatever you want to as long as its respectful and on topic.

Carry on, I want to see the progress on getting this device rooted...
[G2 and Desire Z Android Development] wrxtc714:
+1

calm down ace

you shouldn't be calling shots buddy
[G2 and Desire Z Android Development] lbcoder:
Here's my theory on things as they are now;

The europe and north-america HTC VISION are IDENTICAL. They both have 4GB chips in them.

The difference is that in europe, there are different rules about misleading information, so when they publish the specs, they have to say 1.5 GB, which approximately matches the space AVAILABLE on the north-american VISION.

There is another bloody long thread about the missing internal storage; I believe that these two problems are RELATED. The missing storage, and the system writes not sticking.

It is pretty much confirmed now that the thing actually DOES have a 4GB chip in it. The total storage is 2.1 GB, which exceeds what would be available with a 2GB chip -- so it must be more than that, and the next size up is 4GB.

It also reports itself as a 4GB chip with a 2.1GB capacity when you look at the mmc stuff in dmesg.

So what is happening? That is still the question, but what appears to be going on (my theory) is that the writes that don't stick are actually going to the storage that is missing. MMC is more complicated to deal with than simple MTD. MMC has a much more capable controller typically for things like wear-leveling. But certainly it could be used to redirect writes into what amounts to a black hole.
[G2 and Desire Z Android Development] philosophics:
I think we should wait to see what the teardown confirms before we come to any final conclusions about the memory.

There's too many theorys and ideas but nothing concrete yet so once we find out what the text on the NAND chip says...

Besides, this is the wrong thread for that. This thread is about trying to get the device rooted!

You should copy/paste your post into the correct thread so the individuals who are looking for that particular information can find it. But don't end up with a double post either...
[G2 and Desire Z Android Development] xile6:
Ive been saying this for a awhile. there is a copy of the system and on reboot/shutdown it restores/cleans up the system partions.

So when we are temp rooting we are only writing to the temp system not the restorer part(main system). Its kinda like the dell laptops. There is a partion made just for restoring the windows incase something happens its also hidden from view and you need a program just to see it (i have a friend that builds/works on a lot of dells).

also seems to work like the live linux disc that you can make all the changes you wont but when you reboot its all flushed out and you have to start all over again.

MY though on it is that when you get an ota it get unpacked to the main system and then loaded into the temp system which is what the phone runs on normally. Also means sense on the file size of the nand because how the hell would you get 2.1gb on a 2gb chip? 3.7 - 2.1= 1.6/2 600mb for system 600 backup? sounds more like nexus one 512rom right?
[G2 and Desire Z Android Development] ace42588:
could this be why the phone is seen as offline while in recovery? access to real partitions arent available? some sort of flag could be set through usb. ota's would set the flag before reboot.

can anyone sniff the usb traffic to see if the phone is doing anything interesting?

its very doubtful, but there is an off chance it could be sending a simple challenge and not getting a response.

anyone poked around the radio to see if it does anything interesting with the address space?

best case scenario would be a ota to dissect.

and this is relevant to root. we have root, it just disappears after reboot. finding a location to write it to is the current challenge
[G2 and Desire Z Android Development] teferi:
no, that's totally unrelated. the phone shows up as offline in recovery because adb on your pc sees a device with the proper vendor and device ids, but not presenting an adb endpoint.
[G2 and Desire Z Android Development] ace42588:
okay. so is it too far-fetched for the for there to be a "magic" bit to be set somewhere to access the hypothetical, unseen areas of the nand? if so, what would be a good approach?
[G2 and Desire Z Android Development] theclueless:
the entire uncompressed os or snapshot could simply an image loaded onto the memory on startup, leaving only /data/ and settings paths as symlink in the image or in a mount partition table; this way it is much faster to boot and much easier to flush the changes made without affecting the system integrity, it could also explain the missing ROM space since they were reserved from the system image
[G2 and Desire Z Android Development] thrice43:
I know that if you use rom manager you can get a recovery.img to boot but obviously it won't flash due to the signature check
[G2 and Desire Z Android Development] cheyennewills:
So just to throw some fuel on the 2 Gig vs 4 Gig fire..

$ pwd

/sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/block/mmcblk0

$ cat size

4407296

$ cat device/name

SEM04G

$ df

/dev: 189916K total, 0K used, 189916K available (block size 4096)

/system: 413040K total, 190272K used, 222768K available (block size 4096)

/data: 1348920K total, 141072K used, 1207848K available (block size 4096)

/cache: 197144K total, 17756K used, 179388K available (block size 4096)

/devlog: 20336K total, 5812K used, 14524K available (block size 4096)

/mnt/asec: 189916K total, 0K used, 189916K available (block size 4096)

/mnt/sdcard: 15654144K total, 12852512K used, 2801632K available (block size 32768)

/mnt/secure/asec: Permission denied

$ cat /proc/partitions

major minor #blocks name

7 0 3150 loop0

179 0 2203648 mmcblk0

---

So I do have a SEM04G chip, it's 4 gig, but the mmcblk0 device is about 2 gig
[G2 and Desire Z Android Development] xile6:
4gb nand like i said :P

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

and it has the backup partions kinda like dells. so for rooting we will need to write to the backup part not the temp system that we used for temp root
[G2 and Desire Z Android Development] larryccf:
j0nkatz tore down his G2 and found the nand chip - it's a SanDisk SDIN5C2-4G 0352S0S07A

and it looks like we have 4G - check pg 24 of the below link sandisk doc

in searching for documents for a full descript on that part number, i found something that may serve the developers trying to root this phone, but it's not good news

"The entire iNAND (including the Boot Area Partitions, General Purpose Area Partition, and User/Enhanced User Data Area Partition) may be write-protected by setting the permanent or temporary write protect bits in the CSD."

hopefully, that "CSd" reference tells the developers where to look to see if they can root the phone permanently or fully

a general descript on the chip

"1.1. General Description

iNAND is an Embedded Flash Drive (EFD) designed for mobile handsets and consumer electronic devices. iNAND is a hybrid device combining an embedded thin flash controller and standard MLC NAND flash memory, with an industry standard e.MMC 4.411 interface.

Empowered with a new e.MMC4.41 feature set such as Boot and RPMB partitions, HPI, Background Operations and HW Reset the iNAND e.MMC is the optimal device for reliable code and data storage.

Designed specifically for mobile multimedia applications, iNAND is the most mature on board SD/MMC device since 2005, providing mass storage of up to 32GB in JEDEC compatible form factors, with low power consumption and high performance - an ideal solution for multimedia handsets of 2.5G, 3G, 3.5G and 4G."

both above quotes from http://omapworld.com/iNAND_e_MMC_4_4...1_0[1].pdf
[G2 and Desire Z Android Development] xile6:
Yea larryccf

dont forget this lil bit of nfo

2.4. Reliable Write

iNAND supports 512B reliable write as defined in e.MMC 4.41 spec6.

Reliable write is a special write mode in which the old data pointed to by a logical address must remain unchanged until the new data written to same logical address has been successfully programmed. This is to ensure that the target address updated by the reliable write transaction never contains undefined data. When writing in reliable write, data will remain valid even if a sudden power loss occurs during programming.

I believe that is the part that deleted the temp root.