Database Info

[HOW-TO] ADB for Dummies(How-To Learner's Guide)

Hi,
My name is Joe aka AndroidSamurai.. I will be releasing more guides and media content in the weeks to come.
I'm currently very busy with "life events(new baby)" and apologize for my absence.
I will be updating this post since it was my original with a new guide updated to new SDK and Android methods.
Thanks again,
AndroidSamurai
Android4D Inc

<golf clap>
Well done.
</golf clap>

What do i do if the new hardware device notification doesnt pop-up ? NM i got it. Thanks for the writeup

@King_tee: Assuming windows, you follow the following steps.
1. Start > Control Panel > System.
2. Hardware > Device Manager
3. Click on the last icon below the File menu. It should correspond to "Scan for Hardware Changes."
If that doesn't work, try unplugging / replugging USB cable, different USB cable, restarting phone, restarting computer, etc.

If you never see the notification, navigate to the Device Manager(inside "System" in the control panel in XP and inside Device Manager on Vista).
You will see ADB Android Device at the top of the list with a Yellow Icon beside it meaning the device is not working. Right-click on the device and select "Update Driver".
Follow the dialogs that pop-up and navigate to where the unzipped drivers are at...
You should be good to go from there...

ok, i need some help please... I downloaded the SDK and followed the instruction in this thread, but when i try to update my driver for the phone, it says the driver is not compatible with my phone.. I am using Haykuro's ROM 4.5 with FW 1.5.. would that be the reason for this issue?

devildogg2001 said:
ok, i need some help please... I downloaded the SDK and followed the instruction in this thread, but when i try to update my driver for the phone, it says the driver is not compatible with my phone.. I am using Haykuro's ROM 4.5 with FW 1.5.. would that be the reason for this issue?
Click to expand...
Click to collapse
you may need to uninstall the current driver for your phone if you have mounted it before downloading the SDK. if you don't have the SDK setup the first time you plug the phone in then your computer will auto-update the driver to a regular UMS driver and it won't help you when you try adb. i forget how to uninstall your current driver since i don't use windows, but i'm sure you can find a nice crash course online

tubaking182 said:
you may need to uninstall the current driver for your phone if you have mounted it before downloading the SDK. if you don't have the SDK setup the first time you plug the phone in then your computer will auto-update the driver to a regular UMS driver and it won't help you when you try adb. i forget how to uninstall your current driver since i don't use windows, but i'm sure you can find a nice crash course online
Click to expand...
Click to collapse
I dont know if thats the problem because when i plug it in, it doesnt show up as a notification, and when i go to the device manager it shows the little yellow triangle.. I'll look again. Thanks for the quick reply though. I am no expert in linux, but i have it installed, let me see if i can figure it out there..

tubaking182 said:
you may need to uninstall the current driver for your phone if you have mounted it before downloading the SDK. if you don't have the SDK setup the first time you plug the phone in then your computer will auto-update the driver to a regular UMS driver and it won't help you when you try adb. i forget how to uninstall your current driver since i don't use windows, but i'm sure you can find a nice crash course online
Click to expand...
Click to collapse
ok, so i am in linux now, and i just noticed this guide was for windows.. lol can you or someone tell me how to install the SDK on linux?

devildogg2001 said:
ok, so i am in linux now, and i just noticed this guide was for windows.. lol can you or someone tell me how to install the SDK on linux?
Click to expand...
Click to collapse
Downloading
http://developer.android.com/sdk/1.1_r1/index.html
Installing
http://developer.android.com/sdk/1.1_r1/installing.html
Found through Google...imagine that.

as well as what xyrcncp said can you you can download it and just mv ~/Desktop/sdk/tools/adb /usr/bin/adb abd you should be able to run the adb commands from any directory. not too hard to cd to the correct directory but i personally don't like to type cd ~/Phone/tools/android-sdk/tools every time cause i tend to make typographical errors. let me know how it worked but you shouldn't have any problems at all

umm no offense but your writing a tutorial for people that are not sure on how to do this, so you must assume that they do not know how to run an executable file...... write yourself a better tutorial without actually bashing the self esteem of some people... tutorials are positive not negative. I already know all of this but still... dont degrade someone due to the fact they dont know how, thats the whole point of writing your tutorial. Nothing should have been left out (including how to run a .exe .com or .bat
" (If you do not know how to install a windows executable file, please kill yourself now! ) "
this isnt honestly written with any hatred towards you, it was a good tutorial. Just might want to think about how you write it next time.

The "bashing" comments in my tutorial are directed towards the people with a true sense of humor. My tutorial was written to tell you how to simply complete a task and not to make you feel better about yourself. I do not get pleasure in abusing people's self esteem nor do I enjoy putting people down.
Just because you got a little sand in your crack does not mean you need to come in a very honest and informative thread and start bashing the people who are bending over backwards to help everyone out.
The reason I created this "tutorial" in the first place was because all the other threads are full of "start searching and stop asking so many damn questions" comments.
So start looking in the mirror when you wake up in the morning and stop saying "My, I think I will run over to good ole' XDA and be an @$$ to everyone today".
I am sincerely sorry that a little sense of humor has caused so much hatred in my thread. Please contact the forum moderators and see if the think my tutorial is so hateful.

lol i dont see any hatred but anyway when i download the adb driver when extracting it says unknown method

@ Nabzilla1990
Are you using Windows or Linux?
Are you using the built-in Zip tool or 7-zip from the links I provided?
Are you using a 32 or 64-bit OS?

using the same operating system as you 64bit vista ultimate sp1 and using winrar to extract

Try using 7-zip man, I have been using it for 3 yrs now.
Basically what I am saying is that everything in my guide is guaranteed to work.

Just to add, if you take adb.exe and adbwinapi.dll and copy or move them to the \windows\system32 directory you can run adb from any dos directory prompt.

it worked with 7-zip thank you and also want to add if it doesnt work for some people plug in ur phone and update the usb mass storage with the usb driver from here and it should work i had that problem earlier

Okay, so I did everything and got up to run cmd, when I type in the cd C:\android-sdk-windows-1.1_r1\tools it says not a specififed folder, but when I type it without the \tools it doesnt work. can anyone help?

[Q] Brk root method reports success, but no root

Hello,
Firstly, this is a long explanation, so, for the lazy, I have put a TL;DR version at the bottom of the post. Scroll there to get the general idea.
I have attempted to root my Transformer numerous times now. It is a serial number B60.
I am running Windows XP, so I am trying to use Brk's script.
I am using v6.3.1 of the script, because I have the latest OTA update.
This is my 'Build number' in 'About tablet': HTJ85B.US_epad-8.6.5.9-20110816
I have been trying this method since 8.6.5.6 and at the time I used v6.1 of the script (other methods including a VirtualBox run of rebound's One-Click Universal root linux live-CD).
When I run the script, I follow the instructions exactly.
I backup (option 1), then reboot into APK mode again.
Then, I flash unsecure boot.img (option 4) and CWM. I have tried only installing unsecure boot.img and it has made no difference.
Flashing the unsecure boot.img reports success and flashing CWM reports success.
Next, I reboot into regular Android OS.
Development mode is on for the USB. I check to see if ADB is working (option 7).
ADB is not working. The reason? I do not have root. I have installed the Terminal Emulator application. When I run the command 'su', it says 'Permission denied'.
I have also tried the Transformer pure root tw/us/ww/de/jp (8.4.4.5/11/12/8.6.5.6/7/9) and it has the same results. That is, flashing unsecure boot reports success, as does flashing CWM, but I have no root.
Additionally, I tried a VirtualBox run of rebound's One-Click Universal root linux live-CD. That failed, because I couldn't capture the Transformer as a USB device).
TL;DR version
I have tried several different methods of rooting my Transformer. It is serial #: B60 series running HTJ85B.US_epad-8.6.5.9-20110816.
All drivers are set up completely.
All steps are followed
All steps report success
Root is not granted
ADB will not work
???
More details at the top
One last thing
The only thing that I can think may possibly explain this problem is that I do not have an SD card in the tablet. I know some guides specify that you need one and other ones do not say anything.
I do not think that this is the cause, chiefly because everything reports 'success'.
Are these results typical of what happens when someone tries to flash a B70 or B80 model? If so, is it possible that, although I have a B60 series model, the innards are that of the B70/80 series and thus, incompatible?
I hope that posting my results and problems will help solve someone else's problem at the very least.
At this point, even someone just replying and letting me know that I have done everything correctly would be nice.

Have you got the ASUS drivers installed in your pc? i.e. can you connect and sync your device normally?

Here's a hint from the BRK thread:
Found the problem. I didn't install the ASUS PC Suite, just the drivers. Found a hint in another post that PC Suite seems to contain something in addition to the driver which is needed for ADB connections. No idea what it is, the device manager entries still look same...
so did you install the ASUS PC Suite as well as the drivers?

Success!
AustinMartin said:
Here's a hint from the BRK thread:
Found the problem. I didn't install the ASUS PC Suite, just the drivers. Found a hint in another post that PC Suite seems to contain something in addition to the driver which is needed for ADB connections. No idea what it is, the device manager entries still look same...
so did you install the ASUS PC Suite as well as the drivers?
Click to expand...
Click to collapse
Wow! I feel like a complete idiot...
I downloaded and installed the "Asus Eee PAD Transformer TF101 USB Driver" which I thought was what the PC Suite was. I was wrong.
Everything is working after installing the PC Suite and then trying ADB.
I definitely wrote way too much...

telekenetix said:
I definitely wrote way too much...
Click to expand...
Click to collapse
But that is how we learn, from seeing what others have done...

did you enable development ? it is for adb

I found that out early on that the PC Sync app is essentially just a front-end for ADB, since the app wouldn't work when I had debugging enabled on the TF.

mashi said:
did you enable development ? it is for adb
Click to expand...
Click to collapse
Yes. The trouble was that the PC Suite wasn't installed. I thought I had it installed, but it turned out that I only installed the drivers. Everything is running smoothly now.
The thing that still seems odd to me is that I tested to see if I had root, using the terminal application. It said "Permission denied". But, after installing the PC suite, adb was able to function and apparently did something magical.
So, I have to ask. What is this black magic?!

[Q] Obtaining root on generic tablet

Ok I've got a generic tablet from Walmart, the DOPO MD-740. It's running ICS 4.0.3. I've been in contact with customer service about this thing, and while they're friendly and courteous, they really don't know anything about their product. According to their lead tech "there is no recovery or download mode".
Headache.
Well fooling around with this device, I've found.... SOMETHING....
While holding the volume up button at the same time as the power button, it boots straight to one single image, shown below. I have a feeling it's the download mode. Whatever it is, it's progress. Can anyone recognize what I got into? It's not a fatal error-- when I hit the reset button and reboot the tablet normally, all is fine.
I've tried to reboot into recovery via adb but I get the message that the command is not allowed. And of course, su is not allowed either.
Anyone have any suggestions on running adb on my computer... what process I would need to follow to manually root an ICS tablet? Would I just follow the same steps as I would in manually rooting a gingerbread device, or is there different lines of code I would need to use for ICS?
As for what device the kernel for THIS device has been ported from (it's obviously emulating something that has a magnometer which this unit doesn't have, etc...)... tech support doesn't know that either. The only clue I have that MIGHT help (other than the kernel version, build number, etc... all this is documented in another post, if anyone cares to take a look) is the FIRST boot image is of the penguin.
I would appreciate ANY feedback/information/advice anyone could offer in progressing with this "adventure"!
Thanks
Well with another twenty minutes of blindly pressing buttons I've found the recovery mode. From the screen displaying the android with the open panel (which I have concluded is NOT the download mode), pressing volume up, back, and power at the same time opens the recovery mode. The recovery is:
Android system recovery <3e>
Recovery system v4.00
No option to apply zip from sd, I guess this is to be expected on a stock device.

hi
in application select usb debug mode
install from unknown sources
connect to pc and run DooMLoRD_v4_ROOT
should work
regards
fred

didn't work.
After adb started successfully, sat for two hours and did nothing.

hi
are you using windows ?
is it reconized by windows ? do you have the drivers installed ?
ich processor use that tablet ?

Yeah I'm running Windows Vista, and my PC does recognize the device when it's connected (says drivers have been installed properly when connected under USB debugging mode, no problem transferring files in USB mode)
It's the ARMv7 processor
The device is recognized as Full ASOP on Rk29sdk

I've run across a new problem, which might actually be the main issue of the WHOLE problem. I was trying to push some files with adb from my laptop and it came to my attention that the driver for my device only acknowledges it as a mass storage device, even when the tablet is NOT mounted for mass storage. SOOOO... I guess I need a driver that will allow me to use adb. Any suggestions?

did you try with the drivers package from sdk ?

yup. Even gone as far as uninstalling the adb and sdk programs I had on my pc, downloading the newest versions and reinstalling. My computer "recognizes" the divice, but only as folders. Even when it's not mounted as mass storage.

STILL having te driver issue. Anyone have any suggestions on how to fnd a driver that will work with adb?
Sent from my Full AOSP on Rk29sdk using XDA

How did I root my “Full AOSP Rk29sdk”-MID 7-inch tablet (Android 4.0.3)
Hi Wingnut79 and others,
I have an Android 4.0.3 Tablet 7 inch, named "Full AOSP Rk29sdk" - and was also eager to root it....
After hours of search, trial and error, I succeeded.
My tablet is now fully rooted, and I can use ROM manager and all the aps for rooted android-devices....
How did I do that ?
I explain it here, in the attachment...
As you can see, my Windows is in the Dutch language, so I nevertheless hope everyone can understand what to do where...
I hope this can help...

Make sure it's not a Chinese Apad!
Make sure it's not a Chinese Apad! If u go on ebay u will see tons of tablets with ics 4.0.3. but the android on it it's a modified and weird version. I doublt it even is ics. One of my friends have it, and he cannot use the App Market, bcuz it said "Device not compatible with Market". Did u successfully downloaded stuff form the Market? If not, that maybe it's a piece of Chinese crap and u should call walmart for a refund.

It downloads apps from Android Market, Getjar, Amazon etc... just fine.
BAUDI--
I will try this later this afternoon, is it going to be an issue that my laptop OS is windows vista?

Mine tablet is a chinese tablet - but it's clearly really Android 4.0.3.
So, I also download and install applications from Playstore /Android Market/ etc.
It has Wifi, Bluetooth, 3G, GPS-AGPS, FM-radio,.... and evrything works really fine.
My sole problem was: no rootaccess (what I didn't understand, because it's "Android Open Source Project"...?)
Wingnut79,
as far as described in the guide I refer to, it works equally well on Vista. Just sometimes a little bit other name or place to find the properties or so - but should not be a problem at all.
I forgot to insist on the need to kill and restart adb after each change. I am not sure its really necessary each time, but I experencied that when I first thought "again nothing", it seemed well to work after "adb kill-server" and then "adb start-server"....
At some steps (I can't remember wich) I even rebooted my PC....
Now, everything works immediately...
So ROM Manager etc. works well, I have SuperUser... etc .
Good luck!

baudi said:
Mine tablet is a chinese tablet - but it's clearly really Android 4.0.3.
So, I also download and install applications from Playstore /Android Market/ etc.
It has Wifi, Bluetooth, 3G, GPS-AGPS, FM-radio,.... and evrything works really fine.
My sole problem was: no rootaccess (what I didn't understand, because it's "Android Open Source Project"...?)
Wingnut79,
as far as described in the guide I refer to, it works equally well on Vista. Just sometimes a little bit other name or place to find the properties or so - but should not be a problem at all.
I forgot to insist on the need to kill and restart adb after each change. I am not sure its really necessary each time, but I experencied that when I first thought "again nothing", it seemed well to work after "adb kill-server" and then "adb start-server"....
At some steps (I can't remember wich) I even rebooted my PC....
Now, everything works immediately...
So ROM Manager etc. works well, I have SuperUser... etc .
Good luck!
Click to expand...
Click to collapse
Just because it says it is 4.0.3 doesn't mean its pure AOSP. Remember that the China gov has its hands into a lot and there are things that they like to install on their devices to monitor the users and then close it up so it can't be changed.
Sent from my Inspire 4G using Tapatalk 2

this app rooted my Full AOSP on rk29sdk
I tryed many ways trying to root my tablet, even unlockroot.exe
I found SuperOneClickv2.3.3 and it found my tablet right off, it said my tablet looks rooted( but I knew it was not) so I let it do the root process, it installed superuser also
SuperOneClickv2.3.3
you may have to temp turn your virus program off, I use avira so I right clicked the task bar icon and unchecked realtime protection

universel root
try the universel root for the version of android you have or of similar tabs

asdera-and said:
try the universel root for the version of android you have or of similar tabs
Click to expand...
Click to collapse
Where can we find this?
Is there a download link?
---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------
carl1961 said:
I tryed many ways trying to root my tablet, even unlockroot.exe
I found SuperOneClickv2.3.3 and it found my tablet right off, it said my tablet looks rooted( but I knew it was not) so I let it do the root process, it installed superuser also
SuperOneClickv2.3.3
you may have to temp turn your virus program off, I use avira so I right clicked the task bar icon and unchecked realtime protection
Click to expand...
Click to collapse
Hello,
So SuperOneClick did work for you?
What kind of tablet do you have?
What version of Android was it running when you used SuperOneClick?
Thank you,

baudi said:
Hi Wingnut79 and others,
I have an Android 4.0.3 Tablet 7 inch, named "Full AOSP Rk29sdk" - and was also eager to root it....
After hours of search, trial and error, I succeeded.
My tablet is now fully rooted, and I can use ROM manager and all the aps for rooted android-devices....
How did I do that ?
I explain it here, in the attachment...
As you can see, my Windows is in the Dutch language, so I nevertheless hope everyone can understand what to do where...
I hope this can help...
Click to expand...
Click to collapse
I tried this and it worked. I got root on my device thanks alot for the guide.
Now to the real problem. I have two identical devices (rk29sdk). One is not booting and I can't manage to reset it.
My idea is make a full backup of the working device and somehow install it on the other one (the broken).
How can I do that - when I try to connect with adb it says:
Code:
C:\Windows\system32>adb devices
List of devices attached
0123456789ABCDEF device
Then this
Code:
C:\Windows\system32>
C:\Windows\system32>adb backup -apk -shared -all -f /backup/mybackup.ab
adb: unable to connect for backup
So it sees the device but I can't backup?
[edit]Now I connect to the device, the 'adb reboot' command works and the device responds. it's just the backup command that is not working.
Please help

asemore said:
I tried this and it worked. I got root on my device thanks alot for the guide.
Now to the real problem. I have two identical devices (rk29sdk). One is not booting and I can't manage to reset it.
My idea is make a full backup of the working device and somehow install it on the other one (the broken).
How can I do that - when I try to connect with adb it says:
Code:
C:\Windows\system32>adb devices
List of devices attached
0123456789ABCDEF device
Then this
Code:
C:\Windows\system32>
C:\Windows\system32>adb backup -apk -shared -all -f /backup/mybackup.ab
adb: unable to connect for backup
So it sees the device but I can't backup?
[edit]Now I connect to the device, the 'adb reboot' command works and the device responds. it's just the backup command that is not working.
Please help
Click to expand...
Click to collapse
i am not at my computer to post the commands, but you can type the commands to backup your system (or dump it) from a androids term console, you need busybox installed
edit: try this link
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
;;
Sent from my Full AOSP on Rk29sdk using xda premium
---------- Post added at 03:40 AM ---------- Previous post was at 03:25 AM ----------
Beeg Boy said:
Where can we find this?
Is there a download link?
---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------
Hello,
So SuperOneClick did work for you?
What kind of tablet do you have?
What version of Android was it running when you used SuperOneClick?
Thank you,
Click to expand...
Click to collapse
yes it worked for root, my chinese phone just shows Full AOSP on Rk29sdk
Sent from my Full AOSP on Rk29sdk using xda premium

carl1961 said:
i am not at my computer to post the commands, but you can type the commands to backup your system (or dump it) from a androids term console, you need busybox installed
edit: try this link
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
Click to expand...
Click to collapse
The thing is I don't have access on my tablet. It won't boot.
So I can't start an app from the tablet, or maybe I can?

Bricked phone build.prop missing

Hi to all here. i just want to ask anyone what to do with my phone. well first of all, my phone is a sky pantech vega racer im-a760s, not really a match for samsungs popularity but budget wise this is the model for me. it has a dual core. now my problem starts when i started editing the build.prop in its system (tweaked for some texting problem of limited character sending). of course i know what im doing on that part, but the only thing i didn't think that would happen was, i copied it in my computer, i edited it there, then i saved it as "all" in file type so it wont become a ".txt" format. but when i placed it in my phone. the file instantly disappeared, i think it was only hidden and the phone just cant identify it nor read it like something. now i restarted the phone, it booted up to its logo then it just went blank and it just stops there. i tried pushing recovery with adb in my pc cmd. but it cannot detect my device(no problem with my adb installation to eliminate this from the question), i also tried putting an sd card with a recovery file but there was no option for sd card path. but the phone can still function well, i know because it can still be loaded under flashboot, download screen and S / W upgrade menu and it can still perform wipes for all partition and caches and can reset for factory settings etc. but whenever i will reboot, its not going to complete. anyone please help me how to make my phone be detected by my pc. The usb drivers are just fine, updated it many times, read all procedure for making the driver connect perfectly. i reformatted the sd so it wont be a problem when i put it in. but in the recovery menu i just cant see my sd card, theres just the option for "update from external storage" but it doesn't have anything inside. what a mess. i cant make my phone reflashed cause its not responding with the connection with my pc. but when i am opening an odin (just used for connection monitoring) there are two yellow boxes with com port like these: 0:[com7] and 0:[com9], so i know it is still somehow communicating with my pc. please help any advice, i dont want to resort to jtag for im not sure if it will support my phone and it's already avialable for the model but definitely not going to send my phone for repair cause it will be costly. thanks to all who will respond. Please help thank you. additionally: OS was ics version 4.0.4 and rooted. already gone through rooting several times with no problem. just the editing part.

to edit Android files on Windows use only Notepad++ anyway do not use Windows notepad this is for Windows files formatting only
well, you have to get build.prop from your phone edit on PC then copy back
so enter recovery connect phone to PC create a folder say C:\tmp
to get build.prop from phone
Code:
adb devices
adb shell
mount system
exit
that's to mount system partition then
Code:
adb pull /system/build.prop C:\tmp\build.prop
edit it and copy back to phone
Code:
adb push C:\tmp\build.prop /system/build.prop
maybe is not your case ? but I wanted to give you an idea

@ruscan.calin
Thanks, great. i will try this one once i get my phone recognized by my pc, adb seems not able to find my devcie have this message like this one:
"
c:\>adb devices
adb server is out of date. killing...
*daemon started successfully *
list of devices attached "
and that's it nothing happens.
thanks for the advice i will definitely use this once i get my phone connected with my system. thanks a lot

cruelink said:
@ruscan.calin
Thanks, great. i will try this one once i get my phone recognized by my pc, adb seems not able to find my devcie have this message like this one:
"
c:\>adb devices
adb server is out of date. killing...
*daemon started successfully *
list of devices attached "
and that's it nothing happens.
thanks for the advice i will definitely use this once i get my phone connected with my system. thanks a lot
Click to expand...
Click to collapse
start phone in recovery mode do not connect to PC at this time
open Device Manager now connect phone to PC
if you see ADB Interface connecting in Dev Manager it's ok if not you have a problem with phone drivers so install it again

ruscan.calin said:
start phone in recovery mode do not connect to PC at this time
open Device Manager now connect phone to PC
if you see ADB Interface connecting in Dev Manager it's ok if not you have a problem with phone drivers so install it again
Click to expand...
Click to collapse
Hi, cant still afford to make the adb component in my device manager to appear, but it's good to inform you that it helped me a bit because i was able to see the storage of my phone and i was also able to put some files in there without any hassle that alone was satisfying me that my phone is not really dead. sad to say i did everything i could to have my pc detect my phone via recovery menu, but still no devices found. it's really weird that some links are saying that i should make my phone's "usb debugging" enabled, wherein fact i cant even go beyond my original problem(bricked phone), i can't even see the inside of my phones directory, only the storage one that was activated just recently. i even did a reinstallation of my usb, uninstalled every other phone related usb installation to avoid conflicts reinstalled my phones proper usb installer then restart. no progress still to be called. it makes me feel that the phone was just trap in the state of booting and not knowing what to do because it cant see any command inside its system. i cant go into the systems directory as well. and that's the only way i think i could revive my phone in replacing a new build.prop, as you advised to be edited in a notepad++ which i recently acquired and installed. by the way how do i save the build.prop to its original file format, and what is the extension. thanks alot for helping out. im getting a little brighter each step of the way, im not loosing it to come to smashing my phone to pieces instead of keeping a very expensive paper weight.

usb debugging enabled is not useful in this case (you can't set it )
build.prop is a file with .prop extension save file with notepad++ name it build.prop then check location of file it should be build.prop notepad from Windows saves it as build.prop.txt that's not good also notepad adds some formatting characters inside file that's wrong so use only Notepad++ when working on Android files (or VIM for Windows editor etc anyway do not use Windows editors they are good for Windows files only)
-try these things on another computer (to install drivers etc)
-I advised somebody to send a mail to manufacturer and he got a reply with a link to stock rom... that's great !
-if you link me your build.prop file I can tell you if it's ok
-pc link - that's to be solved firstly check manufacturer site for sync software/ drivers even send mail

isa. rgiespea
ruscan.calin said:
usb debugging enabled is not useful in this case (you can't set it )
build.prop is a file with .prop extension save file with notepad++ name it build.prop then check location of file it should be build.prop notepad from Windows saves it as build.prop.txt that's not good also notepad adds some formatting characters inside file that's wrong so use only Notepad++ when working on Android files (or VIM for Windows editor etc anyway do not use Windows editors they are good for Windows files only)
-try these things on another computer (to install drivers etc)
-I advised somebody to send a mail to manufacturer and he got a reply with a link to stock rom... that's great !
-if you link me your build.prop file I can tell you if it's ok
-pc link - that's to be solved firstly check manufacturer site for sync software/ drivers even send mail
Click to expand...
Click to collapse
that's great news, you actually come to emailing the phones manufacturer? wow, im flattered. well you're a very nice guy to help me out on this. and i have good news too. i found out that i have a little conflicting usb drivers, as i have installed samsung for my previous phone(samsung galaxy 1) i had it liquidated for this new one. but a little hard on the support. you gave me a new idea about the usb. so i uninstalled all the related usb drivers and have it reinstalled. now i am able to communicate with OTA firmware server, and i got a reading that was not happening before(stucked in just detecting the phone) now i have a percentage reading of downloading or so. but i still have to wait if it will complete and have it repaired. so by now you can give me a little more help cause im still not at it in pushing through the use of adb programming. and the link you mentioned, i'll wait for the progress about it and see what really was it. and thanks a lot. really appreciate it.

fixed bricked phone via OTA by fixing link to pc.
Hi, i thank you for your help. i managed to fix the phone myself. i just missed the simple step that you advised me. fix the link first to pc. i have installed another model of the phone for the same manufacturer with different type so that was causing the mixed up for updating and recovering via the OTA site of the phone. so yey. you helped a lot. i thank you. i am now running at ics version 4.0.4 and now rooted. i will not commit the same mistake of saving the build.prop with another format. that was bad. so then i'll be very careful in editing the build.prop and first of all, i will keep a backup inside where i can access it even if it will be hard bricked. never forget that one from now on. so this is it. i thank you. of all the place ive been circling around for answer. here is where i found it. and just one person. hooray. thank you very much.

cruelink said:
Hi, i thank you for your help. i managed to fix the phone myself. i just missed the simple step that you advised me. fix the link first to pc. i have installed another model of the phone for the same manufacturer with different type so that was causing the mixed up for updating and recovering via the OTA site of the phone. so yey. you helped a lot. i thank you. i am now running at ics version 4.0.4 and now rooted. i will not commit the same mistake of saving the build.prop with another format. that was bad. so then i'll be very careful in editing the build.prop and first of all, i will keep a backup inside where i can access it even if it will be hard bricked. never forget that one from now on. so this is it. i thank you. of all the place ive been circling around for answer. here is where i found it. and just one person. hooray. thank you very much.
Click to expand...
Click to collapse
that's good news ! and thanks for feedback
feedback is an invaluable resource ! (some just forget about that from my experience :laugh: NOT your case ! )

[Q] Problems updating to Lollipop

Hi,
To make to perfectly clear I am not a developer and my understanding of such issues should be classed as "novice" but I have done a lot of reading up and believe I now need to post a question regarding my problem.
Here goes...
I bought a 32gb off Amazon before Christmas which arrive with 4.4.4. I assumed after a few days of running it would update itself to Lollipop but to no avail, no matter how many times I "checked for updates". I now believe this is probably due to it being a Japanese import. I suspect this as this is on the barcode sticker and the Android with the hatch open logo in recovery has Japanese text underneath.
Anyways I posted a few questions on the Google community and they have basically told me to sit tight as the update is still rolling out. Seems to me that I could be waiting forever so I started to look at doing the manually install myself, remember I'm a amateur here...
I successfully downloaded the ADK file from Google and, even though this came with the USB drivers, I downloaded these seperatly too. I've since deleted the duplicate files.
The problem I am getting is I cannot get the USB drivers to install for when the phone is in USB debugging mode. When I put the phone into both PTP and MTP mode I can direct the driver location towards the folder and everything works OK, when its debugging mode it says they cannot be installed. I think its important to note that I am using Windows XP.
I've tried removing, restarting and reinstalling but to no avail.
Suspect its an XP thing, how do I get around this?
Thanks in advance!

iainwith2is said:
Hi,
To make to perfectly clear I am not a developer and my understanding of such issues should be classed as "novice" but I have done a lot of reading up and believe I now need to post a question regarding my problem.
Here goes...
I bought a 32gb off Amazon before Christmas which arrive with 4.4.4. I assumed after a few days of running it would update itself to Lollipop but to no avail, no matter how many times I "checked for updates". I now believe this is probably due to it being a Japanese import. I suspect this as this is on the barcode sticker and the Android with the hatch open logo in recovery has Japanese text underneath.
Anyways I posted a few questions on the Google community and they have basically told me to sit tight as the update is still rolling out. Seems to me that I could be waiting forever so I started to look at doing the manually install myself, remember I'm a amateur here...
I successfully downloaded the ADK file from Google and, even though this came with the USB drivers, I downloaded these seperatly too. I've since deleted the duplicate files.
The problem I am getting is I cannot get the USB drivers to install for when the phone is in USB debugging mode. When I put the phone into both PTP and MTP mode I can direct the driver location towards the folder and everything works OK, when its debugging mode it says they cannot be installed. I think its important to note that I am using Windows XP.
I've tried removing, restarting and reinstalling but to no avail.
Suspect its an XP thing, how do I get around this?
Thanks in advance!
Click to expand...
Click to collapse
Install the adb/fastboot drivers. Google is your friend

Firstly thank you for your reply.
I have tried your install but it hasn't worked. I can tell I have been following a smilar update route looking at the pictures you uploaded also, although these screen snaps were obviously from a new OS (windows 7 perhaps).
Whats interesting to note however, is that in my device manager the phone is clearly shown twice, at the top as "Android Device", with "Google Nexus ADB Interface" below it and then again further down as "Other Devices" with MTP below with the familiar yellow exclamation mark.
Significant?

You actually don't need debugging mode if you're intending to manually flash the ROM. Debugging mode is only an android setting and you flash the ROM using fastboot which is outside of android.
Also you don't need the SDK.
I would say go to general > sticky roll-up then read my adb and fastboot thread to start

Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.

iainwith2is said:
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
Click to expand...
Click to collapse
If you used the adb and fastboot installer in my thread, did you use the "install system wide" option?
If not, do.
If you did and it did not work, read more of that section as the manual steps are also mentioned, which you'll need to follow.

iainwith2is said:
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
Click to expand...
Click to collapse
You don't have adb/fastboot set up properly. Google 15 second adb install xda.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
You don't have adb/fastboot set up properly. Google 15 second adb install xda.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
He should already have it from my thread. Its just a question whether he used it correctly or whether it doesn't set up the environment variables on xp properly

Yes installed the 15 second install, Y,Y,N, then installed the Clockmod driver.
I'll go back and read it again, guess I must've missed something.

Have you rebooted? Try that. Is still no, you'll need to manually populate the environment variables.

Right, I have re-read the manual section and I can tell you I HAD edited the path before as I was following another instruction, one where it required SDK tools. So I have deleted the text I added last time (platform-tools was part of it) and copied and pasted the test in the manual area, including the colon.
Still cannot see the adb in the command window though?

iainwith2is said:
Right, I have re-read the manual section and I can tell you I HAD edited the path before as I was following another instruction, one where it required SDK tools. So I have deleted the text I added last time (platform-tools was part of it) and copied and pasted the test in the manual area, including the colon.
Still cannot see the adb in the command window though?
Click to expand...
Click to collapse
Don't copy and paste it. The text is generic. You must put your text there....then reboot.

this is what I pasted:
;c:\adb_fastboot
?

iainwith2is said:
this is what I pasted:
;c:\adb_fastboot
?
Click to expand...
Click to collapse
Which is generic. Is the folder your adb and fastboot executables are in called c:\adb_fastboot? If you used the installer, it is not.

Where would the installer put them? I've searched my computer for "fastboot" and its found the exe that I put in a folder on my desktop. This looks a similar address to what I changed the path to previously...

Oy vey
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Oy vey
Pardon?
Click to expand...
Click to collapse

OK so my path is broken so I won't be able to run adb commands?

Did you look at the root of c:? C:\adb perhaps? Its all covered in my thread isn't it? Are you reading it or skimming it? You don't even *need* to put it in the path. Its just easier. Please read to the end of the thread
Also, you don't need to run any adb commands

Yes I've scanned c: drive.
I've read and understood what I can, I'm not an expert so I can only compute what I understand.
I have reinstalled the adb setup a few times and I have noticed that it clearly says "0 files copied" after I select the exe files and system wide options.
I have also tried to run the adb and fastboot devices commands in the command window which gives me the aforementioned error messages.
For some reason, these programs are not being installed onto my machine?