Database Develop

KFHD System.img Recovery Tool

THIS IS NOT A CUSTOM RECOVERY!!!
KINDLE FIRE HD 8.9 ONLY!!! USE AT YOUR OWN RISK!!
This is an update to the KFHD_SRTool, now for use with the Kindle Fire HD 8.9
This is ONLY for use with 8.9" models, not for use with 7" unless you replace system.img with your own backup.
A factory cable is not needed to enable fastboot on this model. Even if the device is in a loop and ADB can not recognize it. I have personally put my device in a loop to confirm it works. To enable fastboot use option 1 from the tool
Instructions:
1. Download and unzip the tool of your choice from the link below (I have confirmed you can downgrade from 8.1.4 to 8.1.3)
2. Run SR Tool
That's it, wait for the tool to finish. Be patient this can take a few minutes. To exit fastboot use option 6 or hold down the power button for 10-20 seconds. When you reboot the first time it may seem to loop once but this is normal and will boot up. Once again be patient, especially if you chose to erase cache and userdata. The system needs to rebuild those partitions. Hope this helps some of you in the community. Again sorry for the size of the download, this is why I made this a separate tool instead of combining it with the HD7 version.
Downloads:
KFHD_SRTv2.1- 8.1.4
KFHD_SRTv2.0- 8.1.3
KFHD_SRTv1.3- 8.1.2
UPDATES:
12-24-12
System v8.1.4
12-12-12:
System backup from v8.1.3 KFHD_SRTool_v2.0
Option menu has changed
New options: Install of GoogleServicesFramework.apk, enable fastboot with device powered on or off.
Option 4 removed due to new option of enable fastboot
DOWNGRADE:
I no longer own this device so I cannot make backups of newer system versions, for the time being here are instructions for downgrading to 8.1.4:
1.) Download boot and recovery imgs(these are backups from 8.1.4) from this LINK and place in the folder where you have access to fastboot or inside the KFHD_SRTool_v2.1 folder
2.) Use KFHD_SRTool_v2.1 to flash system.img.
3.) Erase userdata and cache
4.) Open a cmd prompt from the folder where you placed the previously downloaded .img's.
Use these cmds:
Code:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
5- Reboot.
Thanks to mdblaze for bringing to my attention that a factory cable is not needed with this device
Again Thanks to kinfauns for the how to on backing up and restoring system software.

Thank you for adding the 8.9 to your tool onemeila. I appreciate the work you've done.
I can confirm this does work to fix an hd stuck on the kindle fire logo. Thanks again.

I can't download it :/
When I click "download anyway" it just refreshes the page.

FroyoShark said:
I can't download it :/
When I click "download anyway" it just refreshes the page.
Click to expand...
Click to collapse
Don't know what is going on there. I just went to the link and had no problem. Try again and let me know. If it doesn't work pm me and I'll send you another link.

onemeila said:
Don't know what is going on there. I just went to the link and had no problem. Try again and let me know. If it doesn't work pm me and I'll send you another link.
Click to expand...
Click to collapse
Hmm, it lets me download it on my desktop, but no matter what browser I try to download it on with my laptop it does the same thing. Weird.
---------- Post added at 05:11 PM ---------- Previous post was at 04:39 PM ----------
I got it working, but how do I get Apex launcher working again after the update?

FroyoShark said:
Hmm, it lets me download it on my desktop, but no matter what browser I try to download it on with my laptop it does the same thing. Weird.
---------- Post added at 05:11 PM ---------- Previous post was at 04:39 PM ----------
I got it working, but how do I get Apex launcher working again after the update?
Click to expand...
Click to collapse
Yeah sorry I made those backups before the update. Download from the play store, go into your file manager and move it from /data/app/ folder to /system/app/ folder then reboot.
Did you have to re-root.

onemeila said:
Yeah sorry I made those backups before the update. Download from the play store, go into your file manager and move it from /data/app/ folder to /system/app/ folder then reboot.
Did you have to re-root.
Click to expand...
Click to collapse
That worked, thanks. I did have to re-root. Maybe make it so it installs the OTA Rootkeeper as well?

FroyoShark said:
That worked, thanks. I did have to re-root. Maybe make it so it installs the OTA Rootkeeper as well?
Click to expand...
Click to collapse
OTA Rootkeeper does not work. There are a couple system apps that can be altered to stop updates, I can't think of them but they are in another thread. Now that you have your device working I would recommend making a backup of your own of all the partitions. If you mess something else up outside the system partition this restore tool won't fix it. Very easy to do check out this thread:
http://forum.xda-developers.com/showthread.php?t=1930656

Firstly, good work. Play store wouldn't open for me, so I ended up needing to manually copy all files from gapps onto the device. It seems that you might be missing the gapps framework permission files. It's painfully slow however, and apps are constantly closing. I full wiped using fastboot.

synergye said:
Firstly, good work. Play store wouldn't open for me, so I ended up needing to manually copy all files from gapps onto the device. It seems that you might be missing the gapps framework permission files. It's painfully slow however, and apps are constantly closing. I full wiped using fastboot.
Click to expand...
Click to collapse
Yeah the google framework was installed as user app on those backups. I don't like installing things as system apks if its not necessary, just more chances of problems. I'm in the process of adding an option to install that separately, via adb. At first I was just trying to keep everything as close to out of the box as possible so people would just have a clean slate, but its nice to have the options of add-ons in one shot if they are wanted.
I was in a hurry when I made the mods to this version for the 8.9 and just haven't had the time to look back over it. So I apologize if something is off. Please let me know if you or anyone catches something. Was it slow after the the restore?

Is this one version 8.1.2 or 8.1.3?
Need a rootable.

timnan said:
Is this one version 8.1.2 or 8.1.3?
Need a rootable.
Click to expand...
Click to collapse
The backup was done right out of the box after root, so it would be as close to factory as possible. It should be 8.1.2, but 8.1.3 is rootable also. I lost root after the update and was still able to root.

Bricked over a dpi change!
onemeila said:
THIS IS NOT A CUSTOM RECOVERY!!!
KINDLE FIRE HD 8.9 ONLY!!! USE AT YOUR OWN RISK!!
About an hour ago I ran a tool to change dpi on my Kindle 8.9 and was greeted with the unpleasant notice that my 8.9 could not boot. System goes to the screen that asks if I want to do a factory restore. That of course fails. Downloading your recovery prog, will try it in the morning, anything need to do other than follow your bouncing ball?
Thanks
[email protected]@dog
---------- Post added at 02:45 AM ---------- Previous post was at 02:36 AM ----------
onemeila said:
THIS IS NOT A CUSTOM RECOVERY!!!
KINDLE FIRE HD 8.9 ONLY!!! USE AT YOUR OWN RISK!!
To come in next version:
Install of GoogleServicesFramework.apk after erase of cache and userdata, thought about adding this after writing this post.
If anyone wants see other options included let me know.
.
Click to expand...
Click to collapse
Have you added Install of GoogleServicesFramework.apk yet?
Click to expand...
Click to collapse

[QUOTE/]
Have you added Install of GoogleServicesFramework.apk yet?[/QUOTE]
Posting link now

Works as Advertised Thank you Onemeila!
onemeila said:
[QUOTE/]
Have you added Install of GoogleServicesFramework.apk yet?
Click to expand...
Click to collapse
Posting link now[/QUOTE]
Started to use KFHD_SRT v 1.3 When I woke up this morning, had to look for GSFa before starting, then spotted your answer to me, still on my laptop! Sooo I went with KFHD_SRT v2.0 instead. Didn't even finish my first cup of coffee and you had me back up. Needless to say, I think I will stay away from the dpi tool that caused this to begin with. One question, (not sure if I ever used option 5). is it included in Option 3??
I think I owe you something, will take care of it before the weekend.

[email protected]@dog said:
Posting link now
Click to expand...
Click to collapse
One question, (not sure if I ever used option 5). is it included in Option 3?? [/QUOTE]
No it is not. I prefer not to install apps as system apps unless it is necessary. There is no sense in potentially causing more problems. Also the more you install as system, the more you will lose and have to redo if you get an update.

I bricked this device playing with permissions to get app store installed. This tool really saved me.
I used option 4 then 3 and all is well.
Installed Google resources manually as the tool lost the device. Every thing except Gmail that I have in the screenshot works.
Thanks a bunch
{
"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"
}
Sent from my KFJWI using Tapatalk 2

Is it work with 8.1.4?
Hi,
I trying root my kindle 8.9, but is not working, my system version is 8.1.4 is this the problem? I follow steps, but SR Tool, is not detecting my kindle it just stay on <waiting for device>. I tried option 1, to start adb and i got message that adb is outdated, after that i tried option 3 and stay on waiting for device.
I now my kindle show up in adb devices list, after install right drivers, but recovery continue waiting for device.
edited 1: any help very appreciated.
edited 2: finaly all works fine.
thanks.

drr00t said:
Hi,
I trying root my kindle 8.9, but is not working, my system version is 8.1.4 is this the problem? I follow steps, but SR Tool, is not detecting my kindle it just stay on <waiting for device>. I tried option 1, to start adb and i got message that adb is outdated, after that i tried option 3 and stay on waiting for device.
I now my kindle show up in adb devices list, after install right drivers, but recovery continue waiting for device.
edited 1: any help very appreciated.
edited 2: finaly all works fine.
thanks.
Click to expand...
Click to collapse
Thats good you got it to work but if you were just trying to root this was not the tool to use. This tool is used to unbrick your device. It will give you root access but at the moment it is for v8.1.3. So as soon as you have wifi connected it is going to upgrade again to 8.1.4 and you will lose root.

Confirmed- downgrading from 8.1.4 to 8.1.3 is possible with this tool without having to flash other partitions.

[Q] TWRP 2.5.0.0 Unresponsive

Hello,
I while ago I decided to root my HTC to get some extra stuff. I used a guide on youtube that seemed to be reasonably well made and followed everystep of the process. But before I could root it I had to unlock the bootloader and install TWRP recovery. I got the latest version and proceeded to the next step, where I encountered my problem. After flashing the recovery everything seemed to be well except that my phone wasn't actually rooted. I decided to redo some of the last steps. This is where things get a bit tricky. I have done this quite a while ago (maybe 3-4 months) and don't exactly remember the steps that I repeated but I think I've also flashed TWRP a second time, as well as some other steps. And when it came to the part where I needed to use the recovery I found out that the recovery doesn't work. I can't press anything on the screen, I can however press the lock button and lock the device but when the *slide to unlock* appears it stops working again. I was running out of time and decided to leave it for another time but time has passed and I never really got the time to tinker with it any more since university started and I'm more busy then ever. This has left me with no ability to root or even update my phone.
This brings me to today, when I restored my phone completely forgetting what has happened. It got back to Android 4.1 and I can't do anything about it.
I hope to sort this out and finally root the phone. But even getting rid of TWRP to the original recovery so I could just update my phone would be very helpfull.
Thank you very much.

aleks945 said:
Hello,
I while ago I decided to root my HTC to get some extra stuff. I used a guide on youtube that seemed to be reasonably well made and followed everystep of the process. But before I could root it I had to unlock the bootloader and install TWRP recovery. I got the latest version and proceeded to the next step, where I encountered my problem. After flashing the recovery everything seemed to be well except that my phone wasn't actually rooted. I decided to redo some of the last steps. This is where things get a bit tricky. I have done this quite a while ago (maybe 3-4 months) and don't exactly remember the steps that I repeated but I think I've also flashed TWRP a second time, as well as some other steps. And when it came to the part where I needed to use the recovery I found out that the recovery doesn't work. I can't press anything on the screen, I can however press the lock button and lock the device but when the *slide to unlock* appears it stops working again. I was running out of time and decided to leave it for another time but time has passed and I never really got the time to tinker with it any more since university started and I'm more busy then ever. This has left me with no ability to root or even update my phone.
This brings me to today, when I restored my phone completely forgetting what has happened. It got back to Android 4.1 and I can't do anything about it.
I hope to sort this out and finally root the phone. But even getting rid of TWRP to the original recovery so I could just update my phone would be very helpfull.
Thank you very much.
Click to expand...
Click to collapse
The background information is helpful but you have given us nothing to go on.
Post a fastboot getvar all except remove the imei and serialno?
What are you trying to accomplish? Return to Stock? S-OFF?

majmoz said:
The background information is helpful but you have given us nothing to go on.
Post a fastboot getvar all except remove the imei and serialno?
What are you trying to accomplish? Return to Stock? S-OFF?
Click to expand...
Click to collapse
Tell me what background information do you need and I'll get everything.
The goal is to get a working recovery, which ever one it would be I don't really care. I just want to be able to update the firmware.

reboot into the bootloader. flash the latest twrp for your device using fastboot flash recovery recoverynamehere.zip
profit

jdgreat4 said:
reboot into the bootloader. flash the latest twrp for your device using fastboot flash recovery recoverynamehere.zip
profit
Click to expand...
Click to collapse
If you could give me a more detailed guide I would toatally do that, because I'm pretty noobish when it comes to this kind of stuff.

aleks945 said:
Tell me what background information do you need and I'll get everything.
The goal is to get a working recovery, which ever one it would be I don't really care. I just want to be able to update the firmware.
Click to expand...
Click to collapse
like he said before, post the output of "fastboot getvar all" except your IMEI and SERIALNO
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
aleks945 said:
If you could give me a more detailed guide I would toatally do that, because I'm pretty noobish when it comes to this kind of stuff.
Click to expand...
Click to collapse
do you have adb and fastboot on your computer?
Do you have HTC drivers installed?

alray said:
like he said before, post the output of "fastboot getvar all" except your IMEI and SERIALNO
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
do you have adb and fastboot on your computer?
Do you have HTC drivers installed?
Click to expand...
Click to collapse
I don't know what adb is, sorry. And no I don't, I had to do everything on my friend's laptop because it didn't seem to work on my machine (W8.1 compared to his W7).
Edit. But I do have acces to it pretty much all the time.

aleks945 said:
I don't know what adb is, sorry. And no I don't, I had to do everything on my friend's laptop because it didn't seem to work on my machine (W8.1 compared to his W7).
Click to expand...
Click to collapse
yes better to use windows 7
go ahead and download adb and fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790
download and install HTC sync from here: http://www.htc.com/us/support/software/htc-sync-manager.aspx
Once installed, uninstall HTC sync but keep the drivers installed
post back when done

alray said:
yes better to use windows 7
go ahead and download adb and fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790
download and install HTC sync from here: http://www.htc.com/us/support/software/htc-sync-manager.aspx
Once installed, uninstall HTC sync but keep the drivers installed
post back when done
Click to expand...
Click to collapse
The downloads are complete, just waiting on the instalation. The computer is quite old and slow unfortunatelly.
Thank you again
EDIT. Everything is done.

aleks945 said:
The downloads are complete, just waiting on the instalation. The computer is quite old and slow unfortunatelly.
Thank you again
EDIT. Everything is done.
Click to expand...
Click to collapse
ok so connect your phone with he usb cable to the computer, reboot it in bootloader mode (hold power and vol -). in bootloader select "fastboot"
then lauch the adb command prompt and type "fastboot getvar all". post the output here but edit out the imei and serialno before.

alray said:
ok so connect your phone with he usb cable to the computer, reboot it in bootloader mode (hold power and vol -). in bootloader select "fastboot"
then lauch the adb command prompt and type "fastboot getvar all". post the output here but edit out the imei and serialno before.
Click to expand...
Click to collapse
Here it is.
{
"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"
}
Link since image seems to be really tiny.
http://i.imgur.com/9cZZRA9.jpg

aleks945 said:
Here it is.
Link since image seems to be really tiny.
http://i.imgur.com/9cZZRA9.jpg
Click to expand...
Click to collapse
you can flash twrp 2.6.3.3
download the file and save it in the same folder where you have installed minimal adb and fastboot
then open the command prompt and with the phone in bootloader/fastboot mode enter these commands:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
What do you want to achieve then? Custom rooted rom? stock rooted rom (latest version)? or you simply what to root the rom you currently have?

alray said:
you can flash twrp 2.6.3.3
download the file and save it in the same folder where you have installed minimal adb and fastboot
then open the command prompt and with the phone in bootloader/fastboot mode enter these commands:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
What do you want to achieve then? Custom rooted rom? stock rooted rom (latest version)? or you simply what to root the rom you currently have?
Click to expand...
Click to collapse
Latest stock rooted ram would be the final goal.

aleks945 said:
Latest stock rooted ram would be the final goal.
Click to expand...
Click to collapse
you can flash this rom: http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.5_odexed.zip
its the stock rom for 6.09.401.5

alray said:
you can flash this rom: http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.5_odexed.zip
its the stock rom for 6.09.401.5
Click to expand...
Click to collapse
Doesn't my phone have to be rooted to be able to instal another rom?

aleks945 said:
Doesn't my phone have to be rooted to be able to instal another rom?
Click to expand...
Click to collapse
no just flash the rom from twrp recovery then you can root it if you want.

[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 with my (bricked?) M9, please?

I've got a T-Mobile M9 with a locked bootloader and no recovery. I am unable to boot into the system and thus can't enable USB debugging. I foolishly relocked it trying to flash an RUU and now it won't boot. I have tried re-unlocking it thru fastboot but the commands are not recognized.
Please help?!?

I would recommend downloading the RUU image, renaming it "0PJAIMG.zip" and then placing it in the root directory of a microsd card and putting that into your device. Then reboot into fastmode (download mode), holding vol-down immediately after powering on. It should hopefully detect the zip image and restore the phone to factory condition.
That's if fastboot is not working. Make sure your commands are correct too. I'm sure you're fully aware but doesn't hurt to double check.
Good luck.
---------- Post added at 07:40 AM ---------- Previous post was at 07:39 AM ----------
BTW, you dont need to relock the bootloader (at least I didnt have to) to install a RUU.

minotauri said:
I would recommend downloading the RUU image, renaming it "0PJAIMG.zip" and then placing it in the root directory of a microsd card and putting that into your device. Then reboot into fastmode (download mode), holding vol-down immediately after powering on. It should hopefully detect the zip image and restore the phone to factory condition.
That's if fastboot is not working. Make sure your commands are correct too. I'm sure you're fully aware but doesn't hurt to double check.
Good luck.
---------- Post added at 07:40 AM ---------- Previous post was at 07:39 AM ----------
BTW, you dont need to relock the bootloader (at least I didnt have to) to install a RUU.
Click to expand...
Click to collapse
Thanks so much, dude! My M9 is back up and running. Looked everywhere on the Internet and didn't see that method anywhere.

I was in the same predicament. Bricked mine trying to install a custom ROM. I get the following error:
Failed: -2, 22: fail to flash via download
Failed: -2, 22: fail to flash via download
Failed: -2, 22: fail to flash via download

minotauri said:
I would recommend downloading the RUU image, renaming it "0PJAIMG.zip" and then placing it in the root directory of a microsd card and putting that into your device. Then reboot into fastmode (download mode), holding vol-down immediately after powering on. It should hopefully detect the zip image and restore the phone to factory condition.
That's if fastboot is not working. Make sure your commands are correct too. I'm sure you're fully aware but doesn't hurt to double check.
Good luck.
---------- Post added at 07:40 AM ---------- Previous post was at 07:39 AM ----------
BTW, you dont need to relock the bootloader (at least I didnt have to) to install a RUU.
Click to expand...
Click to collapse
Thanks so much! I friggin love you for being the only one in the history of the Internet to suggest this very simple solution.

deepdownnyc said:
Thanks so much! I friggin love you for being the only one in the history of the Internet to suggest this very simple solution.
Click to expand...
Click to collapse
Yeah it's actually the most common way of flashing a RUU and it's posted all over. Even a giant thread on it in the international forum. I don't think you looked very hard through "the history of the Internet."

[Superseded] Crossflash US Unlocked Pie to your Bootloader Unlocked V40

SUPERSEDED: Go Here​
Prerequisites:
V35 Engineering Bootloader flashed to your device (Stock bootloader will NOT work for this)
USB 2.0 (USB 3.x does not work well with ADB or Fastboot)
The V40 Pie Conversion Tool
Be in fastboot mode before attempting this
Patience
ADB and Fastboot DRIVERS. Platform tools are already included in the archive
Windows. The tool is not designed for Linux.
This will NOT sim unlock your phone[/CENTER]
Note: I'm not responsible for any bricks that come about from using this tool. Once you crossflash, there's NO going back unless you have backups of your partitions, or a KDZ specifically for your device. I'm going to say this again, DO NOT use USB 3.x while attempting this. You will run into errors. You won't see anything for a little bit when it gets to flashing system_a and vendor_a because it has to load those images into ram.
Download the tool: Google Drive
1. Download the archive and unzip the tool.
2. Navigate to the folder you unzipped the tool to.
3. Enter the folder and inside the folder you should find "V40PIECONVERSION.cmd". Ignore the one with the "Stock Boot" at the end. All it does is flash the stock boot image instead of the TWRP that is required to do this.
4. Execute the batch file and follow the instructions. When the batch file is done, Pie will be flashed, but it will not boot due to encryption. We're going to disable that.
5. Boot TWRP by performing a master reset. To perform a master reset: Press and hold Vol- and Power. When you see the "V40 ThinQ" logo release the power button and quickly press back down. Keep holding Vol- and Power until you see a factory reset screen. Finally, follow the prompts (yes) and you should be in TWRP.
TWRP Instructions​
Head over to the wipe menu and format data (to remove encryption).
Next, head over to mount and mount vendor. Mount ONLY vendor.
Now, open a command prompt, navigate to the folder where you extracted the tool, and open a command prompt inside the folder (Type "CMD" in File Explorer's Address Bar)
{
"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"
}
Execute the adb command:
Code:
adb pull /vendor/etc/fstab.judypn
Edit the file (fstab.judypn) in your favorite text editor and on the /data mountpoint change "forceencrypt" to "encryptable".
Save and Close the file and push the file back with the command:
Code:
adb push fstab.judypn /vendor/etc
Now that encryption is disabled, you NEED to flash back the ORIGINAL boot image that's included with the tool. In order to do that, we need to get back into fastboot.
To get back into fastboot, we need to: Make sure USB is still plugged into the phone. Press and hold VOL+ (Or vol up). Power off the phone (Via TWRP reboot menu) while still holding vol+. Keep holding VOL+ until you see download mode flash for a brief second and you should be in fastboot. The fastboot you see now isn't the V35 Engineering Bootloader. It's the stock pie bootloader. Wiping the laf_a partition allows access to fastboot on devices that are locked (Nearly all US Carriers).
Finally, run the commands:
Code:
fastboot flash boot_a boot_a.image
and
Code:
fastboot format userdata
You should run into an "encryption unsuccessful" screen. Just hit reset phone. You may have to reboot once or twice to get to the setup screen.
For those of you that want root, here's a patched Magisk boot image: Google Drive
You can flash it by running the command:
Code:
fastboot flash boot_a magisk_patched.img
Make sure you open a command prompt in the directory you downloaded the image in. If you don't have adb and fastboot in your environment path, just place it in the V40PIEConversion folder and flash it from there.

How do you get the v35 bootloader on stock Att ?

Evilmonstertruck said:
How do you get the v35 bootloader on stock Att ?
Click to expand...
Click to collapse
Contact @vbenkovskyy on Telegram. He is an awesome guy. Of course, it isn't free, but his prices are better.

Confirmed working - thanks Xsavi for an excellent guide!

Would this method work on the T-Mobile variant? Is there a fee [anywhere]?
---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------
Can someone comment on this?

avaie said:
Would this method work on the T-Mobile variant? Is there a fee [anywhere]?
---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------
Can someone comment on this?
://youtu.be/nSeqIfQeWi4
Click to expand...
Click to collapse
No T-Mobile is not supported

avaie said:
Would this method work on the T-Mobile variant? Is there a fee [anywhere]?
---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------
Can someone comment on this?
://youtu.be/nSeqIfQeWi4
Click to expand...
Click to collapse
Ainz is right. You'll end up with a brick if anything.

Confirmed working on my att variant. ? Thanks again for the great guide ?

pp342261 said:
Confirmed working on my att variant. Thanks again for the great guide
Click to expand...
Click to collapse
You are very welcome! Feel free to contact me if you run into any issues.
On the plus side, your b-slot is untouched throughout all of this, so you can use that to re-root or flash backups should something go wrong, or update. Enjoy the pie.

Xsavi said:
You are very welcome! Feel free to contact me if you run into any issues.
On the plus side, your b-slot is untouched throughout all of this, so you can use that to re-root or flash backups should something go wrong, or update. Enjoy the pie.
Click to expand...
Click to collapse
Will this work on the LG V40 International?

rmgibbs1861 said:
Will this work on the LG V40 International?
Click to expand...
Click to collapse
Yes it will.

rmgibbs1861 said:
Will this work on the LG V40 International?
Click to expand...
Click to collapse
One more question, How will further updates be done after cross flashing? Thank you!

rmgibbs1861 said:
One more question, How will further updates be done after cross flashing? Thank you!
Click to expand...
Click to collapse
By flashing System, Vendor, and boot.

Very confusing. Which variants of V40 this is going to work for?

How to get the v35 engineering bootloader on the phone the only method ive heard about is through octoplus jtag?

twoxa said:
Very confusing. Which variants of V40 this is going to work for?
Click to expand...
Click to collapse
Well it worked for all US Carriers except for T-Mobile

had my sprint v40 bootloader unlocked from octoplus and tried this cause i hate sprint SW (activation screen).it flashed everything from batch file fine but when i went to boot into twrp it booted into normal recovery with the rainbow circle "erasing" then rebooted into os but it was all korean and the android version was 8.1. wtf lol? trying it again now, yes im using "V40PIECONVERSION" not the stock one.

jass65 said:
had my sprint v40 bootloader unlocked from octoplus and tried this cause i hate sprint SW (activation screen).it flashed everything from batch file fine but when i went to boot into twrp it booted into normal recovery with the rainbow circle "erasing" then rebooted into os but it was all korean and the android version was 8.1. wtf lol? trying it again now, yes im using "V40PIECONVERSION" not the stock one.
Click to expand...
Click to collapse
Did you check to make sure you are on Slot A and not B? Becuase i remember when i had everything flashed the first time i tried to boot TWRP in Slot A and somehow ended up switching to Slot B

Ainz_Ooal_Gown said:
Did you check to make sure you are on Slot A and not B? Becuase i remember when i had everything flashed the first time i tried to boot TWRP in Slot A and somehow ended up switching to Slot B
Click to expand...
Click to collapse
thats what it ended up being. xSavi helped me out :good:

Hi guys,
I have a Sprint V40 bought off of Taobao that was rooted, sim unlocked, and crossflashed to US Cellular 11d but after I installed Pix3lify trying to get gestures on 8.1 I lost root. I don't seem to be able to get into fastboot, either with Vol- + cable or via adb, but I have an unlocked bootloader and I can get to download mode. Factory reset just reboots. Any tips as to how can I get root back, or upgrade to Pie? Can anybody please explain how to switch from slot a to slot b and vice versa?
Jeff