KFHD System.img Recovery Tool - 8.9" Kindle Fire HD Android Development

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.

Related

[Fastboot] Droid Razr M Xt907 Ice Cream Sandwich

DROID RAZR M XT907 Ice Cream Sandwich software update availability​
The following table is for reference only.
Country|Carrier Name|Android|System version
US|Verizon|4.0.4|Blur_Version.77.111.10.XT907.Verizon.en.US
BUILT PROPERTIES
build.id=7.7.1Q-144_SMQ_S136-10
build.version.release=4.0.4
build.date=Mon Aug 27 06:18:07 CDT 2012
Blur_Version.77.111.10.XT907.Verizon.en.US
Click to expand...
Click to collapse
Click to expand...
Click to collapse
1. 7.7.1Q-144_SMQ_S136-10 - Verizon
Source: http://www.droidevelopers.com/showt...e-Cream-Sandwich-software-update-amp-download
mine tried to update today, it wouldn't go through. Also when I try to reboot into recovery I'm having issues there, just doesn't want to do it... anyone know why?
Are you pressing all physical buttons then scroll with v down select with v up then press both v buttons at red android screen then select file from SD and apply
https://www.youtube.com/watch?v=6efI1iGAgsU&feature=youtube_gdata_player
Video link to most of process from my YouTube
Sent from my XT907 using xda app-developers app
I missed the step about both v keys at the M, I'm getting it to work now, except I can't find the file. I know its there, can go look at it in the file explorer, but can't find it in recovery.
Did you move it to your SD card it goes to your internal first not external which is where it has to be also did you rename to update.zip?
Sent from my XT907 using xda app-developers app
I apologize if this is something obvious, but when I try and run this through rsdlite (5.7 and 5.9) on my retail M running the JB leak, it immediately fails and says "Failed flashing process. Unknown fastboot command. (getvar)".
{
"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"
}
Got it, didn't know it wasn't downloaded to my external memory. Its all good now, thanks!
Got it to work by removing the getvar line in the xml (per mattlgroff, no way I would've tried that myself) - works perfectly from the JB leak, thanks again for this!
Just to be clear, is the the stock ROM that came with the RAZR M? That way people could try out the JB leak, and then use this to revert back. Since there isn't a way to install CWM and do a backup.
FAUguy said:
Just to be clear, is the the stock ROM that came with the RAZR M? That way people could try out the JB leak, and then use this to revert back. Since there isn't a way to install CWM and do a backup.
Click to expand...
Click to collapse
Correct, on the current leak anyway. Obviously if you have to do this your data will be wiped as well.
jntdroid said:
Correct, on the current leak anyway. Obviously if you have to do this your data will be wiped as well.
Click to expand...
Click to collapse
But the only way you could get it to work was by removing the getvar line in the XML?
FAUguy said:
But the only way you could get it to work was by removing the getvar line in the XML?
Click to expand...
Click to collapse
That's the only way mine would work - rsdlite wouldn't go past that.
Use RSD Lite 6.1.4
When using RSD Light, does the phone have to be in normal "power on" mode, or in a special "download" mode for RSD to install the files?
FAUguy said:
When using RSD Light, does the phone have to be in normal "power on" mode, or in a special "download" mode for RSD to install the files?
Click to expand...
Click to collapse
AP Fastboot - from powered off, hold down volume-up AND volume-down, then while holding those, press and hold the power button until you see a menu pop-up that's simply white text on a black background. Once that comes up, use volume-down to move down to AP Fastboot, and volume-up to select it. Then plug it into your computer, fire up rsdlite (6.1.4! ), open the file linked in the OP, and go!
Sent from my XT907 using Tapatalk 2
Ok, thanks.
I've posted the files and instruction here:
http://www.phonearena.com/news/How-to-restore-your-Motorola-DROID-RAZR-M-back-to-stock_id35580
If anything needs editing, let me know.
FAUguy said:
Ok, thanks.
I've posted the files and instruction here:
http://www.phonearena.com/news/How-to-restore-your-Motorola-DROID-RAZR-M-back-to-stock_id35580
If anything needs editing, let me know.
Click to expand...
Click to collapse
Credits Firmware Team?
Enviado desde mi HTC Sensation XE with Beats Audio Z715e usando Tapatalk 2
help im stuck
ok so i messed with the build.prop and cant get the original one in through adb, i tried flashingjust system img thru fastboot but the file is too big just error after error with cmd prompt...
so i downloaded stock firmware per phonearena link, and i have rsdlite 6.1.4 installed as well as all the latest drivers, it fails on step 1 "gpt_main0.bin" so i removed that line from xml and tried again, it got further but failed at fsg.mbn
i dont know what to do, i figure if all i need is a good build.prop i should have rsd flash just the system.img but that doesnt work either...
i don't know what to do? any suggestions, or ideas?
---------- Post added at 08:11 PM ---------- Previous post was at 07:30 PM ----------
ok i solved it, nevermind
tadgerloks said:
ok so i messed with the build.prop and cant get the original one in through adb, i tried flashingjust system img thru fastboot but the file is too big just error after error with cmd prompt...
so i downloaded stock firmware per phonearena link, and i have rsdlite 6.1.4 installed as well as all the latest drivers, it fails on step 1 "gpt_main0.bin" so i removed that line from xml and tried again, it got further but failed at fsg.mbn
i dont know what to do, i figure if all i need is a good build.prop i should have rsd flash just the system.img but that doesnt work either...
i don't know what to do? any suggestions, or ideas?
---------- Post added at 08:11 PM ---------- Previous post was at 07:30 PM ----------
ok i solved it, nevermind
Click to expand...
Click to collapse
PLEASE post what you did to fix this issue as it may creep up again for someone else. These posts I run into every so often on google asking a problem and then all I see is "fixed it" no solutions posted. =) thanks!
I deleted the bad build.prop from the system, and The recovery-from-boot.p file or something similar in name, they're the only 2 files in /system that aren't folders, after I rebooted into AP Fast boot and through cmd.exe on win7 and typed in "fastboot -w"
Then "fastboot reboot"
Back too fastboot mode, start RSDLite 6.1.4 w/admin privileges, extracted firmware manually, edited XML too remove any line wit "var" or "OEM" in them, as well as the line with "gpt-main0.bin" I pointed RSD too the XML and it flashed flawlessly
Now I'm back on JB Leak and rooted

"beg for a system image" thread

Hello!
I'd appreciate it if anybody could make a backup image of his KFHD and post it here. Pls make a backup after 2nd part of rooting, as it said http://forum.xda-developers.com/showthread.php?t=1930656
Thx in advance!
Yes please .... you will help a lot of depressed users
This evening I'm going to set everything back to stock(except for su binary) on my system partition and will post it here when I finish. You will need a factory cable to enable fastboot
Sent from my SCH-I500 using xda app-developers app
In case you have tried downloading these files and were not able to, I have changed the links below(the others were disabled by dropbox for too much traffic). You must now unzip these files before use!!
Here are copies of backups I created from KFHD(Don't think this will work with KF2).
WARNING!!!- use at your own risk, I am not responsible for anything you do to your device. If you do not know what these .img files are for you should not be using them. See- http://forum.xda-developers.com/showthread.php?t=1930656 for directions on restoring with fastboot
System.img-(with su binary, vending.apk, and latest versions of go-launcher ex and apex launcher. Note: you will still need superuser.apk to obtain root and googleservicesframework.apk to access play store) These new links have zipped files, you MUST unzip before using :
https://docs.google.com/open?id=0B4lZEJI5lYeMR2k3NW1QRUR3dzg
System.img-(with su binary only. Note: same as above plus vending.apk), Also this file is named [system(2)] you may want to rename to [system] These new links have zipped files, you MUST unzip before using :
https://docs.google.com/open?id=0B4lZEJI5lYeMcldVWUwzd3BqRUE
I just noticed on Play that go-launcher ex has been updated so the above image does not have latest go-launcher ex, but will still work, just update in Play store
I messed up my kindle and now i have to restore a backup, do I have to have one of these cables that is mentioned? because in my country there is no kfhd much less these cables? please help this kfhd of mine has been giving me hard time since I got it.
You are the hero. Thank you.
hamidwt said:
I messed up my kindle and now i have to restore a backup, do I have to have one of these cables that is mentioned? because in my country there is no kfhd much less these cables? please help this kfhd of mine has been giving me hard time since I got it.
Click to expand...
Click to collapse
Yes you must have a factory cable to enable fastboot(unless you still have the ability to download and open an app with root access). Check out this link- http://forum.xda-developers.com/showpost.php?p=20380015&postcount=9. They say they ship international and pricing is extremely cheap with what looks to be good quality. Personally I made mine, It is pretty simple if you have a spare micro usb cable, a 1k resistor, and a soldering iron. Just google factory cable kindle fire. Be very careful it might be simple but there is the potential to ruin your device and fry the usb board on your computer(at the minimum) if not done correctly. I do not say this lightly be absolutely sure of everything you are doing before attempting.
Works like a dream
Thanks for the image! I used it revive my dead kindle and it works!
Only thing right now is that my Date and time settings seems to have greyed out. I will need to figure this out as the date and time is wrong.
Also, i didn't use a factory cable - I had an issue with a blank screen appearing after the words Kindle Fire upon start up. So I got into fastboot by using the ADB: Fastboot reboot-bootloader
Cheers1
onemeila said:
Sorry this took so long just wanted to make sure I had the files straight and they worked
Here are copies of backups I created from KFHD(Don't think this will work with KF2).
WARNING!!!- use at your own risk, I am not responsible for anything you do to your device. If you do not know what these .img files are for you should not be using them. See- http://forum.xda-developers.com/showthread.php?t=1930656 for directions on restoring with fastboot
System.img-(with su binary, vending.apk, and latest versions of go-launcher ex and apex launcher. Note: you will still need superuser.apk to obtain root and googleservicesframework.apk to access play store) :
https://www.dropbox.com/s/y90vk1igk0ml5qv/system.img
System.img-(with su binary only. Note: same as above plus vending.apk), Also this file is named [system(2)] you may want to rename to [system] :
https://www.dropbox.com/s/t5rarzakk9p1to5/system (2).img
I just noticed on Play that go-launcher ex has been updated so the above image does not have latest go-launcher ex, but will still work, just update in Play store
Click to expand...
Click to collapse
onemeila said:
Yes you must have a factory cable to enable fastboot(unless you still have the ability to download and open an app with root access). Check out this link- http://forum.xda-developers.com/showpost.php?p=20380015&postcount=9. They say they ship international and pricing is extremely cheap with what looks to be good quality. Personally I made mine, It is pretty simple if you have a spare micro usb cable, a 1k resistor, and a soldering iron. Just google factory cable kindle fire. Be very careful it might be simple but there is the potential to ruin your device and fry the usb board on your computer(at the minimum) if not done correctly. I do not say this lightly be absolutely sure of everything you are doing before attempting.
Click to expand...
Click to collapse
thank you for your help
my kindle is working , I download and install easily but I have problem with Google play and also logging into Imo and I'm+ , I did some factory reset but still nothing ,that got me thinking there must be something wrong with system. so considering what I said , do I still need this cable?
hamidwt said:
thank you for your help
my kindle is working , I download and install easily but I have problem with Google play and also logging into Imo and I'm+ , I did some factory reset but still nothing ,that got me thinking there must be something wrong with system. so considering what I said , do I still need this cable?
Click to expand...
Click to collapse
No you wouldn't need a factory cable but if the device is still working then the best thing would be to figure what mods you made to the system and reverse them before flashing an image in fastboot. If you cant figure that out and need to flash the system.img, the post above said they were able to get into fastboot through cmd window(though I think because the device was frozen, I was not able to do this with my working device, then again i could be doing something wrong). I know that if you use the app- Rom Toolbox Lite and under the rebooter section there is an option to reboot bootloader, that will boot into fastboot. Then you can use a regular cable.
---------- Post added at 11:37 AM ---------- Previous post was at 11:31 AM ----------
Arithon said:
Thanks for the image! I used it revive my dead kindle and it works!
Only thing right now is that my Date and time settings seems to have greyed out. I will need to figure this out as the date and time is wrong.
Also, i didn't use a factory cable - I had an issue with a blank screen appearing after the words Kindle Fire upon start up. So I got into fastboot by using the ADB: Fastboot reboot-bootloader
Cheers1
Click to expand...
Click to collapse
Glad it helped. With the date and time mine are grayed out as well(think its like that from factory, don't remember noticing since date and time were changed during initial setup), you just need to select the right time zone and it automatically changes to proper time.
Also are you still able to get into fastboot via cmd prompt now that your device is working properly? If so what commands did you use?
cmd
onemeila said:
No you wouldn't need a factory cable but if the device is still working then the best thing would be to figure what mods you made to the system and reverse them before flashing an image in fastboot. If you cant figure that out and need to flash the system.img, the post above said they were able to get into fastboot through cmd window(though I think because the device was frozen, I was not able to do this with my working device, then again i could be doing something wrong). I know that if you use the app- Rom Toolbox Lite and under the rebooter section there is an option to reboot bootloader, that will boot into fastboot. Then you can use a regular cable.
---------- Post added at 11:37 AM ---------- Previous post was at 11:31 AM ----------
Glad it helped. With the date and time mine are grayed out as well(think its like that from factory, don't remember noticing since date and time were changed during initial setup), you just need to select the right time zone and it automatically changes to proper time.
Also are you still able to get into fastboot via cmd prompt now that your device is working properly? If so what commands did you use?
Click to expand...
Click to collapse
fastboot reboot-bootloader
---------- Post added at 02:23 AM ---------- Previous post was at 01:58 AM ----------
Arithon said:
fastboot reboot-bootloader
Click to expand...
Click to collapse
sorry it was "adb reboot-bootloader"
Arithon said:
fastboot reboot-bootloader
---------- Post added at 02:23 AM ---------- Previous post was at 01:58 AM ----------
sorry it was "adb reboot-bootloader"
Click to expand...
Click to collapse
Are you still able to do this with the device working? I couldn't.
adb
onemeila said:
Are you still able to do this with the device working? I couldn't.
Click to expand...
Click to collapse
Yes - but i think you must turn it (ADB) on in 'Settings'....
Another Beg!
I am adding a BEG!!!
Anyone have a system.img file for the 10.2.1 Kindle Fire 2 device?
Please..
I did a backup when I was on 10.1.3 and it wont let me restore that system..img file!!!!!!!
I get this error!
fastboot -i 0x1949 flash system system.img
sending 'system' (907264 KB)...
FAILED (remote: data too large)
finished. total time: 0.188s
[edit:] nevermind
Thanks the image files has saved my Kindle Fire HD!
I know this is a system.img but I really need a boot.img for the fire hd 7" can someone please post one it would be greatly appreciated thanks
dark_samus said:
I know this is a system.img but I really need a boot.img for the fire hd 7" can someone please post one it would be greatly appreciated thanks
Click to expand...
Click to collapse
Look here:
http://forum.xda-developers.com/showthread.php?t=1951254

[Q] Updating - need help! :(

I have a Kindle Fire HD 7" that was previously rooted. While it was rooted, I used KindleFree to disable OTA updates. Now, I deleted the su binary, uninstalled su, resetted to factory settings, and I can't update.
I downloaded the update and transferred it to "kindleupdates" in storage,
I went to settings > device > about and clicked update.
A brief screen showed up with "Installing OTA update", then it disappeared. The Update button became grey. When I went to the file manager I saw the update was deleted and a file called ".nomedia" was created. I need to update the software to 7.4.8. PLEASE HELP!
Purpose: I want to root, then install fire flash (requires 7.4.8), install TWRP, then install CM11 Unofficial.
Thanks!
EDIT: I saw this on the amazon website.
Update appears to start, but doesn't update the device
Issue: After selecting the Update Your Kindle button, the software update doesn't appear to work.
Cause: The update file may have been renamed, or you have duplicate files on your computer.
Solution: Delete the update file(s) on your computer and Kindle Fire, and then repeat the software update process. Verify that the firewall on your computer isn't blocking downloads from the Internet.
I have no idea what that means..
androidnewbie123 said:
I have a Kindle Fire HD 7" that was previously rooted. While it was rooted, I used KindleFree to disable OTA updates. Now, I deleted the su binary, uninstalled su, resetted to factory settings, and I can't update.
I downloaded the update and transferred it to "kindleupdates" in storage,
I went to settings > device > about and clicked update.
A brief screen showed up with "Installing OTA update", then it disappeared. The Update button became grey. When I went to the file manager I saw the update was deleted and a file called ".nomedia" was created. I need to update the software to 7.4.8. PLEASE HELP!
Purpose: I want to root, then install fire flash (requires 7.4.8), install TWRP, then install CM11 Unofficial.
Thanks!
EDIT: I saw this on the amazon website.
Update appears to start, but doesn't update the device
Issue: After selecting the Update Your Kindle button, the software update doesn't appear to work.
Cause: The update file may have been renamed, or you have duplicate files on your computer.
Solution: Delete the update file(s) on your computer and Kindle Fire, and then repeat the software update process. Verify that the firewall on your computer isn't blocking downloads from the Internet.
I have no idea what that means..
Click to expand...
Click to collapse
Delete the update files from the computer. Pretty straightforward. And btw im 99% sure you don't need 7.4.8 to use FireFlash. Just use Seokhuns guide to install it, keep the rom you want to flash on the KFHD's Sd card before hand, then install the rom, after using fireflash to get twrp plus second bootloader.
miztah1999z said:
Delete the update files from the computer. Pretty straightforward. And btw im 99% sure you don't need 7.4.8 to use FireFlash. Just use Seokhuns guide to install it, keep the rom you want to flash on the KFHD's Sd card before hand, then install the rom, after using fireflash to get twrp plus second bootloader.
Click to expand...
Click to collapse
Thanks, but fire flash DOES NOT work. I open it, it asks for root permissions, I grant it. Then a box pops up saying "fire flash has stopped." And I tried the mentioned tutorial but fire flash doesn't work. Fire flash crashes on startup.. allowed superuser permissions and reinstalled many times but I get a box that says "fire flash has stopped." I tried factory resetting, unroot + reroot, but no avail. I really want fire flash but it crashes on startup!
androidnewbie123 said:
Thanks, but fire flash DOES NOT work. I open it, it asks for root permissions, I grant it. Then a box pops up saying "fire flash has stopped." And I tried the mentioned tutorial but fire flash doesn't work. Fire flash crashes on startup.. allowed superuser permissions and reinstalled many times but I get a box that says "fire flash has stopped." I tried factory resetting, unroot + reroot, but no avail. I really want fire flash but it crashes on startup!
Click to expand...
Click to collapse
Try this instead of fire flash it does practically the same thing. Keep the rom you want to flash on the sd card before hand.
http://forum.xda-developers.com/showthread.php?t=2685414
miztah1999z said:
Try this instead of fire flash it does practically the same thing. Keep the rom you want to flash on the sd card before hand.
http://forum.xda-developers.com/showthread.php?t=2685414
Click to expand...
Click to collapse
Thanks, and again I have some questions..
Does this run on 7.2.4 without screwing things up? The thread mentioned downgrading to 7.2.3 bootloader.. this leaves me utterly confused.
How do I configure the Android SDK for fastboot? I have no idea how to work with that..
What if the device kicks into fastboot but I can't exit fastboot because the drivers aren't working? Then what do I do?
With flasher is it necessary to use fastboot in the process? Will the program kick the device into fastboot?
Is there any risk of the kindle not booting?
Thanks a lot!
BTW may I ask you a favor? If you wouldn't mind can you mind walking me through the process through some chat service, teamviewer, etc. It's fine if you can't too, just asking..
Thanks again
androidnewbie123 said:
Thanks, and again I have some questions..
Does this run on 7.2.4 without screwing things up? The thread mentioned downgrading to 7.2.3 bootloader.. this leaves me utterly confused.
How do I configure the Android SDK for fastboot? I have no idea how to work with that..
What if the device kicks into fastboot but I can't exit fastboot because the drivers aren't working? Then what do I do?
With flasher is it necessary to use fastboot in the process? Will the program kick the device into fastboot?
Is there any risk of the kindle not booting?
Thanks a lot!
BTW may I ask you a favor? If you wouldn't mind can you mind walking me through the process through some chat service, teamviewer, etc. It's fine if you can't too, just asking..
Thanks again
Click to expand...
Click to collapse
EDIT: If you have 7.2.4 you probably won't need to install the 7.2.3 bootloader due to the bootloader only actually changing when the 7.3.x updates came out. Proceed reading
EDIT: If you REALLY need help with this pm me and we can skype.
I'll write a step by step walk through for you. First I will answer your questions.
The program will downgrade by itself.
I am 99.9 percent sure this will work on 7.2.4, because i did it on 7.4.8.
If you install SDK properly Fastboot drivers will work. Drivers will work if SDK is installed properly.
You will need fastboot, and the program will do it by itself as long as drivers are installed properly.
As for risks... There is always a risk. Follow these guidelines when doing this stuff:
Follow Steps Closely
Don't rush it
Don't take risks
Last thing to keep in mind is to keep the rom you want on the device beforehand.
Lets get started.
Step 1: Install the Android SDK if you already haven't. (To check if you have open Command Prompt and type in adb--you should see a list of commands. If you don't see it, google "Install android sdk".)
Step 2: It will automatically install the 7.2.3 bootloader to prevent red screens, so open the flasher tool and backup(optional).
Step 3: Press Step 3. First it will install the 7.2.3 bootloader if you don't already have it. Then it will install the stack override. Then it will disable amazon updates.
PAY ATTENTION NOW FOR THE HARD PART
Step 4: Disconnect your KF. Then turn it off. Press enter, and then plug in your powered off Kindle.
Then it should be done!
miztah1999z said:
EDIT: If you have 7.2.4 you probably won't need to install the 7.2.3 bootloader due to the bootloader only actually changing when the 7.3.x updates came out. Proceed reading
EDIT: If you REALLY need help with this pm me and we can skype.
I'll write a step by step walk through for you. First I will answer your questions.
The program will downgrade by itself.
I am 99.9 percent sure this will work on 7.2.4, because i did it on 7.4.8.
If you install SDK properly Fastboot drivers will work. Drivers will work if SDK is installed properly.
You will need fastboot, and the program will do it by itself as long as drivers are installed properly.
As for risks... There is always a risk. Follow these guidelines when doing this stuff:
Follow Steps Closely
Don't rush it
Don't take risks
Last thing to keep in mind is to keep the rom you want on the device beforehand.
Lets get started.
Step 1: Install the Android SDK if you already haven't. (To check if you have open Command Prompt and type in adb--you should see a list of commands. If you don't see it, google "Install android sdk".)
Step 2: It will automatically install the 7.2.3 bootloader to prevent red screens, so open the flasher tool and backup(optional).
Step 3: Press Step 3. First it will install the 7.2.3 bootloader if you don't already have it. Then it will install the stack override. Then it will disable amazon updates.
PAY ATTENTION NOW FOR THE HARD PART
Step 4: Disconnect your KF. Then turn it off. Press enter, and then plug in your powered off Kindle.
Then it should be done!
Click to expand...
Click to collapse
Thanks a lot! I'll get started today.. though I am kinda confused.
I'm using this tutorial, and is it safe to use Step 13 to 20? Are those necessary? (Tutorial: http://www.theandroidroot.com/how-to-set-up-adb-and-fastboot-with-android-sdk-on-windows/ ) And OTA updater crashes, fire flash won't install too. Does this mean my system is corrupted and anything may happen? (Before I factory reset my KFHD7 was tweaked a LOT and remains may be left) Thanks! BTW my Skype id is androidnewbie123 .
EDIT: Nothing turns up when I type adb in cmd - I have installed the SDK too.
EDIT 2: ADB works, just had to run cmd from adb directory
EDIT 3: What happens if adb doesn't work for some reason in the middle of the tutorial?
Sorry for the immensely large number of questions, just too scared to start without full knowledge of what I'm doing...
And I wanna get started soon..
androidnewbie123 said:
Thanks a lot! I'll get started today.. though I am kinda confused.
I'm using this tutorial, and is it safe to use Step 13 to 20? Are those necessary? (Tutorial: http://www.theandroidroot.com/how-to-set-up-adb-and-fastboot-with-android-sdk-on-windows/ ) And OTA updater crashes, fire flash won't install too. Does this mean my system is corrupted and anything may happen? (Before I factory reset my KFHD7 was tweaked a LOT and remains may be left) Thanks! BTW my Skype id is androidnewbie123 .
EDIT: Nothing turns up when I type adb in cmd - I have installed the SDK too.
EDIT 2: ADB works, just had to run cmd from adb directory
EDIT 3: What happens if adb doesn't work for some reason in the middle of the tutorial?
Click to expand...
Click to collapse
adb wont stop working, adb doesnt work on regular cmd because u didnt set paths.
go to computer, right click and click propteries go to advanced system setting. then go to environ variables, then go to System Varuabels then scroll down to "Path". once u are tehre, click edit and at the end of the line, seperated by semicolon from other pahts, type in where adb is found. for me its " C:\SDK\Platform tools\" stop when u are at the folder its at.
miztah1999z said:
adb wont stop working, adb doesnt work on regular cmd because u didnt set paths.
go to computer, right click and click propteries go to advanced system setting. then go to environ variables, then go to System Varuabels then scroll down to "Path". once u are tehre, click edit and at the end of the line, seperated by semicolon from other pahts, type in where adb is found. for me its " C:\SDK\Platform tools\" stop when u are at the folder its at.
Click to expand...
Click to collapse
Thanks!
Do I need to use steps 13 to 20 on the tutorial I mentioned? And is it fine if you can help me throughout the process using skype? Thanks again
I am so nervous right now
Bump fo' last minute advice
Just do it following my instruction s
Sent from my Amazon Tate using xda app-developers app
Alright, just hope this won't fail..
Sent from my MB865 using XDA Premium HD app
miztah1999z said:
Step 3: Press Step 3. First it will install the 7.2.3 bootloader if you don't already have it. Then it will install the stack override. Then it will disable amazon updates.
Click to expand...
Click to collapse
Well,small correction. My tool installs the stack override and disables the amazon updates. THEN while in fastboot,it will install the 7.2.3 bootloader and other files.
miztah1999z said:
Just do it following my instruction s
Sent from my Amazon Tate using xda app-developers app
Click to expand...
Click to collapse
Do I need to set any ADB variable path/configure anything on my PC before I start? I read a lot of other threads and I'm confusing myself
I was thinking of finishing the scary stuff today (installing the bootmenu and recovery) so yeah.
SafinWasi said:
Well,small correction. My tool installs the stack override and disables the amazon updates. THEN while in fastboot,it will install the 7.2.3 bootloader and other files.
Click to expand...
Click to collapse
BTW I appreciate all the efforts for this tool from you
Does it work on a Kindle 7.2.4 where OTA doesn't work? Thanks.
androidnewbie123 said:
BTW I appreciate all the efforts for this tool from you
Does it work on a Kindle 7.2.4 where OTA doesn't work? Thanks.
Click to expand...
Click to collapse
No problem man. Just trying to help out people like you (and me)
And about your question:it should. Although the Flasher was made for software OS 7.4.6,it should work on any OS version. But it also might give you a bootloop. So be sure to keep a ROM zip and GApps on the sdcard so that you can just install the ROM in recovery.
SafinWasi said:
No problem man. Just trying to help out people like you (and me)
And about your question:it should. Although the Flasher was made for software OS 7.4.6,it should work on any OS version. But it also might give you a bootloop. So be sure to keep a ROM zip and GApps on the sdcard so that you can just install the ROM in recovery.
Click to expand...
Click to collapse
Alright, thanks. And one last thing.. as I posted above.. do I need to set any adb variable path or computer pre-requisites before flashing? Ty in advance I'm kinda new to this stuff..
androidnewbie123 said:
Alright, thanks. And one last thing.. as I posted above.. do I need to set any adb variable path or computer pre-requisites before flashing? Ty in advance I'm kinda new to this stuff..
Click to expand...
Click to collapse
Well,you do need the ADB drivers installed. If ADB cannot recognize your Kindle because of driver issues,then my tool can't do anything at all. Other than that,you don't need to do anything.
SafinWasi said:
Well,you do need the ADB drivers installed. If ADB cannot recognize your Kindle because of driver issues,then my tool can't do anything at all. Other than that,you don't need to do anything.
Click to expand...
Click to collapse
Thanks for the quick help
Now I can finally start after months of waiting xD
I just hope I don't get my Kindle Fire bricked..
Thanks again for this tool which simplifies the steps!
EDIT: Can't get into fastboot using the tool no matter what
I installed stack override and I got a message somewhere saying "failed no such directory found" ending with some "installation.sh" or something. I can't verify the device either. I only have a normal USB cable. When I plug that in my KFHD just turns on and doesn't go into fastboot. Please help! I only managed to backup the system and stuff. Only the stack override is installed now (I think)
Help! Ty
EDIT #2: Stuck on <waiting for device> and my device just boots normally... when connected to PC and powered off at that step.
I used http://forum.xda-developers.com/showthread.php?t=2588979 to install adb and fastboot drivers plus google phone drivers. I also have the SDK..
{
"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"
}

[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:

CWM does not detect my device

hello, I'm kinda desperate on installing recoveries on my phone
I'm following this guide over here
USB debugging mode is turned on, but it is not detected on the shell/command window
when I checked my device manager, my device driver is not found, I tried installing flash tool drivers, but I dunno where to search for these drivers, so I followed the way in this thread
and I found 4 drivers in the list:
- Android ADB interface
- Sony ADB interface
- Sony Composite ADB interface
- Sony Fastboot Interface
tried all the ADB interface but still give same result so I uninstalled the driver back to the way it was
Please help me as I'm really newbie at this and I wanna try Stryflex ROM, thanks
Note:
1. I already unlocked my bootloader, but someone in here said to unlock bootloader first so I assume that it will end the same way as LB
2. The error I received from the command window is "device not found"
3. Phone version C3502
4. currently still using stock ROM with 12.1.A.1.207 firmware, rooted with towelroot
5. I unlock the bootloader using the step on sony site
Bump, pls help anyone?
Sent from my C5302 using Tapatalk
Please explain to me what you are actually wanting to do?
TechnoSparks said:
Please explain to me what you are actually wanting to do?
Click to expand...
Click to collapse
I'm trying to install recoveries to my device, but the CWM tools on the link I gave above didn't detect my device
daryula said:
I'm trying to install recoveries to my device, but the CWM tools on the link I gave above didn't detect my device
Click to expand...
Click to collapse
I strongly advise for you to START with another way and also use TWRP as a default recovery. CWM (and inherently PhilZ) are very old unsupported recoveries.
If you insist, you might want to install DoomLord's driver pack and try again: http://forum.xda-developers.com/showthread.php?t=2635830
If you wish to follow my method, please follow this link: http://forum.xda-developers.com/showpost.php?p=64449411&postcount=4
TechnoSparks said:
I strongly advise for you to START with another way and also use TWRP as a default recovery. CWM (and inherently PhilZ) are very old unsupported recoveries.
If you insist, you might want to install DoomLord's driver pack and try again: http://forum.xda-developers.com/showthread.php?t=2635830
If you wish to follow my method, please follow this link: http://forum.xda-developers.com/showpost.php?p=64449411&postcount=4
Click to expand...
Click to collapse
Ok i will try your method, thanks
Sent from my C5302 using Tapatalk
daryula said:
Ok i will try your method, thanks
Sent from my C5302 using Tapatalk
Click to expand...
Click to collapse
Do report your findings
Also how did you post from tapatalk on C5302? Is it another SP?
TechnoSparks said:
Do report your findings
Also how did you post from tapatalk on C5302? Is it another SP?
Click to expand...
Click to collapse
Nope, this is my only device
Like i said, i cant install recoveries like what the tutorial above said because it's not detected
Hence i cannot proceed to other thing because of the fear of me failing to install cusrom
If i can install recoveries, i can backup (CMIIW) and it's at least reassuring me to do other things, this is my first time doing this so knowing nothing makes me confused and a bit terrified of I fail
Sent from my C5302 using Tapatalk
daryula said:
Nope, this is my only device
Like i said, i cant install recoveries like what the tutorial above said because it's not detected
Hence i cannot proceed to other thing because of the fear of me failing to install cusrom
If i can install recoveries, i can backup (CMIIW) and it's at least reassuring me to do other things, this is my first time doing this so knowing nothing makes me confused and a bit terrified of I fail
Sent from my C5302 using Tapatalk
Click to expand...
Click to collapse
So you're on stock ROM, i believe?
TechnoSparks said:
So you're on stock ROM, i believe?
Click to expand...
Click to collapse
yes I'm on stock rom, but I have root access and unlocked bootloader
daryula said:
yes I'm on stock rom, but I have root access and unlocked bootloader
Click to expand...
Click to collapse
Alright then my link before would definitely help you out
TechnoSparks said:
Alright then my link before would definitely help you out
Click to expand...
Click to collapse
the fastboot tools stated is the same fastboot tool used for unlocking the bootloader, am I right?
also do I need to put the img file on the same folder as the fastboot tools?
daryula said:
the fastboot tools stated is the same fastboot tool used for unlocking the bootloader, am I right?
also do I need to put the img file on the same folder as the fastboot tools?
Click to expand...
Click to collapse
yes, and yes.
You can also point to the absolute path of the img file, but that would be complicated so copying would be easier. (welcome to the world of consoles (not the game consoles (command prompt)))
TechnoSparks said:
yes, and yes.
You can also point to the absolute path of the img file, but that would be complicated so copying would be easier. (welcome to the world of consoles (not the game consoles (command prompt)))
Click to expand...
Click to collapse
I got this notification
{
"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"
}
should be an okay I guess?
thanks for the help
@TechnoSparks I think I got another problem now
I can't seem to reboot into system after I do full backup, it just shows black screen
what should I do?
I haven't done anything aside from doing backup
daryula said:
@TechnoSparks I think I got another problem now
I can't seem to reboot into system after I do full backup, it just shows black screen
what should I do?
I haven't done anything aside from doing backup
Click to expand...
Click to collapse
Can you explain everything, as if you're telling a story, in a chronological order? Remember, explain verbosely!
I need to sleep right now, hopefully i would able to reply to you in the next morning when i got enough information
Also, in the "hide" section of your previous post, there is nothing from inside..
TechnoSparks said:
Can you explain everything, as if you're telling a story, in a chronological order? Remember, explain verbosely!
I need to sleep right now, hopefully i would able to reply to you in the next morning when i got enough information
Also, in the "hide" section of your previous post, there is nothing from inside..
Click to expand...
Click to collapse
firstly I do install TWRP according to your guide over there using fastboot tools
the one with this command
Code:
fastboot flash boot twrp.img
then it shows message like this
http://www.iforce.co.nz/View.aspx?i=ivkcgknl.fyl.png
I then restart my device normally and it boots into recovery mode, in which then I make backup by selecting all the option to my external card, and proceed to reboot after it's done
it returns me to TWRP once again, and I reboot using "reboot system", it shows sony logo and then black screen for a few minutes, and I got sent back to TWRP once more, I've tried "reboot bootloader" menu too and the same result, I've repeat this for a lot of times and still same result pops out
sorry to bother you this late night and have a nice sleep
daryula said:
firstly I do install TWRP according to your guide over there using fastboot tools
the one with this command
Code:
fastboot flash boot twrp.img
then it shows message like this
http://www.iforce.co.nz/View.aspx?i=ivkcgknl.fyl.png
I then restart my device normally and it boots into recovery mode, in which then I make backup by selecting all the option to my external card, and proceed to reboot after it's done
it returns me to TWRP once again, and I reboot using "reboot system", it shows sony logo and then black screen for a few minutes, and I got sent back to TWRP once more, I've tried "reboot bootloader" menu too and the same result, I've repeat this for a lot of times and still same result pops out
sorry to bother you this late night and have a nice sleep
Click to expand...
Click to collapse
Oh i thought you were ready for flashing Stryflex!
Anyway the reason why it booted to the TWRP repeatedly is because of the reason that you flashed a recovery into the boot partition. Please re-read carefully the page that I linked you to
Anyway to boot back to your stock ROM, get yourself a "boot" stock component from this page: http://forum.xda-developers.com/showpost.php?p=62447987&postcount=3
Flash it in the TWRP
sorry for the trouble.
TechnoSparks said:
Oh i thought you were ready for flashing Stryflex!
Anyway the reason why it booted to the TWRP repeatedly is because of the reason that you flashed a recovery into the boot partition. Please re-read carefully the page that I linked you to
Anyway to boot back to your stock ROM, get yourself a "boot" stock component from this page: http://forum.xda-developers.com/showpost.php?p=62447987&postcount=3
Flash it in the TWRP
sorry for the trouble.
Click to expand...
Click to collapse
I forgot to put the rom to my SD card and I don't have card reader
what to do with the files?
oh nvm, I somehow managed to learn how to move my files via adb command
thanks again for your help

Categories

Resources