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
Related
So I have had my Galaxy Nexus since the day it came out, I rooted it before I even activated it.
Like many, I have used all sorts of different ROMs over the year period.
I have never had any problems with adb or anything. I have pushed and pulled files and all of that numerous times.
Until yesterday, I finally upgraded my recovery from an really old (first touch based recovery) to the newest TWRP. It worked fine. I put my phone into fastboot mode, and was able to flash the new recovery through the command prompt (adb/fastboot) on my PC. Then I switched to a new 4.2 rom (Paranoid android 2.99)
So today, I wanted to try some editing on some system files, so I went to go pull some files off of the phone (using adb of course), but now it just tells me that my device is offline.
I tried
"adb kill-server"
"adb start-server"
"adb devices"
It lists my device number, but just says "offline"
I tried to update everything. (Samsung main Drivers - Google's USB SDK drivers - and the newest version of android-sdk)
Also made sure that my USB-debugging was set on my phone.
Even if I put my phone in fastboot mode, it doesn't recognize it anymore. Which is weird because just last night it worked perfectly fine when I upgraded my recovery. I am frustrated to no end...... Can anyone else tell me what I might be missing here?
Nobody?
hxdrummerxc said:
So I have had my Galaxy Nexus since the day it came out, I rooted it before I even activated it.
Like many, I have used all sorts of different ROMs over the year period.
I have never had any problems with adb or anything. I have pushed and pulled files and all of that numerous times.
Until yesterday, I finally upgraded my recovery from an really old (first touch based recovery) to the newest TWRP. It worked fine. I put my phone into fastboot mode, and was able to flash the new recovery through the command prompt (adb/fastboot) on my PC. Then I switched to a new 4.2 rom (Paranoid android 2.99)
So today, I wanted to try some editing on some system files, so I went to go pull some files off of the phone (using adb of course), but now it just tells me that my device is offline.
I tried
"adb kill-server"
"adb start-server"
"adb devices"
It lists my device number, but just says "offline"
I tried to update everything. (Samsung main Drivers - Google's USB SDK drivers - and the newest version of android-sdk)
Also made sure that my USB-debugging was set on my phone.
Even if I put my phone in fastboot mode, it doesn't recognize it anymore. Which is weird because just last night it worked perfectly fine when I upgraded my recovery. I am frustrated to no end...... Can anyone else tell me what I might be missing here?
Click to expand...
Click to collapse
hxdrummerxc said:
Nobody?
Click to expand...
Click to collapse
only thing i can think of right now, before suggesting omap flash or odin, would be try a different usb port, another computer, another OS!
try installing the latest CWM recovery and see if it helps.
hxdrummerxc said:
So I have had my Galaxy Nexus since the day it came out, I rooted it before I even activated it.
Like many, I have used all sorts of different ROMs over the year period.
I have never had any problems with adb or anything. I have pushed and pulled files and all of that numerous times.
Until yesterday, I finally upgraded my recovery from an really old (first touch based recovery) to the newest TWRP. It worked fine. I put my phone into fastboot mode, and was able to flash the new recovery through the command prompt (adb/fastboot) on my PC. Then I switched to a new 4.2 rom (Paranoid android 2.99)
So today, I wanted to try some editing on some system files, so I went to go pull some files off of the phone (using adb of course), but now it just tells me that my device is offline.
I tried
"adb kill-server"
"adb start-server"
"adb devices"
It lists my device number, but just says "offline"
I tried to update everything. (Samsung main Drivers - Google's USB SDK drivers - and the newest version of android-sdk)
Also made sure that my USB-debugging was set on my phone.
Even if I put my phone in fastboot mode, it doesn't recognize it anymore. Which is weird because just last night it worked perfectly fine when I upgraded my recovery. I am frustrated to no end...... Can anyone else tell me what I might be missing here?
Click to expand...
Click to collapse
Try going to settings and look for something related to Root Access and it would have three options:
1. Apps only
2. ADB only
3. Apps & ADB
Choose the 3rd.
You might have to hunt the exact location under Settings where this option will be available as I don't remember them exactly.
Hit Thanks, if this helps...
I looked, but I don't see those settings anywhere.
I tried multiple USB port's. Switching from my USB 3.0 ports to my 2.0 ports. nothing. I can still access the phone storage. So I know it is still connecting to the PC. I could try to boot up linux, but I don't have any of the driver's and sdk tools on my linux drive, and from what I heard it was hard to get it all running in linux.
I guess I could try to change recoveries from TWRP to the newest CWMR,
but last time I turned my phone off, put it in fastboot mode, adb didn't recognize it. So im assuming it won't let me flash anything. Unless fastboot sees it but adb doesn't?
I mean my phone is working perfectly fine, running the new recovery and rom. But I have to be able to connect to adb. Not only for modding but in case of an emergency where I would need to flash.
hxdrummerxc said:
I looked, but I don't see those settings anywhere.
I tried multiple USB port's. Switching from my USB 3.0 ports to my 2.0 ports. nothing. I can still access the phone storage. So I know it is still connecting to the PC. I could try to boot up linux, but I don't have any of the driver's and sdk tools on my linux drive, and from what I heard it was hard to get it all running in linux.
I guess I could try to change recoveries from TWRP to the newest CWMR,
but last time I turned my phone off, put it in fastboot mode, adb didn't recognize it. So im assuming it won't let me flash anything. Unless fastboot sees it but adb doesn't?
I mean my phone is working perfectly fine, running the new recovery and rom. But I have to be able to connect to adb. Not only for modding but in case of an emergency where I would need to flash.
Click to expand...
Click to collapse
I understand your situation... Since you were not able to locate the option suggested, a little Googling answered it's location, check for same and confirm:
Settings > developer options > root access > apps and adb
This should hopefully help resolve the issue.
Hit Thanks, if it helps.
freezer2000 said:
I understand your situation... Since you were not able to locate the option suggested, a little Googling answered it's location, check for same and confirm:
Settings > developer options > root access > apps and adb
This should hopefully help resolve the issue.
Hit Thanks, if it helps.
Click to expand...
Click to collapse
hi. i try all this ways. i know that my usb debuging have problem, in development option i'll checked this, and it says enable. but infact it's not enable and still i got device offline error.
also i use z4root app and when i touch on root, it says that rooting need usb debuging enable (please enable it)!!
then move me to development setting to enable that, but this was checked and enable.
is any way that we make device online from my phone? for example using terminal emulator to turn on usb debuging or turn it off. this way is only my way! any one know some trying this?
i also use usb debugger app, but it move me in settings too! LOL
i need enable my device to root that.
thanks every one
I know this is an old topic, but if somebody else googles it, I had that offline issue, the solution was to upgrade adb : http://stackoverflow.com/questions/10680417/error-device-offline
You simply need to upgrade to the latest version of adb. Went thru this a few weeks ago.
[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?
I have two Nexus 7 2013 one a 16gb and the other a 32gb. I have used Wug's toolkit to upgrade to android 5.0.2. Fro some reason I am now unable to see the 32gb either in adb or mtp. I reboot and get into fastboot and get adb to recognize the tablet. At a loss on what to do. Need some advice. Thanks
gadget069 said:
I have two Nexus 7 2013 one a 16gb and the other a 32gb. I have used Wug's toolkit to upgrade to android 5.0.2. Fro some reason I am now unable to see the 32gb either in adb or mtp. I reboot and get into fastboot and get adb to recognize the tablet. At a loss on what to do. Need some advice. Thanks
Click to expand...
Click to collapse
ADB and Fastboot are not the same. You cannot see the device in ADB while it is in Fastboot mode, and you can't see it with Fastboot when it's booted.
If you can put the device into fastboot by holding the power and volume down and then run "fastboot devices" on your PC, and see it, then fastboot works. With that, you should be able to flash factory images, etc.
If you can't see it in ADB, make sure the device is booted into Android (like I said, ADB won't work when it's off, save for the ADB OTA mode in recovery, to my knowledge), make sure USB debugging is ON in Developer Options (Settings > About > tap build number 7 times to enable), try clearing authorized machines under USB debugging, lastly, try different USB modes. When I was sideloading the 5.2 OTA on my girlfriend's Nexus 6 it wouldn't work in MTP but I switched to PTP and it worked (or maybe the reverse, I don't really remember...).
Those are my suggestions.. hope they help in some way.
Also, LET'S GO WILD.
fury683 said:
ADB and Fastboot are not the same. You cannot see the device in ADB while it is in Fastboot mode, and you can't see it with Fastboot when it's booted.
If you can put the device into fastboot by holding the power and volume down and then run "fastboot devices" on your PC, and see it, then fastboot works. With that, you should be able to flash factory images, etc.
If you can't see it in ADB, make sure the device is booted into Android (like I said, ADB won't work when it's off, save for the ADB OTA mode in recovery, to my knowledge), make sure USB debugging is ON in Developer Options (Settings > About > tap build number 7 times to enable), try clearing authorized machines under USB debugging, lastly, try different USB modes. When I was sideloading the 5.2 OTA on my girlfriend's Nexus 6 it wouldn't work in MTP but I switched to PTP and it worked (or maybe the reverse, I don't really remember...).
Those are my suggestions.. hope they help in some way.
Also, LET'S GO WILD.
Click to expand...
Click to collapse
ADB is enabled, switching back and forth from MTP to PTP does nothing. For whatever reason my pc will not see the tablet. I've uninstalled all the usb drivers I could find for the various devices I own and re-installed just the nexus drivers. Still no luck. I had to use my wifes XP pc to transfer stuff back on the tablet.
Wondering if any of you guys can advise me - having strange problems with fastboot (windows 8.1 and Zenfone 2 ze550ml). Wanted to flash the pre-rooted image to my device so downloaded it and extracted to the flashtools folder and renamed system.img then hooked up my phone. Checked adb drivers were installed and adb devices command returns a code string, so assumed all was good to go with flashing. However, on entering any fastboot command it just sits at "waiting for device". Tried manually starting the phone in fastboot and then connecting it, and this did enable me to execute fastboot commands (reboot or reboot-bootloader work). However, fastboot flash system system.img just results in a message about file size and then "failed to load system.img"
kanagawaben said:
Wondering if any of you guys can advise me - having strange problems with fastboot (windows 8.1 and Zenfone 2 ze550ml). Wanted to flash the pre-rooted image to my device so downloaded it and extracted to the flashtools folder and renamed system.img then hooked up my phone. Checked adb drivers were installed and adb devices command returns a code string, so assumed all was good to go with flashing. However, on entering any fastboot command it just sits at "waiting for device". Tried manually starting the phone in fastboot and then connecting it, and this did enable me to execute fastboot commands (reboot or reboot-bootloader work). However, fastboot flash system system.img just results in a message about file size and then "failed to load system.img"
Click to expand...
Click to collapse
You need to rename the system image to system.img and put it where the fastboot file is. It's looking for it but can't find it.
No, don't think that is my problem - as I said I extracted it to the flashtools folder, so it is already where the fastboot file is. And anyway, though I'd like to solve the problem of flashing the system.img, I am kind of more interested in why I can't get past "waiting for device" without first manually entering the fastboot mode.
Cause Windows sucks. I'm on Linux and no issues. Maybe someone on Windows can chip in?
I can easily do a quick ubuntu install and try it that way if you think it might work better. At the weekend maybe. Could you give me some pointers on how to do it in linux if I do? Would be much appreciated!
kanagawaben said:
No, don't think that is my problem - as I said I extracted it to the flashtools folder, so it is already where the fastboot file is. And anyway, though I'd like to solve the problem of flashing the system.img, I am kind of more interested in why I can't get past "waiting for device" without first manually entering the fastboot mode.
Click to expand...
Click to collapse
I have encountered that problem with the "waiting for device" while I was flashing pre root rom.
Try the cmd adb devices
Then it will list the device connected to the computer...if it says not authorized, then you need to check the phone which is turned on and a pop up window with the RSA key and tap on trust this computer or something..
Then repeat adb devices and it should say allow or something..then it will allow you to flash.
(double check the commands online, I might missed something)
Nah, don't blame Windows... I flashed mine with Windows 10 and worked wonders.
Also... could it be that PC isn't USB 3.0? Perhaps system.img transfer is stopped somewhere during the copying phase?
Thanks, but actually the first time I tried it I did the adb devices command and authorised my pc on the phone. When I connect and do adb devices now it shows the string of numbers code for the device. However, still can't get past "waiting for device"
My pc has both usb 3 and usb 2 ports. Tried on all of them and with various different cables including the asus issued ones, all to no avail.
Can u post a pic of your flashtool folder?
Sent from my Nexus 7
Here is a snap of my platform-tools folder and cmd window
Did you manage to find a solution to this?
I updated the zenfone 2 via OTA to the latest system update.
Ive read and downloaded all relevant files to install the pre root img from the correct sources.
Now when I hold power + vol up. I can see the droid on its back. I choose the RECOVERY option and press power button to select.
When phone reboots it goes to droid icon and says installing system upgrade.................then error appears! No recovery mode!
All the correct drivers are installed into Windows 7, the phone asks me to allow RSA key connection to laptop.
Ive tried the flash tool installer 1.0.7 with phone connected and system img (renamed) and still nothing.
Anyone got any ideas?
Ive factory reset twice in a row and allowed debugging.
Ive placed the (renamed) system.img into the fastboot folder and tried the open command with line ' fastboot flash system system.img' and the reply is usually unable to read system.img or device waiting.
Ive installed the latest android sdk develppment kit and still unable to root using this pre root image.
Im familiar with android and how to follow instructions on rooting, but this zenfone 2 is mind boggling.
Thanks for reading. I know its someone else post. I didnt want to start a fresh post with the same dilemma.
Any advice on whats going wrong would be appreciated.
tsam19 said:
When phone reboots it goes to droid icon and says installing system upgrade.................then error appears! No recovery mode!
Click to expand...
Click to collapse
Hit power and vol up again, just really quickly. Don't hold it, just press and let go. Sometimes it takes several attempts.
hkdmjack, yes your right managed to do it at last.
Cheers
Hi guys, I am facing quite a difficult problem at the moment.
My friend has "accidentally" attempted to use an Asus Zenfone 5 rooting method to root his zenfone 2 550ML.
When I received it to take a look at it, I instantly noticed that I could not get into fast boot (or droidboot). I expected to see usual droid with text on the left side and also expected to be able to select from a number of options using the volume keys (i have some past experience), but instead am met with this solid usb logo. One like this: h ttp://zenfo ne-blog-forum.2 8820.n7.nabble.c om/file/n4 5/P_20140728_051139 .jpg (remove spaces)
I did some research, and found that there were many "bricked" zenfone 5's which were stuck on this usb logo, however this zenfone 2 can start up normally and be used throughout the day normally. Only when I try to enter fast boot, by either ADB commands or by power + volume up, I cannot get past the usb logo.
I have linked up the ZenFone to my computer, and confirmed that ADB devices correctly lists the device (I have usb debugging enabled), however, when I try to go to fast boot and am met with the usb logo, my computer does register and detect the phone, however, under device manager it has a yellow triangle with the device named "" MOOREFIELD". When the ZenFone 2 is in this usb logo state, I cannot access any fast boot commands. I am quite stumped at the moment.
Any help please? By the way, I use a windows 8.1 computer with usb 3 ports. However, I have tested using different cables, and on a windows 7 laptop with usb 2 ports, still to no avail. Should I try and update the firmware using Asus' software? Or is there a better solution?
Thanks
Edit: My friend claims that he did not see at any point in time, the flashing on the zenfone 2 start. He was faced with a "<waiting for devices>" or something similar message, telling me that the phone was not fully in fast boot yet. If I can get it into fast boot, I am sure I can reflash the custom stock onto the phone, and most issues will be resolved.
same error
i have the same error by my zenfone2 after update
please help
amohammadiazar said:
i have the same error by my zenfone2 after update
please help
Click to expand...
Click to collapse
Could you specify which update you did? From your computer? Or via Asus update on ur phone?
pkvk9122 said:
Could you specify which update you did? From your computer? Or via Asus update on ur phone?
Click to expand...
Click to collapse
my orginal firmware is CN and i wanted to change to WW mode i tried by pc .... now when i conect phone t pc it want moorefeild driver for conection and i dont have those ,,
Whenever I try to flash system.img it gets stuck on "writing 'system'..." and just hangs there. I have left it for over half an hour and it still didn't work. Does anyone know a solution to this problem?
Hey guys,
So after a while without any responses, I headed over to Asus customer service to receive a very unhelpful reply.
I gave up hope of finding an answer online and so I decided to take a leap of faith by updating the firmware via the Asus Update app on the phone.
I upgraded from 2.14 to 2.15 and miraculously fastboot seemed to have restored itself. I am not sure whether or not every single update restores fastboot, or whether the update to 2.15 does, but I'm glad that it has been fixed.
My previous problems of being unable to detect fast boot devices has been resolved. Hopefully others who have experienced the same issue can find this post helpful.
Basically, I installed Havoc OS, tried flashing a couple kernels, kept getting systemui crashes, so I decided to dirty flash HavocOS again, and forgot to flash TWRP again before I exited TWRP.
Next, I boot back into my phone, opened Magisk Manager to find that Magisk is not installed, just the manager. I can't install Magisk as I have no TWRP...Which leads me to my next point, trying to boot into recovery brings me no avail as I forgot to flash TWRP. I have zero recovery right now.
Thirdly, HavocOS Suffers from the whole issue of needing SELinux set to permissive, for ADB to work...I can't do that, because I don't have Magisk/root.
Please tell me that someone has an idea here? I'd like to get TWRP back, or back to 100% stock and I can start over, or something other than a custom rom with serious SystemUI crashes and no root...
SOS!
This is not even close to a softbrick. Just boot TWRP using Fastboot and flash the zip from inside TWRP to install it. Also, there are various other solutions to fix your problem. Another one would be to simply use Deuces Recovery Script and go back to Stock.
As d-m-x stated boot twrp with fastboot boot not fastboot flash. Twrp will load into the phone then you can flash twrp and magisk.
I'd tried Fastboot already, will try again momentarily though.
D-m-x said:
This is not even close to a softbrick. Just boot TWRP using Fastboot and flash the zip from inside TWRP to install it. Also, there are various other solutions to fix your problem. Another one would be to simply use Deuces Recovery Script and go back to Stock.
Click to expand...
Click to collapse
Fastboot hasn't worked either. Unless I'm doing something wrong, but I just get "waiting for any device" despite having adb on/off, being in bootloader/fastboot mode or being booted into android, etc.
For Fastboot to work you have to be in the Bootloader Menu. How did you unlock and root your Phone in the first place? That should have taken you through those steps.
Anyways, it's likely that the computer just doesn't recognize the phone. Connect it and go into your Device Manager and see if it's properly recognized. If not install the correct USB Drivers and try again. If everything is set up correctly you can type "fastboot devices" while in the bootloader and you should see your Devices address which means it is connected and ready. Then boot TWRP as stated and install the zip from within.
D-m-x said:
For Fastboot to work you have to be in the Bootloader Menu. How did you unlock and root your Phone in the first place? That should have taken you through those steps.
Anyways, it's likely that the computer just doesn't recognize the phone. Connect it and go into your Device Manager and see if it's properly recognized. If not install the correct USB Drivers and try again. If everything is set up correctly you can type "fastboot devices" while in the bootloader and you should see your Devices address which means it is connected and ready. Then boot TWRP as stated and install the zip from within.
Click to expand...
Click to collapse
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Dragostini said:
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Click to expand...
Click to collapse
Have you tried different USB A to USB C cables and ports?
Dragostini said:
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Click to expand...
Click to collapse
Try these troubleshooting steps:
- make sure you're running the LATEST SDK Tools
- Try diff USB cables (switch from 2.0 to 3.0, or vice versa)
- Try a diff USB port
- Make sure you're in the proper fastboot folder with the fastboot application
- Boot into bootloader type fastboot devices see if you get a serial number
In my sig is a link for troubleshooting, and step by step that includes links to get latest SDK Tools.
If all else fails, I'd reco a fresh factory image install and get back to your cust Rom from there, rather than spend a day or two chasing ghosts.
Good luck!
Az Biker said:
Try these troubleshooting steps:
- make sure you're running the LATEST SDK Tools
- Try diff USB cables (switch from 2.0 to 3.0, or vice versa)
- Try a diff USB port
- Make sure you're in the proper fastboot folder with the fastboot application
- Boot into bootloader type fastboot devices see if you get a serial number
In my sig is a link for troubleshooting, and step by step that includes links to get latest SDK Tools.
If all else fails, I'd reco a fresh factory image install and get back to your cust Rom from there, rather than spend a day or two chasing ghosts.
Good luck!
Click to expand...
Click to collapse
Spoke with Google; getting the phone RMA. Blatantly told the guy it was rooted previously, bootloader unlocked, and running a custom ROM. He said it didn't matter. I will report back on this thread once I have new phone in hand, just to confirm all went well.
Reporting back.
Brought phone to virgin mobile, obviously still heavily modified.
Was given a loaner phone. Signed a paper saying I'd pay 150 for the loaner if it broke. Broke loaner screen same day.
Just picked up a brand new pixel 2 xl they shipped (phone only) because mine was considered unrepairable. I was charged 169 for the loaner phone, to my account with virgin. No cash transaction.
All in all, they honoured googles view of not minding the modifications so long as it's an issue they don't feel is related.
Cheers.