Database Info

Strangest "Bricked" Oneplus One: No recovery, locked OS, can't unlock bootloader

Strangest "Bricked" Oneplus One: No recovery, locked OS, can't unlock bootloader
Hi there, I've come in to the possession of the most stubbornly bricked phone that I've ever seen . Bought a OPO off Craigslist, someone cracked the screen and sold it for cheap instead of fixing it. It had been remote wiped but still has some strange difficult software. Posted this problem to the Oneplus Forum but have had no response, thought XDA would be more qualified!
From what I can tell it's a Oneplus One that was sold through a re-seller that replaced all the software on the phone with a high-security version of Android. It's called EncroChat and from their website (encrochat.network or encrochatsure.com) it looks like it removes the recovery from the phone and replaces it with an EncroChat OS (some kind of Cyanogen) that you can boot to in addition to the Android OS.
Well I assume during the remote wipe something went wrong with the software and the phone no longer really functions. It boots up fine but can't connect to Wifi, cellular, not detected when connected to my PC, and has no real apps to speak of. I think most of the device's drivers are missing. Trying to boot to recovery instead boots to their EncroChat OS which is locked behind a password that neither I nor the person I bought it from knows.
I can get to fastboot and my PC will detect the phone then but running the bootloader unlock command doesn't work, the phone just reboots into the locked EncroChat OS. My idea now is to try and hardbrick the phone and then re-do everything on the phone over again, but I can't figure out how to do that. Does anyone else have any ideas?

Contacting EncroChat
Tried contacting EncroChat via email form, twitter, and reddit. No luck! Still stuck with this. I want to try this unbrick guide: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 for hardbricks but I can't get my phone to show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Any idea how I can do that? This guy seems to have done it:
evronetwork said:
Had one GOOD soft brick in the past, I've used coloros rom(from the Chinese OnePlus One) and fix my phone ...it deleted all media of course but manage to unbrick the phone. Don't ask me how to, it's been a while, google it
It would fix even the most stubborn soft bricks you'll see. Before that I tried everything that was available at the time, no boot as well only fastboot(not even recovery)
Click to expand...
Click to collapse

broccolicakes said:
Tried contacting EncroChat via email form, twitter, and reddit. No luck! Still stuck with this. I want to try this unbrick guide: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 for hardbricks but I can't get my phone to show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Any idea how I can do that? This guy seems to have done it:
Click to expand...
Click to collapse
For your phone to be recognized in your PC as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008, you need to install proper drivers. follow this guide
http://www.androidbrick.com/ultimat...agons-are-unbrickable-qhsusb_dload_qpst_qfil/
let me know, if I can help you furthermore.

broccolicakes said:
Tried contacting EncroChat via email form, twitter, and reddit. No luck! Still stuck with this. I want to try this unbrick guide: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 for hardbricks but I can't get my phone to show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Any idea how I can do that? This guy seems to have done it:
Click to expand...
Click to collapse
Hello dude,
While it was quite some time when I did this unbrick, it was successful ...expect ALL data to be deleted from phone. Google is your friend and I did get all the files from somewhere
You use a special software from the phone, it's coloros software and with provided files it recognise the phone and flash it(2-3 seperate flashes through the software if I remember correctly) - don't worry as long as the phone turns on(mine was turning on but did nothing ...blank, only way to turn it off was to hold power button and hold it(forced turn off))
P.S. The phone wasn't recognised by the OS ...only from this app(cool? ..weird if you ask me - I'm a computer repair tech guy and find this hard to believe if it didn't happen and see it with my own eyes - on the other hand it could be somewhere hidden in the system and recognised like something else so I won't put my hand in fire to verify this )

Thanks!
evronetwork said:
Hello dude,
While it was quite some time when I did this unbrick, it was successful ...expect ALL data to be deleted from phone. Google is your friend and I did get all the files from somewhere
You use a special software from the phone, it's coloros software and with provided files it recognise the phone and flash it(2-3 seperate flashes through the software if I remember correctly) - don't worry as long as the phone turns on(mine was turning on but did nothing ...blank, only way to turn it off was to hold power button and hold it(forced turn off))
P.S. The phone wasn't recognised by the OS ...only from this app(cool? ..weird if you ask me - I'm a computer repair tech guy and find this hard to believe if it didn't happen and see it with my own eyes - on the other hand it could be somewhere hidden in the system and recognised like something else so I won't put my hand in fire to verify this )
Click to expand...
Click to collapse
I figured it out, thanks ! Now I'm stuck with a more minor problem of only having 16gb visible on my 64gb phone. Can't write the userdata_64G image to my phone. Still trying some stuff out and I'll probably just make a new post if I can't get it to work. Thanks again!

broccolicakes said:
I figured it out, thanks ! Now I'm stuck with a more minor problem of only having 16gb visible on my 64gb phone. Can't write the userdata_64G image to my phone. Still trying some stuff out and I'll probably just make a new post if I can't get it to work. Thanks again!
Click to expand...
Click to collapse
I read just the other day that someone needs the 64gb image instead of the 16gb image. You did so well so far, I'm sure you'll figure this one out. Congrats! "Encrochat Beware!"
The mention of the 64gb vs 16gb image is here:
https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
He links to the images here:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541

help
broccolicakes said:
I figured it out, thanks ! Now I'm stuck with a more minor problem of only having 16gb visible on my 64gb phone. Can't write the userdata_64G image to my phone. Still trying some stuff out and I'll probably just make a new post if I can't get it to work. Thanks again!
Click to expand...
Click to collapse
Hi broccolicakes, cane you please tell me how you figured it out. Because Am at your same position with an Oneplus x ??
please tell me how you did it????

redi.c said:
Hi broccolicakes, cane you please tell me how you figured it out. Because Am at your same position with an Oneplus x ??
please tell me how you did it????
Click to expand...
Click to collapse
Hi there, sorry in advance this might not be very helpful in your situation. I ended up using the ColorOS repair tool for Oneplus One that I mentioned earlier in the post. It turned out I just didn't have the correct drivers so once I sorted those out the tool was able to bypass all the software and replace everything on the phone so that I could then install my own OS.
I guess the trick would be to find a version of this tool for OneplusX. I'm not sure if there is one available, I haven't looked. Maybe make a separate post about that? The ColorOS tool I'm talking about is from here: http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136 and it just looks directly for the Qualcomm chip and writes to that. I'm not sure where that tool came from, if it made its way out of Oneplus directly or if someone created it afterwards...

Fastboot not working

Hi everyone,
after a whole day spent try to fix my oneplus 6, now the roblem is that the fastboot is not working anymore. it gets stuck at the starting point with the oneplus logo and the writing Fastboot Mode.
Just to explain better, i rooted my phone but, trying to fix an audio problem, i did something wrong (probavly wiping all datas with twrp) and the phone got stuck at the Fastboot mode (opposite problem that i have now). After i fixed this (flashing manually every partitions) the phone is working again, but i realised that, by mistake, i used the oxygen 9.0.11 for oneplus 6T. So i tried to go to the Fastboot Mode but it gets stuck at that point. I also see that the phone is not rooted anymore.
I installed again Adb and fastboot but it doesn't fix the problem.
Just to give other random informations, the boot loader is still unlocked and i can't lock it.
As you can see i'm totally not an expert. I just wanted to root my oneplus 6 to increase the volume of the headphones.
Anyone that can help me?
Thanks

Pipp8888 said:
Hi everyone,
after a whole day spent try to fix my oneplus 6, now the roblem is that the fastboot is not working anymore. it gets stuck at the starting point with the oneplus logo and the writing Fastboot Mode.
Just to explain better, i rooted my phone but, trying to fix an audio problem, i did something wrong (probavly wiping all datas with twrp) and the phone got stuck at the Fastboot mode (opposite problem that i have now). After i fixed this (flashing manually every partitions) the phone is working again, but i realised that, by mistake, i used the oxygen 9.0.11 for oneplus 6T. So i tried to go to the Fastboot Mode but it gets stuck at that point. I also see that the phone is not rooted anymore.
I installed again Adb and fastboot but it doesn't fix the problem.
Just to give other random informations, the boot loader is still unlocked and i can't lock it.
As you can see i'm totally not an expert. I just wanted to root my oneplus 6 to increase the volume of the headphones.
Anyone that can help me?
Thanks
Click to expand...
Click to collapse
Try: https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
The idea is to boot it in download mode. You'll need the Qualcomm drivers, msm download tool, and oos full rom. Run the tool as administrator.

Pipp8888 said:
Hi everyone,
after a whole day spent try to fix my oneplus 6, now the roblem is that the fastboot is not working anymore. it gets stuck at the starting point with the oneplus logo and the writing Fastboot Mode.
Just to explain better, i rooted my phone but, trying to fix an audio problem, i did something wrong (probavly wiping all datas with twrp) and the phone got stuck at the Fastboot mode (opposite problem that i have now). After i fixed this (flashing manually every partitions) the phone is working again, but i realised that, by mistake, i used the oxygen 9.0.11 for oneplus 6T. So i tried to go to the Fastboot Mode but it gets stuck at that point. I also see that the phone is not rooted anymore.
I installed again Adb and fastboot but it doesn't fix the problem.
Just to give other random informations, the boot loader is still unlocked and i can't lock it.
As you can see i'm totally not an expert. I just wanted to root my oneplus 6 to increase the volume of the headphones.
Anyone that can help me?
Thanks
Click to expand...
Click to collapse
Fastboot require Android SDK(Software Development Kit) and different USB drivers for windows computer may be that's the reason why your Fastboot is not working.
To Root your oneplus 6 :
https://www.theandroidsoul.com/oneplus-6-root/

msm download tool doesn't recognise my phone, and i tried to install the quualcom drivers but my pc whem i try to install it, it says that my phone already has the best drivers.

Pipp8888 said:
msm download tool doesn't recognise my phone, and i tried to install the quualcom drivers but my pc whem i try to install it, it says that my phone already has the best drivers.
Click to expand...
Click to collapse
Maybe uninstall those drivers, reboot pc and reinstall the New ones.

thejase said:
Maybe uninstall those drivers, reboot pc and reinstall the New ones.
Click to expand...
Click to collapse
How can I uninstall the old drivers? Thanks

Pipp8888 said:
How can I uninstall the old drivers? Thanks
Click to expand...
Click to collapse
https://www.drivethelife.com/window...remove-driver-on-windows-10-8-7-xp-vista.html

i unistalled all drivers with Driver Takent. The only driver detected is ADB whem i connect the phone. The Device Manager still recognise my phone in the Usb Devices section as "OnePlus" and still doesn't let me upgrade to the qualcomm drivers.

FINALLY PROBLEM SOLVED with qualcomm drivers!!!! Thank you gus for the big help.
Last question: should i keep useing now the qualcomm drivers? thanks

Pipp8888 said:
FINALLY PROBLEM SOLVED with qualcomm drivers!!!! Thank you gus for the big help.
Last question: should i keep useing now the qualcomm drivers? thanks
Click to expand...
Click to collapse
If it works, yes ofc.

failed root fastboot only help please

I bought a t mobile one plus 7 pro - version gm31cb-on 9.5.10 before I read about the hassle it can be compared to an unbranded phone. The bootloader is unlocked.
I tried the msm tool to go to international version but it got stuck on parameter preload so I decided to try to root and get rid of the tmobile flash screen later.
long story shortened, the phone is stuck on the warning screen.
Pressing buttons, I can get it into fastboot but adb doesnt see the phone to flash/push anything.
If I try to boot into recovery, it sticks at the warning screen.
can I somehow get adb to see the phone in fastboot mode?
do you know if i need a certain os/file so i can get past the parameter preload with msm?
i followed the steps in the msm tutorial.
if msm sees the phone and it gets to parameter preload does it mean it is not a driver issue but maybe the wrong software?
Any advice is appreciated.
thank you for your time and expertise
Marc
through fastboot
I am using the universal fastboot and adb tool and trying to flash boot twrp and start over
current error: failed remote recovery a no such partition
after fastboot --set-active=b
same error
update 2
somehow, after simply trying over and over i got twrp on partition a
i think i will stay here until a kind member can direct me to an img that will work
thank you

marcadamf said:
I bought a t mobile one plus 7 pro - version gm31cb-on 9.5.10 before I read about the hassle it can be compared to an unbranded phone. The bootloader is unlocked.
I tried the msm tool to go to international version but it got stuck on parameter preload so I decided to try to root and get rid of the tmobile flash screen later.
long story shortened, the phone is stuck on the warning screen.
Pressing buttons, I can get it into fastboot but adb doesnt see the phone to flash/push anything.
If I try to boot into recovery, it sticks at the warning screen.
can I somehow get adb to see the phone in fastboot mode?
do you know if i need a certain os/file so i can get past the parameter preload with msm?
i followed the steps in the msm tutorial.
if msm sees the phone and it gets to parameter preload does it mean it is not a driver issue but maybe the wrong software?
Any advice is appreciated.
thank you for your time and expertise
Marc
Click to expand...
Click to collapse
You just need to update Qualcomm drivers.
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659

blas4me said:
You just need to update Qualcomm drivers.
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Click to expand...
Click to collapse
doing so now...
thank you for the help.
I somehow got it up and rooted.
will msm work while rooted or mess up root?
I have a gm1915 wich is not listed in the link for the drivers? any thoughts?

These should work. As for MSM tools use the international version.
If you can't shut off device, hold power + Vup for about 10 seconds without being connected to a power source. If your fast enough, keep device plugged, and just press Vdown, to boot recovery.
https://drive.google.com/file/d/1JoHF6RF1THVn3pQWywaJz2URGTPxL2pH/view

not sure where you are at right now, but i installed a wrong os version (android 10 on my phone with pie on it). It would only boot into fasdtboot screen no matter what I did or tried. Could not get adb to recognize it, had no twrp or rom installed correctly. No way to fix it, could not use MSM tool as phone had to be able to be shutoff, which mine couldn't. never recognized it due to that. tried drivers to no avail. not really many answers out there, til I found out about fastboot roms.
check out this page: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
* IMPORTANT: in above link, remember to only download the OS version that fits your phone previously. DO NOT try to update your phone to a different version using that method. Also this method will NOT work on a branded phone, so if your phone is originally a T-Mobile phone then unfortunately this is not a solution for ya.
You may also want to check out this page as well: https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/
I hope this helps. The Fastboot Rom solution worked for me, it saved me from throwing my phone in the trash. I ran the bat file and it did the rest.

Solved

.

zeroiron said:
Hey guys!
i'm a bloody noob.
i never did something like unbricking my phone or wiping it or flashing it. It was my first time doing something like this because i just hate stock roms nowadays.
to unlocking the bootloader on my phone was no problem. but the problem was, that i updated my phone to adroid 11 and all the files i found in the past (half year ago) was for android 10, i think.
BUT I DIDN'T KNEW THAT BEFORE! I didn't knew that it would cause problems or that i had to be cautions about that.
Whatever. I tried to follow the instructions on this site: https://wiki.lineageos.org/devices/guacamole/upgrade
the twrp site i used was: https://eu.dl.twrp.me/guacamole/
Is the data "https://eu.dl.twrp.me/guacamole/twrp-3.6.0_11-0-guacamole.img.html" from 2021-11-22 know for adroid 11?
Because half year ago, i think, this all didn't work because there was no twrp for adroid 11 outside.
to be honest i don't know if i tried to install something else too in the past. i don't remember anymore.
I stuck half year ago on this bootloop problem. and i didn't worked again on this phone. i thought i could just wait for a new data for android 11 and try it later again.
Later is today but i made i worse!
I downloaded from this site https://download.lineageos.org/guacamole the file:
lineage-18.1-20220227-recovery-guacamole.img
after the command 'fastboot flash boot xxx.img' i reboot my phone.
Now my phone is displaying :
qualcomm crashdump mode
dm-verity device corrupted force dump
kernel-restart
what can i do now?
If i press the sound buttons + off-button i come the the boot screen which says:
blablabla
internetsite
press power button to pause boot
but this display won't stay long enough. after few seconds it's again on this crashdump mode
edit: i think i wiped in the past the whole os. And now? What should i do?
On this MSM Tool my phone isn't recognized. even with newest driver or other cable.
What should i do know? Is my phone lost now?
If some can help me please write exactly down what i should click / download etc.
If someone can german here and knows help, please help me in german. but don't have to. i'm glad if anyone can help me.
Click to expand...
Click to collapse
From what I can gather from your details I would try to get the MSM tool to work, it sounds like a driver issue, just make sure you uninstall previous driver first then go here
https://www.getdroidtips.com/download-qualcomm-qdloader-hs-usb-driver/
and get latest driver , follow all instructions,, also make sure your PC is installing all the optional drivers in the windows update section while your phone is connected to the PC, hth,, good luck

Question Rog Phone 5 Brick

Hello to all,
I apologize in advance for this message.
I mistakenly bricked my phone,
It was running WW-18.0840.2201.226 (Android 11).
I'm not sure if I'm going to be able to use it again, but I'm sure I'll be able to use it again in the future.
The recovery mode does not work anymore. It remains stuck on the logo.
Concerning the device manager :
In Bootloader, nothing is detected
When I test the recovery mode, it detects 'Android Composite ADB interface'.
However, the ADB commands do not work (Unauthaurized)
This is a call for help, I don't know which tutorial to look at to help me.
Do I need to get a Deep Flash Cable to restore the phone?
Excuse my English, I'm French ^^'

Hi, I'm not sure, but I think you will have to delete this POST... It doesn't respect the forum rules... That said, you can follow this link for your problem. https://forum.xda-developers.com/t/...to-unlock-bootloader-to-modify-country-cn-to- ww.4353865/não lido

Hi Rico,
If I have to delete the post I will do it, it's not a problem.
Do you think I can put this post in the topic you gave me?
I had come across it in my research but I didn't know if it needed a Deep Flash Cable
I didn't know that my problem was similar to the one in the post because I don't have a 9008 mode
B.

Balmyr said:
Hi Rico,
If I have to delete the post I will do it, it's not a problem.
Do you think I can put this post in the topic you gave me?
I had come across it in my research but I didn't know if it needed a Deep Flash Cable
I didn't know that my problem was similar to the one in the post because I don't have a 9008 mode
B.
Click to expand...
Click to collapse
There is nothing wrong with your post at all.
Do you have access to see and send Fastboot commands to the phone when on the bootloader screen? You need to get that right first and get your driver on your PC sorted. Forget ADB, that's not going to help you here.
Once you have sorted the above, doing a RAW flash following one of the guides you can find on this form with a rom version that matches your device should get you back on track.
At this stage you shouldn't need EDL or a deep flash cable before exploring the above option.
Good luck.

Hello Andrologic,
Thanks for your reply
I only have access to the Bootloader with 'Start / Restart Bootloader / Recovery Mode / Power Off'.
I bought a Deep Cable, this one detects me when I connect it to the pc, previously my other cables did not want it
So I can indeed use the Fastboot commands whereas before I couldn't

Andrologic said:
There is nothing wrong with your post at all.
Do you have access to see and send Fastboot commands to the phone when on the bootloader screen? You need to get that right first and get your driver on your PC sorted. Forget ADB, that's not going to help you here.
Once you have sorted the above, doing a RAW flash following one of the guides you can find on this form with a rom version that matches your device should get you back on track.
At this stage you shouldn't need EDL or a deep flash cable before exploring the above option.
Good luck.
Click to expand...
Click to collapse
Thank you very much Andrologic!
The phone works like magic again, I can't believe it T_T
When I should do the updates, should I reflash the phone?
It doesn't offer me any new ones even though I'm on Android 11
B.

Balmyr said:
Thank you very much Andrologic!
The phone works like magic again, I can't believe it T_T
When I should do the updates, should I reflash the phone?
It doesn't offer me any new ones even though I'm on Android 11
B.
Click to expand...
Click to collapse
Nice. No, I would suggest updating the conventional way, i.e download ROM for ASUS and let the device pick it up and flash it. If you have TWRP installed, you can flash from there too, but there is no need for that unless the first method is not working