Subject line pretty much sums it up. I've been to loads of GUIs and walkthroughs - in the end my device remains locked down. I have TWRP as my recovery and a rooted version of the stock CM11S. I have my debugging on. My computer has permission with it set to remember my choice. I've dabbled in both OSX and Windows adb. The goal is to go back to stock EVERYTHING. I'm going to send it back.
Please help.
Lol you told us everything except for which operation is not permitted.
Transmitted via Bacon
Flashing pretty much anything via fastboot. When I 'fastboot oem unlock' the system isnt formatted or anything. Is it because my recovery isnt stock? I've tried restoring stock recovery, but after it loads once, a reboot just goes into TWRP again. I dont understand.
Xephrey said:
Flashing pretty much anything via fastboot. When I 'fastboot oem unlock' the system isnt formatted or anything. Is it because my recovery isnt stock? I've tried restoring stock recovery, but after it loads once, a reboot just goes into TWRP again. I dont understand.
Click to expand...
Click to collapse
If you don't have the stock recovery installed, isn't your bootloader unlocked already? What happens when you issue these commands?
Code:
fastboot devices
Code:
fastboot oem device-info
Transmitted via Bacon
timmaaa said:
If you don't have the stock recovery installed, isn't your bootloader unlocked already? What happens when you issue these commands?
Code:
fastboot devices
Code:
fastboot oem device-info
Transmitted via Bacon
Click to expand...
Click to collapse
C:\Users\Chris\Desktop\android-sdk-windows\platform-tools>fastboot devices
97e265f5 fastboot
and
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
What about the question I asked?
Transmitted via Bacon
Oh sorry. Yeah, that's where things get weird. It's locked now, but I guess I was able to get it unlocked long enough to get TWRP injected. Not sure when / how it locked.
So you don't know at what point this started happening?
Transmitted via Bacon
I don't.
Usually there's a catalyst for things like this, without knowing the catalyst it's difficult to troubleshoot.
Transmitted via Bacon
Well shoot.
Come to think of it, I think I may have typed in oem lock at one point and then unlock promptly thereafter.
Solution
Great news! I've solved the issue. I used OnePlus One Toolkit by @manudroid19
http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
I tried the Experimental Method or #2 to unlock the bootloader. Then you're given the option of downloading TWRP. At first I thought that was lame cause I already had that installed - that's what I was trying to get away from. But I finally understood that I had the option of running that recovery off of my PC by initiating fastboot mode on my One, then typing 'fastboot boot <local path of TWRP.zip I just downloaded>'. And from there I was able to sideload the unlock / tamper toggler as made available here:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Sideload actually completed successfully! I had tried sideload before with every attampt ending in red-text failure. I then went into fastboot mode on my One and flashed stock recovery. Then I used OnePlus One Toolbox v2 by @inthiaano:
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
Because it had stock CM11S as an option. This was also the toolbox I used to flash stock recovery earlier cause I couldn't find it anywhere else. After I flashed that, I did the fastboot boot <local TWRP> sideload unlock toggler again to achieve:
DUN DUN DUN DUUUNNNNN...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
Factory reset and return-ready. FINALLY!
So happy. Now I can get my money back and buy an Nvidia Shield 2 instead.
Related
Hello guys, after a long time with the APPLE, i´ve changed to android.. mainly because of OPO. No regrets.
After a few seconds using it i´ve rooted it and was really happy...
But... after the OTA of the version XNPH30O of CyanogenMod i´m unable to root it again...
I can fastboot... but it stay at the fastboot logo...
Reading arond the interwebs, i´ve realized that it could be something related with the bootloader being locked.... so i´ve unlocked (i think) using the OPO toolkit.. I wiped it and still cannot bypass the fastboot screen..
Any sugestion or help would be awesome.
I´m running th OPO on CyaniogenMod XNPH30O, chinese model.
Thanks and cheers from Brazil.
Go into fastboot mode and issue this command:
Code:
fastboot oem device-info
Post the results.
Transmitted via Bacon
ogabriel said:
Hello guys, after a long time with the APPLE, i´ve changed to android.. mainly because of OPO. No regrets.
After a few seconds using it i´ve rooted it and was really happy...
But... after the OTA of the version XNPH30O of CyanogenMod i´m unable to root it again...
I can fastboot... but it stay at the fastboot logo...
Reading arond the interwebs, i´ve realized that it could be something related with the bootloader being locked.... so i´ve unlocked (i think) using the OPO toolkit.. I wiped it and still cannot bypass the fastboot screen..
Any sugestion or help would be awesome.
I´m running th OPO on CyaniogenMod XNPH30O, chinese model.
Thanks and cheers from Brazil.
Click to expand...
Click to collapse
To root you need to unlock the boot loader than you install a customer recovery. After you do this I recommend that you make a nandroid backup for when you want to go back to stock (a nandoid is an exact back up of you phone). Once you have unlocked the boot loader and installed a custom recovery made a backup you would put a flashable root zip on your SD and flash it in recovery. Most will recommend that you do not use a tool kit because it is doing the work for you and you don't really know/understand what is happening. I have not updated to XNPH30O but I'm sure its been rooted.
You need to have ADB and fastboot on your computer. << Google how to get this done.
Use this guide it will help do the following. >> http://forum.xda-developers.com/showthread.php?t=2788632
1. Put phone in fastboot
2. run command "fastboot OEM unlock" < this is what unlocks the bootloader it wipes your phone.
3. You will need to install a customer recovery
4. Flash the flashable Super User.
Hope this helps.
jdh10475 said:
To root you need to unlock the boot loader than you install a customer recovery. After you do this I recommend that you make a nandroid backup for when you want to go back to stock (a nandoid is an exact back up of you phone). Once you have unlocked the boot loader and installed a custom recovery made a backup you would put a flashable root zip on your SD and flash it in recovery. Most will recommend that you do not use a tool kit because it is doing the work for you and you don't really know/understand what is happening. I have not updated to XNPH30O but I'm sure its been rooted.
You need to have ADB and fastboot on your computer. << Google how to get this done.
Use this guide it will help do the following. >> http://forum.xda-developers.com/showthread.php?t=2788632
1. Put phone in fastboot
2. run command "fastboot OEM unlock" < this is what unlocks the bootloader it wipes your phone.
3. You will need to install a customer recovery
4. Flash the flashable Super User.
Hope this helps.
Click to expand...
Click to collapse
That's all good, but we need more information from him before giving advice, hence my post.
Transmitted via Bacon
timmaaa said:
That's all good, but we need more information from him before giving advice, hence my post.
Transmitted via Bacon
Click to expand...
Click to collapse
True
timmaaa said:
Go into fastboot mode and issue this command:
Code:
fastboot oem device-info
Post the results.
Click to expand...
Click to collapse
I am not the original poster, but I seem to have the same problem—no root after flashing the SuperSU zip file. Here is the result of the above command:
Code:
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.000s]
finished. total time: 0.000s
Thanks everyone for the help...
i´ve been reading a lot since this post... and, still wraping my head in Android rooting.
But i managed to fix the problema... I needed to install the TWRP.
So... in this particular case after entering fastboot i´ve installed TWRP (with OPO toolkit in Boot a recovery>Boot!>TWRP) and proceeded to root after that.
hgmichna said:
I am not the original poster, but I seem to have the same problem—no root after flashing the SuperSU zip file. Here is the result of the above command:
Code:
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.000s]
finished. total time: 0.000s
Click to expand...
Click to collapse
So what exactly is your problem? Your bootloader is unlocked, so just flash TWRP and then flash SuperSU.
Transmitted via Bacon
timmaaa said:
So what exactly is your problem? Your bootloader is unlocked, so just flash TWRP and then flash SuperSU.
Click to expand...
Click to collapse
Had done that at least five times without success, but eventually, after finding a slightly newer version, it worked. Problem solved.
Simple process don't use toolkits
For any newbs reading this, your Oneplus is simple to unlock, add custom recovery and root. Please do not use tool kits follow the simple steps to do it manually. You will be better off in the long run.
jk8260 said:
For any newbs reading this, your Oneplus is simple to unlock, add custom recovery and root. Please do not use tool kits follow the simple steps to do it manually. You will be better off in the long run.
Click to expand...
Click to collapse
What he said. http://forum.xda-developers.com/showthread.php?t=2788632 is a great guide to use. Very easy to follow and doesn't take long.
So I'm in the precarious bootloop nightmare... and I'm pretty noobish at Android on the "developer" side, I'll say. I also didn't have USB Debugging enabled when my phone randomly decided to freak out on me.
I tried the fix found here:
Edit: I can't post links yet. The fix is found at Android Police. Story is titled: Here's An Easy Fix For A OnePlus One Sudden Death Bug That Results In Neverending Boot Loops.
I got to the point where I had to input the "adb shell" command then crashed and burned. My computer never recognized the device on the "adb devices" command... and I'm assuming it's because I don't have USB Debugging enabled. There might be another reason why, but I couldn't tell you. The "fastboot devices" command gave me a valid response when I was in fastboot mode.
I'm kinda all over the place, sorry. Just not really sure what to do from here. Can a noob solve this relatively easy with USB Debugging not enabled (if that's the case)? I've submitted an RMA already, but I have a feeling it's going to take OPO forever to get back to me.
TIA!
When you connect your phone to your pc while in fastboot in device manager does it say Android Adb Device?
th3xeroeagle said:
When you connect your phone to your pc while in fastboot in device manager does it say Android Adb Device?
Click to expand...
Click to collapse
Yes, it does.
What I would do if I was stuck in a bootloop (well thats what I did when I soft bricked my phone "NO OS INSTALLED" now it works again )
is go here https://cyngn.com/products/oneplusone/ download the cm-11.0-XNPH38R-bacon-signed-fastboot.zip extract it in your fastboot folder (make sure you have the latest sdk tools from google or else with an older version it will say that system.img is too large when you flash the zip), open a cmd (run as administrator). check if your bootloader is still unlocked (mine got locked so I was facing a similar situation) type fastboot oem device-info ....it should say unlock true.... then
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot update -w cm-11.0-XNPH33R-bacon-signed-fastboot.zip
Click to expand...
Click to collapse
hope it works
hermunn123 said:
So I'm in the precarious bootloop nightmare... and I'm pretty noobish at Android on the "developer" side, I'll say. I also didn't have USB Debugging enabled when my phone randomly decided to freak out on me.
I tried the fix found here:
Edit: I can't post links yet. The fix is found at Android Police. Story is titled: Here's An Easy Fix For A OnePlus One Sudden Death Bug That Results In Neverending Boot Loops.
I got to the point where I had to input the "adb shell" command then crashed and burned. My computer never recognized the device on the "adb devices" command... and I'm assuming it's because I don't have USB Debugging enabled. There might be another reason why, but I couldn't tell you. The "fastboot devices" command gave me a valid response when I was in fastboot mode.
I'm kinda all over the place, sorry. Just not really sure what to do from here. Can a noob solve this relatively easy with USB Debugging not enabled (if that's the case)? I've submitted an RMA already, but I have a feeling it's going to take OPO forever to get back to me.
TIA!
Click to expand...
Click to collapse
Hey I had the same problem today, went into bootloop and unware of what the problem was i just flashed stock 38R but still had the bootloop. now as you can guess my usb debugging was not enabled but i got out of it here is how.
Go to TWRP>advanced>Terminal command.
now you should see the platform folder here
Just hit select button on the bottom right.
Now just type
make_ext4fs /dev/block/mmcblk0p15
Click to expand...
Click to collapse
And voila you are good to go.:good:
vamshi88 said:
Hey I had the same problem today, went into bootloop and unware of what the problem was i just flashed stock 38R but still had the bootloop. now as you can guess my usb debugging was not enabled but i got out of it here is how.
Go to TWRP>advanced>Terminal command.
now you should see the platform folder here
Just hit select button on the bottom right.
Now just type
And voila you are good to go.:good:
Click to expand...
Click to collapse
This seems like the easiest fix... but I don't have TWRP installed. Is it possible to install that in the state my phone is in?
hermunn123 said:
This seems like the easiest fix... but I don't have TWRP installed. Is it possible to install that in the state my phone is in?
Click to expand...
Click to collapse
What is your phones status now?
vamshi88 said:
What is your phones status now?
Click to expand...
Click to collapse
Completely stock phone that is stuck in the constant on,off bootloop. Can boot into fastboot and CyanogenMod Recovery screens.
hermunn123 said:
Completely stock phone that is stuck in the constant on,off bootloop. Can boot into fastboot and CyanogenMod Recovery screens.
Click to expand...
Click to collapse
I do not use CWM and so i dont know how to help you on that, but flashing TWRP is not hard through Fastboot just follow this guide http://forum.xda-developers.com/showthread.php?t=2788632.
let me know if you need further help.
vamshi88 said:
I do not use CWM and so i dont know how to help you on that, but flashing TWRP is not hard through Flashboot just follow this guide http://forum.xda-developers.com/showthread.php?t=2788632.
let me know if you need further help.
Click to expand...
Click to collapse
He can't flash TWRP because he said he's completely stock, which means the bootloader is locked. Btw, it's fastboot, not flashboot.
Transmitted via Bacon
timmaaa said:
He can't flash TWRP because he said he's completely stock, which means the bootloader is locked. Btw, it's fastboot, not flashboot.
Transmitted via Bacon
Click to expand...
Click to collapse
haha while typing i guess i mixed up flashing and fastboot hence flashboot. Also he can unlock the bootloader now cant he? what happens if he flashes TWRP without unchecking "Update recovery with system updates" (after bootloader unlock)? because after i got into the reboot problem i flashed the factory image, by now my bootloader was already unlocked but i was not able to uncheck the "Update recovery with system updates" or enable the usb debugging. still i flashed TWRP via fastboot and i was good to go.
vamshi88 said:
haha while typing i guess i mixed up flashing and fastboot hence flashboot. Also he can unlock the bootloader now cant he? what happens if he flashes TWRP without unchecking "Update recovery with system updates" (after bootloader unlock)? because after i got into the reboot problem i flashed the factory image, by now my bootloader was already unlocked but i was not able to uncheck the "Update recovery with system updates" or enable the usb debugging. still i flashed TWRP via fastboot and i was good to go.
Click to expand...
Click to collapse
He could try unlocking the bootloader, but my guess is that it will fail with his phone in the current state. Failing to uncheck the 'update cm recovery' option in Developer Options shouldn't pose a problem until an update is taken.
Transmitted via Bacon
Stuck in bootloop
th3xeroeagle said:
When you connect your phone to your pc while in fastboot in device manager does it say Android Adb Device?
Click to expand...
Click to collapse
Hey there,
My OPO is stuck in bootloop and believe me, i just took it out of the box (though it was 4 months without charge).
I cannot put it in to fast boot and I tried power cycling too by discharging it for 12 hours & charging for 6+1 hour. Its just the same.
Can you help?
Hey guys,
before i finally give up on this phone and throw it in the bin, my oneplus phone randomly rebooted while i was using it, while it rebooted it just froze on the cyanogen screen, i powered it off and powered it back on and it still boots up to cyanogen screen.
now here is the weird part, i have tried every fix available on xda, reddit, and the official oneplus forums. i have tried to factory reset, wipe cache+ media, tried to fastboot oem unlock but it doesn't seem to do anything.
iv installed every thing to the tee ( drivers etc) tried different cables. i just think this phone has randomly died outta the blue for no reason(3months), RMA is not an option as i voided the warranty after replacing the oneplus screen my self when it cracked.
i didn't have root and had the CM stock recovery.
i had encryption enabled,
the last thing i did was transfer files to my phone approx 15 mins later it just died.
What do you get when giving this fastboot command?
Code:
fastboot oem device-info
XDA Moderator
Transmitted via Bacon
Heisenberg said:
What do you get when giving this fastboot command?
Code:
fastboot oem device-info
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.006s
21gunSALUTE said:
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.006s
Click to expand...
Click to collapse
Ok, have you tried this yet?
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Heisenberg said:
Ok, have you tried this yet?
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
yes i have, what happens is it shows up as COM then
when i click start the green bar starts then half way it goes off then my device reboots with the sound of windows going dun dun it doesn't show up in device manager after.
21gunSALUTE said:
yes i have, what happens is it shows up as COM then
when i click start the green bar starts then half way it goes off then my device reboots with the sound of windows going dun dun it doesn't show up in device manager after.
Click to expand...
Click to collapse
What build of CM were you running?
Heisenberg said:
What build of CM were you running?
Click to expand...
Click to collapse
CM12.
the thing is i cant seem to factory wipe the phone as well, when i clear/wipe it would go to the android man but it would be flashing few times before it goes back to menu.
21gunSALUTE said:
CM12.
the thing is i cant seem to factory wipe the phone as well, when i clear/wipe it would go to the android man but it would be flashing few times before it goes back to menu.
Click to expand...
Click to collapse
I'm stumped unfortunately. My thought is that you potentially have a spontaneously corrupt persist partition (it's more common than you might want to believe), but you can't fix that with a locked bootloader, and you don't seem to be able to unlock your bootloader. Check this automated tool, it might have success in unlocking your bootloader (probably not but it's worth a try):
http://forum.xda-developers.com/showthread.php?t=2970390
Heisenberg said:
I'm stumped unfortunately. My thought is that you potentially have a spontaneously corrupt persist partition (it's more common than you might want to believe), but you can't fix that with a locked bootloader, and you don't seem to be able to unlock your bootloader. Check this automated tool, it might have success in unlocking your bootloader (probably not but it's worth a try):
http://forum.xda-developers.com/showthread.php?t=2970390
Click to expand...
Click to collapse
its ok thanks for trying to help, i have done this before but ill do it again.
I hope you guys can help me, i have been wandering around blogs forums to find a fix to this issue but to no avail. I got my replacement tablet about a few month ago. I decide to keep the old one and install custom rom on it. The old one is still usable now, but the replacement tablet is dead to me. One day i restart the repl tablet and it just stucked at the fastboot menu. When i choose to go into recovery mode. Nothing happened except a blink of message said that cold linux booting failed. So i try to unlock bootloader to flash it using adb command. Now it wont let me unlock boot loader giving me an error same as the guy here ( i cant paste an outside link here, google : Shield Tablet (LTE) won't boot beyond fastboot, fastboot OEM)
Ps : sorry for bad english im from Malaysia and also im tech newbie
flash the official firmware, you shouldn't need the the bootloader unlocked to flash a signed nvidia package.
this should replace your recovery and system and get you up and running again.
if not, perhaps your NAND is corrupted or damaged.
DreadApex said:
flash the official firmware, you shouldn't need the the bootloader unlocked to flash a signed nvidia package.
this should replace your recovery and system and get you up and running again.
if not, perhaps your NAND is corrupted or damaged.
Click to expand...
Click to collapse
I have downloaded the firmware 3.1.1 2.3gb, but it still required me to unlock bootloader to use this command
Fastboot flash recovery recovery. Img
Fastboot flash boot boot. img
Fastboot flash system. Img
........
Would appreciate if you guys can guide me in this matter
RaybenBB said:
I have downloaded the firmware 3.1.1 2.3gb, but it still required me to unlock bootloader to use this command
Fastboot flash recovery recovery. Img
Fastboot flash boot boot. img
Fastboot flash system. Img
........
Would appreciate if you guys can guide me in this matter
Click to expand...
Click to collapse
Hi,
The "fastboot oem unlock" command don't work?
Elpatii said:
Hi,
The "fastboot oem unlock" command don't work?
Click to expand...
Click to collapse
Nope, also cant detect device using adb devices command. Tried same command in the other shield tablet, work just fine. Its not driver problem.
Tried fastboot oem unlock, and somehow it ask me on the shield to unlock or not, choose unlock and this error occured
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
FAILED (remote: (Unknown error code))
finished. total time: 3.736s
Maybe that you can flash the stock image from NVIDIA (https://developer.nvidia.com/shield-open-source)
Elpatii said:
Maybe that you can flash the stock image from NVIDIA
Trying to flash that one, still it require me to unlock bootloader. I think my chipset was damaged or fried. Have escalate this issue to nvdia, and it seems they want to do a replacement
Click to expand...
Click to collapse
RaybenBB said:
Maybe that you can flash the stock image from NVIDIA
Trying to flash that one, still it require me to unlock bootloader. I think my chipset was damaged or fried. Have escalate this issue to nvdia, and it seems they want to do a replacement
Click to expand...
Click to collapse
I think that's the best solution for now!
So, i got my hands on what i was told hard bricked device. i have no idea what has happened to the device before. first thing i got my hands on it and it did boot to OPO logo. so no hard brick. more like soft brick. tried go to recovery but i cant. it wont go how much i try. booting in to fastboot gives only black screen but my pc will see it (qualcomm hs 6008 etc) where i am able to use oneplus recovery tool and install stock cm11s firmware to it. it goes thru and gives green but device wont boot BUT now i can get to fastboot mode. now it says fastboot mode instead of black screen. running fastboot oem device-info gives this result:
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
This tells me its tampered but relocked. running fastboot oem unlock says OKAY but just reboots my phone (i thing it should go to recovery to unlock it but it does not) after rebooting i cannot get to fastboot mode anymore. just black screen again and i need to run recoverytool again and same results on device-info so it was not unlocked.
ill try to add as much info as i can:
because i cant even get to stock recovery i cant access adb.
Drivers are ok (win 10 test mode etc)
recovery tool does something but cant fix.
flashing anything via fastboot wont write because locked BL
tried toolkits but same errors as commands manually
tried many unbrick guides but no luck (CM or ColorOS)
took boot.img from cm someone suggested but because of that lock i cant flash or boot it at all.
hoping someone could help me. i see much topics about same problem but no solution anywhere...
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Maybe this will help
Or after getting fastboot to work, format every partition and reflash COS.
C4SCA said:
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Maybe this will help
Or after getting fastboot to work, format every partition and reflash COS.
Click to expand...
Click to collapse
actually tried that already but no luck. tried again now and no luck still. stuck on 1+ boot logo.
cant format partitions because its locked. (Device not unlocked cannot flash or erase)
restoring coloros or cm12 does not fix bootloop
migidid said:
actually tried that already but no luck. tried again now and no luck still. stuck on 1+ boot logo.
cant format partitions because its locked. (Device not unlocked cannot flash or erase)
restoring coloros or cm12 does not fix bootloop
Click to expand...
Click to collapse
After these steps can u enter recovery? Tried to factory reset via recovery?
No i still cannot get to recovery no matter what i try. i never could. i can get to cm fastboot and coloros fastboot but no recovery at all. its like its missing. ive been tinkering with this phone for almost a week so ive been trying many times and many combinations but nope.
migidid said:
So, i got my hands on what i was told hard bricked device. i have no idea what has happened to the device before. first thing i got my hands on it and it did boot to OPO logo. so no hard brick. more like soft brick. tried go to recovery but i cant. it wont go how much i try. booting in to fastboot gives only black screen but my pc will see it (qualcomm hs 6008 etc) where i am able to use oneplus recovery tool and install stock cm11s firmware to it. it goes thru and gives green but device wont boot BUT now i can get to fastboot mode. now it says fastboot mode instead of black screen. running fastboot oem device-info gives this result:
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
This tells me its tampered but relocked. running fastboot oem unlock says OKAY but just reboots my phone (i thing it should go to recovery to unlock it but it does not) after rebooting i cannot get to fastboot mode anymore. just black screen again and i need to run recoverytool again and same results on device-info so it was not unlocked.
ill try to add as much info as i can:
because i cant even get to stock recovery i cant access adb.
Drivers are ok (win 10 test mode etc)
recovery tool does something but cant fix.
flashing anything via fastboot wont write because locked BL
tried toolkits but same errors as commands manually
tried many unbrick guides but no luck (CM or ColorOS)
took boot.img from cm someone suggested but because of that lock i cant flash or boot it at all.
hoping someone could help me. i see much topics about same problem but no solution anywhere...
Click to expand...
Click to collapse
I also have the same problem what to do? if your problem is solved tell me how to do?
please help if you fixed this..Same thing is happing to me...
phillipmckinnish said:
please help if you fixed this..Same thing is happing to me...
Click to expand...
Click to collapse
You're not being able to boot into fastboot mode and device is bricked?
Same here but I can't boot into recovery or fastboot or anything...
If you have Linux PC try ubports might fix things then reinstall whatever os you feel like
https://ubuntu-touch.io/get-ut