Related
If you flash any gapps in Stock odex rom, then it will give disconnect error after reboot/auto sync error etc. So I am giving you two packages. Flash with custom recovery like cwm/twrp
1. First flash the deodexed_zipaligned_sysApps_framework_NokiaX2ds2.1.0.13flashable.zip
https://yadi.sk/d/nSBRjt5qiQQ7c
2. Then flash the gapps-custom-pico-4.3_signed.zip
https://yadi.sk/d/9NlC8ANFiQQCm
*** deodexed package is for stock version 2.1.0.13. Dont flash it in Custom roms like nokdroid(already deodexed and different system apk folder). Don't flash gapps package in a rom that already includes gapps.
Features:
1. Deodexed
2. Zipaligned
3. Minimal gapps with libs
4. Playstore 4.6.17, location manager(you don't need here maps location manager for network location)
5. No problem for auto sync.
6. No disconnect issue after reboot.
7. No self update of playstore.
**If you want to install the aosp browser with chrome sync you can follow this thread
http://forum.xda-developers.com/nokia-x2/general/aosp-browser-chrome-sync-stock-rom-t3153738
Plz hit thanks if it works and let me know if there is any problem.
Plz someone response if this works in your phone or not. I have only tested it in my ROM.
shafiaszad said:
Plz someone response if this works in your phone or not. I have only tested it in my ROM.
Click to expand...
Click to collapse
this works nicely. i tested it in my phone. still no errors and images load nicely :angel:
I'm use advanced Nokia x2 tools for deodex my Nokia stock rom 2.1.0.12 and flash your gapps but when I reboot my device, disconnect reboot still persist. Sorry my bad English
@jmmigo you have to use stock rom 2.1.0.13, and use my deodex package. That'show its working. I haven't tested with stock rom 2.1.0.12.
Thanks for the explanation
sorry but this is the most idiot package at all...why did u make it delet the whole system app file ? u could just replace everything there only....and play store have the same problem ..disconnect after reboot....and yes it s 2.1.0.13
@thebiggboss180, No u cant just replace. The Odex files must be removed, deleting system app folder simplifies the process. Dont know why its not working for you. For me, for the first commenter its working. But, I am waiting for more reviews. Anyway, saying something is idiot doesnt make you smart.
Does the deodex zip file work for 2.1.0.11 or not because I really hate the disconnect issue after reboot
Don't know, just try after taking a backup.
I flashed the deodex file and it work but when I rebooted my phone the play store app disappear
Worked
i dont know what others say.. but it worked for me.. yeh :laugh: :cyclops:
Help I flash this two using cwm, but when I reboot my phone it stuck on updating application. Good thing I have cwm backup
shafiaszad said:
If you flash any gapps in Stock odex rom, then it will give disconnect error after reboot/auto sync error etc. So I am giving you two packages. Flash with custom recovery like cwm/twrp
1. First flash the deodexed_zipaligned_sysApps_framework_NokiaX2ds2.1.0.13flashable.zip
https://yadi.sk/d/nSBRjt5qiQQ7c
2. Then flash the gapps-custom-pico-4.3_signed.zip
https://yadi.sk/d/9NlC8ANFiQQCm
*** deodexed package is for stock version 2.1.0.13. Dont flash it in Custom roms like nokdroid(already deodexed and different system apk folder). Don't flash gapps package in a rom that already includes gapps.
Features:
1. Deodexed
2. Zipaligned
3. Minimal gapps with libs
4. Playstore 4.6.17, location manager(you don't need here maps location manager for network location)
5. No problem for auto sync.
6. No disconnect issue after reboot.
7. No self update of playstore.
**If you want to install the aosp browser with chrome sync you can follow this thread
http://forum.xda-developers.com/nokia-x2/general/aosp-browser-chrome-sync-stock-rom-t3153738
Plz hit thanks if it works and let me know if there is any problem.
Click to expand...
Click to collapse
Its working on 2.0.1.3 or not?
papu-lashari said:
Its working on 2.0.1.3 or not?
Click to expand...
Click to collapse
Its working on 2.0.1.3
which recovery should i use ?
I created this thread in order to get some discussion going with the possibility to use DualBootPatcher for our Device. The device is supported and so far i got roms to patch but no luck to get it booting.
I hope we can share some information here to get us some dual booting.
Device must be rooted and decrypted for starters.
Got now rr as primary rom and will try later on to flash some roms on the second space... Let you know if that works out.
Tried to dual RR and liquid rom ..No luck. Just reboots to twrp..
Skickat från min ONEPLUS A5010 via Tapatalk
superior8888 said:
Tried to dual RR and liquid rom ..No luck. Just reboots to twrp..
Skickat från min ONEPLUS A5010 via Tapatalk
Click to expand...
Click to collapse
I have also rr as primary but second rom install ended in error 1 in twrp. Maybe you can try to reset data of second rom with the dualboot patcher zip.
It might be helpful to read the Dual Boot Patcher thread for the OP5, as there may be some important info there that is relevant for getting it to work on the 5T.
I tried rr as primary, no problem. Tried adding 2nd rom as secondary, as data slot 1, and no dice. Even tried removing assert lines in the updater script as suggested in op5 with rr as 2nd rom but that didn't work either; either booted back to twrp or booted to a black screen. If anyone makes it work please document and share your work. I'm encrypted by the way, even though you're "supposed" to be decrypted I was able to switch between primary and the non-booting rom just fine.
Anyone having any luck with this?
matteosaeed said:
Anyone having any luck with this?
Click to expand...
Click to collapse
Nope primary install goes good with a oos rom not stock. But when you try to install a second rom it gives error 1 in twrp and rom don't boot up.
That's great! Old MultiROM user here!
Ok, so I was able to successfully patch and boot into LOS and RR. LOS as primary and as slot 1 ROM, and RR as slot 2 ROM while encrypted. This wouldn't allow me to access any files in the phone via file managers for either slot ROMs, only in primary, so you must be decrypted if you're wanting to use/see the data in your internal memory on secondary ROMs. By the way I was only able to boot Nougat ROMs, dualpatcher doesn't work for Oreo ROMs yet. I'll do a small write up tomorrow, it's 1 am here ?
superior888 said:
I created this thread in order to get some discussion going with the possibility to use DualBootPatcher for our Device. The device is supported and so far i got roms to patch but no luck to get it booting.
I hope we can share some information here to get us some dual booting.
Device must be rooted and decrypted for starters.
Click to expand...
Click to collapse
Here is what I did:
IF YOU DON'T KNOW HOW TO DECRYPT, BACK UP YOUR STUFF, FLASH, ROOT, ETC, STOP READING NOW, THIS IS SOME HEAVY STUFF GETTING READY TO HAPPEN ?
If you want functional internal storage and have access to it on all secondary ROMs you must be decrypted. This guide assumes you have all required files on phone and/or computer
1. Flash bluspark recovery (wouldn't work on codeworkx for me)
2. Back up all your data, including internal storage somewhere safe
3. Wipe system, cache, and data (not internal)
4. Coming from Phoenix, so I flashed the Nougat firmware and then LOS 14.1 and booted it
5. Flash magisk 14.0, then install dualbootpatcher app
6. After granting root permission to dualbootpatcher go ahead and go to ROMs and set kernel now
7. Now you must patch another Nougat ROM as data-slot, ID 1 or 2 or 3, whatever you want. You can use the same LOS 14.1 as a test, or the RR Nougat version
8. Transfer the patched ROM to your PC or laptop and without unzipping/extracting the zip go to META-INF/com/google/android and open updater-script with notepad++. Delete the first two lines that's start with the word "assert" and save
9. It should now ask you if you want to update the zip, hit yes. Then transfer the updated patched ROM back to your phone
(you can do this from your phone too using winrar and your favorite file manager; it s a tad easier on your computer as you don't have to extract anything)
10. Now reboot into recovery and flash the patched ROM (do not flash from within the app)
11. Now flash the dualboot utilities in recovery and it should take you to an Aroma menu where you can see both primary and and data slot ROM. Tap the data slot ROM and choose "switch to". If you did everything right it should say "succeeded" and now you can reboot your phone and should boot into the secondary ROM.
12. To root data slot ROMs you must patch the magisk zip for that data slot ROM and then flash it in recovery, the same goes for gapps. Make sure whatever you patch does not have the "assert" lines in the updater script after patching it, else you must delete these lines.
Try it and report back. I can hardly debug my own device so I can't provide much support for you. The above is what I did while encrypted, so again, if you want functional internal storage for the additional ROMs must be decrypted before you try this.
cubandanger05 said:
Ok, so I was able to successfully patch and boot into LOS and RR. LOS as primary and as slot 1 ROM, and RR as slot 2 ROM while encrypted. This wouldn't allow me to access any files in the phone via file managers for either slot ROMs, only in primary, so you must be decrypted if you're wanting to use/see the data in your internal memory on secondary ROMs. By the way I was only able to boot Nougat ROMs, dualpatcher doesn't work for Oreo ROMs yet. I'll do a small write up tomorrow, it's 1 am here ?
Click to expand...
Click to collapse
Thanks for updating us, I'm an old multirom user as well and I'm going to keep my eye on this.
cubandanger05 said:
Here is what I did:
IF YOU DON'T KNOW HOW TO DECRYPT, BACK UP YOUR STUFF, FLASH, ROOT, ETC, STOP READING NOW, THIS IS SOME HEAVY STUFF GETTING READY TO HAPPEN
If you want functional internal storage and have access to it on all secondary ROMs you must be decrypted. This guide assumes you have all required files on phone and/or computer
1. Flash bluspark recovery (wouldn't work on codeworkx for me)
2. Back up all your data, including internal storage somewhere safe
3. Wipe system, cache, and data (not internal)
4. Coming from Phoenix, so I flashed the Nougat firmware and then LOS 14.1 and booted it
5. Flash magisk 14.0, then install dualbootpatcher app
6. After granting root permission to dualbootpatcher go ahead and go to ROMs and set kernel now
7. Now you must patch another Nougat ROM as data-slot, ID 1 or 2 or 3, whatever you want. You can use the same LOS 14.1 as a test, or the RR Nougat version
8. Transfer the patched ROM to your PC or laptop and without unzipping/extracting the zip go to META-INF/com/google/android and open updater-script with notepad++. Delete the first two lines that's start with the word "assert" and save
9. It should now ask you if you want to update the zip, hit yes. Then transfer the updated patched ROM back to your phone
(you can do this from your phone too using winrar and your favorite file manager; it s a tad easier on your computer as you don't have to extract anything)
10. Now reboot into recovery and flash the patched ROM (do not flash from within the app)
11. Now flash the dualboot utilities in recovery and it should take you to an Aroma menu where you can see both primary and and data slot ROM. Tap the data slot ROM and choose "switch to". If you did everything right it should say "succeeded" and now you can reboot your phone and should boot into the secondary ROM.
12. To root data slot ROMs you must patch the magisk zip for that data slot ROM and then flash it in recovery, the same goes for gapps. Make sure whatever you patch does not have the "assert" lines in the updater script after patching it, else you must delete these lines.
Try it and report back. I can hardly debug my own device so I can't provide much support for you. The above is what I did while encrypted, so again, if you want functional internal storage for the additional ROMs must be decrypted before you try this.
Click to expand...
Click to collapse
Thanks! I'll try this next days.
Thanks. Nothing works with Oreo as of yet i suppose :/
superior888 said:
Thanks. Nothing works with Oreo as of yet i suppose :/
Click to expand...
Click to collapse
It may be possible to have oreo as primary and flash Nougat as data slot roms. I tried with Phoenix as primary and I could boot into rr Nougat in data slot but Phoenix wouldnt boot. If someone can try rr oreo as primary and report back. I'm tempted to try with otg and see if I can install secondary roms using extsd option
*Quick update*
I was able to keep latest Phoenix oreo ROM as primary and install and boot Nougat RR as data-slot and as secondary using the latest dualbootpatcher app which may have fixed the "failed to update mbtool" error I was getting on Phoenix ROM. Also I used Magisk 14.0 for root as the latest version 16.0 kept booting back to recovery on non primary ROMs.
I'm still unable to flash Oreo ROMs as data-slot or secondary. At least we're able to keep Oreo as primary and test Nougat ROMs until dualbootpatcher app is compatible with Oreo or until some other fix is released.
Internal storage/data is still encrypted and unreadable on all non-primary ROMs; you must be decrypted prior to installing additional ROMs to have access to it, which I haven't tested yet.
See screenshots
Thanks for keeping up with this. I'm really interested but traveling without my PC so don't want to get stuck without a backup plan. Hopefully it's sorted by the time I get back home or I'll help test some more too.
es0tericcha0s said:
Thanks for keeping up with this. I'm really interested but traveling without my PC so don't want to get stuck without a backup plan. Hopefully it's sorted by the time I get back home or I'll help test some more too.
Click to expand...
Click to collapse
It's been relatively "safe" all the testing that I've done, not many scares, but you can never be too careful.
Edit: Now that it's working almost as intended we should make an official "how to" thread
cubandanger05 said:
It's been relatively "safe" all the testing that I've done, not many scares, but you can never be too careful.
Click to expand...
Click to collapse
If I wasn't out of the country, it'd probably be different. I've customized 100s of phones, 1000s of times but sometimes it's better safe than sorry. I'm great at fixing stuff because I've broken about everything I can (sometimes on purpose, sometimes not lol) but I need navigation and translation more than another custom rom I suppose.
es0tericcha0s said:
If I wasn't out of the country, it'd probably be different. I've customized 100s of phones, 1000s of times but sometimes it's better safe than sorry. I'm great at fixing stuff because I've broken about everything I can (sometimes on purpose, sometimes not lol) but I need navigation and translation more than another custom rom I suppose.
Click to expand...
Click to collapse
? understandable
[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.
I got a brand new Samsung Tab E 9.6" (SM-T560). Shame on me, I didn't notice before it comes with Android 4.4.4
As many apps require newer OS, I'm wondering if I can upgrade it to Android 6.0.
Plase note:
1. I'm not an expert, so please explain me as easy as possible how to do it, if it can be done;
2. please tell me, in case,if it's 100% legal and/or if it can void warrant.
Thank you.
Samsung Tab E
Check again --- Just picked up the same thing this week at Walmart for $129.00 + $25 Google Play credits - it came with 7.1.1. - Take it back sounds like you got some real old stock..
They do come with Android 4.4, however if you go to Samsungs web page you can find a crispy 7.1.1 image you can flash with Odin. Then if you wish you can unlock bootloader and flash a custom recovery like CWM or TWRP and then chainfires systemless root. Cheers! Upgrading to just 7.1.1 with Odin will not void your warranty, anything else that involves unlocking the bootloader will and is will trip samsungs knox security feature. If warranty is important only flash the 7.1.1 image using Odin.
Hello,
I'm searching forsuch an update, too. But It seems, that it was only released for USA and CA. But I'm from Germany. @xSLAYERx do you have a link to the ROM?
xSLAYERx said:
They do come with Android 4.4, however if you go to Samsungs web page you can find a crispy 7.1.1 image you can flash with Odin. Then if you wish you can unlock bootloader and flash a custom recovery like CWM or TWRP and then chainfires systemless root. Cheers! Upgrading to just 7.1.1 with Odin will not void your warranty, anything else that involves unlocking the bootloader will and is will trip samsungs knox security feature. If warranty is important only flash the 7.1.1 image using Odin.
Click to expand...
Click to collapse
heya, could you please share a link of this 7.1.1 with me? or the image itself, I can't find it anywhere and I'm stuck with 4.4.4
thank you!
hurkagyurka123 said:
heya, could you please share a link of this 7.1.1 with me? or the image itself, I can't find it anywhere and I'm stuck with 4.4.4
thank you!
Click to expand...
Click to collapse
Hi, I was with the same problem, and I posted here in XDA, I'm from Brazil, i have the model SM-T560, and now i'm using nougt, from Lineageos 14.1, and this was only possible, because someone from Xda, gave me the following link:
http://www.gearappsnap.com/2018/03/14/how-to-install-android-nougat-on-the-galaxy-tab-e-sm-t561/
The rom is of the SM-T561 model, but also works on the SM-T560, read everything before doing anything. When installing TWRP, you can install the version of the SM-t560, which will not make any difference.
One more thing, I advise you to see some YouTube tutorials how to install TWRP. Just in case.
Thank You for your help!
hurkagyurka123 said:
Thank You for your help!
Click to expand...
Click to collapse
For nothing, follow step by step that will work perfectly. Except this will end your warranty, but it's the only way to install an update. If you need any help, just talk.
gearappsnap site is not really good made.. The download links behind text which look like a normal one and also that it says, flash boot.img only when the memory is wrong..
Well, CM14.1 did not work for me.. I had to flash boot.img before EVERYTHING else, then rebooted again to TWRP and THEN install cm14.1.
Um, did you follow step by step?
I followed what was written, and for me it worked normal, The boot.img file is to fit just the memory of the table because it had some problem with the rom, without installing it, has tablet that got locked in infinite loop. And the links were working normal for me.
Links that i download:
ROM: https://drive.google.com/file/d/1D0wrGM4XyZMo-t3ll4trvJ93Pl1KEZ1V/view
Boot.img: https://drive.google.com/file/d/1bqGmu4NTlEeKdsFPGjIY9lnPqujjazr4/view
softkeys: https://drive.google.com/file/d/1ddSB28g1xTd0J7sl8V6QmlPZA1aX77ot/view
Gaps: https://opengapps.org/
First the TWRP is installed, with the battery above 70%, then restarts the tablet.
Within the TWRP:
1) Wibe-> advanced wibe-> selects almost anything but not microSD and OTC. and Wibe.
2) Back to the home page-> Install-> select the external storage (the files must be saved on the SD card).
3) The first file to be installed is the rom.
4) Once installed, go back to the files and at the bottom of the page you will click install image and install boot.img.
5) After Boot.img is installed, switch back to Install Zip, and Install the Softkeys.
6) After installing the softkeys go back and install the Gaps. (I used the ARM-7.1-Pico) and restart the tablet.
In my case I did not install superSU. That's what I did. This rom has some flaws but better than Kitkat, that's what I think.
thE_29 said:
gearappsnap site is not really good made.. The download links behind text which look like a normal one and also that it says, flash boot.img only when the memory is wrong..
Well, CM14.1 did not work for me.. I had to flash boot.img before EVERYTHING else, then rebooted again to TWRP and THEN install cm14.1.
Click to expand...
Click to collapse
HEY!
download this: https://mega.nz/#!yEpjCITA!9EA101hYDOajDwmBHKxSZhv3QkV-RI61MkLn0JYNRZY
unzip and install and follow steps.
1-install TWRP 3.0.2-1 via odin
2- copy ALL files of .zip in one folder in storage (mem stick)
3- power off and then power on IN TWRP (vol + + home + power button)
4- make full wipes except externar storage
5- install zip (first choice lineage -14, then choice open gapps, next choice key.zip)
6- install img (choice boot.img)
7- WIPE (Dalvik, cache)
enjoy android 7.1 in your tab e T560
63or63 said:
HEY!
download this: https://mega.nz/#!yEpjCITA!9EA101hYDOajDwmBHKxSZhv3QkV-RI61MkLn0JYNRZY
unzip and install and follow steps.
1-install TWRP 3.0.2-1 via odin
2- copy ALL files of .zip in one folder in storage (mem stick)
3- power off and then power on IN TWRP (vol + + home + power button)
4- make full wipes except externar storage
5- install zip (first choice lineage -14, then choice open gapps, next choice key.zip)
6- install img (choice boot.img)
7- WIPE (Dalvik, cache)
enjoy android 7.1 in your tab e T560
Click to expand...
Click to collapse
In reality you have to install boot.img and softkeys before, the reason is because they are modified for the T56X, otherwise install themselves after the gaps will give error when to use. At least it is what was written on the site, and so far I have been using no defect at all.
marcelo010 said:
In reality you have to install boot.img and softkeys before, the reason is because they are modified for the T56X, otherwise install themselves after the gaps will give error when to use. At least it is what was written on the site, and so far I have been using no defect at all.
Click to expand...
Click to collapse
I do not think that is effective. if you come from 4.4.4 and install it before the lineage ROM (BASE 7.1 for example) it will be erased again because with the new base everything is overwritten.
63or63 said:
I do not think that is effective. if you come from 4.4.4 and install it before the lineage ROM (BASE 7.1 for example) it will be erased again because with the new base everything is overwritten.
Click to expand...
Click to collapse
Well that didnt work for me.. Was coming from Stock 4.4 ROM. Flashed the CM14.1 AND softkeys, but NOT the boot.img, because you cannot flash zip and img files at the same time. Then I booted it and it crashed 10-60secs after it booted. Sometimes it had a boot loop.
Then I tried CM 13 which worked fine and in a german board, someone wrote (based on the gearappsnap site) that the boot.img has to be the first thing to flash and even reboot into twrp again and then flash CM14.1 + softkeys + gapps.
If you could install it, that's what matters, in my case it worked the way it was on the site, there are some bug's, but it's a lot better than the stock rom, and I was already using a custom rom on the T560 before installing this LineageOS 14.1,and it was this link:
https://forum.xda-developers.com/galaxy-tab-e/development/rom-lightning-t3716039
Szia!
did the upgrade work for You For galaxy tab e?
Done this and it worked but.........
The tablet is really slow, not netflix compatible with this version, and so on....
I think I just might downgrade again
After I have tried step 3, it didnt open in twrp mode. My tab stucks in black screen with "Samsung galaxt tab e " text in background.Please let me know how to proceed.
[QUOTE = "63or63, Post: 78613279, Mitglied: 4438103"]
HI THERE!
Download this: https://mega.nz/#!yEpjCITA!9EA101hYDOajDwmBHKxSZhv3QkV-RI61MkLn0JYNRZY
unzip and install and follow the steps.
1-install TWRP 3.0.2-1 through odin
2- Copy ALL .zip files to a folder in memory (mem stick).
3- turn off and then turn on IN TWRP (vol + + home + power button)
4- Make full towels except for external storage
5- install zip (first choice line -14, then select open gaps, next choice key.zip)
6- install img (choose boot.img)
7- WIPE (Dalvik, Cache)
enjoy Android 7.1 in your Tab e T560
[/ZITAT]
1000 tanks BR
.
1000 x danke es hat funktioniert
Translation: 1000 x thank you it worked