Hi,
Am a novice when it comes to rooting, unlocking android devices. So please excuse my ignorance and my long-winded style of writing. I want the expert users to educate me on this issue and so I don't want to miss any trivial (or not so trivial) information.
1) So, I got Samsung gear live from ebay. It came with a sprat-userdebug 5.0.1. After googling I found out that it's a user/refurb build and can't be updated to 5.1.1
2) Thanks to rootjunky! I used Gear live restore tool V3 and unlocked the bootloader (option 2). Faced few issues in getting the driver. However, fixed everything and unlocked it. Flast TWRPd it (option 8). Flashed recovery (option 4) and bootimage (option 5). Then I sideloaded stock image from 4.4W.2 (using boot.img and system.img). That was the version I found after googling.
3) Then I tried to update it via OTA download. Download completed and it went back to recovery mode and did't apply the download. There was an error message that said something like "Unable to verify the download"
4) Tried multiple times and no luck with that
5) Then tried to sideload new version 5.1.1 LCA43 from xda wiki page. However, when my device went to recovery mode, my pc lost the connection and i wasn't able to sideload (received - device "null" not found" - error from adb command)
6) Until this point I was able to pair my device with my samsung S5 phone and only problem was not able to install the update
7) Then I reset my watch to factory setting, restarted multiple times, went to recovery mode to boot as a new device etc. No luck
8) Then I did something I shouldn't have done (or I think I shouldn't have done). Used option 7 root gear live. When the system went to SH mode, I panicked and closed the cmd prompt and hard reset the device by holding power button
9) After this step, I was not able to pair my device with my phone. Now the version says 4.4W.1 - KGW42N
10) Tried resetting my device, restarted it, used recovery mode to restart it, revoked all debug access, deleted adbkey from my PC, uninstalled android SDK, all drivers, etc. Reinstalled it again with no help.
11)Suddenly android wear in my phone sees my wifirouter as a device (strange)
11) When I plug in the device to my Pc, I could see it in my device manager. When I use recovery tool it says unregistered device and asking me to register it via my phone. Where as am not able to pair it with my phone. Tried to pair it with a new phone (moto e) and no help either
12)Somewhere read that disabling wifi in the phone before pairing works. Tried that and no luck
So here am with a bricked device that stays in the screen where it says "install android wear in your phone" and detects nothing else. Am able to go to bootloader mode, recovery mode from the device. However when it's in recovery mode, my PC doesn't detect it. Even the recovery tool says unregistered device.
Please help in unbricking this device and thank you for reading thru the whole problem. Any help would be much appreciated!
Use Gear live restore tool v2. Lots of known issues with v3
Thanks for the reply. I will try this. However, how will I make my device discoverable? Now, none of my phones detect my device.
So I guess I will get "Unauthorized Device" error when I use recovery tool. Could you please let me know if there's other way around? Or am i missing something?
I've never used it
Pretty sure all the info you need is in the thread
http://forum.xda-developers.com/gear-live/development/utility-gear-live-watch-tool-t2846696
No luck. Tried V2. Tool doesn't recognize my watch. It says 'Device Unauthorized. Please check the confirmation dialog on your device'. My device is stuck in 'Install Android wear on your phone' screen.
unbricked using v2 of the tool. Now trying to update the os version. Will see if I can get lucky this time. Thanks for the help!
All is good now. Now my gear live is running on 5.1.1 with latest updates.
Good work
Please can you tell what exactly you done, as I'm on the same root.. and I'm using win 10... but without any luck so far..
darwchprish said:
Please can you tell what exactly you done, as I'm on the same root.. and I'm using win 10... but without any luck so far..
Click to expand...
Click to collapse
Simple procedure.
Just download v2 of this tool
Make sure to install USB drivers
Unlock bootloader - option 2
Then use option 6 to flash it. Then you'll get new OTA updates.
Refer rootjunky video - https://www.youtube.com/watch?v=x7oRjESQh_o
I'm not able to pair my device with my phone. Now the version says 4.4W.1 - KGW42N,
and ... I tried V2 and V3. Tool but doesn't recognize my watch. It says 'Device Unauthorized. My device is stuck in 'Install Android wear on your phone' screen.
darwchprish said:
I'm not able to pair my device with my phone. Now the version says 4.4W.1 - KGW42N,
and ... I tried V2 and V3. Tool but doesn't recognize my watch. It says 'Device Unauthorized. My device is stuck in 'Install Android wear on your phone' screen.
Click to expand...
Click to collapse
Follow this procedure.
1)Make sure all drivers are installed properly in your PC
2) Make sure when you connect your device to your PC, it's discovered as unauthorized device. It's ok
3) Long press power button in the device and swipe from top left to botom right corner when you see samsung gear live logo
4)This will get the device to bootloader mode
5)Now connect the device to your PC and run V2 of the tool. Your device will be discovered in fastboot mode
6)Now select option 6 to flash the device to stock. It'll flash it
7) Now swipe down to highlight start and swipe from right to left to start. If it goes to Raw dump code = 6. do a hard restart by long pressing power button. You'll get back your device in original setting.
Check rootjunky youtube video to get the live demo of this procedure.
noviceinandroid said:
No luck. Tried V2. Tool doesn't recognize my watch. It says 'Device Unauthorized. Please check the confirmation dialog on your device'. My device is stuck in 'Install Android wear on your phone' screen.
Click to expand...
Click to collapse
How did you get past this? I'm stuck here now too.
-- update after trying that procedure again, it worked to get to fastboot mode. Now I'm doing that 'option 6' to flash it.
mike061215 said:
How did you get past this? I'm stuck here now too.
-- update after trying that procedure again, it worked to get to fastboot mode. Now I'm doing that 'option 6' to flash it.
Click to expand...
Click to collapse
Good luck.
It worked -- and I finally got the OS to update an all that and now I finally have a functional Gear Live. Phew!
My Gear Live was bricked a lot... Computer detect device as RELINK HS-USB QDLoader 9008. Has anyone any idea how fix it?
lamik91 said:
My Gear Live was bricked a lot... Computer detect device as RELINK HS-USB QDLoader 9008. Has anyone any idea how fix it?
Click to expand...
Click to collapse
sounds like USB driver issue. Please install correct drivers and follow the steps mentioned above. It should be unbricked.
Where can i find correct drivers? Additionally my Gear Live doesn't turn on and has only black screen.
I am confused on how to use the tool. My watch is stuck at the Install Android Wear App and won't do anything short of turning it off. How do I enable developer mode \ debugging without being able to get to the watch settings. Please help! Thanks
pedalquickly said:
I am confused on how to use the tool. My watch is stuck at the Install Android Wear App and won't do anything short of turning it off. How do I enable developer mode \ debugging without being able to get to the watch settings. Please help! Thanks
Click to expand...
Click to collapse
You need to factory reset first of all. After that let connect to your wifi, the updates will download on their own. They put a new one out today. I can't go into how but if you look at the forum and search the answers are there. There's even a tool to use.
Sent from my SM-N910T3 using XDA-Developers mobile app
Related
Rooted LG D405n, nothing done to the software beyond that (unless you count having zooper/nova launcher configured on it). Gave the phone to a friend for a short while and she decided to update the software using the LG software update on the phone. After she selected install on the latest update which came out not long ago and was supposedly going to update the apps, it restarted and got stuck on boot screen with Boot Ceritification Error [560].
I've tried this guide http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479 but I got stuck on step 4. because I cannot make the PC recognize the device (it does not show up at all), so the LG tool can't install USB drivers. If i try to do it manually (it gives me an option to select a device from a list) it doesn't seem to do anything, just gets stuck on the Downloading USB driver window.
I can put the phone in Firmware Upgrade Mode just fine, but it doesn't seem to do anything useful. The PC still won't recognize the device, however I can hear the 'usb pluged in' sound (I'm on Win7).
Did a factory reset, didn't help.
Asayanami said:
Rooted LG D405n, nothing done to the software beyond that (unless you count having zooper/nova launcher configured on it). Gave the phone to a friend for a short while and she decided to update the software using the LG software update on the phone. After she selected install on the latest update which came out not long ago and was supposedly going to update the apps, it restarted and got stuck on boot screen with Boot Ceritification Error [560].
I've tried this guide http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479 but I got stuck on step 4. because I cannot make the PC recognize the device (it does not show up at all), so the LG tool can't install USB drivers. If i try to do it manually (it gives me an option to select a device from a list) it doesn't seem to do anything, just gets stuck on the Downloading USB driver window.
I can put the phone in Firmware Upgrade Mode just fine, but it doesn't seem to do anything useful. The PC still won't recognize the device, however I can hear the 'usb pluged in' sound (I'm on Win7).
Did a factory reset, didn't help.
Click to expand...
Click to collapse
You could try the LG Support Tool. Not sure it will work but it's worth a shot. The problem with the phone not getting detected by the PC is the fact that 1) The OS was upgraded by your friend and 2) The factory reset you performed . Both of those acts would have disabled USB debugging hence no device detected.
I unfortunately have no encouraging information to give you.
shinobisoft said:
You could try the LG Support Tool. Not sure it will work but it's worth a shot. The problem with the phone not getting detected by the PC is the fact that 1) The OS was upgraded by your friend and 2) The factory reset you performed . Both of those acts would have disabled USB debugging hence no device detected.
I unfortunately have no encouraging information to give you.
Click to expand...
Click to collapse
It appears that I have fixed it.
Since The tool would not download the USB drivers by itself I went to the LG website and got them manually, installed them and restarted the PC.
After that I launched the LG Mobile Support Tool, but it still didn't see the device.
However, I clicked Options and Upgrade Recovery. It asked me for my IMEI. I put the phone into Firmware Upgrade mode and the program started upgrading the phone.
After it was all done, the phone restarted, and the software update simply said that instalation failed, I have lost root but everything else seems fine. Rooted again with towelroot and I'm back in game.
Asayanami said:
It appears that I have fixed it.
Since The tool would not download the USB drivers by itself I went to the LG website and got them manually, installed them and restarted the PC.
After that I launched the LG Mobile Support Tool, but it still didn't see the device.
However, I clicked Options and Upgrade Recovery. It asked me for my IMEI. I put the phone into Firmware Upgrade mode and the program started upgrading the phone.
After it was all done, the phone restarted, and the software update simply said that instalation failed, I have lost root but everything else seems fine. Rooted again with towelroot and I'm back in game.
Click to expand...
Click to collapse
Well I'm glad you managed to fix it.
Since this issue appears to be solved, please insert '[SOLVED]', without the quotes, at the beginning of your thread title.
some assistance please.
I've been at it for about 40 minutes now, trying to sideload 5.1 onto the N6. Go me! Unfortunately I have come to a halt due to my computer not being able to recognize my device in recovery mode. I have the nexus root tool kit installed on my Win7 PC and i have done all the steps as far as driver installation and the toolkit says it is a success. I even open up command prompt when the device is turned on and type "adb devices" and it gives me the device info, I can even use my explorer to see the files I have in storage on the device too. Now if I type the same command while the device in in recovery mode, my computer tells me the device is not found. I have since downloaded the google drivers and tried updating the driver manually through Device Manager and that tells me that the drivers are up to date/best driver is already installed etc. So after goofing with that for a few tries, I uninstalled ALL nexus/google drivers and reinstalled them, twice now, with the same result.
Am I doing something wrong? Why does my computer not want me to update? why does it hate me?
melficeapollo said:
some assistance please.
I've been at it for about 40 minutes now, trying to sideload 5.1 onto the N6. Go me! Unfortunately I have come to a halt due to my computer not being able to recognize my device in recovery mode. I have the nexus root tool kit installed on my Win7 PC and i have done all the steps as far as driver installation and the toolkit says it is a success. I even open up command prompt when the device is turned on and type "adb devices" and it gives me the device info, I can even use my explorer to see the files I have in storage on the device too. Now if I type the same command while the device in in recovery mode, my computer tells me the device is not found. I have since downloaded the google drivers and tried updating the driver manually through Device Manager and that tells me that the drivers are up to date/best driver is already installed etc. So after goofing with that for a few tries, I uninstalled ALL nexus/google drivers and reinstalled them, twice now, with the same result.
Am I doing something wrong? Why does my computer not want me to update? why does it hate me?
Click to expand...
Click to collapse
Here is a channel i subscribe and the guy goes in detail about wugfresh root tool kid, some of the videos are from december. hope it helps.
https://www.youtube.com/channel/UCWhQwvCaC2ZMkCnrC15NfAw
i went the the link and viewed a video about sideloading through the toolkit, never knew i could do that, but i still came across the same problem. my computer wont recognize it.. smh..
melficeapollo said:
i went the the link and viewed a video about sideloading through the toolkit, never knew i could do that, but i still came across the same problem. my computer wont recognize it.. smh..
Click to expand...
Click to collapse
When you get the device not found error, unplug USB and reconnect. May have to repeat once or twice.
Evolution_Freak said:
When you get the device not found error, unplug USB and reconnect. May have to repeat once or twice.
Click to expand...
Click to collapse
Tried that like it was going out of style lol. No luck.
i finally got it figured out!!
i used the toolkit and install;ed Universal Google Drivers (option #3) and my pc was finally able to detect my device in recovery mode.
so if anyone comes across the same problem of not having the "right" drivers or not having your device detected,
1.) Install Universal Google Drivers and reboot your computer
2.) proceed to sideload your update.
If anyone has been paying attention to any of my threads you'd know i've been having a horrible time trying to get my LG G4 to work. After much trouble of not being able to connect my phone to the computer via download mode ( driver wont start , code 10) my cyanogenmod recovery magically allowed me to install the supersu zip to root the system, and finally the global root access option in cm13 worked which enabled me to install an app and flash twrp. From here I was able to download prometheus rom, and install it from twrp because the cm recovery kept giving me errors., ran smoothly.. was able to get all of my downloaded apps retrieved via google. I reboot the phone this morning after deleting some un wanted apps I had now i'm getting ' secure boot error 1003" and will not boot past the Lg screen. I am really at a lost here and would appreciate it if someone would take the time out to help me. Now I am totally screwed because I cant get windows to install the download mode driver correctly as there is a yellow exclamation mark next "LGE Android MTP device" with a code 10. That is important because adb/fastboot wont recognize the device unless this driver is running and working. I mean sheesh ive tried this on three computers and cant get this da*n driver to install, really? am i seriously missing something? lg software wont even recognize my phone unless its in download mode and even then, will fail to run because * the device can not start* so the software shuts down
Please, help. and if any suggestions, please provide tutorials to back it up.
Sunaj1 said:
If anyone has been paying attention to any of my threads you'd know i've been having a horrible time trying to get my LG G4 to work. After much trouble of not being able to connect my phone to the computer via download mode ( driver wont start , code 10) my cyanogenmod recovery magically allowed me to install the supersu zip to root the system, and finally the global root access option in cm13 worked which enabled me to install an app and flash twrp. From here I was able to download prometheus rom, and install it from twrp because the cm recovery kept giving me errors., ran smoothly.. was able to get all of my downloaded apps retrieved via google. I reboot the phone this morning after deleting some un wanted apps I had now i'm getting ' secure boot error 1003" and will not boot past the Lg screen. I am really at a lost here and would appreciate it if someone would take the time out to help me. Now I am totally screwed because I cant get windows to install the download mode driver correctly as there is a yellow exclamation mark next "LGE Android MTP device" with a code 10. That is important because adb/fastboot wont recognize the device unless this driver is running and working. I mean sheesh ive tried this on three computers and cant get this da*n driver to install, really? am i seriously missing something? lg software wont even recognize my phone unless its in download mode and even then, will fail to run because * the device can not start* so the software shuts down
Please, help. and if any suggestions, please provide tutorials to back it up.
Click to expand...
Click to collapse
This happened to me last night. I tried to "relock" the bootloader. I had to put the phone in download mode, and recover using LG bridge. I found several different ways to accomplish the download mode listed but only one worked., i believe it was here. http://www.androidexplained.com/lg-g4-how-to-boot-into-download-mode/
I used these directions mostly but did one thing a little differently
Download LGUP and install it. I used the DropBox link in this thread:
http://forum.xda-developers.com/g4/h...mm-lp-t3249803
Remember to install the LGUP_8994_DLL file BEFORE LGUP_Install
Download and install LG Bridge (for the USB drivers) here:
http://www.lg.com/uk/support/pc-suite
Select the LG 815 model, the drivers will work. I only used the LG Bridge to install the USB drivers. Nothing else.
OK, now here's where your phone comes in.
Step 1: Turn off your phone (pull the battery if you must, but put it back in).
Step 2: Hold the VOLUME UP button and plug the USB cable into your PC. This puts your phone into DOWNLOAD MODE.
Step 3: On your PC, open up LGUP. The program shoud recognize the phone as H811 in COM3 or COM4. Highlight it and click the SELECT button.
Step 4: Under the "Process" row, select UPGRADE
Step 5: Click the blank space under File Path, it will pop up a [...] [X] at the end. Click the [...].
Step 6: Select the H81120i_00_0201.kdz and click on Start. The program will push the STOCK H811 MM ROM to your phone. This will bring your phone out of Brick mode, but you will have to go through the entire rooting process again.
Instead of using the KDZ files, I used lg bridge. Once i was actually in download mode, and lg bridge recognized my phone, i went the the software update tab and clicked on the error recovery, the tool downloaded the proper rom, installed in and I was back to stock, no root.
Take the cover off of your battery, have a good usb cable handy. I had to remove the battery, hold the buttons and start over several times before I got it to work, but I did.
Good luck.
happimeal said:
This happened to me last night. I tried to "relock" the bootloader. I had to put the phone in download mode, and recover using LG bridge. I found several different ways to accomplish the download mode listed but only one worked., i believe it was here. http://www.androidexplained.com/lg-g4-how-to-boot-into-download-mode/
I used these directions mostly but did one thing a little differently
Download LGUP and install it. I used the DropBox link in this thread:
http://forum.xda-developers.com/g4/h...mm-lp-t3249803
Remember to install the LGUP_8994_DLL file BEFORE LGUP_Install
Download and install LG Bridge (for the USB drivers) here:
http://www.lg.com/uk/support/pc-suite
Select the LG 815 model, the drivers will work. I only used the LG Bridge to install the USB drivers. Nothing else.
OK, now here's where your phone comes in.
Step 1: Turn off your phone (pull the battery if you must, but put it back in).
Step 2: Hold the VOLUME UP button and plug the USB cable into your PC. This puts your phone into DOWNLOAD MODE.
Step 3: On your PC, open up LGUP. The program shoud recognize the phone as H811 in COM3 or COM4. Highlight it and click the SELECT button.
Step 4: Under the "Process" row, select UPGRADE
Step 5: Click the blank space under File Path, it will pop up a [...] [X] at the end. Click the [...].
Step 6: Select the H81120i_00_0201.kdz and click on Start. The program will push the STOCK H811 MM ROM to your phone. This will bring your phone out of Brick mode, but you will have to go through the entire rooting process again.
Instead of using the KDZ files, I used lg bridge. Once i was actually in download mode, and lg bridge recognized my phone, i went the the software update tab and clicked on the error recovery, the tool downloaded the proper rom, installed in and I was back to stock, no root.
Take the cover off of your battery, have a good usb cable handy. I had to remove the battery, hold the buttons and start over several times before I got it to work, but I did.
Good luck.
Click to expand...
Click to collapse
Thanks so much. Hopefully I can get this to work, if I can get the PC to see the LGE MTP download mode driver then the rest is golden. Will keep things updated. Will try when I get home.
happimeal said:
This happened to me last night. I tried to "relock" the bootloader. I had to put the phone in download mode, and recover using LG bridge. I found several different ways to accomplish the download mode listed but only one worked., i believe it was here. http://www.androidexplained.com/lg-g4-how-to-boot-into-download-mode/
I used these directions mostly but did one thing a little differently
Download LGUP and install it. I used the DropBox link in this thread:
http://forum.xda-developers.com/g4/h...mm-lp-t3249803
Remember to install the LGUP_8994_DLL file BEFORE LGUP_Install
Download and install LG Bridge (for the USB drivers) here:
http://www.lg.com/uk/support/pc-suite
Select the LG 815 model, the drivers will work. I only used the LG Bridge to install the USB drivers. Nothing else.
OK, now here's where your phone comes in.
Step 1: Turn off your phone (pull the battery if you must, but put it back in).
Step 2: Hold the VOLUME UP button and plug the USB cable into your PC. This puts your phone into DOWNLOAD MODE.
Step 3: On your PC, open up LGUP. The program shoud recognize the phone as H811 in COM3 or COM4. Highlight it and click the SELECT button.
Step 4: Under the "Process" row, select UPGRADE
Step 5: Click the blank space under File Path, it will pop up a [...] [X] at the end. Click the [...].
Step 6: Select the H81120i_00_0201.kdz and click on Start. The program will push the STOCK H811 MM ROM to your phone. This will bring your phone out of Brick mode, but you will have to go through the entire rooting process again.
Instead of using the KDZ files, I used lg bridge. Once i was actually in download mode, and lg bridge recognized my phone, i went the the software update tab and clicked on the error recovery, the tool downloaded the proper rom, installed in and I was back to stock, no root.
Take the cover off of your battery, have a good usb cable handy. I had to remove the battery, hold the buttons and start over several times before I got it to work, but I did.
Good luck.
Click to expand...
Click to collapse
bro, thanks for taking the time to write this out. Not sure what I was doin wrong before, but i was able to flash back to stock
I'm in a big predicament. A few weeks ago I installed the MOAR ROM on my Note 5. After installing this ROM I was no longer able to connect my phone to PC. I tried a Windows 8 PC which says I have an unrecognized USB device plugged in. I tried going into Developer settings to set USB mode to MTP but the option didn't exist. I had all USB drivers installed as well. My wife's phone is recognized no problem. When plugging the phone into my linux machine absolutely nothing happened. It used to show the phone in the left navigation panel in my window manager but after installing MOAR ROM it was no longer detected.
Anyway, today I was trying to play Cartoon Wars 3 and since my phone is rooted it wouldn't let me play. I decided to go into the Super User app and disable it to see if the game would work and it didn't. When I went to re-enable the app it said installation failed and asked me to reboot. I clicked reboot and was sent into a boot loop. I thought okay no big deal, I'll just restore a backup in TWRP. When I go to restore the backup and select the backup file it asks which partitions to restore, but there are no boxes to check. It usually has options like system and data but now it's just blank. I tried a factory reset and I'm still in a bootloop. I'm at a complete loss. I don't know what else to do. I've tried download mode and everything but no matter what I do my phone isn't detected by my pc.
I appreciate any help. I don't know what to do. I'm out of a phone right now and don't have a backup. Not to mention I'm in between jobs right now and can't afford a new one right now.
Just flash a stock rom from sammobile.com
Pre req:
*Odin(any vers)
*Stock rom
Steps
*Extract the downloaded stock rom in your PC
*In twrp wipe everything except internal, then boot in to download mode.
*Once in download mode, connect your phone to your pc, then open Odin.
*In Odin, check the "AP" section and locate the downloaded stock rom(the extracted one)
*Hit start.
Hpe that helps
herculesPh said:
Just flash a stock rom from sammobile.com
Pre req:
*Odin(any vers)
*Stock rom
Steps
*Extract the downloaded stock rom in your PC
*In twrp wipe everything except internal, then boot in to download mode.
*Once in download mode, connect your phone to your pc, then open Odin.
*In Odin, check the "AP" section and locate the downloaded stock rom(the extracted one)
*Hit start.
Hpe that helps
Click to expand...
Click to collapse
Thank you for your reply but it seems you didn't read my post. My phone is not recognized by any pc.
What is the terminal command to restore a backup? That's pretty much my last ditch effort.
Well I broke my recovery so I'm screwed. I contacted Samsung and they said they would service it for free. Wish me luck.
What would cause the phone to stop being recognized by the PC? I narrowed it down to the MTP software or the micro usb charge port. My Windows computer says Device Descriptor Request Failed. Linux box does nothing. No USB devices are listed when I run lsblk.
weinerwad3000 said:
I'm in a big predicament. A few weeks ago I installed the MOAR ROM on my Note 5. After installing this ROM I was no longer able to connect my phone to PC. I tried a Windows 8 PC which says I have an unrecognized USB device plugged in. I tried going into Developer settings to set USB mode to MTP but the option didn't exist. I had all USB drivers installed as well. My wife's phone is recognized no problem. When plugging the phone into my linux machine absolutely nothing happened. It used to show the phone in the left navigation panel in my window manager but after installing MOAR ROM it was no longer detected.
Anyway, today I was trying to play Cartoon Wars 3 and since my phone is rooted it wouldn't let me play. I decided to go into the Super User app and disable it to see if the game would work and it didn't. When I went to re-enable the app it said installation failed and asked me to reboot. I clicked reboot and was sent into a boot loop. I thought okay no big deal, I'll just restore a backup in TWRP. When I go to restore the backup and select the backup file it asks which partitions to restore, but there are no boxes to check. It usually has options like system and data but now it's just blank. I tried a factory reset and I'm still in a bootloop. I'm at a complete loss. I don't know what else to do. I've tried download mode and everything but no matter what I do my phone isn't detected by my pc.
I appreciate any help. I don't know what to do. I'm out of a phone right now and don't have a backup. Not to mention I'm in between jobs right now and can't afford a new one right now.
Click to expand...
Click to collapse
you can try this code and test if it work
*#0808#
Familiaaa said:
you can try this code and test if it work
*#0808#
Click to expand...
Click to collapse
The phone does not boot. Recovery does not boot. The only thing the phone does is go into download mode. The phone does not connect to any computer so I cannot use odin.
weinerwad3000 said:
The phone does not boot. Recovery does not boot. The only thing the phone does is go into download mode. The phone does not connect to any computer so I cannot use odin.
Click to expand...
Click to collapse
when your phone is in download mode,it doesn't work to connect it with samsung kies on your pc?
You could try using the Kies software to reload the stock firmware. Here's an overview of what to do:
- if you don't already have the Kies software installed on your PC, download it (just search Google) and install it. The first time it runs it'll update itself to the latest version so make sure you run it once before proceeding.
- put your phone in Download mode: with the phone completely off, press and hold the Volume Down and Home and Power buttons simultaneously, and release them all when you see the Samsung splash screen
- connect the phone to your PC with the USB cable that came with the phone
-- if you've never had the phone connected to your Windows-based computer before, you'll see messages about installing drivers, etc - just wait until this is done (may take 5 or 10 minutes) [I don't know what happens if you have a Mac - it probably just works]
- in the Kies software, select the second item in the Tools menu and just follow the prompts to enter the model number (in CAPS) and IMEI/Serial Number (both found under the battery - it's ok to remove the battery at this point)
- the Kies software should start downloading the correct firmware for your phone from the Internet; once that's done (depending on your Internet connection speed) it'll begin downloading that to the phone (this probably takes 10 minutes or so)
jubei79 said:
when your phone is in download mode,it doesn't work to connect it with samsung kies on your pc?
You could try using the Kies software to reload the stock firmware. Here's an overview of what to do:
- if you don't already have the Kies software installed on your PC, download it (just search Google) and install it. The first time it runs it'll update itself to the latest version so make sure you run it once before proceeding.
- put your phone in Download mode: with the phone completely off, press and hold the Volume Down and Home and Power buttons simultaneously, and release them all when you see the Samsung splash screen
- connect the phone to your PC with the USB cable that came with the phone
-- if you've never had the phone connected to your Windows-based computer before, you'll see messages about installing drivers, etc - just wait until this is done (may take 5 or 10 minutes) [I don't know what happens if you have a Mac - it probably just works]
- in the Kies software, select the second item in the Tools menu and just follow the prompts to enter the model number (in CAPS) and IMEI/Serial Number (both found under the battery - it's ok to remove the battery at this point)
- the Kies software should start downloading the correct firmware for your phone from the Internet; once that's done (depending on your Internet connection speed) it'll begin downloading that to the phone (this probably takes 10 minutes or so)
Click to expand...
Click to collapse
Kies doesn't work either. I already tried that. When I hook up the phone It says "Device Descriptor Request Failed". It used to connect to my computers until I put MOAR ROM on the phone. Since then it stopped being recognized by my computers. There's either something wrong with the connection or something got corrupted.
weinerwad3000 said:
Kies doesn't work either. I already tried that. When I hook up the phone It says "Device Descriptor Request Failed". It used to connect to my computers until I put MOAR ROM on the phone. Since then it stopped being recognized by my computers. There's either something wrong with the connection or something got corrupted.
Click to expand...
Click to collapse
What have you already tried?
- are you sure you're using a data cable and not a charging-only cable?
- have you tried a different computer?
- have you installed the Kies software?
- what does Device Manager show when the phone is connected?
- assuming that the phone is working normally, does the phone show anything when you connect it?
- do you have try windows 8 or 10?
can be you found a solution in this forum
http://forums.androidcentral.com/sa...-not-being-recognised-download-mode-odin.html
jubei79 said:
What have you already tried?
- are you sure you're using a data cable and not a charging-only cable?
- have you tried a different computer?
- have you installed the Kies software?
- what does Device Manager show when the phone is connected?
- assuming that the phone is working normally, does the phone show anything when you connect it?
- do you have try windows 8 or 10?
can be you found a solution in this forum
http://forums.androidcentral.com/sa...-not-being-recognised-download-mode-odin.html
Click to expand...
Click to collapse
I've tried 4 different cables. My wife's S5 works perfectly fine on all computers. I have tried in Windows 7, 8, 8.1, and 10. I've also tried in Linux Mint. It used to work until I installed MOAR Rom. Windows says Device Descriptor Request Failed. Linux doesn't do anything when hooked up. lsblk doesn't show the device either.
I have a bit of an update. Apparently something happened with all my data cables. I hooked up my wife's phone the other day and I was all of a sudden receiving the same error as the note 5. I went out and bought a new data cable and now her phone connects again. I'm waiting for the Note 5 to charge up so I can try Odin. I'll post back my results.
I apologize to those who told me it was the cable. I just didn't see that it was conceivable that all 4 of my data cables were all of a sudden damaged. Never underestimate the ability of children to destroy every working cable you own.
Well I'm still getting the error. I have some usb cables coming in the mail so once i try those out I'll get back to everyone.
weinerwad3000 said:
Well I'm still getting the error. I have some usb cables coming in the mail so once i try those out I'll get back to everyone.
Click to expand...
Click to collapse
Were you able to fix your issue. I have the same issue. Note 5 N9208, I can get into Recovery (TWRP) and Download mode, but can not boot. The USB connection is showing USB Device Descriptor failed. I have tried 5 different cables and Windows 7/10 Ubuntu and cant get the phone to show up on the PC. I also have changed the USB port of the phone. Any insight would be helpful.
musab_bari said:
Were you able to fix your issue. I have the same issue. Note 5 N9208, I can get into Recovery (TWRP) and Download mode, but can not boot. The USB connection is showing USB Device Descriptor failed. I have tried 5 different cables and Windows 7/10 Ubuntu and cant get the phone to show up on the PC. I also have changed the USB port of the phone. Any insight would be helpful.
Click to expand...
Click to collapse
I ended up trying to replace the port and accidentally cut the ribbon for the LCD screen. Ended up getting a new phone.
Hi there,
perhaps you guys can help me
I use a onePlus 3T 128GB and directly after delivery I update the OS, install twrp, make a clean backup and then personalized the phone.
Runs quite good but yesterday I wanted to update the system to 4.0 Nougat...
So I downloaded the full installer, backuped the full current system via twrp and then flash and install the 4.0 version.
Yeah... doesn't work really good...
After the Pin and the code for the sim card, the OS ask for a third pin code but none of both works. And I never have another pin code since years...
Then I wipe the cache and system with twrp and restore the last backup. Doesn't work. It only boots to the onePlus Logo and then nothing happens.
Same for the first clean backup without any personalisation...
For now I have an great smartphone that doesn't work... yayy...
Anyone of you has an idea how can I get my running phone back – with all my data and apps?
Edit1: adb sideload doesn't work
Edit2: Full Installer installed >> reboot >> no OS installed
Thanks for all guys.
Oliver
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
You said you wiped your system..
what did you expect?
use this guide to unbrick. This will definitely work
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
raj7749 said:
use this guide to unbrick. This will definitely work
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
No, it doesn't work
You said you wiped your system..
what did you expect?
Click to expand...
Click to collapse
The friend who gave me twrp recommend this to me.
But unfortunetly the full image here is just a update, too... so of course didn't work.
But at this moment I can't transfer any stuff to the internal storage because I have no possibility.
Only success is that the device manager lists the oneplus as "Android Bootloader Interface". But nothing for transfer works.
Jo_Jo_2000 said:
You said you wiped your system..
what did you expect?
Click to expand...
Click to collapse
When wiping system before installing a full roms zip (not only an incremental update), I would expect a working, os containing partition - like on the oneplus one (did that many times on bacon). But I can confirm, it's not working on opt3; at least not with oos4. In this case I need to restore working systemmpartition (from twrp-3.0.3-0), and flash then the rom zip.
current status:
twrp 3.0.2
I wipe the system and the cache again.
Restore my backup from sunday before I start this odyssey.
Try to boot the restored system >> stacks during oneplus logo on screen
Flash and install the 4.0 Update Rom
Boot >> enter Pin >> enter Sim Code >> see my customize lockscreen and a pop-uped telegram message
Want to unlock >> ask for another Pin that isn't my Pin or Sim Code (use these two for years from phone to phone)
Also have a full installed onePlus3T (perhaps with Nougat 4.0) that I can't unlock because of an unknown pin.
:good:
GammarursPulex said:
current status:
twrp 3.0.2
I wipe the system and the cache again.
Restore my backup from sunday before I start this odyssey.
Try to boot the restored system >> stacks during oneplus logo on screen
Flash and install the 4.0 Update Rom
Boot >> enter Pin >> enter Sim Code >> see my customize lockscreen and a pop-uped telegram message
Want to unlock >> ask for another Pin that isn't my Pin or Sim Code (use these two for years from phone to phone)
Also have a full installed onePlus3T (perhaps with Nougat 4.0) that I can't unlock because of an unknown pin.
:good:
Click to expand...
Click to collapse
Would you try the following: From twrp restore your very first backup (firmware, system and boot), don't leave twrp and wipe (reformat with f2fs) data (I'm talking of the entire userdata partition, not only "wiping data without wiping media"); flash the full oos4 zip (the one with 1.4GB); don't leave twrp, go to Advanced->copy logfile. Try to boot system.
If the system stiil refuses to boot up completly, get the logfile with adb via twrp and show us.
DO NOT try this, without usb-c otg cable and usb stick, because you are reformating your data partition. That's the reason I have not tried this: need to get an usb-c otg cable (BTW: recommendations on usb-c otg cables welcome, but OT: so PM).
GammarursPulex said:
No, it doesn't work
The friend who gave me twrp recommend this to me.
But unfortunetly the full image here is just a update, too... so of course didn't work.
But at this moment I can't transfer any stuff to the internal storage because I have no possibility.
Only success is that the device manager lists the oneplus as "Android Bootloader Interface". But nothing for transfer works.
Click to expand...
Click to collapse
the unbrick tool works 100 percent - i had to use it myself too.
if you see "Android Bootloader Interface" in your device manager you did something wrong.
in the thread for the unbrick tool it says "hold volume up button while connecting your op3t to your computer". unless you dont to it this way you will always see the Android Bootloader Interface instead of the unkown device - trust me.
turn off the phone, wait a few seconds, hold volume up key and plug it in. it will work at least it did for me
mcdachpappe said:
the unbrick tool works 100 percent - i had to use it myself too.
if you see "Android Bootloader Interface" in your device manager you did something wrong.
in the thread for the unbrick tool it says "hold volume up button while connecting your op3t to your computer". unless you dont to it this way you will always see the Android Bootloader Interface instead of the unkown device - trust me.
turn off the phone, wait a few seconds, hold volume up key and plug it in. it will work at least it did for me
Click to expand...
Click to collapse
I gave my phone to my girlfriend, because I had to head to work. She wrote to me:
"Tryed it a couple of times now and then there was something like "QHUSB_BULK" showed up. But only for around 3 seconds, then i got the message "RELINK HS-USB QDLOADER 9008 (COM4) installed". Now the device-manager has this "RELINK..."-thing, but not at "unknown devices" but at "Connections (COM & LPT)". I tryed to go to point "Update Device Software", but all I get is "its already installed". When i go to details, it sais something about "\system32\DRIVERS\cmnxusber.sys".
After this i tryed to get the QHUSB_BULK back on the screen, but it seems like Windows7 is installing this DeviceSoftware every time when i reconnect the phone with "volume button while connecting the phone to the computer". I even tryed to deactivate/deinstall the DeviceSoftware, but its the same game every time i try it from the beginning.
Then i tryed the MsmDownloadTool, but hey.. no response. Guess i need to update the software first."
Shes now sitting in front of my PC and trying the steps. I'm out of ideas at the moment, do you have an idea what she is doing wrong or where the problem is now? (At least we are a step further now, haha!)
@nvertigo67
I can look up for this sort of cable when I'm back home. But i hope this unbrick tool will succeed.
GammarursPulex said:
Only success is that the device manager lists the oneplus as "Android Bootloader Interface". But nothing for transfer works.
Click to expand...
Click to collapse
Look for my comment in that thread, I had numerous issues with the driver. I don't know exactly how I got it to work, but try my steps to get the driver to show up as Qualcomm 9008.
rms4067 said:
Look for my comment in that thread, I had numerous issues with the driver. I don't know exactly how I got it to work, but try my steps to get the driver to show up as Qualcomm 9008.
Click to expand...
Click to collapse
Girlfriend here: Whoever said that having a break and eat something before going back to some PC problem was right xD
Ok, what i did now:
First i deactivated the automatic Windows-Update (not sure if there was the problem, but i had some problems with this automatically-Winstupid-Stuff... doesn't matter..).
Then i connected the op3t with the volume-up-trick to the computer and i got the "RELINK HS-USB QDLOADER 9008" back in the DeviceManager. Now i deinstalled the DeviceSoftware and like you said (maybe i was blind before...) there was a checkbox unlocked. I locked it (said something like "deleting DeviceSoftware from PC" or something like that) and clicked on "OK" to deinstall the DeviceSoftware.
I interrupted the "automatical installing drivers" in the Popup what shows at the right side of the task-line (i only got ~3-5 seconds until it was finished, so i had to do this step 2 times until i was fast enough^^). Windows said now that there was no success in downloading/installing the DeviceSoftware. Finally!
Next step (now i had enough time, because Windows didn't download/install anything) was right-click on the "QHUSB_BULK" and finally could install the downloaded drivers. DeviceManager now shows a "Qualcomm HS-USB QDLoader 9008 (COM3)" at "Connections (COM & LPT)".
I started the MsmDownloadTool aaaaand got Sahara-Error
Tryed another run with changed properties (compatibility mode (Win XP, SP3) and gave AdminRights). Now it shows me "Start Download Firehose Binary" and then returns to the "Sahara Communication Failed"-msg. Glad i found lyall29's post at page 6. Needed to make the whole thing 4 times until this error was gone >_<
When the download started, the op3t got a.. not sure, yellow? maybe lightgreen? LED-signal during the download is now running.
Until i wait:
Maybe the first mistake i also had was:
When pressing the power-button for 40 seconds, the op3t has to be turned off at the end. Then wait some seconds. Then push the volume-up for 10 seconds and then while still pushing the volume-button, connect the op3t with the computer to get the msg at DeviceManager.
Nvm, after the download finished, i got another popup sais "unknown device" and that Windows couldn't install the DeviceSoftware.
I did "Step 9: Disconnect phone from PC and boot into system." aaaaaaaaaaand.... it worked. Q,Q
Now all i need to do is trying to get the backup back until my boyfriend is home
But one question is still open:
When we tryed to load the backup, then the op3t said, that the backup is encrypted. But.. i'm pretty sure we didn't encrypt the phone-data. We also thing, that the problem why the backup didn't work correctly was, that the data was encrypted and so we couldn't gain access to it. We tryed this with his Win7-PC and my Linux-Laptop. Even with different USB-Ports (2.0 and 3.0).
I'm going to do a new backup now from the op3t, but what if the problem shows up again?
Someone got an idea if the MD5-Backup-Stuff should be encrypted or decrypted?
Besides that:
Thank you very much for the help!! I guess i wasnt that qualified with fixing phone-issues and i might did some very nooby failures... so really thank you for your patience
GammarursPulex said:
Girlfriend here: Whoever said that having a break and eat something before going back to some PC problem was right xD
Ok, what i did now:
First i deactivated the automatic Windows-Update (not sure if there was the problem, but i had some problems with this automatically-Winstupid-Stuff... doesn't matter..).
Then i connected the op3t with the volume-up-trick to the computer and i got the "RELINK HS-USB QDLOADER 9008" back in the DeviceManager. Now i deinstalled the DeviceSoftware and like you said (maybe i was blind before...) there was a checkbox unlocked. I locked it (said something like "deleting DeviceSoftware from PC" or something like that) and clicked on "OK" to deinstall the DeviceSoftware.
I interrupted the "automatical installing drivers" in the Popup what shows at the right side of the task-line (i only got ~3-5 seconds until it was finished, so i had to do this step 2 times until i was fast enough^^). Windows said now that there was no success in downloading/installing the DeviceSoftware. Finally!
Next step (now i had enough time, because Windows didn't download/install anything) was right-click on the "QHUSB_BULK" and finally could install the downloaded drivers. DeviceManager now shows a "Qualcomm HS-USB QDLoader 9008 (COM3)" at "Connections (COM & LPT)".
I started the MsmDownloadTool aaaaand got Sahara-Error
Tryed another run with changed properties (compatibility mode (Win XP, SP3) and gave AdminRights). Now it shows me "Start Download Firehose Binary" and then returns to the "Sahara Communication Failed"-msg. Glad i found lyall29's post at page 6. Needed to make the whole thing 4 times until this error was gone >_<
When the download started, the op3t got a.. not sure, yellow? maybe lightgreen? LED-signal during the download is now running.
Until i wait:
Maybe the first mistake i also had was:
When pressing the power-button for 40 seconds, the op3t has to be turned off at the end. Then wait some seconds. Then push the volume-up for 10 seconds and then while still pushing the volume-button, connect the op3t with the computer to get the msg at DeviceManager.
Nvm, after the download finished, i got another popup sais "unknown device" and that Windows couldn't install the DeviceSoftware.
I did "Step 9: Disconnect phone from PC and boot into system." aaaaaaaaaaand.... it worked. Q,Q
Now all i need to do is trying to get the backup back until my boyfriend is home
But one question is still open:
When we tryed to load the backup, then the op3t said, that the backup is encrypted. But.. i'm pretty sure we didn't encrypt the phone-data. We also thing, that the problem why the backup didn't work correctly was, that the data was encrypted and so we couldn't gain access to it. We tryed this with his Win7-PC and my Linux-Laptop. Even with different USB-Ports (2.0 and 3.0).
I'm going to do a new backup now from the op3t, but what if the problem shows up again?
Someone got an idea if the MD5-Backup-Stuff should be encrypted or decrypted?
Besides that:
Thank you very much for the help!! I guess i wasnt that qualified with fixing phone-issues and i might did some very nooby failures... so really thank you for your patience
Click to expand...
Click to collapse
When you say load the backup, you mean a backup that you made in TWRP recovery, prior to bricking your phone?
My experience with the unbricking guide was that it in essence did a full wipe and reset (including the recovery partition). That would eliminate TWRP from your phone as well as any stored backups you had.
When I unbricked, I opted to just leave it stock as nougat was around the corner.
I also re-read your original post. I wouldn't have considered your phone "bricked" at that point.
I would bet that you could have booted the phone into TWRP.
You'll want to keep these things in mind too for future TWRP encryption issues (it's a known issue that most likely won't be fixed).
1) before you make a twrp backup, remove any figerprints/pins/passwords from your device, sometimes prevents issues for me
2)if you existing pins/passwords don't work try "default_password" that may work
3)if all else fails, boot into twrp, navigate to /data/system/ and down the list will be a few files to delete
- password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
4) the last step is always the first step for me, too many issues with twrp and encryption
GammarursPulex said:
I gave my phone to my girlfriend, because I had to head to work. She wrote to me:
"Tryed it a couple of times now and then there was something like "QHUSB_BULK" showed up. But only for around 3 seconds, then i got the message "RELINK HS-USB QDLOADER 9008 (COM4) installed". Now the device-manager has this "RELINK..."-thing, but not at "unknown devices" but at "Connections (COM & LPT)". I tryed to go to point "Update Device Software", but all I get is "its already installed". When i go to details, it sais something about "\system32\DRIVERS\cmnxusber.sys".
After this i tryed to get the QHUSB_BULK back on the screen, but it seems like Windows7 is installing this DeviceSoftware every time when i reconnect the phone with "volume button while connecting the phone to the computer". I even tryed to deactivate/deinstall the DeviceSoftware, but its the same game every time i try it from the beginning.
Then i tryed the MsmDownloadTool, but hey.. no response. Guess i need to update the software first."
Shes now sitting in front of my PC and trying the steps. I'm out of ideas at the moment, do you have an idea what she is doing wrong or where the problem is now? (At least we are a step further now, haha!)
@nvertigo67
I can look up for this sort of cable when I'm back home. But i hope this unbrick tool will succeed.
Click to expand...
Click to collapse
u r doing something wrong.. please follow guide correctly
It works 100℅
Just out of curiosity, did you unlock the bootloader before you did everything? Also did you go into settings -->developer mode and turn on OEM unlock and USB debugging?
From my experience, try wiping everything through twrp --> install the firmware/backup --> and then try doing another wipe and reboot. Now I understand you might lose your root/SU after wiping, but perhaps this will at least boot into the system for you.
If all else fails, try using ODIN and flash your stock firmware http://downloads.oneplus.net/devices/oneplus-3t/
EDIT:
If you're having driver issues try this.
1. Go into device manager (as admin)
2. Double click the device that you're having trouble with
3. Click on "Details" tab
4. Under "Property" dropdown, choose "Hardware Ids"
5. When you select that you should see a bunch of values under there. Right click the first one and copy it.
Ex:\ I have an S7 phone so mine looks like "USB\VID_04E8&PID_6860&REV_0400&ADB"
6. Now the value you copied, try searching it in google. Or paste it on here for us to help you find drivers compatible with it. Usually you can find compatible drivers in google. Once you find them and download them, if you go back to that device and click "Update Driver" you can manually point to the extracted drivers. It will find the compatible *.inf file and install it for that device.
Hope this helps!
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
this works for me, every time i kill my 3T.
you must be doing something wrong.
Follow everyline