Develop Bugs

Regarding Moorefield functionality

I'm wondering, when going through the different boot modes, bootloader and recovery, there is a third option that shows up on the pc called Moorefield. It's an unknown driver, which leads me to believe there is some sort diagnostic functionality to it. I guess it's just a matter of figuring out what drivers work. I was wondering if anyone has had this experience, and/or knows how to work with it.

Moorefield is the name for intel processor. It will come handy when all other option to recover phone are not working. But for that we need drivers and image file to jumpstart.

harpreet.s said:
Moorefield is the name for intel processor. It will come handy when all other option to recover phone are not working. But for that we need drivers and image file to jumpstart.
Click to expand...
Click to collapse
how ?

Ex search for intel phone tool which allows to flash images. I have not used it till now however i am pretty sure it will help recovering phone when fastboot , recovery , adb are unable to.

rikkxzzz said:
how ?
Click to expand...
Click to collapse
We've been looking into that over here: http://forum.xda-developers.com/zenfone2/general/unbricking-research-unbricking-method-t3162848

lg g3 bricked shows qdloaderboard diag says ap check failed device not in dwnld mode

i rooted my lg g3 d 855 lollipop and tried to install TWRP
but it was not a success i lost recovery + download mode but it boots perfectly into android system and can use it normally
to install twrp again i tried to flash it again and again but no success
then i flash aboot.img and it all went blank not booting not rrecovery etc
i tried board diag method to unbrick it shows up in my system as qcomm hs usb 9008
but when using board diag it says DEVICE NOT FOUND IN DLOAD MODE
plz help this is my first android phone after months of hardwork
i dont think i have enough money to replace the mobo or buy a new one:crying:

Hello,
it's recoverable, but you need to read and some knowledge...
Refer to this thread. Proceed point by point and use willcracker boarddiag.

halekhonza said:
Hello,
it's recoverable, but you need to read and some knowledge...
Refer to this thread. Proceed point by point and use willcracker boarddiag.
Click to expand...
Click to collapse
brother i used board diag method it is succesfully able to show my device as qcomm hs usb 9008
and im able extract the files with program
but when i click start after some time it says ap check failed ,device not found in dload mode
i desperately need ur help IM NEW TO XDA FORUMS I HOPE ANYONE WOULD BE ABLE TO SOLVE PROBLEM
tnx in advanc

adilismail62 said:
brother i used board diag method it is succesfully able to show my device as qcomm hs usb 9008
and im able extract the files with program
but when i click start after some time it says ap check failed ,device not found in dload mode
i desperately need ur help IM NEW TO XDA FORUMS I HOPE ANYONE WOULD BE ABLE TO SOLVE PROBLEM
tnx in advanc
Click to expand...
Click to collapse
I understand. I'm just asking if you really using right boarddiag (thread that I mentioned - willcracker.rar)
Also be sure that you have a phone connected to right port (check it in device manager)

halekhonza said:
I understand. I'm just asking if you really using right boarddiag (thread that I mentioned - willcracker.rar)
Also be sure that you have a phone connected to right port (check it in device manager)
Click to expand...
Click to collapse
halekhonza said:
I understand. I'm just asking if you really using right boarddiag (thread that I mentioned - willcracker.rar)
Also be sure that you have a phone connected to right port (check it in device manager)
Click to expand...
Click to collapse
yes im using the r8 port it shows in device manager and in board daig also i gave port 14
before my phone was going to get bricked its battery was low
is it affecting the procedure i think my battery is not charging
when i remove battery and connect to pc phone shows battery not inserted sign when i insert the batery it disappear and no sign of charging
i thought this might help:good:

You have to use the original LG usb cable. Dont try with fake china cables because its a lot possible to have troubles with them.

bricked my amazon fire phone

I was trying to go back to stock os from cm11 on the Amazon fire phone. Downloaded a stock rom and tried to install using safestrap.
After I pressed reboot the phone turned off but didn't turn back on. It's not responding to anything , not even goes into recovery , but when I connect it to computer by cable , six partitions show up , five of which it says are in need of format , and one contains a folder named image , which has a lot of files.
I'm new to this , got cm by following a simple guide , help pls

Hi to you all!
I have exactly the same issue.
If I connect the Fire Phone to the Pc there are six partitions that show up. So ADB sideload is not possible any more. Ialready disconected the battery- did not work out
Does any of you have any idea?
Thanks

How come no one answered to this issue since 2016
Good day everyone,
I wonder why this issue was not replied to since 2016 on a professional forum. Is it because its not fixable?
I just bought an Amazon Fire Phone 64GB, the AT&T version. I already knew the phone was a complete disaster, but I still bought due to my low budget. Its the SnapDragon 800 series processor which I considered for such a small budget phone. Anyways, I rooted it via KingRoot, installed Safestrap-Kodiak-4.0.1-B01. I then downloaded the Unlocked version of the Fire phone Fireware "update-kindle-35.4.6.6_user_466000820" (since I wanted to avoid AT&T bloatware. I reside outside the States so cant use AT&T, so no use keeping it running all the time and sacrifice my battery) and flashed that. It flashed alright but got stuck after the welcome screen after selecting English (United Sates or UK). I then thought of of reverting it back to its original state Fire OS Ver 3.5, so downloaded "update-fire-phone-121_1.0.1_user_101012120" and now it has no life what so ever. Now it in the same state as mentioned by 2 others on this thread. It shows total 6 partitions with only 1 partition with an "Image" named Dir and a few files around 53MB or so residing in it.
I have snapshots of the Image folder files and the "QHSUSB_Bulk" status shown in Device manager, but I cant seem to find an option here to attach my jpg's here. Gosh! It doesnt get dumber than this.
Requesting help from someone who can help me out with anything at all, links, text, vdo's.
I've already downloaded the following files, but dont have a clue what to do with any one of them
QPST.2.7.460
Qualcomm_Flash_Image_Loader_v1.0.0.3
SRKtool_2.1_droidth
Qualcomm HS-USB QDLoader 9008 Driver Qualcomm HS-USB QDLoader 9008 Driver2.1.0.4
Qualcomm HS-USB QDLoader 9008 Driver Ver8.5

Have you tried going into adb sideload, installing adb drivers and sideloading the stock rom?

Now deleted the 29 partitions of the phone.
After experimenting with it, i deleted the 29 partitions of the phone, now its not even showing Qualcomm eMMC USB Storage in device manager.:crying:. Is there anyone who can help me out here. I'd really be grateful.

No life in the phone except for QDLoader 9008 (COM4)
Android# said:
Have you tried going into adb sideload, installing adb drivers and sideloading the stock rom?
Click to expand...
Click to collapse
Its not powering up, going into stock recovery even so i cant get into sideload, if my understanding is correct.

SohailAzeem said:
Its not powering up, going into stock recovery even so i cant get into sideload, if my understanding is correct.
Click to expand...
Click to collapse
*****Sorry, just realized that you can't get into stock recovery anymore please disregard the following as obviously that would only help if you could enter recovery*****
I am sure you already tried but what i meant to say was if you tried power + volume up button, you end up in stock recovery and that's where you gotta go, and select "apply update from ADB" from the recovery menu.
But even before all this, first make a new folder on your desktop, then download the ADB drivers for windows from here: https://developer.android.com/studio/releases/platform-tools.html
Extract the ADB drivers into the new folder you just made. Now, go to https://www.amazon.com/gp/help/customer/display.html?nodeId=201607550 and download the 4.6.6.1 bin file for Amazon Fire Phone, either version will work with AT&T phone, and also put the bin file in the new folder you made earlier. Rename the bin file to just 'fire' or something short and easy. Now on an empty space in that folder press Shift + Right Click together, and select 'open command prompt or windows powershell from here' depending on your computer OS.
Now make sure your phone is powered off, then press power + volume up together to get into stock recovery, and you will see option "apply update from ADB", select that and when phone is ready, connect it to the computer via usb cable. In the command prompt window on the computer, type 'adb devices' and press enter. It should show the amazon phone in adb devices list. Next, type 'adb sideload fire.bin'. If you named the bin file something else make sure you replace 'fire' with that. It will take about 5-10 minutes and once done it should be able to boot normally. You can use kingroot 4.1 and then replace the kinguser with SuperSU using the supersume app. You can download supersume app by searching online or from google appstore, either one works. Hope this helps.

SohailAzeem said:
After experimenting with it, i deleted the 29 partitions of the phone, now its not even showing Qualcomm eMMC USB Storage in device manager.:crying:. Is there anyone who can help me out here. I'd really be grateful.
Click to expand...
Click to collapse
No you bricked it good and proper now.
I have bricked 3 now
It seems while you still have QDLoader 9008 showing up the device is repairable and any Official repairer would be able to restore the phone easily with the correct software and recovery firmware package.
I was in this exact same situation and was unable to get out of this mode even after using "dd" to send the stock recovery and my backed up .img's
Once you Kill the phone in this mode (As I did) it's un fixable and Amazon will send you a new or replacement phone if it still has any manufacture warranty time left.
They will be unable to prove you tampered with it since they cant revive them :laugh:
Just tell them it bricked during a adb side load of the official firmware.

bigrammy said:
No you bricked it good and proper now.
I have bricked 3 now
It seems while you still have QDLoader 9008 showing up the device is repairable and any Official repairer would be able to restore the phone easily with the correct software and recovery firmware package.
I was in this exact same situation and was unable to get out of this mode even after using "dd" to send the stock recovery and my backed up .img's
Once you Kill the phone in this mode (As I did) it's un fixable and Amazon will send you a new or replacement phone if it still has any manufacture warranty time left.
They will be unable to prove you tampered with it since they cant revive them :laugh:
Just tell them it bricked during a adb side load of the official firmware.
Click to expand...
Click to collapse
Wow! That very sad. That was a new phone. Didnt even have a chance to use it. I thought android phones were unbrickable. What brands give away there firmware to be flashed, or in other words Phones which are unbrickable.

SohailAzeem said:
Wow! That very sad. That was a new phone. Didnt even have a chance to use it. I thought android phones were unbrickable. What brands give away there firmware to be flashed, or in other words Phones which are unbrickable.
Click to expand...
Click to collapse
If your able just return the phone as said then they will likely send you a replacement or refund. :good:
Nearly all phones are brickable if you try hard enough but this fire phone is very very easy to brick :laugh:
(In My Opinion only) If you want a cheap almost unbrickable phone then go with the cheap china brands using the MediaTek CPU's. Stay away from the flag ship brands like sony htc lg samsung which use MediaTek CPU's as these manufacturers locked their devices down by removing the MediaTek flashing method and installing their own.
SPFlashTool is the PC software and the Swiss Army knife used for MediaTek so ensure you research :good:
Team MAD (MediaTek Android Developers) Have quite a few devices they support so choose any of those depending on your budget and it will ensure you get some decent updates and running the Latest Android Version. :good:
Do your research by reading the associated threads before you choose.
https://github.com/MediatekAndroidDevelopers

i think you don't read carefully what the Problem is.
Hi to you all!
I have exactly the same issue.
If I connect the Fire Phone to the Pc there are six partitions that show up. So ADB sideload is not possible any more. The Phone is not working not getting ON. The phone is in Dead Condition but if you Connect with PC it shows its Memory Partations. if any phone not getting ON than how can enter to ADB Mode...???

Lumia 820 bricked NEED HELP please

my lumia 820 bricked ,connect to pc is showed below ; how to fix it

you tried Windows Device Recovery Tool?
http://go.microsoft.com/fwlink/p/?LinkId=522381

dxdy said:
you tried Windows Device Recovery Tool?
http://go.microsoft.com/fwlink/p/?LinkId=522381
Click to expand...
Click to collapse
i'm tried WDRT,cmd prompt methods and wpinternals but didn't show my lumia ,any other idea to recover my lumia

plz help.... any idea about this

Gokul Rajan said:
plz help.... any idea about this
Click to expand...
Click to collapse
USE THIS AS STARTING POINT!!!
I once bricked a LG Leon and the solution to pc not recognizing the device was pinning the motherboard so the pc recognizes the qualcomm and you would be able to flash it, something like this:
Pinning

xxJMarian said:
USE THIS AS STARTING POINT!!!
I once bricked a LG Leon and the solution to pc not recognizing the device was pinning the motherboard so the pc recognizes the qualcomm and you would be able to flash it, something like this:
Pinning
Click to expand...
Click to collapse
how to reinstall qualcumm bootloader?

Gokul Rajan said:
how to reinstall qualcumm bootloader?
Click to expand...
Click to collapse
You need something like boardiag as shown in the video and some files to flash it, once you do the pinning and the pc recognizes the device, you will be able to flash it, you need some specific files. As far as i remember i had some folders with files with some LG models, G2, G3, etc... you need to find all the files compatibles with your device, i would suggest you first try everything to make it work without the pinning step, if you don't succeed then start thinking about this step, you can also try to do it without flashing the qualcomm, once your pc recognizes the device you might be able to recover it with WDRT without having to flash the qualcomm. Sadly, i cannot provide you with a full tutorial (including must dos if something goes wrong) because i don't have the required experience to do so.

emmc error? Suddenly black screen

Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!

slev!n said:
Hello guys,
Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.

knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/

knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
slev!n said:
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/
Click to expand...
Click to collapse
slev!n said:
Hello guys,
I've got an issue and don't know if it belongs to the build or not. I'm on the last build with my 3T and today after charging my phone I couldn't turn on WiFi or start any app. It just didn't open. So I restated my phone but it never booted. Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
Sounds to me like an hardware error involving (but not necessarily limited to) emmc access. That would explain, why the parts still in ram (like homescreen) were still working but apps won't start anymore, as well as the blank screen on device startup (even the logo needs emmc access to read the logo partition).
Try unbricking (I'm afraid your pc won't find the device, if my guess is correct), if that fails: rma or repair center.

slev!n said:
Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)

150208 said:
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)
Click to expand...
Click to collapse
Thanks, I'll create a post there. Just one more post here:
I used this phone just carefully at home as a media device. So this brick came totally out of nowhere. When I connect my bricked 3T now to my computer it makes the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more pop up again.

slev!n said:
I'll create a post there.
Click to expand...
Click to collapse
When you've created that post ask the moderators to move this complete conversation from this thread to the newly created on in the help forum, please. This helps to keep this thread readable and searcheble.
For your trouble: if you can't boot rom, recovery nor fastboot mode, it doesn't make sense to debug the usb connection: what should the pc connect to if none of the three is bootable? There is just nothing up to connect to. That's why I recommended unbrick tool - if that fails rma or go to a repair center.

Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!

Post SS of the device manager after connecting the phone to the PC

150208 said:
Post SS of the device manager after connecting the phone to the PC
Click to expand...
Click to collapse
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
@slev!n: please ask the moderators to move the existing conversation to thos from the los16 thread here. If all postings have moved, ask the moderators to move this thread from op3/help to op3t/help.

@nvertigo67 I wanted to do so and was searching how to contact moderators but couldn't find it in my XDA app. Maybe someone can give me a hint? I'm kind of new on xda... Thanks!
@150208 And as I wrote: it's not possible to get any kind of message on windows anymore. Just the sound appears when I connect and disconnect.
@nvertigo67 I was also following your advice to use the unbrick tool. I followed the steps on oneplus forum:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
When it comes to the integrity check windows doesn't accept "TESTSIGNING ON". And so windows doesn't recognise my phone in the device manager for the next steps.
And I guess RMA or repair centres are super expensive. I don't know if it's worth it? I thought about buying a device with a broken screen on eBay and try to change the motherboard...

Log in with a web browser locate each posting of the comversation. For each posting in question use the little triangle icon at the botom on the left side, report each posting, set non-urgent and pit the link of this thread together with something like "Please move this posting to the linked thread, thanx in advance".
For disabling driver signature enforcement try method 2. from this post: http://maxedtech.com/about-testmode/
Most of tbe time xda postings are more reliable and more current then the Oneplus forums: https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722, https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722

slev!n said:
[MENTION=4405529]i thought about buying a device with a broken screen on eBay and try to change the motherboard...
Click to expand...
Click to collapse
If you already have a thought why do you keep asked here though? If you want another possible solution, at least put an effort to provide the information needed when asked by the one who tried to help you
I'm not into a guessing games, so i'm out
nvertigo67 said:
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
Click to expand...
Click to collapse
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
If it's hw problem, i'll try not to jump on MB conclussion yet, since there are still another possible reason
When talking about MSM, you need to make sure it's available first on the device manager
Otherwise, it's a waste of data for downloading the tool in these human malware days
Oh yes, the msm guide is quite lag behind. You don't need to boot into test mode anymore with the current driver for qualcomm
I flashed a lot qualcomm devices with w10 without the need to boot into test mode

150208 said:
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
Click to expand...
Click to collapse
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
For the costs of rma: maybe it's expensive - maybe oneplus will be obliging... Since you don't relay on the device as your daily driver, you can ask for an estimate of costs - so you can decide if it's worth the costs.

nvertigo67 said:
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
Click to expand...
Click to collapse
Wait, I fail to see your explanation in line with mine. I want to start debug it on the windows side, but you seems to see it on the phone side.
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.

150208 said:
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.
Click to expand...
Click to collapse
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc. In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side. Once this is fixed (at least fastboot mode is up again) you can utilize the "normal" usb connection again.
What do you want to do with the usb connection, if neither fastboot mode nor recovery is up amd running? What is your suggested next step, if the device is recognized? What should the pc recognize if neither fastboot nor adb os an option? Which command or procedure will fix the emmc?

nvertigo67 said:
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc.
Click to expand...
Click to collapse
Yes, there are other tools but i'm not gonna bother since it's paid
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect. There are 4 status when a device plugged into the pc.
1. detected and driver is loaded
2. detected and driver isn't loaded
3. detected but not recognized
4. no sign at all
1 and 2 is sw problem, 3 and 4 is hw problem
In order for MSM to do it's job, you need to have either problem no 1 or 2 with qualcomm qloader 9008 driver already or later detected in devmanager
So it's important to know the driver status
OP states there was sounds coming then nothing, which mean it's either 2 or 3, more like 3 but again i repeating myself i don't like guessing games
I don't understand the part why you're explaining/asking about fastboot recovery or etc, his phone is on dead state, nothing-literally-no sign of life unless he plug it to the pc and then it making sounds for the first time,
Why do you even bother thinking about it?
nvertigo67 said:
Which command or procedure will fix the emmc?
Click to expand...
Click to collapse
No procedure will fixed his phone since there are no enough information
I think your other question should be already answered. If else, i don't know what to say anymore.

150208 said:
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect.
Click to expand...
Click to collapse
If so, please explain how you can format a partition or fix the partition table if neither fastboot mode nor recovery (or a rooted system for that matter) is bootable.
@slev!n: please give a screenshot of the device manager to @150208. I'm too curious to learn how to fix a broken emmc without recovery nor fastboot mode.

Thank you so far!
I dont want to bother someone. Just thinking about further options thats why I wrote my thought about replacing the motherboard down.
I 'm in test mode now and I did this:
"Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for a few seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB (under COMs and Ports)]."
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?

slev!n said:
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?
Click to expand...
Click to collapse
The pic is from msm tool, not the device manager. No unknown device in device manager?