Database Users

[INFO] How to sideload 5.1.1 (LYZ28E), & maintain no encryption - no wipe required

[INFO] How to sideload 5.1.1 (LYZ28E), & maintain no encryption - no wipe required
Simplified procedures with LMY47M / LYZ28E now available as a factory image.
Hopefully this isn't blatantly obvious to everyone, it is a little different than the normal sideload procedure. Thought it might be useful to some who want to load 5.1.1 (and get Wifi calling with T-Mobile!) and not be forced to encrypt.
Requirements:
1. I'm assuming you have adb/fastboot working on your computer / connecting to your device and you understand a little bit about using adb / fastboot with an android phone.
2. Your phone cannot be encrypted, if you're encrypted already - this will not un-encrypt your data - you need to turn off forced encryption and format the "userdata" partition to disable the encryption.
3. You need to have an unlocked bootloader for this to work of course.
How to follow this procedure:
1. If you're on LMY47M (T-Mobile) and unencrypted, you can follow option 2, starting with Step 3 - only a small ~150MB download required.
2. If you're on anything other than LMY47M, you should use option 1 unless you have a desire to flash LMY47M and sideload LYZ28E.
I didn't do much here - except spent a bunch of time writing the procedure.
All Credit for tools / ideas goes to:
- efrant for his explanation of how to get OTA updates to work with TWRP ( http://forum.xda-developers.com/nexus-6/general/nexus-6-ota-help-desk-t2992919/page4 )
- hlxanthus for the NO FORCE ENCRYPT mod ( http://forum.xda-developers.com/nexus-6/development/mod-disable-force-encryption-rom-kernel-t3000788 )
- Q9Nap and mhous33 for the LMY47M factory image ( http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052 )
- bbedward and others for the original disable forced encryption boot.img ( http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715 )
- TeamWin - the TWRP Developer ( https://twrp.me/ )
——————————————————————————————————
OPTION 1 - Easy Method - Flash the LYZ28E factory image directly:
1. Download hlxanthus's NO FORCE ENCRYPT mod and put it onto your phone so you can flash it later (in /storage/sdcard0) - https://basketbuild.com/filedl/devs...u/misc/NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip
2. Download LYZ28E for Nexus 6 ( https://dl.google.com/dl/android/aosp/shamu-lyz28e-factory-b542b88a.tgz ) and extract the files, there is a zip file you want to extract that too.
Boot to the bootloader ("adb reboot bootloader") and fastboot flash the boot, cache, recovery, radio and system:
Code:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img (OPTIONAL - If you have TWRP or another alternative recovery you can skip this step)
fastboot flash radio radio-shamu-<variable>.img
fastboot flash system system.img
3. Restart the Bootloader, and flash TWRP, found here: ( https://twrp.me/devices/motorolanexus6.html )
Code:
fastboot flash recovery twrp-2.8.6.0-shamu.img
4. Restart the Bootloader again and then go to Recovery (TWRP). Now flash NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip through TWRP, and flash SuperSU if you want root and whatever other zips you want to flash (Xposed, etc)
After flashing the NO FORCE ENCRYPT mod, reboot and you should be running 5.1.1 with all of your data and with your userdata partition intact and unencrypted!
———————————————————————————————————————————————————
OPTION 2 - SIDELOAD Method (Makes sense if you’re already on LMY47M):
1. Download hlxanthus's NO FORCE ENCRYPT mod and put it onto your phone so you can flash it later (in /storage/sdcard0) - https://basketbuild.com/filedl/devs...u/misc/NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip
2. Follow the normal procedure, if you're already on LMY47M you can skip to step 3. Download LMY47M for Nexus 6 ( https://dl.google.com/dl/android/aosp/shamu-lmy47m-factory-5228e84a.tgz ) and extract the files, there is a zip file you want to extract that too.
Boot to the bootloader ("adb reboot bootloader") and fastboot flash the boot, cache, recovery, radio and system:
Code:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio-shamu-<variable>.img
fastboot flash system system.img
3. Now flash TWRP, found here: ( https://twrp.me/devices/motorolanexus6.html )
Code:
fastboot flash recovery twrp-2.8.6.0-shamu.img
4. Restart the bootloader, and enter recovery mode (TWRP). Once in TWRP, go to Advanced -> ADB Sideload. You may need to unplug/plug in the USB cable to your computer again.
Download my version of LYZ28E from here: https://www.androidfilehost.com/?fid=23991606952609905
Note: I modified this version to work with TWRP, it will not work with the stock recovery (because I modified it, the signature on the file is now invalid). The only thing I changed was I edited the updater-script to remove the release keys check which seems to fail on the stock recovery and doesn't work right with TWRP).
Code:
adb sideload f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
5. After it finishes, do not reboot yet. Go back and I recommend rebooting to recovery again. Now flash NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip through TWRP, and flash SuperSU if you want root and whatever other zips you want to flash (Xposed, etc)
After flashing the NO FORCE ENCRYPT mod, reboot and you should be running 5.1.1 with all of your data and with your userdata partition intact and unencrypted!

why would you think that you have to be encrypted to push anything to recovery??? plus sideload is only one method to do it, the other is adb push. and if you use twrp recovery, you don't need any of those method's, as you can just move files over to twrp via your usb.

simms22 said:
why would you think that you have to be encrypted to push anything to recovery??? plus sideload is only one method to do it, the other is adb push. and if you use twrp recovery, you don't need any of those method's, as you can just move files over to twrp via your usb.
Click to expand...
Click to collapse
Sorry if I gave the impression you need to be encrypted to push to recovery, that wasn't my intent. Where did I give that impression? I can try to fix it in my original post. At no point in this procedure will your phone be encrypted - there will be times that the kernel will have the force encryption option turned ON in the fstab but you never will boot the phone when that is the case (like right after LRX22C is loaded, after LYM47M is sideloaded, and after you flash the stock boot.img for LYM47M - but you are not booting in any of these cases - not before you install a no forced encryption kernel)
adb push requires the phone is booted right? I wasn't able to get adb push to work in recovery.
I also didn't know TWRP allowed you to copy data over to your phone via USB, I know CWM recovery can do it - but that was a feature missing from TWRP - maybe they added it, I didn't check. You can do an adb push with TWRP, but what in my procedure would you change to use the adb push method in TWRP versus whatever I put in there? The only thing I can think of is asking you to put the mod file on the phone in the beginning.

liqice said:
Sorry if I gave the impression you need to be encrypted to push to recovery, that wasn't my intent. Where did I give that impression? I can try to fix it in my original post. At no point in this procedure will your phone be encrypted - there will be times that the kernel will have the force encryption option turned ON in the fstab but you never will boot the phone when that is the case (like right after LRX22C is loaded, after LYM47M is sideloaded, and after you flash the stock boot.img for LYM47M - but you are not booting in any of these cases - not before you install a no forced encryption kernel)
adb push requires the phone is booted right? I wasn't able to get adb push to work in recovery.
I also didn't know TWRP allowed you to copy data over to your phone via USB, I know CWM recovery can do it - but that was a feature missing from TWRP - maybe they added it, I didn't check. You can do an adb push with TWRP, but what in my procedure would you change to use the adb push method in TWRP versus whatever I put in there? The only thing I can think of is asking you to put the mod file on the phone in the beginning.
Click to expand...
Click to collapse
"So I just figured out how to sideload LYZ28E on my Nexus 6 without enabling forced encryption. "
actually adb push is very easy.. boot unto recovery, type adb push filename.zip, then it pushes to your phone and is listed in the main storage filesystem. id say its nearly identical to adb sideload.

simms22 said:
"So I just figured out how to sideload LYZ28E on my Nexus 6 without enabling forced encryption. "
actually adb push is very easy.. boot unto recovery, type adb push filename.zip, then it pushes to your phone and is listed in the main storage filesystem. id say its nearly identical to adb sideload.
Click to expand...
Click to collapse
Sorry maybe that first sentence is poorly worded. What I meant was, I figured out how to get LYZ28E onto my phone and disable the forced encryption on the OS too. The process wasn't as straightforward because the 2nd sideload wouldn't work correctly without booting into the OS first. After that, I couldn't get the LYZ28E image to sideload on stock recovery or TWRP without errors - but I was able to modify the LYZ28E OTA file so it would load with TWRP, and then I was able to load the no encrypt mod and supersu and get the phone working the way I wanted again.
Are you saying it would be easier if I push the zip file to the phone and install using TWRP as a zip file instead of trying to sideload it?

Step 3: "Hold down the Power and Volume Up button (may need to do it a few times) to get to the Recovery menu".
Actually, the correct key combination is: Hold power, then (while holding power button) press and release volume up.
Works first time, every time.

cam30era said:
Step 3: "Hold down the Power and Volume Up button (may need to do it a few times) to get to the Recovery menu".
Actually, the correct key combination is: Hold power, then (while holding power button) press and release volume up.
Works first time, every time.
Click to expand...
Click to collapse
Thanks, updated the original post.

liqice said:
Sorry maybe that first sentence is poorly worded. What I meant was, I figured out how to get LYZ28E onto my phone and disable the forced encryption on the OS too. The process wasn't as straightforward because the 2nd sideload wouldn't work correctly without booting into the OS first. After that, I couldn't get the LYZ28E image to sideload on stock recovery or TWRP without errors - but I was able to modify the LYZ28E OTA file so it would load with TWRP, and then I was able to load the no encrypt mod and supersu and get the phone working the way I wanted again.
Are you saying it would be easier if I push the zip file to the phone and install using TWRP as a zip file instead of trying to sideload it?
Click to expand...
Click to collapse
easier/harder isnt an option here, since any way takes seconds. im just saying there are several options for this, thats all

liqice said:
Code:
fastboot flash f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
Click to expand...
Click to collapse
Shouldn't this step be
Code:
adb sideload f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
instead of fastboot flash?

So if your starting out with 47E, your rooted and have TWRP ..... would you use adb sideload in TWRP or you issue the command from the PC?

Chahk said:
Shouldn't this step be
Code:
adb sideload f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
instead of fastboot flash?
Click to expand...
Click to collapse
Oops, you're right. Thanks!

Gage_Hero said:
So if your starting out with 47E, your rooted and have TWRP ..... would you use adb sideload in TWRP or you issue the command from the PC?
Click to expand...
Click to collapse
This is where I was, LMY47E, rooted, unencrypted and with TWRP. I followed the entire procedure - went back to LRX22C using fastboot, then sideloaded LMY47M (T-Mobile version) - then flashed the no force encrypt boot.img - booted, after it finished booting, rebooted to the bootloader and so on ...
When you go to LRX22C you flash back to the stock recovery. So you need to boot into the stock recovery, pick "apply update from adb" and then run the adb sideload command from the PC.

Cheers for this.. just what I was looking for. I'm at work so I only scanned this quickly, but any major change in the directions from what you've posted going from an unencrypted LMY47D?

With the factory images being posted, I just did the following:
Flashed the factory images
While still in bootloader, flashed TWRP
Rebooted into TWRP
Pushed SuperSU and the No_Force_encrypt to the /sdcard/ partition
Installed via TWRP
Profit.

lamenting said:
Cheers for this.. just what I was looking for. I'm at work so I only scanned this quickly, but any major change in the directions from what you've posted going from an unencrypted LMY47D?
Click to expand...
Click to collapse
For LMY47D you need to get to LMY47M first, so you would follow the entire procedure, downgrade to LRX22C and then sideload LMY47M and so on.

Heavily updated the procedure since LMY47M and LYZ28E factory images are now available directly from Google.
Should be a lot easier and more straight forward now!

I just recently have this Nexus 6 and came from an LG G2. I went through the process of unlocking the phone and installing rooted LMY47D which meant 2 factory resets in a short period.
I'm now on 5.1 and would like to get rid of the memory leak which this build apparently has.
The title mentions "maintain no encryption".
I never found the time to find out about Lollipop. The title implies that encryption is mandatory on 5.1.1
Is this so?
I merely want the latest upgrade to 5.1.1 and don't want to enforce encryption on my data (Google already knows everything about me) is this the way to achieve this?
I am correct in thinking that I will not get an OTA offered anymore?

Boot loader and radio only...
So if I understand the instructions correctly, if you are still encrypted but rooted, from any Lollipop installation, fast boot flash the factory images... then flash TWRP ... root and done right? Then I have another question... the kernel I am running EX 1.07 along with Flar's app is running perfect for me.... any dangers in just flashing the boot loader and radio? I would like to wait on the system part until the kernel has been updated.....
Also, if I needed to do a restore, if I only flash the boot loader and radio have I pooched being able to go backwards to a nand backup?

FYI, step 3 in option one should read:
fastboot flash recovery twrp-2.8.6.0-shamu.img
vs
fastboot flash twrp-2.8.6.0-shamu.img

frater said:
I just recently have this Nexus 6 and came from an LG G2. I went through the process of unlocking the phone and installing rooted LMY47D which meant 2 factory resets in a short period.
I'm now on 5.1 and would like to get rid of the memory leak which this build apparently has.
The title mentions "maintain no encryption".
I never found the time to find out about Lollipop. The title implies that encryption is mandatory on 5.1.1
Is this so?
I merely want the latest upgrade to 5.1.1 and don't want to enforce encryption on my data (Google already knows everything about me) is this the way to achieve this?
I am correct in thinking that I will not get an OTA offered anymore?
Click to expand...
Click to collapse
Starting with Android Lollipop (5.0) and newer - at least on the Nexus 6 - encryption is turned on by default for the userdata partition.
You would - if you wanted to - backup all of the data on your userdata partition (e.g. Any pictures you've taken with the phone, etc - all of the data basically that shows up when you plug your phone into your computer).
Then you need to be running an OS that doesn't force encryption (for example if you follow my instructions) - this would also get you running 5.1.1.
After that you need to format your userdata - it wouldn't be encrypted at that point, and then copy your data back if you want to.
If you don't care about encryption, you can simply flash the factory 5.1.1 image following my instructions and skip the TWRP parts.

Help help help with a hard bricked 6P

Hello guys,
I had my phone rooted with latest twrp. I flashed stock+ rom with Franco Kernel 25r and the A.R.I.S.E file for better sound. I've done the same set up minus the ARISE file and never had an issue.
well to my luck it kept bootlooping and I wasn't able to get back into my custom recovery. When I got home and got my hands on a pc I did a factory reset by manually flashing stock google img . I even used a couple tools since I ran out of ideas and still no luck.
I'm able to do anything through fastboot but I can't seem to get into my recovery at all.
Any ideas or tips of where I should go next?

Not a Hardbrick
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..

At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.

leninmon said:
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..
Click to expand...
Click to collapse
First of all thank you for the response.
I've tried flashing the most current twrp and it seems to go through fine on fast boot but when I actually try to get into recovery from the device it will boot loop and just keep doing that.
How can I get into the phones storage through fastboot?
Where can I get the factory zip?
it feels as if everything seems to go good through fastboot but when I actually try to boot the phone nothing seems to work.

Wiltron said:
At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.
Click to expand...
Click to collapse
Thanks for the reply.
I've done the manual flashing already and flashed everything single item the most current factory image. Everything seemed to have gone through okay but when I rebooted the phone it was back to 0.
I'm actually considering getting rid of the phone now since it is my daily =/

Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.

Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..

leninmon said:
Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..
Click to expand...
Click to collapse
I flashed the twrp.img and it went through successfully at least on the computer it did but when the phone actually tries to get into recovery (twrp) it will start to boot loop and keep on doing that. I tried both an encrypted and decrypted boot img but it still made no difference.
I'm really going crazy over this

Wiltron said:
Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.
Click to expand...
Click to collapse
I just tried this and had no luck =/....the phone wont get past the google boot screen

You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.

leninmon said:
You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.
Click to expand...
Click to collapse
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through

edgarted said:
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through
Click to expand...
Click to collapse
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.

Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM

i42o said:
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.
Click to expand...
Click to collapse
I was really really hoping this would help. I erase/formated everything before flashing anything. I then ran the flash-all file and it took a couple of minutes and it said finished on the command box and my phone restarted and went into the white google logo and rebooted again with a bootloop. I waited around 15 minutes hoping it would start but it didn't.
It honestly feels as if the phone is not processing the full commands but on the pc it seems to go through successfully
is there a way to force an install of a rom and see if maybe a dirty flash over the stock one will allow it to start up?

leninmon said:
Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM
Click to expand...
Click to collapse
i know how to flash the radio and bootloader but how do i do a fastboot update?

edgarted said:
i know how to flash the radio and bootloader but how do i do a fastboot update?
Click to expand...
Click to collapse
Just unzip the factory image and there U can see the flash shell script files too. Open them in a text editor & U could see the exact command. In a factory img, they also do the same thing via script files. Flashing the radio & bootloader & updating the rest archive

so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/

edgarted said:
so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/
Click to expand...
Click to collapse
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.

blitzkriegger said:
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.
Click to expand...
Click to collapse
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709

edgarted said:
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Click to expand...
Click to collapse
This is weird. What version of the stock factory images did you flash? I've been using leviticus 1.3 since it came out and when i was still on stock rom. I switched over to cm builds and have been flashing every nightly since the 7/24th build, and in the process repeatesly reflashing the aound mod along, and i've had zero issues with the phone booting afterwards.

Bootloop With locked bootloader 7.0

My 6p is stuck in a bootloop. nbd90x build my bootloader is locked is there anyway to unlock from adb. I have already tried sideloading ndb90x through adb wipping chache and user data and still no luck. Help me Xda youre my only hope..

So you previously enabled USB debugging, how about OEM unlocking? If so, use 'fastboot flashing unlock' to unlock the bootloader. Note that internal storage will be completely wiped. Everything. Though with USB debugging enabled, you should be able to adb pull the contents of you SD card first. If you can unlock the bootloader you can try flashing factory images with fastboot. Otherwise, not much else besides RMA it with Google. There's been a few reports of stock N6Ps bootlooping. Haven't seen anyone post that Google denied the claim.

no bootloader is locked so cant flash using flashboot but debugging is enabled so I am able to use adb .

I know. What I'm asking is if you enabled allow OEM unlocking in developer settings? That doesn't unlock your bootloader in itself. You still need to use fastboot to do it. However if that setting IS enabled what you can do is... Use ADB to pull your internal storage to PC. Then use fastboot to unlock the bootloader and flash factory images. If the setting is not enabled, and wiping data and flashing an OTA don't work, I'm not sure what else can be done.
You can try downloading the 7.1 dev preview OTA and seeing if it updates whatever is causing it to fail. Other than those, RMA would be your best bet.
https://developer.android.com/preview/download.html#device-preview

After sideloading a ton of times between 7.0 and 7.1, one time i got it to boot up then i immediately enabled oem unlock then it crashed again... so now I am able to flash through fastboot although I havent been able to get it to boot again. Is it normal for bootloops to not get fixed by flashing?

Hijacking your post to report what is happening to me. I posted the same thing on the Android Beta program community on G+.
Have been using the latest beta since it came out on completely stock 6P (locked bootloader, unrooted). Everything working normally when yesterday around 10 or 11AM, phone starts to bootloop OUT OF NOWHERE, it was just sitting there on the table while I was working. I could still get to bootloader/recovery, so that was a bit of a relief. First thing I tried: clear cache, nothing. Then proceed to wipe/factory reset the device, to no avail. Immediately downloaded the latest factory image from Google's page, tried flashing it but couldn't since the bootloader was locked (OEM unlock option also disabled). Then downloaded the beta OTA and sideloaded it, process went through OK but device still bootloops. Tried sideloading the latest stable OTA but didn't work since it was from a previous build. Ran out of ideas. So there I was creating a thread on XDA for help while the device was still on its bootloop rush, about to hit the Submit button when again OUT OF THE BLUE SKY the device decides to boot itself back up. First thing I did was unlock the bootloader. Phone worked normally for 6 or 7 hours, when I'm doing something on it and then again, screen froze and bootloop starts again. This time I only reset the device and left the it bootlooping, after about 30 minutes it boots up again. I unenrolled from the beta and installed the latest 7.0 build. Everything working fine for the last 12 hours. Anyone have any idea on what can cause the device to bootloop like that? Never seen anything like it.

Yea I signed up for the beta program too do you have the link to unenroll? So you just reset and let it sit?

Here you go
google.com/android/beta

do you remember what you did to get it to boot?

noetre said:
do you remember what you did to get it to boot?
Click to expand...
Click to collapse
Well, that's the thing. Everything I tried didn't seem to work. I couldn't flash the factory image since the bootloader was locked. I was able to sideload the beta OTA but the device still bootlooped after that. So I just left it bootlooping and after around 20 or 30 minutes the device booted normally. I have no idea what caused it and what I did to make it work again.
P.S: device restarted 2 times while I was typing this.

noetre said:
do you remember what you did to get it to boot?
Click to expand...
Click to collapse
If your boot loader is locked you are screwed, sorry to say, I would RMA it. Unbelievable an update can mess a phone up...that's why I always unlock the bootloader first thing and never lock it. I need complete control of my phone.
Edit: Only thing I can think of is delete the partitions with fastboot or adb and reflash factory image.

boot loader is unlocked now Ive tried flashing using the flash-all script but the phone still wont boot

noetre said:
boot loader is unlocked now Ive tried flashing using the flash-all script but the phone still wont boot
Click to expand...
Click to collapse
As a last resort, flash all of the images manually with fastboot. This will wipe all userdata and completely format the SDcard. Nothing will be left. Extract the bootloader and radio images from the factory images zip. Flash them in fastboot. Reboot to fastboot again. Extract the next zip in the same folder as BL & radio images and flash the vendor, system, boot, recovery & userdata image files. Just for good measure, boot to recovery (stock Android recovery) and perform a factory reset & cache wipe. If the phone still fails to boot, your only option would be to RMA it at this point.
Note: As per Heisenberg's sticky thread, do NOT flash userdata.img if you have anything besides the 32gb model as you will only have the ~32gb storage available. If you're using a model with more storage, just use fastboot to format userdata but don't flash the image.

Ill try that.. but isnt the warranty voided because the bootloader is unlocked?

noetre said:
Ill try that.. but isnt the warranty voided because the bootloader is unlocked?
Click to expand...
Click to collapse
Not on a Nexus, no.
Added: I had to RMA mine after the phone got its first update. I unlocked the bootloader and stayed stock for a long time (until N came out). I took the OTA in About Phone and it applied with no problems but the phone would not boot. Factory images also couldn't get it running. Stock recovery and all. RMA'd without issues. I didn't tell them, just sent it in. If they tried to boot it they would've seen the unlock symbol. There's also a thread somewhere buried in the general section where someone called Google and asked and they confirmed to them that unlocking does not void warranty. I'll try to find it for you.
Found it: http://forum.xda-developers.com/nexus-6p/general/unlocking-bootloader-warranty-google-t3229804/page1
I also returned 4 faulty Nexus 5's (mostly screen artifacts) all unlocked with no problems.

again: Cannot unlock bootloader

Hi folks,
I have the problem that the fomerly unlocked bootloader became locked again, and I am not able to unlock it again.
The story:
I got a used OPO 2 a week ago.
I first unlocked the bootloader, installed TWRP 3.0.2, rooted the device, made a backup of the current system and installed LineageOS.
Unfortunately I discovered a bad battery drain, so I restored the backup.
Later I upgraded to Firmware 3.5.6.
When I tried to install a new daily build of LineageOS again the device rebooted immediately when it tried to access WIFI (or mobile, I'm not sure). For testing reasons I restored the old Lineage version (the one with the battery drain). But this installation is now also effected by the reboot bug.
So I dived into the forums and learned that a new modem in 3.5.6 might be the reason for the reboots. People said that rollback to Firmware 3.1.0 via the intermittent Version 3.1.1 will restore the old modem. In order to do the rollback I tried to flash stock recovery and found that the bootloader was locked again and it's not possible to unlock it again. Interestingly even the "tempered" flag has been reset.
I finally reinstalled the V3.1.1 and after it the V3.1.0 with TWRP, but the LineageOS reboot bug still remains Maybe it's not the same than flashing with the stock recovery? Now I'm back to V3.5.6 (Flashing system and backup/restore with TWRP is still possible, only recovery is affected)
I contacted the customers service, but they are not able or willing to help me.
Has anyone encountered that problem?
What can I do.

if you are 100% on OOS 3.1.0 with a locked bootloader, do a factory reset (just in case for a fesh start), boot into the fastboot mode (vol up + power) and type this in the commandprompt/terminal:
fastboot devices (note, here you will have to see your device, otherwise it will do nothing)
fastboot oem unlock
fastboot reboot

unlocked bootloader re-locked itself
@Schinkenwuerfel: Are you reading here, too? Any progress with your's?
FPSUsername said:
if you are 100% on OOS 3.1.0 with a locked bootloader, do a factory reset (just in case for a fesh start), boot into the fastboot mode (vol up + power) and type this in the commandprompt/terminal:
fastboot devices (note, here you will have to see your device, otherwise it will do nothing)
fastboot oem unlock
fastboot reboot
Click to expand...
Click to collapse
I am on 3.5.6 but installed 3.1.0 (with TWRP) but no avail.
After sending "fastboot oem unlock" the phone immediately reboots into recovery and the bootloader is still locked. No error message; no confirmation for a wipe.
Still getting this
Code:
# fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.073s]
finished. total time: 0.073s
btw. I know the commands, buttons and prerequisites for unlocking and have done it before on this device . So, even if it's in good intention, no need to explain the commands.
I'm pretty sure that this is an device issue and not an operator's error.
Any hint in this direction is highly appreciated.

the command is not working because the unlock command only works with oxygen os recovery(stock) it wont work with twrp because it does not prompt for doing this after rebooting. but in stock recovery when unlock command is provided rebooting is done and there appears a prompt for unlocking and wiping. That's the reason. Now the solutions
There are two options:
1st and most preferred is if you have twrp then flash oos 3.1.1 which will restore your modem to old modem without volte then go on this link (https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/ )
and follow guide 2 or 3 it will work as it worked for me too
2nd method
just follow this guide without flashing oos 3.1.1 but u will loose your imei numbers and for the next step you have to flash oos 3.5.7 which can be found on xda on spanna's thread.(not preferred)

raoakashyadav said:
...
There are two options:
1st and most preferred is if you have twrp then flash oos 3.1.1 which will restore your modem to old modem without volte then go on this link (https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/ )
and follow guide 2 or 3 it will work as it worked for me too
2nd method
just follow this guide without flashing oos 3.1.1 but u will loose your imei numbers and for the next step you have to flash oos 3.5.7 which can be found on xda on spanna's thread.(not preferred)
Click to expand...
Click to collapse
That sounds pretty scary to me
I definitely DON'T want to loose my IMEI (already have a null IMEI honor 4x here on my desk ) TWRP seemed to make an EFI backup (that's where the IMEI is stored!?), but due to lack of knowledge I am not confident in that.
Why isn't that mentioned in the OnePlus forum??? People must have bricked their devices !?

tosho1 said:
@Schinkenwuerfel: Are you reading here, too? Any progress with your's?
I am on 3.5.6 but installed 3.1.0 (with TWRP) but no avail.
After sending "fastboot oem unlock" the phone immediately reboots into recovery and the bootloader is still locked. No error message; no confirmation for a wipe.
Still getting this
Code:
# fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.073s]
finished. total time: 0.073s
btw. I know the commands, buttons and prerequisites for unlocking and have done it before on this device . So, even if it's in good intention, no need to explain the commands.
I'm pretty sure that this is an device issue and not an operator's error.
Any hint in this direction is highly appreciated.
Click to expand...
Click to collapse
Never seen someone so disrespectful. @FPSUsername wants to help you and you answered him like this? Damn, don't ask for help so, as it seems you know so well fastboot and bootloader stuff.

tosho1 said:
That sounds pretty scary to me
I definitely DON'T want to loose my IMEI (already have a null IMEI honor 4x here on my desk ) TWRP seemed to make an EFI backup (that's where the IMEI is stored!?), but due to lack of knowledge I am not confident in that.
Why isn't that mentioned in the OnePlus forum??? People must have bricked their devices !?
Click to expand...
Click to collapse
Follow the official 3.5.5 downgrade to 3.1.0 guide. Just wipe system, data and caches, install 3.5.5 and use the guide. Doesn't matter if you have twrp or stock I believe. As long as you have stock with unlocking
Sent from my oneplus2 using Tapatalk

casual_kikoo said:
Never seen someone so disrespectful. @FPSUsername wants to help you and you answered him like this? Damn, don't ask for help so, as it seems you know so well fastboot and bootloader stuff.
Click to expand...
Click to collapse
So, you find it disrespectful to explain, what I know and what I don't? Strange.
You have no Idea how many hours I've spent on this subject alone reading instructions on how to unlock a bootloader. So in my opinion it's a good idea to make it clear what I'm NOT searching for.
But that's pretty off topic here.
Have a nice day.

FPSUsername said:
Follow the official 3.5.5 downgrade to 3.1.0 guide. Just wipe system, data and caches, install 3.5.5 and use the guide. Doesn't matter if you have twrp or stock I believe. As long as you have stock with unlocking
Sent from my oneplus2 using Tapatalk
Click to expand...
Click to collapse
Unfortunately I have twrp and a locked bootloader.
I'm here because I cannot get my bootloader unlocked again.

tosho1 said:
Unfortunately I have twrp and a locked bootloader.
I'm here because I cannot get my bootloader unlocked again.
Click to expand...
Click to collapse
@raoakashyadav already told you the reason. So go ahead, search how too backups EFS (@Spannaa make a tool to backup EFS). If you have TWRP, you have root shell.
Then "go back to stock".
Already told you too much.
Have a nice day, as you say.

Oops. My last reply was ment for @FPSUsername

tosho1 said:
Unfortunately I have twrp and a locked bootloader.
I'm here because I cannot get my bootloader unlocked again.
Click to expand...
Click to collapse
I'm sorry, but do you even read? You have twrp, so wipe your system, data and caches and flash the official 3.5.5, then follow the instructions to go back to 3.1.0
Sent from my oneplus2 using Tapatalk

FPSUsername said:
I'm sorry, but do you even read? You have twrp, so wipe your system, data and caches and flash the official 3.5.5, then follow the instructions to go back to 3.1.0
Sent from my oneplus2 using Tapatalk
Click to expand...
Click to collapse
I read
FPSUsername said:
Doesn't matter if you have twrp or stock I believe. As long as you have stock with unlocking
Click to expand...
Click to collapse
and answered
tosho1 said:
Unfortunately I have twrp and a locked bootloader.
Click to expand...
Click to collapse
I already executed the official rollback process exactly as written there with no avail (see my first post). Still, I can neither unlock the bootloader nor can I install a non-rebooting-all-the-time LineageOS
I think I'll try @raoakashyadav suggestion in a quiet moment after saving my efs.
Thank you for the help so far, and please excuse that I sometimes express myself mistakable. It's a known weakness of mine

if u dont wanna unlock your bootloader and flash custom roms then go for aosp or caf based roms other than lineage or lineage based roms. because at present lineage is rebasing itself to caf which is causing it to have bootloop issue and bypassing setup issue. And if you wanna unlock your bootloader then follow naman bhalla's guide for which the link i have given but save your data in pc because it will wipe everything and repair everything. It also relock your phone's bootloader. The n unlock your bootloader with the commands and then do whatever you want. Hope it will help.
please don't back up efs using twrp because it wont backup due to an anomaly in twrp. So do it manually using commands or use a flashable zip made by spanna then copy that efs backup folder in pc before following naman bhalla's guide.

raoakashyadav said:
please don't back up efs using twrp because it wont backup due to an anomaly in twrp. So do it manually using commands or use a flashable zip made by spanna then copy that efs backup folder in pc before following naman bhalla's guide.
Click to expand...
Click to collapse
Thank you for this valuable hint. I tried to backup the efs parition with TWRP and viewed the logs, but could not find the modem entries in the log that are shown here https://forums.oneplus.net/threads/guide-backup-restore-efs-partition.278167/.
This is like walking on a glacier without a rope
One more silly question:
I cannot find the "=" key in the TWRP (v3.0.2-2) terminal emulator, so cannot save the modem with a 'dd' command.
EDIT: I just tried the dd commands from the adb console, and they SEEMed to work.
Code:
[email protected]:/ # dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.116 secs (9039448 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.057 secs (18396070 bytes/sec)
Is there any way to confirm?

just flash this file from this link and find my backup folder in internal storage.
it always works. and in above case these files are not in any folder they are in internal storage.
Backing up your EFS is the wisest single thing you can do on your smartphone. If you don't and should the worst happen, you will lose mobile connectivity permanently. There are two ways you can do it:
1. Flashing a zip:
- Spannaa has created a TWRP flashable zip: https://www.androidfilehost.com/?fid=385035244224401891
- Check that you are actually left with files called modemst1.bin and modemst2.bin in your internal storage
- Copy them to your PC, cloud, USB stick etc.
2. Doing it manually:
- Download a terminal app from Play Store, for example Material Terminal
- Open it and give it root rights by executing
su
- Give these two commands, one after the other:
dd if=/dev/block/mmcblk0p17 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p18 of=/sdcard/modemst2.bin bs=512
- Check that you are actually left with files called modemst1.bin and modemst2.bin in your internal storage
- Copy them to your PC, cloud, USB stick etc.
Video guide by rishuP can be found here: https://youtu.be/S8OdytR5O9w
Restoring the backup:
- Restoring happens in fastboot mode
- Spannaa's zip contains a scipt that does it for you. Extract it and run restore_all.bat
- Alternatively you can do it manually with these commands:
fastboot flash modemst1 modemst1.bin
fastboot flash modemst2 modemst2.bin

tosho1 said:
Hi folks,
I have the problem that the fomerly unlocked bootloader became locked again, and I am not able to unlock it again.
The story:
I got a used OPO 2 a week ago.
I first unlocked the bootloader, installed TWRP 3.0.2, rooted the device, made a backup of the current system and installed LineageOS.
Unfortunately I discovered a bad battery drain, so I restored the backup.
Later I upgraded to Firmware 3.5.6.
When I tried to install a new daily build of LineageOS again the device rebooted immediately when it tried to access WIFI (or mobile, I'm not sure). For testing reasons I restored the old Lineage version (the one with the battery drain). But this installation is now also effected by the reboot bug.
So I dived into the forums and learned that a new modem in 3.5.6 might be the reason for the reboots. People said that rollback to Firmware 3.1.0 via the intermittent Version 3.1.1 will restore the old modem. In order to do the rollback I tried to flash stock recovery and found that the bootloader was locked again and it's not possible to unlock it again. Interestingly even the "tempered" flag has been reset.
I finally reinstalled the V3.1.1 and after it the V3.1.0 with TWRP, but the LineageOS reboot bug still remains Maybe it's not the same than flashing with the stock recovery? Now I'm back to V3.5.6 (Flashing system and backup/restore with TWRP is still possible, only recovery is affected)
I contacted the customers service, but they are not able or willing to help me.
Has anyone encountered that problem?
What can I do.
Click to expand...
Click to collapse
Hey so i finallly landed here. And I complettly ****ed it up dude.

Schinkenwürfel said:
Hey so i finallly landed here. And I complettly ****ed it up dude.
Click to expand...
Click to collapse
So, what's your current state?
For now I can live with the locked bootloader as I already have TWRP installed and could install the last LineageOS. For the long run off cause I also want that issue to be fixed on my phone, too.
Someone explained to me that unlocking of the bootloader can only be done with the original recovery installed, as part of the unlocking is done by code from the recovery. I have no idea though how to flash a different recovery with a locked bootloader.
Right now I'm too short of time to play with this, but still interested on further information on this subject. The moderator of the OnePlus Forum (the one where all the idiots go mentioned a tool today. I cannot login there as I'm travelling without login data.

[OP6T] fastboot erase persist

Hello ALL!
I normally don't message much because usually I can find most of my problems can be fixed by searching threads online. However, this particular case for me has been exhausting because through trial and error I have been unsuccessful in getting my 6T to boot into any rom normally.
I went from a stock T-Mobile to International version to LOS. The reason I did what I did was because I could get a IMEI or SIM to register on LOS. That worked fine on OOS 9.0.11. but as soon a I flash the latest LOS, no sim, bootloader, or IMEI detection.
I was rooted and unlocked. Now I am neither.
While on LOS, someone on another forum suggested to erase the persist partition and reflash to get the sim imei back so the phone would get service, when the phone rebooted it still didn't work and then the second time it rebooted it always gets stuck on the boot screen and never boots into the OS.
I tried to repair and reflash but was unsuccessful.
Since doing all of that, Ive reflashed using msm tool and although that was successful for OOS 9.0.11 and T-Mobile stock rom. It gets stuck on the boot screens for both.
I flashed LOS on A & B so I don't have a stock recovery.
I can't ADB anymore. I can only seem to connect via FASTBOOT but cannot seem to flash anything because the BOOTLOADER is now LOCKED.
How can I get this phone back to its original state? What ever the persist partition is. Removing it had made the phone non-bootable.
What can I do to fix? I greatly appreciate any help to get the phone operational again.
Thank you all!

https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
- Go to the thread linked above and download the latest OOS (.13) stable.
- Download latest Magisk.
- Have the latest TWRP .img downloaded and on-hand, you will use a few times as well as the installer .zip.
- Be sure to have adb/fastboot installed.
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
- Put your phone into fastboot mode (reboot to bootloader).
- Go to the folder you downloaded in the first step and run the "flash all.bat".
- Ignore errors. If it's get stuck for more than 45 seconds, just hit enter to keep it going.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP.
- In TWRP, go to Reboot and changed the boot partition to the one NOT CURRENTLY enabled. In other words, switch boot partitions.
- Reboot bootloader.
- Go to the folder you downloaded in the first step and run the "flash all.bat" again.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP again.
- Move Magisk installer and TWRP installer from steps two and three onto the internal memory of your device.
- Flash TWRP, reboot recovery to make sure it sticks.
- Flash Magisk for root.
- Wipe dalvik and reboot system.
You will have the latest stable OOS on both partitions at this point! I literally just did this yesterday. Good luck!

..Cory.. said:
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
- Go to the thread linked above and download the latest OOS (.13) stable.
- Download latest Magisk.
- Have the latest TWRP .img downloaded and on-hand, you will use a few times as well as the installer .zip.
- Be sure to have adb/fastboot installed.
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
- Put your phone into fastboot mode (reboot to bootloader).
- Go to the folder you downloaded in the first step and run the "flash all.bat".
- Ignore errors. If it's get stuck for more than 45 seconds, just hit enter to keep it going.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP.
- In TWRP, go to Reboot and changed the boot partition to the one NOT CURRENTLY enabled. In other words, switch boot partitions.
- Reboot bootloader.
- Go to the folder you downloaded in the first step and run the "flash all.bat" again.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP again.
- Move Magisk installer and TWRP installer from steps two and three onto the internal memory of your device.
- Flash TWRP, reboot recovery to make sure it sticks.
- Flash Magisk for root.
- Wipe dalvik and reboot system.
You will have the latest stable OOS on both partitions at this point! I literally just did this yesterday. Good luck!
Click to expand...
Click to collapse
Thank you but how can I flash if my bootloader is locked? Everything I try fails.

I guess the real question is: How can I get the phone to turn on OEM UNLOCK so I can fastboot unlock the Bootloader if it wont boot up the OS?

Is there a way to fix it via the msmdownload tool? Custom file maybe? I've tried the files 9.0.11 & 12 OOS files and all I get is the boot screen white ball logo circling the red ball - stuck in loop and same with stock t-mobile rom.

My friend, sounds like you need to restore your EFS partitions
... I'm trying to figure out how the hell you successfully flashed MSM tool in EDL mode and not have ALL your partitions restored. That tool is supposed to literally write the phone as it came out of the box. Also I think there are different MSM tools for each device respectively, you did use the T-Mobile one right?

Causical said:
My friend, sounds like you need to restore your EFS partitions
... I'm trying to figure out how the hell you successfully flashed MSM tool in EDL mode and not have ALL your partitions restored. That tool is supposed to literally write the phone as it came out of the box. Also I think there are different MSM tools for each device respectively, you did use the T-Mobile one right?
Click to expand...
Click to collapse
My thoughts exactly. So, when it was on LOS I erased the persist partition and that really messed things up. So yes, how can I restore the partition back with a locked bootloader? Every time I've used MSM tool it fixes everything. This time no such luck. I flashed 9.0.11 & 12 and then I did the T-Mobile version. All only boot to the boot screen and hang. In doing so, I wasn't thinking if that failed and it locks the bootloader, then what? I saw an old video somewhere on a oneplus 2 or 3 where the person used the msm tool 3.0 and fixed a bricked locked bootloader phone. Similar to the fastboot method of reformatting. In the msm tool folder he had all the image files for all the partitions not sure if that the same thing as msm tool 4.0 with just one ops image file?
Anyway, is there a way to unlock the bootloader without booting into the OS? Or a way to restore the partitions via msm tool?

defcondoc said:
My thoughts exactly. So, when it was on LOS I erased the persist partition and that really messed things up. So yes, how can I restore the partition back with a locked bootloader? Every time I've used MSM tool it fixes everything. This time no such luck. I flashed 9.0.11 & 12 and then I did the T-Mobile version. All only boot to the boot screen and hang. In doing so, I wasn't thinking if that failed and it locks the bootloader, then what? I saw an old video somewhere on a oneplus 2 or 3 where the person used the msm tool 3.0 and fixed a bricked locked bootloader phone. Similar to the fastboot method of reformatting. In the msm tool folder he had all the image files for all the partitions not sure if that the same thing as msm tool 4.0 with just one ops image file?
Anyway, is there a way to unlock the bootloader without booting into the OS? Or a way to restore the partitions via msm tool?
Click to expand...
Click to collapse
Try this and tell me if it works.

Have you tried this dudes stuff? https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
... Not even sure what it is really, just says collection of unbrick tools.

_Masked_ said:
Try this and tell me if it works.
Click to expand...
Click to collapse
Yes, I did try that. That is what I just flashed with the msm tool. Gets stuck on the OOS boot animation.

Causical said:
Have you tried this dudes stuff? https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
... Not even sure what it is really, just says collection of unbrick tools.
Click to expand...
Click to collapse
Looks like the MSM tool. I'm going to give 9.0.13 a try but I'm thinking I may have the same problem.

Causical said:
Have you tried this dudes stuff? https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
... Not even sure what it is really, just says collection of unbrick tools.
Click to expand...
Click to collapse
Tried 9.0.13. Still gets stuck on OOS boot animation screen. There's got to be something to flash to fix this.

So you're booting EDL mode then flashing the MSM tool that exactly matches the way your phone came stock? At this point I would discontinue trying to convert it to international or upgrade the OS to a more recent version or any of that. I would focus on strictly flashing it to exactly the way you bought it.

Causical said:
So you're booting EDL mode then flashing the MSM tool that exactly matches the way your phone came stock? At this point I would discontinue trying to convert it to international or upgrade the OS to a more recent version or any of that. I would focus on strictly flashing it to exactly the way you bought it.
Click to expand...
Click to collapse
Yes. I did flash the stock T-Mobile ROM via the MSM tool. Freezes at the pink T-Mobile boot screen. Pretty sure the partitions need to be fixed but I thought the MSM tool would do that? I guess not. Is there a more advanced MSM tool where I can see what's being partitioned or is the MSM tool not doing any partitioning and that's why the phone is having the boot problem?

defcondoc said:
Yes. I did flash the stock T-Mobile ROM via the MSM tool. Freezes at the pink T-Mobile boot screen. Pretty sure the partitions need to be fixed but I thought the MSM tool would do that? I guess not. Is there a more advanced MSM tool where I can see what's being partitioned or is the MSM tool not doing any partitioning and that's why the phone is having the boot problem?
Click to expand...
Click to collapse
I know this is a stupid question but have you tried a factory reset in recovery mode? I know its a stupid question but I did not see it asked or noted.

Scott said:
I know this is a stupid question but have you tried a factory reset in recovery mode? I know its a stupid question but I did not see it asked or noted.
Click to expand...
Click to collapse
No stupid questions and I don't mind repeating answers to questions. I have tried that, but it does nothing. I get wipe cache or reboot to fastboot or reboot to recovery. When I choose system wipe, it takes 1 second to finish. It reboots and it gets stuck on the boot screen. Ever since persist partition was deleted it just freezes on startup and now that the bootloader is locked I cant seem to get anything to work. MSM tool I thought was supposed to fix this sort of thing but it has failed. Someone must know a way to get back into the OS so I can turn on OEM Unlock.

How do you know your bootloader is locked?

Causical said:
How do you know your bootloader is locked?
Click to expand...
Click to collapse
Fastboot says bootloader is locked. Shows it on the fastboot screen. Wont let me transfer any files from pc to phone. I can start the transfer process but it fails.

defcondoc said:
Fastboot says bootloader is locked. Shows it on the fastboot screen. Wont let me transfer any files from pc to phone. I can start the transfer process but it fails.
Click to expand...
Click to collapse
So you're able to enter EDL mode with a locked bootloader? How do you know your computer is seeing your device in EDL mode?
I'm going to place this here for myself for now. I'm just trying to understand your situation a little better, but this is just for later.... maybe, depending on your answer. https://forum.xda-developers.com/an...how-to-reboot-to-edl-fastboot-t3394292/page12
ALSO; If you don't mind can you link the thread that contains the original discussion where your problem began?

Causical said:
So you're able to enter EDL mode with a locked bootloader? How do you know your computer is seeing your device in EDL mode?
I'm going to place this here for myself for now. I'm just trying to understand your situation a little better, but this is just for later.... maybe, depending on your answer. https://forum.xda-developers.com/an...how-to-reboot-to-edl-fastboot-t3394292/page12
ALSO; If you don't mind can you link the thread that contains the original discussion where your problem began?
Click to expand...
Click to collapse
The point of EDL is to get around any restrictions or issues with the device, so yes, you can boot to EDL while locked. Your link will not help much because he can already get to EDL. Not to mention he will have no ADB access. Whatever he does, he has to fix it in EDL.
OP: Are you up and running yet? I am willing to try copying out my partition and sending to you.
Let me know...
---------- Post added at 08:12 PM ---------- Previous post was at 08:08 PM ----------
Wait, I just realized that my persist.img would not work because he has no way to flash it.
Nevermind.