Database Develop

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...

Htc one boots again and again, memory problem?

Hello, my problem is:
After an update from Htc my phone boot again and again.
Some times in recoverey it boot again.
sometimes data can not be mount, or cache can not be mount or unmount.
Installing an rom ends in bootloop.
The google rom starts up with google logo and colors. but also ends with a bootloop
Please help me

roluc said:
Hello, my problem is:
After an update from Htc my phone boot again and again.
Some times in recoverey it boot again.
sometimes data can not be mount, or cache can not be mount or unmount.
Installing an rom ends in bootloop.
The google rom starts up with google logo and colors. but also ends with a bootloop
Please help me
Click to expand...
Click to collapse
Hi, here's what I'd like you to do: reboot your phone into recovery and connect to PC, then
adb devices <- to confirm it's working
adb shell
~ # cat /proc/emmc
~ # mount
copy/paste the command prompt output and post here for us to take a look at, then we can proceed

nkk71 said:
Hi, here's what I'd like you to do: reboot your phone into recovery and connect to PC, then
adb devices <- to confirm it's working
adb shell
~ # cat /proc/emmc
~ # mount
copy/paste the command prompt output and post here for us to take a look at, then we can proceed
Click to expand...
Click to collapse
~ # ←[6ncat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
~ # ←[6nmount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,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)
/dev/block/mmcblk0p37 on /data type ext4 (rw,relatime,data=ordered)
/dev/block/mmcblk0p37 on /sdcard type ext4 (rw,relatime,data=ordered)
/dev/block/mmcblk0p36 on /cache type ext4 (rw,relatime,data=ordered)
/dev/block/mmcblk0p35 on /system type ext4 (rw,relatime,data=ordered)
~ # ←[6n

roluc said:
mmcblk0p37: 680000000 00000200 "userdata"
~ # ←[6nmount
/dev/block/mmcblk0p37 on /data type ext4 (rw,relatime,data=ordered)
/dev/block/mmcblk0p37 on /sdcard type ext4 (rw,relatime,data=ordered)
~ # ←[6n
Click to expand...
Click to collapse
/dev/block/mmcblk0p37 on /sdcard type ext4 (rw,relatime,data=ordered) <- hmm
ok now:
~ # umount /data
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
if e2fsck says it's still mounted, then
~ # umount /sdcard
and try again:
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
was you filesystem encrypted by any chance?
copy/paste back

nkk71 said:
/dev/block/mmcblk0p37 on /sdcard type ext4 (rw,relatime,data=ordered) <- hmm
ok now:
~ # umount /data
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
if e2fsck says it's still mounted, then
~ # umount /sdcard
and try again:
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
was you filesystem encrypted by any chance?
copy/paste back
Click to expand...
Click to collapse
I do not know if filesystem was encrypted, How can this be done?
~ # ←[6numount /data
umount /data
~ # ←[6ne2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p37
Filesystem mounted or opened exclusively by another program?
~ # ←[6numount /sdcard
umount /sdcard
~ # ←[6ne2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
64 inodes used (0.00%)
0 non-contiguous files (0.0%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 55
261437 blocks used (3.84%)
0 bad blocks
1 large file
2 regular files
52 directories
0 character device files
0 block device files
0 fifos
0 links
1 symbolic link (1 fast symbolic link)
0 sockets
--------
55 files
~ # ←[6n

roluc said:
I do not know if filesystem was encrypted, How can this be done?
~ # ←[6numount /data
umount /data
e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p37
Filesystem mounted or opened exclusively by another program?
~ # ←[6numount /sdcard
umount /sdcard
~ # ←[6ne2fsck -n -v -f /dev/block/mmcblk0p37
... 55 files
~ # ←[6n
Click to expand...
Click to collapse
filesystem doesn't seem to be corrupt at all, can you
~ # cd /data
~ # ls <- thats lowercase L not an i
~ # cd /data/media
~ # ls

nkk71 said:
filesystem doesn't seem to be corrupt at all, can you
~ # cd /data
~ # ls <- thats lowercase L not an i
~ # cd /data/media
~ # ls
Click to expand...
Click to collapse
i have already done some commands from your other post.
these are the results:
/data # ←[6ncd /data
cd /data
/data # ←[6nls
ls
/data # ←[6ncd data/media
cd data/media
/sbin/sh: cd: can't cd to data/media
/data # ←[6nls
ls
/data # ←[6n

roluc said:
i have already done some commands from your other post.
these are the results:
/data # ←[6ncd /data
cd /data
/data # ←[6nls
ls
/data # ←[6ncd data/media
cd data/media
/sbin/sh: cd: can't cd to data/media
/data # ←[6nls
ls
/data # ←[6n
Click to expand...
Click to collapse
/data # ←[6ncd /data/media
cd /data/media
/sbin/sh: cd: can't cd to /data/media
/data # ←[6n

roluc said:
i have already done some commands from your other post.
/data # ←[6ncd data/media
cd data/media
/sbin/sh: cd: can't cd to data/media
Click to expand...
Click to collapse
please note the command "cd /data/media" not "cd data/media". honestly please be careful with missing spaces, extra spaces, etc.
some of the commands (not yet but eventually) can be quite dangerous if mistyped, and if you end up formatting a wrong partition, you'll really have a brick on your hands.
So far it looks like the filesystem was encrypted, and not corrupt, and a simple wipe/format/factory rest, should do the job just fine, if it doesn't we can go for the "real" formatting, but let's not be too hasty about it.
---------- Post added at 06:08 PM ---------- Previous post was at 06:07 PM ----------
roluc said:
/data # ←[6ncd /data/media
cd /data/media
/sbin/sh: cd: can't cd to /data/media
/data # ←[6n
Click to expand...
Click to collapse
OK, just saw that after I typed the post, try a wipe / factory reset / format (whatever it's called in TWRP) of /data , /sdcard , /data/media

nkk71 said:
please note the command "cd /data/media" not "cd data/media". honestly please be careful with missing spaces, extra spaces, etc.
some of the commands (not yet but eventually) can be quite dangerous if mistyped, and if you end up formatting a wrong partition, you'll really have a brick on your hands.
So far it looks like the filesystem was encrypted, and not corrupt, and a simple wipe/format/factory rest, should do the job just fine, if it doesn't we can go for the "real" formatting, but let's not be too hasty about it.
---------- Post added at 06:08 PM ---------- Previous post was at 06:07 PM ----------
OK, just saw that after I typed the post, try a wipe / factory reset / format (whatever it's called in TWRP) of /data , /sdcard , /data/media
Click to expand...
Click to collapse
At wipe i get error unable to wipe /usb-otg
/data # ←[6ncd /data/media
cd /data/media
/data/media # ←[6nls
ls
/data/media # ←[6n
and this

roluc said:
At wipe i get error unable to wipe /usb-otg
/data # ←[6ncd /data/media
cd /data/media
/data/media # ←[6nls
ls
/data/media # ←[6n
and this
Click to expand...
Click to collapse
not "/usb-otg" that would refer to an external USB stick attached with an OTG cable. hold on while I install TWRP to see the options, I'll post back in a few minutes.....
PS: Hit the thanks button if I'm helping
---------- Post added at 06:24 PM ---------- Previous post was at 06:18 PM ----------
roluc said:
At wipe i get error unable to wipe /usb-otg
Click to expand...
Click to collapse
EDIT: do you insist on TWRP, I have CWM installed:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
could you flash it instead of TWRP:
in bootloader/FASTBOOT USB:
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
fastboot erase cache
fastboot reboot-bootloader
then enter RECOVERY, select "mounts and storage" -> "format /data and /data/media (/sdcard)"

nkk71 said:
not "/usb-otg" that would refer to an external USB stick attached with an OTG cable. hold on while I install TWRP to see the options, I'll post back in a few minutes.....
PS: Hit the thanks button if I'm helping
---------- Post added at 06:24 PM ---------- Previous post was at 06:18 PM ----------
EDIT: do you insist on TWRP, I have CWM installed:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
could you flash it instead of TWRP:
in bootloader/FASTBOOT USB:
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
fastboot erase cache
fastboot reboot-bootloader
then enter RECOVERY, select "mounts and storage" -> "format /data and /data/media (/sdcard)"
Click to expand...
Click to collapse
I see now clockworkmod recovery v6.0.3.2
e:can't mount /cache/recovery/command
e:can't mount /cache/recovery/log
e:can't open cache/recovery/log
e:can't mount /cache/recovery/last_log
e:can't open /cache/recovery/last_log
formatting /data...
after formatting i get back done

roluc said:
I see now clockworkmod recovery v6.0.3.2
e:can't mount /cache/recovery/command
e:can't mount /cache/recovery/log
e:can't open cache/recovery/log
e:can't mount /cache/recovery/last_log
e:can't open /cache/recovery/last_log
formatting /data...
after formatting i get back done
Click to expand...
Click to collapse
cant mount cache is perfectly normal.
now push you rom to your phone:
adb push <name of rom>.zip /data/media/
this will take anywhere between 5 to 15 minutes, after which it should report success, then in recovery "install zip" -> "choose zip" -> select the ROM you just pushed.
if at any point it reboots, let me know, and we'll just "real" format your /data partition (eventhough it does not look corrupted)

nkk71 said:
cant mount cache is perfectly normal.
now push you rom to your phone:
adb push <name of rom>.zip /data/media/
this will take anywhere between 5 to 15 minutes, after which it should report success, then in recovery "install zip" -> "choose zip" -> select the ROM you just pushed.
if at any point it reboots, let me know, and we'll just "real" format your /data partition (eventhough it does not look corrupted)
Click to expand...
Click to collapse
Okay the rom is now ready, must i install it?

roluc said:
Okay the rom is now ready, must i install it?
Click to expand...
Click to collapse
yep go to: install zip -> choose zip, select it and go through the installer

nkk71 said:
yep go to: install zip -> choose zip, select it and go through the installer
Click to expand...
Click to collapse
I am now installing android revulution hd by mike1986
Now rebooting
Htc is booting
now google and the collors
seeem to freez i see 4 points,
now rebooting
white screen with htc logo
reboots again withe htc logo
now google a four couloprd box
rebooting
white htc again
rebooing google and the 4 colours again and freezing
rebooting
white htc logo again.
and again white htc logo again
white htc again.
now for about 40 seconds
and again
shall i stop it?

roluc said:
I am now installing android revulution hd by mike1986
Now rebooting
Htc is booting
now google and the collors
seeem to freez i see 4 points,
now rebooting
white screen with htc logo
reboots again withe htc logo
now google a four couloprd box
rebooting
white htc again
rebooing google and the 4 colours again and freezing
rebooting
white htc logo again.
and again white htc logo again
white htc again.
now for about 40 seconds
and again
shall i stop it?
Click to expand...
Click to collapse
Sorry but have to go for about 15 minutes
Will you still be here?
Thanks for now hope to see you in a few minutes

roluc said:
I am now installing android revulution hd by mike1986
Now rebooting
Htc is booting
now google and the collors
seeem to freez i see 4 points,
now rebooting
Click to expand...
Click to collapse
what's that? the "rebooing google and the 4 colours again and freezing"
can you take a picture and post it please. also go to bootloader/FASTBOOT USB and post a "fastboot getvar all" (remove IMEI and s/n before posting)
---------- Post added at 07:03 PM ---------- Previous post was at 07:01 PM ----------
roluc said:
Sorry but have to go for about 15 minutes
Will you still be here?
Thanks for now hope to see you in a few minutes
Click to expand...
Click to collapse
No problem. I'll be here for a while, will let you know if I have to stop.
Hit the thanks button from time to time

nkk71 said:
what's that? the "rebooing google and the 4 colours again and freezing"
can you take a picture and post it please. also go to bootloader/FASTBOOT USB and post a "fastboot getvar all" (remove IMEI and s/n before posting)
---------- Post added at 07:03 PM ---------- Previous post was at 07:01 PM ----------
No problem. I'll be here for a while, will let you know if I have to stop.
Hit the thanks button from time to time
Click to expand...
Click to collapse
Here are the photo's

roluc said:
Here are the photo's
Click to expand...
Click to collapse
Ok this it
C:\mini-sdk>adb push romA.zip /data/media
2218 KB/s (452221989 bytes in 199.102s)
C:\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA369W*******
(bootloader) imei: 35786*********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.052s
C:\mini-sdk>

[Q] Htc One Bricked [SOLVED]

I bricked my phone trying to install some costum ROM.
I cant enter my recovery or boot the device.
Only thing i can enter is HBOOT 1.54.0000
If i try to go in recovery from it, it resets and it says over the htc logo at the start that it is entering recovery, and then for like a fraction of a second i see my CWM recovery and then it restarts again.
My bootloader is relocked. I cant do anything, any help?

Unlock your bootloader first and then flash a recovery. Then using adb sidelow of adb push send a Rom over to your phone and flash it. You should be fine
Sent from my HTC One using Tapatalk

How do i re-unlock my bootloader?

Search ?

Via HTCDev. The first you unlocked you got an unlock ticket in bin format.
Sent from my HTC One using Tapatalk

pavo122 said:
then for like a fraction of a second i see my CWM recovery and then it restarts again.
Click to expand...
Click to collapse
"fastboot erase cache" would solve that part ^^
pavo122 said:
How do i re-unlock my bootloader?
Click to expand...
Click to collapse
Are you s-on or s-off?

Found it!
But it says my device is not connected, i have htc drivers installed and everything.
Its connected via usb cable and in fastboot usb mode.
I have s-on

pavo122 said:
Found it!
But it says my device is not connected, i have htc drivers installed and everything.
Its connected via usb cable and in fastboot usb mode.
I have s-on
Click to expand...
Click to collapse
hboot 1.54, and s-on, and no rooted ROM ---> you need to unlock using HTCdev

nkk71 said:
hboot 1.54, and s-on, and no rooted ROM ---> you need to unlock using HTCdev
Click to expand...
Click to collapse
Just did, now im downloading CM 10.2 ROM for my phone. I tried to restore my ROM from CWM recovery but it cant "Can't mount /sdcard"
Probably because i cleared cache.

pavo122 said:
it cant "Can't mount /sdcard"
Probably because i cleared cache.
Click to expand...
Click to collapse
cant mount /sdcard
clearing the cache gives you this output:
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
nothing to do with /sdcard.

nkk71 said:
cant mount /sdcard
clearing the cache gives you this output:
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
nothing to do with /sdcard.
Click to expand...
Click to collapse
Yeah, but when i try to access my sdcart to install costum ROM i cant access it, can i install a ROM via fastboot command?

pavo122 said:
Yeah, but when i try to access my sdcart to install costum ROM i cant access it, can i install a ROM via fastboot command?
Click to expand...
Click to collapse
no only ruu.zip in fastboot ruu mode, but that won't work unless s-off.
i need a little more info please:
1- go to bootloader/FASTBOOT USB, and post a "fastboot getvar all" (remove IMEI and s/n before posting)
2- go to CWM recovery again, and open a shell "adb shell" then "~# mount"
EDIT: 3- you can try adb sideload

nkk71 said:
no only ruu.zip in fastboot ruu mode, but that won't work unless s-off.
i need a little more info please:
1- go to bootloader/FASTBOOT USB, and post a "fastboot getvar all" (remove IMEI and s/n before posting)
2- go to CWM recovery again, and open a shell "adb shell" then "~# mount"
EDIT: 3- you can try adb sideload
Click to expand...
Click to collapse
INFOversion: 0.5
INFOversion-bootloader: 1.54.0000
INFOversion-baseband: 4A.17.3250.14
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 2.24.401.8
INFOversion-misc: PVT SHIP S-ON
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 3894mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-d959c75800
INFOhbootpreupdate: 11
INFOgencheckpt: 0
I tryed adb shell, it gives me this http://prntscr.com/270h5i

pavo122 said:
INFOversion-bootloader: 1.54.0000
INFOversion-main: 2.24.401.8
INFOversion-misc: PVT SHIP S-ON
INFOproduct: m7_ul
INFOmodelid: PN0710000
INFOcidnum: HTC__032
I tryed adb shell, it gives me this http://prntscr.com/270h5i
Click to expand...
Click to collapse
ok /data is not mounted, not nice!!
in the shell can you check if it's corrupt:
~# e2fsck -n -v -f /dev/block/mmcblk0p37
example:
Code:
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
39356 inodes used (2.31%)
350 non-contiguous files (0.9%)
31 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 38933/54
4696398 blocks used (68.91%)
0 bad blocks
1 large file
36560 regular files
2426 directories
0 character device files
0 block device files
0 fifos
0 links
357 symbolic links (357 fast symbolic links)
4 sockets
--------
39347 files
~ #
don't repair anything just yet, let me know the output. also please copy/paste command prompt (preferred over screenshots)

Code:
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p
37
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Even i can see that im screwed

pavo122 said:
Code:
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p
37
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Even i can see that im screwed
Click to expand...
Click to collapse
hold on, be back in a few minutes, we're gonna "real" format your partition, and hope it's not a hardware fault!! gimme 5 mins or so...

nkk71 said:
hold on, be back in a few minutes, we're gonna "real" format your partition, and hope it's not a hardware fault!! gimme 5 mins or so...
Click to expand...
Click to collapse
ok, I'll wait! Thanks for helping bro, just have to point it out!

Try something before nkk71 gets your do some mounting and fixing...
http://d-h.st/9xX recovery 2.24.401.8.img - download and rename to recovery.img
Make sure you're in the bootloader go into fastboot and make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running
Phone will go out and start bootlooping. Now power off and go back to bootloader mode:
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into recovery and see if you have the same error?

pavo122 said:
ok, I'll wait! Thanks for helping bro, just have to point it out!
Click to expand...
Click to collapse
Dont worry hes good, Helped me back fully stock.. :good::good::good: @nkk71

pavo122 said:
ok, I'll wait! Thanks for helping bro, just have to point it out!
Click to expand...
Click to collapse
okay, so let's do this one step at a time shall we, no rushing into things, no panicking,
1- if it software ----> we can fix it
2- if it's hardware problem, no matter how much we try it's hardware
let's hope for number 1, and here we go:
in the shell
~ # cat /proc/emmc
Code:
~ # [B]cat /proc/emmc[/B]
cat /proc/emmc
dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
[B]mmcblk0p35: 73fffc00 00000200 "system" <-- we're gonna check this[/B]
mmcblk0p26: 00140200 00000200 "local"
[B]mmcblk0p36: 27fffe00 00000200 "cache" <-- we're gonna check this[/B]
[B]mmcblk0p37: 680000000 00000200 "userdata" <-- we're gonna check this[/B]
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
cache seems so me still mounted so:
~# umount /cache <-- (no "n"; it umount not unmount)
~# e2fsck -n -v -f /dev/block/mmcblk0p35
~# e2fsck -n -v -f /dev/block/mmcblk0p36
~# e2fsck -n -v -f /dev/block/mmcblk0p37 <- we know this is corrupt, but let's check the other too
post back and we'll take it from there...
---------- Post added at 08:08 PM ---------- Previous post was at 08:07 PM ----------
mctodd said:
Dont worry hes good, Helped me back fully stock.. :good::good::good: @nkk71
Click to expand...
Click to collapse
thanks for the vote of confidence, have you seen my SuperGuide (LOL, shameless advertising): http://forum.xda-developers.com/showthread.php?t=2541082

[Q] Full-wipe --> no ROM on SD --> mac OS issues

Hello guys,
first of all: thanks for the great things you're creating around the android os and for the useful and worthy enhancements, i really appreciate that...not just saying so because I'm in trouble..what I actually really am!
Had my HTC One M7 (unlocked boot loader) flashed with AR HD 62....had some issues with rebooting and freezing, so i wanted to do a full wipe...unfortunately (because of simply not really knowing too much about the function of the shell and android os itself) I deleted obviously everything...I think also the whole SD card, as it seems
So as it says in the title, I'm running a Mac for my flashing...and now the phone is out of reach somehow
I managed - as far as the terminal window and i can tell - to flash recovery by use of fast boot...but from that moment on, I don't know how to continue...
I also think, that my adb does not completely work...can't access the bootloader by using adb commands....
adb devices is listing the phone, but when I want do wipe it with fastboot -w, it reads "waiting for device"...nothing changes!
Can anyone tell me how to get on? This is the worst case I've had so far and I've been using custom roms and flashing since the Desire HD onwards...
Thanks in advance!
greetings from austria
alex

If you use CWM, you can use adb while in recovery. Just type in "adb push NAMEOFFILE /sdcard/rom.zip". Then reboot into recovery again and flash it. I don't think this works in TWRP, but it might...I've never tried it.

aooga said:
If you use CWM, you can use adb while in recovery. Just type in "adb push NAMEOFFILE /sdcard/rom.zip". Then reboot into recovery again and flash it. I don't think this works in TWRP, but it might...I've never tried it.
Click to expand...
Click to collapse
Yes, I'm running TWRP...and I've tried to do so...but if i type in the command an press enter, the terminal window just gets kinda inactive....it neither freezes nor reacts to commands any more from this moment on...
I hope there's something like the CWM procedure for TWRP, too...
However..thanks for your input!
Greetings Alex
Appendix:
*** TAMPERED ***
*** UNLOCKED ***
S-ON
HBOOT-1.44.0000
RADIO-4A.13.3231.27
I've already tried this http://forum.xda-developers.com/showthread.php?t=2318497, but my devices keeps being listed as "host" instead of "sideload"
If I want to push the file, the same issues as I described above turn up in context with the terminal window
How likely is it, that it's just my Mac that keeps me from successfully installing the ROM?!...I'm quite curious about that...

dr.zikzak said:
Yes, I'm running TWRP...and I've tried to do so...but if i type in the command an press enter, the terminal window just gets kinda inactive....it neither freezes nor reacts to commands any more from this moment on...
I hope there's something like the CWM procedure for TWRP, too...
.....
How likely is it, that it's just my Mac that keeps me from successfully installing the ROM?!...I'm quite curious about that... [/B]
Click to expand...
Click to collapse
I have a mac and I just tried it with twrp and it worked fine. What do you get when you run "adb devices" while in recovery.
Also, worst case, just run an RUU and root again.

Okay...so there seems to be sth wrong with me or the mac!
If I'm in fastboot usb, I get "list of devices attached"....and nothing else
If I'm in recovery, I get the ID of the device and "recovery" as the status
Oh my...I'm the man :-/
Greetings Alex

So when it comes to flashing RUU....i don't really know which one matches my HTC...
I got a 1.28.771.6 installed, CID is H3G_106...so I couldn't really find the matching file on the internet....which one can i use as an alternative?
Is there sth wrong with my bootloader itself? I can't access it via Mac as I was used to before...so adb reboot bootloader doesn't work at all...it also seems to be kind of a matter of luck what i get with the fastboot commands...sometimes I can e.g. read the version-main, a few seconds later it says "waiting for device" and I have to exit the terminal window...
Please be lenient with me if there's an obvious fallacy...
Would it make sense or is it even possible to flash CWM over TWRP to solve the sideload issue respectively mount the SD card?
Thanks and greetings
Alex

Is there a way to get SuperCID from my point?
Or flash another RUU than the original H3G? Are there any universal RUUs, just to get out of this misery at least?
Thanks!
Here some more input:
fastboot getvar all
Alexanders-MacBook-Pro:~ dr_zikzak$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.771.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35********
(bootloader) imei: 3544360******
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__106
(bootloader) battery-status: good
(bootloader) battery-voltage: 4249mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.042s
~ # mount
~ # mount
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
~ #
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Greetings Alex

dr.zikzak said:
Is there a way to get SuperCID from my point?
Greetings Alex
Click to expand...
Click to collapse
take a look at http://forum.xda-developers.com/showthread.php?p=51774312&postcount=50
(either the entire thread, from the beginning, or whatever part you think applies to you)
PS: this is for m7_u or m7_ul models only... Sprint and Verizon have different partitions

nkk71 said:
take a look at http://forum.xda-developers.com/showthread.php?p=51774312&postcount=50
(either the entire thread, from the beginning, or whatever part you think applies to you)
PS: this is for m7_u or m7_ul models only... Sprint and Verizon have different partitions
Click to expand...
Click to collapse
Hello!
Thanks for having a look...I've gone through the thread and did what pavel122 did, here are the results:
~ # cat /proc/emmc
dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
~ # umount /cache
umount: can't umount /cache: Invalid argument
~ # umount /data
~ # umount /data
umount: can't umount /data: Invalid argument
~ # umount /system
~ # umount /system
umount: can't umount /system: Invalid argument
~ # e2fsck -n -v -f /dev/block/mmcblk0p35
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
11 inodes used (0.01%)
0 non-contiguous files (0.0%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 3
15607 blocks used (3.28%)
0 bad blocks
0 large files
0 regular files
2 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
2 files
~ # e2fsck -n -v -f /dev/block/mmcblk0p36
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
18 inodes used (0.04%)
1 non-contiguous file (5.6%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 10
5279 blocks used (3.22%)
0 bad blocks
0 large files
6 regular files
3 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
9 files
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p37
Filesystem mounted or opened exclusively by another program?
What does it tell me...are the files okay? Should i mount data again?
And if so, just go to adb sideload in TWRP and try command "adb sideload ROM.zip" and it should work?
Thank you!
Greetings Alex

If I mount data again and go to sideload in TWRP and type "adb sideload ROM.zip", it gives me this:
Alexanders-MacBook-Pro:Android dr_zikzak$ adb push /Users/dr_zikzak/Desktop/Android/R62.zip
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number is specified.
Using this ocmmand with no additional arguments
will disconnect from all connected TCP/IP devices.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.
By the way, as it does neither work the one, nor the other way: is "adb sideload ROM.zip" just to name the zips only name or the whole path?
Thanks!

If I check with the e2fsck commands, it shows exactly the same as pavel122 device!
data is in use or still mounted --> but if i force "umount /data", it says:
~ # umount /data
umount: can't umount /data: Invalid argument
If i mount data and go with that, i can actually send sth. to the device with "adb sideload"...but if I want to install the zip, it fails!
What to do?
Thanks and greetings Alex

You can never "sideload" an entire rom. Thats just for updating a current rom, thats why you fail. The md5sum checks will not add up.
The mmcblk0p35 is the userdata partition so why was it busy? Either way it doesn´t matter.
If all you need to do is copy a complete rom to your phone from you computer the command is
Code:
adb push filename.zip /sdcard/download
and the rom should end up in your download folder on your phone. Install it from the menu in recovery.

xxerkxx said:
You can never "sideload" an entire rom. Thats just for updating a current rom, thats why you fail. The md5sum checks will not add up.
The mmcblk0p35 is the userdata partition so why was it busy? Either way it doesn´t matter.
If all you need to do is copy a complete rom to your phone from you computer the command is
Code:
adb push filename.zip /sdcard/download
and the rom should end up in your download folder on your phone. Install it from the menu in recovery.
Click to expand...
Click to collapse
1- you can sideload an entire ROM, it has nothing to do with updating current ROM
2- mmcblk0p35 is: mmcblk0p35: 73fffc00 00000200 "system" not userdata
dr.zikzak said:
If I check with the e2fsck commands, it shows exactly the same as pavel122 device!
data is in use or still mounted --> but if i force "umount /data", it says:
~ # umount /data
umount: can't umount /data: Invalid argument
If i mount data and go with that, i can actually send sth. to the device with "adb sideload"...but if I want to install the zip, it fails!
What to do?
Thanks and greetings Alex
Click to expand...
Click to collapse
Did you fix (ie format) the partition?
this error:
Code:
~ # umount /data
umount: can't umount /data: Invalid argument
is normal if it's already unmounted, but did you also umount /sdcard
then run e2fsck
if you still get errors you need to format it, not just wipe.
Once the format is complete, you can either:
1- OTG cable
2- adb push <name of rom>.zip /sdcard/
3- initiate sideload in custom recovery, then adb sideload <name of rom>.zip
.

imo, it is much easier (and safer) to get yourself an USB OTG cable / cardreader and write your backup to it and flash your roms from it
I use this one LINK
Whats sucks more than eraseing that last backup when you do a full wipe by accident. next to that, when i switch to a complete other rom I always do a full wipe. realy helps the stability of your rom

nkk71 said:
1- you can sideload an entire ROM, it has nothing to do with updating current ROM
2- mmcblk0p35 is: mmcblk0p35: 73fffc00 00000200 "system" not userdata
Did you fix (ie format) the partition?
this error:
Code:
~ # umount /data
umount: can't umount /data: Invalid argument
is normal if it's already unmounted, but did you also umount /sdcard
then run e2fsck
if you still get errors you need to format it, not just wipe.
Once the format is complete, you can either:
1- OTG cable
2- adb push <name of rom>.zip /sdcard/
3- initiate sideload in custom recovery, then adb sideload <name of rom>.zip
.
Click to expand...
Click to collapse
Hello again!
I'm just writing this from the HTC One...unbelievable
Thanks for your help....I was on the brink of smashing it yesterday!
I've gone through the e2fsck once again and it seemed okay...so I tried to push the rom as it is supposed, so just the zip name and correct order of steps!
I also asked mike1986. for his opinion and he told me that the "freezing" does only look as if it freezes....
A mistake I made was not to wait until the cursor started blinking again when I was pushing the rom over to the device....I didn't notice that there was a running process...no percentage or something!
So I tried again and pushed the ROM again...it took approx 7 minutes and the cursor started blinking again...
The file was completely transferred and so I could start flashing it fr recovery! Worked at first attempt, no bootloop or crashes!
The phone is smooth again..even better than before I dare say....
I've learned a lot, especially from you, Mr. nkk71..thank you for spending so much time on the problems caused by the stupidity of people like me
THANKS THANKS THANKS very much!
Greetings Alex

Thanks for the info about sideload, didn´t know that it could replace the entire rom!
nkk71 said:
1- you can sideload an entire ROM, it has nothing to do with updating current ROM
2- mmcblk0p35 is: mmcblk0p35: 73fffc00 00000200 "system" not userdata
.
Click to expand...
Click to collapse
It was i typo from my part I ment blk37:
e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p37
Filesystem mounted or opened exclusively by another program?
Click to expand...
Click to collapse

dr.zikzak said:
Hello again!
I'm just writing this from the HTC One...unbelievable
Thanks for your help....I was on the brink of smashing it yesterday!
I've gone through the e2fsck once again and it seemed okay...so I tried to push the rom as it is supposed, so just the zip name and correct order of steps!
I also asked mike1986. for his opinion and he told me that the "freezing" does only look as if it freezes....
A mistake I made was not to wait until the cursor started blinking again when I was pushing the rom over to the device....I didn't notice that there was a running process...no percentage or something!
So I tried again and pushed the ROM again...it took approx 7 minutes and the cursor started blinking again...
The file was completely transferred and so I could start flashing it fr recovery! Worked at first attempt, no bootloop or crashes!
The phone is smooth again..even better than before I dare say....
I've learned a lot, especially from you, Mr. nkk71..thank you for spending so much time on the problems caused by the stupidity of people like me
THANKS THANKS THANKS very much!
Greetings Alex
Click to expand...
Click to collapse
yeah, sorry, i should have mentioned that, i should have actually linked this:
Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [I][B]<- yes, it took over 5 mins,
[U]without[/U] showing any progress[/B][/I]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
xxerkxx said:
Thanks for the info about sideload, didn´t know that it could replace the entire rom!
It was i typo from my part I ment blk37:
Click to expand...
Click to collapse
no worries, just pointed it out so the OP doesn't get confused, and adb sideload can install a full ROM with no problems:
in TWRP recovery -> Advanced -> ADB Sideload -> swipe
C:\ADB3>adb devices
List of devices attached
HT34xxxxxxxx sideload
^^ now you're in sideload, and can start adb sideload rom.zip
I believe sideload even shows progress, though I've never used it, I prefer push

It was just my mistake...could have waited a little longer, couldn't I? ....patience has never been one of my virtues
Nonetheless everything's fine and I'm happy again...
I should also remain behind increasing my knowledge about android an it's components...just to know what I'm actually doing and what is possible with this system!
What would you recommend? Just read the forum or is there any source where I can read about that...just basics about the system itself...
Thanks once more and keep it up, really appreciate it!
Greetings Alex

dr.zikzak said:
What would you recommend? Just read the forum or is there any source where I can read about that...just basics about the system itself...
Click to expand...
Click to collapse
yeah mostly the forum and also @mike1986. blog has very good info: http://android-revolution-hd.blogspot.com/p/android-guides.html

[Q] unable to mount + internal storage 0mb + stuck in hboot

Background :
Rooted phone and installed Cyanogen rom, then installed PackMan rom then HTC Google Edition rom. Everything was working perfect for a year.
The phone was always in protective silicon case and didn't give me any problems.
Problem :
Without installing any new application or change any settings or anything other then normal daily use. One day, out of the blue (didnt fell or anything), the screen wouldn’t turn on, but the screen touch buttons at bottom would lite up.
Did hard reset but then it kept getting stuck or screen again and again, the screen wouldn’t turn on, kept doing more and more and more hard resets. Sometimes after hard reset it would get to the “slide to unlock” screen and once i would unlock it would get stuck, so more hard resets.
Then after the 10th ~ hard reset it seemed to rollback on its own to the factory rom without my apps and contacts. But still get stuck and more hard resets. After the 13th ~ hard reset it got stuck on the green HTC logo with white background.
TWRP shows E: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount internal storage
and Internal Storage 0MB
Current status:
Booting directly to hboot menu and nothing else.
Fastboot is working
ADB and ADB Shell is working
Booting into TWRP command : fastboot boot openrecovery-twrp-2.8.3.0-m7.img
Booting into philz command : fastboot boot philz_touch_6.15.4-m7ul.img
I’m not able to get to the RUU mode (black screen with silver HTC logo) !
flashing recovery twrp and then selecting recovery at the hboot menu will not get into twrp. only
fastboot boot openrecovery-twrp-2.8.3.0-m7.img
will get me into twrp
Version :
Unlocked
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.00000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
May 4 2013, 14:29:10:-1
Device Screenshots :
From TWRP and philpz
the forum will not let me post outside url image links. you can see the images in the word document i've uploaded
Solution attempts:
TWRP “Restore from backup” failed. And now there are no backups.
Was able to copy zip rom but wasn’t able to install it (cannot mount errors)
I’m not able to get to the RUU mode (black screen with silver HTC logo)
found many posts in many forms and youtube videos but wasn't able to fix
output of 'fastboot getvar all' :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.631.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT367W913960
(bootloader) imei: 354439051186122
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4270mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.044s
“fastboot oem lock” output :
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.244s
“fastboot oem rebootRUU” reboots back to hboot menu.
I’m not able to get to the RUU mode (black screen with silver HTC logo) !
Getting ADB to respond :
“adb devices” command output :
List of devices attached
HT***numbers**** sideload
“adb shell“ command output:
error: closed
the forum will not let me post outside url image links. you can see the images in the word document i've uploaded
Then
“adb shell“ command output:
~ # ←[6n
Which is good!
according to htcdev.com/bootloader/rom_flashing_guide#flashing_from_device
“cd /proc/” command output :
cd /proc/
~ # ←[6ncd /proc/
“cat emmc/” command output
cat emmc
dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
/proc # ←[6n
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p33
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p33
12968+0 records in
12968+0 records out
6639616 bytes (6.3MB) copied, 2.222748 seconds, 2.8MB/s
/proc # ←[6nreboot
Ouput of command “adb shell dmesg > dmesg_log1.txt” is attached
Important to notice in the dmesg :
<3>[ 15.868743] EXT4-fs (mmcblk0p37): VFS: Can't find ext4 filesystem
<3>[ 16.723510] EXT4-fs (mmcblk0p36): VFS: Can't find ext4 filesystem
this is the closest posts I could find :
http://forum.xda-developers.com/showthread.php?t=2300511
http://forum.xda-developers.com/htc-one/help/0-mb-internal-storage-t2993567
I am completely lost and miss my HTC. any advise?

shariksharik said:
TWRP shows E: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount internal storage
and Internal Storage 0MB
Click to expand...
Click to collapse
Corrupted data partition? Boot twrp 2.6.3.3 go in wipe --> format data --> then reboot the recovery and see if your Internal storage is showing the correct size instead of 0MB. If yes push and flash a rom.
What version of ADB and HTC drivers that you are using?
What is very strange is that you can't boot in ruu mode and that you can't flash the recovery. Just in case, have you erased cache and rebooted the bootloader after flashing the recovery?
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Im starting to think your phone is having an hardware problem. Would explain why it bootlooped and that your bootloader looks bricked.
Where is parition p25? It should be listed when you do "cat proc/emmc"
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
mmcblk0p25 ???
Click to expand...
Click to collapse

first of all thank you for your quick response.
I will try to answer everything you wrote in the best accuracy and details i can.
Boot twrp 2.6.3.3 go in wipe --> format data --> then reboot the recovery and see if your Internal storage is showing the correct size instead of 0MB.
Click to expand...
Click to collapse
i did this
Code:
fastboot boot openrecovery-twrp-2.6.3.3-m7.img
it loaded twrp
i did "wipe ->format data" results attached.
then i did reboot , it got me back to the hboot menu
to enter twrp i again
Code:
fastboot boot openrecovery-twrp-2.6.3.3-m7.img
and internal storage still 0MB
and the output is :
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
What version of ADB and HTC drivers that you are using?
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.31
how do I know what version of HTC drivers i am using? according to the Device Manager there is "HTC MTP Device" under "Portable Devices" node its version is 1.0.0.20. is this what you meant? btw there is a small yellow warning triangle on that "HTC MTP Device". not sure if it should be like that.
have you erased cache and rebooted the bootloader after flashing the recovery?
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
where can i get recovery.img ? do you mean recovery.img is openrecovery-twrp-2.6.3.3-m7.img ? can you give me more input on this ?
Where is parition p25? It should be listed when you do "cat proc/emmc"
Click to expand...
Click to collapse
i noticed that i can use adb only with openrecovery-twrp-2.8.3.0-m7.img and not with 2.6.3.3
i ran
Code:
cat emmc
again and confirmed p25 is not there. to be fair if you look here "htcdev.com/bootloader/rom_flashing_guide#flashing_from_device" also dont have p25, my output is exactly as the one in that link.

i did "wipe ->format data" results attached.
Click to expand...
Click to collapse
forgot to attach the result. now attached

Sadly probably a bad EMMC. This means it is able to mouth the drive, and the ability to only boot TWRP 2.8.3.0 (pushes it self to the memory completely b4 running, uses no Storage space) and not older versions (which don't) only reaffirms that sad reality. The fact that you can't boot to recovery from HBOOT reaffirms it again, as HBOOT mounts system and then finds the recovery partition to boot by looking in the mount area symlinks on the system partition, which in your case, doesn't exist.
The other possibility is a corrupted partition map, but that would most likely require JTAG recovery, which you can google, bit is ridiculously hard.
Another possibility is using a debrick image and pushing it through QCOM download mode, but I'm unsure of how to get to QCOM mode on the M7 (maybe try googling it?)
---------- Post added at 11:14 PM ---------- Previous post was at 11:12 PM ----------
Ok. Wait I failed to read the cat prof output, huh, so the eMMC is mounting, must be a faulty partition map. Use ext4unpacker to check and see if that recovery IMG you made is legit, or broken, if its a legit IMG, then that could help us out [emoji14]
---------- Post added at 11:17 PM ---------- Previous post was at 11:14 PM ----------
Hmmm. May have figured it out. If you accidentally used a recovery meant for a slightly different m7, wiping data could have wiped a low level boot loader partition instead...

thank you for replying .
npjohnson said:
Use ext4unpacker to check and see if that recovery IMG you made is legit, or broken, if its a legit IMG, then that could help us out
Click to expand...
Click to collapse
what recovery IMG that I made? i didnt make any recovery.
can you give me more details about ext4unpacker . i found this http://forum.xda-developers.com/showthread.php?t=2294909 , will this help me?
npjohnson said:
Hmmm. May have figured it out. If you accidentally used a recovery meant for a slightly different m7, wiping data could have wiped a low level boot loader partition instead...
Click to expand...
Click to collapse
yes it is possible i did flash something that was not meant exactly for my m7....

My bad, you made a boot image with Dd=. Could you use the same method to dump your system and recovery partitions?
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
And then just google how to extract a system.IMG. it will probably require ext4unpacker.

npjohnson said:
My bad, you made a boot image with Dd=.
Click to expand...
Click to collapse
you are correct, i did try to put a boot.img that i found online but i am not sure its 100% for my device version, it was a "hail marry" attempt.
npjohnson said:
Could you use the same method to dump your system and recovery partitions?
And then just google how to extract a system.IMG. it will probably require ext4unpacker.
Click to expand...
Click to collapse
i'm sorry i am somewhat a noob in linux and the core stuff like adb and fastboot, i learned what i could from other posts and tutorials. i didn't understand what you meant, if i will dump system.img and recovery.img partitions why would i need to extract them afterwords ?

i've been writing back and forth with HTC, i gave them all this info and they gave me a zip (1.1GB) to flash.
PN07IMG_M7_UL_JB43_SENSE50_MR_Rogers_WWE_3.22.631.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336568_signed_2.zip
however, after i've downloaded the zip, if i try to open it with winzip it will say "Error: central directory not found" , this tells me that it might be corrupted download, so i downloaded it again and again and again, using chrome, using explorer, it keeps saying the same. i've also opened it in winrar and it does show me the content. inside i can see :
boot_signed.img (6.5 MB)
recovery_signed.img (12 MB)
system.img (1,879 MB)
and other files.
but i can't seem to extract them.
any advise?

why not?
I do not understand what is the use of packing the opened in ext4_unpacker .img file into .ext4 file and extracting it with ext2explore afterwards!?!
It is just simple way to extract [Alt+E] all bunch right away from ext4_unpacker window:
My Question is:
if there is the same easy way for Windows OS to compile the extracted system folder back to .img file AND make the system.new.dat file for Lollipop ROM ?

Nar4 said:
I do not understand what is the use of packing the opened in ext4_unpacker .img file into .ext4 file and extracting it with ext2explore afterwards!?!
It is just simple way to extract [Alt+E] all bunch right away from ext4_unpacker window:
My Question is:
if there is the same easy way for Windows OS to compile the extracted system folder back to .img file AND make the system.new.dat file for Lollipop ROM ?
Click to expand...
Click to collapse
im sorry for asking, how is this related to the thread?

Same problem on my OnePlus ONe
@shariksharik, Do you get any resolution for the same?

I'm here for same problems, anyone solved it?