I have a note 3 and a galaxy mega. Both screens broken. How can I Find out the android version without using the touchscreen?
Sent from my SM-N900V using XDA Free mobile app
Plug it in to the computer and type: "adb shell getprop ro.build.version.sdk" into the command prompt.
Baconer said:
Plug it in to the computer and type: "adb shell getprop ro.build.version.sdk" into the command prompt.
Click to expand...
Click to collapse
Ok.thanks. You guys know.all.the commands
Sent from my SM-N900V using XDA Free mobile app
Related
I have installed the SDK and I'm able to run ADB
But when I try to run "adb remount"
it returns remount failed: Operation not permitted, even if I run it as su
as a note I'm running Snow Leopard, newest SDK
And VillainROM 1.0 KE2 on a Galaxy S 2
On my mac i have to enter ./adb remount....
Are u entering the ./ at the beginning of the command?
Sent from my HTC Evo
The ./ is cause the path to your adb isn't set in your shell.
From something awesome
Yes, I am. Otherwise it would have said command not found
I can do adb shell, but not remount
Sent from my GT-I9100 using XDA Premium App
WTH? Little help please? I had just got CM7 up and running, went into the file manager and tried to install the gapps from there. A menu came up and said I had to reboot and I've been stuck in Recovery/TWRP mode ever since. What gives? I've searched but not yet found my same problem on here. Please help me, guys.
Please help!!!
Don't panic. You were supposed to install gapps via TWRP. Does it let you into TWRP?
Sent from my Kindle Fire using XDA Premium.
il Stalk3r li said:
Don't panic. You were supposed to install gapps via TWRP. Does it let you into TWRP?
Sent from my Kindle Fire using XDA Premium.
Click to expand...
Click to collapse
Yes, it does. Yeah I figured that one out real quick once I realized I had done so in error. Lol.
Connect to your computer and run:
adb shell
idme bootmode 4000
Then, reboot.
Sent from my Kindle Fire using XDA Premium.
il Stalk3r li said:
Connect to your computer and run:
adb shell
idme bootmode 4000
Sent from my Kindle Fire using XDA Premium.
Click to expand...
Click to collapse
I cant even pull up adb shell. Wtf? I know I have adb...I'm so screwed
Does your computer recognize the device?
Sent from my Kindle Fire using XDA Premium.
il Stalk3r li said:
Does your computer recognize the device?
Sent from my Kindle Fire using XDA Premium.
Click to expand...
Click to collapse
Yep android phone with a composite adb interface
I go to my searchbar and nothing comes up when i type adb shell
Not the searchbar. The command prompt.
Start Menu > Search (Windows 7) > cmd
Sent from my Kindle Fire using XDA Premium.
il Stalk3r li said:
Not the searchbar. The command prompt.
Sent from my Kindle Fire using XDA Premium.
Click to expand...
Click to collapse
gotcha thank you
WTF
il Stalk3r li said:
Not the searchbar. The command prompt.
Sent from my Kindle Fire using XDA Premium.
Click to expand...
Click to collapse
I did and it tells me that:
"adb shell is not recognized as an internal or external command, operable program or batch file"
CD to the directory where you have adb installed.
Example: /AndroidSDK/Platform-Tools
Sent from my Kindle Fire using XDA Premium.
il Stalk3r li said:
CD to the directory where you have adb installed.
Example: /AndroidSDK/Platform-Tools
Sent from my Kindle Fire using XDA Premium.
Click to expand...
Click to collapse
Sorry man, bear with me...I know the folder you speak of but how do I do that? Thank you for your patience
It's fine. Do you have the path to your sdk? If so, in the command prompt...
cd C:\Path-To-Sdk\Etc\Etc
Sent from my Kindle Fire using XDA Premium.
il Stalk3r li said:
It's fine. Do you have the path to your sdk? If so, in the command prompt...
cd C:\Path-To-Sdk\Etc\Etc
Sent from my Kindle Fire using XDA Premium.
Click to expand...
Click to collapse
so on and so forth to the platforms-tools then to the adb?
Yes, adb will be there. Then you can issue the commands I gave to you.
adb shell
idme bootmode 4000
Sent from my Kindle Fire using XDA Premium.
il Stalk3r li said:
Yes, adb will be there. Then you can issue the commands I gave to you.
adb shell
idme bootmode 4000
Sent from my Kindle Fire using XDA Premium.
Click to expand...
Click to collapse
I typed:
C:\android\platform-tools
Which is where the adb is located and I get this
http://i.imgur.com/Hglve.png
Issue the commands now.
Sent from my Kindle Fire using XDA Premium.
il Stalk3r li said:
Issue the commands now.
Sent from my Kindle Fire using XDA Premium.
Click to expand...
Click to collapse
Now I got this:
http://i.imgur.com/ny45G.png
I even tried routing it to the adb file that came in the tools of my kindle fire utility as you see at the top, but nothing.
can someone send me a screenshot of all partitions in note 2 using "df" command in terminal emulator
Taken via terminal emulator
Sent from my GT-N7100 using xda app-developers app
Hey iwant to use adb shell to grant permission for morelocal2 and when I put the command it says error adb closed isearched online and I couldn't find any thing can help any solutions?
Sent from my GT-I9505 using xda app-developers app
Thezombiet said:
Hey iwant to use adb shell to grant permission for morelocal2 and when I put the command it says error adb closed isearched online and I couldn't find any thing can help any solutions?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
in developer options set "root access" as "Apps and ADB"
and use adb shell as su
unlock bootloder,TWRP,super su, and I hane accidentally format it through TWRP now its not getting on just stuck on circle . in internal there is no data to flash and also not detecting adb or fastboot mode .
please help me
You'll need to get adb or fastboot working. Google 15 second adb drivers xda. Then adb push a rom on to your device while in recovery or side load a rom
Sent from my Nexus 5 using XDA Free mobile app
GS150R said:
unlock bootloder,TWRP,super su, and I hane accidentally format it through TWRP now its not getting on just stuck on circle . in internal there is no data to flash and also not detecting adb or fastboot mode .
please help me
Click to expand...
Click to collapse
Wipe your whole system via TWRP and restart into recovery. Connect your phone with your computer and check if your phone is recognized. Also check if you have install all necessary drivers.
jd1639 said:
You'll need to get adb or fastboot working. Google 15 second adb drivers xda. Then adb push a rom on to your device while in recovery or side load a rom
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
1) ADB is working .recovery mode is also working.
2) i have tried this adb sideload youtube video https://www.youtube.com/watch?v=CivvxcM1PCY.
3) when ever i was sliding abs sideload in TWRP
UPDATING PARTITION DETAILS...
E:STORAGE PARTATION "/TERP/BACKUP/004aef8c978b8659" not found
starting adb sideload feature...
4) by doing all above steps i am stuck at transferring ROM
GS150R said:
1) ADB is working .
2) i have tried this adb sideload youtube video https://www.youtube.com/watch?v=CivvxcM1PCY.
3) when ever i was sliding abs sideload in TWRP
UPDATING PARTITION DETAILS...
E:STORAGE PARTATION "/TERP/BACKUP/004aef8c978b8659" not found
starting adb sideload feature...
4) by doing all above steps i am stuck at transferring ROM
Click to expand...
Click to collapse
Rename the rom zip you're trying to flash to just rom.zip and put it on the root directory of your pc. Then open a command window in the folder your adb.exe is and run the command
adb push c:\rom.zip /sdcard/download
That'll put the rom on your device and you can then flash it in recovery
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Rename the rom zip you're trying to flash to just rom.zip and put it on the root directory of your pc. Then open a command window in the folder your adb.exe is and run the command
adb push c:\rom.zip /sdcard/download
That'll put the rom on your device and you can then flash it in recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
thanks but not working . it behaves same as in screen shot
this might be help
using mskip tool kit
GS150R said:
thanks but not working . it behaves same as in screen shot
Click to expand...
Click to collapse
first use the command
adb devices
Does your device show up or do you get the same as you did before?
If it works use
adb push c:\rom.zip /sdcard/Download/rom.zip
jd1639 said:
first use the command
adb devices
Does your device show up or do you get the same as you did before?
If it works use
adb push c:\rom.zip /sdcard/Download/rom.zip
Click to expand...
Click to collapse
not working.
i am doing
1) open cmd from start run.
2) then type cd (copy address of platform tool in sdk)
3)adb devices it show device no.
4) adb push c:\rom.zip /sdcard/Download/rom.zip then some command run an stop .
GS150R said:
not working.
i am doing
1) open cmd from start run.
2) then type cd (copy address of platform tool in sdk)
3)adb devices it show device no.
4) adb push c:\rom.zip /sdcard/Download/rom.zip then some command run an stop .
Click to expand...
Click to collapse
If adb devices doesn't show a device then you don't have the usb drivers setup. Did you try the 15 second adb install I posted in one of my first posts? Just Google it
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If adb devices doesn't show a device then you don't have the usb drivers setup. Did you try the 15 second adb install I posted in one of my first posts? Just Google it
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
15 sec adb works now he is showing my device.
but after push command it goes through long execution and stop same.
how i get into this situation
1) bootloder unlock,rooted,custom recovery ,
2) stock 4.4.4 running
3) then instead of flashing velocity rom I flash velocity gapp from TWRP.
4) reboot perform updating app and stuck.
5) then i have done "FORMAT DATA" in TWRP
6) AND STILL NOT BOOTING
GS150R said:
15 sec adb works now he is showing my device.
but after push command it goes through long execution and stop same.
Click to expand...
Click to collapse
Try a different usb port and cable. It will take a long time to push the rom, 5 to 10 minutes. It sounds like your usb connection is not good
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Try a different usb port and cable. It will take a long time to push the rom, 5 to 10 minutes. It sounds like your usb connection is not good
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
not working :crying:
GS150R said:
not working :crying:
Click to expand...
Click to collapse
Boot into recovery and see if you can find the rom you pushed. If you do, flash it
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Boot into recovery and see if you can find the rom you pushed. If you do, flash it
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
whenever i try to send a zip file it execute bunch of instruction and stop.
I have copied it in notepad take a look
GS150R said:
whenever i try to send a zip file it execute bunch of instruction and stop.
I have copied it in notepad take a look
Click to expand...
Click to collapse
This comes up if you try to execute a command adb doesn't know. Are you typing it in correctly?
Edit, I see the problem. You need a space after adb push c:\rom.zip. it should be adb push c:\rom.zip /sdcard....
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
This comes up if you try to execute a command adb doesn't know. Are you typing it in correctly?
Edit, I see the problem. You need a space after adb push c:\rom.zip. it should be adb push c:\rom.zip /sdcard....
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
By giving space it shows error:closed
GS150R said:
By giving space it shows error:closed
Click to expand...
Click to collapse
What error does it give? Everything must be typed correctly and the rom.zip must be on the root directory of your pc.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
What error does it give? Everything must be typed correctly and the rom.zip must be on the root directory of your pc.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
error is - error:closed and execution is terminated.
yes it is in the directory rom.zip