Used the one click el29 root and then used e4gauto, but option c, L just gets me an error:
failed to copy 'copy2sd/000root/superuser.apk -> /sdcard/000root/superuser.apk'
not a directory.
Flashed back to stock el29 and started over, same result. Any idea on how to get clockwork mod flashed onto this phone?
I'd suggest using the Odin method from sfhub (again). Download the file then use something like 7zip or Winzip to extract the actual OneClick.exe file to a folder of your choice. Then run if run it from there. Make sure you are able to boot a few times and all works (I usually use the no data file to preserve my settings). Then head over to the e4gauto etc. One thing I have found (and MANY others too!) is to make sure you use a very good USB cable. I have had SO many problems with roots/etc. because of ****ty cables! It is incredible the amount of time I've wasted when all I needed was to just get a new good USB cable! For printers, phones, cameras and other devices. Good luck
Cannot install clockworkmod
I have tried the odin method several times, both nodata and the one that cleared my settings. I have no problem with rooting. I even urooted back to stock with a factory reset and started over.
I have been using the Samsung usb cable that came with the phone. It has never failed me in the past.
It seems as though eg4auto is trying to access a directory that doesn't exist. On my phone superuser.apk is located in the system\apps directory. I think Eg4auto is looking for 000root\superuser.apk.
bgbuffalo said:
Used the one click el29 root and then used e4gauto, but option c, L just gets me an error:
failed to copy 'copy2sd/000root/superuser.apk -> /sdcard/000root/superuser.apk'
not a directory.
Flashed back to stock el29 and started over, same result. Any idea on how to get clockwork mod flashed onto this phone?
Click to expand...
Click to collapse
It appears you may have missed the pre-requisite that usb storage mode should be disable (ie the android guy should be green)
Cannot install clockworkmod
I thought of that, but you cannot get into usb storage mode when you have USB Debugging ticked. Or am I missing something here?
bgbuffalo said:
I thought of that, but you cannot get into usb storage mode when you have USB Debugging ticked. Or am I missing something here?
Click to expand...
Click to collapse
You can in fact connect to USB storage with debugging enabled.
You must have debugging enabled and USB storage must not be enabled.
Then I must be a complete idiot. if I turn on debugging mode and go to usb storage, it tells me to turn off debugging mode. If I go to usb storage first and get the green man, then go back to tick debugging mode it will not allow it until I disconnect cable.
WoW just WoW. think hard, you can do it, I have faith in ya.
How about a hint?
Well, I was messing around and hit "stop adb". Now I get a "more than one device or emulator". Reflashed el29 with odin one click, but still get the error message.
Hint, you're in the wrong mode (USB). You might want to reread the directions.
cannot install clockworldmod
Ok. Here's what I do. First make sure debugging mode is on. Then connect usb cable. I slide down the notification bar and click on connected to usb which brings me to the screen with the green guy.
At that point I run the program and get an error. What am I missing?
bgbuffalo said:
Ok. Here's what I do. First make sure debugging mode is on. Then connect usb cable. I slide down the notification bar and click on connected to usb which brings me to the screen with the green guy.
At that point I run the program and get an error. What am I missing?
Click to expand...
Click to collapse
Sounds like a bad download. Redownload try it over. report back. I actually have not used this method. I rooted with bubbys **** a long time ago and have never had to go back to stock. But I will try to help ya out.
bgbuffalo said:
Ok. Here's what I do. First make sure debugging mode is on. Then connect usb cable. I slide down the notification bar and click on connected to usb which brings me to the screen with the green guy.
At that point I run the program and get an error. What am I missing?
Click to expand...
Click to collapse
What error are you getting now? Is it the same as before or a different error?
All that part of the script is doing is using adb to push some files to your phone in the /sdcard/000root directory.
If you do "adb shell" and "cd /scard", then type "ls -l", what do you see?
If it has no files or subdirectories, then your /sdcard partition is not visible for some reason.
sfhub said:
What error are you getting now? Is it the same as before or a different error?
All that part of the script is doing is using adb to push some files to your phone in the /sdcard/000root directory.
If you do "adb shell" and "cd /scard", then type "ls -l", what do you see?
If it has no files or subdirectories, then your /sdcard partition is not visible for some reason.
Click to expand...
Click to collapse
Listen to Sfhub. He will not steer ya wrong.
Bear with me here. Do I do those commands on the phone using connectbot in local mode? If so, the adb shell command returns "adb: not found". Or do I need the developer toolkit?
When you plug in the phone as long as usb debugging is on, you shouldn't be clicking on the green android, that would enable usb mode. The files will be pushed thru adb you should not have be clicking anywhere on the green android guy.
bgbuffalo said:
Bear with me here. Do I do those commands on the phone using connectbot in local mode? If so, the adb shell command returns "adb: not found". Or do I need the developer toolkit?
Click to expand...
Click to collapse
Does your USB storage mode look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It should NOT be orange. It should look exactly like the picture above.
If you need to run "adb shell", use Option D, then choose adb shell. If your auto root package doesn't have "adb shell" as an option, get the latest one.
Then type:
Code:
cd /sdcard
ls -l
Yes it looks exactly as pictured. That's why I was sure it wasn't that i had the usb mode wrong. I will try your other suggestion and get back to you.
I got what looks like a directory of the sd card.
Now when I run eg4tauto I am getting daemon not running, adb server didn't ack
Related
I am trying to install the ADB for my G2 and it won't install. I have downloaded the USB drivers, pointed the installation to my android sdk folder and it still comes back and says
Cannot Install this Hardware
I gotta be missing something here. Last time I did this was on my G1, worked fine it seemed, I followed the instructions from way back then. But it seems to be much different now.
Can someone help me with this? I Googled around, but found nothing that helped.
SOLUTION:
I modified and uploaded the usb drivers to work for the G2, these will work fine.
http://www.corylulu.com/usb_driver.zip
Click to expand...
Click to collapse
http://forums.t-mobile.com/t5/Opera...OW-TO-Get-ADB-to-recognize-your-G2/m-p/487554
You can do that or in my case I just forced the driver with Have Disk.
The above solution is more elegant.
This thread was up a few days ago and I wrote out a how to on manually choosing the drivers for mass storage and adb but it vanished somewhere and I haven't been able to find it since I pposted it. I even subscribed to the thread cause that's what I do with threads I've made posts in...
Sent from my HTC Vision
Thanks, got that working perfectly.
I can't get Windows to recognize the new driver. I updated the file as per the thread above, updated the SDK and all, but Windows keeps seeing the phone as USB only. There is an entry under Disks in device manager as HTC Android Phone USB Device, but won't update the driver because it says it's up to date already. Any thoughts?
Make sure you have USB Debugging enabled under Applications. Then select the driver manually using Have Disk.
Sent from my T-Mobile G2 using XDA App
hendusoone said:
Make sure you have USB Debugging enabled under Applications. Then select the driver manually using Have Disk.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Wow do I feel retarded ...I've been so used to my G1 that I completely forgot about the USB debugging option...lol Thanks.
On that note...
philosophics said:
This thread was up a few days ago and I wrote out a how to on manually choosing the drivers for mass storage and adb but it vanished somewhere and I haven't been able to find it since I pposted it. I even subscribed to the thread cause that's what I do with threads I've made posts in...
Sent from my HTC Vision
Click to expand...
Click to collapse
Is this the thread post you were referring to? I couldn't find it either but Google Cache found it:
http://webcache.googleusercontent.c...dating+g2+adb+driver&cd=4&hl=en&ct=clnk&gl=us
philosophics said:
Haven't been able to auto mount a portable device for some time now. Here's what you do, and this is assuming you have the android sdk complete with tools on your system as well.
-Usbdeview (find it, use it, love it)
-Uninstall all htc and android labeled devices (disconnect device/s first)
-Connect device
-Start/right-click on computer
-Device manager
-You'll see android phone with the unknown image next to it.
-Right-click it, update driver
-Let me choose/browse the preconfigured ones.
-You'll see android phone and adb something something in the list, click adb something something
-Select the qualcomm ADB composite ... one and select ok and your good to go.
If you're having problems mounting sd to pc do the same thing EXCEPT
-You'll see android phone and adb something something in the list, scroll all the way down and select universal serial bus controllers
-left column, select compatible usb device
-right column, select mass storage device and select ok
-mount sd card as usual...
When I get to my pc, I'll clean up the how to (remove the something something's along with the ...'s and replace with correct ... directories)
Sent from my HTC Vision
Click to expand...
Click to collapse
NOOB ALERT: Anyone know the correct steps to get adb working with linux(ubuntu)?
What I'ved is to follow other steps for the Vibrant replacing the vid and pid with the one from that thread but its not sticking. Any ideas?
man for the life of me i cant get this thing working at all.
does anyone have a link for the g2 adb driver? i think im going to have to use usbdeview
and now my g2 is being recognized as a usb mass storage device...
any help?
You turned debugging on right?
Sent from my T-Mobile G2 using XDA App
schwiz said:
You turned debugging on right?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
I used the pdanet method. So easy even a caveman could do it lol
You don't need the G2 driver. Just force the ADB driver and it'll work just fine.
What are you talking about ? You need to go in the phone settings under applications and enable USB debugging.
sheek360 said:
I used the pdanet method. So easy even a caveman could do it lol
Click to expand...
Click to collapse
Sent from my T-Mobile G2 using XDA App
schwiz said:
What are you talking about ? You need to go in the phone settings under applications and enable USB debugging.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
i already had that checked on, but by using the pdanet app i was able to force adb to recognize the phone. if u install it on your pc, and connect your phone it will make sure u get adb. works with every phone so far. adb worked for the vibrant, slide 3g, a g1 and a n1 too. every android phone i throw at pdanet is being recognized by adb so far.
Thanks the new driver worked.
xyrcncp said:
Is this the thread post you were referring to? I couldn't find it either but Google Cache found it:
http://webcache.googleusercontent.c...dating+g2+adb+driver&cd=4&hl=en&ct=clnk&gl=us
philosophics said:
Haven't been able to auto mount a portable device for some time now. Here's what you do, and this is assuming you have the android sdk complete with tools on your system as well.
-Usbdeview (find it, use it, love it)
-Uninstall all htc and android labeled devices (disconnect device/s first)
-Connect device
-Start/right-click on computer
-Device manager
-You'll see android phone with the unknown image next to it.
-Right-click it, update driver
-Let me choose/browse the preconfigured ones.
-You'll see android phone and adb something something in the list, click adb something something
-Select the qualcomm ADB composite ... one and select ok and your good to go.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This method worked pretty well, except I chose "Google, Inc." as the category, then specifically chose "ADB Testing Interface" as the driver. Works like a charm!
USB mounting works fine automatically on Windows 7 64-bit.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Link is dead, just brings you to godaddy.
I had a working Kindle Fire. Made a Backup of my OS/ROM using TWRP. Moved that to my Desktop.
Formatted and Installed Stock 6.xx
Rebooted...And now i'm in a static Kindle Fire Logo
Tried Fast (5001), Recovery (4002), Normal (4000)
KFU and Plain adb did not help.
When plugged in.. Green Light, Unplugged No Light.
"If it's not broken, Don't fix it." - My Mom
*Face Palm*
Edit* I tried fastboot oem idme bootmode 4000
Just keep saying < Waiting for Device >
Everything says < Waiting for Device >
It will reboot on Command, but after reboot it does < Waiting for Device >
Iv also seen a post with a Pic and it showed ABCDEF1234567 (Or something like that) when I type adb Devices
Mine says 2DDA002600000001
Edit**
"fastboot -i 0x1949 oem idme bootmode 4000"
&
"fastboot -i 0x1949 reboot"
< Waiting for Device >
I love a fix before Monday (24 Hours From Now)
I really Do not want to buy a Graphing Calculator or Hall Collage / High School Books around.
Looks like we have a similar issue. See my thread over here http://forum.xda-developers.com/showthread.php?t=1838201
There might be something that works for you but not for me.
fixed by monday hmm dont think so http://forum.xda-developers.com/showthread.php?t=1392693 you need fff and twrp back on your device after flashing stock ... did you wipe before flashing it? doesnt sound like it
Believe it or not, your problem is as "simple" (sarcasm implied) as fixing your drivers so the computer can communicate with the device in fastboot mode.
More Help is Needed
soupmagnet said:
Believe it or not, your problem is as "simple" (sarcasm implied) as fixing your drivers so the computer can communicate with the device in fastboot mode.
Click to expand...
Click to collapse
How would I go about fixing my Drivers?
I used Device Manager and uninstalled anything related to the Kindle.
I stopped windows from updating it and installed KFU's Drivers.
*Edit Do I need SDK Installed? Iv just been using KFU.
Ill install anyway.
I also Modded my adb_usb.ini (Or something like that)
**Edit I read a reply you made on another Thread.
Code:
adb shell mkdir /data/local/tmp
[/QUOTE]
Failed
Ill stick with the Drivers for Now as you said.
I tried the Push commands and that works. But any Adb Shell commands does nothing.
Can I push a new Adb Shell or Push FFF (What ever that is) or TWRP and go from there?
I was able to push a fbmode file
Chat_Ghosty said:
**Edit I read a reply you made on another Thread.
Click to expand...
Click to collapse
that was involving a completely unrelated matter
http://forum.xda-developers.com/showpost.php?p=26255153
That post describes how another user fixed the same problem.
soupmagnet said:
that was involving a completely unrelated matter
http://forum.xda-developers.com/showpost.php?p=26255153
That post describes how another user fixed the same problem.
Click to expand...
Click to collapse
I did that to a T.
*Edit: I dont thank this matters. But...
If I turn on the kindle it does one of two things.
#1. Shows KF Logo Bright, Then Dem, Then Bright, then two Green squares apeare on the top and bottom right for 0.2 of a Sec and disappear.
#2. Shows KF Logo, then No Screen and Green Light turns off and screen and light turns back on.
I also included a Picture of KFU.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
have you tried removing the drivers and re-installing them ... i know that it is a pain but it helped me out
Follow http://support.microsoft.com/kb/315539
Open CMD
Code:
set devmgr_show_nonpresent_devices=1
then
Code:
start devmgmt.msc
In device manager do view -> show hidden devices
then remove anything labeled kindle or android adb / android composite
Use KFU install_driver.bat and then play around with KFU to see what happens...
Improvement
Zlatty said:
have you tried removing the drivers and re-installing them ... i know that it is a pain but it helped me out
Follow http://support.microsoft.com/kb/315539
Open CMD
Code:
set devmgr_show_nonpresent_devices=1
then
Code:
start devmgmt.msc
In device manager do view -> show hidden devices
then remove anything labeled kindle or android adb / android composite
Use KFU install_driver.bat and then play around with KFU to see what happens...
Click to expand...
Click to collapse
I did what you said just now and things are now changed.
In Device Manager now says Android adb Interface.
It did say Android adb Composite Interface (Or something like that)
Nothing shows up in adb Devices
KFU Still does nothing and shows nothing.
Ill try some boot commands and see what happens.
Chat_Ghosty said:
Ill try some boot commands and see what happens.
Click to expand...
Click to collapse
It probably won't do any good. You need good communication between the device and your computer (drivers) before anything significant happens. Yes, it's a pain (thank Microsoft), but short of using a different computer or another operating system altogether, it's your only option.
soupmagnet said:
It probably won't do any good. You need good communication between the device and your computer (drivers) before anything significant happens. Yes, it's a pain (thank Microsoft), but short of using a different computer or another operating system altogether, it's your only option.
Click to expand...
Click to collapse
Ill try my Aunts computer. I have never hooked up my Kindle to it.
Ill even install Ubuntu it that will make it work. Ill do just about anything,
Just remember, Linux isn't "plug-n-play" like Windows is. In addition to installing drivers, you have to set up your udev rules and make sure you have all of the appropriate libraries and packages installed, which can be complicated for some users. Luckily there's Google.
soupmagnet said:
Just remember, Linux isn't "plug-n-play" like Windows is. In addition to installing drivers, you have to set up your udev rules and make sure you have all of the appropriate libraries and packages installed, which can be complicated for some users. Luckily there's Google.
Click to expand...
Click to collapse
Honestly. What is the fastest and easiest way to fix this?
Ill re-install my OS if I have too.
Will a Factory Cable Work? Illl buy one.
*Side Note - Iv really only used windows. I fix computers, Build, and some light programming if needed. I don't have much money.*
Thank You for your help so far.
Chat_Ghosty said:
Honestly. What is the fastest and easiest way to fix this?
Ill re-install my OS if I have too.
Will a Factory Cable Work? Illl buy one.
*Side Note - Iv really only used windows. I fix computers, Build, and some light programming if needed. I don't have much money.*
Thank You for your help so far.
Click to expand...
Click to collapse
First of all, the factory cable, while it's extremely useful and nice to have, just in case. It won't help you if you can't get the computer to detect properly. If you know someone with a Mac that would be willing to use it for this purpose, it's likely that would be the easiest route. Linux isn't THAT complicated, just different, and you need to be comfortable using the command line, but it is the most likely to work out of all of them.
As far as reinstalling your OS, there are no guarantees that it will fix the problem, only improve your chances. I'm not going to be the one to tell you it's a good or bad idea either way.
I looked into Linux and FireKit. I do not have a Flash Drive but I did some cds.
Took me a few but I got the basics down for Terminal.
I tryed "Sudo ./fk" & "Sudo ./normal_boot"
But it keeps saying no fastboot.
So I downloaded Kindle Fire Utiltiy and placed FireKit in KFU and still nothing.
I understand it says to use Flash Drive. But is that a must??
I looked on Google and YouTube for a How-To and Nothing,
Short answer...yes.
Chat_Ghosty said:
I looked into Linux and FireKit. I do not have a Flash Drive but I did some cds.
Took me a few but I got the basics down for Terminal.
I tryed "Sudo ./fk" & "Sudo ./normal_boot"
But it keeps saying no fastboot.
So I downloaded Kindle Fire Utiltiy and placed FireKit in KFU and still nothing.
I understand it says to use Flash Drive. But is that a must??
I looked on Google and YouTube for a How-To and Nothing,
Click to expand...
Click to collapse
Have you tried to charge the kindle for a whole day with a wall charger? I found it that ever time I had to screw around with a KF, it was much easier to get stuff done with it fully charged.
Per my earlier comment, deleting old drivers somehow also fixes some issues. Try charging your kindle with the wallcharger, get a good microUSB cable and start anew. It took me 3 computers and about 5 hours to get my third KF rooted and booted.... KF:never again
Use this http://forum.xda-developers.com/showthread.php?t=1850038 mint mate 13 32 bit and pendrive universal usb installer cds wont cut it like this will usb sticks are cheap like 5-8 dollars and your set
Thepooch said:
Use this http://forum.xda-developers.com/showthread.php?t=1850038 mint mate 13 32 bit and pendrive universal usb installer cds wont cut it like this will usb sticks are cheap like 5-8 dollars and your set
Click to expand...
Click to collapse
I got a friends Two GB laying around here somewhere. I just need to find. I might just take my Laptop over there this Sunday.
I broke my Kindle Fire Wall Charger. But they are 5v DC. So I cut a Computer PSU and added a MicroB and shorted the PSU to run with out a computer. I can add a tutorial if wanted.
*Note - Computer PSU is a great stable 3.3, 5v, 12v DC Power. And High Amps. Warning! They will kill you.
Example. My PSU does 2.5A @ 5v. You need 0.01 Amps to kill you. That's 2,500x whats needed to kill you.
I installed Ubuntu on my Computer, I then Installed the :idiot-proof" and adb works.
Any command I type from the List I get eather <Waiting for Device> or waiting for OMAP44xx device
I'm trying to use KFU to root, I'm on 6.3.1. I went into device manager on windows and it says "android phone > android adb interface" every time I plug my KF in. So I'm guessing my PC is recognizing it? When I try to open KFU to root it doesn't show up, it still says "adb status: offline". Anyone know what I'm missing? - Thanks
xXezmacXx said:
I'm trying to use KFU to root, I'm on 6.3.1. I went into device manager on windows and it says "android phone > android adb interface" every time I plug my KF in. So I'm guessing my PC is recognizing it? When I try to open KFU to root it doesn't show up, it still says "adb status: offline". Anyone know what I'm missing? - Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1552547
The second post will help you to get your device drivers in order.
xXezmacXx said:
I'm trying to use KFU to root, I'm on 6.3.1. I went into device manager on windows and it says "android phone > android adb interface" every time I plug my KF in. So I'm guessing my PC is recognizing it? When I try to open KFU to root it doesn't show up, it still says "adb status: offline". Anyone know what I'm missing? - Thanks
Click to expand...
Click to collapse
Which version of KFU did you try running.. suggest you try the KFU 0.9.6
my drivers are working. when i plug my KF in i see this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
im also using 0.9.6
i plug my kf into my pc, that above screenshot is what i see so i dunno whats going on?
Did u run the first option to reset the boot mode to normal or fast..
If u run this option u can set ur boot mode appropriately and then root it using option 2 which is burrito root installation
Sent from my MB526 using Tapatalk 2
kinfauns said:
http://forum.xda-developers.com/showthread.php?t=1552547
The second post will help you to get your device drivers in order.
Click to expand...
Click to collapse
kishorev said:
Did u run the first option to reset the boot mode to normal or fast..
If u run this option u can set ur boot mode appropriately and then root it using option 2 which is burrito root installation
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
no i never did that...how do i got about that? im horrible at this, apologies.
xXezmacXx said:
I'm trying to use KFU to root, I'm on 6.3.1. I went into device manager on windows and it says "android phone > android adb interface" every time I plug my KF in. So I'm guessing my PC is recognizing it? When I try to open KFU to root it doesn't show up, it still says "adb status: offline". Anyone know what I'm missing? - Thanks
Click to expand...
Click to collapse
I'll see if I can help. The description of what you are seeing in the device manager "android adb interface" matches the picture in the upper right box in the table you posted. That is the fastboot driver, look at the description in the left column of the table. ADB doesn't work with the fastboot driver. You need to keep playing with drivers until you get the "normal" ADB driver working, see the listing in the lower right box of the table. The word "composite" must appear in the driver description for your computer to recognize your KF as an ADB device. KFU includes and installs both drivers but windows is easily confused and frequently uses the wrong one. Personally I think it is because the KF goes through different modes as it boots up and windows isn't accustomed to a device changing modes, but that is just my guess.
Sent from my Amazon Kindle Fire using xda premium
xXezmacXx said:
no i never did that...how do i got about that? im horrible at this, apologies.
Click to expand...
Click to collapse
Have uploaded some screenshots for you on checking your driver and also how to run ur KFU
Let me know if u were able to succeed
i try adding the drivers again and it says its up to date already. i have no idea what im doing wrong but im sure is something easily fixable. should i press "disconnect" when i plug the kf in or should i leave usb cable screen up?
xXezmacXx said:
i try adding the drivers again and it says its up to date already. i have no idea what im doing wrong but im sure is something easily fixable. should i press "disconnect" when i plug the kf in or should i leave usb cable screen up?
Click to expand...
Click to collapse
Yes, you have to disconnect mass storage to enable debugging.
soupmagnet said:
Yes, you have to disconnect mass storage to enable debugging.
Click to expand...
Click to collapse
sorry for the stupid ? but how do i do that?
edit: i got rooted following this guide: http://forum.xda-developers.com/showthread.php?t=1638452
for some reason KFU doesnt work for me.
hello everyone.
Can anyone help me with unbricking my M8?
Its a live , its reacting on usb connection with my pc, but i can not communicate throug usb, i can not see anything on the phone screen, i can not get it in recovery/bootloader netiher download mode,
yes
Yes its possible.
Open device Manager in windows. Plug in your device an you must see for seconds a new device named qhusb.
You must be fast and right click on this for seconds pop uped device and click properties.
Then look for the Qualcomm bootloader driver With google.qhusb driver.
Then install this driver with the opened properties settings.
If you get this, make a post here.
Good luck.
Hi Konsolen,
Thanks for the reply. I connected the phone, and qualcom hs usb showed up and i have added some screenshot , but i dont exactly understand your last comments qualcom bootloader driver and so on.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
[/IMG]
i added some picture, but where do i find the bootloader driver?
konsolen said:
Yes its possible.
Open device Manager in windows. Plug in your device an you must see for seconds a new device named qhusb.
You must be fast and right click on this for seconds pop uped device and click properties.
Then look for the Qualcomm bootloader driver With google.qhusb driver.
Then install this driver with the opened properties settings.
If you get this, make a post here.
Good luck.
Click to expand...
Click to collapse
It looks that your Windows install it automaticly.
Are the device always in the device manager or only for seconds?
I will upload some tools in my dropbox and send you a link with infos.
Gkhnnn said:
hello everyone.
Can anyone help me with unbricking my M8?
Its a live , its reacting on usb connection with my pc, but i can not communicate throug usb, i can not see anything on the phone screen, i can not get it in recovery/bootloader netiher download mode,
Click to expand...
Click to collapse
Does the M8's screen come on? Any charge LED (and what color)?
Very key detail (among others): what did you do to get the phone into this condition?
m8
the notification light flashes for a second when connecting to a charger. it flashes also when connecting to pc. also flashes when holding power butt for 15sec.
i installed cm12 but i couldnt use my navigation as the ohone couldnt find any sattelites.
so i tried several firmwares and after changing to supercid i managed to update firmware and hboot. after installing cm12 the phone asked me for a password and i found the installation was corrupt somehow. i find some commands i typed in recovery twrp but it freezed and after a forced restart i saw red triangles on each corner and has never seen anytging on scrreen since. always black.
Gkhnnn said:
the notification light flashes for a second when connecting to a charger. it flashes also when connecting to pc. also flashes when holding power butt for 15sec.
Click to expand...
Click to collapse
Red LED? I asked what color before.
Gkhnnn said:
after installing cm12 the phone asked me for a password and i found the installation was corrupt somehow. i find some commands i typed in recovery twrp
Click to expand...
Click to collapse
That is remarkably vague. What commands exactly?
m8
sorry, the color is orange.
i'm on phone now and can send the commands i have tried
but the codes never worked but i believe i managed to delete a wrong partition .
when onnecting Phone to pc, 14 disk partition shows up, only 4-5 of them has files inside.
konsolen said:
It looks that your Windows install it automaticly.
Are the device always in the device manager or only for seconds?
I will upload some tools in my dropbox and send you a link with infos.
Click to expand...
Click to collapse
Device is always in the device manager. If i remove the driver it shows up as qusb bulk with question-mark.
I tried to download several driver but i couldnt get the device in fastboot or download mode.
I look forward to your link
Thanks
m8
redpoint73 said:
Red LED? I asked what color before.
That is remarkably vague. What commands exactly?
Click to expand...
Click to collapse
TWRP after installing a rom giving me "unable to mount data" all the time.
I done a research and found out that i could type following commands and get it work.
cd /d c:\mini-sdk
adb push mkfs.ext4 /tmp
adb shell
chmod 777 /tmp/mkfs.ext4
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p37
But i heard from somebody that these codes were for HTC M7 and not M8
What carrier or region (CID)?
m8
redpoint73 said:
What carrier or region (CID)?
Click to expand...
Click to collapse
Its a Verizon , i live in Europe, but i got the phone for free from company i worked in.
This is a pic i took for a weeks ago.
[/IMG]
Why not just try and flash the RUU?
http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
That might at least get it working again, as you can do it via a microSD card
m8
i have now downloaded the standalone zip and copied that to sd card, renamed to 0P6BIMG.zip
as the screen doesnt show anything, i have powered on with vol down, i assume the hboot ask for vol up for continue to installing, now i wait but i dont thing anything happens
The exe RUU says "USB error, could not connect to the phone"
m8
When connecting the phone to pc, as said before 14 disk partition opens up, and here are the folder which contains the files showed
[/IMG]
[/IMG]
[/IMG]
[/IMG]
m8
When the phone connected to my pc , its shows in device-manager:
PORTS: Qualcomm HS-USB Diagnostics 9006 (COM12)
Ah, right. Yeah you've bricked the phones internal memory. Not sure if it's repairable but if it is it's WELL over my head...
EddyOS said:
Ah, right. Yeah you've bricked the phones internal memory. Not sure if it's repairable but if it is it's WELL over my head...
Click to expand...
Click to collapse
Screen not coming on, and device showing as Qualcomm on PC is a bad sign. Agree it might not be recoverable.
Someone did the same thing (M7 internal storage "fix") a week or 2 ago. I'll see if I can find the thread, and if there was any favorable outcome.
But extreme care needs to be taken before manually messing with partitions like the OP did. A single mis-typed character can be disastrous. And there are safer ways to have recovered from the fairly common internal storage issue (format with computer or in TWRP).
redpoint73 said:
Someone did the same thing (M7 internal storage "fix") a week or 2 ago. I'll see if I can find the thread, and if there was any favorable outcome.
Click to expand...
Click to collapse
That someone is the same one
And what I know ... that's a hard brick .. corrupted partition
TLDR: p2xl won't adb or fastboot on my mac
Lets see if you guys can help, or if my phone is stuck here.
I updated to December 2017 update
Used adb to root with magisk and twrp 3.1.1 beta 2 I believe
I noticed twrp wouldn't work when I would boot into it using the hardware buttons
Did some research and discovered that if you flash a custom kernel it would solve that issue.
When I went to push twrp img to my phone & I noticed my phone's adb stopped connecting to my Mac. I wouldn't get any response from the Mac. It was if I had just plugged my phone into a wall USB to charge. I tried the usb configurations, toggling USB debugging, toggling developer mode, restarting both devices & nothing (I tried on my 2 macs & tried 2 different cables & a micro USB to USB c adapter.)
I let about 4 months pass by and yesterday I decided I would try to fix this issue again.
I selected factory reset & when the phone rebooted into twrp to reset, it asked for a password and twrp started working again. I did a normal reboot & thought the issue was fixed. I booted into twrp again and did the factory reset & flashed flash kernel and twrp was working again.
I decided I would update the phone to the newest update. So I turned on USB debugging and plugged in my phone to my Mac to adb the newest update & still nothing.
So I decided to try to take the ota but it didn't work because of the custom kernel I flashed.
I read somewhere on here that you can flash the boot.img of your current version thru twrp. It would put me back at the stock recovery & kernel. I extracted the boot.img from the zip and flashed it with twrp. And it said it flashed fine. I booted up and checked the kernel and it's was still on the flash kernel. Went back to recovery and now I get the broken Android with the red triangle & I can't get into stock recovery from there by pressing the volume up + power or any other combo.
So now I'm here with a phone that won't adb or fastboot. Doesn't have a working recovery. & Can't take an ota.
Thanks for reading ^_^
What do you think I should do next?
Desert.pro.riders said:
TLDR: p2xl won't adb or fastboot on my mac
Lets see if you guys can help, or if my phone is stuck here.
I updated to December 2017 update
Used adb to root with magisk and twrp 3.1.1 beta 2 I believe
I noticed twrp wouldn't work when I would boot into it using the hardware buttons
Did some research and discovered that if you flash a custom kernel it would solve that issue.
When I went to push twrp img to my phone & I noticed my phone's adb stopped connecting to my Mac. I wouldn't get any response from the Mac. It was if I had just plugged my phone into a wall USB to charge. I tried the usb configurations, toggling USB debugging, toggling developer mode, restarting both devices & nothing (I tried on my 2 macs & tried 2 different cables & a micro USB to USB c adapter.)
I let about 4 months pass by and yesterday I decided I would try to fix this issue again.
I selected factory reset & when the phone rebooted into twrp to reset, it asked for a password and twrp started working again. I did a normal reboot & thought the issue was fixed. I booted into twrp again and did the factory reset & flashed flash kernel and twrp was working again.
I decided I would update the phone to the newest update. So I turned on USB debugging and plugged in my phone to my Mac to adb the newest update & still nothing.
So I decided to try to take the ota but it didn't work because of the custom kernel I flashed.
I read somewhere on here that you can flash the boot.img of your current version thru twrp. It would put me back at the stock recovery & kernel. I extracted the boot.img from the zip and flashed it with twrp. And it said it flashed fine. I booted up and checked the kernel and it's was still on the flash kernel. Went back to recovery and now I get the broken Android with the red triangle & I can't get into stock recovery from there by pressing the volume up + power or any other combo.
So now I'm here with a phone that won't adb or fastboot. Doesn't have a working recovery. & Can't take an ota.
Thanks for reading ^_^
What do you think I should do next?
Click to expand...
Click to collapse
The first thing I would do is take a drink!! Wow! Seems you have quite the mess on your hands. Seriously though, you really can't do much until you get fastboot working. Question, when you unlocked the bootloader, did you run BOTH unlocking commands??? Also, is OEM unlocking and USB debugging still enabled from the developer options menu??
Do you have the latest SDK/platform-tools on your pc? Have you tried different USB cables and ports??
Here's a recovery thread you may want to look at to help you along and get you back up and running :good:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
I believe I only used the unlock critical, but I unlocked the bootloader before I did the December update. Not sure that has anything to do with it?
Oem unlocking is enabled, but it is greyed out in the on position. I'll attach picture. And USB debugging is enabled as well
I updated to the latest platform tools yesterday, I tried on my two macs & swapped ports and tried my two different cables that I had on hand, maybe today I'll see if I can get anything with my buddy's pc. Windows 7 I believe.
And okay I'll look getting the recovery going again
Thanks a lot ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I believe I only used the unlock critical, but I unlocked the bootloader before I did the December update. Not sure that has anything to do with it?
Oem unlocking is enabled, but it is greyed out in the on position. I'll attach picture. And USB debugging is enabled as well
I updated to the latest platform tools yesterday, I tried on my two macs & swapped ports and tried my two different cables that I had on hand, maybe today I'll see if I can get anything with my buddy's pc. Windows 7 I believe.
And okay I'll look getting the recovery going again
Thanks a lot
View attachment 4492382
Desert.pro.riders said:
I believe I only used the unlock critical, but I unlocked the bootloader before I did the December update. Not sure that has anything to do with it?
Oem unlocking is enabled, but it is greyed out in the on position. I'll attach picture. And USB debugging is enabled as well
I updated to the latest platform tools yesterday, I tried on my two macs & swapped ports and tried my two different cables that I had on hand, maybe today I'll see if I can get anything with my buddy's pc. Windows 7 I believe.
And okay I'll look getting the recovery going again
Thanks a lot ?
Click to expand...
Click to collapse
Well at least you can still get into your OS apparently, which is good. I'm not a Mac guy, so I can't help much in that regard, just seems a bit more quirky when using fastboot. Be interested to know how it goes on the Windows 7 machine. That's what I use without issues at all :good:
Yes! At least the phone os on the phone works fine
Yeah you're right about the macs. They are pretty cool because it works with removable devices without having to mess with drivers. But it sucks when something goes bad because there are really any device managers or drivers to mess with.
Blessing/curse.
I'm usually a pc dude too, but my ex took my PC ?
Well once I get home from school I'll get to trying to fix this once again
Badger50 said:
Well at least you can still get into your OS apparently, which is good. I'm not a Mac guy, so I can't help much in that regard, just seems a bit more quirky when using fastboot. Be interested to know how it goes on the Windows 7 machine. That's what I use without issues at all :good:
Click to expand...
Click to collapse
So the windows PC does detect that something gets plugged in But this the only thing that happens
This sucks
Edit:
I was able to get into stock recovery now. But I don't think you can do much from there.
Adb & fastboot continue to be unresponsive
..
Well couple things about Mac, you don't need any usb drivers for it. To view the file contents of the /sdcard you need Android File Transfer --> https://www.android.com/filetransfer/ plug in your phone then make sure you change it to MTP on the phone. As for adb and fastboot in terminal, download the latest platform tools for mac --> https://developer.android.com/studio/releases/platform-tools You will get a folder called "platform-tools" put that folder some where you like on your mac. I put mine at /Users/"my username"/platform-tools So to get it working correctly you need to open terminal and run "cd ~/" [no quotes on these commands btw] then run "sudo nano ~/.bash_profile" when nano opens it should be blank, type on the first line export PATH="$PATH:your/path/to/platform-tools" [with the quotes on that one]. In my case mine is export PATH="$PATH:~/platform-tools" or export PATH="$PATH:Users/ericarthurc/platform-tools"
Just make sure you get the right file path and that its writing correctly; then type ctrl + x and then y for yes to save. Then in terminal type source ~/.bash_profile
Quite terminal and relaunch, run the command "adb version" you should now see the correct file path and no errors; run adb device now and it will start the adb server
I never had problems connecting my Pixel to mac, even to other hackintosh...
I have Android File transfer installed and no SDK platform tools.
Usually I just download the package from Google and place it somewhere. Than opening Terminal, going into that folder, which btw contains adb and fastboot...
For example: when typing the " ./ adb devices" for the first time, the message about not running / starting Daemon service pops up. This is normal.
I presume that you are using the "./" before every command in Terminal.... This is obligatory on Mac.
Yes so I've gotten adb, fastboot, and the Android file transfer working before on both of my Macs, so I know they are set up right. The problem was when I updated my pixel to the December version via adb. Adb stopped completely working.
I can have my phone booted up and in usb debugging mode and run the "./adb devices" and it'll show the list of devices empty.
Same thing if I put the phone in fastboot and try running "./fastboot devices" it hangs for about a second then it shows up with an empty device list.
I was able to wipe the phone clean with the stock recovery & got my stock kernel back I think.( I'll attach a picture) but I'm still not able to ota to the April patch, I'm thinking because I used twrp right?
Either way I still cant get fastboot & adb working, I've tried my two Macs one in high Sierra & the other on El capitan. And a Windows 10 pc and a combination of about 6 different us cables.
Has anyone ever seen this happen? I think I might have hit a wall here
,,
Ericarthurc said:
Well couple things about Mac, you don't need any usb drivers for it. To view the file contents of the /sdcard you need Android File Transfer --> https://www.android.com/filetransfer/ plug in your phone then make sure you change it to MTP on the phone. As for adb and fastboot in terminal, download the latest platform tools for mac --> https://developer.android.com/studio/releases/platform-tools You will get a folder called "platform-tools" put that folder some where you like on your mac. I put mine at /Users/"my username"/platform-tools So to get it working correctly you need to open terminal and run "cd ~/" [no quotes on these commands btw] then run "sudo nano ~/.bash_profile" when nano opens it should be blank, type on the first line export PATH="$PATH:your/path/to/platform-tools" [with the quotes on that one]. In my case mine is export PATH="$PATH:~/platform-tools" or export PATH="$PATH:Users/ericarthurc/platform-tools"
Just make sure you get the right file path and that its writing correctly; then type ctrl + x and then y for yes to save. Then in terminal type source ~/.bash_profile
Quite terminal and relaunch, run the command "adb version" you should now see the correct file path and no errors; run adb device now and it will start the adb server
Click to expand...
Click to collapse
The way I do it is
1. Open terminal
2.write "cd "
3. Drag the platform tools folder from the desktop to the terminal window
4. Check adb devices , "./adb devices"
I will try to reinstall adb again your way, as I am out of options so anything helps, thanks
Desert.pro.riders said:
Yes so I've gotten adb, fastboot, and the Android file transfer working before on both of my Macs, so I know they are set up right. The problem was when I updated my pixel to the December version via adb. Adb stopped completely working.
I can have my phone booted up and in usb debugging mode and run the "./adb devices" and it'll show the list of devices empty.
Same thing if I put the phone in fastboot and try running "./fastboot devices" it hangs for about a second then it shows up with an empty device list.
I was able to wipe the phone clean with the stock recovery & got my stock kernel back I think.( I'll attach a picture) but I'm still not able to ota to the April patch, I'm thinking because I used twrp right?
Either way I still cant get fastboot & adb working, I've tried my two Macs one in high Sierra & the other on El capitan. And a Windows 10 pc and a combination of about 6 different us cables.
Has anyone ever seen this happen? I think I might have hit a wall here
Click to expand...
Click to collapse
Just outa curiosity, since it appears your stock everything again, do you get any response from Google when you go into....settings/system/system update??
Ericarthurc said:
Well couple things about Mac, you don't need any usb drivers for it. To view the file contents of the /sdcard you need Android File Transfer --> https://www.android.com/filetransfer/ plug in your phone then make sure you change it to MTP on the phone. As for adb and fastboot in terminal, download the latest platform tools for mac --> https://developer.android.com/studio/releases/platform-tools You will get a folder called "platform-tools" put that folder some where you like on your mac. I put mine at /Users/"my username"/platform-tools So to get it working correctly you need to open terminal and run "cd ~/" [no quotes on these commands btw] then run "sudo nano ~/.bash_profile" when nano opens it should be blank, type on the first line export PATH="$PATH:your/path/to/platform-tools" [with the quotes on that one]. In my case mine is export PATH="$PATH:~/platform-tools" or export PATH="$PATH:Users/ericarthurc/platform-tools"
Just make sure you get the right file path and that its writing correctly; then type ctrl + x and then y for yes to save. Then in terminal type source ~/.bash_profile
Quite terminal and relaunch, run the command "adb version" you should now see the correct file path and no errors; run adb device now and it will start the adb server
Click to expand...
Click to collapse
Badger50 said:
Just outa curiosity, since it appears your stock everything again, do you get any response from Google when you go into....settings/system/system update??
Click to expand...
Click to collapse
This, stops before it goes into step 2
disconnect your phone from the mac.
reboot the mac
open developer options on the pixel
disable USB debugging
tap on 'revoke USB debugging authorizations'
enable USB debugging
reboot your phone
plug your phone into the mac again
If all goes well, you will need to authorize it on the phone, and adb/fastboot should work correctly
if you wish to easily install adb/fastboot into your PATH, see here.
That will properly install it, as well as the latest version(s) of each.
uicnren said:
disconnect your phone from the mac.
reboot the mac
open developer options on the pixel
disable USB debugging
tap on 'revoke USB debugging authorizations'
enable USB debugging
reboot your phone
plug your phone into the mac again
If all goes well, you will need to authorize it on the phone, and adb/fastboot should work correctly
if you wish to easily install adb/fastboot into your PATH, see here.
That will properly install it, as well as the latest version(s) of each.
Click to expand...
Click to collapse
Still nothing I tried this a few times & did the path install too
IDK what else there is trouble try I'm pretty much open to anything
Do you guys think I can do anything thru stock recovery?
I tried adb sideload with no success and I tried the apply update thru sd card and I gave me a error unable to mount message?
Desert.pro.riders said:
Do you guys think I can do anything thru stock recovery?
I tried adb sideload with no success and I tried the apply update thru sd card and I gave me a error unable to mount message?
Click to expand...
Click to collapse
You can adb side load from stock recovery as well.
uicnren said:
disconnect your phone from the mac.
reboot the mac
open developer options on the pixel
disable USB debugging
tap on 'revoke USB debugging authorizations'
enable USB debugging
reboot your phone
plug your phone into the mac again
If all goes well, you will need to authorize it on the phone, and adb/fastboot should work correctly
if you wish to easily install adb/fastboot into your PATH, see here.
That will properly install it, as well as the latest version(s) of each.
Click to expand...
Click to collapse
Badger50 said:
You can adb side load from stock recovery as well.
Click to expand...
Click to collapse
If I'm on adb sideload mode & I type adb devices into the terminal, should the serial number show up in the terminal? Because it's not. I'll try messing with it a lil more once I get home from work