I have noticed that FTM mode isn't always accessible (VolDown+Power for about 5 seconds). And I think it is dependent on which ROM and bootstack is installed. I can't seem to access it if I'm running a ROM like AOSP Extended, LineageOS, Resurrection Remix, or similar. But it always seems to be accessible if I am running the stock ROM.
FTM itself isn't important, except that it provides a restricted ADB shell that can be used to reboot into other modes, like EDL. Let's say you get into a situation where recovery, boot, and system are inaccessible. And you can't access EDL either. This happened to me recently and I had to send the phone back to ZTE. Back then, FTM would have been very useful for getting into EDL, rather than being stuck in DFU.
Can some people running various ROMs (stock/stock-based or custom) test access to FTM and say whether you can get into it or not? I don't particularly care whether it is Marshmallow, Nougat, Oreo, which model of the A7 you have, etc. And it is a quick test that won't inconvenience anyone. Please state which ROM and bootstack you were running at the time of the test, and which A7 variant. I'm just curious, is all. To prevent bricking the phone, access to as many modes as possible are important, the 2 most important being EDL and TWRP.
I think I remember reading on one of ZTE's websites says that FTM is "field test mode", and is a software-based mode rather than hardware. Probably used for running various tests. And it seems to be dependent on the presence of certain files in the system partition (located at /system/vendor/etc), which aren't present on non-stock custom ROMs. I have noticed that this mode is also not accessible if the system partition is empty (wiped/formatted), even if on a stock ROM with the stock bootstack.
Thanks!
AnonVendetta said:
I have noticed that FTM mode isn't always accessible (VolDown+Power for about 5 seconds). And I think it is dependent on which ROM and bootstack is installed. I can't seem to access it if I'm running a ROM like AOSP Extended, LineageOS, Resurrection Remix, or similar. But it always seems to be accessible if I am running the stock ROM.
FTM itself isn't important, except that it provides a restricted ADB shell that can be used to reboot into other modes, like EDL. Let's say you get into a situation where recovery, boot, and system are inaccessible. And you can't access EDL either. This happened to me recently and I had to send the phone back to ZTE. Back then, FTM would have been very useful for getting into EDL, rather than being stuck in DFU.
Can some people running various ROMs (stock/stock-based or custom) test access to FTM and say whether you can get into it or not? I don't particularly care whether it is Marshmallow, Nougat, Oreo, which model of the A7 you have, etc. And it is a quick test that won't inconvenience anyone. Please state which ROM and bootstack you were running at the time of the test, and which A7 variant. I'm just curious, is all. To prevent bricking the phone, access to as many modes as possible are important, the 2 most important being EDL and TWRP.
I think I remember reading on one of ZTE's websites says that FTM is "field test mode", and is a software-based mode rather than hardware. Probably used for running various tests. And it seems to be dependent on the presence of certain files in the system partition (located at /system/vendor/etc), which aren't present on non-stock custom ROMs. I have noticed that this mode is also not accessible if the system partition is empty (wiped/formatted), even if on a stock ROM with the stock bootstack.
Thanks!
Click to expand...
Click to collapse
FTM is factory testing mode (says so right in the mode itself) and won't work if you have a DFU brick, even on stock. That's the whole point of DFU unbricking. One guy said that he could save his phone by running down the battery entirely then using the combination to enter ftm. I've been telling bricked people to replicate this for quite some time, nobody could.
@Choose an username...: Thanks for the clarification, but the exact meaning of FTM is really just semantics if you ask me. The important thing is that it allows rebooting into EDL in the event that other boot modes are inaccessible. I have heard that EDL can't be accessed on the A2017G via the hardware button combo, so 'adb reboot edl' from FTM is the only way if you are locked out of Android. I'll take your word that FTM won't work if you are DFU bricked, I couldn't access it either.
The whole point of this topic is to ask people who are *not bricked* if they can access FTM, as a means of getting elsewhere.
AnonVendetta said:
@Choose an username...: Thanks for the clarification, but the exact meaning of FTM is really just semantics if you ask me. The important thing is that it allows rebooting into EDL in the event that other boot modes are inaccessible. I have heard that EDL can't be accessed on the A2017G via the hardware button combo, so 'adb reboot edl' from FTM is the only way if you are locked out of Android. I'll take your word that FTM won't work if you are DFU bricked, I couldn't access it either.
The whole point of this topic is to ask people who are *not bricked* if they can access FTM, as a means of getting elsewhere.
Click to expand...
Click to collapse
You can acces EDL with button combo onthe G variant.Also you can boot in EDL if FTM works
AnonVendetta said:
@Choose an username...: Thanks for the clarification, but the exact meaning of FTM is really just semantics if you ask me. The important thing is that it allows rebooting into EDL in the event that other boot modes are inaccessible. I have heard that EDL can't be accessed on the A2017G via the hardware button combo, so 'adb reboot edl' from FTM is the only way if you are locked out of Android. I'll take your word that FTM won't work if you are DFU bricked, I couldn't access it either.
The whole point of this topic is to ask people who are *not bricked* if they can access FTM, as a means of getting elsewhere.
Click to expand...
Click to collapse
Some time ago I had a serious problem by reverting back to A2017G stock B10 to achieve B12. I did something wrong in a hurry and afaik DFU bricked the phone.
There was only the QUSB when trying the button EDL combo and the hardwareID under QUSB was : (there was even a text 'DFU...'
Code:
USB\VID_19D2&PID_0112&REV_0000
USB\VID_19D2&PID_0112
My friend djkuz acknowlegded it was a DFU because values should look like :
Code:
USB\VID_05C6&PID_9008&REV_0000
USB\VID_05C6&PID_9008
But the good part was - and i dont know why - i COULD enter FTM with the 2 button combo.
But only the drivers were not installed the right way. There was 'adb interface' and 'android' with an exclamation sign.
I just reflashed drivers : https://androidfilehost.com/?fid=745425885120753806
And I could adb reboot EDL.
Im not an expert on this but I can only say that the symptons were DFU but there was that way to unbrick through FTM.
Nice info, but the real point of this thread is to establish whether FTM is only available if you are running a stock/stock-based ROM. Because when I have tried to access FTM on AOSP/Lineage/CM-based ROMs (or similar), I have never been able to access FTM. That's why I'm specifically asking whether others can test too, regardless of their specific configuration.
hi, cause of my work (pc and smartphone engineer) i fix only hardware. But there are some very rare cases that some people trust their phone to me to unbrick it when nobody else here at my town can.
So now i have to fix a xiaomi mi a1 which is hard bricked and the customer didn't allow bootloader unlock in developer settings.
It doesn't boot and so it doesn't allow me to fix it in bootloader mode (not allowed to flash partitions).
In EDL mode i get errors too.
What i need is some guidance how i can fix that xiaomi and any xiaomi when that happens.
Let's start with mi a1 now.
Which mode should i use ? (i guess EDL)
And which stock rom ?
Nevermind I fixed it on my own. Booted to edl and flashed all the partitions there.
I have a smartphone that I need to recover data from, I can't find information anywhere as to the EDL points on the motherboard. Can someone help? I attach the photos.
Hey yall, I've put myself in a dumb position.
I bricked my phone to the point where any time I boot up my phone, it only shows "QUALCOMM CRASH DUMP". Not to mention both fastboot and recovery are gone from the picture. My only real option is EDL mode.
I was able to find a couple methods and was able to dump userdata.bin (219GB) using the first link's method.
Recovering data from Mi 4c able to get only to fastboot (StackExchange)
[GUIDE] How to dump and write back the storage on most of Qualcomm devices
I'm fairly out of my element with all this and I haven't figured out how to mount it properly, so I'm not really sure what to do from this point on. Any info is a great help, even if you have to break the news that my work may be for nought.
hi guys, i have a oneplus 8 pro model phone. I tried to install OTA with a program called Fastboot Enchancer. However, after the installation was complete, my phone did not turn on again. Fastboot mode, and recovery mode won't boot. It doesn't open in edl mode, which is the only one I trust and use often. When I connect it to the computer, it does not respond at all. I have done recovery with edl mod many times with MSM tool, but now I can't. Looking forward to your help and ideas.
If your device no longer ever appears as a USB device and the screen is not helpful and you've tried all the "magic" gestures like holding down 3 buttons and standing on your head, then you'll have to do something different.
This kind of thing happens when something is broken, but it's not broken enough that it realizes that it's broken.
Life is easier when it's totally broken.
Possibilities are:
1) find the EDL test points inside and connect them while reseting.
2) disable data lines or clock to the flash so that it can't read anything and knows that it can only go to EDL.
3) JTAG to fix the problem or else just wipe the SBL so that it goes to EDL.
4) Use a USB UART. Maybe it's getting as far as u-boot and you can stop it and make it go to fastboot.
x_files_X said:
hi guys, i have a oneplus 8 pro model phone. I tried to install OTA with a program called Fastboot Enchancer. However, after the installation was complete, my phone did not turn on again. Fastboot mode, and recovery mode won't boot. It doesn't open in edl mode, which is the only one I trust and use often. When I connect it to the computer, it does not respond at all. I have done recovery with edl mod many times with MSM tool, but now I can't. Looking forward to your help and ideas.
Click to expand...
Click to collapse
Sometimes you have to hold VolUp + VolDown + Power for a long time before anything happen. As far as i know we dont know about any EDL points ant the op8 and we have the button combo anyway.
SInce you post on the op8pro forum you probably have a op8pro (obviously) and since you used fastboot i guess you simly hard bricked you phone beyond repair. Your phone RAM is overvolted and dead. And i dont think JTAG or anything else next to a motherboard swap can help you here.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Renate said:
If your device no longer ever appears as a USB device and the screen is not helpful and you've tried all the "magic" gestures like holding down 3 buttons and standing on your head, then you'll have to do something different.
This kind of thing happens when something is broken, but it's not broken enough that it realizes that it's broken.
Life is easier when it's totally broken.
Possibilities are:
1) find the EDL test points inside and connect them while reseting.
2) disable data lines or clock to the flash so that it can't read anything and knows that it can only go to EDL.
3) JTAG to fix the problem or else just wipe the SBL so that it goes to EDL.
4) Use a USB UART. Maybe it's getting as far as u-boot and you can stop it and make it go to fastboot.
Click to expand...
Click to collapse
Is there any documentation of the OP8pro about the steps you mention? For example we had a discussion about edl points some days ago and the guy could not find them. And we came to the conclusion the wont help because we already have the button combo.
If the ram is overvolted and fried, which is most likely the case because anything else wont keep the phone away from EDL. Nothing can help to repair a dead ram.
I was listing 4 alternatives above.
Why do you think the RAM is dead?
EDL itself doesn't use any external RAM. There's a bit of static RAM on the chip and it uses that.