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.
Related
First,
I really want to thank everyone for their support in this forum. Everyone has been amazing.
I was trying to bring my MZ601 back to stock yesterday. Something bad happened during fastboot and asked me if I wanted to unlock my device. Then the screen locked up and didnt do anything. I rebooted the device and now it gets stuck in a boot loop with the EOS symbol (last rom I installed). When I enter recovery there is nothing there, all of my data is gone.
Worse the device is not recognized on my computer nor can it be found in adb fastboot. I have updated motorola drivers, but I think the device never gets past a certain point in order to be found.
Can somebody please help me.
Thanks,
Pretty impossible to brick XOOM's but i'll ask the basics. Can you get into recovery from a cold boot? Can you get into fastboot from a cold boot?
By the sounds of it you've just corrupted your rom or tried to re-unlock the device which would cause the entire sdcard partition to be erased.
Boot XOOM into Recovery, Fastboot, or RSD mode
So you need to get into Recovery to backup your XOOM (you do nandroid don't you?). Or perhaps you were working on creating new levels of awesome and something happend and you find yourself staring at the Motorola Dual Core boot screen with your XOOM refusing to boot any further. Fear not, you are only a few clicks away from finding your way back into recovery or fastboot goodness.
Turn your XOOM off
Press Power to turn your XOOM back on
When the Motorola Dual Core boot screen appears tap Volume Down repeatedly until "Android Recovery" is displayed
Press Volume Up to enter Recovery
You can also choose from Fastboot protocol support and RSD mode by using the same method but instead selecting their respective menu prompts.
Note:
If your XOOM is caught in bootloops or you find yourself stuck in RSD mode or Fastboot Protocol support you can hardware reboot your XOOM by pressing and holding Volume Up + Power until the tablet reboots (usually a few seconds but could be longer).
demunted said:
Pretty impossible to brick XOOM's but i'll ask the basics. Can you get into recovery from a cold boot? Can you get into fastboot from a cold boot?
By the sounds of it you've just corrupted your rom or tried to re-unlock the device which would cause the entire sdcard partition to be erased.
Boot XOOM into Recovery, Fastboot, or RSD mode
So you need to get into Recovery to backup your XOOM (you do nandroid don't you?). Or perhaps you were working on creating new levels of awesome and something happend and you find yourself staring at the Motorola Dual Core boot screen with your XOOM refusing to boot any further. Fear not, you are only a few clicks away from finding your way back into recovery or fastboot goodness.
Turn your XOOM off
Press Power to turn your XOOM back on
When the Motorola Dual Core boot screen appears tap Volume Down repeatedly until "Android Recovery" is displayed
Press Volume Up to enter Recovery
You can also choose from Fastboot protocol support and RSD mode by using the same method but instead selecting their respective menu prompts.
Note:
If your XOOM is caught in bootloops or you find yourself stuck in RSD mode or Fastboot Protocol support you can hardware reboot your XOOM by pressing and holding Volume Up + Power until the tablet reboots (usually a few seconds but could be longer).
Click to expand...
Click to collapse
Hi,
Thanks for the tips. Unfortunately, it seems that I have caused the entire sd card partition to be erased. That mean when I trry to fastboot my device is not recognized. Also, i cannot add anything to my xoom through usb. I have tried to flash through the external sd card, but to no avail. What do I have to do?
What does your xoom show up as when plugged into your pc APX? Can you boot into fastboot mode. with power off press power and volume down until you see fastboot.
dfib1 said:
What does your xoom show up as when plugged into your pc APX? Can you boot into fastboot mode. with power off press power and volume down until you see fastboot.
Click to expand...
Click to collapse
Hi thanks for the reply to my message.
Unfortunately I cannot find my device when it is plugged into my computer (PC). It does not show up on my computer nor in the device manager. I can start the fastboot protocol on my device by rebooting, but I also cannot find my device in ADB.
Thanks for the reply, but I am still very stuck.
are you sure your device is in fastboot ? did you reinstall the drivers, try with another usb cable, adb shoud see the device after the drivers were installed correctly ...
Sent from my MZ601 using xda app-developers app
ndanl said:
are you sure your device is in fastboot ? did you reinstall the drivers, try with another usb cable, adb shoud see the device after the drivers were installed correctly ...
Sent from my MZ601 using xda app-developers app
Click to expand...
Click to collapse
I did everything I have done before. I have setup android sdk, java, and motorola drivers on two different PCs. Both fail to find my device when i type ADB devices nor does ADB reboot bootloader work. I tried the different cable, but that also did not work.
Hi,
I see that your problem is quite hard, try doing this:
1 - Force your tablet to shut down (vol+ + Power)
2 - Turn on while holding the vol- button
3 - Keep pressing vol-
4 - Plug on your PC and try fastboot devices, adb won't work!
5 - If 4 didn't work, keep trying until it does
6 - Install a Stock ROM (so you will solve your problems)
If the above don't work, contact me via PM, so we can talk easily (maybe GTalk or something like this). Good Luck
~XxLordxX
"This Story Ends Where It Began" - Octavarium (Dream Theater)
XxLordxX thank you!!!
I took your advice and just used fastboot. Then I flashed the stock rom I wanted to use. My xoom is back up and running. I really appreciate the tip.
Also thank you to everyone that responded in the post, again, that is why I love coming here.
demunted said:
Pretty impossible to brick XOOM's but i'll ask the basics. Can you get into recovery from a cold boot? Can you get into fastboot from a cold boot?
By the sounds of it you've just corrupted your rom or tried to re-unlock the device which would cause the entire sdcard partition to be erased.
Boot XOOM into Recovery, Fastboot, or RSD mode
So you need to get into Recovery to backup your XOOM (you do nandroid don't you?). Or perhaps you were working on creating new levels of awesome and something happend and you find yourself staring at the Motorola Dual Core boot screen with your XOOM refusing to boot any further. Fear not, you are only a few clicks away from finding your way back into recovery or fastboot goodness.
Turn your XOOM off
Press Power to turn your XOOM back on
When the Motorola Dual Core boot screen appears tap Volume Down repeatedly until "Android Recovery" is displayed
Press Volume Up to enter Recovery
You can also choose from Fastboot protocol support and RSD mode by using the same method but instead selecting their respective menu prompts.
Note:
If your XOOM is caught in bootloops or you find yourself stuck in RSD mode or Fastboot Protocol support you can hardware reboot your XOOM by pressing and holding Volume Up + Power until the tablet reboots (usually a few seconds but could be longer).
Click to expand...
Click to collapse
I have this problem now but I don't know what to do. Please help me out
Hello, I came to this forums looking to get some help with a device that a friend gave me to fix. He tried to install some sort of custom ROM on his phone (Moto E XT1527), and after installing it, Im not totally sure what did he touch, but now the phone only boots up to a screen saying the following:
AP Fastboot Flash Mode (Secure)
BL: 80.0B (sha-2c9fcbc 2015-03-13 20:15:21)
Baseband: Not Available
Product/Variant: surnia XT1527 8GB P3
Serial Number: T00930M5JK
CPU: MSM8916 ES1. 0
eMMC: 8gb Samsung RV=07 PV=01 TY=57
DRAM: 1024MB Samsung S8 SDRAM DIE=4GB
Console [NULL]: null
Battery Ok
Device is LOCKED. Status Code: 2
Software status: modified
Transfer Mode: USB Connected
Click to expand...
Click to collapse
(There could be some sort of typo on it)
So far I have tried with a tool that suposedly would flash a ROM into the phone without typing any commands, but it failed at some point.
As for unlocking the bootloader, I was abble to obtain the code, yet when I try to unlock it via fastboot, it says that I need the permission to "Allow OEM Unlock", wich I can't grant because of the SO not booting.
Regarding to what my friend did with it, he's not sure, but he think he deleted some sort of file
Im not an expert on this kind of stuff, yet I can follow steps that are given to me to provide any info or to execute a fix, so I would appreciate any kind of help from you to diagnose and solve this problem
Thanks in advance
A little bump
Javier14 said:
Hello, I came to this forums looking to get some help with a device that a friend gave me to fix. He tried to install some sort of custom ROM on his phone (Moto E XT1527), and after installing it, Im not totally sure what did he touch, but now the phone only boots up to a screen saying the following:
(There could be some sort of typo on it)
So far I have tried with a tool that suposedly would flash a ROM into the phone without typing any commands, but it failed at some point.
As for unlocking the bootloader, I was abble to obtain the code, yet when I try to unlock it via fastboot, it says that I need the permission to "Allow OEM Unlock", wich I can't grant because of the SO not booting.
Regarding to what my friend did with it, he's not sure, but he think he deleted some sort of file
Im not an expert on this kind of stuff, yet I can follow steps that are given to me to provide any info or to execute a fix, so I would appreciate any kind of help from you to diagnose and solve this problem
Thanks in advance
Click to expand...
Click to collapse
it can be simply solved ....if you are able to boot to fast boot mode
HOW TO BOOT INTO FAST BOOT
First of all, you have to power off your Moto E.
In order to do so, press power button once and then select “power off” or keep pressing the power button for about 15 seconds.
Wait a few seconds until applying the next step.
After powering off your phone, press power button and volume down key at the same time.
Keep pressing these buttons for about 6, or 7 seconds.
Release the keys when the fastboot / bootloader mode is being displayed.
In fastboot use volume up and volume down keys in order to scroll up and down within bootloader menu and press power button in order to select your option.
if it enters fast boot mod unlock boot loaders ....when it says grant permission using volume up or down button
then flash a custom recovery ...make a factory data reset after you flash custom recovery .....
after all above steps flash any custom rom this will fix all your issues ... you can also try to flash stock rom images via fast boot
Adi Shakthi said:
it can be simply solved ....if you are able to boot to fast boot mode
HOW TO BOOT INTO FAST BOOT
First of all, you have to power off your Moto E.
In order to do so, press power button once and then select “power off” or keep pressing the power button for about 15 seconds.
Wait a few seconds until applying the next step.
After powering off your phone, press power button and volume down key at the same time.
Keep pressing these buttons for about 6, or 7 seconds.
Release the keys when the fastboot / bootloader mode is being displayed.
In fastboot use volume up and volume down keys in order to scroll up and down within bootloader menu and press power button in order to select your option.
if it enters fast boot mod unlock boot loaders ....when it says grant permission using volume up or down button
then flash a custom recovery ...make a factory data reset after you flash custom recovery .....
after all above steps flash any custom rom this will fix all your issues ... you can also try to flash stock rom images via fast boot
Click to expand...
Click to collapse
Hello and thanks for your answer. I have managed to get into fastboot mode, yet I still can't unlock the bootloader. It stills asks me to grant OEM permissions. Is there any way to grant it without booting into the SO?
Heya peoples, I have a problem and am hoping for some help in a work around.
I am trying to root my J3 but my volume up button does not work. I have adb installed, and the correct drivers for my phone. I can use adb command to reboot to the bootloader and it brings me to the Odin "downloading" screen. I can then use the program to install TWRP so I can root. Everything goes fine up until this point. After TWRP is installed there is a single massive problem I am hoping there is a work around for. My volume up button does not work. I can only reboot to recover using adb once the phone boots up, and I read that if you let that happen it overwrites TWRP with the stock recovery (which is what happens when I do this). I read that you have to reboot directly from the downloading screen into recovery using Vol up and home and power. But I can't do that since my Vol up doesn't work. When I am at the download screen after installing TWRP none of the adb commands work so I can't reboot directly to recovery to access TWRP the first time. I hope this all makes since, and I hope someone has some advice because as far as I can tell I can't continue passed this point without a working volume up button.
A little more info in case it matters. When using adb command prompt I have to type ".\adb" instead of "adb" as the tutorials say. When I do ".\adb devices" my device shows up as connected. After rebooting to the bootloader using adb, typing ".\fastboot devices" shows nothing is attached, and any command I try to put in results in "waiting on devices". Checking the device management at this point does not show any unknown usb devices (one guide I read said if fastboot wasn't recognizing to check to update drivers if something was showing as unknown usb".
Basically hoping there is some way of booting directly to recovery from bootloader without having to use the vol up key combination so I can access TWRP for the first time. Any help at all is appreciated. I realize having a working volume button would take all the headache out of this but unfortunately fixing it is not an option at the moment.
Edit: I have also unlocked the bootloader using the Crom Services app from samsung, and have developer options and usb debugging enable.
Question: If I use an app to remap the buttons would that work? Wont be around a computer until tonight. Does remapping the buttons affect it at the level of being in bootloader (because if so I could just switch the up and down volume, use adb to reboot to bootloader then power/home/and remapped volume to reboot to recovery). But I feel like it wouldn't work if the app is not actually changig it but intercepting the button press and then changing it. I dunno.
CopaseticDream said:
Question: If I use an app to remap the buttons would that work? Wont be around a computer until tonight. Does remapping the buttons affect it at the level of being in bootloader (because if so I could just switch the up and down volume, use adb to reboot to bootloader then power/home/and remapped volume to reboot to recovery). But I feel like it wouldn't work if the app is not actually changig it but intercepting the button press and then changing it. I dunno.
Click to expand...
Click to collapse
Can this device even be rooted? Doesn't virgin lock their devices?
In any case if you flash twrp to the boot partition (rename it to boot.img) it'll boot directly to twrp then just use twrp to flash to the recovery partition.
Reflash the stock boot.img back to the boot partition.
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.
Hi. After installing ROM from TWRP and restart, i got this as a bootloop. The problem is, it cannot boot into recovery despite the recovery word at the bottom left. So it looped on this page over and over. I tried all the known buttons and i cannot find anything similiar to my problem elsewhere. Anyone can help?
fireflyzzz said:
Hi. After installing ROM from TWRP and restart, i got this as a bootloop. The problem is, it cannot boot into recovery despite the recovery word at the bottom left. So it looped on this page over and over. I tried all the known buttons and i cannot find anything similiar to my problem elsewhere. Anyone can help?
Click to expand...
Click to collapse
A bit more information , like phone model , how and which version you flashed.
otherwise pull battery (or wait to drain) charge and reboot back to download mode and reflash recovery.
this time making sure you do it right.
atleast ths is my procedure on samsung phones
dandudikof said:
A bit more information , like phone model , how and which version you flashed.
otherwise pull battery (or wait to drain) charge and reboot back to download mode and reflash recovery.
this time making sure you do it right.
atleast ths is my procedure on samsung phones
Click to expand...
Click to collapse
Hi. Phone model Realme C2. TWRP flashing Realme UI. I think i made the mistake of formatting first or something before installing the ROM. I did took off the battery cable. Just that when the phone is powered on thru the cable, it also powered into the pic shown, which is a bootloop but can't boot into recovery. I believe this is an extremely rare situation. I'd be happy if it can boot into adb, then i can at least install back the original phone ROM.
Sometimes i managed to press and hold (vold down power) at the right time. on samsung phones
(right after it screen goes black i think) to get in to download mode during some bootloops.
But i am unfamiliar with fastboot mode i think your phone uses.
Try holding the physical buttons needed for you phones downloadmode/fastbootmode
while it is off and then plug the cable in ? just a guess though.
first google links for 'Realme C2 fastboot physical buttons'
How to Boot Realme C2 Recovery Mode and Fastboot Mode - Droid Recovery
Want to Boot Realme C2 into Recovery Mode or Fastboot Mode or Bootloader Mode? Then follow the instructions listed on this page to successfully Boot Realme C2 to Fastboot Mode or Recovery Mode.Realme C2 Recovery Mode allows the users to perform advanced operations like flashing Root Package and...
droidrecovery.com
https://www.hardreset.info/devices/realme/realme-c2/fastboot-mode/
dandudikof said:
Sometimes i managed to press and hold (vold down power) at the right time. on samsung phones
(right after it screen goes black i think) to get in to download mode during some bootloops.
But i am unfamiliar with fastboot mode i think your phone uses.
Try holding the physical buttons needed for you phones downloadmode/fastbootmode
while it is off and then plug the cable in ? just a guess though.
first google links for 'Realme C2 fastboot physical buttons'
How to Boot Realme C2 Recovery Mode and Fastboot Mode - Droid Recovery
Want to Boot Realme C2 into Recovery Mode or Fastboot Mode or Bootloader Mode? Then follow the instructions listed on this page to successfully Boot Realme C2 to Fastboot Mode or Recovery Mode.Realme C2 Recovery Mode allows the users to perform advanced operations like flashing Root Package and...
droidrecovery.com
https://www.hardreset.info/devices/realme/realme-c2/fastboot-mode/
Click to expand...
Click to collapse
Hi. Nope. It will still boot into the screen on the pic, and it will loop over and over again. I took off the battery cable but when i plug the USB cable, it will also reboot into the pic with bootloop.
I felt that this is a very rare case of the phone screwing up. My initial intention was to install a light rom so i can use the extra space (even after root, App2SD doesnt work). Sigh.
if you remove the cable and let it drain , when it is off and you hold correct buttons for download/fastboot mode
and then plug the cable in it goes it to recovery mode ?
and keep trying press and hold different time in the loop , around the point of black screen/reboot point,
just before/at/and after.
dandudikof said:
if you remove the cable and let it drain , when it is off and you hold correct buttons for download/fastboot mode
and then plug the cable in it goes it to recovery mode ?
and keep trying press and hold different time in the loop , around the point of black screen/reboot point,
just before/at/and after.
Click to expand...
Click to collapse
Sorry, nope. It will boot into the Realme Logo and the recovery mode word on bottom left as shown in the pic. And then bootloop into the same thing again. It cannot enter recovery mode. I tried every combination of buttons with the battery attached and without. I believe the recovery section is erased, or it might be in another part of the memory but inaccessible.
fireflyzzz said:
Sorry, nope. It will boot into the Realme Logo and the recovery mode word on bottom left as shown in the pic. And then bootloop into the same thing again. It cannot enter recovery mode. I tried every combination of buttons with the battery attached and without. I believe the recovery section is erased, or it might be in another part of the memory but inaccessible.
Click to expand...
Click to collapse
are you sure you are trying button combinations for download/fastboot mode (not recovery).
we know recovery is fubared. so is system most probably.
you need to get in to download/fastboot to reflash recovery or stock firmware .
(hold buttons till you see download/fastboot , not just push and let go)
try correct button combination at all the different times in the loop.
and i had a siimmular problem once with a phone turning itself on and looping,
(turned out to be a glitchy power button , try fiddling with that , excersize it to get to unbind if it is)
dandudikof said:
are you sure you are trying button combinations for download/fastboot mode (not recovery).
we know recovery is fubared. so is system most probably.
you need to get in to download/fastboot to reflash recovery or stock firmware .
(hold buttons till you see download/fastboot , not just push and let go)
try correct button combination at all the different times in the loop.
and i had a siimmular problem once with a phone turning itself on and looping,
(turned out to be a glitchy power button , try fiddling with that , excersize it to get to unbind if it is)
Click to expand...
Click to collapse
Yes sir, i did. Tried all button combination at different times. The only thing that worked is the on/off button. When it is on, i press and hold a long time, and let go when the screen is off to turn off. And to turn it on, i press and hold a long time until the screen is on to turn on.
As noted, i might have screw up the installing 3rd party ROM process. I screwed up many times earlier, but i managed to reinstall back the original ROM because it was in adb. And now it isn't. Phones in my country aren't cheap, so if possible, i'd like to save this phone. My initial purpose to install a 3rd part ROM is to make use of the extra internal memory space (i rooted initially but i wasn't able to use App2SD).
so when you hold the power button and it turns off. then you need to use the
combination of buttons for fast boot to turn it on , not just power button .
make sure you have the correct buttons , double , tripple check with the correct buttons
and when to let them go.
also look at
Hard Brick Fix Realme C2
Requirements PC Bypass Extracted OFP Sourceforge or AndroidFileHost C2 Keep restarting from download mode to keep c2 in download mode run brom.bat then connect device holding volume up, down & power after that install drivers (you can install...
forum.xda-developers.com
maybe you need to start from beginning