Related
Hey guys.....
I'm using an Xperia Acro and need a little help in terms of flashing a custom kernel. Please bare with me as I'm pretty new to this.
I'm to upload the DoomKernel, and I *think* I'm ready to go. My phone is rotted, bootloader unlocked, fastboot enabled. Also, I have the necessary files that need to be flashed.
However, I got lost pretty quickly. I'm supposed to put the .img file into the "flashboot binaries folder". I have NO idea what this means. I looked at the systems folders and cant find anything labeled flashboot.
What am I'm supposed to do? Where is this elusive folder?
Appreciate the help...
Anybody? just trying to figure out where to put the boot.img file.....
On your pc you should have a fastboot folder, open that and one of the sub folders should be boot. Place the file there. Shift-right click and select open command window here, enter in the command window fastboot flash boot xxxx.img, xxxx being the bootfile name.
sinkster©
sinkster said:
On your pc you should have a fastboot folder, open that and one of the sub folders should be boot. Place the file there. Shift-right click and select open command window here, enter in the command window fastboot flash boot xxxx.img, xxxx being the bootfile name.
sinkster©
Click to expand...
Click to collapse
Thanks for the reply. Where would a fastboot folder be on my pc?
Thanks
When you unlocked your bootloader via SE you should have downloaded the SDK files, think it's in there. You'll need the drivers too, there are a few threads on here where people were looking for help with fastboot so you'll find everything there.
sinkster said:
When you unlocked your bootloader via SE you should have downloaded the SDK files, think it's in there. You'll need the drivers too, there are a few threads on here where people were looking for help with fastboot so you'll find everything there.
Click to expand...
Click to collapse
I didn't. I had it unlocked remotely by another user on this forum actually......
try these http://min.us/miDhsNng1
I recommend going to the se page about unlocking your bootloader first, it'll give you a link for all the files you need. If you're unsure, create a folder "fastboot", drop the files above in it, any bootfiles just go in the folder beside the dll files, in open folder shift and right-click, create command window, type in window"fastboot flash boot xxxx.img" and see if it asks for drivers
i'll give it a try. thanks!
Says "waiting for device". That mean im good to go?
seems fine, is the blue light on?
Any joy? Can't remember exactly how I set it up, there's a few extra things to download like adb, drivers and such but those files are the fastboot stuff I use. Think you need the Java jre too...
Hey, sorry for the delay. Had to sleep then go to work. Will attempt to do this once i get home!
Hey,
So yeah....it's a no go. I'm not sure if I'm entering fastboot mode correctly, cause the light is green. I hold the back button while plugging in the usb cord.....thats the correct way to enter fastboot mode right?
Anyway, command prompt continues to read, "waiting for device"
Okay, so apparently I needed to be holding the menu key, not the back key to enter fastboot mode.
So, I got the blue light now, but the command prompt still says "waiting for device"
sinkster said:
Any joy? Can't remember exactly how I set it up, there's a few extra things to download like adb, drivers and such but those files are the fastboot stuff I use. Think you need the Java jre too...
Click to expand...
Click to collapse
Also, tried opening the fastboot.exe file manually, and it just opens and then shuts down immediately.
So frustrating!
hi mate
most likely ur missing drivers
my set up is fast boot folder inside which is all fast boot files and adb files and I place the .img here ,just in the fast boot folder not a sub folder.
I plug in phone in fast boot then open fast boot folder hold shift and right click on empty part of folder,click open command prompt here then enter "fastboot flash boot boot.img" should flash in 2-3 seconds if all is correct
some times hangs waiting for me if I open command prompt before plugging in phone
hope that helps
Sent from my VS910 4G using xda premium
pushtostop said:
hi mate
most likely ur missing drivers
my set up is fast boot folder inside which is all fast boot files and adb files and I place the .img here ,just in the fast boot folder not a sub folder.
I plug in phone in fast boot then open fast boot folder hold shift and right click on empty part of folder,click open command prompt here then enter "fastboot flash boot boot.img" should flash in 2-3 seconds if all is correct
some times hangs waiting for me if I open command prompt before plugging in phone
hope that helps
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
Tried it. Also tried downloading SDK Tools as well. Nada.....just waiting for device.....
Did you download from SE site? This thread is prob the best guide http://forum.xda-developers.com/showthread.php?t=1034087
what happens if u type. fastboot devices in command prompt wit phone connected
Sent from my VS910 4G using xda premium
C:\Users\sinclair\Downloads\fastboot_with_Android_USB_file\fastboot>fastboot dev
ices
CB5A1DE0GJ&ZLP fastboot
C:\Users\sinclair\Downloads\fastboot_with_Android_USB_file\fastboot>
I have a pretty big problem and need some guided help. My stock samsung usb charger sometimes charges the phone and sometimes does not. Tried multiple different chords and got the same results, sometimes works sometimes does not. So now I am assuming this is an internal hardware problem soo I decided I should flash stock images, unroot and relock the bootloader and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash stock images so I can return it to VZW....
Not sure what to do next.. any suggestions would be great...
It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.
mwalt2 said:
It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.
Click to expand...
Click to collapse
I tried that. uninstalled the old ones (that worked for 3 months) reinstalled them again and still no luck..
Do you have any other Android processes running on your cpu? Droid Explorer or alike? Droid Ex **** blocks adb; I had a frustrating few minutes once when adb wouldn't connect to my device until I realized DE was running in the background.
Long shot, but just a thought.
This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.
chuckdz3 said:
and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash
Click to expand...
Click to collapse
You mean fastboot
Melhouse said:
This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.
Click to expand...
Click to collapse
Yeah I believe that is what I am going to do, I just have to find the sch-i515 CDMA version because I am finding a lot of GSM versions out there right now.
bk201doesntexist said:
You mean fastboot
Click to expand...
Click to collapse
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.
chuckdz3 said:
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.
Click to expand...
Click to collapse
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?
bk201doesntexist said:
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?
Click to expand...
Click to collapse
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?
chuckdz3 said:
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?
Click to expand...
Click to collapse
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).
mwalt2 said:
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).
Click to expand...
Click to collapse
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?
chuckdz3 said:
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?
Click to expand...
Click to collapse
yes, you can download the images for your device from google and flash them to your phone using fastboot if you want. I'm pretty sure that would put you back at stock with an unlocked bootloader.
@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.
bk201doesntexist said:
@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.
Click to expand...
Click to collapse
I know how to. It was just your demeanor and wording/phrasing that had me confused.
I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader
brooklynite said:
I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader
Click to expand...
Click to collapse
*facepalm*
Make sure USB debugging is turned on.
Sent from my Galaxy Nexus
mentose457 said:
Make sure USB debugging is turned on.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
*facepalm*
Melhouse said:
*facepalm*
Click to expand...
Click to collapse
Did I say something stupid?
mentose457 said:
Did I say something stupid?
Click to expand...
Click to collapse
debugging has nothing to do with it.
Windows XP absolutely HATES the samsung galaxy nexus.
The don't play along and it's almost impossible to get the drivers (especially MTP) installed correct.
Fortunately I have a W7 BEAST rig at home.. But the work XP pc can't handle the Nexus
Hi guys,
Just wanted to put it out there that I'm totally new at this rooting, custom ROM thing, and I got excited which led me to fail the number ONE rule of backing-up your phone!
Anyways, here's the situation
- Rooted my HTC One X
- Tried to install a custom ROM (IceCold Jelly)
- Phone went into bootloop, after the pink unicorn screen
Some facts
- I can get into the bootloader
- When I plug the phone into the PC, PC makes a sound, but it does not recognize the phone at all
- PC detects a "fastboot" device, but no phone
- went through a few "How to save a soft-bricked" phone tutorial to no avail
- fastboot cmd stuff don't work
- i have boot.img, fastboot.exe etc all on my pc
- drivers and htc sync up to date
I'm sorry if its been answered, but in the bunch of threads I've looked at, everything revolves around being able to use the CMD and the PC actually detecting the phone. Couldn't find any way of fixing my phone, as I said above, the PC doesn't register that theres anything connected to it.
I'd appreciate some help, its been a couple of days, and having no phone is really really hurting!
I'm really really new at this, so I apologize in advance if I don't really understand the terminologies used!
Thanks in advance!
What is the output when you run "fastboot devices" from cmd with your HOX connected in fastboot mode?
Michealtbh said:
What is the output when you run "fastboot devices" from cmd with your HOX connected in fastboot mode?
Click to expand...
Click to collapse
when i type fastboot devices, it comes up as a serial number then fastboot
but when i type adb devices, nothing
appasionata said:
when i type fastboot devices, it comes up as a serial number then fastboot
but when i type adb devices, nothing
Click to expand...
Click to collapse
That's good, fastboot works.
Flash the boot.img from the rom you're trying to flash by putting it into your fastboot folder and running "fastboot flash boot boot.img" then "fastboot erase cache". Then boot into recovery and perform a full wipe then reflash the rom.
Michealtbh said:
That's good, fastboot works.
Flash the boot.img from the rom you're trying to flash by putting it into your fastboot folder and running "fastboot flash boot boot.img" then "fastboot erase cache". Then boot into recovery and perform a full wipe then reflash the rom.
Click to expand...
Click to collapse
I tried flashing it, the result on the cmd said something about not recognizable internal or external command
appasionata said:
I tried flashing it, the result on the cmd said something about not recognizable internal or external command
Click to expand...
Click to collapse
Are you sure you're typing it correctly? If "fastboot devices" works then those commands should also work.
Try just "fastboot erase cache", without quotation marks of course
Michealtbh said:
That's good, fastboot works.
Flash the boot.img from the rom you're trying to flash by putting it into your fastboot folder and running "fastboot flash boot boot.img" then "fastboot erase cache". Then boot into recovery and perform a full wipe then reflash the rom.
Click to expand...
Click to collapse
Michealtbh said:
Are you sure you're typing it correctly? If "fastboot devices" works then those commands should also work.
Try just "fastboot erase cache", without quotation marks of course
Click to expand...
Click to collapse
Yeah ofcourse typing the exact same things.
Alright lets clear things up,
where should the fastboot folder be? and I type "fastboot flash boot boot.img" right after i type cmd into the windows search bar. Is there anywhereI should be running the cmd from? like the directory of the cmd?
also what boot.img file should it be? custom rom?
Thanks
appasionata said:
Yeah ofcourse typing the exact same things.
Alright lets clear things up,
where should the fastboot folder be? and I type "fastboot flash boot boot.img" right after i type cmd into the windows search bar. Is there anywhereI should be running the cmd from? like the directory of the cmd?
also what boot.img file should it be? custom rom?
Thanks
Click to expand...
Click to collapse
Go to the folder with boot.img and fast boot exe, hold shift and press right mouse button on this folder. Than choose run cmd here (or smthng like this, I don't know how it called in English). Than type commands
Sent from my HTC One X using xda app-developers app
If you'd like a hand, I could help you do it remotely via TeamViewer.
appasionata said:
Yeah ofcourse typing the exact same things.
Alright lets clear things up,
where should the fastboot folder be? and I type "fastboot flash boot boot.img" right after i type cmd into the windows search bar. Is there anywhereI should be running the cmd from? like the directory of the cmd?
also what boot.img file should it be? custom rom?
Thanks
Click to expand...
Click to collapse
You should be running the fastboot commands from the folder your fastboot file is in. Either open a command prompt and cd to your fastboot folder, or navigate to the folder in Windows Explorer and open a command prompt there by holding shift and right clicking and choosing "open command window here".
Your fastboot folder should be in your Android SDK, probably in the root of your C drive. It could be somewhere else though depending on how you set up fastboot and adb in the first place.
The boot.img you want to flash is the one inside the rom.zip you want to flash, this goes for all roms.
Michealtbh said:
You should be running the fastboot commands from the folder your fastboot file is in. Either open a command prompt and cd to your fastboot folder, or navigate to the folder in Windows Explorer and open a command prompt there by holding shift and right clicking and choosing "open command window here".
Your fastboot folder should be in your Android SDK, probably in the root of your C drive. It could be somewhere else though depending on how you set up fastboot and adb in the first place.
The boot.img you want to flash is the one inside the rom.zip you want to flash, this goes for all roms.
Click to expand...
Click to collapse
Thanks for the help guys, I'll keep trying and will let you guys know. I think the root of the problem is that I'm inputting the fastboot commands right as I enter the cmd prompt from the windows search bar.
Will keep you guys posted, thanks for the help so far. Don't have my phone on me this minute as its with my friend whos trying to fix it too, will get it back in the morning!
Alright,
I've tried it now, and now theres a different problem. When I try to get into recovery from the bootloader, a picture of a htc device and red triangle and exclamation mark appears. And the custom rom load screen no longer appears. PC still does not recognize the phone.
Are u installed custom recovery ? Are u unlocked your device via hrc dev website?
Sent from my HTC One X using xda premium
incident said:
Are u installed custom recovery ? Are u unlocked your device via hrc dev website?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I'm not sure.
How do I install a custom recovery at this point? and how do I unlock my device via htc site. If you're talking about unlocked with operator, then yes, its an unlocked phone.
As far as I've read into this issue, I think the problem is that maybe installed the stock recovery but from a different RUU?
appasionata said:
I'm not sure.
How do I install a custom recovery at this point? and how do I unlock my device via htc site. If you're talking about unlocked with operator, then yes, its an unlocked phone.
As far as I've read into this issue, I think the problem is that maybe installed the stock recovery but from a different RUU?
Click to expand...
Click to collapse
I think he means that have you unlocked your bootloader via the htcdev.com website?
Sent from my HTC One X using xda premium
OP's first post states that he tried to install a rom, so his bootloader must be unlocked and a custom recovery must have been installed at some point.
@OP - all you have to do is download a custom recovery (CWM or TWRP) then flash it using "fastboot flash recovery nameofrecovery.img", then follow the steps previously explained to you in this thread.
Problem is though he says he rooted HOX he has no idea about unlocking bootloader at HTC Dev? So when he says he's rooted did he unlock the bootloader? He mentions he has an "operator" unlocked phone, and I think this is where he's getting confused. Otherwise suggesting further flashing will make a bad problem worse.
Also it sounds like he's trying to run CMD from start menu. He needs to run it from from where the fastboot file is located, or at least "point" to it in CMD.
---------- Post added at 06:54 PM ---------- Previous post was at 06:46 PM ----------
If you can get into bootloader as you stated have you tried a factory reset?
appasionata, my offer of helping you do it remotely still stands. As long as your there to plug in and handle the handset, I'm pretty sure (95%~) that we can recovery your handset.
andyharney said:
appasionata, my offer of helping you do it remotely still stands. As long as your there to plug in and handle the handset, I'm pretty sure (95%~) that we can recovery your handset.
Click to expand...
Click to collapse
Thanks, I really appreciate it, I think I might have to resort to this. How do we go about it? shall we talk about it via PM? I'm pretty busy this whole week, so we can do it on the weekends?
Looks like you have a stock recovery, try to install the correct RUU (stock ROM for your phone, manuals, can be found in a sticky post of the ROMs thread). So first get back to stock, then start over and read the f**king manuals very carefully. no offence.
If you don't know what you are doing, please don't start at all.
Manuals: http://forum.xda-developers.com/showthread.php?t=1832891
Sent from my HTC One X using xda premium
was trying to flash cm10 onto my one x from this website:
pocketnow title "Jelly Bean on the HTC One X with CyanogenMod 10 (Video)"
ended up getting stuck one #8 because i assume "Shift+right click in the browser window" means do that in the android sdk program. now my one x wont be able to boot because on my pc it wont work but im now try to attempt at it with my mac. any suggestions on how i can boot it up? even it i do volume down+power button or volume up+down+power button it restarts but stops at the boot logo. your help is greatly appreciated, thanks.
Did you flash the boot.img?
Sent from my HTC One X using xda app-developers app
Shift + Right Click is usually done in Fastboot folder (for me) then click "open command prompt here" to use fastboot commands
Marc199 said:
Did you flash the boot.img?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
that was the next step in the guide but some im not sure how... its my first time flashing on the one x
Can you use fastboot commands with your phone?
If so then extract the boot.img from the rom you want to use, and copy it to the fastboot folder, then right click and open command prompt in the folder and enter the command fastboot flash boot boot.img
craftycarper1 said:
Shift + Right Click is usually done in Fastboot folder (for me) then click "open command prompt here" to use fastboot commands
Click to expand...
Click to collapse
alright thanks ill try that out but the only problem is that i cant seem connect my phone to the computer now as it cant seem to find it. i can enter fastboot mode and all that aswell as cwm. I'll prob just bring it to a cell shop nearby to get their help.
LittleBigTit said:
alright thanks ill try that out but the only problem is that i cant seem connect my phone to the computer now as it cant seem to find it. i can enter fastboot mode and all that aswell as cwm. I'll prob just bring it to a cell shop nearby to get their help.
Click to expand...
Click to collapse
Does it show Fastboot USB on the phone screen when you connect the USB cable to the computer?
craftycarper1 said:
Does it show Fastboot USB on the phone screen when you connect the USB cable to the computer?
Click to expand...
Click to collapse
yes it shows up as red when it says "FASTBOOT USB". damn this 5min per post is annoying
Sounds like everything should work, have you extracted the boot.img from the rom?
place it in the fastboot folder on your computer, then shft+ right click and open command prompt and you should be good to go from there with flashing the boot.img
LittleBigTit said:
yes it shows up as red when it says "FASTBOOT USB". damn this 5min per post is annoying
Click to expand...
Click to collapse
In that state try typing fastboot devices
You should something like HTxxxxxxxxxx fastboot
If the response is blank then you may not have the correct drivers installed for your phone. There are a number of ways to get the drivers; one way is to install PDAnet http://junefabrics.com/android/download.php
You don't even have to complete the whole install, just go until the driver is installed. In any case you can uninstall PDAnet and it will leave the drivers on your system.
When fastboot is finally able to recognize your phone then you can flash the boot.img by doing fastboot flash boot boot.img
(this assumes that boot.img is the actual name of the file, it should be unless you renamed it or downloaded it from somewhere)
is fastboot just a folder i create with the boot.img inside of it?
LittleBigTit said:
is fastboot just a folder i create with the boot.img inside of it?
Click to expand...
Click to collapse
No, fastboot is a tool within the Android SDK. You used it when you unlocked your bootloader.
i bought this phone off another guy who had it rooted and loaded
where is the fastboot folder located in android sdk manager?
Download this file http://www.mediafire.com/?50baad8rykng2j0
Create a folder on your C: drive called fastboot and extract the .zip into the fastboot folder
craftycarper1 said:
Download this file http://www.mediafire.com/?50baad8rykng2j0
Create a folder on your C: drive called fastboot and extract the .zip into the fastboot folder
Click to expand...
Click to collapse
alright ill try that out thanks
ended up bringing my phone to the cell shop. I know its an easy fix but cant seem to find that folder.. they said it was a 50/50 chance and will charge me $80 if they can get it to work...think it was a good idea?
Not really. Seems the only thing your phone needed to boot was the boot.img. That would have been done in a couple minutes. As already said here: you simply need to put the android sdk on your c: drive, put the boot.img in that folder, go into bootloader and connect your device with your pc, it should say fastboot USB, open command prompt, go to the direction of your sdk folder and use the fastboot command to flash the boot.img. It should then boot.
Sent from my HTC One X using xda app-developers app
LittleBigTit said:
ended up bringing my phone to the cell shop. I know its an easy fix but cant seem to find that folder.. they said it was a 50/50 chance and will charge me $80 if they can get it to work...think it was a good idea?
Click to expand...
Click to collapse
Sounds like they haven't got a clue what they're doing.
Should have just done it yourself, it's really not difficult.
hmm okay i might just go back tmr and get it my phone back.. thanks. I'll let you know if I succeed or not
Hi,
I've wrote some days ago this post
Hi there!! First of all thanks for the explanation! I've try to understand in wich position is my KF.... but nothing...
A little bit of history:
KF HXD 8,9
I've rooted the KF, after that I've install Safestrap Recovery APK and successfully flash/install 2 different rom into 2 different rom slot not in the stock rom(backed up in the device).
Great! I've tested both and chose one running well. I've chose to delete one and give to the one more space... 7GB.
Well after the installation I've reboot the device........ white fix logo (all white) on screen.... after some reboot pushing the power button (I don't how) it show a screen where I can chose restore device or reboot. I've restored the device to the default factory...
Well now I really don't know what can I do. The command adb devices doesn't recognize any device. Fastboot: ./fastboot getvar product is waiting for the device...
p.s. Only one positive thing is when I plug the KF with the usb in my MAC start Android Transfer Tool.
Any help or suggestions are welcome.
Thanks.
sorry for the bad english
Click to expand...
Click to collapse
and they move me to this section....
Well now I really don't know what I have to do. And in wich state is my kf... brick/no brick
Plase can you suggest me the right way?
Now I'm using an ubuntu 12.04 as pc, there are some tool or script that can I run into ubuntu?
Thanks.
You should be able to get it into fastboot.
Make sure the tablet is off then run the command.
fastboot -i 0x1949 getvar product
Then turn it back on
macman005 said:
You should be able to get it into fastboot.
Make sure the tablet is off then run the command.
fastboot -i 0x1949 getvar product
Then turn it back on
Click to expand...
Click to collapse
I've run the fastboot command from the platform-tools folder into the Android sdk and...
still < waiting for device >
I think it might be a driver issue. If you open the driver manager does something flash on the screen when the tablet turns on?
macman005 said:
I think it might be a driver issue. If you open the driver manager does something flash on the screen when the tablet turns on?
Click to expand...
Click to collapse
with the mac it's start Android Transfer tool but it say that it can't find the device, into ubuntu 12.40 nothing.