Qualcomm HS-USB QDLoader 9008..... - LG G5 Questions & Answers
there any way to solve the problem, my G5 is in this state when the I installed a wrong firmware, the phone does not turn on .Qualcomm
I have same the Problem
Any help ??
Then you can not fix it. Programs that restore or overwrite the bootloader simply do not exist.
Or you can buy octopus box and he can probably flash the phone, but there is no guarantee that he will see the phone at all and it will be possible to do something with him
No chance, no soft for 810 and 820. You can only fix it with lg g2 on snap 800.
So only lg service can help.
Best chance is to send to lg repair service and play dumb about what happened.
What about my case lg service says my iemi isnt valid even though its on the side of the box. Lg wont warranty mine. Nm I called them and i pay shipping. And they will asscess the device for repair
Same problem here in Cali
thaifani said:
I have same the Problem
Any help ??
Click to expand...
Click to collapse
Did you finally figure out how to get your phone to work? I can't even get my phone into download mode.
RS988 phone hard bricked
teknokill said:
Did you finally figure out how to get your phone to work? I can't even get my phone into download mode.
Click to expand...
Click to collapse
No, but I believe a dumphfile from a rom can be used as in the LG V10 case applied by "Tungkick." Currently there is no such thing.
RS988 phone hard bricked
kacak11 said:
No, but I believe a dumphfile from a rom can be used as in the LG V10 case applied by "Tungkick." Currently there is no such thing.
Click to expand...
Click to collapse
https://forum.xda-developers.com/tm...ent/debrick-phone-h901-qualcomm-9008-t3440359
Can I return it?
kacak11 said:
https://forum.xda-developers.com/tm...ent/debrick-phone-h901-qualcomm-9008-t3440359
Click to expand...
Click to collapse
I know where I screwed up. I installed the rooted stock for a LG-H850 instead of the RS998 for the American unlocked version. I know my idea is kind of not being 100% truthful, but I was considering returning the phone to Best Buy, where I bought it at an amazing price of $250. I'm going to tell them that the phone locked up after doing a LG/Android security update. They won't be able to tell because it's dead. This way I can exchange it for the another one and don't have to pay $150 for a repair. Best Buy will just send the phone back and get a credit and LG will fix it for free and sell it again recouping all of the cost. It's only been 2 days since I purchased the phone, so I'm well within the return period. I did so much reading that after awhile the RS998 became a LG-H850. I thought they were the same phone.
Just a reminder to all Android Enthusiasts.....I know I the following has been said many times over and over in different ways by fellow members either by re-using important catch-phrases or similar syntax, so it is absolutely vital to develop and adopt a manifesto for yourself to follow while compiling procedures that matches the way you think and operate. Remember that we all strive to get the same end result, but our minds think in different ways and one person's methodology many times is only useful for people who think alike. We're all different and develop methodologies that suit ourselves over time, so a device tinkering manifesto to live by that suites your thought process will always be the best for you in the end. The following manifesto is what I will follow for now on and I will Always and I mean always do the following before tinkering:
I will always have a backup phone with me in case of emergency and I don't have the time to fix my phone right away. There is nothing safer than to allowing yourself to make a mistake and to still be able to have a phone in case of emergency.
I will always create a special folder on your computer with all of your phone's information, including screen shots and technical notes.
I will never install or flash anything without completely confirming 100% you have everything on-hand and the correct firmware and zips are designated for your phone by name and model number.
I will always repeat to myself that when developers on XDA remind you before any you do to completely understand that they are not liable for any phone problems that occur, especially phone bricks. All of the responsibility is on you, so completely make sure you have read everything thoroughly and remember to ensure that what I am flashing is for my specific phone or tablet. What good is flashing a phone or tablet if the end result is a bricked piece of electronics that that's only useful as a paperweight because I didn't take the time to completely research and confirm that what I was doing to my device will have the my desired outcome.
When researching my phone on XDA ensure that I will not open more than 3 tabs on my browser at the same time to links to other forums for descriptions or files to download. Go to one site forum link download the files I will need. I will copy the information I will need and paste it to a word document that can be stored on my computer for immediate use or archive it in case I need to refer to it in the future. If I don't want to copy and paste, I will at least save the page by printing to a PDF and saving it the device folder I created on my computer.
In addition to bookmarking the forum pages that I am using for my phone project, I will save the links in a spreadsheet or Word Document. Building a simple spreadsheet is a great way to save all of your forum Links dedicated to your phone and/or tablet. You can keep one spreadsheet and open individual tabs within the spreadsheet for each different device you have.
I will always have my Manifesto and Procedure lists on hand no matter what I do to my device. I will take notes and screen shots for future reference and reminders. I can possibly use this information in the future to assist other XDA members in the future.
My solution to a problem or my process can one day save another user a lot of time and misery the same way I have been saved in the past due to someone's kindness on these forums for sharing their solutions and procedures.
RS988 phone hard bricked
teknokill said:
I know where I screwed up. I installed the rooted stock for a LG-H850 instead of the RS998 for the American unlocked version. I know my idea is kind of not being 100% truthful, but I was considering returning the phone to Best Buy, where I bought it at an amazing price of $250. I'm going to tell them that the phone locked up after doing a LG/Android security update. They won't be able to tell because it's dead. This way I can exchange it for the another one and don't have to pay $150 for a repair. Best Buy will just send the phone back and get a credit and LG will fix it for free and sell it again recouping all of the cost. It's only been 2 days since I purchased the phone, so I'm well within the return period. I did so much reading that after awhile the RS998 became a LG-H850. I thought they were the same phone.
Just a reminder to all Android Enthusiasts.....I know I the following has been said many times over and over in different ways by fellow members either by re-using important catch-phrases or similar syntax, so it is absolutely vital to develop and adopt a manifesto for yourself to follow while compiling procedures that matches the way you think and operate. Remember that we all strive to get the same end result, but our minds think in different ways and one person's methodology many times is only useful for people who think alike. We're all different and develop methodologies that suit ourselves over time, so a device tinkering manifesto to live by that suites your thought process will always be the best for you in the end. The following manifesto is what I will follow for now on and I will Always and I mean always do the following before tinkering:
I will always have a backup phone with me in case of emergency and I don't have the time to fix my phone right away. There is nothing safer than to allowing yourself to make a mistake and to still be able to have a phone in case of emergency.
I will always create a special folder on your computer with all of your phone's information, including screen shots and technical notes.
I will never install or flash anything without completely confirming 100% you have everything on-hand and the correct firmware and zips are designated for your phone by name and model number.
I will always repeat to myself that when developers on XDA remind you before any you do to completely understand that they are not liable for any phone problems that occur, especially phone bricks. All of the responsibility is on you, so completely make sure you have read everything thoroughly and remember to ensure that what I am flashing is for my specific phone or tablet. What good is flashing a phone or tablet if the end result is a bricked piece of electronics that that's only useful as a paperweight because I didn't take the time to completely research and confirm that what I was doing to my device will have the my desired outcome.
When researching my phone on XDA ensure that I will not open more than 3 tabs on my browser at the same time to links to other forums for descriptions or files to download. Go to one site forum link download the files I will need. I will copy the information I will need and paste it to a word document that can be stored on my computer for immediate use or archive it in case I need to refer to it in the future. If I don't want to copy and paste, I will at least save the page by printing to a PDF and saving it the device folder I created on my computer.
In addition to bookmarking the forum pages that I am using for my phone project, I will save the links in a spreadsheet or Word Document. Building a simple spreadsheet is a great way to save all of your forum Links dedicated to your phone and/or tablet. You can keep one spreadsheet and open individual tabs within the spreadsheet for each different device you have.
I will always have my Manifesto and Procedure lists on hand no matter what I do to my device. I will take notes and screen shots for future reference and reminders. I can possibly use this information in the future to assist other XDA members in the future.
My solution to a problem or my process can one day save another user a lot of time and misery the same way I have been saved in the past due to someone's kindness on these forums for sharing their solutions and procedures.
Click to expand...
Click to collapse
I can not tell you, though thank you for your advice. Best regards.
teknokill said:
Did you finally figure out how to get your phone to work? I can't even get my phone into download mode.
Click to expand...
Click to collapse
No, I couldn't get it to work. I downloaded all of the files to flash the Qualcomm chip, but it was just too easy to return it and get a new one. Which was what I did. I'm unlocking the bootloader now and then root it. This time I will install the correct stock rom for my phone, but I think first I will just root it and use it for a while. I don't need anymore drama right now.
kdz extract linux sd card write done
command link https://mega.nz/#!cJ9WUAiA!TSt9L5G3C...n8vx0pQ9ToxCFw
https://forum.xda-developers.com/g4/...-qfil-t3748946
sorry english
---------- Post added at 12:02 PM ---------- Previous post was at 11:57 AM ----------
[email protected]:~/Downloads$ sudo dmesg -c >> /dev/null
[sudo] password for aaya:
[email protected]:~/Downloads$ dmesg
[email protected]:~/Downloads$ sudo fdisk -l /dev/sdb
Disk /dev/sdb: 58,4 GiB, 62730010624 bytes, 122519552 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 122519551 122517504 58,4G c W95 FAT32 (LBA)
[email protected]:~/Downloads$ cd kdz
[email protected]:~/Downloads/kdz$ sudo -s
[email protected]:~/Downloads/kdz# dd if=PrimaryGPT.bin of=/dev/sdb
48+0 records in
48+0 records out
24576 bytes (25 kB, 24 KiB) copied, 0,0441583 s, 557 kB/s
[email protected]:~/Downloads/kdz# sync
[email protected]:~/Downloads/kdz# ls -la /dev/disk/by-partlabel
total 0
drwxr-xr-x 2 root root 60 Луу 18 19:32 .
drwxr-xr-x 7 root root 140 Луу 18 19:32 ..
lrwxrwxrwx 1 root root 10 Луу 18 18:35 EFI\x20System\x20Partition -> ../../sda1
[email protected]:~/Downloads/kdz# cd kdz
bash: cd: kdz: No such file or directory
[email protected]:~/Downloads/kdz# for i in $(ls *.bin |egrep -v "(GPT|userdata)");do echo dd if=$i of=/dev/disk/by-partlabel/${i/\.bin};done
dd if=abootbak.bin of=/dev/disk/by-partlabel/abootbak
dd if=aboot.bin of=/dev/disk/by-partlabel/aboot
dd if=apdp.bin of=/dev/disk/by-partlabel/apdp
dd if=boot.bin of=/dev/disk/by-partlabel/boot
dd if=cache.bin of=/dev/disk/by-partlabel/cache
dd if=cdt.bin of=/dev/disk/by-partlabel/cdt
dd if=cmnlib64bak.bin of=/dev/disk/by-partlabel/cmnlib64bak
dd if=cmnlib64.bin of=/dev/disk/by-partlabel/cmnlib64
dd if=cmnlibbak.bin of=/dev/disk/by-partlabel/cmnlibbak
dd if=cmnlib.bin of=/dev/disk/by-partlabel/cmnlib
dd if=ddr.bin of=/dev/disk/by-partlabel/ddr
dd if=devcfgbak.bin of=/dev/disk/by-partlabel/devcfgbak
dd if=devcfg.bin of=/dev/disk/by-partlabel/devcfg
dd if=devinfo.bin of=/dev/disk/by-partlabel/devinfo
dd if=dip.bin of=/dev/disk/by-partlabel/dip
dd if=dpo.bin of=/dev/disk/by-partlabel/dpo
dd if=drm.bin of=/dev/disk/by-partlabel/drm
dd if=eksst.bin of=/dev/disk/by-partlabel/eksst
dd if=encrypt.bin of=/dev/disk/by-partlabel/encrypt
dd if=factory.bin of=/dev/disk/by-partlabel/factory
dd if=fota.bin of=/dev/disk/by-partlabel/fota
dd if=fsc.bin of=/dev/disk/by-partlabel/fsc
dd if=fsg.bin of=/dev/disk/by-partlabel/fsg
dd if=grow2.bin of=/dev/disk/by-partlabel/grow2
dd if=grow3.bin of=/dev/disk/by-partlabel/grow3
dd if=grow4.bin of=/dev/disk/by-partlabel/grow4
dd if=grow5.bin of=/dev/disk/by-partlabel/grow5
dd if=grow6.bin of=/dev/disk/by-partlabel/grow6
dd if=grow.bin of=/dev/disk/by-partlabel/grow
dd if=hypbak.bin of=/dev/disk/by-partlabel/hypbak
dd if=hyp.bin of=/dev/disk/by-partlabel/hyp
dd if=keymasterbak.bin of=/dev/disk/by-partlabel/keymasterbak
dd if=keymaster.bin of=/dev/disk/by-partlabel/keymaster
dd if=keystore.bin of=/dev/disk/by-partlabel/keystore
dd if=lafbak.bin of=/dev/disk/by-partlabel/lafbak
dd if=laf.bin of=/dev/disk/by-partlabel/laf
dd if=misc.bin of=/dev/disk/by-partlabel/misc
dd if=modem.bin of=/dev/disk/by-partlabel/modem
dd if=modemst1.bin of=/dev/disk/by-partlabel/modemst1
dd if=modemst2.bin of=/dev/disk/by-partlabel/modemst2
dd if=mpt.bin of=/dev/disk/by-partlabel/mpt
dd if=msadp.bin of=/dev/disk/by-partlabel/msadp
dd if=persist.bin of=/dev/disk/by-partlabel/persist
dd if=pmicbak.bin of=/dev/disk/by-partlabel/pmicbak
dd if=pmic.bin of=/dev/disk/by-partlabel/pmic
dd if=raw_resourcesbak.bin of=/dev/disk/by-partlabel/raw_resourcesbak
dd if=raw_resources.bin of=/dev/disk/by-partlabel/raw_resources
dd if=rct.bin of=/dev/disk/by-partlabel/rct
dd if=recoverybak.bin of=/dev/disk/by-partlabel/recoverybak
dd if=recovery.bin of=/dev/disk/by-partlabel/recovery
dd if=reserve.bin of=/dev/disk/by-partlabel/reserve
dd if=rpmbak.bin of=/dev/disk/by-partlabel/rpmbak
dd if=rpm.bin of=/dev/disk/by-partlabel/rpm
dd if=sec.bin of=/dev/disk/by-partlabel/sec
dd if=sns.bin of=/dev/disk/by-partlabel/sns
dd if=spare1.bin of=/dev/disk/by-partlabel/spare1
dd if=spare2.bin of=/dev/disk/by-partlabel/spare2
dd if=ssd.bin of=/dev/disk/by-partlabel/ssd
dd if=system.bin of=/dev/disk/by-partlabel/system
dd if=tzbak.bin of=/dev/disk/by-partlabel/tzbak
dd if=tz.bin of=/dev/disk/by-partlabel/tz
dd if=xbl2bak.bin of=/dev/disk/by-partlabel/xbl2bak
dd if=xbl2.bin of=/dev/disk/by-partlabel/xbl2
dd if=xblbak.bin of=/dev/disk/by-partlabel/xblbak
dd if=xbl.bin of=/dev/disk/by-partlabel/xbl
[email protected]:~/Downloads/kdz# for i in $(ls *.bin |egrep -v "(GPT|userdata)");do dd if=$i of=/dev/disk/by-partlabel/${i/\.bin};done
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0645802 s, 32,5 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,033826 s, 62,0 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0139195 s, 37,7 MB/s
81920+0 records in
81920+0 records out
41943040 bytes (42 MB, 40 MiB) copied, 0,538989 s, 77,8 MB/s
1048576+0 records in
1048576+0 records out
536870912 bytes (537 MB, 512 MiB) copied, 6,8639 s, 78,2 MB/s
8+0 records in
8+0 records out
4096 bytes (4,1 kB, 4,0 KiB) copied, 0,000314755 s, 13,0 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00478674 s, 110 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00568034 s, 92,3 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00660332 s, 79,4 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00483936 s, 108 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0297275 s, 70,5 MB/s
256+0 records in
256+0 records out
131072 bytes (131 kB, 128 KiB) copied, 0,00236585 s, 55,4 MB/s
256+0 records in
256+0 records out
131072 bytes (131 kB, 128 KiB) copied, 0,00274482 s, 47,8 MB/s
2048+0 records in
2048+0 records out
1048576 bytes (1,0 MB, 1,0 MiB) copied, 0,0135021 s, 77,7 MB/s
2048+0 records in
2048+0 records out
1048576 bytes (1,0 MB, 1,0 MiB) copied, 0,0120692 s, 86,9 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0153506 s, 34,2 MB/s
20480+0 records in
20480+0 records out
10485760 bytes (10 MB, 10 MiB) copied, 0,13946 s, 75,2 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00688644 s, 76,1 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0049967 s, 105 MB/s
135168+0 records in
135168+0 records out
69206016 bytes (69 MB, 66 MiB) copied, 1,01334 s, 68,3 MB/s
8192+0 records in
8192+0 records out
4194304 bytes (4,2 MB, 4,0 MiB) copied, 0,0511182 s, 82,1 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00611613 s, 85,7 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0170799 s, 123 MB/s
8+0 records in
8+0 records out
4096 bytes (4,1 kB, 4,0 KiB) copied, 0,000273026 s, 15,0 MB/s
8+0 records in
8+0 records out
4096 bytes (4,1 kB, 4,0 KiB) copied, 0,000179081 s, 22,9 MB/s
8+0 records in
8+0 records out
4096 bytes (4,1 kB, 4,0 KiB) copied, 0,000323429 s, 12,7 MB/s
8+0 records in
8+0 records out
4096 bytes (4,1 kB, 4,0 KiB) copied, 0,00018018 s, 22,7 MB/s
8+0 records in
8+0 records out
4096 bytes (4,1 kB, 4,0 KiB) copied, 0,000267083 s, 15,3 MB/s
7080+0 records in
7080+0 records out
3624960 bytes (3,6 MB, 3,5 MiB) copied, 0,0571791 s, 63,4 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00556187 s, 94,3 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00537099 s, 97,6 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00457723 s, 115 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0146511 s, 35,8 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00600904 s, 87,2 MB/s
98304+0 records in
98304+0 records out
50331648 bytes (50 MB, 48 MiB) copied, 0,67333 s, 74,8 MB/s
98304+0 records in
98304+0 records out
50331648 bytes (50 MB, 48 MiB) copied, 0,616455 s, 81,6 MB/s
65536+0 records in
65536+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 0,404057 s, 83,0 MB/s
176128+0 records in
176128+0 records out
90177536 bytes (90 MB, 86 MiB) copied, 1,1437 s, 78,8 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0244209 s, 85,9 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,0240775 s, 87,1 MB/s
65536+0 records in
65536+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 0,426183 s, 78,7 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00713832 s, 73,4 MB/s
65536+0 records in
65536+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 0,405352 s, 82,8 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0956617 s, 5,5 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00720851 s, 72,7 MB/s
8192+0 records in
8192+0 records out
4194304 bytes (4,2 MB, 4,0 MiB) copied, 0,0700125 s, 59,9 MB/s
8192+0 records in
8192+0 records out
4194304 bytes (4,2 MB, 4,0 MiB) copied, 0,0754277 s, 55,6 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0422099 s, 12,4 MB/s
82944+0 records in
82944+0 records out
42467328 bytes (42 MB, 40 MiB) copied, 0,51604 s, 82,3 MB/s
82944+0 records in
82944+0 records out
42467328 bytes (42 MB, 40 MiB) copied, 0,542084 s, 78,3 MB/s
64+0 records in
64+0 records out
32768 bytes (33 kB, 32 KiB) copied, 0,00882342 s, 3,7 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0230715 s, 22,7 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0240835 s, 21,8 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,00557492 s, 94,0 MB/s
12288+0 records in
12288+0 records out
6291456 bytes (6,3 MB, 6,0 MiB) copied, 0,100289 s, 62,7 MB/s
8192+0 records in
8192+0 records out
4194304 bytes (4,2 MB, 4,0 MiB) copied, 0,0708991 s, 59,2 MB/s
4096+0 records in
4096+0 records out
2097152 bytes (2,1 MB, 2,0 MiB) copied, 0,042133 s, 49,8 MB/s
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0,0214201 s, 24,5 MB/s
dd: writing to '/dev/disk/by-partlabel/system': No space left on device
1740777+0 records in
1740776+0 records out
891277312 bytes (891 MB, 850 MiB) copied, 11,3213 s, 78,7 MB/s
dd: writing to '/dev/disk/by-partlabel/tzbak': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,0257604 s, 0,0 kB/s
dd: writing to '/dev/disk/by-partlabel/tz': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,0130488 s, 0,0 kB/s
dd: writing to '/dev/disk/by-partlabel/xbl2bak': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,0112316 s, 0,0 kB/s
dd: writing to '/dev/disk/by-partlabel/xbl2': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,00448855 s, 0,0 kB/s
dd: writing to '/dev/disk/by-partlabel/xblbak': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,00429619 s, 0,0 kB/s
dd: writing to '/dev/disk/by-partlabel/xbl': No space left on device
1+0 records in
0+0 records out
0 bytes copied, 0,00457151 s, 0,0 kB/s
[email protected]:~/Downloads/kdz#
and who is key decryption?
Related
[Q]HTC Desire HD hboot2.00.0029 How to change the ship s-on to ship s-off?
When I use the way that using the CMD comand # su su # C:\Users\woop\Desktop\sos2.0>adb shell # sh /sdcard/DHD/1 sh /sdcard/DHD/1 * daemon not running. starting it now on port 5037 * * daemon started successfully * insmod: can't insert '/sdcard/DHD/wpx.ko': invalid module format If you get this error: # su su # sh /sdcard/DHD/1 sh /sdcard/DHD/1 insmod: init_module '/sdcard/DHD/wpx.ko' failed (Function not impl insmod: can't insert '/sdcard/DHD/wpx.ko': invalid module format If you get this error: or insmod: can't insert '/sdcard/DHD/wpx.ko': Function not implemente insmod: init_module '/sdcard/DHD/wpx.ko' failed (Function not impl This means the module worked 2048+0 records in or insmod: can't insert '/sdcard/DHD/wpx.ko': Function not implemente 2048+0 records out 1048576 bytes (1.0MB) copied, 27.108576 seconds, 37.8KB/s 2048+0 records in T2048+0 records out his means the module worked 2048+0 records in 1048576 bytes (1.0MB) copied, 0.201596 seconds, 5.0MB/s 2a28dcd53ea26504be9a86572a348aa1 /sdcard/DHD/hboot_orig0.bin 18e89249b976d17cb20332511099fb9a /sdcard/DHD/hboot_check.bin 2048+0 records out 1048576 bytes (1.0MB) copied, 27.108576 seconds, 37.8KB/s 2048+0 records in 2048+0 records out IF THE ABOVE MD5 SUMS DO NOT MATCH YOU ARE IN SERIOUS TROUBLE!!! THIS SHOULD NOT HAPPEN AT ALL 1048576 bytes (1.0MB) copied, 0.201596 seconds, 5.0MB/s 2a28dcd53ea26504be9a86572a348aa1 /sdcard/DHD/hboot_orig0.bin PLEASE SEEK HELP ON THE FORUMS BUT WHATEVER YOU DO DO NOT TURN OFF YOUR PHONE IF YOU FAIL TODO SO IT WILL BE BRICKED it always act this problom。I don't know how to do the next step.I want to chang the phone.Who can tell me,please?
DHD S off wooplc said: When I use the way that using the CMD comand # su su # C:\Users\woop\Desktop\sos2.0>adb shell # sh /sdcard/DHD/1 sh /sdcard/DHD/1 * daemon not running. starting it now on port 5037 * * daemon started successfully * insmod: can't insert '/sdcard/DHD/wpx.ko': invalid module format If you get this error: # su su # sh /sdcard/DHD/1 sh /sdcard/DHD/1 insmod: init_module '/sdcard/DHD/wpx.ko' failed (Function not impl insmod: can't insert '/sdcard/DHD/wpx.ko': invalid module format If you get this error: or insmod: can't insert '/sdcard/DHD/wpx.ko': Function not implemente insmod: init_module '/sdcard/DHD/wpx.ko' failed (Function not impl This means the module worked 2048+0 records in or insmod: can't insert '/sdcard/DHD/wpx.ko': Function not implemente 2048+0 records out 1048576 bytes (1.0MB) copied, 27.108576 seconds, 37.8KB/s 2048+0 records in T2048+0 records out his means the module worked 2048+0 records in 1048576 bytes (1.0MB) copied, 0.201596 seconds, 5.0MB/s 2a28dcd53ea26504be9a86572a348aa1 /sdcard/DHD/hboot_orig0.bin 18e89249b976d17cb20332511099fb9a /sdcard/DHD/hboot_check.bin 2048+0 records out 1048576 bytes (1.0MB) copied, 27.108576 seconds, 37.8KB/s 2048+0 records in 2048+0 records out IF THE ABOVE MD5 SUMS DO NOT MATCH YOU ARE IN SERIOUS TROUBLE!!! THIS SHOULD NOT HAPPEN AT ALL 1048576 bytes (1.0MB) copied, 0.201596 seconds, 5.0MB/s 2a28dcd53ea26504be9a86572a348aa1 /sdcard/DHD/hboot_orig0.bin PLEASE SEEK HELP ON THE FORUMS BUT WHATEVER YOU DO DO NOT TURN OFF YOUR PHONE IF YOU FAIL TODO SO IT WILL BE BRICKED it always act this problom。I don't know how to do the next step.I want to chang the phone.Who can tell me,please? Click to expand... Click to collapse ____________________________________________________________________________________ Hello I know you have posted your question long time, I assume that you have s offed your DHD hbooot-00.0029. I am also struggling to s-off my DHD, when I check my hboot_orig0.bin it is 18e89249b976d17cb20332511099fb9a. But I couldn't find correct Hboot eng file. Can you please help me out?
Microsd Card Read-Only Issue: DD read-only file system
My micro sd card seems to not be working at all. Have been googling this problem for about a good 2 weeks now. Reason this happened: was installing a ROM on phone, and I have no idea what happened. Weird enough though, I was listening to music randomly one night no problem. Morning after I had some blank/unsupported fiel system error on sd card. Tried many things: fdisk (gave bad file descriptor error) DD (read-only file system) Disk management in windows (shows up, but no options availble. Won't even let me format.) Device Manager in Windows says I need to troubleshoot USB MASS Storage (Using Microsd card adapter), troubleshoot to no avail. Diskpart in windows ChkDsk in Windows as well fdisk -l output Code: Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000255e5 Device Boot Start End Blocks Id System /dev/sda1 2048 67583 32768 83 Linux /dev/sda2 67584 1116159 524288 82 Linux swap / Solaris /dev/sda3 1116160 976773167 487828504 83 Linux Disk /dev/sdd: 15.8 GB, 15829303296 bytes 256 heads, 63 sectors/track, 1916 cylinders, total 30916608 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdd1 * 2048 30916607 15457280 c W95 FAT32 (LBA) When I try mounting /dev/sdd Code: mount /dev/sdd /media/usb1 mount: block device /dev/sdd is write-protected, mounting read-only mount: you must specify the filesystem type
flash back to odin...
[Q] A Problem when root using Easy Root Tool
Hello, I'm using EasyRootTool v11.zip from http://forum.xda-developers.com/showthread.php?t=2784900. When I run it, it shows that: Code: ============================================= Getting device variables ============================================= Device model is L50u Firmware is 17.1.1.F.0.39 ============================================= Sending files ============================================= 36 KB/s (1585 bytes in 0.042s) 25 KB/s (1133 bytes in 0.042s) 207 KB/s (9496 bytes in 0.044s) 275 KB/s (13672 bytes in 0.048s) 2788 KB/s (657704 bytes in 0.230s) Copying kernel module... 819 KB/s (34473 bytes in 0.041s) 17 KB/s (767 bytes in 0.042s) 291 KB/s (13592 bytes in 0.045s) Kernel version is 3.4.0-perf-g1cb2b9a-01879-gd0acb0a Version does not match 3.4.0-perf-ge4322cd, needs patching... 1+0 records in 0+1 records out 34 bytes transferred in 0.001 secs (34000 bytes/sec) Kernel module patched. modulecrcpatch (by zxz0O0) module_layout: patched to 0xCFADE050 __aeabi_unwind_cpp_pr1: match kallsyms_lookup_name: not found printk: not found mem_text_write_kernel_word: not found __aeabi_unwind_cpp_pr0: match successfully patched ============================================= Loading geohot's towelroot (modified by zxz0O0) ============================================= 281 KB/s (13592 bytes in 0.047s) 2660 KB/s (197320 bytes in 0.072s) ============================================= Waiting for towelroot to exploit... towelzxperia by zxz0O0 (EasyRootTool Version) libexploit by geohot libzxploit.so created doing the magic creating vm (loljavasucks) insmod: init_module '/data/local/tmp/wp_mod.ko' failed (Exec format error) mount: Operation not permitted /system/bin/chcon: Could not label /system/xbin/su with u:object_r:system_file:s0: No such file or directory chcon: Could not label /system/xbin/su with u:object_r:system_file:s0: No such file or directory sh: /system/xbin/su: not found cleaning up done Checking if device is rooted... Error: device not rooted
yanjingtao said: Hello, I'm using EasyRootTool v11.zip from http://forum.xda-developers.com/showthread.php?t=2784900. When I run it, it shows that: Code: ============================================= Getting device variables ============================================= Device model is L50u Firmware is 17.1.1.F.0.39 ============================================= Sending files ============================================= 36 KB/s (1585 bytes in 0.042s) 25 KB/s (1133 bytes in 0.042s) 207 KB/s (9496 bytes in 0.044s) 275 KB/s (13672 bytes in 0.048s) 2788 KB/s (657704 bytes in 0.230s) Copying kernel module... 819 KB/s (34473 bytes in 0.041s) 17 KB/s (767 bytes in 0.042s) 291 KB/s (13592 bytes in 0.045s) Kernel version is 3.4.0-perf-g1cb2b9a-01879-gd0acb0a Version does not match 3.4.0-perf-ge4322cd, needs patching... 1+0 records in 0+1 records out 34 bytes transferred in 0.001 secs (34000 bytes/sec) Kernel module patched. modulecrcpatch (by zxz0O0) module_layout: patched to 0xCFADE050 __aeabi_unwind_cpp_pr1: match kallsyms_lookup_name: not found printk: not found mem_text_write_kernel_word: not found __aeabi_unwind_cpp_pr0: match successfully patched ============================================= Loading geohot's towelroot (modified by zxz0O0) ============================================= 281 KB/s (13592 bytes in 0.047s) 2660 KB/s (197320 bytes in 0.072s) ============================================= Waiting for towelroot to exploit... towelzxperia by zxz0O0 (EasyRootTool Version) libexploit by geohot libzxploit.so created doing the magic creating vm (loljavasucks) insmod: init_module '/data/local/tmp/wp_mod.ko' failed (Exec format error) mount: Operation not permitted /system/bin/chcon: Could not label /system/xbin/su with u:object_r:system_file:s0: No such file or directory chcon: Could not label /system/xbin/su with u:object_r:system_file:s0: No such file or directory sh: /system/xbin/su: not found cleaning up done Checking if device is rooted... Error: device not rooted Click to expand... Click to collapse You cannot use EasyRootTool for the newest ROM's - you might be able to use How To Root the newest firmware (.314) Btw. .39 is for the Chinese Z2?
Well I rooted my Z2. 314 firmware last night and it worked. I used ERT V11. It took 2 attempts mind you, cause I wasn't watching what I was doing the 1st time lol ? Sent from my D6503 using xda premium from "Somewhere, but not here..."
harfot said: You cannot use EasyRootTool for the newest ROM's - you might be able to use How To Root the newest firmware (.314) Btw. .39 is for the Chinese Z2? Click to expand... Click to collapse Thanks, is this tool unlocked the bootloader? I don't want to unlocked the bootloader. .39 is Chinese Z2 LTE version's last fireware. Z2 in China has three version, 3G/TD-LTE/LTE
[Q] Z2 running .690 firmware won't root with community root kit v01
Hi guys,
So I have an Xperia z2 (android 5.0.2) running on firmware 23.1.A.0.690 (downgraded from 23.1.A.0.726)
I'm attempting to my root my .690 fw using community rootkit v01, however it is with no avail, despite having the correct adb drivers installed, USB debugging & unknown sources enabled & ADK installed. Here is what rootkit keeps telling me...
# Semi-Automated script written by Sacha.
# With exploit method developed by GranPC.
# I assume you have adb installed, etc etc..
# I also assume you are using a Z2 on .69 firmware
# with contributions from DooMLoRD, norti and RyokoN
Installing exploit app.
3616 KB/s (348942 bytes in 0.094s)
pkg: /data/local/tmp/exploit.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Copying small files...
4538 KB/s (1109128 bytes in 0.238s)
3378 KB/s (121260 bytes in 0.035s)
3336 KB/s (13672 bytes in 0.004s)
93 KB/s (569 bytes in 0.005s)
1306 KB/s (9496 bytes in 0.007s)
401 KB/s (2050 bytes in 0.004s)
18 KB/s (97 bytes in 0.005s)
1478 KB/s (13672 bytes in 0.009s)
82 KB/s (505 bytes in 0.005s)
66 KB/s (404 bytes in 0.005s)
123 KB/s (764 bytes in 0.006s)
2906 KB/s (83364 bytes in 0.028s)
991 KB/s (3089 bytes in 0.003s)
122 KB/s (629 bytes in 0.005s)
5 KB/s (33 bytes in 0.006s)
5089 KB/s (2326385 bytes in 0.446s)
Copying BIG file... please have patience, this might take a while...
6223 KB/s (63931904 bytes in 10.031s)
Correcting permissions...
Starting Part 1
--- DooMing device: PART 1!
--- Correcting permissions
--- Running services
/data/local/tmp/vdcCreate[5]: vdc: not found
ln: /data/app-lib/ServiceMenu/libservicemenu.so: No such file or directory
ln: /data/local/tmp/vlib: Permission denied
Starting: Intent { act=android.intent.action.MAIN cmp=com.sonyericsson.android.s
ervicemenu/.ServiceMainMenu }
Test VDC #1:
Failure
PART 1 complete!
Complete!
----------------[ ATTENTION ]----------------
Please 'crash' the Service Menu app to complete.
For example: Service Info - Configuration.
The screen will probably blink when it has worked.
Press any key to continue . . .
Click to expand...
Click to collapse
I cannot 'crash' the service menu. When I hit 'configuration', the screen does not blink, despite restarting the entire process. I've tried this probably 20 times.
Any help would be greatly appreciated.
if i'm not mistaken the rootkit v01 is for Kitkat firmwares not for Lollipop, to root Lollipop you could try this http://forum.xda-developers.com/xperia-z2/general/root-t3108230
Unlocking Sony Xperia M4 Aqua (Android) bootloader with Debian?
i found these tools in Synaptic: fastboot ddms (sdk) & adb Can i use these to unlock the bootloader instead of downloading a bunch of stuff from websites? i found the device using fastboot and the unlock code from sony but thats about as far as i got.
Sure, you also need the linux version of flashtool, which you can get from the site (no need to install), and you are good to go. :thumbup: Sent from my E2303 using XDA Free mobile app
would anyone mind guiding me through the steps?
xinjian said: would anyone mind guiding me through the steps? Click to expand... Click to collapse There is a linux version of Flashtool and its an sh script so the command would be sudo bash LocationOfFlashtool/Flashtool Click to expand... Click to collapse And then when the bootloader is unlocked and you want to flash recovery sudo fastboot flash recovery LocationOfRecovery/recovery.img Click to expand... Click to collapse
xinjian said: i found these tools in Synaptic: fastboot ddms (sdk) & adb Can i use these to unlock the bootloader instead of downloading a bunch of stuff from websites? i found the device using fastboot and the unlock code from sony but thats about as far as i got. Click to expand... Click to collapse I just rooted my phone under Gentoo using adb commands from install.bat file which I downloaded from here: http://www.mediafire.com/download/awrsi78ddjl0x2r/rootkitXperia_E23xx_26.1.X.3.xxx.zip Just unpack this zip, change directory to where you unzipped it and run: Code: adb push files/getroot /data/local/tmp/ adb push files/su /data/local/tmp/ adb push files/supolicy /data/local/tmp/ adb push files/libsupol.so /data/local/tmp/ adb push files/Superuser.apk /data/local/tmp/ adb push files/busybox /data/local/tmp/ adb push files/99SuperSUDaemon /data/local/tmp/ adb push files/install-recovery.sh /data/local/tmp/ adb push files/install_tool.sh /data/local/tmp/ adb shell "chmod 0755 /data/local/tmp/getroot" adb shell "chmod 0755 /data/local/tmp/busybox" adb shell "chmod 0755 /data/local/tmp/install_tool.sh" adb shell "/data/local/tmp/getroot /data/local/tmp/install_tool.sh" After last command you should get something like this: Code: Patching address 0xffffffc00112a9d0 Start map/unmap thread. Start write thread. Spraying kernel heap. 100 200 300 400 500 600 700 800 900 1000 Start read thread. Done. Patching address 0xffffffc058b34008 Start map/unmap thread. Start write thread. Spraying kernel heap. 100 200 300 400 500 600 700 800 900 1000 Start read thread. 10000 Done. 2047+1 records in 2047+1 records out 1048328 bytes transferred in 0.057 secs (18391719 bytes/sec) 203+1 records in 203+1 records out 104368 bytes transferred in 0.009 secs (11596444 bytes/sec) 203+1 records in 203+1 records out 104368 bytes transferred in 0.004 secs (26092000 bytes/sec) 203+1 records in 203+1 records out 104368 bytes transferred in 0.004 secs (26092000 bytes/sec) 203+1 records in 203+1 records out 104368 bytes transferred in 0.004 secs (26092000 bytes/sec) 58+1 records in 58+1 records out 30168 bytes transferred in 0.005 secs (6033600 bytes/sec) 613+1 records in 613+1 records out 314232 bytes transferred in 0.016 secs (19639500 bytes/sec) 11948+1 records in 11948+1 records out 6117378 bytes transferred in 0.189 secs (32367079 bytes/sec) 1+1 records in 1+1 records out 629 bytes transferred in 0.003 secs (209666 bytes/sec) 0+1 records in 0+1 records out 55 bytes transferred in 0.001 secs (55000 bytes/sec)
Actually you don't need to have Flashtool to unlock the bootloader since the device is officially supported by Sony Just follow the instructions in its webpage