Hello guys.
I need your help. My phone bricked itself. I left it on charge for the night and faced a black screen issue next day. Bootloader is not unlocked, so I can't enter the fastboot mode. When I press and hold all three buttons I see Mi logo for some time and nothing after. When I connect it to PC via usb it connects after some time but almost instantly disconnects. During that short period of connected state I see usb serial device(COM7) in device manager which disappears then. Then 20-40 sec pause and the same connection and disconnection. Of cource, miflash doesn't see it at all when I try to flash it. I have no experience with disassembling so I cannot flash the phone using motherboard directly or try to enter fastboot by pulling out and in battery. Any thoughts what it can be and how to fix it? Appreciate any helpful info related. I saw a bunch of articles and cases but everything got stuck because of that frequent usb toggling. Not much you can do when you can't even connect
T_Hladiuk said:
Hello guys.
I need your help. My phone bricked itself. I left it on charge for the night and faced a black screen issue next day. Fastboot is not enabled. When I press and hold all three buttons I see Mi logo for some time and nothing after. When I connect it to PC via usb it connects after some time but almost instantly disconnects. During that short period of connected state I see usb serial device(COM7) in device manager which disappears then. Then 20-40 sec pause and the same connection and disconnection. Of cource, miflash doesn't see it at all when I try to flash it. Fastboot isn't enabled for sure because I cannot enter that mode. I have no experience with disassembling so I cannot flash the phone using motherboard directly or try to enter fastboot by pulling out and in battery. Any thoughts what it can be and how to fix it? Appreciate any helpful info related. I saw a bunch of articles and cases but everything got stuck because of that frequent usb toggling. Not much you can do when you can't even connect
Click to expand...
Click to collapse
Excuse me, but, there are a lot of errors and misunderstanding in your post, so you should need to sort them out, to can advance on this.
Fastboot doesn't need to be enabled, fastboot is always there, you just need to press the right buttons to send it to this mode.
USB debugging enables the ADB connection, most probably, you don't need it to fix your device.
Although this said, keep in mind that your device must have the bootloader unlocked, in order to use fastboot to flash.
If this is not the case, then you should need to use a different mode, the EDL mode, also called QHUSB-9008.
You can try, firstly, by booting in stock recovery, formatting data, sometimes this may fix the bootloop issue.
SubwayChamp said:
Excuse me, but, there are a lot of errors and misunderstanding in your post, so you should need to sort them out, to can advance on this.
Fastboot doesn't need to be enabled, fastboot is always there, you just need to press the right buttons to send it to this mode.
USB debugging enables the ADB connection, most probably, you don't need it to fix your device.
Although this said, keep in mind that your device must have the bootloader unlocked, in order to use fastboot to flash.
If this is not the case, then you should need to use a different mode, the EDL mode, also called QHUSB-9008.
You can try, firstly, by booting in stock recovery, formatting data, sometimes this may fix the bootloop issue.
Click to expand...
Click to collapse
Sorry, you are right. I am not good at firmware and all the related stuff. I've updated the post. I was confused about 'fastboot' and 'bootloader'. I meant bootloader was not unlocked. But about EDL - Redmi 6 has MediaTek SoC, but still it has something similar to EDL mode. Anyway, you showed me what I can try to do next. I will try to use preloader like here https://forum.xda-developers.com/t/...icked-redmi-note-9-merlin-hard-brick.4347025/
Thanks a lot!
T_Hladiuk said:
Sorry, you are right. I am not good at firmware and all the related stuff. I've updated the post. I was confused about 'fastboot' and 'bootloader'. I meant bootloader was not unlocked. But about EDL - Redmi 6 has MediaTek SoC, but still it has something similar to EDL mode. Anyway, you showed me what I can try to do next. I will try to use preloader like here https://forum.xda-developers.com/t/...icked-redmi-note-9-merlin-hard-brick.4347025/
Thanks a lot!
Click to expand...
Click to collapse
Ok, I didn't check exactly the processor on Redmi 6, due to lack of time. Anyway, a MediaTek device is even easier to fix (in the paper). Qualcomm's devices have EDL (Emergency DownLoad) mode, and MTK has Download mode (apart from many more modes.)
You also, can follow this guide, with more visual insights https://forum.xda-developers.com/t/...india-6s-using-spflash-tool-for-free.4222027/ of course replace carefully the files from the ones that are for your device.
And this tool also can be useful, to take a complete backup, after to try a thing https://github.com/bkerler/mtkclient
Be advised, that, in any case you have to make a complete format, in SPFT only use the Download option.
Just as a side note, even your bootloader is locked, you always can enter to fastboot mode, the case is that is almost useless, specially in this situation, because a Xiaomi locked device can't be flashed through fastboot.
And to enter to fastboot mode, it's not the three buttons, you have within the various options, as ADB and commands are not available, you can enter manually, either, pressing the volume minus + PWR at same time, or pressing the volume minus button, at same time you connect your device to your PC.
Related
I'm attempting to flash clockwork recovery and can't get the phone to respond to fastboot devices when in fastboot mode. I've tried everything I can find with regards to the drivers (pdanet, usbdeview, etc) and I can get google's and pdanet's drivers working fine with the phone booted normally (responds to adb devices). The problem seems to be that windows appears not to even notice that the phone is plugged in in fastboot mode and does not appear in the device manager, making the manual installation of drivers an impossibility.
Anyone know how to fix this?
stoo said:
I'm attempting to flash clockwork recovery and can't get the phone to respond to fastboot devices when in fastboot mode. I've tried everything I can find with regards to the drivers (pdanet, usbdeview, etc) and I can get google's and pdanet's drivers working fine with the phone booted normally (responds to adb devices). The problem seems to be that windows appears not to even notice that the phone is plugged in in fastboot mode and does not appear in the device manager, making the manual installation of drivers an impossibility.
Anyone know how to fix this?
Click to expand...
Click to collapse
in the main setting, application, developer settings.. is usb debugging enabled?
stoo said:
I'm attempting to flash clockwork recovery and can't get the phone to respond to fastboot devices when in fastboot mode. I've tried everything I can find with regards to the drivers (pdanet, usbdeview, etc) and I can get google's and pdanet's drivers working fine with the phone booted normally (responds to adb devices). The problem seems to be that windows appears not to even notice that the phone is plugged in in fastboot mode and does not appear in the device manager, making the manual installation of drivers an impossibility.
Anyone know how to fix this?
Click to expand...
Click to collapse
When I first set up ADB and Fastboot on my pc, I was getting a response when writing 'adb devices' in the console. However, 'fastboot devices' returned absolutely nothing.
Solution (with phone connected to pc and usb debugging cheched):
1-shut down the phone
2-press and hold Volume Up key + Power
3-once in bootloader interface, in the pc command prompt, type 'fastboot devices'.
Voila!
By the way, don't mount the phone as usb storage device.
Thanks for the responses guys but yes, USB debugging is enabled and yes, I've used that way to get to fastboot mode as well as adb reboot bootloader
Hi stoo
I have a same issue - did you managed to find solution for yours?
Cheers,
Wiktor
vstar said:
Hi stoo
I have a same issue - did you managed to find solution for yours?
Cheers,
Wiktor
Click to expand...
Click to collapse
easy way to set up fastboot
Any solution
Have the same problem: locked bootloader, not rooted 4.1.2. In ADB everything is ok, drivers ok (in device manager), can get it through "adb devices". But when I boot in fastboot (adb reboot bootloader), I hear the ti-da windows sound (usb unpluged - from adb session), but no ta-di when the phone re-boot in fastboot. No exclamation mark in device manager, nothing. The USB receive nothing when in fastboot. Is it possible that the fastboot image is corrupted? Can I reflash it? Or any other advice?
Thanks
EDIT - SOLVED - at least this step
The problem was the famous "broken power button"! I knew that I had problems with the power button (didn't work - that's why I try to flash a rom (4.2.1 or customized) with sleep tile in notification area).
I thought that the button is all the time OFF and don't switch to ON, but I finally understood that when when I boot in fastmode it freeze before installing device on the PC (I also had no volume up / down navigation in fastboot, a sign that it was frozen). So I ended to consider that the power button was permanently in ON position. I opened my phone and I measure the impedance on the power button. I had ~ 4ohms in off position of the button and 1.8 ohms (cheap multimetter.... probably should be almost 0) in on position. I measured also on volume switch where I had ~ infinite on off position, so I concluded that the button if blocked. I tried to see if I can resurrect it but no choice, so I took it off (unsoldered). I put the battery and the USB cable and boot it. From ADB I reboot it in fastboot and voila! The device popped in device manager! One problem solved! BUT...
I tried to use the Nexus Root Toolkit and it boots in fastmode and try to unlock the bootloader, but it asked me on phone screen if I agree for unlocking. I was able to use the volume to select Yes but I couldn't choose it with power! I had no option but to take the battery off. Starting from that point it was almost impossible to power it again. When I plugged the USB it shown the battery icon (charging). I tried every trick that I found on web, but nothing worked (even to fast plug / unplug many times the USB to overcharge it, but nothing). I was able only by pressing on the middle of volume (so Up and DOWN in the same time) and plus the USB to get to the screen of unlocking bootloader, but without the options YES/NO on the screen. Seems that it saves this state between boots, but why no option? Finally I was unable to boot at all, and it is like totally bricked
I thought that the power button is a simple switch ON / OFF, so I soldered 2 wires and I tried to touch them (short circuit) to simulate the ON, but nothing happened. Is it the button more complex that a simple switch? no ideea...
So now have a better phone than before (at least theoretically it should be able to fastboot), but it values zero because I can't power it on....
OK So I am in the exact same situation.
Nexus S, Broken power button, adb can see the device, fastboot cannot. fastboot cannot be navigated with the volume keys.
I also want to put an other rom onto it, but firstly I want to put TWRP recovery on it, as it supports touch, CW needs the power
button which like mentioned does not work.
I would rather not unsolder my power button to get into fastboot, any suggestions on how that might still be achieved?
thx
catalinu said:
Have the same problem: locked bootloader, not rooted 4.1.2. In ADB everything is ok, drivers ok (in device manager), can get it through "adb devices". But when I boot in fastboot (adb reboot bootloader), I hear the ti-da windows sound (usb unpluged - from adb session), but no ta-di when the phone re-boot in fastboot. No exclamation mark in device manager, nothing. The USB receive nothing when in fastboot. Is it possible that the fastboot image is corrupted? Can I reflash it? Or any other advice?
Thanks
EDIT - SOLVED - at least this step
The problem was the famous "broken power button"! I knew that I had problems with the power button (didn't work - that's why I try to flash a rom (4.2.1 or customized) with sleep tile in notification area).
I thought that the button is all the time OFF and don't switch to ON, but I finally understood that when when I boot in fastmode it freeze before installing device on the PC (I also had no volume up / down navigation in fastboot, a sign that it was frozen). So I ended to consider that the power button was permanently in ON position. I opened my phone and I measure the impedance on the power button. I had ~ 4ohms in off position of the button and 1.8 ohms (cheap multimetter.... probably should be almost 0) in on position. I measured also on volume switch where I had ~ infinite on off position, so I concluded that the button if blocked. I tried to see if I can resurrect it but no choice, so I took it off (unsoldered). I put the battery and the USB cable and boot it. From ADB I reboot it in fastboot and voila! The device popped in device manager! One problem solved! BUT...
I tried to use the Nexus Root Toolkit and it boots in fastmode and try to unlock the bootloader, but it asked me on phone screen if I agree for unlocking. I was able to use the volume to select Yes but I couldn't choose it with power! I had no option but to take the battery off. Starting from that point it was almost impossible to power it again. When I plugged the USB it shown the battery icon (charging). I tried every trick that I found on web, but nothing worked (even to fast plug / unplug many times the USB to overcharge it, but nothing). I was able only by pressing on the middle of volume (so Up and DOWN in the same time) and plus the USB to get to the screen of unlocking bootloader, but without the options YES/NO on the screen. Seems that it saves this state between boots, but why no option? Finally I was unable to boot at all, and it is like totally bricked
I thought that the power button is a simple switch ON / OFF, so I soldered 2 wires and I tried to touch them (short circuit) to simulate the ON, but nothing happened. Is it the button more complex that a simple switch? no ideea...
So now have a better phone than before (at least theoretically it should be able to fastboot), but it values zero because I can't power it on....
Click to expand...
Click to collapse
Yes, it should have been better for me to have also a possibility to enter in fastboot with the power button blocked in ON position, but I didn't find. And now I know no way how to power it up...
fastboot drivers
http://www.samsung.com/us/support/owners/product/GT-I9020PWAATT#
has anybody considered using this executable from samsung ..
from what i understood when installing it ,it only unzips the contents at programfiles/Samsung/drivers
then you can check this thread to install them spesifically http://forum.xda-developers.com/showthread.php?t=1901617
..In short.
Go to
"Device Manager"
find
"Android 1.0" or something like that (i had my device in fastboot/bootloader mode, dont know if it was necessary)
install drivers from the drivers directory and install
P.S. Mine is an ordinary 9023nexus s (slcd) though
be a bit more careful with nexus s4g
Hello guys,
I just replaced screen on my 64GB OPO. Phone was fine before screen broke and I had a PIN lock on it. Now, when I turn on phone, I cannot do anything on my phone besides pulling down notification bar and swipe notifications. If I try to unlock by entering my PIN, screen turns off right after. If I enter wrong PIN, it will say Wrong PIN, but as soon as I enter right PIN, screen turns off.
I'm not sure why this is happening. I decided to boot into recovery and reflash the ROM. I hold Power + Vol Down, but phone starts booting normally, no recovery. Then, I try to go into Fastboot by Power + Vol UP, and phone boots normally, no fastboot. At this point, I cannot access recovery or fastboot. Then, I try ADB on laptop, I get "Unauthorized." I can't authorize ADB RSA dialog on my phone because as I said, when I enter my PIN to unlock my phone, screen turns off. Recovery, Fastboot, and ADB worked perfectly before replacing screen.
Anyone know how to fix this?. Thank you
TL;DR:
Replaced screen. Entering my PIN turns screen off immediately. No recovery, No fastboot, ADB gives "Unauthorized" Error.
xymic said:
Hello guys,
I just replaced screen on my 64GB OPO. Phone was fine before screen broke and I had a PIN lock on it. Now, when I turn on phone, I cannot do anything on my phone besides pulling down notification bar and swipe notifications. If I try to unlock by entering my PIN, screen turns off right after. If I enter wrong PIN, it will say Wrong PIN, but as soon as I enter right PIN, screen turns off.
I'm not sure why this is happening. I decided to boot into recovery and reflash the ROM. I hold Power + Vol Down, but phone starts booting normally, no recovery. Then, I try to go into Fastboot by Power + Vol UP, and phone boots normally, no fastboot. At this point, I cannot access recovery or fastboot. Then, I try ADB on laptop, I get "Unauthorized." I can't authorize ADB RSA dialog on my phone because as I said, when I enter my PIN to unlock my phone, screen turns off. Recovery, Fastboot, and ADB worked perfectly before replacing screen.
Anyone know how to fix this?. Thank you
TL;DR:
Replaced screen. Entering my PIN turns screen off immediately. No recovery, No fastboot, ADB gives "Unauthorized" Error.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
You can use this,it does not uses fastboot and instead uses hardware debugging port.
Also using this on Xp system will make it easier to detect the device.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
You can use this,it does not uses fastboot and instead uses hardware debugging port.
Also using this on Xp system will make it easier to detect the device.
Click to expand...
Click to collapse
I looked at that tool before I made this thread and in 3rd step, it says to press Power + Vol Up? Doesn't that mean you have to be in fastboot? Anyway, I tried it in Windows 10 and it didn't do anything. My phone gets detected by my laptop and everything. I will try in Windows XP and see if anything changes.
xymic said:
I looked at that tool before I made this thread and in 3rd step, it says to press Power + Vol Up? Doesn't that mean you have to be in fastboot? Anyway, I tried it in Windows 10 and it didn't do anything. My phone gets detected by my laptop and everything. I will try in Windows XP and see if anything changes.
Click to expand...
Click to collapse
No, power+vol+ is actually done to trigger the qualcomm port,if your device can't boot to fastboot,it means it's actually dead then your pc should be able to detect it as "Qhs_bulk" or "usb qcom diagnostics 9006".
Make sure you install the drivers given in the thread or Qualcomm 2012 drivers.Again this procedure doesn't work on fastboot/adb drivers!
You'll have to disable driver signature check on win8/10,Xp works without any issues.
Mr.Ak said:
No, power+vol+ is actually done to trigger the qualcomm port,if your device can't boot to fastboot,it means it's actually dead then your pc should be able to detect it as "Qhs_bulk" or "usb qcom diagnostics 9006".
Make sure you install the drivers given in the thread or Qualcomm 2012 drivers.Again this procedure doesn't work on fastboot/adb drivers!
You'll have to disable driver signature check on win8/10,Xp works without any issues.
Click to expand...
Click to collapse
Oh ok. I will try soon. I'll report back with results.
Thanks for your help man!
xymic said:
Oh ok. I will try soon. I'll report back with results.
Thanks for your help man!
Click to expand...
Click to collapse
Click "Thanks" button
Hello.
I am Finnish, so I try to tell my problem with correct english.
I have a Huawei P9 Mini Lite phone with Android 7, stock ROM. I unlocked the bootloader. I tried to install custom recovery, TWRP, but it failed, must have been wrong version, for other P9 model. I used Windows software just for for Huawei phones, that you can use to unlock, relock bootloder, root, and many stuff (I cannot remember the name of that software, it works in command prompt window). Situation was kind of messy, but after unlocking, I was able to boot phone to Android OS, only entering eRecovery first, and there press the "reboot" option. So I thought if I relock the bootloader, it maybe helps. After relocking, I rebooted my phone, and I got notification, that there is some problem with file system, and I must do factory reset. It offered me that option right away, so I clicked factory reset. After that, phone went into boot loop state, and also there is a warning screen, about that phone cannot be trusted, because of bootloader is unlocked-relocked. Cannot remember clearly, because the warning screen appears only for few seconds. I was able to press power, vol up/down buttons, that are mentioned in warning screen to enter recovery or continue etc., but it doesn´t help. Huawei logo appears, phone vibrates, and then it starts again... I cannot enter eRecovery anymore. I can enter to normal stock recovery only when I connect USB cable to PC, and press power and vol down, but there is no options to anything. Only notification, that I must connect phone to computer with USB cable, and I did that already. But computer doesn´t recognize my phone, so I cannot do nothing by using computer to try factory reset or something else. In a simple way, I have drivers on my PC for USB, and Huawei software too, but I cannot connect phone to PC. Interesting thing is, that Huawei software on my PC recognizes that there is my phone, when I use USB cable, but there is no connection between phone and PC. So how I can do anything to my phone, when I cannot use my PC to work with my phone? Battery is not removable, and I also let my battery to go empty, and when I connected phone to charger after that, and later tried to turn it on, boot loop started again.
[WANTED!!!] TWRP port for Huawei SLA-L02
Hi and welcome to this forum.
I apologize for the late reply. In the meantime, did you resolve the issue?
Is your device a Huawei SLA-L02?
If you still need help for the above-mentioned smartphone, let me know.
Thanks and greetings
can you please help me I need help because this is happening to me and can you please respond fast
Simon Šircelj said:
can you please help me I need help because this is happening to me and can you please respond fast
Click to expand...
Click to collapse
You can follow this guide.
Make sure that the build number ends in an even number (if your phone is a dual-sim model). For example, SLA-L22C432B150
In order to recover Android properly, it's necessary to discover which build number is installed now on your phone. So please, turn off your phone. Plug your phone to a computer by a usb cable, then hold down simultaneously the volume down button and the power button, so that the FASTBOOT&RESCUE MODE can start on your phone. Then, on Windows, run a command prompt as administrator and move to the directory where there are fastboot and adb.
Now, type and enter the following command:
Code:
fastboot oem get-build-number
Then, post the returned result, thanks.
My phone is not turning on. When I connect the charging cable, the phone starts in to fastboot mode. When I flash in fastboot mode, the phone turns off in the middle of the flash. And the phone switches to EDL mode. Or diagnostic mode port 900e com 10. And the flashing is incomplete. Please help me how i fix?
This is the screen of death/near-death for this device.
Try Vol Up+Power for an extended time and see if you can snap back to BL or EDL mode. Flash EDL or RAW depending on which state you manage to get back to. If not, try to remove and re-connect the battery from the mainboard if you have the skills and tools to open it and put it back together. You can try to JTAG it (I don't know the pin locations for this device)
If it's a hardware issue (e.g damaged memory etc), none of these tricks will help. There is a real chance your device is hard bricked and will never recover unfortunately.
If you have warranty, send it straight to ASUS without doing anything else. If not, paying for a motherboard replacement + repair costs will come close to buying a new device...
Andrologic said:
This is the screen of death/near-death for this device.
Try Vol Up+Power for an extended time and see if you can snap back to BL or EDL mode. Flash EDL or RAW depending on which state you manage to get back to. If not, try to remove and re-connect the battery from the mainboard if you have the skills and tools to open it and put it back together. You can try to JTAG it (I don't know the pin locations for this device)
If it's a hardware issue (e.g damaged memory etc), none of these tricks will help. There is a real chance your device is hard bricked and will never recover unfortunately.
If you have warranty, send it straight to ASUS without doing anything else. If not, paying for a motherboard replacement + repair costs will come close to buying a new devic
Click to expand...
Click to collapse
Thanks for reply!
When I flash raw file in fastboot mode, the phone turns off in the middle of the flash. And the phone switches to EDL mode. Or diagnostic mode port 900e com 10. And the flashing is incomplete.
hardware issue it seems.... also your device is still locked, so it'll not accept anything custom that you're trying to flash
Any solution?
Which RAW script do you use? Try the "fash_raw_and_wipe_data" file. Also check the content of the flashraw_.log file after it fails for any clues. If you have Fastboot access, try also to switch your active slot from a>b or b>a (although don't think you can do that when the device is in this state).
Did you manage to solve the problem?
Hi all!
Long story short, basically my OnePlus Nord gen 1 is bricked (no recovery, no ROM). In the current state all it is able to do is boot into the bootloader. The bootloader gives several 'options' such as "boot to recovery", and more importantly, "power off". But no matter what option I choose, the phone ends up rebooting back into the bootloader.
I've tried to follow guides on XDA instructing how to unbrick the device, to no avail. The main guide I'm trying to follow is the MSMdownloadTool guide, but that requires me to power off the device to enter EDL mode (which it isn't doing).
The device seems to be stuck in fast boot mode, but isn't using fastbootd so I can't make changes to critical partitions. Since it is stuck in fastboot mode, adb commands don't work. I've tried reflashing the recovery, but that didn't work. I've tried clearing cache but there I'm running into 'cannot generate userdata' (fastboot erase cache spat out "failed; check device logs").
As for hardware buttons, using volume down + volume up or even volume down+power does nothing, volume up + power button or holding all 3 just restarts the bootloader, and holding just the power button does nothing except for repeatedly select "start"(causing it to reboot back into bootloader).
I feel if I can just get it into EDL mode somehow, everything else will fall into place. Any help at all will be much appreciated
zeuses23 said:
Hi all!
Long story short, basically my OnePlus Nord gen 1 is bricked (no recovery, no ROM). In the current state all it is able to do is boot into the bootloader. The bootloader gives several 'options' such as "boot to recovery", and more importantly, "power off". But no matter what option I choose, the phone ends up rebooting back into the bootloader.
I've tried to follow guides on XDA instructing how to unbrick the device, to no avail. The main guide I'm trying to follow is the MSMdownloadTool guide, but that requires me to power off the device to enter EDL mode (which it isn't doing).
The device seems to be stuck in fast boot mode, but isn't using fastbootd so I can't make changes to critical partitions. Since it is stuck in fastboot mode, adb commands don't work. I've tried reflashing the recovery, but that didn't work. I've tried clearing cache but there I'm running into 'cannot generate userdata' (fastboot erase cache spat out "failed; check device logs").
As for hardware buttons, using volume down + volume up or even volume down+power does nothing, volume up + power button or holding all 3 just restarts the bootloader, and holding just the power button does nothing except for repeatedly select "start"(causing it to reboot back into bootloader).
I feel if I can just get it into EDL mode somehow, everything else will fall into place. Any help at all will be much appreciated
Click to expand...
Click to collapse
You might be able to enter EDL mode by opening the device and using a jumper to touch certain contact points on the board and force it into EDL mode. I don't know your hardware so I don't know which points to tell you to use the jumper on, you'll have to do some research to figure that out based on the specific device you have.
zeuses23 said:
The device seems to be stuck in fastboot mode, but isn't using fastbootd so I can't make changes to critical partitions.
Click to expand...
Click to collapse
unrelated. you can flash super.img from fastboot. flashing critical partitions maybe needs unlocking.
Hello if this can help my device was dead , not even fastboot or recovery was working and was bootlooping. What i did is installing MTK authentication bypass ( i dont know if your phone is mtk cpu ) , then i instaled libUsb driver that came packed with that tool.
Then you open libusb driver installer, and when you keep pressed power + vol down to enter Brom mode, it should detect a com port that disappear in few seconds, what u need to do is click install driver as soon you see that com port appear.
Now you open the bypass tool with phone disconnected, click on bypass, and then connect the cable, now enter Brom mode with power + vol down, and the tool will say Success.
Now your phone is ready to use with any flash tool ,like sptools.
Hope this helps.
Droidriven said:
You might be able to enter EDL mode by opening the device and using a jumper to touch certain contact points on the board and force it into EDL mode. I don't know your hardware so I don't know which points to tell you to use the jumper on, you'll have to do some research to figure that out based on the specific device you have.
Click to expand...
Click to collapse
Hey, thanks for the suggestion! But i would very much prefer not to open up my device. I've also heard that there is an EDL cable, but I don't know if that'll work either. Lets see
aIecxs:
unrelated. you can flash super.img from fastboot. flashing critical partitions maybe needs unlocking.
Click to expand...
Click to collapse
Thanks for your reply! A silly question, but what does super.img do? I tried flashing the critical partitions after running "fastboot oem unlock_critical", but that still gave me the error.
innergat:
Hello if this can help my device was dead , not even fastboot or recovery was working and was bootlooping. What i did is installing MTK authentication bypass ( i dont know if your phone is mtk cpu ) , then i instaled libUsb driver that came packed with that tool.
Then you open libusb driver installer, and when you keep pressed power + vol down to enter Brom mode, it should detect a com port that disappear in few seconds, what u need to do is click install driver as soon you see that com port appear.
Now you open the bypass tool with phone disconnected, click on bypass, and then connect the cable, now enter Brom mode with power + vol down, and the tool will say Success.
Now your phone is ready to use with any flash tool ,like sptools.
Hope this helps.
Click to expand...
Click to collapse
Hey innergat, unfortunately I believe my phone has a qualcomm chipset, so this probably won't work
Dynamic partitions are logical partitions hosted in physical super partition. logical partitions can only be accessed from fastbootd, physical partitions from fastboot.
To enter EDL mode try selecting power off and then immediately hold volume up + volume down.