Related
Hey All,
Been rooted/unlocked since launch and the only time I've flashed a ROM to this device was when the IMM76K leak hit. After flashing I lost CWM and root. Didn't worry too much at the time, but the past couple days I've been attempting to get it back.
I cannot, for the life of me, get the Fastboot drivers to work. I've tried every driver I could think of and I constantly get a "Device cannot start (error 10)". I've tried every USB port, multiple cables and even different machines. Everytime I plug the device in while in the bootloader I get the Windows popup that says my device can perform faster if I plug it into a USB 2.0 port.
When I did the update, does the new bootloader now require a different driver? Everything else works. MTP, ADB etc. Just not fastboot.
I'll include the specs at the bootloader screen.
Fastboot Mode
Product Name - tuna
Variant - toro 32GB
HW Version - 9
Bootloader Version PRIMELA03
Baseband Version - I515.FC05 CDMA - I515.FC04
Carrier Info - None
Serial Number
Signing - production
Lock State - Unlock
Has anybody had this problem since flashing to the latest update? Does anybody have any suggestions or advice?
BonzTM said:
Hey All,
Been rooted/unlocked since launch and the only time I've flashed a ROM to this device was when the IMM76K leak hit. After flashing I lost CWM and root. Didn't worry too much at the time, but the past couple days I've been attempting to get it back.
I cannot, for the life of me, get the Fastboot drivers to work. I've tried every driver I could think of and I constantly get a "Device cannot start (error 10)". I've tried every USB port, multiple cables and even different machines. Everytime I plug the device in while in the bootloader I get the Windows popup that says my device can perform faster if I plug it into a USB 2.0 port.
When I did the update, does the new bootloader now require a different driver? Everything else works. MTP, ADB etc. Just not fastboot.
I'll include the specs at the bootloader screen.
Fastboot Mode
Product Name - tuna
Variant - toro 32GB
HW Version - 9
Bootloader Version PRIMELA03
Baseband Version - I515.FC05 CDMA - I515.FC04
Carrier Info - None
Serial Number
Signing - production
Lock State - Unlock
Has anybody had this problem since flashing to the latest update? Does anybody have any suggestions or advice?
Click to expand...
Click to collapse
No, there should not be any issue. I suggest to re-install the fastboot driver. Use 1wayjonny's drivers here.
I've seriously never had any issues whatsoever in any way with the drivers I'm using, and I got them from the knives & forks package. Check my sig.
Well I don't know what's your case but as I do stuff with Nexus, Galaxy tab and lg o2x on my computer sometimes one of the drivers gets messed for randoms reasons.. So I re install drivers and that's it... Try that suggestions
Sent from my Galaxy Nexus using xda premium
No matter what I do I get this error message.
No matter what driver I use. Even the Universal Naked Drivers.
{
"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 just spent the last hour in the hell where everything is great when Android is booted up, but no ADB in fastboot mode.
After trying anything and everything, I got it to work:
1. Installing the Samsung Drivers while Android was up and running.
2. Reboot device to Fastboot (adb reboot bootloader)
Windows 7 now identified the device as "Android 1.0" with a yellow triangle
3. Right click | Update Drivers | Select Device
From list selected Android Phone
The dialog now showed two possible devices : Google and Samsung. Clicking Samsung showed 3 different drivers. Picked the newest.
Accepted warning about unsigned drivers, it installed it. Voila...I now see no more errors.
rmagruder said:
I just spent the last hour in the hell where everything is great when Android is booted up, but no ADB in fastboot mode.
After trying anything and everything, I got it to work:
1. Installing the Samsung Drivers while Android was up and running.
2. Reboot device to Fastboot (adb reboot bootloader)
Windows 7 now identified the device as "Android 1.0" with a yellow triangle
3. Right click | Update Drivers | Select Device
From list selected Android Phone
The dialog now showed two possible devices : Google and Samsung. Clicking Samsung showed 3 different drivers. Picked the newest.
Accepted warning about unsigned drivers, it installed it. Voila...I now see no more errors.
Click to expand...
Click to collapse
I must've done this a million times. Where are the newest drivers? I've downloaded 1.4.6.0 from Samsung's website. If you or somebody has these "newest" drivers, could I please get a link?
I've used the ones from Samsung's website, the Universal Naked drivers, Google's drivers from SDK, Drivers from Galaxy Nexus Toolkit v7, drivers from Galaxy Nexus Root Toolkit 1.4 by WugFresh. I get the same issue with all of them.
BonzTM said:
No matter what I do I get this error message.
No matter what driver I use. Even the Universal Naked Drivers.
Click to expand...
Click to collapse
Uninstall all drivers related to the Galaxy Nexus using Driver Sweeper, then check my signature and give knives & forks a go.
Theshawty said:
Uninstall all drivers related to the Galaxy Nexus using Driver Sweeper, then check my signature and give knives & forks a go.
Click to expand...
Click to collapse
Did one even better. Went to a brand new machine that had never seen an Android phone to be sure I was getting a clean experience.
Firstly, when I plugged the phone in (Android on), immediately said that the device could perform faster if I plugged it into a USB 2.0 port. Problem is, it was a 2.0 port. Got all the drivers installed etc. MTP, PTP, ADB works; granted very slowly because it's only going at 1.1 instead of 2.0.
Rebooted into Fastboot, same problem as before. Device failed to start (error code 10).
I've done just about everything I can think of to do. It's gotta be something wrong with the hardware itself to be doing this. Problem is, how do I send it back if I can't even un-root it and re-lock it.
BonzTM said:
[snip]
I've done just about everything I can think of to do. It's gotta be something wrong with the hardware itself to be doing this. Problem is, how do I send it back if I can't even un-root it and re-lock it.
Click to expand...
Click to collapse
Have you checked your USB port on your device? Is it dirty/bent/etc? I doubt there is anything wrong with your phone besides that.
And yes, there is no way to re-lock the bootloader if you can't plug into a computer OR if you don't have root.
efrant said:
Have you checked your USB port on your device? Is it dirty/bent/etc? I doubt there is anything wrong with your phone besides that.
And yes, there is no way to re-lock the bootloader if you can't plug into a computer OR if you don't have root.
Click to expand...
Click to collapse
It seems to be fine. :crying:
BonzTM said:
It seems to be fine. :crying:
Click to expand...
Click to collapse
Try using a different cable. I just went through the exact same experience. Hours of not being able to get fastboot drivers to work (ADB would though!).
I have a small desk dock that I got off of E-Bay, and I too was getting the USB 1.1 speed warnings when using it. Never really thought much about it until this particular problem.
I've un-installed, re-installed drivers and done everything short of standing on my head in a corner
Unplugged it from the 'Dock' and used a regular USB2.0 compatible cable, and fastboot fired right up.
(read the guides so please don't just link it....i've seen that on other threads)
for some reason kfu wont install the kindle driver.... (unsigned driver)
it didn't give me a prompt but i went into my driver signing and clicked allow.... still wont go through
can someone help me out please?
(i've only rooted a MT4G and i had no issues back then...)
running windows xp x32
i've been at it for hours and came across one on youtube but it says android composite ADB instead of android ADB
im still on stock 6.3.1 ( no changes have been made yet to the device )
this is the guide i've been reading which kindav just says " ur own your own" to my unsigned driver problem
http://forum.xda-developers.com/showthread.php?t=1552547
NovaxxBite said:
...
this is the guide i've been reading which kindav just says " ur own your own" to my unsigned driver problem
http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
Is that really all it says on the topic? Is "you're on your own" truly what you got out of reading the following?
kinfauns said:
If Windows refuses to install unsigned drivers, that feature must be disabled before continuing. The process differs for various Windows releases, so search Google and find a suitable method for your system.
Click to expand...
Click to collapse
I gave you a "search Google" link. The first item the search returns gives you step-by-step directions on how to get around the problem. Have you read it? Have you tried it?
kinfauns said:
Is that really all it says on the topic? Is "you're on your own" truly what you got out of reading the following?
I gave you a "search Google" link. The first item the search returns gives you step-by-step directions on how to get around the problem. Have you read it? Have you tried it?
Click to expand...
Click to collapse
wow i just reread my post. that wasnt what i meant to say. sorry, i hope/wasnt trying to be rude or offend anyone:angel:
the google link kindav felt like i was on my own...i've searched all over google and all the windows xp steps either say press F8
( no driver option there on my PC) or to click ignore /warn for the dialog prompt
( basically.. no link addressed my issue)
( following the first link)
i'm not getting the dialog to begin with, i've clicked both ignore and warn but nothing works
also... when i click instal.bat i get
'and' is not recognized as an internal or external command ( did i miss a step?)
after that the kindle driving window pops up, i hit next and after not even a split second it says it wouldnt install..unsigned driver
-edit-
tried using 2 other computers...same problem
NovaxxBite said:
wow i just reread my post. that wasnt what i meant to say. sorry, i hope/wasnt trying to be rude or offend anyone:angel:
the google link kindav felt like i was on my own...i've searched all over google and all the windows xp steps either say press F8
( no driver option there on my PC) or to click ignore /warn for the dialog prompt
( basically.. no link addressed my issue)
( following the first link)
i'm not getting the dialog to begin with, i've clicked both ignore and warn but nothing works
also... when i click instal.bat i get
'and' is not recognized as an internal or external command ( did i miss a step?)
after that the kindle driving window pops up, i hit next and after not even a split second it says it wouldnt install..unsigned driver
-edit-
tried using 2 other computers...same problem
Click to expand...
Click to collapse
1) Download KFU from this link http://forum.xda-developers.com/show....php?t=1399889
2) Before you start rooting ur device.. do the below
3) Extract the util.. run the install_drivers.bat.. this will help you install the drivers..
4) Once it is successfully done..follow the steps outlined in the document attached below (install drivers for ur kindle.docx)
5) Next step is to root ur device and install the google framework and market
6) To root your device.. run run.bat.. select option 2 to install the root.. it might take sometime and will restart the kindle and notify you
7) to install the google apps..run option 6 and then select 1.. sit back and watch the magic happen
This should help you.. let me know if you are not able to do it.. it will good if you can tell me in which step you are facing trouble
kishorev said:
1) Download KFU from this link http://forum.xda-developers.com/show....php?t=1399889
2) Before you start rooting ur device.. do the below
3) Extract the util.. run the install_drivers.bat.. this will help you install the drivers..
4) Once it is successfully done..follow the steps outlined in the document attached below (install drivers for ur kindle.docx)
5) Next step is to root ur device and install the google framework and market
6) To root your device.. run run.bat.. select option 2 to install the root.. it might take sometime and will restart the kindle and notify you
7) to install the google apps..run option 6 and then select 1.. sit back and watch the magic happen
This should help you.. let me know if you are not able to do it.. it will good if you can tell me in which step you are facing trouble
Click to expand...
Click to collapse
link broken?
NovaxxBite said:
link broken?
Click to expand...
Click to collapse
Thats wierd.. try it again http://forum.xda-developers.com/showthread.php?t=1399889
:good:
kishorev said:
Thats wierd.. try it again http://forum.xda-developers.com/showthread.php?t=1399889
:good:
Click to expand...
Click to collapse
this is the same link from the guide lol
i can't get past your 3rd step...
(unsigned driver )
ALSO... why cant i get ADB in device manger?
i've installed SDK tool, SDK Platorm-tools, Android 2.3.3 SDK Platform and Google USB Driver via Android SDK Manager
but when i plug in my kindle fire, it's listed under "other" instead ADB or Android ( and no driver can be found for it....)
kfu wont install kindle drivers because its unsigned
i've done the methods to allow it / ignore the warning prompt but again... its not working
(i didn't get a warning btw... it just said it wouldnt install after not even a second)
i've installed a different (non-related) unsigned driver perfectly ( to test ) but when i use kfu, i the unsigned error immediately after clicking next :crying:
and i've tested on 3 computers now...its all the same for me :<
NovaxxBite said:
this is the same link from the guide lol
i can't get past your 3rd step...
(unsigned driver )
ALSO... why cant i get ADB in device manger?
i've installed SDK tool, SDK Platorm-tools, Android 2.3.3 SDK Platform and Google USB Driver via Android SDK Manager
but when i plug in my kindle fire, it's listed under "other" instead ADB or Android ( and no driver can be found for it....)
kfu wont install kindle drivers because its unsigned
i've done the methods to allow it / ignore the warning prompt but again... its not working
(i didn't get a warning btw... it just said it wouldnt install after not even a second)
i've installed a different (non-related) unsigned driver perfectly ( to test ) but when i use kfu, i the unsigned error immediately after clicking next :crying:
and i've tested on 3 computers now...its all the same for me :<
Click to expand...
Click to collapse
What you can do is try adding the drivers manually to ur device instead of running the .bat file.. using the update driver option in ur device manager..
The driver will be available in the folder Kindle Fire Utility\drivers\kindle
kishorev said:
What you can do is try adding the drivers manually to ur device instead of running the .bat file.. using the update driver option in ur device manager..
The driver will be available in the folder Kindle Fire Utility\drivers\kindle
Click to expand...
Click to collapse
thanks, that seemed to work
now under android phone, i have Android Composite ADB Interface
-sigh-
when i checked cmd.exe for adb devices, it says
List of devices attached
( shows nothing )
well at this point, i've tried 4 different computers...
3 windows xp x32
1 windows 7 x64
On windows 7, the kfu installed the drivers but when i click run.bat , i get
adb offline
Boot status : unknown
Ive tried uninstalling, reinstalling, manually installing, rebooting computer and device
( everything i can find on xda and google )
nothing works
please help :/
Sent from my HTC Glacier using xda app-developers app
NovaxxBite said:
well at this point, i've tried 4 different computers...
3 windows xp x32
1 windows 7 x64
On windows 7, the kfu installed the drivers but when i click run.bat , i get
adb offline
Boot status : unknown
Ive tried uninstalling, reinstalling, manually installing, rebooting computer and device
( everything i can find on xda and google )
nothing works
please help :/
Sent from my HTC Glacier using xda app-developers app
Click to expand...
Click to collapse
Did u try changing the boot mode by selecting the option 1 (Boot Mode menu)
What error message did u c then?
Was the KFU able to restart ur kindle?
Recovery and Normal hangs on waiting while fastboot gives the " oops " error
no kfu never restarted my device
here's a screenshot from my XP computer ( its the same results on each computer )
( the boot menu is from trying to use fastboot mode )
{
"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"
}
there a problem with XP vendor code? apparently
"Thepooch" fixed that for me and showed me how to work kfu so thanks
thanks "kishorev" for helping out also btw
The kindle fire's vendor id was missing from adb_usb.inf . It was just a matter of opening adb_usb.inf with notepad and adding and saving this change.
Code:
0x1949
Then KFU could recognize the kindle as online bootmode 4000.
NovaxxBite said:
well at this point, i've tried 4 different computers...
3 windows xp x32
1 windows 7 x64
On windows 7, the kfu installed the drivers but when i click run.bat , i get
adb offline
Boot status : unknown
Click to expand...
Click to collapse
I hope this isn't redundant or anything, but if you still have your Windows 7 machine still handy, try rolling back the driver. That's how I got mine to work. It should be listed under Android Phone -> Android ADB Interface in the first place. If not, try reinstalling the drivers first.
I hope this helps!
jma9454 said:
I hope this isn't redundant or anything, but if you still have your Windows 7 machine still handy, try rolling back the driver. That's how I got mine to work. It should be listed under Android Phone -> Android ADB Interface in the first place. If not, try reinstalling the drivers first.
I hope this helps!
Click to expand...
Click to collapse
thanks, unfortunately the win 7 laptop i used was borrowed
( i need to get one... XP drivers are crappy lol )
but i'm sure this will help someone whos having this problem, searches xda or google and comes across this :highfive:
Alright, you've been messing around with Windows for far too long. Now it's time to do it the right way.
Indeed I second that the right way
Thepooch said:
Indeed I second that the right way
Click to expand...
Click to collapse
soupmagnet said:
Alright, you've been messing around with Windows for far too long. Now it's time to do it the right way.
Click to expand...
Click to collapse
nice. thanks & thanks again :victory:
:highfive:
[Q] i747 (AT&T) Galaxy S3. No Rom, No recovery. Odin not recognized by Win7. Screwed?
THREAD CLOSED:Final update made
Solution: JTAG. I have updated the main page for anyone who comes across this in their troubles. Try the advice in this thread. It's good advice. I just couldn't be helped. These guys are smart as ****. Take their advice. Good luck, and good night.
Original post
Alright, I'll give as much info as possible. If anyone can save me from having a $250 paperweight, I would... Well, probably whatever they asked me to. Here it is in a nutshell. I was on AOKP with TWRP recovery. I jump ROMS everyday it seems, so why would today be any different? I boot into TWRP, make a backup, wipe cache, factory reset (data and cache), delvik cache, and then system (here was my mistake). Then I was going to install another ROM when I was suddenly needed by family. In my infinite genius I decided "Oh I'll just shut down without a ROM installed, that'll go well!" and shut the phone down through TWRP options (/facepalm).
Finally, I come back to it and decide "Ok, I'd like to install a ROM now". I boot it up (holding up, home, power), but accidentally let go of home and power instead of just power so it tries to boot. No prob, I just do it again. Now I hold it this time and the trusty "teamwin" splash comes up. But something isn't right. It restarts instead of giving me options. "ok...." I think, and I try it again. Same thing. F**k, I have no recovery... So I go to my last resort. Odin mode. I get into Odin Mode, grab my USB cable and plug in (to my computer with drivers already on it from the toolkit) and! TADA! USB not recognized. That's right. USB. NOT. RECOGNIZED.
Recap
So lets recap:
No ROM
No recovery
Drivers from Toolkit installed
Odin Mode = USB not Recognized in Windows
What I tried
Here is what I have tried (in no particular order)
New USB cable. 3 to be exact.
Different ports. All of them on all of the computers.
Different computers. 2 laptops, 2 desktop. All Win 7 64-bit.
Going into recovery (it bootloops)
Letting it boot. (Does nothing)
Uninstalling and reinstalling drivers
Installing Kies
Installing nothing
"adb devices" (doesn't show up)
Using toolkit (no devices seen)
Manually chosing every driver from "Samsung electronics LTD" that my computer has installed.
Plugging in before starting Odin
Plugging in after starting Odin.
Every combination of "Power cycle, Odin Mode, connect to computer" I can think of
Actually praying to Odin
Crying
Giving up
Gaining Second Wind
Searching Google, XDA and numerous forums extensively.
Making a new thread myself
I would really, REALLY appreciate it if someone, somewhere has ANY idea on how I can flash something ANYTHING to my phone again. Thank you SO much for your time. Honestly. I mean it, thank you. Let me buy you a beer. I'm serious.
Extra Info
Extra Information: The pop up is always the "USB not Recognized" balloon. Device manager comes up with an "Unknown Device" and yellow [!] triangle. Sometimes, under details, I'll see "Code 10: Device could not start". To reiterate, the phone WILL go into Odin Mode. Thanks again.
Conclusion:
Windows GS3Toolkit fails to see it
Windows Kies fails to see it
Windows 7 OS fails to recognize it
Windows adb fails to see it
Linux adb fails to see it
Mac OS X heimdall fails to see it
Mac OS X adb fails to see it
My conclusion: For some reason, my phone is reporting itself incorrectly, with a potentially damaged usb port on the phone.
Solution A: Try to JTAG myself. (NOT RECOMMENDED) Pros: Learning. Cons: Too much to buy and ugh. F that noise.
Solution B: (Chosen path) Send to someone to JTAG it for me. Pros: Fast, easy (for me) Cons: $60
Solution C: Sell the phone. Pros: Potentially less cost (through loss) Cons: Time to sell and buy, jockey for prices, potentially lose my ass.
Solution D: Do nothing. Pros: No more loss, no more work, maybe something will come through. Cons: bricked phone
Kilo__ said:
Alright, I'll give as much info as possible. If anyone can save me from having a $250 paperweight, I would... Well, probably whatever they asked me to. Here it is in a nutshell. I was on AOKP with TWRP recovery. I jump ROMS everyday it seems, so why would today be any different? I boot into TWRP, make a backup, wipe cache, factory reset (data and cache), delvik cache, and then system (here was my mistake). Then I was going to install another ROM when I was suddenly needed by family. In my infinite genius I decided "Oh I'll just shut down without a ROM installed, that'll go well!" and shut the phone down through TWRP options (/facepalm).
Finally, I come back to it and decide "Ok, I'd like to install a ROM now". I boot it up (holding up, home, power), but accidentally let go of home and power instead of just power so it tries to boot. No prob, I just do it again. Now I hold it this time and the trusty "teamwin" splash comes up. But something isn't right. It restarts instead of giving me options. "ok...." I think, and I try it again. Same thing. F**k, I have no recovery... So I go to my last resort. Odin mode. I get into Odin Mode, grab my USB cable and plug in (to my computer with drivers already on it from the toolkit) and! TADA! USB not recognized. That's right. USB. NOT. RECOGNIZED.
So lets recap:
No ROM
No recovery
Drivers from Toolkit installed
Odin Mode = USB not Recognized in Windows
Here is what I have tried (in no particular order)
New USB cable. 3 to be exact.
Different ports. All of them on all of the computers.
Different computers. 2 laptops, 1 desktop. All Win 7 64-bit.
Going into recovery (it bootloops)
Letting it boot. (Does nothing)
Uninstalling and reinstalling drivers
Installing Kies
Installing nothing
"adb devices" (doesn't show up)
Using toolkit (no devices seen)
Manually chosing every driver from "Samsung electronics LTD" that my computer has installed.
Plugging in before starting Odin
Plugging in after starting Odin.
Every combination of "Power cycle, Odin Mode, connect to computer" I can think of
Actually praying to Odin
Crying
Giving up
Gaining Second Wind
Searching Google, XDA and numerous forums extensively.
Making a new thread myself
I would really, REALLY appreciate it if someone, somewhere has ANY idea on how I can flash something ANYTHING to my phone again. Thank you SO much for your time. Honestly. I mean it, thank you. Let me buy you a beer. I'm serious.
Extra Information: The pop up is always the "USB not Recognized" balloon. Device manager comes up with an "Unknown Device" and yellow [!] triangle. Sometimes, under details, I'll see "Code 10: Device could not start". To reiterate, the phone WILL go into Odin Mode. Thanks again.
Click to expand...
Click to collapse
Uninstall Kies
Uninstall the Samsung USB Drivers
Run CCleaner
Reboot
Install The Samsung USB Drivers
Go into Download Mode
Open ODIN
Hook up, and see if drivers install and ODIN sees the phone
DirtyOldMan said:
Uninstall Kies
Uninstall the Samsung USB Drivers
Run CCleaner
Reboot
Install The Samsung USB Drivers
Go into Download Mode
Open ODIN
Hook up, and see if drivers install and ODIN sees the phone
Click to expand...
Click to collapse
Followed this to the letter. Didn't work. Thanks though! Can I send you money for a beer?
Kilo__ said:
Followed this to the letter. Didn't work. Thanks though! Can I send you money for a beer?
Click to expand...
Click to collapse
You could do some research into putting twrp on via adb.....or cwm depending on your preference..... if I remeber correctly you need to download the android sdk... I am sure it tells you on the trwp page though....... I know I have adb'd myself out of some tight spots with my transformer and also my old htc hero... haven't commited to changing the s3 yet though... concept is the same....
http://www.teamw.in/project/twrp2/104
Download - Recovery Image Method (using dd):
--------------------------------------------------------------------------------
Select the latest .img file from here
Download the above file. Using adb shell or terminal emulator:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p18
Make certain that you get this command right. Typing the wrong number could result in a brick!
After the SU on the PC i copy paste the command.....
Kilo__ said:
Followed this to the letter. Didn't work. Thanks though! Can I send you money for a beer?
Click to expand...
Click to collapse
It's cool man... If you want me to look at it, PM me, I can probably fix it...
Gage_Hero said:
You could do some research into putting twrp on via adb.....or cwm depending on your preference..... if I remeber correctly you need to download the android sdk... I am sure it tells you on the trwp page though....... I know I have adb'd myself out of some tight spots with my transformer and also my old htc hero... haven't commited to changing the s3 yet though... concept is the same....
http://www.teamw.in/project/twrp2/104
Download - Recovery Image Method (using dd):
--------------------------------------------------------------------------------
Select the latest .img file from here
Download the above file. Using adb shell or terminal emulator:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p18
Make certain that you get this command right. Typing the wrong number could result in a brick!
After the SU on the PC i copy paste the command.....
Click to expand...
Click to collapse
I'm not sure how this applies. I think this is a good solution except that I can't get it to connect to my computer at all. ADB, ODIN, nor Windows 7 will recognize the device in Odin Mode and I have no ROM or recovery installed, and I can't install anything without getting it to connect. I'll keep this in case I can get something to connect and Odin doesn't work, so thank you!
DirtyOldMan said:
It's cool man... If you want me to look at it, PM me, I can probably fix it...
Click to expand...
Click to collapse
I'll talk with you no doubt.
Kilo__ said:
I'm not sure how this applies. I think this is a good solution except that I can't get it to connect to my computer at all. ADB, ODIN, nor Windows 7 will recognize the device in Odin Mode and I have no ROM or recovery installed, and I can't install anything without getting it to connect. I'll keep this in case I can get something to connect and Odin doesn't work, so thank you!
I'll talk with you no doubt.
Click to expand...
Click to collapse
to you start a command prompt, open the directory where adb.exe is. Press and hold shift while right clicking in the window, select open command prompt here...... manytimes if you don't do this ... adb isn't going to work for you.....
Once you do this then type devices if you get your device showing up then you can install twrp or cwm.....
When the instructions say to enter a command, highlight it on the webpage and copy then in your command window right click and paste (control V does not work here)
If you use adb to install anything, that file MUST be in the same directory as the adb.exe
Gage_Hero said:
to you start a command prompt, open the directory where adb.exe is. Press and hold shift while right clicking in the window, select open command prompt here...... manytimes if you don't do this ... adb isn't going to work for you.....
Once you do this then type devices if you get your device showing up then you can install twrp or cwm.....
When the instructions say to enter a command, highlight it on the webpage and copy then in your command window right click and paste (control V does not work here)
If you use adb to install anything, that file MUST be in the same directory as the adb.exe
Click to expand...
Click to collapse
Well that's the thing. It does not show up in devices. ADB will not recognize the device. I'm fairly knowledgeable with using adb and I have 3 versions on my computer. None of the three (adb.exe adb-toolkit.exe or SOCadb.exe) will view it.
{
"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 using another computer that has no trace of android drivers or anything else and installed ODIN and drivers from scratch? Also make sure you are using the stock usb cable. Just wondering if you might potentially have conflicting drivers you are not aware of.
aybarrap1 said:
Have you tried using another computer that has no trace of android drivers or anything else and installed ODIN and drivers from scratch? Also make sure you are using the stock usb cable. Just wondering if you might potentially have conflicting drivers you are not aware of.
Click to expand...
Click to collapse
No I haven't. I can try to do that too. And I have the cable that came with the phone (but I bought it used). I'll try it tomorrow at work
aybarrap1 said:
Have you tried using another computer that has no trace of android drivers or anything else and installed ODIN and drivers from scratch? Also make sure you are using the stock usb cable. Just wondering if you might potentially have conflicting drivers you are not aware of.
Click to expand...
Click to collapse
Kilo__ said:
No I haven't. I can try to do that too. And I have the cable that came with the phone (but I bought it used). I'll try it tomorrow at work
Click to expand...
Click to collapse
Tried it. Unrecognized still. I think I may just be f***ed
Kilo__ said:
Tried it. Unrecognized still. I think I may just be f***ed
Click to expand...
Click to collapse
So when you get into recovery mode (or attempt to) it just reboots after a few seconds ?
You have the teamwin spleash screen and then it doesn't give you time to select any options ? There's really no harm in formating system because it will just boot into twrp without a recovery. You might have a borked recovery but it seems like more. Samsung cords are crap and like to die randomly so another cord is really worth a shot of course make sure it has data.
When you say odin mode I assume you mean download mode and odin just doesn't light up with a com port showing a device ?
hednik said:
So when you get into recovery mode (or attempt to) it just reboots after a few seconds ?
You have the teamwin spleash screen and then it doesn't give you time to select any options ? There's really no harm in formating system because it will just boot into twrp without a recovery. You might have a borked recovery but it seems like more. Samsung cords are crap and like to die randomly so another cord is really worth a shot of course make sure it has data.
When you say odin mode I assume you mean download mode and odin just doesn't light up with a com port showing a device ?
Click to expand...
Click to collapse
No, I don't get any options. "Teamwin" for about 30 seconds. Then black... 5 seconds. Then vibrate twice and then reboot. I think I wiped system, and then TWRP borked as you say. I have used many cords for this.
And yes, the phone goes into Odin mode, but the Odin program doesn't pick it up, neither will ADB and windows says "USB not recognized"
DirtyOldMan said:
Uninstall Kies
Uninstall the Samsung USB Drivers
Run CCleaner
Reboot
Install The Samsung USB Drivers
Go into Download Mode
Open ODIN
Hook up, and see if drivers install and ODIN sees the phone
Click to expand...
Click to collapse
Gage_Hero said:
You could do some research into putting twrp on via adb.....or cwm depending on your preference..... if I remeber correctly you need to download the android sdk... I am sure it tells you on the trwp page though....... I know I have adb'd myself out of some tight spots with my transformer and also my old htc hero... haven't commited to changing the s3 yet though... concept is the same....
http://www.teamw.in/project/twrp2/104
Download - Recovery Image Method (using dd):
--------------------------------------------------------------------------------
Select the latest .img file from here
Download the above file. Using adb shell or terminal emulator:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p18
Make certain that you get this command right. Typing the wrong number could result in a brick!
After the SU on the PC i copy paste the command.....
Click to expand...
Click to collapse
DirtyOldMan said:
It's cool man... If you want me to look at it, PM me, I can probably fix it...
Click to expand...
Click to collapse
Gage_Hero said:
to you start a command prompt, open the directory where adb.exe is. Press and hold shift while right clicking in the window, select open command prompt here...... manytimes if you don't do this ... adb isn't going to work for you.....
Once you do this then type devices if you get your device showing up then you can install twrp or cwm.....
When the instructions say to enter a command, highlight it on the webpage and copy then in your command window right click and paste (control V does not work here)
If you use adb to install anything, that file MUST be in the same directory as the adb.exe
Click to expand...
Click to collapse
aybarrap1 said:
Have you tried using another computer that has no trace of android drivers or anything else and installed ODIN and drivers from scratch? Also make sure you are using the stock usb cable. Just wondering if you might potentially have conflicting drivers you are not aware of.
Click to expand...
Click to collapse
hednik said:
So when you get into recovery mode (or attempt to) it just reboots after a few seconds ?
You have the teamwin spleash screen and then it doesn't give you time to select any options ? There's really no harm in formating system because it will just boot into twrp without a recovery. You might have a borked recovery but it seems like more. Samsung cords are crap and like to die randomly so another cord is really worth a shot of course make sure it has data.
When you say odin mode I assume you mean download mode and odin just doesn't light up with a com port showing a device ?
Click to expand...
Click to collapse
I just wanted to say thank you all for the help on this situation. Nothing has turned up with the phone but I'm 99% sure this isn't a driver thing now. I'm gonna face the music and try to find either a Jtag kit somewhere or possibly someone to buy it from me. If anyone has any ideas on this and wants to weigh in, I'll of course attempt their solution, but I am going to try other solutions now. Once the device has been either sold or fixed, I will close this thread and edit my first thread with the solution for others to see. Again, each and every one of you, thank you. Hopefully, I can return the favor some day
Jtag is a little harsh at this point. That's typically reserved for devices that show absolutely zero signs of life.
mrhaley30705 said:
Jtag is a little harsh at this point. That's typically reserved for devices that show absolutely zero signs of life.
Click to expand...
Click to collapse
Yea, yea it is but I don't know what else to try. I've browsed forum after forum after forum. Of all the people that have received help this problem (Odin is the only choice and isn't recognized), a total of 0 have had something work for them and most threads die unsuccessful. I partially blame the OPs for their lack of through information and replies, but also to the fact that I believe this is just a case of Bad Luck Brian. To have me mess up with the ROM, TWRP take a nose dive, and ODIN play enigma all at the same time seems like a very unlucky scenario.
It has been 8 days now that I've had no phone. Now, I'm not an important person, but I'd at least like to have the phone number I'm paying for, be usable to me. I am really grateful for all of the help and I don't feel slighted or let down in any way, it's just plain and simple that I want a working phone back. If something comes up here before I remedy the situation myself, I'll be sure to let y'all know how it goes, but I'm at the point where I want a usable phone. Again, thank you all for help you have provided and the time you've put into my issue.
Do you have a friend/colleague that also had an s3? Try their computer if you do. They should have the proper drivers installed, so Odin should work. This is the last idea I have. Also, check your pm.
mrhaley30705 said:
Do you have a friend/colleague that also had an s3? Try their computer if you do. They should have the proper drivers installed, so Odin should work. This is the last idea I have. Also, check your pm.
Click to expand...
Click to collapse
Ah, yes. Actually, one of my posts (probably the main one) I bring up 2 laptops and 1 desktop being used, one of the laptops was his. He has an S3 (he's actually the one that pushed me towards getting one). It was the first one with this problem, as I was at his house when it all happened.
I saw that all of your attempted solutions were with a win 7 machine. Have you given using a Linux environment any thought? No drivers to worry about, and if adb will recognize it you can push a recovery, as mentioned earlier
mrhaley30705 said:
I saw that all of your attempted solutions were with a win 7 machine. Have you given using a Linux environment any thought? No drivers to worry about, and if adb will recognize it you can push a recovery, as mentioned earlier
Click to expand...
Click to collapse
I haven't. Is there an easy guide on how to do this or how to get adb on linux?
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
So, after upgrading to Android 8.1 OPP28-85-13 . somehow I could not upgrade to version OPP28-85-16 (OFFICIAL VERSION) and so I tried to update the computer, but the same did not recognizes the cell phone.
I already installed the drivers of the motorola 5x, I changed PC, cable, I activated USB debugging, I already changed that MTP option and nothing! The cell phone does not live on the PC, the only thing that happens is that it carries, nothing else! Does anyone have a solution to this? I'm stuck in a version that still has bugs and I can not update anymore ... I've tried everything!
Excuse my English, I'm from Brazil and I can not find anyone here to solve this.
Assuming you did find the correct OTA to go from OPP28-85-13 to OPP28-85-16, you'd have to go to fastboot, and I doubt those options matter then. Also if you didn't sign up for soak test you wouldn't be able to go from a soak to official version through OTA. Check if your PC recognizes your phone in fastboot.
Hyoretsu said:
Assuming you did find the correct OTA to go from OPP28-85-13 to OPP28-85-16, you'd have to go to fastboot, and I doubt those options matter then. Also if you didn't sign up for soak test you wouldn't be able to go from a soak to official version through OTA. Check if your PC recognizes your phone in fastboot.
Click to expand...
Click to collapse
it does not work in fastboot mode, in fact it is as if the cell phone was dead, it stopped working on the computer, it only loads, I already installed drivers, everything ... but no use, I already tried to use rsd lite but it does not recognize!
Kinda dumb but you're using fastboot command right? Last time that happened to me I was using adb devices and it never showed up
Hyoretsu said:
Kinda dumb but you're using fastboot command right? Last time that happened to me I was using adb devices and it never showed up
Click to expand...
Click to collapse
to recognize in fastboot mode, the cell phone does not need to be recognized on the pc first? I connect the USB cable and it's the same as nothing, besides that, debugging usb also does not work to proceed in fastboot
Nope. If it's in fastboot, it won't get recognized as an actual device, you'll just hear the plugging sound and be able to interact with it via commands
Hyoretsu said:
Nope. If it's in fastboot, it won't get recognized as an actual device, you'll just hear the plugging sound and be able to interact with it via commands
Click to expand...
Click to collapse
{
"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"
}
Does not recognize, neither in fastboot nor in normal mode
@kolple
Hey I know you said you installed drivers and all.. But maybe you should uninstall them and try again. This really sounds like a driver problem honestly.
You could try looking up for UsbDeview on google. It's a pc app which lets you see installed devices.. You could uninstall everything related to your Moto g5.. Then reinstall official Motorola drivers.
Chekm8Qc said:
@kolple
Hey I know you said you installed drivers and all.. But maybe you should uninstall them and try again. This really sounds like a driver problem honestly.
You could try looking up for UsbDeview on google. It's a pc app which lets you see installed devices.. You could uninstall everything related to your Moto g5.. Then reinstall official Motorola drivers.
Click to expand...
Click to collapse
I already tested it on other computers, and the same thing happens, does not install anything, nor does the device manager appear. It is as if the cell phone was no longer receiving data through the cable ... I do not know, it could be an android bug or the faulty usb port, some solution to that?
kolple said:
I already tested it on other computers, and the same thing happens, does not install anything, nor does the device manager appear. It is as if the cell phone was no longer receiving data through the cable ... I do not know, it could be an android bug or the faulty usb port, some solution to that?
Click to expand...
Click to collapse
This is odd for sure. I wish I could help more honestly. Trying USB 2.0 or 3.0 ports doesn't change anything right? Probably not.
kolple said:
Does not recognize, neither in fastboot nor in normal mode
Click to expand...
Click to collapse
I would say update your adb/fastboot
I never use minimal adb/fastboot but always the package that comes with the full android sdk
Also try a different USB cable
And you can try cmd as admin instead of the windows power shell not that it should make a difference
kolple said:
So, after upgrading to Android 8.1 OPP28-85-13 . somehow I could not upgrade to version OPP28-85-16 (OFFICIAL VERSION) and so I tried to update the computer, but the same did not recognizes the cell phone.
I already installed the drivers of the motorola 5x, I changed PC, cable, I activated USB debugging, I already changed that MTP option and nothing! The cell phone does not live on the PC, the only thing that happens is that it carries, nothing else! Does anyone have a solution to this? I'm stuck in a version that still has bugs and I can not update anymore ... I've tried everything!
Excuse my English, I'm from Brazil and I can not find anyone here to solve this.
Click to expand...
Click to collapse
Try using Moto lenovo smart assistant it will flash the latest firmware.
riyan65 said:
Try using Moto lenovo smart assistant it will flash the latest firmware.
Click to expand...
Click to collapse
Really? I didn't even know that.
riyan65 said:
Try using Moto lenovo smart assistant it will flash the latest firmware.
Click to expand...
Click to collapse
No application that will connect USB will not work, nor with debugging, no use! My salvation would be if there was an application that does these methods over wifi.
kolple said:
No application that will connect USB will not work, nor with debugging, no use! My salvation would be if there was an application that does these methods over wifi.
Click to expand...
Click to collapse
Man this is so weird.. In your screenshot the bootloader screen actually detects the phone being connected to usb.
Chekm8Qc said:
Man this is so weird.. In your screenshot the bootloader screen actually detects the phone being connected to usb.
Click to expand...
Click to collapse
Exactly! But it does not recognize on the system, on any computer. In fastboot it appears that it recognized, but without signal ... With the cellphone turned on normal, also nothing appears in the computer, even with usb debugging
kolple said:
Exactly! But it does not recognize on the system, on any computer. In fastboot it appears that it recognized, but without signal ... With the cellphone turned on normal, also nothing appears in the computer, even with usb debugging
Click to expand...
Click to collapse
Have you tried in device manager to scan for hardware changes when the phone is connected? And of course you selected mtp right? Have you selected mtp in developer options? You should try to revoke USB debugging authorizations ( right under USB debugging) this will reset the adb permission you first allowed. You should get prompt for permission again when you type adb devices under cmd ( if phone is seen by pc)
When you check your installed programs on pc do you have other USB drivers installed at the same time as the Motorola ones? If so that might cause some issues.
Chekm8Qc said:
Have you tried in device manager to scan for hardware changes when the phone is connected? And of course you selected mtp right? Have you selected mtp in developer options? You should try to revoke USB debugging authorizations ( right under USB debugging) this will reset the adb permission you first allowed. You should get prompt for permission again when you type adb devices under cmd ( if phone is seen by pc)
When you check your installed programs on pc do you have other USB drivers installed at the same time as the Motorola ones? If so that might cause some issues.
Click to expand...
Click to collapse
I've already changed all these options, I already installed and reinstalled the motorola drivers and nothing works for me
kolple said:
I've already changed all these options, I already installed and reinstalled the motorola drivers and nothing works for me
Click to expand...
Click to collapse
There seems to be quite a few cases like yours if you Google the problem.
Mind looking at this to start with?
https://www.google.ca/amp/s/forum.x...p-problems-8-1-official-windows-t3715171/amp/
Chekm8Qc said:
There seems to be quite a few cases like yours if you Google the problem.
Mind looking at this to start with?
https://www.google.ca/amp/s/forum.x...p-problems-8-1-official-windows-t3715171/amp/
Click to expand...
Click to collapse
did not work, even changing the options MPT, PTP, loading, the device manager did not appear anything either!
@edit
USB HOST DIAGNOSTIC