Related
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 to all.
I landed on XDA because I am not able to hack my Asus Zenfone Laser 2 dual-sim (ZE550KL, which seems to be also called as Z00L or Z00LD... I don't know why... ?!? ). Actually I'm very new on smartphone hacking, so I did my best recently to understand what "rooting", "recovery", "brick" etc mean.
I tried to enter this world because my phone gets gradually very slow as I use it and so I supposed that erasing the pre-installed applications and overclocking it would help, possibly installing a lighter and more performing custom rom. In order to do this I read that in short I have to unlock the boot loader, root the phone and then eventually install a custom rom. In fact I suppose that getting root privileges should already do the job by keeping the original rom, unistall all unwanted apps and eventually overclocking it. Is that correct?
However, the problems I found on my way are the following two:
I've not been able to follow those procedures on Linux. In detail, I'm not able to use "fastboot boot" instruction because it gets stuck on "waiting for any device". The device is listed and allowed when running "adb devices", the boot had been unlocked previously, the phone is in debug mode etc... but the problem is still there despite I've been trying with both the adb package included in the repositries and the one downloaded from the related google page. I've been told it may be a matter of USB drivers, so I also installed the android studio package thinking it would help, but I was wrong. I'm quite confused on this, despite I do hope I can hack my phone using my favourite operating system (I'm a Linux user since 2006). If you do not feel like helping on this then I will try on Windows.
After trying the same procedures on Windows 10, I realised that the Android Usb drivers released by Google did not work. I had to install the proprietary ASUS USB Drivers from the official website and only then I was able to overcome on Windows the same "waiting for any device" I had experienced on Linux. However, the phone "bricks". I suppose this should be the technical term used in this field to tell that the phone gets stuck for hours on the boot animation. I tried several times to reboot it, but each time the same story.
Maybe the problem on Linux is that I do not have the proper Android Device Usb drivers installed. In this case, how to solve the problem taking into account that ASUS only released the drivers for Windows?
RECAP: I have my phone bricked now (Android is unable to reboot, but I can do access both to the Power+VolumeUP menu (by the way, what's the name of this menu? Fast boot?) and the Power+VolumeDOWN menu (by the way, what's the name of this menu? Recovery boot?)
So sorry for the long story.
Hope you can help.
Thanks for your attention and best regards.
Uhm... no replies till now?
i dont know how you get this kind of trouble, maybe try other computer? , im using wondows 10, download small package of of fastboot driver and adb driver, flash twrp using fastboot command. all done. then i make full backup using twrp, next flash magisk .now i have root access, any problem or bootloop i just restore the full backup that work.
---------- Post added at 04:53 PM ---------- Previous post was at 04:22 PM ----------
i see a lot of this zen2 laser got bricked on this general forum , you should read some more if that could help
When I had this device, I remember booting a temporary recovery TWRP and rooted it in that recovery. Then once I got rooted, I installed TWRP app and installed a permanent recovery from within the TWRP app, which needed root of course. Then I got everything working.
You can try booting on a temporary TWRP using fastboot then flash supersu or magisk or whatever rooting client you want. Though, I think you need an unlocked bootloader. I'm sure there's a guide around here somewhere
I'm using a Z00T and just installed LineageOS yesterday using Windows 10, following a guide by Android Authority and LineageOS.
Volume Up + Power = Fastboot
Volume Down + Power = Recovery
Sounds like you can get into Fastboot, so I'm wondering if maybe you can use it to flash the recovery image??? (I'm not a dev in any form; try this at own risk)
I'm assuming you unlocked the bootloader already...
In the directory where all your images are, perhaps try flashing the recovery with the following, where RECOVERY.img is whatever you may have renamed the TWRP image to be:
Code:
fastboot flash recovery RECOVERY.img
After it's finished flashing, turn off the phone, then reboot into recovery mode with Volume Down + Power.
Something Similar happened with my phone and looking for answer
Hi All,
I'm new to this but do some hands on reading these forums. Recently i don't know how but my phone continuously boot into Fast-Boot mode. If I try to push some zip file as mentioned i'm getting error related to partition. "failed to write partition."
Can someone help me out with this.
Thank in advance.
CerealKiIIel said:
Hi to all.
I landed on XDA because I am not able to hack my Asus Zenfone Laser 2 dual-sim (ZE550KL, which seems to be also called as Z00L or Z00LD... I don't know why... ?!? ). Actually I'm very new on smartphone hacking, so I did my best recently to understand what "rooting", "recovery", "brick" etc mean.
I tried to enter this world because my phone gets gradually very slow as I use it and so I supposed that erasing the pre-installed applications and overclocking it would help, possibly installing a lighter and more performing custom rom. In order to do this I read that in short I have to unlock the boot loader, root the phone and then eventually install a custom rom. In fact I suppose that getting root privileges should already do the job by keeping the original rom, unistall all unwanted apps and eventually overclocking it. Is that correct?
However, the problems I found on my way are the following two:
I've not been able to follow those procedures on Linux. In detail, I'm not able to use "fastboot boot" instruction because it gets stuck on "waiting for any device". The device is listed and allowed when running "adb devices", the boot had been unlocked previously, the phone is in debug mode etc... but the problem is still there despite I've been trying with both the adb package included in the repositries and the one downloaded from the related google page. I've been told it may be a matter of USB drivers, so I also installed the android studio package thinking it would help, but I was wrong. I'm quite confused on this, despite I do hope I can hack my phone using my favourite operating system (I'm a Linux user since 2006). If you do not feel like helping on this then I will try on Windows.
After trying the same procedures on Windows 10, I realised that the Android Usb drivers released by Google did not work. I had to install the proprietary ASUS USB Drivers from the official website and only then I was able to overcome on Windows the same "waiting for any device" I had experienced on Linux. However, the phone "bricks". I suppose this should be the technical term used in this field to tell that the phone gets stuck for hours on the boot animation. I tried several times to reboot it, but each time the same story.
Maybe the problem on Linux is that I do not have the proper Android Device Usb drivers installed. In this case, how to solve the problem taking into account that ASUS only released the drivers for Windows?
RECAP: I have my phone bricked now (Android is unable to reboot, but I can do access both to the Power+VolumeUP menu (by the way, what's the name of this menu? Fast boot?) and the Power+VolumeDOWN menu (by the way, what's the name of this menu? Recovery boot?)
So sorry for the long story.
Hope you can help.
Thanks for your attention and best regards.
Click to expand...
Click to collapse
hey I have the same issue im on windows 10 and asus hasn't realeased drivers for asus zenfone laser connectivity so It wont show up no matter what I do, and the windows 7 drivers cant be used.
BlondebigboobsIRL said:
hey I have the same issue im on windows 10 and asus hasn't realeased drivers for asus zenfone laser connectivity so It wont show up no matter what I do, and the windows 7 drivers cant be used.
Click to expand...
Click to collapse
I'm using Z00T and Windows 10. Had no issues using the Android Authority and LineageOS guides.
These guides are great but I don't want to lose my data by formatting my bootlooping device, and the drivers asus gives do not work with windows 10, the adb drivers work fine but the asus drivers do not.
So, basically I will make this short as possible
Due to some problems I had to sell my G6 Plus (Brazilian -8 model) but it was on a custom rom, and did the most dumb thing that I could do: Reflashing pure stock and locking it, I've used the LMSA tool then relocked in Fastboot, the thing is some files were corrupt and when locked, it doesn't boot up anymore, as i still had hope for it, I tried to LSMA again, but it doesnt recognize anymore, as the lock flag is now "Flashing_Locked", flashing manually via Fastboot gives a error related to the lock flag (also LSMA resets the device, so using my unlock key asks to enable OEM Unlock at settings, a impossible thing when OS is broken) , then searched for some solutions, first it was booting a Boot.img file from the last stock, which was the flashed one, it bootloops, then tried something on the recovery that works, but is the stock one and pretty limited, so the logical thing to do is flashing a OTA file, but only works for old versions that requires one version before the target one, so its a no go. The last thing i tried to do is booting TWRP, but it gets stuck on a red warning that indicates that system is corrupt. Then the last hope was EDL Mode, and thats the point where i want to go, i've bought a EDL Cable that's basically a green and black wire thing used on most Qualcomm based Redmi/Xiaomi devices, but it automatically boots to fastboot, so I need help to get EDL Test Points for this device, im with access to the board, i just need the right Pads to short-circuit it and blankflash it, so i can finally get it to work like normal again.
Schematics (for people who understands): https://androidfilehost.com/?fid=4349826312261726244
Any help is important, I'm sorry for some typos, english isnt my main language considering i didnt use translate
and please don't come with instructions like "have you tried LSMA?, try booting up the device and select oem unlock" because its clear that it doesnt work.
The official way to unlock the bootloader has been unavailable for just over a year, since LG ended their developer program as of 01/01/2022 and you now can't apply for an unlock file anymore.
Searching for a work-around I found this: https://drfone.wondershare.com/unlock/lg-bootloader-unlock-how-to.html
I have tried as best I can to follow these instructions and fail because I can't get my device to enter Qualcomm EDL 9008 mode by any keypress combination, or ADB or fastboot command from OS (Windows and Linux tested). I suspect my edition of the phone doesn't have EDL, or the method of accessing it is not correct in all instructions I've seen. I can get in to fastboot, and LG download mode (which shows in device manager as LGE AndroidNet USB Serial Port), but not Qualcomm ADL 9008 mode which should show in device manager as Qualcomm HS-USB QDLoader 9008.
I'd rather not brick my device, but it is a spare, and I thought I'd try and soup it up with a newer AOSP-Extended before maybe gifting to my partner.
AND!! I'm suspicious of the instructions in the first place! At the bottom, it advertises a piece of software to something related. As a Windows technician in my day job, I see this too often, can't solve bluescreen error 0x123abc45 just download this trialware to fix your PC!!
Try "adb reboot edl" from adb, anyway yes that site is not good
Hey, thanks for coming back to me.
I have tried that, but have just repeated right now to remind myself the outcome, which is, phone reboots as normal. Does not enter EDL mode. Windows and Linux.
Cheers
Anne-d'Royd said:
I suspect my edition of the phone doesn't have EDL, or the method of accessing it is not correct in all instructions I've seen
Click to expand...
Click to collapse
Isn't the method to access EDL on the G6 through shorting two pins on the mobo?
LG G6 TestPoints for EDL Mode (9008)
Simple af. Just short them. For incase that doesn't work;
forum.xda-developers.com
Also, that guide is just a re-worded one for the LG G7 One, not the G6, which use different processors. An engineering bootloader for the LG G6 has not leaked yet, and likely will not leak since it's been 6 years.
LG G7 One Bootloader Unlock [How-to]
Disclaimer: Do this at your own risk, blah blah blah. Brick your phone its on you.. Just a quick tutorial on bootloader unlocking the G7 One. Lots of the info in here can be found in other areas of XDA. *****Read full post before...
forum.xda-developers.com
Hey thanks for the input!
I'm reluctant to go in since the glass is splintered on the back of the unit, that's the main reason I changed my phone nearly 2 years ago.
There are enough varying instructions of there to suggest that EDL on that phone can be accessed by I think five methods.Two methods involve commands from PC, one method is button press combinations whilst connected to PC, another is a special EDL cable and then lastly, the test points.
The guides I've seen explaining the keypress routine says it works for a range of LG phones with qualcomm chips, including the G6 but I have they're wrong. Example:
Dont bother with dr phone. I previously used it to backup my phone. It wanted me to pay to restore but all it did was create a zip of my internal storage.
I think it is highly unlikely that they have a secret way of unlocking one of the hardest to unlock bootloaders on a phone.
After trying to flash TWRP (by following this guide: https://www.thecustomdroid.com/root-oneplus-6t-guide/ ) my device would no longer boot to the OS,but (stock) recovery and fastboot modes worked, so I tried to fix it by flashing some Android 9 roms from https://forum.xda-developers.com/t/...t-stock-fastboot-roms-for-oneplus-6t.3862516/ , and flashing a stock Android 10 boot.img (for some reason).
But my attemps at fixing it by flashing only made things worse, my current situation is as follows:
Device: Oneplus 6T (6/128)
Version (either Global or T-Mobile): Unsure
OxygenOS Version: Unsure, only know that it is Android 9
Bootloader: Unlocked
- Neither Recovery mode nor TWRP work
- Bootloader and Baseband versions show as empty
- I can only access Fastboot mode and EDL mode
- A power outage left my main pc (which had the drivers, permissions and backup i had been using, and need, to do this) a burning mess
- I´m currently using an old desktop computer i had stored (which has Windows 7), but it fails to recognize my device.
- I have installed and tried multiple versions of the Qualcomm, Oneplus, Adb and Android drivers, but it never recognizes it
- Windows doesnt allow me to manually select the drivers for the Unknown device as ¨the specified folder doesnt contain a software driver compatible with this device¨
- By searching the system and internet it always says that ¨the best software driver for this device is already installed¨
- Both of the above were tried with a disabled driver signature requirement
- When using it on the other PC, the msm download tool, it always said that the image didnt match the device, no matter which of the 13 versions I tried
- On my current PC, the msm download tool doesnt detect my device
I implore anyone that can provide any help or advise to do so, as I´ve already spent an entire week scouring the Internet (including the Oneplus and XDA forums) for any solution, but so far, nothing has worked. Have a good day and thank you for reading my post.