Database Develop

[Q] Anyone else get this fastboot error when trying to flash system.img - Kindle HD

I am trying to restore my Kindle HD to version 7.2.3 using Windows XP and when executing the fastboot command to flash the system.img I get the following error:
Code:
C:\temp\KFHD_SRT_v1.2.3>fastboot -i 0x1940 flash system system.img
load_file: could not allocate 929038336 bytes
error: cannot load 'system.img'
The system.img file is in the same directory as the fastboot.exe.
I get my Kindle into fastboot mode using a factory cable and to verify fastboot I get the product and it returnsTATE-PVT-08. I have checked the max-download-size and I get
Code:
max-download-size: 1006632960
finished. total time: 0.000s
i have tried flashing with both the factory cable and the regular USB cable and I keep getting the same error. Any thoughts on what the error means?

rjgonzalez73 said:
I am trying to restore my Kindle HD to version 7.2.3 using Windows XP and when executing the fastboot command to flash the system.img I get the following error:
Code:
C:\temp\KFHD_SRT_v1.2.3>fastboot -i 0x1940 flash system system.img
load_file: could not allocate 929038336 bytes
error: cannot load 'system.img'
The system.img file is in the same directory as the fastboot.exe.
I get my Kindle into fastboot mode using a factory cable and to verify fastboot I get the product and it returnsTATE-PVT-08. I have checked the max-download-size and I get
Code:
max-download-size: 1006632960
finished. total time: 0.000s
i have tried flashing with both the factory cable and the regular USB cable and I keep getting the same error. Any thoughts on what the error means?
Click to expand...
Click to collapse
There was another user a while back with the same problem, but I could never figure out why. Your system image is obviously smaller than the max-download size, so it doesn't make much sense to me.
From my perspective, if you can't get it to work, I would think you can (theoretically) boot into TWRP using the method found by Powerpoint45 and that would give you access to the adb shell so you can 'dd' the system image in place. I don't have an HD so I can't confirm that it will work, but I can't see any reason why it wouldn't.
That being said, I suggest you don't even attempt it unless you know exactly what you are doing.
"That's a special kind of stupid. The kind that makes me laugh."

soupmagnet said:
There was another user a while back with the same problem, but I could never figure out why. Your system image is obviously smaller than the max-download size, so it doesn't make much sense to me.
From my perspective, if you can't get it to work, I would think you can (theoretically) boot into TWRP using the method found by Powerpoint45 and that would give you access to the adb shell so you can 'dd' the system image in place. I don't have an HD so I can't confirm that it will work, but I can't see any reason why it wouldn't.
That being said, I suggest you don't even attempt it unless you know exactly what you are doing.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
I noticed there was an error in the command I copied and pasted. The 0x1940 should be 0x1949, however I still get the same error message. I am of the opinion it is an issue with the computer I am using. I will try with a computer with Windows 7 and see if I have better results.
UPDATE: It was an issue with my XP machine. I was able to flash the system.img using a Windows 7 machine and was able to downgrade to version 7.2.1.

rjgonzalez73 said:
I noticed there was an error in the command I copied and pasted. The 0x1940 should be 0x1949, however I still get the same error message. I am of the opinion it is an issue with the computer I am using. I will try with a computer with Windows 7 and see if I have better results.
UPDATE: It was an issue with my XP machine. I was able to flash the system.img using a Windows 7 machine and was able to downgrade to version 7.2.1.
Click to expand...
Click to collapse
Sorry to revive this thread, but I'm having the same issue and I'm a little desperate.
I'm running a Vista, as are all the computers in my household.

[Q] ??? OMAP4440 refreshing every second as I connect KFHD 7

My kindle got screwed up again after a restore from back up. Now it goes like this
a)shows Kindle fire (yellow) 1 second
b)shows fastboot 1 second
c)then screen goes blank, until I switch it off
As I switch it on, repeats a, b & c
The device manger keeps searching & refreshing OMAP4440 drivers every 2 second( with ding sounds)
This happens both with a factory cable as well as the standard usb.
Any one knows how to troubleshoot this?

Bump

OK I have no experience with bricked kindles that are bricked in that manner but I think kindle fire first aid may be useful, but if that device is not installing fast enough because of it shutting off before windows can complete installing the drivers I have to say and this may not be useful or something you want to try, but Linux might be the way to go, it typicly doesn't need to install the driver because drivers are either integrated into the kernel or loaded immediately as modules, and Linux comes with quite a few drivers by default. So your device would be recognized as its flashing off and on, from their I don't know what you could really do even if u have access to fast boot if it keeps shutting off evert two seconds I don't see you successfully flashing it unless u know how to write a bash script that waits for it to show up and then immediately flashes the boot loader, which is fairly small, it might be able to flash before it shuts off if your extremely lucky. From what my thought track is seeing i think it might stop with the constant rebooting once you manage to flash the bootloader, from their i woukd see fixing any other bad partitions as easy. This is all from a novice unbrickers standpoint. I may be completely off, haven't ever used kf first aid, so I don't know if your brick is fixable or not. Just thought I'd post my two cents since no one has been posting any help for you yet. Hopefully someone else that knows more about this can help you out.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

looks like your device doesn't have enough power to stay in fastboot. just leave it charging for about an hour even if it doesn't display anything. it should still be charging.

UMM!!
stunts513 said:
OK I have no experience with bricked kindles that are bricked in that manner but I think kindle fire first aid may be useful, but if that device is not installing fast enough because of it shutting off before windows can complete installing the drivers I have to say and this may not be useful or something you want to try, but Linux might be the way to go, it typicly doesn't need to install the driver because drivers are either integrated into the kernel or loaded immediately as modules, and Linux comes with quite a few drivers by default. So your device would be recognized as its flashing off and on, from their I don't know what you could really do even if u have access to fast boot if it keeps shutting off evert two seconds I don't see you successfully flashing it unless u know how to write a bash script that waits for it to show up and then immediately flashes the boot loader, which is fairly small, it might be able to flash before it shuts off if your extremely lucky. From what my thought track is seeing i think it might stop with the constant rebooting once you manage to flash the bootloader, from their i woukd see fixing any other bad partitions as easy. This is all from a novice unbrickers standpoint. I may be completely off, haven't ever used kf first aid, so I don't know if your brick is fixable or not. Just thought I'd post my two cents since no one has been posting any help for you yet. Hopefully someone else that knows more about this can help you out.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
1. I tried pluging it in ubuntu-12.04-desktop-i386 live usb, didnt detect the device. Do I have to download some thing before?
2. After a,b,c, the screen goes black but the OMAP4440 keeps refreshing in device manger it only stops when I push the power button for more than 20 seconds. I beleive the KFHD is not switching of but just goes to a black screen.
3. What is a bash script?

OK bash is a way more flexible scripting language you use in Linux. Think the Linux equivalent of a windows batch file but way better. You said it was going into fast boot for a brief moment. Before rebooting, I figured if its long enough for the fast boot command to recognize it in Linux, you could have the command for flashing the boot partition handy in a terminal. I figured if you had a stroke of luck, because the boot partition is so small, you might be able to flash it and unbrick it to at least get it to boot into fast boot to the point where you could restore the other partitions. I don't remember how exactly the fast boot command works in terms of waiting for the device to show up, that's why j was thinking use a batch script to repeat itself until sometching happened, but if it waits for the device u could simply run fastboot -i 0x1949 flash boot boot.img. Note boot.Img would be whatever the boot image restore file is called. Also Ubuntu probably is detect it, you must don't know it, its not going to popup anything or do anything unusual when its detected, only way u would know is to either install a device manager, I use a gnome one because I use an older distro of ubuntu, or run a command from a terminal the moment u see fast boot screen, I don't remember the command offhand, actually running dmesg would probably show it being picked up as a device connected, not sure what exactly it would say though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Hey, the description is quite technical for me. Can you write a step by step guide, starting from once i boot up a linus live usb (12.4 ubuntu)?
stunts513 said:
OK bash is a way more flexible scripting language you use in Linux. Think the Linux equivalent of a windows batch file but way better. You said it was going into fast boot for a brief moment. Before rebooting, I figured if its long enough for the fast boot command to recognize it in Linux, you could have the command for flashing the boot partition handy in a terminal. I figured if you had a stroke of luck, because the boot partition is so small, you might be able to flash it and unbrick it to at least get it to boot into fast boot to the point where you could restore the other partitions. I don't remember how exactly the fast boot command works in terms of waiting for the device to show up, that's why j was thinking use a batch script to repeat itself until sometching happened, but if it waits for the device u could simply run fastboot -i 0x1949 flash boot boot.img. Note boot.Img would be whatever the boot image restore file is called. Also Ubuntu probably is detect it, you must don't know it, its not going to popup anything or do anything unusual when its detected, only way u would know is to either install a device manager, I use a gnome one because I use an older distro of ubuntu, or run a command from a terminal the moment u see fast boot screen, I don't remember the command offhand, actually running dmesg would probably show it being picked up as a device connected, not sure what exactly it would say though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse

I am literally falling asleep right now, I will write it tomorrow after I finish writing my résumé... I will warn you it will be slightly vague because I don't use the newer distributions of Ubuntu and am unfamiliar with the ui. Actually for simplicity I will upload a zip file with the fastboot binary and any files it requires, so I don't have to explain how to install stuff in Ubuntu. Hopefully the nautilus browser is the same. For the record nautilus is basically like Ubuntu version of windows explorer. As long as you can find your home folder and launch a terminal you should be able to follow my vague instructions. Anyways I will write a guide tomorrow since I am literally nodding off.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

OK I haven't finished my resume but I figured this wouldn't take long to explain and I will just keep procrastinating if I don't clear everything in my mind. OK so to start with you need to open a terminal, I am unfamiliar with exactly where that will be located on new versions version f Linux because it doesn't use gnome ui. Last I checked if u hit the Ubuntu logo a menu with apps would come out, if there's an accessories section it would probably be there, if not there's a search function, if not that try Ctrl alt t, not sure if that keyboard shortcut is standard or not though.OK now I feel I can use numbers.
1. Download included zip file( will post from my PC in a moment)
2. Open the home folder in Ubuntu, again unsure where this will be but usually it shows u some things on that bar on the left, if home isn't mong them then click on like videos or music and go up a level, that is usually home.
3. Extract the contents of the zip file to a folder in the home directory, let's call the folder kindlefix
4. Download http://goo.im/devs/Hashcode/tate/kfhd7-u-boot-prod-7.2.3.bin this file and put it in the kindlefix directory.
5. In the terminal and type "CD kindlefix", now type "md5sum kfhd7-u-boot-prod-7.2.3.bin". Now check that the string outputted is the same as the one on the website. If it is continue to next step if not try redownloading the file again and checking it again.
6. In the terminal now type ./fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
7. Try hitting enter with your device powered off and when fastboot says waiting for device, power it on with fastboot cable.
Like I've been saying this is going to take a bit of luck to flash successfully, and if it does try to flash and fail it will probably just brick it worse, at which point I'd return to amazon. You might have to repeat this step a few times to get the timing right to see if it will flash, its a fairly small file so u might get extremely lucky. Post back and tell me what kind of luck u manage to get.

Your problem is that you are using OMAP drivers instead of fast boot or adb drivers.
Sent from my Amazon Kindle Fire HD using xda app-developers app

It does that yes, but only after it stays in fast boot for a few seconds, so we are trying to catch the kindle while its in fastboot with Linux so it can try to reflash the boot loader, if we could succeed in that then getting the rest working would be the easy part, though this as is is very difficult, only reason I even suggested trying this is because the boot loader is so small it doesn't take that long to flash, so I am hoping for it to flash in the few seconds it is in fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
It does that yes, but only after it stays in fast boot for a few seconds, so we are trying to catch the kindle while its in fastboot with Linux so it can try to reflash the boot loader, if we could succeed in that then getting the rest working would be the easy part, though this as is is very difficult, only reason I even suggested trying this is because the boot loader is so small it doesn't take that long to flash, so I am hoping for it to flash in the few seconds it is in fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
If the device IS actually going into fastboot, then it's entirely possible to re-flash the bootloader.
In order to do this, you have to enter the command while the device is unplugged, then plug it in when you see "waiting for device". As soon as fastboot mode is detected, the command will execute and the bootloader will be flashed, but be warned....
While flashing the bootloader happens rather quickly, if for some reason only part of the bootloader is flashed, the device will likely be unrecoverable. I suggest that you make sure the md5sum of the downloaded u-boot-bin checks out, and that you aren't using an extraordinarily slow computer.

Yea at this point his kindle is going to go either way, either way though if he didn't try what he's doing or if he did and it didn't work he'd be sending it into amazon though more than likely and seeing if they'd take it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
OK I haven't finished my resume but I figured this wouldn't take long to explain and I will just keep procrastinating if I don't clear everything in my mind. OK so to start with you need to open a terminal, I am unfamiliar with exactly where that will be located on new versions version f Linux because it doesn't use gnome ui. Last I checked if u hit the Ubuntu logo a menu with apps would come out, if there's an accessories section it would probably be there, if not there's a search function, if not that try Ctrl alt t, not sure if that keyboard shortcut is standard or not though.OK now I feel I can use numbers.
1. Download included zip file( will post from my PC in a moment)
2. Open the home folder in Ubuntu, again unsure where this will be but usually it shows u some things on that bar on the left, if home isn't mong them then click on like videos or music and go up a level, that is usually home.
3. Extract the contents of the zip file to a folder in the home directory, let's call the folder kindlefix
4. Download http://goo.im/devs/Hashcode/tate/kfhd7-u-boot-prod-7.2.3.bin this file and put it in the kindlefix directory.
5. In the terminal and type "CD kindlefix", now type "md5sum kfhd7-u-boot-prod-7.2.3.bin". Now check that the string outputted is the same as the one on the website. If it is continue to next step if not try redownloading the file again and checking it again.
6. In the terminal now type ./fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
7. Try hitting enter with your device powered off and when fastboot says waiting for device, power it on with fastboot cable.
Like I've been saying this is going to take a bit of luck to flash successfully, and if it does try to flash and fail it will probably just brick it worse, at which point I'd return to amazon. You might have to repeat this step a few times to get the timing right to see if it will flash, its a fairly small file so u might get extremely lucky. Post back and tell me what kind of luck u manage to get.
Click to expand...
Click to collapse
I lost you on step 5. Which website? the md5sum that i get is (bb029673d8f186db4dff6d38f4aa28cf) <---Nevermind. I know what website you are talking about.
---------- Post added at 01:49 AM ---------- Previous post was at 01:22 AM ----------
Once I get to number 6 I get this?
[email protected]:~/Kindlefix$ ./fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
bash: ./fastboot: No such file or directory
And the fastboot file and kfhd7...bin file are inside the folder.

Update.. FIXED
Thanks @stunts513 for your help. I was able to fix my kindle. The linux didn't work. Somehow it managed to stay on fastboot screen. I went back to Windows. Opened a command prompt typed fastboot -1 0x1949 getvar product and hit enter. it waited for device. turned Kindle off. plugged fastboot cable to kindle then PC and was able to read it. Once that happened I was able to manually input the info
{fastboot -i 0x1949 flash boot "C:\KFFirstAide\path\to\boot.img"
fastboot -i 0x1949 flash recovery "C:\KFFirstAide\path\to\recovery.img"
fastboot -i 0x1949 flash system "C:\KFFirstAides\path\to\ystem.img"} ofcourse changing the paths.
I downloaded Hashcode's Kindle OS from here http://forum.xda-developers.com/showthread.php?t=2218475.
And it worked.
[ Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Orlando>fastboot -i 0x1949 getvar product
< waiting for device >
product: Tate-PVT-08
finished. total time: 0.004s
C:\Users\Orlando>fastboot -i 0x1949 flash boot "C:\KFFirstAide\path\to\boot.img"
target reported max download size of 1006632960 bytes
error: cannot load 'C:\KFFirstAide\path\to\boot.img': No error
C:\Users\Orlando>fastboot -i 0x1949 flash boot "C:\KFFirstAide\images\boot.img"
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 2.826s]
writing 'boot'...
OKAY [ 0.688s]
finished. total time: 3.517s
C:\Users\Orlando>fastboot -i 0x1949 flash recovery "C:\KFFirstAide\images\recove
ry.img"
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 2.826s]
writing 'recovery'...
OKAY [ 0.681s]
finished. total time: 3.513s
C:\Users\Orlando>fastboot -i 0x1949 flash system "C:\KFFirstAide\images\system.i
mg"
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [312.188s]
writing 'system'...
OKAY [ 73.516s]
finished. total time: 385.710s]
THANKS to all the 50+ threads that I read about this. And all the people that make it happen!

lo pudiste solucionar?
ToPViP said:
Thanks @stunts513 for your help. I was able to fix my kindle. The linux didn't work. Somehow it managed to stay on fastboot screen. I went back to Windows. Opened a command prompt typed fastboot -1 0x1949 getvar product and hit enter. it waited for device. turned Kindle off. plugged fastboot cable to kindle then PC and was able to read it. Once that happened I was able to manually input the info
{fastboot -i 0x1949 flash boot "C:\KFFirstAide\path\to\boot.img"
fastboot -i 0x1949 flash recovery "C:\KFFirstAide\path\to\recovery.img"
fastboot -i 0x1949 flash system "C:\KFFirstAides\path\to\ystem.img"} ofcourse changing the paths.
I downloaded Hashcode's Kindle OS from here http://forum.xda-developers.com/showthread.php?t=2218475.
And it worked.
[ Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Orlando>fastboot -i 0x1949 getvar product
< waiting for device >
product: Tate-PVT-08
finished. total time: 0.004s
C:\Users\Orlando>fastboot -i 0x1949 flash boot "C:\KFFirstAide\path\to\boot.img"
target reported max download size of 1006632960 bytes
error: cannot load 'C:\KFFirstAide\path\to\boot.img': No error
C:\Users\Orlando>fastboot -i 0x1949 flash boot "C:\KFFirstAide\images\boot.img"
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 2.826s]
writing 'boot'...
OKAY [ 0.688s]
finished. total time: 3.517s
C:\Users\Orlando>fastboot -i 0x1949 flash recovery "C:\KFFirstAide\images\recove
ry.img"
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 2.826s]
writing 'recovery'...
OKAY [ 0.681s]
finished. total time: 3.513s
C:\Users\Orlando>fastboot -i 0x1949 flash system "C:\KFFirstAide\images\system.i
mg"
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [312.188s]
writing 'system'...
OKAY [ 73.516s]
finished. total time: 385.710s]
THANKS to all the 50+ threads that I read about this. And all the people that make it happen!
Click to expand...
Click to collapse
hola soy latino pero frecuento bastante el foro, antes no opinaba puesto que no hablo ingles , alguno que hable español me podria ayudar? me pasa lo mismo que el joven que inicio el tema, veo que algo hizo para arreglarlo pero yo no entiendo , porfavor ayudenme:crying:

stunts513 said:
OK I haven't finished my resume but I figured this wouldn't take long to explain and I will just keep procrastinating if I don't clear everything in my mind. OK so to start with you need to open a terminal, I am unfamiliar with exactly where that will be located on new versions version f Linux because it doesn't use gnome ui. Last I checked if u hit the Ubuntu logo a menu with apps would come out, if there's an accessories section it would probably be there, if not there's a search function, if not that try Ctrl alt t, not sure if that keyboard shortcut is standard or not though.OK now I feel I can use numbers.
1. Download included zip file( will post from my PC in a moment)
2. Open the home folder in Ubuntu, again unsure where this will be but usually it shows u some things on that bar on the left, if home isn't mong them then click on like videos or music and go up a level, that is usually home.
3. Extract the contents of the zip file to a folder in the home directory, let's call the folder kindlefix
4. Download http://goo.im/devs/Hashcode/tate/kfhd7-u-boot-prod-7.2.3.bin this file and put it in the kindlefix directory.
5. In the terminal and type "CD kindlefix", now type "md5sum kfhd7-u-boot-prod-7.2.3.bin". Now check that the string outputted is the same as the one on the website. If it is continue to next step if not try redownloading the file again and checking it again.
6. In the terminal now type ./fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
7. Try hitting enter with your device powered off and when fastboot says waiting for device, power it on with fastboot cable.
Like I've been saying this is going to take a bit of luck to flash successfully, and if it does try to flash and fail it will probably just brick it worse, at which point I'd return to amazon. You might have to repeat this step a few times to get the timing right to see if it will flash, its a fairly small file so u might get extremely lucky. Post back and tell me what kind of luck u manage to get.
Click to expand...
Click to collapse
Lol,nice guide mate. I saw the title and just thought,"How the hell does OMAP4 refresh itself?" Anyway,I think that he would be better off installing android-tools-fastboot since he's running Ubuntu.

Yea true, I hadn't familiarized myself at the time with the package names and such, just checked that post and man is the date old, almost a year... Learned quite a bit since then.

stunts513 said:
Yea true, I hadn't familiarized myself at the time with the package names and such, just checked that post and man is the date old, almost a year... Learned quite a bit since then.
Click to expand...
Click to collapse
help me please please

Translation: hi i am latino but quite frequent the forum, not previously thought since I do not speak English , some speak Spanish could help me ? I feel the same as the young man who started the topic , see something done to fix it but I do not understand , please help : crying :
My Spanish is horrible so I ran it through Google.
If it is doing exactly what the original poster is doing rather than showing up only as a omap4boot and not turning on then I recommend using Linux and running "fastboot -i 0x1949 erase boot" once it clears the boot partition it should kick it into fastboot until the boot partition gets re-flashed.

[Q] Fastboot issues

Hi there,
I have a Nexus 7 (2012) and I'm trying to flash the recovery as per the instructions here:
****Edit*** As a new member, I'm not allowed to post a link.. So basically Google instructions for installing CyanogenMod on a nexus 7, and the first or second link is the one I'm using as a guide.
Basically, I type: fastboot flash recovery recovery.img but the flash fails.
See below....
C:\Users\Mike\Desktop\q>fastboot flash recovery recovery.img
sending 'recovery' (7298 KB)...
FAILED (remote: (Timeout))
finished. total time: 2.019s
What's causing this to happen? If i type "fastboot devices", it does show the serial # for my tablet, so I know it sees it.
Edit: I see that I jumped the gun and posted this in the wrong section. Can a mod please move it to the right place?

m_bisson87 said:
Hi there,
I have a Nexus 7 (2012) and I'm trying to flash the recovery as per the instructions here:
****Edit*** As a new member, I'm not allowed to post a link.. So basically Google instructions for installing CyanogenMod on a nexus 7, and the first or second link is the one I'm using as a guide.
Basically, I type: fastboot flash recovery recovery.img but the flash fails.
See below....
C:\Users\Mike\Desktop\q>fastboot flash recovery recovery.img
sending 'recovery' (7298 KB)...
FAILED (remote: (Timeout))
finished. total time: 2.019s
What's causing this to happen? If i type "fastboot devices", it does show the serial # for my tablet, so I know it sees it.
Click to expand...
Click to collapse
i would suggest using a different USB cable. If fastboot looses contact with the phone for a split second the timeout error will be displayed.

synisterwolf said:
i would suggest using a different USB cable. If fastboot looses contact with the phone for a split second the timeout error will be displayed.
Click to expand...
Click to collapse
You know what? I tried a few different uSB ports and one of them finally worked. Not sure why
Anyways, I have a new problem now...
I'm using the ClockworkMod recovery thing, and I'm trying to sideload Cyanogen but when I navigate to the "adb sideload" on the tablet, my PC (Windows 7) makes that "usb disconnected" noise, plus a second noise that I've not heard before. It's a very low tone chime. At this point, I try to sideload using "abd sideload ....." and it says "error: device not found".
Any tips for this?
I may have found my answer This forum is excellent!!! For the sake of others, in case Google points them here...:
Originally Posted by mashedbymachines
Had the same problem.
Right click the "nexus 4" with the yellow exclamation mark.
Go to the details tab
Choose "hardware id"
you will see something like
USB\VID_18D1&PID_D001
USB\VID_18D1&PID_D001&REV_0228
Open your folder with the usb_driver
edit the android_winusb.inf
depending on if you use 32/64 bit, navigate to
for 32 bit
[Google.NTx86]
xxxxxx
;Google Nexus (generic)
xxxx
for 64 bit
[Google.NTamd64]
xxxxx
;Google Nexus (generic)
xxxx
Add these two lines
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0228
Be sure that the text after "USB_Install" matches what you had on your hardware id tab in device manager.
Now try to install these drivers and voila, it should install and work under recovery
Click to expand...
Click to collapse

[ROM][ALPHA][WIP] -- Asteroid OS \\ New OS \\ Open Source \\ Non-Android Wear

Asteroid OS​
Introduction and Warning:
Asteroid OS is a Free Open Source alternative operating system for smartwatches. It utilizes libhybris to ensure maximum compatibility with the watch. The OS team is currently looking for active contributors to make it grow (more info at the project's webpage: https://asteroidos.org/). The OS is NOT based on Android wear and is currently in an Alpha Phase, has limited functions, applications and customizability so flash at your own risk. The current build is mostly meant for developers rather than end-users, so these images in no way reflect the finished Asteroid OS. I take no responsibility for what happens by the use of this software. By using the method bellow you don't flash Asteroid but rather run it side by side with Android wear. Essentially you place the OS file inside the watch and fastboot into it. This way Android Wear stays installed and you can test Asteroid. Asteroid at its current phase is not meant as a daily OS as it has bugs and issues.
Click to expand...
Click to collapse
Media:
YouTube Video: https://www.youtube.com/watch?v=b_GJiQYTAIk
Photos and Videos can be found in the project's twitter account (mentioned bellow).
Downloads:
Official prebuilt Asteroid OS image: https://release.asteroidos.org/nightlies/lenok/
Instructions:
1. Make sure you have an ADB installation (Minimal adb and fastboot should do) and your watches' bootloader is unlocked and debugging is enabled from the settings.
2. Download the two files in the download section and place them in the same folder and connect the watch to the computer
3. Open up the shell or command prompt (cmd) and navigate to that folder
4. Issue these commands:
Code:
adb push -p asteroid-image-lenok.ext4 /sdcard/asteroidos.ext4
adb reboot bootloader
fastboot boot zImage-dtb-lenok.fastboot
5. The watch will reboot into Asteroid OS. Every time you want to boot into asteroid you have to issue the last two commands or else you will boot into android wear normally.
Removal Instructions:
Just open up shell or command prompt (cmd), connect the watch to the computer and issue this command:
Code:
adb shell rm /sdcard/asteroidos.ext4
Known issues:
https://github.com/AsteroidOS/meta-lenok-hybris/issues/
Credits:
kido - Creator of the OS
atx - lenok port
Everyone on the #asteroid IRC
Links:
Webpage: asteroidos.org
Twitter: @asteroidOS
IRC: #asteroid

hELP
Good evening, I have installed asteroidos on my watch r lg, I would like to go back to wear, what should I do? Thank you

Great OS and thanks for porting it. The coping and starting worked like a charm and that super fast boot time is so amazing! But I can't do anything when started. I can only use the touch screen for waking up the watch, when I want to use it nothing happens. Only one time I was able to use the watch (scroll through menus, open apps and change settings) but then after I restarted, it did't work anymore. I don't know why, I only know that the watch didn't hang itself because the wallpaper still moves.

ilpianista said:
4. Issue these commands:
Code:
adb push asteroid-image-lenok.ext2 /sdcard/linux/rootfs.ext2
adb reboot bootloader
fastboot boot zImage-dtb-lenok.fastboot
5. The watch will reboot into Asteroid OS. Every time you want to boot into asteroid you have to issue the last two commands or else you will boot into android wear normally.
Click to expand...
Click to collapse
Is there a way to make it default OS? Is there any IMG files to flash without having to have AW on the watch?
My watch isnt working with AW at the moment because of 'battery problems'. But stays on for days on fastboot or recovery.

miffymiffy said:
Is there a way to make it default OS? Is there any IMG files to flash without having to have AW on the watch?
My watch isnt working with AW at the moment because of 'battery problems'. But stays on for days on fastboot or recovery.
Click to expand...
Click to collapse
Yes, I'm using it this way too. Type:
Code:
adb reboot bootloader
fastboot flash userdata asteroid-image-lenok.ext2
fastboot flash boot zImage-dtb-lenok.fastboot
Cameo164 said:
But I can't do anything when started. I can only use the touch screen for waking up the watch, when I want to use it nothing happens.
Click to expand...
Click to collapse
That's a known issue, restart lipstick by typing:
Code:
adb shell systemctl restart [email protected]

ilpianista said:
fastboot flash userdata asteroid-image-lenok.ext2
fastboot flash boot zImage-dtb-lenok.fastboot[/CODE]
Click to expand...
Click to collapse
F:\Downloads\Mobile\ADB and Fastboot>fastboot flash userdata asteroid-image-lenok.ext2
< waiting for device >
target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
erasing 'userdata'...
OKAY [ 2.158s]
sending sparse 'userdata' (250209 KB)...
OKAY [ 11.035s]
writing 'userdata'...
FAILED (remote: sparse image write failure)
finished. total time: 85.842s
This is what I get if I do so. It just boot loops. Any ideas?

miffymiffy said:
F:\Downloads\Mobile\ADB and Fastboot>fastboot flash userdata asteroid-image-lenok.ext2
< waiting for device >
target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
erasing 'userdata'...
OKAY [ 2.158s]
sending sparse 'userdata' (250209 KB)...
OKAY [ 11.035s]
writing 'userdata'...
FAILED (remote: sparse image write failure)
finished. total time: 85.842s
This is what I get if I do so. It just boot loops. Any ideas?
Click to expand...
Click to collapse
Ah damn, the nightly build is old and it misses a required fix. You could try to build it yourself, I can't share mine at the moment because I'm outside.
I just built a new image:
Download

ilpianista said:
Yes, I'm using it this way too. Type:
Code:
adb reboot bootloader
fastboot flash userdata asteroid-image-lenok.ext2
fastboot flash boot zImage-dtb-lenok.fastboot
That's a known issue, restart lipstick by typing:
Code:
adb shell systemctl restart [email protected]
Click to expand...
Click to collapse
Is there a way to activate ADB even if the touch isnt working?
Device isnt listed under "ADB Devices" in CMD so its not possible to execute it

ilpianista said:
.
Click to expand...
Click to collapse
I can get it to run if I push the file like in post 1, but not to run stand alone.
Same thing happens as posted above, cant use touch screen. If I reflash boot image, it works again, but until reboot.

FurFur_ said:
Is there a way to activate ADB even if the touch isnt working?
Device isnt listed under "ADB Devices" in CMD so its not possible to execute it
Click to expand...
Click to collapse
adb is enabled by default, but due to a regression, MTP was enabled instead of ADB. This has been reverted, please try with this new build.

I am unable to get it started on my GWATCHR. It will refuse to boot. D:

ilpianista said:
adb is enabled by default, but due to a regression, MTP was enabled instead of ADB. This has been reverted, please try with this new build.
Click to expand...
Click to collapse
I'll give it a try tonight :good:
Edit :
Had the time to do it and still the same :/
It seems like MTP was enabled again instead of ADB.

Hello, no luck, not working here
Reboots after LG logo

Getget said:
Reboots after LG logo
Click to expand...
Click to collapse
Hi, please try again with the new installation instructions.

Just reviving an old thread. Could anyone get this running on lenok? full install?

hornedfiend said:
Just reviving an old thread. Could anyone get this running on lenok? full install?
Click to expand...
Click to collapse
https://forum.xda-developers.com/g-watch-r/general/asteroidos-alternative-to-wear-os-t3791741

PierPaolo said:
hELP
Good evening, I have installed asteroidos on my watch r lg, I would like to go back to wear, what should I do? Thank you
Click to expand...
Click to collapse
Go to setting and reboot and wait some time

AyanRashid said:
Go to setting and reboot and wait some time
Click to expand...
Click to collapse
go to the chat, and share your experience here, that is what I suggest.

Peter Gamma said:
go to the chat, and share your experience here, that is what I suggest.
Click to expand...
Click to collapse
Contact - AsteroidOS
AsteroidOS is an open-source operating system for smartwatches.
asteroidos.org

There is a newer thread for LG G Watch R here:
AsteroidOS on lg watch r
Hi There, I was thinking of resurrecting my old watch R and I noticed that there is nightly port for linux os AsteroidOS https://asteroidos.org/install/ Has anyone tried to load it to our watch and advice if it worth the try? thx in advacnce
forum.xda-developers.com

unknkown oem command

Hey folks, long time xda user heavy search user results in minimal posts..
ok here we go.
I unlocked bootloader and rooted device with magisk now im attempting to re lock my boot loader.
i factory reset device and flashed google factory image with supplied zip file from google
command im using is
"fastboot oem lock"
results
C:\Users\RyeMc>fastboot oem lock
FAILED (remote: 'Unknown OEM command')
fastboot: error: Command failed
this is first lines from google factory image...
Sending 'bootloader' (8761 KB) OKAY [ 0.253s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
next i opened cmd and entered
"fastboot flash boot" then went and moved boot file into cmd window and said successful also tried boot_a and boot_b
unsure why i have tried to re download sdk manager android studio and input the file locations in the path under advanced settings.
albeit iv been out of the root game for a couple years made the mistake of getting a note 8 so i was stuck in that eco system.
some help or advice would be nice thanks.
before i rooted i made sure i was able to lock and unlock bootloader .

Use Adb tools or Sdk tools to unlock your phone.
Sent from my Pixel 4 XL using Tapatalk

Thaiban said:
Use Adb tools or Sdk tools to unlock your phone.
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
device is currently unlocked looking to relock device..

the correct command is: fastboot flashing lock
make 100% certain however that your device is 100% stock before relocking, very good chance of bricking it if it is not.

uicnren said:
the correct command is: fastboot flashing lock
make 100% certain however that your device is 100% stock before relocking, very good chance of bricking it if it is not.
Click to expand...
Click to collapse
C:\Users\RyeMc>fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
im going to go double check my path make sure it still exist. i did try and download sdk tools again.

RyeMcFly17 said:
C:\Users\RyeMc>fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
im going to go double check my path make sure it still exist. i did try and download sdk tools again.
Click to expand...
Click to collapse
if you want an easy (does require a little work on Windows) fool-proof way to keep adb/fastboot up to date and installed correctly, see: https://github.com/corbindavenport/nexus-tools
Easier Windows choice: https://developer.android.com/studio/releases/platform-tools.html
No need for the SDK or anything else, unless you actually dev apps.

uicnren said:
if you want an easy (does require a little work on Windows) fool-proof way to keep adb/fastboot up to date and installed correctly, see: https://github.com/corbindavenport/nexus-tools
Easier Windows choice: https://developer.android.com/studio/releases/platform-tools.html
No need for the SDK or anything else, unless you actually dev apps.
Click to expand...
Click to collapse
What he said! :laugh:
Easier Windows choice : r29.0.6

download the latest platform tools and extract it, in the folder with the PT files in the top search bar type cmd and then try.

oem unlocking already unlocked
uicnren said:
if you want an easy (does require a little work on Windows) fool-proof way to keep adb/fastboot up to date and installed correctly, see: https://github.com/corbindavenport/nexus-tools
Easier Windows choice: https://developer.android.com/studio/releases/platform-tools.html
No need for the SDK or anything else, unless you actually dev apps.
Click to expand...
Click to collapse
resolved added sdk platform tools to path in advanced settings flashed new google image and retired fastboot flashing lock and seems to have worked, thanks for all your paitence and advice. ill head back to the shadows and read read read before i post again till next time folks.

RyeMcFly17 said:
resolved added sdk platform tools to path in advanced settings flashed new google image and retired fastboot flashing lock and seems to have worked, thanks for all your paitence and advice. ill head back to the shadows and read read read before i post again till next time folks.
Click to expand...
Click to collapse
:good::good:
glad you got it sorted.