Database Info

[HOW-TO] Fix soft brick & error mounting sdcard

EDIT: I solved my own problem. Scroll down to post #8 for the solution.
My problem was that my phone (T-Mobile USA HTC One S) would not boot into ICS anymore, but I was still able to get into recovery (CWM), yet I had no access to the sdcard ("unable to mount /sdcard").
Post #8 below tells you how you can restore access to the sdcard in CWM so that you can push a ROM zip file to the sdcard via adb.
-J

Have you made any nandroids? If you have maybe you can restore. Also check in the download file in cwm that is possible place where that file may be.
Sent from my myTouch 4G Slide using xda premium

archie53 said:
Have you made any nandroids? If you have maybe you can restore. Also check in the download file in cwm that is possible place where that file may be.
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
Unfortunately I didn't have the foresight to make a nandroid backup. My previous phone was a Samsung Galaxy S 4G, which, like most Android phones, has a removable SD-Card that stuff can be copied onto (and then flashed). Not so here obviously.
Is it even possible to push files to the sdcard using the method I tried when in CWM?

When you push the file via ADB, have you tried placing it into a folder that you know is on the /sdcard?

joshnichols189 said:
When you push the file via ADB, have you tried placing it into a folder that you know is on the /sdcard?
Click to expand...
Click to collapse
It just got worse. I got the idea to format all partitions (data, system, cache, sdcard) through CWM, and now CWM can't even mount /sdcard/ anymore...

I had to do the same thing:
adb push "NameOfFile.zip /sdcard
then go to install from zip.
Look on sd card and it will be there.
I always rename the zip files to there can be less errors.
you can also do
adb shell pull "nameOfFile.zip /sdcard
make sure the zip file is where your adb and fastboot is

My problem is CWM can't mount the /sdcard directory, so I can't flash the new OS. Is there anybody that knows how to recover from that problem?

LuckyMethod said:
My problem is CWM can't mount the /sdcard directory, so I can't flash the new OS. Is there anybody that knows how to recover from that problem?
Click to expand...
Click to collapse
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Code:
adb push utb.zip /sdcard
6) While still in CWM, flash the zip.
The trick here is that only the stock recovery is capable of restoring access to the sdcard by it's proprietary "clear storage" option.
Good luck!
-J

If that doesn't work an easy fix is boot into bootloader, goto fastboot and use "fastboot flash boot boot.img" and so fouth. In the dev section I seen a stock tmobile naindroid. Download it and you'll have your data.img and boot.img. You should be able to flash them without needing to push to /sdcard. letme know how it works
I know you fixed this already just thought this still might help

cannondale0815 said:
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
...cut...
-J
Click to expand...
Click to collapse
It worked like a charm, thank you very much. You saved my life, I was in a time crunch.

LuckyMethod said:
It worked like a charm, thank you very much. You saved my life, I was in a time crunch.
Click to expand...
Click to collapse
Happy it worked for you. Took me several days to figure this out
Sent from my HTC One S using xda premium

I too formatted my sd card but a little trial and error and using your direction, I am back in business ! Thank you , this should really be a sticky
Sent from my HTC VLE_U using xda premium

j3.cole said:
I too formatted my sd card but a little trial and error and using your direction, I am back in business ! Thank you , this should really be a sticky
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Thank you. I changed the title and original post to make it easier for people to find this thread.

I am going to try this trick tomorrow after having spent endless hours trying to fdisk/parted via adb, and flashing endless roms and updates to no avail. I will post the outcome here. I really hope this works for me like it has for you guys...

mrmoretti said:
I am going to try this trick tomorrow after having spent endless hours trying to fdisk/parted via adb, and flashing endless roms and updates to no avail. I will post the outcome here. I really hope this works for me like it has for you guys...
Click to expand...
Click to collapse
IT WORKED! This thread should be made sticky! I'm sure a lot of users who have HTC One S with built-in SD will have the same issue when mucking about with their phone. Thank you!

Bump, as too many people are having this problem.
Sent from my HTC One S using Tapatalk 2

cannondale0815 said:
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Code:
adb push utb.zip /sdcard
6) While still in CWM, flash the zip.
The trick here is that only the stock recovery is capable of restoring access to the sdcard by it's proprietary "clear storage" option.
Good luck!
-J
Click to expand...
Click to collapse
THANK YOU SO MUCH! THIS WORKED PERFECTLY!
This should definitely be included in a stickied guide for people like me who have managed to corrupt their recoveries.

Got it after several tries

hey guys i have the same problem, the solution sort of work, but when i try to do a adb push its show it was sucessful but when i do to flash it i cant see it.

yasir_jan87 said:
hey guys i have the same problem, the solution sort of work, but when i try to do a adb push its show it was sucessful but when i do to flash it i cant see it.
Click to expand...
Click to collapse
Try to shorten the filename, i.e. "rom.zip".
And try this slightly modified command instead:
adb push rom.zip /sdcard/rom.zip
Sent from my aokp_tenderloin using Tapatalk 2

[Q] huge boot problem

hello everyone
here's my problem
i've managed to root and install revolution HD rom but i don't know how while trying to instal brobot's metro ui
the tab wont boot and now i can't even manage to access to the boot screen ( the tablet stay at the Eee pad logo + nvidia) and i can't do anything with CWM as it can't read external SD card, no backup (with another rom or the original ics rom) and can't access to the internal storage from my computer
somebody can help me to fix this bloody hell ?

NvFlash for Sbkv1/2
If you have a slider or tf101G You'll have to try to get adb working, try universal naked drivers.
Then you should update your recovery to something that reads ext and int, so this doesn't happen again

ok i'm going to try this solution thanks ^^
will it work under Win 7 x64 ?

What are the first 3 characters of your serial-number?
If they start with B70 (Or a higher number/letter) It's linux only for now (Sbkv2)
If they start with B60 (Or a lower number) It's windows too (Sbkv1)

Thing O Doom said:
What are the first 3 characters of your serial-number?
If they start with B70 (Or a higher number/letter) It's linux only for now (Sbkv2)
If they start with B60 (Or a lower number) It's windows too (Sbkv1)
Click to expand...
Click to collapse
how can i see that when my tab won't boot and i can only access the recovery menu ?

Its on the box you purchased it in or on a clear sticker that runs along the bottom of the back of it.
When did you buy it?

is there any way that i can access the internal storage of my TF101 while it is in CWM ?so i can throw a safe rom in there
with a win7 x64 computer

magingl said:
is there any way that i can access the internal storage of my TF101 while it is in CWM ?so i can throw a safe rom in there
with a win7 x64 computer
Click to expand...
Click to collapse
If your computer recognizes the tablet as ADB in recovery then you can do it that way. What version of ARHD are you using. i can create a proper version for you

mrevankyle said:
If your computer recognizes the tablet as ADB in recovery then you can do it that way. What version of ARHD are you using. i can create a proper version for you
Click to expand...
Click to collapse
the very last one

magingl said:
the very last one
Click to expand...
Click to collapse
OK the metroUI on brobot's site is for ARHD3.2 not ARHD3.4 and thats what caused our problems it will take me a while to download ARHD but once i have it the file should be up pretty quick

mrevankyle said:
OK the metroUI on brobot's site is for ARHD3.2 not ARHD3.4 and thats what caused our problems it will take me a while to download ARHD but once i have it the file should be up pretty quick
Click to expand...
Click to collapse
so with your software i will be able to access to inner storage of the TF101 and put a clean rom inside ?

magingl said:
so with your software i will be able to access to inner storage of the TF101 and put a clean rom inside ?
Click to expand...
Click to collapse
No. You need to install the android SDK. Then plug the device into the computer in recovery. You can try to mount usb there. Or run adb devices in command prompt then push the systemUI and framework-res through there.
this is the format
adb push <local> <remote>
code will be something like this
adb push systemUI.apk /system/app/systemUI.apk
and
adb push framework-res.apk /system/framework/framework-res.apk
all i was doing was fixing metro UI so that you can install it without bricking

mrevankyle said:
No. You need to install the android SDK. Then plug the device into the computer in recovery. You can try to mount usb there. Or run adb devices in command prompt then push the systemUI and framework-res through there.
this is the format
adb push <local> <remote>
code will be something like this
adb push systemUI.apk /system/app/systemUI.apk
and
adb push framework-res.apk /system/framework/framework-res.apk
all i was doing was fixing metro UI so that you can install it without bricking
Click to expand...
Click to collapse
I should use Eclipse then ?

magingl said:
I should use Eclipse then ?
Click to expand...
Click to collapse
um no just ADB you do not need to exit anything java. That code goes into command prompt

Allways worked for me
1) http://forum.xda-developers.com/showthread.php?t=1622628
2) http://www.transformerforums.com/fo...overy-bootloop-fix-tested-my-c10-windows.html
make both steps and root/ unroot/ unbrick your TF101 easily (worked 9.2.1.21/ 9.2.2.3)

Cascabreu said:
1) http://forum.xda-developers.com/showthread.php?t=1622628
2) http://www.transformerforums.com/fo...overy-bootloop-fix-tested-my-c10-windows.html
make both steps and root/ unroot/ unbrick your TF101 easily (worked 9.2.1.21/ 9.2.2.3)
Click to expand...
Click to collapse
The first would delete his data which he does not want and the second is not the cause of the problem
The issue is that by flashing a theme that pushes in an incompatible systemUI and framework-res causes the tablet not to boot. The problem is kind of like putting the wrong engine in a car so that it still looks fine and almost everything is in tact but it will not start

mrevankyle said:
The problem is kind of like putting the wrong engine in a car so that it still looks fine and almost everything is in tact but it will not start
Click to expand...
Click to collapse
LOL I love that Analogy, yeah if it was MetroUI that broke it then flashing right UI files will fix it. Unless he already wiped.

This should fix it.
View attachment 1097888
Thing O Doom does this update script look fine to you a haven't really done many
Code:
mount("ext4", "/dev/block/mmcblk0p1", "/system");
package_extract_dir("system", "/system");
unmount("/system");
and Magingl if you have a microSD try to put that into your computer via an adapter or phone and transfer the clean rom or my file then use that to flash via CWM otherwise push this file with ADB to /sdcard

Yeah that script is good.
run_program("/sbin/busybox", "mount", "/system");
also works. XD Yours is less lazy though.

I'm kinda noobish but i don't know how to access the adb console

[Q] How make the TF101 Stock and unroot?

Hi
I've been having heavy troubles with the "Android Revolution HD" ROM, my battery lasts forever while in use, but drowns easily and extremely fast when in sleep / shutdown mode.
So I give up, I am going to sell this tablet and I don't want this ROM any more, I don't want my devince Root. I want to get it back to the way it was when I opened the box.
The only think I'd like to get is the Eee Pad Transformer TF101 Firmware: V9.2.1.27 original from Asus to keep using the Android 4.0.X, nothing else.
Since all my attemps of install / reinstall / stock / root / unroot became a mass failure and later on I end coming here and QQ for help I am here to ask what need to be done before doing anything on the tablet.
So here is the summarized question:
How make the TF101 Stock and unroot?
Thank you
And sorry for my silliness

Here is a solution for you, "Instructions for unbricking/flashing ASUS stock firmware" part.
http://forum.xda-developers.com/showthread.php?t=1688012

pstryju said:
Here is a solution for you, "Instructions for unbricking/flashing ASUS stock firmware" part.
http://forum.xda-developers.com/showthread.php?t=1688012
Click to expand...
Click to collapse
It just doesn't work (as I was expecting) after doing exactly everything it says, it start installing something and then that is it, nothing happens on my tablet.

Filipebergami said:
Hi
I've been having heavy troubles with the "Android Revolution HD" ROM, my battery lasts forever while in use, but drowns easily and extremely fast when in sleep / shutdown mode.
So I give up, I am going to sell this tablet and I don't want this ROM any more, I don't want my devince Root. I want to get it back to the way it was when I opened the box.
The only think I'd like to get is the Eee Pad Transformer TF101 Firmware: V9.2.1.27 original from Asus to keep using the Android 4.0.X, nothing else.
Since all my attemps of install / reinstall / stock / root / unroot became a mass failure and later on I end coming here and QQ for help I am here to ask what need to be done before doing anything on the tablet.
So here is the summarized question:
How make the TF101 Stock and unroot?
Thank you
And sorry for my silliness
Click to expand...
Click to collapse
Download any firmware on the asus site. Extract the downloaded firmware (eg. WW_epaduser9_2_1_27UpdateLauncher.zip) take the file extracted (eg. WW_epad-user-9.2.1.27.zip) and place on sdcard. Follow the same procedure for installing a custom rom.

gilpederiva said:
Download any firmware on the asus site. Extract the downloaded firmware (eg. WW_epaduser9_2_1_27UpdateLauncher.zip) take the file extracted (eg. WW_epad-user-9.2.1.27.zip) and place on sdcard. Follow the same procedure for installing a custom rom.
Click to expand...
Click to collapse
How do I place things into the SD?
I can only place them into the internal storage, which "Full Wipe" will wipe it out?

Filipebergami said:
How do I place things into the SD?
I can only place them into the internal storage, which "Full Wipe" will wipe it out?
Click to expand...
Click to collapse
Sorry, put the file on the external sdcard. I also used a full wipe script. It takes a little more than installing a custom rom but it works.
I would like to take a question with you. I have already installed several custom ICS rom or JellyBean on my TF101, but the HD videos on youtube are with small crashes. But with Android 3.2.1 works well. This has happened to you?

gilpederiva said:
Sorry, put the file on the external sdcard. I also used a full wipe script. It takes a little more than installing a custom rom but it works.
I would like to take a question with you. I have already installed several custom ICS rom or JellyBean on my TF101, but the HD videos on youtube are with small crashes. But with Android 3.2.1 works well. This has happened to you?
Click to expand...
Click to collapse
I have no MicroSD card into my tablet, only internal storage

Filipebergami said:
It just doesn't work (as I was expecting) after doing exactly everything it says, it start installing something and then that is it, nothing happens on my tablet.
Click to expand...
Click to collapse
Please provide further details. What does easyflasher's window/log say? I've used this hundreds of times of not more to go back to stock or fix issues. Did you install the proper APX drivers?

Lethe6 said:
Please provide further details. What does easyflasher's window/log say? I've used this hundreds of times of not more to go back to stock or fix issues. Did you install the proper APX drivers?
Click to expand...
Click to collapse
It says everything was installed successfully and yes APX drivers are fine I've had others troubles with ROMs so I have it installed properly.
http://img10.imageshack.us/img10/9625/es5b.jpg

Filipebergami said:
It says everything was installed successfully and yes APX drivers are fine I've had others troubles with ROMs so I have it installed properly.
http://img10.imageshack.us/img10/9625/es5b.jpg
Click to expand...
Click to collapse
Did you see any text on the TF display? It should show some text when it is flashing.
Also, when in recovery you can use ADB to push the ww-epad firmware to your tablet's sdcard. Update the driver for the naked driver ADB and then:
adb push ROM.zip /sdcard/
If you need ADB, you can get the adb and dll files required to run here: https://dl.dropboxusercontent.com/u/34321735/adb.zip

frederuco said:
Did you see any text on the TF display? It should show some text when it is flashing.
Also, when in recovery you can use ADB to push the ww-epad firmware to your tablet's sdcard. Update the driver for the naked driver ADB and then:
adb push ROM.zip /sdcard/
If you need ADB, you can get the adb and dll files required to run here: https://dl.dropboxusercontent.com/u/34321735/adb.zip
Click to expand...
Click to collapse
Hi frederuco, you saved me once.
http://forum.xda-developers.com/showthread.php?t=2144143
Do I need to do this all over again?

Filipebergami said:
Hi frederuco, you saved me once.
http://forum.xda-developers.com/showthread.php?t=2144143
Do I need to do this all over again?
Click to expand...
Click to collapse
Yup!
Push the rom to flash to the /sdcard/ and you should be good to flash. Obviously dontjisnafter the full wipe.

frederuco said:
Yup!
Push the rom to flash to the /sdcard/ and you should be good to flash. Obviously dontjisnafter the full wipe.
Click to expand...
Click to collapse
Am I doing this right?
http://img24.imageshack.us/img24/6711/rlof.jpg
http://imageshack.us/f/545/wxne.jpg/

Almost....
You need a space between the .zip and the /sdcard/

frederuco said:
Almost....
You need a space between the .zip and the /sdcard/
Click to expand...
Click to collapse
I am getting error like last time,
http://img850.imageshack.us/img850/2954/lemh.jpg

Try using this version of adb: https://dl.dropboxusercontent.com/u/34321735/adb.zip
It is just the adb.exe and the two dll files required to run it.
I use those in a folder called c:\adb and then put the asus.zip in there and try it.
Also, try executing adb devices to make sure it can connect to your tablet. It should find 1 device.

frederuco said:
Try using this version of adb: https://dl.dropboxusercontent.com/u/34321735/adb.zip
It is just the adb.exe and the two dll files required to run it.
I use those in a folder called c:\adb and then put the asus.zip in there and try it.
Also, try executing adb devices to make sure it can connect to your tablet. It should find 1 device.
Click to expand...
Click to collapse
I still getting error, here is my screen if this helps:
http://imageshack.us/f/534/4vsd.jpg/
and the error log:
http://imageshack.us/f/32/ogc1.jpg/

on your PC try running these, then try to push the file again:
adb kill-server
adb start-server

frederuco said:
on your PC try running these, then try to push the file again:
adb kill-server
adb start-server
Click to expand...
Click to collapse
Here:
http://img850.imageshack.us/img850/2543/h9vj.jpg

Hmm, not sure what to say....
Do you have another PC you can try it on? At least try a PC reboot if nothing else.
Or perhaps a Linux live cd. ADB is native to Linux, just run from a terminal window.

Full Screen?

Hi,
I have root,is there anyway we can make use of this great screen easily by getting rid of the navigation on the bottom and the google search bar then use a pie app for navigation?
Cheers.
PS I did search the forum but did not see this question come up.
MJ-12

FYI this has been covered in at least a few threads here.
But this is what I did-
Install this app (it's what I use) or a similar one of your choosing- https://play.google.com/store/apps/details?id=tk.eatheat.pie&hl=en
And add this line to your build.pro to get rid of your navbar- qemu.hw.mainkeys=1
Reboot after editing your build.prop.
That's all you gotta do.

_MetalHead_ said:
FYI this has been covered in at least a few threads here.
But this is what I did-
Install this app (it's what I use) or a similar one of your choosing- https://play.google.com/store/apps/details?id=tk.eatheat.pie&hl=en
And add this line to your build.pro to get rid of your navbar- qemu.hw.mainkeys=1
Reboot after editing your build.prop.
That's all you gotta do.
Click to expand...
Click to collapse
did this and now my phone won't boot, just black screen after google logo

special.k said:
did this and now my phone won't boot, just black screen after google logo
Click to expand...
Click to collapse
Did you edit anything else in your build.prop? All that does is trick the phone into thinking you've got hardware keys, thus eliminating the need for a navbar. There's no reason why that mod alone would cause your phone to not boot. Can you get into fastboot or recovery?

_MetalHead_ said:
Did you edit anything else in your build.prop? All that does is trick the phone into thinking you've got hardware keys, thus eliminating the need for a navbar. There's no reason why that mod alone would cause your phone to not boot. Can you get into fastboot or recovery?
Click to expand...
Click to collapse
I just copy and pasted it in at the bottom, I think that was my problem. I can get into fastboot

special.k said:
I just copy and pasted it in at the bottom, I think that was my problem. I can get into fastboot
Click to expand...
Click to collapse
Well you can try using adb to push an unedited build.prop back to /system and that should get you running again.

_MetalHead_ said:
Well you can try using adb to push an unedited build.prop back to /system and that should get you running again.
Click to expand...
Click to collapse
Okay, where can I find that?

special.k said:
Okay, where can I find that?
Click to expand...
Click to collapse
Just download the stock ROM and pull it out of /system. There should be one over in the dev section.
If you're not familiar with adb, you should probably be able to copy the build.prop over with the file manager in TWRP. Just put it on your SD and use TWRP to move it to /system.
If you have trouble finding the build.prop just let me know and I'll pull mine and post it for you.

_MetalHead_ said:
Just download the stock ROM and pull it out of /system. There should be one over in the dev section.
If you're not familiar with adb, you should probably be able to copy the build.prop over with the file manager in TWRP. Just put it on your SD and use TWRP to move it to /system.
If you have trouble finding the build.prop just let me know and I'll pull mine and post it for you.
Click to expand...
Click to collapse
Okay thanks I will find it, I am on a ubuntu computer right now and am having trouble setting up adb on my old windows xp computer. ADB on ubuntu won't detect my device, I don't have TWRP installed or any recovery of that matter. Can only access fastboot

special.k said:
Okay thanks I will find it, I am on a ubuntu computer right now and am having trouble setting up adb on my old windows xp computer. ADB on ubuntu won't detect my device, I don't have TWRP installed or any recovery of that matter. Can only access fastboot
Click to expand...
Click to collapse
Well that's gotta be annoying. I'm not familiar with ubuntu but have you made sure your drivers are installed on your xp machine?

_MetalHead_ said:
Well that's gotta be annoying. I'm not familiar with ubuntu but have you made sure your drivers are installed on your xp machine?
Click to expand...
Click to collapse
I don't think so, it's not showing that any devices are connected

special.k said:
I don't think so, it's not showing that any devices are connected
Click to expand...
Click to collapse
Look around for the drivers and manually install them. If you can't find them, this toolkit will install them for you- http://forum.xda-developers.com/showthread.php?t=2508817

Help i've accidentally deleted my backup on my nexus 5

Help i've accidentally deleted my backup OS on my nexus 5. i am using CWM. i was trying to put android L on my nexus 5 and it couldnt install. so i went back to the recovery mode in attempt to restore my device to the backup i made. i couldnt find the backup on my sd card...weird. so i am stuck. trying to find a way to get my device back.

AHMEDNATOR said:
Help i've accidentally deleted my backup OS on my nexus 5. i am using CWM. i was trying to put android L on my nexus 5 and it couldnt install. so i went back to the recovery mode in attempt to restore my device to the backup i made. i couldnt find the backup on my sd card...weird. so i am stuck. trying to find a way to get my device back.
Click to expand...
Click to collapse
If your backup got deleted then it is lost forever. Flash cwm again then flash the rom you used before L

You should keep a copy of the backup off your device. Maybe third time will be the charm.
http://forum.xda-developers.com/showthread.php?t=2750414

Wakamatsu said:
You should keep a copy of the backup off your device. Maybe third time will be the charm.
http://forum.xda-developers.com/showthread.php?t=2750414
Click to expand...
Click to collapse
i kept a copy of it but when i went back to try and restore with that copy. i didnt see it any more. the bad luck i get with android phones

bitdomo said:
If your backup got deleted then it is lost forever. Flash cwm again then flash the rom you used before L
Click to expand...
Click to collapse
how to flash it again if i have no way to get back in my device?

AHMEDNATOR said:
how to flash it again if i have no way to get back in my device?
Click to expand...
Click to collapse
What do you mean by "get back in my device"? You cant turn it on?

bitdomo said:
What do you mean by "get back in my device"? You cant turn it on?
Click to expand...
Click to collapse
scratch that. i can turn it off and back on. i tried adb sideload but i cant seem to be able to push a rom on the nexus.

AHMEDNATOR said:
scratch that. i can turn it off and back on. i tried adb sideload but i cant seem to be able to push a rom on the nexus.
Click to expand...
Click to collapse
Have you flashed cwm?

bitdomo said:
Have you flashed cwm?
Click to expand...
Click to collapse
yeah i have CWM installed

AHMEDNATOR said:
yeah i have CWM installed
Click to expand...
Click to collapse
What is the command you use to push the rom?

bitdomo said:
What is the command you use to push the rom?
Click to expand...
Click to collapse
the rom i downloaded is called something hammerhead. i renamed it to Rom.zip . when i am in my command prompt. i type "adb push Rom.zip" or when i do the sideload, i do "adb sideload Rom.zip"

AHMEDNATOR said:
the rom i downloaded is called something hammerhead. i renamed it to Rom.zip . when i am in my command prompt. i type "adb push Rom.zip" or when i do the sideload, i do "adb sideload Rom.zip"
Click to expand...
Click to collapse
There is the problem. You didnt tell where to push the zip.
Use this:
adb push rom.zip /data/media/0
after that you should see the rom.zip on the internal storage

bitdomo said:
There is the problem. You didnt tell where to push the zip.
Use this:
adb push rom.zip /data/media/0
after that you should see the rom.zip on the internal storage
Click to expand...
Click to collapse
alright, let me give it a try.

bitdomo said:
There is the problem. You didnt tell where to push the zip.
Use this:
adb push rom.zip /data/media/0
after that you should see the rom.zip on the internal storage
Click to expand...
Click to collapse
it says "error: cloased"

AHMEDNATOR said:
it says "error: cloased"
Click to expand...
Click to collapse
running
adb devices
command showes you any output?

bitdomo said:
running
adb devices
command showes you any output?
Click to expand...
Click to collapse
yeah, it shows some numbers and letters which i assume is my device and next to it, it says "sideload"

AHMEDNATOR said:
yeah, it shows some numbers and letters which i assume is my device and next to it, it says "sideload"
Click to expand...
Click to collapse
Then use
adb sideload rom.zip
command

bitdomo said:
Then use
adb sideload rom.zip
command
Click to expand...
Click to collapse
i get a bunch of stuff and commands come up in the command prompt. i ll try to take a picture for you

bitdomo said:
Then use
adb sideload rom.zip
command
Click to expand...
Click to collapse
there it is

If you don't have path variables set up make sure your rom.zip is in the platform-tools folder of the sdk.
NM. Looks like you do have path variables set up. That second longer error in you screen shot is because you put a space after rom. The first looks like it can't read it because your typing the name wrong. Remember it's case sensitive so Rom.zip and rom.zip are two different things.