whats up guyz im new/old to this forums new/old means , i dont get online to much
well i have been tweaking a little bit with my droid DNA and found out some work around for some problems people might be having trying to unlock their bootloaders
the first problem i encountered was the adb killing process , adb is out of date . there is a little work around for this , that worked with me and my friend s DNAs to resolve this we just killed the adb daemon with this command
adb kill-server
then we started the server with the command
adb start-server
allright . the only way you will not get that error of adb out of date is , if you see adb starting on some port . i forgot the port number, but thats the only way you will not be getting the error ..
the second problem i encountered in the process of unlocking my phone was the restore update not finishing , which was caused by the bug of adb out of date error. once you resolve the problem with the adb bug out of date error , then you will be able to restore the phone successfully
but hold on , there is another problem some people might be getting , when you execute the command " adb restore backup.ab " if your device is taking to long to finish the restore and the window is behind looping, dont worry about it just wait couple of minutes control -c on the window looping and control -c on the window that you waiting on the restore to finish ... i tried that couple of times then i figure that the restore did go thru ..
some people might be getting an error with this command "adb shell mv /data/DxDrm /data/DxDrm_org" if you getting the error that says failed to blah blah blah permission denied , the cause for of that error is that the restore didnt go thru . if you got that error you can reboot safely , your device is not bricked yet lolz ..
when you get to the section that you have to repeat the exploit again , you gonna start getting the error again with the adb killing the process out of date thingy , dont worry just redo the work around i posted above , i control c the restore window and the loop window
couple of times just to make sure it was working fine , and it did . it was working fine
sorry for my english guys . i just wanted to point out those little flaws in the process of unlocking the bootloader , just in case some people get the same errors , they wont have to break their heads with it ... blessed be ..
Minor audible...
I was using the video made by DroidModderX and was able to get through it basically step by step with one minor hiccup. One the step where you start the first command prompt to do that "loop of errors" and move to the second command prompt, my system had an error doing this until I unplugged the phone and plugged in again. That wasn't mentioned in the tutorial but worked great once I did that part. It seemed like ADB got a little screwed up or something but, once I unplugged/ replugged it all worked normally. One other thing I noticed was that in the video (he uses a mac) the first command prompt continues to "loop" until you hit CRTL + C and on mine as soon as did the command in "prompt 2" the loop stopped on its own although all of the commands still worked as planned. I was doing this on Windows7 32bit. Hopefully that makes sense or is helpful to someone...
all you had to do was kill, then restart adb? that's not doing the trick for me, damn
EDIT: I got mine to work by uninstalling HTC Sync, it has an adb.exe file that was causing the error
I was able to leave HTC Sync installed but I had to uninstall Droid Explorer from my Incredible days. Only then did the ADB out of date error stop.
I used this before with HTC Sync. Maybe that is why I was able to keep it installed.
The attached zip is from http://visualgdb.com/adbfix/
Related
So I've been trying to root my thunderbolt for about a week with no success.
At first I used the method here: http://forum.xda-developers.com/showthread.php?t=1005292
It has continually failed on step 2, tried on different computer also. No luck.
I gave up on rooting it for a few days/
Since the first step went through I am downgraded, running 1.03.605. It's got quite a few bugs and when I try to software update from the phone nothing is found. All I really wanted was to get it to the current firmware to fix connectivity bugs but after searching high and low I still have no idea how to/if it is possible.
I assumed I may have to just root it at this point, so I gave the manual root on theMikMik a shot. While setting up my ABD everything runs smooth until I try to enter commands into abd. I get permissions denied, every time. I've tried looking for an answer to this with no luck. Guide I used found here: http://www.themikmik.com/forums/viewtopic.php?f=66&t=256
So my main question, is there any way to get the latest firmware onto my phone without rooting? I've tried downloading an update, naming it update.zip then updating from bootloader with no luck.
If not, what the hell am I doing wrong that is denying me permission in ABD. I've turned anti-virus off, rebooted etc.
assuming adb is properly set up (drivers working), you've checked Debugging and unchecked Fastboot (under setting->apps->dev), plugged the phone into your computer, and typing "adb devices" acknowledges your phone is connected, and you are in fact on the downgrade as you said you were. Make sure PG05IMG.zip is removed from your sdcard then...
Go here and start at step 5: http://forum.xda-developers.com/showthread.php?t=996616
You were getting permission denied errors with those adb commands on mikmik because you are not rooted yet hence the "rooted evo" under requirements.
Edit:
While that may should work, I believe you could start from the beginning with Step 1 using the link I just posted as well. Just don't flash the old firmware (1.0.3.605 that you currently have) after you go through that for any reason (see: http://forum.xda-developers.com/showthread.php?t=1008824).
Absolute_Zero said:
assuming adb is properly set up (drivers working), you've checked Debugging and unchecked Fastboot (under setting->apps->dev), plugged the phone into your computer, and typing "adb devices" acknowledges your phone is connected, and you are in fact on the downgrade as you said you were. Make sure PG05IMG.zip is removed from your sdcard then...
Go here and start at step 5: http://forum.xda-developers.com/showthread.php?t=996616
You were getting permission denied errors with those adb commands on mikmik because you are not rooted yet hence the "rooted evo" under requirements.
Click to expand...
Click to collapse
*Facepalm*
So I tried what you said from that guide, step 5 failed for me. So I tried from the beginning...still failed.
So, I decided to record it and hopefully you can tell me what I'm doing wrong.
Link: http://www.youtube.com/watch?v=o2AFZEIVIio
Figured that'd be a better way to get the help I need with less reading on your part.
Sorry, I was commuting home from work.
According to the output of "adb shell" you're either already rooted or psneuter has already been run since boot. (note the "#" output instead of "$").
There's no reason to run psneuter to gain permroot again. So once you see that pound sign, start from a two steps down where it says "/data/local/busybox md5sum /data/local/misc.img". IOW, skip that particular "/data/local/psneuter" step.
And I would highly recommend that if you are going to copy/paste, only copy one line at a time to prevent errors.
Off to grab dinner. I'll check back later when I can but hopefully you will be good from here on out.
Edit:
I'm perfectly happy with walking you through it (and I believe you should be fine after this post anyway) but if you still wanted to use that easyroot method that you started with you might want to read this if you haven't http://bit.ly/qsvOkN. I didn't use that easyroot method but it looks like if a step fails, people just run it again until it works. /shrug
I like adb and people should know how to use it anyway.
Hi, I just purchased the new LG myTouch (all myTouches are now made by LG) from tmobile and I have been trying to root it with no luck. I have been trying to use superoneclick but it always gets to step 7 and stops working. I made sure my SD card is unmounted, the phone has USB debugging turned on, I have tried the pdanet method, and I tried unplugging and replugging the USB cord but it always stops on step 7. The phone has android 2.3.4 but I have seen other threads where people with 2.3.4 got their phones rooted so why can't I? Any ideas?
Sorry if I'm posting this in the wrong place but there is no forum dedicated to this phone. I'm guessing because it just came out this month.
i just got the Q for my girl, i was wondering the same, just to remove the bloat. can someone please point me to the right direction?
Just checking in to see if anyone has found any answers.
Network24 said:
Hi, I just purchased the new LG myTouch (all myTouches are now made by LG) from tmobile and I have been trying to root it with no luck. I have been trying to use superoneclick but it always gets to step 7 and stops working. I made sure my SD card is unmounted, the phone has USB debugging turned on, I have tried the pdanet method, and I tried unplugging and replugging the USB cord but it always stops on step 7. The phone has android 2.3.4 but I have seen other threads where people with 2.3.4 got their phones rooted so why can't I? Any ideas?
Sorry if I'm posting this in the wrong place but there is no forum dedicated to this phone. I'm guessing because it just came out this month.
Click to expand...
Click to collapse
where can i find these threads? can you point me to it... maybe i can try and find something, or do something different and help out with solving it.
EDIT: did these threads say for the MTQ or was it just a thread for a random 2.3.4 device?
The threads I saw were just for a random 2.3.4 device. I saw another thread on xda with someone trying to root this phone but just like this thread no one is answering.
Has anyone found any methods to root this phone?
Success!
After several attempts to root via SuperOneClick 2.2, I tried something totally random from another LG rooting thread that seems to have worked. Install ADB, then do:
WINDOWS> adb shell
$ echo 1 > /data/local/lge_adb.conf
$ exit
Then run SuperOneClick 2.2 and it should root properly.
I will have to give this a try on one of my Windows PC's. Linux and SuperOneClick are not playing nice together right now.
+1
Good Job Man....Worked for me. Have root and superuser.
Ditto! Root, & Superuser
== Instructions that worked for me ==
- Download myTouch Q drivers (Search "mytouch Q usb drivers" - Can't post links yet! XD )
- Check that adb recognizes device: C:\> adb devices
- Follow eamondaly's instructions:
WINDOWS> adb shell
$ echo 1 > /data/local/lge_adb.conf
$ exit
Click to expand...
Click to collapse
- Run SuperOneClick v2.2
- Wait for phone to reboot (SuperOneClick seems to be paused)
- Reset USB debugging (mine was turned off after reboot)
- Wait for SuperOneClick to finish.
- Enjoy rooted phone
Thanks
Okay thanks for the root methods greatly appreciated but now I am starting to get into developing anyone can teach me how to make a system dump to try and make my own roms I am a fast learner ort at least point me in right direction thanks again
Im not shure if im doing something wrong, i had better luck rooting an xperia play, a Droid X, and a htc mytouch, but this lg mytouch wont go for me. I tryed runing adb, i know how to use, was doing a little programming with it and eclipse. Anyhow, typed everything in and this is what my cmd shell looked like...
C:\ADB>adb shell
$ echo 1> /data/local/lge_adb.conf
echo 1> /data/local/lge_adb.conf
$ exit
exit
Then i tryed running superoneclick , tryed root and shell root, neither seem to work, it goes threw some and then hangs. my phone disconnects and reconects, thats it though. i checked in terminal, typed su, access is denied. i tryed it with debugging on and off, sd mounted and not.
Any ideas or tips. im using windows vista.
DMOYER said:
Im not shure if im doing something wrong, i had better luck rooting an xperia play, a Droid X, and a htc mytouch, but this lg mytouch wont go for me. I tryed runing adb, i know how to use, was doing a little programming with it and eclipse. Anyhow, typed everything in and this is what my cmd shell looked like...
C:\ADB>adb shell
$ echo 1> /data/local/lge_adb.conf
echo 1> /data/local/lge_adb.conf
$ exit
exit
Then i tryed running superoneclick , tryed root and shell root, neither seem to work, it goes threw some and then hangs. my phone disconnects and reconects, thats it though. i checked in terminal, typed su, access is denied. i tryed it with debugging on and off, sd mounted and not.
Any ideas or tips. im using windows vista.
Click to expand...
Click to collapse
you are running under admin right I know silly question but had to as lol
Thanks eamondaly
I just want to thank eamondaly for this method. I just ran superoneclick 2.3.1 and it worked perfectly. I don't know if it was your method that worked or if superoneclick 2.3.1 fixed it but all that matters is my phone is now rooted. Thanks.
Thanks a lot for the root method, I've been waiting patiently for this. Now can we get to making mods for this phone now?
Edit: Anyone having trouble sending/receiving MMS messages? I cant seem to send or receive them.
I was having an issue with receiving MMS on both my wife's and my phone. Ditching the stock messaging client and downloading Handcent resolved it for both.
Switching MMS apps didn't work. Tried a number of countless APN setups. I just decided to unroot and factory reset. Everything is working again.
titanium pro back up image
hey all,
Im sure this is a random spot for this but, since we dont have a home yet.
Im looking for a stock back up image (Titanium backup pro)with all apps and system settings. I think I may have cleared out a system file or two when cleaning out all the Tmo bloat.
Any help or other suggestions would be great.
I found another way to root easily. http://www.unlockroot.com download, install and click root. I had issues with superoneclick and the adb method but this gave me full root with superuser and now I am happy that all the t-mobile crapware is gone
I'm trying to root my T-Mobile MyTouch Q and not having any luck. It's Android 2.3.6, but I tried running "echo 1 > /data/local/lge_adb.conf" and I get a permission denied error. I tried SuperOneClick version 2.2 and 2.3.3. SuperOneClick gets to step 7 than hangs and nothing happens. It says waiting for device. I also tried Unlock Root and it fails to get shell root. I searched all over google and the xda forums, but all say to run that command then run SuperOneClick and that hasn't worked for me. Anyone have any ideas?
Hello all!
I'm trying to root my HTC Legend using Chirag's manual.
I somehow managed to complete all steps until step 4 (that is, flashing the rooted rom), but now i'm stuck.
I but the phone in fastboot mode, plug it to my computer, and the phone says "fastboot USB". When i run 'step1-windows.bat', nothing happens, i get the message:
"Legend Root Step 1
Erasing cache and rebooting in RUU mode...
<waiting for device>"
And that is all. Any ideas? It would be pretty lousy to go through all those steps, including downloading and losing all apps not to be able to finish the very last step...
--edit--
I do have superuser "app" in the drawer of my legend. Don't know if it's important...
Ok, so my PC doesn't see the legend when in FASTBOOT mode, "adb devices" returns an empty list. When the phone is on, and normal, i see it with adb services.
Okay, made it past step one. I turned off HTCSync, and the PdaNet, which i installed earlier (i was that desperate). Nothing seemed to work. I then entered FASTBOOT mode, plugged it into the PC, and then in control panel went to 'devices', found 'Android 1.0 devices' and installed the drivers automatically. The moment i did that, step one started to work, and finished in about couple of minutes.
Just in case someone else gets this problem, this is the solution.
Now starting step 2, i hope it will succeed.
--edit--
Yesss!!! It worked like a charm, i now (finally) have rooted 2.1 with sense
Sorry for talking to myself, but i wanted to share the solution, i usually get pissed when someone solves his problems and doesn't share
Nah Your all right with me, its good to see you managed to get it fixed on your own. I think all the guides need to be updated with that information regarding the need for android 1.0 drivers as it seams to be THE most common issue when not being able to get through the rooting steps.
Enjoy and have fun!
Sent from my HTC Legend using XDA App
I've got an Iconia tablet with a broken recovery (I've been using CWM and Thor's ICS ROM). I'm going to follow the steps outlined here
http://forum.xda-developers.com/showthread.php?t=1129873
but.... when I look up the UID from every method, all I get is 0123456789ABCDEF.
Given all the dire warnings about not being able to recover if/when things go wrong without the real UID... this 123 UID isn't the real UID.... is it safe to proceed with the repair here? Or are things really messed up?
I have not messed with ICS myself, but my understanding from reading the ICS threads in the Iconia forums is that the device is no longer using the uid for usb serial number. So it seems you can't get it that way if you have installed any of the ICS updates.
The suggestion I have seen is to look for androidboot.serialno in dmesg directly after booting, but that does not seem to help everyone.
Another option might be to get the device into APX mode and do a usb bulk read, the first read should return 8 bytes that is the UID. I would assume this to still work even after you have installed ICS but I have not tried. I pasted some code for opening the device, reading and printing the uid (using libusb, tested on Linux) on the Iconia forum earlier this week.
Hmm OK that's helpful info. Thanks.
I tried the androidboot.serialno in dmesg, but I wasn't able to find the string.... I will try that again after a clean boot.
I've been doing all the debugging from my one Windows machine... I haven't tried plugging it into my Linux PC yet... that's next... I haven't discovered APX mode yet. Time to do some more reading, thanks for the pointers.
Edit 1: OK checked lsusb -v and I serial also shows 0123456789ABCDEF
Edit 2: Clean boot and did a new dmesg dump.. parsed the output and no sign of androidboot.serialno or anything that even resembles it.
OK, things are not getting better here. I've been tinkering a lot, and in some respect I've just made things worse.
I still cannot find the UID with any of the documented methods here on XDA. I've tried
using adb devices
using Linux lsusb -v
checking the output of dmesg for androidboot.serialno
plugging in to Windows and looking at the USB mount info using USBDeview
looking at the device manager in Windows and checking the "Parent" field
I have also booted into APX mode and to discover the UID that way too... and nothing.
All I get is 0123456789ABCDEF
At this point the frustration level was getting high enough for me to be a bit reckless... I copied "itsmagic" into /data made it executable and ran it. No errors.
I rebooted into Recovery mode, and there I get scrambled graphics on the screen (it's the Acer logo duplicated several times with loads of tearing and distortion) and the tablet vibrates constantly.. non stop until I reboot it.
I can boot normally into the current ROM (Thor2002ro v96) so I haven't busted it completely. If I try to use my existing CWM manager to install any other ROM or use the manager to reboot into recovery mode, it goes back to the scrambled screen and vibrating constantly.
Does anyone have any ideas or suggestions here? I'd be happy to even roll back to stock and start fresh. There is nothing on the tablet that needs to be saved... except the functionality of the tablet itself.
When you write nothing about APX mode, does that mean literary nothing or nothing different?
If you have root you can see if you have anything interesting in /proc/cmdline.
If not I'm out of ideas on how the get the UID for now.
While i very much doubt 0x0123456789ABCDEF is the UID used to generate the SBK of the device you could try reading and decrypting the beginning of mmcblk0 using the SBK that would give (0xA9EA7E00 0xF12BEB06 0x3AD20804 0x364A5F03) to verify this.
You could probably overwrite the restore partition from your running system, I have never done that myself though.
OK, it's SOLVED.
After much swearing and crying and a little help from the forum here and in other posts the solution to fixing the broken tablet was actually quite easy.
Based on the information here:
http://forum.xda-developers.com/showthread.php?t=1459821
- I downloaded recovery-ra-iconia-3.16-gnm.img using teh links provided on the thread above
- I ran itsmagic
- Then I did these steps:
Code:
adb push recovery-ra-iconia-3.16-gnm.img /mnt/sdcard
adb shell
su
dd if=/mnt/sdcard/recovery-ra-iconia-3.16-gnm.img of=/dev/block/mmcblk0p1
sync
reboot recovery
This booted a working recovery mode (FINALLY), and I was able to successfully flash the latest Thor2002ro ICS ROM.
Thanks for your help and suggestions eppeP, they got me thinking in the right direction.
Hello guys I am trying to bypass screen lock via adb but when I write adb devices it shows "0123456789ABCDEF Device" and then when I type adb shell then it shows"$" after that whatever I type it shows permission denied(even if I write adb).Please Help
please clear up Google
account lock
Hello guys, first i hope it's in the right place to post this and second sorry for my english.
And also thx for many tips i got from here on my road to get this working. But now i don't know what to do.
(Win 7 Starter 32bit, Android Debug Bridge version 1.0.31)
My situation: had a S3 (I9300) with Android 4.3 and a broken screen. Touch is still working. The broken screen wasn't a problem at first, because as it fell down, the screen was all right. After about 15 min it started to get black at the top. But most of the screen was ok. After the night everything was black.
So i read about droidatscreen and started to root and play with the device. First i put CF-Root-SGS3-v6.4 with Odin on the phone and then started to try to make adb work under Android.
I was in recovery and add this line to the build.prop "persist.service.adb.enable=1" .
I'm not sure, but i think after a reboot of the phone i had adb running under Android. At this time adb said not authorized and the window with the confirmation for usb debugging wasn't popping out (because i tried and tried to touch at the place where it shold be).
Than i read about "persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=mtp,adb" adding to default and build.prop , also didn't work.
Than i added "ro.adb.secure=0" and changed "ro.adb.qemud=1" to 0 in both files, and after rebooting the phone i hit the place on the screen and adb devices went from unauthorized to device. I finally made it and could use droidatscreen. (i don't think that ro.adb.secure=0 deactivated the rsa fingerprint, but i think it got it to pop up the confirmation window).
Now i was able to see the menue, i changed some things in options, like touch sound and screen unlock sound to be able to hear the things i couldn't see, i also changed the setting for showing touches in the dev menue.
And now the bad thing happened, i touched the option usb debugging (not on the check, but on the word itself (i could see it because of the latency of droidatscreen and the phone rebooted and wasn't able to connect to adb).
Now i only get the mtp device and adb devices shows nothing but a blank line.
I'm still able to change build.prop and other data in recovery but even load the original files to the phone and going step by step further didn't bring me the unauthorized message in adb devices.
I hope someone could help me. Maybe someone knows the files which are changed during changing the options in Android menue.
Btw. i already wiped cache, but do not want to do more than this (i mean wiping ).
Thx
Edit:
Solved the problem.
Found out about the getprop and setprop commands and used getprop in adb shell. Didn't found anything like "persist.service.adb.enable" ... , only something like
[service.adb.root]: [1] [ro.adb.qemud]: [1] and [persist.sys.usb.config]: [mtp] .
Searched in /data/property for adb things, and saw "persist.service.adb.enable" "persist.sys.usb.config" .
"getprop persist.service.adb.enable" showed a blank line, so i "setprop persist.service.adb.enable 1",
now "getprop persist.service.adb.enable" showed a 1 and after rebooting phone, i was able to get a unauthorized message from adb devices, and reconneting the usb let the confirmation popup.
Thx anyways.