Related
I know it sounds repetitive. I constantly work on computers and use my own at home but all I use is macs! I had a g1 and everything was pretty manageable by flashing zips and metamorph etc, but adb is something I really never needed to learn, and all I hear is how windows users use adb. Are there any setups for mac users? That doesn't involve too much trouble? Thanks, and I'm sure this thread could help any other mac user that is looking into rooting their phone.
You don't have to use adb.. reread the root thread for updated, easier instructions. With it this easy, yes it's worth it.
heygrl said:
You don't have to use adb.. reread the root thread for updated, easier instructions. With it this easy, yes it's worth it.
Click to expand...
Click to collapse
no, no. I know you can root it without adb, but it seems like if you want to theme/mod things adb will be a big part of this. Just kind of looking for a savior mac solution that I maybe haven't heard of to accomplish adb.
joe.kerwin said:
no, no. I know you can root it without adb, but it seems like if you want to theme/mod things adb will be a big part of this. Just kind of looking for a savior mac solution that I maybe haven't heard of to accomplish adb.
Click to expand...
Click to collapse
No, usually theming/modding requires flashing more .zip files through recovery. ADB is probably most commonly used to push .apk (apps) files to the system that are otherwise uninstallable or more or less built into the system.
Many people with modded phones will never use adb.
I'm also a mac user, this is my first android phone, and my programming knowledge is a high school java class which i took 6 years ago. With that being said I've had no problems learning some of the commands involved with ADB. If you are some what tech savvy and have decent problem solving skills you can work your way around most of it.
As far as setting up my mac, I just downloaded the SDK and was able to use ADB without having to download any drivers like I had read in a lot of guides, but then again most of those are written for windows users. I'm still learning as I go but its pretty interesting and XDA is definitely a good place to start.
Even of you need to use adb for something in the future, adb works fine on a mac. I have been rooting and modding my android phones since the G1 and have always used one of my mac computers. Drivers are not needed and most phones communicate without a problem.
-sent from my T-Mobile Vibrant ; )
Hi everyone, i am trying to root my kindle fire device , but the process is not working.
Here is what i've done:
1. Installed Drivers from "install_drivers.bat" file from KFU
2. Manually Installed Drivers
Still cannot make ADB Status to go "ONLINE".
The way i can make it "ONLINE" is by executing the "run.bat" file as administrator, but, doing this, leads me to error "cannot find tools/wget.exe". Ofc, because running with administrator privileges forces it to run from system32 folder.
I've already tried to run from the Command Prompt, even running the command prompt as administrator aswell.
Any idea of how to solve it ?
My Kindle is 6.3 Version. I bought it in February.
I used the KFU 0.9.5 version.
I also tried to install drivers manually, from a difference source ( a youtube video tutorial of how to root 6.2 version ), but, the device manager says the drivers are already up to date.
My device manager shows a "Android device" at the top of the list, but no "Kindle" or "Amazon Kindle" device in the whole list.
What am i doing wrong ?
Please, if you can't solve it, at least, bump this thread.
Thanks !
Try this... delete your drivers and configure and reinstall your own from the AndroidSDK
http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
Then use command prompt to issue the appropriate adb and fastboot commands to manually root your device using the method posted here:
http://forum.xda-developers.com/showthread.php?p=24124828
If, after you reinstalled your drivers, you can't get adb to connect through command prompt, you may need to make sure that your user account has the appropriate permissions to perform such tasks (although I can't imagine why you wouldn't anyway).
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
Try this... delete your drivers and configure and reinstall your own from the AndroidSDK
http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
Then use command prompt to issue the appropriate adb and fastboot commands to manually root your device using the method posted here:
http://forum.xda-developers.com/showthread.php?p=24124828
If, after you reinstalled your drivers, you can't get adb to connect through command prompt, you may need to make sure that your user account has the appropriate permissions to perform such tasks (although I can't imagine why you wouldn't anyway).
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I've seen you mention the Android SDK a number of times as it relates to driver installation. This is not meant as an argumentative post, but the SDK is entirely unnecessary if the user won't be "developing" software and just wants to install the drivers.
The SDK method is a lot of unneeded bulk to install the Java JDK, so you can install the Android SDK installer to get at the USB driver extras. Then the user has to go manually edit the .INF file with the necessary KF details before installing. Then create the .android folder in the right place and add a correctly named .INI file with more information. All these hoops create problems because most people who come here looking for help are flustered enough as it is and missing any one of these things or doing it wrong will just cause more issues that will have to be ironed out. It's just a bad idea all around.
And just in case you believe that the SDK drivers are somehow "better" than the KFU ones... they're not. All of the relavant files are identical. When I was writing my drivers guide, I checked them all to see if it could be a potential source for differences on why one install would work and not another. All of the md5 checksums for each and every .DLL and .CAT file match each other.
The only difference I found was in the source.properties files and that was just in the order of the name=value pairs at the bottom and the SDK distribution has an "Extra.NameDisplay=Google USB Driver" pair while the KFU one does not. I tried to find out how this file gets used in the driver installation, but the fact that I came up empty leads me to believe that it's a a non-player in the whole scheme of things.
Of course, the android_winusb.inf file is different between the two because some Kindle Fire specific information has already been added to it in KFU, but this is a good thing because you won't have to go do it manually and therefore skip an error prone task.
Please do not complicate matters by having people do this unnecessarily. If people want to install the drivers manually, they can point the driver update wizard to the KFU folder containing the android_winusb.inf file and it will do the same thing. If they use KFU's install_drivers batch file to install, they'll even get the .android folder created in the right place and the adb_usb.ini tossed in there with the correct values.
If you believe my reasoning is flawed, please let me know how installing from the SDK makes a difference. If you have a sound argument, I'm perfectly willing to admit my wrong, change my position and my guide as well.
I am inclined to agree with you with so many different instructions with different levels of experience how the new user can achieve root and proper driver installation has become muddled to the point where people are getting stuck in modes rendering thier devices unseen by thier computers. Stuck in fastboot or recovery or soft and hard bricked with batteries draining and time running out to achieve a fix. There is a serious need for a clear easy exploit for very low experience level OS dedicated. KFU worked perfect for me and so did adb but with others it has created a problem if I had the knowledge base to build a one click wonder I would but its way out of my experience level even though I have successfully rooted every device I have 2 kindles a galaxy tab 10.1 and my droidx after the .621 ota for droidx. So where do we go from here?
kinfauns said:
I've seen you mention the Android SDK a number of times as it relates to driver installation. This is not meant as an argumentative post, but the SDK is entirely unnecessary if the user won't be "developing" software and just wants to install the drivers.
The SDK method is a lot of unneeded bulk to install the Java JDK, so you can install the Android SDK installer to get at the USB driver extras. Then the user has to go manually edit the .INF file with the necessary KF details before installing. Then create the .android folder in the right place and add a correctly named .INI file with more information. All these hoops create problems because most people who come here looking for help are flustered enough as it is and missing any one of these things or doing it wrong will just cause more issues that will have to be ironed out. It's just a bad idea all around.
And just in case you believe that the SDK drivers are somehow "better" than the KFU ones... they're not. All of the relavant files are identical. When I was writing my drivers guide, I checked them all to see if it could be a potential source for differences on why one install would work and not another. All of the md5 checksums for each and every .DLL and .CAT file match each other.
The only difference I found was in the source.properties files and that was just in the order of the name=value pairs at the bottom and the SDK distribution has an "Extra.NameDisplay=Google USB Driver" pair while the KFU one does not. I tried to find out how this file gets used in the driver installation, but the fact that I came up empty leads me to believe that it's a a non-player in the whole scheme of things.
Of course, the android_winusb.inf file is different between the two because some Kindle Fire specific information has already been added to it in KFU, but this is a good thing because you won't have to go do it manually and therefore skip an error prone task.
Please do not complicate matters by having people do this unnecessarily. If people want to install the drivers manually, they can point the driver update wizard to the KFU folder containing the android_winusb.inf file and it will do the same thing. If they use KFU's install_drivers batch file to install, they'll even get the .android folder created in the right place and the adb_usb.ini tossed in there with the correct values.
If you believe my reasoning is flawed, please let me know how installing from the SDK makes a difference. If you have a sound argument, I'm perfectly willing to admit my wrong, change my position and my guide as well.
Click to expand...
Click to collapse
Yes, I know.
The point is to get people to forget about KFU for a minute and learn to do it the right way first (so as not to get distracted) so when they ARE ready to use a utility like the KFU they will know what to do when problems arise. You learn to do it the hard way first (one that will be around LONG after the KFU is gone) and THEN you can take shortcuts. That's pretty much standard procedure for learning anything.
I think it's safe to say that the KFU has caused more problems for newbies than has helped. And the ones it has helped usually have to learn the old way anyway. I'm just trying to get rid of the middleman.
Just think of how great this place would be if everyone knew how to how to do this on their own.
Sent from my Amazon Kindle Fire using xda premium
That being said, the people that I told to do it the "hard" way haven't needed any further help.
And if it does come back to bite me in the ass, you can rest assured, I'll eat my words.
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
Yes, I know.
The point is to get people to forget about KFU for a minute and learn to do it the right way first (so as not to get distracted) so when they ARE ready to use a utility like the KFU they will know what to do when problems arise. You learn to do it the hard way first (one that will be around LONG after the KFU is gone) and THEN you can take shortcuts. That's pretty much standard procedure for learning anything.
I think it's safe to say that the KFU has caused more problems for newbies than has helped. And the ones it has helped usually have to learn the old way anyway. I'm just trying to get rid of the middleman.
Just think of how great this place would be if everyone knew how to how to do this on their own.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I get your point about KFU and I think my guide is evidence of that. However, I'm in complete disagreement about your suggestion for the driver installation process. I don't believe fixing one's Kindle Fire should first involve learning the roundabout way of installing the drivers. In my mind, the KFU utility is entirely separate from the driver installation batch file. I see no good reason make that part of it any more difficult than it has to be. I also think your middleman analogy is a bit flawed. It's more like having the guy go chop down a tree in the dead of night when you've already got a stack of firewood for him.
---------- Post added at 09:47 PM ---------- Previous post was at 09:43 PM ----------
marcelloLins said:
Hi everyone, i am trying to root my kindle fire device , but the process is not working.
Here is what i've done:
1. Installed Drivers from "install_drivers.bat" file from KFU
2. Manually Installed Drivers
Still cannot make ADB Status to go "ONLINE".
The way i can make it "ONLINE" is by executing the "run.bat" file as administrator, but, doing this, leads me to error "cannot find tools/wget.exe". Ofc, because running with administrator privileges forces it to run from system32 folder.
I've already tried to run from the Command Prompt, even running the command prompt as administrator aswell.
Any idea of how to solve it ?
My Kindle is 6.3 Version. I bought it in February.
I used the KFU 0.9.5 version.
I also tried to install drivers manually, from a difference source ( a youtube video tutorial of how to root 6.2 version ), but, the device manager says the drivers are already up to date.
My device manager shows a "Android device" at the top of the list, but no "Kindle" or "Amazon Kindle" device in the whole list.
What am i doing wrong ?
Please, if you can't solve it, at least, bump this thread.
Thanks !
Click to expand...
Click to collapse
So, instead of totally hijacking this thread for the sake of an argument...
I think you need to confirm that your drivers are installed properly. Regardless of what path you take to get them installed, pay attention to the middle part of this post...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
and make sure that you are seeing the right things in the device manager. You'll have to verify that part of it is working right, so Windows and the Kindle Fire are able to communicate with each other before moving ahead in your troubleshooting.
kinfauns said:
I get your point about KFU and I think my guide is evidence of that. However, I'm in complete disagreement about your suggestion for the driver installation process. I don't believe fixing one's Kindle Fire should first involve learning the roundabout way of installing the drivers. In my mind, the KFU utility is entirely separate from the driver installation batch file. I see no good reason make that part of it any more difficult than it has to be. I also think your middleman analogy is a bit flawed. It's more like having the guy go chop down a tree in the dead of night when you've already got a stack of firewood for him
Click to expand...
Click to collapse
Let me say just this and I'll let it be. Ask yourself, "What's more likely to stand the test of time? Android SDK or KFU?" What happens when KFU becomes obsolete/unmaintained and is no longer hosted for people to download? What happens when KF owners move on to other Android devices not supported in such a way? Configuring and installing device drivers is a basic skill that every Android device owner should have anyway, and it causes no harm pushing people to learn it. I'm not breaking any rules by doing so and until now you are the only one to have had a problem with it.
That being said, don't let my disagreement fool you into thinking I have anything anything less than the utmost respect for you. - Quite the contrary in fact. I personally have learned a lot from you and many others here and I feel it is my duty to pay it forward. I apologize if the method I use offends you, and if others here feel the same way I will definitely take it into consideration.
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
Let me say just this and I'll let it be. Ask yourself, "What's more likely to stand the test of time? Android SDK or KFU?" What happens when KFU becomes obsolete/unmaintained and is no longer hosted for people to download? What happens when KF owners move on to other Android devices not supported in such a way? Configuring and installing device drivers is a basic skill that every Android device owner should have anyway, and it causes no harm pushing people to learn it. I'm not breaking any rules by doing so and until now you are the only one to have had a problem with it.
That being said, don't let my disagreement fool you into thinking I have anything anything less than the utmost respect for you. - Quite the contrary in fact. I personally have learned a lot from you and many others here and I feel it is my duty to pay it forward. I apologize if the method I use offends you, and if others here feel the same way I will definitely take it into consideration.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Believe me, I'm not offended by this discussion. We are just having a respectful disagreement over a mutually shared desire to help people who want to mod their KF. I understand that you aren't doing anything wrong. I'm not wagging my finger at you or yelling, "my way or the highway!" It's just my belief that going the SDK route is error prone and the cost/benefit of doing it that way may be too high for most users to bear.
Let me share an experience I had with someone who PM'd me for help after deciding to install the drivers from the SDK. After days of back and forth, he figured out that he had created the adb_usb.ini file as a text file and Windows was hiding the file suffix. So, he actually had an adb_usb.ini.txt file and with Windows Explorer only showing the adb_usb.ini part, he hadn't really considered the possibility that the file could have been named incorrectly. It's the silly things that will trip up even a knowledgeable user.
I'm not saying never to the SDK... I'm just saying it shouldn't be the first choice. I certainly won't be upset if you decide to instruct users to install the SDK just for the drivers, but they might be if they figure out they could have gotten to the same place with KFU's driver installer in 1/20th of the time.
So I am not quite sure what exactly fastboot is supposed to do. I know you can flash recoveries, bootloaders, etc with it but that is about it for my understanding.
I tried to get into fastboot (following instructions here on the forum) mode earlier today and while the tablet gives me the fastboot message in the upper left, windows says that fastboot failed. Is there a folder I am supposed to be running cmd prompt from?
Sorry, still new to this stuff and my understanding of some of these tools is limited at best.
Sent from my A500 using Tapatalk 2
a friendly warning
CyaN1de said:
So I am not quite sure what exactly fastboot is supposed to do. I know you can flash recoveries, bootloaders, etc with it but that is about it for my understanding.
I tried to get into fastboot mode earlier today and while the tablet gives me the fastboot message in the upper left, windows says that fastboot failed. Is there a folder I am supposed to be running cmd prompt from?
Sorry, still new to this stuff and my understanding of some of these tools is limited at best.
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Give me 30 mins got all the reading u gonna need b4 u make an attempt
if u fk up in here there is definitely NO WAY BACK in meantime you'll
Want to set adb as environmental variable in windows gonna make it
Helluva lot easier . Android sdk will too. f u don't know what I'm on About..
.best do some reading up on these as well.
Fast boot ain't something someone else can talk u thru and I doubt the devs will
Have any sympathy for anyone asking ....i bricked my tab pls help....
dibb_nz said:
Give me 30 mins got all the reading u gonna need b4 u make an attempt
if u fk up in here there is definitely NO WAY BACK in meantime you'll
Want to set adb as environmental variable in windows gonna make it
Helluva lot easier . Android sdk will too. f u don't know what I'm on About..
.best do some reading up on these as well.
Fast boot ain't something someone else can talk u thru and I doubt the devs will
Have any sympathy for anyone asking ....i bricked my tab pls help....
Click to expand...
Click to collapse
Running adb from its native folder is not an issue.....is fastboot the same way having to run cmd from folder that a file is located?
I prefer not to mess stuff that I do not fully comprehend (not that I fully comprehend ANY of this) but some of it makes more sense once you are into it rather than reading someone elses interpretation.
Sent from my A500 using Tapatalk 2
CyaN1de said:
Running adb from its native folder is not an issue.....is fastboot the same way having to run cmd from folder that a file is located?
I prefer not to mess stuff that I do not fully comprehend (not that I fully comprehend ANY of this) but some of it makes more sense once you are into it rather than reading someone elses interpretation.
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
yeh just a group of extended adb commands that allow you to do some pretty awesome stuff - like really, really bricking your tab for instance, lol. I'm unsure as to whether all the fastboot commands are available to us - i havent had enough spare time to devote to heavy duty reading in the Dev Forums!!!! You can flash everything in here so its like a supercharger;;;;Sort of like going from timmydeans EUU root to Civ's nvflash unlocking bootloaders thing, if you know what i mean.......
But heres some reading, most of it tutorial step by step stuff, mostly for other devices which may not apply to our tab but definitely apply to fastboot. AS you know, there is alot of info in our own dev forum but its hard to find a flow as the devs actually speak a different language to us!!!! So the tutorials are quite good in that respect as they use noob-ite speak
the backup and restore tute is a goody, couldnt get it going on v3 so looking forward to giving it a go on v4 (when i can find a quiet 30 mins or so, that is)
anyways happy reading be interested in your thoughts and keep us posted about what you get around to trying
rgds
Full Phone Backup http://forum.xda-developers.com/showthread.php?t=1420351
setup adb http://forum.xda-developers.com/showthread.php?t=1249798
adb http://forum.xda-developers.com/showthread.php?t=879701
adb logcat http://droid-force.com/showthread.php?tid=150&pid=573#pid573
ics BL by Skrilax_CZ http://forum.xda-developers.com/showthread.php?t=1514951
So I located Fastboot in D:\Android\android-sdk\platform-tools\Fastboot.exe
But putting tablet into fastboot mode yields the driver installer to report that "Device driver software was not succesfully installed".......Fastboot X Failed....is this normal? Will it run when I use cmd prompt from D:\Android\android-sdk\platform-tools?
I guess a little linux knowledge would go a long way.....too bad I can't get a grasp on that either.
Thanks for the links.....hopefully I can find time to give a read.
Set up adb/fastboot for noob-ites 101
CyaN1de said:
So I located Fastboot in D:\Android\android-sdk\platform-tools\Fastboot.exe
But putting tablet into fastboot mode yields the driver installer to report that "Device driver software was not succesfully installed".......Fastboot X Failed....is this normal? Will it run when I use cmd prompt from D:\Android\android-sdk\platform-tools?
I guess a little linux knowledge would go a long way.....too bad I can't get a grasp on that either.
Thanks for the links.....hopefully I can find time to give a read.
Click to expand...
Click to collapse
weird??? i kicked straight in to bl, fastboot drivers installed, never saw red x
u mean u arent cmd from platform tools???
in the cpuid guide I suggested extracting the just_adb.zip into C:\ so setting
up the env. var. would be easier I have been meaning to post the steps for
doing that, guess theres no time like the present
Set adb as Environment Variable or call adb direct from command prompt
............ first, copy the path to your install - in your case:
............ "Path to adb" = D:\Android\android-sdk\platform-tools
1. Click on the Start menu
2. Right click on Computer
3. Click on Advanced system settings
4. Click on the Environment Variables button
5. Look for Path in the System Variables section. Double click on it
6. Go to the end of the Variable value box and put in a semicolon ;
7. Now paste your "Path to adb" after the ;
8. it should look like this in your case ;D:\Android\android-sdk\platform-tools
9. Now test it out - start - run/search - cmd - in cmd window type: adb devices
10. If you've followed the steps you will see your device ID - voila!!!!
as you can see this makes trouble shooting so dam easy -
if you cant get a device id do not go any further in what u r doing
cos it aint gonna work....period!!!!! also since ICS has screwed
with getting our cpuid like this, for our purpose here, it is only important
that a device id is shown - not how right or wrong it is.....clear????
so getting back to it, check fastboot*.exe in same folder as adb.exe -
it came like this in my own setup not sure about the asdk setup -
remember too fastboot only has a few commands and i still havent
got round to trying them all out yet....
to anyone following this, I cannot say enough how dangerous this can be
please, please, please take a moment to read thru just one of the links i
posted earlier - they are tutorials and if you see the dev thread regarding
v4 unlock...you will not only learn something amazing but begin to
appreciate and respect the work done by these devs who laid the groundwork
that enabled civato and blakthund3r to produce what they have with the
unlocked bootloader - without this groundwork we would still be waiting
for a way to get full root access and cwm, custom roms, themes and mods......
Thanks for that
Seems my Windows skillz need brushing up on again too....LOL
C:\Users\username>adb devices
List of devices attached
11717XXXXXX device
CyaN1de said:
Thanks for that
Seems my Windows skillz need brushing up on again too....LOL
C:\Users\username>adb devices
List of devices attached
11717XXXXXX device
Click to expand...
Click to collapse
sweet m8 -
yeh whoever thought windoze would actually be useful!!!!
which i guess is freakn handy as having to go linux would spin me out....
what can i say??? I'm a child of windoze had no choice, forced-addiction
before i was born, lol - breaking the habit, but always go back, goddamit
OK....I get the adb ok.
But when I put tab into FB i get the driver error (see attachment). I suppose that I should not be getting this?
Trying just "fastboot reboot" (not wanting to go any farther until I get a grasp...HAHA) I get "waiting for device"
CyaN1de said:
OK....I get the adb ok.
But when I put tab into FB i get the driver error (see attachment). I suppose that I should not be getting this?
Click to expand...
Click to collapse
dont let windows install
choose let me choose where to install dunno exact wording
Does not give me a choice.
Driver is located at D:\Android\android-sdk\extras\google\usb_driver ???
This is making my head hurt....LOL
CyaN1de said:
Does not give me a choice.
Driver is located at D:\Android\android-sdk\extras\google\usb_driver ???
This is making my head hurt....LOL
Click to expand...
Click to collapse
Yr head hurts????
Ive updated the cpuid guide u my wanna take 5 min timeout to read it, the answers r all in there
I don't use full sdk there's a link to mini sdk zip in that post just has ad and fast boot
I've never had to use google drivers
Just plugged my tab in and its just 'worked'
DL Acer drivers if u haven't already . These are the most important ones to have installed right.
Disconnect and reboot everything
Run Acer setup.exe
Plug USB in
Go into fast boot, win doze will want to install f/b drivers let win doze do it, but if they fail, then run again and choose let me install, blah, blah, blah
What OS u got? Vista/win 7 don't normally have any probs
Acer drivers have been installed and all relevant sdk packages installed and up to date AFAIK. (USB_Acer_1.06.1500_A30HA31H_A.zip)
Had no issues installing ICS Bootloader V.3 manually through APX (no auto script) via instructions so I know I can at least do that well.....LOL
Might have to try reinstalling USB drivers and see if that helps.
Thanks
EDIT: Reinstalled USB Drivers now I can't get adb working....F#@K!!!!!!!!!
EDIT II: Re-Re-Installed Drviers and ADB working again...yay...LOL
EDIT III: Used A500_Manager.exe, clicked on "Enter Fastboot" and windows installed and recognized drivers......DBL YAY!!!!
C:\Users\username>fastboot reboot
rebooting...
finished. total time: 0.165s
Now.......to Brick this puppy.....
Thanx for your help dibb_nz....looks like all I needed in the first place was a driver reinstall...HAHA.
Hek m8 for a second or two there, I was feeling ya pain, lol
Oh but the elation when it finally happens!!!!!
I dunno why those drivers act out like that, but it always the same....
Fail, reinstall, fail, reinstall u can understand why peeps get frustrated
Glad u got it m8
First off I'd like to apologize if this is in the wrong place or if it is perceived as advertising, I simply want to contribute to the dev community and this site, and in particular the Nexus 9 forum that has been the centre of my learning as I took up the hobby of AOSP.
I have been back and forth with AOSP, I've contributed a little bit here and there on the Android development forums but would like to properly document how to build AOSP and more importantly (because it is even less well documented) how to add features, change existing features and generally customize the operating system to your liking. I am by no means an expert but I feel I have enough knowledge that I can share it with others who may be in the position I was a number of months ago. I always found it very difficult to find a centralized location for the information I needed.
To this end I have started a site to do just that. I am using a Nexus 9 for my AOSP development but most (if not all) of the tutorials and information should be applicable to basically any AOSP/Nexus device. I have started things off by creating a tutorial on how to build AOSP from 'scratch' so to speak and a tutorial on how to add items to the power menu such as 'reboot', 'airplane mode' etc.
If anybody would like certain topics covered or just have any feedback or comments please reply here or leave them on the articles themselves. I'll do my best to accommodate / respond.
The link is: http://littlelostandroid.wordpress.com
From tomorrow the following (nicer) link should also work: www.alittlelostandroid.com
I should also add that the blog will be ongoing about all things android device but this initial series will be about also and implementing features.
wow this is a real good guide/blog u put together please do continue
Dreamlogix said:
wow this is a real good guide/blog u put together please do continue
Click to expand...
Click to collapse
Thanks! The next post should be up in a day or two, its been a busy week.
New post up about flashing the build to a device!
www.alittlelostandroid.com
This is a great website. Lol i'm gonna have to learn to use ubuntu(was gonna do it anyway on my old computer but motherboard died and i got lazy). Can you make this in chronological order? or better add each section to a sitemap? Just a suggestion:cyclops:
whowatchlist said:
This is a great website. Lol i'm gonna have to learn to use ubuntu(was gonna do it anyway on my old computer but motherboard died and i got lazy). Can you make this in chronological order? or better add each section to a sitemap? Just a suggestion:cyclops:
Click to expand...
Click to collapse
So I changed the theme so that you can see the most recent posts on the side and work from that. I'm still getting to grips with WordPress to be honest but hopefully that's better now.
Another post about setting up and storing your code on GIT repos:
https://littlelostandroid.wordpress...-open-source-project-part-4-git-repositories/
Thanks for this
Do you have any insight to share on your site about building the LTE variants at all?
THX for your work !
There are plans to continue this great guide?
scoobydu said:
Thanks for this
Do you have any insight to share on your site about building the LTE variants at all?
Click to expand...
Click to collapse
Sadly I won't be able to do any work around the LTE version as I don't have the hardware to test it on. I don't want to release advice I haven't tested and potentially end up inadvertently damaging someones tablet for example
Topse said:
THX for your work !
There are plans to continue this great guide?
Click to expand...
Click to collapse
Sorry for the late reply, I don't get any emails when someone posts on this thread, I need to subscribe to it. I do plan on doing more, in fact I think I may have some written already, just a matter of getting time to do it. I'll get to work on the next section of the tutorials and post here when it's up. Is there anything in particular you would like covered?
seanashmore said:
Sadly I won't be able to do any work around the LTE version as I don't have the hardware to test it on. I don't want to release advice I haven't tested and potentially end up inadvertently damaging someones tablet for example
Sorry for the late reply, I don't get any emails when someone posts on this thread, I need to subscribe to it. I do plan on doing more, in fact I think I may have some written already, just a matter of getting time to do it. I'll get to work on the next section of the tutorials and post here when it's up. Is there anything in particular you would like covered?
Click to expand...
Click to collapse
I m actually try to make my own little aosp rom.
I have some probs with gapps flashing.
Wrong api level error.
I tried different commits.
With pure nexus gapps it works .I need to flash it twice.
I do "make otapackage", this is different to your guide.
When I flash a custom kernel I don't have this gapps problems.?
Next thing I will integrate is that reboot option.
But with reboot recovery.
Once after flashing I was surprised with stock recovery..
How can I disable that?
At the moment I build only for my bullhead.
But if that recovery and gapps problem is solved.
I will try for my flounder and shamu too.
Actually I use n7 r 15 as source. But will will switch to 7.1*
When it is evaluable.
Topse said:
I m actually try to make my own little aosp rom.
I have some probs with gapps flashing.
Wrong api level error.
I tried different commits.
With pure nexus gapps it works .I need to flash it twice.
I do "make otapackage", this is different to your guide.
When I flash a custom kernel I don't have this gapps problems.?
Next thing I will integrate is that reboot option.
But with reboot recovery.
Once after flashing I was surprised with stock recovery..
How can I disable that?
At the moment I build only for my bullhead.
But if that recovery and gapps problem is solved.
I will try for my flounder and shamu too.
Actually I use n7 r 15 as source. But will will switch to 7.1*
When it is evaluable.
Click to expand...
Click to collapse
I'm not 100% sure about the GAPPS issue, maybe try http://opengapps.org/, it lets you choose your android version, architecture etc.
In terms of the recovery; You'll see in my tutorials that I am using the stock Google factory images as a base. In that image is a recovery.img file; You should be able to replace this file with TWRP or any other custom recovery and flash it as part of your ROM.
Hope this helps.
seanashmore said:
I'm not 100% sure about the GAPPS issue, maybe try http://opengapps.org/, it lets you choose your android version, architecture etc.
In terms of the recovery; You'll see in my tutorials that I am using the stock Google factory images as a base. In that image is a recovery.img file; You should be able to replace this file with TWRP or any other custom recovery and flash it as part of your ROM.
Hope this helps.
Click to expand...
Click to collapse
I tried opengapps. But i run in an error. Opengapps say my ROM has the wrong api level.
I tried this commit (and other like that)
https://github.com/Cardinal-AOSP/frameworks_base/commit/6c8322f3ad221ea2092e82b99ece537b85ec996f
And with pure nexus dynamic gapps . it works when I flash the gapps two times. First I get the error and the second try works.
Change recovery to twrp sounds good. But with more devices its a dangers thing. Cause ever device needs special twrp.
I think there is a way to disable this flashing recovery.
But till now I didn't find it.
Topse said:
I tried opengapps. But i run in an error. Opengapps say my ROM has the wrong api level.
I tried this commit (and other like that)
https://github.com/Cardinal-AOSP/frameworks_base/commit/6c8322f3ad221ea2092e82b99ece537b85ec996f
And with pure nexus dynamic gapps . it works when I flash the gapps two times. First I get the error and the second try works.
Change recovery to twrp sounds good. But with more devices its a dangers thing. Cause ever device needs special twrp.
I think there is a way to disable this flashing recovery.
But till now I didn't find it.
Click to expand...
Click to collapse
If it's just the case of not flashing the recovery img then just remove that line/command from the script. However you will have to assume that the device already has a recovery img (which to be honest is a fairly safe assumption).
[/STRIKE]
seanashmore said:
If it's just the case of not flashing the recovery img then just remove that line/command from the script. However you will have to assume that the device already has a recovery img (which to be honest is a fairly safe assumption).
Click to expand...
Click to collapse
I try this for recovery https://github.com/peteralfonso/platform_build/commit/9b3a020058b84fb1f9cfba600f4a958572a805c3
edit: i think this is to old...
seanashmore said:
I'm not 100% sure about the GAPPS issue, maybe try http://opengapps.org/, it lets you choose your android version, architecture etc.
In terms of the recovery; You'll see in my tutorials that I am using the stock Google factory images as a base. In that image is a recovery.img file; You should be able to replace this file with TWRP or any other custom recovery and flash it as part of your ROM.
Hope this helps.
Click to expand...
Click to collapse
I use this way to build:
cd ~/aosp/kernel/lge/bullhead
make clean
export ARCH=arm64
export CROSS_COMPILE=~/aosp/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-
export USE_CCACHE=1
make bullhead_defconfig
make -j6
cd ~/aosp
mkdir ~/aosp/device/lge/bullhead-kernel
rm ~/aosp/device/lge/bullhead-kernel/Image.gz-dtb
cp ~/aosp/kernel/lge/bullhead/arch/arm64/boot/Image.gz-dtb ~/aosp/device/lge/bullhead-kernel
source build/envsetup.sh
make clobber
lunch aosp_bullhead-userdebug
export USE_CCACHE=1
make -j6 otapackage
Topse said:
I use this way to build:
cd ~/aosp/kernel/lge/bullhead
make clean
export ARCH=arm64
export CROSS_COMPILE=~/aosp/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-
export USE_CCACHE=1
make bullhead_defconfig
make -j6
cd ~/aosp
mkdir ~/aosp/device/lge/bullhead-kernel
rm ~/aosp/device/lge/bullhead-kernel/Image.gz-dtb
cp ~/aosp/kernel/lge/bullhead/arch/arm64/boot/Image.gz-dtb ~/aosp/device/lge/bullhead-kernel
source build/envsetup.sh
make clobber
lunch aosp_bullhead-userdebug
export USE_CCACHE=1
make -j6 otapackage
Click to expand...
Click to collapse
Ah ok, see the way I build gives me separate .img files, and I write a script similar to the flash-all script you get with the factory images. This allows me to pretty easily change what i want to do and what i want to flash or not.
seanashmore said:
Ah ok, see the way I build gives me separate .img files, and I write a script similar to the flash-all script you get with the factory images. This allows me to pretty easily change what i want to do and what i want to flash or not.
Click to expand...
Click to collapse
Year , but zip is easier to use/share.
Topse said:
Year , but zip is easier to use/share.
Click to expand...
Click to collapse
Definitely, though you can always put your script and .img files inside a zip just like the factory images. so users would download your zip, unzip it and run your script. Its all down to personal taste i guess, there are many ways to skin a cat.
seanashmore said:
Definitely, though you can always put your script and .img files inside a zip just like the factory images. so users would download your zip, unzip it and run your script. Its all down to personal taste i guess, there are many ways to skin a cat.
Click to expand...
Click to collapse
:good:
I like it to try different ways.Good for learning and deeper understanding.
For my personal use is this way no problem.
But for sharing with other people is a flashable zip file the most used way.
I've been watching videos and reading threads and installing drivers and I just can't make this work. All I can think is maybe I am required to root my phone? Or that the drivers are all invalid now that I updated to 8.1?
I have full android studio installed and the Google USB driver.
My goal is to control my phone from my PC.
Threads here seem either out of date to complicated by much more serious goals, like flashing etc.
I don't even want to root heh.
Halp X)
Innomen said:
I've been watching videos and reading threads and installing drivers and I just can't make this work. All I can think is maybe I am required to root my phone? Or that the drivers are all invalid now that I updated to 8.1?
I have full android studio installed and the Google USB driver.
My goal is to control my phone from my PC.
Threads here seem either out of date to complicated by much more serious goals, like flashing etc.
I don't even want to root heh.
Halp X)
Click to expand...
Click to collapse
What is it what you want to do? What do you mean with "control my phone"? If you have Motorola (not Google) drivers installed (and something like minimal ADB & Fastboot) you should be able to boot your device into bootloader mode and it should be recognized.
Motorola drivers:
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view?usp=drivesdk
Minimal ADB & Fastboot:
https://drive.google.com/file/d/10NEzpxKpYWfq-HdK42ctwoEnCg-BfsRQ/view?usp=drivesdk
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
What is it what you want to do? What do you mean with "control my phone"? If you have Motorola (not Google) drivers installed (and something like minimal ADB & Fastboot) you should be able to boot your device into bootloader mode and it should be recognized.
Motorola drivers:
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view?usp=drivesdk
Minimal ADB & Fastboot:
https://drive.google.com/file/d/10NEzpxKpYWfq-HdK42ctwoEnCg-BfsRQ/view?usp=drivesdk
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Like in the title, scrcpy.
https://github.com/Genymobile/scrcpy
I want a window on my desktop that is my phone in which I can click and such, which to my understanding is exactly what that app does. But naturally it cannot manipulate what it cannot see, and it sees with adb, and adb can't see my phone. But my operating system can. At least it says it can.
Update: Apparently I had not enabled USB debugging. Now I can see my device but it is not "authorized." I try to grant permission and get "because an app is obscuring a permission request, Settings can't verify your response." I'm working on that now, thanks! I'll make a new thread if that problem persists.
Update: It was the application "Tap'n'turn." Temporarily disabling its permission to display over other apps solved it. (Search for "display" in settings.)
Everything is now working
I'd just like to say that that's a very cool looking app, so thanks for posting your question about it, maybe I'll end up using it myself :good:
NZedPred said:
I'd just like to say that that's a very cool looking app, so thanks for posting your question about it, maybe I'll end up using it myself :good:
Click to expand...
Click to collapse
I know right? It's pretty amazing. Were someone to make an open source and user friendly wrapper for everything else about getting it to work I'm sure it would become immensely popular.