hi guys, i hope you can help me.
I install android sdk and usb google drivers.
when my n9 is on adb recognise it and i can find it in list of device attacched.
when i reboot in recovery my device insn't listed anymore and when i try to sideload the ota it says "device not found"
i tried to reinstall drivers but it hasn't fixed anything.
What can i do?
zera89 said:
hi guys, i hope you can help me.
I install android sdk and usb google drivers.
when my n9 is on adb recognise it and i can find it in list of device attacched.
when i reboot in recovery my device insn't listed anymore and when i try to sideload the ota it says "device not found"
i tried to reinstall drivers but it hasn't fixed anything.
What can i do?
Click to expand...
Click to collapse
When booted into recovery go to device manager on your pc. Do you see an icon with a yellow exclamation mark? If so, right click on it and go to where it lets you choose a driver from a list on the computer. Choose android adb composite interface.
Sent from my Nexus 5 using XDA Free mobile app
zera89 said:
hi guys, i hope you can help me.
I install android sdk and usb google drivers.
when my n9 is on adb recognise it and i can find it in list of device attacched.
when i reboot in recovery my device insn't listed anymore and when i try to sideload the ota it says "device not found"
i tried to reinstall drivers but it hasn't fixed anything.
What can i do?
Click to expand...
Click to collapse
jd1639 said:
When booted into recovery go to device manager on your pc. Do you see an icon with a yellow exclamation mark? If so, right click on it and go to where it lets you choose a driver from a list on the computer. Choose android adb composite interface.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
In addition to what @jd1639 said, once your device is recognized by your PC, if you continue to have problems when in recovery menu, try to unplug and replug in your USB cable.
jd1639 said:
When booted into recovery go to device manager on your pc. Do you see an icon with a yellow exclamation mark? If so, right click on it and go to where it lets you choose a driver from a list on the computer. Choose android adb composite interface.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
EDIT
i found it and i install composite adb driver even if windows was saying me that it can't verify driver's signature.
installing ota with sideload is safe?
zera89 said:
EDIT
i found it and i install composite adb driver even if windows was saying me that it can't verify driver's signature.
installing ota with sideload is safe?
Click to expand...
Click to collapse
Yes. I would add that it's a good idea to unlock your bootloader first. If something goes wrong and your bootloader is locked, you're pretty much screwed.
cam30era said:
Yes. I would add that it's a good idea to unlock your bootloader first. If something goes wrong and your bootloader is locked, you're pretty much screwed.
Click to expand...
Click to collapse
are you talking about OEM UNLOCK in developer options?
zera89 said:
are you talking about OEM UNLOCK in developer options?
Click to expand...
Click to collapse
Actually two steps. 1st check that box in developer options. 2nd, boot to bootloader and enter this command > fastboot oem unlock
NOTE: This will wipe the contents of your SDcard.
cam30era said:
Actually two steps. 1st check that box in developer options. 2nd, boot to bootloader and enter this command > fastboot oem unlock
NOTE: This will wipe the contents of your SDcard.
Click to expand...
Click to collapse
i was looking for a way to force ota without wipe or unlocking...
do you suggest me OTA sideload procedure or wait for official ota?
zera89 said:
i was looking for a way to force ota without wipe or unlocking...
do you suggest me OTA sideload procedure or wait for official ota?
Click to expand...
Click to collapse
Your choice. Process and likely outcomes do not differ. My point is regarding risk and reward. I understand that you don't want to unlock or wipe. My caution to you is this: the OTA package sometimes fails to install, part way through the process. If your bootloader is locked, your device will probably be bricked and your only option will be RMA. I'm not trying to scare you into doing something you don't want to do, just pointing out the facts. And it doesn't matter whether you sideload the OTA, or wait for it to show up on your device. The risk is the same.
On the other hand, if your bootloader is unlocked, and the OTA fails, you can easily recover from it. In fact, you don't even need to sideload the OTA. You can then fastboot flash the Google factory image.
uhm... ok... i'm understanding...
don't you think a bricking ota is almost a paradox?
i mean... Htc & Google make a update with errors or problems? it's foolish.
I can understand a custom rom but two giants like 'em...
i don't know what to do... i'm gonna think about it
thanks for your help!
zera89 said:
uhm... ok... i'm understanding...
don't you think a bricking ota is almost a paradox?
i mean... Htc & Google make a update with errors or problems? it's foolish.
I can understand a custom rom but two giants like 'em...
i don't know what to do... i'm gonna think about it
thanks for your help!
Click to expand...
Click to collapse
I'm certainly not debating the paradox with you. I'm just providing advice based on my own experience, and the (unfortunate) experience of other users on this forum. Good luck with what ever you decide to do here....
Related
I'm sorry if there is something already posted here somewhere about the rezound, but I haven't seen anything...yet...lol.
I've been trying to root my rezound ALL DAY and can't seem to figure anything out apparently.
If someone could help me out with sending me a link to the best way of unlocking bootloader and then rooting my phone. I had a dinc2 previously and that was not as hard to root compared to the rezound IMO. So please, if someone can take the time for me and help me out with getting my phone unlocked and rooted I would greatly appreciate it a TON!!!
Try this out http://forum.xda-developers.com/showthread.php?t=1648578
http://bit.ly/N3cfpa
hey guys thanks for replying back....I'm still getting no luck whatsoever with unlocking the bootloader.....I'm doing everything (or so I think I am) right with the steps on htcdev.com and when I get to the command prompt and type in fastboot oem get_identifier_token...this is what comes up
'fastboot' is not recognized as an internal or external command,
operable program or batch file.....now I have NO CLUE what the heck to do!! I'm getting pissed off lol. I could really use some help here. thanks
You need to change the directory to where your fastboot is located.
Sent from my ADR6425LVW using xda premium
EmerikL said:
You need to change the directory to where your fastboot is located.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Fastboot is located in the Android folder that i created....I found out my problem. My laptop isn't recognizing my phone at all. I read about this on a few forums about a lot of other people having this same issue with the rezound.....I try to install drivers on my pc for my phone to be recognized but its still not working....How did you or anyone else on here get their pc to recognize their phone???
npainter7 said:
Fastboot is located in the Android folder that i created....I found out my problem. My laptop isn't recognizing my phone at all. I read about this on a few forums about a lot of other people having this same issue with the rezound.....I try to install drivers on my pc for my phone to be recognized but its still not working....How did you or anyone else on here get their pc to recognize their phone???
Click to expand...
Click to collapse
Did you install HTC Sync properly? And have you tried installing the android usb drivers using SDK Manager?
kzoodroid said:
Did you install HTC Sync properly? And have you tried installing the android usb drivers using SDK Manager?
Click to expand...
Click to collapse
Yep I've installed htc sync multiple times now and SDK manager as well. Still a no go. It's really frustrating I can even unlock my [email protected]#$%& phone lol. After I install SDK manager, is there something else I have to do to it??? I think I have everything ready to unlock my device but once I click fastboot OEM get identifier token it says waiting for device and doesn't do anything after that. Freakin sucks
Yeah make sure you have the HTC drivers installed. I had the same issue in Jan when I rooted mine, drivers weren't there.
Posted from my Rooted and ICS'd Rezound
Fastbird said:
Yeah make sure you have the HTC drivers installed. I had the same issue in Jan when I rooted mine, drivers weren't there.
Posted from my Rooted and ICS'd Rezound
Click to expand...
Click to collapse
I'm pretty sure I had them downloaded. Just to make sure, what is included in the drivers?? That way I know everything is there when its downloaded.
npainter7 said:
Yep I've installed htc sync multiple times now and SDK manager as well. Still a no go. It's really frustrating I can even unlock my [email protected]#$%& phone lol. After I install SDK manager, is there something else I have to do to it??? I think I have everything ready to unlock my device but once I click fastboot OEM get identifier token it says waiting for device and doesn't do anything after that. Freakin sucks
Click to expand...
Click to collapse
After you install Android SDK the directions on the HTCdev site tell you to run sdk manager and download the Android SDK Tools and Android SDK Platfrom-tools. What I did was to take this a step further and also install the Google USB Driver which is listed in ADB Manager under Extras and also the API's for GB and ICS. The API's really aren't necessary but I don't think ADB will recognize the phone without the Google USB Drivers.
npainter7 said:
I'm pretty sure I had them downloaded. Just to make sure, what is included in the drivers?? That way I know everything is there when its downloaded.
Click to expand...
Click to collapse
This may not work for you, but one time my drivers weren't working because I plugged my phone into a USB 3.0 port, so when I used a USB 2.0 port, it worked fine.
So, my phone is stuck in a boot loop. I can restore factory setting but first i want to back up my data .. specifically my text messages and pictures. They are very important. Is there a way i can do that ?
the bad news is Im not rooted. now im trying to find ways to save data from my the phone before i do a factory reset. i hope i can sort it out.
Thanks,
runingwild said:
So, my phone is stuck in a boot loop. I can restore factory setting but first i want to back up my data .. specifically my text messages and pictures. They are very important. Is there a way i can do that ?
the bad news is Im not rooted. now im trying to find ways to save data from my the phone before i do a factory reset. i hope i can sort it out.
Thanks,
Click to expand...
Click to collapse
Your pictures should be on your SD and unaffected, but without root I'd say goodbye to your messages.
XperienceD said:
Your pictures should be on your SD and unaffected, but without root I'd say goodbye to your messages.
Click to expand...
Click to collapse
so is there no hope even by using ADB commands for example, or some other way? :crying:
up
runingwild said:
so is there no hope even by using ADB commands for example, or some other way? :crying:
Click to expand...
Click to collapse
I think, without root, you can't view /data, but you can try.
If you can, the sms should be located in this .xml: er /data/data/com.android.providers.telephony/databases/mmssms.db
Then backup it via adb, reflash your rom and replace the file with the backuped one.
If you can't access /data, maybe you can root/flash cwm to your phone too, if it's bootloped? (Phone specific, so I don't know.)
Good luck.
Sent from my GT-I9100 using xda app-developers app
cakebomb said:
I think, without root, you can't view /data, but you can try.
If you can, the sms should be located in this .xml: er /data/data/com.android.providers.telephony/databases/mmssms.db
Then backup it via adb, reflash your rom and replace the file with the backuped one.
If you can't access /data, maybe you can root/flash cwm to your phone too, if it's bootloped? (Phone specific, so I don't know.)
Good luck.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
thanks for the advice,
and how can i view the .xml file? (im not experienced with android..)
btw, its an Htc Desire S. yes its stuck in bootloop now
runingwild said:
thanks for the advice,
and how can i view the .xml file? (im not experienced with android..)
btw, its an Htc Desire S. yes its stuck in bootloop now
Click to expand...
Click to collapse
Connect your phone to your computer, start adb shell and type in su and then cd data
If you can view the directory by typing in ls you should be able, to copy the .xml to your computer.
Sorry for the late reply.^^
cakebomb said:
Connect your phone to your computer, start adb shell and type in su and then cd data
If you can view the directory by typing in ls you should be able, to copy the .xml to your computer.
Sorry for the late reply.^^
Click to expand...
Click to collapse
ok thanks. i downloaded SDK, then installed ADB package. But now i click on Adb icon and it wont open. what am i doing bad??
runingwild said:
ok thanks. i downloaded SDK, then installed ADB package. But now i click on Adb icon and it wont open. what am i doing bad??
Click to expand...
Click to collapse
You have to open cmd.exe and navigate to the location, where the adb file is located.
Then type in ‘adb shell’.
Sent from my Nexus 7 using xda app-developers app
cakebomb said:
You have to open cmd.exe and navigate to the location, where the adb file is located.
Then type in ‘adb shell’.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
when i type in adb shell, it says Error: device not found, while the phone was in the boot menu.
Is it maybe because im missing drivers? I googled a bit and now i have the driver i need, its .exe file , what should i do with this file? if i double click on it, i get an error message.
thanks
runingwild said:
when i type in adb shell, it says Error: device not found, while the phone was in the boot menu.
Is it maybe because im missing drivers? I googled a bit and now i have the driver i need, its .exe file , what should i do with this file? if i double click on it, i get an error message.
thanks
Click to expand...
Click to collapse
Yes, the drivers could be the problem or maybe (but I don't hope so) the phone isn't recognizable in this mode via adb.
If you're using Windows, go to the device manager and check, if there's a android thing with a exclamation, then refresh the driver of this, if it's possible. Simply via right click etc. (Of course, if the device is connected.)
And have you tried this here? http://forum.xda-developers.com/showpost.php?p=15585507&postcount=2
btw: Your phone seems to don't boot up since a few days, do you don't need it? Another idea is, maybe you can backup all your files via fastboot/download mode or something else, but you'll have to post this question in the device specifically forum, because it's different on phones.
Okay, one more time good luck.
hello
cakebomb said:
Yes, the drivers could be the problem or maybe (but I don't hope so) the phone isn't recognizable in this mode via adb.
If you're using Windows, go to the device manager and check, if there's a android thing with a exclamation, then refresh the driver of this, if it's possible. Simply via right click etc. (Of course, if the device is connected.)
And have you tried this here? http://forum.xda-developers.com/showpost.php?p=15585507&postcount=2
btw: Your phone seems to don't boot up since a few days, do you don't need it? Another idea is, maybe you can backup all your files via fastboot/download mode or something else, but you'll have to post this question in the device specifically forum, because it's different on phones.
Okay, one more time good luck.
Click to expand...
Click to collapse
yes, in the device manager there is an android thing with a yellow exclamation. i clicked on refresh the driver and i get the window asking me where i want to get the driver from. since i have the driver in an Sd card, i´ll try that tomorrow.
well, i do need the phone, but now im using my old one. until i can finally fix this issue.
What did you mean with the Fastboot mode? when im in the boot menu, i can select Fastboot, but it wont help much, because it will just start the booting again (bootloop). but i dont know if this is what you meant with fastboot.
thanks
runingwild said:
yes, in the device manager there is an android thing with a yellow exclamation. i clicked on refresh the driver and i get the window asking me where i want to get the driver from. since i have the driver in an Sd card, i´ll try that tomorrow.
well, i do need the phone, but now im using my old one. until i can finally fix this issue.
What did you mean with the Fastboot mode? when im in the boot menu, i can select Fastboot, but it wont help much, because it will just start the booting again (bootloop). but i dont know if this is what you meant with fastboot.
thanks
Click to expand...
Click to collapse
Okay, but you can also let Windows automaticly search the internet for the drivers.
About fastboot, I don't know if you can backup files with this. (Normally you can use this to flash boot.img etc.) And I don't know, how it works on your device, so ask in your device forum.
Sent from my GT-I9100 using xda app-developers app
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
runingwild said:
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
Click to expand...
Click to collapse
Okay.
Are you talking about flashing stock rom, when you said factory reset?
If not, maybe this helps. (There's a link to flash stock rom in this thread.)
http://forum.xda-developers.com/showthread.php?t=1186401
Sent from my GT-I9100 using xda app-developers app
Okay, just wanted to put this info here for easy reference. Feel free to correct anything I may have wrong.
*Based on my experiences performing the operation on windows 7 x64.
1. Install the LG USB driver for windows found under the software tab from their site here
2. Download and extract the English version of the root optimus g created by fiddy619 from here
3. Set USB debugging on and attach your phone to usb, then put it in MTP/Media Sync mode. Next, open a command prompt and navigate to the "stuff" sub-directory of the extracted file. Run the command "adb devices" to make sure your phone has been detected. Go back to the main directory and run the RootOptimusG.bat file.
4. When prompted on your phone choose restore data. Leave your phone plugged into USB until the program tells you it is finished! Sit back and let the magic happen. Your phone will reboot. Mine acted weird for a few seconds after it rebooted, the buttons at the bottom were going on and off and the screen was flickering. Just be patient and give it a couple minutes if needed.
5. When prompted that all is complete you can disconnect your phone from your computer and open the Play store to get the update for SuperSU
Now you are ready to unlock!
should be a sticky.
Thanks!
I followed the thread to root no fiddy619 instructions. I did use MTP.
But instead of Command prompt, I just double clicked the BAT file. and it run without problems, I think.
I have the SuperSU icon on my phone.
How can i make sure it was rooted?
p.s
The unlock also ran without problems.
karelson said:
I followed the thread to root no fiddy619 instructions. I did use MTP.
But instead of Command prompt, I just double clicked the BAT file. and it run without problems, I think.
I have the SuperSU icon on my phone.
How can i make sure it was rooted?
p.s
The unlock also ran without problems.
Click to expand...
Click to collapse
well if you have the supersu then it should be rooted. also if you now have it unlocked then it is rooted because i dont think you can unlock unless you root. also please search around the forums about what apps to not remove after root. a lot of people have noted issues after removing google apps.
showstopper03 said:
well if you have the supersu then it should be rooted. also if you now have it unlocked then it is rooted because i dont think you can unlock unless you root. also please search around the forums about what apps to not remove after root. a lot of people have noted issues after removing google apps.
Click to expand...
Click to collapse
Great Thank You.
karelson said:
Great Thank You.
Click to expand...
Click to collapse
actually it looks like V.05 you can uninstall any app without fear of security warnings. Please read all of this link for more info on it.
http://forum.xda-developers.com/showthread.php?t=2001655
Correct, you can just double click the bat file...my steps vary because I included a check to make sure adb is recognizing your device properly.
karelson said:
I followed the thread to root no fiddy619 instructions. I did use MTP.
But instead of Command prompt, I just double clicked the BAT file. and it run without problems, I think.
I have the SuperSU icon on my phone.
How can i make sure it was rooted?
p.s
The unlock also ran without problems.
Click to expand...
Click to collapse
Bumping this back to the top until stickied.
Sent from my LG Optimus G using Tapatalk 2
IrateCustomer said:
Bumping this back to the top until stickied.
Sent from my LG Optimus G using Tapatalk 2
Click to expand...
Click to collapse
Mine is stuck at "Select Restore Data" from my Phone step ... not sure whats going on.
kirdroid said:
Mine is stuck at "Select Restore Data" from my Phone step ... not sure whats going on.
Click to expand...
Click to collapse
I tried unrooting and re-rooting just to test our guides here and I am stuck at this step too. Obviously I can simply flash su in CWM but I wonder why this is happening.
carrett said:
I tried unrooting and re-rooting just to test our guides here and I am stuck at this step too. Obviously I can simply flash su in CWM but I wonder why this is happening.
Click to expand...
Click to collapse
Go to general-developer options- set desktop backup password. Set the password and then use that when you run the script and restore from desktop backup screen shows up.
Sent from my LG-E970 using Tapatalk 2
kirdroid said:
Go to general-developer options- set desktop backup password. Set the password and then use that when you run the script and restore from desktop backup screen shows up.
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
If that worked for you, I'm happy for you. I am at this time unable to find a way to unroot and then re-root aside from restoring a backup in CWM or flashing a superuser zip in CWM. This could be because of a "bug" in our rooting script, in SuperSU's un-rooting function, or just an incompatibility between the two. Either way, I think this rooting mechanism works for more virgin LGOGs than not.
worked for me, easy peasy.
When i run the script it gives an error saying that i'm missing backup-restore.apk and /system/bin/ric does not exist. Any ideas as to why this is?
nice. thank you.
aznracer62 said:
When i run the script it gives an error saying that i'm missing backup-restore.apk and /system/bin/ric does not exist. Any ideas as to why this is?
Click to expand...
Click to collapse
That is probably because your phone is not rooted yet. I got that too as I was rooting it. Worked great.
I'm trying to root. USB debugging is on, connected as MTP. Run ADB, run adb-devices, returns an empty screen.
Try to run the script, it tells me "please check setting again"
HALP.
bebop_ said:
I'm trying to root. USB debugging is on, connected as MTP. Run ADB, run adb-devices, returns an empty screen.
Try to run the script, it tells me "please check setting again"
HALP.
Click to expand...
Click to collapse
Also need to allow "unknown sources" in security settings.
adfurgerson said:
Also need to allow "unknown sources" in security settings.
Click to expand...
Click to collapse
I had that checked as well.
bebop_ said:
I had that checked as well.
Click to expand...
Click to collapse
Do you have lg usb drivers installed?
So not sure exactly what happened while running the lastest paranoid build. Everything was fine until a random reboot happened, said proccess stopped working and rebooted once more except for im on white screen. went to wipe data and reflash the rom but sd card has been wiped. I am s-on and cant get adb to recognize my device. Any advice please.
IceAzures said:
So not sure exactly what happened while running the lastest paranoid build. Everything was fine until a random reboot happened, said proccess stopped working and rebooted once more except for im on white screen. went to wipe data and reflash the rom but sd card has been wiped. I am s-on and cant get adb to recognize my device. Any advice please.
Click to expand...
Click to collapse
go into recovery and try turning adb sideload on then off and see if adb recognizes your device after that.
failed to open driver control: no such file or directory
when i start adb, it zooms really fast through codes and then exits.
IceAzures said:
failed to open driver control: no such file or directory
when i start adb, it zooms really fast through codes and then exits.
Click to expand...
Click to collapse
Then you didn't set adb up correctly
Edit: now that I think of it you may be typing in the command incorrectly.
Sent from my HTC6435LVW using xda app-developers app
Ill reinstall the sdk and drivers and ill report back.
This is the correct way right?
http://forum.xda-developers.com/showthread.php?t=2131284
edit1: so to use adb im using the windows vista cmd promt correct?
edit 2: okay so we are somewhere. Adb now works. I just need to get the dna to be able to be detected. Any way i can do this?
(double post accident)
IceAzures said:
(double post accident)
Click to expand...
Click to collapse
Get into twrp
Find to sideload option.
Select it.
Plug your phone into your computer, make sure to use usb 2.0 not 3.0.
Open up a command prompt where the rom is located.
Type adb sideload rom.zip
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Get into twrp
Find to sideload option.
Select it.
Plug your phone into your computer, make sure to use usb 2.0 not 3.0.
Open up a command prompt where the rom is located.
Type adb sideload rom.zip
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
So i was getting help from another member and I feel like he is getting frustrated as I am. Im running CWM 6.0.2.1 and this is what im dealing with
Device is not recognized even though i have the drivers for it. I heard USB debugging is enabled regardless in recovery I just don't know why I cant push or sideload anything even if im on install zip from sideload.
IceAzures said:
So i was getting help from another member and I feel like he is getting frustrated as I am. Im running CWM 6.0.2.1 and this is what im dealing with
Device is not recognized even though i have the drivers for it. I heard USB debugging is enabled regardless in recovery I just don't know why I cant push or sideload anything even if im on install zip from sideload.
Click to expand...
Click to collapse
CWR has some issues with adb. flash latest version of twrp here:
http://techerrata.com/browse/twrp2/dlx
beaups said:
CWR has some issues with adb. flash latest version of twrp here:
http://techerrata.com/browse/twrp2/dlx
Click to expand...
Click to collapse
Do you think vista might be an interference? Im currently on waiting on device while trying to flash the recovery in fastboot
IceAzures said:
Do you think vista might be an interference? Im currently on waiting on device while trying to flash the recovery in fastboot
Click to expand...
Click to collapse
nope. Vista sucks and all, but it isn't the problem here.
IceAzures said:
Do you think vista might be an interference?
Click to expand...
Click to collapse
There's your problem. "Vista"
Sent from my Galaxy Nexus using xda app-developers app
beaups said:
nope. Vista sucks and all, but it isn't the problem here.
Click to expand...
Click to collapse
So what would you recommend at this point? Because at this rate im surprised my phone is not dead yet. Although i do see the led light in recovery mode
AGoogleUser said:
There's your problem. "Vista"
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Yeah and unfortunately its all i got
IceAzures said:
So what would you recommend at this point? Because at this rate im surprised my phone is not dead yet. Although i do see the led light in recovery mode
Yeah and unfortunately its all i got
Click to expand...
Click to collapse
I'd recommend you flash twrp then adb push your rom, then flash it
Okay im going to post the steps and maybe this will be easier for all of us.
1- Flashed Paranoid
2- Flashed crpalmers boot.img in flashgui
3- Phone was good for a solid day, then rebooted.
4- After reboot phone said a lot of the services are force closing and then rebooted into the white htc screen
5- http://forum.xda-developers.com/showthread.php?t=2131284 and followed it to the T
6- phone is not being recognized in adb
7- went to flash the recovery but its waiting on device even though its in fastboot usb
Maybe im missing a driver or a step I am not sure about but hopefully that helps a bit more than posting little by little.
IceAzures said:
Okay im going to post the steps and maybe this will be easier for all of us.
1- Flashed Paranoid
2- Flashed crpalmers boot.img in flashgui
3- Phone was good for a solid day, then rebooted.
4- After reboot phone said a lot of the services are force closing and then rebooted into the white htc screen
5- http://forum.xda-developers.com/showthread.php?t=2131284 and followed it to the T
6- phone is not being recognized in adb
7- went to flash the recovery but its waiting on device even though its in fastboot usb
Maybe im missing a driver or a step I am not sure about but hopefully that helps a bit more than posting little by little.
Click to expand...
Click to collapse
Do you htc's adb drivers installed? Not just the sdk.
Sent from my VIPER DNA
reaverclan said:
Do you htc's adb drivers installed? Not just the sdk.
Sent from my VIPER DNA
Click to expand...
Click to collapse
I believe i have them installed, but everytime i try to install the drivers via device manager I have windows telling me its already and its latest driver installed.
Good thing though is now my device is being recognized in adb and fastboot <devices> but still having issues pushing or flashing rom
IceAzures said:
I believe i have them installed, but everytime i try to install the drivers via device manager I have windows telling me its already and its latest driver installed.
Good thing though is now my device is being recognized in adb and fastboot <devices> but still having issues pushing or flashing rom
Click to expand...
Click to collapse
When in device manager , how is the unit listed? Does the listing have an yellow exclamation point in front of it?
IceAzures said:
I believe i have them installed, but everytime i try to install the drivers via device manager I have windows telling me its already and its latest driver installed.
Good thing though is now my device is being recognized in adb and fastboot but still having issues pushing or flashing rom
Click to expand...
Click to collapse
Might want to unplug from the net when installing them so it doesn't look for others which driver version you installing? EDIT: also if you have a otg cable then you can put the rom on a flash drive and flash it from that.
Sent from my VIPER DNA
IceAzures said:
I believe i have them installed, but everytime i try to install the drivers via device manager I have windows telling me its already and its latest driver installed.
Good thing though is now my device is being recognized in adb and fastboot <devices> but still having issues pushing or flashing rom
Click to expand...
Click to collapse
What error is it giving you when you try to push a rom.
Sent from my HTC6435LVW using xda app-developers app
Hi there guys,
I'm new to the forum so apologies if this has been posted in the wrong place.
So I was directed to this forum to attempt to solve a different problem but in my hast, I have caused an even bigger problem!
So initially I was having problems with the new Android Wear update with regards to rooting, so I wanted to find a way to roll the software back or restore the device to stock.
I came across this post http://forum.xda-developers.com/g-watch/development/tool-lg-g-watch-return-to-stock-t3158349 and attempt to do as advised, but half way through the process, the program froze. I then tried to reset the watch from the button at the back, but the watch is now stuck on the fastboot menu. I used ADB to see if I could still connect to the device but no devices can be found.
I have checked the device manager and can see the device as "Android Bootloader Interface" but can't seem to get it past the fastboot menu.
Any help would be much appreciated.
Thanks in advance.
just do it again, as long you can get fastboot, you are safe.
Jaocagomez said:
just do it again, as long you can get fastboot, you are safe.
Click to expand...
Click to collapse
The problem is, the program requires a connection via ADB, but ADB can no longer see the device. So when I try to run it again, nothing happens :/
Montezz1 said:
The problem is, the program requires a connection via ADB, but ADB can no longer see the device. So when I try to run it again, nothing happens :/
Click to expand...
Click to collapse
F the program it is outdated as **** get adb minimal here and the last 5.1.1 images here
Extract to the same folder you put adb minimal and open a terminal here.
do these commands:
Code:
fastboot flash boot nameofboot.img
fastboot flash system nameofsystem.img
(optional) fastboot flash recovery recovery.img
fastboot format/erase data
fastboot format/erase cache
Oh yeah btw if the only problem you had was with rooting just use my guide here and system images from here instead
Xmaster24 said:
F the program it is outdated as **** get adb minimal here and the last 5.1.1 images here
Extract to the same folder you put adb minimal and open a terminal here.
do these commands:
Code:
fastboot flash boot nameofboot.img
fastboot flash system nameofsystem.img
(optional) fastboot flash recovery recovery.img
fastboot format/erase data
fastboot format/erase cache
Oh yeah btw if the only problem you had was with rooting just use my guide here and system images from here instead
Click to expand...
Click to collapse
Hi there,
Thanks for the response.
I have just completed the steps as advised, download the minimal ADB and fastboot and extracted the G Watch images into that file. I opened ADB and ran the following command:
Code:
fastboot flash boot nameofboot.img
But received the following error:
http://i.imgur.com/URh0IsF.png
Any ideas on how to solve that error?
Thanks in advance
Montezz1 said:
Hi there,
Thanks for the response.
I have just completed the steps as advised, download the minimal ADB and fastboot and extracted the G Watch images into that file. I opened ADB and ran the following command:
Code:
fastboot flash boot nameofboot.img
But received the following error:
http://i.imgur.com/URh0IsF.png
Any ideas on how to solve that error?
Thanks in advance
Click to expand...
Click to collapse
Check the bootloader lock status and report back
Xmaster24 said:
Check the bootloader lock status and report back
Click to expand...
Click to collapse
Secure boot - Enabled
Lock state - unlocked.
I did try to unlock it again just to make sure and it is showing that is it unlocked.
Montezz1 said:
Secure boot - Enabled
Lock state - unlocked.
I did try to unlock it again just to make sure and it is showing that is it unlocked.
Click to expand...
Click to collapse
Do this command:
flashing get_unlock_ability
and also try and flash another partition eg system and report back what happens
Xmaster24 said:
Do this command:
flashing get_unlock_ability
and also try and flash another partition eg system and report back what happens
Click to expand...
Click to collapse
Hi,
The result from the flashing get_unlock_ability command is provided here:
http://i.imgur.com/jczJRST.png
I attempted to flash the system image and received the following error:
http://i.imgur.com/83RXdFi.png
The watch responses the same as when attempting to flash the boot image and is stuck on "Downloading".
I also tried to flash the recovery image and received the same error as shown when flashing the boot image.
Thanks
Montezz1 said:
Hi,
The result from the flashing get_unlock_ability command is provided here:
http://i.imgur.com/jczJRST.png
I attempted to flash the system image and received the following error:
http://i.imgur.com/83RXdFi.png
The watch responses the same as when attempting to flash the boot image and is stuck on "Downloading".
I also tried to flash the recovery image and received the same error as shown when flashing the boot image.
Thanks
Click to expand...
Click to collapse
Looks like it is either that adb minimal is messed up (I use the full 1gb sdk) or there is a driver problem or you can try running cmd as administrator instead
Xmaster24 said:
Looks like it is either that adb minimal is messed up (I use the full 1gb sdk) or there is a driver problem or you can try running cmd as administrator instead
Click to expand...
Click to collapse
I did try adb from the SDK that you've mentioned and have had the same results.
I also run in Administrator every time.
What I have just noticed with regards to the drivers is the change in the name of the device in device manager. Previously it showed as "Android Composite ADB Interface" but now it is showing as "Android Bootloader Interface".
I believe that might just be because the watch is stuck on the bootloader menu so that is how it is displayed, but it could be the cause.
Montezz1 said:
I did try adb from the SDK that you've mentioned and have had the same results.
I also run in Administrator every time.
What I have just noticed with regards to the drivers is the change in the name of the device in device manager. Previously it showed as "Android Composite ADB Interface" but now it is showing as "Android Bootloader Interface".
I believe that might just be because the watch is stuck on the bootloader menu so that is how it is displayed, but it could be the cause.
Click to expand...
Click to collapse
Your pc seems to be having trouble writing anything to the watch so if it is not the sdk then it must be your driver or bootloader
---------- Post added at 12:49 PM ---------- Previous post was at 12:43 PM ----------
Just checked the tool and it shouldn't do any harm at all to your watch unless you tried the bootloader lock so it must be your drivers
Xmaster24 said:
Your pc seems to be having trouble writing anything to the watch so if it is not the sdk then it must be your driver or bootloader
---------- Post added at 12:49 PM ---------- Previous post was at 12:43 PM ----------
Just checked the tool and it shouldn't do any harm at all to your watch unless you tried the bootloader lock so it must be your drivers
Click to expand...
Click to collapse
Hi there,
I've just tried to update the drivers but they seem to be up to date.
Yeah, the only reason I thought the program had done some damage is because it froze which resulted in getting stuck on the fastboot menu, but you've more knowledge so I guess that's not the issue.
I'm not entirely sure what else can be done here. I think I might have to just get another watch and stop the update as that is when all the problems occurred.
If you can think of anything else to try, I would be willing to give it a go but don't worry yourself too much if you're out of ideas.
I really appreciate your help up to this point anyways
Thanks
Montezz1 said:
Hi there,
I've just tried to update the drivers but they seem to be up to date.
Yeah, the only reason I thought the program had done some damage is because it froze which resulted in getting stuck on the fastboot menu, but you've more knowledge so I guess that's not the issue.
I'm not entirely sure what else can be done here. I think I might have to just get another watch and stop the update as that is when all the problems occurred.
If you can think of anything else to try, I would be willing to give it a go but don't worry yourself too much if you're out of ideas.
I really appreciate your help up to this point anyways
Thanks
Click to expand...
Click to collapse
Try and lock your watch with
fastboot oem lock
then try again with
fastboot oem unlock
Also when was the first time you flashed anything anyway?
Xmaster24 said:
Try and lock your watch with
fastboot oem lock
then try again with
fastboot oem unlock
Also when was the first time you flashed anything anyway?
Click to expand...
Click to collapse
I was able to lock and then unlock, and the device notified me that it was erasing, but when I try to start the device, it still brings be back to the fastboot menu.
Do you mean flashing devices in general or flashing this specific device?
Montezz1 said:
I was able to lock and then unlock, and the device notified me that it was erasing, but when I try to start the device, it still brings be back to the fastboot menu.
Do you mean flashing devices in general or flashing this specific device?
Click to expand...
Click to collapse
This device I just want to know if you ever actually successfully flashed anything to this device
Xmaster24 said:
This device I just want to know if you ever actually successfully flashed anything to this device
Click to expand...
Click to collapse
The first attempting of flashing anything to this device I believe was when using the Return to Stock tool.
I choose the "Install ROM" option which I can see from the script attempts to flash.
So I guess it's never been successful on this device.
Montezz1 said:
The first attempting of flashing anything to this device I believe was when using the Return to Stock tool.
I choose the "Install ROM" option which I can see from the script attempts to flash.
So I guess it's never been successful on this device.
Click to expand...
Click to collapse
This whole problem started due to the fact that I couldn't see the device using ADB, so I tried to look for a method to solve that which then caused the problem I'm having now.
The only variable I can put it down to is an update that was pushed to the watch as prior to that, I had no problems at all.
Montezz1 said:
This whole problem started due to the fact that I couldn't see the device using ADB, so I tried to look for a method to solve that which then caused the problem I'm having now.
The only variable I can put it down to is an update that was pushed to the watch as prior to that, I had no problems at all.
Click to expand...
Click to collapse
Yup sounds like a driver problem for sure uninstall the watch drivers and download the google drivers here
Xmaster24 said:
Yup sounds like a driver problem for sure uninstall the watch drivers and download the google drivers here
Click to expand...
Click to collapse
I do not believe it...
After all of this, it was the drivers...
I don't get it though!! I tried to reinstall them before and nothing changed!
It's only when I completely deleted them and reinstalled that it worked.
Honestly dude, thank you so much for your help and patience. My watch is now working and paired with my phone.
I'm waiting for it to sync but hopefully I will be able to run ADB and all will be well again
Thanks you so much again.