Related
Ok. Despite factory resets and clearing google services data, I get google talk authentication errors and error retrieving etc from play store. I've tried a few different versions.
Here's what's great about this phone. It has no sprint service. I can't update the firmware. The USB port will only charge, it won't connect to any computer under any circumstance. It's on gingerbread.
Most apps I try to sideload just say 'app not installed'. Probably incompatible.
Need some suggestions on what to do to unlock the potential of this device (secondhand and headed for someone else to play with). Apparently I can't flash a rom without USB working. Can't use most apps, it's a horrible pain trying to find compatible ones outside the play store.
What to do?
adam.nox said:
Ok. Despite factory resets and clearing google services data, I get google talk authentication errors and error retrieving etc from play store. I've tried a few different versions.
Here's what's great about this phone. It has no sprint service. I can't update the firmware. The USB port will only charge, it won't connect to any computer under any circumstance. It's on gingerbread.
Most apps I try to sideload just say 'app not installed'. Probably incompatible.
Need some suggestions on what to do to unlock the potential of this device (secondhand and headed for someone else to play with). Apparently I can't flash a rom without USB working. Can't use most apps, it's a horrible pain trying to find compatible ones outside the play store.
What to do?
Click to expand...
Click to collapse
It is possible to flash a ROM without USB, but you'll need to use the internet to download the ROM to your device directly. However, you won't be able to flash that ROM properly without USB unless you are already S-OFF, and you already have a custom recovery on it. I don't know of any way to get S-OFF without a USB connection. SO, if you're sitting with a broken USB port, and you're S-ON, the answer is to fix your USB port.
But first, are you sure you loaded the correct usb drivers, and that you're USB cable works? I'd answer that first.
oh yeah that usb port was dead as far as data goes. But that phone is toast now anyways.
So... now that I think with hindsight, I did something pretty stupid, and I'm going to need some help, since I have no idea what to do.
I have a Nexus 9 tablet, and I never liked it. The OS is just so slow and laggy, and it overheats, and it has many other problems. Quite a couple of times, I installed custom ROM's and so on, and I never had a problem. Let me explain what I did now.
Around a month ago, while looking on the internet, I heard this thing that if I install the original software, but with no encryption, it would work better. It sounded cool at the time, so I downloaded the Nexus Root Toolkit, and did it.
Everything went well. But then I heard about a custom ROM that was apparently working even better, Dirty Unicorns, so using the same toolkit, I installed it. For the first time, my Nexus 9 actually worked the way it is supposed to work, but the custom ROM still had its problems, it crashed from time to time. I was thinking about possibly returning or selling the tablet, so that's why using the Toolkit, I reinstalled the original software. But, if I went all the steps, and also locked the OEM, my device then showed a flag saying that it was a development device, while booting up. So, after messing around with the settings of the Toolkit a little, I decided to reinstall the software, but leave the bootloader unlocked.
But after some time, I reinstalled my Windows, and I also reinstalled the Toolkit. But that's when I started to have problems. My tablet wouldn't connect to my laptop anymore. I used the toolkit and uninstalled drivers, reinstalling others quite a couple of times, and that's where I think that I messed something up. I managed to eventually connect my tablet, and I rooted it, after rooting it, I connected it again. But adb wasn't working for some reason. A little annoyed, I simply copy pasted the zip file of CM13 into my tablet's internal storage, and I rebooted it to the recovery, TWRP. But the recovery failed to flash it, saying something about an Error 7.
Now that I think about it, I was stupid, since after that, I performed a complete factory reset, resetting my TWRP backup too. I tried to connect it again, nothing. It didn't connect at all. I plug it in, my computer doesn't even recognize that something is plugged in. No Nexus 9, no Android Device, no anything. I booted it in fastboot mode, and it worked, my computer recognized it, and after I downloaded a ROM zip file again, I tried to connect the tablet back and flash it manually, but nothing. It didn't recognize anything anymore.
I tried to reinstall the drivers countless times. I deleted what I had, reinstalled it, nothing. I uninstalled and reinstalled the Toolkit. But strangely, now, even if I know that I installed the Google USB drivers, and the ADB drivers, as I even installed Android SDK, if I use USB Deview, it doesn't show me any of them. I can't see any Google or ADB drivers, although I tried installing them multiple times. So now, I'm stuck with a tablet with TWRP and no OS, which I can't connect to my PC, and I can't use ADB or fastboot.
Is it something from my laptop? I can't check to see if it will connect to another PC right now, so I don't know for sure. Is there any way to delete all the traces from my (failed) attempts at reinstalling the drivers, and to install them again properly? Or is it something from the tablet itself? I don't have an OS, so I can't enable USB debugging.
So, shortly, I have no idea what's happening. And I'm quite obviously a noob in all of these. Can anyone help me? Please?
If you boot into the bootloader and from a command prompt type fastboot devices you don't get anything?
Sent from my Nexus 9 using XDA-Developers mobile app
I still couldn't get ADB to work, but I managed to work out fastboot. It may be something from my USB cable, it works perfectly.
I flashed the original software back, and I'll go to check my cable, although I feel kinda stupid that I didn't think about that in the first place.
Thanks for the help anyway.
If fastboot is working and bootloader is unlocked, you can still install a factory image.
Depending of your device download for wifi Version:
https://dl.google.com/dl/android/aosp/volantis-mob30p-factory-2cb57a1b.tgz
If you habe the LTE variant:
https://dl.google.com/dl/android/aosp/volantisg-mob30p-factory-ae9ce05a.tgz
Extract the files and put them into the same directory link fastboot and execute the flash-all.bat
WARNING: Any data will be erased!!! Also TWRP
Now it should boot up with stock firmware.
If you want your device decrypted install twrp. format the internal storage and flash the pure nexus rom which i can highly recommend and is decrypted by default. Dont forget do flash gapps
my issue is same
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
rohanzakie said:
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
Click to expand...
Click to collapse
Use fastboot, not adb.
what if fastboot isn't working, either?
uberSkeptic said:
what if fastboot isn't working, either?
Click to expand...
Click to collapse
Is the tablet in fastboot mode?
madbat99 said:
Is the tablet in fastboot mode?
Click to expand...
Click to collapse
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
uberSkeptic said:
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Hi, uberSkeptic...
Just a quick thought... Have you tried a different USB cable?
Rgrds,
Ged.
Edit & Additional...
The command is not fastboot list devices... it's fastboot devices
One last point... Ensure your Nexus 9 is definitely booted into fastboot mode and not just HBOOT (the bootloader). Take a look at the two screenshots below - your Nexus 9 should look like the screenshot on the right, the one with my green explanatory text.
Apologies for the poor image quality; there's no way of taking a screenshot in the bootloader, so I had to take photographs instead.
Hope this helps and good luck.
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
uberSkeptic said:
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
Click to expand...
Click to collapse
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
GedBlake said:
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
Click to expand...
Click to collapse
Sadly, me too. I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Too bad, too - the tablet is otherwise in great condition and even has a custom-painted backplate (long story).
Thanks for trying to help, though!
uberSkeptic said:
...The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Mmm...
uberSkeptic said:
...I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Click to expand...
Click to collapse
Mmm... (scratches head, raises eyebrow quizzically)...
If I was Hercule Poirot and this was a murder case, and with all the suspects gathered in one room, prior to revealing a brilliant deduction... I'd be casting very dark glances in the direction of your Nexus 9's USB port right now as the likely culprit here.
Think about it. Different computers. Different USB cables. An OTG cable... And none of them work. What's the one thing they all have in common?
Answer: The USB port on the Nexus 9 itself, and where you've replaced the USB daughter-board.
Maybe, possibly, that replacement don't go so well. Maybe there's some unknown problem with it. I can't comment too much on this, 'cos it outside the scope of my knowledge - I'm a software guy; circuit boards and dismantling devices to fix 'em isn't something I'm comfortable with. I always think I'm going to damage something or rip a wire out somewhere, so I bow to your superior knowledge in this area, as I may be talking complete cobblers here. It certainly wouldn't be the first time.
Anyway... Sorry I wasn't able to help find a working solution for you. If anything occurs to me that might help, I'll be sure to let you know.
Rgrds,
Ged.
I would be suspect if the replacement as well if it weren't for the fact that I did it only AFTER the other symptoms/problems appeared. Hence the replacement (which is known good because the battery charges no problem). There cables and everything inside the tablet tests just fine... It feels like the firmware for USB is somehow corrupt or something.
Thanks for all the advice, though. ?
So I can't believe I didn't think of this before, but when I run "dmesg" from the terminal app included w/ TWRP, I see that there a TON of errors, mostly referencing problems accessing the recovery image. I could screenshot it, if anyone at all might be able to tell me a little more specifically what the dmesg log is trying to tell me...
Hey guys, new member here but been a lurker off and on for awhile.. not sure what to do, you guys are my last hope.
I have a Samsung Galaxy Core Prime from straighttalk. Android version is 4.4.4 (I think).
Anyway, I was screwing with it trying to speed it up using a few apps I downloaded from the store, the apps let you uninstall apps that the normal manager won't let you and manage what system apps are allowed to run at startup..etc. also I was messing with applock and phone encryption.. So I'm not sure what messed things up.
Well needless to say, I shoulda been more careful, because now my phone is screwed! I can't view my home screen at all so can't call/txt and can't access my settings to try to fix the problem..
Before people tell me to reformat it, I have tried 100 times.. I press volume up + power + home to get to bootloader and tried doing a full reformat as well as wiping the cache partition... Reboot phone the setup screen comes up asking for my name/google account..etc but I can't complete it, it always crashes sayin either "hangouts has stopped working" "setup wizard stopped working" or something about a android.keyguard service.
So next I jumped on Google and read to try the Kies software but I can't for life of me get it to detect my phone.. took awhile but I think I got all the drivers installed.. kies will just say it's connecting to my device but never does. Tried kies 2 and 3 and different cords, I think it's because android isn't even truly fully installed since the setup wizard crashes.. so the MTP capability isn't even there.. under my computer I don't see my phone either like I use to, just a blank drive that has no name and can't be accessed.
So then after more reading I decided to try "ADB sideloading".. I'm a newb is to this stuff so idk if I even did it right but hooked usb up went into bootloader and reformatted/cleared cache then I went to ADB and using cmd on my pc I tried to send a zip of cyanogenmod (got it on xda, suppose to work on galaxy core prime) and it said it was successful but it doesn't do anything.. so idk if it's cuz u can't use custom roms with the stock bootloader? I read about other Rom managers but how am I suppose to install them?
if a stock firmware will work, where can I find one?
Sorry for the wall of text, I'm just stuck here and wanted to add everything I could think of that I tried already.
I dont think it's a physical hardware problem, I think i just screwed some system files up somehow which screwed up the recovery partition..
Extra note:
I am able to use the internet browser though, when the setup gets to the step to link your google, in the top right I can go to "enter browser signin" and then I can bypass the fact there's no search bar by clickin privacy policy and clicking a logo to bring me to Google's homepage.
At this point I don't even care about saving data, what Rom is used or anything. Just wanna be able to text and make calls again.
Forgot to add but using the Google accounts bypass to use the browser I also tried going to google play from there and got the play app to open on my phone but it won't let me install any apps (stuck downloading forever) and will say the app isnt supported on my device even when it should be... tried the android device manager but it cant locate my phone and the reformat option there doesnt work either.
Mr.cryptkeeper said:
At this point I don't even care about saving data, what Rom is used or anything. Just wanna be able to text and make calls again.
Forgot to add but using the Google accounts bypass to use the browser I also tried going to google play from there and got the play app to open on my phone but it won't let me install any apps (stuck downloading forever) and will say the app isnt supported on my device even when it should be... tried the android device manager but it cant locate my phone and the reformat option there doesnt work either.
Click to expand...
Click to collapse
Get a custom recovery (preferably twrp) and then wipe EVERYTHING in the wipe section except your sdcard and then just adb sideload cyanogenmod or any other CUSTOM rom for your phone.
You should just be able to reload the original firmware with Odin. Or Kies will probably work, but you have to use Download Mode to be able to restore it, not while it is booted into the OS.
Thanks for the replies, bit I wish it was as easy as you guys make it sound. Kies isn't working because the MTP driver fails to install on windows no matter what mode I'm in or usb port/cord, no way to access usb settings on phone since I can't get past android setup into the homescreen. Also usb debugging is probably not enabled.. how can I enable that when I can't access settings?
I tried to install TWRP (through adb sideload since can't install anything from store) but when I do "adb devices" nothing is listed.. when I tried it on linux there WAS a device listed though so I did sudo adb sideload twrp.zip from within adb folder and it said it sent it but on my phone it says something about a error verifying it or something then it automatically tries again and says it completed and goes to reboot but it doesn't appear to have worked because there's no sign of it.. is TWRP just suppose to replace the stock bootloader if the sideload is successful? If not how do I access it? Also tried sideloading cyanogen right from the stock bootloader but get the same thing.. says it was sent 100% and phone reboots but there's no sign of it... perhaps I'm doing something wrong?
Argh so frustrating all the time I've wasted trying to fix this. I even completely wiped linux off my pc and installed windows 7 again thinking it was a compatibility problem, but now I think I just went backwards because at least on linux my phone was detected doing "adb devices"...
Mr.cryptkeeper said:
Thanks for the replies, bit I wish it was as easy as you guys make it sound. Kies isn't working because the MTP driver fails to install on windows no matter what mode I'm in or usb port/cord, no way to access usb settings on phone since I can't get past android setup into the homescreen. Also usb debugging is probably not enabled.. how can I enable that when I can't access settings?
I tried to install TWRP (through adb sideload since can't install anything from store) but when I do "adb devices" nothing is listed.. when I tried it on linux there WAS a device listed though so I did sudo adb sideload twrp.zip from within adb folder and it said it sent it but on my phone it says something about a error verifying it or something then it automatically tries again and says it completed and goes to reboot but it doesn't appear to have worked because there's no sign of it.. is TWRP just suppose to replace the stock bootloader if the sideload is successful? If not how do I access it? Also tried sideloading cyanogen right from the stock bootloader but get the same thing.. says it was sent 100% and phone reboots but there's no sign of it... perhaps I'm doing something wrong?
Argh so frustrating all the time I've wasted trying to fix this. I even completely wiped linux off my pc and installed windows 7 again thinking it was a compatibility problem, but now I think I just went backwards because at least on linux my phone was detected doing "adb devices"...
Click to expand...
Click to collapse
Yes you have to be in recovery to actually be able to do adb sideload, try adb reboot recovery.
Hello Everyone
I am putting my problem in this general section with the hope to ask for help to more people compared to the Mate 8 section where not a lot of people go these days.
Since a while I am not able to connect my phone to a laptop. If I connect it to a laptop it just starts charging but nothing else. I have tried everything like:
Changing Cables (tried more than 5. I dont have the original anymore)
Changing Laptops
Changing the USB port of the phone itself
Updating Drivers
Installing Hisuite (current version 5.0.3.300)
Restore phone to factory settings
Complete formatting
Updating to the latest version (Current version Nxt-L29C185B582)
Changing the USB debugging/ Connection (MTP/PTP/etc)
And what not
The problem is, it doesnt get detected on the computer and cant connect to adb as well. All I want is to unlock bootloader and Install TWRP and Magisk. I have the unlock bootloader code but no way to unlock it since I cant connect.
Can anyone help me in fixing this stupid problem ? It is getting frustrating. If there is a hardware issue, what part needs to be replaced? Any help would be appreciated.
USB connection icon on top of the phone when connecting laptop
gandotratushar said:
Hello Everyone
I am putting my problem in this general section with the hope to ask for help to more people compared to the Mate 8 section where not a lot of people go these days.
Since a while I am not able to connect my phone to a laptop. If I connect it to a laptop it just starts charging but nothing else. I have tried everything like:
Changing Cables (tried more than 5. I dont have the original anymore)
Changing Laptops
Changing the USB port of the phone itself
Updating Drivers
Installing Hisuite (current version 5.0.3.300)
Restore phone to factory settings
Complete formatting
Updating to the latest version (Current version Nxt-L29C185B582)
Changing the USB debugging/ Connection (MTP/PTP/etc)
And what not
The problem is, it doesnt get detected on the computer and cant connect to adb as well. All I want is to unlock bootloader and Install TWRP and Magisk. I have the unlock bootloader code but no way to unlock it since I cant connect.
Can anyone help me in fixing this stupid problem ? It is getting frustrating. If there is a hardware issue, what part needs to be replaced? Any help would be appreciated.
Click to expand...
Click to collapse
Go to the Settings of your phone---> About phone----> Build number tap this 7 to 8 times-----> Developers option is enabled----> back to settings ----> go to developers option ----> enable USB debugging.
When you connect to the phone to the laptop you will find an icon on top of the screen of your phone with a USB mark "like a trident", pull down the top menu and find the USB connection tab, (like changing the sim card if you intend to call through a specific card) e.g quoted, double tap the USB tab to obtain options ---> 3 options 1) MTP 2)PTP 3) USB charging only----> select the first option MTP (Media transfer protocol).
Now connect to the laptop you will find exclamation marks in the device manager of your laptop. Load the appropriate drivers on your computer and viola! this will establish connection with the device you are having. if you find difficulty in installing USB drivers, search the thread "Attempt to load USB drivers for Micromax E484 on win XP is a fiasco" in this forum. You will find the solution for USB drivers
http://forum.xda-developers.com/android/help/attempt-to-load-usb-drivers-micromax-t3696432
Regards,
689alza
Thanks for your reply
Go to the Settings of your phone---> About phone----> Build number tap this 7 to 8 times-----> Developers option is enabled----> back to settings ----> go to developers option ----> enable USB debugging.
Already Tried
When you connect to the phone to the laptop you will find an icon on top of the screen of your phone with a USB mark "like a trident", pull down the top menu and find the USB connection tab, (like changing the sim card if you intend to call through a specific card) e.g quoted, double tap the USB tab to obtain options ---> 3 options 1) MTP 2)PTP 3) USB charging only----> select the first option MTP (Media transfer protocol).
Already tried too
Now connect to the laptop you will find exclamation marks in the device manager of your laptop. Load the appropriate drivers on your computer and viola! this will establish connection with the device you are having. if you find difficulty in installing USB drivers, search the thread "Loading USB drivers in Win XP turned to be a fiasco"
Nope. Doesnt happen
When i connect with the laptop, my laptop doesnt even make that sound for the connection.
What is the model and OS version of the device and the model and OS version of the computer? According to your symptoms your phone appears to be in option 3) USB charging only. The phone will not be detected by your laptop or the like(Computer) in this mode. Merely remains in a charging state. Are you certain the option 1) is picked MTP? If the phone is not detected there appears to be some hardware failure, try another USB port to connect to the laptop. if all else fail a service technician will pinpoint the fault. It may perhaps be a data transmission failure of the devices port to the interior of the phone. This is merely an assumption.
best remedy would be a service technician.
Hope this helps
689alza
alza689 said:
What is the model and OS version of the device and the model and OS version of the computer? According to your symptoms your phone appears to be in option 3) USB charging only. The phone will not be detected by your laptop or the like(Computer) in this mode. Merely remains in a charging state. Are you certain the option 1) is picked MTP? If the phone is not detected there appears to be some hardware failure, try another USB port to connect to the laptop. if all else fail a service technician will pinpoint the fault. It may perhaps be a data transmission failure of the devices port to the interior of the phone. This is merely an assumption.
best remedy would be a service technician.
Hope this helps
689alza
Click to expand...
Click to collapse
I have tried changing the usb charging only to all possible options but it still is the same. I tested in Linux and when I connect the phone nothing shows up in the logs. It's like it's not being connected . I have tried changing the usb port itself from the phone but it remained the same.. can the flex cable be a problem ? Mate series was never launched in India so I don't have any help from the service centre. I have to order the spare from eBay.com so there is no qualified technician who can help.. that's why I have to fix it myself somehow..
Thank you for your help
gandotratushar said:
I have tried changing the usb charging only to all possible options but it still is the same. I tested in Linux and when I connect the phone nothing shows up in the logs. It's like it's not being connected . I have tried changing the usb port itself from the phone but it remained the same.. can the flex cable be a problem ? Mate series was never launched in India so I don't have any help from the service centre. I have to order the spare from eBay.com so there is no qualified technician who can help.. that's why I have to fix it myself somehow..
Thank you for your help
Click to expand...
Click to collapse
I quite doubt the cable will be the culprit as your device charges the battery while in an established connection with the laptop. As you state the phone USB port was replaced, it could be a some glitch before the USB port in the device where there is an interruption in the data transmission signal that cannot be detected by your laptop.
Could you boot your device, computer and connect the two and take a snapshot of your device (whilst connected to the laptop) and paste the same in the forum?
Perhaps visual cue could be better at dealing such mishaps.
alza689 said:
I quite doubt the cable will be the culprit as your device charges the battery while in an established connection with the laptop. As you state the phone USB port was replaced, it could be a some glitch before the USB port in the device where there is an interruption in the data transmission signal that cannot be detected by your laptop.
Could you boot your device, computer and connect the two and take a snapshot of your device (whilst connected to the laptop) and paste the same in the forum?
Perhaps visual cue could be better at dealing such mishaps.
Click to expand...
Click to collapse
Yes of course. It is connected to a computer now. You can see it getting charged but that's about it
alza689 said:
I quite doubt the cable will be the culprit as your device charges the battery while in an established connection with the laptop. As you state the phone USB port was replaced, it could be a some glitch before the USB port in the device where there is an interruption in the data transmission signal that cannot be detected by your laptop.
Could you boot your device, computer and connect the two and take a snapshot of your device (whilst connected to the laptop) and paste the same in the forum?
Perhaps visual cue could be better at dealing such mishaps.
Click to expand...
Click to collapse
Can it be something because of some wrong flash ? This problem has survived through 2 versions and 1 system upgrade through firmware finder .. and a complete format
USB trident is not seen on the device
gandotratushar said:
Yes of course. It is connected to a computer now. You can see it getting charged but that's about it
Click to expand...
Click to collapse
Your USB trident icon is not indicated on the device, If you were to receive power from the laptop the trident would be displayed on top of the screen, even for charging the battery. The power source for your device appears to from other than the laptop.
I have pasted my device after connecting to the computer and the second icon from the top left is the USB Trident icon indicating connection with my laptop. Have taken the snapshot of the menu that I was describing .
I strongly feel you have a hardware failure rather than a simple fix and would require the help of a technician (ordinary if professional is unavailable). Am skeptic you could mend that on your own unless you are proficient in electronics. This mishap is not due to flashing wrongly too, unless you have changed the stock ROM with some custom ROM which has some bug that affect the USB alone.
Take the assistance of a technician whether professional or less is my counsel
Thank you
alza689 said:
Your USB trident icon is not indicated on the device, If you were to receive power from the laptop the trident would be displayed on top of the screen, even for charging the battery. The power source for your device appears to from other than the laptop.
I have pasted my device after connecting to the computer and the second icon from the top left is the USB Trident icon indicating connection with my laptop. Have taken the snapshot of the menu that I was describing .
I strongly feel you have a hardware failure rather than a simple fix and would require the help of a technician (ordinary if professional is unavailable). Am skeptic you could mend that on your own unless you are proficient in electronics. This mishap is not due to flashing wrongly too, unless you have changed the stock ROM with some custom ROM which has some bug that affect the USB alone.
Take the assistance of a technician whether professional or less is my counsel
Thank you
Click to expand...
Click to collapse
I did flash a different rom .. but then back to stock recently.
I can do basic electronics but the if the problem lies in Mobo .. then nothing can be done .. as I don't have the spares available in India. But I would hate to lose this phone as it was a perfect fit for my needs
gandotratushar said:
I did flash a different rom .. but then back to stock recently.
Then the question of wrong flash or ROM issue does not arise
I can do basic electronics but the if the problem lies in Mobo .. then nothing can be done .. as I don't have the spares available in India.
If you do not have spares is best left alone rather than tampering with it and rendering the device useless if any untoward incidents tends to occur.
But I would hate to lose this phone as it was a perfect fit for my needs
Send to the vendor directly if you have warranty for the device stating its complaints or request your relative or friends who live in the area where you bought your phone to hand it to the vendor or service technician and bear its expenses
Click to expand...
Click to collapse
Thank you
alza689 said:
Thank you
Click to expand...
Click to collapse
Is there a way to unlock bootloader somehow without connecting to usb ? That would also solve the purpose.. I want to root it for some of the things to work and with the latest upgrade to latest version I lost the unlocked bootloader and root.. if somehow I can unlock and root .. I should be fine without the usb connection to computer.. but I have ran out of ways
Does Kingroot work for you?
I mean did u try it or u just want magisk?
If u didn't, kingroot may be able to root ur device and unlock ur bootloader, then u can flash TWRP using rasher.. & make a backup BTW...
After that, try using the adb sideload in TWRP to test ur connection with ur computer.
TWRP for ur device : (q.gs/DxuAH)
There is a way to unlock bootloader without USB via developers option.
Go to settings-----> About phone-----> Build number ( Tap this option around 7 or 8 times) till developers option is enabled------> go back to settings-----> developers option-----> OEM unlock option (Enable this option) to unlock the bootloader.
Xeedius said:
Does Kingroot work for you?
I mean did u try it or u just want magisk?
If u didn't, kingroot may be able to root ur device and unlock ur bootloader, then u can flash TWRP using rasher.. & make a backup BTW...
After that, try using the adb sideload in TWRP to test ur connection with ur computer.
TWRP for ur device : (q.gs/DxuAH)
Click to expand...
Click to collapse
Thank you for the advice.. I hadn't tried it earlier but after your suggestion I did.. kingroot says I need to unlock my bootloader to root it.. so I am back to square one..
alza689 said:
There is a way to unlock bootloader without USB via developers option.
Go to settings-----> About phone-----> Build number ( Tap this option around 7 or 8 times) till developers option is enabled------> go back to settings-----> developers option-----> OEM unlock option (Enable this option) to unlock the bootloader.
Click to expand...
Click to collapse
This gives me an frp unlock and not a phone unlock.. still not able to root
There is no FRP unlock.
gandotratushar said:
This gives me an frp unlock and not a phone unlock.. still not able to root
Click to expand...
Click to collapse
There is no FRP unlock, to circumvent FRP you need to factory reset or flash your firmware. The above quotation was to unlock the boot loader as you cannot access through your computer. Your sole option to unlock boot loader was through the above directions.
Moreover, King root application never ask for boot loader to be unlocked. Although a little unstable this is the initial program to root any device. Once you have the TWRP setup then you could switch to Super Su etc. according to your preference.
Could you paste your developers option snapshot here...
Regards,
689alza
gays
me too have this problem ( only usb port for charge and other option's not work)
and i want back to orignal system
and i want know how download orignal system (from Huawei web site) to my phone
can any one help me how
or how can fixed this problem
and i have other problem
when i try to boot to TWRP phone stay on " your device is booting now..."
so any one can help me how reinstall TWRP without PC or why this problem ??
TWRP is not installed duly on your phone
Hello! Omar Dahy,
OmarDahy said:
gays
me too have this problem ( only usb port for charge and other option's not work)
Connect your phone to your computer or laptop, a trident icon appears on your phone notification area, pull down the notifications and identify the notice as USB connection, tap twice you willk be provided with options.
and i want back to orignal system
and i want know how download orignal system (from Huawei web site) to my phone
My phone was Micromax and I am not aware of your phone's firmware, try and google or search the Xda developers forum under your phones model number for the original firmware.
can any one help me how
or how can fixed this problem
and i have other problem
when i try to boot to TWRP phone stay on " your device is booting now..."
Your phone has not installed TWRP duly, therefore it boots straight to the system. Search again in this XDA forum, with your pnone name and model number to obtain instructions
so any one can help me how reinstall TWRP without PC or why this problem ??
Click to expand...
Click to collapse
I purchased a Pixel 6 advertised as unlocked, but the OEM unlock option was greyed out in Developer Tools. I read somewhere that giving it the OTA update for at least June 2022 would unlock it, so I set out to do that.
After many issues trying to get the computer and phone to communicate, I found I should just use the ADB 1.0.32 binary (Linux), then try a combination of killing ADB, unplugging the phone, plugging it back in, starting ADB, etc., etc. until there is no longer "offline", "no device", or "unauthorized" shown. Eventually, I got it to communicate once it recognized the phone as being in "sideload" status.
So, after running `./adb_Linux sideload oriole-ota-sq3a.220705.003-17fec7eb.zip`, it finally did something. Except, it was stuck at, "Verifying update package..." No matter how many times I reach this point, no matter how many minutes or hours I wait, nothing happens.
Any ideas? I couldn't find any solutions or similar problems posted anywhere.
Since you're mucking around with ota's, it sounds like you are deliberately keeping it disconnected from the network, otherwise it would prompt you with an update almost immediately and there would be no need for this.
In order for the unlocking switch to be enabled, the phone MUST be connected to the network.
Also be CERTAIN that your device is a Pixel 6 and not a Pixel 6a. The 6a is the one that needs a particular update version in order for unlocking to work due to a bug. The 6 will unlock just fine on factory firmware. Assuming that you have a 6a, this would explain why trying to install "oriole" firmware would fail for you since it is a DIFFERENT PHONE.
So I take it no one has found a solution for not connecting it to the network in order to unlock it? There have been some workarounds for other devices, so I'm just asking.
Zakku said:
So I take it no one has found a solution for not connecting it to the network in order to unlock it? There have been some workarounds for other devices, so I'm just asking.
Click to expand...
Click to collapse
I don't see it as a huge issue in need of a resolution. Google does NOT blacklist you in any way for unlocking the bootloader, and they already know all of the identifying codes on every phone anyway so its not like you're keeping any information from them. Just don't put a sim card in it before unlocking it, and if you're worried they will connect the phone with your IP address, use a VPN or public AP.
USB C to USB 2.0 will work. USB C to C will not, ADB does not have the proper protocols to work with USB C. I have tried with myself. My computer has Gen2 3.1 USB C. Transferring files between are fast. But when sideload mode, it doesn't work. After investigating this issue, it was ADB not the computer nor the phone. Finally got it work once I put it in a 2.0 USB.
nerdsquadmember1 said:
USB C to USB 2.0 will work. USB C to C will not, ADB does not have the proper protocols to work with USB C. I have tried with myself. My computer has Gen2 3.1 USB C. Transferring files between are fast. But when sideload mode, it doesn't work. After investigating this issue, it was ADB not the computer nor the phone. Finally got it work once I put it in a 2.0 USB.
Click to expand...
Click to collapse
What are you talking about? And what does this have to do with this thread? And where are you coming up with this nonsense?
96carboard said:
What are you talking about? And what does this have to do with this thread? And where are you coming up with this nonsense?
Click to expand...
Click to collapse
His comments seem to have a lot to do with this thread. Clearly, at least to me, he tried sideloading and had a problem. He was simply relaying what he tried to fix it.
nerdsquadmember1 said:
USB C to USB 2.0 will work. USB C to C will not, ADB does not have the proper protocols to work with USB C. I have tried with myself. My computer has Gen2 3.1 USB C. Transferring files between are fast. But when sideload mode, it doesn't work. After investigating this issue, it was ADB not the computer nor the phone. Finally got it work once I put it in a 2.0 USB.
Click to expand...
Click to collapse
Clearly there is something to that... I had my Pixel 6 Pro sit at verifying (on phone screen) and 0% (in cmd window) for over an hour before i found this helpful comment. Killed the process (CTRL+C), then force rebooted into recovery (Power + VolUP) without trying to start the device because there was already an "install failed dont reboot" warning and then plugged it into the last remaining USB 2.0 port. There, the verification was done in 101 seconds and the flashing started when the cmd window hit about 50%.
The Pixel 6 Pro is just rebooting into Android 13 while typing this message.
Thank you for pointing this problem out.
[EDIT]
I might want to add that this happened on a Gigabyte Z390 board that has mostly USB 3 and one USB C plus just one USB 2.0 port out front. I could imagine this not applying to all USB C ports on PCs. Maybe its just because of the older Intel platform or the active (with its own controller chip inside) USB-PD cable i was using.
Yep same thing on my XPS 9710 which only has TB4 ports: using a TB4 to USB A adapter and then an A to C cable worked, stupid of Google to not include native C support since they have been using C as the standard since 2016 with the Nexus 6P lol.
I think the USB issue might be more of a combination of thighs, since when I tried to sideload through classic C to A cable it was really slow and basically got stuck at like 5%, then I used "higher quality" C to C cable and the update was done in minute.
Sneakyghost said:
Clearly there is something to that... I had my Pixel 6 Pro sit at verifying (on phone screen) and 0% (in cmd window) for over an hour before i found this helpful comment. Killed the process (CTRL+C), then force rebooted into recovery (Power + VolUP) without trying to start the device because there was already an "install failed dont reboot" warning and then plugged it into the last remaining USB 2.0 port. There, the verification was done in 101 seconds and the flashing started when the cmd window hit about 50%.
The Pixel 6 Pro is just rebooting into Android 13 while typing this message.
Thank you for pointing this problem out.
[EDIT]
I might want to add that this happened on a Gigabyte Z390 board that has mostly USB 3 and one USB C plus just one USB 2.0 port out front. I could imagine this not applying to all USB C ports on PCs. Maybe its just because of the older Intel platform or the active (with its own controller chip inside) USB-PD cable i was using.
Click to expand...
Click to collapse
Yep. This the bloody fix! Exact same problem. Stuck at verifying at 2% for the September patch. I switched USB ports from my new laptop to the dock itself and finally, sideloaded it. Does ADB need to be updated to work with USB 3.0?