Database Develop

Fastboot flash failed: error too many links

trmacdonal said:
How to Restore your phone on a Windows PC using a Nandroid backup
I am going to assume you already have a Nandroid backup created on your SD card using JF 1.31's recovery Alt-B feature. The backup will create a folder called nandroid on your SD.
What you need:
The Android SDK:
Fastboot Windows Binary in this post:http://forum.xda-developers.com/showpost.php?p=3083753&postcount=1
From your Nandroid backup you need three files:
data.img
system.img
boot.img
Steps to restore your phone
1) Put the files Adb and AdbWinApi.dll from the tools folder in the Android SDK into C:\WINDOWS\System32 folder on your PC. Substitute the correct drive letter if windows is not installed on you C: drive
2) Put the Windows Fastboot.exe into the C:\WINDOWS\System32 folder on your PC
3) Create a folder on the C: drive of your PC called android. The path should be C:\Android.
4) Copy the Nandroid backup files data.img, system.img, and boot.img from your SD card to the folder called Android you created by mounting your SD card as removable disk.
5) Unplug the USB cord and power off your phone
6) Power up your phone by holding CAMERA+POWER, you should see three androids on skateboards. If you don't see this go install the Engineering boot loader
7) Plug the USB cord back into your phone and press back. The screen on your phone should say fastboot.
8) Make sure your pc is using the correct driver. Open the device manager on your pc. It is helpfull to have all other USB storage devices besides your phone unplugged for this part. Look for a USB Mass Storage device in the list of the USB devices. Right click on it and update the driver. Pick the option to browse for a driver on your pc. The driver is located in the Android SDK your downloaded in the folder called usb_driver. If this is done right you will now see a device called HTC Dream
9) Press start, go to run and type cmd (If you are on Vista just type cmd in the search box and hit enter). The command prompt will pop up.
10) Type cd C:\android
then enter the following commands:
fastboot flash system system.img
it will say Sending, then writing and say OKAY if it was successful
then type
fastboot flash userdata data.img
wait for the second OKAY and type
fastboot flash boot boot.img
wait for the second OKAY and type
fastboot reboot
Your phone should now be restored exactly as you had it when it was backed up.
Click to expand...
Click to collapse
I'm young yet in my android/linux learnings and this guide here is great. I've been soaking in information for weeks now on the boards but still, my kungfu is weak.
Hence I'm having an issue today and I've been working on it almost all day so far. Something happened and I ended up having to factory restore my phone and I'm attempting to recover from my nandroid backup files.
I've followed the above instructions to the letter, but now that I'm ready to do the actual fastboot flash system system.img command, I keep getting a "FAILED <command write failed <Too many links>> error". And I've searched high & low looking for a solution to this.
My HTC is correctly running in Fastboot as an ADB Interface in WinXP Pro SP3, I've got my nandroid backup files placed in the C:\Android folder on my pc as directed. Fastboot is in the /system32 folder (and in cmd Fastboot devices lists my phone), but I keep banging my head into this error over & over. Its driving me pretty insane and any help would be appreciated. I know you guys aren't a support desk and I'm probably screwing up something elementary, but I just wanted to say that I'm finally asking as a last resort. I've been trying to figure this out myself for about 9 hours now. My thanks in advance.

Xeroproject said:
I've followed the above instructions to the letter, but now that I'm ready to do the actual fastboot flash system system.img command, I keep getting a "FAILED <command write failed <Too many links>> error". And I've searched high & low looking for a solution to this.
Click to expand...
Click to collapse
If it transfers the image to the phone but aborts halfway or at the end, try adding a ferrite core to your usb cable at the host side, or use one with an integrated ferrite core.
Unfortunately we don't have the source to the SPL so I'm mostly clueless what the "too many links" error means. Alternatively, try on a different pc.

infernix said:
If it transfers the image to the phone but aborts halfway or at the end, try adding a ferrite core to your usb cable at the host side, or use one with an integrated ferrite core.
Unfortunately we don't have the source to the SPL so I'm mostly clueless what the "too many links" error means. Alternatively, try on a different pc.
Click to expand...
Click to collapse
Thanks for the suggestion, I'll have to see if I can find a suitable USB cable, although from some inquires to linux buddies more in the know, I was told it was indicating a "a circular reference symlink" either in fastboot or in the command I used.
Considering I used exactly the commands in the guide, I'm puzzled. Also, I pulled the fastboot.exe for win32 from JF's own attachment.
Regarding another PC, yes, that would be ideal for troubleshooting this, however the pc I have at home is Vista 64bit (unfortunately), so shouldn't I run into issues there?

Xeroproject said:
Hrm, sorry about the few posts in here mods, it seems my issue isn't related to a mistype in the command line of trmacdonal's guide like I thought it was, so its most likely not related to this thread & needs to be split into a separate thread to prevent clutter.
I have noticed something regarding my situation: in command line when I type "fastboot devices" it recognizes & lists my phone. However when I type "adb devices" it does not list my phone. Might this be related?
Click to expand...
Click to collapse
ADB won't see your device till it has booted into android.
And send me a PM with the post numbers and a new thread title and I will move your posts and any posts related to them.

So unfortunately getting any work done on this on my Vista machine has been a total no-go. Vista won't take the 64-bit homebrewed driver, regardless of disabling driver authentication.
So I'm stuck. Day 2 here and I still get the "too many links" error. I've since retraced all my steps, redownloaded the SDK, JF's fastboot-win32, and completely removed all drivers from the system (including registry entiries) then reinstalled everything, and tried a shielded USB cable today. Still pulling up that error.
Is there any information I can include that would help pinpoint whats causing this issue?

Xeroproject said:
So unfortunately getting any work done on this on my Vista machine has been a total no-go. Vista won't take the 64-bit homebrewed driver, regardless of disabling driver authentication.
So I'm stuck. Day 2 here and I still get the "too many links" error. I've since retraced all my steps, redownloaded the SDK, JF's fastboot-win32, and completely removed all drivers from the system (including registry entiries) then reinstalled everything, and tried a shielded USB cable today. Still pulling up that error.
Is there any information I can include that would help pinpoint whats causing this issue?
Click to expand...
Click to collapse
Have you tried booting normally at least once?
Maybe try "fastboot erase cache", then try again?

JesusFreke said:
Have you tried booting normally at least once?
Maybe try "fastboot erase cache", then try again?
Click to expand...
Click to collapse
If you mean booting normally into Vista 64, yes, it sees the G1 as an "unknown device" in Device Manager and when I point it to the 64-bit driver, it won't take it. Same for when driver auth is disabled. (although the message changes from "no device drivers found" to "this driver is not compatible with your device)
If you mean the phone, yes, the phone works, its not bricked, but there's a lot of data I'm losing if I can't solve this issue & backup from my nandroid backups.
I'll give the erase cache thing a shot now and post results, thanks for the suggestion.

interesting, the "fastboot erase cache" command also returns a "FAILED <status read failed <Too many links>>" error
Perhaps the problem is with the fastboot.exe file?

Xeroproject said:
interesting, the "fastboot erase cache" command also returns a "FAILED <status read failed <Too many links>>" error
Perhaps the problem is with the fastboot.exe file?
Click to expand...
Click to collapse
I doubt it. I remember seeing this error once when I stopped a fastboot flash while it was doing it's thing. I don't remember exactly what I did to fix it. I thought I just rebooted or something.
It's a shot in the dark, but maybe take the battery out for a few seconds and put it back in and try again?
I would also try any and all of the fastboot commands
If nothing else, you could try reflashing the engineering SPL, or even the RC29 nbh.

JesusFreke said:
I doubt it. I remember seeing this error once when I stopped a fastboot flash while it was doing it's thing. I don't remember exactly what I did to fix it. I thought I just rebooted or something.
It's a shot in the dark, but maybe take the battery out for a few seconds and put it back in and try again?
I would also try any and all of the fastboot commands
If nothing else, you could try reflashing the engineering SPL, or even the RC29 nbh.
Click to expand...
Click to collapse
Yeah, I wish I knew the cause of it, but the initial use was uninterrupted (and everytime I reboot, I will get 5-10sec lag before getting the error, while after that the error will popup immediately)
I'm happy to try any of the fastboot commands, but being a little nubbin, I'm a little afraid of doing any damage. I did try fastboot reboot and fastboot reboot-bootloader and got no response from the phone. "fastboot devices" immediately sees my phone. "fastboot flashall" returns: "error: neither -p product specified nor ANDROID_PRODUCT_OUT set".
Removing the battery is something I've done a couple times the other day, just gave it another shot now, same result. I've noticed the too many links error will say it "failed to read" on the first attempt, after that it reverts to "failed to write".
Concerning reloading the phone back to RC29....you mean taking it back to RC29, then reflashing the Engineering SPL, then immediately trying to backup from my nandroid backups? (prior to installing any of the JF OS versions?)

I have also faced this error few time, what I do is disconnect the USB, restart both PC and G1, next time I get proper connection, once time I was able to resolve just by moving the ramdisk.img and kernel file from the directory, this was when I was using the fastboot -w flashall command!!
-Pramod

Might be onto something there JF, I just checked my SPL edition and I'm running the HardSPL not the EngineSPL.
Is the HardSPL not suited for this perhaps?

for fastboot -w flashall to work you need to set the ANDROID_PRODUCT_OUT variable, where boot.img, recovery.img and system.img file are, on window just use the set command
set ANDROID_PRODUCT_OUT=c:\<your directory where the files are>
and then run fastboot -w flashall
-Pramod

pramods said:
for fastboot -w flashall to work you need to set the ANDROID_PRODUCT_OUT variable, where boot.img, recovery.img and system.img file are, on window just use the set command
set ANDROID_PRODUCT_OUT=c:\<your directory where the files are>
and then run fastboot -w flashall
-Pramod
Click to expand...
Click to collapse
Alright, I'm with you, just returned "error: could not load android-info.txt"

The same directory also need to have android-info.txt file, this file just have a single entry as board=trout in it, if you don't have it create this file and then run fastboot again
-Pramod

pramods said:
The same directory also need to have android-info.txt file, this file just have a single entry as board=trout in it, if you don't have it create this file and then run fastboot again
-Pramod
Click to expand...
Click to collapse
Alright, so I did a search on my computer to see if I had an android-info.txt I could copy over, didn't have anything (including in the android-sdk files). So I went ahead and created one and just put "board=trout" in it like you said. New error: "getvar:version-bootloader FAILED <command write failed <Too many links>>"
Progress?
btw Pramod, you're a stud, thank you for all these suggestions

Xeroproject said:
I've noticed the too many links error will say it "failed to read" on the first attempt, after that it reverts to "failed to write"./QUOTE]
Do you mean on the first attempt after a reboot?
This makes me suspect usb issues. Do you happen to have any usb cords with a ferrite bead on them laying around that you could try?
Reboot, and then try flashing one of the splash images. They are relatively small, so if it is an issue with usb communication, there is less of a chance of it failing. Try it a couple of times.. if you can get it to work once, then I would say it's more than likely some sort of usb communication issue, bad cable, interference, etc.
Click to expand...
Click to collapse

JesusFreke said:
Xeroproject said:
I've noticed the too many links error will say it "failed to read" on the first attempt, after that it reverts to "failed to write"./QUOTE]
Do you mean on the first attempt after a reboot?
This makes me suspect usb issues. Do you happen to have any usb cords with a ferrite bead on them laying around that you could try?
Reboot, and then try flashing one of the splash images. They are relatively small, so if it is an issue with usb communication, there is less of a chance of it failing. Try it a couple of times.. if you can get it to work once, then I would say it's more than likely some sort of usb communication issue, bad cable, interference, etc.
Click to expand...
Click to collapse
Yeah, the first attempt after a reboot.
Yeah I actually picked a ferrite bead USB cable up the other day and then I also shut off my speakers (just in case a magnet or something was causing interference). Just checking around my desk at work, I don't really have anything else that would interfere to my knowledge. We deal with high speed check scanners at work and I haven't had any issues with the images they pull (also via USB, same computer).
I'll give the image deal a whirl, I believe I have all that software for converting them already on my computer.
Click to expand...
Click to collapse

Just try one more thing, creat a new directory and put all *.img files and *.txt file there and reboot your system(PC and G1[fastboot mode]) then set the ANDROID_PRODUCT_OUT variable and then fire the command fastboot devices , if the fastboot return the device identity then try fastboot -w flashall command
-Pramod

pramods said:
Just try one more thing, creat a new directory and put all *.img files and *.txt file there and reboot your system(PC and G1[fastboot mode]) then set the ANDROID_PRODUCT_OUT variable and then fire the command fastboot devices , if the fastboot return the device identity then try fastboot -w flashall command
-Pramod
Click to expand...
Click to collapse
All *img & *txt files off the SD card you mean?

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

How-To: Fix Faulty Baseband and Faulty Modem

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 method​Prerequisites: 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 method​Prerequisites: 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

Kindle Fire HD 7" Stuck on Splash Screen [No Mods]

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

[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