I managed to hard brick one of my Axon 10 Pro phones.
Short story. I upgraded accidentally to Android 10 v2.9 - The bootloader is still locked.
There is no upgrade or downgrade path from this version.
So I did a "full EDL" backup from my other Axon that is on MyOS Android 11.
I flashed this backup via EDL-Tool (restore --> Full EDL).
Afterwards it rebooted to Android 10. So I flashed again. Again it rebooted to Android 10.
After I had it run out of power and recharged, I tried to boot and it only shows the ZTE logo, no matter how long I wait.
Rebooting in to Recovery with Volume+ and Power does not work.
Also rebooting into FTM/EDL via Volume- and Power does not work anymore.
Is there any chance to recover the phone? Can it boot via USB? Or is there a debug port on the PCB?
Related
Hi guys,
I have a OPO bricked in a very weird way... It's booting straight to TWRP (v3.0.2-0) and nothing else. It is impossible to boot into bootloader (Vol. Up + Power), it still goes to TWRP. And when it is plugged on a computer, it's also booting straight to TWRP...
First a little recap :
- The OPO has (had) an unlocked bootloader and was updated from COS13 to Oxygen OS a while ago.
- The screen was smashed, touch screen not working anymore, and I had it replaced
- Then this problem occured (before screen change, it was booting to Android without a problem)
What I tried :
- Tried to reboot into bootloader, from TWRP via the reboot menu, nope.
- Tried to reboot into bootloader, from TWRP with "adb reboot bootloader", nope.
- Hard Reset from TWRP, nothing.
- Flash latest COS from TWRP (cm-13.1.2-ZNH2KAS3P0-bacon-signed.zip) found here, nothing.
- I wanted to try this last chance unbrick "OnePlus Recovery Tool", but for that the OPO has to be OFF while plugged on a computer, and mine automatically boots on TWRP when plugged , so it's not bricked enough to use it, f***!
Since I can't access the bootlader, I can't do a proper clean/flash
I'm really out of ideas here. I'm starting to think that the problem isn't software but hardware...
Has anyone ever encountered such a brick, or has another idea?
Thanks in advance for your help.
fully shutdown your device and then press the volume up while connecting your phone to pc and see if it can boot into fastboot or not...
just.befa said:
Hi guys,
I have a OPO bricked in a very weird way... It's booting straight to TWRP (v3.0.2-0) and nothing else. It is impossible to boot into bootloader (Vol. Up + Power), it still goes to TWRP. And when it is plugged on a computer, it's also booting straight to TWRP...
First a little recap :
- The OPO has (had) an unlocked bootloader and was updated from COS13 to Oxygen OS a while ago.
- The screen was smashed, touch screen not working anymore, and I had it replaced
- Then this problem occured (before screen change, it was booting to Android without a problem)
What I tried :
- Tried to reboot into bootloader, from TWRP via the reboot menu, nope.
- Tried to reboot into bootloader, from TWRP with "adb reboot bootloader", nope.
- Hard Reset from TWRP, nothing.
- Flash latest COS from TWRP (cm-13.1.2-ZNH2KAS3P0-bacon-signed.zip) found here, nothing.
- I wanted to try this last chance unbrick "OnePlus Recovery Tool", but for that the OPO has to be OFF while plugged on a computer, and mine automatically boots on TWRP when plugged , so it's not bricked enough to use it, f***!
Since I can't access the bootlader, I can't do a proper clean/flash
I'm really out of ideas here. I'm starting to think that the problem isn't software but hardware...
Has anyone ever encountered such a brick, or has another idea?
Thanks in advance for your help.
Click to expand...
Click to collapse
Open the back panel of your device and clean it properly with isopropyl alcohol and microfiber cloth.Also clean the power and volume buttons strips.
Reattach it correctly and then try booting into system or fastboot.
Thank you guys for your help.
So, what happened is that the volume buttons connector was dead, and that the volume down signal was "permanent", that is why the device was systematically booting in recovery mode, no matter what I tried.
Replacing it worked just fine
SOLVED
The answer is that I'm installed a wrong version of TWRP (the android Pie version), but I'm using Realme UI rom which is android 10.
Problem solving was :
1. Turn off the phone by quickly access fastboot and choose turn off, because it can't be turned off normally
2. Wait about 30 minute to 1 hour on turned off state to fix the restarting issue
3. Access the fastboot again and install a latest official rom. I've installed the ColorOS because my country doesn't get the official Realme UI yet
4. Reboot and it's all work normal again
Hi guys,
I've recently attempted to install TWRP on my Realme 5. But it always failed to boot to TWRP after I pressed vol up + power. So I decided to force boot to recovery using command adb reboot recovery. But it booted to stock recovery, even the twrp flashing was succeed.
The disaster begin now after I've accidentally erase the boot and recovery directory using fastboot command. It starts to bootlooping after a few minute, and it showed "The current image (boot/recovery) have been destroyed and can not boot" and it always restarted on that screen.
The fastboot can be accessed, but on a short time because it keeps restarting after a few minute. The device detected on my pc too if I boot to fastboot.
I've tried flashing the stock recovery image, but it didn't work. So I decided to go to a general phone repair shop, but they said that the eMMC was broken. What? The eMMC broken? I don't trust them and take back my phone because before it get bricked, it was fine and normal without any trouble.
Can someone help me? I'm desperate now
Click to expand...
Click to collapse
You need to go to Realme/Oppo service centre. They will fix it free of cost. Dont If you can excess fastboot. Flash boot image and Lastest TWRP image to try to unbrick.
I faced this problem so much. Now it's just fun to me.
You've install Android pie twrp to your stock Android 10 Realme UI.
You've to install Android 10 compatible twrp to the Android 10 Realme 5. Realme UI update has changed the partition table so that it can't get downgraded or flashed via .zip file via twrp. It's company's bad policy that they want to lock the phone after major update.
Now you should download all available twrp from Realme 5 XDA rom section and install one by one and check which one is compatible or works.
Always go to fastboot for flashing twrp.
To forcefully go to fastboot mode do the following :
1. Power Button + Volume Up Button + Volume Down Button
2. When the screen goes off then instantly
3. Power Button + Volume Down Button
Once I also couldn't get fastboot mode but after a full day trial I found this solution by myself. Now Realme 5 is a really fun phone to me which is completely under my control.
imran00_1 said:
I faced this problem so much. Now it's just fun to me.
You've install Android pie twrp to your stock Android 10 Realme UI.
You've to install Android 10 compatible twrp to the Android 10 Realme 5. Realme UI update has changed the partition table so that it can't get downgraded or flashed via .zip file via twrp. It's company's bad policy that they want to lock the phone after major update.
Now you should download all available twrp from Realme 5 XDA rom section and install one by one and check which one is compatible or works.
Always go to fastboot for flashing twrp.
To forcefully go to fastboot mode do the following :
1. Power Button + Volume Up Button + Volume Down Button
2. When the screen goes off then instantly
3. Power Button + Volume Down Button
Once I also couldn't get fastboot mode but after a full day trial I found this solution by myself. Now Realme 5 is a really fun phone to me which is completely under my control.
Click to expand...
Click to collapse
I found that's the major point (which I bold the quote). With a help from a friend, it's solved. Thanks for the answer.
same problem, do you have correct TWRP file? i've tried install twrp from all realme 5 sub forum, but no one it's working
Hello people!
I have a J400F phone model, I was working with android 9 rooted & working well, I updated to android 10 with a fresh install, the phone works well, and I wanted to use a custom recovery TWRP and root the phone, it stuck in boot loop, this is how I flashed:
- Used Odin with the latest stock firmware "J400FXXU6CTGO".
- restart the phone, and the bootloader is already unlocked "OEM Unlocked".
- Downloaded TWRP for J400F from halabtech, flashed it, then rebooted to recovery.
- In home screen, Wipe --> Format.
- With TWRP I flashed RMM_Bypass_v3_corsicanu.zip then no-verity-opt-encrypt-6.1.zip
After this I tried booting to system but then It kept rebooting after reaching the samsung logo.
Any help is appreciated guys.
I managed to access the download mode by taking out the battery, put it back in the phone, connect it to USB in the computer, press vol down and home button and you should be able to enter the download mode to flash the stock ROM (still reading on the second part).
Help.
I was on Android 10 and I just flashed latest 2021 MARCH full firmware.
following this: https://forum.xda-developers.com/goto/post?id=84193795
Update was fine and phone rebooted successfully.
Magisk was fine too.
I flashed Magisk afterwards (flash to inactive slot after OTA)
Then, I found out that I did not have TWRP anymore,
so I went into Bootloader mode, and via ADB, booted up TWRP 3.4.0.0
then, I flashed TWRP [twrp-3.4.0-0-I0W1D-Q-mauronofrio]
and rebooted to recovery, to see if TWRP was there...
...and now my Zenfone 6 cannot boot up anymore.
I think I flashed TWRP 3.4 and not 3.5
I really, really don't know what to do now,
ie. phone screen is black but I can briefly see the TWRP logo,
before phone goes black again.
I cannot go into Bootloader mode nor does pressing down on the power button down for 10-seconds do anything.
EDIT:
it's the same situation as this
-- https://forum.xda-developers.com/t/...enfone-6-stable.3937844/page-12#post-84205699
It seems official android 11 support is broken. Twrp logo flashes for a sec and then bootloops. Any chance for quick update?
I managed to boot into the phone (by pressing VOL down + POWER).
Basically, my TWRP is corrupt or incompatible with Android 11.
So, I got to figure out how to remove TWRP completely (because I have lost root too)
MODS,
please delete this thread because i am certain now that
the cause of my bootloops, etc... were due to TWRP
not being compatible with Android 11
How would one go about reflashing a softbricked Redmi 6 that can only be recognized by a PC for only 2 - 3 seconds in COM mode (Entered via Vol + and Power)? I need advice from first-hand experience.
The device is boot looping with a dark screen, the vibrator only initializes briefly, as opposed to a constant vibration.
This occurred after an attempt at resurrecting it in a prior softbrick state (constant vibration bootloop) using SP Flash tool utilizing the Cereus MIUI v11 fastboot ROM. I have heard now that MIUI v11 can 'lock' the phone, unfortunately I was unaware preceeding this event...
(Note: I accidentally installed TWRP over the boot partition which lead to the perpetual vibration softbrick).
Atleast in the incessant vibration brick state it was feasible to flash the phone via COM mode, again, by holding Vol + and Power; But in this current state it seems F.U.B.R.
Can't enter Fastboot, but had it unlocked prior to the brick with the intention to install TWRP on the recovery partition in an attempt to install Lineage OS, but it would never boot into TWRP mode, neither manually or automatically...
Thanks.
Bump!