Database Info

Failed to restore fastboot following petrov.0's GUIDE

Hi everyone,
I have received my new Idol 3 4.7 (6039Y, european version) yesterday. I was stupid enough to apply all proposed updates before reading the forums thoroughly, so I got stuck with a 01005 build, with fastboot disabled.
I followed petrov.0’s guide to restore fastboot: http://forum.xda-developers.com/idol-3/development/6039-guide-how-to-return-fastboot-t3201077 or at least I tried.
I chose the files for "6039Y (repartitioned by following the repartitioning guide)" in the hope that it would save me some further work. QFIL seemed happy, but on restart, there was a message complaining about something like "unencryption failed", then saying that it was necessary to wipe the memory and perform factory reset. Then the phone spent some time wiping the data, and reboot took me to the stock recovery with a big nasty red error message.
So I used Alcatel Mobile Upgrade to restore the stock system, which went fine, but I was still stuck with a 01005 build. Then I tried again to follow petrov.0’s instructions, now using the files for "6039Y (8GB stock partition sizes)". According to QFIL's log, all went fine (except it waited forever in the final step, after the phone rebooted).
Once rebooted, the phone works ok, "adb devices" lists the phone, but "fastboot devices" still doesn’t.
Does anyone have the same problem? Any idea on how to solve it?
P.S.: this is my first post so I can't reply to petrov.0’s thread, and I couldn't find a Q&A thread on this subject, so here it is.

Fastboot -i 0x1bbb devices should be the right syntax. You have to directly adresy the devices by add “-i 0x1bbb“. Next zimě try to use search and read a little before posting stupid questions.
?

DallasCZ said:
Fastboot -i 0x1bbb devices should be the right syntax. You have to directly adresy the devices by add “-i 0x1bbb“. Next zimě try to use search and read a little before posting stupid questions.
Click to expand...
Click to collapse
No need to be rude : of course, I also tested the "fastboot -i 0x1bbb devices" with no more success.
(AFAIK, the -i option is just a filter: am I wrong?)

Turns out I was even more stupid than DallasCZ thought: my problem was that I used the fastboot commands in recovery mode rather than fastboot mode!
In case anyone as dumb as I passes by: use "adb reboot-bootloader" before trying any fastboot command.
And I confirm that the phone is NOT listed if I omit the -i option. The man page is really not clear about that: maybe the XDA-University guide about fastboot http://forum.xda-developers.com/showthread.php?t=2277112 could mention this kind of quirk?
Sorry for the noise.

I really have failed to restore fastboot commands using @petrov.0 's guide.
The problem I had having failed at flashing a modified OTA update file...well to cut a long story short I resorted to using Alcatels Mobile Upgrade Q 4.9.2 to fix my phone. I have no windows so was running the program on Linux host using VirtualBox. After loads of trouble with the drivers with 64 bit windows XP finally got everything to work using Windows 7.
I thought it would now be simple to restore fastboot commands using QFIL and to get my awesome 16GB internal memory back but despite phone definitely being in download mode and the phone showing up as Android HS-USB QDLoader 9008 on COM6 and QFIL automatically choosing COM6 etc and following everything in the guide as it should be I got an error when I hit the download button. Something about the phone not being in Firehose mode. I tried again and this time the error was about Sahara.
Anyone have any ideas?! Is it perhaps just not possible through Virtualbox?
Please help me! I want my 16GB internal memory back!
(phone is 6039Y-2AALWE7 and Upgrade Q updated it from 1AB2AZ22 to 1AJEAZE0)

fastboot - no permisions
deleted - found a simple solution.... for fastboot command in linux you need "sudo"!
Thank you

deleted
please a moderator wipe this post

gridmuncher said:
I really have failed to restore fastboot commands using @petrov.0 's guide.
The problem I had having failed at flashing a modified OTA update file...well to cut a long story short I resorted to using Alcatels Mobile Upgrade Q 4.9.2 to fix my phone. I have no windows so was running the program on Linux host using VirtualBox. After loads of trouble with the drivers with 64 bit windows XP finally got everything to work using Windows 7.
I thought it would now be simple to restore fastboot commands using QFIL and to get my awesome 16GB internal memory back but despite phone definitely being in download mode and the phone showing up as Android HS-USB QDLoader 9008 on COM6 and QFIL automatically choosing COM6 etc and following everything in the guide as it should be I got an error when I hit the download button. Something about the phone not being in Firehose mode. I tried again and this time the error was about Sahara.
Anyone have any ideas?! Is it perhaps just not possible through Virtualbox?
Please help me! I want my 16GB internal memory back!
(phone is 6039Y-2AALWE7 and Upgrade Q updated it from 1AB2AZ22 to 1AJEAZE0)
Click to expand...
Click to collapse
Any progress with this ?!? I'm a Linux user too, but I must admit that for this process I had to start my dusty Windows installation. As for the second attempt ... if the first one fails you must restart the phone in download mode again.

petrov.0 said:
Any progress with this ?
Click to expand...
Click to collapse
Sadly no. I don't understand why Upgrade Q would work in Virtualbox but QFIL doesn't. Still get the firehose error:
NOP: Fail Code: 10
Unable to send FireHose NOP, Device is not in Firehose mode!
Download Fail: System.Exception: Failed to send Firehose NOP to the phone
As I said before the phone is definitely in download mode and shows up in device manager correctly. I tried altering the USB filter in Virtualbox to be less device specific and a few other things, plugging unplugging, different usb cable, different usb port on laptop etc but no luck.
I might try a different Windows version but I think I'll probably resort to using a friends computer at some point.
Don't want to dual-boot windows as my laptop HDD is toooooooooo full and it would involve altering a few of my partitions etc.

T-Mobile LG G5 H30 Boot issues

I discovered a forum pertaining to the G5 a few days ago for methods of rooting the device (http://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-t3384526). To the best of my abilities, I believe I followed each step correctly. After I used the LGUP tool to install the file while the device was in download mode, it began boot-looping on the initial boot screen with an error message displaying "boot verification failed". I found a post on the same forum from someone who was experiencing the same error on their device. Tungkick posted a response that provided a solution to the issue; "IF Boot Verification Failed error > download stock full flash again>> enabable usb debugging + oem unlock> adb reboot bootloader> fastboot oem unlock> then up file tot add twrp again." I downloaded the stock file and used LGUP to flash it to the device.
I believe I made the mistake of selecting "upgrade" instead of "refurbish" before I initiated the flash. When the file finished installing, the screen on my device went black. Since then, I've been incapable of booting my phone up. When I connect it to my laptop, the Device Manager reads it as: "Qualcomm HS-USB QDLoader 9008". I researched some methods but wasn't successful in finding one that fixed my phone. Although, I could've found a site that provided a solution but I might've failed to follow the instructions properly. I assure you I gave my best effort to fix this issue myself, but I'm desperate to seek help from anyone at this point.
I would sincerely appreciate any feedback that would assist in resolving this issue. Here are the Web addresses:
(1) http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
(2) http://www.androidbrick.com/unbrick...-you-have-the-right-kind-of-rom-qhsusb_dload/
(3) http://www.androidbrick.com/ultimat...agons-are-unbrickable-qhsusb_dload_qpst_qfil/

Coolpad Modena E501 scatter-file

Hello, I'm really new here, so I apologize if I posted in the wrong category or if I ask something that is considered a stupid question, but as I'm still new, I must ask so I can learn.
I'm currently trying to unbrick a Coolpad Modena E501, it only shows logo and hangs in there. I can access fastboot and bootloader but it is not unlocked cause every command from ADB returns unknown.
I'm trying to patch it with YGDP and it constantly says unknown error and quits after 0 seconds and for SP Flash tool I dont have a scatter file so I cant flash, and cant for the life of me find one.
I have a device which is the same model and is working and tried pulling out scatter file from it using MTK droid tool, but the blocks are empty, it doesnt show anything except bmtpool (idk what it is).
Both devices are rooted, but the bricked one doesnt have enabled USB Debugging.
If someone could give me some advice, or if you need more info or what I did in more insight, please feel free to reply.
If anyone by any chance has or knows where/how to get the scatter file that goes into SP flash tool and is compatible with my device, please say.
Thank you.

Also, every fastboot command returns "FAILED (remote: unknown command)". Whatever I try to do.

Blackview Tab 8 unlocked Bootloader, but how to magisk?

Hi,
so with this Tutorial i was able to unlock the bootloader of the Blackview tab 8.
but i just could not find any way to flash magisk.
- "fastboot boot patched_img.img" and "fastboot flash boot patched_img.img" gave me "fastboot: error: Couldn't parse partition size '0x'"
- "fastboot flash:raw boot boot.img" was able to flash the patched_boot.img (a twrp i tried to port as well), but then i was stuck at blackview logo (SOFTBRICK)
- SPD Research Tool R24.0.0003 was able to flash patched_boot.img, but same stuck at logo (SOFTBRICK)
The only way i was able to unbrick it, involved opening back cover and disconnecting the battery and reconnecting it again.
then put research tool to download mode and flash stock img
I'm hoping for some advices, what i could try to get magisk flashed
- Tab8 Firmware (DK_SC9863A_P30_5G_10.0_Tab8_EEA_20201022_V1.0)
- SPD Research Tool R24 (there are 2 other tools but afaik research tool is the only one, where i can choose which partitions to flash)
best regards
Oxo

Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards

I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?

nr0000000 said:
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
Click to expand...
Click to collapse
I did it like described in the tutorial i linked. did you use linux? maybe in a VM or so, to use the .sh script. AFAIK it doesnt work with windows
also dont forget to activate "OEM unlocking" in dev options
StormChaser1337 said:
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
Click to expand...
Click to collapse
i dont know about test point actually. you can open it pretty easily and just disconnect battery. then connect again, use sdp tool and start the flash process, then press vol- and hold it while pluging in usb cable. thats what i do, if im stuck and cant do anything else.
regarding button combination, i'm not sure. usually i use adb reboot bootloader.
Also for the Blackview Tab 8 you need to extract keys from your vbmeta.img and sign it differently, also every other .img you wanna flash, like patched magisk boot.img. i successfully rooted mine some time ago, but i flashed some magisk modules and something went wrong and i ended up bootlooping. now im trying to root again.
somehow i cant flash the vbmeta.img. i dont remember if i did anything different last time.
all the stuff i did to get it rooted, i have taken from that hovatek forum.
edit: uploaded Stock Rom Images and stuff like for example a magsik patched boot image, which got repacked with android image kitchen then signed and repacked again with avbtool here
PS: dont have time to invest to this atm, also i just read that there was a update sometime this year which i didnt get, so maybe that changed some stuff.

I was considering buying this Blackview tablet and before I ordered it I got in touch with the Blackview home people in Hong Kong. They were extremely UNHELPFUL AND EVEN RUDE (not unusual for the chinese). As far as I am concerned this mob does not deserve to be supported and having a product that is so difficult to do any tinkering with precludes it from my list for sure. It is so time for consumers to DEMAND that any product that does not give explicit instructions as to unlocking and flashing is not supported. Why is it not possible in this day and age for this to happen. OK I know why but you get my meaning.

Question ROG 5s program speaks firehose protocol while your target is speaking sahara (Actual FIX)

Edit: I am keeping the information below intact, just incase someone goes through the same issues that I had gone through.
My recommendation is follow through with Johnny886 video on his installation guide and just skip any steps that aren't applicable to your set up. I recommend using his 0-update_image_edl.bat and not using Qfil or xiaomi. His video ends up showing most of the steps required to accomplish the repair, with exception of showing the phone and when you have to bring your phone into bootloader mode and what not.
I can personally attest to the fact this does bring a hard bricked phone from the grave. When I mean hard bricked, I mean black screen and in edl mode (shows up as a usb devices or port on your PC).
I am not a regular on these forums so I probably won't be here for long. I'll help if I see your posts, if I can help.
//////////////////////////////////////////////////////
Hello,
I am having issues installing johnny 886 ROG 5s firmware install via any method (Qfil, xiaomi flash, and update image edl windows batch file).
It says that the program speaks firehose and the device speaks sahara protocol on a text file on my computer.
I tried using xiaomi flash, but it makes a device disconnect sound and fails to ping target via firehose. (I am guessing because device is speaking sahara protocol).
I tried using Qfil flat build, and running firehose_ddr.elf and rawprogram and patch files 0-6 and it starts running the firehose_ddr.elf but it also runs into an error. (sahara_rx_data:276 Unable to read packet header. Only read 0 bytes. ( I think this also relates to the program speaks Firehose / device speaks Sahara protocol issue.)
Anyone have a way forward with dealing with this firehose/sahara issue?
I am also in windows 10 test mode.
EDIT, Fix found:
So I found out what was wrong. It shows "program speaks firehose protocol while your target is speaking sahara" because I was using the ddr.elf file.
If you pay attention to it, which I didn't at first, it says this:
"
This can mean
1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13: prog_firehose_lite.elf)
2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target"
I found out you are suppose to use the prog_firehose_lite.elf file (or whatever file it say is the device programmer first).
When using the QFIL program, I was using the prog_firehose_ddr.elf and this caused the error to appear.
I will post an image showing how it is suppose to look like when configured correctly.
NOTE: (I ended up bricking my phone to the point of not having an accessible bootloader/recovery when ONLY using raw program 0 and patch 0 files). This made it so you can only turn on the phone using the - volume and power button and it gets stuck on the "republic of gamers" splash screen. I have a solution for that issue further down in the thread.

Trash.umu said:
Hello,
I am having issues installing johnny 886 ROG 5s firmware install via any method (Qfil, xiaomi flash, and update image edl windows batch file).
It says that the program speaks firehose and the device speaks sahara protocol on a text file on my computer.
I tried using xiaomi flash, but it makes a device disconnect sound and fails to ping target via firehose. (I am guessing because device is speaking sahara protocol).
I tried using Qfil flat build, and running firehose_ddr.elf and rawprogram and patch files 0-6 and it starts running the firehose_ddr.elf but it also runs into an error. (sahara_rx_data:276 Unable to read packet header. Only read 0 bytes. ( I think this also relates to the program speaks Firehose / device speaks Sahara protocol issue.)
Anyone have a way forward with dealing with this firehose/sahara issue?
I am also in windows 10 test mode.
Click to expand...
Click to collapse
Try here
Repair ROG Phone 5S through edl firmware, no need to unlock Bootloader to modify COUNTRY CN to WW
Success is disgusted by some people, and will not share any files for free in the future.
forum.xda-developers.com

JazonX said:
Try here
Repair ROG Phone 5S through edl firmware, no need to unlock Bootloader to modify COUNTRY CN to WW
Success is disgusted by some people, and will not share any files for free in the future.
forum.xda-developers.com
Click to expand...
Click to collapse
I did, but no one seems to be answering. Also, I am not sure if the error itself is related to the firmware, such as a setting in qfil or xiaomi needs to be changed somewhere. Other people seem to have similar issues on other phones but it didn't look like anyone actually replied to their question.

Trash.umu said:
I did, but no one seems to be answering. Also, I am not sure if the error itself is related to the firmware, such as a setting in qfil or xiaomi needs to be changed somewhere. Other people seem to have similar issues on other phones but it didn't look like anyone actually replied to their question.
Click to expand...
Click to collapse
You need to install the correct Qualcomm driver, and then your folder cannot have spaces or some unsupported characters.

After prompting the error, the phone needs to re-enter the edl mode, and then operate again.
Trash.umu said:
I did, but no one seems to be answering. Also, I am not sure if the error itself is related to the firmware, such as a setting in qfil or xiaomi needs to be changed somewhere. Other people seem to have similar issues on other phones but it didn't look like anyone actually replied to their question.
Click to expand...
Click to collapse
After prompting the error, the phone needs to re-enter the edl mode, and then operate again.

johnny886 said:
After prompting the error, the phone needs to re-enter the edl mode, and then operate again.
After prompting the error, the phone needs to re-enter the edl mode, and then operate again.
Click to expand...
Click to collapse
So my phone attempted to install the firmware but now it does not have a bootloader, it does not connect to the PC and it can only get up to the point of showing the republic of gamers logo and letters.
I am guessing the only way forward is opening this thing up or buying a new phone. Unless you have a way out of this?
1. It is no able to go into edl via computer through adb.
2. It does not appear on device manager nor disk management.
3. It does not have a recovery option appearing and pressing +volume and power button does nothing.
4. You can only press the - volume and power button, the regular power button does nothing and when using the - volume button and power button, it just gets stuck on the republic of gamers screen.
5. It does not go into edl mode when connected to either the bottom or the side port on the phone.
6. It does not connect to the computer even if you delete the device, the drivers, reinstall the drivers and device. reset the computer and device and all forms of these things in different orders.
If the only way forward is possibly removing the battery and maybe shorting two pins together, do you have an idea which pins these are?
EDIT, Fix found:
So I found out that if you connect the ROG 5s phones side port to the computer while it is frozen in the republic of gamers logo for about 20 minutes, it resets and the android recovery screen pops up with only the options of "try again" and "factory data reset" and appears as an asus I005D in universal serial bus devices on my device manager. Now that I have it connected to the PC, I have a way forward.
It appears as in recovery mode in adb. you can not do anything other than enter "adb devices" and "adb reboot edl"
forcing the phone into edl using the adb cmd of "adb reboot edl" makes the device appear as a port device. This will allow me to reinstall the firmware again using the QFIL program.

I seem to keep falling through the same loop of errors. I wonder if there is a firmware error somewhere or if my phone is somehow rejecting the firmware.
I will update if I get anywhere.

NOTE:
If for some reason you can not get your phone to turn on or it turns off as you press the recovery option.
You need to connect the usb port to provide power via the bottom port and NOT the side port.
I am not sure why it is required, maybe the bottom port energizes more things than the side port does and it causes this fault. If you have both ports connected, it disconnects the bottom port and automatically uses the side port.

Trash.umu said:
我似乎不断陷入同样的错误循环。我想知道某个地方是否存在固件错误，或者我的手机是否以某种方式拒绝了固件。
如果我到达任何地方，我会更新。
Click to expand...
Click to collapse
There is no error in the firmware, and it is only released after it has been tested and there is no problem.

johnny886 said:
There is no error in the firmware, and it is only released after it has been tested and there is no problem.
Click to expand...
Click to collapse
I'll attempt to figure out why my phone isn't working properly. It may take awhile. Maybe it has to do with multiple attempts of installing the same firmware, or it could be that some of my phones components are already dying and it is just a coincidence.

NOTE: My phone kept failing to properly download johnny886 firmware because my phone (in particular) kept requiring me to switch between the side and bottom ports to keep my phone alive. I am unsure why I this was the case but I was able to finally install the firmware on my phone and my phone is now up and running properly.
I have to give thanks to johnny886 for his files, his video and his efforts. If not for him, my phone would still be a brick.