Database Users

I9020T - How to ROOT?!

Hi!
I'm about to put my SNS up where the sun don't shine..
I've followed this guide:
http://forum.xda-developers.com/showthread.php?t=895545
But when i come to part 2 i have some problems.. The Command Prompt hangs at < Waiting for Device > and nothing happens from here.
All drivers are installed as they should. What would be wrong?
Phones info:
Baseband: I9020XXKD1
Version: GRJ22
Kernel: 2.6.35.7-ge382d80
[email protected] #1
Please help my phone to survive

What operating system are you using? If you're using windows going to device manager and see what it says for android devices.
Sent from my Nexus S 4G using XDA Premium App

cteneyck said:
What operating system are you using? If you're using windows going to device manager and see what it says for android devices.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
I'm using Windows 7 x64 Ultimate - And it says what it should:
When phone is turned on normally:
Android Composite ADB Interface
Phone in Fast-Boot:
Android Bootloader Interface
Nothing should be wrong there..

i would try another usb cable. they have been know to not work. also make sure that your android sdk has been updated fully before starting step 2

Installing PDAnet had proven time and time again to be the easiest and most foolproof method of getting the correct up to date drivers installed. Please try that. Install PDAnet on your machine and follow the prompts. Then try again.
Sent from my Nexus S using XDA App

matt2053 said:
Installing PDAnet had proven time and time again to be the easiest and most foolproof method of getting the correct up to date drivers installed. Please try that. Install PDAnet on your machine and follow the prompts. Then try again.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
truth!
here is their site http://www.junefabrics.com/android/index.php install the free version onto your computer then just follow the on screen instructions. itll install the proper driver for you.

Tried another cable, and using PDAnet - still hangs at Waiting for device...

Does ADB work?
Sent from my Nexus S using XDA App

I am having same problem, so I can relate, but not unhappy with stock. I also can not find anything wrong even on device manager everything looks like out ought to work.
I tried adb fastboot devices and my phone is supposed to show up, but didn't. You might try yours as well, probably get same result.
Makes me think still a problem with the driver.
Sent from my Nexus S 4G using XDA App

matt2053 said:
Does ADB work?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
No idea, i actually don't know what ADB actually is and does?

Hansen1142 said:
No idea, i actually don't know what ADB actually is and does?
Click to expand...
Click to collapse
It is a Command Line Interface application that comes packaged with the Android SDK, just like fastboot. ADB is used to interface with your device while it is booted normally, and fastboot interfaces with your device at the bootloader level.
With your phone booted up into Android, plug in USB and do "fastboot devices". What happens?
But before you do that, let me ask: are you sure when you were having trouble with fastboot that you had the phone in bootloader? You have to hold volume up + power until you see a screen that says FASTBOOT MODE at the top with a lot of other text. You can only use fastboot commands such as "fastboot oem unlock" when the phone is in bootloader.

matt2053 said:
It is a Command Line Interface application that comes packaged with the Android SDK, just like fastboot. ADB is used to interface with your device while it is booted normally, and fastboot interfaces with your device at the bootloader level.
With your phone booted up into Android, plug in USB and do "fastboot devices". What happens?
But before you do that, let me ask: are you sure when you were having trouble with fastboot that you had the phone in bootloader? You have to hold volume up + power until you see a screen that says FASTBOOT MODE at the top with a lot of other text. You can only use fastboot commands such as "fastboot oem unlock" when the phone is in bootloader.
Click to expand...
Click to collapse
I am sure i'm in fastboot, and not Android system
The ADB finds a Device - Screenshot added..

If you are not sure what adb is, I am wondering what method you are using to root?
Sent from my Nexus S 4G using XDA App

q711179 said:
If you are not sure what adb is, I am wondering what method you are using to root?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I am following the guide i'm linking to in first post

Sorry, but using phone and didn't catch the first post after reading few of the others. Since we having same problem I will try it tuesday, which is my next day off work and let you know how out goes.
If you do get this resolved, let me know how you did out.
Sent from my Nexus S 4G using XDA App

Possible problem
So I checked on my device manager and the android device driver says; Android ADB Interface, rather than Android Bootloader Interface.
Anyone that can help me change it to the correct one as I can use ADB to get phone to bootloader but when I type bootloader devices my phone is not found.
Thanks in advance.

Figured it out (maybe lucky guess)
I moved a copy of bootloader from tools folder to platform tools then opened a terminal from that window and it worked.
Bootloader unlocked and on way to full root.

Accidentally wiped everything. No adb during recovery or bootloader.

I'm on TWRP 2.3.3.0., and my computer is W8 Pro. I've searched but most people seem to be able to get adb working during the bootloader at least, but not for me. I've tried sideloading a zip through the command prompt (and picking the adb sideload option in TWRP) but it tells me that adb is not recognized. I've tried using the Nexus Root Toolkit to restore a backup I have on my computer, but, yeah, no adb. I was wondering if disabling driver signature enforcement was temporary, so I went through the menus and disabled it again on my computer. I've used the cable/port that I rooted it with but I've also used different cables and ports as well. Why isn't this working? Am I bricked?

Have you tried jromflasher for nexus 7? With that tool you can wipe your system, upload ROM, temporary load custom recovery, and flash the ROM.
Sent from my Nexus 7 using Tapatalk HD

xbox1513 said:
Have you tried jromflasher for nexus 7? With that tool you can wipe your system, upload ROM, temporary load custom recovery, and flash the ROM.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Error 103. I think my device needs to be booted into an actual ROM.
I thought that maybe the drivers from plugging my phone in were interfering, so I used the Nexus Root Toolkit again, and went through the driver installation for a second time, deleting all the old ADB drivers and such. Well, when I tried to install the RAW drivers, I get "Windows was unable to install your unknown device," and basically it could not find the driver software and to check the company website and so on. Did I just dig myself into a deeper hole? Gah! I wish I could remember which wipe option deleted sdcard so I know to never do it again.

OP is using Win8 - might want to try to do it with a PC or laptop running Win7 or Vista OS and start fresh by loading the drivers and/or use Jromflasher - borrow a friend/neighbor's PC to see if it can be jump started, assumed that s/he cannot get it to boot into Fastboot and/or Recovery as the file systems are likely corrupted. (I have an old/aging laptop running Windows XP SP3 that's set aside for fixing often the impossible)
Otherwise, it might be time for an RMA to get it repaired by Google/Asus and/or exchange - it could cost $$ if they determined that the warranty has been "compromised" ...

You know you won't get adb while in bootloader? You need fastboot.
Sent from my SGH-I777 using xda premium

korockinout13 said:
You know you won't get adb while in bootloader? You need fastboot.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
It says "fastboot mode" on the bootloader.

Letitride said:
OP is using Win8 - might want to try to do it with a PC or laptop running Win7 or Vista OS and start fresh by loading the drivers and/or use Jromflasher - borrow a friend/neighbor's PC to see if it can be jump started, assumed that s/he cannot get it to boot into Fastboot and/or Recovery as the file systems are likely corrupted. (I have an old/aging laptop running Windows XP SP3 that's set aside for fixing often the impossible)
Otherwise, it might be time for an RMA to get it repaired by Google/Asus and/or exchange - it could cost $$ if they determined that the warranty has been "compromised" ...
Click to expand...
Click to collapse
Thanks. I'll try this later tonight. Would they RMA in this scenario, even though it is my fault? Assuming I can't get it working.

I don't understanding why you would RMA? You can get into twrp right? So you can still flash ROMs and whatnot. Just need to get adb installed on cpu

You can also try "disable driver signature check" on advanced reboot on windows 8.
Sent from my Nexus 7 using Tapatalk HD

Bullonie said:
It says "fastboot mode" on the bootloader.
Click to expand...
Click to collapse
Well....use fastboot then.
You should have done some reading before you started flashing ROM's. You dont seem to even know what fastboot is.

Have you tried downloading the android sdk from Google and installing their usb driver?
Sent from my Nexus 7 using XDA Premium HD app

Adb works in recovery and in Android OS, only fastboot works in the bootloader. Installing Windows 8 messed it up for me, but I simply grabbed the Nexus 7 driver from ASUS'S website. I suggest you read and learn how to use fastboot.
Sent from my Nexus 7 using Tapatalk HD

Soft brick but with no adb connection on bootloader

Ok, tired of waiting for the OTA KitKat update for my Nexus 7 2012 tablet, I downloaded the OTA update and sideloaded it with adb. Got a status 7 error and now it's stuck on a bootloop. Thing is, my Windows 8 laptop won't recognize the device anymore (code 43 error on device manager) when on recovery or bootloader. There's even no way to instal google's usb drivers or anything because it says the device malfunctioned. I downloaded the factory image but, obviously, can't sideload it or do anything with it.
Please give me a hand with this, I'm really desperate.

More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app

nobody_nowhere said:
More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Sorry, wasn't sure what you needed. The bootloop esentially goes from recovery to off and then to recovery again. I am able to go to fastboot normally (power and volume down when off).
Wanting to root the device a while ago, I unlocked it and rooted it whitout issues. Since the 4.3 update though, it was a little more difficult to root so having no time to research I just left it at that. That's all that was done to the Nexus 7. No Custom Recovery, no ROM, no nothing. Now, waiting for 3 weeks for KitKat, decided to sideload the OTA update (I did check the version was my device's version) the status 7 error appeared and all hell broke loose with the computer not recognizing the device.

Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app

Duplicate post. Please erase.

nobody_nowhere said:
Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Yeah, that's what relaxes me a bit, but I can't seem to fix it for 20 hours straight. I use this for studying.

Well, I suggest using another computer (a friend's or relatives') or installing a Linux distro like ubuntu. Oses other than Windows usually don't have such problems. I suggest you download something called adb gui which as I recall did a pretty fine job of 're installing the drivers for me.
But then, please do correct me if I'm wrong... I think that you must first use the device on adb and get the drivers installed and then only can you use it by the fastboot interface.
Sent from my GT-S5570 using xda app-developers app

I used Wug nexus root toolkit to install drivers (windows 8.1) there are clear instructions (if you click manual or something similar) how to get drivers to work.

Yeah, actually I did use the toolkit when I was trying to update to KitKat. Thing is, it doesn't work since the bricking occurred.
Yeah, I'll try on another pc, and I'll keep you posted.
Thanks
Sent from my Nexus 4 using xda app-developers app

I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.

Johnson90512 said:
I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.
Click to expand...
Click to collapse
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app

nobody_nowhere said:
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?

Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
It pretty much cancels out any problems with drivers.
It is easy to do.
It takes 5 minutes to boot up and test? Try it for yourself
Sent from my Nexus 5

Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app

nobody_nowhere said:
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
I appreciate the advice, I will give it a shot this evening, and let you know if this works. I'm sure that it will.

Alright, so I got SDK up and running on Linux! It was a little bit of a pain, but it installed just fine. Once I got it all installed I was able to see the nexus 7 through fastboot! From there I was able to reinstall the bootloader. Then was able to get to recovery to do an adb push to get a rom of 4.4 on to it. 4.4 installed just fine. All problems are fixed Good suggestions guys!

Help Extracting Data

I don't know how, but my S4's screen broke internally (Through pressure, according to AT&T saying they are "pressure cracks").
Beyond that
I upgraded to the S5 (Knowing if I get a replacement S4, it's likely to be upgraded which I don't want so might as well get the S5), and I would love to get my pictures and stuff back without having to repair the S4 screen. The only problem is that it has a pattern lock on it. I do not think it had USB debugging on it, but it was rooted with SS. Kies and Windows don't completely recognize the device, only that it's plugged in. Need help on getting the stuff off. Please help!!

If usb debugging is off there's not much you can do. You could try to boot into recovery and the use adb to pull files off. Try "adb devices" and see if it regonizes your device. If it does then use "adb pull/sdcard/ c:\sdcard"
Sent from my Nexus 5

jd1639 said:
If usb debugging is off there's not much you can do. You could try to boot into recovery and the use adb to pull files off. Try "adb devices" and see if it regonizes your device. If it does then use "adb pull/sdcard/ c:\sdcard"
Sent from my Nexus 5
Click to expand...
Click to collapse
Boot to stock recovery or SS recovery? Also, can you use the volume keys on SS? I haven't tried it, so if you can I could use screenshots so I can guide myself through and mount USB. Or do that through the stock recovery but I don't know if it has that option. Other than that, just booting into either recoveries doesn't detect the device....

Bumppp?

SkyAttacksX said:
Bumppp?
Click to expand...
Click to collapse
Try booting into ss and then use adb pull /sdcard/*·* c:\sdcard If it works it'll take a long time
Edited
Sent from my Nexus 5

jd1639 said:
Try booting into ss and then use adb pull /sdcard/*·* c:\sdcard If it works it'll take a long time
Edited
Sent from my Nexus 5
Click to expand...
Click to collapse
No devices attached....

SkyAttacksX said:
No devices attached....
Click to expand...
Click to collapse
Sorry man, I'm out of ideas.
Sent from my Nexus 5

You could probably send it off to mobiletechvideos who could probably pull the data off.
Brain fact! What about using Heimdall to do a partial flash. You might be able to get past that lockscreen then.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Red_81 said:
You could probably send it off to mobiletechvideos who could probably pull the data off.
Brain fact! What about using Heimdall to do a partial flash. You might be able to get past that lockscreen then.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Heimdall? Sorry for being a noob, I only had the S4 from September xD

Heimdall is an open source alternative to Odin. The MAC guys are forced to use it since Odin will not run on a MAC.
The part I was curious about is why your device does not mount as a hard drive when you plug it into your PC. Is that because of the lockscreen? I never use once personally.
It sounds like you may just have driver issues. You could even try downloading the Ubuntu LiveCD, booting to that, and then plug in your phone to see if it appears.

Red_81 said:
Heimdall is an open source alternative to Odin. The MAC guys are forced to use it since Odin will not run on a MAC.
The part I was curious about is why your device does not mount as a hard drive when you plug it into your PC. Is that because of the lockscreen? I never use once personally.
It sounds like you may just have driver issues. You could even try downloading the Ubuntu LiveCD, booting to that, and then plug in your phone to see if it appears.
Click to expand...
Click to collapse
Well, it does mount. The problem is that no files are shown since it has a lockscreen... And alright I think http://forum.xda-developers.com/showthread.php?t=2374441 that's it right?

[Q] Cracked Screen Nexus 4 Screen, How to recover my data files?

Hi all,
I've got my old Nexus 4 Device out but the only issue is I dropped it face down on a concrete floor, The entire screen is smashed. The LCD works fine, but is unresponsive to touch. I've tried accessing it through my computer but because I have a lock on it, it won't let me access the files.
It is rooted, but I'm not 100% with as my friend did it for me. He's away at the moment so can't really help me.
I had titanium backup on it. Does this mean anything?
Also I've seen the method of people wiping the cache. However this doesn't work for me as I have a different screen appear TWRP, Team Win Recovery Project, which also requires a slide to unlock....
Is there any other possible methods of obtaining my data?
If there isn't thats not too much of a problem, and Im not too concerned about losing the data, so Im open to experimentation!
Cheers guys!

Few months back I had a similar problem with my nexus 7 . Easy way is to connect a USB hub and a mouse via OTG to unlock the device and then connect it to a computer .
Let me know if it works.
Sent from my XT1022 using XDA Free mobile app

chaithanyaprasad said:
Few months back I had a similar problem with my nexus 7 . Easy way is to connect a USB hub and a mouse via OTG to unlock the device and then connect it to a computer .
Let me know if it works.
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
Okay, and this would work?
An OTG cable looks like this right?:
http://www.trademe.co.nz/computers/...ssories/chargers-cables/auction-789171735.htm
Cheers

Yes, that's the OTG cable.
In my case ,I have connected a keyboard and mouse then with the mouse I have unlocked the pattern lock.
You can then take a backup with PC or a flash drive
Sent from my XT1022 using XDA Free mobile app

The N4 doesn't support OTG unless you're running a kernel that supports it (stock kernel doesn't have it).
When I cracked my screen, I used adb to send tap and swipe commands. Of course, you need to to have previously enabled USB debugging...

0mnom said:
Hi all,
I've got my old Nexus 4 Device out but the only issue is I dropped it face down on a concrete floor, The entire screen is smashed. The LCD works fine, but is unresponsive to touch. I've tried accessing it through my computer but because I have a lock on it, it won't let me access the files.
It is rooted, but I'm not 100% with as my friend did it for me. He's away at the moment so can't really help me.
I had titanium backup on it. Does this mean anything?
Also I've seen the method of people wiping the cache. However this doesn't work for me as I have a different screen appear TWRP, Team Win Recovery Project, which also requires a slide to unlock....
Is there any other possible methods of obtaining my data?
If there isn't thats not too much of a problem, and Im not too concerned about losing the data, so Im open to experimentation!
Cheers guys!
Click to expand...
Click to collapse
Since you have twrp installed you can pull files using adb
In a cmd prompt
adb pull /sdcard/
You might need to install adb and drivers first, koush universal drivers work well.

DrFredPhD said:
Since you have twrp installed you can pull files using adb
In a cmd prompt
adb pull /sdcard/
You might need to install adb and drivers first, koush universal drivers work well.
Click to expand...
Click to collapse
Sorry, I have no idea of what you are talking about. I'm a relative newbie when it comes to all this rooting and roms and stuff as my friend did this for me, but Im willing to learn?
Id be more than happy to continue this conversation through PM?
Cheers,

0mnom said:
Sorry, I have no idea of what you are talking about. I'm a relative newbie when it comes to all this rooting and roms and stuff as my friend did this for me, but Im willing to learn?
Id be more than happy to continue this conversation through PM?
Cheers,
Click to expand...
Click to collapse
Boot into twrp, then on your pc run the commands drfred said. Before you do that Google 15 second adb install. Install that
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Boot into twrp, then on your pc run the commands drfred said. Before you do that Google 15 second adb install. Install that
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Okay, so did the 15 second install, couldnt get past step 3 however. For some reason when I pressed y, it would just quit out of it.
1. Run it (Require administrator privileges)
2. Press Y/Yes to install ADB and Fastboot or N/No to skip
3. Press Y/Yes to install ADB system-wide or N/No for current user only
4. Press Y/Yes to install Drivers or N/No to skip
5. Continue Driver installation
6. 15 seconds passed - finished!
But Im assuming its done? I booted my phone into recovery mode, and it comes up with the TWRP screen. I've plugged it in. Now do I just go into cmd and literally type in 'adb pull /sdcard/'?
Or is there added extras in there?
Cheers,

So I tried it out, but I don't think anything happened. How do I tell?
I ran that command, and it just gave me a huge message, I read through a bit of it, and I recognised the device commands, but not sure what message I should be receiving?
Cheers,

If you get a big message with all the adb options then I think you must be typing the command slightly wrong. The output should be a list of your files as they transfer.
If you run the command right but the driver or something else is wrong you'll get an error message eg. no device or device offline.