Upon getting an permission error when using ./adb shell .... I noticed that in the displayed output, http links are being used instead of google's own aggresive years-long push for sites to use https due to security concerns of the http protocol etc...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The whole developer.android.com site actually uses the https protocol, yet they refer to http in the output?
IMHO you should ask this question to the people who put the ADB version you are using into the world.
jwoegerbauer said:
IMHO you should ask this question to the people who put the ADB version you are using into the world.
Click to expand...
Click to collapse
Touche you're right.
Related
New Custom Logcat Grabber for noobs
Please put adb.exe into Path of Put this exe into Tool folder of SDK
Require Microsoft.Net 2.0 SP2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If useful try to cast vote to make it on one of the WiKi or Stickies
For Error and Feature Request Please post here
http://mobile5.in/viewtopic.php?f=3&t=77&p=219#p219
Why would you use this tool when you have DDMS in the STK already ??
Amon_RA said:
Why would you use this tool when you have DDMS in the STK already ??
Click to expand...
Click to collapse
i think too
is it possible you can make it a bit faster?
It seems like its playing catch up compared to the output from doing adb logcat?
Also i left it running and it crashed, not sure whether it had filled a buffer of something...
if it matters i'm using the modaco desire rom.
Has anyone tried to use QEMU or BOCHS with GP5? I haven't seen anything saying it will specifically work with Galaxy devices but I just wondered if maybe someone has gotten it working. I don't fully understand the Android OS yet so I wasn't sure about trying it myself.
Yeah, I got Boochs working!
And I have got it to work with Redhat, and windows 95.
however both are a bit hard to control, and have no internet support:
Boochs:
http://forum.xda-developers.com/showthread.php?p=21293078
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
redhat image:
http://superb-sea2.dl.sourceforge.net/project/bochs/Disk Images/RedHat Linux/redhat_6-512mb.zip
If you want to use the redhat image rename it to c.img and put it in the sdl folder
username:root Password: redhat
Boochs install instructions on the download page.
Sorry to bother you further but after it boots and I put in the username and password, it just starts as a command line tool or something and anything I try it just says isn't a proper command. Is a ui supposed to boot?
Good day!
My android phone is Alcatel OT-978, Gingerbread 2.3.7. After days of extensive research, I really couldn't find a way to root my phone. I had tried each of these methods but they all failed:
- z4root;
-super oneclick;
-gingerbreak;
-zergrush;
-psneuter;
I had stumbled upon some random post on the net saying that another workaround is by "hacking" the bootloader. Using ADB, I had these files on my phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My problem is, I can't use the command adb pull on the concerned mtdblock. Every time I use the mentioned command, RE: adb pull /dev/block/mtdblock4 c:\users\ash^03\desktop\system.img, i get the result REMOTE OBJECT '/DEV/BLOCK/MTDBLOCK4' NOT A FILE OR DIRECTORY
Can somebody help me on this. I really need to "hack" or have somebody root my bootloader for me to be able to gain a full root on my device.
BTW, when i type "adb root", it says 'adb cannot run as root in production builds."
I want to share a program that could easily detect, kill and protect from annoying Ghost Push Trojan Android Virus with friendly user interface. I have tested many times on my customers' phones and so far so good. This virus may persist even if you flash firmware. But this tiny tool will save your device from that Virus. Busybox will also be installed because it is needed to execute required scripts.
Turn on USB Debugging
Plug the phone
Run Software
Authorize incoming usb connection
Choose any action from tool
Root Access is Required!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks to Myanmar Developer Phyo Nyi Nyi.
DOWNLOAD LINK - CLICK ME
Thread Deleted
@ell123
It's bricked Normally the reason why is shown, too.
Example:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Such a screen is originated by BootLoader
FYI:
When you turn on an Android device, it checks the operating system to make sure it's safe to use. This means the code comes from a trusted source and hasn't been changed or corrupted.
If your operating system could have a problem, you can get a warning message that brings you to page g.co/ABH what you should visit.
jwoegerbauer said:
@ell123
It's bricked Normally the reason why is shown, too.
Example:
Click to expand...
Click to collapse
Damn, it's very similar to that except with a <!> instead of the triangle and without the explanation or press power to continue.
@ell123
Unless you enabled USB debugging, means you can access phone by means of ADB, you can nothing do, IMHO.