Related
Hi,
after some complications with the partition mapping on my tablet i finaly extracted the boot.img created a custom boot.img. Now want to flash it back using adb, fastboot or flash_image. Afaik flash_image isnt supported, get some errors "error scanning partitions"....
So i tried to flash with adb / fastboot, but it is required to boot to bootloader mode.
I tried many key combinations on my tablet (power button, home, volume keys) and apps to boot it into bootloader mode but was not successfull yet ("adb shell reboot bootloader" and Quick Boot App from Play Store).
I´ve got an Allwiner A10 Tablet with T15A_V5 Mainboard and 1GB RAM (like the goclever a103 tablet). Also known as (same hardware):
- Manta MID06
- Point of View Protab XXL
- Goclever A103
- Storex eZee'Tab 10C
- Coby 1042
- Yarvik TAB464
Any idears how to get to bootloader mode or flash the img back?
Ty.
*push*
easier to get anwsers for apple devices than getting feedback here... wtf?!
You don't reflash these A10-based tablets from bootloader mode. AFAIK they don't even have a bootloader mode.
You reflash them from your PC using the Livesuit program, with the tablet connected over USB.
The tablet has to be put in a specific mode (FEL mode) in which the screen will remain dark and a different USB device will be detected by the PC (Livesuit comes with a driver for this).
To put the tablet in this mode :
- turn in off completely (not just standby mode) and disconnect the USB cable
- start the Livesuit program, and select the firmware image (.img file) you want to flash
- hold the Volume- button on the tablet and while holding it, connect the USB cable to the PC
- while still holding Volume-, make a succession of quick press and release on the power button (at least 5 or 6 in my experience)
You'll hear your PC detecting a new USB device.
- release the button
- make a force installation of the driver that came with Livesuit
A popup should appear asking if you want to do a forced format. Choose yes, then flashing should begin (progression bar)
livesuit wont install
i downloaded livesuit but when i try to install it blinks out and nothing happens can i get help please ? im so close to fixing my Eglide Pro III
I tried unlocking the bootloader an atrix that was given to me about a month ago, and it had 3.4.6 (or something like that) and I couldn't find an unlocker for that version so I tried the one for the previous version, which failed at some point in the process and now it just boots to "Failed to boot 1". I've been trying every method I can find to try to fix this, I even bought the little red adapter to change any cable into a dev cable, and i know it works because if I power it on with the volume up key pressed it says "power reason: factory cable".
I've tried RSD lite when connected with the adapter, but device properties stays blank. I tried loading an image and pressing start but nothing happens. The computer is seeing the phone but it says that it doesn't recognize the device. Also, if I start it with the volume up pressed it goes STRAIGHT to the fastboot protocol thing, I never get the option to choose RSD protocol. "fastboot devices" is just blank.
I tried it on several different computers with the same results.
Is this a hard brick? Any advice would be very much appreciated.
Did you install the windows drivers?
Scrub13 said:
Did you install the windows drivers?
Click to expand...
Click to collapse
Yea. I did.
Tekzel said:
I've tried RSD lite when connected with the adapter, but device properties stays blank. I tried loading an image and pressing start but nothing happens. The computer is seeing the phone but it says that it doesn't recognize the device. Also, if I start it with the volume up pressed it goes STRAIGHT to the fastboot protocol thing, I never get the option to choose RSD protocol. "fastboot devices" is just blank.
Click to expand...
Click to collapse
If you power on while pressing volume-up, it should go straight to fastboot since it's the first option available. What happens when you reboot with volume-down?
Also, if the phone says "Starting fastboot protocol support" it's not hard-bricked, even if it's seriously screwed up at the moment. If it says "Entering NVFlash recovery mode," that's the point where it's toast (from the user end anyway).
With your phone in fastboot, does your computer recognize either of the SD cards? Have you re-downloaded the Motorola drivers, just to be sure? If "fastboot devices" comes back blank, then either the phone isn't truly in fastboot mode or the drivers aren't up to date.
Tekzel said:
I tried unlocking the bootloader an atrix that was given to me about a month ago, and it had 3.4.6 (or something like that) and I couldn't find an unlocker for that version so I tried the one for the previous version, which failed at some point in the process and now it just boots to "Failed to boot 1". I've been trying every method I can find to try to fix this, I even bought the little red adapter to change any cable into a dev cable, and i know it works because if I power it on with the volume up key pressed it says "power reason: factory cable".
I've tried RSD lite when connected with the adapter, but device properties stays blank. I tried loading an image and pressing start but nothing happens. The computer is seeing the phone but it says that it doesn't recognize the device. Also, if I start it with the volume up pressed it goes STRAIGHT to the fastboot protocol thing, I never get the option to choose RSD protocol. "fastboot devices" is just blank.
I tried it on several different computers with the same results.
Is this a hard brick? Any advice would be very much appreciated.
Click to expand...
Click to collapse
This isn't a hard brick:good:
when you boot your phone don't hold down the volume button, then hit the volume down button right when the menu comes up. Then just cycle through and hit RSD and that should do it
here is a thread specifically talking about fixing this issue http://forum.xda-developers.com/showthread.php?t=1528729
also, in the future I would recommend using this tool for unlocking and rooting your phone, it's no sweat, and this tool even has an automatic fix for your current problem. if I'm not mistaken..I'm not totally sure
here is the thread where the automatic BL unlocker came from, though the link there is broken http://forum.xda-developers.com/showthread.php?t=1182871
sheeparecurious said:
If you power on while pressing volume-up, it should go straight to fastboot since it's the first option available. What happens when you reboot with volume-down?
Also, if the phone says "Starting fastboot protocol support" it's not hard-bricked, even if it's seriously screwed up at the moment. If it says "Entering NVFlash recovery mode," that's the point where it's toast (from the user end anyway).
With your phone in fastboot, does your computer recognize either of the SD cards? Have you re-downloaded the Motorola drivers, just to be sure? If "fastboot devices" comes back blank, then either the phone isn't truly in fastboot mode or the drivers aren't up to date.
Click to expand...
Click to collapse
Powered on with volume-up it goes to:
Failed to boot 1
PwrReason: FACTORY_CABLE
Starting Fastboot protocol support
With power down (which I didn't know about), I see something flash on the screen really fast and then it goes blank. The computer recognizes it, but it still says "unknown device".
I recently downloaded the Motorola Device Manager from here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
This machine is Windows 8, but I also tried it on a Windows 7 machine with the same result.
With the phone in fastboot, as above, it the computer doesn't see the internal storage, but it doesn't have an SD card in it, I will put one in it today and see what happens.
I've downloaded the above software fresh on each of the three machines I have tried this on, two Windows 8 machines, and one Windows 7.
Thanks for the suggestions, I really appreciate it.
thewarhawk said:
This isn't a hard brick:good:
when you boot your phone don't hold down the volume button, then hit the volume down button right when the menu comes up. Then just cycle through and hit RSD and that should do it
here is a thread specifically talking about fixing this issue http://forum.xda-developers.com/showthread.php?t=1528729
also, in the future I would recommend using this tool for unlocking and rooting your phone, it's no sweat, and this tool even has an automatic fix for your current problem. if I'm not mistaken..I'm not totally sure
here is the thread where the automatic BL unlocker came from, though the link there is broken http://forum.xda-developers.com/showthread.php?t=1182871
Click to expand...
Click to collapse
Great, I'm glad to know it's not hard bricked!
When I boot the phone with nothing pressed, it goes straight to a single line:
Failed to boot 1
I never get the menu. Also, just tried some presses of the button as it was booting up and found that I don't need to hold either power up or down. If I power it on, and when it stops at failed to boot 1, I can press the power up once and it goes to the fastboot protocol support screen or power down and the screen goes blank.
I'll check out the links you posted, thanks!
Failed to boot 1 should be the same as rsd mode.
Tekzel said:
Great, I'm glad to know it's not hard bricked!
When I boot the phone with nothing pressed, it goes straight to a single line:
Failed to boot 1
I never get the menu. Also, just tried some presses of the button as it was booting up and found that I don't need to hold either power up or down. If I power it on, and when it stops at failed to boot 1, I can press the power up once and it goes to the fastboot protocol support screen or power down and the screen goes blank.
I'll check out the links you posted, thanks!
Click to expand...
Click to collapse
As I understood you wanted to unlock bootloader and failed. So I suggest you to try automatized bootloader unlock tool(@thewarhawk give you link) and then fix the "Failed to boot 1" because if you failed something now you probably hard brick your device I have experience whit one of my atrix. So I in your situation will do that:
1) manually in fastboot (better in win7) fastboot oem unlock (I just doest know command for unique device id in fastboot so it need you to search in xda)
2) then flash fully system partition whit fastboot
3) and then if device doesn't boot correctly try this http://forum.xda-developers.com/showthread.php?t=1528729 as you early said @thewarhawk
Hi, the problem is the windows 8 drivers,First download this. Then you need to boot the phone in fastboot mode, then go in device manager then you will see fastboot with an exclamation mark. Right click on it and select update drivers. Next do search for a driver on my computer, Then you do choose from a drivers list (or something along those lines). Select ADB interface -> Motorola -> Mot composite ADB interface. You will get a warning, say yes anyway then bang... your phone is detected by adb and fastboot.
Well, i've flashed the ftf file downloaded directly from xperifirm {E2306_26.3.A.0.131_R2C_Customized GEL_1294-3902}
-update-
some mysterious, magical stuff hapened and i entered fastbootmode
can boot recovery and boot.img from fastboot and now everything is fine
<3
thanks everyone
then, i've try to install root (following a tutorial for this device and this comp.) but i could not enter to FASTBOOT MODE
try using:
- (vol+) + (plug the phone)
-(power btn) + (vol+) + (plug the phone)
-(power btn) + (vol+) + (vol-) + (plug the device)
and the only thing that happened is: -Vibrate + sony logo ---> normal boot
----
Then i try to enter fastboot using the adb command {ADB REBOOT-BOOTLOADER}
but it just reboot normally (sony logo and then start normally)
[[ADB do recognize my device and all drivers were properly installed; but can't enter to fastboot mode]]
---
I've try to reflash my device again, but then i couldn't be able to enter to flashmode
{ with the device off; press vol- and then connect to usb}
after several attempts using - [(power btn) + (vol-)] i entered flashmode and reflash my device...
----
then i activate dev mode: [usb debuggin and OEM UNLOCK]
and try to get to fastboot mode, but the same results...
i got my device recognized by {ADB DEVICES}
but can't get fastboot
-----
Then the user who's helping me told me to reflash using this config
[in excludes section check all except AMSS_FSG, AMS_FS1, AMS_FS2,BOOT DELIVERY, KERNEL. Don't check anything else.]
But i can't get flashmode now... i try all the combinations, try in ubuntu 16, and windows 10... but nothing
the device starts normally nothing wrong.... except well, i can't enter any -mode- now...
any help?
Thanks
try enable usb debugging. go to setting, about phone, then scroll to build number. tap it repeadly till developer option appear on setting. set enable usb debugging there. and try flash it again.
I can't get anything to start!
~~~~
...Well said:
]
---
~~~~I've try to reflash my device again, but then i couldn't be able to enter to flashmode
~~~~{ with the device off; press vol- and then connect to usb}
~~~~after several attempts using - [(power btn) + (vol-)] i entered flashmode and reflash my device...
----
~~~~then i activate dev mode: [usb debuggin and OEM UNLOCK]
~~~and try to get to fastboot mode, but the same results...
~~~~i got my device recognized by {ADB DEVICES}
~~~~but can't get fastboot
-----
.~~~~.. nothing wrong.... except well, i can't enter any -mode- now..
~~~~any help?
~~~~Thanks
Click to expand...
Click to collapse
[~~~~QUOTE=shouqinz;67837866]try enable usb debugging. go to setting, about phone, then scroll to build number. tap it repeadly till ~~~~developer option appear on setting. set enable usb debugging there. and try flash it again.[/QUOTE]
Girlfriend tried to update her Sony Aqua M4 e2306...
she says that the boot loader was unlocked, and she installed the twrp update... and the root check came back rooted.... she powered off the phone and put it on a charger. ...
a few hours later she tried to restart it and only got the Sony Xperia screen then reboot loop.
I've spent 2 days reading everything that i can find and trying various solutions but most won't work because it won't stay connected long enough to use companion, adb, fastboot, bootloader, etc. When the devices is seen by pc it is only for a moment and comes up as a generic MTP device or a hard drive i can't open.
I can get the occasional green or blue lights and sometimes a generic battery symbol by powering off and pressing + or - with power, but never get a recovery or boot load screen... only alternating "sony Xperia" and darkness
also, Emily won't update.
I've tried multiple solutions using different versions of SDK, ADB, sony and xperia Companion, fastboot, bootloader, odin, pwm, and more on multiple machines from XP to Win10, but nothing seems to even make a dent!
I've removed the back and disconnected the battery for 2 hours and am currently trying to research a more physical hack/repair using riff jtag.
i see many people with "boot loop" issue , but no one seems to follow through and say how to get out if you don't have the option of booting to anything....
merwinaleman said:
Well, i've flashed the ftf file downloaded directly from xperifirm {E2306_26.3.A.0.131_R2C_Customized GEL_1294-3902}
then, i've try to install root (following a tutorial for this device and this comp.) but i could not enter to FASTBOOT MODE
try using:
- (vol+) + (plug the phone)
-(power btn) + (vol+) + (plug the phone)
-(power btn) + (vol+) + (vol-) + (plug the device)
and the only thing that happened is: -Vibrate + sony logo ---> normal boot
----
Then i try to enter fastboot using the adb command {ADB REBOOT-BOOTLOADER}
but it just reboot normally (sony logo and then start normally)
[[ADB do recognize my device and all drivers were properly installed; but can't enter to fastboot mode]]
---
I've try to reflash my device again, but then i couldn't be able to enter to flashmode
{ with the device off; press vol- and then connect to usb}
after several attempts using - [(power btn) + (vol-)] i entered flashmode and reflash my device...
----
then i activate dev mode: [usb debuggin and OEM UNLOCK]
and try to get to fastboot mode, but the same results...
i got my device recognized by {ADB DEVICES}
but can't get fastboot
-----
Then the user who's helping me told me to reflash using this config
[in excludes section check all except AMSS_FSG, AMS_FS1, AMS_FS2,BOOT DELIVERY, KERNEL. Don't check anything else.]
But i can't get flashmode now... i try all the combinations, try in ubuntu 16, and windows 10... but nothing
the device starts normally nothing wrong.... except well, i can't enter any -mode- now...
any help?
Thanks
Click to expand...
Click to collapse
did you flashed hole ftf using flashtool or only the mencioned partitions above?
PiSpecialist said:
did you flashed hole ftf using flashtool or only the mencioned partitions above?
Click to expand...
Click to collapse
I still can't enter any-mode, so i haven't flash any ftf
me too
merwinaleman said:
I still can't enter any-mode, so i haven't flash any ftf
Click to expand...
Click to collapse
Same Here - is there no-one willing to help?!?
anyone know how to physically cause a device to self test, or reload defaults, ....or.... boot from sd by shorting a pin OR SOMETHING???
grrr - help:crying:
well... a little progress after 100s of reboot attempts!
i see a HD in the Device manager.
I can't access the disk, but it isn't constantly rebooting..
any one have a suggestion for my next move?
Error 7/24/2016 8:40:41 AM DeviceSetupManager 121 None
Device USBSTOR\Disk&Ven_SONY&Prod_Mass_storage&Rev_0310\YT9115VK6R&0 was configured.
Driver Name: disk.inf
Class Guid: {4d36e967-e325-11ce-bfc1-08002be10318}
Driver Date: 06/21/2006
Driver Version: 10.0.10586.0
Driver Provider: Microsoft
Driver Section: disk_install.NT
Driver Rank: 0xFF0006
Matching Device Id: GenDisk
Outranked Drivers: disk.inf:GenDisk:00FF2002
Device Updated: false
Parent Device: USB\VID_0FCE&PID_E1AD\YT9115VK6R
...still need help....
-update-
some mysterious, magical stuff hapened and i entered fastbootmode
can boot recovery and boot.img from fastboot and now everything is fine
<3
thanks everyone
merwinaleman said:
-update-
some mysterious, magical stuff hapened and i entered fastbootmode
can boot recovery and boot.img from fastboot and now everything is fine
<3
thanks everyone
Click to expand...
Click to collapse
dude... PLEASE tell me what mysterious, magical stuff happened?!?!!?!?!? I've been having exactly your issue for days now and can't get past it!!! Please
Ugh. I'm having the same problem. Magical stuff isn't very helpful :/
Boot loop
trechurch said:
~~~~
[~~~~QUOTE=shouqinz;67837866]try enable usb debugging. go to setting, about phone, then scroll to build number. tap it repeadly till ~~~~developer option appear on setting. set enable usb debugging there. and try flash it again.
Click to expand...
Click to collapse
Girlfriend tried to update her Sony Aqua M4 e2306...
she says that the boot loader was unlocked, and she installed the twrp update... and the root check came back rooted.... she powered off the phone and put it on a charger. ...
a few hours later she tried to restart it and only got the Sony Xperia screen then reboot loop.
I've spent 2 days reading everything that i can find and trying various solutions but most won't work because it won't stay connected long enough to use companion, adb, fastboot, bootloader, etc. When the devices is seen by pc it is only for a moment and comes up as a generic MTP device or a hard drive i can't open.
I can get the occasional green or blue lights and sometimes a generic battery symbol by powering off and pressing + or - with power, but never get a recovery or boot load screen... only alternating "sony Xperia" and darkness
also, Emily won't update.
I've tried multiple solutions using different versions of SDK, ADB, sony and xperia Companion, fastboot, bootloader, odin, pwm, and more on multiple machines from XP to Win10, but nothing seems to even make a dent!
I've removed the back and disconnected the battery for 2 hours and am currently trying to research a more physical hack/repair using riff jtag.
i see many people with "boot loop" issue , but no one seems to follow through and say how to get out if you don't have the option of booting to anything....[/QUOTE]
I have the same issue. I have an unlocked bootloader and booted with boot.img. everything was fine for a day or two, and when I started to factory reset my phone it is causing bootloop issues. sony logo and black screen. It never appears on my computer when connected to use adb. Any idea on how to fix this?
My mob is not able to flsh the stock rom......der s a error showing cannot open bundle....help me out plz
When i do VolumeUp & connect my phone it connects to windows with blue led on phone and after ~6 seconds it just disconnects and shows battery charging thing
Try this, jesus bless you
merwinaleman said:
Well, i've flashed the ftf file downloaded directly from xperifirm {E2306_26.3.A.0.131_R2C_Customized GEL_1294-3902}
-update-
some mysterious, magical stuff hapened and i entered fastbootmode
can boot recovery and boot.img from fastboot and now everything is fine
<3
thanks everyone
then, i've try to install root (following a tutorial for this device and this comp.) but i could not enter to FASTBOOT MODE
try using:
- (vol+) + (plug the phone)
-(power btn) + (vol+) + (plug the phone)
-(power btn) + (vol+) + (vol-) + (plug the device)
and the only thing that happened is: -Vibrate + sony logo ---> normal boot
----
Then i try to enter fastboot using the adb command {ADB REBOOT-BOOTLOADER}
but it just reboot normally (sony logo and then start normally)
[[ADB do recognize my device and all drivers were properly installed; but can't enter to fastboot mode]]
---
I've try to reflash my device again, but then i couldn't be able to enter to flashmode
{ with the device off; press vol- and then connect to usb}
after several attempts using - [(power btn) + (vol-)] i entered flashmode and reflash my device...
----
then i activate dev mode: [usb debuggin and OEM UNLOCK]
and try to get to fastboot mode, but the same results...
i got my device recognized by {ADB DEVICES}
but can't get fastboot
-----
Then the user who's helping me told me to reflash using this config
[in excludes section check all except AMSS_FSG, AMS_FS1, AMS_FS2,BOOT DELIVERY, KERNEL. Don't check anything else.]
But i can't get flashmode now... i try all the combinations, try in ubuntu 16, and windows 10... but nothing
the device starts normally nothing wrong.... except well, i can't enter any -mode- now...
any help?
Thanks
Click to expand...
Click to collapse
1. Turn off OEM Unlock
2. Keep USB Debugging on
3. Enter Fastboot mode
4. Done
5. Jesus Bless You
Thymue said:
When i do VolumeUp & connect my phone it connects to windows with blue led on phone and after ~6 seconds it just disconnects and shows battery charging thing
Click to expand...
Click to collapse
I'm having the same issue.
Anoyone knows how to fix? Maybe is a problem of the cable?
PD: Tested with official cabled and turning Off OEM unlock and still the same.
iFlashed said:
I'm having the same issue.
Anoyone knows how to fix? Maybe is a problem of the cable?
PD: Tested with official cabled and turning Off OEM unlock and still the same.
Click to expand...
Click to collapse
also for me :´(
Thales720 said:
also for me :´(
Click to expand...
Click to collapse
Not sure what your problem is exactly but it is most likely a problem with the cable or the s1 driver's(if your using window's?) one or the other ,
However i need to point out that you must have your OEM lock at the SWITCHED ON position(allow the device to be oem unlocked) or you will trip the frp at the next reboot and will have to reflash your firmware unnecessarily , so to sum up Oem unlock at the switched on position
Hi7m3up said:
Not sure what your problem is exactly but it is most likely a problem with the cable or the s1 driver's(if your using window's?) one or the other ,
However i need to point out that you must have your OEM lock at the SWITCHED ON position(allow the device to be oem unlocked) or you will trip the frp at the next reboot and will have to reflash your firmware unnecessarily , so to sum up Oem unlock at the switched on position
Click to expand...
Click to collapse
the drivers are all installed correctly, I tried doing this with the OEM off and on and it did not work
none of the methods works, adb does normal boot
recovery reboot (and other apps) crash or boot normal too
volume (+) and power button only makes the phone vibrate (and sometimes the Sony logo appears)
I can't stress to you enough that Enable Oem need's to be on the "on position" so switch it on (allow the device to be oem unlocked)and leave it alone it's nothing to do with you not being able to get to fastboot. If you trip the frp on your phone you will not be pleased.
with that said with your phone switched on and USB DEBUGGING SWITCHED ON plug into your usb on computer open a command window and input the following command- adb reboot bootloader you will now see your blue light on the phone this means your sony is now ready for you to flash a custom recovery (assuming you have unlocked your bootloader ?)
Hi all,
What I did:
- Install TWRP
- Installed a bad ROM through recovery mode
- #brick
Now:
- Stuck in mi logo bootloop
- I can't get to EDL
- I can get to fastboot, but I can't seem to run any commands on my PC
- I can't get to recovery mode
EDL Mode
- I can't seem to get to EDL mode where the red light flashes
- I have tried going to fastboot --> Removing power --> Power + and Power - and Power. Wait for Mi logo to flash twice, and it goes into "Power off mode"
- When I connect to USB again, it connects to the PC and charges
- In device manager, I can see Xiaomi Composite MDB Interface
- No connectivity over adb command
Fastboot Mode
- I can get into Fastboot
- Connect Fastboot into the PC, I am unable to run any adb or fastboot commands.
- Fastboot devices shows nothing, adb devices shows nothing
- In device manager, I can see Android Bootloader Interface
I've tried many soft options and have read through probably 30+ guides. I have not tried the test point method because I do not want to void my warranty.
Anyone experience this and can help?
Thanks!
Try re-installing the driver and see if those adb/fastboot commands work.
U said u installed TWRP right . Then u can go to recovery by pressing volume up+power button and then install another custom rom or stock rom but if u have unofficial unlocked bootloader then flashing stock rom will relock ur bootloader and device will not bootup.So go for another custom rom like resurrection remix its super stable n smooth too.
Follow these two tutorials.
http ://en.miui.com/thread-274589-1-1 . html
http ://en.miui.com/thread-235865-1-1 . html
To enter EDL mode, you need to unplug the battery, wait 10 seconds, replug it. Then, remove the USB plug, replace it, then while holding both volume + and -, plug the phone in the computer using the original cable.
Make sure to check what you're getting in device manager. If you get USB_BULK, you need to download the drivers. If you're getting diagnostics, you did the earlier procedure wrong so try it again. If you're getting 9008, you've gained access to EDL.
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