Bricked phone after update - locked bootloader - Realme 7 Questions & Answers

Hi there,
My Phone after automatic update have now bootloops.
I can't use fastboot to flash because phone dont have unlocked bootloader, when i hold volume UP and power - nothing happens.
In recovery mode i have 'no update found' notification when i try to re-flash software.
There is any way to unbrick phone?

Related

Help recover phone.

I unfortinately formated system in clockworkmod touch recovery. Afterwards phone gets stuck at sony logo when i power on the phone. Am able to boot into fastboot and flashmode using key combinations but cant enter into the clockworkmod with key combinations as i used to do before the system format. However, i unlocked my bootloader and rooted the device before i had this problem. As a result, am not able to get sony pc companion to repair my phone. I tried flashtool but then upon flashing, it asks me to enable usb debug mode and am not able to enable debud mode since the phone doesnt boot past the sony logo.
I will appreaciate it greatly if anyobe can help me get my cute phone out of this situation
On android 4.0.4
Sorry if i posted in a wrong forum.I'm new here

Bricked H960A after root attempt?

Edit:
Problem solved - phone recovered, and rooted successfully. I think the problem was that I didn't use the most recent version of SuperSU. I was using version 2.46 iirc, but I finally got the root working with version 2.76 (filename UPDATE-SuperSU-v2.76-20160630161323). The TWRP version I used is twrp-3.0.2.0-0-h960a.img. (I used this version of twrp both in the failed root attempt as well as the successful one). After I attempted root with 2.46, the phone just hung at the "your device software can't be checked for corruption". To get my phone back, I booted it and connected to USB (you might have to enter fastboot by holding the down volume button and plugging in the USB cable, keeping the down volume pressed until the phone boots, or you might just boot the phone normally and plug it into the USB cable, even though the phone will "hang" doing this, lgup can detect it and you'll be able to "refurbish" with marshmallow kdz which you should have on your computer. I updated my phone to marshmallow before attempting the root, so I had the kdz already. The one I used is v20a. Anyway, after refurbishing, the phone is recovered and usable again, you still get the "can't check for corruption" screen on boot but it only stays for 5 seconds, and then the phone starts. This is normal for an unlocked bootloader. What I did after recovering the phone was to save SuperSU 2.76 (again, filename is UPDATE-SuperSU-v2.76-20160630161323) onto my phone's SD card. Then I reflashed twrp (boot into fastboot, then from console window "fastboot flash recovery twrp-3.0.2.0-0-h960a.img". Then I had to disconnect from the USB cable, and remove the battery. Apparently some phones will perform a factory reset if you attempt a reboot via the console after installing twrp - this is why I removed the battery - then I put the battery back in and booted into recovery mode. To do this (contrary to most instructions I found online which give the wrong button presses), I held the down volume arrow, and then pressed power until the LG logo showed up. Keeping the down volume pressed, I released only the power button, then tapped the power button until I got to a recovery screen (again, keeping the down volume pressed this whole time). Select "yes" both times and you should be in TWRP. Just follow instructions from there that you can find in rooting guides. When you're ready to restart the phone, you'll get the familiar "can't check for corruption" nag screen, but this will go away after a few seconds - LG logo will briefly appear, then disappear and back to that stupid nag screen. But after a few more seconds, the phone starts up. Confirmed rooted with rootchecker!
Below is my original thread where I describe the problem
So I unlocked bootloader, installed twrp and everything fine so far. I put supersu zip file into download folder, flashed with twrp, cleared cache, and went to system reboot - now the phone just hangs at "your device software can't be checked for corruption"
I should say that instead of pushing the supersu zip to sd card, I just saved it in 'downloads' folder of the phone. I also had to do the trick where I flash twrp, and then remove battery, restart phone to recovery mode, because a reboot of the phone would not allow me to use twrp (it just did factory reset)
I can get back into twrp via recovery boot via down volume + power, and I can get into fastboot via down volume + USB cable, but I can't get anywhere else.
I installed stock recovery image from here: droidviews. com/install-stock-recovery-on-lg-v10-using-fastboot/
Went into recovery boot, the android icon shows up and starts to work, but then goes right back to "your device software can't be checked for corruption"
How can I recover this phone? It's H960A
edit:
Ok, so lgup was not recognizing it, and I couldn't install kdz to recover android. I installed lgbridge, then plugged phone in via fastboot (down arrow + usb). lgup then recognized it, and I refurbished with mm kdz. Seems ok now, but still not rooted, and I still get the "your device software can't be checked for corruption" when I boot up (afaik this is because bootloader is unlocked). Tried to root again, same issue. Except this time lgup would not recognize from fastboot, so I just booted phone normally and connected via USB. Then lgup recognized it and I was able to refurbish again
How can I root this thing? at least I have a working phone again

Sord bricking!

Hi there,
I need your help with my device which I just bricked in a peculiar way...
So, something I flashed was not correct. That resulted in an infinite reboot loop (the logo is shown for half a second and it reboots... endlessly). I just used the volume-up rocker to go into fastboot mode to fix the thing as I usually do. I booted into fastboot and this is where it become weird: I cannot do anything!
If I try to use fastboot continue, the phone reboots endlessly again.
If I try to boot to any img (TWRP or signed recovery or signed boot), the device tells me it cannot because it is locked.
If I try to unlock the bootloader (again, because it was), I am told that I am not allowed to do it. The problem is that I cannot boot into a ROM to go into dev mode to allow this.
If I try to flash things, it obviously doesn't work either as the bootloader is considered locked.
The worse here is that since my phone is "not" hard-bricked, I cannot go into qhsusb_bulk mode and use Qualcomm tools to unbrick the thing.
Can I still do something myself or am I screwed?
Lltp said:
Hi there,
I need your help with my device which I just bricked in a peculiar way...
So, something I flashed was not correct. That resulted in an infinite reboot loop (the logo is shown for half a second and it reboots... endlessly). I just used the volume-up rocker to go into fastboot mode to fix the thing as I usually do. I booted into fastboot and this is where it become weird: I cannot do anything!
If I try to use fastboot continue, the phone reboots endlessly again.
If I try to unlock the bootloader (again, because it was), I am told that I am not allowed to do it. The problem is that I cannot boot into a ROM to go into dev mode to allow this.
If I try to flash things, it obviously doesn't work either as the bootloader is considered locked.
The worse here is that since my phone is "not" hard-bricked, I cannot go into qhsusb_bulk mode and use Qualcomm tools to unbrick the thing.
Can I still do something myself or am I screwed?
Click to expand...
Click to collapse
Still you can do that hard brick recovery method it will work for sure..switch off your phone completely and try to connect qhsusb mode.
I had no idea that I could force the qhsusb mode. It worked indeed. Damn ARM devices with their non-standard way of doing anything...

OnePlus X soft brick. All I can access is fastboot mode.

Hi!
I have a OnePlus X and the year after I bought it, I flashed TWRP and installed Lineage OS. Since then, I've flashed many custom roms on my phone. A few weeks back, I decided to flash Resurrection Remix. The battery life on my phone with resurrection was pathetic so I assumed it could be fixed by flashing a custom kernel (franco kernel). I downloaded franco kernel, copied it to my SD card and powered off my phone.
Instead of pressing the VOLUME DOWN and POWER button simultaneously to enter TWRP, I pressed the VOLUME UP and POWER button by accident and went into Fastboot mode. When in Fastboot mode, I pressed the VOLUME DOWN and POWER button thinking my phone would boot into recovery, but it got stuck in a bootloop.
Now my phone can boot only into fastboot mode by pressing the volume up+power button. Any other combination of buttons and it goes into a bootloop.
All this is completely my fault and I would do anything to try and fix it.
Is my phone soft bricked or hard bricked? ( I have a feeling that it is soft bricked).
I've downloaded the android SDK and Minimal adb and fastboot on my pc. I'm able to run fastboot commands, but when I type 'fastboot oem unlock', I get an error saying
"FAILED (remote: oem unlock is disabled)". I've tried 'fastboot flashing unlock' too, but the screen just says "...". Hence, I'm not able to flash TWRP. I tried flashing even the stock recovery but it wouldn't work.
Is there any other way to unlock the bootloader?
I haven't tried the Mega unbrick guide for a hard bricked OnePlus X yet, since I'm able to boot into fastboot mode. Should I give it a shot?
And lastly, can I recover my phone from this mess or is it permanently bricked?
I would appreciate any help.
Thank you!
Sounds very similar to my situation. I did end up following that guide to get mine going again. The link is broken to get the recovery tool, the 2nd one below is the "minimal" version which isn't supposed to wipe data. That is the one that worked for me. I would backup any data if you can first, no guarantee it wont wipe it. Mine wouldn't boot into the stock rom after, but at least it would get to the stock bootloader (VolDOWN + PWR). From there I was able to adb sideload the stock rom (Install from USB). This completely restored it to stock.
23santosh24 said:
Hi!
I have a OnePlus X and the year after I bought it, I flashed TWRP and installed Lineage OS. Since then, I've flashed many custom roms on my phone. A few weeks back, I decided to flash Resurrection Remix. The battery life on my phone with resurrection was pathetic so I assumed it could be fixed by flashing a custom kernel (franco kernel). I downloaded franco kernel, copied it to my SD card and powered off my phone.
Instead of pressing the VOLUME DOWN and POWER button simultaneously to enter TWRP, I pressed the VOLUME UP and POWER button by accident and went into Fastboot mode. When in Fastboot mode, I pressed the VOLUME DOWN and POWER button thinking my phone would boot into recovery, but it got stuck in a bootloop.
Now my phone can boot only into fastboot mode by pressing the volume up+power button. Any other combination of buttons and it goes into a bootloop.
All this is completely my fault and I would do anything to try and fix it.
Is my phone soft bricked or hard bricked? ( I have a feeling that it is soft bricked).
I've downloaded the android SDK and Minimal adb and fastboot on my pc. I'm able to run fastboot commands, but when I type 'fastboot oem unlock', I get an error saying
"FAILED (remote: oem unlock is disabled)". I've tried 'fastboot flashing unlock' too, but the screen just says "...". Hence, I'm not able to flash TWRP. I tried flashing even the stock recovery but it wouldn't work.
Is there any other way to unlock the bootloader?
I haven't tried the Mega unbrick guide for a hard bricked OnePlus X yet, since I'm able to boot into fastboot mode. Should I give it a shot?
And lastly, can I recover my phone from this mess or is it permanently bricked?
I would appreciate any help.
Thank you!
Click to expand...
Click to collapse
Surely your bootloader is already unlocked isn't it?
You don't actually say what happens when you try to reboot into recovery using fastboot commands. Does that fail too? What happens when you try to flash twrp again? You don't actually say.
That's what I thought too. It would just say 'recovery.img' not found or something like that. But, I followed the Mega unbrick guide and was able to install the stock ROM through the stock recovery. My OPX is alive again!
i'm stuck here. the phone does not go into recovery at all .. stuck on oneplus logo .. I don't know what to do .. any ideas?
---------- Post added at 09:20 AM ---------- Previous post was at 08:24 AM ----------
I managed to get it alive again with this guide

Switched ROMS (Evolution X -> Nusantara) -> NOW Bootloop

Hi Community,
I read some posts how to fix my Problem, but i cant go to a service Point.
So I was using the Evolution X for a long Time (Installed with TWRP 3.1.0).
And now i wanted to change to the Nusantara Project (Vanilla), I did a clean Flash, everything worked i could access the System.
Than i had problems installing Play Store, so i rebooted into Recovery via the System. But now im Stuck in the Loop.
Can i Somehow connect my Phone to the PC and Reset?
Can someone tell me if i Hard/soft bricked my phone ?
Just a little advice, would be really appreciated.
Thanks a lot
Go to TWRP, wipe system, cache, data and dalvik. Now flash nusantra and whichever GApps are recommended for it (if there are no recommendations then use OpenGApps, make sure the architecture is correct). Now wipe dalvik and restart. Sometimes, certain roms begin to bootloop if you boot into the rom first, then try to install gapps later.
If you still have issues, just reflash the stock rom.
I cant access the TWRP anymore, im just stuck on the Bootloader, no matter how i turn on The Phone (Volume Up + Power ON ), (Volume Down + Power), (All 3 Buttons)
Nothing works anymore i dont understand ....
Im searching the net but i cant go to fastboot or something else, its just keeps on rebooting ...
So it's bootlooping, but you cant access recovery?
When the screen turns off, press the key combo and it should go to recovery.
Your best bet is to take it to a service centre, but if that really isn't possible for you, then wait for its battery to drain completely, then when you plug in the charger, instead of turning the phone on, press the key combo to enter the recovery. From there, wipe and flash some other OS.
I've also heard that certain versions of TWRP don't support some roms, leading to a bootloop. In that case, you'll have to use orangefox recovery to flash the rom (orangefox is flashable via twrp)
Yes its Bootlooping.
When i turn it on, on the Left Corner "Recovery Mode" blinks for one second. Than the usual Text appears:
"Orange State
Your Device has been unlocked and cant be trusted
Your Device will boot in 5 Seconds".
So after a couple of seconds (around 10-20 sec)
It turns off and immediately on again. I Just can turn it OFF when i hold all 3 Buttons.
Than i try starting it with Volume up + Power / Volume down + Power, But i cant access Recovery or TWRP.
So i should wait til the battery gets low and try it again ?
Like i said, my custom Rom (Evolutionx) and TWRP just worked fine. I dont know man ...
Well since your bootloader is unlocked, try flashing the stock rom again. Look for a tutorial and follow it.
Hi I managed to unbrick my device with this guide, and im back on a stock rom
Unbrick
i ran following commands to get to my custom rom:
I run adb reboot bootloader,
add executed following commands.
(Pitch Black recovery 3.1)
- adb reboot bootloader
- fastboot flash recovery recovery.img
-fasboot reboot recovery
It just hang up and booted after a while into the normal system.
But im not able to get to the recovery menu ?
When I restart and hold Volume up + Power, i go in a loop and the phone keeps restarting over and over again.
what have i Fu**ed up ?
Do i need another recovery tool ?
sorry guys, i appreciate your help a lot tho !
EDIT: Is my bootloader unlocked ?
I can access via "adb reboot bootloader" the phone
and on the blackscreen on the phone it is written:
oppo verfiy pass
fastboot_unlock_verify ok
Update:
So i tried some Stuff and i got Red State. No Problem i Unbricked it once again and now im on Stock Android 10.
Now im Trying to enable the bootloader again.
I downloaded the In Depth Test_Realme_6.apk but i keep getting the Error that i should update the system.
So should i update the system ?
I cant find a CURRENT Tutorial to make this work, please help...
If you cant find a tutorial for your version, why not downgrade back to a previous one if possible.

Categories

Resources