Develop Bugs

Softbrick'd. No idea what to do.

I've got quite a problem.
A few weeks ago, I unlocked the bootloader on my phone and flashed SuperSu to root it.
Today I decided to lock it back for personal reasons, wiping everything.
After it wiped, the phone kinda softbricked. When it turns on the OnePlus logo flashes for a second and turns off.
Won't let me unlock bootloader again, got stock recovery. Tried to use sideload, but ADB can't read the file. My guess it's too large.
What can I do?

I had same problem. Follow the steps. Unlock it again and reboot to the system.
There enable developer option, enable debugging, enable unlock bootloader option.
Rebooted to fastboot mode
Install stock recovery
Adb sideload 3.2 full firmware.
After that reboot your phone to fastboot mode.
Unlock bootloader.
This should do it.
Sent from my ONEPLUS A3003 using Tapatalk

It's like you didn't even read what I wrote...
I said it doesn't boot to system, OnePlus logo appears for a split second and phone turns off.
Bootloader is locked and I cannot flash anything.
ADB Sideload won't read files. Gives the 'cannot read' error.

You know that you can load to bootloader by pressing volume up and power button right?
Sent from my ONEPLUS A3003 using Tapatalk

Monskiller said:
I've got quite a problem.
A few weeks ago, I unlocked the bootloader on my phone and flashed SuperSu to root it.
Today I decided to lock it back for personal reasons, wiping everything.
After it wiped, the phone kinda softbricked. When it turns on the OnePlus logo flashes for a second and turns off.
Won't let me unlock bootloader again, got stock recovery. Tried to use sideload, but ADB can't read the file. My guess it's too large.
What can I do?
Click to expand...
Click to collapse
You should be fine so long as you didn't deactivate the"OEM UNLOCK " option from the developer setting....
do the following
1. press and hold the volume up an power buttons simultaneously to enter the boot loader menu.
2.select start option from the bootloader menu sorry that menu is the boot loader.
3. now connect to pc and use the "fastboot devices" command to see if your pc recognizes you op3 as an android device.
4.type "fastboot oem unlock"
5. flash the custom recovery thru fastboot
5. enter custom recovery and flash your desired rom.
hope this works for you!

ajaysoranam said:
You should be fine so long as you didn't deactivate the"OEM UNLOCK " option from the developer setting....
do the following
1. press and hold the volume up an power buttons simultaneously to enter the boot loader menu.
2.select start option from the bootloader menu sorry that menu is the boot loader.
3. now connect to pc and use the "fastboot devices" command to see if your pc recognizes you op3 as an android device.
4.type "fastboot oem unlock"
5. flash the custom recovery thru fastboot
5. enter custom recovery and flash your desired rom.
hope this works for you!
Click to expand...
Click to collapse
And if by mistake I have deactivate the "OEM UNLOCK " what can I do?

I relocked the bootloader. Which wiped to factory reset.
That wipe deactivated the ability to unlock bootloader until reactivated from the system, which I cannot get to because the phone turns off/bootlops before loading it.

This happened quite a few times on this forum, there is really no reason to relock the bootloader on the op3, it is covered through warranty, but u will have to contact oneplus and they should walk u through and send u files to unbrick it if u r lucky

ovidiu1982 said:
And if by mistake I have deactivate the "OEM UNLOCK " what can I do?
Click to expand...
Click to collapse
then you better get in touch with the op customer service. they will, from what i know, fix it thru a remote connection sitting.

I have no solution for you, but I wonder if you went back to stock recovery first before you relocked the bootloader? I think if you have TWRP and try to relock the bootloader, this happens. NOT that its helpful to you, but if this is the case and you can verify it, might help others avoid making the same mistake.
As far as your problem is concerned, I would look for unbricking guides. I know I saw at least one guide that lets you recreate the entire partition table manually and make it just like new for the OP2 (and has the company's blessings to do so). So it should apply here as well. Sorry, do not remember where I saw this, but must have been either on xda or the oneplus forums.

karthikrr said:
I have no solution for you, but I wonder if you went back to stock recovery first before you relocked the bootloader? I think if you have TWRP and try to relock the bootloader, this happens. NOT that its helpful to you, but if this is the case and you can verify it, might help others avoid making the same mistake.
As far as your problem is concerned, I would look for unbricking guides. I know I saw at least one guide that lets you recreate the entire partition table manually and make it just like new for the OP2 (and has the company's blessings to do so). So it should apply here as well. Sorry, do not remember where I saw this, but must have been either on xda or the oneplus forums.
Click to expand...
Click to collapse
I have stock recovery. I did boot TWRP first and let it change system by mistake, but reflashed stock later. That's what might have caused the bootloop once I relocked.
So I guess if you decide to relock in the future, don't flash TWRP, cause it bootloops, even if stock is reflashed.

Bro don't worry now.
I am gonna guide you out of this.
First install an adb package like this.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Now get a toolkit like this.
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Try to connect to fastboot and check for your device in the toolkit.
If failed then kill process adb in your task manager.
Now once connected.
Check OEM status and bootloader status.
Unlock if required.
Now.
Push twrp to your phone .
Then boot into it through the toolkit.
Now load a full ROM.
http://forum.xda-developers.com/oneplus-3/development/rom-op3lite-debloated-tweaked-fast-t3404996
Just copy paste it using your file manager on PC.
Them flash first make it boot and then root.
Hope this helped.

Monskiller said:
I have stock recovery. I did boot TWRP first and let it change system by mistake, but reflashed stock later. That's what might have caused the bootloop once I relocked.
So I guess if you decide to relock in the future, don't flash TWRP, cause it bootloops, even if stock is reflashed.
Click to expand...
Click to collapse
Nah, I think this happens only if you let TWRP modify the system partition. But, I have not and am not willing to test it out

karthikrr said:
Nah, I think this happens only if you let TWRP modify the system partition. But, I have not and am not willing to test it out
Click to expand...
Click to collapse
Don't test it. I've already done it by mistake.
It replaced recovery with TWRP by allowing the modification of system and even after reflashing stock it'll bootloop on relocking recovery.
So I found something useful then.

Hey, i think i found a solution for you. I don't know if i can post here xda thread links, so search "EDL Mode xda" on Google and the first link it is. Hope i helped

Stuck in fastboot. No recovery... no bueno :(

So I had my ze551ml / Z00A rooted, was loving life, all was great. Then I tried getting XPosed access and didn't read up on it prior. Anyways, now my phone is stuck in fastboot, I'm able to flash partitions and all, including recovery partition, yet I cannot enter any mode but the hung ASUS logo, or fastboot. I weas even able to load CM's "upgrade to MM bootloader" package, but still the same thing only with green letters where they once were blue..... Please help, I need my beloved phone back.....

I'm not a pro but if you can access fastboot it is just a soft brick and I'm sure many people can point you on the right thread to recover it.

I've scoured the depths of both XDA and the ASUS forums, and while I've gained much knowledge of how I can possibly fix it, nothing seems to work. I go to select "recovery mode" and it instantly just boots right back in to fastboot.....

joecost85 said:
I've scoured the depths of both XDA and the ASUS forums, and while I've gained much knowledge of how I can possibly fix it, nothing seems to work. I go to select "recovery mode" and it instantly just boots right back in to fastboot.....
Click to expand...
Click to collapse
What ifwi version does it state you have in bootloader screen
Example :-
0094.0XXX
X=?

timbernot said:
What ifwi version does it state you have in bootloader screen
Example :-
0094.0XXX
X=?
Click to expand...
Click to collapse
0094.0183

joecost85 said:
0094.0183
Click to expand...
Click to collapse
Thanks -- you can install giovix`s modder tool from general section
Set it up , use`return to stock option` --in that option , first select boot , then after- recovery(both will be stock)
You then can either
A- Reboot to stock recovery ,adb Sideload stock M -- Follow on to B-( to back-up stock before flashing)
B- Unlock bootloader again , flash twrp and root (if twrp version in modder is now 3.0.3.M4 you can flash lineageos)
---------------------------------------------------------------(if twrp version in modder is still 3.0.2.1 M - you will have to flash 303M4 in fastboot or in 3021M twrp.
1) You might be able to, fastboot flash 3.0.3.M4 immediately and forget above A&B completely
For 303M4 recovery see lineageOS in original android development section OP for download link

timbernot said:
Thanks -- you can install giovix`s modder tool from general section
Set it up , use`return to stock option` --in that option , first select boot , then after- recovery(both will be stock)
You then can either
A- Reboot to stock recovery ,adb Sideload stock M -- Follow on to B-( to back-up stock before flashing)
B- Unlock bootloader again , flash twrp and root (if twrp version in modder is now 3.0.3.M4 you can flash lineageos)
---------------------------------------------------------------(if twrp version in modder is still 3.0.2.1 M - you will have to flash 303M4 in fastboot or in 3021M twrp.
1) You might be able to, fastboot flash 3.0.3.M4 immediately and forget above A&B completely
For 303M4 recovery see lineageOS in original android development section OP for download link
Click to expand...
Click to collapse
So I've yet to try your solution, but I do have an update, I was able to, one by one, flash all the stock files (stock as in the stuff I downloaded from asus site) and was almost able to boot to recovery, but when I got to the red triangle android, I couldn't get it to go further. I've heardf alternate key combos for proceeding from there, and tried them all, but maybe I'm just an idiot...... I'll try the giovix solution when I've got time (patience).
**when I tried flashing the cm upgrade package after that, it went back to square 1, so I gave up for the evening.**

joecost85 said:
So I had my ze551ml / Z00A rooted, was loving life, all was great. Please help I need my beloved phone back.....
Click to expand...
Click to collapse
Hello again , when you come here begging for help to get your life back and someone with the decency gives you a hand ,a solution , out of respect its got to be worth a try ?
joken btw , I typed out a solution to a regular problem that if you try , will work, you can then like and I can direct others to and also help those that search.
At xda , this helps immensely to prevent same posts,people posting just to waste time or just to spam
---------- Post added at 09:30 AM ---------- Previous post was at 09:19 AM ----------
joecost85 said:
So I've yet to try your solution,
but maybe I'm just an idiot...... I'll try the giovix solution when I've got time (patience).
**when I tried flashing the cm upgrade package after that, it went back to square 1, so I gave up for the evening.**
Click to expand...
Click to collapse
The last bit btw wasn't in any of my suggestions
TY
The solution I posted fixes many problems , consider that TWRP is now 303M4 , upgraded .
https://forum.xda-developers.com/ze...-apps-apps-t3554565/post70980108#post70980108

timbernot said:
Hello again , when you come here begging for help to get your life back and someone with the decency gives you a hand ,a solution , out of respect its got to be worth a try ?
joken btw , I typed out a solution to a regular problem that if you try , will work, you can then like and I can direct others to and also help those that search.
At xda , this helps immensely to prevent same posts,people posting just to waste time or just to spam
---------- Post added at 09:30 AM ---------- Previous post was at 09:19 AM ----------
The last bit btw wasn't in any of my suggestions
TY
The solution I posted fixes many problems , consider that TWRP is now 303M4 , upgraded .
https://forum.xda-developers.com/ze...-apps-apps-t3554565/post70980108#post70980108
Click to expand...
Click to collapse
Here's the thing. I'm super stubborn, and I think I know everything (cuz I do....) so of course I decided that I could figure something out, so I tried my way first............ didn't pan out.... anyway, I'm finding any time I flash a TWRP file, I have no access to recovery mode. Regardless if I do it manually through fastboot, or CM upgrade/downgrade or even the giovix fix (yes I tried it). My question is this, Where is there a return to stock option? of the giovix DLs I could find, I see a 'magisk root' 'TWRP' 'bootloader unlocker' and 'Xposed' tools, nothing else.... Am I missing something? or am I just skimming over that part?
I do appreciate all the help, seriously. Even if it seems like I'm not taking suggestions very well. It's moreso I don't have access to a computer most of the day, and it's not a huge priority since I went and bought a zfone 3 max a few days ago (decent phone for what it is....crazy battery life)

https://forum.xda-developers.com/zenfone2/general/tool-ze551mlmodder-t3458145
Functions:
1- Check connection status
2- Bootloader Unlocker
3- Flash TWRP 3.0.2-0 M1
4- Full-auto xposed flasher!
5- Full-auto root flasher!
5B- Full-auto root (Magisk+Phh's) compatible with 184!
6- ADB Shell
7- Return back to stock
8- Erase /system, /data and /cache for a clean upgrade
9 (HIDE)- Auto-reboot to bootloader
10- More functions inside!

well then forgive me for not downloading the correct option. I nowhere see this list among anything I downloaded, so maybe specify which is which ('full' or 'auto')....... I'm already downloading both of them again, because I'm not sure which I already had. But yea, one of the 2 only has the 4 options I mentioned.

Its not rocket science

timbernot said:
Its not rocket science
Click to expand...
Click to collapse
So i finally see what you've been trying to tell me, and I returned everything back to stock, but I still have the same problem, recovery now loads but system wont boot up. I'll try loading the individual factory IMG files today, via fastboot, or should I use a zip file from Asus via recovery?

joecost85 said:
So i finally see what you've been trying to tell me, and I returned everything back to stock, but I still have the same problem, recovery now loads but system wont boot up. I'll try loading the individual factory IMG files today, via fastboot, or should I use a zip file from Asus via recovery?
Click to expand...
Click to collapse
In stock recovery - choose update from adb -- adb sideload cmd is >
adb sideload MOFD_SDUPDATE.zip
Put .134 M asus firmware in adb/fastboot folder first rename it to MOFD_SDUPDATE(without zip) before this cmd above and then open up adb and type it in and hit enter.
Just in case you are trying different methods (see if this works )

timbernot said:
In stock recovery - choose update from adb -- adb sideload cmd is >
adb sideload MOFD_SDUPDATE.zip
Put .134 M asus firmware in adb/fastboot folder first rename it to MOFD_SDUPDATE(without zip) before this cmd above and then open up adb and type it in and hit enter.
Just in case you are trying different methods (see if this works )
Click to expand...
Click to collapse
I'll try it today. Last I checked it was hanging at the ”! Android” screen. But then again I'm not sure I know the combo to get passed that screen, I know it's either power and + or power and - but my only success I got into by button mashing all three keys rapidly, so, yea, I know, I'm am idiot.

joecost85 said:
I'll try it today. Last I checked it was hanging at the ”! Android” screen. But then again I'm not sure I know the combo to get passed that screen, I know it's either power and + or power and - but my only success I got into by button mashing all three keys rapidly, so, yea, I know, I'm am idiot.
Click to expand...
Click to collapse
EDIT"""" because i got it wrong too , i dont even think about , i just do it
It`s ->
From powered off position
Press Power and Vol +
at two vibes, release power
at boot up screen ,release vol+
in bootloader ,scroll vol up or down to and then select(press power) at recovery selection.
At dead android guy -> press vol + and power for 4 seconds -> release Vol +
You should be in recovery.

i am replying in this post since i have a similar problem, and I am as stubborn as OP. Me posting here is a big step in acknowledging my defeat at last. Hours of digging through the internet didn't solve my problem
I have changed my ifwi and dnx more times than i can remember. (my clean slate is mostly using xFSTK downloader with xFSTK_ZE551ML-sal358-amtech.vn files)
Using the above mentioned method (giovix`s modder tool) to go back to stock i still boot into fastboot, not recovery mode.
trying to unlock bootloader it says on the phone "unlock fail"
Using asus flash tool with raw files i get "gpt command failed"
Using a manual method i get the "gpt command failed" on the "6. fastboot oem partition /tmp/partition.tbl" step
in my opinion as soon as i get some kind of recovery my problems are solved. But have been working four hours on this problem with all possible solutions i could think of, nothing but frustration.
info: current ifwi 0094.0183 (wich should be M)
serial 01234........EF
and using the toolkit on "https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293" i found out my device firmware version is 198 (wich is probably not good in combo with the ifwi)
little update in a certain config (android 5 / ifwi 0094.177 / stock recovery) i can boot up untill the dead android icon, but with whatever key combo can't get past it... (vol up + power) / (vol down + power)
fastboot flash boot recovery.img (yep i am really desperate to get into recovery) doesn't even give me the dead android.
thank you beforehand!

Last paragraph with android 5 ifwi 0094.0177
Is your serial correct ?
Press vol + once is it correct?, if not you will have to xfstk first again and flash raw (twice) with temp bootloader 0094.1069
See my unbrick video for help

First of all, thank you very much for your reply!
I was not very specific there, the android 5 is not the rom (still wasnt able to flash the rom) its only the files like droidboot, ifwi, dnx, .... that i got form lolipop.
Indeed the serial is still 1234........EF (so not the correct one)
I do understand i have to flash the raw twice to get the correct serial, but flashing raw doesn't work. I get "gpt command failed" every time. (so the point where i have to restart flashtool is not even reached). Also if i try to do it manualy.
I watched your video (thanks it was my first steps into understanding how it all worked) but unfortunatly didn't work for me.
Any other ideas?

Speybrouck said:
First of all, thank you very much for your reply!
I was not very specific there, the android 5 is not the rom (still wasnt able to flash the rom) its only the files like droidboot, ifwi, dnx, .... that i got form lolipop.
Indeed the serial is still 1234........EF (so not the correct one)
I do understand i have to flash the raw twice to get the correct serial, but flashing raw doesn't work. I get "gpt command failed" every time. (so the point where i have to restart flashtool is not even reached). Also if i try to do it manualy.
I watched your video (thanks it was my first steps into understanding how it all worked) but unfortunatly didn't work for me.
Any other ideas?
Click to expand...
Click to collapse
Did you get this device in this condition ?
If not, what happened so that you lost serial ?
Anyway , i have never tried this because i have ALWAYS succeeded flashing raw (twice) to correct serial BUT it may work for you.( i am not sure you have a device that can have the serial corrected due to whether its been tampered with previous ) which affects recovery and IMEI.
Usually , xFSTK is used to install temp bootloader - Its supposed to be the lowest level form of unbricking procedure and restores temp bootloader so you can fastboot after-- flashing raw in fastboot via AFT(twice) restores serial -- 1st flash approx 3mins is with incorrect serial and temp bootloader.
After a couple of mins, cmds on phone pauses on RESULT=OK on phone.
You close AFT and open AFT again , input raw and set AFT up -- press Vol+ on phone -> once, serial will be corrected and 2nd flash can be started and left until it boots into android 5 by itself.
If GPT trouble , that link may help.
There is other programmes for starting to create serial and restoring .
Usually people who use these , have to dig deep into buildprop stuff which if tampered with can end up with problem such that you have.
Good luck
see if anything here helps
https://forum.xda-developers.com/showpost.php?p=70223946&postcount=8

Oneplus 3 Bricked - Unbrick doesn't work...

Hello guys,
my Oneplus 3 is hard bricked, I tried the methods in the Mega Unbrick guide, my device already gets shown as Qualcomm 9008 ... in Device Manager, so I started the MSM DownloadTool and it flashed anything without errors. But when the phone reboots I get a black screen and the white led is on.
I can't even boot to stock recovery (Volume down + power doesn't work and rebooting to recovery through fastboot doesn't work, too....) my bootloader is locked and all attempts to unlock the bootloader are failing with the error "remote: oem unlock is not allowed"
So at the moment I'm stuck in fastboot and nothing else works -.-
Can someone please help me?
The unbrick tool has an old firmware, can I replace the files with files from a newer firmware?
Thanks!

Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.

Puddi_Puddin said:
Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.
Click to expand...
Click to collapse
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.

min-dfreak said:
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.
Click to expand...
Click to collapse
Ye thats the only thing you can currently do... May i ask what you have done how did it get bricked?

I just updated AICP ota and after flashing the update my phone didn't boot up. The screen went black immediately.
So I thought that it is maybe a Problem with the ROM and I tried to go back to stock.
Flashed the stock recovery and locked the bootloader, but I couldn't boot to the stock recovery.
There it started...

Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.

drmuruga said:
Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.
Click to expand...
Click to collapse
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.

min-dfreak said:
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.
Click to expand...
Click to collapse
Never but never lock your bootloader...

If recovery, boot or system partition is modified. There's no harm in re locking otherwise..

Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off

Dsn Fouad said:
Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off
Click to expand...
Click to collapse
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)

SivaMaxwell said:
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)
Click to expand...
Click to collapse
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?

Dsn Fouad said:
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?
Click to expand...
Click to collapse
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload

SivaMaxwell said:
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload
Click to expand...
Click to collapse
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?

Dsn Fouad said:
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?
Click to expand...
Click to collapse
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery

SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Thanks i will download and give it a try

SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working

Dsn Fouad said:
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working
Click to expand...
Click to collapse
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP

SivaMaxwell said:
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP
Click to expand...
Click to collapse
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it

Dsn Fouad said:
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it
Click to expand...
Click to collapse
Even if the bootloader is locked, you can boot into the current rom and unlock simply by going to advanved options.
It is a very simple process.

Getting "Your device is corrupt. It can't be trusted and may not work properly"

Getting "Your device is corrupt. It can't be trusted and may not work properly"
Hey guys
I tried playign with the new magisk. Decided to factory reset and ran the script, and keep getting:
Getting "Your device is corrupt. It can't be trusted and may not work properly"
Any suggestions? I thought factory reset, literally reset everything...
Thanks in advance

docluv01 said:
Hey guys
I tried playign with the new magisk. Decided to factory reset and ran the script, and keep getting:
Getting "Your device is corrupt. It can't be trusted and may not work properly"
Any suggestions? I thought factory reset, literally reset everything...
Thanks in advance
Click to expand...
Click to collapse
A factory reset erases the partition where user data is stored. It does not touch any other partition. You're getting that message because the phone detects that the boot image is no longer stock. If you want to undo the changes you have made, you'll have to flash the stock Google image.

Ok, SO teh message is normal?
I flashed factory 8.0.0, and I get the same message,
TheSt33v said:
A factory reset erases the partition where user data is stored. It does not touch any other partition. You're getting that message because the phone detects that the boot image is no longer stock. If you want to undo the changes you have made, you'll have to flash the stock Google image.
Click to expand...
Click to collapse

docluv01 said:
Ok, SO teh message is normal?
After I did a factory reset, I got the message, clicked power when it asked to, then phone just sits at the google screen.
Click to expand...
Click to collapse
I haven't had a chance to test Magisk on this phone yet (I returned mine and am waiting on the replacement) but when I've used Magisk in the past, the first boot took a really long time. Give it like 10 minutes or so. If it never makes it past that, something went wrong and you should flash the stock image.
Oh wait, you get the same message if you flash the stock image? Well in that case, I'm not sure what's wrong. You may need to re-lock the bootloader before that message goes away, but make sure you're on 100% stock software before that happens. It might have something to do with the fact that Pixel devices have A and B firmware slots, so if you bring A back to stock, B might still have the Magisk patched image on it. Someone more familiar with Pixel devices should chime in.

TheSt33v said:
I haven't had a chance to test Magisk on this phone yet (I returned mine and am waiting on the replacement) but when I've used Magisk in the past, the first boot took a really long time. Give it like 10 minutes or so. If it never makes it past that, something went wrong and you should flash the stock image.
Click to expand...
Click to collapse
Well, to clarify...
I was able to get Magisk to run fine. But decided I wanted fresh stock image, so went to flash stock google image, flash went fine, but at reboot i get the same thing. could this be a slot issue?

docluv01 said:
Well, to clarify...
I was able to get Magisk to run fine. But decided I wanted fresh stock image, so went to flash stock google image, flash went fine, but at reboot i get the same thing. could this be a slot issue?
Click to expand...
Click to collapse
I'm thinking so. I'm not sure what the proper procedure is for designating which slot you're flashing to on the Pixel 2's, but it's possible that you now have 1 slot with stock firmware and 1 slot with the Magisk patched image. For the original Pixel devices, the partition names were boot_a and boot_b. So I think, and someone please correct me if I'm wrong, fastboot flash boot <file> will flash the file to whichever slot is active, but using boot_a and boot_b will flash to those designated slots. So to fix your issue, you need to make sure that both boot_a and boot_b contain stock images.
Keep in mind that I've never owned a Pixel before now (although I'm pretty comfortable with flashing other android devices), and I'm not 100% sure about this, so you might not want to take my advice.

relock the bootloader.

Here is what I did:
Fastboot flashing lock
fastboot flashing lock_critical
then tried running the flash-all.bat, got FAILED being it was locked
SO then I ran
Fastboot flashing unlock
fastboot flashing unlock_critical
ran flash-all.bat, seemed to have gone fine. Phone reboots, then after you get the circle, where it says "erasing", after about 10 seconds it reboots and says "your device is corrupt..."
Ughhh, I hope I didn't brick this thing???

sorry guys, im an ass, i thought i was using teh latest fastboot, but apparently, not
all is good. I wish I was able to delete this thread

docluv01 said:
sorry guys, im an ass, i thought i was using teh latest fastboot, but apparently, not
all is good. I wish I was able to delete this thread
Click to expand...
Click to collapse
What was the fix cuz i am getting this now after flashing the latest factory image...help!! Lol

canemaxx said:
What was the fix cuz i am getting this now after flashing the latest factory image...help!! Lol
Click to expand...
Click to collapse
relock your bootloader

canemaxx said:
What was the fix cuz i am getting this now after flashing the latest factory image...help!! Lol
Click to expand...
Click to collapse
Make sure you have the latest version of adb and fastboot from the developer site.
https://developer.android.com/studio/releases/platform-tools.html

I got the message as soon as I unlocked the bootloader. It's normal

I had this issue with old platform tools and could not get my device to boot no matter how many times I flash-all'ed or changed the current boot slot. Upgrade to the latest platform tools and run the flash-all from that directory. If it's still not working, I also unlocked critical: fastboot flashing unlock_critical , so that the flash-all could flash my bootloader as well.

Like some have said already. This message appears every time you boot after you unlock your bootloader, whether you are still running stock OS or not. Same thing happened on my 6P. Only way to get it to go away is relocking the bootloader. Don't worry though, your device isn't really corrupt. Just a scare tactic by Google.

charesa39 said:
Like some have said already. This message appears every time you boot after you unlock your bootloader, whether you are still running stock OS or not. Same thing happened on my 6P. Only way to get it to go away is relocking the bootloader. Don't worry though, your device isn't really corrupt. Just a scare tactic by Google.
Click to expand...
Click to collapse
This is somewhat true. There are 2 different messages. One that says you are running unsupported software and the color is orange. This message pops up on every boot while the bootloader is unlocked. The other message says your device is corrupt, in red. The phone will not boot. I just ran into this issue while trying to flash the november update
EDIT:
I was able to resolve this by updating adb/fastboot. I updated adb/fastboot before but i guess i did it on my other computer.

So was there any way to fix this without having to relook the bootloader? I've already had to set this phone up a second time after the longest marathon session of trying to get both TWRP and magisk to live happily together on this device, so I'd rather not do it again if it's avoidable.
Literally all I did to cause this is press the button in TWRP to switch to slot A, and after rebooting I immediately got the new scarier message that requires a power button press to boot, after which you get the regular nag about the unlocked BL. The device then hung at the Google padlock screen, so I used the buttons to reboot into BL then tried TWRP. TWRP then hung at the splash screen, so I hooked up to the PC and fastboot booted TWRP. When I tried to switch back to B, strangely, it said I already was. I pressed the button to switch to B anyway, then rebooted. The error happened again, but at least the device boots. I tried rebooting again to see if it had cleared up, but unfortunately not.
I would really like to be rid of this without having to start over. I do have a nandroid but I don't even know if I trust a restore to be successful and potentially make **** worse. Thanks in advance!

Fastboot setactive=_b
Double check exact command but this worked for me.
Make sure you flash boot.img first using
Fastboot flash boot XXX.img
Sent from my Pixel 2 XL using Tapatalk

matt1313 said:
Fastboot setactive=_b
Double check exact command but this worked for me.
Make sure you flash boot.img first using
Fastboot flash boot XXX.img
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I was able to switch back and forth between the slots with fastboot. I thought maybe I was getting the error because they had two different boot images installed, so I backed up my boot on side B, and then restored it to slot A. No dice. I still get the error message.

IrocD said:
I was able to switch back and forth between the slots with fastboot. I thought maybe I was getting the error because they had two different boot images installed, so I backed up my boot on side B, and then restored it to slot A. No dice. I still get the error message.
Click to expand...
Click to collapse
Flash boot.img first. Don't select which slot
Then reboot bootloader and fastboot active slot b
Sent from my Pixel 2 XL using Tapatalk

Question Soft brick no backup

Hi all!
Long story short, I beefed it...
I tried flashing the unofficial twrp and accidentally did format all on spflashtool.
I'm two months in and for the life of me I can't fix my phone... I've even tried to learn how to write a custom OS myself to fix it but I'm definitely not smart enough.
So, here's where I'm at right now:
When I flash the engineering ROM, the phone boots normally and all that seems to work, but flashing the official MIUI causes a bootloop to the stock recovery.
In there, there's the message "NV data is corrupted".
I'm 2 months in now, so I've seen almost all google pages, so yes, I've tried flashing using the official tool, flashed vbmeta with --disable-verity and --disable-verification.
It's my phone and I have the box here, so I have both IMEI numbers which I managed to flash in the engineering ROM, but flashing the normal MIUI somehow deletes the IMEI numbers again.
I can get into fastboot so the bootloader is unlocked, but I can't boot into the system so I can't enable dev options.
please, if you can help I'm more than happy to answer any other questions and being called an idiot :')
help me, XDA, you're my only hope

check the link
BootLoop not letting me access fastboot
Okay so when I flashed Magisk boot image my device activated boot problems. And when I tried to access recovery mode via adb (from Android Studio), my phone entered a bootloop from which I cannot exit. Vol down + power buttons does not work...
forum.xda-developers.com

I'm in the same exact boat as you...That guide was absolute trash and I can't find anything.

historypm said:
I'm in the same exact boat as you...That guide was absolute trash and I can't find anything.
Click to expand...
Click to collapse
Hold tight, I'm very close to fixing it!
Got everything working except mobile network. As soon as I figure that out, I'll post a fix here

RadixMalum said:
Hi all!
Long story short, I beefed it...
I tried flashing the unofficial twrp and accidentally did format all on spflashtool.
I'm two months in and for the life of me I can't fix my phone... I've even tried to learn how to write a custom OS myself to fix it but I'm definitely not smart enough.
So, here's where I'm at right now:
When I flash the engineering ROM, the phone boots normally and all that seems to work, but flashing the official MIUI causes a bootloop to the stock recovery.
In there, there's the message "NV data is corrupted".
I'm 2 months in now, so I've seen almost all google pages, so yes, I've tried flashing using the official tool, flashed vbmeta with --disable-verity and --disable-verification.
It's my phone and I have the box here, so I have both IMEI numbers which I managed to flash in the engineering ROM, but flashing the normal MIUI somehow deletes the IMEI numbers again.
I can get into fastboot so the bootloader is unlocked, but I can't boot into the system so I can't enable dev options.
please, if you can help I'm more than happy to answer any other questions and being called an idiot :')
help me, XDA, you're my only hope
Click to expand...
Click to collapse
Good evening, sorry for my bad English, but I have the same problem when this happened, I had miui V13.0.7.0 there, I got bootlop, I loaded V12.5.2.0 there and the phone worked everything except the network, try and let me know

You have to download the firmware and paste it into the platform tools folder and click flash all.bat