Develop Bugs

OTA Update Elephone P8000 stucks at Boot Logo

Hi there,
I just updated P8000 via OTA update and after downloading the Update, the phone restarted and stops at the elephone boot Logo (about 30 min )!!
I did 5 Restarts but every time it hangs at the boot logo...
In the past i did no other updates or flashing ROMS.. nothing!
When i press "Volume Up" and "Power" to Start, i get three Options:
Recovery Mode
Fastboot Mode
Normal Boot
Using Recovery Mode leads to: Symbol Android Robot with "No Order" (in german : "Kein Befehl")
Using Fastboot Mode leads to: Nothing (Recovery Menue stays)
Using Normal Boot leads to: restart and hanging at Elephone Boot Logo
So, I am running out of Options... any ideas?
Cheers, Albert

Same. I tried using the official instructions to flash the stock rom but the SP flash tool stops responding after download button is pressed

a.cid said:
Same. I tried using the official instructions to flash the stock rom but the SP flash tool stops responding after download button is pressed
Click to expand...
Click to collapse
The Hardware of P8000 is pretty cool, but the Software is "§$§"%§""!$%

When you go to recovery mode and get the the android robot symbol. Press again Vol up + Power until you enter to recovery. Make a 3 wipe (data factory , cache and dalvink). Reboot and uninstall the El loader. Use another Loader instead of El Loader

i had the same problem. (in English NO COMMAND) I only flash Eragon ROM again. Sometimes you have to repeate.
AL 6677 - ELEPHONE MUST BE TURN-OFF !!!!!!! and CONNECT USB CABLE REPEATEDLY !!!
After that everything goes according to instructions
https://translate.google.at/transla...-p8000-rooten-und-flashen/&edit-text=&act=url

same problem since OTA my phone is bricked and cant unbrick

neonero said:
When you go to recovery mode and get the the android robot symbol. Press again Vol up + Power until you enter to recovery. Make a 3 wipe (data factory , cache and dalvink). Reboot and uninstall the El loader. Use another Loader instead of El Loader
Click to expand...
Click to collapse
THX a lot, I found only the 2 Options to wipe data factory and cache....... dalvink was not displayed in the menue (screenshot attached)
How to uninstall the EL Loader ?

showshow747 said:
i had the same problem. (in English NO COMMAND) I only flash Eragon ROM again. Sometimes you have to repeate.
AL 6677 - ELEPHONE MUST BE TURN-OFF !!!!!!! and CONNECT USB CABLE REPEATEDLY !!!
After that everything goes according to instructions
THX, I will try to flash Eragon, CM 12.1 is still not available, isn't it?
Click to expand...
Click to collapse

No CM 12.1 is not available yet.
In order to uninstall EI Loader, install first root (superSU), then install ccleaner and you can uninstall EI Loader (In system app)

Hi there, sorry for the revival !
But i got the same problem: OTA update, fail, P8000 blocked on boot screen.
I tried wipe data/factory reset + wipe cache -> nothing changed, still boot screen blocked...
Then, i tried to use flash tool, but, the phone isn't booting, so my pc isn't recognizing the phone..
I'm not even sure that I correctly installed the drivers..
Can i use flash tool even if the phone is blocked to boot screen?
I downloaded this ROM: stock-rom-elephone-p8000-20150907-android-5-1 (this is my first post i can't post URL..)
Because i got some issues with my phone and support told me to try it.
But when i follow the tutorial, launching "donwload" and connecting the phone, nothing happening..
The phone turn on, and display recharging logo, and flash tool still wainting.
Recovery mode -> "No command", Volume up + power is working, i used it to wipe datas
But at the moment, i'm still blocked, since 2 days, i dont know what to do
Can someone help me?
Thank you by advance, i hope my english isn't so bad

Zywoon said:
Hi there, sorry for the revival !
But i got the same problem: OTA update, fail, P8000 blocked on boot screen.
I tried wipe data/factory reset + wipe cache -> nothing changed, still boot screen blocked...
Then, i tried to use flash tool, but, the phone isn't booting, so my pc isn't recognizing the phone..
I'm not even sure that I correctly installed the drivers..
Can i use flash tool even if the phone is blocked to boot screen?
I downloaded this ROM: stock-rom-elephone-p8000-20150907-android-5-1 (this is my first post i can't post URL..)
Because i got some issues with my phone and support told me to try it.
But when i follow the tutorial, launching "donwload" and connecting the phone, nothing happening..
The phone turn on, and display recharging logo, and flash tool still wainting.
Recovery mode -> "No command", Volume up + power is working, i used it to wipe datas
But at the moment, i'm still blocked, since 2 days, i dont know what to do
Can someone help me?
Thank you by advance, i hope my english isn't so bad
Click to expand...
Click to collapse
Yes you can use SPFlash tool evenif the phone stucks in the boot screen. Simply switch the phone off, start SPFlash tool and then connect the phone to usb.
If you follow the instructions from elephone, then your phone should working again: http://bbs.elephone.hk/thread-1037-1-1.html#.VofQ13wvdpo
Cheers

Hi, and thx for the help.
The driver is correctly installed now, i had to allow unsigned drivers in windows parameters.
So, i followed the tutorial, again.
I configured SP flash tool, clicked download, and then connected powered off P8000 with USB.
But, again, the phone displays recharging logo, and flash tool still waiting...
The phone is recharging so the USB is working, so i don't know how to make my PC detect the phone......
Is there a way or a thing that i missed?
thank you..
EDIT: i finally got a timeout error from flashtool..
I missed something, but what !? i can't remove P8000 battery, is there somthing to do to get it detected by windows?
Like a boot mode, or a magic formula... i'm open

For MTK Driver installation:
Did you follow skeletons Guide? http://forum.xda-developers.com/elephone-p8000/help/guide-windows-10-mtk-vcom-usb-drivers-t3264884
I'm sorry to say, that I do not have any experience with windows installation, this problem, because SPFlash tool performes on my 64bit Linux very well, without any driver trouble.
Cheers

Hi,
I'm on windows 8.
I used SP_driver_v2.0, that is an .exe
it's the only driver tips gived in most of tutorial
I allowed unsigned drivers installation, and i correctly installed it.
I tried too use flashtool before and after restarting the PC-> no changes
Flashtool doesnt detect the phone
I start getting crazy..

I have repaired mine, so i'll share
Al6677 said:
Hi there,
I just updated P8000 via OTA update and after downloading the Update, the phone restarted and stops at the elephone boot Logo (about 30 min )!!
I did 5 Restarts but every time it hangs at the boot logo...
In the past i did no other updates or flashing ROMS.. nothing!
When i press "Volume Up" and "Power" to Start, i get three Options:
Recovery Mode
Fastboot Mode
Normal Boot
Using Recovery Mode leads to: Symbol Android Robot with "No Order" (in german : "Kein Befehl")
Using Fastboot Mode leads to: Nothing (Recovery Menue stays)
Using Normal Boot leads to: restart and hanging at Elephone Boot Logo
So, I am running out of Options... any ideas?
Cheers, Albert
Click to expand...
Click to collapse
So the simple way to solve it is flashing the latest stock elephone p8000 ROM, which you can find on google easly
1. as described on other forums, you have to install the adnroid drivers, then get the sp flash tool, and have an un-zipped stock elephone p8000 ROM.
2. if you are stuck at bootloop, do the following to power off the phone so you can flash the ROM
1. Long press power button until power off
2.Do it fast--Press volume Up and then hold power button
3. choose recovery (volume up choose menu, volume down enter)
4. android logo with red triangle is displayed( "no command")
5. hold power button and press volume up
You're in recovery mode
3. select power off
4. open the SP flash tool >go to download tab>opne "scatter loading"( you will find it in the Folder where you unzipped the stock elephone p8000 ROM, if you have more folders there, chose "firmware" folder)
5. on the left side, under scatter loading, you will find a "pull-down" tab - it will be written "download" chose "firmware upgrade" or "upgrade"
6. start the process, then connect your elephone p8000 (it must be powere off) via usb cable to the PC, the process will start,and in less then 5 Minutes you have a factory new Elephone p8000 with the latest good update
7. WATCH OUT- it will erase all your data, absolutely all your data on the phone, except SIM and SD card.
Hope it helped, if not, feel free to ask me =)

Hello,
I have similar problem. Bought P8000 5 days ago. Did update today. Bricked. Stuck at logo ... I tried to flash but SP flush tool but the process isn't starting. When I downloaded ROM I received long list as on the screenshot: kaczorowscy.name/Screenshot.png
I have ubuntu - I see lsusb and dmesg see the phone (it is shut down from recovery menu) but maybe I am missing something ....

Ok here is what id did:
1. Get SP flashtool
2. get newest stock ROM
3. Shut down phone through android recovery menu (start phone with holding volume up, select recovery mode, wait for dead android, hold volume up and unblock button for 3 sec.)
4. Open SP flashtool - use "format all + download" of ROM (unzip and select scatter file from rom) - click start
5. Connect shut downed phone
6. Dot OK! from flashtool
PS. Flashing removed IMEIs - they are both written on the battery - you need to use android service menu to check them with special codes and reboot the phone.
Thanks ALL! :good:

Fix - Recovery Mode
Al6677 said:
Hi there,
I just updated P8000 via OTA update and after downloading the Update, the phone restarted and stops at the elephone boot Logo (about 30 min )!!
I did 5 Restarts but every time it hangs at the boot logo...
In the past i did no other updates or flashing ROMS.. nothing!
When i press "Volume Up" and "Power" to Start, i get three Options:
Recovery Mode
Fastboot Mode
Normal Boot
Using Recovery Mode leads to: Symbol Android Robot with "No Order" (in german : "Kein Befehl")
Using Fastboot Mode leads to: Nothing (Recovery Menue stays)
Using Normal Boot leads to: restart and hanging at Elephone Boot Logo
So, I am running out of Options... any ideas?
Cheers, Albert
Click to expand...
Click to collapse
When I was trying to root my p8000 I couldn't flash a custom recovery, fortunately I discovered that to access recovery on stock android you need to go to the screen with the android and "no command"/"no order" text and hold down Vol+Up and Power for 3~ seconds and then release power, this will boot you into recovery mode, If wiping cache/factory reset isn't enough "fastboot flash recovery <image>.img" SHOULD work now
hope this helped

Am I bricked or is it a step I may have missed? ZenFone 2 ZE551ML

Quick background on situation.
I was running CM13 and I still have TWRP 3.0.2-0. I wanted to try out CM14 or some other variant. I went into TWRP Recovery Mode and Advanced WIPED everything except the Internal Storage and MicroSD (this is probably where I messed up?)
Then went to install and navigate to the new rom and gapps on my microsd card. Well TWRP does not see either. It lists both of them but with 0MB and unselectable. I tried two other card, no go (all FAT32). Tried OTG with 3 different thumb drives, same results. The OS is gone and all I get of course is the white ASUS boot screen loop. ADB doesn't see any devices as well (windows device manager see no new devices when I attached the cable or when I list devices).
The only thing I can boot into is TWRP and I have tried everything to access the SD/OTG without success.
So can I assume I have bricked this thing and must go onto the IntelSOC XFStik procedure? and if so, does having a working TWRP on there force me to deviate from the normal unbrick procedure I have see here and on youtube?
Or is it something really easy that I am missing? I am fairly novice (as noted by my current situation), so maybe it's an easy fix?
Any help is appreciated. Thanks.

@Endosmok
You have LP version twrp recovery? , not the mmbl twrp recovery installed ? which ends in 3.0.2.M1 ??
If you do have 3.0.2.0 for LP bootloader which early versions of CM13 used , then you can fastboot flash stock recovery for 4 20 40 196 in bootloader from here....
https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Thanks go to Shakalaca
To get into bootloader -- from Twrp , select reboot , select power off !
Count to ten after switching off.
Press power and vol + , release power when it vibes , release vol+ at asus screen.
Fastboot flash stock recovery for above LP .196 in bootloader , when flashed --- scroll via vol buttons to recovery and hit power. At the dead android , press power and vol+ together for 4 secs , release vol+
You should be in stock recovery now.
Scroll to `update over adb` and select .
adb sideload LP official firmware from asus for LP .196 or .198
If you need help to get thru this step , just ask:good:

Thanks for the response. I am not sure if I have the LP version. It was done back I think in April of last year... I looked around TWRP and I don't see anything except 3.0.2-0 listed.
So still a little confused. This is how i have been navigating so far....
Power button, volume up... I get to the dead robot. There I can see FASTBOOT MODE is in Red, product name, variant, IFWI, Serial #. The rest is either ? or unknown (bootloader version is unknown).
Then at the bottom i can see 'continue the fastboot process' in blue. With the volume rocker i can select, NORMAL BOOT, POWER OFF, RECOVERY MODE and RESTART BOOTLOADER. I have been select Recovery Mode to get into TWRP. Restart Bootloader gets me back to the dead robot. I would assume this is the bootloader. Normal Boot just gives me the white asus splash where it hangs. In TWRP i can see ADVANCED -> ADB Sideload, I can start and it shows starting adb sideload feature with the blue color scrolling. But still when I connect to the computer I get no connection and nothing is listed when i run adb devices.
My TWRP doesn't let me select either the OTG or MicroSD, they show 0MB but are listed. So no way for me to flash via TWRP. I figured if i can get the computer adb to recognize the phone I can try to sideload via there. But so far my device manager doesn't see a thing, not even an unknown device waiting for their proper drivers.
Where am i going wrong?

Endosmok said:
Thanks for the response. I am not sure if I have the LP version. It was done back I think in April of last year... I looked around TWRP and I don't see anything except 3.0.2-0 listed.
So still a little confused. This is how i have been navigating so far....
Power button, volume up... I get to the dead robot. There I can see FASTBOOT MODE is in Red, product name, variant, IFWI, Serial #. The rest is either ? or unknown (bootloader version is unknown).
Then at the bottom i can see 'continue the fastboot process' in blue. With the volume rocker i can select, NORMAL BOOT, POWER OFF, RECOVERY MODE and RESTART BOOTLOADER. I have been select Recovery Mode to get into TWRP. Restart Bootloader gets me back to the dead robot. I would assume this is the bootloader. Normal Boot just gives me the white asus splash where it hangs. In TWRP i can see ADVANCED -> ADB Sideload, I can start and it shows starting adb sideload feature with the blue color scrolling. But still when I connect to the computer I get no connection and nothing is listed when i run adb devices.
My TWRP doesn't let me select either the OTG or MicroSD, they show 0MB but are listed. So no way for me to flash via TWRP. I figured if i can get the computer adb to recognize the phone I can try to sideload via there. But so far my device manager doesn't see a thing, not even an unknown device waiting for their proper drivers.
Where am i going wrong?
Click to expand...
Click to collapse
You have LP bootloader .
Type in bootloader >
fastboot devices
If recognised, fastboot flash , follow my first reply above , adb wont be recognised until stock recovery is flashed and selected.
Please try to follow what as been already advised
It is V important to follow this from above , dont miss this step ;-
To get into bootloader -- from Twrp , select reboot , select power off !

timbernot said:
You have LP bootloader .
Type in bootloader >
fastboot devices
If recognised, fastboot flash , follow my first reply above , adb wont be recognised until stock recovery is flashed and selected.
Please try to follow what as been already advised
It is V important to follow this from above , dont miss this step ;-
To get into bootloader -- from Twrp , select reboot , select power off !
Click to expand...
Click to collapse
Ok... let me get this straight.... before I sound too dumb...
You want me to go into the bootloader from TWRP (using Reboot > Power Off), even though I get to TWRP via the bootloader (recovery mode) from a power on?
Also, how do I know if fastboot is enabled? Is it when I see FASTBOOT MODE in the color red on the bootloader screen with 'continue the fastboot process' at the bottom?
I've done step by step what you wrote and I get to the bootloader but fastboot devices shows nothing (I've tried different computers/cables as well). I have the computer connect to the phone w/ bootloader screen on with what i wrote about FASTBOOT MODE in red and contine the fastboot process. If that is not correct, let me know. I did hold down the Volume Up for a bit longer
I'm almost thinking I have a hardware issue with my phone. I did replace the mic with a new module prior. I never checked if the usb storage was functioning after. Though it charges via the usb (even connected to a computer it charges but not recognized as a device). I'll have to double check that as well.... not sure why the sd card is not recognized though either... never touched that area. Could be the reason why TWRP can't access either the micro sd or otg?
I do appreciate the help... and i have been reading other threads... just seem to be at a stand still for now... suggestions are always welcome.
update: tried adjust the cable on the mic module ... no dice... replaced with older mic module, no dice... don't think it's a hardware issue.

To get into fastboot mode, power off the phone. Press and hold the volume up button and press the volume button. Once the phone vibrates, let go of the power button, then the volume button. You should not be in fastboot mode. You can choose recovery, power off, etc. with the volume button when in fastboot mode.
Connect the phone to the computer. Do you see any Android devices in device manager? Do you see any unknow devices?
Did you open a command prompt window on your computer, connect the phone in fastboot mode, and type "fastboot devices" (without quotation marks) and press enter to see if the phone is recognized?

audit13 said:
To get into fastboot mode, power off the phone. Press and hold the volume up button and press the volume button. Once the phone vibrates, let go of the power button, then the volume button. You should not be in fastboot mode. You can choose recovery, power off, etc. with the volume button when in fastboot mode.
Connect the phone to the computer. Do you see any Android devices in device manager? Do you see any unknow devices?
Did you open a command prompt window on your computer, connect the phone in fastboot mode, and type "fastboot devices" (without quotation marks) and press enter to see if the phone is recognized?
Click to expand...
Click to collapse
So made some progress here. I think it was a hardware issue now... I put back the new mic module and reconnected the cable and now I can see my SD card and the computer sees it as well in adb and fastboot. That's the good news....
But ran into a new issue when trying to install any ROM from my micro sd card. I get ERROR 7 no matter what ROM I try to install. I have verified that they are the proper roms for my Z00A ZE551ML but still a no go.
What steps should I take next if I can now communicate but get error 7?
Thanks

Which recovery are you using to flash and which file are you trying to flash?

I am using TWRP 3.0.2.-0. Using the install from zip. I select any rom (Nougat Based so far I have tried). RR, Lineage, Octopus, all with the same error.

The phone is running a MM bootloader? What about MM or LP based ROMs?

I believe Timbernot said it was an LP based. I believe I installed about April last year and it was 3.0.2-0
Looks exactly like this
https://forum.xda-developers.com/zenfone-2-laser/development/recovery-twrp-3-0-0-0-recovery-t3319704

You probably need an MM bootloader for custom Nougat ROMs. Did you try any LP-based ROMs?

I have not tried any LP based yet. I will try in a bit and forward the results.
Thanks

Post removed. Let's keep things respectful here folks. :good:
And remember, to each their own.
Cheers,
Darth
Senior Moderator

Soft-brick problem

I restored an lineage os update last night, then i restored a BOOT update that didnt belong to that rom and i`m in bootloop unable to enter recovery or enter bootload, my phone responds only to power button+ volume up ( it restarts), tried to connect fastboot and i get that device isnt found( its connected to usb ports, i installed htc sync manager for htc drivers)
What can i do to go into bootloader, because if i get there i flash twrp then restore the correct rom, but now its just bootloops in RR remix( it doesnt restart itself just loading loading )
Can i get some help with right drivers or something that i could use that command" adb reboot bootloader" and it wont answer with device not found
P.S I get the device in device manager but in adb just says "device not found"
P.S2 Close the thread, i let the phone fully discharge then Volume down + power and it entered fastboot and i was able to get to recovery, nvm

Callliope said:
my phone responds only to power button+ volume up ( it restarts)
Click to expand...
Click to collapse
I know you fixed the problem, but for future reference, in the above scenario, as long as you can force a reboot (power+vol up); the moment the screen goes black to reboot, just slide your finger to vol down (no need to hold power button any longer) and keep holding it; and the phone will go to bootloader.
Callliope said:
Can i get some help with right drivers or something that i could use that command" adb reboot bootloader" and it wont answer with device not found
P.S I get the device in device manager but in adb just says "device not found"
Click to expand...
Click to collapse
adb would never have worked in the condition your phone was in. The phone needs to be booted to OS or custom recovery for adb to work.

How to root TP-LINK NEFFOS Y5L ANDROID 6.1

Hi everyone. Just like in the title of my post. I've just bought a TP-LINK NEFFOS Y5L smartphone, and I started to looking information, how I can get root for this device. And I found it:
https://morfitronik.pl/android-root-smartfona-neffos-y5l-tp-link/
Sad that this site is`t online anymore, but u can find it on github or gitlab.
I've flash this recovery, and it's working fine. The next step to root was to download the zip package from the chainfire site (currently abandoned, but u may use magisk from xda) :
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Latest MAGISK:
https://github.com/topjohnwu/Magisk/releases/download/v16.0/Magisk-v16.0.zip
Well, I've done it. It's working, and I have root on Android 6.1.
Here it is :
View attachment recovery-neffos-y5l-tp-link-twrp.apk
u will have to change extention of file from *.apk to *.img due to xda registration of size file uploaded.
Tutorial how to do this:
https://youtu.be/SfkbkcXSa2M
And if u want to buy me a beer, that is my account number:
PL 37 1020 4317 0000 5402 0389 9689
IBAN BPKOPLPW
Thanks a lot for your support.

How did you flash that twrp recovery...:laugh:

I just flash this recovery via fastboot mode.

TuanPengarah said:
How did you flash that twrp recovery...:laugh:
Click to expand...
Click to collapse
U may also try to boot your phone in this recovery throu fastboot boot image.img

Hello,
I am a bit new... It seems I can't use flashboot mode.
I have DL ADB, then when I key : /adb devices, I see my Y5L.
Then I try to relaunch my device by pressing the VOL + / Restart button => I reach a picture of android and 3 japanese (or chinese characters).
When I plug the device to my PC, it seems that nothing happen (like it was not recognised by the PC).
Du you have any idea?
Best regards

Hello. It is a very annoying thing, but also very simple to solve. If u see the broken robot when u trying to enter to recovery, u must push and hold power button and short press vol+. But if you want to go to recovery or fastboot mode, u don't have to power down your phone. Just go to cmd (or whatever) console and write:
" adb reboot recovery" to boot up you device in recovery mode or
"and reboot bootloader" to boot into fastboot mode
Seeia.

Greetings!
The custom TWRP link does not seem to work as it should be. Either that or I am missing something
Could you please re-upload the recovery file?
Thanks!
"edit: I found it"

Can someone write a tutorial please, it's the first time i try to root with TWRP and i don't understand if the bootloader method for emample is from the device or from the pc because i can enter to the official android device (Y5L ANDROID 6.0.1 ) recovery menu but when i choose to boot at bootloader the phone freeze at the logo. Thanks a lot for any help.

Calaad said:
Hello,
I am a bit new... It seems I can't use flashboot mode.
I have DL ADB, then when I key : /adb devices, I see my Y5L.
Then I try to relaunch my device by pressing the VOL + / Restart button => I reach a picture of android and 3 japanese (or chinese characters).
When I plug the device to my PC, it seems that nothing happen (like it was not recognised by the PC).
Du you have any idea?
Best regards
Click to expand...
Click to collapse
1. pressing the VOL up + Power button => reached a picture of android and 3 Chinese characters (means no command !)
2. pressing again the VOL up + Power button => then you will reached recovery mode.

I had seem this polish method but I get afraid because there is no method to recovery to original rom.
I hope to see a custom rom in next days.

thanks

Hi, I'm trying to install the custom bootloader but after running:
abd reboot bootloader
the phone gets stuck on the tp-link logo.
Trying with volume-up + power shows the broken android logo, from there, holding power + vol-up gets me to recovery but neither fastboot nor adb detect the device. Selecting the "reboot to bootloader" option there ends in the same lock on the tp-link logo.
(I did activate the "unlock bootloader" in developer options.)
Any ideas on how to proceed? thx in advance.

TieSKey said:
Hi, I'm trying to install the custom bootloader but after running:
abd reboot bootloader
the phone gets stuck on the tp-link logo.
Trying with volume-up + power shows the broken android logo, from there, holding power + vol-up gets me to recovery but neither fastboot nor adb detect the device. Selecting the "reboot to bootloader" option there ends in the same lock on the tp-link logo.
(I did activate the "unlock bootloader" in developer options.)
Any ideas on how to proceed? thx in advance.
Click to expand...
Click to collapse
Yeah i also had this problem, open at the android menu your phone and make sure you have enable developer settings and USB Debugging, install Wondershare MobileGo at your pc ( you don't need to install the app at your phone) and connect your phone with the pc, wait to find the drivers at the charge usb selection and after that swap from your phone to all 4 settings of usb connections, mobilego will download 4 drivers total and after that it will read it.
I cant post a link but if you have Chrome to translate from polish to english there is a new simple tutorial, go at the first link at the op post and at the site click at the red text at the beginning next to "twrp" text and translate to english for guide.

sixdiceray said:
Yeah i also had this problem, open at the android menu your phone and make sure you have enable developer settings and USB Debugging, install Wondershare MobileGo at your pc ( you don't need to install the app at your phone) and connect your phone with the pc, wait to find the drivers at the charge usb selection and after that swap from your phone to all 4 settings of usb connections, mobilego will download 4 drivers total and after that it will read it.
I cant post a link but if you have Chrome to translate from polish to english there is a new simple tutorial, go at the first link at the op post and at the site click at the red text at the beginning next to "twrp" text and translate to english for guide.
Click to expand...
Click to collapse
That worked fine. Weird there's no official drivers for download.
Thx.

TieSKey said:
That worked fine. Weird there's no official drivers for download.
Thx.
Click to expand...
Click to collapse
NP and maybe there is but i didn't find any official mobile app management tool from tplink to download.

Thx!

A little offtopic but, any idea on how to enable diagnostic usb port on this device? Nothing in this guide worked so far: https://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059

hi
Why does not this mobile display the number of unread messages (sms)?
Why can not I choose one or two SIM cards in my message program?
Why does not the percentage of battery remaining up the screen?
Why does gps work too slowly?

I Have Successfully installed TWRP But when restart TWRP I got blank image
I have successfully install but when reboot recovery I got blank image that have don't show TWRP Logo

How to root!?
Whit out pc?

OnePlus 7T bricked on Qualcomm Crashdump mode, unable to boot to fastboot

Hey everyone!
So, I've got a HD1903, 8GB RAM 128GB ROM. I updated to OxygenOS 11.0.02, but it was still buggy as hell, so I decided to downgrade. I also had rooted the phone, and decided to get rid of that too. I went to the stock fastboot roms page, downloaded the 10.0.13 ROM and used 'flash-all.bat' file to clear everything. But halfway, it reboots, goes into recovery, then goes to Qualcomm Crashdump mode. That's it. No code or anything, just Qualcomm Crashdump mode, in Blue and Red letters. I tried to hold vol-up, vol-down and power to get into fastboot, but it just loads the fastboot splash screen, then goes back to the same qualcomm crashdump mode screen. Even if i try to hard reset it, by holding vol-up and power, it still goes to the same screen.
Anyone know what to do? I have no idea how to use the 'MSM tool' that everyone talks about, so any guiding advice would be great!
Thanks!

DM me here - https://www.facebook.com/prantor.khan.16 I'll help

HueyT said:
Click to expand...
Click to collapse
I didn't install TWRP, this was all on stock recovery. I also cannot get into fastboot mode.

Msmtool does not need twrp or fastboot--just the software, rom image, drivers, and button combo pushes and holding

OK, so I got it working again, thanks to the advice of reddit users, discord users and the latest msm tool and some googling. I held the vol-up and vol-down buttons for 30 seconds, then connected it to the laptop, with msm running, to a usb 2.0 port, and pressed start. hey presto, it worked. Thanks guys!!

scoped_ar07 said:
Hello
Using the MSM tool is very simple, you just have to download it from this link.
https://drive.google.com/file/d/12y3lO0wIgb2_LSDeVw9x_2C_HjbgZlb_/view?usp=sharing
NOTE: only works on Windows PC
1. Unzip the contents of the RAR into a folder.
2. Run the MSM application
3. Click Start.
4. Connect the cell phone in EDL mode (volume up + down button)
5. Wait for the process to finish (it takes a long time, please be patient)
6. The phone will restart automatically and a message will appear informing you that the equipment is damaged (don't be careful).
Note: The phone should automatically boot into fastboot mode and display a menu, but if it doesn't and instead boots to the T-mobile screen, you need to force shutdown with the power button for several seconds and then manually start it in fastboot mode. (volume up + volume down + power button)
7. Now you need to unlock the bootloader with the command from a Windows CMD window, but you need to download this ADB tool first.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
-Unzip the tool into a folder
-Open a Windows command window, in administrator mode and direct it to the path where you unzipped the ADB tool.
8- Execute this command while the cell phone is connected in Fastboot mode.
fastboot flashing unlock_critical
9- A question will appear on the phone in which you must allow the unlocking.
-With the volume keys select the option to allow it and press the power button.
-At this time your bootloader will be unlocked.
10. Copy the ADB tool files into the folder where ROM 10.0.13 is and replace everything.
11. With the phone connected to the PC, on the command line, run the flash-all.bat file
12. When the phone restarts and the yellow and white letters appear informing that the phone is not safe because the bootloader is unlocked, repeatedly press the (volume down) button until a menu in Chinese appears.
-PC will detect the phone again in fastboot mode and continue to flash
-Leave the phone and PC still until the process is finished.
-In the command line it will indicate that it cannot find files or partitions (ignore it)
13. Finally, the computer will restart automatically and you will be able to use it normally.
Notes:
1. If the phone after the flashing process with MSM starts up and shows the T-mobile logo, don't worry, just turn it off with the power button and connect it in fastboot mode.
2. Do not try to use it with the firmware that I install with MSM, as it will not work properly.
3. Before locking the bootloader again (if you plan to do so) first update via OTA, to the most recent version of Oxygen, otherwise the system will crash again and you will have to repeat the whole process.
Click to expand...
Click to collapse

Stronger1101 said:
Hi
Using the MSM tool is very simple, you just have to download it from this link.
hotdogt_11_O.01_190920 op7t tmo usa patched unlock bootloader.7z
drive.google.com
NOTE: It only works on Windows pc
1. Unzip the contents of the RAR into a
2. Run the MSM application
3. Click Start
4. Connect the cell phone in EDL mode (volume up + volume down button)
5. Wait for the process to finish (it is delayed)
6. A message appears informing that the equipment is damaged, do not be careful.
7- Now you must unlock the bootloader with a command from a windows CMD window, but first you must download this ADB tool.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
-Unzip the tool into a folder
-Open a windows command window, in administrator mode and direct it to the path where you unzipped the ADB tool.
8. Now run this command while the cell phone is connected in Fastboot mode.
fastboo ...
Hi
Using the MSM tool is very simple, you just have to download it from this link.
https://drive.google.com/file/d/12y3lO0wIgb2_LSDeVw9x_2C_HjbgZlb_/view?usp=sharing
NOTE: Only works on Windows PC
1. Unzip the contents of the RAR into a folder
2. Run the MSM application
3. Click Start
4. Connect the cell phone in EDL mode (volume up + volume down button)
5. Wait for the process to finish (it's time consuming, be patient)
6. The phone will restart automatically and a message will appear informing you that the equipment is damaged (don't be careful).
Note: The phone should automatically start in fastboot mode and show a menu, but if it doesn't and instead starts on the T-mobile screen, you must force shutdown with the power button for several seconds and then manually start it in fastboot mode. (volume up + volume down + power button)
7. Now you must unlock the bootloader with command from a windows CMD window, but first you must download this ADB tool.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
-Unzip the tool into a folder
-Open a windows command window, in administrator mode and direct it to the path where you unzipped the ADB tool.
8- Execute this command while the cell phone is connected in Fastboot mode.
fastboot flashing unlock_critical
9- A question will appear on the phone in which you must allow the unlocking.
-With the volume keys select the option to allow it and press the power button.
-At this moment your bootloader will be unlocked.
10. Copy the ADB tool files into the folder where ROM 10.0.13 is and replace everything.
11. With the phone connected to the PC, in the command line, run the file flash-all.bat
12. When the phone restarts and the yellow and white letters appear informing that the phone is unsafe due to having the bootloader unlocked, repeatedly press the (volume down) button until a menu in Chinese appears.
-The PC will detect the phone again in fastboot mode, and continue flashing
-Leave the phone and the pc still until the process is finished.
-In the command line it will indicate that it cannot find files or partitions (don't pay attention)
13. Finally the equipment will restart automatically and you will be able to use it normally.
Notes:
1. If the phone after the flashing process with MSM starts up and shows the T-mobile logo, don't worry, just force it off with the power button and connect it in fastboot mode.
2. Do not try to use it with the firmware that I install with MSM, as it will not work properly.
3. Before blocking the bootloader again (if you plan to do it) first update via OTA, to the most recent version of Oxygen, otherwise it will crash the system again and you will have to repeat the whole process.
Click to expand...
Click to collapse
Oh wow that was a long and well defined post. Thank you for taking the time to type it out.
As it happens, I fixed my issue already (IDK if there's a solved flair for XDA or something?). I downloaded the latest (10.0.15) MSM Tool from the XDA page, held the vol-up and vol-down for 30 seconds this time (as per advice from discord users) got the phone into edl mode, connected to a usb 2.0 port and let msm tool do it's thing. Everything is working perfectly now.

I've got the same problem but even with holding vol up+down buttons for 30 seconds I can't get into edl mode. It boots into qualcomm crashdump mode. I don't have fastboot working, I only see fastboot splash screen for a sec and then qualcomm crashdump mode appears. Could someone help?! As soon as usb cable is connected phone boots into qualcomm crashdump mode. no matter what I do.

Also do service centers undertake servicing for such phones which bricked because of badly flashed roms.

Āryan-9909 said:
Also do service centers undertake servicing for such phones which bricked because of badly flashed roms.
Click to expand...
Click to collapse
Yes, theyll just change out the motherboard

HueyT said:
Yes, theyll just change out the motherboard
Click to expand...
Click to collapse
If they're going to just change the motherboard, I wonder what the EDL mode is meant for. Anyways, I won't go for motherboard change one can buy a new and better phone at that kinda price.
Anyways, I Fixed it through EDL method, you have to hold vol up and down simultaneously and immediately connect to windows (while still holding both buttons) via original USB cable. Check with Device manager if your device shows up, it's easy enough but you might have to keep trying to you get it right. Thereafter, disable driver verification in windows and if Sahara communications failed message appears in msm tool, turn off phone and repeat the procedure again.

The repair peeps only fix hardware and not software. It's more cost effective for them to swap out hardware faster than messing with msmtool like us

Āryan-9909 said:
I've got the same problem but even with holding vol up+down buttons for 30 seconds I can't get into edl mode. It boots into qualcomm crashdump mode. I don't have fastboot working, I only see fastboot splash screen for a sec and then qualcomm crashdump mode appears. Could someone help?! As soon as usb cable is connected phone boots into qualcomm crashdump mode. no matter what I do.
Click to expand...
Click to collapse
OK, so you won't get any confirmation that you're in EDL modem you just have to wing it. What I did, I first opened the MSM tool on my laptop, connected the USB side to the laptop at a USB 2.0 port, and kept the USB-C side within easy reach. I held the buttons down with one thumb for 30-35 seconds, and while still holding them down with one hand, i connected the cable to the phone and clicked enum in MSM, it showed connected so I let the buttons go, and it didn't restart. I clicked start, and it worked for me.

scoped_ar07 said:
OK, so you won't get any confirmation that you're in EDL modem you just have to wing it. What I did, I first opened the MSM tool on my laptop, connected the USB side to the laptop at a USB 2.0 port, and kept the USB-C side within easy reach. I held the buttons down with one thumb for 30-35 seconds, and while still holding them down with one hand, i connected the cable to the phone and clicked enum in MSM, it showed connected so I let the buttons go, and it didn't restart. I clicked start, and it worked for me.
Click to expand...
Click to collapse
You don't have to hold buttons for that long, you can immediately connect it to PC. There is usually a sound to indicate that a new device has been connected to windows, you can also keep device manager open for confirmation. This video really helped.

After receiving a " qualcomm crash dump" , I was able to boot into recovery. Then I had done a factory reset.
Phone turns on fine, charges as well.
Although, On my Laptop / Desktop it does not see the phone within MSM, ASs well as ADB, Fastbootd or device manager.
I have the correct drivers downloaded.
Ideas ?

hightech316 said:
After receiving a " qualcomm crash dump" , I was able to boot into recovery. Then I had done a factory reset.
Phone turns on fine, charges as well.
Although, On my Laptop / Desktop it does not see the phone within MSM, ASs well as ADB, Fastbootd or device manager.
I have the correct drivers downloaded.
Ideas ?
Click to expand...
Click to collapse
Qualcomm 9008 drivers too?

HueyT said:
Qualcomm 9008 drivers too?
Click to expand...
Click to collapse
Yes.
I went ahead and ran another factory reset via recovery, no luck.

New cable, another PC?

HueyT said:
New cable, another PC?
Click to expand...
Click to collapse
Tried both, my desktop would always connect, adb, fastboot, etc.
I had just just freshly installed oneplus drivers including qualcomm on my laptop. Device was not recognized before driver installation or after.
Figure id try on my Mac, and linux laptop. no dice.
ADB is enabled.
Here are the drivers that are installed on my PC ( I enabled hidden devices, in order to see them ) These were recognizing prior to " qualcomm crash dump" . Not phone will not even be seen