Hi have the cable and trying to use a terminal to read the SIM Lock
I get as far as entering dualser and get back the AT-Command Interpreter ready message but then i don't get anything showing up when i try and type in the command AT%UREG?3FE00C,4
I am using HyperTerminal on Windows 98SE, I've set the ASCII properties to Echo typed characters locally, but nothign comes up when I try and enter the AT command
Is there a way to have it show you what you are typing in.
any suggestions / help?
thanks,
Brian
Related
hi again. I am a mac osx user and I was trying to install androidscreencast following the steps from http://code.google.com/p/androidscreencast/ , but it doesn't worked for me. can somebody to give some more details? I got this message...
At which step did you get this message? What happens if you click on the "Details" button from your picture?
Perhaps you need Java Web Start.
this error happens to me as well, before running the screencast. You need to make sure "daemon" is running (what ever that is) by simply running an adb command, such as "adb devices"
If you build your own serial cable for the G1 or use mtty, and boot your phone into the STOCK SPL (hold the camera button while booting) you will see the tri-color bootloader screen and the text "Serial0"
With a proper serial cable set to 115200 8n1 you will see a console that you can type stuff into.
each line is prefixed by "UART0:Cmd>"
task is a valid command For example
task 8 seems to reset the device
task 32 "Checks Security Level (Level=0xFF = Unprivileged, Level=0x00 = SuperCID) "
set is also a valid command however I haven't validated any arguments for it.
What other commands are avaliable? I have tried some of the documented Hermes_Boot loader commands with little success.
I have also parsed through the stock hboot binary for ascii strings and tried a few but to no success.
Has anybody gotten into the oemspl bootloader through stock too? I'm having trouble doing this. It would be really great to figure out how to issue AT command to the phone.
Dear smart people,
When attempting to root my phone, in command prompt I type adb devices and my phone shows up but also emulator-5554. It prevents me from rooting or much else because I get error -2 devices connected.
So because of this I tried lots of other options and I was afraid I might have done something wrong onto my phone and last night I flashed with lg flash tool to 11a.
I am back to stock. please help me with root and recovery install.
thanks!
emulator-5554
hi
emulator-5554 refers to your Bluestack application in windows
you need to stop or kill those services, to do it follow the steps
1. Open Run command: press start and type run ( or ) press Window key +R
2. type "services.msc" and enter
3. wait for some time and this should open a window
4. In the new window, select "BlueStacks Android Service" and click stop [you just need to stop that service]
5. Now check in adb with "adb devices"
6. This should have removed the additional emulator, so you can continue with the rest of the process
If above steps didn't helped then try "adb -e reboot"
Good Luck :good:
Never mind. I
For LG use stump root application for easy root
Fisrt, a little backgroung:
I have a Samsung Galaxy S4 I9500, Rooted, and I flashed Cyanogenmod 12.1 (CM now on) for testing purposes. First I noticed that in CM i couldn't retreive my own phone number and my SMS Center to be able to send SMS messages. CM does have a hidden menu (*#*#4636#*#*), but i wasn't able to update the SMS Center because everytime y entered the number (in my case +584240000954), the phone didn't update and allways returned blank SMSC. So I spent a couple days trying to find out the solution and the only procedure that worked for me was:
..:: THE SOLUTION ::..
::: Fixing the "Own Phone Number" :..
- I inserted the SIM card into my Blackberry phone (torch 9800) and inside setup I was able to write and save my own phone number to the SIM Card. Problem 1 Solved.
::: Fixing the SMS Center Number
- I inserted the SIM Card into my HUAWEI E353 USB STICK and plugged into my Computer. After Windows Installed and recognized the USB Stick, I went to Device Manager and Expanded the Modem devices, then after right-clic and properties I could find out the com port my modem was using (in my case was COM6), then i closed all the device manager opened windows.
- I then started PUTTY terminal connecting to the serial com6, then I fired the following AT commands:
AT (hit enter) <--- Response "OK"
AT+CGMI (hit enter) Response "HUAWEI"
AT+CSCA? (hit enter) Response in my case was "",145 wich means blank or nothing
AT+CSCA="+584240000954",145 (hit enter) --- The SMSC here is from Movistar Venezuela --- Response "OK"
In my case it's all i nedded to fix the SMSC on the SIM Card. Some people report that is needed the following extra AT command
AT+CSAS="+584240000954",145 (hit enter) <--- Response should be "OK", but in my case was "command not supported"
-Closed the putty terminal window, unplugged the USB Modem, removed the SIM Card and placed into my Galaxy S4 and.... voila.. I was able to send SMS Messages again in CM12.1
I hope this can help, i couldn't find any solution trying to send commands directly to the Galaxy S4 through USB or shell terminal.
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Same issue - following
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Sunil_511 said:
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Click to expand...
Click to collapse
Hi, Sunil_511...
Bit speculative this, and I can't say for certain if the following solution would work, because I've never had this problem myself. It also requires that your Nexus 7 be in a fully bootable state.
Go to your Nexus 7 Developer Options in the devices settings and tap on 'Revoke USB debugging authorisations'. Tap on OK to confirm. See attached screenshot.
This, theoretically, should wipe the slate clean.
Reboot both your N7 and your PC/laptop and when you next reconnect your N7 to your PC/laptop, you'll be asked to authorise this new USB connection when you perform some action that requires it.
Well, that's the plan anyway.
Good luck?.
Rgrds,
Ged.
Nope, in my case my tab is not booting to recovery or system. The only option is adb and it is showing unauthorized. My last option what i think off is to change the motherboard.
Following
I have the same error and like to follow
Sunil_511 said:
I have the same error and like to follow
Click to expand...
Click to collapse
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
thanks buddy, i have tried pushing the adb keys but no luck. I will try tge second option. Will let you know after trying.
No difference still the same
BxG4ever said:
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Click to expand...
Click to collapse
tnsmani said:
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
Click to expand...
Click to collapse
Tried your suggestion.. Which i might have tried eventually from googling.. Doesn't make any difference.
Fixed
After doing all the researches, i had to buy a new motherboard and then replace it. Installed new rom and now using it. Spared about 1400INR for a 32 gig version.