Post Reply

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

10th April 2014, 08:23 PM   |  #11  
OP Junior Member
Thanks Meter: 0
 
12 posts
Join Date:Joined: Jan 2011
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
Last edited by dr.zikzak; 10th April 2014 at 08:40 PM. Reason: added sth
11th April 2014, 12:00 AM   |  #12  
Junior Member
Thanks Meter: 1
 
12 posts
Join Date:Joined: Oct 2010
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.
Last edited by xxerkxx; 11th April 2014 at 12:08 AM. Reason: spellcheck!
11th April 2014, 12:09 PM   |  #13  
nkk71's Avatar
Recognized Contributor
Flag Beirut
Thanks Meter: 2,969
 
5,986 posts
Join Date:Joined: May 2010
More
Quote:
Originally Posted by xxerkxx

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



Quote:
Originally Posted by dr.zikzak

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

.
The Following User Says Thank You to nkk71 For This Useful Post: [ View ]
11th April 2014, 01:49 PM   |  #14  
Senior Member
Thanks Meter: 6
 
163 posts
Join Date:Joined: Apr 2005
More
Thumbs up
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
11th April 2014, 02:20 PM   |  #15  
OP Junior Member
Thanks Meter: 0
 
12 posts
Join Date:Joined: Jan 2011
Quote:
Originally Posted by nkk71

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
11th April 2014, 02:22 PM   |  #16  
Junior Member
Thanks Meter: 1
 
12 posts
Join Date:Joined: Oct 2010
Thanks for the info about sideload, didnīt know that it could replace the entire rom!

Quote:
Originally Posted by nkk71

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:

Quote:

e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p37
Filesystem mounted or opened exclusively by another program?

Last edited by xxerkxx; 11th April 2014 at 02:28 PM. Reason: messed up quote!
11th April 2014, 02:58 PM   |  #17  
nkk71's Avatar
Recognized Contributor
Flag Beirut
Thanks Meter: 2,969
 
5,986 posts
Join Date:Joined: May 2010
More
Quote:
Originally Posted by dr.zikzak

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:

 
Code:
C:\ADB3>adb devices
List of devices attached
HT34xxxxxxxx    recovery <- you are now in recovery


C:\ADB3>adb push Android_Revolution_HD-One_52.0.zip /sdcard/
2990 KB/s (1172224138 bytes in 382.835s) <- yes, it took over 5 mins,
                                            without showing any progress

Just to double-check the file is not corrupt
C:\ADB3>adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip
2eff0d37fec5789b946c43f7da2c13bf  /sdcard/Android_Revolution_HD-One_52.0.zip
from the OP: Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF -- ==> so all is good :)
C:\ADB3>
-> in recovery, select "install" and install the ROM



---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------

Quote:
Originally Posted by xxerkxx

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
The Following User Says Thank You to nkk71 For This Useful Post: [ View ]
11th April 2014, 05:45 PM   |  #18  
OP Junior Member
Thanks Meter: 0
 
12 posts
Join Date:Joined: Jan 2011
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
12th April 2014, 11:04 AM   |  #19  
nkk71's Avatar
Recognized Contributor
Flag Beirut
Thanks Meter: 2,969
 
5,986 posts
Join Date:Joined: May 2010
More
Quote:
Originally Posted by dr.zikzak

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.blogspo...id-guides.html

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes