I have LG G3 STYLUS SYSTEM.IMG AND BOOT-RAMDISK topic

I have lg g3 stylus system.img and boot-ramdisk
who can transplant for a110q

[Help] Nexus 7 refuses to flash system.img in fastboot topic

Hey all,

A little background: I was a little late to the Lollipop scene, and seeing as my phone wasn't getting an update anytime soon, I thought I'd crack out my ol' Nexus 7 2012 Wifi-edition. This thing was running an old version of Paranoid Android and was pretty slow and unreliable, I'd assumed I'd flashed a bad kernel or made some bad configurations or something. I very promptly downloaded the Lollipop factory image, fired up fastboot and wiped the device and attempted to flash the image.

It didn't work. I then assumed the image was bad, so I figured, as I had done in the past for KitKat, I'd download an older image and just accept the OTA. Once again the image refused to flash. It got stuck at the bootloader every time, but stubborn as I am, I tried yet an older image. flashing different versions of Jellybean, I discovered that my Nexus 7 wouldn't take any bootloader version higher than 4.18, and that if the bootloader did flash, the system.img would fail.

The procedure for flashing went as follows:
1. Download and extract nakasi gzipped tar images
2. cd into the folder containing an image
3. run ./flash-all.sh, or extract the zip archive and manually erase partitions and flash the contained images

I noticed that the script wasn't working at all, so I took to manually flashing each image myself, and discovered that the issue usually occured with system.img and bootloader-group-x.xx.img

Note that I run an Arch Linux box, but also tried the equivalent to the above procedure using my other Windows machine, to no avail.

Looking for a solution to my problem. I'm running out of images to flash, and I have no way of transferring files to the tablet. I tried loading CWM so I could flash an unofficial image to get the thing booting, but I received errors when I tried to mount the USB storage.

Any and all help would be appreciated, I'm thinking this is a flash memory issue (i.e. one or more partitions is corrupt or formatted incorrectly), and I don't have the slightest clue how to fix it. Thanks!

[Q] Stuck at Sending system.img topic

Hello Guys,

Ok, I have been searching and searching, but cannot find the answer to my problem. I am using the LG G Watch Tool to return my watch to stock, then update it with the OTA provided in an update.zip

1) My bootloader is unlocked (LG Unlock icon at bottom)
2) My ROM was rooted

Everytime I connect the watch while it is in the bootloader, it is recognized by my PC and it says Fastboot. When the ROM did boot up, it would also be connected through ADB and showing on the list of connected devices.

Based on the screenshot below, I am able to erase the system image, but it gets stuck sending the system.img. Even when I try boot.img, or any other ADB command, it delays indefinitely.

Any thoughts?

Attached Thumbnails

 

[Q] Error when flashing system.img topic

Im currently following a guide to update my encrypted N6 to 5.0.1 and it is all working well up until i go to flash the system.img that i got from 5.0.1 where i get an error.

Code:

---

C:\Users\Chris\Desktop\android-sdk-windows\platform-tools>fastboot flash system
system.img
target reported max download size of 536870912 bytes
sending 'system' (457800 KB)...
OKAY [ 14.332s]
writing 'system'...
(bootloader) Invalid sparse image
FAILED (status read failed (Too many links))
finished. total time: 14.353s

---

Im not sure where to go from here, any tips?