how do i mount my phone to my pc from the console? i dont have my mini sd card reader and i'm stuck on the t-mobile g1 screen. I need to load the build onto the card so i can flash it
what have you done so far
installed radio, installed spl, im on the g1 screen and its not moving forward, after i install the spl and it reboots to recovery, am i supposed to do anything on the recovery screen?
Yeah you need to do an alt w and wipe. Also what rom are you running currently?
right now im running JF 1.5
The problem is you need to re-flash the rom to your phone when you're done applying the spl. I dont think you can do it thru fastboot. And I dont believe adb works until the phone has booted. I think your only bet is a card reader....sorry man
sweet, 19.00 for a new usb card reader, cheap one
fast boot would mount, right? by pressing the camera and power button, i managed to get to the fastboot menu with the 3 skateboard androids, should i be able to load it that way?
to mount the sd on your computer via usb from the recovery console (alt x) type:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
then to unmount:
echo "" > /sys/devices/platform/usb_mass_storage/lun0/file
keatonreckard said:
to mount the sd on your computer via usb from the recovery console (alt x) type:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
then to unmount:
echo "" > /sys/devices/platform/usb_mass_storage/lun0/file
Click to expand...
Click to collapse
This post should be sticky'd
keatonreckard said:
to mount the sd on your computer via usb from the recovery console (alt x) type:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
then to unmount:
echo "" > /sys/devices/platform/usb_mass_storage/lun0/file
Click to expand...
Click to collapse
this is only if u can get the recovery right?
if you can get to the recovery is there another way to have this done?
once i insert echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file in recovery mode it tells me that permission is denied? what do i do?
romeo9710 said:
once i insert echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file in recovery mode it tells me that permission is denied? what do i do?
Click to expand...
Click to collapse
try su before it?
Umm... actually, ADB does work when it is hanging, have you tried that yet? Just do:
adb push (location of firmware) /sdcard/
and you should be able to boot up from their.
Related
i have a problem, for some reason i cant go to recovery mode. i have JFv 1.42_RC33... what can i do
What exactly do you mean by that? Have you tried booting into recovery straight from the terminal?
Iceucold said:
Have you tried booting into recovery straight from the terminal?
Click to expand...
Click to collapse
That made even less sense.
forgive me if im mistaken, but doesnt it have something to do with the bootloader as well?
kydcleric said:
forgive me if im mistaken, but doesnt it have something to do with the bootloader as well?
Click to expand...
Click to collapse
i dont know im new to this stuff but what happens is that the g1 boot screen pops up when i press home+power then it just restarts and shows the g1 boot screen again then it goes to the normal home screen
Iceucold said:
What exactly do you mean by that? Have you tried booting into recovery straight from the terminal?
Click to expand...
Click to collapse
i dont know what u mean
Sorry about that. I was referring to going into the terminal emulator and typing in the command:
Code:
# reboot recovery
Iceucold said:
Sorry about that. I was referring to going into the terminal emulator and typing in the command:
Code:
# reboot recovery
Click to expand...
Click to collapse
nothing happens i put that in there and it just shows a money sign under it.. and when i just put reboot it says
reboot: operation not permitted
You are holding down home first right? I.e. press home and hold it down and then press power(I continue to hold home down all the way up until I see recovery mode starting)
Can you check if the recovery image (/system/recovery.img) is intact?
if you're using the haykuro builds, it is known that reboot won't work from terminal emulator. but you should be able to reboot recovery through adb shell.
I remember I read somewhere that certain bootloaders have a different key sequence for recovery mode, but i've never seem any of them.
ooooo crap i just checked it and there is no recovery.img in there ok what do i do??
someone plz help me out
probably best to dl the one from the Rooting Hacking & Flashing... post. They have a link to the file there. Just dl it and, as su, copy it to the folder they say.
what post???
Cosine said:
what post???
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=442480
yea but thats only to get to root and i already did that... and i just tried it and it dosent work
Cosine said:
yea but thats only to get to root and i already did that... and i just tried it and it dosent work
Click to expand...
Click to collapse
The suggestion was to try restoring the recovery image as outlined in that thread: (though you shouldn't need to do the "telnetd" part)
Instructions:
1. Download recovery.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
2. Download the Hard SPL and copy the zip file to the SD card.
3. All files must be on the root of your SD card.
4. Restart your phone. Wait for your phone to start up fully and show the home screen.
5. After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
6. Download an Android "Telnet" application from the Market and connect to localhost.
7. If you connect successfully, you will have a root prompt "#".
8. Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img
Now you have root!
Click to expand...
Click to collapse
so should i just try
8. Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img
in the terminal emulator
UPDATE: First of all, thanks to everyone that responded. You guys are awesome! I'm returning the phone to HTC and hopefully it gets fixed. I do believe its hardware related but I think the real answer is way over my head.
I'm not really sure whats going on here, but the only ROM I can use / flash is Cyanogen. I was running trickdroid and then the phone decided to freeze and just reboot whenever I tried to launch anything. I cant use my nand from stock, install any sense, aokp or miui ROM. They install and even boot, but then it just freezes and reboots as soon as I unlock the lock screen. I even went as far as returning it back to stock with the RUU, but same scenario. I'm completely stumped. Anyone have anything to suggest? Thanks.
You flashed with a fullwipe and boot.img?
I did, multiple times. I typically do a factory reset, wipe cache, format data, format system, format dalvik then install the ROM. Once the ROM is installed, I then reboot back into fastboot and flash the boot.img. Just to add a little more, your ROM rocks man and I really want to go back to using it. The reason why I had to flash the boot by fastboot is because when I used your script it kept telling me permission denied on certain lines.
Bump
try to flash any sense rom, Format /system in recovery before flashing. Then run an RUU
An RUU wont run unless you have a sense ROM already, So dont worry if the phone dont boot, Aslong as the rom flashes, the RUU should work.
Then just start from the beginning.
Oh and RUU requires RELOCKED bootloader and in some cases Stock recovery
azzledazzle said:
try to flash any sense rom, Format /system in recovery before flashing. Then run an RUU
An RUU wont run unless you have a sense ROM already, So dont worry if the phone dont boot, Aslong as the rom flashes, the RUU should work.
Then just start from the beginning.
Oh and RUU requires RELOCKED bootloader and in some cases Stock recovery
Click to expand...
Click to collapse
I tried this and it didn't work. As soon as i unlock the lock screen it just freezes and reboots. So confused....
dubntz said:
I tried this and it didn't work. As soon as i unlock the lock screen it just freezes and reboots. So confused....
Click to expand...
Click to collapse
Yes but dont worry about that, The RUU should still work even with the phone freezing. You just need the Sense ROM on the phone, Whether it boots or not.
azzledazzle said:
Yes but dont worry about that, The RUU should still work even with the phone freezing. You just need the Sense ROM on the phone, Whether it boots or not.
Click to expand...
Click to collapse
Sorry, but what I meant to say is that I put a sense ROM back on, ran the RUU and it still froze once i tried to unlock the lock screen.
dubntz said:
Sorry, but what I meant to say is that I put a sense ROM back on, ran the RUU and it still froze once i tried to unlock the lock screen.
Click to expand...
Click to collapse
Oh i see... That is so weird
Have you asked in the Cyanogen thread ? The ROM must have altered something deep inside for something like this to happen...
Ive never seen anything like it
azzledazzle said:
Oh i see... That is so weird
Have you asked in the Cyanogen thread ? The ROM must have altered something deep inside for something like this to happen...
Ive never seen anything like it
Click to expand...
Click to collapse
I have not posted anything, although i'm going to now. It is so weird. I can install any sense ROM, but it freezes when I try to unlock the lock screen. I can not install AOKP or MIUI as they just boot loop. Cyanogen is the only ROM that I can flash...lol
dubntz said:
I have not posted anything, although i'm going to now. It is so weird. I can install any sense ROM, but it freezes when I try to unlock the lock screen. I can not install AOKP or MIUI as they just boot loop. Cyanogen is the only ROM that I can flash...lol
Click to expand...
Click to collapse
Have you tried taking out your sim card and rebooting? My phone kept freezing as soon as I unlocked the lockscreen and this is what worked for me...
I have, but no luck.
Sent from my HTC One S using Tapatalk 2
I feel like the phone is not properly wiping or installing the boot.img correctly. I have been trying different things for days. Just doesn't make sense. No pun intended..ha
Just some more experimenting. I tried to use a script from the trickdroid ROM to flash to boot and It came back with some permission denied errors. I'm wondering if that has something to do with it. I don't get any errors like that when I install it through fastboot though...
I'm beginning to think it has something to do with the boot.img not flashing properly. I think there might be some permission issues going on with the phone. I just tried to flash the latest CM nightly with the new boot and it just boot loops.
do you have an sdcard bu
you could try formatting and reloading the card, assume you can get to recovery
also, i fastbooted boot img before flashing rom, one right after the other. thought you said you flashed rom rebooted then flashed boot img, not sure if that matters
good you are wiping system also, or that can cause issues too
rugmankc said:
do you have an sdcard bu
you could try formatting and reloading the card, assume you can get to recovery
also, i fastbooted boot img before flashing rom, one right after the other. thought you said you flashed rom rebooted then flashed boot img, not sure if that matters
good you are wiping system also, or that can cause issues too
Click to expand...
Click to collapse
The ONES has an internal SD Card only so I cant remove it; however, I have formatted it and still the same results. I'm thinking I can't install any ROM that requires a new boot.img. Is something not mounting properly?
dubntz said:
Just some more experimenting. I tried to use a script from the trickdroid ROM to flash to boot and It came back with some permission denied errors. I'm wondering if that has something to do with it. I don't get any errors like that when I install it through fastboot though...
Click to expand...
Click to collapse
This script youre running, is it the one linked from the Trickdroid 4.3 thread, from http://d-h.st/2JV ?
If so check below where it tries to chmod +x fastboot-linux comes before the script cd's to the files directory where fastboot-linux actually lives. So fastboot-linux never gets execute permissions and therefore everything except the echo stuff fails.
Code:
@echo off
chmod +x fastboot-linux
echo "Flashin boot.img"
sleep 1
echo ...
cd files
./fastboot-linux flash boot ../boot.img
echo ...
echo "Flashing complete"
echo ...
echo "Erasing cache partition"
sleep 1
./fastboot-linux erase cache
echo ...
echo "Cache partition cleaned"
echo ...
echo "If there were no errors, you can continue"
echo ...
echo "If not, try again!"
echo ...
echo "Enjoy TrickDroid!"
sleep 20
To make it work edit it like this (move the cd files) or go into files and run chmod +x fastboot-linux before running the script. The Mac script has the same problem.
Code:
@echo off
cd files
chmod +x fastboot-linux
echo "Flashin boot.img"
sleep 1
echo ...
./fastboot-linux flash boot ../boot.img
echo ...
echo "Flashing complete"
echo ...
echo "Erasing cache partition"
sleep 1
./fastboot-linux erase cache
echo ...
echo "Cache partition cleaned"
echo ...
echo "If there were no errors, you can continue"
echo ...
echo "If not, try again!"
echo ...
echo "Enjoy TrickDroid!"
sleep 20
Dunno if this will help your general situation though, good luck!
frdd said:
This script youre running, is it the one linked from the Trickdroid 4.3 thread, from http://d-h.st/2JV ?
If so check below where it tries to chmod +x fastboot-linux comes before the script cd's to the files directory where fastboot-linux actually lives. So fastboot-linux never gets execute permissions and therefore everything except the echo stuff fails.
Code:
@echo off
chmod +x fastboot-linux
echo "Flashin boot.img"
sleep 1
echo ...
cd files
./fastboot-linux flash boot ../boot.img
echo ...
echo "Flashing complete"
echo ...
echo "Erasing cache partition"
sleep 1
./fastboot-linux erase cache
echo ...
echo "Cache partition cleaned"
echo ...
echo "If there were no errors, you can continue"
echo ...
echo "If not, try again!"
echo ...
echo "Enjoy TrickDroid!"
sleep 20
To make it work edit it like this (move the cd files) or go into files and run chmod +x fastboot-linux before running the script. The Mac script has the same problem.
Code:
@echo off
cd files
chmod +x fastboot-linux
echo "Flashin boot.img"
sleep 1
echo ...
./fastboot-linux flash boot ../boot.img
echo ...
echo "Flashing complete"
echo ...
echo "Erasing cache partition"
sleep 1
./fastboot-linux erase cache
echo ...
echo "Cache partition cleaned"
echo ...
echo "If there were no errors, you can continue"
echo ...
echo "If not, try again!"
echo ...
echo "Enjoy TrickDroid!"
sleep 20
Dunno if this will help your general situation though, good luck!
Click to expand...
Click to collapse
It flashed the boot with no issues this time. Still not able to use another ROM. Its so odd. They install but as soon as I unlock the lock screen it just freezes and reboots.
assume you are using the latest clockworkmod recovery for the "OneS"
checked all md5's before flashing anything
can you take the system and boot images from a good sense nandroid or sense rom and put them on your pc in your fastboot.exe folder, open command window cd to fasboot.exe folder and adb reboot bootloader to get into fastboot
then run these commands 3 times
fastboot -w
fastboot erase system
fastboot erase cache
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
you will have restore any user data manully
if you don't have a nandroid copied to you pc from phone do that first
It sounds like maybe you have not wiped everything from cm rom from phone, erasing multiple times may help
Hello community,
Earlier I was messing with the voltages on setcpu, and I guess I ticked the box "set on boot" and now my phone wont boot pass the lockscreen. I don't want to wipe my phone if i don't need to.
I tried removing it via adb shell with these instructions i found:
1) Boot into recovery
2) Connect USB
3) open ADB shell - 'adb shell'
4) mount the Data folder - 'mount /data'
5) navigate to the Data folder - 'cd /data/data'
6) Remove the config file - 'rm -r com.mhuang.overclocking'
7) exit and reboot phone
but i can't mount data. any help would be great. Thank you
Hello,
The SetCPU program can generate a "safe mode" script in case that happens.
It puts it into the root directory of the sdcard.
You have to generate it from within the program, it does not do it automatically.
I have attached the file I generated on my phone, I hope it can help you.
I think the instructions will be to boot in "red recovery" then flash the safe mode file to remove the "set on boot" flag.
Do not set on boot until you are sure the OC/UV settings do not crash your phone.
Good luck!
jayson94538 said:
Hello community,
Earlier I was messing with the voltages on setcpu, and I guess I ticked the box "set on boot" and now my phone wont boot pass the lockscreen. I don't want to wipe my phone if i don't need to.
I tried removing it via adb shell with these instructions i found:
1) Boot into recovery
2) Connect USB
3) open ADB shell - 'adb shell'
4) mount the Data folder - 'mount /data'
5) navigate to the Data folder - 'cd /data/data'
6) Remove the config file - 'rm -r com.mhuang.overclocking'
7) exit and reboot phone
but i can't mount data. any help would be great. Thank you
Click to expand...
Click to collapse
A lot of the time the recovery isn't setup to properly use adb but maybe you just need to try a different command.
First see what is mounted and
ih what mount options by simply typing 'mount' in adb shell
Normally about halfway down you will see /dev/block/mmcblk0p2 /data make sure it is there and mounted read write. If it's not mounted try mounting it with 'mount -o rw /dev/block/mmcblk0p2 /data'
Or if it is mounted read only (which would be weird) try mount -o remount rw /dev/block/mmcblk0p2 /data
If that doesn't help you might need to do a nand droid backup, wipe data, reboot, create a safemode script like mentioned above, restore the nand backup and run the script in recovery.
Thank you very much for your replies. Helped me a ton. I got it fixed thanks to you guys.
Sent from my SAMSUNG-SGH-I997
Hi,I am an user of Micromax A87.My device is not detected in normal mode by adb device comm. But it is detected by fastboot devices comm in fbm. Is there any way to root in fastboot /download mode?
idhbar said:
Hi,I am an user of Micromax A87.My device is not detected in normal mode by adb device comm. But it is detected by fastboot devices comm in fbm. Is there any way to root in fastboot /download mode?
Click to expand...
Click to collapse
No, but you can use fast boot to flash a rooted rom. I'd highly suggest flashing a recovery first which fast boot can also do.
Sent from my LG-P509
I'm sure I could make a script to do it easily...
Code:
mount|grep sys
echo Making an image of system
adb shell cat /dev/block/mtdblock2>/cache/sys.img
echo Pulling the system image
adb pull /cache/sys.img /tmp/
mkdir /tmp/sys
echo Putting phone in fastboot
adb reboot fastboot
echo Mounting system
mount -o loop -t yaffs2 /tmp/sys.img /tmp/sys
echo Getting the SU binary
wget [url]http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip[/url] -O /tmp/su.zip
mkdir /tmp/suarch
unzip su.zip -d /tmp/suarch
echo Installing SU
cp /tmp/suarch/system/app/Superuser.apk /tmp/sys/system/app/
cp /tmp/suarch/system/bin/su /tmp/sys/system/bin/
echo Unmounting system
unmount /tmp/sys.img
echo Replacing the devices /system
fastboot flash system /tmp/sys.img
echo Done!
echo Cleaning up...
rm /tmp/sys
rm /tmp/su.zip
rm /tmp/suarch
rm /tmp/sys.img
fastboot erase cache
echo Rebooting...
fastboot reboot
Adjust it for your system/phone, this is for linux clearly, and this is a work in progress!
I haven't tested it yet, just happened to be on xda-developers while in soc 102 and saw a challenge
You learn something new every day. Thanks. I'm a Windows programmer not a Linux programmer, although I'm learning...
bill.weckel said:
You learn something new every day. Thanks. I'm a Windows programmer not a Linux programmer, although I'm learning...
Click to expand...
Click to collapse
I only use linux, but I have a windows buildbot...
Also, my little script has a few problems, such as the /system block not often the same between devices; /cache partion size limitations, assuming fastboot and adb exist on the host, etc...
With a bit of bash fun you could easily find out the partion block name, regardless of the device.
You can stream the /system img, possibly compressing it via gzip and pipes, solving the /cache part and speeding up rooting times.
Ship with binaries, fixes the fastboot/adb assumption problem.
At that stage we would have a share-able script that could run on a rooted android itself, rooting others with only a male to male micro usb cable and usb host mode support. You could even in theory do it from adb over tcp, minus the flashing it back part.
Hey.
I got a Samsung Galaxy S4 Mini (I9190 3G version) and the device is rooted. Unfortunately, I wiped all my roms from the SDcard and no:crying:w I cant access my device.
I trıed to connect my device to the PC, but the PC detects the device; but not the storage. Therefore, I cannot transfer files from the computer to the device. I tried mounting the /system, /data and /cache. I got CWM recorvery v6.0.3.5.
I searched a bıt on the internet and I found out that I were needed to use ADB. I downloaded and placed my ROM ın the MODDED_FILE folder. I open the CMD and change the ADB to recorvery. When I have changed it, I choose the file and I push the file from MODDED_FILE to the /sdcard section. When I push it, it give me this message:
" daemon not runningç starting ıt now on port 5037 "
" deaemon started successfully "
su
mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /data
mkdir /data/media/rr
exit
exit
" # su
/sbin/sh: su: not found
" # mkdir /data/media/rr
" # exit
C:/Users/XXXX/Desktop/ff/tools/tmp1
----------------------------------------------------
pushing cm-10.2.1.3-serrano3gxx.zip to /data/media/rr ....
------------------------------------------------------
The ADB tool is stuck here. I have waited many hours and tried again and again.
The PC wont detect my storage.
I tried to set the external sdcard onto my computers SDCard slot, and placed the ROM in the external sdcard. I tried to install the zip, but it gives me the error;
(bad)
İnstallation aborted.
Thank you for fast answers.
needs
can921 said:
Hey.
I got a Samsung Galaxy S4 Mini (I9190 3G version) and the device is rooted. Unfortunately, I wiped all my roms from the SDcard and no:crying:w I cant access my device.
I trıed to connect my device to the PC, but the PC detects the device; but not the storage. Therefore, I cannot transfer files from the computer to the device. I tried mounting the /system, /data and /cache. I got CWM recorvery v6.0.3.5.
I searched a bıt on the internet and I found out that I were needed to use ADB. I downloaded and placed my ROM ın the MODDED_FILE folder. I open the CMD and change the ADB to recorvery. When I have changed it, I choose the file and I push the file from MODDED_FILE to the /sdcard section. When I push it, it give me this message:
" daemon not runningç starting ıt now on port 5037 "
" deaemon started successfully "
su
mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /data
mkdir /data/media/rr
exit
exit
" # su
/sbin/sh: su: not found
" # mkdir /data/media/rr
" # exit
C:/Users/XXXX/Desktop/ff/tools/tmp1
----------------------------------------------------
pushing cm-10.2.1.3-serrano3gxx.zip to /data/media/rr ....
------------------------------------------------------
The ADB tool is stuck here. I have waited many hours and tried again and again.
The PC wont detect my storage.
I tried to set the external sdcard onto my computers SDCard slot, and placed the ROM in the external sdcard. I tried to install the zip, but it gives me the error;
(bad)
İnstallation aborted.
Thank you for fast answers.
Click to expand...
Click to collapse
have to installed cwm?
is odin able to detect your device?
[email protected] D€\/¡! said:
have to installed cwm?
is odin able to detect your device?
Click to expand...
Click to collapse
Hey.
Thank you for fast answer.
No, I do not get any message in Odin saying "Added" when plugging in my device. I have installed Samsung USB drivers too.
get it into download mode then try as odin work in download mode only