Available: there is a phone, 12/256, DN2103, black screen, recovery and fastboot do not turn on (but the buttons are working), when charging is connected via a USB tester (measures volts, amps and transmitted mAh) and when the power button is pressed for a long time, charging stops for a moment and starts again (restarts?). When you press all the buttons on the smartphone (volume minus and plus, the power button), the "USB Serial Interface Device (COM4)" ("Устройство последовательного интерфейса USB (COM4)) appears in the device manager. Yes, the drivers are installed.
Spoiler
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The MTK Auth Bypass Tool V7.8.0.5 program shows disable device security fail! when connecting a smartphone and pressing all the buttons for a long time.
Spoiler
MTKClient Program
When all the buttons or volume buttons are held down for a long time, it gives out:
Handshake failed, retrying...
Spoiler
And so it repeats several times, with the system sound of the connected device.
Are there any ways to recover?
From GitHub, where the MTKClient program is located, I downloaded the disk image, booted from it. The phone began to be determined, but even here to no avail
Spoiler
Maybe you have the same issue as we have?
In my case I got it to show the oneplus logo then black and bootloop, but as you no fastboot or recovery or brom access
bootloop,bricked device after trying to do local ota update
so i have tried updating my phone os by using local ota because i have root, i downloaded the zip with oxygen updater and tried flashing it with twrp but it said its wrong device twrp was reporting denniz and the update was for OP515BL1 but when...
forum.xda-developers.com
username_my_name said:
Available: there is a phone, 12/256, DN2103, black screen, recovery and fastboot do not turn on (but the buttons are working), when charging is connected via a USB tester (measures volts, amps and transmitted mAh) and when the power button is pressed for a long time, charging stops for a moment and starts again (restarts?). When you press all the buttons on the smartphone (volume minus and plus, the power button), the "USB Serial Interface Device (COM4)" ("Устройство последовательного интерфейса USB (COM4)) appears in the device manager. Yes, the drivers are installed.
Spoiler
The MTK Auth Bypass Tool V7.8.0.5 program shows disable device security fail! when connecting a smartphone and pressing all the buttons for a long time.
Spoiler
MTKClient Program
When all the buttons or volume buttons are held down for a long time, it gives out:
Handshake failed, retrying...
Spoiler
And so it repeats several times, with the system sound of the connected device.
Are there any ways to recover?
From GitHub, where the MTKClient program is located, I downloaded the disk image, booted from it. The phone began to be determined, but even here to no avail
Spoiler
Click to expand...
Click to collapse
Join this telegram group theres a diffrent mtkclient on there - https://t.me/OnePlusNord2GlobalOfficial/
Search for mtkclient in that group
i am in the same boat as you , i use mtk bypass auth v6 and it does bypass but then after sometime the phone is getting disconnected , Giovix himself said he is going to look into this issue of black screen and me and giovix are in talks regarding the same , his laptop is in service center so waiting for his laptop so me and him can discuss and work on it .
Note : i am no developer i am just a normal guy like you .
I suggest you to join that group on telegram and tag giovix and have a talk with him and let him know that there are many people with this problem .
Meanwhile ill wait till he gets his laptop back to me and him can start experimenting what the problem is , i think he will definitely solve the problem .
Hi there, I'll try to summarize everything:
Unfortunately, the new bootloader doesn't actually provide a way to enter BROM mode like it did before, nor access fastboot. If y'all were on/upgraded to C.10/11, then there's no chance for now.
I've tried to contact bkerler, MTKClient's dev (here, github issue) regarding this specific problem, and as of now it affects both Nord 2 and Nord 2T.
There isn't really a way to recover it, cause it would need a signed preloader (at least that's what I'm assuming, since the preloader itself spits an authorization error), like any Xiaomi device.
If you can, go to a service center and get it repaired. If you can't, I'm afraid the only thing you can do is to wait for a possible solution.
Nonetheless, I'll try to see if there's a way to bypass that.
Giovix92 said:
Hi there, I'll try to summarize everything:
Unfortunately, the new bootloader doesn't actually provide a way to enter BROM mode like it did before, nor access fastboot. If y'all were on/upgraded to C.10/11, then there's no chance for now.
I've tried to contact bkerler, MTKClient's dev (here, github issue) regarding this specific problem, and as of now it affects both Nord 2 and Nord 2T.
There isn't really a way to recover it, cause it would need a signed preloader (at least that's what I'm assuming, since the preloader itself spits an authorization error), like any Xiaomi device.
If you can, go to a service center and get it repaired. If you can't, I'm afraid the only thing you can do is to wait for a possible solution.
Nonetheless, I'll try to see if there's a way to bypass that.
Click to expand...
Click to collapse
Thank you for your input Giovix .
Giovix92 said:
If you can, go to a service center and get it repaired.
Click to expand...
Click to collapse
Thanks for the reply. Does it make sense to contact any service center to try to solve this problem?
Will buying a board from another disassembled phone solve this problem?
username_my_name said:
Thanks for the reply. Does it make sense to contact any service center to try to solve this problem?
Will buying a board from another disassembled phone solve this problem?
Click to expand...
Click to collapse
Absolutely for both questions.
username_my_name said:
Thanks for the reply. Does it make sense to contact any service center to try to solve this problem?
Will buying a board from another disassembled phone solve this problem?
Click to expand...
Click to collapse
SVC will revive your phone rightaway , no need to buy another board , they have diffrent tools for flashing , they revived my phone but for some reasons i deleted my system partition so they were not able to flash my imei partition which is weird .
But in your case SVC will definitely solve your problem without needing to buyba motherboard , just ask them to flash your phone .
Related
Hello everyone, i have hard bricked my PhonePad Duo S7 / ppxs7 (MT6737) while installing firmware update by accidentally unhooking the cable. I am wondering if anyone can help me fix this issue. The phone hardware is all in good condition but the software seems to be completely wrecked, the phone doesn't start at all no matter what combination of buttons and how long i hold it. I tried to flash it again, to no avail because my PC doesn't recognize the phone anymore. I tried to charge it and it didn't do anything either. When i connect the phone to the PC i hear the connection sound and a warning pops up "device not recognized", you can see it in the image i attached below ( also image of what it looks like now in device manager ). I am confident there is a way to fix this, i just need to find a way to make it recognizable once more. Ive sent an email to the manufacturer as well but i hope i might in the meanwhile find a solution as they are not guaranteed to respond, i do not have warranty on this phone. I would be extremely super thankful to any input related to my case.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As long the the hardware is not damaged, it is recoverable. First, are you unchecking preloader when flashing? If still it doesn't work., then keep phone charging overnight to see if you get a response. Other than that, you might have to get your motherboard replaced. :good:
minute214 said:
Hello everyone, i have hard bricked my PhonePad Duo S7 / ppxs7 (MT6737) while installing firmware update by accidentally unhooking the cable. I am wondering if anyone can help me fix this issue. The phone hardware is all in good condition but the software seems to be completely wrecked, the phone doesn't start at all no matter what combination of buttons and how long i hold it. I tried to flash it again, to no avail because my PC doesn't recognize the phone anymore. I tried to charge it and it didn't do anything either. When i connect the phone to the PC i hear the connection sound and a warning pops up "device not recognized", you can see it in the image i attached below ( also image of what it looks like now in device manager ). I am confident there is a way to fix this, i just need to find a way to make it recognizable once more. Ive sent an email to the manufacturer as well but i hope i might in the meanwhile find a solution as they are not guaranteed to respond, i do not have warranty on this phone. I would be extremely super thankful to any input related to my case.
Click to expand...
Click to collapse
Hope I helped.
I was experimenting on an old device (lenovo tab 2 a7 30hc) and hard bricked it.
I've been trying to install the stock rom from SP Flash tool and installed the mtk vcom preloader drivers but the phone still won't get detected.
Someone please help me out here please.
rishabhrocks said:
I was experimenting on an old device (lenovo tab 2 a7 30hc) and hard bricked it.
I've been trying to install the stock rom from SP Flash tool and installed the mtk vcom preloader drivers but the phone still won't get detected.
Someone please help me out here please.
Click to expand...
Click to collapse
Install vcom and Lenovo drivers.
minute214 said:
my PC doesn't recognize the phone anymore. I tried to charge it and it didn't do anything either. When i connect the phone to the PC i hear the connection sound and a warning pops up "device not recognized",
Click to expand...
Click to collapse
I had similar soft brick problem with MTK tablet. Generally you need to remove battery (or unplug the battery connector) and install (plug) it back. If your battery has soldered wires you need to unsolder Vcc (usually red) wire and solder it back after a while (like a couple minutes after). If your battery is not able to remove/unsolder/unplug your only solution is discharge the battery and it can takes a long time.
Hi, can anyone help me
I have my asus rog phone locked in fastboot with starting error qualcomm craachDump Mode.
I am looking for an img image to be flashed via fastboot.
Or any guide to bringing my phone back to life thanks.
Maybe you need to flash the raw files in fastboot mode.
WW_ZS600KL_15.1630.1907.98_M3.15.35.29-ASUS_1.1.12_Phone-user.raw.zip
Download raw.zip and unzip
ROG reboot into fastboot mode
Click on "flashall_AFT.cmd"
Thanks tried but not working it runs all ok, but it restarts again in Qualcomm crash ....... any other solution? Ver __Zs600kl __15.1616.1808.23 i can not find It
Ashba01 said:
Thanks tried but not working it runs all ok, but it restarts again in Qualcomm crash ....... any other solution? Ver __Zs600kl __15.1616.1808.23 i can not find It
Click to expand...
Click to collapse
What usb port on your phone did you use? I believe it will only work on the side port.
yes I used the side one, does everything but then restarts and enters ancota in Qualcomm Crash .......
Ashba01 said:
yes I used the side one, does everything but then restarts and enters ancota in Qualcomm Crash .......
Click to expand...
Click to collapse
Will it go into regular fastboot mode if while the phone is off, hold down volume up and power buttons?
you in fastboot by pressing plus button and ignition, and enter faatboot
Ashba01 said:
you in fastboot by pressing plus button and ignition, and enter faatboot
Click to expand...
Click to collapse
And when you do that do you get the error or just get the error when normal power on.
I get the error only when it starts normally
Ashba01 said:
I get the error only when it starts normally
Click to expand...
Click to collapse
When you tried the above raw install, were you in the normal fastboot or in the fastboot with the error? If you were in fastboot with the error maybe try the normal fastboot mode.
fastboot I never have the error, written error occurs only if I start asus rog phone normally.
With fastboot and lateral usb I did the procedure until the end, then unfortunately when Asus rog starts normal error returns
Ashba01 said:
fastboot I never have the error, written error occurs only if I start asus rog phone normally.
With fastboot and lateral usb I did the procedure until the end, then unfortunately when Asus rog starts normal error returns
Click to expand...
Click to collapse
I know of an ASUS flasher tool. I don't know if it is clean, so be careful. If you have an old computer, I would use it and keep it off your network.
https://www.asusflashtool.com/
That is the only idea I have left to try. Maybe others will have more ideas.
Thanks for the help, you are very kind, explain to me how to use the tools this evening when I come home I try.
Seeing my asus phone brick is sad.
Ashba01 said:
Thanks for the help, you are very kind, explain to me how to use the tools this evening when I come home I try.
Seeing my asus phone brick is sad.
Click to expand...
Click to collapse
You're welcome. To use the tool you'll have to download the firmware that matches your phone from here:
https://www.asus.com/us/Phone/ROG-Phone/HelpDesk_BIOS/
If the flash tool doesn't work, maybe ASUS support can help:
https://www.asus.com/zentalk/forum.php?mod=forumdisplay&fid=433
Perfect tonight or tomorrow morning I try, we hope to be able to solve !!!! thank you all friend.
Tesla74 said:
You're welcome. To use the tool you'll have to download the firmware that matches your phone from here:
https://www.asus.com/us/Phone/ROG-Phone/HelpDesk_BIOS/
If the flash tool doesn't work, maybe ASUS support can help:
https://www.asus.com/zentalk/forum.php?mod=forumdisplay&fid=433
Click to expand...
Click to collapse
Errore: Device Is not connected Yet ........
hi friends my asus rog phone i flash it with qfile with stock rom now my imei has be 0 nothing and me serial has be chance how i can fix it back i need unlock boot loader i cant use the tool when ik flash raw file and its done and i go to phone info and go to imei i have no imei and me serial has not the orginal one and if i wil use unlock tool to unlock boot loader it no works tels me something error me network has some thing how i can fix this i need some qcn file to fix that me imei is this i got 2 imei codes the first imei 351555101262549 now the 2 imei 351555101262556 and me serial is this JCAZGV040926299 i cant fix this by flashing need help now rog 2 phone can be unlocked the boot loader with fastboot this must also voor the rog phone zs600kl work voor it users please so whe dont need more the unlock tool of asus boot loader apk need unlock rog phone zs600kl with fastboot no more unlock ttool need help
nenebear said:
Maybe you need to flash the raw files in fastboot mode.
WW_ZS600KL_15.1630.1907.98_M3.15.35.29-ASUS_1.1.12_Phone-user.raw.zip
Download raw.zip and unzip
ROG reboot into fastboot mode
Click on "flashall_AFT.cmd"
Click to expand...
Click to collapse
This File Link Error
404. That’s an error.
The requested URL was not found on this server. That’s all we know.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Good day. Did you succeed?
Tih1 said:
Good day. Did you succeed?
Click to expand...
Click to collapse
Not Now Succeed Still
Hello. Today I have a problem with my mothers' Huawei P20 Lite.
So lets start from the begging. Phone was lying about 1.5 years.
Yestreday I decided to turn it on. The battery was totally dead so I took off backplate and disconected the battery.
Then I connected phone to power and tried to turn it on.
I saw only Huawei logo and then phone enter eRecovery mode.
Spoiler: Photo after try to turn on
I tried first eRecovery option "Download the latest version and recovery but it didn't work
Spoiler: Photo fail recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When i connect it to PC i can enter FASTBOOT&RESCUE MODE (volume down+power btn)
Spoiler: Photo FASTBOOT MODE
On PC it's shows
Spoiler: Photo PC
So here is my question. How can I unbrick it? Is there any option?
Majke123PL said:
Hello. Today I have a problem with my mothers' Huawei P20 Lite.
So lets start from the begging. Phone was lying about 1.5 years.
Yestreday I decided to turn it on. The battery was totally dead so I took off backplate and disconected the battery.
Then I connected phone to power and tried to turn it on.
I saw only Huawei logo and then phone enter eRecovery mode.
Spoiler: Photo after try to turn on
I tried first eRecovery option "Download the latest version and recovery but it didn't work
Spoiler: Photo fail recovery
When i connect it to PC i can enter FASTBOOT&RESCUE MODE (volume down+power btn)
Spoiler: Photo FASTBOOT MODE
On PC it's shows
Spoiler: Photo PC
View attachment 5504805
So here is my question. How can I unbrick it? Is there any option?
Click to expand...
Click to collapse
I've never tried it, but I don't think the phone will boot properly without a battery. Battery plays primary role in the mobile phone circuitry.
You do not have access to Recovery and eRecovery (see your photo No.1), that's why update via eRecovery doesn't work, imo.
So I need to buy new battery and then try again? Or maybe you have any idea to recover old one?
Majke123PL said:
So I need to buy new battery and then try again?
Click to expand...
Click to collapse
Exactly.
Majke123PL said:
to recover old one?
Click to expand...
Click to collapse
it is strongly not recommended
Okey so i changed the battery and phone still isn't working .
When I connected new battery and connected to charger phone blink red LED 3 times and then started blinking like it is charing but no image of charging. When i tried to turn it on it bilnked again 3 times red LED and nothing else. I let it charge for about 12 hours and nothing changed.
Tommorow i will send a video.
Majke123PL said:
Okey so i changed the battery and phone still isn't working .
When I connected new battery and connected to charger phone blink red LED 3 times and then started blinking like it is charing but no image of charging. When i tried to turn it on it bilnked again 3 times red LED and nothing else. I let it charge for about 12 hours and nothing changed.
Tommorow i will send a video.
Click to expand...
Click to collapse
No need to send the video.
It looks like a damaged motherboard or dead emmc memory (see screen No.1), hard to say. It may not have been a good idea to turn on your phone without a battery...
Plug it on a computer, if it only says USB SER, then you can probably only restore it using testpoint & board firmware (if it is a software problem).
-Alf- said:
No need to send the video.
It looks like a damaged motherboard or dead emmc memory (see screen No.1), hard to say. It may not have been a good idea to turn on your phone without a battery...
Plug it on a computer, if it only says USB SER, then you can probably only restore it using testpoint & board firmware (if it is a software problem).
Click to expand...
Click to collapse
Okey so when the battery is connected i can just turn phone by power + vol down. And then phone enter fastboot&rescue mode. PC detect it like others -> fastboot 2.0
Link to video
Few months ago I tried to turn phone on and it turned on correctly.
It may not have been a good idea to turn on your phone without a battery...
Click to expand...
Click to collapse
And then about week ago i decided to turn it again and it won't turn on. So i thought that the battery may be down and i tried to turn it on without battery.
Majke123PL said:
PC detect it like others -> fastboot 2.0
Click to expand...
Click to collapse
It should be "Android Sooner Single ADB Interface", if I'm not mistaken. "fastboot 2.0" = 'black fastboot' = hard bricked phone.
I saw the video, but I can't advise you anything new, sorry.
Uncle Google is your friend, or ask here
Okey
Thanks
greetings. i need help with my lg v10 f600s which is now hard bricked. the story go so, when i go the phone . it was running on marshmelow no issues or problems.then i installed termux and when i wanted to update or download packages it kept on giving me errors.o googled around and found out it had to o the it no longer been maintained on mm software.so i searched around and found an update for the phone to nougaout firmware, so i downloaded it and updated the phone and thats when all my problems started .first my speaker phone stoped working , the major issue was the phone would randomly turn off at 40, 50, 60 percent charge.so i donwloaded the stock mm firmware to downgrade back to mm used lg up but it would not work and kept giving error.tried several other lg flash tools to no avail. then so a video about using qfil, then i built a qfil flashable firmware and managed to get the phone in to edl mode but while flashing i got these errors
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then i switched to miracle tool and kept gettint this error even with the system.img file present
all throug this process my phone was boot up but all of a sudden when i tried turning it on ,it would not boot up or charge again. i can still enter the edl mode by shorting test points, and also the pcd would heat up when i enter edl mode.pleas how do i solve this.
The V10 was a flagship with known bootloop & heat issues. LG extended it's warranty by 2yrs. Try https://duckduckgo.com/?q=xda unbrick v10
ok thanks let me check it out
It is a really neat phone. Mine still works.
Try clearing Davik, etc, caches.
Try pulling the battery, then holding the power button down for a few.
Try another charger and cord.
If all else fails, it might like to visit the inside of your freezer for a few min.
Anyways, dont worry it to hard. $10-$30 ones can be easily gotten on ebay.
ǀcey said:
It is a really neat phone. Mine still works.
Try clearing Davik, etc, caches.
Try pulling the battery, then holding the power button down for a few.
Try another charger and cord.
If all else fails, it might like to visit the inside of your freezer for a few min.
Anyways, dont worry it to hard. $10-$30 ones can be easily gotten on ebay.
Click to expand...
Click to collapse
tried the link but could not find any solution, and i cant clear cache even if the phone was on because i had booted in to recovery but there were no cammmands, and it does not boot into fastboot mode.and i am in cameroon so ebay is not an option.this phone is realy giving me a headache and right now i am not in the position to buy a new PHONE NOW.if only i had access to a box that would make things easier .there is also one thing i noticed when i disassembled the phone it written on the board F600L__EAX66751701_1.1_MAIN. I THINK THIS MEANS I ACTUALLY HAVE BUT AN F600L AND NOT F600S.BUT THEN ON LGUP IT SHOWED F600S
Once mine was updated by LG repair(vs990), LG up could not overwrite it or roll it back.
I think all other variants could be rolled back via workarounds which can be all found here within xda.
If I remember correctly it had to be plugged into a pc(?), While power button(+ volume up(?)) was held down to enter certian menus.
There is apps out now which can send it adb commands via wifi ip or bluetooth. Easy Fire Tools is one.
Often their charge ports would go bad due to a weak soder. The batteries often failed from heat. You mentioned heat.
It sounds like you may have used a wrong update file meant for a different board/variant.
ǀcey said:
Once mine was updated by LG repair(vs990), LG up could not overwrite it or roll it back.
I think all other variants could be rolled back via workarounds which can be all found here within xda.
If I remember correctly it had to be plugged into a pc(?), While power button(+ volume up(?)) was held down to enter certian menus.
There is apps out now which can send it adb commands via wifi ip or bluetooth. Easy Fire Tools is one.
Often their charge ports would go bad due to a weak soder. The batteries often failed from heat. You mentioned heat.
It sounds like you may have used a wrong update file meant for a different board/variant.
Click to expand...
Click to collapse
i managed to flash all other partitions using MIRACLE except the SYSTEM partition by editing the RAWPROGRAM0 XML file and removing the line of code that enables flashing SYSTEM partition which got rid of the error "CAN NOT FIND SYSTEM.IMG".now i am trying to flash the system partition alone
i am getting "sahara_rx_data:194 unable to read packet header.only read 0 bytes"
using qfil
finally flashed the system partition using MIRACLE TOOLl but phone wont still turn on.i think it realy is an f600l and not f600s.i will build a different firmware using the f600l kdz and flash it see if that works
greetings i have flashed the f600l firmware but still no change phone is still dead. even flashed the firmware dump that i took before the phone got bricked but still no change.and the firehose file only works with miracle tool when i use qfil it keeeps given me errors.pleas can some one help me with a firehose file that will work with qfil
I have an Oppo A51w (Oppo Mirror 5) that I just reset to factory settings, out of nowhere when I restared the phone after that it shows encryption unsuccessful, and a reset phone button, which I couldn't press.
Going into ColorOS recovery mode, I tried wiping data and cache, but wiping data doesn't work because it says I have no space it needs at least 250mb, but I remember the phone does have plenty of space, more than 7gbs, so I don't get why it shows that.
As for fastboot mode it doesn't really do anything other than show its starting logo and text and it turns off? Is there anything else I'm supposed to do I'm not sure?
Anything I could do to get past the encryption screen? I don't mind having to fully reset the phone or flash it but I might need a guide.
There is also an install from sd option in the recovery mode, if somehow it can be fixed from there then please help me with that.
The android version is 5.1.1 and ColorOS 2.1.0i
The version that shows on the ColorOS recovery is 1.2
Android 5.1 is too old. I am not sure which fastboot commands are supported for this version but you can try this even if Fastboot works for few seconds.
fastboot -w
fastboot erase userdata
If the fastboot method does not work then you need to find a MSM Download tool and correct firmware for your device model and flash it.
NextGenMagisk said:
Android 5.1 is too old. I am not sure which fastboot commands are supported for this version but you can try this even if Fastboot works for few seconds.
fastboot -w
fastboot erase userdata
If the fastboot method does not work then you need to find a MSM Download tool and correct firmware for your device model and flash it.
Click to expand...
Click to collapse
Does this need USB debugging? I don't have it enabled and can't enable it because I can't get past the encryption screen.
I tried using MSM download tool but for some reason it won't detect my phone and I'm not sure which usb driver to use and how to install it.
The phone also isn't rooted.
Update:
The phone is now stuck on boot loop. I tried to flash it from sd card using stock rom from the official website, without wiping data first because it wasn't possible (needs 250mb of storage space even though there IS enough free space). It said it was successful, but after rebooting it just gets stuck on boot loop.
- for adb I'd need usb debugging? Which can't be enabled
- the phone isn't rooted, so no cwm
- msm download tool I tried, v4 and v5 doesn't work it says "Packed image not exist" but v1.6.7 does? except even it won't detect the phone, and the rom that i downloaded for that from a different source had different phone model options which i do not recognize (oppo15008.bin etc and rawprogram0_MSM_15070.xml) so I'm not sure which one to choose. Maybe I haven't installed the driver but I don't know which to install and how to.
I really have no experience with this and just tried different guides on the internet to get the phone working. For now I don't know what to do. Any help is appreciated.
Your device seems to have Qualcomm chipset so it can be repaired in the EDL mode (9008). Search google "unbrick oppo a51w". It will give you all info you need to fix this.
If your device is not detected even after installing correct drivers, then you need to use Test Point method (shorting JTAG pins) to access EDL mode. This step needs expertise to short correct pins, if your attempts fail then your best option is the Oppo service center.
NextGenMagisk said:
Your device seems to have Qualcomm chipset so it can be repaired in the EDL mode (9008). Search google "unbrick oppo a51w". It will give you all info you need to fix this.
If your device is not detected even after installing correct drivers, then you need to use Test Point method (shorting JTAG pins) to access EDL mode. This step needs expertise to short correct pins, if your attempts fail then your best option is the Oppo service center.
Click to expand...
Click to collapse
I searched and I seem to have tried following steps like this before and it didn't detect my phone even with Qualcomm driver installed, also didn't know which phone model mine is and I'm supposed to choose between these, how do I know?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
southeeast said:
I searched and I seem to have tried following steps like this before and it didn't detect my phone even with Qualcomm driver installed, also didn't know which phone model mine is and I'm supposed to choose between these, how do I know?
Click to expand...
Click to collapse
Sorry, I cannot help with selection of firmware.
Is there any reason why you can't get this repaired in the Oppo service center?