Related
In order to flash a custom recovery we need to find out IF there is a apx mode for the A500 and HOW to get into this mode.
apx mode would furthermore help to restore our tablets if things are borked.
EDIT: This describes how to get there: http://forum.xda-developers.com/showpost.php?p=13629976&postcount=155
the thing with apx mode is that on some tablets its needed to hold both volume buttons to get to apx mode and on a500 acer made this physically impossible, could be locked behind this issue...
the question is if it may be forced in another force like an adb reboot command.
samsung devices have adb reboot download as command for the odin interface.
BUMP: http://forum.xda-developers.com/showpost.php?p=13629976&postcount=155
APX Mode seems to be found
When he says "the right driver" he means the same one I use to adb shell into the device? Or a different one? I can't remember how it was with my gtablet.
Am I stuck in APX mode with no USB connectivity and how do I get out of this? Here is what happened:
A500 with OTA Android Build: Acer_AV041_A500_1.033.00_PA_CUS1
Windows 7x64 with UAC turned off and restarted OS
- Launch Afterota v1.09
- Info tab > Install Driver ... "ACER ICONIA 3G DRIVER INSTALL"
- Boot A500 > ENABLE USB debugging
- Plug USB cable into A500 ... "Acer Iconia Tab A500 ... Your device is ready to use"
- Tablet Information ...
Tablet Serial : 11933073415
Tablet Cpuid : 028841854280E4D7
Tablet Sbk : 0x15290000 0x7FC6C006 0x47E52404 0x302C2103
Android Build : Acer_AV041_A500_1.033.00_PA_CUS1
Bootloader : 0.03.12-ICS
- Save Values to AcerIDs.txt
- Standard tab > Bootloader Ics v3.14.8 + Recovery Thor v1.7.3 > For A50X
- Install sys rw patched kernel (sys rw patch only, no overclocking)?
- Yes > OK
- A500 boots to APX Mode
- Afterota status ... flashing (about 1 minute) ... idle (no further activity ... ever)
A500 screen is BLACK, Power LED is ON, all the Afterota buttons are grayed out except for Unsoftbrick Browse.
Driver: OK - driver installed
Usb: ERROR - connect usb cable and enable usb debugging
I've tried reinstalling the USB driver multiple times and using different USB ports with no luck. I can turn A500 on and off by holding down the Power LED button for 3 seconds, but still a black screen.
Any ideas will be appreciated
May have a possible Fix for you
EDIT: OK May have a possible Fix for you I've just run this myself from apxmode and it worked for me...give it a whirl and see how you go!!!
check this thread here
##############################################################
the 'mode' yr tab is in now - black screen with power lite....
i'm sure its waiting for the apx driver to load this will enable yr tab to enter the next stage where the flash takes place..(this stage is called different things depending on which tool u use...which doesn't help matters at all...) you will know when u enter "the next stage" because yr tab will display some white text "a500 apx mode" or "acer download mode" even "a500 bootloader mode" they're all the same -
so if u do not have the white text displayed the only conclusion one can come to is that the required driver cannot be found....(if I'm wrong on this then please put your 2cents worth in and maybe we can get this problem solved once and for all)
you need to have the "acer usb-boot recovery driver" displayed in your system tray under safely remove h/w or in device manager. Is it there....?
Device manager is yr friend always have it open when trying to troubleshoot flash issues.
connect yr tab to yr pc with yr mini usb data cable - the flash will definietly not happen if you're using a regular sized usb cab le!!!!
is the driver listed under usb controllers?
is there an "APX Device" listed?
if not disconnect and power yr tab off
then enter apx mode manually and reconnect cable and see if the boot-recovery driver installs itself - if it doesn't then reinstall the acer drivers....again!
also if it hangs on the black screen again
always disconnect yr usb cable close the program down and try again.
your other choice is to use civs nvFlash cos it requires yr tab to be in apx mode first - if it fails it will show you an error which will help
There seems to be alot of ppl of late getting stuck in this mode...and there seems to be no real solution to it.....sometimes you just have to keep at it until it works... if all else fails then u may need to downgrade back to HC and try from there!!!
Please let us know how u get on....
cheers
EDIT you need the android drivers too - theres a zip file in my cpuid thread if u need them
I've tried your suggestions, only using AfterOTA so far ... still no success.
These are the steps I've been following:
1) Disable UAC > Restart
2) Run Afterota.exe
3) AfterOTA (Info tab): Install Driver
4) Power on A500 (screen is still black, Power LED is white) ... plug in micro-USB cable from PC ... "driver successfully installed"
5) AfterOTA (Advanced tab): Unsoftbrick ... browse to ... recovery_thor17_403.img
6) AfterOTA (Advanced tab): Unsoftbrick ... browse to ... ics_boot_unlk_V6_500.bin
7) AfterOTA (Advanced tab): Unsoftbrick ... Install
[1/3]loading apx mode bootloader
[2/3]flashing recovery ..
This is where it gets stuck. No vibrating, the screen remains black (no text), nothing even after 5 minutes. I've repeated steps 5-7 trying two different USB cables plugged into the A500 micro-USB (small) port and also connected to different USB ports on my PC. Each time I shut down AfterOTA, unplugged the USB cable, powered off A500 ... then try again. I've also tried uninstalling and reinstalling the USB driver using AfterOTA.
Every time A500 is powered on and connected to USB ...
- "Acer USB Boot-recovery driver" is listed in Device Manager, USB controllers
- "APX" is listed as an Unspecified device in Devices and Printers (not in Device Manager)
- "Usb: ERROR - connect usb cable and enable usb debugging" listed in AfterOTA (Info tab)
It appears AfterOTA can't establish communication over the USB connection.
The very first time I used AfterOTA, A500 was still able to boot to ICS, the USB connection was OK and I was able to retrieve the Acer IDs and save them to a txt file. It was only after flashing "Bootloader Ics v3.14.8 + Recovery Thor v1.7.3" that I got the "Black" screen. It appeared the flashing was successful, as it had completed step [5/5] and then showed status "idle .."
I guess first priority is to find a something (maybe other than AfterOTA) to see if it can communicate with A500. Haven't tried civs nvFlash ... yet.
Thanks for your help.
FCBelser said:
Every time A500 is powered on and connected to USB ...
- "Acer USB Boot-recovery driver" is listed in Device Manager, USB controllers
- "APX" is listed as an Unspecified device in Devices and Printers (not in Device Manager)
Click to expand...
Click to collapse
ok, this is weird:
you are saying device manager reports the boot-recovery driver installed
But there is also an unspecified APX device????
Are u using win7/64 by any chance as there have been some issues reported by those users - are u able to try another pc??
Try manually installing the driver the apx device, by pointing it to the acer folder in program data
what happens there??
- "Usb: ERROR - connect usb cable and enable usb debugging" listed in AfterOTA (Info tab)
It appears AfterOTA can't establish communication over the USB connection.
Click to expand...
Click to collapse
- while yr tab is in apx mode you will have no access to adb or usb b/c apx is using the USB connection -
I guess first priority is to find a something (maybe other than AfterOTA) to see if it can communicate with A500
Click to expand...
Click to collapse
Yeh I wish it were that easy - I've been working on this for a whole week now, as lately there have been a number of "stuck in apx mode" reports - altho yours is the first of it happening using afterOTA - there just doesnt seem to be an easy way out of it,,,its happened twice previously on my tab - i got it working but i cant tell you how....i just kept trying over and over till it worked!!!
If you do give nvFlash a try - edit the .bat file and delete the "cls" commands this will give you a chance to 'see' whats going on...
another tip: after entering your sbk make sure the "system information" window pops up - it will show amongst other things your "chip uid" this is yr cpuid - if you carry on without yr tab being in "bootloader mode" you can end up with a really, truly 'brick' on yr hands - see the walkthru in my sig if you need further guidance
[1/3]loading apx mode bootloader
[2/3]flashing recovery ..
Click to expand...
Click to collapse
once it completes "loading apx mode bootloader" this is when yr tab should vibrate and display the white text "acer a500 apx mode" which is what
leads me to believe that for some reason its waiting for the driver even when it seems to be installed already.....this is where i think the problem lay.
The only other tool that may work is timmydeans v4 it uses apx mode as well but will roll u back to HC, it also repartitions and 'resets' your tabs file system as alot of tabs have got stuck on "formatting partitions" with the flash...hopefully this won't happen to yours but you'll find out after running nvFlash tool...
apxFlash has never been able to pick up the fact my tab is in apx mode, it, like afterOTA relies on adb to gather the required tab info, and of course if it doesnt recognise your tab it doesnt know its connecteD!!! At least afterota recognises this by the fact the "unbrick" menus are not greyed out...
The only other thing i might suggest is putting yr tab in apx mode manually -
Turn tab off
use a paper clip to push and hold the reset button
then press and hold the power button UNTIL the power Lite comes on
count 3 secs and release
then after another second release the reset button
might seem strange thing to try, but you never know it may just 'jog' something into life
Yes ... I'm using Win7 64-bit.
When I plug the USB cable into the A500 ...
1) Acer USB Boot-recovery driver shows up in Device Manager ... listed under USB controllers
2) An APX icon shows up in Devices and Printers (not in Device Manager) ... it's listed under a category call "Unspecified"
When I unplug the USB cable, both 1) and 2) go away.
For manual driver install ... are you referring to:
C:\Program Files (x86)\Acer Inc\ACER ICONIA TAB3G\Win7\ADB\x64\android_usb.inf
-or-
C:\Program Files (x86)\Acer Inc\ACER ICONIA TAB3G\Win7\USB_ethernet_rndis\x64\acer_usb_ethernet_rndis.inf
-or- something else?
I have an older laptop running Win7 32-bit, so I'll also try that too.
FCBelser said:
Yes ... I'm using Win7 64-bit.
When I plug the USB cable into the A500 ...
1) Acer USB Boot-recovery driver shows up in Device Manager ... listed under USB controllers
2) An APX icon shows up in Devices and Printers (not in Device Manager) ... it's listed under a category call "Unspecified"
When I unplug the USB cable, both 1) and 2) go away.
For manual driver install ... are you referring to:
C:\Program Files (x86)\Acer Inc\ACER ICONIA TAB3G\Win7\ADB\x64\android_usb.inf
-or-
C:\Program Files (x86)\Acer Inc\ACER ICONIA TAB3G\Win7\USB_ethernet_rndis\x64\acer_usb_ethernet_rndis.inf
-or- something else?
I have an older laptop running Win7 32-bit, so I'll also try that too.
Click to expand...
Click to collapse
something else, lol hold on....i'll just go check
I tried the paper clip / power button trick ... and then back to AfterOTA on Win7x64 ... no luck. I also tried AfterOTA on my laptop (Win7 32-bit) ... exact same problem.
ok this is where things get even weirder...and from memory it was a real pain to get this apx device installed....windows kept wanting an inf file but i'm positive that in the end i got it to install from a folder - i just cant remember how????
I cancelled the hardware wizard from doing its thing
then in the next window there are 2 options
let windows choose or let me choose - something like that
i kept trying let me choose and got nowhere
then i think i tried "search my computer" and chose the C drive - i'm sure it found the right ones that way
and i think i uninstalled all acer and android drivers, rebooted and reinstalled them before i could get any joy....i know it took a good 5-6 hours of mucking about - until finally something worked...
and yes def give 32 bit a go before we get too carried away!!!
oh no... i think i've jsut got stuck in apx mode...
---------- Post added at 08:41 AM ---------- Previous post was at 08:17 AM ----------
FCBelser said:
I tried the paper clip / power button trick ... and then back to AfterOTA on Win7x64 ... no luck. I also tried AfterOTA on my laptop (Win7 32-bit) ... exact same problem.
Click to expand...
Click to collapse
then the only other thing to do is a rollback using timmydeansv4. run the tool without yr cable connected and wait for the instructions to put yr tab into manual apx mode - you wont have to worry bout that seeing as you're in it already!!! connect yr cable and click OK - enter cpuid and wait 10mins for it to do its thing...it won't take any longer than this -
let us know how you go!! and good luck m8
Where can I find timmydeansv4? Google search isn't finding it.
Thanks
FCBelser said:
I tried the paper clip / power button trick ... and then back to AfterOTA on Win7x64 ... no luck. I also tried AfterOTA on my laptop (Win7 32-bit) ... exact same problem.
Click to expand...
Click to collapse
i renamed the Acer Folder in Program Files
I then put my tab in manual apx
when the driver went to install
i cancelled "skip searching windows update"
in usb controllers an acer picasso boot recovery is listed
AND in Printers and Hardware the APX device is there - i didnt do anything with it at all
I fired up afterOTA but it couldnt see my tab
So I used civs V8 nvflash pckg
tab went into the proper apx mode with the txt displayed
it flashed and now running v8 and cwm 1.7.3
I did this via HC 3.1 win7 32
That worked !!!
I followed your The Chickens Guide to Flashing the bootloader manually after installing the USB driver from the Acer support website. Now I'm back to ICS without having lost any of my data or settings.
A couple of noob questions:
1) Would an ota update from Acer wipe out the newly installed V8 bootloader & Thor 1.7.3 recovery?
2) What's the most reliable way to root ICS?
Thanks so much for your patience with my problem!
FCBelser said:
That worked !!!
I followed your The Chickens Guide to Flashing the bootloader manually after installing the USB driver from the Acer support website. Now I'm back to ICS without having lost any of my data or settings.
A couple of noob questions:
1) Would an ota update from Acer wipe out the newly installed V8 bootloader & Thor 1.7.3 recovery?
2) What's the most reliable way to root ICS?
Thanks so much for your patience with my problem!
Click to expand...
Click to collapse
Oh m8 thats made my day:laugh::laugh::laugh::laugh: rapt for u!!!
So u think it was the drivers??
1) don't know, we haven't recd an ota to find out - but in my experience nothing wipes unless u do! An EUU may do it or an official updaate.zip.
2) icsroot by blackthund3r google it
3) if u install a custom rom you will need to do a full wipe and format via cwm b4 and after flashing this includes Jr internal storage else all sorts of glitches happen.
Your welcome., as I said its been a problem with no real solution, awesome to know it that in the end it finally worked
I'm not sure it is the drivers. I installed Acer USB Driver v1.00.0524 (2011-10-06) from the Acer website. It appears to be the same version installed by AfterOTA. Maybe it's something else in AfterOTA that just gets hung up on a combination of hardware and software that wasn't anticipated? I'm sure gersma couldn't anticipate or check out every combination.
I'll try ICS Root.
Thanks again for all the help.
FCBelser said:
Where can I find timmydeansv4? Google search isn't finding it.
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1307539
i have exactly the same problem, issue is that wen ur in APX mode and win7 has detected ur acer recovery driver and when u start your process of ICS rooting OR apxflashing or bootloading whatever the USB driver disconnects and that's the reason why nothing works and its stuck in partiton format or what ever process your in btwn and when you once again in a hurry power off the device and power u the acer recovery driver, its back there but still its stuck nothing goes on... Also even when acer recovery driver is there and you enter any mode then it says device not connected or found...please help
rondlu said:
i have exactly the same problem, issue is that wen ur in APX mode and win7 has detected ur acer recovery driver and when u start your process of ICS rooting OR apxflashing or bootloading whatever the USB driver disconnects and that's the reason why nothing works and its stuck in partiton format or what ever process your in btwn and when you once again in a hurry power off the device and power u the acer recovery driver, its back there but still its stuck nothing goes on... Also even when acer recovery driver is there and you enter any mode then it says device not connected or found...please help
Click to expand...
Click to collapse
If the usb connection is disconnecting here's a few things you can check.
Both sets of drivers are installed. The Acer ones and the android ones.
Try a different usb cable.
Win 64 bit has issues try xp, ,vista or win 7 machine.
If still no joy try civs manual flash or Ubuntu.
Sounds like a driver issue so check those first.
Dibb
Sent from my GT-I9300 using Tapatalk 4 Beta
Thanks so much for the reply the drive i have is Acer USB boot recovery drive and before that Picasso was visible .. there is just one driver how can i get two drives here? i have read many forum and the links they gaved is Just one two drivers, one was Picasso and the other was simple that i mentioned at first but the Device Manager just shows one (Acer USB boot recovery drive)
Three cables are changed but all it happens that it stuck at partition fomating or flashing recovery
Also like to mention that i Used AFTEROTA which shows the status under
Driver - OK - driver installed
USB - ERROR connect usb cable and enable usb debugging
(how can usb debugging be enabled when tablet is totally dead)
In the cpuid guide in my sig there's a download for adb/fast boot drivers. You must have these installed.
Was yr tab running ok before all this?
Sent from my GT-I9300 using Tapatalk 4 Beta
Sorry but i m new to this android and this forum ,i have followed ur link and im confused that which version (honeycomb or ICs was my tab) yes everything was working fine and suddenly the OS and apps started to held and behave abnormal so then i had to turn it off and after that all this happened
I have followed ur link and this is what i see
DRIVERS
Acer Support for Acer APX/Fastboot/Recovery Drivers
Android SDK for the adb/USB drivers - You can d/l a mini zip containing just the adb and fastboot drivers attached to this post "adb_fast.zip"
i went to ace support and download the honeycomb first version but the adb_fast.zip doesn't have any driver its a program... Kindly suggest where is the other driver
Sir Kindly reply i am waiting for your suggestion.:crying:
I'm trying to debrick A500 with a WinXP PC.
It can be detected by the PC as "MTD device". Installed the Acer driver for it (not sure what it does).
It can enter the APX mode, detected by the PC correctly, and installed the APX driver "Universal_Naked_Driver_0.72".
But, adb devices does not detect it, so cannot move further to PBJ20upgrade.exe and so on.
What does this mean? Bricked beyond repair?
- dd
ddbug said:
I'm trying to debrick A500 with a WinXP PC.
It can be detected by the PC as "MTD device". Installed the Acer driver for it (not sure what it does).
Click to expand...
Click to collapse
I'm assuming that you mean MTP (Media Transfer Protocol)?
I'm assuming this means that you are booting Android as I'm not aware of the device being represented as anything but an APX device (0955:7820) if you do not.
What is the problem?
ddbug said:
It can enter the APX mode, detected by the PC correctly, and installed the APX driver "Universal_Naked_Driver_0.72".
But, adb devices does not detect it, so cannot move further to PBJ20upgrade.exe and so on.
Click to expand...
Click to collapse
When in APX mode Android is not loaded so you cannot use ADB (Android Debug Bridge). It should not really matter as, from what I recall, PBJ20upgrade will only use ADB to reboot the device into AXP mode.
Thank you eppeP,
Yes, it was MTP.
So I'll try to proceed with PBJ20upgrade.
(am away now for a week or so ... )
-- dd
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
daevion0 said:
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
Click to expand...
Click to collapse
I assume you're not on Windows 10 x64? If you aren't, either get a PC with Win10 x64, or do this:
Connect the phone, get into EDL mode. Now go to the Device Manager, and tell me where it appears.
It can appear as:
-"Qualcomm HS-USB QDLoader 9008" under Ports (COM & LPT);
-"ZTE DFU Interface, under Ports too; or
-"QUSB_BULK" under Universal Serial Bus devices or unknown devices.
If it appears as the DFU stuff, you'll have to follow the 4th category brick repair guide. If it appears as QDLoader, right click on it, then Properties, then go to Bits per second and put the number at 115200 or 128000 if it's not there. Then hold the 3 buttons (vol and power) until Windows beeps and the device manager spazzes and the phone flashes the red led, then try MiFlash again.
If it appears as QUSB_BULK, uninstall the driver (tick delete driver software too) and restart edl.
Choose an username... said:
I assume you're not on Windows 10 x64? If you aren't, either get a PC with Win10 x64, or do this:
Connect the phone, get into EDL mode. Now go to the Device Manager, and tell me where it appears.
It can appear as:
-"Qualcomm HS-USB QDLoader 9008" under Ports (COM & LPT);
-"ZTE DFU Interface, under Ports too; or
-"QUSB_BULK" under Universal Serial Bus devices or unknown devices.
If it appears as the DFU stuff, you'll have to follow the 4th category brick repair guide. If it appears as QDLoader, right click on it, then Properties, then go to Bits per second and put the number at 115200 or 128000 if it's not there. Then hold the 3 buttons (vol and power) until Windows beeps and the device manager spazzes and the phone flashes the red led, then try MiFlash again.
If it appears as QUSB_BULK, uninstall the driver (tick delete driver software too) and restart edl.
Click to expand...
Click to collapse
I'm on win10 64bit
daevion0 said:
I'm on win10 64bit
Click to expand...
Click to collapse
Then do everything I described above or just try another PC. It always happens that one PC can be decided not to let you unbrick your phone for some reason
Choose an username... said:
Then do everything I described above or just try another PC. It always happens that one PC can be decided not to let you unbrick your phone for some reason
Click to expand...
Click to collapse
Is there no other option? is there no other way to at least get fast boot mode back on my phone?
daevion0 said:
Is there no other option? is there no other way to at least get fast boot mode back on my phone?
Click to expand...
Click to collapse
Lol nope, not if EDL is not working for you. You still didn't tell me whether you have a DFU brick or not. If you do have a DFU brick the only surefire way is to disassemble your phone and short a testpad, so don't complain.
Try what I told you above. It may be that it's set at 9600 baud
daevion0 said:
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
Click to expand...
Click to collapse
1. You must use "Qualcomm HS-USB QDLoader 9008" driver (there is another one call zidag but it's not work here)
2. As soos as you enter EDL mode, you must press "Flash" as quick as possible
i'm in a similar situation... i did "fastboot oem lock" and now i'm in a loop trying to boot the phone, after the 3time it enters edl (i see the red light).
My model is de G model (2017G) can i use miFlash just to restore the recovery and fastboot?
i had installed lineageOS, when connecting my phone it says that is the U model (2017U) but i think is only a label tag from the rom...
Thansks for the help!!
A 64 bit computer is not really necessary, however it is adviced.
I used a 32bit laptop running Win 10 to rescue mine.
Drivers seem to be a major problem, having the correct up to date drivers is a must.
Also try using Edl Tool and the Axon7 tool kit to access flashing.
Zadig drivers can help in some instances.
With the error you are receiving, have you tried another Edl package?
I was using an Edl package that would not finish flashing either, try a different package and make sure its correct for your phone.
I hope you get it sorted
The hello read package does occur when the phone is not really EDL mode anymore. You always have to restart the phone and boot manually into EDL mode with + - Power and you have to reboot everytime you did or if the hello error happens.
Look under device manager if it says Qualcomm instead of ZTE Device Handset. If that is the case you can build your own EDL cable.
"First I opened the cable and cut the Black and green open, then I connected all the black and green one together and pressed the power button until the red led was gone and 2 additional seconds.
After that I disconnected the modded cable and connected the Phone to the PC with the orginal cable and it showed up as Qualcomm HS-USB QDLoader 9008. "
You can install the qualcomm drivers under the MiFlash tab in the latest version.
i finally solve my issue following the guide: https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898 there is also a resume on https://forum.xda-developers.com/axon-7/how-to/guide-dfu-unbrick-guide-disassembly-t3731152
My Axon 7 is the A2017U, i had the B32 Nougat running on it and wanted to try the new lineageos 15.1, but had to unlock my bootloader first i used the toolkit like I've done in the past and was able to unlock it and flash twrp, when i try to boot it back on it goes to factory testing mode, i was able to get into twrp and i wiped everything and it stopped the problem of booting directly to FTM but after that i tried to go into EDL mode and it seemed to try to enter the mode but the red led indicator light stays on rather than doing a quick blink. its no longer picked up as a COM port, when i enter fastboot mode adb doesn't seem to work and I'm unsure what to do or if I'm out of luck. Thank you for your time and the advice and help you guys are able to provide.
use ADB
Enable ADB in developer options
use command "adb reboot edl"
Used Twrp to flash Custom ROM, EDL still not fixed
sauerkraut17 said:
use ADB
Enable ADB in developer options
use command "adb reboot edl"
Click to expand...
Click to collapse
I had no OS installed, only twrp recovery and I was able to unlock my boot loader. I tried to flash Lineage-OS ROM in twrp and didn't have much luck because i would get an error code saying it wasn't compatible with my phone and had to go into the ROM files and edit the updater-script file to remove the compatibility check.
In the end I have a working phone with a custom ROM but EDL mode is still not responsive and seems to freeze my phone as soon as I press the 3 buttons to get into EDL. the notification light blink remains on so ill take it as an indicator that something is wrong with the firmware that it uses. i still want to fix it so EDL can be used but unsure how to fix it. I did some researching and was wondering if using a deep flash Engineering cable would work to fix the EDL mode and any other problems that could be there.
levittc5280 said:
I had no OS installed, only twrp recovery and I was able to unlock my boot loader. I tried to flash Lineage-OS ROM in twrp and didn't have much luck because i would get an error code saying it wasn't compatible with my phone and had to go into the ROM files and edit the updater-script file to remove the compatibility check.
In the end I have a working phone with a custom ROM but EDL mode is still not responsive and seems to freeze my phone as soon as I press the 3 buttons to get into EDL. the notification light blink remains on so ill take it as an indicator that something is wrong with the firmware that it uses. i still want to fix it so EDL can be used but unsure how to fix it. I did some researching and was wondering if using a deep flash Engineering cable would work to fix the EDL mode and any other problems that could be there.
Click to expand...
Click to collapse
EDL using the volume/power button has issues with the newer bootstack (which it sounds like you're on). However, since you have an OS now do as I recommended. It will 'reset' the EDL and once done via ADB command it will work with the volume/power buttons like it did before moving forward.
sauerkraut17 said:
EDL using the volume/power button has issues with the newer bootstack (which it sounds like you're on). However, since you have an OS now do as I recommended. It will 'reset' the EDL and once done via ADB command it will work with the volume/power buttons like it did before moving forward.
Click to expand...
Click to collapse
Using the ADB command i was able to get into EDL mode and it was able to get a COM port. using the volume + power buttons had the same problem. Would using an older bootstack fix it?
levittc5280 said:
Using the ADB command i was able to get into EDL mode and it was able to get a COM port. using the volume + power buttons had the same problem. Would using an older bootstack fix it?
Click to expand...
Click to collapse
Have the same issue as you do after installing the bootstack. but even with the adb reboot edl command my phone just restarts normally.. But my OS is working fine, is there any way?
Try to use volume up and volume down only and plugging in USB cable........
stinka318 said:
Try to use volume up and volume down only and plugging in USB cable........
Click to expand...
Click to collapse
Tried everything already. Can only get to DFU mode..
So, I have a similar problem: after flashing a new version of TWRP, now Recovery doesn't start. The problem is that I haven't any OS installed and the last chance to save the phone should be reflash stock by EDL... BUT EDL mode doesn't start if I press vol UP + vol DOWN during power on... (it became black with a red light, but if I digit "ADB devices" on ADB, no devices seems connected, and in the same way it's impossible to use Axon7Toolkit). So: no Recovery, no EDL mode, no OS installed, my phone is a paperweight.
Is there a method to save my Axon 7?
Here is something to try ...
Enter edl via button combo (volup + voldn + pwr)
You should have a black screen ...
Now plug your phone into the cable on your PC/laptop ..
If your PC / laptop doesn't recognise your phone via Miflash or app you are using ...
Try tapping the power button once ...this seems to open/close the port ...
I noticed this when I was using edl mode to flash a ROM
I hope this helps
levittc5280 said:
My Axon 7 is the A2017U, i had the B32 Nougat running on it and wanted to try the new lineageos 15.1, but had to unlock my bootloader first i used the toolkit like I've done in the past and was able to unlock it and flash twrp, when i try to boot it back on it goes to factory testing mode, i was able to get into twrp and i wiped everything and it stopped the problem of booting directly to FTM but after that i tried to go into EDL mode and it seemed to try to enter the mode but the red led indicator light stays on rather than doing a quick blink. its no longer picked up as a COM port, when i enter fastboot mode adb doesn't seem to work and I'm unsure what to do or if I'm out of luck. Thank you for your time and the advice and help you guys are able to provide.
Click to expand...
Click to collapse
I had the same problem a few days ago. When I booted to EDL Mode the red led was instantly on but the PC recognized it somthing like ZTE Handset Device Mode.
1. You can download TWRP Treble by NFound and flash it via your TWRP. Then reboot to recovery again and under the reboot tab its possible to boot to EDL/9008 Mode.
2. You build a EDL Cable to get the device from the red light to EDL mode. Just open some usb cable and connect the green and black (all four) together, plug it in the device and press the power button
until the red light is gone and hold on two additional seconds. Then remove the cable and plug another working cable in and the PC recognize it as Qualcomm in EDL mode.
This is literally how I unbricked my device.
Syberclone said:
Here is something to try ...
Enter edl via button combo (volup + voldn + pwr)
You should have a black screen ...
Now plug your phone into the cable on your PC/laptop ..
If your PC / laptop doesn't recognise your phone via Miflash or app you are using ...
Try tapping the power button once ...this seems to open/close the port ...
I noticed this when I was using edl mode to flash a ROM
I hope this helps
Click to expand...
Click to collapse
Thanks, I tried but this doesn't solve my problem. The strange thing is that connecting my phone in EDL mode, the phone appears in device manager as COM port, but is not seen launching an "ADB devices" command and is not seen in MiFlash too. I tried to change drivers from "ZTE device (something)..." to "Qualcomm HS-USB QDLoader 9008" and in this way, although ADB doesn't detect nothing yet, MiFlash detects a COM port, but flashing an EDL image still fails with a "cannot receive hello packet" error.
Now I ordered a deep flash cable, hope this can solve... next week I'll know if it works.
Thanks, I tried but this doesn't solve my problem. The strange thing is that connecting my phone in EDL mode, the phone appears in device manager as COM port, but is not seen launching an "ADB devices" command and is not seen in MiFlash too. I tried to change drivers from "ZTE device (something)..." to "Qualcomm HS-USB QDLoader 9008" and in this way, although ADB doesn't detect nothing yet, MiFlash detects a COM port, but flashing an EDL image still fails with a "cannot receive hello packet" error.
Now I ordered a deep flash cable, hope this can solve... next week I'll know if it works.
Click to expand...
Click to collapse
Did you resolve problem?
spasacamen said:
Thanks, I tried but this doesn't solve my problem. The strange thing is that connecting my phone in EDL mode, the phone appears in device manager as COM port, but is not seen launching an "ADB devices" command and is not seen in MiFlash too. I tried to change drivers from "ZTE device (something)..." to "Qualcomm HS-USB QDLoader 9008" and in this way, although ADB doesn't detect nothing yet, MiFlash detects a COM port, but flashing an EDL image still fails with a "cannot receive hello packet" error.
Now I ordered a deep flash cable, hope this can solve... next week I'll know if it works.
Click to expand...
Click to collapse
No need to order that cable... If you still can cancel it i'd tell you to do that. You made a mistake by changing the drivers, you had the "ZTE Handset Diagnostic Interface (DFU)" driver, and replaced it with the EDL driver.
This of course does not work because your phone is in DFU MODE instead of EDL. What you have to do is uninstall the device via device manager and also tick "Uninstall driver software for this device", then turn the phone off and enter DFU again, and then use MultiDL from this forum to enter EDL. After that, use MiFlash or EDL Tool, and try flashing a FULL EDL file
By the way ADB will only work on FTM mode or the recovery or on a working system. You won't get ADB on edl mode or dfu mode because they simply don't have adb working, it's normal
i never use xda but this quote thing is what i have aswell
levittc5280 said:
Using the ADB command i was able to get into EDL mode and it was able to get a COM port. using the volume + power buttons had the same problem. Would using an older bootstack fix it?
Click to expand...
Click to collapse
all i see is the red light in edl, whatever i try it Always just goes to a red light and a black screen. this happened after trying to unlock the bootloader. i was in android 8 and tried to lock it, it messed it up as my Phone could not boot anymore, i flashed the stock android 6.0 or something that came with the axon 7 toolkit and it did work but when trying to unlock the bootloader as the device state suddenly was locked it broke the whole thing and i oped edl could save me but even that is broken just like what the person in the quote has
Well the only fix to get EDL mode is through test point, there's a thread of unbricking Axon 7 using test point, find it, you'll need to open your back cover to do this
This in case nothing works to get into EDL mode.