Related
I'm trying to return to stock without usb, but the links from this post don't work http://forum.xda-developers.com/showpost.php?p=34749844&postcount=2
I need a flashable .zip of the stock rom & recovery so that I can turn my phone in for RMA
studjuice said:
I need a flashable .zip of the stock rom & recovery so that I can turn my phone in for RMA
Click to expand...
Click to collapse
Right now there is no flashable image of the stock OS. Google pulled it from their site. But if you can't use USB, you can still use a computer to unzip the image into partitions, then use terminal and `flash_image` to flash each partition. (When I tried using flash_image, it didn't work, so be cautious. If you're rooted you can also use `dd` to flash images, but a typo could brick your phone so don't.)
I bet the easiest thing for you to do is to create individual flashable images for each partition, then boot into CWM and flash each (recovery last, obviously). But I don't know how. In any case, you'll need to wait until Google puts a new mako image on their site: https://developers.google.com/android/nexus/images
---------- Post added at 07:30 AM ---------- Previous post was at 06:56 AM ----------
Actually, depending on how desperate you are, I (or anybody else) could help you. I have a stock recovery installed right now (JOP40D) and I could pull the image with "dd". That won't be a flashable .zip, but you should be able to flash it from within the ROM. I could also get you a copy of my /system partition--there's nothing personal or private in there
If you have a .img, you could pack it into a flashable .zip and download it via dropbox.
Unless you have no access at all to a computer. In that case, you'll just need to wait for Google to release the next version of the image.
fenstre said:
Right now there is no flashable image of the stock OS. Google pulled it from their site. But if you can't use USB, you can still use a computer to unzip the image into partitions, then use terminal and `flash_image` to flash each partition. (When I tried using flash_image, it didn't work, so be cautious. If you're rooted you can also use `dd` to flash images, but a typo could brick your phone so don't.)
I bet the easiest thing for you to do is to create individual flashable images for each partition, then boot into CWM and flash each (recovery last, obviously). But I don't know how. In any case, you'll need to wait until Google puts a new mako image on their site: https://developers.google.com/android/nexus/images
---------- Post added at 07:30 AM ---------- Previous post was at 06:56 AM ----------
Actually, depending on how desperate you are, I (or anybody else) could help you. I have a stock recovery installed right now (JOP40D) and I could pull the image with "dd". That won't be a flashable .zip, but you should be able to flash it from within the ROM. I could also get you a copy of my /system partition--there's nothing personal or private in there
If you have a .img, you could pack it into a flashable .zip and download it via dropbox.
Unless you have no access at all to a computer. In that case, you'll just need to wait for Google to release the next version of the image.
Click to expand...
Click to collapse
I would love some help on packing into a flashable .zip. I found the images here, http://www.randomphantasmagoria.com/firmware/nexus-4/occam/ but I can't do anything with them without fastboot.
I found one guide for creating the flashable zip here: http://forum.xda-developers.com/showthread.php?t=1721680
And a better one here: http://forum.xda-developers.com/showthread.php?t=1949367
In principle, I think you could use your phone to do these, but it would be hard. The hardest step would be extracting individual files from .img files, and I don't know whether you can do that with your phone--it depends on the kernel and the "mount" utility--you would need to mount the .img files as a filesystem and extract from them. Obviously you should avoid flashing /data to ensure that you can keep /sdcard and your CWM backup. And flashing stock recovery should be your last step. In fact, don't flash your stock recovery. Flash the Nexus image version C, then reboot and let the image automatically reflash the recovery. This is safest. But if this step messes up, you will absolutely need to use a computer to fix it.
Actually, there's a far easier way. Somebody could create a CWM backup for you--a backup of version JOP40C. You download it to /data/media/clockworkmod/backups, then use CWM to recover it (use advanced options to recovery ONLY the /system partition (maybe others?), then clear the cache and dalvik cache). Then you OTA upgrade to JOP40D. This will involve downloading a flashable .zip (here). The key is that this will remove root and CWM when you next reboot! If it doesn't remove root, I think you can probably do that yourself.
The thing you can't do without a computer: lock your bootloader. Is using somebody else's computer really out of the question? I think "adb" and "fastboot" work without the rest of the Android SDK, so you could just download them and get to a computer just for the very final step of re-locking the bootloader.
I documented the process I went through to get it back to stock here for future reference:
http://forum.xda-developers.com/showpost.php?p=37064957&postcount=10
You can lock your bootloader without a computer using the BootUnlocker app
I own a nexus 7 2012, unlocked, rooted, twrp recovery and stock lollipop.After following this
guide http://nexus7.wonderhowto.com/how-to/boost-stock-volume-levels-your-nexus-7-for-louder-sounds-all-around-0158699/#
i lost all the sound in my device!!!Even when i flashed the back-to stock-level zip, nothing happened and i have no sound at all.Probably this guide is not for lollipop, but i want your help.Is there any way to get back the sound, avoiding clean install and setting up the whole tablet from the beggining?
If you open the zip you downloaded, you will notice It contains an xml file. Find a copy of the same file and place it in /system/etc
Technically, you could download a factory image from google, extract the system.img from it and flash it using fastboot
Hi all, I posted this in the 6P bootloop thread, but didn't get a response. As that is a pretty LONG thread, i'm thinking my question may have gotten lost in the jumble.
Quick run down.
A few months back my 6P started the BLOD. I found the fix listed on these pages, applied it, and have been happily using my phone ever since. Phone is bone stock 7.1.2 other than the TWRP recovery and the modified EX kernel for 4 cores.
Since the fix, my phone FINALLY got the OTA update to go to Android 8.0 and i obviously want to get it done. My concern is HOW to do this without causing more headache.
Can anyone point me in the right direction? Should i use the OTA update or download the factory image from Google?
I've got some knowledge as i used to be into the "rooting" scene back in the day, but haven't for a while, so i feel a little lost.
Thanks for any help.
johnnyphive said:
Hi all, I posted this in the 6P bootloop thread, but didn't get a response. As that is a pretty LONG thread, i'm thinking my question may have gotten lost in the jumble.
Quick run down.
A few months back my 6P started the BLOD. I found the fix listed on these pages, applied it, and have been happily using my phone ever since. Phone is bone stock 7.1.2 other than the TWRP recovery and the modified EX kernel for 4 cores.
Since the fix, my phone FINALLY got the OTA update to go to Android 8.0 and i obviously want to get it done. My concern is HOW to do this without causing more headache.
Can anyone point me in the right direction? Should i use the OTA update or download the factory image from Google?
I've got some knowledge as i used to be into the "rooting" scene back in the day, but haven't for a while, so i feel a little lost.
Thanks for any help.
Click to expand...
Click to collapse
Well, for starters do NOT take the OTA. It will either fail or boot loop your phone. Due to the fact you have a modified boot.img you will need to update manually using fastboot with the full image. Re-apply the modified kernel after you finish updating the partitions, but BEFORE booting the first time. You can follow most guides on how to manually update a full image using fastboot, just add the step of flashing the modified kernel before booting.
Thanks for the reply and the help. If i could ask for a little more help, as this is my only phone.
Can you explain the difference between the modified boot.img and the modified kernel?
If i download the factory image from here (https://developers.google.com/android/images) is it ok to the get the latested one (Nov 2017) or do i need to get the original one (Sep 2017 as i'm on Fi)
Once i flash the factory image, is it going to replace the modified boot image as well as the modified kernel?
Follow the OP on this thread (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) in the downloads section there appear to be 2 files i would need, the "Boot.img from stock 6.17, 8.0 firmware" and "EX kernel version 5.03". Am i understanding that correctly?
Like i said, this is my only phone, and i'm probably just being overly paranoid about bricking it, but any clarification would be greatly appreciated.
johnnyphive said:
Thanks for the reply and the help. If i could ask for a little more help, as this is my only phone.
Can you explain the difference between the modified boot.img and the modified kernel?
If i download the factory image from here (https://developers.google.com/android/images) is it ok to the get the latested one (Nov 2017) or do i need to get the original one (Sep 2017 as i'm on Fi)
Once i flash the factory image, is it going to replace the modified boot image as well as the modified kernel?
Follow the OP on this thread (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) in the downloads section there appear to be 2 files i would need, the "Boot.img from stock 6.17, 8.0 firmware" and "EX kernel version 5.03". Am i understanding that correctly?
Like i said, this is my only phone, and i'm probably just being overly paranoid about bricking it, but any clarification would be greatly appreciated.
Click to expand...
Click to collapse
Use the latest November image. The boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. When you flash the new boot.img contained in the Google image, it will overwrite the patched kernel. You then need to re-patch it by installing EX kernel before booting. EX writes to (modifies) the stock boot.img. There are also pre-modifed boot.img files floating around. You will probably get more detailed help in the dedicated thread. Learning to flash manually (or remember how) is not really a big deal and a necessary skill for modding (and for getting yourself out of trouble). Good luck. :good:
v12xke said:
Use the latest November image. The boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. When you flash the new boot.img contained in the Google image, it will overwrite the patched kernel. You then need to re-patch it by installing EX kernel before booting. EX writes to (modifies) the stock boot.img. There are also pre-modifed boot.img files floating around. You will probably get more detailed help in the dedicated thread. Learning to flash manually (or remember how) is not really a big deal and a necessary skill for modding (and for getting yourself out of trouble). Good luck. :good:
Click to expand...
Click to collapse
Ok, so 1 last time (sorry)
1 - Downloaded the latest 8.0.0 factory image from google (this contains the bootloader, radio, and partitions (.zip).
2 - Get phone to fastboot and apply the above 3 new images
3- before rebooting, flash oreo4core (new, modified boot.img), TWRP recovery.img
4- reboot to recovery (TWRP) and apply the modified EX kernel
5 - reboot and (hopefully) profit
Am i missing anything, or doing anything that isn't needed?
johnnyphive said:
Ok, so 1 last time (sorry)
1 - Downloaded the latest 8.0.0 factory image from google (this contains the bootloader, radio, and partitions (.zip).
2 - Get phone to fastboot and apply the above 3 new images
3- before rebooting, flash oreo4core (new, modified boot.img), TWRP recovery.img
4- reboot to recovery (TWRP) and apply the modified EX kernel
5 - reboot and (hopefully) profit
Am i missing anything, or doing anything that isn't needed?
Click to expand...
Click to collapse
<<Disclaimer: I don't use the 4 core kernel, so I don't know if it comes with installer script or someone has just modified the latest boot.img>> Unzip the "partitions" zip you refer to and extract those image files to the same folder as bootloader and modem. For example, you can keep TWRP recovery if you don't flash the recovery.img. That is how you preserve your custom recovery. So in other words you'll now have a folder (your ADB folder?) with 5 image files.... bootloader, radio, boot, system, and vendor all in one folder. <<Note: it is my understanding you just substitute the latest oreo4core file (should be boot.img?) If this is true, copy that file into your ADB folder and let it overwrite the stock boot.img. Stop. Copy over flash-all.bat, change the *.bat extension to *.txt and open in notepad. You will see (and can copy/paste) the fastboot commands to get you started with bootloader and radio. Then flash the last 3 (boot, system, vendor). At this point you can reboot into the OS. Since you substituted the oreo4core boot.img file for the stock boot.img there is no need to use TWRP to flash anything. That and since you skipped flashing the recovery.img, TWRP is still there.
v12xke said:
<<Disclaimer: I don't use the 4 core kernel, so I don't know if it comes with installer script or someone has just modified the latest boot.img>> Unzip the "partitions" zip you refer to and extract those image files to the same folder as bootloader and modem. For example, you can keep TWRP recovery if you don't flash the recovery.img. That is how you preserve your custom recovery. So in other words you'll now have a folder (your ADB folder?) with 5 image files.... bootloader, radio, boot, system, and vendor all in one folder. <<Note: it is my understanding you just substitute the latest oreo4core file (should be boot.img?) If this is true, copy that file into your ADB folder and let it overwrite the stock boot.img. Stop. Copy over flash-all.bat, change the *.bat extension to *.txt and open in notepad. You will see (and can copy/paste) the fastboot commands to get you started with bootloader and radio. Then flash the last 3 (boot, system, vendor). At this point you can reboot into the OS. Since you substituted the oreo4core boot.img file for the stock boot.img there is no need to use TWRP to flash anything. That and since you skipped flashing the recovery.img, TWRP is still there.
Click to expand...
Click to collapse
Thank for the help! Everything seems to be up and running. I know you said you don't use the "4 cores" (can only assume your either on a different phone or yours isn't affected by the BLOD), but do you know if i still need to apply the EX kernel update, or know of a way to tell if it's already been applied?
Thanks again for all the help. I was pretty much in the right direction, but being as how i'd been away from it for a while, i wanted some backup
johnnyphive said:
Thank for the help! Everything seems to be up and running. I know you said you don't use the "4 cores" (can only assume your either on a different phone or yours isn't affected by the BLOD), but do you know if i still need to apply the EX kernel update, or know of a way to tell if it's already been applied? Thanks again for all the help. I was pretty much in the right direction, but being as how i'd been away from it for a while, i wanted some backup
Click to expand...
Click to collapse
I don't think you can flash EX kernel from now on. I think you have to use a modded boot.img that will contain his kernel/ramdisk. This is my guess. You really should be getting your information in the dedicated thread where everyone is actually installing and using it. Google "oreo 4 core" and you will find the XDA thread is the first hit. Good luck. :good:
[DEPRECATED] no longer working on due to real life issues. [DEPRECATED]
Please feel free to use my post and work on it yourselves, sorry.
Nexus 5x BLOD fix (OPM2.171019.029)
I recently purchased a Nexus 5x from ebay; it had the BLOD issue and, after many days I managed to fix it.
So I have decided to update the boot image to the 'latest' android factory image; this will allow people who have applied the patch to use a later version of Android or a custom ROM.
A huge thanks to @XCnathan32 for the original fix!
The steps below will wipe all data from your device!
For Rooting Information and Google Pay fix, see 2nd post.
Changelog
02/05/2018 - Updated method and added custom ROM method.
01/05/2018 - Updated TWRP from version 3.1.1.0 to 3.2.1-0.
What does this do?
There are two versions;
The first process will install the 'newest' stock version of Android onto your device; it will then install a custom recovery, and finally flash the updated boot.img file.
The boot.img has been modified slightly to only use 4 out of the 6 cores on the processor, this fixes the overheating issue with the Nexus 5x devices.
The other version is similar except using a custom version of Lineage OS.
Instructions
For detailed instructions and more info please visit the original thread.
Please make sure to have all of the downloaded file ready.
First Method - Stock Image
1. Boot into fastboot mode.
2. Extract factory image zip file and go into its directory.
3. With the phone in fastboot mode and connected the computer, open 'flash-all.bat'.
3a. Let the process finish; the device will reboot.
4. Go back into fastboot mode.
4a. [optional] you may wish to flash a custom recovery. If so move into the directory where you have the custom image downloaded. follow step 6a and type in
Code:
fastboot flash recovery [filename].img
5. Now move into the directory in which you downloaded the boot.img file.
6. Once inside; shift-right-click in the file manager and select 'open in powershell' or 'open in cmd'
7. Once the command window has opened: type in
Code:
fastboot flash boot boot.img
8. Now reboot the device!
Second Method - Custom ROM
1. Boot the device into fastboot mode
2. Download the ROM [linked below].
3. Download the GAPPS package [linked below].
4. Download Magisk [linked below].
5. Download the stock factory image; this is important as it contains the newest version of the bootloader, radio and vendor images, which is needed for Lineage to work [linked below].
6. Extract the stock factory image and go into it’s directory.
6a. There should be a file called ‘flash-all.bat’ - double-click to run it (Make sure phone is plugged in and in fastboot mode!).
6b. Let the process finish; the device should reboot.
7. Once the device has rebooted, again make sure it’s in fastboot mode.
8. Now download the custom version of TWRP; go into it’s directory then shift-right-click and select ‘open with cmd’ or ‘open with powershell’.
9. Then type the following:
Code:
fastboot flash recovery [filename].img
10. Once that process has finished (it should only take a sec), boot into recovery mode by selecting it via the volume up & down keys; the using the power button to select.
11. Once in recovery;
11a. Copy and paste the ROM zip archive, Magisk and the GAPPS package to the phone. You should be able to view your phone in the file explorer. If not please install the adb & fastboot drivers.
11b. Once done; go to ‘Install’ -> the select the zip file you transfered. It will now ask you to confirm, drag the bar across to accept the flash.
12. The ROM will now be flashing; leave it until it is done!
13. Once that process has finished; go back into the install section.
13a. Now you need to flash the GAPPS package.
14. Once the GAPPS has finished flashing; you now need to flash Magisk. This allows you to root your device and use services like Google Pay.
15. Now reboot!
If all is good then the device will reboot. You should see a boot animation (This can take up to 30 mins, so please wait!), after you should now see the android setup process.
Downloads
The fixed boot image can be downloaded from here.
The factory image: please make sure the version you are downloading matches the updated boot images'. It can be found here.
Modified Lineage OS ROM (boot image updated to the fix); it can be found here.
Magisk -> here.
GAPPS -> here. (Download for ARM64).
A fixed version of TWRP created by @XCnathan32 and updated by me to work with the 4-core boot image. Download Here.
Disclaimer
I will not be held responsible for anyone that decides to proceed with the steps listed above. If there are any issues please post them below with as much detail as you can. I will try my best to answer them, but I do have real-life stuff to deal with.
The original mod was not created myself! I have simply updated it.
Rooting info & Google pay fix
Rooting info & Google Pay fixFlashing Magisk after ROM will allow you to have root privileges and will also allow you to use
Magisk: it's HERE
My phone has bootloader locked. Is it needed?
lollazzo said:
My phone has bootloader locked. Is it needed?
Click to expand...
Click to collapse
Unfortunately, it is required so that you can flash the images. If you can't turn the device on then try the steps linked below;
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Goto the "*If your phone is bootloader locked/OEM locked:" section, I had the same issue and freezing my phone for 15 mins worked great.
Might work for you to
could you please fix the link to the Modified Lineage OS ROM.
thank you
deoneR said:
could you please fix the link to the Modified Lineage OS ROM.
thank you
Click to expand...
Click to collapse
Fixed it sorry for the wait; was busy with college etc.
if i do all your steps for the second method i always get a reboot to TWRP after ~ 3mins
what am i doing wrong?
deoneR said:
if i do all your steps for the second method i always get a reboot to TWRP after ~ 3mins
what am i doing wrong?
Click to expand...
Click to collapse
Try following method #1 first, then If you want; flash the custom ROM etc.
The custom ROM I provided works for me so I'm not 100% sure why it's not working. Trying the first method may help :|
lollazzo said:
My phone has bootloader locked. Is it needed?
Click to expand...
Click to collapse
Freezing did not worked for me , I put mine the oven and heated it to about 60 Grad Celsius.
That even gave me enough time to back up my data .
however, is back to live because of this tread.
Thanks.
This is the clear and simple instructions that always make things work first try! Thank you so much!
For June 5th security update I managed to work with those instructions, works perfect with making my own 4 core boot image and recovery.
http://aurelio.net/articles/nexus-5x-bootloop-fix.html
First fix that actually brought my phone back to life
Wow, amazing job, thank you very much! I tried many other methods to fix my device, and some allowed me to boot back into my phone, but I encountered errors like my wifi died etc. So I thought it was the end for my device and it turned into a very expensive USB flash drive lol. I don't know how your fix differs from the other ones on xda ( I used the first method), but it worked for me. So thanks again!
Something happened to my phone today. Its running 8.1 Pixel rom with the bload fix applied. All of a sudden my phone turned off today after running fine from so many months with blod fix. Now it doesn't boot. Google logo and turns off. Not even recovery is working (TWRP 4 core, patched). Can anyone suggest what's wrong?
Dragon's Fedora said:
Nexus 5x BLOD fix (OPM2.171019.029)
I recently purchased a Nexus 5x from ebay; it had the BLOD issue and, after many days I managed to fix it.
So I have decided to update the boot image to the 'latest' android factory image; this will allow people who have applied the patch to use a later version of Android or a custom ROM.
A huge thanks to @XCnathan32 for the original fix!
The steps below will wipe all data from your device!
For Rooting Information and Google Pay fix, see 2nd post.
Changelog
02/05/2018 - Updated method and added custom ROM method.
01/05/2018 - Updated TWRP from version 3.1.1.0 to 3.2.1-0.
What does this do?
There are two versions;
The first process will install the 'newest' stock version of Android onto your device; it will then install a custom recovery, and finally flash the updated boot.img file.
The boot.img has been modified slightly to only use 4 out of the 6 cores on the processor, this fixes the overheating issue with the Nexus 5x devices.
The other version is similar except using a custom version of Lineage OS.
Instructions
For detailed instructions and more info please visit the original thread.
Please make sure to have all of the downloaded file ready.
First Method - Stock Image
1. Boot into fastboot mode.
2. Extract factory image zip file and go into its directory.
3. With the phone in fastboot mode and connected the computer, open 'flash-all.bat'.
3a. Let the process finish; the device will reboot.
4. Go back into fastboot mode.
4a. [optional] you may wish to flash a custom recovery. If so move into the directory where you have the custom image downloaded. follow step 6a and type in
Code:
fastboot flash recovery [filename].img
5. Now move into the directory in which you downloaded the boot.img file.
6. Once inside; shift-right-click in the file manager and select 'open in powershell' or 'open in cmd'
7. Once the command window has opened: type in
Code:
fastboot flash boot boot.img
8. Now reboot the device!
Second Method - Custom ROM
1. Boot the device into fastboot mode
2. Download the ROM [linked below].
3. Download the GAPPS package [linked below].
4. Download Magisk [linked below].
5. Download the stock factory image; this is important as it contains the newest version of the bootloader, radio and vendor images, which is needed for Lineage to work [linked below].
6. Extract the stock factory image and go into it’s directory.
6a. There should be a file called ‘flash-all.bat’ - double-click to run it (Make sure phone is plugged in and in fastboot mode!).
6b. Let the process finish; the device should reboot.
7. Once the device has rebooted, again make sure it’s in fastboot mode.
8. Now download the custom version of TWRP; go into it’s directory then shift-right-click and select ‘open with cmd’ or ‘open with powershell’.
9. Then type the following:
Code:
fastboot flash recovery [filename].img
10. Once that process has finished (it should only take a sec), boot into recovery mode by selecting it via the volume up & down keys; the using the power button to select.
11. Once in recovery;
11a. Copy and paste the ROM zip archive, Magisk and the GAPPS package to the phone. You should be able to view your phone in the file explorer. If not please install the adb & fastboot drivers.
11b. Once done; go to ‘Install’ -> the select the zip file you transfered. It will now ask you to confirm, drag the bar across to accept the flash.
12. The ROM will now be flashing; leave it until it is done!
13. Once that process has finished; go back into the install section.
13a. Now you need to flash the GAPPS package.
14. Once the GAPPS has finished flashing; you now need to flash Magisk. This allows you to root your device and use services like Google Pay.
15. Now reboot!
If all is good then the device will reboot. You should see a boot animation (This can take up to 30 mins, so please wait!), after you should now see the android setup process.
Downloads
The fixed boot image can be downloaded from here.
The factory image: please make sure the version you are downloading matches the updated boot images'. It can be found here.
Modified Lineage OS ROM (boot image updated to the fix); it can be found here.
Magisk -> here.
GAPPS -> here. (Download for ARM64).
A fixed version of TWRP created by @XCnathan32 and updated by me to work with the 4-core boot image. Download Here.
Disclaimer
I will not be held responsible for anyone that decides to proceed with the steps listed above. If there are any issues please post them below with as much detail as you can. I will try my best to answer them, but I do have real-life stuff to deal with.
The original mod was not created myself! I have simply updated it.
Click to expand...
Click to collapse
With the second method, I flash all the files separately, and when I reboot it, the bootagement of Lineage OS started, but it got stuck, how do I fix it?
Dragon's Fedora said:
Nexus 5x BLOD fix (OPM2.171019.029)I recently purchased a Nexus 5x from ebay; it had the BLOD issue and, after many days I managed to fix it.
So I have decided to update the boot image to the 'latest' android factory image; this will allow people who have applied the patch to use a later version of Android or a custom ROM.
Click to expand...
Click to collapse
Good job! Works great for me and my similarly acquired device. Easy to read and follow write up too!
For others who may have done something weird like myself during the flash all process. The only issue I had initially was getting a boot and recovery sig not verified error message (or something like that). Worked around it by extracting the zipped image-bullhead-opm file and copying my fastboot files within the folder then fastboot flashing recovery, system and vendor manually. Then everything per steps explained worked as described. This is probably a common, well known error and fix to the BLOD Nexus 5X owners but I've just had this crazy device 2 days.
Thanks again!
Used 2nd method and worked perfectly.
Phone has been on non-the-less for a solid 3 hours and battery is stable (had really bad battery drain before, and the system was locking up and freezing and unresponsive as well 2-3 weeks before the BLOD.
I had also previously tried to flash a few other newer 8.1 roms after getting this BLOD, however phone crashed several times during installation and returned to BLOD and was unable to return to TWRP/recovery.
Glad the phone is back to life. Thanks a bunch for the modified rom, TWRP link, and guide!
On a side note, do you feel it is safe to try to flash other vendor images + roms + kernels now... or will the device go back to BLOD. From what I understood this is hardware issue, not software? @Dragon's Fedora
only4dank said:
Used 2nd method and worked perfectly.
Phone has been on non-the-less for a solid 3 hours and battery is stable (had really bad battery drain before, and the system was locking up and freezing and unresponsive as well 2-3 weeks before the BLOD.
I had also previously tried to flash a few other newer 8.1 roms after getting this BLOD, however phone crashed several times during installation and returned to BLOD and was unable to return to TWRP/recovery.
Glad the phone is back to life. Thanks a bunch for the modified rom, TWRP link, and guide!
On a side note, do you feel it is safe to try to flash other vendor images + roms + kernels now... or will the device go back to BLOD. From what I understood this is hardware issue, not software? @Dragon's Fedora
Click to expand...
Click to collapse
Whilst the issue is caused by the hardware; it's actually the software that causes the BLOD. The phone tries to use the 6 cores, but when it detects two of them failing it reboots the device. You can try use other; newer vendor images BUT you must make sure to change the boot.img file within the vendor zip folder.
Whilst the issue is caused by the hardware; it's actually the software that causes the BLOD. The phone tries to use the 6 cores, but when it detects two of them failing it reboots the device. You can try use other; newer vendor images BUT you must make sure to change the boot.img file within the vendor zip folder.
Dragon's Fedora said:
Whilst the issue is caused by the hardware; it's actually the software that causes the BLOD. The phone tries to use the 6 cores, but when it detects two of them failing it reboots the device. You can try use other; newer vendor images BUT you must make sure to change the boot.img file within the vendor zip folder.
Click to expand...
Click to collapse
there is a modified rom that is not stock to boot with the 4 cores, and flashed this boot and the recovery fixed and my nexus is restarted every 5 seconds I would appreciate your help and read many post and I think there is no solution
only4dank said:
Used 2nd method and worked perfectly.
Phone has been on non-the-less for a solid 3 hours and battery is stable (had really bad battery drain before, and the system was locking up and freezing and unresponsive as well 2-3 weeks before the BLOD.
I had also previously tried to flash a few other newer 8.1 roms after getting this BLOD, however phone crashed several times during installation and returned to BLOD and was unable to return to TWRP/recovery.
Glad the phone is back to life. Thanks a bunch for the modified rom, TWRP link, and guide!
On a side note, do you feel it is safe to try to flash other vendor images + roms + kernels now... or will the device go back to BLOD. From what I understood this is hardware issue, not software? @Dragon's Fedora
Click to expand...
Click to collapse
Which version of gapps did you use?
I was messing around and deleted google play store, now none of the google apps works. I went a head to download gapps and tried sideloading it. It showed me the error, then i downloaded the pico version and also fix my system partition. It says i have 140mb of free space in that partition. I tried sideloading pico again and still the same error.
Yurodd said:
I was messing around and deleted google play store, now none of the google apps works. I went a head to download gapps and tried sideloading it. It showed me the error, then i downloaded the pico version and also fix my system partition. It says i have 140mb of free space in that partition. I tried sideloading pico again and still the same error.
Click to expand...
Click to collapse
You're probably going to have to flash your phone back to stock to re-gain all of your apps.
Zachisimo said:
You're probably going to have to flash your phone back to stock to re-gain all of your apps.
Click to expand...
Click to collapse
So flash the rom again? is that going to wipe my phone?
Dark Nightmare said:
This is a basic write up to convert your bootloader unlocked T-Moilbe OnePlus 6T to the International Version firmware via fastboot flashable firmware files.
Contents:
-Disclaimer
- Full Device Backup - Precautionary - Optional, but Recommended.
-Firmware Versions and Flashing Instructions
-Rom Sources
-MSMDownloadTool
-FAQ's
-Additional/Optional Tools
-Credits
Disclaimer:
Like any other form of modding, there are risk involved, we have a near flawless option to recovery by use of the MSMDownload linked at the end of this post, but like with any form of modification, you are solely responsible for what is done to your device and you accept all risk involved, should something go wrong, for the most part, recovery is fairly simply, no matter how bad we screw up, thanks to OP.
Instructions to a full device backup:
1. Download the zip below and extract it to it's own folder
2. run cmd.exe while in fastboot mode and run the following commands:
3. Once twrp boots, run the backup.bat script included, it will backup all partitions on your device, including your efs.
4. zip all of the image files and store it somewhere safe.
Backup: https://androidfilehost.com/?fid=11410963190603855581
For Users Looking to Flash to Firmware versions 9.0.4-9.0.5
FLASHING STEPS
Requirements:
1. Bootloader Unlocked T-Mobile OP 6T
Unlock Processs Can Be Found Here: https://support.oneplus.com/app/ans...-bootloader-for-oneplus-6t-(t-mobile-version)
2. OOS Stock ROM of your choice: all necessary zip files are included in the rom file.
3. PC/MAC/LINUX
Flashing Process
1.. Whichever full rom zip you choose, extract its contents. (In my case I used the 9.0.5 full zip)
2. In each zip file you'll find images.zip as well as others_flashall.zip, extract both of them into the same folder/directory as the rest of the original zip file.
(Optional, download the modded flash-all-partitions-fastboot.bat file at the end of the thread, it includes the reboot command to auto reboot when done flashing)
Attached Below is also a flash-all-partitions-fastboot.sh script for Mac OS users (Note this script will not wipe your device, so if you need to wipe, run the ./fastboot -w command in fastboot manually)
All bat files, images and adb files should all be in the exact same folder, no subfolder(s)
3. Now boot into fastboot using either the vol+/vol- and power key combo or via adb using the following adb command .
4. Once in fastboot run the bat file called flash-all-partitions-fastboot.bat
9
5. When asked, I would advise typing 'Y' for yes to format the device. (wipe only if you're converting for the first time)
The sparse header error is completely normal.
6. Upon completion, the script should pause and say press enter to continue, it will not reboot your device...
WAIT UNTIL NOTHING ELSE IS HAPPENING AND ITS NO LONGER FLASHING ANY FILES
At this point, hit power and reboot.
All done!
Firmware Version 9.0.6
Requirements
1. Bootloader Unlocked T-Mobile OP 6T
Unlock Processs Can Be Found Here: https://support.oneplus.com/app/ans...-bootloader-for-oneplus-6t-(t-mobile-version)
2. OOS Stock ROM of your choice: all necessary zip files are included in the rom file.
3. PC/MAC/LINUX
Steps to Flash
Note: Modded fastboot flashing script attached at the end with the reboot command included, also attached is a script for MAC users, mac script will not wipe your device, wipe manually if you need to using
ROM Sources
Mauronofrio's Thread
T-Mobile 9.0 FULL Fastboot ROM
Saythis' International Firmware 9.0.6
Recovery - MSMDownloadTool
If for some WEIRD reason you brick, have a HW mismatch, etc, or you just can't boot go to this thread -> MSMDownloadTool - T-Mobile 9.0
OPTIONAL Steps
Root is available via two Options below:
- OnePlus Rooter
- Manual Root Using a Patched Boot Image
Automated Process
Luckily There are devs looking to make things simpler:
More an automated tool to carry out this process, go to the thread below:
https://forum.xda-developers.com/oneplus-6t/how-to/rom-oxygen-os-9-0-6-fastboot-windows-t3870170
WARNINGS!
-Advisable you disable automatic updates in developer options upon boot if it is enabled.
-Do not attempt to update using the OTA files, so far we've had one softbrick due to it and said user was unable to boot into fastboot to attempt any kind of recovery.
-ALSO DO NOT FLASH WITHOUT THE FILES IN THE FOLDER, IF YOU DO YOU WILL END UP WITH A SOFTBRICK
-If you get either dump mode or fastboot bootloop check your downloaded rom file to make sure its complete, unzip again and flash again
FAQ
Q. Will this enable dual sim functionality?
A. Dual sim functionality works, volte, Wifi calling and vvm.
Q. Can I take OTA's like a regular device?
A. No, sadly.
Q. What about when a new update comes out?
A. Once a fastboot flashable ROM is made, you can update using the steps above, using the new ROM files.
Q. What if I brick or have a HW/SW mismatch?
A. Use the MSMDownloadTool to recover.
Q. Do all the features work?
A. For the most part, there are minor bugs, but they aren't consistent, so can't really say.
Q. Is this a full conversion?
A. Somewhat.
Q. Do I have to wipe everytime I update?
A. No, wiping may only be necessary for conversions, no wipe needed to update.
Q. Do I have to root everytime I update?
A. Yup, sadly.
Q. Do I have to convert to a specific version?
A. Nope, you can convert to any version.
if any edits are suggested, I'll include them.
Credits:
@mackentosh for testing and unfortunately bricking using the OTA File
@Velrix for being the second successful tester, among others.
All the other users who've been testing/contributing to testing
I'll add names when I get to comb through the threads.
@Dameon87 for the correct ROM source link of the unpacked ROM with batch files.
@Krunk_Kracker for the disable auto updates image
Thanks to @Addiso for the Stock T-Mobile Backup images
@mauronofrio for the scripts and for hosting the Rom zip @hartleyshc for testing and confirming full dual sim functionality.
@Saythis - for the 9.0.6 FULL ROM Zip
Click to expand...
Click to collapse
I would follow this guide. Than choose Y when asked to wipe data. If you want to choose N let me know how it goes. But the easiest way is going to be to start from fresh using this guide by @Darknightmare.