Database Info

Need help! Super soft Bricked stock phone. Tried many methods!

Hi all. So my stock opo somehow got bricked overnight while charging. It's completely stock and I have no idea why.
Status of my problem:
-Stuck on Android boot screen.
-Able to access fastboot.
-Can't access recovery mode
-No TRWP
-it's still locked
-Tried unlocking with fastboot oem unlock cmd / toolbox but it just reboots back to android stuck screen after its done but its still locked after checking with fastboot oem device-info cmd.
*USB debugging not enabled (cant enable it cuz i cant go in my phone duh)
-Cm11 33r I think...
-Installed android adb on device manager
But couldn't detect it on the list ("adb devices" cmd)
-Able to detect serial using fastboot device cmd tho.
-Tried universal adp, adb bootloader driver, Samsung adb driver, composite driver and it still won't detect it on list.
-Tried using another usb port.
-computer doesn't detect phone unless I go on fastboot or hold power+up volume for 10 sec (this shows QHUSB_BULK)
-Tried using msm9874downloadtool.exe with cm 11, doesn't do anything even tho it's completed and it's green.
-Tried using msm9874downloadtool.exe with color os but it doesnt work as well, in fact, it made my screen have multiple grey lines vertically across my screen and no fastboot display or android display.
-Tried just flashing Cm11 33r images but it won't work cuz I'm locked.
-Tried unlocking but goes back to my other problem of device not being on the list and not having usb debugging enabled.
Tldr;
Phone stuck on Android boot screen
USB debugging not enabled
Phone is not unlocked so I can't flash anything
Thanks for your time and effort. I really need help.

I still need help guys plzzz. Thankss

Have you tried getting into download mode? I think you power it off. Connect to USB and hold vol down? Or vol down + power. Something like that. Once in DL mode, flash it. There's a tutorial somewhere.
Sent from my A0001 using Tapatalk

ackliph said:
Have you tried getting into download mode? I think you power it off. Connect to USB and hold vol down? Or vol down + power. Something like that. Once in DL mode, flash it. There's a tutorial somewhere.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
download mode? you mean fast boot? power + down doesnt load anything. Power + up goes into fastboot mode.
And i cant flash anything because you have to unlock the phone first. But mine is not unlocked. And i cant unlock it with fastboot oem unlock cmd because all it does it reboots my phone. Yes i checked if im unlocked after that with fastboot oem device-info.

First try to go to recovery by pressing volume down+ power button at the same time and then clear data and factory reset. This will wipe out ur data on phone but u can revive ur device by flashing stock rom using flashing tolls available... Check youtube videos for flashing tools.
Once you clear the data and factory reset from recovery mlde then ur device will be at the state where there is no OS in it n just a stock kernel. Give it a try and let me know

I can't get into recovery. Power + down only stays at android boot screen.

Have the exact same issue. Did you find a fix???

Even if your bootloader is not unlocked you can flash stock rom. Use oneplus one flashtool and flash cm11s. There are plenty of videos available on net for these problem, just go through them or try the hard bricked video to solve your problem. I hope it helps you. I lost my one device because of a silly mistake so i know the pain.

I've tried flashing stock rom. Cm11 33r. But it keeps telling me I'm locked.

put it on fastboot mode, download the stock rom from this:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Choose carefully between 16gb or 64
unzip the file and click on the flashall.bat or something like that , it's a script and it will flash everything
and you should be good
you will loose all your data, i don't know if you dont flash userdata and you remove it from the file and remove it's line from the script, maybe you wont loose your data, but try it
if you want i can help you through teamviewer

i bricked my honor, is there anything i can do?

So I had an unlocked H8 with LOS. As I wanted to install EMUI, I put the proper restore Update.app into the dload folder and started Huawei's recovery. Everything went well, I formated data and wanted to install the EMUI 4.1 ROM using the same method.
Unfortunately my H8 is bootlooping and there is now way into erecovery nor any other recovery. It simply reboots on every single known vol up or down key pressing combination. The only thing I can go to is fastboot mode when holding down vol down and plugging in usb wire. But, it says frd locked and I can't install nor boot twrp. It's simply gone and reboots all the time.
Any hints? I can't even turn it off.

I wanted to give away that phone that's the reason. Last time I did it this way, I could flash the EMUI 4.1 since it's signed. But not this time.
Interesting part is, that although fastboot says frd locked, I still get the "phone unlocked" warning on every reboot. dload method isn't working, as it simply keeps rebooting.
It's my hardest brick so far I ever encountered

the same thing happened to me.....on my phone lock/unlocked frp and bootloader were tweaked for some reason(I mean that what was written wasn't the reality) so how did I fix it? I kept on to flash rollback package many times and I tried to unlock/relock bootloader again, at the end the phone let me to flash the firmware, I didn't know how but the phone allowed me to flash things throw recovery(using dload method). At the begin I only could access to erecovery and fastboot. I suppose that I broke system and data partition and while I looked/unlocked the bootloader, the wipe fixed the partition table. Sorry I'm tired and I know that my English sucks, I hope you understand what I have written.

How did you enter erecovery as this isn't working for me.... What did you flash over fastboot?

Have you tried flashing the firmware separately using adb on computer?
For this you just need to extract the Update.app using the firmware extractor for huawei. Then flash them individually using adb commands in cmd.

I can't access any state that would allow to do adb.

faeArai said:
How did you enter erecovery as this isn't working for me.... What did you flash over fastboot?
Click to expand...
Click to collapse
sorry. I'll try to explain better, however on Huawei/honor devices there are not one but two recoveries, so one is the normal recovery flashed in recovery partition, the second one is the Huawei recovery that is flashed in recovery2 partition, so if you didn't touch recovery2 partition, your erecovery is still there, now, if you press VOL+ VOL- and POWER it will reboot to recovery2 and it starts to flash something from dload in your sd card, so in my opinion you should do this things, first try this method to flash rollback package(this is the transition package from 7 to 6 and you will find it on honor site) if this is still not working try locking and unlocking again your bootloader(I hope this fix partitions of your device) then try to enter recovery and do a wipe and then boot your device, if this doesn't work flash rollback package(now it would work) and then flash an emui 4 full firmware image, always using dload method. trust me... I did the same... and it worked for me. let me know if it works for you :good:

faeArai said:
So I had an unlocked H8 with LOS. As I wanted to install EMUI, I put the proper restore Update.app into the dload folder and started Huawei's recovery. Everything went well, I formated data and wanted to install the EMUI 4.1 ROM using the same method.
Unfortunately my H8 is bootlooping and there is now way into erecovery nor any other recovery. It simply reboots on every single known vol up or down key pressing combination. The only thing I can go to is fastboot mode when holding down vol down and plugging in usb wire. But, it says frd locked and I can't install nor boot twrp. It's simply gone and reboots all the time.
Any hints? I can't even turn it off.
Click to expand...
Click to collapse
I ran into this issue not that long ago. What you have to do is relock your bootloader using ADB. The ADB commands and instructions can be found in this thread.
Just a FYI, do not use the links to the software listed in that thread as it is a little outdated. The method still works but the software will probably not work. Just be sure to get the most recent/appropriate version of SuperSU and TWRP via their official threads (This is if you want to re-root). There are Honor 8 specific TWRP files if I remember correctly, so be sure to check around the Honor 8 forums for the correct files.
A quick summary of what I did:
1) Power your phone off and then boot into fastboot by holding Vol down + Power; as soon as it boots up, plug your phone into your combuter via your usb cord.
2) With ADB running, type:
Code:
fastboot oem relock [COLOR="LightBlue"]################[/COLOR]
NOTE: The '#' should be replaced with your unique unlock code that you obtained to unlock your bootloader.
3) Wait for it to format and reset your phone and go through the setup. BE SURE TO BYPASS all google registration; skip everything you can to get into the phone itself. If you do register, it will reactivate FRP and you'll have to start over again.
4) Turn on USB Debugging and every other setting that enables developer administrative navigation and control just to be safe. USB Debugging being the most important one, though.
5) Restart your phone and boot into fastboot again using Vol down + Power.
6) Unlock your phone again with:
Code:
fastboot oem unlock [COLOR="LightBlue"]################[/COLOR]
7) Once the command is entered, it'll reset your phone once more and - as stated before - bypass/skip all google (FRP) registration.
8) Enable developer options and USB debugging again and make sure that OEM Unlocked is checked and grayed out.
9) Reboot into fastboot mode to confirm that FRP is disabled and you should be able to install TWRP now via ADB.

@Numerics thanks. The thing is, that I can't boot anything. I can't even go into eRecovery. Nor can I flash a stock EMUI 4.1. It just boot loops all the time and I can only access fastboot.

If you can flash twrp..........Install los or other Rom ..................Go back to stock.......you must flash b360 ober adb...... because los is 7.1...............if you on b360 you can usw the rollback for emui 4.1........,..............sry for bad english

I can easily go to fastboot. But I can't flash anything. I extracted the img from the update.app but can't flash. It simply says that it's not permitted.

faeArai said:
I can easily go to fastboot. But I can't flash anything. I extracted the img from the update.app but can't flash. It simply says that it's not permitted.
Click to expand...
Click to collapse
With my method, you don't need to flash anything. Just relock your bootloader via adb in fastboot mode and let it reset. Unless I'm not understanding your issue entirely.

@Numerics as I said, in won't boot anything as it is constantly boot looping. There is no way to access any kind of recovery nor erecovery. There is no boot into Android. The only thing accessible right now is fast boot (which is not ADB). But even in fast boot I can't do anything als operations are not permitted.
after boot looping and starting fast boot mode, I can see a "Android reboot reason" section saying:
AP_S_PANIC
data is invalid
There is still a lineageos installed on system as firmware but as I tried to get rid of it by going back to stock EMUI, I guess Huawei's rollback did something wrong and killed recovery (although I did it in the past successfully).
I tried to run HiSuite to recover my phone, but it just says, that my phone is not supported.
Speaking of this, Huawei messed up with that whole fastboot locking bull****.

faeArai said:
@Numerics as I said, in won't boot anything as it is constantly boot looping. There is no way to access any kind of recovery nor erecovery. There is no boot into Android. The only thing accessible right now is fast boot (which is not ADB). But even in fast boot I can't do anything als operations are not permitted.
after boot looping and starting fast boot mode, I can see a "Android reboot reason" section saying:
AP_S_PANIC
data is invalid
There is still a lineageos installed on system as firmware but as I tried to get rid of it by going back to stock EMUI, I guess Huawei's rollback did something wrong and killed recovery (although I did it in the past successfully).
I tried to run HiSuite to recover my phone, but it just says, that my phone is not supported.
Speaking of this, Huawei messed up with that whole fastboot locking bull****.
Click to expand...
Click to collapse
No, I know ADB isn't Fastboot. What I'm trying to say is that you should be able to still run ADB via CMD on Windows when you're in fastboot mode to relock your bootloader with the directions I gave in my previous post. It'll force-restore your phone to a non-bricked/vanilla state. At least that is how I fixed mine.
Like... You can't even try using the 'fastboot oem relock ################' function via the ADB console while in fastboot?

yes boy trust us, you haven't a working OS so it is a normal thing that your phone reboot, you cannot access to recovery because some partitions are corrupted (data partition) , so these are the steps that could help you:
1) using fastboot, relock your boot loader
2)using fastboot, unlock your boot loader (partition table would be ok now, and you would be able to use load method to flash things trow stock recovery)
4)put inside your sd card \dload\update.app(use rollback package)
3) press all the buttons while your device is rebooting(do this before the blue screen logo appear), your phone is now looking for something inside your sd card
5) if the next step doesn't work do a factory reset from recovery that now would be working
6) put inside your sd card a full android 6 (emus 4) update.app and pressing all buttons it will install the firmware
7) your device now is locked and back to stock, maybe without cust partition or maybe in test mode but it is certainly alive
8) do a factory reset and reinstall the firmware
9) your phone is now ok

You don't lock the bootloader via ADB but via fastboot.
As I said, northing was restored and nothing is booting and I can't unlock my bootloader again. As I said, recovery is not working so the file in dload is not loaded and used. Which is strange.
Locking bootloader didn't do anything besides locking the bootloader. Device is still dead and I still can only access fastboot.

faeArai said:
You don't lock the bootloader via ADB but via fastboot.
As I said, northing was restored and nothing is booting and I can't unlock my bootloader again. As I said, recovery is not working so the file in dload is not loaded and used. Which is strange.
Locking bootloader didn't do anything besides locking the bootloader. Device is still dead and I still can only access fastboot.
Click to expand...
Click to collapse
Which model do u own?
Sent from my Honor 8 using XDA Labs

The European one.

faeArai said:
You don't lock the bootloader via ADB but via fastboot.
As I said, northing was restored and nothing is booting and I can't unlock my bootloader again. As I said, recovery is not working so the file in dload is not loaded and used. Which is strange.
Locking bootloader didn't do anything besides locking the bootloader. Device is still dead and I still can only access fastboot.
Click to expand...
Click to collapse
This is not the truth.....locking bootloader will erase all your data and fix partitions....and with fixed partition you can access to recovery ......trust me the only thing that you can do is to lock your bootloader......you can't flash anything from fastboot and boot recovery or system now...... lock your bootloader and then unlock it again, try using "fastboot OEM lock *****" or "fastboot OEM relock *******" (try cmd runned as admin, people say that this makes the difference) then unlock your device again and .....magic your recovery will boot......the same thing happened to me and I fixed my phone using this trick, however, even if you had frp unlocked it would say you that isn't possible to write anything because you broke some partition, and that's the reason why you can't boot recovery, wait one second and think: why doesn't my recovery boot?

It has nothing to do with trust. I did it and device is still a full stone brick. Nothing changed by locking the bootloader besides that now I can't unlock the bootloader anymore.

Bricked Huawei P9 Lite - Stuck in Boot Screen

Hello,
as the title says... I bricked my phone. In the past, I successfully installed LineageOS on my old Galaxy S3. I got a used Huawei P9 Lite recently and wanted to install a custom ROM. Here's what happened:
1. Unlocked the phone
2. Accessed Fastboot mode
3. Installed TWRP* via fastboot flash recovery file.img
4. This didn't work and I read on the web, I could try to flash revocery2 with fastboot flash recovery2 file.img
5. This didn't help either, so I decided to cancel my plan and use the manufactorer's system since the system still booted (of course, I didn't install any custom OS).
6. The phone told me on each startup it's unlocked. I didn't need the unlock anymore, so I accessed the Fastboot mode again.
7. I re-locked the system by using fastboot oem relock password.
8. The phone asked me to do confirm this action and do a factory reset
9. After this, I'm stuck at the Huawei logo and can't access Fastboot mode anymore!
When I shut down the phone, it immediately restarts itself. No chance to get into Fastboot mode again, which I did through pressing Vol- and plugging in an USB cable.
*I tried several versions, 3.0.1 and 3.2.1 since no version worked
This may be a beginner's fault, my last phone was already unlocked and I had not a single problem back then. But this time... I hope you can help me.
What would happen if I let drain the battery down to 0% - the phone wouldn't restart of course. If I press Vol- and plug it in, would I come back to Fastboot mode or would it stay in this loop?
Any help is appreciated!

Pixel 4a stuck in fastboot mode

Tried to follow this guide to root my pixel 4a and completed all steps up to 3.4. My phone is now stuck in fastboot mode and I can't get into recovery mode to do a factory reset. Not sure what to do, I'm a little lost. I accidentally used this or this image for Android 10 when I think I should have used this image for Android 11.
Any help would be very appreciated.

Maybe you can use this guide:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
And start on this line in "First Step" section:
Plug the phone into a usb port of your pc.
Then complete all the tasks in "Second Step" section to get your phone at least booting in android 10.

ifixibrick said:
Tried to follow this guide to root my pixel 4a and completed all steps up to 3.4. My phone is now stuck in fastboot mode and I can't get into recovery mode to do a factory reset. Not sure what to do, I'm a little lost. I accidentally used this or this image for Android 10 when I think I should have used this image for Android 11.
Any help would be very appreciated.
Click to expand...
Click to collapse
Run the online flash tool from bootloader screen bro. Make sure you install adb and fastboot tools.

Raj Pandiyan said:
Run the online flash tool from bootloader screen bro. Make sure you install adb and fastboot tools.
Click to expand...
Click to collapse
How do I do that? I seem to be stuck in fastboot mode.

ifixibrick said:
How do I do that? I seem to be stuck in fastboot mode.
Click to expand...
Click to collapse
Is it bricked? Cannot flash stock Android to remove ArcaneOS
I recently purchased a used Pixel 4a, and I now understand why the seller was offering such good price for it and why he refused to respond to me now I have it. This phone has ArcanseOS 10 installed, which has only 3 apps installed... Setting...
forum.xda-developers.com

reboot to recovery, press volume up + power to bring up the recovery settings, turn on sideloading
then adb sideload the factory image.

jawz101 said:
reboot to recovery, press volume up + power to bring up the recovery settings, turn on sideloading
then adb sideload the factory image.
Click to expand...
Click to collapse
Hello. Currently stuck in fastboot mode. Using the volume buttons to select recovery mode and pressing the power button to go into it doesn't take me to recovery mode. The screen briefly goes dark before entering fastboot again. I think the phone is trying to restart but not getting past fastboot mode.

ifixibrick said:
Hello. Currently stuck in fastboot mode. Using the volume buttons to select recovery mode and pressing the power button to go into it doesn't take me to recovery mode. The screen briefly goes dark before entering fastboot again. I think the phone is trying to restart but not getting past fastboot mode.
Click to expand...
Click to collapse
Can you type fastboot reboot recovery and get into recovery mode? You'll see a little Android guy with a red thing if you're in there.
If that doesn't work- it almost sounds as though your recovery partition is deleted or something. You can reflash the recovery from fastboot.

Hey, I had the same problem. I've got it resolved now and wasn't able to find any help on how to resolve it, but this thread is as close as it came, so in the off chance that somebody else comes along, I thought I'd write up the steps I took.
Because it was in fastboot mode, I was able to easily restore my phone to factory settings by running flash factory image script I downloaded here.
My original image was sunfish-rq3a.210605.005-factory-be541467 which I followed the steps with but couldn't get it to work. I got to the Google logo with a status bar that just ran forever. But the flash-all.sh script worked to get the phone booting again.
So what I did to get Magisk to work was to use that same factory image site to download an older version. I used a version that was listed in a different root guide with the idea that maybe the version I tried before wasn't compatible with magisk, but presumably the one from the guide was. So I tried sunfish-rq1a.210105.002, ran the flash-all in fastboot, and confirmed that it booted--it did.
Next I redid 2.2 through 3 and it worked, and the boot completed with Magisk installed. Everything seems to be working fine now.

Bricked Oneplus 8T (device state - locked) data recovery

Hi All!
I am in a bit of an unfortunate situation, and am also not that knowledgeable with Android.
I want to recover data on my phone, I would be happy with just recovering the photos.
My Oneplus 8T currently gives me a Quallcom crash dump error when trying to boot. I am also able to go into Fastboot mode with the power button + volume up/down.
Just now, I tried booting the device to TWRP recovery. I first installed Google usb driver, then updated the driver of my Oneplus 8T in device manager. I installed a TWRP recovery image of a Oneplus 8T and put that file where I downloaded Google platform tools. I then ran 'fastboot devices' and saw my device. However, after running 'fastboot boot twrp.img', I received the error 'boot is not allowed in Lock state'.
I cannot remember if USB debugging is enabled or not. I would really appreciate it if anyone could help me out as online articles have been quite useless and also very confusing.

Try fastboot getvar all then do fastboot set_active to either a or b depending on which partion you are on you want to change it also pretty sure USB debugging doesn't matter in bootloader you can also try fastboot oem unlock to unlock bootloader to boot twrp unless you updated to oos twrp doesn't work yet

No no no no.
you have loaded dynamic system image = Super image with incorrect.
Go to this link https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_8T/
And choose your union and version you want.
Download better driver https://onepluscommunityserver.com/list/Unbrick_Tools/Qualcomm drivers.7z
Now you can use the MSM download troll and get your phone back. Install driver and unzip MSM. Start MSM with admin. Select download mode in MSM. Now press power and vol - and vol + at the same time. Your PC will see a new device. Your phone screen is black. Start MSM and wait for it to finish. Google Translate.

JonasHS said:
No no no no.
you have loaded dynamic system image = Super image with incorrect.
Go to this link https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_8T/
And choose your union and version you want.
Download better driver https://onepluscommunityserver.com/list/Unbrick_Tools/Qualcomm drivers.7z
Now you can use the MSM download troll and get your phone back. Install driver and unzip MSM. Start MSM with admin. Select download mode in MSM. Now press power and vol - and vol + at the same time. Your PC will see a new device. Your phone screen is black. Start MSM and wait for it to finish. Google Translate.
Click to expand...
Click to collapse
With MSM he will get everything wiped on his device. This is not he is intending to do.

AK138 said:
Hi All!
I am in a bit of an unfortunate situation, and am also not that knowledgeable with Android.
I want to recover data on my phone, I would be happy with just recovering the photos.
My Oneplus 8T currently gives me a Quallcom crash dump error when trying to boot. I am also able to go into Fastboot mode with the power button + volume up/down.
Just now, I tried booting the device to TWRP recovery. I first installed Google usb driver, then updated the driver of my Oneplus 8T in device manager. I installed a TWRP recovery image of a Oneplus 8T and put that file where I downloaded Google platform tools. I then ran 'fastboot devices' and saw my device. However, after running 'fastboot boot twrp.img', I received the error 'boot is not allowed in Lock state'.
I cannot remember if USB debugging is enabled or not. I would really appreciate it if anyone could help me out as online articles have been quite useless and also very confusing.
Click to expand...
Click to collapse
Run fastboot flash recovery twrp.img ... And then fastboot reboot recovery or choose recovery on your phone.
Sometimes holding volume up and power to do a soft reset boots back into system worth a try.