Anyone know why that after 2-5 seconds after typing adb shell and i get the #. it exits back to the C:\Directory prompt. Its rather frustrating. I am at the clockwork 5.8.2.0 screen trying to setup to run what i need to on my unlocked prime to JB. makes it really hard to transfer big files like the .28 blob file.
Related
I can't seem to get the custom recover working on my eris. I followed the "adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
4. Close the command prompt and turn off you phone."
to the tee and everything seemed to work.I didnt recieve any error msg on the cmd console but when I boot up holding the Vol+ and power I get and Android under a ! in a triangle and a message that says "E:Can't open /cache/recovery/command then I only get 4 options and none of them are to flash a rom so I always reboot system. I really want to put a rom on here but I have no idea what went wrong. Im sorry if this is a redundant post. I combed a hundred of them and couldnt find anything like this. Thank you for any help in advance.
Oh and before I forget I tried the adb fastboot bootloader version as well. Everytime I do it it sits in the command console stating "waiting for device". Im plugged in so I dont understand what Im doing wrong.
Curious to know... are you using windows or mac? have you tried:
adb shell reboot recovery
to see if that does anything?
Maybe you have a different version of the recovery saved than I do, but mine is named "recovery-RA-eris-v1.6.2.img"...maybe you just had an input error somewhere along the line? forgot a capital letter or something? I had the same error myself and following the directions I got the recovery image back
Im running windows 7 and I have both recovery-RA-eris-v1.6.2.img and the recovery-RA-eris.img. I have been using the v1.6.2 and I just modify the command to look like this "adb push recovery-ra-eris-v1.6.2.img /sdcard" How would I use adb shell reboot recovery would I just sub that in place of something? kinda getting discouraged because I have tried this 10x now. I have checked and the usb debugging is on and I do have the eris 2.1 root and not the leak. I wonder is there any way I can flash this with something from the droid mkt place like SUFBS? Or maybe change a rom's name to look like an update zip?Just looking for ways to make this work Im so jealous of everyone that has got it to work.
here is another question and it might be that this is why its not working with the fastboot option but on this website's walk through thefuzz4.net it states to "You will have FASTBOOT highlighted in red like it is here" Now Im not a pro at this but what does this mean? How do I highlight text in the command shell? I would post the full url but since Im new it wont let me post urls yet.
Dachix said:
here is another question and it might be that this is why its not working with the fastboot option but on this website's walk through thefuzz4.net it states to "You will have FASTBOOT highlighted in red like it is here" Now Im not a pro at this but what does this mean? How do I highlight text in the command shell? I would post the full url but since Im new it wont let me post urls yet.
Click to expand...
Click to collapse
when hes saying fastboot will be highlighted in red he's referring to booting your phone into the standard recovery mode (when power is off) hold volume up and power.
Walking Taco seriously love that name. The only options I get when I hold down vol+ and pwr is 1. reboot system now 2. apply sdcard update 3. Wipe Data/ factory reset 4. Wipe cache partition and all are in purple and at the bottom on the phones screen is "E:Can't open/cache/recovery/command"
The website fuzz4net says to:
WINDOWS USERS
From your tools directory in the sdk do the following command
adb fastboot bootloader
You will have FASTBOOT highlighted in red like it is here
Now on your computer do the following
Fastboot flash recovery recovery-RA-eris-v1.6.2.img
Ok after that completes pull the battery then power back up with Vol Up + Power to enter recovery
But when I get done ...after the last step the cmd.exe window states <waiting for device> any ideas? Thanks for helping too. Leave it to me to hit a snare
almost forgot when it gets to <waiting for device> nothing happens I literally have left and come back 3 hours later and no progress was made
Dachix said:
almost forgot when it gets to <waiting for device> nothing happens I literally have left and come back 3 hours later and no progress was made
Click to expand...
Click to collapse
I honestly don't know man, I would factory wipe it and try and start from the beginning. I followed the fuzz's instructions and was rooted in less than a half hour. Sorry brother.
Thanks!
ROOTED!!!!!! Here is what I did:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.v1.6.2.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.v1.6.2.img
This was not working until I deleted the spaces in between img/sdcard for all the commands. Then and I do not know why but when I would turn odd my phone the vol+ pwr on it would not work so instead I used the adb shell reboot recovery command like droidfreak suggested then BOOYAH the custom recovery was loaded thank you all for helping me.
Dachix said:
ROOTED!!!!!! Here is what I did:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.v1.6.2.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.v1.6.2.img
This was not working until I deleted the spaces in between img/sdcard for all the commands. Then and I do not know why but when I would turn odd my phone the vol+ pwr on it would not work so instead I used the adb shell reboot recovery command like droidfreak suggested then BOOYAH the custom recovery was loaded thank you all for helping me.
Click to expand...
Click to collapse
Awesome news! Have fun with your rooted phone!
Forgive the noob question but...
So I've flashed the stock, deodexed TW ROM posted by DocRambone. Now, when I open Terminal Emulator and enter 'su', the 'reboot' command doesn't seem to be available anymore. I ran 'ls /system/bin' and definately didn't see it listed in the output. Has anyone else noticed this? Am I not doing something right?
This isn't a huge problem, but any input would be appreciated. Thanks!
In ADB you should just type reboot or reboot recovery you can't be in su when this is done. Just start communication through ADB then type one of those commands.
too complicated though
Yeah I can still connect my Tab to my computer and use adb to reboot it, but that's too complicated.
Prior to flashing the new ROM, if I ever felt the need to reboot my Tab, I'd just open Terminal Emulator, type in 'su' then 'reboot' and then wait for it to come back up. Basically I'm just too lazy to reboot it using the power button, but if I gotta then I gotta.
Hello friends,
I've a problem with CWM 5.8.2.0. Until now I replaced with ease different ROM and went all right. But after the last one, system doen't reboot. Everything is installed properly, the system restarts properly with the factory image (eeepad asus Tegra etc..), but after few seconds it returns to the previous commands (reboot system now, install zip fron sdcard, wipe data and so on). I tried to restore the "old" ROM, all the step are complete, but I can't go further. The installation stop always after a few seconds. Thank you for your help.
How to Unbrick your Transformer Prime
"DiamondBack" discovered this, i tried it and it worked for me:
Don't be afraid, your Prime should be recoverable. This is the good news. The bad news is, that you need quite some knowledge of ADB.
To recover your Prime (most likely) you need the following:
A working ADB setup (please google that if you don't have it, "tutorial setup adb" or something like that should do the trick)
The USB-Cable to connect the Prime to your PC
A few minutes time
Now do the following:
Make sure your Prime is in Recovery mode (CWM)
Open a cmd line on your pc
Type: "adb shell"
You should see a "#" now
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter]
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
I Hope it helps!
I looked all over the internet for help with this phone. I rooted it for a friend and a week later, he said he restarted the phone and everything started force closing.
I troubleshot all day, and came to figure out that my only known to me as of now, is flashing CWM to it, via ADB. I am having several issues with setting up ADB, and getting the phone to communicate with my computer. Device manager DOES show that there is an ADB device installed correctly, so what would my next move be? I got the phone into FTM mode, (fastboot?) and I know that that is what I need to do to get ADB to communicate with my phone.
halp pls
Really no one can help???
bamp
cammiso94 said:
bamp
Click to expand...
Click to collapse
ADB Drivers for Windows Vista/7
Tutorial- http://www.youtube.com/watch?v=RDA8PpPSFuk
If you havn't found this yet...
Your answer is here: androidforums.com/flash-all-things-root/ Good luck!:good:
CWM Beta
From Android Forums ... Thanks to Junkie2100
this is an unfinished copy of cwm, tested to be almost completely functional
standard warnings apply, use at your own risk, you try to blame me for breaking your phone i will laugh at you
instructions:
fastboot method is possible, but i will go through the terminal/adb method
download the recovery file, and put it on the root of your sd. no folders, just directly on the sd
get your phone rooted and get a copy of terminal emulator or connect to it through adb on your computer, adb will require zte drivers and the adb program on the pc. the choice is yours
fire up adb by typing
Code (Text):
adb shell
in the command prompt, if its not working you dont have adb in the directory youre in, just copy adb.exe and the two .dll files to c:\windows\system32\ and itll work from anywhere, or learn how command prompt works
or fire up terminal emulator on the phone
on adb shell or terminal emulator type
Code (Text):
su
dd if=/sdcard/flash_cwm_test2.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
you will then need to run
Code (Text):
reboot recovery
and then hit reboot when cwm comes up, if it asks to disable recovery flashing press yes or it will put stock recovery back next time the rom boots
known bugs:
unmounting doesnt work
downloads:
w.ww.4shared.com/file/2qBR2Kfr/flash_cwm_test2.html
i apologize for it being 4shared, if someone wants to make a mirror ill put it up
Hi everyone! Please help me. I've accidentaly typed in Terminal Emulator commad "stop" with SU permissions and my phone first freezed then don't want to boot up. How can i start my phone? I can access only recovery and fastboot.
Edit: Also i can run adb commands. So the question, what command i need to run for start phone?
If you have access to fastboot you could simply use RSD Lite to reflash your phone to stock.
DeathChaos said:
If you have access to fastboot you could simply use RSD Lite to reflash your phone to stock.
Click to expand...
Click to collapse
I don't want to flash stock then again set everything i need. I just need a correct command to run thru adb for start.
It's like "adb start" or "adb shell start", i don't know.
Abstractionist said:
I don't want to flash stock then again set everything i need. I just need a correct command to run thru adb for start.
It's like "adb start" or "adb shell start", i don't know.
Click to expand...
Click to collapse
Honestly, i never heard of the command "stop".
You could check the documentation for adb.
Edit: There is a command called start which "restarts execution of an emulator/device instance."
Abstractionist said:
Hi everyone! Please help me. I've accidentaly typed in Terminal Emulator commad "stop" with SU permissions and my phone first freezed then don't want to boot up. How can i start my phone? I can access only recovery and fastboot.
Edit: Also i can run adb commands. So the question, what command i need to run for start phone?
Click to expand...
Click to collapse
Can also connect that bad boy of yours to comp and run start command in terminal. I have done this too. I also ran bootanimation in android terminal, continous bootloop. But fun is had running those xbin/bin commands. Lol
XT912 RaZR SpYdEr CDMA
hit ThAnKs if I was helpful!!!
I have done this stop command too but my phone still boots up normally it just goes blank and my touch buttons are lit up and all I did was power off by holding power button for 6 seconds and power back on and booted up normally ? I'm alittle scared to play with commands now because I was just typing all random root user commands and I went through a bootloop like 5 times and I reflashed through RSD lite but I know now that I shouldn't play with those cmds now??