I'm unable to find any guides on how to root this device with A64 SoC. The guide here only works with intel cpu. I've heard fast boot is disabled for this version which is quite unfortunate...
Is there maybe a pin somewhere on the PCB to short to access fastboot or MASKROM?
Model is NX16A8116KPB
shaun279 said:
I'm unable to find any guides on how to root this device with A64 SoC. The guide here only works with intel cpu. I've heard fast boot is disabled for this version which is quite unfortunate...
Is there maybe a pin somewhere on the PCB to short to access fastboot or MASKROM?
Model is NX16A8116KPB
Click to expand...
Click to collapse
I have the A64 version, to enter fastboot mode long press vol+ and power until logo then release power and wait for recovery mode, next select reboot bootloader and tablet was in fastboot mode. I need 7.1.1 firmware for this tablet, any help will be appreciate...
Best Regards.
Renmy said:
I have the A64 version, to enter fastboot mode long press vol+ and power until logo then release power and wait for recovery mode, next select reboot bootloader and tablet was in fastboot mode. I need 7.1.1 firmware for this tablet, any help will be appreciate...
Best Regards.
Click to expand...
Click to collapse
I tried to find firmware for this tablet for days, absolutely nothing. Not even in nextbook site resources, it's non-existent. Since my tablet is softbricked and selecting bootloader just reboots to forever stuck logo, I could attempt to flash firmware from other similar devices such as Q64 10.1". I'm able to put tablet into FEL or flash mode by using sd card, instructions here.
I Have the same one and unlocked the boot loader but cant find TWRP for it.
Be careful with FEL mode. I'm currently trying to bring my Ares 10a back2life, but I think I bricked it further when I wrote some bs to somewhere probably important. I used to get to the Android logo at least, now not. Still get FEL mode though.
I found out that when it "gets stuck" at the logo it actually is in fastboot. You should see it in Device Manager if im not mistaken.
Related
My cousin got me this phone from China. According to him, the phone model is Coolpad 7296.
The first problem seems to be that the phone is actually different from the official Coolpad 7296, which is shown in the first attached image. But my phone looks more like the second attached image. I have the link for both phones the official site and a online seller selling a phone 99% like mine while claiming it to be a Coolpad 7296. I can't post the links due to the forum policy requiring me to have a least 10 posts. In other words, there is a very good possibility that my phone is not a legit Coolpad or it may be a variation of the Coolpad 7296.
When i first wanted to unlock the bootloader to root my phone, it was impossible. After booting to fastboot mode, any fastboot command would get stuck. For example, if i did the following:
Code:
fastboot oem unlock
It would get stuck and only show:
Code:
...
Click to expand...
Click to collapse
Or if i tried erasing the user data:
Code:
fastboot erase userdata
It would get stuck and only show:
Code:
erasing...
Click to expand...
Click to collapse
Later, I was able to root the phone via a Chinese app which literately translate to "Baidu One Click ROOT". After some playing, i tried to flash the phone via fastboot, then i literally broke the recovery mode. Most likely, the recovery partition was damaged. After more playing around, i broke the system image. I was still able to boot to fastboot mode back then. Afterwards, i broke fastboot mode as well.
After some time, i was able to install the VCOM Preloader USB Drivers by disabling the digital signatures required for installing the drivers in Windows 8. Then, I flashed the phone using the SP Flash Tool and an official ROM of Coolpad 7296 manufacturer. I am able to turn on the phone and the screen would light up in a black blank screen. The computer is able to recognize the phone via USB and i am able to use ADB commands as well as ADB Shell on it. In addition, i downloaded a program called 刷机精灵, which is a ROM flash tool for Chinese phones. This program is able to show exactly what was supposed to be showing on my phone screen. If i press the Power Button, it shows the phone's pop up window asking for if i want to power-off, reboot or put in airplane-mode. The screenshot is shown in the third attached image.
Sorry for the long post but i thought it would help if i told the whole process. Now are the real questions:
1) I never backed up my phone. So, i can't get it back to the original ROM i had. I wonder if it is possible that the screen doesn't work because the phone doesn't have the right radio image with the proper drivers. I mean, I could assume that the phone is a variation of the current official Coolpad 7296, and it is not compatible with the current official ROM.
2) Or, what are the chances that i burned my screen by charging the phone when the recovery and system images were dead. At that time, the phone could only work on fastboot mode and i left it charging overnight. Next day, the phone camera was extremely hot. And i am not sure if fastboot mode was dead first or the screen stopped showing stuff first.
3) Right now, the phone cannot reboot to neither recovery or fastboot mode (no matter how much i try with the ADB reboot or power & vol key press methods). I believe that the possibility of a somewhat incompatible phone radio, recovery and fastboot images are the cause of my current problem. So, i wonder if anybody have the same phone and know a compatible ROM.
Edit: I also want to mention, that i tried to flash the phone with other official Coolpad ROMs too. The only one that were flashable ere Coolpad 7295 and 7296. When i flash it with Coolpad 7295, i have the same problem plus the phone cannot see my SD Card. On the other hand, when i flash it with Coolpad 7296, i recognizes my SD Card. I have confirmed this via ADB shell and i can see my old files in the SD Card too.
Edit2: Another things i wanted to mention was that when i entered to fastboot mode in the past, the device id was mt6589_phone_720pv2 which means the cpu must have been a mt6589 chipset. However, i remember that when i ran a phone hardware app, it showed that the CPU was a 2.0Ghz mt6592 which was weird. And when i check online, mt6589 the CPU freequency is 1.2Ghz. On the other hand, documents online show that mt6592 has 2.0Ghz frequency but it is a octa core. My phone is definitively a quadcore.
I found a working ROM. It says it is for Coolpad 8750 but it is identical to my original ROM. The irony is that when i download the ROM of Coolpad 8750 from the official site, it doesn't work with my phone.
Code:
pan.baidu.com/share/link?shareid=1988426388&uk=2802944333
Click to expand...
Click to collapse
I have a VIBEZ K910 with locked bootloader after upgrading to version 4.4.2. Now it's bricked. Cannot enter test mode with the combination Volumn - and Power button. I think the droidboot.img is damaged. Cannot enter recovery either. Anybody can help me unbrick the phone? Pls:crying:
Sorry to hear about your bricked phone. I can't help specifically as I don't have a Lenovo, but having a search around XDA there seems to have been some success reported in the following thread:
http://forum.xda-developers.com/showthread.php?t=2597590
See this post - http://forum.xda-developers.com/showpost.php?p=52013378&postcount=412
Another post in that thread suggests:
Turn off the phone --> Run minimal ABD and fastboot as admin--> just write the command for recovery install (don't hit enter yet)--> press volume + and volume - button and connect the phone to pc via usb--> now hit enter and voila. Your phone will boot in recovery.
Click to expand...
Click to collapse
Good luck!
anyone?
f4780y said:
Sorry to hear about your bricked phone. I can't help specifically as I don't have a Lenovo, but having a search around XDA there seems to have been some success reported in the following thread:
http://forum.xda-developers.com/showthread.php?t=2597590
See this post - http://forum.xda-developers.com/showpost.php?p=52013378&postcount=412
Another post in that thread suggests:
Good luck!
Click to expand...
Click to collapse
i tried this aldready, but my phone is locked bootloder so that method is no help. Thank you for your support anyway.
hientran41 said:
i tried this aldready, but my phone is locked bootloder so that method is no help. Thank you for your support anyway.
Click to expand...
Click to collapse
OK, but did you look at the second link there, to the specific post in that thread? It suggests a process for locked bootloader, which is why I thought it might help...
Anyhoo, I hope you manage to get it fixed somehow!
Is anybody have the droidboot.img file from the VibeZ K910 dualsim, pls upload it for me. i cannot find it anywhere.
I look into the second link as well. that method for user have a working phone but locked bootloader and want to downgrade.
Ah, OK. Sorry I couldn't help.
u fix your phone?
hientran41 said:
I have a VIBEZ K910 with locked bootloader after upgrading to version 4.4.2. Now it's bricked. Cannot enter test mode with the combination Volumn - and Power button. I think the droidboot.img is damaged. Cannot enter recovery either. Anybody can help me unbrick the phone? Pls:crying:
Click to expand...
Click to collapse
hi do u fix your phone?
Geguniukas said:
hi do u fix your phone?
Click to expand...
Click to collapse
i bricked also
dunno what to do..
---------- Post added at 12:13 AM ---------- Previous post was at 12:13 AM ----------
hientran41 said:
I have a VIBEZ K910 with locked bootloader after upgrading to version 4.4.2. Now it's bricked. Cannot enter test mode with the combination Volumn - and Power button. I think the droidboot.img is damaged. Cannot enter recovery either. Anybody can help me unbrick the phone? Pls:crying:
Click to expand...
Click to collapse
did you fixed the phone?
lenovo k910e 4.2.2 bricked after TWRP for 4.4.2 installation
Hi , this is my first time on the site , so forgive me if ive posted this in the wrong place.
I briked my Lenovo k910e running 4.2.2 rom with google apps purchased off Aliexpress.
What i did was run the flashrec.exe file for TWRP , but not until too late did i realise it was for 4.4.2 instead of 4.2.2.
Now i cannot boot the phone , TWRP was successfully installed and operational , but after about 20 reboots TWRP flash screen is stuck on the TeamWin logo and not accessable.
Ive tried mostl sugestions on this site and others without luck.
I can get the phone recognised with fastboot only after these commands ;
cd downloads
cd fastboot
adb devices
and it seems i may be able to push files to my device.
Is there a working link to the k910 OEM rom k910_ss_s_2_040_0109_131226 someone could direct me to.
All the links i have found so far are corrupted. Is there a way of repairing the TWRP recovery i have in the phone now.
Am I correct in assuming I have to install the OEM factory 4.2.2 ROM to wipe TWRP and istal Lenovo recovery ?.
Any help would be so appreciated. Thanks
Solution ( k910 bricked )
Ok here is the solution even if your device ( k910 dual sim ) is completely bricked as was mine.
I was stuck in Lenovo logo with no success in finding right and working drivers ( windows 7 64x ) and i was not able to to get in recovery official ...everything was just - somehow - deleted...
I had locked bootloader **** and was not be able to flash cmw in working mode ****
There was nothing for me that could recover my phone even if the "hard" way with QPST or miflash etc
So....after 3 days....find this solution and hope this will help you because it is soooooooooo easy finally!
Steps:
1) Download lenovo driver ( i think it is useless in fact but ok....just run it you dont have anything more to loose )
https://www.dropbox.com/s/frbpz16udrefoit/LenovoUsbDriver_autorun_1.0.112.exe?dl=0
2a) Download and install Minimal adb
https://www.dropbox.com/s/uvngsu4vz4hvsky/minimal_adb_fastboot_v1.1.3_setup.exe?dl=0
So now you have to use the right recovery image ( this file has to be inside minimal adb folder )....so here it is:
https://www.dropbox.com/s/ge05m1fe8n4qgb1/recovery.img?dl=0
2b)
Download this ROM ( this worked for me - with other i did try i did get an error )
http://www.needrom.com/download/lenovo-k910-vibeui-2-0/
prefer the last updated version ( 1501 )
Put this rom in the same ADB folder and renale zip in VIBE1411.ZIP ( in order to be easier later )
3) Turn off the device open Adb and write : fastboot boot recovery.img ( to have it ready )
4) Push volume + $ volume - at the same time and AFTER connect with usb to your pc - At the time the device will vibrate HIT ENTER in ADB
This will flash the recovery and after 1 minute device will open in a recovery screen with an adb update option ***
SELECT THIS adb update OPTION !
Your device kow it is ready to flash the new rom ! ( you will realize that everything is right from many usb beeps you will hear )
5)In adb console write : adb sideload VIBE1411.ZIP
This will take a little ....after that your device will reboot ! Dont panic if for a few minutes it will stuck in lenovo logo....
IT IS NORMAL AND YOU HAVE TO WAIT!
Hope this will help you.....please feel free to tell me if this worked for you.
C u
Same thing happens to my lenovo vibe z k910
buzzbuzz1 said:
Hi , this is my first time on the site , so forgive me if ive posted this in the wrong place.
I briked my Lenovo k910e running 4.2.2 rom with google apps purchased off Aliexpress.
What i did was run the flashrec.exe file for TWRP , but not until too late did i realise it was for 4.4.2 instead of 4.2.2.
Now i cannot boot the phone , TWRP was successfully installed and operational , but after about 20 reboots TWRP flash screen is stuck on the TeamWin logo and not accessable.
Ive tried mostl sugestions on this site and others without luck.
I can get the phone recognised with fastboot only after these commands ;
cd downloads
cd fastboot
adb devices
and it seems i may be able to push files to my device.
Is there a working link to the k910 OEM rom k910_ss_s_2_040_0109_131226 someone could direct me to.
All the links i have found so far are corrupted. Is there a way of repairing the TWRP recovery i have in the phone now.
Am I correct in assuming I have to install the OEM factory 4.2.2 ROM to wipe TWRP and istal Lenovo recovery ?.
Any help would be so appreciated. Thanks
Click to expand...
Click to collapse
After running twrp recovery it operates 3-4 times but now it flashes on twrp screen and screen goes blank and again flashes . I am unable to on it and as it shows only light and lenovo logo after that blank screen . Please help me in this. Its only detecting in adb recovery not any other mode.
lenove vibe Z k910 locked and stuck in logo
hello all
I ve done every word and many other tutorials but still the problem the same:
adb devices give just nothing
but fastboot devices gives the device
the driver is installed correctly detected in devices of the computer
here is the response for :fastboot boot recovery.img:
~/Desktop/lenovo]$ fastboot boot recovery.img (master✱)
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.536s]
booting...
FAILED (remote: Locked)
finished. total time: 0.538s
thanks for everyone to help
Boot into recovery under bricked condition
Today I bricked K910 after reinstalling GMS apk.
The phone hanged at boot logo.
Nothing can be from here.
I decided to take this risk.
I removed the back cover and disconnected the battery terminal.
After that I plugged back the terminal.
Several tries by power button and volume down to get into the recovery mode. All failed.
Each time it hanged at boot logo.
I have to redo the battery terminal unplug sequence again.
This is correct method to get into recovery mode.
Press power button and volume down till the Lenovo logo appears.
Move the power button finger to the position of the " Home " of the touchscreen position.
Hold till the recovery menu appears. Choose factory reset to erase the phone.
There was two lit small icon below. Make your choice.
The phone will be erased by reset.
Reboot after the process.
I solved my phone bricked problem.
Hope the method will solve your problem.
Good day to all K910 users.
my vibe z cannot access the recovery mode (PWR + VLM DOWN), it only vibrate. If turn on only stuck at Logo. Please help .
Let's try unbrick X722
You ask the same thing in several threads.
We offer tests but few comments results.
After several days the people with bricks disappear. Fixed up?
I suggest that anyone who has brick, write it, but if we propose a solution, say whether it works or not, to discard it
We can have 2 cases: hard brick and soft brick.
Hard brick of impossible moment. Requires zip qfil. It is proposed to build one.
Brick soft with fastboot function. Here you can do tests.
Who has a brick ?, publish how it came, and if you have fastboot.
Greetings.
P.S. Sorry for the English. I use a translator
Possible soft brick solution ...
Possible hard brick solution ...
F.J.V said:
Possible soft brick solution ...
Click to expand...
Click to collapse
I installed the 26 s with twrp
soft brick because it goes into fastboot, it enters edl mode.
does not enter recovery mode in any way.
different startup screens by pressing and holding the power button for more than 20 seconds.
I tried all the procedures by using minimal adb and fastbooot without any results
I have two options, I am in Italy, but I strongly doubt it, or send it back to bangood that I have already contacted, or buy another, I'm following over xda, pda, leeco.re, androids.op? sorry.
from the tests I did between a while do not even work the buttons
if you have any questions i can answer.scusate google translate
I seem to have realized that the phone has in the recovery twrp and the recovery stock, failing to decide which start, so it stops at boot, if i try to delete with adb either the stock recovery or twrp tells me ok.
if I try to install the stock or twrp tells me failed
I got this discussion on facebook for n cool1.I wonder if it can work on x722? "If you're interested in getting the device started, I unpacked the firmware file with YGPD and flashed directly that with MiFlash in edl mode. lack of IMEI, but after solving I'm hard brick, I'm scared no more !!! "
YGPD is Coolpad (Yulong) Flayhing Tool and it makes temp folders on C disk during flash preparation.
You could make recovery replacement hack while flashing some coolpad phones.
Try this:
Download Recovery.zip
Decompress.
recstock722.img is recovery stock 722.
Copy recstock722.img to fastboot folder
Open Command Window in Fastboot Folder
writes:
fastboot boot recstock722.img
This does not flashea recovery, only charge on phone.
If all goes well the phone restarts in recovery stock.
Load update.zip (5.8.001D) with recovery.
If I succeed flash another rom and another recovery
Greetings.
[/COLOR]
F.J.V said:
Try this:
Download Recovery.zip
Decompress.
recstock722.img is recovery stock 722.
Copy recstock722.img to fastboot folder
Open Command Window in Fastboot Folder
writes:
fastboot boot recstock722.img
This does not flashea recovery, only charge on phone.
If all goes well the phone restarts in recovery stock.
Load update.zip (5.8.001D) with recovery.
If I succeed flash another rom and another recovery
Greetings.
Click to expand...
Click to collapse
https://imageshack.com/i/pnfE9OeIp
Has the 26s entered the unlock code for the bootloader?
x722 For people who can not charge the phone being in soft brick
If you have the phone that does not charge anymore
connect it to the mains power supply
press volume up and down together and power key
only release when you hear half-vibration
the charging LED lights up
I have a Hard Brick... i lost my hopes..
ste73 said:
https://imageshack.com/i/pnfE9OeIp
Has the 26s entered the unlock code for the bootloader?
Click to expand...
Click to collapse
No.
I have stock rom 20S bangood unmodified
vsrocha said:
I have a Hard Brick... i lost my hopes..
Click to expand...
Click to collapse
Nothing at the moment, but ...
Does it go into EDL mode?
To enter EDL mode:
Press (vol +), (vol-) and plug into the PC.
If the PC recognizes 9008 you have to wait for qfil.
F.J.V said:
Nothing at the moment, but ...
Does it go into EDL mode?
To enter EDL mode:
Press (vol +), (vol-) and plug into the PC.
If the PC recognizes 9008 you have to wait for qfil.
Click to expand...
Click to collapse
Yes, recognizes, i don't need Press (vol +), (vol-) just plug.
Check this...
http://www.leeco.re/topic/2592-hard-bricked-x722/?do=findComment&comment=53338
vsrocha said:
I have a Hard Brick... i lost my hopes..
Click to expand...
Click to collapse
because brick hard
ste73 said:
because brick hard
Click to expand...
Click to collapse
i install miui 8 but i did not know the diference between X720 e X722, after this i had soft brick...
and my anxious speak loud and i install a fast rom for X720...
mate... too bad has three models and diferents roms.
I just read ROM for Le Pro 3 and install soon.
:crying:
I have a silly question, isn't possible change the Qfil le_zl1_qfil_ufs for X722, the unic difference between them is X720 Snapdragon 821 and X722 Snapdragon 820?
F.J.V said:
Nothing at the moment, but ...
Does it go into EDL mode?
To enter EDL mode:
Press (vol +), (vol-) and plug into the PC.
If the PC recognizes 9008 you have to wait for qfil.
Click to expand...
Click to collapse
With Le Eco in financial troubles, it's unlikely they will release the qfil that is needed. I'm thinking of sending back my hard brick X722 to the vendor I bought it from, and just ask how much it would cost to get if fixed.
Try this modified qfil ROM.
modqfil_ufs.zip
It's not official.
It is qfil 720 with some X722 files.
I do not promise anything.
Do not try if you do not have brick
Comment results.
Greetings.
F.J.V said:
Try this modified qfil ROM.
modqfil_ufs.zip
It's not official.
It is qfil 720 with some X722 files.
I do not promise anything.
Do not try if you do not have brick
Comment results.
Greetings.
Click to expand...
Click to collapse
downloading!! :fingers-crossed:
Don't work for me.
After descompress show this error.
Flash file not found, please make sure QFIL flash file is correct.
Does anyone know how to translate the scripts?
https://imageshack.com/i/potoxDAkj
https://imageshack.com/i/pnyUkScQj
depending on how I press the power button
ste73 said:
Does anyone know how to translate the scripts?
https://imageshack.com/i/potoxDAkj
https://imageshack.com/i/pnyUkScQj
depending on how I press the power button
Click to expand...
Click to collapse
Hello, no idea of Chinese.
I compared it with my terminal, I think I recognize the screens.
The first:
http://imageshack.com/i/potoxDAkj
This leaves when I'm in EDL and restart. This screen exits and starts normal.
The second:
http://imageshack.com/i/pnyUkScQj
This leaves when I'm in recovery and restart. This screen exits and starts normal.
The two screens precede the boot, it depends on where you restart.
Every time you do some testing, even if nothing seems to happen, boot into fastboot and try unlocking.
Greetings.
Hi,
I've got a problem where my phone is stuck in bootloop and I cannot go into recovery mode. All I can get into is fastboot mode. I know there's a way to get into recovery from fastboot mode using ADB but I do not know what to do or what steps to follow as I really don't know much about modding phones apart from flashing a ROM that I wan't to use via recovery (which I assume even a ten year old would be able to do effortlessly after seeing it being done once or twice).
I am using the global 4/64 Redmi Note 4 running the latest version of Android Open Source Illusion Project.
Any help would be appreciated. Thank you.
laneofmagic said:
Hi,
I've got a problem where my phone is stuck in bootloop and I cannot go into recovery mode. All I can get into is fastboot mode. I know there's a way to get into recovery from fastboot mode using ADB but I do not know what to do or what steps to follow as I really don't know much about modding phones apart from flashing a ROM that I wan't to use via recovery (which I assume even a ten year old would be able to do effortlessly after seeing it being done once or twice).
I am using the global 4/64 Redmi Note 4 running the latest version of Android Open Source Illusion Project.
Any help would be appreciated. Thank you.
Click to expand...
Click to collapse
Did you try combo key? Holding Power and Volume+ buttons?
If this doesn't works, you have to set up ADB bridge on your PC. Here is the guide: https://www.xda-developers.com/install-adb-windows-macos-linux/
When you do that, type the command via ADB while being in fastboot mode:
fastboot reboot recovery
This should take you into the recovery mode.
Any help please Im stuck in a boot loop and recovery and fastboot are inaccessible, so i cant send any commands? im forking on Mac OS but even ive installed a virtual PC to try some of the countless programs but no seams to work since the phone is not recognized.
The TL;DR is, I bricked my phone (TMo Nord N200 5G, SIM unlocked, Bootloader unlocked). I'm trying to use the MSM to recover it. I can't boot to EDL (hold down volume up and volume down at the same time, while pressing power or plugging a USB cable into my PC). It just boots to Fastboot when I follow that procedure. I can't get to a place where I can use ADB commands (ADB shows device "unauthorized").
Longer version, my stock phone was upgraded to the June patch level, I think.
I did the SIM unlock, unlocked the bootloader, and installed the drivers.
I successfully flashed the latest PHH squeak FOSS by following this guide but it had some quirks that I wasn't completely satisfied with.
I flashed a SparkOS GSI linked from somewhere else, but it constantly beeped at me after I disabled Google Play Services, so I decided to move on.
I think the next OS I tried was CRdroid from the same place, but I also replaced the boot.img with a stock one that was patched for Magisk. I can't remember why I thought this was a good idea. There was also a thread that said Magisk doesn't like having nothing in system_a so flash this blank partition using these commands. It always errored out, but I tried it before rebooting.
At this point, my phone would either boot to Qualcomm CrashDump on its own, or Fastboot if I held volume down.
Using the latest Fastboot Enhance I was able to get into fastbootd by switching to "A" active, then rebooting to fastbootd. Have to remember to switch back to "B" active to get anything else to work.
I've tried flashing a few different things since I can get to fastbootd now. I'm no longer booting into the Qualcomm CrashDump, it reliably boots to fastboot as long as I'm "B" active. I just can't get anything resembling a working OS.
I've tried flashing the OTA TMo with Fastboot Enhance a few different times, and a few different GSIs through fastboot, and I really want to get back to stock now so I can start all over.
I've also tried a couple different MSM tool versions, but since my phone is never in EDL, it's never recognized.
Thank you for any assistance.
Holding the Vol +/- & power WILL force boot the N200 to EDL mode regardless of the software corruption as this is at the hardware level.
The thing you need to be concerned with is that you have the latest Qualcomm ADB tools installed so msmtool will recognise the phone while in this mode.
Install the latest adb driver and go into that folder when typing the command as you might have older adb installed already at another location (and in the system path) that is running instead.
Android MTK - How-to Guide and Root Tutorials
Android MTK is one of the best websites that provides the latest Root Tutorial, USB driver, Android Tool, Stock Firmware and How-to Guide.
androidmtk.com
Then you need to have msmtool running and ready to begin and the mouse button hovering over the start button. As soon as the first logo screen comes up, it will only go into EDL mode for about 3-4 seconds and then move on to booting and dump you into fastboot if the rom is corrupt/missing. You need to watch msmtool on the first line and the second it shows up, click start and it will flash.
If you are still missing it and in fastboot I think the the N200 supports the force phone to edl mode by fastboot command:
fastboot oem edl
scanman0 said:
Holding the Vol +/- & power WILL force boot the N200 to EDL mode regardless of the software corruption as this is at the hardware level.
The thing you need to be concerned with is that you have the latest Qualcomm ADB tools installed so msmtool will recognise the phone while in this mode.
Install the latest adb driver and go into that folder when typing the command as you might have older adb installed already at another location (and in the system path) that is running instead.
Android MTK - How-to Guide and Root Tutorials
Android MTK is one of the best websites that provides the latest Root Tutorial, USB driver, Android Tool, Stock Firmware and How-to Guide.
androidmtk.com
Then you need to have msmtool running and ready to begin and the mouse button hovering over the start button. As soon as the first logo screen comes up, it will only go into EDL mode for about 3-4 seconds and then move on to booting and dump you into fastboot if the rom is corrupt/missing. You need to watch msmtool on the first line and the second it shows up, click start and it will flash.
If you are still missing it and in fastboot I think the the N200 supports the force phone to edl mode by fastboot command:
fastboot oem edl
Click to expand...
Click to collapse
Thank you for responding!
The command fastboot oem edl is returning either:
FAILED (remote: 'Command not supported in default implementation')
FAILED (remote: 'unknown command')
I'm running fastboot version 33.0.2-8557947, it's not in my system path.
From a full power off, holding the buttons and plugging in the USB cable, it's about 5 seconds until I see the OnePlus logo, then 2 more seconds before I drop into Fastboot. I'm not sure what I'm looking for, to confirm EDL mode. I'm not seeing my Device Manager update in that time, and the MSM tool isn't displaying anything, either.
try insert cable then volume + and - and power. keep it holding for 10-15 seconds or till you see qualcomm device in device manager
qualcomm drivers
Qualcomm_Drivers_Setup.exe
drive.google.com
try holding both volume buttons (make sure its off!) then plugging your phone in to the computer with msm tool open (you can pre-press the start button) (make sure you have all the drivers installed)
How can I verify that I have all of the required Qualcomm drivers installed?
I've run pretty much every driver install in this thread, or that I could find by searching, and it still seems like my laptop isn't recognizing the phone.
yrrebeulB said:
How can I verify that I have all of the required Qualcomm drivers installed?
I've run pretty much every driver install in this thread, or that I could find by searching, and it still seems like my laptop isn't recognizing the phone.
Click to expand...
Click to collapse
Open up Device Manager in windows. and then attempt to connect it to the computer while in EDL mode. In EDL mode it will still look like it's off btw, that confused me a lot.
You're looking for a device to show up in Device Manager when you connect it. If you're in EDL mode and have the driver's installed correctly it'll say qualcomm-something-something. If you see unknown device, you don't have the drivers installed. If no new device is detected either you're not in EDL mode or you should try a different cable.
Same issue as OP, won't boot into edl
edit: use USB 2.0
You can try enumusb.exe here: http://www.temblast.com/windows.htm
Code:
C:\>enumusb.exe /l /v05c6 /p9008
It will list the first time that a QUSB_BULK was plugged into a port, even if there was no driver found/loaded.
If you want, you can clear past connections by (needs to be admin command line):
This does no harm. I clear everything out occasionally, it just means that next boot will take 5 seconds longer while it discovers "new" devices and installs the same drivers.
Code:
C:\>enumusb.exe /d /v05c6 /p9008
Or, if you don't like that, just plug your device into a different port and see if another port is listed in enumusb.exe /l
On that same page you can find usblog.exe
You just run it and it will show you what pops up and down.
But, this only shows devices that Windows has loaded drivers for.
swee08315 said:
Open up Device Manager in windows. and then attempt to connect it to the computer while in EDL mode. In EDL mode it will still look like it's off btw, that confused me a lot.
You're looking for a device to show up in Device Manager when you connect it. If you're in EDL mode and have the driver's installed correctly it'll say qualcomm-something-something. If you see unknown device, you don't have the drivers installed. If no new device is detected either you're not in EDL mode or you should try a different cable.
Click to expand...
Click to collapse
THANK YOU!
I didn't know there was a mode where it was powered on and the screen stayed off.
I finally got there by this path: Fastboot -> Recovery (I think?) -> List of languages, I chose English -> Power off -> Yes, really -> Hold down VOL+ and VOL- until I noticed the Qualcomm device in Device Manager
So I'm in EDL mode now! But my MSM tool crashes immediately on launch. So new problem, at least.
yrrebeulB said:
THANK YOU!
I didn't know there was a mode where it was powered on and the screen stayed off.
I finally got there by this path: Fastboot -> Recovery (I think?) -> List of languages, I chose English -> Power off -> Yes, really -> Hold down VOL+ and VOL- until I noticed the Qualcomm device in Device Manager
So I'm in EDL mode now! But my MSM tool crashes immediately on launch. So new problem, at least.
Click to expand...
Click to collapse
I re-installed the Qualcomm driver bundle while my phone was plugged in and in EDL mode, and MSM finally worked! Thank you kind stranger! I'm back to factory now.
Thank you Strangers ,
yrrebeulB , all of you
Ytube21 said:
qualcomm drivers
Qualcomm_Drivers_Setup.exe
drive.google.com
Click to expand...
Click to collapse
thank you
yrrebeulB said:
THANK YOU!
I didn't know there was a mode where it was powered on and the screen stayed off.
I finally got there by this path: Fastboot -> Recovery (I think?) -> List of languages, I chose English -> Power off -> Yes, really -> Hold down VOL+ and VOL- until I noticed the Qualcomm device in Device Manager
So I'm in EDL mode now! But my MSM tool crashes immediately on launch. So new problem, at least.
Click to expand...
Click to collapse
this line literally saved me hours
yrrebeulB said:
So I'm in EDL mode now! But my MSM tool crashes immediately on launch. So new problem, at least.
Click to expand...
Click to collapse
Try my native Windows EDL client. It uses the same Firehose loader as your stock tool does.
At the very least this will give you a second opinion.
http://www.temblast.com/edl.htm