Related
Fix Modem / Baseband JB AT&T ONLY... Sure did fix my problem!
Diagnosis for: (Random) no sound; no phone connectivity such as: WIFI; BLUETOOTH; GSM.
Can happen: Flashing wrong fw; Flash failure.
NOTE: Android SDK is required, go to your OS below and view "prerequisites" for more information...
Windows 7 methodPrerequisites: Android SDK - Tools and SDK! (install here.)
Instructions:
(1. Make a folder in the directory "C:/" and name it "qinara."
(2. Download the following attachment below: "NON-HLOS.bin" (In the attachments / downloads section)
(3. Place "NON-HLOS.bin" in the "C:/qinara/" folder.
(4. Open a cmd prompt.
(5. Change Directory (CD) the cmd to your install location of Android SDK's Platform Tools (type it in to the command prompt.) to make
a command like the following example. Example: CD C:/users/YOUR-USERNAME/android/sdk/platform-tools
(6. Type the following command in...
Code:
fastboot flash modem C:/qinara/NON-HLOS.bin
(7. Wait for the modem to be sent and installed.
(8. Type the following command in...
Code:
fastboot reboot
(9. When the phone boots everything but gsm will be working, to fix it go to settings. From the main settings menu, go to mobile network. It
will freeze, press the home button. Once you press the home button open up recent apps by pressing the multi-tasking button.
it freezes.
(10. Open up your multi-tasking menu and open settings.
(11. Set "select network" to "automatic," then your done.
Ubuntu / Other Linux-distro methodPrerequisites: Android SDK - Tools only! (to install type the following cmds in terminal...)
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Instructions:
(1. Make a folder in the directory "/home/USERNAME/" and name it "qinara."
(2. Download the following attachment below: "NON-HLOS.bin" (In the attachments / downloads section)
(3. Place "NON-HLOS.bin" in the "/home/USERNAME/qinara/" folder.
(4. Open a terminal.
(5. Type the following command in...
Code:
fastboot flash modem /home/USERNAME/qinara/NON-HLOS.bin
(6. Wait for the modem to be sent and installed.
(7. Type the following command in...
Code:
fastboot reboot
(8. When the phone boots everything but gsm will be working, to fix it go to settings. From the main settings menu, go to mobile network. It
will freeze, press the home button. Once you press the home button open up recent apps by pressing the multi-tasking button.
it freezes.
(9. Open up your multi-tasking menu and open settings.
(10. Set "select network" to "automatic," then your done.
Downloads
-NON-HLOS.bin
Ask any questions below... :fingers-crossed:
Kinda feels that way...but on the Linux instructions just use ~/qinara/NON-HLOS.bin instead of /home/USERNAME/qinara/NON-HLOS.bin
~/ means the users home directory
Also, and I'm gonna add this to my faq, but download the fastboot I linked, rename to moto-fastboot, place it in ~/bin and add that to $PATH in ~/.bashrc (or where ever your preferred disto prefers it to be)
My actual path line in .bashrc (the part above I'm referring to is in bold)
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/share/android/bin:/share/android/adt/sdk/tools:/share/android/adt/eclipse:/share/android/adt/sdk/platform-tools:$HOME/bin:"
For the curious, I keep all my Android stuff on its own partition (/share/android) so all I have to do is add those directories to my $PATH if I decide to disto hop. If you dualboot, you can do the same thing only set the partition as NTFS or ext2 (there's an windows ext2 driver). I disto hop about once a month.
Don't have access to my desktop right now trying to install my new ssd and put Linux mint on it. (Noticed your a Linux guy, do you like mint?) Anyways I'll be sure to add that in later. Thanks.
Sent from my MB886 using xda premium
Mints OK. I prefer Mint Debian, but I'm not a fan of Ubuntu. Pure Debian Stable and Testing is also a good choice.
Arch Linux and its derivatives are nice but aren't noob friendly and are prone to breakage due to being so bleeding edge. Manjaro is a noob friendly distro based on Arch repo snapshots with bug fixes.
About to hop to Slackware 14 myself. Gonna be my first time using it.
All the other distros I've used -- too long ago to be fair and relevant to what's out now.
help...
can you tell me its working or not cause i have some gsm problem no signal due to band change
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
sending sparse 'modem' (28172 KB)...
OKAY [ 2.430s]
writing 'modem'...
(bootloader) Unknown chunk type
FAILED (remote failure)
finished. total time: 3.720s
Oooooh Cool.....now after trying to find how to get out of the mess that created. I still dont have signal lol
i really need my signal back ...anyone could help me ,,,i am afraid this method does brick my phone ..and another question is if i install the stock rom from RSD lite , will i lost my root access???
yashrab said:
i really need my signal back ...anyone could help me ,,,i am afraid this method does brick my phone ..and another question is if i install the stock rom from RSD lite , will i lost my root access???
Click to expand...
Click to collapse
Yeah this method bricked my phone. I had to go back to stock through RSD, and lost root access. The good news is it was so easy to reacquire root thanks to Dan Rosenberg's programs.
Can I install stock though myth tool.. I think it does work just like RSD?.. Plz tell me cause I am totally noob in this part.. And I don't want to brick my phone..
Sent from my MB886 using xda premium
Moto Atrix work on any GSM carrier or.. ?
skeevydude said:
Mints OK. I prefer Mint Debian, but I'm not a fan of Ubuntu. Pure Debian Stable and Testing is also a good choice.
Arch Linux and its derivatives are nice but aren't noob friendly and are prone to breakage due to being so bleeding edge. Manjaro is a noob friendly distro based on Arch repo snapshots with bug fixes.
About to hop to Slackware 14 myself. Gonna be my first time using it.
All the other distros I've used -- too long ago to be fair and relevant to what's out now.
Click to expand...
Click to collapse
I have question. If I buy Moto Atrix HD will it possible to make it carrier-unlocked so I can use it here in Saudi Arabia where 90% devices are not carrier-locked?
lonesomedove said:
I have question. If I buy Moto Atrix HD will it possible to make it carrier-unlocked so I can use it here in Saudi Arabia where 90% devices are not carrier-locked?
Click to expand...
Click to collapse
You should be able to, but I'll tell ya that some users have gone through multiple places to get it unlocked since not all the unlock services have the updated unlock codes we need.
Nope
Code:
C:\Program Files\Android SDK\sdk\platform-tools>fastboot flash modem C:/qinara/NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
sending sparse 'modem' (28164 KB)...
OKAY [ 2.185s]
writing 'modem'...
(bootloader) Unknown chunk type
FAILED (remote failure)
finished. total time: 3.429s
Yup. Didn't work.
Any ideas?
BackDoorNoBaby said:
Code:
C:\Program Files\Android SDK\sdk\platform-tools>fastboot flash modem C:/qinara/NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
sending sparse 'modem' (28164 KB)...
OKAY [ 2.185s]
writing 'modem'...
(bootloader) Unknown chunk type
FAILED (remote failure)
finished. total time: 3.429s
Yup. Didn't work.
Any ideas?
Click to expand...
Click to collapse
You didn't use OUR fastboot. I have a link in our fastboot guide, and a direct link here.
/Thank you for posting the full terminal output, command and all.
//It helps
///Most just post "Help, Help, Help" X doesn't work.
Thanks
skeevydude said:
You didn't use OUR fastboot. I have a link in our fastboot guide, and a direct link here.
/Thank you for posting the full terminal output, command and all.
//It helps
///Most just post "Help, Help, Help" X doesn't work.
Click to expand...
Click to collapse
Got it. Thanks.
I'll check it out after my classes tonight and give an update.
Yup
Yup. That did it. Fixed the issue.
Back to my 4G!
Thanks again.
Anyone tried with CM10.2?
Nope. I know Cyanogenmod has issues at the moment, but I don't know if this will fix it.
Best I can say is to try it. Worst case: you reinstall the ROM. Or you can wait for a release version of CM 10 instead of a nightly.
I can say this didn't brick my phone, so you shouldn't have to worry about it. (but as always - no guarantee)
Sent from my Atrix HD using xda app-developers app
I really need help, I need something like this but for a company in Mexico. I tried this but it didn't worked.
Question if i reflash back to stock eith RSD LITE or myth tools will that fix my baseband i delete my baseband by accident
Dumb me
wcdma and lte network problem
i happen to own the mb886 the lte and wcdma used to work then i mistakenly went to change my base band to cellular (800-mhz) then the network went off so i changed it to (aus2 band (gsm-900/ dcs-1900/wcdma-850/wcdma-pcs-1900) but now am only able to get 2g or edge networks but am also in a 3g coverd area. can you guys please help me out
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.
Hello All,
The other night my kindle had approximately 10% battery life left; I forgot to charge it up the next day. I noticed the battery expired and proceeded to charge it up; when I plugged the charger in the battery symbol came up in the middle of the screen. I charged it overnight and proceeded to turn it on the next morning. When I did so, the "Kindle Fire" (all in white lettering) screen popped up and didn't go away. I have not modded this kindle in any way!
I searched the forums and made a fastboot cable, it goes into fastboot mode but my computer doesn't recognize it when i issue the "adb device" command. I am not sure what happened to my kindle (it is 1 month past the warranty date) but I was hoping to re-install the OS back onto the device.
Any help would be greatly appreciated.
MT
MT_Keg said:
Hello All,
The other night my kindle had approximately 10% battery life left; I forgot to charge it up the next day. I noticed the battery expired and proceeded to charge it up; when I plugged the charger in the battery symbol came up in the middle of the screen. I charged it overnight and proceeded to turn it on the next morning. When I did so, the "Kindle Fire" (all in white lettering) screen popped up and didn't go away. I have not modded this kindle in any way!
I searched the forums and made a fastboot cable, it goes into fastboot mode but my computer doesn't recognize it when i issue the "adb device" command. I am not sure what happened to my kindle (it is 1 month past the warranty date) but I was hoping to re-install the OS back onto the device.
Any help would be greatly appreciated.
MT
Click to expand...
Click to collapse
You should use a Linux distro to get the drivers. To restore,use the kindle fire first aid or SRT
Sent from my device running CyanogenMod 11
I believe I have the drivers installed. Under the Device Manager I see a an opting called "Kindle Fire" once I expand to the next level I see "Android ADB Interface". To further clarify, I am not able to "Enable ADB" on the physical device.
I tried using KFHD SRT, I selected Option 1 and the Command Prompt indicated that it transferred 903XXX kb in 53 seconds. when I went to "Erase Cache and User Data" it couldn't find the device and my computer sounded like the USB connection was continuously being connected and disconnected in a loop.
Since that happened I tried issuing the command
Code:
fastboot -i 0x1949 getvar product
My prompt states:
< waiting for device >
product: Soho-PVT-Prod-07
finished. total time 0.004s
Then if I issue the command
Code:
adb devices
My prompt states:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
There are no devices in the list. This is probably because I didn't have ADB Enabled on my Kindle before it Died.
Alternatively, I tried the KF First Aide tried to "Completely Restore the KFHD7 to 7.2.1" (Option 4). It downloaded a bunch of files then spit out the following:
target reported max download size of 1005584384 bytes
error: cannot load 'boot.img': No error
target reported max download size of 1005584384 bytes
error: cannot load 'recovery.img': No error
target reported max download size of 1005584384 bytes
error: cannot load 'system.img': No error
erasing 'userdata'...
OKAY [ 0.024s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.009s]
erasing 'cache'...
OKAY [ 0.022s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.008s]
finished. total time: 0.067s
Would You Like To Wipe Data And Cache (y/n) ?
Am I going down the right path?
Thanks for your help!
MT
Stop! The SRT tool is for the Tate model not the Soho. You could brick your device if you continue. Go to kfsowi.com to get images for the Soho.
And when you're in fastboot it will not respond to adb commands.
thanks for the reply. Apparently kfsowi.com does not exist anymore. Is there another resource? What do I have to do to get the images onto the "SOHO" device?
Thanks for the help!
MT
bump
MT_Keg said:
thanks for the reply. Apparently kfsowi.com does not exist anymore. Is there another resource? What do I have to do to get the images onto the "SOHO" device?
Thanks for the help!
MT
Click to expand...
Click to collapse
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
I've updated to android 10 thinking it was gonna be fun but now I can't receive updates from the play store, my saftetynet is not valid (does not pass), I can't use my bank account apps and chrome cannot download any files (ending with download error)
Is there anyway to return to android 9 or am I doomed until I spend another 800$ cad?
Phone: WW_17.0210.1912.22_0
Tencent 8gb/128gb
Converted from CN to WW with guides from here
I've tried following this:
https://forum.xda-developers.com/rog-phone-2/how-to/rom-asus-rog-phone-ii-zs660kl-ww-t3971059
But get the following:
target reported max download size of 536870912 bytes
sending 'abl' (420 KB)...
OKAY [ 0.020s]
writing 'abl'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.031s
Send help
SirGoldenTaco said:
I've updated to android 10 thinking it was gonna be fun but now I can't receive updates from the play store, my saftetynet is not valid (does not pass), I can't use my bank account apps and chrome cannot download any files (ending with download error)
Is there anyway to return to android 9 or am I doomed until I spend another 800$ cad?
Phone: WW_17.0210.1912.22_0
Tencent 8gb/128gb
Converted from CN to WW with guides from here
I've tried following this:
https://forum.xda-developers.com/rog-phone-2/how-to/rom-asus-rog-phone-ii-zs660kl-ww-t3971059
But get the following:
target reported max download size of 536870912 bytes
sending 'abl' (420 KB)...
OKAY [ 0.020s]
writing 'abl'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.031s
Send help
Click to expand...
Click to collapse
If you want to go back to Android 9, flash the latest RAW
Welp it ended better than I thought, followed this guide:
https://forum.xda-developers.com/rog-phone-2/how-to/guide-convert-cn-to-ww-rom-26-08-t3961042
And was saved by cyber Jesus: JazonX
Thanks for the assistance!
SirGoldenTaco said:
Welp it ended better than I thought, followed this guide:
https://forum.xda-developers.com/rog-phone-2/how-to/guide-convert-cn-to-ww-rom-26-08-t3961042
And was saved by cyber Jesus: JazonX
Thanks for the assistance!
Click to expand...
Click to collapse
Hey, when you ran the flashall_AFT.cmd did it run forvere? Did you ever get a complete message or your phone to reboot? I am trying to downgrade just the same, and I cannot ever get that raw file to flash over. Now my image is corrupt and I cant boot the phone, thank goodness I made backups, but still I cannot seem to flash the phone no matter what.
MrKioFLow said:
Hey, when you ran the flashall_AFT.cmd did it run forvere? Did you ever get a complete message or your phone to reboot? I am trying to downgrade just the same, and I cannot ever get that raw file to flash over. Now my image is corrupt and I cant boot the phone, thank goodness I made backups, but still I cannot seem to flash the phone no matter what.
Click to expand...
Click to collapse
My phone was at android 10 beta when I did these steps:
Tried running the bootloader unlocker and it gave me an error (I ignored it and continued)
I activated devmode for usb debugging (tapping 5 times on build #)
Made sure I allowed my pc to use debug mode (by tapping the always allow porompt)
I already had the google drives installed
I downloaded this file (which is linked in the post)
https://drive.google.com/file/d/1Y1ey0TOWq0pW1Qid7yqy83i0TqLYgwKR/view
Extracted it on my pc desktop (anywhere in a fresh document)
Rebooted my phone in bootloader
Connected my rog 2 to my pc using the side usb (***Important to do not plug it in the bottom usb***)
Ran flashall_aft.cmd and after about 8m - 10m it rebooted, forced me to do a factory reset
Then the phone was all good
If you did all the steps above and it's still not working then sorry I'm more of a "follow guides" kinda guy so my knoledge on the matter is pretty limited
SirGoldenTaco said:
My phone was at android 10 beta when I did these steps:
Tried running the bootloader unlocker and it gave me an error (I ignored it and continued)
I activated devmode for usb debugging (tapping 5 times on build #)
Made sure I allowed my pc to use debug mode (by tapping the always allow porompt)
I already had the google drives installed
I downloaded this file (which is linked in the post)
https://drive.google.com/file/d/1Y1ey0TOWq0pW1Qid7yqy83i0TqLYgwKR/view
Extracted it on my pc desktop (anywhere in a fresh document)
Rebooted my phone in bootloader
Connected my rog 2 to my pc using the side usb (***Important to do not plug it in the bottom usb***)
Ran flashall_aft.cmd and after about 8m - 10m it rebooted, forced me to do a factory reset
Then the phone was all good
If you did all the steps above and it's still not working then sorry I'm more of a "follow guides" kinda guy so my knoledge on the matter is pretty limited
Click to expand...
Click to collapse
Thank you for your help, apparently the USB hub I was using was had horrible transfer rates, and so even in 45 minutes nothing was finished copying over. Went directly to the USB on my pc and everything ran wonderfully! Thank you again!
MrKioFLow said:
Thank you for your help, apparently the USB hub I was using was had horrible transfer rates, and so even in 45 minutes nothing was finished copying over. Went directly to the USB on my pc and everything ran wonderfully! Thank you again!
Click to expand...
Click to collapse
You should be really careful about using USB hubs, for anything flashing related or if you are transferring a file without a checksum I would highly recommend going direct to a normal USB port.