Figured out my Problem Thanks.
For aRoot, I just kept fiddling every day for like 3 days, and it finally worked randomly. Just the combination of debugging and which connection, and the order leading up to it toggled.
boman311 said:
I have a Atrix and when i plug it in it loads all the drivers and everything. I am able to Flash the stock SBF but i cannot load adeo, gingerblur, or use Superroot or aroot. I have installed the proper drivers and I installed the Android SDK. I am on the newer side to hacking android phones but have lots of hacking experience and just cannot figure this one out. Please anyone help.
Click to expand...
Click to collapse
Have you enabled usb debugging? Its under settings applications development. did you make sure your phone is set to none under the the usb connection? Lastly did you run the adb prior to the install? Make sure all of those are done...i have limited knowledge myself but hopefully this helps.
Edit: just curious why did you need to flash sbf if you were unable to do anything you mentioned?
Sent from my MB860 using Tapatalk
I have tried fiddling with gingerblur adeo superroot and aroot for days. I even exchanged my phone once and tried it on 3 computers. Still no luck. It has to be something i am missing or doing wrong. Superroot says it is waiting for device then freezes. aRoot and Gingerblur will says "achieving temporary root then scroll through a whole bunch of stuff and then says rebooting." and the phone never does anything at all.
BBock9 said:
Have you enabled usb debugging? Its under settings applications development. did you make sure your phone is set to none under the the usb connection? Lastly did you run the adb prior to the install? Make sure all of those are done...i have limited knowledge myself but hopefully this helps.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
\
I have enabled usb debugging and i think adb is running do i have to do something special to make it run?
Not sure, when I used aRoot I didn't use adb.
boman311 said:
\
I have enabled usb debugging and i think adb is running do i have to do something special to make it run?
Click to expand...
Click to collapse
I run a windows box and in the files that are downloaded for aroot there is an adb file...i just doubled clicked it prior to the install file.
Sent from my MB860 using Tapatalk
Just click on the file you downloaded. I think it was Run aRoot.
Just starts the dialog for you.
BBock9 said:
I run a windows box and in the files that are downloaded for aroot there is an adb file...i just doubled clicked it prior to the install file.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
I tried this and still no luck. I just did it. I tried to run Gingerblur and it asked me all the questions in red then rushed through all these yellow commands but still nothing on the phone. Please i am desperate
are you sure you are extracting these files out? and not trying to run them from their zip/7z archives?
boman311 said:
I have a Atrix and when i plug it in it loads all the drivers and everything. I am able to Flash the stock SBF but i cannot load adeo, gingerblur, or use Superroot or aroot. I have installed the proper drivers and I installed the Android SDK. I am on the newer side to hacking android phones but have lots of hacking experience and just cannot figure this one out. Please anyone help.
Click to expand...
Click to collapse
Yeah, there is something fiddly about achieving root first... once you achieve it, shell root is a breeze.
I had to fiddle with it for a while. Had to do with toggling debugging at the right moment during the root process. Don't remember when, but one of the longer steps. Presumably at or right before it freezes for you. Try toggling off -> on (or on -> off and back).
Connection mode needs to be "None", after you ran through all the connection modes, so your PC has all the necessary drivers installed.
Related
I'm in the process of flashing the SBF to my atrix, the 1.2.6 or whatever. Well does it matter what I use to root the phone with once its back on stock? I like to use superoneclick. will that work with the after and before update bat files? I can never get aRoot to work for me.
macperson123 said:
I'm in the process of flashing the SBF to my atrix, the 1.2.6 or whatever. Well does it matter what I use to root the phone with once its back on stock? I like to use superoneclick. will that work with the after and before update bat files? I can never get aRoot to work for me.
Click to expand...
Click to collapse
Well I was in the same boat as you. When using aRoot, the trick is to keep it in a folder directly under C: drive. Like c:/aRoot/
Then make sure your phone has usb de bugging turned on and usb set to none.
Run aRoot as administrator. It should do it.
Sent from my Atrix using XDA Premium App.
Okay! Thanks. I'll try that
Thanks, it worked! They should include fixes for this right in the original instructions! haha
Where do I place the mod files for the retain update thing? Its not working for me.. It says that it can't find the device over ADB.. I have USB debugging on and USB none.
So I rooted my Evo successfully as well as the Evo of one of my good friends. However, a second friend of mine wanted his new Evo rooted so I naturally obliged. However, his phone repeatedly gave me the finger when I tried to root it. Here is what happened:
1. Executed root script via THIS METHOD
2. Script began rooting.
3. Script entered first phone restart phase.
4. Script entered second phone restart phase.
5. When phone turned back on my laptop no longer recognized he device (i.e. Android 1.0 in Device Manager) and so the script could not continue its process.
My attempted solutions:
1. Reset to factory settings and reattempt to root. (Failed)
2. Reset to factory settings and attempted to root using RegawMOD (Failed)
3. Did not try to RUU as I did not have the RUU necessary for his device.
My question here is this....if I RUU his device and reattempt the root is it likely that I will encounter the same issue as I did initially? I do not know whether this was an issue of the rooting process or an issue with the drivers on my laptop. My powers of deduction tell me it is based within the phone since immediately after his phone was unrecognized I was able to plug my phone in, as well as my other friend's Evo, and have my laptop recognize both devices instantly.
Cliff Notes:
My Evo: Rooted Successfully
Friend #1's Evo: Rooted Successfully
Friend #2's Evo: Root Unsuccessful
Personally I would just HTCDev unlock his phone and flash TWRP...then download whatever rom (even the rooted stock if he wants to stay 100% stock) and flash it. Best way to root imho. Hasn't failed me yet!
I would try re updating the htc drivers for your pc
Sent from my EVO using Tapatalk
bhint15 said:
Personally I would just HTCDev unlock his phone and flash TWRP...then download whatever rom (even the rooted stock if he wants to stay 100% stock) and flash it. Best way to root imho. Hasn't failed me yet!
Click to expand...
Click to collapse
RagawMOD root uses the htcDev method. It failed as I stated in the original post.
thicklizard said:
I would try re updating the htc drivers for your pc
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
I updated my drivers like 10 times. Plus, like I said, my phone a well as my other friend's phone works just fine.
Sent from my EVO using XDA
Concordium said:
RagawMOD root uses the htcDev method. It failed as I stated in the original post.
I updated my drivers like 10 times. Plus, like I said, my phone a well as my other friend's phone works just fine.
Sent from my EVO using XDA
Click to expand...
Click to collapse
If you have the most up to date drivers in device manager it will show "my htc" not android 1.0.
Sent from my EVO using Tapatalk
Concordium said:
RagawMOD root uses the htcDev method. It failed as I stated in the original post.
I updated my drivers like 10 times. Plus, like I said, my phone a well as my other friend's phone works just fine.
Sent from my EVO using XDA
Click to expand...
Click to collapse
Interesting. It definitely sounds like Drivers. The quote below me is right on. I was having this problem as well. The only thing I can think of is that you have a couple sets of drivers on your computer. When you go to update it updates with the old drivers (don't know why). I had this issue with my Kindle Fire.
Have you tried to update the drivers by manually selecting where to find the drivers?
thicklizard said:
If you have the most up to date drivers in device manager it will show "my htc" not android 1.0.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
purock said:
Interesting. It definitely sounds like Drivers. The quote below me is right on. I was having this problem as well. The only thing I can think of is that you have a couple sets of drivers on your computer. When you go to update it updates with the old drivers (don't know why). I had this issue with my Kindle Fire.
Have you tried to update the drivers by manually selecting where to find the drivers?
Click to expand...
Click to collapse
I guess I should've added that to the OP. Part of my fix prices was also to completely uninstall all HTC drivers and reinstall them. I used the drivers from PDANet since those were the only ones that managed to work correctly. All of the others wouldn't install correctly.
Sent from my EVO using XDA
I'm sorry if there is something already posted here somewhere about the rezound, but I haven't seen anything...yet...lol.
I've been trying to root my rezound ALL DAY and can't seem to figure anything out apparently.
If someone could help me out with sending me a link to the best way of unlocking bootloader and then rooting my phone. I had a dinc2 previously and that was not as hard to root compared to the rezound IMO. So please, if someone can take the time for me and help me out with getting my phone unlocked and rooted I would greatly appreciate it a TON!!!
Try this out http://forum.xda-developers.com/showthread.php?t=1648578
http://bit.ly/N3cfpa
hey guys thanks for replying back....I'm still getting no luck whatsoever with unlocking the bootloader.....I'm doing everything (or so I think I am) right with the steps on htcdev.com and when I get to the command prompt and type in fastboot oem get_identifier_token...this is what comes up
'fastboot' is not recognized as an internal or external command,
operable program or batch file.....now I have NO CLUE what the heck to do!! I'm getting pissed off lol. I could really use some help here. thanks
You need to change the directory to where your fastboot is located.
Sent from my ADR6425LVW using xda premium
EmerikL said:
You need to change the directory to where your fastboot is located.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Fastboot is located in the Android folder that i created....I found out my problem. My laptop isn't recognizing my phone at all. I read about this on a few forums about a lot of other people having this same issue with the rezound.....I try to install drivers on my pc for my phone to be recognized but its still not working....How did you or anyone else on here get their pc to recognize their phone???
npainter7 said:
Fastboot is located in the Android folder that i created....I found out my problem. My laptop isn't recognizing my phone at all. I read about this on a few forums about a lot of other people having this same issue with the rezound.....I try to install drivers on my pc for my phone to be recognized but its still not working....How did you or anyone else on here get their pc to recognize their phone???
Click to expand...
Click to collapse
Did you install HTC Sync properly? And have you tried installing the android usb drivers using SDK Manager?
kzoodroid said:
Did you install HTC Sync properly? And have you tried installing the android usb drivers using SDK Manager?
Click to expand...
Click to collapse
Yep I've installed htc sync multiple times now and SDK manager as well. Still a no go. It's really frustrating I can even unlock my [email protected]#$%& phone lol. After I install SDK manager, is there something else I have to do to it??? I think I have everything ready to unlock my device but once I click fastboot OEM get identifier token it says waiting for device and doesn't do anything after that. Freakin sucks
Yeah make sure you have the HTC drivers installed. I had the same issue in Jan when I rooted mine, drivers weren't there.
Posted from my Rooted and ICS'd Rezound
Fastbird said:
Yeah make sure you have the HTC drivers installed. I had the same issue in Jan when I rooted mine, drivers weren't there.
Posted from my Rooted and ICS'd Rezound
Click to expand...
Click to collapse
I'm pretty sure I had them downloaded. Just to make sure, what is included in the drivers?? That way I know everything is there when its downloaded.
npainter7 said:
Yep I've installed htc sync multiple times now and SDK manager as well. Still a no go. It's really frustrating I can even unlock my [email protected]#$%& phone lol. After I install SDK manager, is there something else I have to do to it??? I think I have everything ready to unlock my device but once I click fastboot OEM get identifier token it says waiting for device and doesn't do anything after that. Freakin sucks
Click to expand...
Click to collapse
After you install Android SDK the directions on the HTCdev site tell you to run sdk manager and download the Android SDK Tools and Android SDK Platfrom-tools. What I did was to take this a step further and also install the Google USB Driver which is listed in ADB Manager under Extras and also the API's for GB and ICS. The API's really aren't necessary but I don't think ADB will recognize the phone without the Google USB Drivers.
npainter7 said:
I'm pretty sure I had them downloaded. Just to make sure, what is included in the drivers?? That way I know everything is there when its downloaded.
Click to expand...
Click to collapse
This may not work for you, but one time my drivers weren't working because I plugged my phone into a USB 3.0 port, so when I used a USB 2.0 port, it worked fine.
I am ready to break something!!!
OK, after spending over a day reading and trying different things to no avail, my brain is a jumbled mess
i have a 16gb NT it was updated to the 1.4.3 when i started. I rooted it using indirect/brianf21 sd card method. everything worked fine for the little bit that i messed with it in this state. i then moved on to Veronica's CM7beta_ribbon_ICS rom for the most part everything was working. I installed a few apps from the market and on a reboot i got stuck in a bootloop. powered off, bootloop again. so i booted into CWM and tried reflashing the ROM only to be met with the 'please restart you device' screen. its all downhill from there. i can currently boot into CWM internally and have tried many different methods. so right now i dont get the 'restart' screen as it just goes into CWM. I have never worked with ABD but have been fighting drivers trying to get my nook to show up and having no luck so that i might try something there. i am new to rooting on the NT but have rooted and flashed different roms to my phone so i feel i have a basic concept. i dont know if im having so much of an issue cuz of the 1.4.3 or what **sigh**
I am now defeated and am in need of some help!!! haha! if anyone has anything to offer i would be so very thankful!
neonblur said:
I am ready to break something!!!
OK, after spending over a day reading and trying different things to no avail, my brain is a jumbled mess
i have a 16gb NT it was updated to the 1.4.3 when i started. I rooted it using indirect/brianf21 sd card method. everything worked fine for the little bit that i messed with it in this state. i then moved on to Veronica's CM7beta_ribbon_ICS rom for the most part everything was working. I installed a few apps from the market and on a reboot i got stuck in a bootloop. powered off, bootloop again. so i booted into CWM and tried reflashing the ROM only to be met with the 'please restart you device' screen. its all downhill from there. i can currently boot into CWM internally and have tried many different methods. so right now i dont get the 'restart' screen as it just goes into CWM. I have never worked with ABD but have been fighting drivers trying to get my nook to show up and having no luck so that i might try something there. i am new to rooting on the NT but have rooted and flashed different roms to my phone so i feel i have a basic concept. i dont know if im having so much of an issue cuz of the 1.4.3 or what **sigh**
I am now defeated and am in need of some help!!! haha! if anyone has anything to offer i would be so very thankful!
Click to expand...
Click to collapse
in order to get drivers working while in recocery mode you need to find the product id of the nook while its in cwm. in windows you need to go to device manager and check to see if your nook shows up in "other devices". then right click and go to properties and go to the tab that relates to hardware and find the neccessary info.
after that you should see two lines. ypu need to copy those two to the android_win.inf and modify the lines in there with notepad or something.
then try installing drivers and it shouls pick it up
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
in order to get drivers working while in recocery mode you need to find the product id of the nook while its in cwm. in windows you need to go to device manager and check to see if your nook shows up in "other devices". then right click and go to properties and go to the tab that relates to hardware and find the neccessary info.
after that you should see two lines. ypu need to copy those two to the android_win.inf and modify the lines in there with notepad or something.
then try installing drivers and it shouls pick it up
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
thanks for the reply. ok my nook is showing up as a mass storage device under other devices but is also showing up under android phone as 'android composite ADB interface' and also under portable devices as 2 drives G: and H: both unclickable. when i right click the android phone i get a hardware tab but all i see there is device functions and device functions summery so im not sure of the info that you are referring to that i need. i have been at this all day and apologize if i am missing something because im tired haha. the other file i found was called android_winusb.inf, is this the right one? thanks again for your help!
neonblur said:
thanks for the reply. ok my nook is showing up as a mass storage device under other devices but is also showing up under android phone as 'android composite ADB interface' and also under portable devices as 2 drives G: and H: both unclickable. when i right click the android phone i get a hardware tab but all i see there is device functions and device functions summery so im not sure of the info that you are referring to that i need. i have been at this all day and apologize if i am missing something because im tired haha. the other file i found was called android_winusb.inf, is this the right one? thanks again for your help!
Click to expand...
Click to collapse
yea that inf file is the one you need to modify. but you already have adb composite interface... so that means drivers are installed.
what happens when you do adb devices after you get into cwm. what's the output?
Sent from my Nook Tablet CM7 BETA using xda premium app
this is where i am a complete noob. i have never used ADB and have been reading threads about people using it but the light bulb has just not gone off yet. i know how to get to the command prompt, heh, so that is one thing. what program do i need to install, is it the android SDK? thanks for your quick reply, i am generally a quick learner when it comes to this stuff just need to get over the ADB hurdle
neonblur said:
this is where i am a complete noob. i have never used ADB and have been reading threads about people using it but the light bulb has just not gone off yet. i know how to get to the command prompt, heh, so that is one thing. what program do i need to install, is it the android SDK? thanks for your quick reply, i am generally a quick learner when it comes to this stuff just need to get over the ADB hurdle
Click to expand...
Click to collapse
did you download the drivers and adb zip from one of the threads? that archive should have all you need for adb. after extractng you need to navigate to the extracted folder and do adb devices.
try looking in thr general section for these drivers I was talking about.
there should be a thread by lavero burgos in there.
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
did you download the drivers and adb zip from one of the threads? that archive should have all you need for adb. after extractng you need to navigate to the extracted folder and do adb devices.
try looking in thr general section for these drivers I was talking about.
there should be a thread by lavero burgos in there.
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
Ha! got it going...ok so when i entered ADB devices it gives me:
2015170003944006 recovery
im feeling better about maybe getting this unbricked
neonblur said:
Ha! got it going...ok so when i entered ADB devices it gives me:
2015170003944006 recovery
im feeling better about maybe getting this unbricked
Click to expand...
Click to collapse
ok well now you have adb working. now the problem is how to fix your problem lol... I'll see if I can think of something.
in the meantime can you go into detail as to how you got tto your current situation?
EDIT: do you get any errors when booting into cwm? like not being able to mount a certain drive or something?
Sent from my Nook Tablet CM7 BETA using xda premium app
no errors booting into cwm internal and never had a problem when booting into it from an sd card. i flashed it internally hoping it would be a little easier seeing as how i only have one sd card but i am going to go get another today just to work through this.
nook started on 1.4.3 i rooted it using brianf23 and indirects sd card method. market and everything worked great. so i flashed Veronica's CM7beta_ribbon_ICS rom. everything for the most part was working, tho i did notice that some menu items would not open for me but they were noting i really needed to mess with at the time. so i installed a few apps and was done for the day. turned it on the next day and got stuck in a bootloop, so powered off and rebooted but got the same bootloop. booted into recovery did the standard dalvik cache ect and reflashed the rom, hoping this might fix the loop. upon rebooting is when i got stuck at the 'please reboot your device' screen. i have tried several methods of just flashing to stock ect, formatted my sd correctly and made sure it was active to try and flash back to stock that way but my nook will not boot from sd. so 12+ hours later i hung my head and asked for help lol! thanks to you i am able to start ADB no clue what to do but hey....step in the right direction!
Happy Dance
i got it working back to stock!! thank you so much for getting me going with ADB, without your help i would have stayed lost. i used kring789's ADB instructions and *poof* it rebooted to stock :good::good: thanks again for your help!
neonblur said:
i got it working back to stock!! thank you so much for getting me going with ADB, without your help i would have stayed lost. i used kring789's ADB instructions and *poof* it rebooted to stock :good::good: thanks again for your help!
Click to expand...
Click to collapse
good job on the fix. glad to help
Sent from my Nook Tablet CM7 BETA using xda premium app
Okay, just wanted to put this info here for easy reference. Feel free to correct anything I may have wrong.
*Based on my experiences performing the operation on windows 7 x64.
1. Install the LG USB driver for windows found under the software tab from their site here
2. Download and extract the English version of the root optimus g created by fiddy619 from here
3. Set USB debugging on and attach your phone to usb, then put it in MTP/Media Sync mode. Next, open a command prompt and navigate to the "stuff" sub-directory of the extracted file. Run the command "adb devices" to make sure your phone has been detected. Go back to the main directory and run the RootOptimusG.bat file.
4. When prompted on your phone choose restore data. Leave your phone plugged into USB until the program tells you it is finished! Sit back and let the magic happen. Your phone will reboot. Mine acted weird for a few seconds after it rebooted, the buttons at the bottom were going on and off and the screen was flickering. Just be patient and give it a couple minutes if needed.
5. When prompted that all is complete you can disconnect your phone from your computer and open the Play store to get the update for SuperSU
Now you are ready to unlock!
should be a sticky.
Thanks!
I followed the thread to root no fiddy619 instructions. I did use MTP.
But instead of Command prompt, I just double clicked the BAT file. and it run without problems, I think.
I have the SuperSU icon on my phone.
How can i make sure it was rooted?
p.s
The unlock also ran without problems.
karelson said:
I followed the thread to root no fiddy619 instructions. I did use MTP.
But instead of Command prompt, I just double clicked the BAT file. and it run without problems, I think.
I have the SuperSU icon on my phone.
How can i make sure it was rooted?
p.s
The unlock also ran without problems.
Click to expand...
Click to collapse
well if you have the supersu then it should be rooted. also if you now have it unlocked then it is rooted because i dont think you can unlock unless you root. also please search around the forums about what apps to not remove after root. a lot of people have noted issues after removing google apps.
showstopper03 said:
well if you have the supersu then it should be rooted. also if you now have it unlocked then it is rooted because i dont think you can unlock unless you root. also please search around the forums about what apps to not remove after root. a lot of people have noted issues after removing google apps.
Click to expand...
Click to collapse
Great Thank You.
karelson said:
Great Thank You.
Click to expand...
Click to collapse
actually it looks like V.05 you can uninstall any app without fear of security warnings. Please read all of this link for more info on it.
http://forum.xda-developers.com/showthread.php?t=2001655
Correct, you can just double click the bat file...my steps vary because I included a check to make sure adb is recognizing your device properly.
karelson said:
I followed the thread to root no fiddy619 instructions. I did use MTP.
But instead of Command prompt, I just double clicked the BAT file. and it run without problems, I think.
I have the SuperSU icon on my phone.
How can i make sure it was rooted?
p.s
The unlock also ran without problems.
Click to expand...
Click to collapse
Bumping this back to the top until stickied.
Sent from my LG Optimus G using Tapatalk 2
IrateCustomer said:
Bumping this back to the top until stickied.
Sent from my LG Optimus G using Tapatalk 2
Click to expand...
Click to collapse
Mine is stuck at "Select Restore Data" from my Phone step ... not sure whats going on.
kirdroid said:
Mine is stuck at "Select Restore Data" from my Phone step ... not sure whats going on.
Click to expand...
Click to collapse
I tried unrooting and re-rooting just to test our guides here and I am stuck at this step too. Obviously I can simply flash su in CWM but I wonder why this is happening.
carrett said:
I tried unrooting and re-rooting just to test our guides here and I am stuck at this step too. Obviously I can simply flash su in CWM but I wonder why this is happening.
Click to expand...
Click to collapse
Go to general-developer options- set desktop backup password. Set the password and then use that when you run the script and restore from desktop backup screen shows up.
Sent from my LG-E970 using Tapatalk 2
kirdroid said:
Go to general-developer options- set desktop backup password. Set the password and then use that when you run the script and restore from desktop backup screen shows up.
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
If that worked for you, I'm happy for you. I am at this time unable to find a way to unroot and then re-root aside from restoring a backup in CWM or flashing a superuser zip in CWM. This could be because of a "bug" in our rooting script, in SuperSU's un-rooting function, or just an incompatibility between the two. Either way, I think this rooting mechanism works for more virgin LGOGs than not.
worked for me, easy peasy.
When i run the script it gives an error saying that i'm missing backup-restore.apk and /system/bin/ric does not exist. Any ideas as to why this is?
nice. thank you.
aznracer62 said:
When i run the script it gives an error saying that i'm missing backup-restore.apk and /system/bin/ric does not exist. Any ideas as to why this is?
Click to expand...
Click to collapse
That is probably because your phone is not rooted yet. I got that too as I was rooting it. Worked great.
I'm trying to root. USB debugging is on, connected as MTP. Run ADB, run adb-devices, returns an empty screen.
Try to run the script, it tells me "please check setting again"
HALP.
bebop_ said:
I'm trying to root. USB debugging is on, connected as MTP. Run ADB, run adb-devices, returns an empty screen.
Try to run the script, it tells me "please check setting again"
HALP.
Click to expand...
Click to collapse
Also need to allow "unknown sources" in security settings.
adfurgerson said:
Also need to allow "unknown sources" in security settings.
Click to expand...
Click to collapse
I had that checked as well.
bebop_ said:
I had that checked as well.
Click to expand...
Click to collapse
Do you have lg usb drivers installed?