Database Develop

Think my One is totally bricked

Hello
First off, thank you in advance. Now to the matter.
My One is completely stuck on bootloader. I tried almost everything but no luck. If i let him do normal boot, it just shows me a black screen and reboots again, over and over. After the update i cannot get acess to fastboot because windows (8.1) tells me that the device is not known. Before the update it was all ok (i had OTA 4.3).
I cannot install a custom recovery, i cannot install anything. Tried to find a RUU.exe for my CID/MID but without luck.
The strange think is that after i update to latest kit kat, i got this (text in red):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can´t do "fastboot getvar all" because i have no acess to fastboot commands.
The only thing i can do is put he phone to charge and pray to the XDA gurus
CID: VODAP102
MODEL: PN07100
SIMLOCK: NO
Anything you need to help me out, just say so and i´ll try and do my best.
Thank you

Zeus_Alex said:
Hello
First off, thank you in advance. Now to the matter.
My One is completely stuck on bootloader. I tried almost everything but no luck. If i let him do normal boot, it just shows me a black screen and reboots again, over and over. After the update i cannot get acess to fastboot because windows (8.1) tells me that the device is not known. Before the update it was all ok (i had OTA 4.3).
I cannot install a custom recovery, i cannot install anything. Tried to find a RUU.exe for my CID/MID but without luck.
The strange think is that after i update to latest kit kat, i got this (text in red):
I can´t do "fastboot getvar all" because i have no acess to fastboot commands.
The only thing i can do is put he phone to charge and pray to the XDA gurus
CID: VODAP102
MODEL: PN07100
SIMLOCK: NO
Anything you need to help me out, just say so and i´ll try and do my best.
Thank you
Click to expand...
Click to collapse
Was this OTA update or did you try and install a file manually?

Zeus_Alex said:
Hello
First off, thank you in advance. Now to the matter.
My One is completely stuck on bootloader. I tried almost everything but no luck. If i let him do normal boot, it just shows me a black screen and reboots again, over and over. After the update i cannot get acess to fastboot because windows (8.1) tells me that the device is not known. Before the update it was all ok (i had OTA 4.3).
I cannot install a custom recovery, i cannot install anything. Tried to find a RUU.exe for my CID/MID but without luck.
The strange think is that after i update to latest kit kat, i got this (text in red):
I can´t do "fastboot getvar all" because i have no acess to fastboot commands.
The only thing i can do is put he phone to charge and pray to the XDA gurus
CID: VODAP102
MODEL: PN07100
SIMLOCK: NO
Anything you need to help me out, just say so and i´ll try and do my best.
Thank you
Click to expand...
Click to collapse
whatever you do don't s-on...
will be easier to recover from.
did you relock your bootloader for any particular reason?
Oh, and don't worry - Win 8 has problems with 'talking' to your device when it's in bootloader mode.
Your phone isn't bricked. Just don't be fiddling about with it until one of the guru's with this type of issue gives you some advice.

If you have another computer or a friend with Windows 7 it won't be hard to fix at all
Sent from my HTC One using XDA Premium 4 mobile app

Zeus_Alex said:
Hello
First off, thank you in advance. Now to the matter.
My One is completely stuck on bootloader. I tried almost everything but no luck. If i let him do normal boot, it just shows me a black screen and reboots again, over and over. After the update i cannot get acess to fastboot because windows (8.1) tells me that the device is not known. Before the update it was all ok (i had OTA 4.3).
I cannot install a custom recovery, i cannot install anything. Tried to find a RUU.exe for my CID/MID but without luck.
The strange think is that after i update to latest kit kat, i got this (text in red):
I can´t do "fastboot getvar all" because i have no acess to fastboot commands.
The only thing i can do is put he phone to charge and pray to the XDA gurus
CID: VODAP102
MODEL: PN07100
SIMLOCK: NO
Anything you need to help me out, just say so and i´ll try and do my best.
Thank you
Click to expand...
Click to collapse
1- the red OS line, is because your firmware flash didnt go through, whether you did it manually or not.
if you do it manually, you do:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <- yes TWICE, if you don't do it twice you'll get the red OS line
fastboot reboot-bootloader
2- your hboot should work with Win8.1, what does it show up as in device manager? anything like this:
3- or just use an Ubuntu Live USB (no need to install, just use Try Ubuntu)

scifitrekkie said:
Was this OTA update or did you try and install a file manually?
Click to expand...
Click to collapse
I did OTA and had a reboot loop.
cr1960 said:
whatever you do don't s-on...
will be easier to recover from.
did you relock your bootloader for any particular reason?
Oh, and don't worry - Win 8 has problems with 'talking' to your device when it's in bootloader mode.
Your phone isn't bricked. Just don't be fiddling about with it until one of the guru's with this type of issue gives you some advice.
Click to expand...
Click to collapse
Thank you. I know Windows 8.1 has problems with fastboot drivers, but before that it was all right.
nateboi81 said:
If you have another computer or a friend with Windows 7 it won't be hard to fix at all
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don´t have. I have a desktop and a laptop, both with Win8
nkk71 said:
1- the red OS line, is because your firmware flash didnt go through, whether you did it manually or not.
if you do it manually, you do:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <- yes TWICE, if you don't do it twice you'll get the red OS line
fastboot reboot-bootloader
2- your hboot should work with Win8.1, what does it show up as in device manager? anything like this:
3- or just use an Ubuntu Live USB (no need to install, just use Try Ubuntu)
Click to expand...
Click to collapse
1. I tried that method before because of the bootloop and did it twice with success. Maybe something went wrong.
2. Thats the strange thing. Hboot 1.55 should indeed work but it doesn´t. And yes, thats exactly what it shows. I tried to enter security mode on win8 and do the unsigned trick, but as soon as i change to modified drivers, my mouse and keyboard stop working, so its a no go.
3. Will test that, but i dont know exactly how to mess good with linux.
And for all of you, thank you for your time. Will update as soon as i find something new.

Zeus_Alex said:
2. Thats the strange thing. Hboot 1.55 should indeed work but it doesn´t. And yes, thats exactly what it shows. I tried to enter security mode on win8 and do the unsigned trick, but as soon as i change to modified drivers, my mouse and keyboard stop working, so its a no go.
Click to expand...
Click to collapse
Please go to my guide http://forum.xda-developers.com/showthread.php?t=2541082
under FAQ #2 to fix it.
If you don't have them (but probably you do), HTC Drivers can be found here: http://forum.xda-developers.com/showthread.php?t=2089508

nkk71 said:
Please go to my guide http://forum.xda-developers.com/showthread.php?t=2541082
under FAQ #2 to fix it.
If you don't have them (but probably you do), HTC Drivers can be found here: http://forum.xda-developers.com/showthread.php?t=2089508
Click to expand...
Click to collapse
I have done the steps in FAQ#2 and this is what it shows and thats what is bothering me.
But still, i´ll go and try to boot up Ubuntu if i can find my usb pendrive
I don´t know what to do later on in ubuntu, so help is apreciated.
Thanks in advance.

Zeus_Alex said:
I have done the steps in FAQ#2 and this is what it shows and thats what is bothering me.
But still, i´ll go and try to boot up Ubuntu if i can find my usb pendrive
I don´t know what to do later on in ubuntu, so help is apreciated.
Thanks in advance.
Click to expand...
Click to collapse
Look in my FAQs, there's instructions there for Ubuntu Live USB + fastboot install
remember in linux, you'll need to use "sudo fastboot ...."

nkk71 said:
Look in my FAQs, there's instructions there for Ubuntu Live USB + fastboot install
remember in linux, you'll need to use "sudo fastboot ...."
Click to expand...
Click to collapse
Installing Ubuntu on my pendrive as i speak.
Later, after i get ADB, what should i do?

Zeus_Alex said:
Installing Ubuntu on my pendrive as i speak.
Later, after i get ADB, what should i do?
Click to expand...
Click to collapse
reflash the firmware, to get it out of "limbo"
sudo fastboot oem rebootRUU
sudo fastboot flash zip <name of firmware>.zip
sudo fastboot flash zip <name of firmware>.zip <- yep TWICE
sudo fastboot reboot-bootloader
then firmware will be back, and you can reinstall custom recovery, and flash ROM

nkk71 said:
reflash the firmware, to get it out of "limbo"
sudo fastboot oem rebootRUU
sudo fastboot flash zip <name of firmware>.zip
sudo fastboot flash zip <name of firmware>.zip <- yep TWICE
sudo fastboot reboot-bootloader
then firmware will be back, and you can reinstall custom recovery, and flash ROM
Click to expand...
Click to collapse
Thank you.
I think i won´t be needing Ubuntu. My laptop has 1 USB 2.0 port and i could make it recognize my One.
Will try those steps now.
Will i be able to go full stock from there?
Update: I did the firmware flash sucessfull. Now whats next?

Zeus_Alex said:
Thank you.
I think i won´t be needing Ubuntu. My laptop has 1 USB 2.0 port and i could make it recognize my One.
Will try those steps now.
Will i be able to go full stock from there?
Update: I did the firmware flash sucessfull. Now whats next?
Click to expand...
Click to collapse
Well where do you want to go?
BTW: i checked your first post (it doesn't say what you want to achieve), but FYI you are S-Off, so no need to LOCK/RELOCK bootloader to flash in ruu mode!!
In aviation terms: "Kindly keep you bootloader unlocked, if you are s-off"

Update 1: Tried to flash TWRP recovery but it tells me "FAILED (remote:not allowed)
So now i am stuck in bootloader because i can´t install a custom recovery.
I want full stock rom.

Zeus_Alex said:
Update 1: Tried to flash TWRP recovery but it tells me "FAILED (remote:not allowed)
Click to expand...
Click to collapse
That's because of locked bootloader.

nkk71 said:
That's because of locked bootloader.
Click to expand...
Click to collapse
How can i install the rom if i can´t do custom recovery? Sorry for all my questions, but i don´t mess with the One alot.
Another brand is ok, but HTC has some crazy stuff around the One.

Zeus_Alex said:
How can i install the rom if i can´t do custom recovery? Sorry for all my questions, but i don´t mess with the One alot.
Another brand is ok, but HTC has some crazy stuff around the One.
Click to expand...
Click to collapse
You can you just have to unlock your bootloader.

nolimit78 said:
You can you just have to unlock your bootloader.
Click to expand...
Click to collapse
Trough HTCDev or any other easy way?

nolimit78 said:
You can you just have to unlock your bootloader.
Click to expand...
Click to collapse
Zeus_Alex said:
How can i install the rom if i can´t do custom recovery? Sorry for all my questions, but i don´t mess with the One alot.
Another brand is ok, but HTC has some crazy stuff around the One.
Click to expand...
Click to collapse
1- like @nolimit78 said, you will have to unlock bootloader (you shouldnt even have locked it in the first place), can you do that? or do you need alternate methods to do that?
2- you still haven't answered my question: what is your goal?

nkk71 said:
1- like @nolimit78 said, you will have to unlock bootloader (you shouldnt even have locked it in the first place), can you do that? or do you need alternate methods to do that?
2- you still haven't answered my question: what is your goal?
Click to expand...
Click to collapse
1. I still have the "Unlock:code.bin" from HTCDev, so yes, it is possible.
2. My goal is to get a full stock rom for my CID (VODAP102) so i can go and do the future OTA´s.

Total Noob - need to install generic HTC software

Hi there, I currently have an HTC One M7 with Tmobile UK firmware and I am fed up waiting for update to KitKat and Sense 6. I understand that this is the correct place to ask a question on how to change the software so that it will take HTC official updates rather than tmob approved updates.
From what I have read I need to s-off with firewater first and flash a recovery. Is that correct? Does anyone have step by step instructions on what to do please as I do not want to brick my phone? I would like to install the "normal" HTC software and receive updates from HTC rather than wait for tmobile.
Thanks

BrownTrout said:
Hi there, I currently have an HTC One M7 with Tmobile UK firmware and I am fed up waiting for update to KitKat and Sense 6. I understand that this is the correct place to ask a question on how to change the software so that it will take HTC official updates rather than tmob approved updates.
From what I have read I need to s-off with firewater first and flash a recovery. Is that correct? Does anyone have step by step instructions on what to do please as I do not want to brick my phone? I would like to install the "normal" HTC software and receive updates from HTC rather than wait for tmobile.
Thanks
Click to expand...
Click to collapse
can you post your fastboot getvar all please ? remove imei and seial number beforeposting

Seanie280672 said:
can you post your fastboot getvar all please ? remove imei and seial number beforeposting
Click to expand...
Click to collapse
Hi Seanie, how do I do that? Sorry for the noobness but I really am new to this. Thank you for your help.

BrownTrout said:
Hi Seanie, how do I do that? Sorry for the noobness but I really am new to this. Thank you for your help.
Click to expand...
Click to collapse
do you have fastboot and adb installed on your computer ?

Seanie280672 said:
do you have fastboot and adb installed on your computer ?
Click to expand...
Click to collapse
No, I have downloaded adt-bundle-windows-x86.zip though, is this the correct thing?

easiest way is to download and install this, you need to run as administrator for it to work:
http://forum.xda-developers.com/showthread.php?t=2317790
---------- Post added at 11:57 AM ---------- Previous post was at 11:52 AM ----------
once installed, reboot your phone to fastboot mode, basically restart it and whilst its shutting down hold down the volume down button, you will enter the bootloader, plug it into the computer and select fastboot on the phone screen, if its not already there, its should now say fastboot usb.
Open a command window in the fastboot and adb window you have just installed on your computer, (control + shift + right mouse click on any white area in that folder, open command window here)
The type:
Code:
fastboot getvar all
post the output here minus imei and serial number

Seanie280672 said:
easiest way is to download and install this, you need to run as administrator for it to work:
http://forum.xda-developers.com/showthread.php?t=2317790
---------- Post added at 11:57 AM ---------- Previous post was at 11:52 AM ----------
once installed, reboot your phone to fastboot mode, basically restart it and whilst its shutting down hold down the volume down button, you will enter the bootloader, plug it into the computer and select fastboot on the phone screen, if its not already there, its should now say fastboot usb.
Open a command window in the fastboot and adb window you have just installed on your computer, (control + shift + right mouse click on any white area in that folder, open command window here)
The type:
Code:
fastboot getvar all
post the output here minus imei and serial number
Click to expand...
Click to collapse
Thanks, I have installed that and a DOS window has popped up and after entering the command it says "Waiting for device". Do I need to boot the phone pressing volume down to get this to work as I am currently on my "normal" boot i.e. what it looks like when phone is powered on.

BrownTrout said:
Thanks, I have installed that and a DOS window has popped up and after entering the command it says "Waiting for device". Do I need to boot the phone pressing volume down to get this to work as I am currently on my "normal" boot i.e. what it looks like when phone is powered on.
Click to expand...
Click to collapse
type adb reboot bootloader in that command window (DOS window)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

BrownTrout said:
Click to expand...
Click to collapse
perfect :good:
Right your on hboot 1.55 s-off should be easy, boot back to android, type fastboot reboot in the command window (if you've not already rebooted that is)
use either rumrunner to s-off http://rumrunner.us/
or
Firewater to s-off http://firewater-soff.com/
Do not update before getting s-off, follow the instructions on each of the sites to use the tools, rumrunner is the easiest, just download the package, extract it and run the file, firewater is a little more complicated.
once done, report back here, there will only be 2 more steps to do after that, but keep adb and fastboot on your computer, do not remove them.

Many thanks, I am getting an error though

ahh ok try firewater temp root method, its the 3rd method down, you will have to download 2 files and put them in the same folder as fastboot and adb, where you open the dos window from, the whole thing is run from the dos window, so just copy and paste the commands one at a time as listed on the page.
ahh do you have USB debugging enabled on your rom ?

Thanks, it is attempting to acquire root just now. Will update when complete.

Thanks, I have temproot and s-off now.

excellent, now that you have s-off, you have to be very careful, if you flash the wrong thing, where the phone will stop you and tell you its wrong with some sort of error with s-on, it wont anymore, it will expect that you know what you are doing and still flash it, if its wrong it will brick.
---------- Post added at 01:19 PM ---------- Previous post was at 01:15 PM ----------
so fist all, if your phone is booted into android still, open a dos window again inside the fastboot / adb folder as before and again, type:
Code:
adb reboot bootloader
once there, make sure to says fastboot USB on the phone screen.
then be very careful with this one, CID is ALWAYS 8 characters long, bear that in mind with the next command, so the next command is 2 underscores not one inbetween the HTC and the 001. always capital letters, take note of your current cid though, you will need it for warranty purposes.
Code:
fastboot oem writecid HTC__001
when complete:
Code:
fastboot reboot-bootloader
---------- Post added at 01:28 PM ---------- Previous post was at 01:19 PM ----------
Its should now say this on your screen or something close to it:
M7_UL PVT SHIP S-OFF ??
CID-HTC__001
HBOOT-?????????
RADIO-??????????
OpenDSP-?????????
OS??????????
etc etc etc, can you confirm please ?

It's been hanging at < waiting for device > after I typed in the fastboot reboot bootloader command

BrownTrout said:
It's been hanging at < waiting for device > after I typed in the fastboot reboot bootloader command
Click to expand...
Click to collapse
the 3rd command or the 1st command ?

Managed to get it working.

BrownTrout said:
Managed to get it working.
Click to expand...
Click to collapse
so sorry, my bad, if it was the 1st command it should of been adb reboot bootloader not fastboot, ive edited the post above.

Seanie280672 said:
so sorry, my bad, if it was the 1st command it should of been adb reboot bootloader not fastboot, ive edited the post above.
Click to expand...
Click to collapse
I have manually rebooted and ran the commands that you mentioned and it appears to have worked as the phone displays what you have posted above.

[Q&A] Stock Boot, Recovery and System for G Watch R

Q&A for Stock Boot, Recovery and System for G Watch R
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Stock Boot, Recovery and System for G Watch R. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Thank you so much!
Happy with my watch....

OTA updates not working
Hi, I flashed all the files and got my watch working again (thanks so much) however ota updates are no longer working, is this normal and if so is there any way to fix it.

tbbgreen said:
Hi, I flashed all the files and got my watch working again (thanks so much) however ota updates are no longer working, is this normal and if so is there any way to fix it.
Click to expand...
Click to collapse
Can you clarify what you mean? Is there an error or something while updating?

intersectRaven said:
Can you clarify what you mean? Is there an error or something while updating?
Click to expand...
Click to collapse
Yeah sorry, whilst going through the process of updating it downloads and then restarts, but as it starts to install an android with a red triangle warning above appears and I then have to restart the watch to get back to the normal software version, and the update is unsuccessful.

tbbgreen said:
Yeah sorry, whilst going through the process of updating it downloads and then restarts, but as it starts to install an android with a red triangle warning above appears and I then have to restart the watch to get back to the normal software version, and the update is unsuccessful.
Click to expand...
Click to collapse
If I'm not mistaken, that android you're seeing is the recovery. Did you also have stock recovery while updating? It's critical to have everything back to stock when using OTA method. If so, then maybe you just have to wait since the recovery is the one that processes the update for OTA.

intersectRaven said:
If I'm not mistaken, that android you're seeing is the recovery. Did you also have stock recovery while updating? It's critical to have everything back to stock when using OTA method. If so, then maybe you just have to wait since the recovery is the one that processes the update for OTA.
Click to expand...
Click to collapse
Ok thanks I will try that

I'm screwed?
I rooted my LG G watch R like months ago and decided to return to stock . So I ran the "windows_returntostock.bat" file that came with it and it mentioned that it's been restore back to the stock firmware but my watch is showing the fastboot menu..
I click on the O icon thinking it will boot normally back to the watch but it keep returning to the fastboot menu... so i choose to boot to recovery and do a factory reset and it still brings me to the fastboot menu after every boot.
I read the readme file and it says i need to lock my bootloader after the restore.. but how do i enter ADB again since I factory reset it? (I guess i screw this part , should not have done this?)
Instructions from the readme
WINDOWS USERS
1. unlock the bootloader (see above)
2. reboot (to make sure no extra apps are running)
3. ensure windows drivers are installed
4. ensure usb debugging is enabled on watch
5. connect watch to computer via usb
6. run windows_installer.bat
------------------------
How To Lock Bootloader
1. Enable ADB Debugging (see above)
2. Open a command prompt where you extracted the zip file
3. Run "adb reboot-bootloader" (you may need to allow connections in the prompt on your phone)
4. Once the watch reboots to the bootloader, run "fastboot oem lock"
5. Choose yes and it will lock the bootloader as well as factory reset the watch, so go re-sync with your phone

I don't own this device but it says:
4. Once the watch reboots to the bootloader, run "fastboot oem lock"
Click to expand...
Click to collapse
So did you try to lock bootleader when watch has booted to bootloader?

That's the thing. My watch just can't boot to bootloader. It always enter the fastboot menu everytime I on or choose any options. The only other thing I can enter is recovery
---------- Post added at 07:08 PM ---------- Previous post was at 06:58 PM ----------
I've lost adb debugging as well due to me factory reset it.
I can't enter bootloader/system. It always brings me to fastboot menu, I can't go anywhere else other than recovery mode.
Also my bootloader is also locked.

d3bugu said:
I rooted my LG G watch R like months ago and decided to return to stock . So I ran the "windows_returntostock.bat" file that came with it and it mentioned that it's been restore back to the stock firmware but my watch is showing the fastboot menu..
I click on the O icon thinking it will boot normally back to the watch but it keep returning to the fastboot menu... so i choose to boot to recovery and do a factory reset and it still brings me to the fastboot menu after every boot.
I read the readme file and it says i need to lock my bootloader after the restore.. but how do i enter ADB again since I factory reset it? (I guess i screw this part , should not have done this?)
Instructions from the readme
WINDOWS USERS
1. unlock the bootloader (see above)
2. reboot (to make sure no extra apps are running)
3. ensure windows drivers are installed
4. ensure usb debugging is enabled on watch
5. connect watch to computer via usb
6. run windows_installer.bat
------------------------
How To Lock Bootloader
1. Enable ADB Debugging (see above)
2. Open a command prompt where you extracted the zip file
3. Run "adb reboot-bootloader" (you may need to allow connections in the prompt on your phone)
4. Once the watch reboots to the bootloader, run "fastboot oem lock"
5. Choose yes and it will lock the bootloader as well as factory reset the watch, so go re-sync with your phone
Click to expand...
Click to collapse
I think you're asking in the wrong thread since I wasn't the source for this "windows_returntostock.bat". You could use the files in this thread though to return to stock through fastboot. Since you're already in fastboot when you turn on your watch, just issue:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img **
*boot, system and recovery image files need to be in the path or just issue where it is
**you could skip recovery but you might have non-stock recovery so better flash it as well
After this you should be able to boot back to system.

Hi but my bootloader is already locked and I can't enter system to turn on adb debugging for any process.
Is there a way to edit some files in recovery mode to manually turn on adb debugging?

d3bugu said:
Hi but my bootloader is already locked and I can't enter system to turn on adb debugging for any process.
Is there a way to edit some files in recovery mode to manually turn on adb debugging?
Click to expand...
Click to collapse
You don't need to be in adb to unlock. To unlock you need to be in fastboot which is exactly where you are. Just issue:
fastboot oem unlock
and follow the instructions. Of course, after you unlock you'll still be stuck in fastboot but then you could follow my previous reply.

Hi there, thanks for the help. I will give it a try and update you all.
Cheers
---------- Post added at 03:06 PM ---------- Previous post was at 02:41 PM ----------
intersectRaven said:
You don't need to be in adb to unlock. To unlock you need to be in fastboot which is exactly where you are. Just issue:
fastboot oem unlock
and follow the instructions. Of course, after you unlock you'll still be stuck in fastboot but then you could follow my previous reply.
Click to expand...
Click to collapse
Hi IntersectRaven, I've performed all the fastboot flash for boot , system and recovery using these files
5.0.2:
Boot: Android File Host Euroskank Mirror
*SHA1: 0E6BB823F9913C88FB745227D5D70995AFBB4E99
Recovery: Android File Host Euroskank Mirror
*SHA1: 72A970ADCE1144B6369E648526F466D46F4B6507
System: Android File Host Euroskank Mirror
*SHA1: 7EAF3EA4482D1B4E448FF3CE0134087A90328D7A
Good news, I'm able to boot to system but i'm stuck at the install android wear on screen on watch.. and my phone can't seems to pair with it.
I've factory wipe and wipe cache as well on recovery but still can't seems to pair

Hi everyone, after flashing everything back to stock,
-wipe cache-
-reset to factory
- uninstall reinstall android wear
- restart phone and watch
I still not able to pair with my phone, it stuck on this screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 03:05 AM ---------- Previous post was at 02:55 AM ----------
1. Hi, can you teach me how do i do a Fastboot clear cache and data?

These are the stock 5.0.2 roms for the LG G Watch R correct?
http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964

Whoops wrong thread nvm
---------- Post added at 07:58 PM ---------- Previous post was at 07:35 PM ----------
Hi! Thanks for the files + guide. I ran into some trouble though and could need some help.
I sideloaded the 5.1 OTA update (coming from 5.0.1.. I think. Pretty sure) and got stuck in an infinite 'animating dots' screen. I've waited for like 15 minutes. Still all I saw were dots, moving about.
Anyway. I found this thread and thought I'd just flash 5.1 files. In order was boot.img, rec.img, system.img. I now get the LG logo and then an android on its back. Soo... try flashing 5.0.1 again? Or..? Help?

RejhGadellaa said:
Whoops wrong thread nvm
---------- Post added at 07:58 PM ---------- Previous post was at 07:35 PM ----------
Hi! Thanks for the files + guide. I ran into some trouble though and could need some help.
I sideloaded the 5.1 OTA update (coming from 5.0.1.. I think. Pretty sure) and got stuck in an infinite 'animating dots' screen. I've waited for like 15 minutes. Still all I saw were dots, moving about.
Anyway. I found this thread and thought I'd just flash 5.1 files. In order was boot.img, rec.img, system.img. I now get the LG logo and then an android on its back. Soo... try flashing 5.0.1 again? Or..? Help?
Click to expand...
Click to collapse
The files are only for restoring to stock from your current version not for upgrading since the upgrades rely on various new bootloader interface checks. Go back to 5.0.1 and upgrade through OTA or sideload.

Hi there,
Thanks for the quick reply. Down-Flashing to 5.0.1 did the trick, after thatI got a nor al boot and the ota's were waiting for me
Thanks again!

ian_wright said:
These are the stock 5.0.2 roms for the LG G Watch R correct?
http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964
Click to expand...
Click to collapse
Im have same problem, help me pls:crying:

Help - cannot enter system after clean installation of Android Revolution

So aftter downloading the Android Revolution and wiping the data, I tried installing the ROM.
However it keeps booting into recovery mode. I have no idea how to fix this.
The phone tries to boot up normally, but fails to do so. It restarts and boots into recovery. (TWRP 2.5.0.0)
I have tried deleting installing a few times. Where I cleared both the cache and dalvik cache.
Still nothing. Is there any way to get another ROM onto my phone now? My computer doesn't recognize the device anymore.
After the installation it says complete, but shows an error: "set_metadata_recursive: some changes failed"
after this it says: "installation was succesful!" and tells me to do 1 full system boot before flashing mods.:crying::crying:
"Update, I found out I used a rom designed for M8 and not M7.
If anyone could help me getting ADB to work and a rom I can flash and pretty much a tutorial. I would be super grateful

So I found a m7 rom. But when trying to push it using ADB it takes a really long time and ends in protocol error.

Aisu64 said:
boots into recovery. (TWRP 2.5.0.0)
Click to expand...
Click to collapse
Here is one problem. You won't be able to flash any recent roms using twrp 2.5.0.0. Update your recovery first: https://dl.twrp.me/m7/
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
make sure you have the latest adb version (1.0.32) using the command:
Code:
adb version
If not update your android sdk-tools: https://developer.android.com/sdk/index.html#Other
Also make sure you have the latest htc drivers installed on your computer
With the latest twrp and drivers you'll be able to transfer a rom to your phone using MTP protocol when booted in twrp main menu (simply drag and drop your file from your computer to your phone storage).
If using newer roms (android 5.0.2) your phone must have a 7.xx.xxx.x firmware installed on it. Older firmware running new roms cam have issues. To determine your firmware version, use the command "fastboot getvar version-main" or "fastboot getvar all"

Finally pushed the files to the phone.
But after installing my phone still keeps entering recovery mode (twrp).

Aisu64 said:
Finally pushed the files to the phone.
But after installing my phone still keeps entering recovery mode (twrp).
Click to expand...
Click to collapse
Did you updated your twrp recovery?

alray said:
Here is one problem. You won't be able to flash any recent roms using twrp 2.5.0.0. Update your recovery first: https://dl.twrp.me/m7/
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
Can you help me a little bit? I can't see the device connected unless I'm in recovery. Can I flash a recovery in recovery?
Click to expand...
Click to collapse

Aisu64 said:
Here is one problem. You won't be able to flash any recent roms using twrp 2.5.0.0. Update your recovery first: https://dl.twrp.me/m7/
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
Can you help me a little bit? I can't see the device connected unless I'm in recovery. Can I flash a recovery in recovery?
Click to expand...
Click to collapse
afaik, not with 2.5.0.0. If you can't see the device when in bootloader / fastboot usb mode then you have drivers issues. make sur eyou have latest htc drivers installed. If needed download htc sync. This will install htc sync and the latest drivers. Then uninstall htc sync (but don't uninstall the drivers). You don't want HTC sync on your computer because it will interfere with fastboot / adb connectivity.

alray said:
Aisu64 said:
afaik, not with 2.5.0.0. If you can't see the device when in bootloader / fastboot usb mode then you have drivers issues. make sur eyou have latest htc drivers installed. If needed download htc sync. This will install htc sync and the latest drivers. Then uninstall htc sync (but don't uninstall the drivers). You don't want HTC sync on your computer because it will interfere with fastboot / adb connectivity.
Click to expand...
Click to collapse
I have tried deleting, restarting and reinstalling the drivers. But my phone wont show up under devices anymore. I really appreciate your help, but I really have to go to bed as I have a long day at work tomorrow.
Click to expand...
Click to collapse

Aisu64 said:
I have tried deleting, restarting and reinstalling the drivers. But my phone wont show up under devices anymore. I really appreciate your help, but I really have to go to bed as I have a long day at work tomorrow.
Click to expand...
Click to collapse
No problem, go take some rest and I'll help you later :good:

alray said:
No problem, go take some rest and I'll help you later :good:
Click to expand...
Click to collapse
So I've been playing around installing and reinstalling and deleting and restarting my computer.
My computer can see the device only in recovery. Everytime I'm in the bootloader/fastboot menu it dissapears from the device list in ADB.
Is it possible to flash the phone while in recovery?

Aisu64 said:
So I've been playing around installing and reinstalling and deleting and restarting my computer.
My computer can see the device only in recovery. Everytime I'm in the bootloader/fastboot menu it dissapears from the device list in ADB.
Click to expand...
Click to collapse
you won't get any adb connectivity when booted in bootloader / fastboot usb mode. ADB only works from a booted rom with usb debug turned on or from a custom recovery. In bootloader you must use fastboot commands. To see if your phone is detected by your computer when in bootlaoder / fastboot usb mode, use the command "fastboot devices"
If your phone isn't listed with this command, please post a screenshot of your Windows devices manager with the phone connected and booted in bootloader / fastboot usb mode. Also need to know what is your bootloader version? 1.44/1.54/1.55/1.56/1.57 or 1.61 ? You can see this info when booted in bootloader mode
Is it possible to flash the phone while in recovery?
Click to expand...
Click to collapse
You might want to read what I said again:
You won't be able to flash any recent rom using twrp 2.5.0.0
You can't flash a new recovery using twrp 2.5.0.0, you must use fastboot
:good:

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It says Hboot - 1.44
atm I can't even get it to show up in recovery.
Screenshot: http://imgur.com/So88OLm

Aisu64 said:
It says Hboot - 1.44
atm I can't even get it to show up in recovery.
Screenshot: http://imgur.com/So88OLm
Click to expand...
Click to collapse
ok hboot 1.44 is the oldest one and have compatibility issues with windows 8 and 10. Do you have access to a windows 7 computer?

alray said:
ok hboot 1.44 is the oldest one and have compatibility issues with windows 8 and 10. Do you have access to a windows 7 computer?
Click to expand...
Click to collapse
Yes I do. A super ancient one.
Also this is how it looks like when I'm in recovery: http://imgur.com/SxW9p66

Aisu64 said:
Yes I do. A super ancient one.
Click to expand...
Click to collapse
Please setup everything on this computer (HTC drivers + Android sdk tools (adb and fastboot), this will be much easier to work with Win7 because of your 1.44 hboot. Later, once your hboot will be updated, you'll be able to use your Win10 computer without any problem but for now better to work with Win7. Once you got everything installed on your win7 computer, boot the phone in bootloader / fastboot usb mode and use the command "fastboot devices" to see if your phone is detected. If yes then use "fastboot getvar all" command. take a screenshot of this command output and post it here (censor the IMEI number and the SERIALNO number before uploading your picture). Don't update the recovery for now.
Also this is how it looks like when I'm in recovery: http://imgur.com/SxW9p66
Click to expand...
Click to collapse
Everything is fine here.

alray said:
Please setup everything on this computer (HTC drivers + Android sdk tools (adb and fastboot), this will be much easier to work with Win7 because of your 1.44 hboot. Later, once your hboot will be updated, you'll be able to use your Win10 computer without any problem but for now better to work with Win7. Once you got everything installed on your win7 computer, boot the phone in bootloader / fastboot usb mode and use the command "fastboot devices" to see if your phone is detected. If yes then use "fastboot getvar all" command. take a screenshot of this command output and post it here (censor the IMEI number and the SERIALNO number before uploading your picture). Don't update the recovery for now.
Everything is fine here.
Click to expand...
Click to collapse
You might aswell type the next part. Cuz this will be taking a few hours ^^

Aisu64 said:
You might aswell type the next part. Cuz this will be taking a few hours ^^
Click to expand...
Click to collapse
well I need to see your "fastboot getvar all" before i can tell anything more.

alray said:
well I need to see your "fastboot getvar all" before i can tell anything more.
Click to expand...
Click to collapse
My windows 7 computer keeps asking for a "android 1.0" driver, even though I installed the HTC one m7 driver package downloaded from HTC. I also tried installing HTC Sync, but it doesn't seem to help. Also it only shows "Android 1.0" while in fastboot so I assume this is the fastboot driver?
one more thing. I can't get it to show it's connected to ADB while in recovery.

Aisu64 said:
My windows 7 computer keeps asking for a "android 1.0" driver, even though I installed the HTC one m7 driver package downloaded from HTC. I also tried installing HTC Sync, but it doesn't seem to help. Also it only shows "Android 1.0" while in fastboot so I assume this is the fastboot driver?
one more thing. I can't get it to show it's connected to ADB while in recovery.
Click to expand...
Click to collapse
Strange, it should be easy to make it work on win7. You might want to try this drivers: http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339

alray said:
Strange, it should be easy to make it work on win7. You might want to try this drivers: http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339
Click to expand...
Click to collapse
I borrowed a friends win7 computer and fastboot works! After installing the drivers you linked me to. Here is a screenshot! http://imgur.com/CN0uLu6

Help! Stuck on "Charging screen" after uninstalling magisk.

I wanted to remove root, tried following some guides and so I came upon trying to uninstall magisk. I was prompted with two choices, "Restore images" and "Complete Uninstall".
I tried out Restore images first and it said "stock backup does not exist" so I then proceeded to do a complete uninstall. I got stuck then in recovery mode bootloop.
I therefore tried to go to my recovery by turning off my phone first and now it's in this perpetual charging state, I removed the connector but it's still "charging". Forcing it to turn off by holding the power button doesn't work as well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was scared of root so I tried removing it since it was rooted when I got it, but now here I am :crying::crying::crying: please help.
Thank you very much.

Try power button + Volume down for up to 10 seconds.....should shutdown and reboot after a few seconds of shutdown
(Meaning, it will shutdown and appear to just be off.....but it will actually start to reboot after a few seconds of nothing.....so be prepared/ready to do the button mash to boot to recovery......it will vibrate once as it begins to boot again....
*****edit.....
Sorry I'm in the wrong thread (different phone), but its possible you need to press and hold power plus volume up/or volume down.
Best of luck
Sent from my [device_name] using XDA-Developers Legacy app

Thank you for the suggestion, but sadly for me it doesn't work. My phone doesn't shutdown at all and is just in this perpetual charging state even after holding the power button for 30 seconds.

Hanzor said:
I wanted to remove root, tried following some guides and so I came upon trying to uninstall magisk. I was prompted with two choices, "Restore images" and "Complete Uninstall".
I tried out Restore images first and it said "stock backup does not exist" so I then proceeded to do a complete uninstall. I got stuck then in recovery mode bootloop.
I therefore tried to go to my recovery by turning off my phone first and now it's in this perpetual charging state, I removed the connector but it's still "charging". Forcing it to turn off by holding the power button doesn't work as well.
I was scared of root so I tried removing it since it was rooted when I got it, but now here I am :crying::crying::crying: please help.
Thank you very much.
Click to expand...
Click to collapse
Which rom version are you on? You need to boot into fastboot mode abs flash the same stock boot img. I may well have it to hand in my cloud folder. Lemme know the version, hopefully all will be well again

reg66 said:
Which rom version are you on? You need to boot into fastboot mode abs flash the same stock boot img. I may well have it to hand in my cloud folder. Lemme know the version, hopefully all will be well again
Click to expand...
Click to collapse
Is the rom like the OS version? I'm not sure but I have this RAW file in my pc. My uncle said to leave it here just in case, it's called "WW_ZS660KL_16.0631.1910.35_M3.13.33.30". I also have this "root&bootstockww191035.zip" file so maybe the 191035 is my OS version? If I remember correctly he said the phone is chinese and he had to do stuff to make it english.
It's either that or Android 9.0.

Hanzor said:
Is the rom like the OS version? I'm not sure but I have this RAW file in my pc. My uncle said to leave it here just in case, it's called "WW_ZS660KL_16.0631.1910.35_M3.13.33.30". I also have this "root&bootstockww191035.zip" file so maybe the 191035 is my OS version? If I remember correctly he said the phone is chinese and he had to do stuff to make it english.
It's either that or Android 9.0.
Click to expand...
Click to collapse
Oh, you need to be quite sure as the boot img needs to match the rom. When it was rooted do you remember ever updating it? I should have 1910.35 boot img hopefully, I'll check in a mo

reg66 said:
Oh, you need to be quite sure as the boot img needs to match the rom. When it was rooted do you remember ever updating it? I should have 1910.35 boot img hopefully, I'll check in a mo
Click to expand...
Click to collapse
I've never gotten to update it, I see other people have android 10 and such but mine doesn't see the update so I just left it be. Should be the same as when I got it.

Hanzor said:
I've never gotten to update it, I see other people have android 10 and such but mine doesn't see the update so I just left it be. Should be the same as when I got it.
Click to expand...
Click to collapse
OK, I'll be in soon, will have a hunt :good:
---------- Post added at 10:57 AM ---------- Previous post was at 10:10 AM ----------
Hanzor said:
I've never gotten to update it, I see other people have android 10 and such but mine doesn't see the update so I just left it be. Should be the same as when I got it.
Click to expand...
Click to collapse
Here's the link for both root and stock boot img's 1910.35_root and stock_imgs
Are you ok with the process or do you need guidance?

reg66 said:
OK, I'll be in soon, will have a hunt :good:
---------- Post added at 10:57 AM ---------- Previous post was at 10:10 AM ----------
Here's the link for both root and stock boot img's 1910.35_root and stock_imgs
Are you ok with the process or do you need guidance?
Click to expand...
Click to collapse
I'm not very familiar with how it works, if it's okay I would be glad to be guided.

Hanzor said:
I'm not very familiar with how it works, if it's okay I would be glad to be guided.
Click to expand...
Click to collapse
That's no problem, but I've been awake now for 2 days straight. I really can't focus on anything right now. Maybe later tonight or tomorrow. Sorry dude

reg66 said:
That's no problem, but I've been awake now for 2 days straight. I really can't focus on anything right now. Maybe later tonight or tomorrow. Sorry dude
Click to expand...
Click to collapse
That's alright, I'm fine with later or tommorow as well. Rest well, and thanks!

reg66 said:
That's no problem, but I've been awake now for 2 days straight. I really can't focus on anything right now. Maybe later tonight or tomorrow. Sorry dude
Click to expand...
Click to collapse
Hey man, hope you got to rest well! Here with just a fair bit of inquiry.
So, today I've tried looking for guides on sideloading. Got my phone to bootloader as well by depleting the battery then charging it up to be able to boot into bootloader.
I got my phone then to fastboot using the adb method, my device was recognized in the adb devices command as well. The problem is, fastboot devices don't show up any results. I'm scared to worsen the problem so I didn't continue past this point.
I could see my device in the device manager as well.
Am I on the right track?

Hanzor said:
Hey man, hope you got to rest well! Here with just a fair bit of inquiry.
So, today I've tried looking for guides on sideloading. Got my phone to bootloader as well by depleting the battery then charging it up to be able to boot into bootloader.
I got my phone then to fastboot using the adb method, my device was recognized in the adb devices command as well. The problem is, fastboot devices don't show up any results. I'm scared to worsen the problem so I didn't continue past this point.
I could see my device in the device manager as well.
Am I on the right track?
Click to expand...
Click to collapse
Hey dude, so sorry for the late reply, so damn tired!! You may well now be aware of some of this etc but I'll post any way so it's all there...
1. Download and install Minimal ADB and Fastboot app (windows). Install it on your PC to root of C drive
2. Download the root&bootstockww191035.zip and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here
3. Boot into fastboot mode ( from powered off, hold volume up then press and hold power button. Fastboot mode is the 1st screen you come across, the one with the options to Start, boot to recovery, etc...)
4. Still in fastboot mode, connect phone to pc using side port on phone.
5. Go to C:\Program Files (x86)\Minimal ADB and Fastboot and double click cmd-here.exe
6. Check your device is recognised in fastboot mode by the pc/laptop by typing 'fastboot devices' in cmd window. If it is recognised you will see a string of numbers and/or letters.
7. Type 'fastboot flash boot boot.img' in cmd window.
That's it, you should now have the correct boot img for your device flashed and hopefully it'll boot up again.
Good luck

reg66 said:
Hey dude, so sorry for the late reply, so damn tired!! You may well now be aware of some of this etc but I'll post any way so it's all there...
1. Download and install Minimal ADB and Fastboot app (windows). Install it on your PC to root of C drive
2. Download the root&bootstockww191035.zip and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here
3. Boot into fastboot mode ( from powered off, hold volume up then press and hold power button. Fastboot mode is the 1st screen you come across, the one with the options to Start, boot to recovery, etc...)
4. Still in fastboot mode, connect phone to pc using side port on phone.
5. Go to C:\Program Files (x86)\Minimal ADB and Fastboot and double click cmd-here.exe
6. Check your device is recognised in fastboot mode by the pc/laptop by typing 'fastboot devices' in cmd window. If it is recognised you will see a string of numbers and/or letters.
7. Type 'fastboot flash boot boot.img' in cmd window.
That's it, you should now have the correct boot img for your device flashed and hopefully it'll boot up again.
Good luck
Click to expand...
Click to collapse
Thanks for the time man, hopefully it does work.
Edit: IT WORKS!
Had a few hiccups which was fixed by disconnecting and reconnecting the cable after going into fastboot.
THANK YOU!
Seriously, THANK YOU!
Please have a good rest, and take care!

Hanzor said:
Thanks for the time man, hopefully it does work.
Edit: IT WORKS!
Had a few hiccups which was fixed by disconnecting and reconnecting the cable after going into fastboot.
THANK YOU!
Seriously, THANK YOU!
Please have a good rest, and take care!
Click to expand...
Click to collapse
Excellent. Glad it's all good again :good: