Hi everyone,
I'm currently using Hisense Pureshot aka HS-L671, using android Lollipop 5.0.2. It has Snapdragon 415 MSM8929, which is very similiar to Snapdragon 615 MSM8939, but with some missing feature (just like rip-off version of SD615). AFAIK currently there are only two phones use this SD415, the other one is Micromax Canvas Nitro 4G (E455) (3, if we count in the 5,5 inch variant of Pureshot+/HS-L695). That's why the documentation is still very scarce.
Edit : it seems there are several phones using this SoC now. I am currently researching about j7
Main Purpose
I post this thread for two main reasons :
1. To do full backup of my current phone, without root or modifiying any existing partitions (as I do below with my previous phone). This is to ensure I can revert back any modified phone to its original state, should we need to claim for RMA in case of hardware failure (not software). I know reverting to original state is possible to be done by flashing rooted stock ROM; then unroot afterward. But AFAIK, full unroot will leave trail of modified timestamp in /system partition. I don't want any trail of modification. (preferred if possible)
2. After backup, I will take the recovery.img and boot.img to compile TWRP in BBQLinux. Then flash it back to the phone. Boot up to TWRP and flash SuperSU.zip to obtain root access. Then I will proceed on a lot of modifications which require root. If number 1 cannot be done first, I have no problem if there is a way to obtain root first, then do the backup later using different tool.
Previous experience with SD200
Based on my experience with previous phone, Andromax C2 aka Hisense AD688G (1st gen), Android JB 4.3, Snapdragon 200 MSM8610; it can boot directly to Qualcomm MMC Storage Mode, which maybe known as Emergency Host DownLoad or Qualcomm HS-USB Diagnostics 9006 (CMIIW). To enter this mode, I need to turn off the phone, unplug the battery, holding down Power + Volume Down button, while connecting it to PC (Win 7 64 bit) via USB cable (I have installed qualcomm driver before). Then it will pop up a lot of prompt to format the drives, which I ignore all of them. In the device manager, it will be detected as Qualcomm MMC Storage. From there, I can proceed on backup every partition of the phone using HDDRaw copy, partition guru or emmc raw tool (preferred one). This can be done without root or any modification to the phone. Which is why this method of backup is preferred, since i can always start with "clean slate", should anything wrong happen (restore using the same method). And it doesn't leave trail of folder modification timestamp as it will be if I flash rooted stock ROM then unroot.
Power button + combination
Now, with the latest snapdragon family 410, 615, including 415 above, it seems there is no way to boot directly to the same Qualcomm MMC Storage / (as far as I read till now from tirta.agung thread). I have tried several combination, and the result is below.
Power : Turn on Phone
Power + Vol Up : nothing happen. If not followed by next action, Phone boot normally
Power + Vol Up, followed by holding vol down at the second logo : Enter safe mode
Power + Vol down : Enter firmware status (Official)
Power + Vol down, followed by holding Power : Enter Recovery mode
In the recovery menu, there is a menu to "Reboot to bootloader", which will boot the phone to Fastboot downloading mode.
Power + Vol Up + Vol Down : TF update
Combining with USB cable
Power + Plug in USB cable : Turn On Phone
Vol Up + Plug USB : Enter Fastboot downloading
Vol up + Vol down + Plug USB : TF Update. Seems like the USB become the power button
Vol Up + Power + Plug USB, Release Power button after vibrate : EngTest mode, diagnostic mode. In QPST will be detected as the diagnostic port, seems to be Hisense Proprietary one.
Unplug battery : Any combination of power button, vol up and vol down didn't give any response or vibration, nothing detected in device manager or usb deview.
Using adb, only 3 reboot choice : reboot, reboot recovery, reboot bootloader. Reboot edl don't work (wonder if anyone success at another phone)
Using fastboot, is similiar to adb : fastboot reboot and fastboot reboot bootloader. Reboot edl don't work either. Fastboot oem unlock do nothing as well.
Enter Qualcomm HS-USB QDLoader 9008
It seems the Engtest mode boot in android OS, as I can see the prompt asking for USB connection mode (MTP, CD ROM, charge only etc). And IDK if it is a bug, but every time I boot to this Engtest, the next reboot always remove all of my account (Google, whatsapp, mysmartfren (my ISP)). I need to add back, resync contact, resetting gmail and etc. Later, I discovered that i don't need this engtest anymore. As long as I have installed all driver : Qualcomm, Hisense and QPST; every time I connect the USB when the phone is on, it will detected as diagnostic mode.
From this diagnostic mode, I can switch the phone to Download mode (9008), by using eMMC software download (QPST) > Switch device to DLoad; or using EFS Pro - Qualcomm NV Tools > Change mode to Download Mode. Phone will reboot, screen off and vibrate a while. Diagnostic port now is closed and it will add a new port, Q/QCP-XXX - Sahara Memory Dump. Device manager will detect Qualcomm HS-USB QDLoader 9008.
From this mode, AFAIK I still need MPRG8929.hex and 8929_msmimage.mbn to boot it to 9006 mode. But the current available hex/bin and mbn only for 8974, 8916 and 8939 (8936 mbn). Looking to the build.prop and the lib folder of my phone, it seems to have a lot of similiarity with MSM8939. So i was thinking to use the MPRG and mbn from MSM8939. But I still haven't tried it yet, as i need more confirmation. This is my main phone, that's why i am very careful with it, my backup phone is too weak now for daily usage.
BTW, I am using latest WHQL qualcomm driver, version 2.1.0.5 and Hisense driver directly from the phone's CDROM iso. Using universal driver installer also give the same driver. QPST 2.7 build 425.1. Build 422 give me the same result. Main PC is Win 7 Ultimate 64 bit SP1. I have tested it in XP SP3, and give the same result, so not the WHQL driver signing problem.
TF Update
Someone point me out about TF Update file for HS-L965 (the 5.5 inch variant). This file supposed to be flashed through TF Update process (Power + Vol Up + Vol Down). I manage to download it and of course i don't flash it to my phone, since it is from different version. I try to extract out recovery.img and boot.img, by mounting it or open it from archive program. Disk Internal Linux reader can mount the bin properly and show up with 20 something partition, which is very similiar to what I see from qualcomm partitions. I try to open each partition, of course it fails, as it is not ext4 file system (even /system also fail). Try to create image from recovery, boot and system partition; and it manage to be extracted out. But the result is very different from the typical raw img. It doesn't contain proper file header for recovery, boot, and system .img. The hex header supposed to be "ANDROID". But all of the extracted img don't have it. If I unpack the boot.img and recovery.img, carliv unpacker also give no folder structured result, only compressed ram-disk. Try to use ext4unpacker also no luck. So any image extracted is useless, as they don't seems to have the correct file header (or maybe it is wrong reading from the linux reader).
I have spent this whole week trying to find the way to boot the phone to 9006 mode. I have googled a lot, have finisihed reading from 1st page to the last page
[PROJECT] Reviving Hard Bricked YU (QLoader 9008 Mode)
[R&D][QUALCOMM] Using QDL, EHostDL and DIAG interfaces & features
and some other thread. I might miss some info, partially because I sometimes read it in half drowsy state. So, I'll be glad to be pointed out the missing info.
Alternative root method
I have searched for the canvas nitro 4G rooting process, and there is no answer yet at http://forum.xda-developers.com/general/xda-assist/root-micromax-canvas-nitro-3-4g-e455-t3225783 and http://forum.xda-developers.com/android/help/how-to-root-micromax-canvas-nitro-4g-t3209976.
I also know about kingroot. But there are a lot of privacy issues with that program, so I want to stay away from it. From my friend, they said they've tried the latest version, but still fail to root. So I don't try it anymore. But if there is no other way, I might give it a shot as well. A lot of other root tools also fail to root this phone. So, flashing SuperSU.zip from TWRP, seems to be the only way to root it.
Question
From all information above, now here comes the questions :
1. Is there a way to enter 9006 Mode without doing any modification or flash programmer file in the latest qualcomm SoC ? (SD410, SD415, SD615, SD810 above)
2. What the MPRG and MBN really do when flashed to device? Do they stay at the emmc, means they replace some partition inside the Phone? Or they just stay at RAM and will be wiped out on the next reboot; so we need to flash it again if we want to enter 9006 from 9008?
3. What is the risk of using wrong MPRG and MBN file from different SoC? As I wanna try to use the ones from MSM8916 and MSM8939 (MSM8936). I have downloaded it already, but too scare to use it.
4. How we can know we are using the correct MPRG and MBN file? How they were created at first? Is it possible to create it from some partition in the phone?
5. How to extract the TF update .bin file properly? And how they were created at first? And it is possible to create it our self, without the need of any signature/certificate from the vendor?
Sorry if there are too many questions and this thread is very long. I don't expect all questions to be answered though. As long as the main purpose above is achieved, that's nice already.
If there is any additional info needed, I will provided it later.
Thanks in Advance.
Hi,
I am also looking for similar solution. Hope somebody comes up with one
Hii i want if there is any root solution for canvas nitro 4g
Have been using this phone for 3 months without any root solution. I will answer my own question
1. No other way found to enter 9006 diag mode
2. I checked at other MSM8916 phone, flashing the MPRG/MBN file means permanent modification, which cannot be reverted again.
3. Haven't tried, as afraid of point 2
4. Also give up, as point 2
5. Still not yet discover the way.
Until today, still no method for rooting SD415 based phone. Have tried :
1. Kingroot, always test the latest version, both PC and android app
2. iroot/vroot, both pc and android
3. Kingoroot, both pc and android
4. Pingpong
5. Towelroot (ofc failed)
6. Framaroot (also outdated)
7. Mobilego
8. Flashing SuperSu.zip, failed in zip signature verification (ofc as still using stock recovery)
Other option remain in compiling TWRP. But so far, I can't even finish compiling TWRP from Blade S6, always got error message.
If compiling keep getting error, I need to find way to extract out the stock recovery image, either from the phone itself (without root) or from the tf update .bin. Then i just only need to dirty port the TWRP from similiar phone, just by changing the recovery.fstab. Or I could just simply upload to CWM, to build the CWM recovery online.
Desmanto said:
Hi everyone,
I'm currently using Hisense Pureshot aka HS-L671, using android Lollipop 5.0.2. It has Snapdragon 415 MSM8929, which is very similiar to Snapdragon 615 MSM8939, but with some missing feature (just like rip-off version of SD615). AFAIK currently there are only two phones use this SD415, the other one is Micromax Canvas Nitro 4G (E455) (3, if we count in the 5,5 inch variant of Pureshot+/HS-L695). That's why the documentation is still very scarce.
Edit : it seems there are several phones using this SoC now. I am currently researching about j7
Main Purpose
I post this thread for two main reasons :
1. To do full backup of my current phone, without root or modifiying any existing partitions (as I do below with my previous phone). This is to ensure I can revert back any modified phone to its original state, should we need to claim for RMA in case of hardware failure (not software). I know reverting to original state is possible to be done by flashing rooted stock ROM; then unroot afterward. But AFAIK, full unroot will leave trail of modified timestamp in /system partition. I don't want any trail of modification. (preferred if possible)
2. After backup, I will take the recovery.img and boot.img to compile TWRP in BBQLinux. Then flash it back to the phone. Boot up to TWRP and flash SuperSU.zip to obtain root access. Then I will proceed on a lot of modifications which require root. If number 1 cannot be done first, I have no problem if there is a way to obtain root first, then do the backup later using different tool.
Previous experience with SD200
Based on my experience with previous phone, Andromax C2 aka Hisense AD688G (1st gen), Android JB 4.3, Snapdragon 200 MSM8610; it can boot directly to Qualcomm MMC Storage Mode, which maybe known as Emergency Host DownLoad or Qualcomm HS-USB Diagnostics 9006 (CMIIW). To enter this mode, I need to turn off the phone, unplug the battery, holding down Power + Volume Down button, while connecting it to PC (Win 7 64 bit) via USB cable (I have installed qualcomm driver before). Then it will pop up a lot of prompt to format the drives, which I ignore all of them. In the device manager, it will be detected as Qualcomm MMC Storage. From there, I can proceed on backup every partition of the phone using HDDRaw copy, partition guru or emmc raw tool (preferred one). This can be done without root or any modification to the phone. Which is why this method of backup is preferred, since i can always start with "clean slate", should anything wrong happen (restore using the same method). And it doesn't leave trail of folder modification timestamp as it will be if I flash rooted stock ROM then unroot.
Power button + combination
Now, with the latest snapdragon family 410, 615, including 415 above, it seems there is no way to boot directly to the same Qualcomm MMC Storage / (as far as I read till now from tirta.agung thread). I have tried several combination, and the result is below.
Power : Turn on Phone
Power + Vol Up : nothing happen. If not followed by next action, Phone boot normally
Power + Vol Up, followed by holding vol down at the second logo : Enter safe mode
Power + Vol down : Enter firmware status (Official)
Power + Vol down, followed by holding Power : Enter Recovery mode
In the recovery menu, there is a menu to "Reboot to bootloader", which will boot the phone to Fastboot downloading mode.
Power + Vol Up + Vol Down : TF update
Combining with USB cable
Power + Plug in USB cable : Turn On Phone
Vol Up + Plug USB : Enter Fastboot downloading
Vol up + Vol down + Plug USB : TF Update. Seems like the USB become the power button
Vol Up + Power + Plug USB, Release Power button after vibrate : EngTest mode, diagnostic mode. In QPST will be detected as the diagnostic port, seems to be Hisense Proprietary one.
Unplug battery : Any combination of power button, vol up and vol down didn't give any response or vibration, nothing detected in device manager or usb deview.
Using adb, only 3 reboot choice : reboot, reboot recovery, reboot bootloader. Reboot edl don't work (wonder if anyone success at another phone)
Using fastboot, is similiar to adb : fastboot reboot and fastboot reboot bootloader. Reboot edl don't work either. Fastboot oem unlock do nothing as well.
Enter Qualcomm HS-USB QDLoader 9008
It seems the Engtest mode boot in android OS, as I can see the prompt asking for USB connection mode (MTP, CD ROM, charge only etc). And IDK if it is a bug, but every time I boot to this Engtest, the next reboot always remove all of my account (Google, whatsapp, mysmartfren (my ISP)). I need to add back, resync contact, resetting gmail and etc. Later, I discovered that i don't need this engtest anymore. As long as I have installed all driver : Qualcomm, Hisense and QPST; every time I connect the USB when the phone is on, it will detected as diagnostic mode.
From this diagnostic mode, I can switch the phone to Download mode (9008), by using eMMC software download (QPST) > Switch device to DLoad; or using EFS Pro - Qualcomm NV Tools > Change mode to Download Mode. Phone will reboot, screen off and vibrate a while. Diagnostic port now is closed and it will add a new port, Q/QCP-XXX - Sahara Memory Dump. Device manager will detect Qualcomm HS-USB QDLoader 9008.
From this mode, AFAIK I still need MPRG8929.hex and 8929_msmimage.mbn to boot it to 9006 mode. But the current available hex/bin and mbn only for 8974, 8916 and 8939 (8936 mbn). Looking to the build.prop and the lib folder of my phone, it seems to have a lot of similiarity with MSM8939. So i was thinking to use the MPRG and mbn from MSM8939. But I still haven't tried it yet, as i need more confirmation. This is my main phone, that's why i am very careful with it, my backup phone is too weak now for daily usage.
BTW, I am using latest WHQL qualcomm driver, version 2.1.0.5 and Hisense driver directly from the phone's CDROM iso. Using universal driver installer also give the same driver. QPST 2.7 build 425.1. Build 422 give me the same result. Main PC is Win 7 Ultimate 64 bit SP1. I have tested it in XP SP3, and give the same result, so not the WHQL driver signing problem.
TF Update
Someone point me out about TF Update file for HS-L965 (the 5.5 inch variant). This file supposed to be flashed through TF Update process (Power + Vol Up + Vol Down). I manage to download it and of course i don't flash it to my phone, since it is from different version. I try to extract out recovery.img and boot.img, by mounting it or open it from archive program. Disk Internal Linux reader can mount the bin properly and show up with 20 something partition, which is very similiar to what I see from qualcomm partitions. I try to open each partition, of course it fails, as it is not ext4 file system (even /system also fail). Try to create image from recovery, boot and system partition; and it manage to be extracted out. But the result is very different from the typical raw img. It doesn't contain proper file header for recovery, boot, and system .img. The hex header supposed to be "ANDROID". But all of the extracted img don't have it. If I unpack the boot.img and recovery.img, carliv unpacker also give no folder structured result, only compressed ram-disk. Try to use ext4unpacker also no luck. So any image extracted is useless, as they don't seems to have the correct file header (or maybe it is wrong reading from the linux reader).
I have spent this whole week trying to find the way to boot the phone to 9006 mode. I have googled a lot, have finisihed reading from 1st page to the last page
[PROJECT] Reviving Hard Bricked YU (QLoader 9008 Mode)
[R&D][QUALCOMM] Using QDL, EHostDL and DIAG interfaces & features
and some other thread. I might miss some info, partially because I sometimes read it in half drowsy state. So, I'll be glad to be pointed out the missing info.
Alternative root method
I have searched for the canvas nitro 4G rooting process, and there is no answer yet at http://forum.xda-developers.com/general/xda-assist/root-micromax-canvas-nitro-3-4g-e455-t3225783 and http://forum.xda-developers.com/android/help/how-to-root-micromax-canvas-nitro-4g-t3209976.
I also know about kingroot. But there are a lot of privacy issues with that program, so I want to stay away from it. From my friend, they said they've tried the latest version, but still fail to root. So I don't try it anymore. But if there is no other way, I might give it a shot as well. A lot of other root tools also fail to root this phone. So, flashing SuperSU.zip from TWRP, seems to be the only way to root it.
Question
From all information above, now here comes the questions :
1. Is there a way to enter 9006 Mode without doing any modification or flash programmer file in the latest qualcomm SoC ? (SD410, SD415, SD615, SD810 above)
2. What the MPRG and MBN really do when flashed to device? Do they stay at the emmc, means they replace some partition inside the Phone? Or they just stay at RAM and will be wiped out on the next reboot; so we need to flash it again if we want to enter 9006 from 9008?
3. What is the risk of using wrong MPRG and MBN file from different SoC? As I wanna try to use the ones from MSM8916 and MSM8939 (MSM8936). I have downloaded it already, but too scare to use it.
4. How we can know we are using the correct MPRG and MBN file? How they were created at first? Is it possible to create it from some partition in the phone?
5. How to extract the TF update .bin file properly? And how they were created at first? And it is possible to create it our self, without the need of any signature/certificate from the vendor?
Sorry if there are too many questions and this thread is very long. I don't expect all questions to be answered though. As long as the main purpose above is achieved, that's nice already.
If there is any additional info needed, I will provided it later.
Thanks in Advance.[/QUOTE
you have the file which i need
MPRG8939 hex file and mbn
could you please give me these ?
Click to expand...
Click to collapse
hiii
my nokia xl black screen dead ..
when phone connect to pc qulicom port detect but mcc strge not dispying .. plzz help
sry for bad english
Desmanto said:
Hi everyone,
I'm currently using Hisense Pureshot aka HS-L671, using android Lollipop 5.0.2. It has Snapdragon 415 MSM8929, which is very similiar to Snapdragon 615 MSM8939, but with some missing feature (just like rip-off version of SD615). AFAIK currently there are only two phones use this SD415, the other one is Micromax Canvas Nitro 4G (E455) (3, if we count in the 5,5 inch variant of Pureshot+/HS-L695). That's why the documentation is still very scarce.
Edit : it seems there are several phones using this SoC now. I am currently researching about j7
Main Purpose
I post this thread for two main reasons :
1. To do full backup of my current phone, without root or modifiying any existing partitions (as I do below with my previous phone). This is to ensure I can revert back any modified phone to its original state, should we need to claim for RMA in case of hardware failure (not software). I know reverting to original state is possible to be done by flashing rooted stock ROM; then unroot afterward. But AFAIK, full unroot will leave trail of modified timestamp in /system partition. I don't want any trail of modification. (preferred if possible)
2. After backup, I will take the recovery.img and boot.img to compile TWRP in BBQLinux. Then flash it back to the phone. Boot up to TWRP and flash SuperSU.zip to obtain root access. Then I will proceed on a lot of modifications which require root. If number 1 cannot be done first, I have no problem if there is a way to obtain root first, then do the backup later using different tool.
Previous experience with SD200
Based on my experience with previous phone, Andromax C2 aka Hisense AD688G (1st gen), Android JB 4.3, Snapdragon 200 MSM8610; it can boot directly to Qualcomm MMC Storage Mode, which maybe known as Emergency Host DownLoad or Qualcomm HS-USB Diagnostics 9006 (CMIIW). To enter this mode, I need to turn off the phone, unplug the battery, holding down Power + Volume Down button, while connecting it to PC (Win 7 64 bit) via USB cable (I have installed qualcomm driver before). Then it will pop up a lot of prompt to format the drives, which I ignore all of them. In the device manager, it will be detected as Qualcomm MMC Storage. From there, I can proceed on backup every partition of the phone using HDDRaw copy, partition guru or emmc raw tool (preferred one). This can be done without root or any modification to the phone. Which is why this method of backup is preferred, since i can always start with "clean slate", should anything wrong happen (restore using the same method). And it doesn't leave trail of folder modification timestamp as it will be if I flash rooted stock ROM then unroot.
Power button + combination
Now, with the latest snapdragon family 410, 615, including 415 above, it seems there is no way to boot directly to the same Qualcomm MMC Storage / (as far as I read till now from tirta.agung thread). I have tried several combination, and the result is below.
Power : Turn on Phone
Power + Vol Up : nothing happen. If not followed by next action, Phone boot normally
Power + Vol Up, followed by holding vol down at the second logo : Enter safe mode
Power + Vol down : Enter firmware status (Official)
Power + Vol down, followed by holding Power : Enter Recovery mode
In the recovery menu, there is a menu to "Reboot to bootloader", which will boot the phone to Fastboot downloading mode.
Power + Vol Up + Vol Down : TF update
Combining with USB cable
Power + Plug in USB cable : Turn On Phone
Vol Up + Plug USB : Enter Fastboot downloading
Vol up + Vol down + Plug USB : TF Update. Seems like the USB become the power button
Vol Up + Power + Plug USB, Release Power button after vibrate : EngTest mode, diagnostic mode. In QPST will be detected as the diagnostic port, seems to be Hisense Proprietary one.
Unplug battery : Any combination of power button, vol up and vol down didn't give any response or vibration, nothing detected in device manager or usb deview.
Using adb, only 3 reboot choice : reboot, reboot recovery, reboot bootloader. Reboot edl don't work (wonder if anyone success at another phone)
Using fastboot, is similiar to adb : fastboot reboot and fastboot reboot bootloader. Reboot edl don't work either. Fastboot oem unlock do nothing as well.
Enter Qualcomm HS-USB QDLoader 9008
It seems the Engtest mode boot in android OS, as I can see the prompt asking for USB connection mode (MTP, CD ROM, charge only etc). And IDK if it is a bug, but every time I boot to this Engtest, the next reboot always remove all of my account (Google, whatsapp, mysmartfren (my ISP)). I need to add back, resync contact, resetting gmail and etc. Later, I discovered that i don't need this engtest anymore. As long as I have installed all driver : Qualcomm, Hisense and QPST; every time I connect the USB when the phone is on, it will detected as diagnostic mode.
From this diagnostic mode, I can switch the phone to Download mode (9008), by using eMMC software download (QPST) > Switch device to DLoad; or using EFS Pro - Qualcomm NV Tools > Change mode to Download Mode. Phone will reboot, screen off and vibrate a while. Diagnostic port now is closed and it will add a new port, Q/QCP-XXX - Sahara Memory Dump. Device manager will detect Qualcomm HS-USB QDLoader 9008.
From this mode, AFAIK I still need MPRG8929.hex and 8929_msmimage.mbn to boot it to 9006 mode. But the current available hex/bin and mbn only for 8974, 8916 and 8939 (8936 mbn). Looking to the build.prop and the lib folder of my phone, it seems to have a lot of similiarity with MSM8939. So i was thinking to use the MPRG and mbn from MSM8939. But I still haven't tried it yet, as i need more confirmation. This is my main phone, that's why i am very careful with it, my backup phone is too weak now for daily usage.
BTW, I am using latest WHQL qualcomm driver, version 2.1.0.5 and Hisense driver directly from the phone's CDROM iso. Using universal driver installer also give the same driver. QPST 2.7 build 425.1. Build 422 give me the same result. Main PC is Win 7 Ultimate 64 bit SP1. I have tested it in XP SP3, and give the same result, so not the WHQL driver signing problem.
TF Update
Someone point me out about TF Update file for HS-L965 (the 5.5 inch variant). This file supposed to be flashed through TF Update process (Power + Vol Up + Vol Down). I manage to download it and of course i don't flash it to my phone, since it is from different version. I try to extract out recovery.img and boot.img, by mounting it or open it from archive program. Disk Internal Linux reader can mount the bin properly and show up with 20 something partition, which is very similiar to what I see from qualcomm partitions. I try to open each partition, of course it fails, as it is not ext4 file system (even /system also fail). Try to create image from recovery, boot and system partition; and it manage to be extracted out. But the result is very different from the typical raw img. It doesn't contain proper file header for recovery, boot, and system .img. The hex header supposed to be "ANDROID". But all of the extracted img don't have it. If I unpack the boot.img and recovery.img, carliv unpacker also give no folder structured result, only compressed ram-disk. Try to use ext4unpacker also no luck. So any image extracted is useless, as they don't seems to have the correct file header (or maybe it is wrong reading from the linux reader).
I have spent this whole week trying to find the way to boot the phone to 9006 mode. I have googled a lot, have finisihed reading from 1st page to the last page
[PROJECT] Reviving Hard Bricked YU (QLoader 9008 Mode)
[R&D][QUALCOMM] Using QDL, EHostDL and DIAG interfaces & features
and some other thread. I might miss some info, partially because I sometimes read it in half drowsy state. So, I'll be glad to be pointed out the missing info.
Alternative root method
I have searched for the canvas nitro 4G rooting process, and there is no answer yet at http://forum.xda-developers.com/general/xda-assist/root-micromax-canvas-nitro-3-4g-e455-t3225783 and http://forum.xda-developers.com/android/help/how-to-root-micromax-canvas-nitro-4g-t3209976.
I also know about kingroot. But there are a lot of privacy issues with that program, so I want to stay away from it. From my friend, they said they've tried the latest version, but still fail to root. So I don't try it anymore. But if there is no other way, I might give it a shot as well. A lot of other root tools also fail to root this phone. So, flashing SuperSU.zip from TWRP, seems to be the only way to root it.
Question
From all information above, now here comes the questions :
1. Is there a way to enter 9006 Mode without doing any modification or flash programmer file in the latest qualcomm SoC ? (SD410, SD415, SD615, SD810 above)
2. What the MPRG and MBN really do when flashed to device? Do they stay at the emmc, means they replace some partition inside the Phone? Or they just stay at RAM and will be wiped out on the next reboot; so we need to flash it again if we want to enter 9006 from 9008?
3. What is the risk of using wrong MPRG and MBN file from different SoC? As I wanna try to use the ones from MSM8916 and MSM8939 (MSM8936). I have downloaded it already, but too scare to use it.
4. How we can know we are using the correct MPRG and MBN file? How they were created at first? Is it possible to create it from some partition in the phone?
5. How to extract the TF update .bin file properly? And how they were created at first? And it is possible to create it our self, without the need of any signature/certificate from the vendor?
Sorry if there are too many questions and this thread is very long. I don't expect all questions to be answered though. As long as the main purpose above is achieved, that's nice already.
If there is any additional info needed, I will provided it later.
Thanks in Advance.
Click to expand...
Click to collapse
Hi ,
i am wondering if we can enable Qualcomm MMC Storage 9006 mode over the adb mode if phone is rooted. Thanks
oakerzaw said:
you have the file which i need
MPRG8939 hex file and mbn
could you please give me these
Click to expand...
Click to collapse
The hex and mbn file seems to be device spesific. You should find the one for your device. I also don't have for my phone, as the vendor don't provide us the stock firmware. You can try to visit needrom to see whether someone have uploaded the ROM for you device.
bluffmaster said:
Hi ,
i am wondering if we can enable Qualcomm MMC Storage 9006 mode over the adb mode if phone is rooted. Thanks
Click to expand...
Click to collapse
No hope till date. I have tried for almost 3 month back then. Until i directly take the risk and port TWRP from other SD615 device using the kernel from other Hisense device. I think it is the only way to root the phone for latest qualcomm chipset. I use the same method to root another SD617 phone. 9006 need some kind of the hex/mbn file to force it to boot that mode. Most of the tool now use QFIL, which use 9008 mode, not 9006 mode anymore.
My ot-5042x one touch pop 2 is hard-bricked ...... I bought this phone second hand, I didn't have any info about the phone apart of the alto45 written in the mainboard.
Phone were running 4.4.2 maybe custom rom and there were wifi and data problem so I wanted to flash it but it were in emmc storage mode so I couldn't use mobile uprade q (otu) and when I tried to flash recovery twrp for the device recovery went white screen then I noticed that all ot-5042 firmware in the internet were 4.4.4 so I wanted to upgrade to solve wifi problem then I used a complete backup of all partition from 5042x with twrp to flash the partition in emmc raw tool and I could use twrp but the system.img were to big for the partition so I did not try to fix but I flashe a russian firmware for 5042d and the problem started...
Phone is now in soft-hardbrick mode... Native recovery, no adb (not authorized) , no fastboot, in qdl9008 mode and I can't switch to 9006 to write full backup, and has battery problem and not get past the thired logo and turn off and tells battery 0% but not charging and turn off even if plugged in the computer. I think bootldoader corrupted and the RPM too so there no power management in the phone..... The backup was from orange Roya so I can't use Mobile upgrade q.... I really want it to get in mmc storage mode again !!!!!
Qualcomm HS-USB QDLoader 9008 samsung shv e110s
upload
-APQ0860.hex <--------------qualcomm
-0860_msimage.mbn <-------------- Main
-rawprogram_16GB.xml
-patch0.xml
Hi Desmanto,
From which software and how to force phone to boot 9008 QD loader mode to 9006 Qualcomm mass storage mode,
I will appreciate if you share any tutorial or method. thanks
Regards
Bluffmaster
Desmanto said:
Hi everyone,
I'm currently using Hisense Pureshot aka HS-L671, using android Lollipop 5.0.2. It has Snapdragon 415 MSM8929, which is very similiar to Snapdragon 615 MSM8939, but with some missing feature (just like rip-off version of SD615). AFAIK currently there are only two phones use this SD415, the other one is Micromax Canvas Nitro 4G (E455) (3, if we count in the 5,5 inch variant of Pureshot+/HS-L695). That's why the documentation is still very scarce.
Edit : it seems there are several phones using this SoC now. I am currently researching about j7
Main Purpose
I post this thread for two main reasons :
1. To do full backup of my current phone, without root or modifiying any existing partitions (as I do below with my previous phone). This is to ensure I can revert back any modified phone to its original state, should we need to claim for RMA in case of hardware failure (not software). I know reverting to original state is possible to be done by flashing rooted stock ROM; then unroot afterward. But AFAIK, full unroot will leave trail of modified timestamp in /system partition. I don't want any trail of modification. (preferred if possible)
2. After backup, I will take the recovery.img and boot.img to compile TWRP in BBQLinux. Then flash it back to the phone. Boot up to TWRP and flash SuperSU.zip to obtain root access. Then I will proceed on a lot of modifications which require root. If number 1 cannot be done first, I have no problem if there is a way to obtain root first, then do the backup later using different tool.
Previous experience with SD200
Based on my experience with previous phone, Andromax C2 aka Hisense AD688G (1st gen), Android JB 4.3, Snapdragon 200 MSM8610; it can boot directly to Qualcomm MMC Storage Mode, which maybe known as Emergency Host DownLoad or Qualcomm HS-USB Diagnostics 9006 (CMIIW). To enter this mode, I need to turn off the phone, unplug the battery, holding down Power + Volume Down button, while connecting it to PC (Win 7 64 bit) via USB cable (I have installed qualcomm driver before). Then it will pop up a lot of prompt to format the drives, which I ignore all of them. In the device manager, it will be detected as Qualcomm MMC Storage. From there, I can proceed on backup every partition of the phone using HDDRaw copy, partition guru or emmc raw tool (preferred one). This can be done without root or any modification to the phone. Which is why this method of backup is preferred, since i can always start with "clean slate", should anything wrong happen (restore using the same method). And it doesn't leave trail of folder modification timestamp as it will be if I flash rooted stock ROM then unroot.
Power button + combination
Now, with the latest snapdragon family 410, 615, including 415 above, it seems there is no way to boot directly to the same Qualcomm MMC Storage / (as far as I read till now from tirta.agung thread). I have tried several combination, and the result is below.
Power : Turn on Phone
Power + Vol Up : nothing happen. If not followed by next action, Phone boot normally
Power + Vol Up, followed by holding vol down at the second logo : Enter safe mode
Power + Vol down : Enter firmware status (Official)
Power + Vol down, followed by holding Power : Enter Recovery mode
In the recovery menu, there is a menu to "Reboot to bootloader", which will boot the phone to Fastboot downloading mode.
Power + Vol Up + Vol Down : TF update
Combining with USB cable
Power + Plug in USB cable : Turn On Phone
Vol Up + Plug USB : Enter Fastboot downloading
Vol up + Vol down + Plug USB : TF Update. Seems like the USB become the power button
Vol Up + Power + Plug USB, Release Power button after vibrate : EngTest mode, diagnostic mode. In QPST will be detected as the diagnostic port, seems to be Hisense Proprietary one.
Unplug battery : Any combination of power button, vol up and vol down didn't give any response or vibration, nothing detected in device manager or usb deview.
Using adb, only 3 reboot choice : reboot, reboot recovery, reboot bootloader. Reboot edl don't work (wonder if anyone success at another phone)
Using fastboot, is similiar to adb : fastboot reboot and fastboot reboot bootloader. Reboot edl don't work either. Fastboot oem unlock do nothing as well.
Enter Qualcomm HS-USB QDLoader 9008
It seems the Engtest mode boot in android OS, as I can see the prompt asking for USB connection mode (MTP, CD ROM, charge only etc). And IDK if it is a bug, but every time I boot to this Engtest, the next reboot always remove all of my account (Google, whatsapp, mysmartfren (my ISP)). I need to add back, resync contact, resetting gmail and etc. Later, I discovered that i don't need this engtest anymore. As long as I have installed all driver : Qualcomm, Hisense and QPST; every time I connect the USB when the phone is on, it will detected as diagnostic mode.
From this diagnostic mode, I can switch the phone to Download mode (9008), by using eMMC software download (QPST) > Switch device to DLoad; or using EFS Pro - Qualcomm NV Tools > Change mode to Download Mode. Phone will reboot, screen off and vibrate a while. Diagnostic port now is closed and it will add a new port, Q/QCP-XXX - Sahara Memory Dump. Device manager will detect Qualcomm HS-USB QDLoader 9008.
From this mode, AFAIK I still need MPRG8929.hex and 8929_msmimage.mbn to boot it to 9006 mode. But the current available hex/bin and mbn only for 8974, 8916 and 8939 (8936 mbn). Looking to the build.prop and the lib folder of my phone, it seems to have a lot of similiarity with MSM8939. So i was thinking to use the MPRG and mbn from MSM8939. But I still haven't tried it yet, as i need more confirmation. This is my main phone, that's why i am very careful with it, my backup phone is too weak now for daily usage.
BTW, I am using latest WHQL qualcomm driver, version 2.1.0.5 and Hisense driver directly from the phone's CDROM iso. Using universal driver installer also give the same driver. QPST 2.7 build 425.1. Build 422 give me the same result. Main PC is Win 7 Ultimate 64 bit SP1. I have tested it in XP SP3, and give the same result, so not the WHQL driver signing problem.
TF Update
Someone point me out about TF Update file for HS-L965 (the 5.5 inch variant). This file supposed to be flashed through TF Update process (Power + Vol Up + Vol Down). I manage to download it and of course i don't flash it to my phone, since it is from different version. I try to extract out recovery.img and boot.img, by mounting it or open it from archive program. Disk Internal Linux reader can mount the bin properly and show up with 20 something partition, which is very similiar to what I see from qualcomm partitions. I try to open each partition, of course it fails, as it is not ext4 file system (even /system also fail). Try to create image from recovery, boot and system partition; and it manage to be extracted out. But the result is very different from the typical raw img. It doesn't contain proper file header for recovery, boot, and system .img. The hex header supposed to be "ANDROID". But all of the extracted img don't have it. If I unpack the boot.img and recovery.img, carliv unpacker also give no folder structured result, only compressed ram-disk. Try to use ext4unpacker also no luck. So any image extracted is useless, as they don't seems to have the correct file header (or maybe it is wrong reading from the linux reader).
I have spent this whole week trying to find the way to boot the phone to 9006 mode. I have googled a lot, have finisihed reading from 1st page to the last page
[PROJECT] Reviving Hard Bricked YU (QLoader 9008 Mode)
[R&D][QUALCOMM] Using QDL, EHostDL and DIAG interfaces & features
and some other thread. I might miss some info, partially because I sometimes read it in half drowsy state. So, I'll be glad to be pointed out the missing info.
Alternative root method
I have searched for the canvas nitro 4G rooting process, and there is no answer yet at http://forum.xda-developers.com/general/xda-assist/root-micromax-canvas-nitro-3-4g-e455-t3225783 and http://forum.xda-developers.com/android/help/how-to-root-micromax-canvas-nitro-4g-t3209976.
I also know about kingroot. But there are a lot of privacy issues with that program, so I want to stay away from it. From my friend, they said they've tried the latest version, but still fail to root. So I don't try it anymore. But if there is no other way, I might give it a shot as well. A lot of other root tools also fail to root this phone. So, flashing SuperSU.zip from TWRP, seems to be the only way to root it.
Question
From all information above, now here comes the questions :
1. Is there a way to enter 9006 Mode without doing any modification or flash programmer file in the latest qualcomm SoC ? (SD410, SD415, SD615, SD810 above)
2. What the MPRG and MBN really do when flashed to device? Do they stay at the emmc, means they replace some partition inside the Phone? Or they just stay at RAM and will be wiped out on the next reboot; so we need to flash it again if we want to enter 9006 from 9008?
3. What is the risk of using wrong MPRG and MBN file from different SoC? As I wanna try to use the ones from MSM8916 and MSM8939 (MSM8936). I have downloaded it already, but too scare to use it.
4. How we can know we are using the correct MPRG and MBN file? How they were created at first? Is it possible to create it from some partition in the phone?
5. How to extract the TF update .bin file properly? And how they were created at first? And it is possible to create it our self, without the need of any signature/certificate from the vendor?
Sorry if there are too many questions and this thread is very long. I don't expect all questions to be answered though. As long as the main purpose above is achieved, that's nice already.
If there is any additional info needed, I will provided it later.
Thanks in Advance.
Click to expand...
Click to collapse
Do you have any kind of rescue/qfil/qpst rom of your variant for unbrick from Qualcomm 9008 ? If yes :
If you are rooted, take a backup of your aboot partition, then " dd if=/dev/zero of=/dev/block/aboot(your partition number), or "fastboot erase aboot" will give you Qualcomm 9006 port.
Desmanto said:
Hi everyone,
I'm currently using Hisense Pureshot aka HS-L671, using android Lollipop 5.0.2. It has Snapdragon 415 MSM8929, which is very similiar to Snapdragon 615 MSM8939, but with some missing feature (just like rip-off version of SD615). AFAIK currently there are only two phones use this SD415, the other one is Micromax Canvas Nitro 4G (E455) (3, if we count in the 5,5 inch variant of Pureshot+/HS-L695). That's why the documentation is still very scarce.
Edit : it seems there are several phones using this SoC now. I am currently researching about j7
Main Purpose
I post this thread for two main reasons :
1. To do full backup of my current phone, without root or modifiying any existing partitions (as I do below with my previous phone). This is to ensure I can revert back any modified phone to its original state, should we need to claim for RMA in case of hardware failure (not software). I know reverting to original state is possible to be done by flashing rooted stock ROM; then unroot afterward. But AFAIK, full unroot will leave trail of modified timestamp in /system partition. I don't want any trail of modification. (preferred if possible)
2. After backup, I will take the recovery.img and boot.img to compile TWRP in BBQLinux. Then flash it back to the phone. Boot up to TWRP and flash SuperSU.zip to obtain root access. Then I will proceed on a lot of modifications which require root. If number 1 cannot be done first, I have no problem if there is a way to obtain root first, then do the backup later using different tool.
Previous experience with SD200
Based on my experience with previous phone, Andromax C2 aka Hisense AD688G (1st gen), Android JB 4.3, Snapdragon 200 MSM8610; it can boot directly to Qualcomm MMC Storage Mode, which maybe known as Emergency Host DownLoad or Qualcomm HS-USB Diagnostics 9006 (CMIIW). To enter this mode, I need to turn off the phone, unplug the battery, holding down Power + Volume Down button, while connecting it to PC (Win 7 64 bit) via USB cable (I have installed qualcomm driver before). Then it will pop up a lot of prompt to format the drives, which I ignore all of them. In the device manager, it will be detected as Qualcomm MMC Storage. From there, I can proceed on backup every partition of the phone using HDDRaw copy, partition guru or emmc raw tool (preferred one). This can be done without root or any modification to the phone. Which is why this method of backup is preferred, since i can always start with "clean slate", should anything wrong happen (restore using the same method). And it doesn't leave trail of folder modification timestamp as it will be if I flash rooted stock ROM then unroot.
Power button + combination
Now, with the latest snapdragon family 410, 615, including 415 above, it seems there is no way to boot directly to the same Qualcomm MMC Storage / (as far as I read till now from tirta.agung thread). I have tried several combination, and the result is below.
Power : Turn on Phone
Power + Vol Up : nothing happen. If not followed by next action, Phone boot normally
Power + Vol Up, followed by holding vol down at the second logo : Enter safe mode
Power + Vol down : Enter firmware status (Official)
Power + Vol down, followed by holding Power : Enter Recovery mode
In the recovery menu, there is a menu to "Reboot to bootloader", which will boot the phone to Fastboot downloading mode.
Power + Vol Up + Vol Down : TF update
Combining with USB cable
Power + Plug in USB cable : Turn On Phone
Vol Up + Plug USB : Enter Fastboot downloading
Vol up + Vol down + Plug USB : TF Update. Seems like the USB become the power button
Vol Up + Power + Plug USB, Release Power button after vibrate : EngTest mode, diagnostic mode. In QPST will be detected as the diagnostic port, seems to be Hisense Proprietary one.
Unplug battery : Any combination of power button, vol up and vol down didn't give any response or vibration, nothing detected in device manager or usb deview.
Using adb, only 3 reboot choice : reboot, reboot recovery, reboot bootloader. Reboot edl don't work (wonder if anyone success at another phone)
Using fastboot, is similiar to adb : fastboot reboot and fastboot reboot bootloader. Reboot edl don't work either. Fastboot oem unlock do nothing as well.
Enter Qualcomm HS-USB QDLoader 9008
It seems the Engtest mode boot in android OS, as I can see the prompt asking for USB connection mode (MTP, CD ROM, charge only etc). And IDK if it is a bug, but every time I boot to this Engtest, the next reboot always remove all of my account (Google, whatsapp, mysmartfren (my ISP)). I need to add back, resync contact, resetting gmail and etc. Later, I discovered that i don't need this engtest anymore. As long as I have installed all driver : Qualcomm, Hisense and QPST; every time I connect the USB when the phone is on, it will detected as diagnostic mode.
From this diagnostic mode, I can switch the phone to Download mode (9008), by using eMMC software download (QPST) > Switch device to DLoad; or using EFS Pro - Qualcomm NV Tools > Change mode to Download Mode. Phone will reboot, screen off and vibrate a while. Diagnostic port now is closed and it will add a new port, Q/QCP-XXX - Sahara Memory Dump. Device manager will detect Qualcomm HS-USB QDLoader 9008.
From this mode, AFAIK I still need MPRG8929.hex and 8929_msmimage.mbn to boot it to 9006 mode. But the current available hex/bin and mbn only for 8974, 8916 and 8939 (8936 mbn). Looking to the build.prop and the lib folder of my phone, it seems to have a lot of similiarity with MSM8939. So i was thinking to use the MPRG and mbn from MSM8939. But I still haven't tried it yet, as i need more confirmation. This is my main phone, that's why i am very careful with it, my backup phone is too weak now for daily usage.
BTW, I am using latest WHQL qualcomm driver, version 2.1.0.5 and Hisense driver directly from the phone's CDROM iso. Using universal driver installer also give the same driver. QPST 2.7 build 425.1. Build 422 give me the same result. Main PC is Win 7 Ultimate 64 bit SP1. I have tested it in XP SP3, and give the same result, so not the WHQL driver signing problem.
TF Update
Someone point me out about TF Update file for HS-L965 (the 5.5 inch variant). This file supposed to be flashed through TF Update process (Power + Vol Up + Vol Down). I manage to download it and of course i don't flash it to my phone, since it is from different version. I try to extract out recovery.img and boot.img, by mounting it or open it from archive program. Disk Internal Linux reader can mount the bin properly and show up with 20 something partition, which is very similiar to what I see from qualcomm partitions. I try to open each partition, of course it fails, as it is not ext4 file system (even /system also fail). Try to create image from recovery, boot and system partition; and it manage to be extracted out. But the result is very different from the typical raw img. It doesn't contain proper file header for recovery, boot, and system .img. The hex header supposed to be "ANDROID". But all of the extracted img don't have it. If I unpack the boot.img and recovery.img, carliv unpacker also give no folder structured result, only compressed ram-disk. Try to use ext4unpacker also no luck. So any image extracted is useless, as they don't seems to have the correct file header (or maybe it is wrong reading from the linux reader).
I have spent this whole week trying to find the way to boot the phone to 9006 mode. I have googled a lot, have finisihed reading from 1st page to the last page
[PROJECT] Reviving Hard Bricked YU (QLoader 9008 Mode)
[R&D][QUALCOMM] Using QDL, EHostDL and DIAG interfaces & features
and some other thread. I might miss some info, partially because I sometimes read it in half drowsy state. So, I'll be glad to be pointed out the missing info.
Alternative root method
I have searched for the canvas nitro 4G rooting process, and there is no answer yet at http://forum.xda-developers.com/general/xda-assist/root-micromax-canvas-nitro-3-4g-e455-t3225783 and http://forum.xda-developers.com/android/help/how-to-root-micromax-canvas-nitro-4g-t3209976.
I also know about kingroot. But there are a lot of privacy issues with that program, so I want to stay away from it. From my friend, they said they've tried the latest version, but still fail to root. So I don't try it anymore. But if there is no other way, I might give it a shot as well. A lot of other root tools also fail to root this phone. So, flashing SuperSU.zip from TWRP, seems to be the only way to root it.
Question
From all information above, now here comes the questions :
1. Is there a way to enter 9006 Mode without doing any modification or flash programmer file in the latest qualcomm SoC ? (SD410, SD415, SD615, SD810 above)
2. What the MPRG and MBN really do when flashed to device? Do they stay at the emmc, means they replace some partition inside the Phone? Or they just stay at RAM and will be wiped out on the next reboot; so we need to flash it again if we want to enter 9006 from 9008?
3. What is the risk of using wrong MPRG and MBN file from different SoC? As I wanna try to use the ones from MSM8916 and MSM8939 (MSM8936). I have downloaded it already, but too scare to use it.
4. How we can know we are using the correct MPRG and MBN file? How they were created at first? Is it possible to create it from some partition in the phone?
5. How to extract the TF update .bin file properly? And how they were created at first? And it is possible to create it our self, without the need of any signature/certificate from the vendor?
Sorry if there are too many questions and this thread is very long. I don't expect all questions to be answered though. As long as the main purpose above is achieved, that's nice already.
If there is any additional info needed, I will provided it later.
Thanks in Advance.
Click to expand...
Click to collapse
i have asus zenfone z010d model, accidenty i have replace emmcblk file using adb,,after that handset goes in diag mode 9006,,there are many partition shows in emmc...i give backup image from emmc using minitool and delete all partition from emmc......now handset connets in qd loader 9008 mode.......what should i do
jitendramohite said:
i have asus zenfone z010d model, accidenty i have replace emmcblk file using adb,,after that handset goes in diag mode 9006,,there are many partition shows in emmc...i give backup image from emmc using minitool and delete all partition from emmc......now handset connets in qd loader 9008 mode.......what should i do
Click to expand...
Click to collapse
Use qfil software and flash the firmware for your device using qfil software(firmware can be found in firmware27.net)
Did you ever have any success with this? I have Huawei Mediapad M3 8.0 lite, and I do not get enumeration of QUALCOMM Just:
Android Adapter Modem
DBadapter reserved interface (com6)
Android adapter PCUI (com5)
Android Composite ADB interface
Huawei HDB Interface
I want to do what you wanted to do get a clean dump of the firmware, so I can keep it for restoring as well as get a clean dump so I can create custom recovery so I can do some slight modifictions and create a standard img that I put onto several hundred tablets that we build into product.
jkindem said:
Did you ever have any success with this? I have Huawei Mediapad M3 8.0 lite, and I do not get enumeration of QUALCOMM Just:
Android Adapter Modem
DBadapter reserved interface (com6)
Android adapter PCUI (com5)
Android Composite ADB interface
Huawei HDB Interface
I want to do what you wanted to do get a clean dump of the firmware, so I can keep it for restoring as well as get a clean dump so I can create custom recovery so I can do some slight modifictions and create a standard img that I put onto several hundred tablets that we build into product.
Click to expand...
Click to collapse
Oh, I just realized, someone still replying to my thread. Sorry. My device has been broken for a long time, eMMC failure. And I never succeed to dump it. I ended up root it using some kind of semi ported TWRP from zte devices and successfull root it using SuperSU and make a full backup using TWRP. Then I proceed to make another small partition backup using Partition Backups. (I can use dd command, but using app is easier). To get back to original unrooted, I have got the stock ROM in TF update format from Needrom. Somehow, someone uploaded it when I request it. Maybe I just got lucky, since the vendor never upload the stock firmware for us.
Related
I have Lenovo Lephone S686 with following specifications. If anyone has any idea on how to root this phone, please reply.
CPU: Qualcomm Snapdragon MSM8225 Dual core 1.2GHz
GPU: Qualcomm Adreno203
Memory : RAM : 512MB / ROM : 4GB eMMC
Found already?
Am sick and tired of the stock....
tried 1-click root, king root, and all other root method and failed...
Anybody knows how to root this? bin4ry method did not work.
Hi everyone,
I found these instructions for rooting the Lenovo S686 from Chinese forums, you can try and see if it works. Below are the instructions which I translate from Chinese.
You need to install a 3rd party recovery, because S686’s original recovery cannot install unsigned update.zip. There are 2 kinds of update.zip, smaller one, about 1-2MB, is for obtaining root. The bigger one is for flashing the entire system. There is no 3rd party recovery for S686, but after looking at some other models’ recovery, I think we can use A765E recovery.
Turn on USB debugging. Connect USB wire. For desktop PCs, it is better to use the back USB port.
Download this: ht tp://pan [dot] baidu [dot] com/share [slash] link?shareid=415868&uk=4130114971
After uncompressing, you will get 2 files, update.zip and Lenovo_A765E_OneKeyTools.exe. Do not uncompress the update.zip. Just put it on the TF card.
Make sure the drivers are installed. Most of the time, if it doesn’t work, it is because of driver problems. You can check whether drivers are properly installed by going to Device Manager.
Installing fastboot driver: without disconnecting USB wire, turn off phone, take out the battery. While pressing ON and VOL -, connect USB wire. Most likely fastboot driver will install automatically.
Run 刷入中文Recovery (Chinese CWM recovery). Phone will reboot 3 times.
Entering recovery mode: Turn on the phone. Red LED will light up, before it goes off, press VOL + and -, hold until Lenovo logo appears. If you see Android recovery, it means the above steps did not work. If you see Chinese CWM recovery, flash in the update.zip that you put onto the TF card.
After this post on the Chinese forums, there were many people saying it works, and many people saying it does not work. I (tangys) could not get it to work with my S686. So either I am an idiot, or the guy who wrote the original post is an idiot. So please try it and post back here whether it works for you or not. Thanks.
sralli said:
i was also facing the same problem. i couldn't root my phone, at last i found solution on this page-
Mod Edit: link removed, it worked for me i hope it works for you, and it roots in just 5 minutes
Click to expand...
Click to collapse
just use framaroot i think it's downloadable on google play then use the gandalf exploit!
Just FYI I`ve noticed that you`ve mentioned Chinese characters in the previous text, let me know if you`ve met any translation problems, i`m the one can do the help
hi.from where i can find kernel or some ROM for lenovo s686.thanks
This following method worked for me. Got ride of the bloatware that Lenovo put on there.
got the files from
www lenovohome net/thread-137736-1-1.html
some detailed instructions to setup here
lenovo zol com cn/177/1763_1767961.html
I'm a noob at rooting/changing firmware so took some extra time.
Need to setup the ADB drivers. This was slightly involved as the drivers from the phone ITSELF showed up as not properly signed. So I had to go and turn off the win8.1 check to get it properly installed. You end up with Lenovo ADB Device in device mgr and a few other Lenovo items.
Basically, there's an exe that you run (name has chinese char in it.. so it may look strange). It's an automated CWM installer. My version now shows CWM 6.0.1.5. All the text in there is in chinese.
Lastly, you flash in the update_v2.zip and when done, you get a root enabled , bloatware removed CYANOGENMOD system.
One note: when done flashing and you choose reboot, there is actually a prompt for you to "repair root". I've found that you must say yes at this point. Otherwise, root is not working when rebooted. You'll have to repair root later.
That's the good side. Now the bad side:
This phone only has 3 keys (pwr, vol+ / -) so there's currently no way to get menu button.
There is also no store in the version flashed....no sure how to install any apps
Need to resolve these issues.
After installing cyanogenmod 10 nightly with cwm my battery began to act weird - it showed 0% charge and the phone turned off as soon as i plugged the charger off. I've read that this can be caused by CWM and that i have to install Amon Ra recovery in order to fix it. However, i wasn't able to enter fastboot mode, so i've decided to write the img directly using from adb shell
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/amonrarecovery.img
reboot recovery
(yes, now i understand that it is dumb, but i wanted to do it faster, without reading all tutorials).
it gave me the error that it cannot write there.
after that the phone won't turn on or enter recovery/download/fastboot mode. the only signs of life - omap 4430 usb device blinking in the device manager(i've installed the required drivers).
as far as i understand - if i'll be able to enter fastboot mode - i'll be able to flash normal bootloader back and install any rom.
But there's no LGE CDMA usb serial port showing in device manager, no matter what pc, cable or key combination(volume up, volume up+power, etc) i use. - it was the same even before i've erased bootloader.
besides when i use wkpark's omap4boot - i get error 121 on the second stage responce (i've tried the EMU version - still no luck)
seems that using OMAPflash is my only option now, but i can't seem to find examples of it's usage. One guy on this forum said that he revived p920 by dumping the firmware from a working p920 and then flashing it back on his device starting from 0000 memory address. maybe someone could upload his or stock firmware obtained this way?
i've tried using LG mobile support tool but it seems not to be able to detect the device (tried holding vol up)
maybe you guys can advice me something else?
PS this is a NOT FOR SALE device, if that changes something
thanks in advance.
Tried to install AmonRa recovery on my phone. No change, still no charging.
Sent from my LG-P920 using xda premium
alexisrozkov said:
After installing cyanogenmod 10 nightly with cwm my battery began to act weird - it showed 0% charge and the phone turned off as soon as i plugged the charger off. I've read that this can be caused by CWM and that i have to install Amon Ra recovery in order to fix it. However, i wasn't able to enter fastboot mode, so i've decided to write the img directly using from adb shell
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/amonrarecovery.img
reboot recovery
(yes, now i understand that it is dumb, but i wanted to do it faster, without reading all tutorials).
it gave me the error that it cannot write there.
after that the phone won't turn on or enter recovery/download/fastboot mode. the only signs of life - omap 4430 usb device blinking in the device manager(i've installed the required drivers).
as far as i understand - if i'll be able to enter fastboot mode - i'll be able to flash normal bootloader back and install any rom.
But there's no LGE CDMA usb serial port showing in device manager, no matter what pc, cable or key combination(volume up, volume up+power, etc) i use. - it was the same even before i've erased bootloader.
besides when i use wkpark's omap4boot - i get error 121 on the second stage responce (i've tried the EMU version - still no luck)
seems that using OMAPflash is my only option now, but i can't seem to find examples of it's usage. One guy on this forum said that he revived p920 by dumping the firmware from a working p920 and then flashing it back on his device starting from 0000 memory address. maybe someone could upload his or stock firmware obtained this way?
i've tried using LG mobile support tool but it seems not to be able to detect the device (tried holding vol up)
maybe you guys can advice me something else?
PS this is a NOT FOR SALE device, if that changes something
thanks in advance.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?p=44532338&nocache=1
Make sure you did this
If the LG COSMO appears in device manager install driver for her by select update driver then select browse my computer for driver {install driver Manual} and select Install driver from "inside folder have drivers"(omap4boot-for_optimus-v1.22 modified by XcachorroX®\usb_drv_windows) then try again step 2 flash fastboot
i resurrected lg p920 not for sale con omap4boot 1.25 option emu
http://www.youtube.com/watch?v=dHZ_RJCyrxk&feature=youtu.be
Praise be he did it. And I wholeheartedly and apologize for my frustration.
This is my first time asking for help directly here, I always find the answers in the other threads solved, but this time I can not find an answer.
I have a alcatel one touch 5020t evolve its a MTK6575 (t-mobile but is used in el salvador), I used to MTKDroidTools to install CWM Revocovery, I did back up with the same program but apparently did not because i look and i cant find anything in the back up folder, only left some files called:
ALCATEL-ONE-TOUCH-5020T_130818__boot_patched_140129-175612.img
ALCATEL-ONE-TOUCH-5020T_130818__recovery_140129-175612.img
in the folder called recovery.
Now the phone on, the startup screen and then turns off, I can enter a menu by pressing on + vol +, where it says enter recovery mode or normal mode, before they tried to install cwm I could go in and delete everything from there, now I get the menu of recovery mode and normal mode but since does not enter recovery mode, got it turns off, like when entering the normal mode.
I tried to flash with sp flash tool but I get an authentication error that is on the img
The pc recognizes my phone, makes the sound when you connect something, now if we go to Device Manager, a device called first appears:
MTK USB Port
After that is disconnected and then a new one appears called :
Media Tek Preloader USB VCOM Port
But there ir a problem, then this becomes a repetitive one disconnects and connects the other, but only when I connect the phone without battery only stays in:
MTK USB Port.
Help what can i do to revive my phone ???????????????
you found any solution i have the same problem ?
:/
harold99 said:
you found any solution i have the same problem ?
Click to expand...
Click to collapse
Sorry, but i could not solve yet, nobody helps me
So were you able to flash cwm to the device? there are several threads requesting a custom recovery for this device and either way could you upload those first two .img files I may be able to use them to try to recover my device
*** Okay so the problem is that the boot loader on this device is locked and for the time being a custom recovery is not possible. I still have access to the recovery on my device so if I could find a way to build an update file from the source code or an official firmware update I could fix mine. Yours may be too far gone. sorry.
any luck with a solution? How close to one have you got to...
ipeedalil said:
*** Okay so the problem is that the boot loader on this device is locked and for the time being a custom recovery is not possible.
Click to expand...
Click to collapse
A friendly warning: Don't just mess around with the Bootloader, that's one delicate piece of software, try to find how to unlock it first, then we can talk of changing the recovery. For rooting purposes I can attest that you can safely root it using the OneClickRoot solutions around the net. I used some chinese root and it worked like a charm.
Soft Bricked 5020T
carlitox2301 said:
This is my first time asking for help directly here, I always find the answers in the other threads solved, but this time I can not find an answer.
I have a alcatel one touch 5020t evolve its a MTK6575 (t-mobile but is used in el salvador), I used to MTKDroidTools to install CWM Revocovery, I did back up with the same program but apparently did not because i look and i cant find anything in the back up folder, only left some files called:
ALCATEL-ONE-TOUCH-5020T_130818__boot_patched_140129-175612.img
ALCATEL-ONE-TOUCH-5020T_130818__recovery_140129-175612.img
in the folder called recovery.
Now the phone on, the startup screen and then turns off, I can enter a menu by pressing on + vol +, where it says enter recovery mode or normal mode, before they tried to install cwm I could go in and delete everything from there, now I get the menu of recovery mode and normal mode but since does not enter recovery mode, got it turns off, like when entering the normal mode.
I tried to flash with sp flash tool but I get an authentication error that is on the img
The pc recognizes my phone, makes the sound when you connect something, now if we go to Device Manager, a device called first appears:
MTK USB Port
After that is disconnected and then a new one appears called :
Media Tek Preloader USB VCOM Port
But there ir a problem, then this becomes a repetitive one disconnects and connects the other, but only when I connect the phone without battery only stays in:
MTK USB Port.
Help what can i do to revive my phone ???????????????
Click to expand...
Click to collapse
I have had a OT-5020T with all the same symptoms as you describe. After much research and diagnosis here is what I have learned and know to be true.
You have soft bricked your phone. For this phone it results in the boot loop you described. At present a Custom Recovery that works is not available for this phone and any attempt to flash an existing one results in a soft brick. There are apps that will flash a Custom Recovery while the phone is one but once you reboot ... !!! Bricked!! This is because ...
a) the memory mapping for this phone is different that other OT-5020 models, so the Custom Recovery placement and indexing is wrong when flashed, causing the boot-loop, and inability for Custom Recovery to load,
and ,
b) the bootloader is locked for the 5020T (different story for other OT 5020 models), and no one has found a way around it yet. Trying to flash back stock firmware for the OT-5020T requires it to be unlocked.
One Touch Update 2.8.0 doesn't seem to want to work one the phone has been altered in this way. SPtools won't work because you need an accurate OT-5020T scatter file (memory map) ,and certification file (bootloader unlocker) to flash any image. In addition to all this the phone doesn't maintain a steady usb connection long enough to allow use of android tools adb and fastboot commands although it does can stay connected in a different mode.
What I have used to restore my phones firmware is a package from Furious Gold that allows the phone to be flashed to factory firmware. I have used it successfully, so I can confirm that the phone wasn't a permanent brick.
Alcatel 5020t T-Mobile plis help flshe file
please am in need of alcatel 5020w firmware, please if someone is having it or having that same phone and want to read the firmware for me my email is [email protected]
thanks
Hello,
After unlocking the bootloader and installing TWRP on my OUKITEL K6000 Plus I was trying to install madOS, but unfortunately my phone went into Orange State bootloop. I could not enter fastboot anymore, and at some point even Recovery stopped to work. My phone was almost dead. I was looking for solutions but actually there was no clear guide how to revive a patient. I found that many people have similar issue so when I finally managed to resurrect my K6000 with original stock ROM I decided to share my solution.
Here's the fix:
1. Google for 'Techprolonged MediaTek MT65xx USB VCOM Drivers'. Using the guide you will find install MediaTek DA USB VCOM Port Drivers via Device Manager (step 5). Do this even if you already previously installed MediaTek USB VCOM Drivers. This is very important to install this DA version of drivers, otherwise you may have problems with uploading stock ROM via SP Flash Tool.
2. Install SP Flash Tool if you don't have it yet. You can find it easily with google.
3. Download original stock K6000 Plus ROM V6.0. You can find it easily on needrom website (NOTE: you have to create an account on needrom if you don't have it yet). Unpack it.
4. Launch SP Flash Tool, go to Options->Option... in Connection settings change USB speed to Full speed and Battery to with battery. Close Option window.
5. In SP Flash Tool go to Download tab, click on choose right next to Scatter-loading file field, navigate to the folder where you unpacked previously downloaded stock K6000 Plus ROM V6.0. Open MT6750_Android_scatter.txt file.
6. In open menu choose Download Only if it's not selected by default. All fields below should have tick enabled. I mean for 'preloader', for 'recovery', etc...
7. Unplug your phone from PC if it's connected. Shut down your phone by clicking and holding for approx 10 secs ALL THREE BUTTONS: VOL UP + VOL DOWN + POWER. If you do this properly, your phone should not self-boot into Orange State anymore.
8. In SP Flash Tool click Download icon (the one with green arrow), all the fields should become inactive.
9. Using one hand only click and hold at the same time VOL UP + POWER button.
10. Now, while you still hold these buttons, you have to connect your phone to PC (plug in micro USB cable into your phone). VERY IMPORTANT: If you have STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003) error after you connect it means you don't have DA version of MediaTek driver properly installed (step no. 1).
11. Your phone should start to flash up and you should see the progress in SP Flash Tool status bar. You can release VOL UP and POWER button now. The process may take long time, for me it was more than 1 hour. The longest part was flashing up the [system]. The good thing is you can observe the progress during whole process.
12. When flashing process is end you will see a small window with the information about completion. Now you can unplug your phone, and launch it with POWER button. You should still see the Orange State message but right after that your phone should boot up into normal mode with freshly uploaded original stock ROM. Congratulations!
Hopefully this will also fix your K6000 Plus and maybe even other models.
I'm really sorry I don't provide any direct links, but I haven't posted 10 posts yet and my XDA account is still limited.
Regards,
Slavedriver
Please help I have error 4032 (BROM ERROR S_FT_ENABLE_DRAM_FAIL)
1. Google for 'Techprolonged MediaTek MT65xx USB VCOM Drivers'. Using the guide you will find install MediaTek DA USB VCOM Port Drivers via Device Manager (step 5). Do this even if you already previously installed MediaTek USB VCOM Drivers. This is very important to install this DA version of drivers, otherwise you may have problems with uploading stock ROM via SP Flash Tool.
this should solve that
STATUS_BROM_CMD_SEND_DA_FAIL
persists even after installing correct drivers?
Solution: Choose
Download Agent as DA-PL in SP flash tools. And follow the same guide.
Thank you so much for this post, just saved an Oukitel K6000 Plus. Just finished process, rebooting normally for first use. It's been stressfull hours, what a relieve.
slavedriver83 said:
9. Using one hand only click and hold at the same time VOL UP + POWER button.
10. Now, while you still hold these buttons, you have to connect your phone to PC (plug in micro USB cable into your phone). VERY IMPORTANT: If
Click to expand...
Click to collapse
this helped me a lot with my ulefone armor 2, thanks
Fixed the orange state, thanks a lot for this guide.
Do you think I shall try again to upgrade to Android 8 anymore?
slavedriver83 said:
9. Using one hand only click and hold at the same time VOL UP + POWER button.
Click to expand...
Click to collapse
Thank you very much for the advice
I thought I put my phone in the trash when I read this.
But in point 9 I had to push only the VOL UP if I press the two buttons, the AP returns an error.
You saved mine as well, slavedriver!
And it is a Teclast Tpad A10S!
I had given it up.
Thanks a lot!
It works also on U20 plus. I had to select DA_SWSEC as Download Agent. Thank you so much!
Guide worked Perfectly for me.
My mobile was bricked in the same Bootloop. The guide worked perfectly for me. Thanks a lot for useful and detailed help.
I understand this thread is almost 1 year old. I tried this procedure and everything went well. The only problem the phone does not boot. It does turn on but nothing comes up. No boot menu no logo just a few flickering lights and a very dark background. Does anyone have any ideas?
OK6000 Plus
pvkid said:
I understand this thread is almost 1 year old. I tried this procedure and everything went well. The only problem the phone does not boot. It does turn on but nothing comes up. No boot menu no logo just a few flickering lights and a very dark background. Does anyone have any ideas?
OK6000 Plus
Click to expand...
Click to collapse
Tried this guide but SP shows the following messagge "STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060005) " (so it doesn't end with 3 but with 5)
Pyandroid said:
1. Google for 'Techprolonged MediaTek MT65xx USB VCOM Drivers'. Using the guide you will find install MediaTek DA USB VCOM Port Drivers via Device Manager (step 5). Do this even if you already previously installed MediaTek USB VCOM Drivers. This is very important to install this DA version of drivers, otherwise you may have problems with uploading stock ROM via SP Flash Tool.
this should solve that
Click to expand...
Click to collapse
Bro I got a different error just looks like:
ERROR STATUS_SEC_AUTH_FILE_NEEDED (0xc0030012)
Please help me out...I use "tecno spark 4 kc2"
slavedriver83 said:
Hello,
After unlocking the bootloader and installing TWRP on my OUKITEL K6000 Plus I was trying to install madOS, but unfortunately my phone went into Orange State bootloop. I could not enter fastboot anymore, and at some point even Recovery stopped to work. My phone was almost dead. I was looking for solutions but actually there was no clear guide how to revive a patient. I found that many people have similar issue so when I finally managed to resurrect my K6000 with original stock ROM I decided to share my solution.
Here's the fix:
1. Google for 'Techprolonged MediaTek MT65xx USB VCOM Drivers'. Using the guide you will find install MediaTek DA USB VCOM Port Drivers via Device Manager (step 5). Do this even if you already previously installed MediaTek USB VCOM Drivers. This is very important to install this DA version of drivers, otherwise you may have problems with uploading stock ROM via SP Flash Tool.
2. Install SP Flash Tool if you don't have it yet. You can find it easily with google.
3. Download original stock K6000 Plus ROM V6.0. You can find it easily on needrom website (NOTE: you have to create an account on needrom if you don't have it yet). Unpack it.
4. Launch SP Flash Tool, go to Options->Option... in Connection settings change USB speed to Full speed and Battery to with battery. Close Option window.
5. In SP Flash Tool go to Download tab, click on choose right next to Scatter-loading file field, navigate to the folder where you unpacked previously downloaded stock K6000 Plus ROM V6.0. Open MT6750_Android_scatter.txt file.
6. In open menu choose Download Only if it's not selected by default. All fields below should have tick enabled. I mean for 'preloader', for 'recovery', etc...
7. Unplug your phone from PC if it's connected. Shut down your phone by clicking and holding for approx 10 secs ALL THREE BUTTONS: VOL UP + VOL DOWN + POWER. If you do this properly, your phone should not self-boot into Orange State anymore.
8. In SP Flash Tool click Download icon (the one with green arrow), all the fields should become inactive.
9. Using one hand only click and hold at the same time VOL UP + POWER button.
10. Now, while you still hold these buttons, you have to connect your phone to PC (plug in micro USB cable into your phone). VERY IMPORTANT: If you have STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003) error after you connect it means you don't have DA version of MediaTek driver properly installed (step no. 1).
11. Your phone should start to flash up and you should see the progress in SP Flash Tool status bar. You can release VOL UP and POWER button now. The process may take long time, for me it was more than 1 hour. The longest part was flashing up the [system]. The good thing is you can observe the progress during whole process.
12. When flashing process is end you will see a small window with the information about completion. Now you can unplug your phone, and launch it with POWER button. You should still see the Orange State message but right after that your phone should boot up into normal mode with freshly uploaded original stock ROM. Congratulations!
Hopefully this will also fix your K6000 Plus and maybe even other models.
I'm really sorry I don't provide any direct links, but I haven't posted 10 posts yet and my XDA account is still limited.
Regards,
Slavedriver
Click to expand...
Click to collapse
Solution?
for:
ERROR STATUS_SEC_AUTH_FILE_NEEDED (0xc0030012)
"Tecno spark 4 kc2"
slavedriver83 said:
Hello,
After unlocking the bootloader and installing TWRP on my OUKITEL K6000 Plus I was trying to install madOS, but unfortunately my phone went into Orange State bootloop. I could not enter fastboot anymore, and at some point even Recovery stopped to work. My phone was almost dead. I was looking for solutions but actually there was no clear guide how to revive a patient. I found that many people have similar issue so when I finally managed to resurrect my K6000 with original stock ROM I decided to share my solution.
Here's the fix:
1. Google for 'Techprolonged MediaTek MT65xx USB VCOM Drivers'. Using the guide you will find install MediaTek DA USB VCOM Port Drivers via Device Manager (step 5). Do this even if you already previously installed MediaTek USB VCOM Drivers. This is very important to install this DA version of drivers, otherwise you may have problems with uploading stock ROM via SP Flash Tool.
2. Install SP Flash Tool if you don't have it yet. You can find it easily with google.
3. Download original stock K6000 Plus ROM V6.0. You can find it easily on needrom website (NOTE: you have to create an account on needrom if you don't have it yet). Unpack it.
4. Launch SP Flash Tool, go to Options->Option... in Connection settings change USB speed to Full speed and Battery to with battery. Close Option window.
5. In SP Flash Tool go to Download tab, click on choose right next to Scatter-loading file field, navigate to the folder where you unpacked previously downloaded stock K6000 Plus ROM V6.0. Open MT6750_Android_scatter.txt file.
6. In open menu choose Download Only if it's not selected by default. All fields below should have tick enabled. I mean for 'preloader', for 'recovery', etc...
7. Unplug your phone from PC if it's connected. Shut down your phone by clicking and holding for approx 10 secs ALL THREE BUTTONS: VOL UP + VOL DOWN + POWER. If you do this properly, your phone should not self-boot into Orange State anymore.
8. In SP Flash Tool click Download icon (the one with green arrow), all the fields should become inactive.
9. Using one hand only click and hold at the same time VOL UP + POWER button.
10. Now, while you still hold these buttons, you have to connect your phone to PC (plug in micro USB cable into your phone). VERY IMPORTANT: If you have STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003) error after you connect it means you don't have DA version of MediaTek driver properly installed (step no. 1).
11. Your phone should start to flash up and you should see the progress in SP Flash Tool status bar. You can release VOL UP and POWER button now. The process may take long time, for me it was more than 1 hour. The longest part was flashing up the [system]. The good thing is you can observe the progress during whole process.
12. When flashing process is end you will see a small window with the information about completion. Now you can unplug your phone, and launch it with POWER button. You should still see the Orange State message but right after that your phone should boot up into normal mode with freshly uploaded original stock ROM. Congratulations!
Hopefully this will also fix your K6000 Plus and maybe even other models.
I'm really sorry I don't provide any direct links, but I haven't posted 10 posts yet and my XDA account is still limited.
Regards,
Slavedriver
Click to expand...
Click to collapse
Hi, do I need my phone to be rooted to do this.
I unlocked bootloader in my gionee f205 from fastboot and now it is in orange state bootloop.
I haven't rooted my phone before doing it.
I'm the lucky one to get this scarce BRICK problem, my pixel 2 occasionally run into this, can't boot up any more, no bootloader, recovery,
plug into the pc, it always tell qualcomm hs-usb qdloader 9008,
had searched out all the forum, need to use QFIL to flash correct, prog_emmc_firehose_xxxx.mbn, together with rawprogram_XXX.xml.
what is that ? anyone happen to know where to get it ?
any idea is pretty appreciated.
I found this for you: https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868/page1
@misslebulletttttt did you fix your Pixel. If yes, how did you do that?
download > Tool all in one. Update it. update the drivers button at the bottom. now....... choose your phone. now choose flash factory image button.
it go to page where you pick the right firmware for you phone. press the download link. go back to Tool all in one and find the file you just download and then flash it with the button.
Tacis said:
@misslebulletttttt did you fix your Pixel. If yes, how did you do that?
Click to expand...
Click to collapse
sadly, the files that download tool asked was far proprietary, I'm not able to peek it a bit
I'm not saying these will fix or even do anything but I found them and maybe they can help you there Qualcomm usb drivers. I apologize if these are of no use.
I will just post here in case someone has the same issue and might contribute with the files...
Basically an Android device has a few steps of initialization
- power on
- initialize cpu and memory
- load bootloader
- bootloader selects boot mode
- having the boot selected, the kernel and device tree are loaded
- drivers are loaded
- system is loaded
- userdata is decrypted
Ok... So knowing that, when we want to write some partition on the device, we use fastboot. But first, the fastboot must have oem unlocked in settings. Well when unlocking in settings, this write in a protected partition (don't remember which one) which is checked if the fastboot can run some commands.
Well the next step is... Where is fastboot located?
Well, fastboot is located inside the bootloader. So, what?
Imagine that there isn't anything written in the memory... What would the processor do? It would think... Well nothing there... But must access the memory. So the cpu opens a port which is known as the emergency download mode (EDL).
EDL mode can be triggered with adb command or by shorting test points (there's another way, but I won't say it here)
Anyway when in edl mode, the processor talks a defined protocol, which is known as firehose.
So the first file you mentioned:
prog_emmc_firehose_xxxx.mbn
Is the programmer for the specific chipset, in order to make a handshake and allow to write.
Then after the handshake, you need to define how the memory will be partitioned (remember... It is considering a raw memory, with nothing on it). This lead us to the second file:
rawprogram_XXX.xml
This is basically how the memory is partitioned and where the image address is.
Besides those files, you need the img files (which will probably be only the system.img non sparsed i think...) And patch.xml too, probably.
But remember... The programmer needs to be signed and for the chipset... So if anyone has any contact with google... Maybe we can get those in order to unbrick devices... Anyway...
I just wanted to have those files, in case i run into a bad update...
I think we have to contact the carrier according to the bootloader files
misslebulletttttt said:
I'm the lucky one to get this scarce BRICK problem, my pixel 2 occasionally run into this, can't boot up any more, no bootloader, recovery,
plug into the pc, it always tell qualcomm hs-usb qdloader 9008,
had searched out all the forum, need to use QFIL to flash correct, prog_emmc_firehose_xxxx.mbn, together with rawprogram_XXX.xml.
what is that ? anyone happen to know where to get it ?
any idea is pretty appreciated.
Click to expand...
Click to collapse
Hello friend! I have the same problem as you! (Hard bricked Pixel 2 and can't find firmware files for flashing device(via QFIL or QPST)). Do you have any progress on this issue ?
I don`t know where to go with this problem except for this forum
Hi, have you found a solution to this problem? I got a hard brick after the update (
Any update from anyone please?
bmw9651 said:
download > Tool all in one. Update it. update the drivers button at the bottom. now....... choose your phone. now choose flash factory image button.
it go to page where you pick the right firmware for you phone. press the download link. go back to Tool all in one and find the file you just download and then flash it with the button.
Click to expand...
Click to collapse
What does any of that mean? There is no download for a, tool all in one around here.