Database Info

thoughts on RC30..whos gonna reject it?

i hope it doesnt force itself on the phone..

cookzitall said:
i hope it doesnt force itself on the phone..
Click to expand...
Click to collapse
Just don't let it force itself on the phone
If you want to disable OTA updates, you can remount your system folder, and delete /system/app/Updater.apk and /system/app/Updater.odex
I've done that on my own phone with no negative effects (so far). I'm fairly sure that should disable any OTA updates from being installed.
Once it does come out, I plan on downloading it (onto my computer), and giving it a good going over. I'll yank out anything that looks like it will disable my root access, and then resign it with the test keys and load it onto the phone using a modified recovery tool.

JesusFreke said:
Just don't let it force itself on the phone
If you want to disable OTA updates, you can remount your system folder, and delete /system/app/Updater.apk and /system/app/Updater.odex
I've done that on my own phone with no negative effects (so far). I'm fairly sure that should disable any OTA updates from being installed.
Once it does come out, I plan on downloading it (onto my computer), and giving it a good going over. I'll yank out anything that looks like it will disable my root access, and then resign it with the test keys and load it onto the phone using a modified recovery tool.
Click to expand...
Click to collapse
Ditto my good man.
We don't have to reject it per se any OTA "official" update. We just have to modify it and load it. It will have benefits to update, just not completly to Google's standards

can some one please help..
in the "how to get root" thread i asked a question..can some one help me out...thank u

JesusFreke said:
Once it does come out, I plan on downloading it (onto my computer), and giving it a good going over. I'll yank out anything that looks like it will disable my root access, and then resign it with the test keys and load it onto the phone using a modified recovery tool.
Click to expand...
Click to collapse
Details? I was under the impression the retail bootloader wouldn't accept any keys except tmob/google's.
With root though its no biggie to just install the update manually.

well who ever does accept this update please make not of the url it's calling so those of us that aren't can manually grab it. assuming this will still be an option

cookzitall said:
i hope it doesnt force itself on the phone..
Click to expand...
Click to collapse
It sounds like the current state of affairs is not safe. Everything typed on the phone is also submitted to a root shell. It is just a matter of time before I inadvertently type something that damages the filesystem.

wolfgangrupprecht said:
It sounds like the current state of affairs is not safe. Everything typed on the phone is also submitted to a root shell. It is just a matter of time before I inadvertently type something that damages the filesystem.
Click to expand...
Click to collapse
So start each reboot by typing "kill 26"

Disconn3ct said:
So start each reboot by typing "kill 26"
Click to expand...
Click to collapse
That won't help, as it's respawned by init when it dies. Maybe kill -STOP 26 would work, but I haven't verified that.

jimparis said:
That won't help, as it's respawned by init when it dies. Maybe kill -STOP 26 would work, but I haven't verified that.
Click to expand...
Click to collapse
Nope
Tried kill -STOP from adb shell, then "<cr>sleep 90<cr>" and ps showed 'sleep' running. (Sure, I could use 'reboot' but thats just a pita.)

has anyone thought to type "exit" and see if that terminal closes?

Darkrift said:
has anyone thought to type "exit" and see if that terminal closes?
Click to expand...
Click to collapse
it does but a new one is automatically spawned, so..

there are a new terminal emulator in the market that close with exit and you can do the same .
Disconn3ct said:
it does but a new one is automatically spawned, so..
Click to expand...
Click to collapse

satru said:
there are a new terminal emulator in the market that close with exit and you can do the same .
Click to expand...
Click to collapse
we are talking about the "invisible" ghost terminal that is open on the G1 by default, not one you install and run.

Can somebody explain to me why you woudnt want to update to rc30?

donutman said:
Can somebody explain to me why you woudnt want to update to rc30?
Click to expand...
Click to collapse
rc30 prevents root access. if you don't know why you want root, you prolly don't

JesusFreke said:
Just don't let it force itself on the phone
If you want to disable OTA updates, you can remount your system folder, and delete /system/app/Updater.apk and /system/app/Updater.odex
I've done that on my own phone with no negative effects (so far). I'm fairly sure that should disable any OTA updates from being installed.
Once it does come out, I plan on downloading it (onto my computer), and giving it a good going over. I'll yank out anything that looks like it will disable my root access, and then resign it with the test keys and load it onto the phone using a modified recovery tool.
Click to expand...
Click to collapse
You are awesome. Thanks and God bless you!

bennekl said:
You are awesome. Thanks and God bless you!
Click to expand...
Click to collapse
Wondering if Google guys are cursed him already

i keep getting a pop up saying that there i an update ready for the hone or something like that. is that the new update trying to come in. i just keep canceling it

The Great NY said:
i keep getting a pop up saying that there i an update ready for the hone or something like that. is that the new update trying to come in. i just keep canceling it
Click to expand...
Click to collapse
Hack it now or never, it will eventually apply the patch anyway.

[Q] Rebooting to Bootstrap

I have been trolling the forums for awhile and I never post but this is something that I have not been able to come across. Why after I used the bootstrap app and load into the recovery menu that now every time I go to reboot my phone I automatically go into the recovery menu even after a successful boot? Hope I worded that right. Please help and thank you!!
just realized I am in the theme section. Can this be moved to the appropriate board. THANKS!!

That's the way it works, it hijacks the bootloader, trust me its a good thing. Bootloop, battery pull, recovery, restore backup. Several times I've been glad it works that way.
Sent from my DROIDX using XDA App

Wait. I have a normal reboot. Maybe mine is messed up?

Yeah I got that but I thought it was only if I pulled the battery after it bootlooped. It does it every reboot except after I flashed a "rom", but I didn't like the rom so I reverted back to stock. I mean its awesome to have the security blanket but it can also be a bad thing if my 14 yo cousin gets ahold of my phone then formats my system an then reboots. Thanks for the help by the way.
Sent from my DROIDX using XDA App

The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
-Z

If you want to remove bootstrap, you can do SBF flash, which I did several times and it perfectly works.

Zaphod-Beeblebrox said:
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
-Z
Click to expand...
Click to collapse
Ok I understand completely I knew the process but did not quite understand. Now the last question, is the only way to remove it to flash or can I use a file manager to remove it?
Oh and thanks for the help by the way.
UPDATE:
So I think I found it.
Unroot and Remove Recovery Via RootExplorer

jkpair said:
Ok I understand completely I knew the process but did not quite understand. Now the last question, is the only way to remove it to flash or can I use a file manager to remove it?
Click to expand...
Click to collapse
You can just delete it with a file manager (I am not sure about the permissions though .. you may need rootexplorer?)
I generally just do things like that from adb shell.
I KNOW I can delete it that way

Zaphod-Beeblebrox said:
You can just delete it with a file manager (I am not sure about the permissions though .. you may need rootexplorer?)
I generally just do things like that from adb shell.
I KNOW I can delete it that way
Click to expand...
Click to collapse
so for adb shell it would be something like:
Code:
adb shell
cd /system/bin
rm -r hijack
If thats right I won't try unless I know for sure. I don't know why but I have just got into a habit of googling after I ask. Lol I think this is it: Easy way to remove Koush's recovery?
So the logwrapper is the main file that matters not the hijack file and the original logwrapper was renamed to logwrapper.bin so I just replace Koush's recovery logwrapper with the previous one by copying over it.
Once again thanks for the help. Seems the answer is always 42.

jkpair said:
so for adb shell it would be something like:
Code:
adb shell
cd /system/bin
rm -r hijack
If thats right I won't try unless I know for sure. I don't know why but I have just got into a habit of googling after I ask. Lol I think this is it: Easy way to remove Koush's recovery?
So the logwrapper is the main file that matters not the hijack file and the original logwrapper was renamed to logwrapper.bin so I just replace Koush's recovery logwrapper with the previous one by copying over it.
Once again thanks for the help. Seems the answer is always 42.
Click to expand...
Click to collapse
I'm sorry, I misunderstood you goal here. I thought you wanted to keep the recovery, just fix it so it didn't come up on each reboot. If you are looking to completely remove the recovery, then I yes, I would follow the directions in the post you referenced, not the code section.
If you are only looking to 'fix' your reboot issues, I would suggest looking to see if /data/.recovery_mode exists on your phone. If it does, delete it. That's likely what is causing you to reboot into recovery each time.

Zaphod-Beeblebrox said:
I'm sorry, I misunderstood you goal here. I thought you wanted to keep the recovery, just fix it so it didn't come up on each reboot. If you are looking to completely remove the recovery, then I yes, I would follow the directions in the post you referenced, not the code section.
If you are only looking to 'fix' your reboot issues, I would suggest looking to see if /data/.recovery_mode exists on your phone. If it does, delete it. That's likely what is causing you to reboot into recovery each time.
Click to expand...
Click to collapse
Oh wow now I feel dumb. I thought I got it. So this would allow me to reboot and keep the recovery without it going into recovery every time I reboot. I hate asking noob questions lol

jkpair said:
Oh wow now I feel dumb. I thought I got it. So this would allow me to reboot and keep the recovery without it going into recovery every time I reboot. I hate asking noob questions lol
Click to expand...
Click to collapse
Assuming that is the problem. There may be another reason that you are getting dumped into recovery each time, but I suspect this is it. I will say that it's not 'normal' for recovery to come up each time. It should only come up if you somehow stop the boot process mid-way (Battery pull, etc) or use the Bootstrap recovery program to set it to reboot in recovery (which basically just creates the data file in question).
I would suggest you work through fixing this problem rather than just getting rid of the recovery. It's quite a powerful tool.

Zaphod-Beeblebrox said:
Assuming that is the problem. There may be another reason that you are getting dumped into recovery each time, but I suspect this is it. I will say that it's not 'normal' for recovery to come up each time. It should only come up if you somehow stop the boot process mid-way (Battery pull, etc) or use the Bootstrap recovery program to set it to reboot in recovery (which basically just creates the data file in question).
I would suggest you work through fixing this problem rather than just getting rid of the recovery. It's quite a powerful tool.
Click to expand...
Click to collapse
Yeah I really don't want to rid myself of it. I do believe I have an understanding now I am going to give it a shot when I can leave work. I will come back and post results.
Awesome It worked like a charm. Deleted the .recovery_mode file and am now happy.
Thanks for replying so quickly before I decided to just go ahead and remove the recovery menu all together.

jkpair said:
Yeah I really don't want to rid myself of it. I do believe I have an understanding now I am going to give it a shot when I can leave work. I will come back and post results.
Awesome It worked like a charm. Deleted the .recovery_mode file and am now happy.
Thanks for replying so quickly before I decided to just go ahead and remove the recovery menu all together.
Click to expand...
Click to collapse
Where is this file located? Im having the same problem.
Sent from my DROIDX using XDA App

DrewDanger said:
Where is this file located? Im having the same problem.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
From my earlier post:
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
Click to expand...
Click to collapse

I went through Astro and searched "/data/.recovery_mode" but it didnt bring up that file. I guess Im just confused at what exactly Im supposed to be looking for...

Yeah I ended up using a root file manager to do this was really easy. Just go the root menu and browse to data find recovery_mode and delete then reboot.
Oh and astro will not show what is in the data folder you have to get a root explorer app I think the one I used was android mate.
Sent from my DROIDX using XDA App

Ok cool I'll check that out. When I use Astro and go under "system" and scroll down it has a "recovery from boot" folder. Any idea what that is? When I open it there is a bunch of code script in it

Ok I deleted that file and it fixed it. I think Im just gonna un-root it when I get off work. Im over all this, lol. I'll wait until the Droid has more development as far as root access and what you can do. Can I just do the un-root through the one -click-root I used?

DrewDanger said:
Ok I deleted that file and it fixed it. I think Im just gonna un-root it when I get off work. Im over all this, lol. I'll wait until the Droid has more development as far as root access and what you can do. Can I just do the un-root through the one -click-root I used?
Click to expand...
Click to collapse
Yeah it has an option to unroot, but I can't state whether or not this is the best method to remove the root. I acctually am keeping my root and bootloader. Yeah I will be glad when there is a true rom as well but progress is progress.

[Boot Splash] "Inspired" by Light (w/Preview Pic)

I hope you enjoy this. These are pretty easy for me to make, so if you have a request... ... At any rate, "thank" me if you like it and use it. And if you screw anything up and your phone explodes, or breaks, or Smurfs attack from outer space, it's your fault. you have been warned!
How to flash:
1. Unzip the file so you have "splash1.img" and place this file in your "tools" folder of your SDK package.
2. Boot into your bootloader (fastboot mode)
3. From the command prompt: Change directories to your SDK "Tools" folder then type:
Code:
fastboot flash splash1 splash1.img
4. Reboot and enjoy

Got a preview pic by chance. Also check your pm's.

Preview pic should be up... I see it on my end?? It's HUGE. lol..
Anyone else not see the pic?
EDIT: Just checked the OP on a different PC, and pic WAS NOT showing up. This has now been corrected. ...

How do we revert to default, if desired?

smalis said:
How do we revert to default, if desired?
Click to expand...
Click to collapse
You will have to re-flash the default boot splash. Using the same method as mentioned.
Note: I will update the OP with the stock Boot splash as well, once I receive my phone.

OK, stupid question time (my specialty) I get into the Inspire bootloader OK, but then how do I call up or otherwise access "command prompt"? It's not like I have a menu button I can push, and command prompt doesn't seem to be one of the options displayed on the screen. I may be overlooking the obvious, and if so I apologize.

Ultra Droid said:
OK, stupid question time (my specialty) I get into the Inspire bootloader OK, but then how do I call up or otherwise access "command prompt"? It's not like I have a menu button I can push, and command prompt doesn't seem to be one of the options displayed on the screen. I may be overlooking the obvious, and if so I apologize.
Click to expand...
Click to collapse
What T.A.G. was referring to was using the command prompt in Windows. This would also be used in conjunction with having the Android SDK installed in Windows.

Wolf_2 said:
What T.A.G. was referring to was using the command prompt in Windows. This would also be used in conjunction with having the Android SDK installed in Windows.
Click to expand...
Click to collapse
OK, *now* I understand! Told you, dumb questions are my specialty!
Thanks much!
-Mike

The only dumb questions are those that are not asked.
Sent from my Inspire 4G using XDA Premium App.

tribalartgod-
Awesome job!

kimtyson said:
tribalartgod-
Awesome job!
Click to expand...
Click to collapse
Thanks. I've been slacking on a lot of stuff here lately. Bout to go full force on this stuff again soon. (Job and life away from Android takes priority.) Stay tuned.

can this be flashed through cwr?

stryfe2010 said:
can this be flashed through cwr?
Click to expand...
Click to collapse
I have not tried it. So as of right now, the official answer is NO. If you decide to try anyway, it's at your own risk. I'm not responsible if your phone becomes a pretty brick.

[Q] Won't turn on properly after installing custom boot animation

I installed a custom boot animation and now my phone won't boot up properly. The animation won't show during boot and basically after the galaxy sIII screen, nothing is shown. The phone seems to be started okay, I hear sounds and vibration when I press buttons, but the screen just is not showing anymore.
I'm trying to boot to recovery and use adp to either delete the bootanimation.zip or push a different version, but I get the device not found error.
PLEASE HELP!!!

ned4spd8874 said:
I installed a custom boot animation and now my phone won't boot up properly. The animation won't show during boot and basically after the galaxy sIII screen, nothing is shown. The phone seems to be started okay, I hear sounds and vibration when I press buttons, but the screen just is not showing anymore.
I'm trying to boot to recovery and use adp to either delete the bootanimation.zip or push a different version, but I get the device not found error.
PLEASE HELP!!!
Click to expand...
Click to collapse
How'd you install it? Do you have a link to what you flashed?
Sent from my SCH-I535 using xda app-developers app

ajrty33 said:
How'd you install it? Do you have a link to what you flashed?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks, but I finally got it figured out. Scarred the crap out of me for a minute there though!
I was able to run "adb push bootanimation.zip /system/media" and it works after reboot. I couldn't get it working in recovery, but was able to with the phone started like "normal".
Not sure what was wrong with the other version of the bootanimation to totally killed the screen though. The only thing I can think of is there was zip compression on. But I would have thought that wouldn't kill the entire screen like that! Dunno.

I am have execet same issue please help
ned4spd8874 said:
Thanks, but I finally got it figured out. Scarred the crap out of me for a minute there though!
I was able to run "adb push bootanimation.zip /system/media" and it works after reboot. I couldn't get it working in recovery, but was able to with the phone started like "normal".
Not sure what was wrong with the other version of the bootanimation to totally killed the screen though. The only thing I can think of is there was zip compression on. But I would have thought that wouldn't kill the entire screen like that! Dunno.
Click to expand...
Click to collapse
So I am experiencing same issue I can please be little be more detailed how you pushed the bootanimation. except command. please i am panicking i know there is a solution but i just cant seem to make it work. You help would be much appreciated. thank you!

MyMymusicIsSoHard said:
So I am experiencing same issue I can please be little be more detailed how you pushed the bootanimation. except command. please i am panicking i know there is a solution but i just cant seem to make it work. You help would be much appreciated. thank you!
Click to expand...
Click to collapse
Sorry, it's been so long I can barely remember this! I think what I did was pretty much as I described. I booted the phone up, waited for a little bit to make sure it was all the way started since I couldn't see the screen. And then plugged in the cable and performed the push command. It was pretty straight forward as long as you can ignore the fact that the screen wasn't displaying anything.

Had to flash the fireware
ned4spd8874 said:
Sorry, it's been so long I can barely remember this! I think what I did was pretty much as I described. I booted the phone up, waited for a little bit to make sure it was all the way started since I couldn't see the screen. And then plugged in the cable and performed the push command. It was pretty straight forward as long as you can ignore the fact that the screen wasn't displaying anything.
Click to expand...
Click to collapse
So my Debugging mode was off so I could not use adb push command, I had to do a complete firmware flash, that got my phone to work but lost all my data on the phone. but still a happy camper.
Thank you for prompt response, all your help it's much appreciated.

I had the same problem but with an ASUS memo pad hd7. I downloaded a bootanimation.zip that was the wrong orientation, so I unzipped it, rotated all the pictures rezipped and placed it back in /system/media/. Mistake! After that the device would not boot! At least that's what I thought until a quick google search led me here, thanks for your help! My situation was a little different, i'll explain my journey below in case it helps others with similar situations.
Installed minimal ADB and Fastboot from here http://forum.xda-developers.com/showthread.php?p=42407269 . I already had the device drivers installed on my computer so I skipped that step. Luckily I had USB debugging selected, however, I had never used ADB and had not given it SU permissions on the tablet. I input the following code into adb:
adb shell
cd /system/media/
ls
This verified that the offending bootanimation.zip was in there. I then tried to remove the offending bootanimation.zip with this command
rm bootanimation.zip
It failed because system was mounted as Read Only and I could not change it because I did not have SU permissions so I hit the power button on my tablet to wake it up, blindly swiped to get through the lock screen, and typed this into ADB to request Super User permissions
su
I then blindly tapped near the middle of my screen. After a few tries I successfully hit the right spot at the right time and granted SU to ADB
Once that was done I remounted system as read write and deleted the offending file with this code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
rm bootanimation.zip
ls
After verifying that bootanimation.zip was gone, I rebooted the tablet and was greeted with success in the form of some generic Android boot animation.

Same thing with my Panasonic p11 and I have a password for SuperSU so I am stuck pls help

I would suggest flashing a backup from before the custom boot animation. Then taking more cautious steps the next time you try.

To avoid this kind of unpleasantness, whether for changing the boot animation or anything else, here's a few tips:
always root your phone
It's your phone, you should have access to everything, shouldn't you? That's like buying a new car and the dealer won't give you a key for the trunk.
always use a custom ROM
Stock ROMs are usually bloated with apps you don't need and can't uninstall. Also, stock ROMs often disable features and access either "for your own good" or to keep the interface simpler. Case in point, neither of the stock ROMs that came with my Galaxy S4 or my Atrtix HD allowed me to customize the LED notification light. Whatever defaults they picked, that's what I got. A flashing green light meant I received "something" (text or email). There are a variety of 3rd party ROMs out there ready to flash for a specific device, find one that you like.

Full Screen?

Hi,
I have root,is there anyway we can make use of this great screen easily by getting rid of the navigation on the bottom and the google search bar then use a pie app for navigation?
Cheers.
PS I did search the forum but did not see this question come up.
MJ-12

FYI this has been covered in at least a few threads here.
But this is what I did-
Install this app (it's what I use) or a similar one of your choosing- https://play.google.com/store/apps/details?id=tk.eatheat.pie&hl=en
And add this line to your build.pro to get rid of your navbar- qemu.hw.mainkeys=1
Reboot after editing your build.prop.
That's all you gotta do.

_MetalHead_ said:
FYI this has been covered in at least a few threads here.
But this is what I did-
Install this app (it's what I use) or a similar one of your choosing- https://play.google.com/store/apps/details?id=tk.eatheat.pie&hl=en
And add this line to your build.pro to get rid of your navbar- qemu.hw.mainkeys=1
Reboot after editing your build.prop.
That's all you gotta do.
Click to expand...
Click to collapse
did this and now my phone won't boot, just black screen after google logo

special.k said:
did this and now my phone won't boot, just black screen after google logo
Click to expand...
Click to collapse
Did you edit anything else in your build.prop? All that does is trick the phone into thinking you've got hardware keys, thus eliminating the need for a navbar. There's no reason why that mod alone would cause your phone to not boot. Can you get into fastboot or recovery?

_MetalHead_ said:
Did you edit anything else in your build.prop? All that does is trick the phone into thinking you've got hardware keys, thus eliminating the need for a navbar. There's no reason why that mod alone would cause your phone to not boot. Can you get into fastboot or recovery?
Click to expand...
Click to collapse
I just copy and pasted it in at the bottom, I think that was my problem. I can get into fastboot

special.k said:
I just copy and pasted it in at the bottom, I think that was my problem. I can get into fastboot
Click to expand...
Click to collapse
Well you can try using adb to push an unedited build.prop back to /system and that should get you running again.

_MetalHead_ said:
Well you can try using adb to push an unedited build.prop back to /system and that should get you running again.
Click to expand...
Click to collapse
Okay, where can I find that?

special.k said:
Okay, where can I find that?
Click to expand...
Click to collapse
Just download the stock ROM and pull it out of /system. There should be one over in the dev section.
If you're not familiar with adb, you should probably be able to copy the build.prop over with the file manager in TWRP. Just put it on your SD and use TWRP to move it to /system.
If you have trouble finding the build.prop just let me know and I'll pull mine and post it for you.

_MetalHead_ said:
Just download the stock ROM and pull it out of /system. There should be one over in the dev section.
If you're not familiar with adb, you should probably be able to copy the build.prop over with the file manager in TWRP. Just put it on your SD and use TWRP to move it to /system.
If you have trouble finding the build.prop just let me know and I'll pull mine and post it for you.
Click to expand...
Click to collapse
Okay thanks I will find it, I am on a ubuntu computer right now and am having trouble setting up adb on my old windows xp computer. ADB on ubuntu won't detect my device, I don't have TWRP installed or any recovery of that matter. Can only access fastboot

special.k said:
Okay thanks I will find it, I am on a ubuntu computer right now and am having trouble setting up adb on my old windows xp computer. ADB on ubuntu won't detect my device, I don't have TWRP installed or any recovery of that matter. Can only access fastboot
Click to expand...
Click to collapse
Well that's gotta be annoying. I'm not familiar with ubuntu but have you made sure your drivers are installed on your xp machine?

_MetalHead_ said:
Well that's gotta be annoying. I'm not familiar with ubuntu but have you made sure your drivers are installed on your xp machine?
Click to expand...
Click to collapse
I don't think so, it's not showing that any devices are connected

special.k said:
I don't think so, it's not showing that any devices are connected
Click to expand...
Click to collapse
Look around for the drivers and manually install them. If you can't find them, this toolkit will install them for you- http://forum.xda-developers.com/showthread.php?t=2508817