Database Develop

how to dump your zio

I wrote this up in another forum and it also got lost in the 1.6 thread. Thought I'd pull it out.
---------
Instructions on how to dump your image manually:
Note: Everything in green is a command to type.
Pre)You installed the Kyocera USB drivers that came with the phone.
Kyocera ZIO - Downloads
Direct: http://www.ziobykyocera.com/downloads/files/M6000_USB_Driver.zip
Also, on the phone: Menu->Settings->Applications->Development->USB Debugging [selected]
Steps:
Root your phone:
[APP] [ROOT] 1-click root for N1 (Latest ver: 1.6.2 beta 5) - xda-developers
Direct: xda-developers
Install Android SDK for windows:
Android SDK | Android Developers
Direct: http://dl.google.com/android/android-sdk_r07-windows.zip
Extract that somewhere convinient, for ex: c:\
You'll need dump_image to get the img, find it here:
My Brain Hurts: Porting Clockwork Recovery to New Devices
Direct: http://koush.tandtgaming.com/test/dump_image
Copy that to the root of your sdcard, we'll use it later.
Lets connet to your phone.
Plug it in to the usb, make sure it is not mounted for reading the sdcard. On the phone, in the notification window tap the 'usb connected' notice and select "don't mount".
Now in windows, click Start->Run and type cmd.
cd \android-sdk-windows\tools\
adb.exe devices
It should list your device if all has gone well.
adb.exe shell
It should have connected to the phone and you have a "$" prompt.
su root
Now look at the phone, the Super User program (was installed after 1-click-root) should have popped up and asked if you want to allow root access, allow it.
Now you are at a "#" prompt.
Installing dump_image:
dump_image should be on the root of your sdcard from step 3.
Copy it to your bin directory:
cat /sdcard/dump_image > /system/bin/dump_image
Give it executable permission:
chmod 6755 /system/bin/dump_image
What to dump:
cat /proc/mtd
You're going to want to copy the output of that to the forum.
There should be a number of lines begining with mtd#
and the last name column has the name we'll need in quotes.
The dump:
mkdir /sdcard/dumped
dump_image boot /sdcard/dumped/boot.img
That just pulled the boot image. We need to do that for all the other images now:
dump_image name_here /sdcard/dumped/name_here.img
There could be 6-8 of them. Total will take a couple hundred megs.
Final:
Now we have it all, so zip up the files in /sdcard/dumped and put it on megaupload.com or something like that and post a link and the output from "cat /proc/mtd"
And that's it
Simple, yeah?
Some of those partitions that were listed in /proc/mtd are probably not needed, but I'm not certain as to which ones those are. I'm guessing "cache" and "userdata" probably aren't needed.

There was some issues with using the dump_image on yaffs2 partitions. For those the yaffs2 utility is useful. Here's some more info that was in the 1.6 thread:
Get it here:
http://jiggawatt.org/badc0de/android/mkfs.yaffs2.arm.tar.gz
(I attached it as well since that's the only place I could find an actual working version)
There's also a utility to extract the yaffs2 image (source)
You can also google for "mkyaffs2image" which is for something I can't recall.
Kind of shows how to use it in the middle of this section:
http://jiggawatt.org/badc0de/android/index.html#dynamic
adb push mkfs.yaffs2 /data/misc/mkfs.yaffs2
adb shell
# cd /data/misc
# ./mkfs.yaffs2 /system /system.img
# exit
adb pull /system.img ./system.img
Click to expand...
Click to collapse
Other useful info:
Code:
#cat /proc/mtd
dev: size erasesize name
mtd0: 01080000 00020000 "fota_amss"
mtd1: 00400000 00020000 "boot"
mtd2: 06780000 00020000 "system"
mtd3: 011e0000 00020000 "flex"
mtd4: 00500000 00020000 "recovery"
mtd5: 0ba60000 00020000 "userdata"
mtd6: 00600000 00020000 "fota_boot"
mtd7: 06780000 00020000 "cache"
mtd8: 000c0000 00020000 "misc"
Code:
#mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mtdblock2 /system yaffs2 rw,relatime 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/mtdblock7 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock3 /data/FLEX yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
So
Code:
boot not yaffs2
system yaffs2
recovery ...most likely yaffs2
userdata yaffs2
cache yaffs2
misc ...no clue

I've also tossed a bug in clockworkmods ears -- maybe if enough people request, we can get a fully supported recovery through rom manager.

dump_image data /sdcard/data.img
can't find data partition
is this a yaffs2 partition?
edit: mkfs.yaffs2 allows me to dump the partition, dump_image will not.
Could you clarify, ftr, what filesystem each of the partitions are?

I added more info the the second post about the yaffs2 and partitions.

[Q] backup EFS partition on Droid!

Hello all!
So I need to backup my EFS partition (with phone info, number, nv_data.bin, etc), but I can't find the partition! Furthermore there is no /efs folder on the phone, and the rootfs is mounted read-only.
I have searched for it on a vanilla ROM, a rooted ROM, and now a Cyanogen7 ROM, but I can't find it.
I have scoured the web for info, but all answers don't apply to this phone. There are many guides talking about reading and writing from /dev/stlX, but my droid seems to use /dev/block/mtdblockX, and none of the mtdblock's have EFS or Baseband information. Does Anyone know Anything about reading from or discovering the EFS partition on the Droid, or communicating with the baseband?
My goal: I ultimately need a way to read and write the nv_data.bin file on a Motorola Droid, or otherwise modify and restore important phone information (ESN, IMEI, MEID, whatever).
Also please no off-topic posts / "just letting me know you think this is wrong/illegal/impossible" / "whatever you think", as I've asked Verizon/lawyers and I have legal authority in my scenario. This seems to be a common response, so those of you who intend to say something like this, I'm asking you to please refrain from posting. Furthermore I know this procedure is possible, because I've seen it done on other Verizon devices.
For the record, when I run "mount" as root, this is what is printed:
Code:
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock4 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock6 on /data type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock5 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock0 on /config type yaffs2 (ro,relatime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
It seems most of my phone's data is contained within mtdblock's. However running "cat /proc/mtd" prints this:
Code:
dev: size erasesize name
mtd0: 00180000 00020000 "pds"
mtd1: 00060000 00020000 "misc"
mtd2: 00380000 00020000 "boot"
mtd3: 00480000 00020000 "recovery"
mtd4: 08c60000 00020000 "system"
mtd5: 05ca0000 00020000 "cache"
mtd6: 105c0000 00020000 "userdata"
mtd7: 00200000 00020000 "kpanic"
Elsewhere on the web, I have seen partitions named "efs" and "radio" pop up. Clearly mine lacks these.. where is this info? It must exist somewhere, as it's visible in Settings->About->Phone Status.

System Dump and Temporary Root

Hopefully good news!
I was able to gain temporary root access via root exploit at http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit/
Code:
[email protected] ~/Downloads/first » adb shell
[email protected]:/ $ /data/local/tmp/pwn
[+] This may take a few minutes.
[+] Success!
[email protected]:/ $ su
[email protected]:/ #
With that access, I was able to use `dd` to pull all of the mmcblk images, which includes the system partition. As I'm not familiar enough with what recovery images look like, I'm not 100% sure if this dump includes that, but since I pulled all 32 non-user partitions, hopefully someone else will know what to do with these. At the very least, it might mean we can use fastboot to push a proper root binary.
According to `mount` from adb shell, the following block devices are mapped as such:
Code:
[email protected]:/sdcard/dump $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /dev/timer_group cgroup rw,relatime,timer_slack 0 0
/dev/block/mmcblk0p32 /system ext4 rw,relatime,data=ordered 0 0
/dev/block/mmcblk0p34 /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p33 /cache ext4 rw,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk0p25 /devlog ext4 rw,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk0p16 /firmware_radio vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p17 /firmware_q6 vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Grab the system dump here: http://pub.noswap.com/myst.txz

Great job! I tried Motochopper but it didn't work for me...but regardless I am glad you got it to work. The good news is, we have the files but now we need to figure out which block has the recovery.img in it. Let's see if I can figure this out...

Weirdly (or maybe this is normal), I tried mounting the system partition on my machine, and doesn't seem to want to let me write anything new to the filesystem:
Code:
[email protected] ~/Downloads/first/myst » sudo mount mmcblk0p32 /mnt
[email protected] ~/Downloads/first/myst » mount | grep mmc
/home/jreese/Downloads/first/myst/mmcblk0p32 on /mnt type ext4 (rw,relatime,data=ordered)
[email protected] ~/Downloads/first/myst » cp ../armeabi/su /mnt/xbin/su
cp: cannot create regular file ‘/mnt/xbin/su’: Read-only file system
Again, as I'm not too terribly familiar with the way this sort of thing is usually done on Android, is there something special I need to do in order to make changes to this filesystem and attempt flashing it back to the device via fastboot?

I am able to write su and busybox to /system/xbin and /system/bin but rebooting the phone blows the binaries away. Any thoughts?
Code:
[email protected]:/ # mount -o remount,rw -t rfs/dev/block/mmcblk0p32 /system
mount -o remount,rw -t rfs/dev/block/mmcblk0p32 /system
[email protected]:/ # cp /sdcard/su /system/xbin/su
cp /sdcard/su /system/xbin/su
[email protected]:/ # cp /sdcard/busybox /system/xbin/busybox
cp /sdcard/busybox /system/xbin/busybox
[email protected]:/ # chmod 4755 /system/xbin/busybox
chmod 4755 /system/xbin/busybox
[email protected]:/ # chmod 4755 /system/xbin/su
chmod 4755 /system/xbin/su
[email protected]:/ # mount -o remount,ro -t rfs/dev/block/mmcblk0p32 /system
mount -o remount,ro -t rfs/dev/block/mmcblk0p32 /system

Here we go...at least we know where recovery is.
Code:
[email protected]:/ # cat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p22: 000ffa00 00000200 "misc"
[B]mmcblk0p21: 00fffe00 00000200 "recovery"
mmcblk0p20: 01000000 00000200 "boot"[/B]
mmcblk0p32: 5ffffc00 00000200 "system"
mmcblk0p29: 00140200 00000200 "local"
mmcblk0p33: 13fffe00 00000200 "cache"
mmcblk0p34: 314000000 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"
mmcblk0p31: 0616a000 00000200 "reserve"

I think the issue with reboots wiping out changes to the filesystem is the same reason I can't even write to the filesystem on my desktop when it's mounted there. It seems they've managed to make the ext4 metadata think that the filesystem is read only, and I haven't been able to figure out how, or how to fix it.
Sent from my HTC first using xda premium

It looks like fsck finds a bunch of errors with the filesystem dumped from mmcblk32/system. After running `fsck.ext4 -y` on a copy of the image, I was able to succesfully mount it and push a copy of the su binary into xbin. Attempts at flashing either image results in the following error message though:
Code:
[email protected] ~/Downloads/first # fastboot flash system system.img
sending 'system' (1572863 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.008s

nuclear_eclipse said:
It looks like fsck finds a bunch of errors with the filesystem dumped from mmcblk32/system. After running `fsck.ext4 -y` on a copy of the image, I was able to succesfully mount it and push a copy of the su binary into xbin. Attempts at flashing either image results in the following error message though:
Code:
[email protected] ~/Downloads/first # fastboot flash system system.img
sending 'system' (1572863 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.008s
Click to expand...
Click to collapse
I'm pretty sure this won't work. In the partition list, each partition has a defined size and placement. Since you've modified the system.img, it can no longer fit within the boundaries of the partition that have been defined for it.

Hmm, I attempted making a new block file of 800MB (~60% the size of the original dumped block device, and about 10% larger than the actual size of the files contained), formatting it with ext4/data=ordered, and then mounting it alongside the dump and rsync'd the data. Fastboot still won't let me flash it for the same reason:
Code:
[email protected] ~/Downloads/first # fastboot flash system new-system-root.img
sending 'system' (819200 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.006s
:-/

Using ClockworkMod's Recovery Builder, I was able to successfully built a recovery.img for the First. However,
HERE BE DRAGONS
Even though the recovery image was successfully created, it does not mean it works. Please do not flash this recovery image. Simply boot into it without flashing to see if it works.
To boot into a recovery image without flashing,
Code:
fastboot boot recovery.img
Hopefully, if this doesn't work, it shouldn't turn your brand new phone into a nice paperweight.
You can download the image here, and view the Jenkins build result here.

Awesome, will try that right now. Thanks!

Hmm, seems no dice. It jumps to an HTC screen momentarily, and then reboots, at which point it loads the normal OS. :'(

At least it didn't blow up your phone. It's also a pretty automated process, so I'm sure someone with some more experience building cwm can figure it out. I'll see if I can ping koushik and get his thoughts.

dstaley said:
Using ClockworkMod's Recovery Builder, I was able to successfully built a recovery.img for the First. However,
HERE BE DRAGONS
Even though the recovery image was successfully created, it does not mean it works. Please do not flash this recovery image. Simply boot into it without flashing to see if it works.
To boot into a recovery image without flashing,
Code:
fastboot boot recovery.img
Hopefully, if this doesn't work, it shouldn't turn your brand new phone into a nice paperweight.
You can download the image here, and view the Jenkins build result here.
Click to expand...
Click to collapse
Good start, but we need to feed it a proper recovery.fstab and highly likely the graphic.c files as well.

Alright, using a modified recovery.fstab from the HTC One (with the correct HTC First partitions), I've cooked up a new recovery. Let's try this and see if it works. Just in the event someone stumbles upon this post without reading my last one:
HERE BE DRAGONS
Even though the recovery image was successfully created, it does not mean it works. Please do not flash this recovery image. Simply boot into it without flashing to see if it works. If you stupidly ignore my warning and flash this to your device, it might activate HTC's proprietary paper weight mode. And there's no coming back from that.
To boot into a recovery image without flashing,
Code:
fastboot boot recovery.img
Download here.

No dice with this one either; gives the same "warning" message from HTC for about 5 seconds, then jumps to a blank screen and eventually reboots into Android.
However, I did notice that on the bootloader screen for my phone, it nows says "*** TAMPERED ***" right above the "*** UNLOCKED ***" message. Is this something to be concerned about, or is that par for the course with HTC bootloaders? Ie, does this show up once you actually try to flash something, even though you can still use `fastboot oem lock` after the fact?

nuclear_eclipse said:
No dice with this one either; gives the same "warning" message from HTC for about 5 seconds, then jumps to a blank screen and eventually reboots into Android.
However, I did notice that on the bootloader screen for my phone, it nows says "*** TAMPERED ***" right above the "*** UNLOCKED ***" message. Is this something to be concerned about, or is that par for the course with HTC bootloaders? Ie, does this show up once you actually try to flash something, even though you can still use `fastboot oem lock` after the fact?
Click to expand...
Click to collapse
Is the warning you get "This build is for development purposes only" etc?
Also, the tampered warning isn't anything to worry about. My HTC One X running CM10.1 has that warning. I think it occurs when you've made an attempt to modify a partition (probably after you tried flashing system.img).

dstaley said:
Is the warning you get "This build is for development purposes only" etc?
Click to expand...
Click to collapse
Yes. It's got the facebook f logo, and red text below it with that warning.
dstaley said:
Also, the tampered warning isn't anything to worry about. My HTC One X running CM10.1 has that warning. I think it occurs when you've made an attempt to modify a partition (probably after you tried flashing system.img).
Click to expand...
Click to collapse
Ok, that's what I was hoping. I just wasn't paying too close of attention to it the past couple days, and it just now caught my eye, so I have no idea exactly when it showed up...

Can you try mounting the recovery partition (I think it was mmcblk0p21?) and inspecting the files? I can't seem to do so for some reason. I'm curious to see if there are any files in there we can use.

dstaley said:
Can you try mounting the recovery partition (I think it was mmcblk0p21?) and inspecting the files? I can't seem to do so for some reason. I'm curious to see if there are any files in there we can use.
Click to expand...
Click to collapse
I have tried mounting as ext3/4, vfat, and yaffs, all without success... Makes me wonder if the images pulled from the phone are somehow incorrect...

[INFO]Partition List HTC ONE M8 / RAW DUMP SCRIPT

Hello Everyone,
I needed the partition read-out of the M8 and thought i can as well leave it here for you as a reference.
I might also extend this to a custom firmware section if no one else takes the job before (see my M7 stuff) once i got the phone.
Well anyhow, here's the list, it's not complete yet, i will further it with the names of the corresponding RUU images for who might find it helpful (should i get device and RUU's rather soon. If not this will be abandoned )
[EDIT]
IF you guys want to dump your brand spanking new M8 as a raw full dump (not sure a restore later works out but better have this, right? ) you can run this batch script, it will pull all partitions EXCEPT userdata (the "sdcard") first to SD and then to PC.
Run the EXE (its a self extracting WinRAR5 archive - i SWEAR its not evil! Its not gonna steal your pizza!
Its just a simple batch for now, the exe will only extract it to C:\Android\com. Then you can double click the batch script and it will attempt to pull the first 46 partitions as RAW material.
Its not really meant as a backup solution for average Joe, its more like giving you an easy method to create a (nearly) full dump of a (nearly) virgin device so there's a way back to (nearly) original state when we get S-OFF (a restore of this will never work with S-ON).
And its probably more a handy script for those of you who do the developing part here. You will know how to adjust the script so it runs wherever and does whatever, you may just use it as a repository of dd pull commands. Save you some typing
M8-Dumper (47 Partitions GSM model)
[EDIT]
Code:
echo. "HTC One / M8 FULL DUMP Script"
echo. ================================
echo.
echo. Warning: the DUMP on M8 can use many Gigabytes free
echo. space on the SDcard! Please make sure that you have
echo. at least 50% free space on your card.
echo. Since SDCard is now part of the /data Partition, i
echo. will not dump /data (around 10 GB) either.
echo. You also absoutely need to get a modified Boot.img
echo. with Insecure ADB added from somewhere or else this
echo. will NOT work!
....
This means: you need to Unlock, flash Custom Recovery, Root, flash Unsecure kernel before you can work with this script. So, Recovery, Boot and System will already be modified when dumping. The other 40+ partitions will be original.
Handy links:
@Guich's Stock Recovery Thread
@Mr Hofs Stock Backup Thread

Nice work, Sneaky, and yes, looking forward to you working your magic on M8 firmware! Waiting on my M8 Dev edition, should ship in a week or so. Really happy to see you here mate, cheers!

Not quite there yet. Still looking for cash or free devices
Could become June before I'll be able to buy it. We shall see.
«--=|[Mobile Viper bite]|=--»

Thanks for the Partition Table! I'll be using this in my toolkit!

Hey sneaky, good to see you here too. Will get my m8 tomorrow.
Verstuurd vanaf mijn HTC One met Tapatalk

Snah001 said:
Hey sneaky, good to see you here too. Will get my m8 tomorrow.
Verstuurd vanaf mijn HTC One met Tapatalk
Click to expand...
Click to collapse
Yeah! Nice to hear that... Seems like virtually every dev with a name around here gets it. Gonna be a mad and exciting year.
Called my carrier today, they have it on pre-order as well now. I can have it for about 400 and keep the M7. So I'll sell that and get the M8 for about 100 quid including excellent two year service.
Thinking about it,I actually haven't paid that little for a good phone in a while
Expect me here within the month.
SixthSenseSuxx... visually... time for venom theming...

@Sneakyghost :
hi mate,
any news how to remove the red warning ?
remeber on M7 that I used yours excellents mods ...
tks bro

jonata said:
@Sneakyghost :
hi mate,
any news how to remove the red warning ?
remeber on M7 that I used yours excellents mods ...
tks bro
Click to expand...
Click to collapse
Not until S-Off iirc.

S-OFF first. Before that, no firmware packs whatsoever. Sorry.
SixthSenseSuxx... visually... time for venom theming...

Could be soon.
http://forum.xda-developers.com/showthread.php?t=2706553

@Sneakyghost s-off is here! Time to get up and start making those amazing FUUs and ZIPs!
Will be getting my m8 within the month (hopefully)
Sent from my iPod touch using Tapatalk

n1234d said:
@Sneakyghost s-off is here! Time to get up and start making those amazing FUUs and ZIPs!
Will be getting my m8 within the month (hopefully)
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
https://twitter.com/Sneakygh0st/status/452941752186712065
Seen and retweeted it 25 minutes after they tweeted. While being half asleep in the middle of the night.
It's my birthday too soon. I'm going shopping then. Thank God some really nice people here already helped finance it a bit. Got about 10% now. That means I'll stick to what I said: I'll have it within the month (April).
[EDIT]
It's gonna be here Friday.
Some good people helped me out a bit, thank you guys.
Will start working here once I've achieved S-OFF. Hope I'm not gonna run into the fails many others have been seeing with firewater.

Sneakyghost said:
https://twitter.com/Sneakygh0st/status/452941752186712065
Seen and retweeted it 25 minutes after they tweeted. While being half asleep in the middle of the night.
It's my birthday too soon. I'm going shopping then. Thank God some really nice people here already helped finance it a bit. Got about 10% now. That means I'll stick to what I said: I'll have it within the month (April).
[EDIT]
It's gonna be here Friday.
Some good people helped me out a bit, thank you guys.
Will start working here once I've achieved S-OFF. Hope I'm not gonna run into the fails many others have been seeing with firewater.
Click to expand...
Click to collapse
Happy Birthday !!!!!!!!!
when have time, and party is over ...
no red warning ?
tks bro and again HAPPY BIRTHDAY

here you go
Verison M8 with ARHD on it:
dev: size erasesize name
mmcblk0p1: 00100000 00000200 "sbl1"
mmcblk0p2: 076f7c00 00000200 "pg1fs"
mmcblk0p3: 00004000 00000200 "board_info
mmcblk0p4: 00800000 00000200 "reserve_1"
mmcblk0p5: 00040000 00000200 "mfg"
mmcblk0p6: 017afc00 00000200 "pg2fs"
mmcblk0p7: 00040000 00000200 "sbl1_updat
mmcblk0p8: 00040000 00000200 "rpm"
mmcblk0p9: 00200000 00000200 "tz"
mmcblk0p10: 00008000 00000200 "sdi"
mmcblk0p11: 00400000 00000200 "hboot"
mmcblk0p12: 00500000 00000200 "sp1"
mmcblk0p13: 00100000 00000200 "wifi"
mmcblk0p14: 00008000 00000200 "ddr"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p17: 00500000 00000200 "wcnss"
mmcblk0p18: 00800000 00000200 "radio_con
mmcblk0p19: 00180000 00000200 "fsg"
mmcblk0p20: 04b00400 00000200 "radio"
mmcblk0p21: 00400000 00000200 "tool_diag
mmcblk0p22: 03200000 00000200 "custdata"
mmcblk0p23: 00effc00 00000200 "reserve_2
mmcblk0p24: 00100000 00000200 "misc"
mmcblk0p25: 00180000 00000200 "modem_st1
mmcblk0p26: 00180000 00000200 "modem_st2
mmcblk0p27: 01400000 00000200 "fataldevl
mmcblk0p28: 00001000 00000200 "debug_con
mmcblk0p29: 00040000 00000200 "pdata"
mmcblk0p30: 00004000 00000200 "control"
mmcblk0p31: 00140400 00000200 "local"
mmcblk0p32: 00010000 00000200 "extra"
mmcblk0p33: 00100000 00000200 "cdma_reco
mmcblk0p34: 00000400 00000200 "fsc"
mmcblk0p35: 00002000 00000200 "ssd"
mmcblk0p36: 00040000 00000200 "skylink"
mmcblk0p37: 01900000 00000200 "carrier"
mmcblk0p38: 00040000 00000200 "sensor_hu
mmcblk0p39: 01e00000 00000200 "devlog"
mmcblk0p40: 00002800 00000200 "cir_img"
mmcblk0p41: 01000000 00000200 "vzw_quali
mmcblk0p42: 01de6000 00000200 "reserve"
mmcblk0p43: 01000000 00000200 "boot"
mmcblk0p44: 01800000 00000200 "recovery"
mmcblk0p45: 05800000 00000200 "reserve_3
mmcblk0p46: a8000000 00000200 "system"
mmcblk0p47: 40000000 00000200 "cache"
mmcblk0p48: 30000000 00000200 "userdata"

jonata said:
Happy Birthday !!!!!!!!!
when have time, and party is over ...
no red warning ?
tks bro and again HAPPY BIRTHDAY
Click to expand...
Click to collapse
You have S-OFF?
I suggest you find yourself a copy of UltraEdit (buy it, its good!) and then head over to my M7 Firmware thread and look up how to edit your hboot yourself. If you stick EXACTLY to my instructions, its not dangerous. If you mess up, it is.
Like i said, i am NOT going to provide hboots i have not tested myself. Because with this file, there are two options only: either it works 100% or it bricks your device. Any error kills it. I am not going to modify it and let others test it. I would feel very bad. Sorry.
If you don't want to do that yourself, you will have to wait until my phone is here (hopefully friday) and then i can start working on it (if i manage to S-OFF it).

Verizon:
Partition Table:
Code:
D:\>adb shell cat /proc/emmc
dev: size erasesize name
mmcblk0p1: 00100000 00000200 "sbl1"
mmcblk0p2: 076f7c00 00000200 "pg1fs"
mmcblk0p3: 00004000 00000200 "board_info"
mmcblk0p4: 00800000 00000200 "reserve_1"
mmcblk0p5: 00040000 00000200 "mfg"
mmcblk0p6: 017afc00 00000200 "pg2fs"
mmcblk0p7: 00040000 00000200 "sbl1_update"
mmcblk0p8: 00040000 00000200 "rpm"
mmcblk0p9: 00200000 00000200 "tz"
mmcblk0p10: 00008000 00000200 "sdi"
mmcblk0p11: 00400000 00000200 "hboot"
mmcblk0p12: 00500000 00000200 "sp1"
mmcblk0p13: 00100000 00000200 "wifi"
mmcblk0p14: 00008000 00000200 "ddr"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p17: 00500000 00000200 "wcnss"
mmcblk0p18: 00800000 00000200 "radio_config"
mmcblk0p19: 00180000 00000200 "fsg"
mmcblk0p20: 04b00400 00000200 "radio"
mmcblk0p21: 00400000 00000200 "tool_diag"
mmcblk0p22: 03200000 00000200 "custdata"
mmcblk0p23: 00effc00 00000200 "reserve_2"
mmcblk0p24: 00100000 00000200 "misc"
mmcblk0p25: 00180000 00000200 "modem_st1"
mmcblk0p26: 00180000 00000200 "modem_st2"
mmcblk0p27: 01400000 00000200 "fataldevlog"
mmcblk0p28: 00001000 00000200 "debug_config"
mmcblk0p29: 00040000 00000200 "pdata"
mmcblk0p30: 00004000 00000200 "control"
mmcblk0p31: 00140400 00000200 "local"
mmcblk0p32: 00010000 00000200 "extra"
mmcblk0p33: 00100000 00000200 "cdma_record"
mmcblk0p34: 00000400 00000200 "fsc"
mmcblk0p35: 00002000 00000200 "ssd"
mmcblk0p36: 00040000 00000200 "skylink"
mmcblk0p37: 01900000 00000200 "carrier"
mmcblk0p38: 00040000 00000200 "sensor_hub"
mmcblk0p39: 01e00000 00000200 "devlog"
mmcblk0p40: 00002800 00000200 "cir_img"
mmcblk0p41: 01000000 00000200 "vzw_quality"
mmcblk0p42: 01de6000 00000200 "reserve"
mmcblk0p43: 01000000 00000200 "boot"
mmcblk0p44: 01800000 00000200 "recovery"
mmcblk0p45: 05800000 00000200 "reserve_3"
mmcblk0p46: a8000000 00000200 "system"
mmcblk0p47: 40000000 00000200 "cache"
mmcblk0p48: 30000000 00000200 "userdata"
Mount:
Code:
D:\HTC One>adb shell
[email protected]_m8wl:/ $ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p46 /system ext4 ro,seclabel,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p47 /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p39 /devlog ext4 rw,seclabel,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p27 /fataldevlog ext4 rw,seclabel,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/radio /firmware/radio vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/adsp /firmware/adsp vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/wcnss /firmware/wcnss vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p22 /custdata ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:129 /mnt/media_rw/ext_sd texfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,umask=0007,allow_utime=0020,nls=utf8,min_prealloc_size=64k,readahead=4M,fail_safe,discard,errors=continue 0 0
/dev/block/vold/179:129 /mnt/secure/asec texfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,umask=0007,allow_utime=0020,nls=utf8,min_prealloc_size=64k,readahead=4M,fail_safe,discard,errors=continue 0 0
/dev/fuse /storage/ext_sd fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]_m8wl:/ $

Sneakyghost said:
You have S-OFF?
I suggest you find yourself a copy of UltraEdit (buy it, its good!) and then head over to my M7 Firmware thread and look up how to edit your hboot yourself. If you stick EXACTLY to my instructions, its not dangerous. If you mess up, it is.
Like i said, i am NOT going to provide hboots i have not tested myself. Because with this file, there are two options only: either it works 100% or it bricks your device. Any error kills it. I am not going to modify it and let others test it. I would feel very bad. Sorry.
If you don't want to do that yourself, you will have to wait until my phone is here (hopefully friday) and then i can start working on it (if i manage to S-OFF it).
Click to expand...
Click to collapse
thanks for reply and again AUGURI
I'm a little bit afraid, and have a lot of time to await
so, next friday, next week ... when you receive your M8 and got S-OFF
I await you
Thanks again

Sneaky partions from my HTC__001https://www.dropbox.com/s/zypbska37jh8xgm/partitions.txt
Sent from my HTC One_M8 using xda app-developers app

Sneakyghost said:
You have S-OFF?
I suggest you find yourself a copy of UltraEdit (buy it, its good!) and then head over to my M7 Firmware thread and look up how to edit your hboot yourself. If you stick EXACTLY to my instructions, its not dangerous. If you mess up, it is.
Like i said, i am NOT going to provide hboots i have not tested myself. Because with this file, there are two options only: either it works 100% or it bricks your device. Any error kills it. I am not going to modify it and let others test it. I would feel very bad. Sorry.
If you don't want to do that yourself, you will have to wait until my phone is here (hopefully friday) and then i can start working on it (if i manage to S-OFF it).
Click to expand...
Click to collapse
Hi Sneaky.
I removed the red text myself, remembered when we did this together on the M7 in the very beginning.
When you want I can send you my orig.hboot and the altered one (3.16) by PM so you can use it. Oh and of course it works

Snah001 said:
Hi Sneaky.
I removed the red text myself, remembered when we did this together on the M7 in the very beginning.
When you want I can send you my orig.hboot and the altered one (3.16) by PM so you can use it. Oh and of course it works
Click to expand...
Click to collapse
:highfive:

How to Read Specific Region on HTC Desire C.?

hi all and android experts..
is there any command for read specific region on HTC Desire C device..? like this; cat /proc/dumchar_info (this is for mtk devices)
Code:
cat /proc/dumchar_info
Part_Name Size StartAddr Type MapTo
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
android 0x0000000020100000 0x0000000001de4000 2 /dev/block/mmcblk0p6
cache 0x0000000020100000 0x0000000021ee4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000020100000 0x0000000041fe4000 2 /dev/block/mmcblk0p3
fat 0x0000000083f1c000 0x00000000620e4000 2 /dev/block/mmcblk0p4
bmtpool 0x0000000000a00000 0x00000000ff9f0050 2 /dev/block/mmcblk0
Part_Name:Partition name you should open;
Size:size of partition
StartAddr:Start Address of partition;
Type:Type of partition(MTD=1,EMMC=2)
MapTo:actual device you operate
when i enter the cat /proc/emmc/
Code:
dev: size erasesize name
mmcblk0p17: 00040000 00000200 "misc"
mmcblk0p21: 0087f400 00000200 "recovery"
mmcblk0p22: 00400000 00000200 "boot"
mmcblk0p25: 31dffe00 00000200 "system"
mmcblk0p28: 0afffe00 00000200 "cache"
mmcblk0p26: 3cfffe00 00000200 "userdata"
mmcblk0p29: 017ade00 00000200 "devlog"
mmcblk0p31: 00040000 00000200 "pdata"
mmcblk0p32: 05ffe000 00000200 "fat"
mmcblk0p30: 00011c00 00000200 "extra"
[email protected]:/ #
but i wanna see emmc address like MTK devices.. is this possbile..?

You're posting in the wrong section, mate. There's a Question, Answer and Troubleshooting section specifically for Q&A.
Sent from my A0001 using XDA Premium 4 mobile app

rudi_j7 said:
You're posting in the wrong section, mate. There's a Question, Answer and Troubleshooting section specifically for Q&A.
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ooohh sorry for that... moderators can move to my thread to correct section...