Database Info

[Q] Droid Razr Locked or Bricked...Please Help!!!

Admins, I apologize if i post in the wrong area. I searched and followed the rules to the best of my knowledge. Please go easy on me? I am going crazy trying to figure out what to do. My razr is rooted. I downloaded a font updater app from the android market, updated some fonts, used the reboot button in options in the app, super user granted permissions and it went to reboot. It is now stuck in the bootloop. i have held the power and volume down button to do the hard reboot but it stalls at the first boot screen. I held down the power and volume down button until screen goes off then released and pressed it again quickly and it brings a screen which says the following...
AP Fastboot Mode (S)
0A.66
Device is LOCKED, Status Code: 0
Battery, OK
OK to Program
Transfer Mode:
USB Connected
(NOTE: I have the USB cable plugged in to my PC at the moment)
PLEASE help me??? I am not a genius at mobile devices or much else for that matter. What can I do to fix my phone. I'm on US Verizon using Motorola I am using a stock gingerbread rom with 2.3.5 and rooted. Thank you for your time and consideration in this matter.
OnTheLevel

This is the thread you want:
http://forum.xda-developers.com/showthread.php?t=1416058
There's a dedicated forum for the RAZR, you'll have more luck there. I only found your thread because I was searching for other things.

I have two solutions for u:
1. flash your phone with any rom you want.
2. find a file named "DroidSansFallback.ttf" on another phone(/system/font)
or rename a correct ttf file to DroidSansFallback.ttf.
download the attachment, use your file replace the
system/font/DroidSansFallback.ttf in the zip file.
rename the zip file to update.zip
reboot to recovery to install teh update.zip.
(or you can use a recovery tools to install it)

Problem Solved
Thank you guys for the replies. I have fixed my razr by using the FastFlash files I found. I am so new to this all and searched so many different places that I can not even remember where I downloaded them from. My apologies. Next time I will try to be more diligent and explain what I did to fix the problem for others to use for possible resolutions to their own similar issues.
Thanks Again,
OnTheLevel

if device rooted and bootstrapped
This is normal, go into boot strap and select boot recovery.
Enjoy

I Think I found a way to force RSD to flash.
The main problem is that boot menu see that battery is low
So now please try this Trick
-restart computer
-plug phone to charge normal-Inow you will see battery ok in ap fastboot
-unpack your firmware
-plug phone to computer main usb socket
-Flash

please help.. urgent!!
my phone is motorola razr xt910. i tried to unroot the phone (using the droidrazrutility 1.42) back to stock... but it is now stuck in the boot mode (recovery)... the message reads
AP Fastboot Mode (S) (Boot Failure)
0A.6C
To return to normal mode - first press power key to power down
Device is LOCKED, Status Code: 0
Battery, OK
OK to Program
Transfer Mode:
USB Connected
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CG HAB (CG: system, status: 0X004E)
Invalid CG (CG: system)
i have tried pressing the power key but no response
AND
when in boot mode (normal powerup)... the message reads
AP Fastboot Mode (S) (Flash Failure)
0A.6C
To return to normal mode - first press power key to power down
Device is LOCKED, Status Code: 0
Battery, OK
OK to Program
Transfer Mode:
USB Connected
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CG HAB (CG: system, status: 0X004E)
Invalid CG (CG: system)
please help. it has been like this all day.. completely inaccessible
thanks

I have a problem with this on my Razr xt926. I have the boot screen thaqt says the same thing as the first poster, I have no experience with getting in this deep with my phone, but am relatively savvy. I downloaded an avb/avd program, but I am struggling with how to "flash" the phone with whatever it is that I am missing. I picjed up the android 4.4 file pack, the phone sees when my USB is connected tot the computer, it says "Transfer Mode:USB connected" but the computer doesn't see it in "my computer", despite having reinstalled all the google USB and motorolla drivers. I am new here and to this. please help. there are things on this phone that I need. please help!

flash with what? how do I get a coomand prompt, and what files am I supposed to use?
goofyog said:
I Think I found a way to force RSD to flash.
The main problem is that boot menu see that battery is low
So now please try this Trick
-restart computer
-plug phone to charge normal-Inow you will see battery ok in ap fastboot
-unpack your firmware
-plug phone to computer main usb socket
-Flash
Click to expand...
Click to collapse
I am new to this, but it looks like it will be fun, once the device I depend on so much, is back up and running. Flash with what? how do I get a command prompt, and what files am I supposed to use?
Thanks!
Tony

tony2ltr said:
I have a problem with this on my Razr xt926. I have the boot screen thaqt says the same thing as the first poster, I have no experience with getting in this deep with my phone, but am relatively savvy. I downloaded an avb/avd program, but I am struggling with how to "flash" the phone with whatever it is that I am missing. I picjed up the android 4.4 file pack, the phone sees when my USB is connected tot the computer, it says "Transfer Mode:USB connected" but the computer doesn't see it in "my computer", despite having reinstalled all the google USB and motorolla drivers. I am new here and to this. please help. there are things on this phone that I need. please help!
Click to expand...
Click to collapse
make sure you are using a usb 2 port not usb3. if that doesnt work try another usb2 port if you have one.
im not sure what files you have to flash, but if you got to the 926 development forum and look for the razr utility made by me, may be a page or so back. download the one you need, there are many versions. all instructions you should need to use the tool are in my post there.

USB2, not 3
bweN diorD said:
make sure you are using a usb 2 port not usb3. if that doesnt work try another usb2 port if you have one.
im not sure what files you have to flash, but if you got to the 926 development forum and look for the razr utility made by me, may be a page or so back. download the one you need, there are many versions. all instructions you should need to use the tool are in my post there.
Click to expand...
Click to collapse
First of all, thank you. it is really important I get this phone working again! I will look back, I just don't understand how to get a command line prompt to send files. I can get the dead android on the screen, but don't know how/where to go from there. I have been able to acess the menu with the "recovery, fastboot, and ap tools" and there is another screen I have gotten to, but don't know how I did it, with a blue menu that has something like "send ADB file" or something like that and another few options. which part of the menu do I have to be in? and how do I know if it is a usb 2, not 3? if I go into the fastboot screen where it says "phone is locked, status 0, I can hear it connect when the computer beeps, but it doesnt show in my computer. the phone will say"USB connected" though.
Thank you for any guidance you can provide. not that I wanted to do emergency surgery, but I have been meaning to learn this stuff anyhow.
Tony
---------- Post added at 04:28 PM ---------- Previous post was at 04:20 PM ----------
I am new to all of this and new to this forum, so I am going to go look for your development post/files. thank you.
bweN diorD said:
make sure you are using a usb 2 port not usb3. if that doesnt work try another usb2 port if you have one.
im not sure what files you have to flash, but if you got to the 926 development forum and look for the razr utility made by me, may be a page or so back. download the one you need, there are many versions. all instructions you should need to use the tool are in my post there.
Click to expand...
Click to collapse

tony2ltr said:
First of all, thank you. it is really important I get this phone working again! I will look back, I just don't understand how to get a command line prompt to send files. I can get the dead android on the screen, but don't know how/where to go from there. I have been able to acess the menu with the "recovery, fastboot, and ap tools" and there is another screen I have gotten to, but don't know how I did it, with a blue menu that has something like "send ADB file" or something like that and another few options. which part of the menu do I have to be in? and how do I know if it is a usb 2, not 3? if I go into the fastboot screen where it says "phone is locked, status 0, I can hear it connect when the computer beeps, but it doesnt show in my computer. the phone will say"USB connected" though.
Thank you for any guidance you can provide. not that I wanted to do emergency surgery, but I have been meaning to learn this stuff anyhow.
Tony
---------- Post added at 04:28 PM ---------- Previous post was at 04:20 PM ----------
I am new to all of this and new to this forum, so I am going to go look for your development post/files. thank you.
Click to expand...
Click to collapse
usb 3 ports are usually blue in the center, but not always. the older your pc is, more likely you have little or no 3.0 and mostly 2.0. the newer the pc it, it tends to reverse that.
fastboot is the one you want to choose. after choosing fastboot, you dont need to do anything else to the phone. thats basically download or flash mode.
all the rest of the work is done by my script after you start it.
one other thing, since your phone is Locked its important to get the proper version of the utility. your options are only to flash the same software or newer. if you dont know what version you were on, you will just have to use the newest version to be safe.

When I click on the " This, and this" haha. all I get is a screen full of nonsense. it doesnt save anywhere on my pc.
or is it actually going to the phone?

tony2ltr said:
When I click on the " This, and this" haha. all I get is a screen full of nonsense. it doesnt save anywhere on my pc.
or is it actually going to the phone?
Click to expand...
Click to collapse
not sure what you are talking about. the thread is here, and all the downloads are in post #1. are you saying those links arent working?
---------- Post added at 11:18 AM ---------- Previous post was at 11:16 AM ----------
tony2ltr said:
When I click on the " This, and this" haha. all I get is a screen full of nonsense. it doesnt save anywhere on my pc.
or is it actually going to the phone?
Click to expand...
Click to collapse
here, use this one. its newer than the ones posted there and not listed for whatever reason.

They are downloading now. When they are done downloading, I'll see how I do from there. SHould the SD card be in the phone, or directly in my laptop with an adapter? and...All my equipment is at least 6 years old. I checked, and have no blue USB ports. I have an antique Vaio and a gateway netbook.
I have both open, so I can download on one, and research with the other. lol.
THEY are both running xp

tony2ltr said:
They are downloading now. When they are done downloading, I'll see how I do from there. SHould the SD card be in the phone, or directly in my laptop with an adapter? and...All my equipment is at least 6 years old. I checked, and have no blue USB ports. I have an antique Vaio and a gateway netbook.
I have both open, so I can download on one, and research with the other. lol.
Click to expand...
Click to collapse
the flashing has nothing to do with your sd card, but if you have something important on there and want to be sure its safe, you can remove it.
in some of my scripts, there is an option to wipe data or not, im not sure about the one i gave you. if the option is there, you should choose the wipe option, unless you have something on the phone itself really important you are trying to save.
ill bbiab, its time to go get some lunch

Cool. Thanks. I am still waiting for your stuff to download. My wife does support for one of the cable companies from home, so she chokes up our internet for downloading stuff. haha.
---------- Post added at 06:43 PM ---------- Previous post was at 05:50 PM ----------
Ok, SO. whaT xp program do I open the RAZR utility in? My PC doesnt know what to do with that or the TR file
SOrry for the noob questions. once I get my wings, I'll be ok. lol.
Tony

tony2ltr said:
Cool. Thanks. I am still waiting for your stuff to download. My wife does support for one of the cable companies from home, so she chokes up our internet for downloading stuff. haha.
---------- Post added at 06:43 PM ---------- Previous post was at 05:50 PM ----------
Ok, SO. whaT xp program do I open the RAZR utility in? My PC doesnt know what to do with that or the TR file
SOrry for the noob questions. once I get my wings, I'll be ok. lol.
Tony
Click to expand...
Click to collapse
the file you downloaded ir a "rar", winrar will extract it.
and its best to Quote the person you are talking to, then everyone will know who your talking to (in bigger threads) and they/i will get a notification that you quoted me. thx

is rarlab a safe place to get the winrar from?

tony2ltr said:
is rarlab a safe place to get the winrar from?
Click to expand...
Click to collapse
yes, they look fine.

How to enter Qualcomm MMC Storage (Diag 9006) in Snapdragon 415 Phone?

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.

Samsung galaxy note edge (sm-n915f) super bricked - need help urgent

Hi Guys,
For unknown reasons my fone went DEAD (BLACK SCREEN... NOT A SINGLE SIGN ON CHARGING OR USB).. Need advice what to do ??? is it dead or can be brought back to life by FLASHING ???
Any senior member or someone please help me ...

If you connect to pc how will it be?try charge it first.then connect to pc.if detect, flash stock rom.if cant,try find spare battery just in case.

FOne is not showing any charge sign or anything... just QD LOADER 9008 in Device Manager

Do you see charging light when you plug in the charger?
As long as the phone receiving power you can fix it.
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
Do you see charging light when you plug in the charger?
As long as the phone receiving power you can fix it.

Try connect to kies.does it detect or not? if you able to flash. try flash it to 5.0.1

What was the battery level (approx.)when the phone died?
You might want to try cleaning the battery and internal phone contacts with some Isopropyl Alcohol and a Qtip.
See if that helps.
Sent from my SM-N915W8 using XDA-Developers mobile app

Tried Everything... NEW BATTERY... But fone is not showing Charge on Adaptive not even on USB on LAPTOP... Just Qualcom Loader 9008 in Device Manager...

Asheque said:
Do you see charging light when you plug in the charger?
As long as the phone receiving power you can fix it.
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
Do you see charging light when you plug in the charger?
As long as the phone receiving power you can fix it.
Click to expand...
Click to collapse
Around 76%

As u can seee ONly Qualcom device in Device Manager.....

basirbilal said:
Hi Guys,
For unknown reasons my fone went DEAD (BLACK SCREEN... NOT A SINGLE SIGN ON CHARGING OR USB).. Need advice what to do ??? is it dead or can be brought back to life by FLASHING ???
Any senior member or someone please help me ...
Click to expand...
Click to collapse
Hello, did you find a solution? I helped the image of the zero block recorded on the sd-card with the program "win32 disk imager" 915F

asmixo said:
Hello, did you find a solution? I helped the image of the zero block recorded on the sd-card with the program "win32 disk imager" 915F
Click to expand...
Click to collapse
No Sir still no solution of this problem

I helped a good man, he sent an image of the device. I recorded this image of the sdcard and the device will start with "Download" mode. Next, it is necessary to firmware flashing.
915F - sorry - region "SER". But the main thing - is to run the device, further will flashing firmware what you need.
Site do not give insert a link to a file. Write me in the mail - "[email protected]" I'll send a link to file/
Write the file need with program "win32 disk imager". If this method does not help is probably a problem with the hardware.
Good luck.

As per the screen shot posted it seems your pc picked up the correct driver. Now all you need to install is Odin. Then go to samobile.com and search your phone under Firmware. Make sure you got the exact model (pull out the battery and look for exact model #). Once downloaded go to Odin and check AP and select the file you downloaded. Then put your phone on Download Mode by pressing Vol Up + PWR at same time. Follow the instructions on your phone screen.
Once you connect your phone to pc it will show up as Port 3 or 4 or wherever the driver is connected to.
** As long as on Odin your phone gets picked up you will be able to push the firmware. Once you can do that you pretty much fixed it. If it's wtong fw then you will get a notice right away, if it's correct then you see the progress bar changing.

BL is corrupted, need to repair it,
Since this is a Qualcomm based device, you can flash only BL files to an SD Card then boot your device from that card until you get into Download mode,
then reflash the device with Odin,
Follow this guide:
1. Download debrick (BL) file from HERE,
2. Download Win32DiskImager from HERE,
3. Get an 32GB SD Card and connect it to PC,
4. Setup Win32 and Run it then do as the following picture,
5. Just let it finish, Then disconnect the SD Card,
6. Make sure the device's battery is well charged,
7. Put the SD Card into the phone,
8. Now you need to boot device into Download mode either by using USB JIG or by holding (Vol-, Home and Power),
9. Once device boot into Download, Pull out the SD,
10. Now just flash the phone with Latest FW (either Factory or One-Package will do the job),
11. There is no 11, we're done ..
##NOTE: Solution is TESTED and it works.

@mirosaw2 Will this also work with the SM-N915FY? Will this keep my data (contacts, SMS, photos etc) on the internal storage? I have my SM-N915FY in a state where it wouldn't recognize any commands, but it makes a connect / disconnect sound on my Windows computer when I just connect it via USB...
My original question is here.... https://forum.xda-developers.com/note-edge/help/note-edge-sm-n915fy-bricked-dreadful-t3754559
Edit: I just tried it and it worked!!! Thank you very much, now I'm able to restore my data and then I'll try to make the error gone with this tutorial: https://forum.xda-developers.com/showpost.php?p=66879466&postcount=10

My N915F stuck at Nand write start and the guide does not work.What else to do?

similar Problem
I have a note edge too, device flashed with stock firmware first but no luck, tried repair firmware and odin froze, talked
to experts and they said the partition is corrupted, device is stuck in "problem encountered while upgrading firmware . connect to kies and try again." how to fix ?????

Samsung Galaxy S8+ Hard Bricked. Only Upload Mode!! How to Enter Download Mode???

Ok so I went to flash twrp recovery onto my phone and something went wrong while using oden... My usb debugging is turned on and OEM Unlocked. Now my phone screen stays completely black. Its caught in a bootloop and No buttons work to bring it back into download mode, Only Upload mode works.. But Odin will not flash anything to my phone in Upload mode. It changes my samsung usb drivers to msm upload or modem drivers. I have been at this for weeks trying to get my s8+ to attach to my computer again using ADB, ODIN, SD CARD, AND EVEN THAT JIG Thing to force it into download mode but TO NO AVAIL.. I Have to some how get back into download mode but no button combinations will work.. It seems to bootloop on me before it reaches those commands. The bootloader is obviously gone to a certain degree since upload mode still works.. Is there any way to use Odin in upload mode? Or is there any other way I can reflash stock rom to fix this issue? I have no recovery, no safe mode, no download mode?? My phone is basically a paper weight right now.. When I know All my stuff is still on there. This S8+ Phone has put up a good fight with me on my pc But Im not one to loose. I love a good challange.. Any suggestions. I thought ADB Was my best bet but with no connect I cant do any thing. I cant' get Adb to find my device. Oh even tryed older versions of odin with low level quallcom drivers and that didn't work either. Odin will read a com port to my device but i'm in the wrong mode (Upload Mode) and Odin cant establish a connection. When in Upload Mode its the hellish one as xda deveopers have said before..
S8+ phone is Model Number SM-G950U
Witch I believe has now been upgraded to SM-G955U OR F.. But I have the original stock rom still for SM-G950U if only I can get into some kind of Download Mode.
Ive even sat watching odin as I push every single button combination watching the ports appear and dissapear as it reboots trying to find some kind of way to download to the phone... But no luck..
UNKNOWN ERROR
DDR VENDER : UNKNOWN
SOC_HW_REVISION : 2.1
SKIP PRINT_SUMMERY_TO_LCD
GENERATING SUMMERY........
GENERAL INFO
DDR INFO
DCVS INFO
RPM INFO
RECOVERED FROM AN EXCEPTION
DONE
Then if I hold the up button for a few seconds I get this underneath
SYNCHRONOUS EXCEPTION
LR : 0x0000000085e36d98
sp : 0x000000001407bbb0
pc : 0x0000000085e36df8
Not sure what that means or how to look up those codes but I know its all bad.. If anyone can think of any other way to connect my phone to reflash stock rom to fix Please let me know any theories or suggestions you may have for me to try... Thank You...

Gkeplar said:
Ok so I went to flash twrp recovery onto my phone and something went wrong while using oden... My usb debugging is turned on and OEM Unlocked. Now my phone screen stays completely black. Its caught in a bootloop and No buttons work to bring it back into download mode, Only Upload mode works.. But Odin will not flash anything to my phone in Upload mode. It changes my samsung usb drivers to msm upload or modem drivers. I have been at this for weeks trying to get my s8+ to attach to my computer again using ADB, ODIN, SD CARD, AND EVEN THAT JIG Thing to force it into download mode but TO NO AVAIL.. I Have to some how get back into download mode but no button combinations will work.. It seems to bootloop on me before it reaches those commands. The bootloader is obviously gone to a certain degree since upload mode still works.. Is there any way to use Odin in upload mode? Or is there any other way I can reflash stock rom to fix this issue? I have no recovery, no safe mode, no download mode?? My phone is basically a paper weight right now.. When I know All my stuff is still on there. This S8+ Phone has put up a good fight with me on my pc But Im not one to loose. I love a good challange.. Any suggestions. I thought ADB Was my best bet but with no connect I cant do any thing. I cant' get Adb to find my device. Oh even tryed older versions of odin with low level quallcom drivers and that didn't work either. Odin will read a com port to my device but i'm in the wrong mode (Upload Mode) and Odin cant establish a connection. When in Upload Mode its the hellish one as xda deveopers have said before..
S8+ phone is Model Number SM-G950U
Witch I believe has now been upgraded to SM-G955U OR F.. But I have the original stock rom still for SM-G950U if only I can get into some kind of Download Mode.
Ive even sat watching odin as I push every single button combination watching the ports appear and dissapear as it reboots trying to find some kind of way to download to the phone... But no luck..
UNKNOWN ERROR
DDR VENDER : UNKNOWN
SOC_HW_REVISION : 2.1
SKIP PRINT_SUMMERY_TO_LCD
GENERATING SUMMERY........
GENERAL INFO
DDR INFO
DCVS INFO
RPM INFO
RECOVERED FROM AN EXCEPTION
DONE
Then if I hold the up button for a few seconds I get this underneath
SYNCHRONOUS EXCEPTION
LR : 0x0000000085e36d98
sp : 0x000000001407bbb0
pc : 0x0000000085e36df8
Not sure what that means or how to look up those codes but I know its all bad.. If anyone can think of any other way to connect my phone to reflash stock rom to fix Please let me know any theories or suggestions you may have for me to try... Thank You...
Click to expand...
Click to collapse
You have a 950 u locked bootloader. First mistake trying to flash twrp. Only option you have is finding the revision bootloader you where on edl files and pinout to 9008 edl mode. There as of last known no fix other than for upload mode only.

Thank You
TheMadScientist said:
You have a 950 u locked bootloader. First mistake trying to flash twrp. Only option you have is finding the revision bootloader you where on edl files and pinout to 9008 edl mode. There as of last known no fix other than for upload mode only.
Click to expand...
Click to collapse
Thank You I will try that And reply back with results

Gkeplar said:
Thank You I will try that And reply back with results
Click to expand...
Click to collapse
What revision bootloader was it on? I have several of them but not all

TheMadScientist said:
What revision bootloader was it on? I have several of them but not all
Click to expand...
Click to collapse
It was on its original bootloader for the Samsung Galaxy S8+ SM-G950U. It was SnapDragon bootloader

TheMadScientist said:
What revision bootloader was it on? I have several of them but not all
Click to expand...
Click to collapse
I'm working on reading this thread now trying to follow there instructions, https://forum.xda-developers.com/galaxy-s8/help/s8-g950u-hardbrick-t3668572

Gkeplar said:
It was on its original bootloader for the Samsung Galaxy S8+ SM-G950U. It was SnapDragon bootloader
Click to expand...
Click to collapse
Mate there are 7 different revisions of the 950 u bootloader. Across all the software updates. No offense intended. But if you can't even give this little bit of info I can assure you. Your not gonna be able to dissemble this device. Ground out the test points to enter edl. And flash needed repair files. Which is very tedious. If there is any issues. I would mark this device as lost and get another. I dont feel that you have the necessary skills needed to complete this process...
---------- Post added at 10:49 PM ---------- Previous post was at 10:38 PM ----------
Gkeplar said:
I'm working on reading this thread now trying to follow there instructions, https://forum.xda-developers.com/galaxy-s8/help/s8-g950u-hardbrick-t3668572
Click to expand...
Click to collapse
Unless you are on revision 2 bootloader that is no use to you
---------- Post added at 10:51 PM ---------- Previous post was at 10:49 PM ----------
Gkeplar said:
I'm working on reading this thread now trying to follow there instructions, https://forum.xda-developers.com/galaxy-s8/help/s8-g950u-hardbrick-t3668572
Click to expand...
Click to collapse
Unless you are on revision 2 bootloader that is no use to you
You are not in edl mode. You are stuck in upload. The only way to get to edl mode is disassemble the device flip the motherboard upside down while hooked up. Ground out a test pin on the mother board while connecting the usb cable.

Bricked My phone, cant get into FastbootD to fix it

So i recently wanted to root my OOS 12 oneplus nord, and i bricked it..
i cant get into fastbootD, Recovery, or anything at all except fastboot, the device is detected as Android bootloader interface in device manager, i have tried using: msm tool, flashing normal rom (error: partition not found and Flashing is not allowed for critical partition)

As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS

Azeld said:
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Click to expand...
Click to collapse
As I said, msm didn’t work for me

Hafted said:
As I said, msm didn’t work for me
Click to expand...
Click to collapse
may be need to reinstall drivers? should be displayed differently in the device manager than Android bootloader interface.

gorro8 said:
may be need to reinstall drivers?
Click to expand...
Click to collapse
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there

Hafted said:
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Click to expand...
Click to collapse
what do you do to enter the edl mode?
what cable are you using?

gorro8 said:
what do you do to enter the edl mode?
what cable are you using?
Click to expand...
Click to collapse
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys

I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com

download the correct drivers and replace them in the device manager

gorro8 said:
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
Click to expand...
Click to collapse
Ok, I’ll try that and give you an update, Ty!

worth trying another USB port too, even if they are supposed to be the exact same. Same thing happened with my laptop, tried another (presumably identical) USB port and it works first time, every time

Hafted said:
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
Click to expand...
Click to collapse
1st, u really should find the exact drivers. But also very important to remember booting your PC into Test Mode with Driver Signature Enforcement OFF - BEFORE installing the EDL 9008 Drivers for your device.
Besides, after you press and hold both Vol buttons, u should plug the device in IMMEDIATELY, not waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.

Hey, so after some time (I got a new phone by now) I managed to fix it, turns out that i had to instantly put in the cable, just like how LinhBT Said
LinhBT said:
waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Click to expand...
Click to collapse

Here is something that might work for unbricking and/or getting in to EDL-mode:
Unable to reinstall Oxygen OS from custom ROM. FAILED (remote: Flashing is not allowed for Critical Partitions ). Need assistance, details below.
Hello, friends. So I am here following this exact tutorial : https://www.thecustomdroid.com/oneplus-nord-oxygenos-restoration-guide/ I currently am stuck there @pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$...
forum.xda-developers.com