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

dr.zikzak · Apr 9, 2014

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

aooga · Apr 10, 2014

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.

dr.zikzak · Apr 10, 2014

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.

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://xdaforums.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...

aooga · Apr 10, 2014

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]

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.

dr.zikzak · Apr 10, 2014

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

dr.zikzak · Apr 10, 2014

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

dr.zikzak · Apr 10, 2014

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)
~ #

Greetings Alex

nkk71 · Apr 10, 2014

dr.zikzak said:
Is there a way to get SuperCID from my point?
Greetings Alex

take a look at http://xdaforums.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

dr.zikzak · Apr 10, 2014

nkk71 said:
take a look at http://xdaforums.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

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

dr.zikzak · Apr 10, 2014

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!

dr.zikzak · Apr 10, 2014

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

xxerkxx · Apr 11, 2014

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.

nkk71 · Apr 11, 2014

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.

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

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

.

willumpie82 · Apr 11, 2014

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

dr.zikzak · Apr 11, 2014

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

.

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

xxerkxx · Apr 11, 2014

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
.

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?

nkk71 · Apr 11, 2014

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

yeah, sorry, i should have mentioned that, i should have actually linked this:

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

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

dr.zikzak · Apr 11, 2014

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

nkk71 · Apr 12, 2014

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

yeah mostly the forum and also @mike1986. blog has very good info: http://android-revolution-hd.blogspot.com/p/android-guides.html

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

Member

Senior Member

Member

Senior Member

Member

Member

Member

Inactive Recognized Developer / Contributor

Member

Member

Member

Member

Inactive Recognized Developer / Contributor

Senior Member

Member

Member

Inactive Recognized Developer / Contributor

Member

Inactive Recognized Developer / Contributor

Similar threads

Top Liked Posts