Related
I wanted to flash the phone, when you install TWRP that it did not, and now the phone does not include and does not respond to the buttons at to connection to a computer is defined as RELINK HS-USB QDLoader 9008 probably fell off the loader
where to find the boot loader files if anyone can help
thank you in advance
tynot43 said:
I wanted to flash the phone, when you install TWRP that it did not, and now the phone does not include and does not respond to the buttons at to connection to a computer is defined as RELINK HS-USB QDLoader 9008 probably fell off the loader
where to find the boot loader files if anyone can help
thank you in advance
Click to expand...
Click to collapse
This sounds like a hard brick. I remember the USB QDloader message from the 2014 Moto X and that's what it meant. I did it once. The only phone I have ever bricked.
To the OP, what exact commands did you use to flash twrp?
Bricking a phone just from flashing a recovery is highly unlikely.
gpz1100 said:
To the OP, what exact commands did you use to flash twrp?
Bricking a phone just from flashing a recovery is highly unlikely.
Click to expand...
Click to collapse
Hey, I am pretty noob at this, and I bricked a 2014 Moto X because I installed 5.0 via OTA having a custom rom, but with some XDA threads I have tried to bring it back to life: I followed a thread (if you want I give you the link), and when I have to run qflash.exe, it gives me this error: "qflash.exe -com5 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloader_singleimage.bin -v -o
C:\Users\usuario\Desktop\blankflash>qflash.exe -com5 -ramload MPRG8960.hex -mbn
33 MSM8960_bootloader_singleimage.bin -v -o
Motorola qflash Utility version 1.3
COMPORT :COM5
RAMLOADER :MPRG8960.hex
type is 0x21
7 mbn file name MSM8960_bootloader_singleimage.bin type 33
verbose mode on
Motorola qflash dll version 1.6
dmss_software_version_req: received invalid or no response
Failed to send software version request"
Any solution?
Check in device manager to see if the phone is even recognized. I recall seeing a driver for this hs-usb 'device', but don't have any links handy. If all else fails, it may still be recoverable but with a jtag set up. Outside of my expertise. Good luck.
It recognises it, and when I have to blankflash it, it gives me that error I wrote above, "dmss_software_versiom_req: received invalid or no response
Failed to send software version request"
Hi, i was playing with my yota2 and think i messed up the radio files, now the phone is dead, no vibration no screen light, nothing.
i tried some methods and was able to get the phone recognized as 'Qualcomm HS-USB QDLoader 9008' but dont know what to do. btw i opened up the phone, is there anyway to revive it or should i just order another one?
Thanks alot
Try flashing it with yotaflasher. Post any errors if they occur.
Hi
My phone does not get recognized. When trying to use yotaflasher it is stuck at 'waiting for device'
yotafree said:
Hi
My phone does not get recognized. When trying to use yotaflasher it is stuck at 'waiting for device'
Click to expand...
Click to collapse
Your adb drivers are not loaded on your laptop/PC , there are many threads about this on here. You cannot do a fastboot flash without these drivers.
Run an adb command from a DOS "cmd" window on your laptop to check this, this is explained on here.
i had a hardbrick yotaphone2 also. only qualcomm 9008 detected. had tried all the way to flash it back due to wrong rom being flashed. please advice....no fastboot, tried power off and volume down, tried kick out from EDL mode...tried qualcomm flasher which support EDL flashing but downloaded rom cannot flash due to only img and bin file, there is no rawprogram xml file.....anybody have dumped rom for this phone?
Thank you but did you forget to add the link which command to run ??
Parmo100 said:
Your adb drivers are not loaded on your laptop/PC , there are many threads about this on here. You cannot do a fastboot flash without these drivers.
Run an adb command from a DOS "cmd" window on your laptop to check this, this is explained on here.
Click to expand...
Click to collapse
Thank you but did you forget to add the link which command to run ??
I've installed TWRP last weekend and installed LineageOS 14.1 for my LG G6 H870.
I was tinkering with Magisk and Magisk Manager to be able to use Netflix, I didn't restart my device after this step.
Last night LineageOS offered an OTA update and afterwards it restarted to recovery mode.
I assumed I had to install the new image manually so that's what I did.
After the installation the phone rebooted back to TWRP Recovery so I wiped cache, data and dalvik.
It still rebooted back to TWRP recovery so I tried to reinstall LineageOS again by following these steps: https://wiki.lineageos.org/devices/h870/install#installing-lineageos-from-recovery
The phone still only boots to recovery so my assumption, after some reading on XDA, is that something is wrong with the bootloader.
This could have happened when I was tinkering with Magisk, I think I've seen a notice that I tried to make changes to the bootloader.
To fix the bootloader the main suggestion is to flash the stock rom so i've started that path.
I've installed Uppercut and LG Up use links from this thread: https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295/
I found a stock rom at https://lg-firmwares.com/lg-h870-firmwares/#firmwaresList and I assume I need the "NEU/NORTHERN EUROPE" rom.
When I open Uppercut it says "There is no handset connected".
I've got no clue what steps to take at this point.
FYI I'm able to get in to the bootloader mode and the recovery mode but havent been able to get into the download mode.
If you still have twrp just flash stock from there.
basicreece said:
If you still have twrp just flash stock from there.
Click to expand...
Click to collapse
I didn't know it was possible to flash a kdz file using twrp.
According to this reply it isn't possible using kdz files https://forum.xda-developers.com/showthread.php?t=2650569
Do you know for sure that this is possible?
I think I need to flash the bootloader using fastboot but I don't know what source to use, and I hardly found bootloader files on the web.
I don't think Magisk is modifying the bootloader, but I could be wrong.
You can find the H870_v10T and US997_v14A bootloaders here:
https://forum.xda-developers.com/showpost.php?p=73161240&postcount=2
ahk31 said:
I don't think Magisk is modifying the bootloader, but I could be wrong.
You can find the H870_v10T and US997_v14A bootloaders here:
https://forum.xda-developers.com/showpost.php?p=73161240&postcount=2
Click to expand...
Click to collapse
Thanks for pointing out that thread!
I downloaded the bootloader and succesfully installed it using `adb sideload LG-H87010f-Flashable.Bootloader.zip`
But the phone still only boots to TWRP.
So I tried to flash a complete stock rom from https://forum.xda-developers.com/lg-g6/development/rom-eu-lg-h870-10t-rom-t3654134
I did wipe Dalvik/ART, Cache, System and Data and afterwards installed that rom.
Unfortunately these steps didn't make any difference to the boot sequence.
I've been trying again to get into the download mode using key combo's and using `adb reboot download` but it reboots to TWRP instead.
What should I try now?
I finally managed to enter download mode!
In the end I figured that I confused the key combo from my previous phone with this one.
I should only hold the volume up button and then plugin in the usb cable.
What I tried numerous times was a combo of volume up and power button.
for reference and people showing up here later. Doing lineage OTA updates on the G6 forces the device into that endless boot loop into recovery. You get out there by entering the shell in TWRP and dd'ing some zeros somewhere. I had it once but sadly did not write down how I solved it. Google for boot loop and twrp you will find hits here on xda where you see a dd if=/dev/zero line and explaining what todo. It is a bit different for each device, but the article tells you what to look for. As I understood it, writing some zeros at the start of a partition ends the loop, but I am no expert there, it just worked for me.
Oh yes, and stay away from lineage OTAs
Edit: ok, not xda but reddit, anyway here is the link
https://www.reddit.com/r/LineageOS/comments/5riech/how_fix_twrp_recovery_boot_loop_after_lineageos/
The life saving post is a comment further down by muniak
I'm using TWRP 3.1 and still had this issue.
Despite thinking my phone was rooted, I couldn't su, adb as root or anything, so I couldn't /fstab. I ended up looking around and comparing the path I was in with other's. So if you're having this problem just keep going around typing ls and pressing tab like below. Basically you're looking for "by-name/misc" in "/dev/block/platform/".
ls /dev/block ls /dev/block/platform ls /dev/block/platform/[dir or two] ls /dev/block/platform/[dir or two]/by-name ls /dev/block/platform/[dir or two]/by-name/misc
Then the dd if=/dev/zero of=/dev/block/platform/[dir or two]/by-name/misc count=1 bs=32
Good luck and thanks so much for the help!
Click to expand...
Click to collapse
ikbentomas said:
I didn't know it was possible to flash a kdz file using twrp.
According to this reply it isn't possible using kdz files https://forum.xda-developers.com/showthread.php?t=2650569
Do you know for sure that this is possible?
I think I need to flash the bootloader using fastboot but I don't know what source to use, and I hardly found bootloader files on the web.
Click to expand...
Click to collapse
Then flash the stock zip.....
If you had searched the forum you would see the stock zips and bootloaders all complied for twrp.
ikbentomas said:
I've installed TWRP last weekend and installed LineageOS 14.1 for my LG G6 H870.
I was tinkering with Magisk and Magisk Manager to be able to use Netflix, I didn't restart my device after this step.
Last night LineageOS offered an OTA update and afterwards it restarted to recovery mode.
I assumed I had to install the new image manually so that's what I did.
After the installation the phone rebooted back to TWRP Recovery so I wiped cache, data and dalvik.
It still rebooted back to TWRP recovery so I tried to reinstall LineageOS again by following these steps: https://wiki.lineageos.org/devices/h870/install#installing-lineageos-from-recovery
The phone still only boots to recovery so my assumption, after some reading on XDA, is that something is wrong with the bootloader.
This could have happened when I was tinkering with Magisk, I think I've seen a notice that I tried to make changes to the bootloader.
To fix the bootloader the main suggestion is to flash the stock rom so i've started that path.
I've installed Uppercut and LG Up use links from this thread: https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295/
I found a stock rom at https://lg-firmwares.com/lg-h870-firmwares/#firmwaresList and I assume I need the "NEU/NORTHERN EUROPE" rom.
When I open Uppercut it says "There is no handset connected".
I've got no clue what steps to take at this point.
FYI I'm able to get in to the bootloader mode and the recovery mode but havent been able to get into the download mode.
Click to expand...
Click to collapse
Use adb and type in: adb shell dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc count=1 bs=32
Then restart your phone!
worked for me
cheers
Boneface Johnson said:
Use adb and type in: adb shell dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc count=1 bs=32
Then restart your phone!
worked for me
cheers
Click to expand...
Click to collapse
I had the same problem, this command worked for me, thanks!
Boneface Johnson said:
Use adb and type in: adb shell dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc count=1 bs=32
Then restart your phone!
worked for me
cheers
Click to expand...
Click to collapse
Worked for me too. Many thanks.
Boneface Johnson said:
Use adb and type in: adb shell dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc count=1 bs=32
Then restart your phone!
worked for me
cheers
Click to expand...
Click to collapse
Thanks, your solution worked for me too
Same happend to me, there are some post that say you have to boot to bootloader and send bootloader continue command with your PC, however that didn't work for me. To flash with LG UP you have to have your phone off, connect USB cable to PC, press Vol+ on phone and connect the USB cable to the phone, it should start in a mode called download mode, then LG UP should find your device
OK so this is where i tell you if you brick your phone and try this and it makes it worse i am not to blame. this has worked on three different phones that i have used no problem.That being said lets dive on in.
ONLY FOR THE H1711!!!!
Downloads (move them all to sd card root)
UPDATED USERDATA thank aslezak for that
https://uploadfiles.io/n5g32 and that
http://www.mediafire.com/file/gybldrcgw8h6x2w/twrp_first%5B1%5D.img you can thank yuweng for that but it is not fully working yet link will be replaced once fully working is released
Steps
get phone to fastboot mode must be unlocked then use the twrp recovery from downloads via this command on your adb/fastboot installed computer connected to phone :
Code:
fastboot flash recovery twrp_first[1].img
Reboot phone to recovery
go to wipe advanced wipe wipe data and system only
go back to home menu open advanced then terminal
enter this command exactly :
Code:
dd if=/external_sd/userdata.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/userdata
that will take a loooonnnnnnggggg time approximately 30-45 min
after it shows # in terminal again do this command :
Code:
dd if=/external_sd/system.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/system
reboot and it should take a loooonnnngggg time but eventually it will finish and you restored if not try asking some of the devs for pointers:laugh::fingers-crossed::highfive:
Make sure you thank everyone who helped aslezak gave me the commands and the userdata img as well as the system img yuweng provided the first semi working twrp (and a few later that are experimental)
if you want root check this thread https://forum.xda-developers.com/huawei-ascend-xt/help/huawei-ascend-xt2-h1711-t3689411/post75115521#post75115521
Your first link for the userdata image says file not found when you go to that link.
UPDATED USERDATA
freedomwarrior said:
Your first link for the userdata image says file not found when you go to that link.
Click to expand...
Click to collapse
Sim unlock
Hey guys,
has anyone managed to find a way to simunlock this phone? I bought one on blackfriday for $49 and since then its been sitting in my closet because it does not accept any other network's sim.
aslezak said:
UPDATED USERDATA
Click to expand...
Click to collapse
That one don't work either
FULL ROOT... ON MY HUAWEI XT2!! Twrp supersu and custom rom !!!
Sent from my HUAWEI H1711 using XDA Labs
The problem with this seems to be, at least for me, that a .bz2 file is not recognized by the recovery as an installable zip.
The dd trick worked for me, but the system image here, is not full stock. IT seems to have a mix of super_su and magisk in it.
Root is working, but I can't seem to mount system as r/w
So trying to figure this out. I used this image to do a restore, and my phone was rooted with magisk.
First time a program tried root, it said that super su was installed. When I went to another one, it said that magisk was installed.
Anyrate, at one time I was able to mount system r/w and make changes. Now it seems that I can't for whatever reason. I don't know exactly how I got it
to the state to be able to modify the system.
I actually pulled an entire copy of the rom at one time, with a dd command. Of course that can't be reflashed from twrp. But I'd like to be able to mount it somehow on a pc so I could do a stringsearch for all files that have an ro, in them to find the master files where the filesystems are mounted, and edit those....
crashburn833 said:
OK so this is where i tell you if you brick your phone and try this and it makes it worse i am not to blame. this has worked on three different phones that i have used no problem.That being said lets dive on in.
ONLY FOR THE H1711!!!!
Downloads (move them all to sd card root)
UPDATED USERDATA thank aslezak for that
https://uploadfiles.io/n5g32 and that
http://www.mediafire.com/file/gybldrcgw8h6x2w/twrp_first%5B1%5D.img you can thank yuweng for that but it is not fully working yet link will be replaced once fully working is released
Steps
get phone to fastboot mode must be unlocked then use the twrp recovery from downloads via this command on your adb/fastboot installed computer connected to phone :
Code:
fastboot flash recovery twrp_first[1].img
Reboot phone to recovery
go to wipe advanced wipe wipe data and system only
go back to home menu open advanced then terminal
enter this command exactly :
Code:
dd if=/external_sd/userdata.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/userdata
that will take a loooonnnnnnggggg time approximately 30-45 min
after it shows # in terminal again do this command :
Code:
dd if=/external_sd/system.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/system
reboot and it should take a loooonnnngggg time but eventually it will finish and you restored if not try asking some of the devs for pointers:laugh::fingers-crossed::highfive:
Make sure you thank everyone who helped aslezak gave me the commands and the userdata img as well as the system img yuweng provided the first semi working twrp (and a few later that are experimental)
if you want root check this thread https://forum.xda-developers.com/huawei-ascend-xt/help/huawei-ascend-xt2-h1711-t3689411/post75115521#post75115521
Click to expand...
Click to collapse
the system.img requires a monthly membership, could an updated link using something like mega or mediafire be created please?
one789 said:
FULL ROOT... ON MY HUAWEI XT2!! Twrp supersu and custom rom !!!
Sent from my HUAWEI H1711 using XDA Labs
Click to expand...
Click to collapse
what custom rom?
HELP PLEEEASE! Bricked h1711
Badly need mmcblk0.img for H1711! Had TWRP and phone was rooted but I screwed up and flashed a wrong IMG. Now I have the dreaded QHSUSB_BULK issue. Nothing but a black screen and a blue light. I googled "How to fix QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008 error" and went on forum.hovatek.com where it said "This error is an indication that the phone is hard bricked due to a corrupted Bootloader. It could occur randomly or after you make a change to the phone, causing the phone to go into Qualcomm Emergency Download Mode." It also stated that I could fix it by creating a bootable SD card using the phone's original mmcblk0.img file using a program called Win32DiskImager. I don't have mmcblk0.img and I can't boot into recovery or fastboot. PLEASE PLEASE HELP!!!! Also first two links in OP's post don't work. Any files or advise you can contribute would be GREATLY appreciated! THANKS!
mmcblk0.img would contain all phone partitions including those with personal information like IMEI number and the /data partition that should not be shared.
Nobody should be sharing that without understanding it contains their IMEI number and other possibly personal information in /data and I'm sure it would be at least 8-10GB.
And what would you do with the file anyway if you can't get into fastboot or recovery?
Whit3Rabbit said:
Badly need mmcblk0.img for H1711! Hard bricked Dreaded QHSUSB_BULK issue. Need mmcblk0.img PLEASE PLEASE HELP!!!! I've lost recovery and fastboot! Nothing but a black screen and a blue light.
Click to expand...
Click to collapse
divineBliss said:
mmcblk0.img would contain all phone partitions including those with personal information like IMEI number and the /data partition that should not be shared.
Nobody should be sharing that without understanding it contains their IMEI number and other possibly personal information in /data and I'm sure it would be at least 8-10GB.
And what would you do with the file anyway if you can't get into fastboot or recovery?
Click to expand...
Click to collapse
What do you recommend I do? All I have is a black screen and a blue light? thank you btw
If it won't go into fastboot mode and won't boot, I think only Huawei can fix it.
Whit3Rabbit said:
What do you recommend I do? All I have is a black screen and a blue light? thank you btw
Click to expand...
Click to collapse
divineBliss said:
If it won't go into fastboot mode and won't boot, I think only Huawei can fix it.
Click to expand...
Click to collapse
That's what I was afraid of Thank you for the quick response.
Whit3Rabbit said:
Badly need mmcblk0.img for H1711! Had TWRP and phone was rooted but I screwed up and flashed a wrong IMG. Now I have the dreaded QHSUSB_BULK issue. Nothing but a black screen and a blue light. I googled "How to fix QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008 error" and went on forum.hovatek.com where it said "This error is an indication that the phone is hard bricked due to a corrupted Bootloader. It could occur randomly or after you make a change to the phone, causing the phone to go into Qualcomm Emergency Download Mode." It also stated that I could fix it by creating a bootable SD card using the phone's original mmcblk0.img file using a program called Win32DiskImager. I don't have mmcblk0.img and I can't boot into recovery or fastboot. PLEASE PLEASE HELP!!!! Also first two links in OP's post don't work. Any files or advise you can contribute would be GREATLY appreciated! THANKS!
Click to expand...
Click to collapse
What is the link to the info you found?
I have the image you need, but it is 15 GIGs in size, and there is no practical way to send that. I also have a system image, and a boot image with magisk in it, as per the OP.
P.M. me.
I don't see how you can recover this if you don't have recovery or fastboot, and can't boot into the phone. If the bootloader is corrupted, well I just don't know.
Can you get into twrp?
You do know that there are two recoveriess, one erecovery and another recovery.
It seems that POWER and VOL up may get you into one, and POWER and VOL down may get you into another one.
NOTE: I KNOW you can't flash the image via fastboot, cause I tried it. it is just to big.
The files are all to big to post here....
https://nofile.io/f/2sfHn8teU1s/system.img.bz2 I put this up 6 days ago for someone else. I don't know how long the link is good for.
This is the system image from the non-working link. You will need to untar it.
https://nofile.io/f/2sfHn8teU1s/system.img.bz2 <<<<<<<<<< file from Original Post
https://nofile.io/f/vTRffT3CM0s/erecovery.zip <<<<<<<<<< erecovery is same as stock recovery
https://nofile.io/f/3DRA4bYjdsq/twrp-xt2.7z <<<<<<<<<< Hweng's original twrp
https://nofile.io/f/uAET5bTqQVk/patched_boot.zip <<<<<< bootloader patched with magisk for a root that does not touch the system partition.
I'll try to put the 15 gig mmblockp0 up here if it will take it, but it is at the office.
I hope this helps.
I now also have a virgin system image, stock. The image given above appears to also have supersu installed it int.
at least it has a su in the system image. Where magisk, just patches the boot image as I understand it.
Any luck on that stock system.img? I formatted mine like an idiot and now sitting on a phone with no OS
same as above, i will even take the rooted system.img i have all other files needed.
I'm a little bit of a noob at all of this but could someone explain to me how they got twrp and root on their xt2? I can really only process step by step and I haven't found that anywhere yet. I'm getting this phone later today so it'd be really cool to get root on it
littletech said:
I'm a little bit of a noob at all of this but could someone explain to me how they got twrp and root on their xt2? I can really only process step by step and I haven't found that anywhere yet. I'm getting this phone later today so it'd be really cool to get root on it
Click to expand...
Click to collapse
step by step root > https://forum.xda-developers.com/hu...ooting-restoring-huawei-elate-h1711z-t3764391
the files for root are the same for the Elate and the XT2
Blue light black screen fix
Whit3Rabbit said:
That's what I was afraid of Thank you for the quick response.
Click to expand...
Click to collapse
My device suffered the same fate, only a blue light black screen unable to enter boot or recovery. I slowly removed the back cover using my fingernails and removed the two screws holding the metal plate above battery on the right. Popped the left most plug to disconnect the power flow and allow phone to power off completely. Be careful not to touch any of the metal near the plug or you will short. I plugged it back in and held volume down while I inserted USB connected to computer. Tada!! Back in action fastboot ready... So OK now what?? I can't seem to be able to flash an update. Zip just keeps saying failed to load, and system image is too big. Can someone point me to the correct files I need to get her working again? Thanks in advance.
Experimental, Not tested.
But if u have hardbricked device u can test it.
So apparently when booting Qualcomm tries to boot internal flash then external and finally OTG, if its mounted, then it gives up 9008 mode or nothing.
However, if we flash the partition layout for our device, it can rework where each partition is on the flash memory and point to it and boot it.
Instructions:
1. Download your device Loader.img or u can create Loader.img from another exact device using cmd, twrp terminal or android terminal using
adb shell
su
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
2. Use Win32 Image Writer to flash the image to a working sdcard, which is same size as your device internal or higher is best.
3.force to your device to fastboot mode by using key combination which apply to your device.
4.if it boot to fastboot, then flash fastboot ROM, or trying to flash twrp.
Contributors:
VK84663
Information:
Statue: Experimental
Reserve
Screenshot
VK84663 said:
Experimental, Not tested.
But if u have hardbricked device u can test it.
So apparently when booting Qualcomm tries to boot internal flash then external and finally OTG, if its mounted, then it gives up 9008 mode or nothing.
However, if we flash the partition layout for our device, it can rework where each partition is on the flash memory and point to it and boot it.
Instructions:
1. Download your device Loader.img or u can create Loader.img from another exact device using cmd, twrp terminal or android terminal using
adb shell
su
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
2. Use Win32 Image Writer to flash the image to a working sdcard, which is same size as your device internal or higher is best.
3.force to your device to fastboot mode by using key combination which apply to your device.
4.if it boot to fastboot, then flash fastboot ROM, or trying to flash twrp.
Contributors:
VK84663
Information:
Statue: Experimental
Click to expand...
Click to collapse
Can u tell me in
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
why sector count is 168960 and not 172032?
{(303103 - 131072) + 1}= 172032
Or am i making some mistake?
I want to know why are we taking 168960 sectors? Why not more or why not less?
If u think this is very noob question, plz enlighten me