Database Info

How to flash the G1

WARNING: Following these instructions may brick your phone, void your warranty and kill your dog. You don't want your dog to die do you?
Once I got root access on my G1, I've been messing around with trying to build reflash the recovery partition. That project is still in progress, but I have learned a bit about how to flash the various partitions on the G1.
First things first, you have to have root access. See this thread.
There are 6 mtd devices or partitions on the G1, mtd0-mtd5. They are located at /dev/mtd. You can use the /system/bin/flash_image tool to flash an image to any of these.
The syntax for the flash_image tool is:
Code:
# flash_image
usage: flash_image partition file.img
#
You can see a list of partition names and which device they are associated with by doing a "cat /proc/mtd".
Code:
#cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 04380000 00020000 "system"
mtd4: 04380000 00020000 "cache"
mtd5: 04ac0000 00020000 "userdata"
#
These should all be self explanatory, except maybe "misc", which just appears to have a few string values.. Not really sure what it's used for..
Before you do any erasing or writing, it's a "really good idea" (tm) to make backups of each of these. Even if you don't plan on writing to them. I had accidentally erased the bootloader partition (typed mtd0 instead of mtd1), which I'm fairly sure would have bricked my phone if I had tried to reboot it. Ugh! Luckily, I had created a backup earlier, so I was able to restore it. (And then was nervous as heck when I tried to reboot it... "Please boot up! Please boot up!")
To create the backups:
Code:
# cat /dev/mtd/mtd0 > /sdcard/mtd0.img
# cat /dev/mtd/mtd1 > /sdcard/mtd1.img
# cat /dev/mtd/mtd2 > /sdcard/mtd2.img
# cat /dev/mtd/mtd3 > /sdcard/mtd3.img
# cat /dev/mtd/mtd4 > /sdcard/mtd4.img
# cat /dev/mtd/mtd5 > /sdcard/mtd4.img
#
Now you can use flash_image to write the new image.
Code:
#flash_image recovery /system/recovery.img
#
And that's how it's done.
Update: You normally don't need to erase the flash before you write, as long as you don't corrupt the flash first, by trying to "cat" an image directly to the mtd device, like I did . If you get a lot of ECC errors when you use flash_image then you need to erase it
Code:
# cat /dev/zero > /dev/mtd/mtd1
write: No space left on device
#
On a related note, Based on my experience so far, the recovery partition is not critical to booting the G1. When I first tried this, I used flash_image to write a new image without erasing the partition first, and it corrupted it pretty good. When I tried to boot the G1 into recovery mode (power+home), it would go to the bootloader screen instead. But it would boot into normal mode just fine.
Additionally, I've verified that the device will boot into recovery mode if you screw up the boot partition (mtd2). So as long as you at least have a good recovery image *or* a good boot image, you should be able to get back in business. Just don't try to update both at the same time.
Even so.. be careful, and don't come crying to me when you brick your phone. Or if your dog dies. You don't want your dog to die do you?

Excellent work!
So if misc is the boot loader, it looks like it is roughly 266k. If you can dump it, have you tried to "open" the image and see if you can see files?
Now you have given me more ideas

readonly sdcard?
When I run: cat /dev/mtd/mtd1 > /sdcard/mtd1.img
I got this:
cannot create /sdcard/mtd1.img: read-only file system
I know I am root...

staulkor said:
So if misc is the boot loader, it looks like it is roughly 266k. If you can dump it, have you tried to "open" the image and see if you can see files?
Click to expand...
Click to collapse
Actually, now that I look at it.. I'm not positive that mtd0 is the bootloader. There's not much data there at all. Just a few strings in the beginning, then lots of nothing. Mostly all FFs, with a few blocks of 00s thrown in. It doesn't look like there's any code at all, so it can't be the bootloader.

Nice work. How about the signing? Does the image you flash have to be correctly signed this way?

blues said:
When I run: cat /dev/mtd/mtd1 > /sdcard/mtd1.img
I got this:
cannot create /sdcard/mtd1.img: read-only file system
I know I am root...
Click to expand...
Click to collapse
Do you have the sdcard mounted for USB access? If so, just unplug the usb cable and plug it back in. (don't select "mount" in the usb notification thingy that pops up)

Chainfire said:
Nice work. How about the signing? Does the image you flash have to be correctly signed this way?
Click to expand...
Click to collapse
Nope. This is a raw write directly to the flash device. The whole signing thing is only applicable to the OTA updates (or Update.zip style update).
But the other project I'm working on is to rebuild the recovery mode and disable the signature check for OTA/update.zip updates.

If you check out the SDK and build the open-source version for the phone, it builds a custom recovery-image that accepts only things signed with the testkeys - which is cool. Since the test keys are in the directory, you can easily resign the images yourself.
I know a guy who has done this now. I'll do it when I get a chance.
There are two proprietary files that you have to suck off the device in addition to the ones that the "extract_files" script in the android build pulls off - I sent in a patch to fix this but who knows if they'll apply it or not (I thnk they think that the crap in the msm7k dir will do something)
What I'm wondering is if we can write an update mode that will backup the contents of the /cache and /data to the SDCard - then erase the three partitions - then recreate /data as a huge partition and leave only 10 or 15 megs for /cache - because... well.. /cache is worthless since OTA updates aren't gonna happen to our phones anymore anyway. It would be nice to get an extra 40 megs for app storage.

JesusFreke said:
Actually, now that I look at it.. I'm not positive that mtd0 is the bootloader. There's not much data there at all. Just a few strings in the beginning, then lots of nothing. Mostly all FFs, with a few blocks of 00s thrown in. It doesn't look like there's any code at all, so it can't be the bootloader.
Click to expand...
Click to collapse
I just looked at my dumped mtd0.img and I see a few interesting strings:
T-MOB010
DeviceWarmBoot
CE Serial InUse
Debug Cable Ena
CE USB InUse
ClearAutoImage
And then a mountain of FFs, lol

You are right. I am on XP machine. So I disabled the usb storage, and it works fine
JesusFreke said:
Nope. This is a raw write directly to the flash device. The whole signing thing is only applicable to the OTA updates (or Update.zip style update).
But the other project I'm working on is to rebuild the recovery mode and disable the signature check for OTA/update.zip updates.
Click to expand...
Click to collapse
It works for me now.

RyeBrye said:
If you check out the SDK and build the open-source version for the phone, it builds a custom recovery-image that accepts only things signed with the testkeys - which is cool. Since the test keys are in the directory, you can easily resign the images yourself.
Click to expand...
Click to collapse
Yep, that's exactly what I'm doing. I'm planning on posting a recovery.img for others to use, since trying to build the thing from scratch is a pain, and takes forever.
RyeBrye said:
There are two proprietary files that you have to suck off the device in addition to the ones that the "extract_files" script in the android build pulls off - I sent in a patch to fix this but who knows if they'll apply it or not (I thnk they think that the crap in the msm7k dir will do something)
Click to expand...
Click to collapse
I assume you're talking about libaudio.so and librpc.so?
RyeBrye said:
What I'm wondering is if we can write an update mode that will backup the contents of the /cache and /data to the SDCard - then erase the three partitions - then recreate /data as a huge partition and leave only 10 or 15 megs for /cache - because... well.. /cache is worthless since OTA updates aren't gonna happen to our phones anymore anyway. It would be nice to get an extra 40 megs for app storage.
Click to expand...
Click to collapse
Good idea. Even better would be if we could put the installed apps and all data on the sdcard.. But that would probably be a harder modification than just resizing the partitions.

staulkor said:
I just looked at my dumped mtd0.img and I see a few interesting strings:
T-MOB010
DeviceWarmBoot
CE Serial InUse
Debug Cable Ena
CE USB InUse
ClearAutoImage
And then a mountain of FFs, lol
Click to expand...
Click to collapse
that partition is the config partition, standard HTC stuff.
T-MOB010 is your CID (carrier ID, spl checks this when flashing NBH), but it is only a backup copy of it, the real CID is in radio part of nand (protected!).
and the rest is just config stuff for SPL and radio. (yes HTC uses strings to set these configs - SPL reads the strings from specific nand addresses and decides what to do)

JesusFreke said:
On a related note, Based on my experience so far, the recovery partition is not critical to booting the G1. When I first tried this, I used flash_image to write a new image without erasing the partition first, and it corrupted it pretty good. When I tried to boot the G1 into recovery mode (power+home), it would go to the bootloader screen instead. But it would boot into normal mode just fine.
Click to expand...
Click to collapse
very nice stuff! have you been able to reflash a recovery.img then to fix the corruption?
and you are right about the boot order... it's : radio bootloader -> SPL (that tricolour screen is SPL mode) -> boot.img or recovery.img.
(if boot.img then the OS loads)

cmonex said:
very nice stuff! have you been able to reflash a recovery.img then to fix the corruption?
Click to expand...
Click to collapse
Yep. I screwed up the recovery partition and rebooted, and wasn't able to boot into recovery mode. It just went into SPL mode when I tried. Then I normal booted and re-flashed with the original recovery.img and rebooted, and was able to boot into recovery mode.
Thanks for the info on the boot order. I didn't realize the radio image was used for booting, I figured it was just firmware for the 3G chip or something.
I'm getting close to being able to apply my own update.zip style update. I've been able to reflash the recovery partition with a custom built recovery image that skips the signature verification. I'm having a touch of trouble getting it to actually install an update.zip though. It keeps saying "update script not found", even though there is a "META-INF/com/google/android/update-script" file in the zip. Arg! Anyways.. I'm in the process of tracking the issue down. More to come!

cmonex said:
that partition is the config partition, standard HTC stuff.
T-MOB010 is your CID (carrier ID, spl checks this when flashing NBH), but it is only a backup copy of it, the real CID is in radio part of nand (protected!).
and the rest is just config stuff for SPL and radio. (yes HTC uses strings to set these configs - SPL reads the strings from specific nand addresses and decides what to do)
Click to expand...
Click to collapse
Ah! Excellent info.

I was finally able to get the rebuilt recovery tool to work. The problem with the update.zip was due to the fact that the zip was built in windows, so it had the wrong path separators. It was looking for META-INF/com/google/android/update-script, but the zip file contained META-INF\com\google\android\update-script
After switching the slashes around in a hex editor, it installed the update no problem.
Next, I was tempted to try to flash the boot partition. I was somewhat sure that I would be able to recover from a bad boot flash, with my nifty new recovery tool. But after reading about the guy that bricked his phone (over in the root thread), I was a bit scared.
But I finally went ahead and decided to give it a try. You only live once, right?
So I opened up a root console, and just wiped the boot partition clean. "cat /dev/zero > /dev/mtd/mtd2" and rebooted. Palms sweaty.. breathing hard.. shaking.. Powered the phone on (without holding down home), and it comes up to the recovery tool. So far so good. Then I ran the update on the sdcard - it was a smallish update I had created before hand that just flashed the original boot image back to mtd2. Update runs fine.. phone reboots....
And it boots up normally.
yes!
*takes a big sigh of relief*
So now I can mess around with the boot partition, and know that I have that recovery tool safety net.
And now. It's time to sleep. *head hits the keyboard*

very cinematic good job mate!

Very nice work

Congrats on the successful flash!

strings in mda1.img include:
Code:
ANDROID!
no_console_suspend=1
-- System halted
ran out of input data
Malloc error
Memory error
Out of memory
incomplete literal tree
incomplete distance tree
bad gzip magic numbers
internal error, invalid method
Input is encrypted
Multi part input
Input has invalid flags
invalid compressed format (err=1)
invalid compressed format (err=2)
out of memory
invalid compressed format (other)
crc error
length error
Uncompressing Linux...
done, booting the kernel.
What are these images? Are they filesystem images that you could theoretically mount? If so, what filesystem (I haven't gotten anything to work).

How do I backup original images?

Hello,
I\'m getting ready to do the RC30->RC29->Android Dev SPL->ModRC30/ADP1 conversion of my G1, but I would like to know if there is any way to dump all three of the current images (spl, recovery.img, and the RC30 stock image) to my computer before I do this so that I can revert back to factory if I even need to.
Anyone know of a way to do that? Also, what sort of differences in the interface or reliability of the phone\'s services are there between the stock RC30 and the modified version? And how about with the G1 development builds?
Thanks ahead of time for answering, folks. I\'m still new to HTC hacking. I appreciate it.
damccull

using fastboot to restore your images

True. But how do I back up the images before I go through with the upgrade in the first place? Restoring is the second step, and from what I understand, fastboot isn't supported by the G1 stock bootloader.

hope this helps
By JesusFreke
How to flash the G1
--------------------------------------------------------------------------------
WARNING: Following these instructions may brick your phone, void your warranty and kill your dog. You don't want your dog to die do you?
Once I got root access on my G1, I've been messing around with trying to build reflash the recovery partition. That project is still in progress, but I have learned a bit about how to flash the various partitions on the G1.
First things first, you have to have root access. See this thread.
There are 6 mtd devices or partitions on the G1, mtd0-mtd5. They are located at /dev/mtd. You can use the /system/bin/flash_image tool to flash an image to any of these.
The syntax for the flash_image tool is:
Code:
# flash_image
usage: flash_image partition file.img
#You can see a list of partition names and which device they are associated with by doing a "cat /proc/mtd".
Code:
#cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 04380000 00020000 "system"
mtd4: 04380000 00020000 "cache"
mtd5: 04ac0000 00020000 "userdata"
#
These should all be self explanatory, except maybe "misc", which just appears to have a few string values.. Not really sure what it's used for..
Before you do any erasing or writing, it's a "really good idea" (tm) to make backups of each of these. Even if you don't plan on writing to them. I had accidentally erased the bootloader partition (typed mtd0 instead of mtd1), which I'm fairly sure would have bricked my phone if I had tried to reboot it. Ugh! Luckily, I had created a backup earlier, so I was able to restore it. (And then was nervous as heck when I tried to reboot it... "Please boot up! Please boot up!")
To create the backups:
Code:
# cat /dev/mtd/mtd0 > /sdcard/mtd0.img
# cat /dev/mtd/mtd1 > /sdcard/mtd1.img
# cat /dev/mtd/mtd2 > /sdcard/mtd2.img
# cat /dev/mtd/mtd3 > /sdcard/mtd3.img
# cat /dev/mtd/mtd4 > /sdcard/mtd4.img
# cat /dev/mtd/mtd5 > /sdcard/mtd4.img
#Now you can use flash_image to write the new image.
Code:
#flash_image recovery /system/recovery.img
#And that's how it's done.
Update: You normally don't need to erase the flash before you write, as long as you don't corrupt the flash first, by trying to "cat" an image directly to the mtd device, like I did . If you get a lot of ECC errors when you use flash_image then you need to erase it
Code:
# cat /dev/zero > /dev/mtd/mtd1
write: No space left on device
#
On a related note, Based on my experience so far, the recovery partition is not critical to booting the G1. When I first tried this, I used flash_image to write a new image without erasing the partition first, and it corrupted it pretty good. When I tried to boot the G1 into recovery mode (power+home), it would go to the bootloader screen instead. But it would boot into normal mode just fine.
Additionally, I've verified that the device will boot into recovery mode if you screw up the boot partition (mtd2). So as long as you at least have a good recovery image *or* a good boot image, you should be able to get back in business. Just don't try to update both at the same time.
Even so.. be careful, and don't come crying to me when you brick your phone. Or if your dog dies. You don't want your dog to die do you?
--------------------------------------------------------------------------------
Thats what i did befor i had root

humble said:
By JesusFreke
How to flash the G1
...
Thats what i did befor i had root
Click to expand...
Click to collapse
Wow, blast from the past . So did your dog die?

the past is what makes today
JesusFreke said:
Wow, blast from the past . So did your dog die?
Click to expand...
Click to collapse
yeah back then but good thing i had thoes back ups you saved me 4 & some change lol

humble, thanks for the repost. That helps. My phone is successfully flashed to JC's modded RC30 now. Hurray! Now what other neato things can I do to this thing? >
And JesusFreke, thanks for the mad cool images. I like the backup feature you and those other people hacked into the recovery mode. ALT-B for the win! How did you figure out how to dump those images in the first place? And then modify them for root? That's beyond my comprehension. Where would you suggest I begin to learn at?
-damccull

damccull said:
And JesusFreke, thanks for the mad cool images. I like the backup feature you and those other people hacked into the recovery mode. ALT-B for the win! How did you figure out how to dump those images in the first place? And then modify them for root? That's beyond my comprehension. Where would you suggest I begin to learn at?
-damccull
Click to expand...
Click to collapse
It depends on your current level of expertise . If you're a programmer, go check out the source, there's tons of useful info. But really, it's just a matter of trying to figure out how it all works. Playing with it, breaking it, fixing it.. you get the idea

Your Welcome
damccull said:
humble, thanks for the repost. That helps. My phone is successfully flashed to JC's modded RC30 now. Hurray! Now what other neato things can I do to this thing? >
-damccull
Click to expand...
Click to collapse
i always try to help now your on a modded image Woot!Woot! enjoy

JesusFreke said:
It depends on your current level of expertise . If you're a programmer, go check out the source, there's tons of useful info. But really, it's just a matter of trying to figure out how it all works. Playing with it, breaking it, fixing it.. you get the idea
Click to expand...
Click to collapse
Hmm. I am a programmer. I'll look at the source. But how do you figure out how to dump an image off of a phone in the first place? You modded the RC30 ota image to create yours right? Did you just copy the system files off somehow? What kinds of tools did you use? I find this stuff really interesting Thanks for the replies!

damccull said:
Hmm. I am a programmer. I'll look at the source. But how do you figure out how to dump an image off of a phone in the first place? You modded the RC30 ota image to create yours right? Did you just copy the system files off somehow? What kinds of tools did you use? I find this stuff really interesting Thanks for the replies!
Click to expand...
Click to collapse
I mainly modified the OTA itself. Added binaries, a new kernel.. etc. etc. I didn't have to pull anything from the phone, because it's all in the OTA.

Oh, you copied the update file off the phone after it downloaded and modded that? Sweet.

T-Mobile (US) MyTouch system folder

Got a dump of the official T-Mobile (US) MyTouch system folder. Not a whole lot of interesting stuff here, the build.prop is different, but otherwise the ROM looks nearly the same as the G1's official 1.5 firmware. The build id is CRB57.
A first attempt at booting a modified recovery thru fastboot failed with the "remote: not allowed" message.
Download here: http://n0rp.chemlab.org/android/mytouchdump.zip
Thanks to markdt098 for grabbing it.

Hey Cy,
This is the one from the test versions. The TMo proprietary stuff that's supposed to set the MyTouch above the G1 isn't on the phones that have been released thus far. So, we'll most likely need to keep our eyes out for a dump that includes those items.

A first attempt at booting a modified recovery thru fastboot failed with the "remote: not allowed" message.
So no go on rooting? I have the phone for a couple of days and really wanted to root. If anyone figures it out Please. PM me.

so did u try both these recovery images?
[Recovery] RAv1.0 : Modded ION recovery!

sangeet.003 said:
so did u try both these recovery images?
[Recovery] RAv1.0 : Modded ION recovery!
Click to expand...
Click to collapse
Yes. They couldn't be booted via "fastboot boot".
I don't actually have the device, though.

So u can alternately get the boot image & other images through "/dev/mtd/mtd*" using "adb pull /dev/mtd/mtd* *.img"
what problem does "fastboot boot" gives?
does it hangs @ the first screen after restart? or the "fastboot boot" itself isn't supported..

thread?
We've already got a thread going on fastboot remote not allow. Should they be merged

nixxofugi said:
We've already got a thread going on fastboot remote not allow. Should they be merged
Click to expand...
Click to collapse
this thread is for getting hands on myTouch 3G system, m telling way 2 get oher stuffs out of the phone like boot & other partitions, not only fastboot thing.

cyanogen said:
Yes. They couldn't be booted via "fastboot boot".
I don't actually have the device, though.
Click to expand...
Click to collapse
I have the devise for a couple of days. You cannot ADB without rooting first. I read about pushing mod recovery through fastboot, I won't do that unless I can revert to original state. Does any one know if you can $fastboot pull system/recovery.img

Mi|enko said:
Hey Cy,
This is the one from the test versions. The TMo proprietary stuff that's supposed to set the MyTouch above the G1 isn't on the phones that have been released thus far. So, we'll most likely need to keep our eyes out for a dump that includes those items.
Click to expand...
Click to collapse
What stuff exactly are you talking about? The Sherpa app is the only thing I can think of that the release myTouch will have that mine does not.
Edit: And exchange support...do you think that will require an OTA update for the myTouch's given out to employees?

try this:
1. Boot the device full till the home screen
2. use cmd & go to "adb shell"
3. then type in "cat /proc/mtd"
u ll see some thing like this:
Code:
cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 05a00000 00020000 "system"
mtd4: 01e00000 00020000 "cache"
mtd5: 059c0000 00020000 "userdata"
4. then use, use mtd<dev number> according to <name>.img
Code:
"adb pull /dev/mtd/mtd1 recovery.img"
"adb pull /dev/mtd/mtd2 boot.img"
"adb pull /dev/mtd/mtd3 system.img"
"adb pull /dev/mtd/mtd5 userdata.img"
by doing so u ll backup recovery & then try flashing recovery...
post what u get here.

sangeet.003 said:
try this:
1. Boot the device full till the home screen
2. use cmd & go to "adb shell"
3. then type in "cat /proc/mtd"
u ll see some thing like this:
Code:
cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 05a00000 00020000 "system"
mtd4: 01e00000 00020000 "cache"
mtd5: 059c0000 00020000 "userdata"
4. then use, use mtd<dev number> according to <name>.img
Code:
"adb pull /dev/mtd/mtd1 recovery.img"
"adb pull /dev/mtd/mtd2 boot.img"
"adb pull /dev/mtd/mtd3 system.img"
"adb pull /dev/mtd/mtd5 userdata.img"
by doing so u ll backup recovery & then try flashing recovery...
post what u get here.
Click to expand...
Click to collapse
I get a permission denied error when trying that.

markdt098 said:
I get a permission denied error when trying that.
Click to expand...
Click to collapse
for what cat proc? or adb pull ?...

Sorry, should of clarified, adb pull gives me the error, cat proc does not.

have unrestricted access to a mytouch as well, if theres anything you'd like me to do let me know... i have the exact same problems with fastboot as well as the adb shell permission errors

k first let me check the available stuff in the system folder by cyanogen so to know what it has & what it dosent... plz wait for some time... may be later... today

cyanogen said:
Got a dump of the official T-Mobile (US) MyTouch system folder. Not a whole lot of interesting stuff here, the build.prop is different, but otherwise the ROM looks nearly the same as the G1's official 1.5 firmware. The build id is CRB57.
A first attempt at booting a modified recovery thru fastboot failed with the "remote: not allowed" message.
Download here: http://n0rp.chemlab.org/android/mytouchdump.zip
Thanks to markdt098 for grabbing it.
Click to expand...
Click to collapse
Does this mean you will soon be blessing us ION/Magic owners with your modified roms?

Gimpeh said:
Does this mean you will soon be blessing us ION/Magic owners with your modified roms?
Click to expand...
Click to collapse
May be he or me too, i am waiting for it to come to India so rooting it can be done together...
Need donations to get our hands on Magic coz we both have an g1... thats hard to spend on too... m 16... 4 me its tooooo hard.. lol
n may be there will be ION/HERO/Ophone ports to magic too... m Currently Downloading Ophone SDK to Get system out of it...

markdt098 said:
What stuff exactly are you talking about? The Sherpa app is the only thing I can think of that the release myTouch will have that mine does not.
Edit: And exchange support...do you think that will require an OTA update for the myTouch's given out to employees?
Click to expand...
Click to collapse
Probably. Sherpa's supposedly what the MyTouch will have that other android devices won't (at least not at first). Then there's exchange and finally the customization options (for making the device your own). I'm actually curious about that last one the most. Wonder if they worked with a dev to bring theme support or what.

Mi|enko said:
Probably. Sherpa's supposedly what the MyTouch will have that other android devices won't (at least not at first). Then there's exchange and finally the customization options (for making the device your own). I'm actually curious about that last one the most. Wonder if they worked with a dev to bring theme support or what.
Click to expand...
Click to collapse
Not tested but i think we just need the myTouch boot img to get it running with root on other devices...
let me try it with other boot img's...

[A510][EXPERIMENTAL][DON'T USE] CWM Recovery 6.0.1.0.

Inspirated by the thread of pawitp (http://forum.xda-developers.com/showthread.php?t=1791165) I just built a CWM 6.0.1.0 /wo touch on http://builder.clockworkmod.com/. (Finished Build: http://jenkins.cyanogenmod.com/job/recovery/2646/)
It starts up but is not usable since the power button is not recognised and therefore not menu entries can be selected. :crying:
I used
Code:
fastboot flash recovery recovery.img
and it works if the recovery is entered by Vol- button. Weird enought it can not be entered by
Code:
adb reboot recovery
which seems to pop up the stock recovery
How is this possible? I am still new to the android infrastructure and learning how everything goes but this is something I have not expected...
If someone could enlighten me with facts to this matter I would be grateful.
I will also try to build a touch versionl. That might work better.
Edit: since also pawitp bricked his device i highly recommend to NOT USE ANY CUSTOM RECOVERY until we have found out what causes this bricks!

mearoth said:
Inspirated by the thread of pawitp (http://forum.xda-developers.com/showthread.php?t=1791165) I just built a CWM 6.0.1.0 /wo touch on http://builder.clockworkmod.com/. (Finished Build: http://jenkins.cyanogenmod.com/job/recovery/2646/)
It starts up but is not usable since the power button is not recognised and therefore not menu entries can be selected. :crying:
I used
Code:
fastboot flash recovery recovery.img
and it works if the recovery is entered by Vol- button. Weird enought it can not be entered by
Code:
adb reboot recovery
which seems to pop up the stock recovery
How is this possible? I am still new to the android infrastructure and learning how everything goes but this is something I have not expected...
If someone could enlighten me with facts to this matter I would be grateful.
I will also try to build a touch versionl. That might work better.
Click to expand...
Click to collapse
Hi mearoth,
My recoveries (see other thread in this forum) are build exactly like that, in my case I used the Dees-Troy fstab file. But... be really, really careful. If you do it this way, backup/restore and format stuff may brick your device. We've had one guy that had a simple FOTA bricking his device, so again... be really really careful...
Regards,
Nika.

just as a comparison :
fstab from dees-troy :
Code:
/system ext4 /dev/block/mmcblk0p3
/data ext4 /dev/block/mmcblk0p10 length=-1048576
/cache ext4 /dev/block/mmcblk0p4
/misc emmc /dev/block/mmcblk0p5
/flexrom ext4 /dev/block/mmcblk0p6
/sdcard vfat /dev/block/sda1 /dev/block/mmcblk1p1
/boot emmc /dev/block/mmcblk0p2
/aboot emmc /dev/block/mmcblk0p8
/recovery emmc /dev/block/mmcblk0p1
/flex ext4 /dev/block/mmcblk0p6
/sdc vfat /dev/block/mmcblk1p1
fstab from the current cwn for a700:
Code:
# mount point fstype device [device2]
/sdcard vfat /dev/block/mmcblk1p1
/emmc datamedia /dev/null
/system ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
/cache ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA length=-32768 # TODO: verify
/misc emmc /dev/block/platform/sdhci-tegra.3/by-name/MSC
/boot emmc /dev/block/platform/sdhci-tegra.3/by-name/LNX
/recovery emmc /dev/block/platform/sdhci-tegra.3/by-name/SOS
/staging emmc /dev/block/platform/sdhci-tegra.3/by-name/USP
can it be only a problem of partition size that cause the crash of data partition ?
Reminder for comparison (credit nikagl ) :
Code:
/dev/block/platform/sdhci-tegra.3/by-name/SOS /dev/block/mmcblk0p1 /recovery
/dev/block/platform/sdhci-tegra.3/by-name/LNX /dev/block/mmcblk0p2 /boot
/dev/block/platform/sdhci-tegra.3/by-name/APP /dev/block/mmcblk0p3 /system
/dev/block/platform/sdhci-tegra.3/by-name/CAC /dev/block/mmcblk0p4 /cache
/dev/block/platform/sdhci-tegra.3/by-name/MSC /dev/block/mmcblk0p5 /misc
/dev/block/platform/sdhci-tegra.3/by-name/FLX /dev/block/mmcblk0p6 /system/vendor /flexrom /flex
/dev/block/platform/sdhci-tegra.3/by-name/AKB /dev/block/mmcblk0p7 ?
/dev/block/platform/sdhci-tegra.3/by-name/USP /dev/block/mmcblk0p8 /aboot (bootloader.blob)
/dev/block/platform/sdhci-tegra.3/by-name/DE2 /dev/block/mmcblk0p9 ?
/dev/block/platform/sdhci-tegra.3/by-name/UDA /dev/block/mmcblk0p10 /data

BENETNATH said:
just as a comparison :
can it be only a problem of partition size that cause the crash of data partition ?
Click to expand...
Click to collapse
Could be well.
I currently try to build CWM and CM10 on my ubuntu machine and have taken the repositories of pawitp as starting point and have found that A700 and A510 have slightly different partition sizing reguarding the APP partition. But that should not be a matter.
pawtip has also changed the following in his repository from recovery.fstab
Code:
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA length=-1081344
Since partition sizes of /data are the same on A510 and A700 that could do the trink as I think pawtip's recovery is working.

mearoth said:
Could be well.
I currently try to build CWM and CM10 on my ubuntu machine and have taken the repositories of pawitp as starting point and have found that A700 and A510 have slightly different partition sizing reguarding the APP partition. But that should not be a matter.
pawtip has also changed the following in his repository from recovery.fstab
Code:
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA length=-1081344
Since partition sizes of /data are the same on A510 and A700 that could do the trink as I think pawtip's recovery is working.
Click to expand...
Click to collapse
it might be a good option to ask to pawtip how he found this value then, can you check with him ?

Guys be EXTRA carefull. Pawitp just bricked his A700 flashing a new version of CM10 he was working on !!! It's not the first time he flashes but this time the process hanged, he had to reboot and now his tablet is stuck in APX mode (which is bad).
I suggest we all stop messing around too much much until we know more about those brick issues...

I just heard he also bricked his device
---------- Post added at 10:25 AM ---------- Previous post was at 10:09 AM ----------
paugustin said:
Guys be EXTRA carefull. Pawitp just bricked his A700 flashing a new version of CM10 he was working on !!! It's not the first time he flashes but this time the process hanged, he had to reboot and now his tablet is stuck in APX mode (which is bad).
I suggest we all stop messing around too much much until we know more about those brick issues...
Click to expand...
Click to collapse
Haha.. sorry, using my test account to see whether I can respond to dev-threads which works fine and also now say you already responded...

paugustin said:
I suggest we all stop messing around too much much until we know more about those brick issues...
Click to expand...
Click to collapse
I hear you and I think you are right. I will try digging a bit deeper into the whole flashing issue. Perhaps we can also investigate further in getting the sbk in order to enable us the APX flashing. I will try contacting Acer Europe once more.
Sent from my MB526 using xda developers app

For my knowledge, can you explain me how you get the mength value for the fstab ??
because the recovery you have created was with "length=-32768"

The "length=-32768" was just a value I have taken over by the nexus i think. however.
I just had a deeper look at the raw content of the mmc (dd if=/dev/block/mmcblk0 of=/data/mmcblck0-40000 count=40000) and have found something like a partition table at offset 0x30.00.00 . Since I believe it is not a regular partition table (nothing I know yet to be honest) I have not found out the sizes and offsets of the partitions. What I have found out though, is the fact that there are far more partitions than we know. Here comes the list in the order as they are in the RAW:
BCT <- (EDIT: Boot Config Table - contains HW timings etc. .. first siginficant offset in raw at 0x10 00 00)
PT <- (Partition Table - only a guess but the data is in the second significant offset at 0x30 00 00)
EBT <- EDIT: first Bootloader - when finished -> loads either LNX or SOS to go on in boot chain
EKS
DE1
GP1
-- Then comes the ones we already know:--
SOS
LNX
APP
CAC
MSC
FLX
AKB
USP
DE2
UDA
-- And one more we do not know:
GPT <- This could be a second partition table. this would not be unusual to have the table doubled at beginning and end. but I have not checket yet.
And here comes a possible explanation for the bricks: could it be since we do not have this in our fstab and the lengh value of UDA beeing probably incorrect that at some point when flashing the system overwrites bytes of this partition destroing the PT ? --> brick because bootloader can not determin right partition sizing any more. also this could happen at some point only when bytes are written to the GPT without us knowing. so flashing might work several times until it happens to strike this partition.
What do you think?
I will definitly investigate a bit more on that matter.

thanks for this
might be useful..
we need more gurus on that point, who can we reach to help us ? koush ?

I just got a reply from pawitp via pm:
pawitp said:
My brick is not due to formatting /data (The CWM I built does /data format using rm -rf), and I'm actually not sure why it bricked. The GPT at the end is the one read by linux.
Click to expand...
Click to collapse
So my guess was wrong. -> back to start.
I will nevertheless have a look at those hidden partitions. Some guru might really help but I don't know enought people here due to having been inactive for a long time.

good to know too.. strange

hi, any news for building the new CWM?

Nah. I first want to know what causes all the bricks or have at least a fallback scenario like working APX mode..
Now regarding APX i once more had no luck with acer people to get the sbk... this folk's so unhelpful :thumbdown:
Reguarding bricks pawitp had an idea that the samsung mmc brickbug might be present on our devices and has disabled mmc erase command in the kernel.
Now that is a todo for me for our kernel or i have time to test if our kernels are compatible. Beside this pawitp is not sure if it really IS the mmc bug. But IMHO it is a good guess.
Sent from my A510 using xda app-developers app

mearoth said:
Nah. I first want to know what causes all the bricks or have at least a fallback scenario like working APX mode..
Now regarding APX i once more had no luck with acer people to get the sbk... this folk's so unhelpful :thumbdown:
Reguarding bricks pawitp had an idea that the samsung mmc brickbug might be present on our devices and has disabled mmc erase command in the kernel.
Now that is a todo for me for our kernel or i have time to test if our kernels are compatible. Beside this pawitp is not sure if it really IS the mmc bug. But IMHO it is a good guess.
Sent from my A510 using xda app-developers app
Click to expand...
Click to collapse
Well, my device does still come up with APX mode (regardless of the broken screen), so if I ever need to test anything in APX mode for anyone, let me know. I've tried many different versions of nvflash, but nothing worked so far. Best option was one that authenticated to acer, but without the acer username and password or some way to spoof that, I don't think we'll be able to get this going...

nikagl said:
Well, my device does still come up with APX mode (regardless of the broken screen), so if I ever need to test anything in APX mode for anyone, let me know. I've tried many different versions of nvflash, but nothing worked so far. Best option was one that authenticated to acer, but without the acer username and password or some way to spoof that, I don't think we'll be able to get this going...
Click to expand...
Click to collapse
You are right. I got a version of nvflash running on my ubuntu machine but since our device is in APX secure mode the secure boot key is needed in order to do anything usefull with it. As long as we do not have this key we can really only ask acer to give it. There might even be a chance to get it since i heard the a200 sbk was also released. That's what i am currently on. Finding out whom to contact to get the sbk..
Sent from my A510 using xda developers app

[4.4.2][HBOOT2.22] New partition layout with 4.4.2 OTA

Update
Watch out! Beginning with the 05/01 nightly the CM11 nightly builds are safe to flash no matter which partition layout you have. Other ROMs may not be independent from the partition layout yet and therefore still need to be modified before flashing. Read your ROM's FAQ or ask the devs for more information on that particular issue.
Introduction - What is this good for?
If you have been on a Stock ROM and got a Stock OTA update to 4.4.2 then it's very likely that you've got a "new partition layout".
This has the effect, that pretty all of the currently available ROMs flying around can't be one-click-flashed via recovery. (Technical background: The install scripts in the usual ROM zips contain instructions that refer to the old partition layout. With the "new layout" the scripts won't work anymore and flashing will fail.)
If you tried already and your phone isn't booting anymore ... Don't panic! As long as you get into fastboot mode, it is highly unlikely that your phone is bricked. And if you're able to flash and boot a recovery you're pretty safe.
Read on to find out how to deal with this.
What do you need?
You need adb and fastboot on your computer and you should basically know how to work with these tools. If you have a Windows computer you need the fastboot and adb drivers to be installed. Just use Google or refer to other sections of this forum on how to do that.
So first let's find out, if you're on the "new partition layout"
As far as I know for now the "new partition layout" comes with HBOOT 2.22. So boot into bootloader and check this out.
If you're not on 2.22 then you still could check the following thing. With 2.22 you definitely should continue.
Boot to your recovery and run the following adb command on your computer:
Code:
adb shell cat /proc/emmc
Compare your output to this:
Code:
$ adb shell cat /proc/emmc
dev: size erasesize name
mmcblk0p22: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 85fffc00 00000200 "system"
mmcblk0p29: 00140200 00000200 "local"
mmcblk0p36: 29fffe00 00000200 "cache"
mmcblk0p37: 2d8000000 00000200 "userdata"
mmcblk0p25: 01400000 00000200 "devlog"
mmcblk0p27: 00040000 00000200 "pdata"
mmcblk0p30: 00010000 00000200 "extra"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p23: 00400000 00000200 "modem_st1"
mmcblk0p24: 00400000 00000200 "modem_st2"
mmcblk0p32: 01fffc00 00000200 "reserve"
mmcblk0p28: 00004000 00000200 "control"
Please check very carefully, especially the lines ending with "system", "data", "cache", "boot" and "recovery"!!!
If your output looks the same then you have the "new partition layout". Then you will need a modified recovery that respects the "new partition layout".
Just use one of these (thanks to @kyasu):
TWRP 2.7.0.5: http://forum.xda-developers.com/showpost.php?p=51612358&postcount=15 (MD5: 0bd688e0f39a6c37806b8695022afcdf)
CWM 6.0.4.7: http://forum.xda-developers.com/showpost.php?p=51740162&postcount=26 (MD5: 061fe34b19a817fb5b039a3531fba5a5)
Flash it via fastboot:
Code:
fastboot flash recovery twrp-2.7.0.5-m4kk.img
If you even can't boot into recovery you have to flash one of these anyway.
Flash a ROM that has been modified to respect the new partition layout
As already said, almost all ROMs currently available don't match your partitions. The updater-scripts within have to be modified.
So let's collect all ROMs or zips that has been modified already and are therefore ready to flash (from the recovery as usual, as long it's one of the aforementioned).
Don't forget to flash boot.img via fastboot if you're S-ON.
Stock ROMs or nandroid backups:
Stock 4.4.2 (3.10.401.4) odexed or Stock 4.4.2 (3.10.631.5) deodexed can be found here:
http://forum.xda-developers.com/showthread.php?p=51779967 (infos about both ROMs in the first post of the thread)
Stock 4.4.2 (3.10.111.4) odexed nandroid backup from a German T-Mobile device:
https://drive.google.com/file/d/0ByRc8IR1ZBiveTludUt1ZUp4QUk/edit?usp=sharing (MD5: 0a1f21529328c7581f366954eeeba46a)
(should work on non-German devices, too)
Customized ROMs:
CM11 nightly 0403: https://drive.google.com/file/d/0ByRc8IR1ZBivZmpjWmt2YXhfT28/edit?usp=sharing (MD5: 3bc8d4694f1ee80992665138b252431f)
CM11 nightly 0412: https://drive.google.com/file/d/0ByRc8IR1ZBivZ2R0Q01fZHpxd1E/edit?usp=sharing (MD5: f502e43aa9cea3dab5a6b05f68953333)

great work, this should clarify things for people. i imagine users with the modified partition will not be able to flash cm11 nightlies until the roms are modified also ?
I currently s-off, hboot 2.19 & twrp 2.6.3. so ....flashing one of these (TWRP 2.7.0.5: http://forum.xda-developers.com/show...8&postcount=15 (MD5: 0bd688e0f39a6c37806b8695022afcdf)
CWM 6.0.4.7: http://forum.xda-developers.com/show...2&postcount=26 (MD5: 061fe34b19a817fb5b039a3531fba5a5)
recoveries will up modify my partition layout ??
cheers

Braddison said:
so ....flashing one of these (TWRP 2.7.0.5: http://forum.xda-developers.com/show...8&postcount=15 (MD5: 0bd688e0f39a6c37806b8695022afcdf)
CWM 6.0.4.7: http://forum.xda-developers.com/show...2&postcount=26 (MD5: 061fe34b19a817fb5b039a3531fba5a5)
recoveries will up modify my partition layout ??
Click to expand...
Click to collapse
No, they don't. They're just modified to match the new partition layout (if you have it already).

OK,thanks.
Seems to me,that the way forward (only speculating) devs will produce Roms that will work with the new modified partition layout as its the latest firmware, meaning that pre hboot 2.22 will become obsolete and user will need to upgrade there hboot? surely there must be a simpler way than the route of supercid and flashing an ruu ?
forgive me if my question is wrong, just been off xda for the last few weeks n trying to catch up.
cheers

hi
I think thats the problem why i cant flash CM 11, because i have this 2.2.2 hboot new layout.
BUt i have a new problem now. I cant pull the rom via adb push onto my device. it says
*deamon started succesfull*
error device
Just dont know what to do..
PS: I have flashed the new TWRP 2.7.0.5, but i cant get the rom zip on the phone dunno why, it worked with 2.6.0.0...

EdiBese said:
I think thats the problem why i cant flash CM 11, because i have this 2.2.2 hboot new layout.
BUt i have a new problem now. I cant pull the rom via adb push onto my device. it says
*deamon started succesfull*
error device
Just dont know what to do..
PS: I have flashed the new TWRP 2.7.0.5, but i cant get the rom zip on the phone dunno why, it worked with 2.6.0.0...
Click to expand...
Click to collapse
I had a similar problem, I just used a OTG (On The Go) cable, with a flash drive.

Braddison said:
OK,thanks.
Seems to me,that the way forward (only speculating) devs will produce Roms that will work with the new modified partition layout as its the latest firmware, meaning that pre hboot 2.22 will become obsolete and user will need to upgrade there hboot?
Click to expand...
Click to collapse
I'm not sure if the new partition layout will become the standard among the devs. Most of the users here switched to custom ROMs way before the OTA with HBOOT 2.22 was released. They all depend on ROMs made for the classic partition layout.
Since upgrading HBOOT isn't that easy (as you mentioned this needs performing a RUU or having S-OFF which is generally not necessary or recommended) it would be the best to stick with the old partition layout as long as possible.
EdiBese said:
I think thats the problem why i cant flash CM 11, because i have this 2.2.2 hboot new layout.
BUt i have a new problem now. I cant pull the rom via adb push onto my device. it says
*deamon started succesfull*
error device
Just dont know what to do..
PS: I have flashed the new TWRP 2.7.0.5, but i cant get the rom zip on the phone dunno why, it worked with 2.6.0.0...
Click to expand...
Click to collapse
Did you check the output of cat /proc/emmc as I mentioned above? Do that with the recovery that seems to work well (2.6.0.0 in your case). That's the only way to be absolutely sure about your partitions. Perhaps checking HBOOT version only is not sufficient.

hi
morschesholz said:
I'm not sure if the new partition layout will become the standard among the devs. Most of the users here switched to custom ROMs way before the OTA with HBOOT 2.22 was released. They all depend on ROMs made for the classic partition layout.
Since upgrading HBOOT isn't that easy (as you mentioned this needs performing a RUU or having S-OFF which is generally not necessary or recommended) it would be the best to stick with the old partition layout as long as possible.
Did you check the output of cat /proc/emmc as I mentioned above? Do that with the recovery that seems to work well (2.6.0.0 in your case). That's the only way to be absolutely sure about your partitions. Perhaps checking HBOOT version only is not sufficient.
Click to expand...
Click to collapse
no i didnt check
but i cant flash cm 11 with 2,6.3
it says symllink failed
error in binary counter or something like that
---------- Post added at 11:10 AM ---------- Previous post was at 10:59 AM ----------
I checked it out bro, it seems to be the same
mmcblk0p22: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 85fffc00 00000200 "system"
mmcblk0p29: 00140200 00000200 "local"
mmcblk0p36: 29fffe00 00000200 "cache"
mmcblk0p37: 2d8000000 00000200 "userdata
mmcblk0p25: 01400000 00000200 "devlog"
mmcblk0p27: 00040000 00000200 "pdata"
mmcblk0p30: 00010000 00000200 "extra"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_con
mmcblk0p23: 00400000 00000200 "modem_st1
mmcblk0p24: 00400000 00000200 "modem_st2
mmcblk0p32: 01fffc00 00000200 "reserve"
mmcblk0p28: 00004000 00000200 "control"

Does your adb really only say: error device?
Usually the output is a little more verbose.
Are you on Windows or on Linux or Mac? On Linux or Mac you could try starting adb with sudo:
Code:
sudo adb kill-server
sudo adb devices
Then your device should be listed (a line containing the id of your device and the word "recovery").

hi
The problem is now.
When i flash 2.7.05, my phone cant be recognized when i am in TRWP mode. And this means i cant push the rom on the device iam stuck here.
I just see something bro look..
i have 2.6.0.0 now and pushed cm on the phone, but now i see i had cm on the /sdcard
But when i flash 2.7.0.5 i cant find cm on the sd card any more? ican find nothing on the sdcard

Just flash 2.7.0.5 again (be sure that it's the modified one from the first post here, it's name should be twrp-2.7.0.5-m4kk.img).
Then run
Code:
sudo adb kill-server
sudo adb devices
and tell us the exact output.

hi
C:\Android>adb devices
adb server is out of date.
* daemon started successfu
List of devices attached
If i try to push
C:\Android>adb push cm-11-20140411-NIGHTLY-m4.zip sdcard/
error: device not found
And in TWRP 2.6 it show 1620 MB Internal Storage, but in 2.7.05 it says 11308 MB, something is wrong..
I cant type in sudo, it doesnt work
---------- Post added at 11:47 AM ---------- Previous post was at 11:27 AM ----------
I downloadede the twrp of your post... flashed again.. same problem
I just cant get this rom on the phone!

Man, you have to use the modified 2.7.0.5 since it matches your new partition layout. That's why 2.7.0.5 is showing you the correct amount of free space: 11308 MB. That's the free space on your userdata partition (which is now at mmcblk0p37). 2.6.0.0 is made for the old layout and expects userdata to be at mmcblk0p35. As you can see from your emmc output, mmcblk0p35 is now /system on your device. That's why 2.6.0.0 is showing you only 1620 MB free space. That's the free space on the system partition.
So stay with 2.7.0.5!!!
The problem you have is that adb is not working. First of all, you can't adb push anything if your device is not recognized. That's what adb devices is doing: listing all recognized devices. So if adb devices shows nothing, nothing is recognized. It's that simple.
But as you can see adb devices tells you "adb server is out of date". Googling that error will give you lots of tips on how to deal with that problem: uninstalling HTC Sync should help.
Then you should be sure to have the latest adb and fastboot versions. You can download a current package here: http://forum.xda-developers.com/showthread.php?t=2317790
Then you first should do this again:
Code:
adb kill-server
adb devices
If - and really only if !!! - your output is something like that:
Code:
[[email protected] ~] adb devices
List of devices attached
HTxxxxxxxxxx recovery
then you're safe to continue.
But before flashing anything to the phone you should wipe all partitions. Go to Wipe > Advanced Wipe, select everything except USB OTG and Internal Storage and then swipe to wipe. After that you can adb push a cm.zip (a modified one) to your sdcard and install it. Finally flash boot.img via fastboot and you're done.

morschesholz said:
Man, you have to use the modified 2.7.0.5 since it matches your new partition layout. That's why 2.7.0.5 is showing you the correct amount of free space: 11308 MB. That's the free space on your userdata partition (which is now at mmcblk0p37). 2.6.0.0 is made for the old layout and expects userdata to be at mmcblk0p35. As you can see from your emmc output, mmcblk0p35 is now /system on your device. That's why 2.6.0.0 is showing you only 1620 MB free space. That's the free space on the system partition.
So stay with 2.7.0.5!!!
The problem you have is that adb is not working. First of all, you can't adb push anything if your device is not recognized. That's what adb devices is doing: listing all recognized devices. So if adb devices shows nothing, nothing is recognized. It's that simple.
But as you can see adb devices tells you "adb server is out of date". Googling that error will give you lots of tips on how to deal with that problem: uninstalling HTC Sync should help.
Then you should be sure to have the latest adb and fastboot versions. You can download a current package here: http://forum.xda-developers.com/showthread.php?t=2317790
Then you first should do this again:
Code:
adb kill-server
adb devices
If - and really only if !!! - your output is something like that:
Code:
[[email protected] ~] adb devices
List of devices attached
HTxxxxxxxxxx recovery
then you're safe to continue.
But before flashing anything to the phone you should wipe all partitions. Go to Wipe > Advanced Wipe, select everything except USB OTG and Internal Storage and then swipe to wipe. After that you can adb push a cm.zip (a modified one) to your sdcard and install it. Finally flash boot.img via fastboot and you're done.
Click to expand...
Click to collapse
Friend, i am on 2.7.0.5 the whole time. I know that my phone is not reognized but i dont know why, because on 2.6.3 it is recognized!

I'm sorry but that's all I can tell you. Do you have HTC Sync installed? Then I advise to uninstall it and use original adb and fastboot executable from the thread I linked to.

morschesholz said:
I'm sorry but that's all I can tell you. Do you have HTC Sync installed? Then I advise to uninstall it and use original adb and fastboot executable from the thread I linked to.
Click to expand...
Click to collapse
Yes HTC sync is installed, i just did everything what you said
But my phone is not recognized, dunno why

Just to be sure: Do you have restarted your computer after uninstalling all the HTC Software?

morschesholz said:
Just to be sure: Do you have restarted your computer after uninstalling all the HTC Software?
Click to expand...
Click to collapse
DId.. the same..
What i dont understand is, under 2.6. my phone i recognized and i can push files, i tried it out an hour ago.. but with 2.7.0.5 it isnt, means there is no problem with the software and drivers on the computer..

What about fastboot? Boot into fastboot mode and check if fastboot devices lists your phone.

hi
morschesholz said:
What about fastboot? Boot into fastboot mode and check if fastboot devices lists your phone.
Click to expand...
Click to collapse
Yes it does
C:\Android>fastboot devices
HT37NWA00458 fastboot