I tried to put the CM10 on my phone, after installing the zip in recovery mode, I rebooted the device and it never returned to start. Does not show a single light. Do not enter in any way with any combination. When I connect by usb the only thing that appears in device manager is "apx device." Already tried so many things and nothing worked.
anyone have any idea what's going on?
by the way, I tried a lot here in xda before opening a thread.
is your bl unlocked?
Rudjgaard said:
is your bl unlocked?
Click to expand...
Click to collapse
yes
does it vibrate? does it turn on? can you control it through adb? can you enter sw mode?
Rudjgaard said:
does it vibrate? does it turn on? can you control it through adb? can you enter sw mode?
Click to expand...
Click to collapse
No, no, no and no. the only sign of life when it is connected to the pc. Appears "apx" in device manager.
Yeah you are in apx mode, which is basically the boot section of the nvidia tegra chipset.
You should be able to boot normally by unplugging the phone, remove battery for a few seconds, reinsert and hold power button for about 10 seconds
Also try holding power and vol+ (hold them a while) you should be able to boot into normal recovery
Rudjgaard said:
Yeah you are in apx mode, which is basically the boot section of the nvidia tegra chipset.
You should be able to boot normally by unplugging the phone, remove battery for a few seconds, reinsert and hold power button for about 10 seconds
Click to expand...
Click to collapse
I've try that but dont work.
In device manager the apx device is it properly installed or does it have the triangle?
When it first connected as apx device it probably asked you for drivers, i doubt you installed them.
I don't know if the apx drivers for the 04 are out already, check these terms in xda i know some people have been working on them.
Maybe you can find them here
If the device isn't bricked you are in a situation in which you should be able to flash stuff.
For some this method worked:
Try turn off phone
take battery out
hold vol- and put usb cable into phone
if s/w mode starts put battery in and flash kdz
Otherwise check this thread out
or this
I have to go out and can't follow you for a while, sorry
Rudjgaard said:
In device manager the apx device is it properly installed or does it have the triangle?
When it first connected as apx device it probably asked you for drivers, i doubt you installed them.
I don't know if the apx drivers for the 04 are out already, check these terms in xda i know some people have been working on them.
Maybe you can find them here
If the device isn't bricked you are in a situation in which you should be able to flash stuff.
For some this method worked:
Try turn off phone
take battery out
hold vol- and put usb cable into phone
if s/w mode starts put battery in and flash kdz
Otherwise check this thread out
or this
I have to go out and can't follow you for a while, sorry
Click to expand...
Click to collapse
it have the triangle, but i jus want it in normal mode. I dont want that apx mode so i dont need the drivers. But tks for every thing
condegil said:
it have the triangle, but i jus want it in normal mode. I dont want that apx mode so i dont need the drivers. But tks for every thing
Click to expand...
Click to collapse
The only way for you to get connected in APX is without battery, connect to PC while pressing vol- & vol+.
Anyway... why you want to do that? APX mode doesn't work in JB.
Ok... I got it.
Did you tried to deactivate the APX device in device manager?
You can try to performe the bootloader unlock again (run adb and connect the phone while the program wait for device...)
http://www.4shared.com/rar/HFf4newq/LGO4X-UNLOCK-BOOTLOADER.html (instructions inside).
Or try to get in SW mode by trying untill it works... (connect to PC while pressed vol-).
Any update on the problem?
Rudjgaard said:
Any update on the problem?
Click to expand...
Click to collapse
No, i think what happened was that all the firmware is erased and this naturally gave access to apx that should be hidden by the software. Probably there was some error when I wipe to put the CM10. I see no other explanation.
The phone is actually mine. Already sent it to warranty hoping they'll fix it.
Resuming, the phone went unexpectadly in APX mode and havent found a way of quitting that mode, couldn't boot S/W neither bootloader.
And btw the phone is carrier locked and to be honest I'm not sure if it might be part of the problem or not. Anyway in about two weeks the phone should be back and hopefully fixed. If not I'll check here for some more help guys, thanks for attetion so far
Hello everyone,
It seems that my worst nightmares came up, and got my device bricked while trying to flash it to a stock ROM (had a custom multilingual ROM installed by the chinese seller), and now it's in a strange stage, as Windows detects the Qualcomm port, but adb can't see it.
The adb devices list is in blank, and QPST detects everything, but when trying to flash the device, the error message on the screenshot appears.
Also tried to do it with MiFlash, but didn't worked too.
Any idea about how to solve this?
Thank you in advance for your help.
P.D.: My device is in black screen, so no menu or anything.
P.D.2: Already downloaded the Android SDK in order to try it's ADB, but it didn't worked too.
Now after some research, I found out that the "ADB interface" is not showing in Windows device manager
I tried to install it manually, but can't find a way to get it working, and after the flash, USB debugging was set on, so can't figure out what could be happening...
Is it possible it's completely dead?
Any idea?
Just to say that I have tried multiple combinations while plugging the device to the PC, and didn't worked...
I mean, the PC seems to react, but always with the same end, only shows the Qualcomm port 9008, nothing about the adb...
Getting out of ideas, anyone more has some?
did you start the tool with admin rights?
read a Little bit here
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/
if you have a Z2 pro take this
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
Zukunft said:
did you start the tool with admin rights?
read a Little bit here
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/
if you have a Z2 pro take this
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
Click to expand...
Click to collapse
Yeah, I already started the cmd with admin rights, but the problem is that adb does not works, as the device is not turning on.
As you can check in my first post, in the screenshot, after running the "adb devices" command, it doesn't gives any kind of error, just returns a blank list.
Noggin said:
Yeah, I already started the cmd with admin rights, but the problem is that adb does not works, as the device is not turning on.
As you can check in my first post, in the screenshot, after running the "adb devices" command, it doesn't gives any kind of error, just returns a blank list.
Click to expand...
Click to collapse
adb will never recognized it, in 9008 mode or it's called EDL, the only program that recognized the port is QFIL / Miflash. if you get an error when flashing you must reset your phone again to repeat the process by pressing power button for a couple seconds. if your bootloader already unlocked that must be simpler to do, just press power button for a couple minutes until shor vibration then press vol up + vol down and connect to usb at the same time..
arif_kholid said:
adb will never recognized it, in 9008 mode or it's called EDL, the only program that recognized the port is QFIL / Miflash. if you get an error when flashing you must reset your phone again to repeat the process by pressing power button for a couple seconds. if your bootloader already unlocked that must be simpler to do, just press power button for a couple minutes until shor vibration then press vol up + vol down and connect to usb at the same time..
Click to expand...
Click to collapse
Thanks for the info, I've tried the vol + and vol- buttons after the short vibration, and the PC does not detect the device...
Is it there any other way to get the device detected by the PC?
Actually, the only thing the device does, is the following:
After pressing the PWR button for around 5-7 seconds, it makes a short vibration and the notifications led makes a flash in green colour, but nothing more... If you keep pressing it, around 7-8 later, it makes a litte bigger vibration and a flash on green too... And if you continue, it does on, and on, and on...
Any idea? Anyone told me about getting a Xiaomi Deep flash cable, but I'm not sure about if that will work or not...
Noggin said:
Thanks for the info, I've tried the vol + and vol- buttons after the short vibration, and the PC does not detect the device...
Is it there any other way to get the device detected by the PC?
Actually, the only thing the device does, is the following:
After pressing the PWR button for around 5-7 seconds, it makes a short vibration and the notifications led makes a flash in green colour, but nothing more... If you keep pressing it, around 7-8 later, it makes a litte bigger vibration and a flash on green too... And if you continue, it does on, and on, and on...
Any idea? Anyone told me about getting a Xiaomi Deep flash cable, but I'm not sure about if that will work or not...
Click to expand...
Click to collapse
i've already tried xiaomi deep flash cable, and its work on my z2 plus, that's how to force phone into 9008 mode.. and also, dont add space between folder names where your firmware files there or there will always sahara fail
Hey man!
I had the same Problem!
Sahara error, no reaction from device, black screen, port recognized in qfil etc.
I found out that this behaviour of the device means, that it is in EDL-mode.
what helped ma was:
1) Unplug everything.
2) Set up the QFIL Tool completely, but do not hit "Download Content".
3) Try to "reboot" the Zuk Z2 Pro by pressing the power button for several seconds. Kind of resets everything.
4) Plug in USB
5) execute: "adb reboot edl" via adb
6) unplug USB
7) plug in USB and immediately (within a second!) hit the "Download Content" buton, just after it is clickable.
8) dowload should start without sahara error
Hope it works! :good:
Well, finally, I talked with the aftersales dpt from the shop where I got the device, and returned it, and incredibly it seems it was defective.
The guy from the tech dpt said that it wasn't supposed to die that way, so they returned me a brand new device, and fortunately it's up to date with ZUK's last official ROM.
Thank you everyone for your ideas and help, now I can enjoy this great device
My Zuk Z2 plus got stuck after TWRP, I need help badly.
sirmclord said:
Hey man!
I had the same Problem!
Sahara error, no reaction from device, black screen, port recognized in qfil etc.
I found out that this behaviour of the device means, that it is in EDL-mode.
what helped ma was:
1) Unplug everything.
2) Set up the QFIL Tool completely, but do not hit "Download Content".
3) Try to "reboot" the Zuk Z2 Pro by pressing the power button for several seconds. Kind of resets everything.
4) Plug in USB
5) execute: "adb reboot edl" via adb
6) unplug USB
7) plug in USB and immediately (within a second!) hit the "Download Content" buton, just after it is clickable.
8) dowload should start without sahara error
Hope it works! :good:
Click to expand...
Click to collapse
I will tell my issue
I bought this device this July month, I was encouraged seeing you guys did a lot of flashing, I thought I could flash myself but it became a nightmare now.
I am not that much technical so please bare my usage of words below, but I need a real help.
I was doing the basic TWRP for getting the AICP ROM 12.1 but after wiping the data from TWRP my device doesnt get recognized for the Sideload and I did whatever I can but it doesnt detect my phone, so I am having a screen with Start "Green" which is showing the device status as unlocked and when I click on Recovery it goes to the Zuk logo and doesn't have any sign after that.. stuck really
I tried using QFIL but my device detects as 900H but not 9008 also adb doesn't detect my device at all after this.
I think I really did a hard brick of my device.
I dont want to loose hope, I want your help really badly.
For those of you who had the same problem don't give up! I was in that same situation and I solved by putting my phone on EDL via this method
https://www.youtube.com/watch?v=2m44xKog-dI
After plugging the phone for the second time and QFIL recognize as EDL mode I clicked on download content as fast as I could so it started to flash the ROM that I spent like 10h trying to figure a way to do it lol. Anyways, the procedure is the same as putting into EDL via adb fastboot, the only difference is that you make it through a "fake" deep flash cable as that guy in the video shows.
Bootloader type = Oxygen (not sure if that is the proper one for the device though)
Bootloader lock = Unlocked via Xiaomi official procedure
USB Debug = Not sure, I'm starting to fear it's off though
Original issue = My phone was bricked. No sound, display or whatsoever.
What did I try?
I followed an unbrick tutorial which made me flash an Oxygen firmware file. After that I get a boot loop. Mi logo and Android loading bar appears and seems to be like that continuously.
I can't access either fastboot or recovery mode. If I try any of the two button combinations I don't even get the Mi logo screen. I see the backlight turn on and nothing happens.
I tried flashing several fastboot roms, stock roms and firmware files I could find, flashing them with different versions of MiFlash. Except for the one I described in step 1 none of them change the situation as described in 'Original issue'.
I need to use the 'test pin method' to even let the computer detect the phone in MiFlash. The phone does not get detected inADB fasboot (which makes sense, as I can't enter fastboot mode anyway).
I'm hoping someone can point me in a direction which leads me to fix my phone. I'm not sure what steps I did to even get to the point where it stopped responding in any way. It has been some time ago, but I think I flashed an Oreo firmware file just before that point.
i did tryied test point (edl mode) and i think either i connect wrong point together or my rom was wrong and my phone can not boot or show anything . when connect to charge it shows key light flashing without any picture in the screen and without any vibration after pushing power button . i either dont have acces to fastboot now . what is wrong with my phone ?
Esemtix said:
i did tryied test point (edl mode) and i think either i connect wrong point together or my rom was wrong and my phone can not boot or show anything . when connect to charge it shows key light flashing without any picture in the screen and without any vibration after pushing power button . i either dont have acces to fastboot now . what is wrong with my phone ?
Click to expand...
Click to collapse
If you find the right points you can get into edl. Did you try a cable already?
Arealhooman said:
If you find the right points you can get into edl. Did you try a cable already?
Click to expand...
Click to collapse
i dont know i connect right point together or not but my phone name changed when connect to pc with xiaomi fastboot installer and i gave my phone to a developer and he install a lot of roms with edl mode ,too but there is no change
Try using edl cable
Arealhooman said:
Try using edl cable
Click to expand...
Click to collapse
i dont need any box tool for use it ?
What do you mean?
Arealhooman said:
What do you mean?
Click to expand...
Click to collapse
boxes like flash you can connect to pc and acces more thing for connecting to your phone
i mean i wont need anything like these except edl cable ?
sorry i ask too many questions
Esemtix said:
boxes like flash you can connect to pc and acces more thing for connecting to your phone
i mean i wont need anything like these except edl cable ?
sorry i ask too many questions
Click to expand...
Click to collapse
Nah it’s k. You still need the right files, but most of the time a edl cable can get you in.
i did tryied edl mode and just black screen does shows. what should i do ? my phone either doesn not vibrate when connect to charge
janus.8x said:
i did tryied edl mode and just black screen does shows. what should i do ? my phone either doesn not vibrate when connect to charge
Click to expand...
Click to collapse
Someone told me the phone got hard problem .
janus.8x said:
i did tryied edl mode and just black screen does shows. what should i do ? my phone either doesn not vibrate when connect to charge
Click to expand...
Click to collapse
hi . I tried to flash the phone a lot but still the phone keys light are just on when I connect the phone to charger and when I disconnected it , it is off even when I push power key
what should I do ?
Hi, I have a new redmi 9c NFC, it has an Mediatek chip, so I can instant unlock bootloader, I installed a MIUI 12.5 Port for this phone "https://forum.xda-developers.com/t/...dmi-9c-nfc-angelica-angelican-stable.4383125/"
I didn't had enough space for GApps I saw a tutorial on YouTube for expand system partition "
"
I deleted partitions, (super, recovery and cache). I accidentally rebooted my phone, and now i'ts on a black screen, no recovery, not fasboot, no vibrations, the only signal of life that I have is when I connect the phone to my computer, It appears like this: "Dispositivo serie USB (COM4)" (It's on spanish because I'm spanish, and sorry for my bad English) I can't use Mi flash or something. PLZ HELP, I'M DESESPERATED
AvZPablo4 said:
Hi, I have a new redmi 9c NFC, it has an Mediatek chip, so I can instant unlock bootloader, I installed a MIUI 12.5 Port for this phone "https://forum.xda-developers.com/t/...dmi-9c-nfc-angelica-angelican-stable.4383125/"
I didn't had enough space for GApps I saw a tutorial on YouTube for expand system partition "
"
I deleted partitions, (super, recovery and cache). I accidentally rebooted my phone, and now i'ts on a black screen, no recovery, not fasboot, no vibrations, the only signal of life that I have is when I connect the phone to my computer, It appears like this: "Dispositivo serie USB (COM4)" (It's on spanish because I'm spanish, and sorry for my bad English) I can't use Mi flash or something. PLZ HELP, I'M DESESPERATED
Click to expand...
Click to collapse
You can use instead SPFT.
I used SP Flash Tool. I watched a YouTube tutorial:
I didn't had luck, It said me : PTM changed from the ROM; It must be downloader. Please select "Formato Allí + Download" scene and try again
It didn't work on Format All . It grave me this error: ERROR : STATUS_UNKNOWN_STORAGE_SECTION_TYPE (0xC003000C). [HINT]:
I tried to search solutions but nothing.
Well, it is very risky to use this function, it may format the calibration data, and your IMEI, within other things, so you shouldn't have to try this option, before to take a backup and even be sure, that this backup will, really, restore the things.
Try flashing only the preloader first, then go for the rest of partitions. You also have this tool to back up every thing that is not corrupted, https://github.com/bkerler/mtkclient
SubwayChamp said:
Well, it is very risky to use this function, it may format the calibration data, and your IMEI, within other things, so you shouldn't have to try this option, before to take a backup and even be sure, that this backup will, really, restore the things.
Try flashing only the preloader first, then go for the rest of partitions. You also have this tool to back up every thing that is not corrupted, https://github.com/bkerler/mtkclient
Click to expand...
Click to collapse
Ok, I have a problem, I think that my phone is bricked forever. I watched a tutorial
It's a bad quality tutorial
It surprisely worked!! I obviously used Redmi 9c NFC files.
When the phone were flashing, my cat passed trough the cable and he desconnected it. It only flashed bootloader, but still no fastboot or something else Now, if I connect the mobile to the computer it says: The usb device is not recognized.
In the device manager it appears as: Unknown USB device (Device descriptor request error).
It has error code 43
I'm going to press the power button or something and try it again
AvZPablo4 said:
Ok, I have a problem, I think that my phone is bricked forever. I watched a tutorial
It's a bad quality tutorial
It surprisely worked!! I obviously used Redmi 9c NFC files.
When the phone were flashing, my cat passed trough the cable and he desconnected it. It only flashed bootloader, but still no fastboot or something else Now, if I connect the mobile to the computer it says: The usb device is not recognized.
In the device manager it appears as: Unknown USB device (Device descriptor request error).
It has error code 43
I'm going to press the power button or something and try it again
Click to expand...
Click to collapse
Well, what the guy is doing, is basically, installing the LibUSB dev filters, to get device recognized, and can bypass the DA/SLAA authentication, then it is flashing a firmware using SPFT, this usually, even in a serious bricking state, is not that hard, BUT, your main issue now, is that you repartitioned some essential images onto your device, so the safe way to keep it trying will be flashing once by once, every partition to detect exactly, which of them were altered (I guess super and data), flash first the preloader, and then proceed one by one.
For sure the option format all will fix your device but unfortunately, this will erase the calibration data and your IMEI, mainly, you have the option that you can back up all your partitions, no matter super nor recovery nor userdata, but the others, using the CLI tool I provided the link, after that you should perform a format all, and then restore them.
SubwayChamp said:
Well, what the guy is doing, is basically, installing the LibUSB dev filters, to get device recognized, and can bypass the DA/SLAA authentication, then it is flashing a firmware using SPFT, this usually, even in a serious bricking state, is not that hard, BUT, your main issue now, is that you repartitioned some essential images onto your device, so the safe way to keep it trying will be flashing once by once, every partition to detect exactly, which of them were altered (I guess super and data), flash first the preloader, and then proceed one by one.
For sure the option format all will fix your device but unfortunately, this will erase the calibration data and your IMEI, mainly, you have the option that you can back up all your partitions, no matter super nor recovery nor userdata, but the others, using the CLI tool I provided the link, after that you should perform a format all, and then restore them.
Click to expand...
Click to collapse
Thanks for the reply!!
I can't backup, Flash or something, my pc down't detect my phone, it's unrecognised, by device manager or in lib usb, I changed the usb cable and port but nothing, I can't connect the phone to the pc.
If I get the possibility of connect the phone to the pc successfully, I would try that! ( I reset PC but nothing)
I sent a (tablet quality) video reporting the problem a bit.
AvZPablo4 said:
Thanks for the reply!!
I can't backup, Flash or something, my pc down't detect my phone, it's unrecognised, by device manager or in lib usb, I changed the usb cable and port but nothing, I can't connect the phone to the pc.
If I get the possibility of connect the phone to the pc successfully, I would try that! ( I reset PC but nothing)
I sent a (tablet quality) video reporting the problem a bit.
Click to expand...
Click to collapse
Windows not recognizing is normal in this state because your device is trying to boot to system, then Windows can't detect it as MTP BUT to have the device detected properly for preloader mode, you firstly have to install all the proper MediaTek drivers, then, from LibUSB entries listed choose one from all, i.e. Dispositivo Compuesto USB, it doesn't matter that it is the right entry, but this entry, if it is succesfully changed, would serve to recognize it, always that the VCom, and preloader drivers are properly installed.
I installed all LibUSB entries, install mtk drivers but nothing, it says (the same as before):
USB device not recognized
The last USB device you connected to this computer did not work properly, and Windows did not recognize it.
Remember that I flashed bootloader (I don't know what it is for you, but in case it causes a conflict with the IMEI or I don't know)
AvZPablo4 said:
I installed all LibUSB entries, install mtk drivers but nothing, it says (the same as before):
USB device not recognized
The last USB device you connected to this computer did not work properly, and Windows did not recognize it.
Remember that I flashed bootloader (I don't know what it is for you, but in case it causes a conflict with the IMEI or I don't know)
Click to expand...
Click to collapse
You have to keep pressed the buttons, even while the device is connected to the PC, your device will pass through various states, then quickly you have to release your fingers.
Well, preloader is a kind of bootloader, in MediaTek.
Use this tool, to bypass, https://androidfilehost.com/?fid=17825722713688275528 when you have success from the tool, then just run SPFT, uncheck the options LIB USB DA match storage and Storage Life Cycle, also check USB full speed.
I'm going to try it right now. Im' going to edit this for give the results
1st edit: I didn't start yet to bypass that, but, it has password
2nd edit: I pressed power button for 15 seconds and pw button + vol up for 10 seconds but nothing, with all drivers and all, still at: unknown usb device
AvZPablo4 said:
I'm going to try it right now. Im' going to edit this for give the results
1st edit: I didn't start yet to bypass that, but, it has password
2nd edit: I pressed power button for 15 seconds and pw button + vol up for 10 seconds but nothing, with all drivers and all, still at: unknown usb device
Click to expand...
Click to collapse
The tool is mirrored from other sites though https://gsmatoztool.com/mtk-auth-bypass-tool-v26-new-update-latest-tool/
Press the three buttons, but pay attention to the sound of PC and to device manager when something change.
Also download the UsbDk 64-Bit installer from the site I linked, with mtk-client tool you also can do some things.
SubwayChamp said:
Press the three buttons, but pay attention to the sound of PC and to device manager when something change.
Click to expand...
Click to collapse
I pressed the 3 buttons at the same time by 5 minutes but nothing, no sound, no changes on device manager
AvZPablo4 said:
I pressed the 3 buttons at the same time by 5 minutes but nothing, no sound, no changes on device manager
Click to expand...
Click to collapse
The way to use the tool I linked is, clicking on bypass and pressing the two volume buttons, but probably you have to get your device listed in LibUSB, and quickly, install it, otherwise you won't be able to use SPFT.
This is the guide to get the things working, read carefully every step, if it's needed, then uninstall all the drivers and reinstall them, just what you need. https://forum.xda-developers.com/t/...india-6s-using-spflash-tool-for-free.4222027/
SubwayChamp said:
The way to use the tool I linked is, clicking on bypass and pressing the two volume buttons, but probably you have to get your device listed in LibUSB, and quickly, install it, otherwise you won't be able to use SPFT.
This is the guide to get the things working, read carefully every step, if it's needed, then uninstall all the drivers and reinstall them, just what you need. https://forum.xda-developers.com/t/...india-6s-using-spflash-tool-for-free.4222027/
Click to expand...
Click to collapse
Nope, I installed all, but when I connect it (vol up + vol down) the same, usb not recognized. This is a redmi 9C NFC, that realme has the same mtk chip, but it might change on this xiaomi
AvZPablo4 said:
Nope, I installed all, but when I connect it (vol up + vol down) the same, usb not recognized. This is a redmi 9C NFC, that realme has the same mtk chip, but it might change on this xiaomi
Click to expand...
Click to collapse
This is a generic guide that applies for any MediaTek device, I had Realme and Xiaomi. Try combining other hardware buttons, pay attention to this: you should keep pressing (even blindly because of no sign of life) assuming that your device is either on or off, and interchanging the buttons.
SubwayChamp said:
This is a generic guide that applies for any MediaTek device, I had Realme and Xiaomi. Try combining other hardware buttons, pay attention to this: you should keep pressing (even blindly because of no sign of life) assuming that your device is either on or off.
Click to expand...
Click to collapse
I kept pressing vol up + vol down for like 10 min, but, nothing
AvZPablo4 said:
I kept pressing vol up + vol down for like 10 min, but, nothing
Click to expand...
Click to collapse
It's not a matter of time, if after 15 seconds or around, you don't hear something either from your PC or your device, then clearly, it's not working.
What I'm trying to say is, that you have to press all the modes available, PWR + vol. down, PWR + vol. up, both volume buttons, three buttons, all that doing it blindly because you can't see something onto your display, so no sign of life.
To better understand what I'm trying to say, suppose that your device is on, then make the combination keys, to quickly power off your device, and pressing rapidly the combination keys to enter to preloader mode, but again, you have to do it BLINDLY, just assuming that your device is on, and after, if no results, the other way around, assuming that your device is off, just do the combination keys, if your device is off, then pressing the three buttons around 10 seconds, then your device can tend to power on, in this short time you have to press, only the two volume buttons and release the PWR button, do you understand? I have bricked my Redmi Note 9 some year ago, and I have really, really bricked my Realme 7, and I recovered this way.
SubwayChamp said:
It's not a matter of time, if after 15 seconds or around, you don't hear something either from your PC or your device, then clearly, it's not working.
What I'm trying to say is, that you have to press all the modes available, PWR + vol. down, PWR + vol. up, both volume buttons, three buttons, all that doing it blindly because you can't see something onto your display, so no sign of life.
To better understand what I'm trying to say, suppose that your device is on, then make the combination keys, to quickly power off your device, and pressing rapidly the combination keys to enter to preloader mode, but again, you have to do it BLINDLY, just assuming that your device is on, and after, if no results, the other way around, assuming that your device is off, just do the combination keys, if your device is off, then pressing the three buttons around 10 seconds, then your device can tend to power on, in this short time you have to press, only the two volume buttons and release the PWR button, do you understand? I have bricked my Redmi Note 9 some year ago, and I have really, really bricked my Realme 7, and I recovered this way.
Click to expand...
Click to collapse
No, i didn't get something, I'm desesperated, you can teamviwer me or something or... I DON'T KNOW
AvZPablo4 said:
No, i didn't get something, I'm desesperated, you can teamviwer me or something or... I DON'T KNOW
Click to expand...
Click to collapse
Not much I can do. I recommended all the best to bypass this. If you have taken it in consideration, then you should sort it out.
- Uninstall all the drivers, reinstall exactly only what you need.
- Be sure that LibUSB is properly installed.
- Install the UsbDK 64 bits installer from the site I linked and try also the mtk-client tool.
- The option Format all except bootloader in SPFT may help, but consider that it may erase your calibration data and IMEI, mainly.
Hi Guys,
I really need help with this one. I have tried almost everything.
Here is my problem.
I have an Rog phone 3 strix edition QUALCOMM based.
I repaired the screen because i dropped the phone.
Everything was fine working well. Me with my big head decided to do an factory reset to wipe everything clean from the phone and then the problem started.
The phone was restarting every time i plugged in a usb c cable. If i wanted to listen to some music on headset wont work because it will end in a bootloop.
Now the phone is stuck in CSC Fastboot mode and PC wont recognized it. The screen will turn on and send me to CSC fastboot but that's it. I can turn it back off.
Can i Revive the phone or is it food for the recycling bin?
Please Help.
Sincerely,
Ayolyas
With some effort you should be able to get back on track - unless it's hardware related to the display change you've done.
Can you do a reboot to bootloader from the boot menu? If you can confirm if you have fastboot access. If you do, RAW flash the device.
Worst case, you force the device into EDL mode and do a flash from there, but leave at as the last option.
If the relpaced display is causing harware issues, that's a bigger problem...
Hi Andrologic,
I cannot reboot to the bootloader. I am stuck in csc fastboot. I was trying to put it in edl mode i even bought an edl cable. But i have no idea how to use it or how to put the phone in edl.
I went back to the repair shop but the phone was working fine when it left the phone shop. The problem started when i decided to go for factory reset.
ayolyas said:
Hi Andrologic,
I cannot reboot to the bootloader. I am stuck in csc fastboot. I was trying to put it in edl mode i even bought an edl cable. But i have no idea how to use it or how to put the phone in edl.
I went back to the repair shop but the phone was working fine when it left the phone shop. The problem started when i decided to go for factory reset.
Click to expand...
Click to collapse
So, when you turn on the device, it falls into CSC FB and you can't navigate anywhere at all from there?
What happens if you try to do a RAW flash from CSC FB?
Flashing it in EDL mode may otherwise be the only option. Power off the device completely. Then hold Vol up+down pressed and connect to the USB side port. You should land with a completely black screen and on your pc see the device identified in 9008 mode - that's EDL. Since you have a flash cable, you can obviously use that too.
Remember you need Qualcom drivers installed to work in EDL mode. There is a guide with steps for EDL flashing somewhere here on the forum. All the steps are explained.
Andrologic said:
So, when you turn on the device, it falls into CSC FB and you can't navigate anywhere at all from there?
What happens if you try to do a RAW flash from CSC FB?
Flashing it in EDL mode may otherwise be the only option. Power off the device completely. Then hold Vol up+down pressed and connect to the USB side port. You should land with a completely black screen and on your pc see the device identified in 9008 mode - that's EDL. Since you have a flash cable, you can obviously use that too.
Remember you need Qualcom drivers installed to work in EDL mode. There is a guide with steps for EDL flashing somewhere here on the forum. All the steps are explained.
Click to expand...
Click to collapse
I cannot navigate anywhere from csc. If i try to reboot bootloader i will end in the same place.
I try to connect like you told me Vol up + down but i ended up at the same place. An raw flash from csc fb how do i do that?
And the steps for edl if you can help where to find those steps because my google history is full off items and still no luck finding the right one.
ayolyas said:
I cannot navigate anywhere from csc. If i try to reboot bootloader i will end in the same place.
I try to connect like you told me Vol up + down but i ended up at the same place. An raw flash from csc fb how do i do that?
And the steps for edl if you can help where to find those steps because my google history is full off items and still no luck finding the right one.
Click to expand...
Click to collapse
Yes, you have flash cable, so getting into EDL shouldn't be an issue any way.
This is a useful video on how to use your flash cable to force the device to EDL:
Just remember you need QCom drivers installed to flash in EDL mode, the normal drivers won't do it in EDL.
What is the device identified as on your PC when in CSC FB? Can you send any FB commands to the device at all? Does 'Fastboot Devices' return your device id? If so, try first to do a RAW flash from the Fastboot state you are stuck at. You don't really want to mess with EDL if you can avoid it. Download one of the RAW rom's from the links here on the forum. Version number doesn't matter as long as it matches with your device version, i.e. WW assuming you're on Global.
ayolyas said:
Hi Guys,
I really need help with this one. I have tried almost everything.
Here is my problem.
I have an Rog phone 3 strix edition QUALCOMM based.
I repaired the screen because i dropped the phone.
Everything was fine working well. Me with my big head decided to do an factory reset to wipe everything clean from the phone and then the problem started.
The phone was restarting every time i plugged in a usb c cable. If i wanted to listen to some music on headset wont work because it will end in a bootloop.
Now the phone is stuck in CSC Fastboot mode and PC wont recognized it. The screen will turn on and send me to CSC fastboot but that's it. I can turn it back off.
Can i Revive the phone or is it food for the recycling bin?
Please Help.
Sincerely,
Ayolyas
Click to expand...
Click to collapse
Have you fix it?
osomakohj said:
Have you fix it?
Click to expand...
Click to collapse
Hi,
Nope. I can get into EDL mode so i think it is hardware related. You can say it is fresh for the garbage.
ayolyas said:
Hi,
Nope. I can get into EDL mode so i think it is hardware related. You can say it is fresh for the garbage.
Click to expand...
Click to collapse
maybe try edl cable maybe it'll work? its very cheap in online store
osomakohj said:
maybe try edl cable maybe it'll work? its very cheap in online store
Click to expand...
Click to collapse
I did use a EDL cable and i also build one but no succes for both.
ayolyas said:
I did use a EDL cable and i also build one but no succes for both.
Click to expand...
Click to collapse
Hope you did the proper way of entering edl mode. btw you can still send that to service center. but first try some other way as your phone still boot