I try to use the new version of Heimdall but when starting to flash I had the following error:
Code:
Heimdall v1.3.0, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -3
Is there anybody that could explain the problem ?
However my SGS-2 is detect in the utilities tab.
Thanks for your answers.
Django313 said:
I try to use the new version of Heimdall but when starting to flash I had the following error:
Code:
Heimdall v1.3.0, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -3
Is there anybody that could explain the problem ?
However my SGS-2 is detect in the utilities tab.
Thanks for your answers.
Click to expand...
Click to collapse
Heimdall is flashing software? Why not use Odin?
As far as I understand Heimdall is for use on Galaxy S, not S2.
theo80 said:
Heimdall is flashing software? Why not use Odin?
As far as I understand Heimdall is for use on Galaxy S, not S2.
Click to expand...
Click to collapse
Because Heimdall is stable, reliable, open-source, cross-platform, allows for a large degree of flashing freedom and is guaranteed to be legal. None of these are true for Odin. Although not necessarily overly important Heimdall also flashes substantially faster.
Also as of 1.3.0 Heimdall Frontend now supports Heimdall Firmware Packages, which are by far a superior than attempting to flash several description-less tar archives with Odin.
EDIT: Heimdall works with all Galaxy S devices, except the Droid Charge, which we've had difficulties with. Which is another advantage over Odin; one version of Heimdall works with all devices so there's less confusion about versions.
Django313 said:
I try to use the new version of Heimdall but when starting to flash I had the following error:
Code:
Heimdall v1.3.0, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -3
Is there anybody that could explain the problem ?
However my SGS-2 is detect in the utilities tab.
Thanks for your answers.
Click to expand...
Click to collapse
What OS are you running? If it's Windows make sure you follow the README and install the drivers.
@Benjamin Dobell
Yes, I use heimdall 1.3.0 on Kubuntu 11.04.
I read your e-mail and I try to launch Heimdall with sudo and it works !
but it's finished bad, resulting in a "half-bricked" SGS-2.
the flash of the datafs partition, when reaching 100% freeze and heimdall sent the error that it couldn't load datafs. ending the session...
I try twice flashing my phone:
- one with my own built heimdall-firmware-packages
- the other was custom flashing.
both failed.
The third flashing I made with odin in a virtualbox, and succeeded.
here is the results when launching Heimdall in a terminal :
Code:
[email protected]:~$ sudo heimdall-frontend
[sudo] password for didier:
Error: "/var/tmp/kdecache-didier" is owned by uid 1000 instead of uid 0.
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun fichier ou dossier de ce type
QFileSystemWatcher: failed to add paths: /home/didier/.config/ibus/bus
KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work
Error: "/tmp/kde-didier" is owned by uid 1000 instead of uid 0.
Error: "/tmp/ksocket-didier" is owned by uid 1000 instead of uid 0.
kdeinit4: Shutting down running client.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Error: "/tmp/ksocket-didier" is owned by uid 1000 instead of uid 0.
Error: "/tmp/kde-didier" is owned by uid 1000 instead of uid 0.
Error: "/var/tmp/kdecache-didier" is owned by uid 1000 instead of uid 0.
kbuildsycoca4 running...
Error: "/var/tmp/kdecache-didier" is owned by uid 1000 instead of uid 0.
Error: "/var/tmp/kdecache-didier" is owned by uid 1000 instead of uid 0.
Error: "/var/tmp/kdecache-didier" is owned by uid 1000 instead of uid 0.
Error: "/tmp/ksocket-didier" is owned by uid 1000 instead of uid 0.
Error: "/var/tmp/kdecache-didier" is owned by uid 1000 instead of uid 0.
[email protected]:~$
Django313 said:
@Benjamin Dobell
Yes, I use heimdall 1.3.0 on Kubuntu 11.04.
I read your e-mail and I try to launch Heimdall with sudo and it works !
but it's finished bad, resulting in a "half-bricked" SGS-2.
the flash of the datafs partition, when reaching 100% freeze and heimdall sent the error that it couldn't load datafs. ending the session...
I try twice flashing my phone:
- one with my own built heimdall-firmware-packages
- the other was custom flashing.
both failed.
Click to expand...
Click to collapse
In regards to sudo permissions being required, I just did a bit of searching and I found some information (although it may have been old) that Kubuntu's udev rules are in a different location to Ubuntu's. I also found separate information indicating that Kubuntu is using an outdated udev rules specification. Either of these two things would cause the -3 permissions error without running Heimdall as a super user.
Do you know exactly what the error was you received from Heimdall when flashing failed? The output from Heimdall Frontend only contains the permissions errors and aren't related to the flashing process. When you use Heimdall Frontend, Heimdall's output is displayed in "Status" section of the "Flash" tab so that it can easily be copy and paste.
By the way if your phone gets stuck in a "half-bricked" state again then it can usually be fixed by going to the "Utilities" tab and running the "Close PC Screen" action. This doesn't repair any corrupted files on device (if there are any). This literally just tells the phone that it should at least try boot up, instead of displaying the phone <--> PC screen.
Help please
trying to run heimdall 1.3.0 on Mac OS 10.5.8, I have qt/xcode installed, still doesn't seem to work. everytime i run frontend and try to detect my device (samsung captivate)or save my .pit file I get "FRONTEND ERROR Heimdall crash"
Any suggestions ?
ERROR: Failed to access device. libusb error: -12
Win7 x64
Installed drivers:
Heimdall v1.3.0, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Beginning session...
Handshaking with Loke...
Uploading PITERROR: Failed to send end session packet!
ERROR: Failed to send file part packet!
PIT upload failed!
Ending session...
Odin works, back to odin.
Problem with heimdall on mac 0s 10.5.8
Crappyvate said:
trying to run heimdall 1.3.0 on Mac OS 10.5.8, I have qt/xcode installed, still doesn't seem to work. everytime i run frontend and try to detect my device (samsung captivate)or save my .pit file I get "FRONTEND ERROR Heimdall crash"
Any suggestions ?
Click to expand...
Click to collapse
@benjamin
Problem solved after updating to osx 10.6
there seem to be issues between Heimdall 1.3 on Leopard 10.5 and certain binaries. Heimdall command line does not execute and just crashes.
I'm getting a similar error on Arch Linux running Heimdall v1.3.0 with my Fascinate:
Code:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: 4
I do have the proper udev rules in place:
Code:
$ lsusb | grep Samsung
Bus 002 Device 068: ID 04e8:6601 Samsung Electronics Co., Ltd Mobile Phone
I couldn't get Heimdall to even detect the device on my MacBook Pro running 10.6.8. I don't have access to a Windows machine to do further testing, and have had a lot of issues trying to update pretty much anything on my phone after I rooted and put a Superclean ROM on a few months ago. Here's my current setup: pastie.org/2358372
Today I tried to flash my SGS-II with heimdall 1.3.0 on Linux Kubuntu 11.04.
I used the latest firmware XXKH3 and it failed as it did with the firmware XXKG6 few weeks ago. Just after it downloaded the file "datafs" it freeze resulting in a half-bricked phone.
Certainly there is a bug in heimdall at this point because all the others files are correctly downloaded.
the question is : why ?
I'm on Mac OsX 10.6.8, and after tried to flash my firmware using the downloaded PIT from my device, Heimdall told me that there were an error with libusb while it was trying to upload the PIT.
My SGS got semi-bricked, and after putting it to download mode again and unchecking Repartition in Heimdall, everything was fine with the flashing.
So, the question is... is there a bug with repartitioning? is it possible to use my device's PIT to repartition?
Need new bootloader for EPIC? How do I tell?
All, I picked up an EPIC from someone and they put DK28 on it which is a bit of a dead end. All searches turned up needing Odin and I don't have a Windows box. I then found Heimdall and then this thread here:
http://forum.xda-developers.com/showthread.php?t=1353310
This all looks promising but then I've read where I need to update the bootloader if I'm using a Mac. My question is, with an EPIC of somewhat unknown past, how do I know if I have the right bootloader on it? DK28 is the leaked Froyo that never got OTA'd. I want to get this EPIC back onto the OTA track so it can get Gingerbread. I've found CWM flashable images but the modem seems to be the biggest struggle. Of course, if Heimdall works, the thread above looks like it will get me all that I want.
So if anyone can help and tell me how to figure out if I've got the right bootloader and won't get the black screen problem, that would be cool.
thanks peterb
Need some help please
My device got messed up and I know nothing about using Linux or fixing partitions with ADB, I have the partition tables I need to fix it but I have no clue and no one in our community knows how to change the "head" sectors from four to ONE. Please this is my partition list from heimdal
Entry Count: 14
Unknown 1: 15718400
Unknown 2: 1
Unknown 3: 0
Unknown 4: 0
Unknown 5: 7703
Unknown 6: 237
Unknown 7: 62704
Unknown 8: 18
--- Entry #0 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 1
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 0
Unknown 3: 0
Partition Name: IBL+PBL
Filename: boot.bin
--- Entry #1 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 2
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 0
Unknown 3: 0
Partition Name: PIT
Filename: YPG70_8G-0304.pit
--- Entry #2 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 3
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL
Filename: Sbl.bin
--- Entry #3 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 4
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 6226025
Unknown 3: 7143533
Partition Name: SBL2
Filename: Sbl.bin
--- Entry #4 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 5
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 20
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
--- Entry #5 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 6
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 40
Unknown 2: 39021280
Unknown 3: 7143533
Partition Name: EFS
Filename: efs.rfs
--- Entry #6 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 7
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 36662408
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage
--- Entry #7 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 8
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 6684793
Unknown 3: 3014771
Partition Name: RECOVERY
Filename: zImage
--- Entry #8 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 9
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1160
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.rfs
--- Entry #9 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 10
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 536
Unknown 2: 6684780
Unknown 3: 115
Partition Name: DBDATAFS
Filename: dbdata.rfs
--- Entry #10 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 11
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 256
Unknown 2: 115
Unknown 3: 115
Partition Name: CACHE
Filename: cache.rfs
--- Entry #11 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 12
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 7696
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: datafs.rfs
--- Entry #12 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 13
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 20516
Unknown 2: 0
Unknown 3: 0
Partition Name: USERFS
Filename: userfs_8G.rfs
--- Entry #13 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 0
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: GANG
Filename: inand_8G.bin
Ending session...
Rebooting device...
Heyo guys, idk if this can be seen as somehow relate to this topic, cuz its a diff problem with heimdall than originally mentioned in this thread, but my problem is that while trying to flash twrp, my sm-a750fn got half-bricked, and odin didnt want to flash the phones stock ROM, beeing stuck at establishing a connection, so i went and tried to flash it via heimdall-frontend, without sudo cuz else id have issues with the pit not beeing recognised, and everytime i try to flash smth, no matter what .img, be it recovery, boot, misc, etc, heimdall gets stuck at 93% and later gets a fail msg:
"Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Donate | Glass Echidna
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
0%
1%
2%
3%
4%
5%
[...]
80%
81%
82%
83%
84%
85%
86%
87%
88%
89%
90%
91%
92%
93%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOT upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface..."
The phone also shows like bout 45% of progress:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
Process Index:0
please select the XML file
Start Download
COM Port number:4
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Ack Raw Data:False
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:4
Sending NOP
FireHose NOP sent successfully
Sending Configuration
Device Type:eMMC
Platform:8x26
Set TxBuffer 0x4000, RxBuffer 0x4000
Firehose configure packet sent successfully!
Total Bytes To Program 0x102A2A0
Download Image
PROGRAM: Partition 0, Sector: 0, Length: 33 Sectors, Sector Size: 512 Bytes
File: C:\unbrick\gpt_backup0.bin
PROGRAM: Written Bytes 0x4200 (64)
Program Size: 0.02 MB
PROGRAM: Partition 0, Sector: 0, Length: 34 Sectors, Sector Size: 512 Bytes
File: C:\unbrick\gpt_main0.bin
PROGRAM: Written Bytes 0x4400 (64)
Program Size: 0.02 MB
PROGRAM: Replace the partition sectors number 0xc000 to file size in sector 0x7134
PROGRAM: Partition 0, Sector: 93184, Length: 28980 Sectors, Sector Size: 512 Bytes
File: C:\unbrick\laf.img
PROGRAM: Written Bytes 0xe26800 (64)
Program Size: 14.15 MB
PROGRAM: Replace the partition sectors number 0x1000 to file size in sector 0x7d9
PROGRAM: Partition 0, Sector: 5120, Length: 2009 Sectors, Sector Size: 512 Bytes
File: C:\unbrick\emmc_appsboot.mbn
PROGRAM: Written Bytes 0xfb200 (64)
Program Size: 0.98 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x12f
PROGRAM: Partition 0, Sector: 4096, Length: 303 Sectors, Sector Size: 512 Bytes
File: C:\unbrick\rpm.mbn
PROGRAM: Written Bytes 0x25e00 (64)
Program Size: 0.15 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x70
PROGRAM: Partition 0, Sector: 3072, Length: 112 Sectors, Sector Size: 512 Bytes
File: C:\unbrick\hyp.mbn
PROGRAM: Written Bytes 0xe000 (64)
Program Size: 0.05 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x3b1
PROGRAM: Partition 0, Sector: 2048, Length: 945 Sectors, Sector Size: 512 Bytes
File: C:\unbrick\tz.mbn
PROGRAM: Written Bytes 0x76200 (64)
Program Size: 0.46 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x2b1
PROGRAM: Partition 0, Sector: 1024, Length: 689 Sectors, Sector Size: 512 Bytes
File: C:\unbrick\sbl1.mbn
PROGRAM: Written Bytes 0x56200 (64)
Program Size: 0.34 MB
Total Size: 16.16 MB
Total Size: 1 Seconds
Throughput: 16.16 MB/Seconds
PATCH: Partition 0, Sector: 11, Offset 296 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 0, Offset 296 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 1, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 0, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 1, Offset 32 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
PATCH: Partition 0, Sector: 0, Offset 24 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
PATCH: Partition 0, Sector: 0, Offset 72 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-33.
PATCH: Partition 0, Sector: 1, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(2,5120)
PATCH: Partition 0, Sector: 0, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-33.,5120)
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: 0
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(1,92)
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: 0
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-1.,92)
Total download file size: 16.16455MB
Throughput: 16.16455M/s
Reset Phone
Waiting for reset done...
Finish Download
Successful unbrick LG LS770 9008 mode
Use QFIL to flash the LS770 recovery file, it works on LS770 with ZV5 only. If you hard bricked at LS770ZV5, then you can unbrick it by flashing the recovery file with QFIL
emmc_appsboot.mbn
gpt_backup0.bin
gpt_both0.bin
gpt_main0.bin
hyp.mbn
laf.img
MPRG8916.mbn
New9008.zip
old_prog_emmc_firehose_8916.mbn
partition-c70n_global_com.xml
patch0.xml
prog_emmc_firehose_8916.mbn
rawprogram0.xml
rpm.mbn
sbl1.mbn
tz.mbn
validated_emmc_firehose_8916.mbn
asialove2013 said:
Hi, I am trying to find out how to unbrick a G Stylo LS770 stuck on Qualcomm HS-USB QDLoader 9008 mode.
First, I need to get the rawprogram0.xml for G Stylo LS770..
from a rooted working LS770 model:
Code:
adb shell su -c 'dd if=/dev/block/mmcblk0 of=/cache/partition0.bin bs=512 count=20480'
Get partition0.bin
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
00 04 00 is sbl1 -Start LBA
00 07 FF is sbl1 - end LBA
In the original Boarddiag tool, there are rawprogram0.xml file for other LG models.
I have to edit it based on the information from partition file i just got.
below entry is what i create based on partition table
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="sbl1.mbn" label="sbl1" num_partition_sectors="1024" physical_partition_number="0" size_in_KB="512.0" sparse="false" start_byte_hex="0x80000" start_sector="1024" />
num_partition_sectors: End LBA- start LBA+1 = 400, Convert it to HEX, that is 1024
start_sector = Start LBA, and convert it to HEX, that is 1024.
start_byte_hex : 1024*512= 524288 convert to hex, it is 80000
Now we have the rawprogram0.xml
---
Forgive my bad English,..(
Click to expand...
Click to collapse
wheres the rawprogram can you share it with me ?
---------- Post added at 03:13 PM ---------- Previous post was at 03:01 PM ----------
jcsaclolo said:
wheres the rawprogram can you share it with me ?
Click to expand...
Click to collapse
hello i got bricked LG LS770 ZV7 it is hard bricked and stuck on QDLoader 9008 i need tot firmware DLL and xml files if you can help me unbrick it im willing to pay just give me step by step instructions. Im not tech savvy willing to pay 100$ to 150$ depend on situation i am very upset about this so i would thank you a lot and pay you if you could really help me please email me at [email protected].com
No need DLL
jcsaclolo said:
wheres the rawprogram can you share it with me ?
---------- Post added at 03:13 PM ---------- Previous post was at 03:01 PM ----------
hello i got bricked LG LS770 ZV7 it is hard bricked and stuck on QDLoader 9008 i need tot firmware DLL and xml files if you can help me unbrick it im willing to pay just give me step by step instructions. Im not tech savvy willing to pay 100$ to 150$ depend on situation i am very upset about this so i would thank you a lot and pay you if you could really help me please email me at [email protected]
Click to expand...
Click to collapse
Just start working on this. I know you! We have been talking about the LS770 QDLoader 9008 issue for almost 30 days.
No need DLL, I am just trying to use LG's official smart boot diag tool to solve this, I will let you know when i got further information.
Successful GOT My LS770 back from Qualcomm HS-USB QDLoader 9008 mode.
now in download mode,
ZV5 is fine,
But ZV7 has Qufse check fail error,
asialove2013 said:
Successful GOT My LS770 back from Qualcomm HS-USB QDLoader 9008 mode.
now in download mode,
ZV5 is fine,
But ZV7 has Qufse check fail error,
Click to expand...
Click to collapse
Could you please post the files you used to do so?
jcsaclolo said:
wheres the rawprogram can you share it with me ?
---------- Post added at 03:13 PM ---------- Previous post was at 03:01 PM ----------
hello i got bricked LG LS770 ZV7 it is hard bricked and stuck on QDLoader 9008 i need tot firmware DLL and xml files if you can help me unbrick it im willing to pay just give me step by step instructions. Im not tech savvy willing to pay 100$ to 150$ depend on situation i am very upset about this so i would thank you a lot and pay you if you could really help me please email me at [email protected]
Click to expand...
Click to collapse
Do you have the ZV5 tot file? What was the final outcome of flashing back to ZV5 from ZV7?
I would like to get a copy of zv5, so how can I get that? Thank you
another try
All LG G Stylo use 8X26, SEE Screen shot below
no way
Sorry, can not share the file!
I am working on it.
I will share as I success
Sent from my XT1093 using XDA-Developers mobile app
asialove2013 said:
Not free! It is no shame to share free kdz firmware, I have share lots of G5, V10, G4, G3, K10, firmware.
I do not share LG G5 H850 TOT firmware because it was build by some developers at xda.
I do not share LG LS770 tot because it was build by others too.
Some one said that it should be free, but you can never get it from AT & T or Sprint,
I noticed you (Wired66) shared other developers ls770 firmware and making profit from it?
So I will never share files to unbrick Quancomm 9008 mode, SORRY
Click to expand...
Click to collapse
Are you okay, really? You know the code in those .TOT files is owned by LG right. Making a tot file is just copy and pasting someone else's work. It does not make it yours no matter how much you want it to be.
And no i'm not in the business of selling big corporations code, where the heck did you pull that out of.
This is your thread you can argue with whoever unwittingly post in it, but I'm out.
sorry
Wired66 said:
Are you okay, really? You know the code in those .TOT files is owned by LG right. Making a tot file is just copy and pasting someone else's work. It does not make it yours no matter how much you want it to be.
And no i'm not in the business of selling big corporations code, where the heck did you pull that out of.
This is your thread you can argue with whoever unwittingly post in it, but I'm out.
Click to expand...
Click to collapse
Sorry, It is my mistake, I mistake you with some one else
you are right
I am trying to edit my previous post,,
asialove2013 said:
Sorry, It is my mistake, I mistake you with some one else
Click to expand...
Click to collapse
No hard feelings, on my part.
I'm taking a stab at throwing together some .TOT files on my own. I should have at least one that I'm throwing together for the LS-770 here later today. I'll post them here on XDA as the community really could use them. If you change your mind about posting those files I would have three other phones to test them out on that I bricked poking at this locked bootloader.
Please do a tot file for for boost stylo zv5 (5.11).Thanks!!
Sent from my N9521 using Tapatalk
please help me for how repair LG G Stylo LS770 Unbrick MSM8916 fast
thank you
After researching, and waiting months for a .tot file to come out, I have successfully fixed my LS770 Boost Mobile Stylo. I kinda missed this thing. I'll help anyone who needs it. I WILL NOT charge, either. Ain't Android suppose to be Open Source? Then lets keep it 'Open'
mabry said:
After researching, and waiting months for a .tot file to come out, I have successfully fixed my LS770 Boost Mobile Stylo. I kinda missed this thing. I'll help anyone who needs it. I WILL NOT charge, either. Ain't Android suppose to be Open Source? Then lets keep it 'Open'
Click to expand...
Click to collapse
I am trying to find a ZV5 tot, if you can help, thanks. Also if you understand quse, how can I understand flashing and qfuse, thanks
mabry said:
After researching, and waiting months for a .tot file to come out, I have successfully fixed my LS770 Boost Mobile Stylo. I kinda missed this thing. I'll help anyone who needs it. I WILL NOT charge, either. Ain't Android suppose to be Open Source? Then lets keep it 'Open'
Click to expand...
Click to collapse
You were in QDLoader Mode? I could really use the files to debrick some phones. I got as far as getting to a download mode with a black screen and a battery symbol before I put the battery back in but nothing flashes and then upon reboot I'm back to QDloader mode. I must have one of the files off.
jcsaclolo said:
wheres the rawprogram can you share it with me ?
---------- Post added at 03:13 PM ---------- Previous post was at 03:01 PM ----------
hello i got bricked LG LS770 ZV7 it is hard bricked and stuck on QDLoader 9008 i need tot firmware DLL and xml files if you can help me unbrick it im willing to pay just give me step by step instructions. Im not tech savvy willing to pay 100$ to 150$ depend on situation i am very upset about this so i would thank you a lot and pay you if you could really help me please email me at [email protected]
Click to expand...
Click to collapse
can u help my lg ls770zv7 don't pass from lg screen it's on 6.0 android
mabry said:
After researching, and waiting months for a .tot file to come out, I have successfully fixed my LS770 Boost Mobile Stylo. I kinda missed this thing. I'll help anyone who needs it. I WILL NOT charge, either. Ain't Android suppose to be Open Source? Then lets keep it 'Open'
Click to expand...
Click to collapse
would like help in fixing my lg g stylo I'm stuck in QUALCOMM hs-usb qdloader 9008 after using the lg up tool to flash zv7 tot I had forgothen the bloody device updated itself to zv8, so I was playing around with kingoroot managed to delete the recovery wihich in part enables fastboot mode. after failing to input commads I decided to flash back and now qfuse screws me over. help would be appreciated.