Related
ok so on most roms this happens. i need a SU request but my phone freezes obn a black screen and on the top in gray it says SU request. i wait paciently and maybe 1-2 mins later is asks to FC because its not responding. is there a fix or what am i doing wrong. usb debugging is on and so is install nonmarket apps idk wtf im doing wrong or if somthing is just not working. any input??
I've heard su is not working properly until you activate it once via adb. In your teriminal (cmd or similar)
Code:
adb shell
$su
You should get a working super user request after which all other su requests should work fine.
Marisa said:
I've heard su is not working properly until you activate it once via adb. In your teriminal (cmd or similar)
Code:
adb shell
$su
You should get a working super user request after which all other su requests should work fine.
Click to expand...
Click to collapse
yes same thing happens to me
plug in your phone
goto your android sdk tools
and input adb shell
now go back to your phone and try it while still plugged
thats what i have been doing...
the same thing is happening for me and the instructions of simply input adb shell into terminal arent helping really. if someone could tell me exactly where to be aiming the command prompt and what the exact commands are in order to fix this I would greatly appreciate it.
WalkingTaco said:
the same thing is happening for me and the instructions of simply input adb shell into terminal arent helping really. if someone could tell me exactly where to be aiming the command prompt and what the exact commands are in order to fix this I would greatly appreciate it.
Click to expand...
Click to collapse
Are you getting the same crshes and things, but when you do the adb shell # pops up instead of $?
whenever i do adb shell I get #, so that means SU is already activated, but it's actually not on my phone, so i have no idea what's going on and no one seems to know how to fix it.
no. my Su permissions always force close after a minute of black screen. there is a fix posted above but my nerd level is not high enough to.infer the rest
Sent from my Eris using the XDA mobile application powered by Tapatalk
I don't know the exact command prompt setup, I'm running linux. However, when you originally rooted your phone you used the Android SDK correct?
With your phone plugged in, and USB Debugging enabled on your phone (Settings -> Applications -> Development -> USB Debugging) Open command prompt and get to the tools directory you used during rooting, I don't know where you installed it, so I cannot guide you through that part. If you used Ivan's guide http://forum.xda-developers.com/showthread.php?t=647707 it's probably best to refresh yourself there.
Once you've found your SDK /tools/ in command prompt, it should be as easy as running the code I mentioned earlier
Code:
adb shell
$su
in the command prompt.
The superuser prompt should show up on your phone, tell it to allow it and it should work without fail until you flash a new ROM that has the bug.
thanks very much. I used Ivans guide. I rooted it yesterday when o got my replacement from Verizon in store. I had been using the 2.1 leak on my old one and complained in store for thirty seconds. they didn't even look at it gave me a replacement in ten minutes
Sent from my Eris using the XDA mobile application powered by Tapatalk
Rock out thanks for the Super Help
I used root explorer, made a copy of my original and named it original, then copied over another build.prop from my SGSII to play with MC3 and now the prime wont boot.
Im sure I will have to wait until i get home to use my USB cable but is this something I can fix through ADB?
how can i get the Prime into state that ADB can talk to it since now all i get is a black screen after the Eee pad splash screen?
Can you get into the recovery?
yes but it it shows the little android on his back with a red triangle.
is that because im rooted?
see if you can get adb access, if so push back an original build.prop...
note... never ever push a build.prop from a different device.. its the most stupid thing you can do.
yes i feel extremely stupid. i hope i didnt brick my prime doing something this retarded.
nextelbuddy said:
yes i feel extremely stupid. i hope i didnt brick my prime doing something this retarded.
Click to expand...
Click to collapse
i hope so to bro, although i did read someone messed up his build.prop before on his prime, dunno how that went afterwards... u might need to search for that
If you have access to either adb.. or maybe if you can flash zip files from your recovery you're good to go.
Using Adb:
Running "adb devices" should print your Device #, if it prints nothing, it won't work..
adb pull /system/build.prop build.prop.bootloop
adb pull /system/original.build.prop original.build.prop (>> Edited to original.build.prop as per your last post)
Then if you look at the files on your PC..
build.prop.bootloop would be the one you have right now that's causing loops
build.prop would be your backed up working build.prop.original
Then just push the good one:
adb push original.build.prop /system/build.prop
adb pull/push usage:
adb pull remotefile localfile
adb push localfile remotefile
You may be able to go this route and reflash the entire rom if you dont have adb access. From what I understand is you rename the update.zip file to whatever it says in the link to rename to and put on the root of sd card and do the power + volume and go into recovery.
http://forum.xda-developers.com/showthread.php?t=1492887&page=18
the latest asus update can be found here.
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+Prime+TF201&p=20&s=16
thank you very much i will get to work on this when i get home with my cable. i was just about to post where can i get another one but you posted directions on how to pull my copy that i created which i renamed original.build.prop
Also might wanna take a look at this thread
http://forum.xda-developers.com/showthread.php?t=1514088
PM_mobile said:
If you have access to either adb.. or maybe if you can flash zip files from your recovery you're good to go.
Using Adb:
Running "adb devices" should print your Device #, if it prints nothing, it won't work..
adb pull /system/build.prop build.prop.bootloop
adb pull /system/original.build.prop original.build.prop (>> Edited to original.build.prop as per your last post)
Then if you look at the files on your PC..
build.prop.bootloop would be the one you have right now that's causing loops
build.prop would be your backed up working build.prop.original
Then just push the good one:
adb push original.build.prop /system/build.prop
adb pull/push usage:
adb pull remotefile localfile
adb push localfile remotefile
Click to expand...
Click to collapse
i can get the device into APX mode because i installed the APX driver and when i hold VOl UP and Power, my windows 7 computer shows Asus Prime APX under System Devices and it goes away if i unplug it and vice versa plugging it back in however ABD stil shows Blank for connected devices.
not sure what Im doing wrong so im uninstalling my OLD SDK from last year and reinstalling the latest SDK to see if that helps.
ok so my Prime boots into APX mode according to windows 7 Device manager. it shows APX not greyed out.
however despite this, in CMD when i type ADB Devices it shows BLANK and of course any adb commands return no device found.
if i let the Prime reboot into its Boot loop, then ADB Composite appears in Device manager.
if i go to CMD and type ADB Devices, it always says ADB Server out of date killing server and then it shows Daemon starting and then says Failed.
if i try 2 times back to back i eventually get the Device Serial number.
so then i try PULL command and that works no problem
when i try the PUSH command i get an error that says READ ONLY FILE SYSTEM and it fails.
i'm stuck now
nextelbuddy said:
ok so my Prime boots into APX mode according to windows 7 Device manager. it shows APX not greyed out.
however despite this, in CMD when i type ADB Devices it shows BLANK and of course any adb commands return no device found.
if i let the Prime reboot into its Boot loop, then ADB Composite appears in Device manager.
if i go to CMD and type ADB Devices, it always says ADB Server out of date killing server and then it shows Daemon starting and then says Failed.
if i try 2 times back to back i eventually get the Device Serial number.
so then i try PULL command and that works no problem
when i try the PUSH command i get an error that says READ ONLY FILE SYSTEM and it fails.
i'm stuck now
Click to expand...
Click to collapse
I think its bricked... because from the research Swift and I did on a battery mod, he tried a mod I don't remember what and it ended up in boot loop. ADB won't work because of the boot loop it doesn't stay long enough in a booted state for ADB to send/receive the commands. If your still in your return period try for exchange.
nextelbuddy said:
when i try the PUSH command i get an error that says READ ONLY FILE SYSTEM and it fails.
i'm stuck now
Click to expand...
Click to collapse
The file system will be read only by default. You need to remount /system as read/wrire.
Regards,
Dave
Sent from my GT-N7000 using Tapatalk
Had the same problem back then.
I did a search on the problem at the forum and found this:
"I did this and that worked for me : http://forum.xda-developers.com/show...4&postcount=21"
You need a micro sd and rename a file, easy, poof, fixed.
As far as adb goes
adb remount
or
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
foxmeister said:
The file system will be read only by default. You need to remount /system as read/write.
Regards,
Dave
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Unfortunately i can not remount the system. if i try to remount it says either device not found or error it can not.
its like it never listens long enough..
for example if i type ADB Devices, it will say "ADB Server out of date killing server and then it shows Daemon starting and then says Failed"
if i try that 2-3 times then it will eventually say Devices and list my Serial number.
if i try immediately after that to go to ADB SHELL, it starts and then i type:
adb push original.build.prop /system/build.prop
as soon as i hit enter it says Device not found.
even if i try that command 5 times in a row hoping that it takes one of the times, it does not.
Brollie said:
Had the same problem back then.
I did a search on the problem at the forum and found this:
"I did this and that worked for me : http://forum.xda-developers.com/show...4&postcount=21"
You need a micro sd and rename a file, easy, poof, fixed.
Click to expand...
Click to collapse
i cant look at that link, its truncated. can you post the full link please?
i tried downloading the .15 firmware from Asus site and pasting it on a micro SD card and putting it in the Prime and then booting into recovery mode but it always shows the android laying down with a red triangle.
PM_mobile said:
As far as adb goes
adb remount
or
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
i cant remount, i can shell but if i do that then it says no devices connected.
wow, i royally screwed things up with this stupid build.prop like an idiot.
For the record, once in adb shell it's not adb push anymore..
That'd be
cp /system/original.build.prop /system/build.prop
I doubt this will do you any good, it seems you just can't stay in adb long enough because it reboots.
You don't gave a working custom recovery do you? (like clockwork mod)
I think I've seen people with custom recoveries on their primes.. that'd allow you to adb properly or flash a zip file with your build.prop..
Also, Did you look at this thread?
http://forum.xda-developers.com/showthread.php?t=1514088
They have a few unbrick solutions and something about getting adb to work from recovery. Recovery wouldn't bootloop while you're trying to adb..
aznmode said:
You may be able to go this route and reflash the entire rom if you dont have adb access. From what I understand is you rename the update.zip file to whatever it says in the link to rename to and put on the root of sd card and do the power + volume and go into recovery.
http://forum.xda-developers.com/showthread.php?t=1492887&page=18
the latest asus update can be found here.
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+Prime+TF201&p=20&s=16
Click to expand...
Click to collapse
THIS!!!
i downloaded the latest stock firmware .15 from asus support site. renamed it to
EP201_SDUPDATE.zip and copied to a micdro SD card.
held VOL DOWN + Power and when i saw the white text hit VOL UP twice
and the recovery manager detected the file on the SD card and started flashing.
no more RED triangle android anymore.
im sooo excited this worked and will definitely take more caution in regards to the build.prop file. never realized how much of an integral role it played in the android OS.
thank you very much for all your help and to the others thanks for your help with ADB. even though it didnt work, i played with ADB so much last night and today that i feel much more comfortable with it.
Like me I'm sure many of you were very surprised to log in today, as most have been doing everyday for the past month or so to find that not one, but two methods for obtaining s-off on the DNA were released within minutes of each other. First Revone and then, coincidentally enough, Moonshine was released minutes later. Somebody didn't want somebody else stealing their thunder I'm guessing. I'm just kidding...I'm sure both sides worked extremely hard on their respective methods and deserve mad props for the time spent on this and for waving a middle finger in the face of Verizon. Having said that I have tried both methods and have been unsuccessful so far at each one. I have to pose my questions here because I'm a new member and the development threads are off limits to me.
I tried the Revone Method first and like many were saying in the actual thread, my phone kept auto rebooting after the ./revone.dna -P step. I tried everything I could think of including all of the suggestions from the other users who finally got it to work by trying different things. Has anyone figured out what is causing the auto reboot? There has to be something specific causing this. One thing I have noticed with my phone is that USB Debugging has been very unreliable as of late. It turns itself off and on at random times and a lot of times the box is checked to enable it but it's not on. I don't know if this is playing a role in the process not working for me. I got the "success" message after every step several times but never actually achieved s-off.
I finally gave up on Revone to try Moonshine. I really didn't want to have to fo this route since I don't know a thing about Linux. I decided to go the boot from flash drive route so I downloaded 32 bit Ubuntu 13.04 iso and used universal USB installer to put it on my drive. I am using an external hard drive that is already formatted to fat32. I did NOT format the drive because I didn't think I had to since it was already fat32. Universal USB Installer was successful in putting Ubuntu on the external drive. I then went into my bios and changed the boot sequence to boot from the external drive first but when I rebooted it just loaded up Windows like normal. What am I doing wrong here? I'm running Windows 7 64bit but it was my understanding that this should not be a problem. Do I have to format and/or partition the external hard drive even though it is already fat32 before putting Ubuntu on it?
I'm dying to get one of these methods working but I'm currently stuck. Any newbies like me that can't post in the Development forums have any ideas as to what is going wrong here or would anyone else like to chime in with their own issues? Thanks in advance. I'm sure I'll get there eventually. :good:
Follow this guide for using an external USB device.
Modify the boot sequence like you were doing before, hopefully you'll get in to Ubuntu.
You say you don't have Linux experience, so I'll simplify the process for you:
Once at the desktop, press Control + Shift + T. This will open the Terminal, which is basically the Linux version of Windows' cmd.exe. Once inside, open up Mozilla Firefox (included) by using the side bar, the icon should be there. Download the version of Moonshine for the DNA, and then switch back to the terminal.
Type in these commands:
cd /home/Downloads
tar -zxf moonshine_dlx_2.06.605.1.tgz
sudo ./distiller
Click to expand...
Click to collapse
And then let Moonshine do its thing.
Modify the boot sequence like you were doing before said:
Thank you for the response. I saw in the instructions it says to put the moonshine file in the ~Downloads directory. How do I do that? Also, I think I am going to try the disc method instead. Does it matter if its a cd or dvd? And I never did ask if the version of Ubuntu I had downloaded was compatible with this method. I downloaded Ubuntu 13.04 32bit for use on Windows 7 64bit. Will I have any problems? Thanks again!!
Click to expand...
Click to collapse
Oh and one other thing I forgot to mention regarding the revone method...the directory \data\local\temp did not exist on my device prior to me creating it when I pushed the revone.dna to my phone. Should I have had that directory on my phone already?
Sent from my HTC6435LVW using xda premium
I am in a similar boat. I am trying to use revone as I can't get ahold of linux. I downloaded the sdk and revone, moved adb to my C: with the revone file. Everything goes smoothly until i reach the -P step. Every single time it reboots after saying success. If I try to run the -s 0 -u command after that I get failed to map memory, success, revone failed = -1. If I try the -P command again, I get the same message with error code 2. If I try to reboot the bootloader, I get error device not found. I've been at this for hours, and Jerry from Android central even walked me through it, everything ended up successful ans when the bootloader rebooted, it was still locked and s on. Help please?
I dont even know what command to type into CMD for Revone. how do i push the file I have revone on my desktop downloaded and SDK installed..
Next step is?
Gorilla* said:
I dont even know what command to type into CMD for Revone. how do i push the file I have revone on my desktop downloaded and SDK installed..
Next step is?
Click to expand...
Click to collapse
I moved adb and its two counterparts in a folder named ADB_WIN, in my C: drive. From there, I typed cmd.exe in the search bar, it opened the command box. I typed in adb push revone.dna /data/local/tmp/ ENTER adb shell ENTER cd /data/local/tmp ENTER chmod 755 revone.dna ENTER ./revone.dna -P and that's where my error started coming in. You can try this, not sure if this right, but if its not, hopefully someone will correct me.
Krispenwah said:
Thank you for the response. I saw in the instructions it says to put the moonshine file in the ~Downloads directory. How do I do that? Also, I think I am going to try the disc method instead. Does it matter if its a cd or dvd? And I never did ask if the version of Ubuntu I had downloaded was compatible with this method. I downloaded Ubuntu 13.04 32bit for use on Windows 7 64bit. Will I have any problems? Thanks again!!
Click to expand...
Click to collapse
32 bit should work fine. You need a DVD because a CD is too small. ~/Downloads directory is just the current user's downloads folder. So most likely it would get downloaded to there anyway.
Sent from my DNA using Tapatalk 2
"1. Download revone (above) and push it to your device: adb push revone.dna /data/local/tmp/"
How is this done? I have no idea how to push to the DNA. Anybody help? Thanks
michaelrager said:
"1. Download revone (above) and push it to your device: adb push revone.dna /data/local/tmp/"
How is this done? I have no idea how to push to the DNA. Anybody help? Thanks
Click to expand...
Click to collapse
That's the command you use, adb push. Use it in a terminal. So..assuming windows use explorer to go yo where you downloaded the files and have revone.dna then hold shift and right click, choose open prompt here then type
adb push revone.dna /data/local/tmp
If it complains about command not found for adb add the adb.exe and its libraries to the same folder then try again.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
That's the command you use, adb push. Use it in a terminal. So..assuming windows use explorer to go yo where you downloaded the files and have revone.dna then hold shift and right click, choose open prompt here then type
adb push revone.dna /data/local/tmp
If it complains about command not found for adb add the adb.exe and its libraries to the same folder then try again.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
Thanks for the quick response. I don't have that option when i shift and right click, I only have "open with" Any Ideas?
michaelrager said:
Thanks for the quick response. I don't have that option when i shift and right click, I only have "open with" Any Ideas?
Click to expand...
Click to collapse
Hold shift while you right click, can't be on a file, just someplace in the explorer, no folders, etc clicked on, someplace blank.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
Hold shift while you right click, can't be on a file, just someplace in the explorer, no folders, etc clicked on, someplace blank.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
Got it. I misunderstood what you meant thanks! However, I am getting that error.
I got the error 'adb' is not recognized as an internal or external command, operable program or batch file. Can you elaborate on what to fix? Thanks Again!
michaelrager said:
Got it. I misunderstood what you meant thanks! However, I am getting that error.
I got the error 'adb' is not recognized as an internal or external command, operable program or batch file. Can you elaborate on what to fix? Thanks Again!
Click to expand...
Click to collapse
add adb.exe to your command, instead of just adb
Gorilla* said:
add adb.exe to your command, instead of just adb
Click to expand...
Click to collapse
Thanks, but the same type of error came up.
michaelrager said:
Thanks, but the same type of error came up.
Click to expand...
Click to collapse
Put revone.dna in the same folder that has fastboot and adb then try
Sent from my HTC6435LVW using xda premium
Krispenwah said:
Put revone.dna in the same folder that has fastboot and adb then try
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
That worked I got daemon started successfully. Then it says error: device not found
I am in debugging mode.
Any help is much obliged. Thanks!
michaelrager said:
That worked I got daemon started successfully. Then it says error: device not found
I am in debugging mode.
Any help is much obliged. Thanks!
Click to expand...
Click to collapse
Try 'adb devices' and see if it recognizes your phone. Do you have usb debugging enabled? If so toggle it off and then back on while the phone is plugged in then wait about 10-15 seconds and try 'adb devices' again to see if its recognized now
Krispenwah said:
Try 'adb devices' and see if it recognizes your phone. Do you have usb debugging enabled? If so toggle it off and then back on while the phone is plugged in then wait about 10-15 seconds and try 'adb devices' again to see if its recognized now
Click to expand...
Click to collapse
Got it!
* daemon started successfully *
3372 KB/s (645920 bytes in 0.187s)
Is it all set so I can move on to the next step?
michaelrager said:
Got it!
* daemon started successfully *
3372 KB/s (645920 bytes in 0.187s)
Is it all set so I can move on to the next step?
Click to expand...
Click to collapse
Yeah looks like the file pushed successfully. Now u do "adb shell" then "cd data/local/tmp" then "chmod 755 revone.dna" ....and so forth. Make sure ur adding the extension ".dna" to revone (revone.dna) each time u type it. If u just put revone it won't work ull just get an error
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
Hi guys,
EDIT: See the last posts - I have figured this out, and tried to include helpful information, if you are having this problem too.
Firstly please accept my apologies if this has been answered already. I have searched the forum, and the Internet, and cant find specific instructions, or a guide that I can follow with any success.
I stupidly deleted system files from my Kindle, but now I have purchased a fastboot cable, and I'am able to get it into fastboot mode.
I have correctly installed the ADB Drivers, and the device is now recognized by my Windows 7 Device Manager. It shows 'Android ADB Interface'.
I would guess that I need to flash the entire Kindle, but I'm unsure of how to do this, as I cannot seem to access the device at all. It currently loops when booting, giving me no time to see it as external storage via My Computer.
Please would someone more versed in this, guide me specifically through how to get myself back up and running again? I would be forever greatful.
I have SDK and JDK installed, but do not have the knowledge I need to learn how to use them properly.
Thanks so much in advance.
urbainmenace said:
Hi guys,
Firstly please accept my apologies if this has been answered already. I have searched the forum, and the Internet, and cant find specific instructions, or a guide that I can follow with any success.
I stupidly deleted system files from my Kindle, but now I have purchased a fastboot cable, and I'am able to get it into fastboot mode.
I have correctly installed the ADB Drivers, and the device is now recognized by my Windows 7 Device Manager. It shows 'Android ADB Interface'.
I would guess that I need to flash the entire Kindle, but I'm unsure of how to do this, as I cannot seem to access the device at all. It currently loops when booting, giving me no time to see it as external storage via My Computer.
Please would someone more versed in this, guide me specifically through how to get myself back up and running again? I would be forever greatful.
I have SDK and JDK installed, but do not have the knowledge I need to learn how to use them properly.
Thanks so much in advance.
Click to expand...
Click to collapse
what is the fastboot cable? where can I get it? can a normal usb cable do the job?
goodayoo said:
what is the fastboot cable? where can I get it? can a normal usb cable do the job?
Click to expand...
Click to collapse
You definitely need the fastboot cable to push files through the ADB Interface dude. You can buy one for dirt cheap on EBay. Then all you do is simply plug it into your PC and Kindle, and it should put the Kindle straight into Fastboot mode.
Then you need to install the ADB Drivers for the Kindle.
From there, I'm stuck I'm afraid.
urbainmenace said:
You definitely need the fastboot cable to push files through the ADB Interface dude. You can buy one for dirt cheap on EBay. Then all you do is simply plug it into your PC and Kindle, and it should put the Kindle straight into Fastboot mode.
Then you need to install the ADB Drivers for the Kindle.
From there, I'm stuck I'm afraid.
Click to expand...
Click to collapse
OK，I think I'm gonna get one and give it a try. the only way to fix this brick is in the ADB Interface I'm sure. though I also don't know How to do.
I've finally figured out how to get ADB up and running, and how to start command prompt. I found this link helpful:
developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing
If anyone needs help pushing files through ADB, I recommend that link!
Do the following to detect your Kindle Fire tablet through ADB:
Open a command prompt window.
Change directory to your Android SDK platform-tools directory. - To do this, find out where SDK is installed on your PC. Copy the path.
Type cd in command prompt, then space, then paste the directory path. EG, C:\Users\Administrator\sdk\platform-tools
Hit enter, and the command line will change to read C:\Users\Administrator\sdk\platform-tools.
Run the following commands and confirm that the serial number for your Kindle Fire tablet appears in the list of devices.
adb kill-server
adb start-server
adb devices
Then follow the rest of the guide. I think all you need to to do, is push a system update through, by putting the file in the tools folder of SDK. This should make the device update, and put back any critical system files that you had previously deleted.
Now I'm just having issues with it finding the device, so I'm going to charge the Kindle for a few hours, and then try it again.
:good:
urbainmenace said:
I've finally figured out how to get ADB up and running, and how to start command prompt. I found this link helpful:
developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing
If anyone needs help pushing files through ADB, I recommend that link!
Do the following to detect your Kindle Fire tablet through ADB:
Open a command prompt window.
Change directory to your Android SDK platform-tools directory. - To do this, find out where SDK is installed on your PC. Copy the path.
Type cd in command prompt, then space, then paste the directory path. EG, C:\Users\Administrator\sdk\platform-tools
Hit enter, and the command line will change to read C:\Users\Administrator\sdk\platform-tools.
Run the following commands and confirm that the serial number for your Kindle Fire tablet appears in the list of devices.
adb kill-server
adb start-server
adb devices
Then follow the rest of the guide. I think all you need to to do, is push a system update through, by putting the file in the tools folder of SDK. This should make the device update, and put back any critical system files that you had previously deleted.
Now I'm just having issues with it finding the device, so I'm going to charge the Kindle for a few hours, and then try it again.
:good:
Click to expand...
Click to collapse
good to hear that! I hope you can tell me how to push the system folder into the fire hdx via ADB ,I got a thor-amazon-os-13.3.1.0.zip file.
goodayoo said:
good to hear that! I hope you can tell me how to push the system folder into the fire hdx via ADB ,I got a thor-amazon-os-13.3.1.0.zip file.
Click to expand...
Click to collapse
In command prompt, there is an ADB push command, so I think all you do is type that, then the path of the file.
To list all the commands you can use, change command prompt to your platform-tools folder within SDK, type ADB in command prompt, and it will give you all the options.
You'll need to unzip the update file first I think.
:good:
bootlooped, adb runs some commands
urbainmenace said:
In command prompt, there is an ADB push command, so I think all you do is type that, then the path of the file.
To list all the commands you can use, change command prompt to your platform-tools folder within SDK, type ADB in command prompt, and it will give you all the options.
You'll need to unzip the update file first I think.
:good:
Click to expand...
Click to collapse
Working with the HDX 8.9.
I think I have deleted some of the system files also. I was reloading a safestrap backup and rebooted but the backup had failed to complete. I don't know what may be missing from the system files and would like to push the system files onto the device.
Right now I get a gray kindlefire screen for about 90 seconds, during which I have adb access, then it goes to the color kindlefire screen and asks if I want to Restore to Factory Defaults or reboot. I finally subjected it to the Restore to Factory Defaults, but that just wiped the cache and data partitions, I don't see where it did anything to the system files. It did not change my adb access.
In adb I can push files to some locations but others say: failed to copy ....: Read-only file system.
I cannot run shell commands
# adb shell
soinfo_link_image(linker.cpp:1617): could not load library "/vendor/lib/libNimsWrap.so" needed by "/system/bin/sh"; caused by load_library(linker.cpp:745): library "/vendor/lib/libNimsWrap.so" not foundCANNOT LINK EXECUTABLE
I was working in Windows 8.1 but have switched to Suse Linux but the results are the same so far.
I have the stock system files but I am not sure how to push them to the device, if it can be done, while the device is trying to reboot.
fastboot
I can put the HDX in Fastboot mode with the adb command. But when I try to pass commands to the HDX I get:
< waiting for device >
and I have to Ctrl-c to stop the process.
Do the fastboot commands only work if you have a fastboot cable???
Since you guys are using adb checkout these threads:
http://forum.xda-developers.com/showthread.php?t=2530623 Factory Reset
http://forum.xda-developers.com/showthread.php?t=2636817 [Video Tutorial] GAPPS + Amazon from Cpasjuste
http://forum.xda-developers.com/showthread.php?t=2638241 How to un-boot-loop (another way)
http://forum.xda-developers.com/showthread.php?t=2598577 [TUT/FIX] Fix the Boot Loop on Kindle Fire HDX 7"
This guy may also be able to help, forum member: GSLEON3 Post #16
http://forum.xda-developers.com/showthread.php?t=2580989&page=2