Related
OK. Firstly, I have extensive experience with rooting moto droids and custom roms. That said I got cocky and didn't do enough homework trying to root my girls Eris and proceeded following the instructions in the "1.5 to rooted 2.1" thread. Step 1 went fine. I THINK I have root access. Anyway, like I was tired and couldn't get adb shell working so I left it at that with intent to finish today when I get home from work. Now she's telling me her icons are different and some are linking to different programs. Any ideas? Second, can someone point me in the direction of an adb shell how to, on my Droid I can just use terminal emulation and don't actually need a computer so I'm not too familiar with the process... sorry for the stupid newborn questions, don't pull the flame throwers out yet, thanks!
You can use terminal emulator, same thing for the most part as adb... I use that more then adb, faster then having to connect to a pc IMO.
I tried the terminal emulator and got adb not found or not allowed or some craziness like that. Does that mean I didn't root like I thought? Also, any clue about the icon s changing or linking to other apps like shes claiming? I'm going to try again when she gets home
In the terminal emulator you would not need to type adb.. adb is the program you would be using on a pc to talk to the phone... what is it that you are trying to type through adb or the terminal?
III: Flashing a Custom Recovery
Flashing a custom recovery will make your life easier when flashing ROMs in the future.
1. Download this file: Recovery.zip
2. Extract file contents to your \tools\ directory of your Android SDK.
3. Open up a command prompt and go to your tools directory, and execute these commands:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
4. Success! You now have a recovery partition installed on your phone. You can access it by running "adb shell reboot recovery" or by powering off your phone, holding "Volume Up + Power On"
step 3. im an ass. ok so dont type the adb. like i said, not much exp in this part... im guessing i dont tye shell either, but i do type mount?
evilsway said:
III: Flashing a Custom Recovery
Flashing a custom recovery will make your life easier when flashing ROMs in the future.
1. Download this file: Recovery.zip
2. Extract file contents to your \tools\ directory of your Android SDK.
3. Open up a command prompt and go to your tools directory, and execute these commands:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
4. Success! You now have a recovery partition installed on your phone. You can access it by running "adb shell reboot recovery" or by powering off your phone, holding "Volume Up + Power On"
step 3. im an ass. ok so dont type the adb. like i said, not much exp in this part...
Click to expand...
Click to collapse
Oh I see, for that yes you will need to get the SDK setup on your PC as per step 2... There is another thread that has a batch file that does all of this for you. You still need the SDK though.
see: http://forum.xda-developers.com/showthread.php?t=651669
ok, i have the sdk, i followed these instructions to the letter, and i still couldnt get it running last night, where in the sdk do i do this from or is it a command promp, or can i use the terminal emulator?
yes in the command prompt, typically adb.exe will be in your tools folder.
also, and i know im being a pain now, but by adb does it mean the adb in the tools directory of the sdk, i click it and it runs a script then dissapears.
evilsway said:
also, and i know im being a pain now, but by adb does it mean the adb in the tools directory of the sdk, i click it and it runs a script then dissapears.
Click to expand...
Click to collapse
yes, adb needs to be ran through the command prompt, if you click on it in windows it wont work... read the thread I linked you to, you wont need to run adb if you use that method, it does it all for you.
yeah im downloading the file now, but im just curious, now i want to be able to do it just to do it. i hate when i cant figure crap like this out,
so far ive done this, opened command promp, put in C:\androidsdk\android-sdk-windows\tools\adb.exe and it runs a script then nothing
evilsway said:
yeah im downloading the file now, but im just curious, now i want to be able to do it just to do it. i hate when i cant figure crap like this out,
so far ive done this, opened command promp, put in C:\androidsdk\android-sdk-windows\tools\adb.exe and it runs a script then nothing
Click to expand...
Click to collapse
go to start, run and type cmd and enter. then in that window
you have to change to the tools directory at the command prompt like so"
cd androidsdk\android-sdk-windows\tools
then type adb
Renocat said:
go to start, run and type cmd and enter. then in that window
you have to change to the tools directory at the command prompt like so"
cd androidsdk\android-sdk-windows\tools
then type adb
Click to expand...
Click to collapse
Yeah, once you do what he states and type...
cd androidsdk\android-sdk-windows\tools ... or where ever you have your SDK saved at on your computer ... you should be good to start running those scripts in the directions.
I tried loading the Aria into an adb shell, then tried the reboot command (just "reboot"). It replies "reboot: no such tool".
I also wrote a quick script with GScript and ran it with su permissions (my phone is rooted with clockworkmod, and liberated), and the same message showed on screen.
I also made a separate script that just runs "ls /system/bin" and I can clearly see the "reboot" command in the directory. Again, when I try to run /system/bin/reboot with su priveleges, it gives the same message.
I'm tempted to think that the reboot command in /system/bin simply runs the command "echo reboot: no such tool". Does anyone have any more information about this? I'd like a script that would use the reboot command to reboot into recovery mode.
I believe you should be able to use "shutdown /r" to reboot the phone.. probably needs to be done with sudo though..
jleehey said:
I tried loading the Aria into an adb shell, then tried the reboot command (just "reboot"). It replies "reboot: no such tool".
I also wrote a quick script with GScript and ran it with su permissions (my phone is rooted with clockworkmod, and liberated), and the same message showed on screen.
I also made a separate script that just runs "ls /system/bin" and I can clearly see the "reboot" command in the directory. Again, when I try to run /system/bin/reboot with su priveleges, it gives the same message.
I'm tempted to think that the reboot command in /system/bin simply runs the command "echo reboot: no such tool". Does anyone have any more information about this? I'd like a script that would use the reboot command to reboot into recovery mode.
Click to expand...
Click to collapse
I can reboot the phone using ADB by typing adb reboot... Or in terminal on the phone itself I su and then enter reboot and voila...
Not sure if this helps or not.
Edit: I am also running CM6 which has busybox installed.
The way I do it from shell is to type 'exit', this takes you out of shell. Then I type 'adb reboot'
Your path is probably not correct on the device. To change the path you need to edit init.rc and add the correct path.
I have had this same problem and now think that the tool unrevoked is messing the path variable up.
Let me know what you discover.
Same
I also have the same problem. I checked init.rc and i didnt find something about reboot. I run S5 Sensenation ROM. I will check again, But i happy to see that im not the only one who have the problem.....
Lil' Help... New stock SGS2 phone arrived today... I successfully flashed Entropy512's "stock kernel + rooted stock system image" via Odin3 (v1.85). Worked perfect, phone rebooted, now I have root. 2nd step, I extracted the zImage from Codeworkx's CWM tar file (put zImage in same PC desktop folder as my adb.exe files). I want to use adb push to push zImage file to phone so I can avoid the triangle/counter of death. Anyway, I got this error in my CMD window:
C:\Android\android-sdk-windows\platform-tools>adb push zImage /sdcard/zImage
error: device not found
What went wrong? The "phone" and "card" are recognized by windows explorer, but when trying to use adb commands, get "error: device not found"
Thx.
DoctorQMM said:
Lil' Help... New stock SGS2 phone arrived today... I successfully flashed Entropy512's "stock kernel + rooted stock system image" via Odin3 (v1.85). Worked perfect, phone rebooted, now I have root. 2nd step, I extracted the zImage from Codeworkx's CWM tar file (put zImage in same PC desktop folder as my adb.exe files). I want to use adb push to push zImage file to phone so I can avoid the triangle/counter of death. Anyway, I got this error in my CMD window:
C:\Android\android-sdk-windows\platform-tools>adb push zImage /sdcard/zImage
error: device not found
What went wrong? The "phone" and "card" are recognized by windows explorer, but when trying to use adb commands, get "error: device not found"
Thx.
Click to expand...
Click to collapse
Try to start by verifying that adb can see your phone.
type "adb devices" (no quotes)
This should return a number, if not, the phone is not being seen by adb.
If not check drivers, cable, try different usb port.
If it does return a number you are properly connected.
Proceed to:
adb push zImage /sdcard/zImage
adb shell dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
Might need to as su if prompt shows $ instead of #
Try adb remount
i didnt realize so many people cared about a little triangle that you see for about 3 seconds on boot.
DoctorQMM said:
Lil' Help... New stock SGS2 phone arrived today... I successfully flashed Entropy512's "stock kernel + rooted stock system image" via Odin3 (v1.85). Worked perfect, phone rebooted, now I have root. 2nd step, I extracted the zImage from Codeworkx's CWM tar file (put zImage in same PC desktop folder as my adb.exe files). I want to use adb push to push zImage file to phone so I can avoid the triangle/counter of death. Anyway, I got this error in my CMD window:
C:\Android\android-sdk-windows\platform-tools>adb push zImage /sdcard/zImage
error: device not found
What went wrong? The "phone" and "card" are recognized by windows explorer, but when trying to use adb commands, get "error: device not found"
Thx.
Click to expand...
Click to collapse
You're missing drivers or haven't enabled USB debugging. Drivers for USB Mass Storage are built into Windows, drivers for ADB are not. Not sure what the procedure is for installing Windows ADB drivers... It's one of the reasons I almost never use Windows for working with my phone.
I've heard Droid Explorer might come with a drivers package, not sure.
Entropy512 said:
You're missing drivers or haven't enabled USB debugging. Drivers for USB Mass Storage are built into Windows, drivers for ADB are not. Not sure what the procedure is for installing Windows ADB drivers... It's one of the reasons I almost never use Windows for working with my phone.
I've heard Droid Explorer might come with a drivers package, not sure.
Click to expand...
Click to collapse
PDANET is free and simple to install on any Windows based machine. Less than 30 seconds and it recognises every phone I have tried so far. You just need to be sure to get the right one for you OS, 64 or 32 bit.
I sent to my kids that are too lazy to install the Android SDK.....
SNadler said:
Try to start by verifying that adb can see your phone.
type "adb devices" (no quotes)
This should return a number, if not, the phone is not being seen by adb.
If not check drivers, cable, try different usb port.
If it does return a number you are properly connected.
Proceed to:
adb push zImage /sdcard/zImage
adb shell dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
Might need to as su if prompt shows $ instead of #
Click to expand...
Click to collapse
I appreciate everyone's input... OK, here's where I stand:
adb does now recognize phone. After typing "adb devices", cmd window showed my phone in list of devices attached. I then proceeded to "adb push zImage /sdard/zImage... that seemed to work also [cmd window came back with "2544 KB/s (6718048 bytes in 2.578s)]. Next, I typed "adb shell dd if=/sdcard/zImage of=/dev/block/mmcblk0p5" [cmd window came back with "/dev/block/mmcblk0p5: cannot open for write: Permission denied"]
so is still a drivers issue? cable issue? or something else? Thx again
EDIT: one additional clue for all the experts: the zImage is now on my /sdcard. When I type "adb shell", I do get "$" instead of "#" in cmd window... and I know I have root on phone. When I type "adb shell su" in cmd window, I get "Permission denied".
Sometimes the root install won't completely work until you go to the Superuser app once manually. (e.g. in Applications).
Also, another possibility may be that there are two ways to run adb shell:
One is
Code:
adb shell <command>
Where it'll run <command> and then exit
Then there is
Code:
adb shell
<command1>
<command2>
exit
In the second, when you first type "adb shell" you'll get a shell prompt on your phone.
Then you'll type su (this will give you superuser privileges)
Then you run the dd command
Then you should be good.
The difference is: If you have a custom "insecure" kernel, an ADB shell defaults to root privileges. If you have a stock kernel, ADB shell defaults to "mortal user", and you need to manually use su to get root privileges.
Pushing the file to the SD card does not require root, writing the kernel to the kernel partition (mmcblk0p5) does.
Entropy512 said:
Sometimes the root install won't completely work until you go to the Superuser app once manually. (e.g. in Applications).
Also, another possibility may be that there are two ways to run adb shell:
One is
Code:
adb shell <command>
Where it'll run <command> and then exit
Then there is
Code:
adb shell
<command1>
<command2>
exit
In the second, when you first type "adb shell" you'll get a shell prompt on your phone.
Then you'll type su (this will give you superuser privileges)
Then you run the dd command
Then you should be good.
The difference is: If you have a custom "insecure" kernel, an ADB shell defaults to root privileges. If you have a stock kernel, ADB shell defaults to "mortal user", and you need to manually use su to get root privileges.
Pushing the file to the SD card does not require root, writing the kernel to the kernel partition (mmcblk0p5) does.
Click to expand...
Click to collapse
===============
Entropy512... you da man! I'm good to go now. As you recommended, even though I've been using Root Explorer and I know I was 'rooted', had to open SuperUser app on phone... then in the cmd window when I typed "adb shell" I got the "$" prompt. So at the $ prompt I typed "su"... this gave me the "#" prompt. SuperUser App then asked for SU permission acceptance. Then did the "dd xxxxxxxx" command, and it came back with:
13121 +1 records in
13121 +1 records out
6718048 bytes transferred in 2.895 secs (2320569 bytes/sec).
Rebooted phone to recovery, and have the light blue CWM Recovery 5.0.2.3.
Now I'm rooted, have CWM, and no triangle/counter of death. Hope this helps anyone else with a similar situation.
Again, a BIG shoutout to Entropy512, SNadler, jivy26, et al., for your constructive and quick replies. This forum is the best!
DocQ
One last [Q] Do I have to leave the large "zImage" file (6.41mb) in the /sdcard folder, or can it be removed /moved now that CWM successfully flashed?
DoctorQMM said:
One last [Q] Do I have to leave the large "zImage" file (6.41mb) in the /sdcard folder, or can it be removed /moved now that CWM successfully flashed?
Click to expand...
Click to collapse
No need to leave it, although I keep a bunch of various kernels in /sdcard/kernels myself - it's up to you.
Hi,
Did a search and someone said they were able to root with thecubed method on Mac via Terminal, but I've had no luck so far. Are there any other options for us Mac users?
Thanks
BTW I did see some instructions but it only applies to Verizon. I have the international version D802.
Any help would be greatly appreciated.
use virtual machine and use windows?
I haven't found any easy way to do it, other that running bootcamp and windows on the mac..
You can do it via adb just fine on osx (I'm on snow leopard). You can check which commands to run by opening the Windows script as a text document. It's easy to follow what's going on and has sections for each device
xdabbeb said:
You can do it via adb just fine on osx (I'm on snow leopard). You can check which commands to run by opening the Windows script as a text document. It's easy to follow what's going on and has sections for each device
Click to expand...
Click to collapse
I opened root.bat as a text file but as far as how to input the commands I'm not sure what to do as it seems to differs from the video. Sorry I'm not that familiar working with Terminal.
If you could help out that would be great.
Thanks
xdabbeb said:
You can do it via adb just fine on osx (I'm on snow leopard). You can check which commands to run by opening the Windows script as a text document. It's easy to follow what's going on and has sections for each device
Click to expand...
Click to collapse
Ahhhhh! You know Mavericks is free, right? UPGRADE THAT THING!
On another note... same issue w/ me. I ended up rooting it via my PC, but after that you can use Android File Transfer to manage files and load roms and stuff via OSX.
sell ur POS apple and get a pc...?
digitard said:
Ahhhhh! You know Mavericks is free, right? UPGRADE THAT THING!
On another note... same issue w/ me. I ended up rooting it via my PC, but after that you can use Android File Transfer to manage files and load roms and stuff via OSX.
Click to expand...
Click to collapse
Ha! I haven't upgraded because I still feel snow leopard is the best. I don't like how they've integrated so much ios in the last two, and SL is lean/efficient.
If I have some time I'll write down the commands in a reply. Do you have adb already set up?
xdabbeb said:
Ha! I haven't upgraded because I still feel snow leopard is the best. I don't like how they've integrated so much ios in the last two, and SL is lean/efficient.
If I have some time I'll write down the commands in a reply. Do you have adb already set up?
Click to expand...
Click to collapse
Yes already have adb set up. Thanks for this. Really appreciate it.
No problem. What version of the G2 do you have?
---------- Post added at 11:49 PM ---------- Previous post was at 11:48 PM ----------
Ignore that, I just saw you mentioned the international version
OK, here you go:
1) Go here here and here and thank them both for their work...and read their disclaimers about breaking your phone. The same applies here.
2) Download the attached archive and extract the contents into whatever folder you want...for the purposes of this I'll assume you did so to a directory called ~/D802_OSXroot. If you chose a different directory, modify the steps below accordingly. The archive I attached only contains the appropriate file for the international (D802) LG G2, and I used Chainfire's SuperSU instead of the older ChainsDD su binary and apk. While you're at it, go here and thank him.
3) Make sure USB Debugging is enabled on your phone in Settings>Developer Options
4) Connect your phone via usb cable. You'll get the popup asking what type of connection on your phone. Select Internet connection and then Ethernet when asked. You should see the debugging icon in the status bar of your phone
5) Open terminal on your mac
6) To verify that you are properly connected run the following command:
Code:
adb shell "ls -a /"
you should see the contents of the root of your phone...inlcuding a number of init files. If you do, proceed. If you don't, you have an adb/connection problem.
7) Execute the following in the terminal window to go to the directory where the archive has been extracted on your mac:
Code:
cd ~/D802_OSXroot
8) Execute the following to push the loki exploit file to your phone
Code:
adb push ./g2_security /sdcard/g2_security
9) Unplug your usb cable from the phone
10) On your phone go to Settings>Developer Options and disable USB Debugging
11) Re-enable USB Debugging
12) Plug in your USB cable (follow step 4)
13) Verify adb connectivity (follow step 6)
14) Go back to your terminal window, make sure you are still in the same directory with the files from the archive and execute the following commands in order:
Code:
adb shell "mount -o remount,rw /system"
Code:
adb push ./su /system/xbin/su
Code:
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
Code:
adb install superuser.apk
15) Launch the SuperSU app on your phone. It will likely prompt you to update the su binary...let it do so and then reboot your phone. You should be rooted now.
Good luck!
xdabbeb said:
OK, here you go:
1) Go here here and here and thank them both for their work...and read their disclaimers about breaking your phone. The same applies here.
2) Download the attached archive and extract the contents into whatever folder you want...for the purposes of this I'll assume you did so to a directory called ~/D802_OSXroot. If you chose a different directory, modify the steps below accordingly. The archive I attached only contains the appropriate file for the international (D802) LG G2, and I used Chainfire's SuperSU instead of the older ChainsDD su binary and apk. While you're at it, go here and thank him.
3) Make sure USB Debugging is enabled on your phone in Settings>Developer Options
4) Connect your phone via usb cable. You'll get the popup asking what type of connection on your phone. Select Internet connection and then Ethernet when asked. You should see the debugging icon in the status bar of your phone
5) Open terminal on your mac
6) To verify that you are properly connected run the following command:
Code:
adb shell "ls -a /"
you should see the contents of the root of your phone...inlcuding a number of init files. If you do, proceed. If you don't, you have an adb/connection problem.
7) Execute the following in the terminal window to go to the directory where the archive has been extracted on your mac:
Code:
cd ~/D802_OSXroot
8) Execute the following to push the loki exploit file to your phone
Code:
adb push ./g2_security /sdcard/g2_security
9) Unplug your usb cable from the phone
10) On your phone go to Settings>Developer Options and disable USB Debugging
11) Re-enable USB Debugging
12) Plug in your USB cable (follow step 4)
13) Verify adb connectivity (follow step 6)
14) Go back to your terminal window, make sure you are still in the same directory with the files from the archive and execute the following commands in order:
Code:
adb shell "mount -o remount,rw /system"
Code:
adb push ./su /system/xbin/su
Code:
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
Code:
adb install superuser.apk
15) Launch the SuperSU app on your phone. It will likely prompt you to update the su binary...let it do so and then reboot your phone. You should be rooted now.
Good luck!
Click to expand...
Click to collapse
Has anyone tried this method?
Sent from my LG-D802 using Tapatalk
xdabbeb said:
OK, here you go:
1) Go here here and here and thank them both for their work...and read their disclaimers about breaking your phone. The same applies here.
2) Download the attached archive and extract the contents into whatever folder you want...for the purposes of this I'll assume you did so to a directory called ~/D802_OSXroot. If you chose a different directory, modify the steps below accordingly. The archive I attached only contains the appropriate file for the international (D802) LG G2, and I used Chainfire's SuperSU instead of the older ChainsDD su binary and apk. While you're at it, go here and thank him.
3) Make sure USB Debugging is enabled on your phone in Settings>Developer Options
4) Connect your phone via usb cable. You'll get the popup asking what type of connection on your phone. Select Internet connection and then Ethernet when asked. You should see the debugging icon in the status bar of your phone
5) Open terminal on your mac
6) To verify that you are properly connected run the following command:
Code:
adb shell "ls -a /"
you should see the contents of the root of your phone...inlcuding a number of init files. If you do, proceed. If you don't, you have an adb/connection problem.
7) Execute the following in the terminal window to go to the directory where the archive has been extracted on your mac:
Code:
cd ~/D802_OSXroot
8) Execute the following to push the loki exploit file to your phone
Code:
adb push ./g2_security /sdcard/g2_security
9) Unplug your usb cable from the phone
10) On your phone go to Settings>Developer Options and disable USB Debugging
11) Re-enable USB Debugging
12) Plug in your USB cable (follow step 4)
13) Verify adb connectivity (follow step 6)
14) Go back to your terminal window, make sure you are still in the same directory with the files from the archive and execute the following commands in order:
Code:
adb shell "mount -o remount,rw /system"
Code:
adb push ./su /system/xbin/su
Code:
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
Code:
adb install superuser.apk
15) Launch the SuperSU app on your phone. It will likely prompt you to update the su binary...let it do so and then reboot your phone. You should be rooted now.
Good luck!
Click to expand...
Click to collapse
Thanks for this. I'm having an issue at the first step. I have tested adb when I downloaded the SDK and if I direct the command ./adb devices to that specific folder it can read my phone, but just going into terminal and entering adb shell "ls -a /" al I get is -bash: adb: command not found
Also when I connect my phone to the mac I get options on the G2 but none are internet then ethernet. I get: Charge Phone, Media Sync, Tethering, LG Software, Send Images. The Mac does not ask me what connection I want.
ck37 said:
Thanks for this. I'm having an issue at the first step. I have tested adb when I downloaded the SDK and if I direct the command ./adb devices to that specific folder it can read my phone, but just going into terminal and entering adb shell "ls -a /" al I get is -bash: adb: command not found
Also when I connect my phone to the mac I get options on the G2 but none are internet then ethernet. I get: Charge Phone, Media Sync, Tethering, LG Software, Send Images. The Mac does not ask me what connection I want.
Click to expand...
Click to collapse
It sounds like the first issue may just be due to you not having adb set up properly. If you execute "echo $PATH" in terminal and don't see the android/tools and android/platform-tools directories there, that's the problem. You can either set your path variable to include those directories or just edit the commands I listed accordingly.
The second issue may be due to a difference in the D802 rom vs the VS980. The important thing is that USB Debugging is enabled and that you can access your phone via adb. The 802 may not prompt you in the same way, but if you fix your adb setup the commands will work the same. The rooting method listed (which is the same as thecubed method) is predicated on that working properly.
xdabbeb said:
It sounds like the first issue may just be due to you not having adb set up properly. If you execute "echo $PATH" in terminal and don't see the android/tools and android/platform-tools directories there, that's the problem. You can either set your path variable to include those directories or just edit the commands I listed accordingly.
The second issue may be due to a difference in the D802 rom vs the VS980. The important thing is that USB Debugging is enabled and that you can access your phone via adb. The 802 may not prompt you in the same way, but if you fix your adb setup the commands will work the same. The rooting method listed (which is the same as thecubed method) is predicated on that working properly.
Click to expand...
Click to collapse
I think I figured it out. What I did was transfer the ADB icon from my SDK folder into this one. From there I was able to get access to adb inside the D802 folder. I did have to enter the ./adb as opposed to adb though.
As for the LG I selected tethering as that seemed to be the option similar to the internet/ ethernet choice you mentioned.
All other commands worked accordingly.
Binaries updated for SuperUser as well. At this point how do I get into recovery to upload ROMS etc?
ck37 said:
I think I figured it out. What I did was transfer the ADB icon from my SDK folder into this one. From there I was able to get access to adb inside the D802 folder. I did have to enter the ./adb as opposed to adb though.
As for the LG I selected tethering as that seemed to be the option similar to the internet/ ethernet choice you mentioned.
All other commands worked accordingly.
Binaries updated for SuperUser as well. At this point how do I get into recovery to upload ROMS etc?
Click to expand...
Click to collapse
What I did was installed flashify from the market. This app allows you to backup and then flash a new recovery. Make sure you dl the right one for your device!
Sent from my LG-VS980 using Tapatalk
I was trying to install gapps and now when I reboot I am stuck and the Play Store language select screen. When I click next, it takes me to settings. I have no home or back button so I cant get anywhere other than the settings menu. I have tried a factory reset with no avail. I also tried a manual update, but I have disable OTA updates so it wont recognize the .bin file on my SD. If only I could get to ES File Explorer. Any tips on fixing this problem?
Code:
adb shell "su -c 'mount -o rw,remount /system'"
adb shell "su -c 'mv /system/priv-app/SetupWizard.apk /system/priv-app/SetupWizard.apk.old'"
adb shell "su -c 'mount -o ro,remount /system'"
ONYXis said:
Code:
adb shell "su -c 'mount -o rw,remount /system'"
adb shell "su -c 'mv /system/priv-app/SetupWizard.apk /system/priv-app/SetupWizard.apk.old'"
adb shell "su -c 'mount -o ro,remount /system'"
Click to expand...
Click to collapse
Care to elaborate? I am a complete noob and shouldn't have been trying this at all. I can't access anything on my Kindle other than settings. Do I run this in command prompt on windows?
Edit: I also wanted to add that I am not one of the guys who sits around waiting for an answer without researching the problem lol
You need install adb on your PC - http://forum.xda-developers.com/showthread.php?t=2317790
Install drivers for our tablet (no need to reboot fastboot just manual install drivers for your kindle at device manager) - http://forum.xda-developers.com/showpost.php?p=59268023&postcount=8
Open CMD (cd C:\Program Files (x86)\Minimal ADB and Fastboot>)and paste these commands. I assume you rooted if you can block ota.
ONYXis said:
You need install adb on your PC - http://forum.xda-developers.com/showthread.php?t=2317790
Install drivers for our tablet (no need to reboot fastboot just manual install drivers for your kindle at device manager) - http://forum.xda-developers.com/showpost.php?p=59268023&postcount=8
Open CMD (cd C:\Program Files (x86)\Minimal ADB and Fastboot>)and paste these commands. I assume you rooted if you can block ota.
Click to expand...
Click to collapse
Apparently I no longer have root since I reset to factory. I do have the adb drivers installed, but I get stuck when using the command prompt because I dont have su access. Anyway for me to root it with only access to settings? I am on 4.5.2
are you sure?
earlier I had root even after hard reset on 4.5.2
anyway you could try install kingroot but I do not sure
I think @Cl4ncy and @Davey126 may clarify this.
ONYXis said:
are you sure?
earlier I had root even after hard reset on 4.5.2
anyway you could try install kingroot but I do not sure
I think @Cl4ncy and @Davey126 may clarify this.
Click to expand...
Click to collapse
Yes, I no longer had root access. Thanks to all of your other help and suggestions, I have been able to successfully get my Fire HDX working again. With all of the info you gave I was able to research and piece together what I needed. I was able to install Kingroot through cmd and then use the commands you gave to get rid out of settings. Thanks alot!