[SOLVED] [RMX1821] Realme 3 Hardbrick, No Charge, No Fastboot, No Recovery - Oppo Realme 3 Guides, News, & Discussion

I hard bricked my phone (realme 3) yesterday, by flashing boot.img and recovery.img from Android 9 firmware to my current C.14 (Android 10) firmware.
Now my phone is dead.
Problems:
Screen wont turn on
No Fastboot
No Recovery
Solution i tried:
Remove battery and put back again and Power On (No luck)
Remove Screen ribbon and put back again and Power On (No luck)
Removes Screen and Battery Ribbon and the same time and Power ON (Still no luck)
Posible Hope:
Everytime i connect the phone into computer (usb cable), and holding the Volume - + Volume + + Power button at the same time, the computer recognized the phone. In the computer device manager it shows Ports and Com > (USB Serial [COM5]). it only show for a second and suddenly it will disconnect.
AUTH-FLASH Realme DownloadTool can fix this i think but it need Flash Credit (username & password), well credit is too expensive 1 credit is = 1 flash , 1 credit is = to $15 here in my country.
Is there any Tool for (MTK Chipset) Realme Device that can flash like AUTH-FLASH Realme DownloadTool without any payment? or some other ways to repair this kind of problem? Please if there is anyone know HELP ME. Thank You So Much!

[SOLVED]
Repair DEAD(HARD BRICKED) Realme 3 | 3i Tutorial
In this tutorial we are going to Repair Realme 3 (RMX1821) MT6771 Chipset. from being hard bricked (no charge, no recovery, no fastboot) using SP Flashtool. with the help of Bypass Utility "MTK-bypass" to disable bootrom protection(sla and daa)...
forum.xda-developers.com

Related

[TUTO] How to Unbrick (Soft brick // No Droidboot) ASUS Fonepad 7 FE375CG K019

Hello ! I had a problem on my FE375CG. It was rooted, and after an ASUS update, my device stuck with only a USB logo on the screen ! No Boot Droid nothing. There was a lot of error and I was unable to flash my device with Fastboot...
But I prepared a kit with a lot a tools to unbrick the devices ! I don't really know who are the authors of this tools, but here is the pack !
First Download the package : "Unbrick_Fonepad_7.zip" : https://mega.nz/#F!qM0EECyA
Second, unzip the package. Install the ADB drivers and the Intel DnX USB Drivers.
Then, Maintain + and - and power on your device for 4 secondes. The screen should remain off.
Connect the tablet to your computer : It should be recognize, screen remaining off.
Then you have to run the "Predowngrade.cmd" in the "3 - PreDebrick" directory.
At the end, you will see an Intel Logo (hourra). Disconnect you device, power off.
Then you have to run the "Downgrade.cmd" in the "3 - Full Debrick" directory.
The processus will stop, and the intel logo appears again.
Maintain + and - and power on your device for 4 secondes. The screen should remain off.
Disconnect you device, power off.
Then, Maintain + and - and power on your device for 4 secondes. The screen should remain off.
Reconnect your device
And hit enter on your computer.
And... Tadaaaaaaaaaaaaaaaaa ! It should work again ^^ ! You have just to flash the last firmware with Bootdroid ! Last firmware can be found here : https://www.asus.com/support/Download/28/7/0/10/Ss6JyhD8bOcmeH6f/32/
Sorry for my english, I'm french ^^ ! Hope it will help some peoples.
Will this work for k004?
Hello,
my FE375CG is bricked: when I turned it on, it's stuck on INTEL logo.
I tried your method, but, after third passage, I can't turned it off. So I waited battery discharge, but when I plug to recharge, the tablet turned on and stuck on INTEL screen, I' can't proceed to the fourth step (I' can't maintain + and - and power on your device for 4 seconds, it turns itself on, remains on INTEL bootscreen and I can't do anything)
Have you some suggestions?
This tutorial work for K01N/FE171CG??
Alviyansyah said:
This tutorial work for K01N/FE171CG??
Click to expand...
Click to collapse
I'd like to know as well.
Sent from my ASUS_Z00LD using Tapatalk 2
Successfully unbrick my ASUS FONEPAD 7 (FE375CG)
after trying more than 10 times i am succeeded. 2nd step of fulldebrick is quite difficult but it works.... volume + and - and power button pressing just 4 second and at 3rd second the screen will flash lightly which can be observed in dark environment.
help me please......... i have an FONEPAD 7 , but its ME175CG... probably i've bricked the device... i cant load recovery mode, the device is blocked in logo android green, and my pc doesn't read nothing!!! PLEAZ HELP ME!!!!
Fonepad k004 me371mg
Hello. I need a help tô my fonepad k004 me371mg. Its bricked. No droidboot. .. no system... nothing. .. only asus logo or usb cable logo. .. the imagem o found only raw formar. ... Tks
Is work in K00E? i need help
suzukube said:
Hello ! I had a problem on my FE375CG. It was rooted, and after an ASUS update, my device stuck with only a USB logo on the screen ! No Boot Droid nothing. There was a lot of error and I was unable to flash my device with Fastboot...
But I prepared a kit with a lot a tools to unbrick the devices ! I don't really know who are the authors of this tools, but here is the pack !
First Download the package : "Unbrick_Fonepad_7.zip" : https://mega.nz/#F!qM0EECyA
Second, unzip the package. Install the ADB drivers and the Intel DnX USB Drivers.
Then, Maintain + and - and power on your device for 4 secondes. The screen should remain off.
Connect the tablet to your computer : It should be recognize, screen remaining off.
Then you have to run the "Predowngrade.cmd" in the "3 - PreDebrick" directory.
At the end, you will see an Intel Logo (hourra). Disconnect you device, power off.
Then you have to run the "Downgrade.cmd" in the "3 - Full Debrick" directory.
The processus will stop, and the intel logo appears again.
Maintain + and - and power on your device for 4 secondes. The screen should remain off.
Disconnect you device, power off.
Then, Maintain + and - and power on your device for 4 secondes. The screen should remain off.
Reconnect your device
And hit enter on your computer.
And... Tadaaaaaaaaaaaaaaaaa ! It should work again ^^ ! You have just to flash the last firmware with Bootdroid ! Last firmware can be found here : https://www.asus.com/support/Download/28/7/0/10/Ss6JyhD8bOcmeH6f/32/
Sorry for my english, I'm french ^^ ! Hope it will help some peoples.
Click to expand...
Click to collapse
Your tutorial is not working for ASUS K004 and file xfstk-dldr-solo can not be run..
My device is not recognized by the pc. It shows the usb logo everytime. I opened the back cover and disconnected the battery. As soon as i connect the battery it turns on by itself, vibrates twice and shows the usb logo. it only turns off if i disconnect the battery. Without the battery it has the same behaviour if i connect the usb cable. None of the keys works except the VOL- or VOL+ and VOL - or PWR and VOL-. If i press vol- or any combination that has VOL- and connect the battery or the cable the device wont turn on and is not detected by the pc. If i do it with vol + or power or a combination of both it starts like i said earlier with two vibrations and the usb logo but not being detected. I'm lost because it being detected by the pc is a requirement. I installed drivers from folder 1 - ASUS_Android_USB_drivers_for_Windows and folder 2 - IntelDnXUSBDriverSetup.
The device is a FE375CG (K019) Asus Fonepad 7
Tried with windows 10 x64 on 2 different computers.
PS: I have disabled driver signature enforcement.
Hi
How can I obtain .img files for K00E (me372cg) ?
if Predownload Cmd worked just proceed to full debrick Download-3cmd then install updated firmware BESURE TO RENAME OFFICIAL FIRMWARE TO MOFD_SDUPDATE.zip it will auto install in recovery mode.

Recovered a bricked Zenphone 2 Z008 after 2 years...

Backstory
2 years ago, I installed nougat into my marshmallow zenphone. A few days later there was a problem with 3g and wifi, so after some searching, I found out I needed to flash modem.zip, after doing so, the phone no longer boot, bootloader is good, recovery is gone and fastboot is gone. Spent about 20+ hours trying to recover... but to no success. The main problem was using the XFSTK method, it did boot to fastboot, but the damn phone product code becomes a Z00A, so flashing a z008 rom led to fastboot refusing to flash. Flashing a z00a rom led to bootloop...
Since I wasted too much damn time trying to recover, and I needed a phone quickly, I bought a 32GB mi max for $120 and never looked back.... until today 03 March 2018.
Recovering the hardbricked Asus phone easily
1) Install the intel usb soc http://drive.google.com/file/d/0B2oMRhweQ4CHbURUNk1ZTHI2Mjg/view?usp=sharing
2) Disable driver verification in Windows 8/10 by rebooting into advanced menu
3) Install intel usb soc above
4) Download and install Download xFSTK Downloader v1.7 https://drive.google.com/file/d/0B2oMRhweQ4CHbDNQdy1jVUJFcEE/view
5) Download the files for xFSTK and unzip
ZE550ML http://drive.google.com/file/d/0B2oMRhweQ4CHcHg4WXJQckFGOTA/view? Usp = sharing
ZE551ML http://drive.google.com/file/d/0B2oMRhweQ4CHR21YaDdXdUNlOGs/view? Usp = sharing
6) Open xFSTK,
go settings, tick enable GP flag override and use the number 0x800000807
link the dnx fwr, ifwi and droidboot from step 5 as follows: https://i.imgur.com/mKZoUdi.png
7) Make sure your phone is off, click begin download then plug in phone, it will start flashing
Sometimes it fails while flashing firmware, sometimes it fails while flashing OS. Doesn't matter keep retrying. Pressing volume button while plugging in phone MAY help.
8) Once successful, you will see 4 color background, then usb cable image, then fastboot mode. If you fail halfway in flashing you will stop at either one of the images. Keep retrying until you reach fastboot.
9) At fastboot, you are safe. Go charge your phone for 1 hour. If your screen dies, do not press power button, press volume button it will remain in fastboot mode.
10) While your phone is charging, install asus flash tool https://drive.google.com/open?id=0B4uMV7GwfDAEYm5RWTFydXZWOTQ
Download the raw file https://drive.google.com/drive/folders/13In6163G8S9BbjiNlEOF-fOXhVIC0z9r?usp=sharing
11) With phone charged, plug in your phone and open the flash tool. Your phone should appear. If not replug usb cable/change usb cable/port, restart the flash tool and leave it plugged in and wait UNTIL the flash tool recognizes it. It will recognize... eventually.
12) select correct model, tick erase data, and locate the firmware. Once recognized, highlight it and click START
13) After 20 minutes, it will be stuck because of the change in serial number. plug out usb cable, restart program, plug back in.
14) Wait for the program to recognize the NEW serial number, then reflash the phone, this time IT WILL BE SUCCESSFUL and will boot into Android marshmallow.
Miscellaneous steps after unbricking
Unlock bootloader, flash recovery, flash custom firmware, root, gapps
Good of you to share. Thanks.
Bricked my own yesterday got it up and running after 6 hrs of looking at guides nice phone good spec but probably be selling on as it not getting any security updates any more I could live with marshmallow but bit wary of no security updates

Help with bootlooped mi5s :(

Hi.
I have a Xiaomi mi5s 64/3 GB in an endless bootloop. Here are the details:
The phone is:
rooted
bootloader unlocked
developer mode enabled
internal storage *not* encrypted
no MIUI account activated
USB debugging on
running the last EU MIUI 9.x development version (don't remember the exact version) with Android 7.0
has TWRP 3.2.1.0 and supersu 2.82
no password is set for unlocking the screen etc.
For some unknown reason the phone suddenly rebooted yesterday and got into an infinite bootloop cycle. I haven't changed any roms recently or done any such flashing. My google play automatic updates were disabled, but a few days ago I manually updated all the apps.
The only odd thing that happened prior to this bootloop, was that when shooting some photos with the google camera mod (same one I've been using for the past few weeks), 2 images were saved as corrupt unreadable files. But that happened a few hours before the bootloop suddenly started.
The current status is:
1. I cannot turn the power off (tried holding the power button, or power button + vol up and down for a very long time --> nothing).
2. I cannot enter recovery mode using vol up + power.
3. I cannot enter EDL using all 3 buttons.
4. If I hold volume down, it enters fastboot but automatically exits from it within 4 seconds (ADB and miflash cannot detect the device in this short period of time). holding the volume down button for a long time has a repating enter-exit-after-4-seconds from the fastboot graphics.
I waited until the battery was completely dead, than started charging it and the status described above was unchanged.
QUESTION 1 - restoring the internal data is my number one priority - does it seem possible here?
To be exact: I want the DCIM folder with the photos+ videos. What should I try now?
QUESTION 2 - I ordered an EDL cable, but am unsure if it supported for my MIUI version. if the EDL cable works, can I force the phone to enter recovery mode from within EDL?
If so - I guess I can copy the internal data to an external USB OTG flash drive I have (that works well with the phone).
If my data is restored, I will then move onto trying to reflash the phone, but at this point this is the least of my worries...
Thanks all.
Anyone?
Maybe it's a problem with the button? I would disassembly the phone and check the hardware.
bedson87 said:
Maybe it's a problem with the button? I would disassembly the phone and check the hardware.
Click to expand...
Click to collapse
I don't know - the buttons don't seem like they are stuck in any way. When I push them, they click back out as usual.
Update - I created an EDL flash cable by stripping the cable gently, exposing the green and black wires, and looping them together - connecting this cable to the phone didn't help either.
Maybe I need to wait for the battery to die so the phone will turn off, connect this cable to the phone, keep the power button pressed while I connect it to the usb port in my PC... what do you think?
I have the same problem with mi 5s which started after update. Don't know what to do.
Took the phone to a local lab - it was all due to a faulty power button module.

Unbrick Redmi Note 8 PRO for Incorrect TWRP Installation Without Authorized Account

After I try to flash twrp using Miui 11 the device turned brick, follow the tutorial to resurrect the RN8PRO without using Mi Authorized Account:
0 - If your RN8PRO turns brick and is connected to USB on the pc just 5 seconds make this tutorial.
1 - This method works only if you have installed TWRP and the device turned brick.
2 - Disassemble your device by doing test point your device asks for mi.
3 - After trying to pass the official rom via miflash or sptools, the RN8PRO asks for the authorized account. CANCEL.
4 - Disconnect all devices from the motherboard, GPS, 3G ANTENNA, CAMERAS and WIFI, leave only the battery on, if the procedure does not work disconnect the battery too.
5 - At this point your device will be working perfectly, plug in the USB cable, press the power button + volume button - the device will go into fastboot, flash to rom STOCK by miflash leaving selecting the Clean All option only. Wait to flash the rom , this process may take 15 minutes.
6 - After Flash your device will turn on normally, turn off the device, remove the USB cable, reconnect all previously disconnected devices, close the device and turn on again.
7 - Ready your device will be working again. :fingers-crossed:
8 - If the procedure is unsuccessful, wait for 4 to 5 days for his battery to completely exhaust, charge it for 3 hours and then redo the process. :good:
portugueiz2 said:
After I try to flash twrp using Miui 11 the device turned brick, follow the tutorial to resurrect the RN8PRO without using Mi Authorized Account:
0 - If your RN8PRO turns brick and is connected to USB on the pc just 5 seconds make this tutorial.
1 - This method works only if you have installed TWRP and the device turned brick.
2 - Disassemble your device by doing test point your device asks for mi.
3 - After trying to pass the official rom via miflash or sptools, the RN8PRO asks for the authorized account. CANCEL.
4 - Disconnect all devices from the motherboard, GPS, 3G ANTENNA, CAMERAS and WIFI, leave only the battery on, if the procedure does not work disconnect the battery too.
5 - At this point your device will be working perfectly, plug in the USB cable, press the power button + volume button - the device will go into fastboot, flash to rom STOCK by miflash leaving selecting the Clean All option only. Wait to flash the rom , this process may take 15 minutes.
6 - After Flash your device will turn on normally, turn off the device, remove the USB cable, reconnect all previously disconnected devices, close the device and turn on again.
7 - Ready your device will be working again. :fingers-crossed:
8 - If the procedure is unsuccessful, wait for 4 to 5 days for his battery to completely exhaust, charge it for 3 hours and then redo the process. :good:
Click to expand...
Click to collapse
This is good for a last resort.. Specially since this phone doesn't have water proofing..
Thread cleaned
Please do not request/advertise/exchange remote unlock services on xda-developers(see Forum Rules 7,11,13):highfive:
Thank you all!
strongst
Forum Moderator
Hi, my r8 pro has bricked recently, i'm really scared, can you help me? i already tried these options:
°boot > recovery = black screen
°boot > fastboot = black screen
°boot = black screen
°i disassembly my cellphone and disconected and re conected the battery but nothing
°i'm trying to drain battery power to 0% because it was charged to 80% and now i'm connecting some things to negative and positive parts of the cable of the battery to consume energy and drain the battery
°i tried "test point" but it is the same has enter to the recovery (vol+ pwr) because it boot to the recovery, and it ask me for MI account authorized when i try to flash stock rom in sp download tool
my redmi note 8 pro only led blinks when i connect the usb to my pc or when i charge it.
Can you help me? please. my discord
zumboy#2354
zumboy said:
Hi, my r8 pro has bricked recently, i'm really scared, can you help me? i already tried these options:
°boot > recovery = black screen
°boot > fastboot = black screen
°boot = black screen
°i disassembly my cellphone and disconected and re conected the battery but nothing
°i'm trying to drain battery power to 0% because it was charged to 80% and now i'm connecting some things to negative and positive parts of the cable of the battery to consume energy and drain the battery
°i tried "test point" but it is the same has enter to the recovery (vol+ pwr) because it boot to the recovery, and it ask me for MI account authorized when i try to flash stock rom in sp download tool
my redmi note 8 pro only led blinks when i connect the usb to my pc or when i charge it.
Can you help me? please. my discord
zumboy#2354
Click to expand...
Click to collapse
Discharging battery will only be useful for when recovery/boot are not crashed. When anything happened, installing twrp, boot image etc, it will very easy to crash, based on your desc, it's hard bricked, need authorised account to refresh. Prepare for $30 to deep flash....

Realme x2 got bricked while downgrading,HELP!!

I had been using realme ui 2.0 on my realme x2 but was frustrated by the bugs so decided to roll back to ui 1.0 (from official website) while the loadng was going on the screen went blank and since then my phone is just bricked as i cannot enter fastboot,recovery modes,not charging nothing just dead .But when i connect it to the pc ,it is recognised as qualcom 9008 com3 as i installed qualcom drivers on pc.(my phone was never rooted nor the bootloader was unlocked).
Hint: Add Realme X2 to this thread's title thus mainly owners of this phone get addressed.
Qualcomm EDL/ 9008 Mode is an Emergency Download mode that is present in every Qualcomm device.
This "Download mode" is enabled when the device can't properly boot (It can also be booted into , using twrp or commands) this can be because of an Improper flash (Like yours) or something on the inside being damaged (less likely).
How do we get out of this EDL mode?
1.If device isn't actually damaged/bricked and just accidentally booted into EDL pressing all three buttons will reboot the device out of EDL , you will have to press it for a long time. (Easiest)
2.Give up and by a new device. (second easiest but also the most expensive)
3Give it to Realme service , many people have done this and gotten back their phone most of the time for free! , but they can charge about $30.
4. Do-It-Yourself , as of now the Firehose file for the Realme X2 is not available which is required to be able do anything useful in EDL mode. (Think of Firehose as a secret key , it is different for other phones , Realme X2 Pro firehose won't work on the Realme X2 , sometimes just submodels of the same phone can have different keys for this.)

Categories

Resources