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

[SOLVED] Soft bricked my HTC One M7, ADB not working

Hi there,
So I was installing CM10.2 on my HTC One (GSM) m7ul this evening when suddenly everything went wrong.
- I copied the CM .zip and GAPPS .zip to the internal storage using windows (7) file explorer;
- I installed the CM boot.img via fastboot flash boot boot.img;
- I rebooted into recovery mode (twrp 2.6.3.0);
- wiped cache and dalvik cache;
- Tried to find the installation.zip;
No zip files found. Actually, twrp did not find any file and could not mount f.i. system, cache, sdcard, etc
I tried using another bootloader (clockwork touch 6.0.4.3), but has the same issues as twrp.
ADB is not working as my phone was not in developer mode when I started to install CM10.2. Rebooting my phone is not working also because I replaced the boot.img via fastboot. I cannot reach my backup via twrp (on phone and PC).
Do you have tips for me to get my phone to work properly again?

basv81 said:
So I was installing CM10.2 this evening when suddenly everything went wrong.
- I copied the CM .zip and GAPPS .zip to the internal storage using windows (7) file explorer;
- I installed the CM boot.img via fastboot flash boot boot.img;
- I rebooted into recovery mode (twrp 2.6.3.0);
- wiped cache and dalvik cache;
- Tried to find the installation.zip;
No zip files found. Actually, twrp did not find any file and could not mount f.i. system, cache, sdcard, etc
I tried using another bootloader (clockwork touch 6.0.4.3), but has the same issues as twrp.
ADB is not working as my phone was not in developer mode when I started to install CM10.2. Rebooting my phone is not working also because I replaced the boot.img via fastboot. I cannot reach my backup via twrp (on phone and PC).
Do you have tips for me to get my phone to work properly again?
Click to expand...
Click to collapse
Mate you made a bad move flashing the boot.img file before installing the .zip. Always install the zip first then flash the boot.img and after clear cache. And make sure the zip is at the root of your sdcard in twrp before proceeding to anything!
I tried using another bootloader (clockwork touch 6.0.4.3)
Click to expand...
Click to collapse
You mean ''I tried another RECOVERY''
Rebooting my phone is not working also because I replaced the boot.img via fastboot
Click to expand...
Click to collapse
try holding power + Vol down and reboot in bootloader
Nowt that you are in bootloader, select fastboot and connect usb cable, navigate to your adb/fastboot folder of your computer and start a cmd prompt from there.
you can flash twrp again as your recovery
Code:
fastboot flash recovery <name-of-recovery>.img
reboot into bootloader
Code:
fastboot reboot bootloader
then go in recovery (adb is supported inside twrp).
push your zip files to your phone
Code:
adb push <name_of_rom>.zip /sdcard/
adb push <name_of_gapps>.zip /sdcard/
- install the zip of your cm rom first via twrp ---> select ''install'' and then navigate to /sdcard/ and select your zip.
- reboot phone in bootloader ---> select reboot from twrp main menu, after select bootloader.
- when in bootloader select fastboot
flash your kernel:
Code:
fastboot flash boot boot.img
after go back in twrp recovery and install you gapps.zip and after clear cache and dalvik cache then reboot normally.

Thanks for your reply.
alray said:
Mate you made a bad move flashing the boot.img file before installing the .zip. Always install the zip first then flash the boot.img and after clear cache. And make sure the zip is at the root of your sdcard in twrp before proceeding to anything!
You mean ''I tried another RECOVERY''
Click to expand...
Click to collapse
:good:
try holding power + Vol down and reboot in bootloader
Nowt that you are in bootloader, select fastboot and connect usb cable, navigate to your adb/fastboot folder of your computer and start a cmd prompt from there.
you can flash twrp again as your recovery
Code:
fastboot flash recovery <name-of-recovery>.img
reboot into bootloader
Code:
fastboot reboot bootloader
then go in recovery (adb is supported inside twrp).
Click to expand...
Click to collapse
Done all that. ADB sideload option tells me it cannot mount /sdcard, /data, /system.
push your zip files to your phone
Code:
adb push <name_of_rom>.zip /sdcard/
adb push <name_of_gapps>.zip /sdcard/
Click to expand...
Click to collapse
ADB cannot find the device.
- install the zip of your cm rom first via twrp ---> select ''install'' and then navigate to /sdcard/ and select your zip.
Click to expand...
Click to collapse
twrp and cwmod can't see any files (although I allready put the zip files in the root directory of the device)
- reboot phone in bootloader ---> select reboot from twrp main menu, after select bootloader.
- when in bootloader select fastboot
flash your kernel:
Code:
fastboot flash boot boot.img
after go back in twrp recovery and install you gapps.zip and after clear cache and dalvik cache then reboot normally.
Click to expand...
Click to collapse
I think the data on my device somehow got corrupt.

./

Stolpert said:
I assume you've got the correct drivers installed, you should be able to use ADB in recovery, at least in cwm but I guess also in twrp. Try and install HTC Sync manager for all the drivers, go back in recovery and type:
Code:
adb devices
If it's there you can follow the guide above.
Click to expand...
Click to collapse
Most recent drivers installed. I only don't get any serial numbers on my screen (only "List of devices attached" and below is empty). Not sure whether I get te "error: device not found" message with that command.

basv81 said:
Thanks for your reply.
:good:
Done all that. ADB sideload option tells me it cannot mount /sdcard, /data, /system.
ADB cannot find the device.
twrp and cwmod can't see any files (although I allready put the zip files in the root directory of the device)
I think the data on my device somehow got corrupt.
Click to expand...
Click to collapse
to check you're /data partition, reboot to recovery then:
adb devices -> to make sure it's connected, if OK proceed with below:
adb shell
~ # umount /data
umount /data
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
and see if it reports errors or not. (copy/paste your command prompt)

nkk71 said:
to check you're /data partition, reboot to recovery then:
adb devices -> to make sure it's connected, if OK proceed with below:
adb shell
~ # umount /data
umount /data
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
and see if it reports errors or not. (copy/paste your command prompt)
Click to expand...
Click to collapse
I'll do that tonight (that's within 12 hrs).

alray said:
you can flash twrp again as your recovery
Code:
fastboot flash recovery <name-of-recovery>.img
reboot into bootloader
Code:
fastboot reboot bootloader
then go in recovery (adb is supported inside twrp).
Click to expand...
Click to collapse
basv81 said:
Thanks for your reply.
Done all that. ADB sideload option tells me it cannot mount /sdcard, /data, /system.
Click to expand...
Click to collapse
ADB tells you that? You are using the fastboot commands? ADB cannot communicate with fastboot and shouldn't tell you anything.

basv81 said:
I'll do that tonight (that's within 12 hrs).
Click to expand...
Click to collapse
We're one hour apart, so hopefully I'll check in on you tonight

Stolper said:
ADB tells you that? You are using the fastboot commands? ADB cannot communicate with fastboot and shouldn't tell you anything.
Click to expand...
Click to collapse
fastboot commands work perfectly within fastboot, but adb does not as the ADB sideload options in twrp and cw fail.

Are you using a Sprint Htc one? (M7WLS) If yes you need a different version of twrp. Go back in fastboot and type "fasboot getvat all" and copy paste info here (remove imei and s/n)
Sent from my HTC One using xda app-developers app

alray said:
Are you using a Sprint Htc one? (M7WLS) If yes you need a different version of twrp. Go back in fastboot and type "fasboot getvat all" and copy paste info here (remove imei and s/n)
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
No, I'm using a HTC One (GSM) m7ul
I'll post the info tonight.

I had the same crap happen on SPRINT HTC One. All I ended up doing in the end was booting to bootloader and derp- I mean, uh, running a stock RUU. Repartitioned all the partitions.
Sent from my HTC One using XDA Premium 4 mobile app

nkk71 said:
to check you're /data partition, reboot to recovery then:
adb devices -> to make sure it's connected, if OK proceed with below:
adb shell
~ # umount /data
umount /data
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
and see if it reports errors or not. (copy/paste your command prompt)
Click to expand...
Click to collapse
Code:
C:\Users\Bas\Desktop\HTC_One_files\HTCOneRoot\HTCOneRoot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT35CW***** recovery
Code:
C:\Users\Bas\Desktop\HTC_One_files\HTCOneRoot\HTCOneRoot>adb shell
~ # ←[6numount /data
umount /data
umount: can't umount /data: Invalid argument
~ # ←[6ne2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p37
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>
~ # ←[6n

alray said:
Are you using a Sprint Htc one? (M7WLS) If yes you need a different version of twrp. Go back in fastboot and type "fasboot getvat all" and copy paste info here (remove imei and s/n)
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Code:
C:\Users\Bas\Desktop\HTC_One_files\HTCOneRoot\HTCOneRoot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: **********
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s

basv81 said:
nkk71 said:
Hi basv81,
If "e2fsck -n -v -f /dev/block/mmcblk0p37" returns an error, send me a PM so it get's my attention to check your thread, before proceeding. Another guy turned out to have this and we were able to fix it, coincidentally he was from the Netherlands too.
I'll probably be here till 10~11pm your time.
Click to expand...
Click to collapse
Hi nkk71,
I get the following results:
Code:
C:\Users\Bas\Desktop\HTC_One_files\HTCOneRoot\HTCOneRoot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT35xxxxxxxxxxxxx recovery
Code:
C:\Users\Bas\Desktop\HTC_One_files\HTCOneRoot\HTCOneRoot>adb shell
~ # ←[6numount /data
umount /data
umount: can't umount /data: Invalid argument
~ # ←[6ne2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p37
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>
~ # ←[6n
I think I can be pretty sure the file system is corrupt :crying:
Click to expand...
Click to collapse
oh man, it's pretty late. can we pick this up anytime tomorrow or over the weekend? i need to get some sleep, and yeah looks like a corrupt partition. sorry man, i hate to be the bad guy
check into this: http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html
first thing you need to make sure of, is "cat /proc/emmc" to make sure we're looking at the right partition.
I can't do this tonight, but you might wanna check: http://forum.xda-developers.com/showthread.php?t=2504542
page 8 or 9 and onwards.
sorry man, but too late for me, i need to get some sleep before work tomorrow

nkk71 said:
oh man, it's pretty late. can we pick this up anytime tomorrow or over the weekend? i need to get some sleep, and yeah looks like a corrupt partition. sorry man, i hate to be the bad guy
check into this: http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html
first thing you need to make sure of, is "cat /proc/emmc" to make sure we're looking at the right partition.
I can't do this tonight, but you might wanna check: http://forum.xda-developers.com/showthread.php?t=2504542
page 8 or 9 and onwards.
sorry man, but too late for me, i need to get some sleep before work tomorrow
Click to expand...
Click to collapse
No problem I have to go to sleep too because of the same.
cat /proc/emmc responds as follows:
Code:
C:\Users\Bas\Desktop\HTC_One_files\HTCOneRoot\HTCOneRoot>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # ←[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)
I don't dare to format the partition yet (http://forum.xda-developers.com/showthread.php?t=2504542&page=9&p=47046727 and onwards). I'm online in the vicinity of my phone again tomorrow night after 8/9PM CET and Thursday night. After that it will be after the weekend.

basv81 said:
No problem I have to go to sleep too because of the same.
cat /proc/emmc responds as follows:
Code:
C:\Users\Bas\Desktop\HTC_One_files\HTCOneRoot\HTCOneRoot>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # ←[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)
I don't dare to format the partition yet (http://forum.xda-developers.com/showthread.php?t=2504542&page=9&p=47046727 and onwards). I'm online in the vicinity of my phone again tomorrow night after 8/9PM CET and Thursday night. After that it will be after the weekend.
Click to expand...
Click to collapse
Anyway back to your thread, so /data isn't mounting, even if encrypted it should mount, but not be readable.
Here's what I'd like you to do, reboot to recovery, then:
adb shell
# e2fsck -v -f /dev/block/mmcblk0p37
and let's see if it ask for repair of any kind

alray said:
push your zip files to your phone
Code:
adb push <name_of_rom>.zip /sdcard/
adb push <name_of_gapps>.zip /sdcard/
- install the zip of your cm rom first via twrp ---> select ''install'' and then navigate to /sdcard/ and select your zip.
- reboot phone in bootloader ---> select reboot from twrp main menu, after select bootloader.
- when in bootloader select fastboot
flash your kernel:
Click to expand...
Click to collapse
This first part is working by the way: adb push worked when I used another USB port on my PC. I can see the two zip files I pushed, but cannot install them.

nkk71 said:
Anyway back to your thread, so /data isn't mounting, even if encrypted it should mount, but not be readable.
Here's what I'd like you to do, reboot to recovery, then:
adb shell
# e2fsck -v -f /dev/block/mmcblk0p37
and let's see if it ask for repair of any kind
Click to expand...
Click to collapse
Code:
~ # ←[6ne2fsck -v -f /dev/block/mmcblk0p37
e2fsck -v -f /dev/block/mmcblk0p37
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p37
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>
I think I know what happened: I got my work e-mail on the phone, so the storage is encrypted. That's probably the reason that I don't see any files in there. Only problem is that I can't boot the phone to undo the encryption.

[Q]M7_u wont boot

Hello,
I have a m7_u that wont boot up, I tried few custom roms by sideload, and aroma backups but nothing helped. every thing goes fine but after few min on the first lockscreen it reboots.
any thing I can try?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: **************
(bootloader) imei: **************
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__K18
(bootloader) battery-status: good
(bootloader) battery-voltage: 3648mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

deadwolf666 said:
Hello,
I have a m7_u that wont boot up, I tried few custom roms by sideload, and aroma backups but nothing helped. every thing goes fine but after few min on the first lockscreen it reboots.
any thing I can try?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__K18
(bootloader) battery-status: good
(bootloader) battery-voltage: 3648mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Remove the s/n and imei please!!!
What Rom are you running at the minute? When installing the Rom did it say it was complete and did you do a full wipe?
---------- Post added at 12:57 PM ---------- Previous post was at 12:56 PM ----------
stovie_steve said:
Remove the s/n and imei please!!!
What Rom are you running at the minute? When installing the Rom did it say it was complete and did you do a full wipe?
Click to expand...
Click to collapse
Also what is the status of your bootloader - locked or unlocked? And have you installed any custom firmware?

stovie_steve said:
Remove the s/n and imei please!!!
What Rom are you running at the minute? When installing the Rom did it say it was complete and did you do a full wipe?
---------- Post added at 12:57 PM ---------- Previous post was at 12:56 PM ----------
Also what is the status of your bootloader - locked or unlocked? And have you installed any custom firmware?
Click to expand...
Click to collapse
At the moment I flashed Guru_Reset_M7_3.62.401.1.zip with no root, It was complete successfully and I fully wiped. tried to boot directly after flash also after installing stock recovery )from the zip file) and locking the bootloader.

deadwolf666 said:
At the moment I flashed Guru_Reset_M7_3.62.401.1.zip with no root, It was complete successfully and I fully wiped. tried to boot directly after flash also after installing stock recovery )from the zip file) and locking the bootloader.
Click to expand...
Click to collapse
Try the 2.24.401.8 guru reset - I'm wondering if that one you flashed is for the latest firmware and latest hboot
Try that and see how it goes
After that I would run rumrunner for 2.24.401.8 to get s-off, remove tampered and lock the bootloader using the adb shell command then update via OTA

stovie_steve said:
Try the 2.24.401.8 guru reset - I'm wondering if that one you flashed is for the latest firmware and latest hboot
Try that and see how it goes
After that I would run rumrunner for 2.24.401.8 to get s-off, remove tampered and lock the bootloader using the adb shell command then update via OTA
Click to expand...
Click to collapse
Same after 2.24.401.8 stuck on the first lockscreen, I changed the cid to 11111111 with riff box but same result.

deadwolf666 said:
Same after 2.24.401.8 stuck on the first lockscreen, I changed the cid to 11111111 with riff box but same result.
Click to expand...
Click to collapse
Try this guide I wrote. Use the appropriate firmware. I know you are not S-OFF but try and wipe as much as possible before reinstalling everything.
Which firmware are you using ? And what ROM are you installing ?

attanasi0 said:
Try this guide I wrote. Use the appropriate firmware. I know you are not S-OFF but try and wipe as much as possible before reinstalling everything.
Which firmware are you using ? And what ROM are you installing ?
Click to expand...
Click to collapse
Cant find any firmware\RUU\Nand (Stock ot not) to match and cant get s-off. 2.24.401.8 wont work and net next one is 3.XX...\
Also I can erase only the cache partition.

deadwolf666 said:
Cant find any firmware\RUU\Nand (Stock ot not) to match and cant get s-off. 2.24.401.8 wont work and net next one is 3.XX...\
Also I can erase only the cache partition.
Click to expand...
Click to collapse
We'll just try it without updating the firmware, then once you have S-OFF you'll be able to make everything work.
Just do the Reinstalling Recovery and Installing Custom ROM portion of the guide.

attanasi0 said:
We'll just try it without updating the firmware, then once you have S-OFF you'll be able to make everything work.
Just do the Reinstalling Recovery and Installing Custom ROM portion of the guide.
Click to expand...
Click to collapse
No matter what I try to install I cant get pass the lock screen, the phone just reboots (also after minute)

deadwolf666 said:
Same after 2.24.401.8 stuck on the first lockscreen, I changed the cid to 11111111 with riff box but same result.
Click to expand...
Click to collapse
deadwolf666 said:
Cant find any firmware\RUU\Nand (Stock ot not) to match and cant get s-off. 2.24.401.8 wont work and net next one is 3.XX...\
Also I can erase only the cache partition.
Click to expand...
Click to collapse
1- How did you chance CID if you're not S-Off
2- rumrunner should work to get s-off for you (provided u are on a 2.24.401.x rom and rooted), it did for two others with HTC__K18 and 2.24 ROM/firmware

nkk71 said:
1- How did you chance CID if you're not S-Off
2- rumrunner should work to get s-off for you (provided u are on a 2.24.401.x rom and rooted), it did for two others with HTC__K18 and 2.24 ROM/firmware
Click to expand...
Click to collapse
1- Jtag with riff box..
2- Cant run any Soff method if the wont boot normally, It wont get to the main screen so I cant debug also it wont stay on for more then 1 min or so

deadwolf666 said:
No matter what I try to install I cant get pass the lock screen, the phone just reboots (also after minute)
Click to expand...
Click to collapse
You have to be on the white Fastboot screen. If that doesn't load it doesn't look good but it did since you said you were able to erase cache.
So go into Fastboot and do this :
Download this
Hold the Volume-Down button
Hold the Power button for around 10 seconds
Release the Power button (but keep Volume-Down pressed)
You should see something similar to this :
{
"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"
}
Using the Volume buttons and the Power button, select Fastboot and make sur FASTBOOT USB shows up (like on the picture)
To make sure fastboot is properly connected, use
Code:
fastboot devices
If the results show up as positive, then use
Code:
fastboot flash recovery [pathonyourcomputer/recovery.img]
Using the Volume buttons, select Bootloader and then select Recovery.
Select the option "Wipe data/factory reset" (You will loose everything not previously backed up outside the phone.)
Select "Wipe Cache partition"
Select "Advanced -> Wipe Dalvik Cache"
While in recovery, type
Code:
adb push [path/rom.zip] /sdcard/rom.zip
Select "Install zip"
Select "Choose zip from sdcard"
Voila ! You should be good to go !

deadwolf666 said:
1- Jtag with riff box..
2- Cant run any Soff method if the wont boot normally, It wont get to the main screen so I cant debug also it wont stay on for more then 1 min or so
Click to expand...
Click to collapse
but flashing is going normal? have you tried factory reset and format/wipe /data and /data/media (/sdcard) then install? also try changing recovery, which one and version are you on?

attanasi0 said:
You have to be on the white Fastboot screen. If that doesn't load it doesn't look good but it did since you said you were able to erase cache.
So go into Fastboot and do this :
Download this
Hold the Volume-Down button
Hold the Power button for around 10 seconds
Release the Power button (but keep Volume-Down pressed)
You should see something similar to this :
Using the Volume buttons and the Power button, select Fastboot and make sur FASTBOOT USB shows up (like on the picture)
To make sure fastboot is properly connected, use
Code:
fastboot devices
If the results show up as positive, then use
Code:
fastboot flash recovery [pathonyourcomputer/recovery.img]
Using the Volume buttons, select Bootloader and then select Recovery.
Select the option "Wipe data/factory reset" (You will loose everything not previously backed up outside the phone.)
Select "Wipe Cache partition"
Select "Advanced -> Wipe Dalvik Cache"
While in recovery, type
Code:
adb push [path/rom.zip] /sdcard/rom.zip
Select "Install zip"
Select "Choose zip from sdcard"
Voila ! You should be good to go !
Click to expand...
Click to collapse
nkk71 said:
but flashing is going normal? have you tried factory reset and format/wipe /data and /data/media (/sdcard) then install? also try changing recovery, which one and version are you on?
Click to expand...
Click to collapse
All is good I did flashed custom roms and guru nands (with every recovery I found - various versions of CWM and TWRP) but after I finish the phone gets to the first lock screen before the first wizard and then it reboots

deadwolf666 said:
All is good I did flashed custom roms and guru nands (with every recovery I found - various versions of CWM and TWRP) but after I finish the phone gets to the first lock screen before the first wizard and then it reboots
Click to expand...
Click to collapse
can you check you're /data partition please:
1- reboot into recovery, and connect to PC
2- confirm it's recognized "adb devices" -> should show your serial number
3- now do the following on your pc:
adb shell
~ # mount
~ # umount /data
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
copy/paste the command prompt output (not screenshot, just copy/paste the text)

nkk71 said:
can you check you're /data partition please:
1- reboot into recovery, and connect to PC
2- confirm it's recognized "adb devices" -> should show your serial number
3- now do the following on your pc:
adb shell
~ # mount
~ # umount /data
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
copy/paste the command prompt output (not screenshot, just copy/paste the text)
Click to expand...
Click to collapse
~ # mount
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/mmcblk0p36 on /cache type ext4 (rw,nodev,noatime,nodiratime,data=orde
red)
/dev/block/mmcblk0p37 on /data type ext4 (rw,nodev,noatime,nodiratime,data=order
ed)
~ # umount /data
umount /data
~ # 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
Directory inode 2, block #0, offset 0: directory corrupted
Salvage? no
e2fsck: aborted
Edit: after running # e2fsck -v -f /dev/block/mmcblk0p37 and pressing Yes for some fixes
~ # 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
12 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: 3
150981 blocks used (2.22%)
0 bad blocks
1 large file
0 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
--------
3 files

deadwolf666 said:
~ # mount
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/mmcblk0p36 on /cache type ext4 (rw,nodev,noatime,nodiratime,data=orde
red)
/dev/block/mmcblk0p37 on /data type ext4 (rw,nodev,noatime,nodiratime,data=order
ed)
~ # umount /data
umount /data
~ # 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
Directory inode 2, block #0, offset 0: directory corrupted
Salvage? no
e2fsck: aborted
Edit: after running # e2fsck -v -f /dev/block/mmcblk0p37 and pressing Yes for some fixes
~ # 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
12 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: 3
150981 blocks used (2.22%)
0 bad blocks
1 large file
0 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
--------
3 files
Click to expand...
Click to collapse
CRAP, corrupt data partition, let's hope it's not a hardware fault, repairing is OK, and should get you going, but I would recommend a full "real" format, gimme a few minutes and I'll post back with details.....
Hit the thanks button if I've helped
---------- Post added at 07:49 PM ---------- Previous post was at 07:16 PM ----------
deadwolf666 said:
~ # 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
Directory inode 2, block #0, offset 0: directory corrupted
Salvage? no
Click to expand...
Click to collapse
Ok, so here's how to "real" format the data partition: (thanks to @mike1986. for his article http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html)
1- download this: http://goo.gl/pmZ9Mt
2- then push it to your phone: adb push mkfs.ext4 /tmp
3- open a shell:
adb shell
~# chmod 777 /tmp/mkfs.ext4
~# umount /data
Code:
~# [B]/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37[/B]
(I have to enclose that in a code section, otherwise there's an extra space which should NOT be there)
the output should be similar to:
Code:
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
1703936 inodes, 6815744 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
208 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 24 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
if all OK, you need to recreate media, so within the shell
~# mount /data
~# mkdir -p /data/media/0
exit the shell using ~# exit
finally push or sideload your rom, and flash it. if everything goes well, it will no longer reboot, if it does then it could be a hardware fault.
So far I've helped 3 people with this, two out of the three worked fine, the last one was a hardware fault.

nkk71 said:
CRAP, corrupt data partition, let's hope it's not a hardware fault, repairing is OK, and should get you going, but I would recommend a full "real" format, gimme a few minutes and I'll post back with details.....
Hit the thanks button if I've helped
---------- Post added at 07:49 PM ---------- Previous post was at 07:16 PM ----------
Ok, so here's how to "real" format the data partition: (thanks to @mike1986. for his article http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html)
1- download this: http://goo.gl/pmZ9Mt
2- then push it to your phone: adb push mkfs.ext4 /tmp
3- open a shell:
adb shell
~# chmod 777 /tmp/mkfs.ext4
~# umount /data
Code:
~# [B]/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37[/B]
(I have to enclose that in a code section, otherwise there's an extra space which should NOT be there)
the output should be similar to:
Code:
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
1703936 inodes, 6815744 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
208 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 24 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
if all OK, you need to recreate media, so within the shell
~# mount /data
~# mkdir -p /data/media/0
exit the shell using ~# exit
finally push or sideload your rom, and flash it. if everything goes well, it will no longer reboot, if it does then it could be a hardware fault.
So far I've helped 3 people with this, two out of the three worked fine, the last one was a hardware fault.
Click to expand...
Click to collapse
Thanks for your help, I tried your guide but same result(restart after first screenlock) then I installed CM and I got pass the screenlock but it reboots after 2-5 minutes :\

deadwolf666 said:
Thanks for your help, I tried your guide but same result(restart after first screenlock) then I installed CM and I got pass the screenlock but it reboots after 2-5 minutes :\
Click to expand...
Click to collapse
did you format the partition as suggested? if so go back to post #16 and run e2fsck again, if it gives error again, then it's faulty hardware
The reason CM installs is because it doesnt use the /data partition, however after booting up, at some point it needs to use /data and if it's corrupt, it will reboot without any error message.
So if you did successfully format it, and e2fsck reports errors again after one or two reboots, then it's unfortunately a hardware issue.

nkk71 said:
did you format the partition as suggested? if so go back to post #16 and run e2fsck again, if it gives error again, then it's faulty hardware
The reason CM installs is because it doesnt use the /data partition, however after booting up, at some point it needs to use /data and if it's corrupt, it will reboot without any error message.
So if you did successfully format it, and e2fsck reports errors again after one or two reboots, then it's unfortunately a hardware issue.
Click to expand...
Click to collapse
Code:
~ # e2fsck -v -f /dev/block/mmcblk0p37
e2fsck -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
2147 inodes used (0.13%)
207 non-contiguous files (9.6%)
2 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 2031/8
193238 blocks used (2.84%)
0 bad blocks
0 large files
1602 regular files
437 directories
0 character device files
0 block device files
0 fifos
0 links
93 symbolic links (92 fast symbolic links)
6 sockets
--------
2138 files
No errors this time, Any suggestion for a ROM that works OK on the M7_U ?
EDIT:
I Soff ed with revone and now trying this guide :
http://forum.xda-developers.com/showthread.php?t=2489914
will post soon

[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