[Q] Bootloader unlock help. - Droid RAZR M Q&A, Help & Troubleshooting

So, since the new root method is out, and motopocalypse works again, I thought it'd be good to unlock it while possible. So I got the drivers reinstalled, rooted, installed supersu, checked for root (verified), turned on USB debugging, and started the program. I hit enter and it says
*waiting for device
*starting daemon on port 5***
*daemon started successfully
It says nothing after that. Even after minutes. The driver are installed correctly, root works fine, I have my original cable but I just don't know what to do. Any help would be appreciated. Thanks.
Sent from my XT907 using xda app-developers app

poppers162 said:
So, since the new root method is out, and motopocalypse works again, I thought it'd be good to unlock it while possible. So I got the drivers reinstalled, rooted, installed supersu, checked for root (verified), turned on USB debugging, and started the program. I hit enter and it says
*waiting for device
*starting daemon on port 5***
*daemon started successfully
It says nothing after that. Even after minutes. The driver are installed correctly, root works fine, I have my original cable but I just don't know what to do. Any help would be appreciated. Thanks.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
ADB will send a prompt to your phone, you'll need to except it. Just use the apk instead, it's easier.

ATTACK said:
ADB will send a prompt to your phone, you'll need to except it. Just use the apk instead, it's easier.
Click to expand...
Click to collapse
I found the app last night, it's unlocked now, thanks.
Sent from my XT907 using xda app-developers app

Related

[Q] Stuck at AT&T Logo

Hey all,
My Atrix is rooted and has been running fine until as of late. While trying to reboot the device, it gets pass the Moto logo but hangs on the very lovely AT&T "Rethink Possible" logo. I don't think my situation is considered a 'soft brick' but I still tried norcal einstein's soft brick recovery in attempt to remedy my cause. Unfortunately, SuperOneClick can't even access the ADB shell for the soft brick recovery to work.
Does this sound like a SuperOneClick issue or an ADB Shell issue?
Anyone have any clues? Thanks in advance.
Anyone? After further troubleshooting, I have discovered that while plugged via usb to PC, I cannot access internal or external SD. Yikes.
have you try taking out the battery on the back and reset it that way?
motoatrix said:
have you try taking out the battery on the back and reset it that way?
Click to expand...
Click to collapse
Yes. After about 15 attempts, I finally got pass the ATT logo screen. However, once I reboot, it's deja vu.
Thanks.
djdino said:
Yes. After about 15 attempts, I finally got pass the ATT logo screen. However, once I reboot, it's deja vu.
Thanks.
Click to expand...
Click to collapse
Did you by chance freeze your launcher screen? Is this one of the deodexed rom's (like we have many)? Did you install a piece of software prior to this happening?
DarrellRaines said:
Did you by chance freeze your launcher screen? Is this one of the deodexed rom's (like we have many)? Did you install a piece of software prior to this happening?
Click to expand...
Click to collapse
Only Stock rom. I did install ADW Launcher but that should be okay right? I'm about to just do a factory reset.
I am also more concern about getting SuperOneClick working. It just freezes on 'waiting for device'. I cannot access ADB to make any changes. I have the right drivers because the Motorola Portal pops when I plug the device via USB.
Thanks guys!
djdino said:
Only Stock rom. I did install ADW Launcher but that should be okay right? I'm about to just do a factory reset.
I am also more concern about getting SuperOneClick working. It just freezes on 'waiting for device'. I cannot access ADB to make any changes. I have the right drivers because the Motorola Portal pops when I plug the device via USB.
Thanks guys!
Click to expand...
Click to collapse
Definatly restore and see if that works
Sent from my MB860 using XDA App
Okay, I just did a restore. It boots up fine. However, I stil cannot get SuperOneClick to recognize my device. I'm getting the infamous "waiting for device". I have Debuggin enabled and dismounted internal and external SDcard. Even when I don't have the device plugged in, SuperOneClick still freezes. I've tried 1.6.3 and 1.7.0 versions.
I'm running Win7 32Bit Enterprise and even tried on my XP Pro machine and still the same result. Yikes.
Thanks guys.
djdino said:
Okay, I just did a restore. It boots up fine. However, I stil cannot get SuperOneClick to recognize my device. I'm getting the infamous "waiting for device". I have Debuggin enabled and dismounted internal and external SDcard. Even when I don't have the device plugged in, SuperOneClick still freezes. I've tried 1.6.3 and 1.7.0 versions.
I'm running Win7 32Bit Enterprise and even tried on my XP Pro machine and still the same result. Yikes.
Thanks guys.
Click to expand...
Click to collapse
Have you tried reinstalling the drivers?
Sent from my MB860 using XDA App
DarrellRaines said:
Have you tried reinstalling the drivers?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Yes I have sir. I even tried on a difference PC that never had the drivers installed.
Try another usb cable. Might be a bad cable, or could even be a port.
Sent from my MB860 using XDA App
DarrellRaines said:
Try another usb cable. Might be a bad cable, or could even be a port.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Thanks! I just tried that. I have 3 different cables and different usb ports. Could the problem be pointed back at SuperOneClick?? Even without the cable, it just 'waiting for device'. Not even an error message feedback.
I don't think so. It possible, but at this point I would just warranty it and try a new one.
Sent from my MB860 using XDA App
Unroot if you used superoneclick. Atrix already has busybox and superoneclick installs it again. DG recommends adopt to root your Atrix
Sent from my MB860 using XDA App
rjayflo said:
Unroot if you used superoneclick. Atrix already has busybox and superoneclick installs it again. DG recommends adopt to root your Atrix
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
How could I unroot if SOC can't even recognize the device? Thanks.

My nexus won't root!

I've tried eveything, the Nexus toolbox, ADB, and even Chainfire's auto root. I've managed to unlock my bootloader, but whenever it comes to rooting (depending on which way I try to root) the command prompt will stay at "Downloading boot.img" or "Sending Recovery (7806 kb)" until i either reboot my Nexus or close cmd. How can i root this damn device? I'm going insane! Thank you!
AW: My nexus won't root!
Did you tried Wugs nexus root toolkit? Of not try it, you can't do something wrong it's sooo easy!
http://forum.xda-developers.com/showthread.php?t=2015469
Tell me if it worked or not
Swyped from my beast the Nexus 4
Fast boot devices , check if a device comes up
Sent from my Nexus 4 using Tapatalk 2
miniAndroidian said:
Did you tried Wigs nexus root toolkit? Of not try it, you can't do something wrong it's sooo easy!
http://forum.xda-developers.com/showthread.php?t=2015469
Tell me if it worked or not
Swyped from my beast the Nexus 4
Click to expand...
Click to collapse
Thank you. But it still sticks on "Booting modified boot.img to enable running privileged commands..."
I've just noticed that My Computer/Windows Explorer isn't showing my Nexus when its connected as MTP. Could that be the problem? And if so, do you know how to fix it? thanks.
okmijnlp said:
Thank you. But it still sticks on "Booting modified boot.img to enable running privileged commands..."
I've just noticed that My Computer/Windows Explorer isn't showing my Nexus when its connected as MTP. Could that be the problem? And if so, do you know how to fix it? thanks.
Click to expand...
Click to collapse
Try doing the whole process again from step one using the toolkit and install that will guide you step by step in installing the proper drivers and such. I usually do everything manually but I went into lazy mode and did everything just fine and with little time as well. :good:
UZ7 said:
Try doing the whole process again from step one using the toolkit and install that will guide you step by step in installing the proper drivers and such. I usually do everything manually but I went into lazy mode and did everything just fine and with little time as well. :good:
Click to expand...
Click to collapse
Thanks but I've even done that 3 times now. uninstalling & reinstalling drivers, unlocking & relocking. still, the sae problem persists :crying:
Try a new USB cord and port. Make sure USB debugging is on
Sent from my SPH-D710 using xda premium
Go to androidrootz.com and try his method. Worked for me on a Mac and I am not very computer savy. He also has windows version for rooting.
Ian B
Censura_Umbra said:
Try a new USB cord and port. Make sure USB debugging is on
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
+1 I'm betting usb debugging not turned on again after you unlocked bootloader.
clockcycle said:
+1 I'm betting usb debugging not turned on again after you unlocked bootloader.
Click to expand...
Click to collapse
Usb debugging is on .
Sent from my GT-I9100 using xda app-developers app
It's a long process but i ended up having to use a Linux virtual machine (luckily i had one for work anyway).
No matter what toolkit or manual step to install drivers, i couldn't get Win7 to detect the phone, however, attaching it in VmWare to an Ubuntu guest system worked straight away. I got the adb/fastboot files by following instructions in a thread here on XDA and was rooted in minutes
May be worth a shot
Toolkits are a waste of space. Do it manually, it's only like four steps and you will see exactly what is happening and where (if anywhere) you're going wrong.

Kingo Root fails repeatedly. HELP!!!!!

Had root on Mj7. Rumning Beans 4.
Odined back to MJ7-went perfectly.
Factory restored the phone.
Took the new UPDATE.
Now on MJE
Installed and opened Kingo.
Gave USB permission.
Kingo runs, and FAILS. Says NOSUPPORT.
I've tried 5 times....FAILS!!
I'm beside myself!!!
I can't lose the ability to root, I just cant. I cannot stand an unrooted phone.
PLEASE HELP!!! :crying::crying::crying::crying::crying::crying:
Nidisa said:
Had root on Mj7. Rumning Beans 4.
Odined back to MJ7-went perfectly.
Factory restored the phone.
Installed and opened Kingo.
Gave USB permission.
Kingo runs, and FAILS. Says NOSUPPORT.
I've tried 5 times....FAILS!!
I'm beside myself!!!
I can't lose the ability to root, I just cant. I cannot stand an unrooted phone.
PLEASE HELP!!! :crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
make sure you don't have an antivirus running, make sure you phone is on debug mode, try a different usb port, set you display timeout to 10 minutes and last but not least select always accept when it prompts you on your phone for access
Try a different USB port or if not a cable. It happened to me too and my computer wouldn't recognized my phone even when I have all the drivers installed. Nothing to worry about.
Sent from my SM-N900V using XDA Premium 4 mobile app
Nidisa said:
Had root on Mj7. Rumning Beans 4.
Odined back to MJ7-went perfectly.
Factory restored the phone.
Took the new UPDATE.
Now on MJE
Installed and opened Kingo.
Gave USB permission.
Kingo runs, and FAILS. Says NOSUPPORT.
I've tried 5 times....FAILS!!
I'm beside myself!!!
I can't lose the ability to root, I just cant. I cannot stand an unrooted phone.
PLEASE HELP!!! :crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
You sure you reenabled Developer Options and USB debugging? After the update you will need to do that. Also is Kingo recognizing your device is connected?
Sent from my SM-N900V using Tapatalk
All is well. Phone was always recognized by the computer. I shut off virus protection and it worked! !
I am rooted again and all is right with the world
Thank you for all the help!
Sent from my SM-N900V using xda app-developers app
Nidisa said:
All is well. Phone was always recognized by the computer. I shut off virus protection and it worked! !
I am rooted again and all is right with the world
Thank you for all the help!
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
What if it turns out that your anti-virus program is reporting correctly that Kingo is a virus?
I scanned the kingo app, then turned off virus scanner n the installed kingo!
I'm a careful girl
Sent from my SM-N900V using xda app-developers app

LG G2 Root Access Error using TheCubed's IORoot

TheCubed LG G2 Root Thread: http://forum.xda-developers.com/show....php?t=2448887
In the CMD I get an error while rooting my LG G2 (AT&T).
~See Attatchment for CMD error screenshot~
Can anyone help me fix/troubleshoot this error?
probably usb debugging needs to be on.
Sent from my g2 using xda app-developers app
Make sure you have USB debugging on.
If it's the VZW variant, when you connect it to the PC, make sure you connect it via Ethernet.
Again for VZW variant, when you plug it in, your computer will prompt you for an action with the phone. I found that connecting with LG's software was the trick in allowing you the computer to communicate with the phone (at least for me).
I think this happened because you ignored/didn't see the step about unplugging the device and plugging it back in when the program tells you to. Just re-do the root and read the steps in the program carefully. You have done everything else correct, De-bugging is on and you have chosen the right connection mode, otherwise the program would not have been able to even start rooting your device, as it wouldn't see it. So it must just be the unplug part you missed, just try again :good:
Will retry and get back to you guys. Thanks for the tips!
Sent from my LG-D800 using xda app-developers app
After trying a few tries and getting the same results, I've made no progress. Same error each time.
Sent from my LG-D800 using xda app-developers app
Stupid question but have you checked your root status?
I'm actually getting the same error. Im on T-Mobile variant. I did not unplug the first time so I redid 8more xs following the procedure the right way with no avail. I did a soft reset and a hard reset attempted again and still nothing...it does install superuser though
Exactly! Superuser is installed but i don't have root access.
Sent from my LG-D800 using xda app-developers app
Villisca said:
TheCubed LG G2 Root Thread: http://forum.xda-developers.com/show....php?t=2448887
In the CMD I get an error while rooting my LG G2 (AT&T).
~See Attatchment for CMD error screenshot~
Can anyone help me fix/troubleshoot this error?
Click to expand...
Click to collapse
Does anyone know of any other methods to root the LG G2?
I keep getting the same error as well
It would install superuser but would not root the phone
I uninstalled superuser and redid the process multiple times, but getting the same thing
I finally downloaded vroot and used that to root my G2
it worked like a charm. the program does everything for you. just plug the phone and run vroot
first post so I can't post links haha
Vroot worked flawlessly despite being in chinese. i had no trouble getting it to work. I was rooted in less than 3 minutes
Sent from my LG-D800 using xda app-developers app
glad it worked for you as well

Help! Root gone bad!

So, I installed Kingo 1.2.2.1915, installed Samsung drivers, and Kingo would not root the device, it kept saying USB debugging was off, and I verified several times it was on. So I went the Vroot method and it rooted in 3 seconds (seriously). I was surprised it went so fast. I was able to install Safestrap successfully, but after I rebooted (and can see Safestrap recovery on reboot), the phone no longer has root. I tried rooting again using either Kingo or Vroot, now neither app will detect my device. They both behave like USB debugging is off, but it's clearly on. Otherwise, the device works fine. Any thoughts?
Sent from my SM-N900V using xda app-developers app
sixtoedgunmonkey said:
So, I installed Kingo 1.2.2.1915, installed Samsung drivers, and Kingo would not root the device, it kept saying USB debugging was off, and I verified several times it was on. So I went the Vroot method and it rooted in 3 seconds (seriously). I was surprised it went so fast. I was able to install Safestrap successfully, but after I rebooted (and can see Safestrap recovery on reboot), the phone no longer has root. I tried rooting again using either Kingo or Vroot, now neither app will detect my device. They both behave like USB debugging is off, but it's clearly on. Otherwise, the device works fine. Any thoughts?
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
Try downloading Chainfires flashable supersu zip from here and install it in safestrap.
Thanks! Worked like a champ!
Sent from my SM-N900V using xda app-developers app

Categories

Resources