I am not responsible for your bricked phone or pigeon poo on your toupe. Do at your own risk.
Many thanks to @SupahCookie for idea and motivation!
INTENTIONALLY DOES --NOT-- LOCK BOOTLOADER!!!
Get factory images here:
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
THIS GUIDE IS FOR FACTORY/STOCK ROMs - NOT YOUR AVERAGE CUSTOM ROM which may not have bootloaders!!! (thanks!!!!! @echo92 )
FIX:
IF YOU ARE ABLE TO GET TO FASTBOOT THIS SHOULD WORK.
IF YOU HAVE 8.x bootloaders AND ARE DOWNGRADING TO 7, use "Alternative to RSDlite" below.
1 boot to win - 7 or 10 works fine.
2 boot phone to fastboot, and connect phone to computer.
3 start RSDlite
pick a ROM. I believe I used a 7.1.1 rom
3Nov9-ADDISON_NPNS26.118-22-2-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
RSDlite installed it and fixed the problem.
- -
I was then able to use RSDlite to install @rafikowy 's signed 8.0 . - going up from 7 to 8.
- -
- -
If you are on 8.x bootloaders and want to go to 7.x bootloaders, use this (RSDlite throws an error and stops):
ALTERNATIVE TO RSDlite:
1 I used 7zip to extract that 7.1.1 zip (or any ROM zip) into a folder x,
2 add all the adb and fastboot junk to folder x,
3 add the attached file (rename it to flash.bat) to folder x.
4 boot phone to fastboot and connect to computer.
5 click on flash.bat - it throws a lot of "slot" errors but works just fine.
6 reboot your phone if it hasn't already and go through the 7.x install stuffs.
7 you will not show an IMEI if you are coming from an 8.x bootloader. However, it IS there.
NOTE: you may need to add a line to the flash.bat if there are more/less sparsechunk's in your FACTORY/STOCK ROM...
THIS IS NOT FOR CUSTOM ROMs!!!!!!!
EDIT: 3-8-19: I just did this myself to go back very briefly to 7.1 - be sure you don't flash TWRP to it if your going to take OTAs - it will brick it. boot to TWRP if you need TWRP briefly: fastboot boot twrpimg.img
----------
If you can boot to fastboot screen, you can do anything.
Never OTA a ROM if you have modified recovery (TWRP, etc) or if magisk is present.
https://forum.xda-developers.com/mo...p-flashing-t3813498/post77011495#post77011495
I changed the attached file to add pause and reboot and exit to make it slightly more automated.
I have successfully used this many times going back and forth. If you can boot to fastboot screen, you can save your phone and flash anything you want.
You may wish to advise users that if they downgrade to Nougat not to use Nougat OTA updates. The reason being that a downgraded stock Oreo device may still have the Oreo bootloader on it. Thus, attempting to use Nougat OTA updates may hard brick their device (as the bootloader is likely corrupted, meaning no fastboot).
Users could either use the Feb 2018 NPN26.118-22-2-17 firmware from your link https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/ as that was the last Nougat firmware (and thus no Nougat OTA updates) or avoid using OTA updates whilst downgraded.
echo92 said:
You may wish to advise users that if they downgrade to Nougat not to use Nougat OTA updates. The reason being that a downgraded stock Oreo device may still have the Oreo bootloader on it. Thus, attempting to use Nougat OTA updates may hard brick their device (as the bootloader is likely corrupted, meaning no fastboot).
Users could either use the Feb 2018 NPN26.118-22-2-17 firmware from your link https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/ as that was the last Nougat firmware (and thus no Nougat OTA updates) or avoid using OTA updates whilst downgraded.
Click to expand...
Click to collapse
Interesting. I used the above GUIDE to go up and down a number of times on my phone (about 20 total) , installing and running on both 7 and 8, and then went down to a Nov 7.1.1 and let it ota all the way up to 8.0 and that is what I am using now. I found that when i used a factory zip, and the above procedure, it corrected the bootloaders to the appropriate version that i was flashing - either RSDlite or the more manual path which ignores the errors worked for me.
Using the above procedure , you get the correct bootloaders, which are in the zip.
Please correct me if i am wrong!
KrisM22 said:
Interesting. I used the above GUIDE to go up and down a number of times on my phone (about 20 total) , installing and running on both 7 and 8, and then went down to a Nov 7.1.1 and let it ota all the way up to 8.0 and that is what I am using now. I found that when i used a factory zip, and the above procedure, it corrected the bootloaders to the appropriate version that i was flashing - either RSDlite or the more manual path which ignores the errors worked for me.
Using the above procedure , you get the correct bootloaders, which are in the zip.
Please correct me if i am wrong!
Click to expand...
Click to collapse
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device (hence the number of users asking for a blankflash, as fastboot no longer works). I don't know if these users hard bricked by downgrading their firmware too far and then flashed an OTA radically different to their previous firmware, or whether it's a risk that's taken by any downgrading of firmware.
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
echo92 said:
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device (hence the number of users asking for a blankflash, as fastboot no longer works). I don't know if these users hard bricked by downgrading their firmware too far and then flashed an OTA radically different to their previous firmware, or whether it's a risk that's taken by any downgrading of firmware.
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
Click to expand...
Click to collapse
YES - that's why I wrote these 3 guides - before, it was quite possible to wind up with a bootloader mix - esp depending on the zip you use! - factory/stock only!!!
I added a line to the guide saying that it is only intended to be used for the factory/stock zips as these have (I believe) the bootloaders appropriate to the ROM.
Many thanks for pursuing this! - I wonder if we'll have to exclude certain ROMs that are in the factory lists?????
echo92 said:
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device
Click to expand...
Click to collapse
If you have TWRP (or I assume any custom recovery) present when you try to ota, it can download just fine and then reboot to the update. I had TWRP and wound up in a situation where my phone would only boot to twrp no matter what I flashed or restored. I booted phone to fastboot, RSDlite'ed that 11-09-17 factory zip and all was well. In that particular case I did not fully install 7.x but immediately RSDlite'ed rafikowy's 8.0 signed stock and went on with my testing. Since then I always boot to TWRP rather than intalling it and do my thing. (thanks @jceballos )
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
Click to expand...
Click to collapse
Sorry - since it throws a million errors I never look at it if it works.
The particular build I am on at the moment - is BL: C1.82
This one started from that Nov '17 build and ota'ed all the way to 8.0 Apr.
I root and unroot as needed per rafikowy's method but using a boot to TWRP - never an install TWRP.
I'll put up a new guide ref ota and recovery and brick.
KrisM22 said:
If you have TWRP (or I assume any custom recovery) present when you try to ota, it can download just fine and then reboot to the update. I had TWRP and wound up in a situation where my phone would only boot to twrp no matter what I flashed or restored. I booted phone to fastboot, RSDlite'ed that 11-09-17 factory zip and all was well. In that particular case I did not fully install 7.x but immediately RSDlite'ed rafikowy's 8.0 signed stock and went on with my testing. Since then I always boot to TWRP rather than intalling it and do my thing. (thanks @jceballos )
Sorry - since it throws a million errors I never look at it if it works.
The particular build I am on at the moment - is BL: C1.82
This one started from that Nov '17 build and ota'ed all the way to 8.0 Apr.
I root and unroot as needed per rafikowy's method but using a boot to TWRP - never an install TWRP.
I'll put up a new guide ref ota and recovery and brick.
Click to expand...
Click to collapse
1) If you have TWRP, then using an OTA will fail - as you've not got stock recovery (and likely other modifications, including possibly a system partition set to read-write status). As you noted, having TWRP seems to cause a bootloop when rebooting - I'm not sure if the OTA sets a boot flag to stay in recovery until the update is completed. For the G4/Plus, there's a possible solution by wiping the misc partition but I don't know if there's a similar partition for Z Play devices: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
The only other solution I've seen is a clean flash of the stock ROM to get your device booting properly.
Booting to TWRP rather than flashing would mean your stock recovery is still present on your device. The only downside is if you need to make modifications, you'd need your computer to boot to TWRP.
2)BL C1.82 seems to be the bootloader provided by the Oreo April 2018 security patch update, so your device looks to be on the right bootloader. It's still curious that the Nov 2017 firmware worked whereas countless other 'factory' stock ROMs caused hard bricks when downgraded to and then OTA updates were installed.
As you mentioned, custom ROMs don't have bootloaders and thus don't care about your bootloader version usually (though I've seen some ROMs require a certain bootloader). However, stock ROMs and stock OTA updates do have bootloaders, which is why downgrading can be risky.
echo92 said:
1) If you have TWRP, then using an OTA will fail - as you've not got stock recovery (and likely other modifications, including possibly a system partition set to read-write status). As you noted, having TWRP seems to cause a bootloop when rebooting - I'm not sure if the OTA sets a boot flag to stay in recovery until the update is completed. For the G4/Plus, there's a possible solution by wiping the misc partition but I don't know if there's a similar partition for Z Play devices: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
The only other solution I've seen is a clean flash of the stock ROM to get your device booting properly.
Booting to TWRP rather than flashing would mean your stock recovery is still present on your device. The only downside is if you need to make modifications, you'd need your computer to boot to TWRP.
2)BL C1.82 seems to be the bootloader provided by the Oreo April 2018 security patch update, so your device looks to be on the right bootloader. It's still curious that the Nov 2017 firmware worked whereas countless other 'factory' stock ROMs caused hard bricks when downgraded to and then OTA updates were installed.
As you mentioned, custom ROMs don't have bootloaders and thus don't care about your bootloader version usually (though I've seen some ROMs require a certain bootloader). However, stock ROMs and stock OTA updates do have bootloaders, which is why downgrading can be risky.
Click to expand...
Click to collapse
Downgrading is a piece of cake if you don't use RSDlite - it throws an error and stops. Using the bat file it can happily throw all the errors it wants and all I care is at the end I have what I want.
It does indeed change the entire environment when you bat file the zip contents. You can bat file to get from 8 to 7 and then use RSDlite to flash a different 7 OR 8 zip file. There is no resulting difference in whether you RSDlite it or bat file it - the bat file simply comes from the .xml file that is within the zip. There is very little or no difference between that among addison factory/stock zips. Other zips are different (custom ROMs.)
Grab any factory/stock zip for addison and expand it and you will see modems, bootloaders, indeed absolutely everything you would find on that phone if you went to a store and bought it. SupahCookie simply added a couple lock command lines because it was intended for folks who somehow thought that if phone was locked they could take it back to the store and get their money back. Or some such. I found that ATT folk didn't care if you were on CM or whatever if you just needed to swap SIMs or whatever.
I DON'T want to lock the phone as it prevents me from modifying forever. Oh yeah that reminds me I was going to post the obligatory guide (again) about how to flash a white boot logo so you don't get that message - it's still there LOL but since the font is in white, you can't see it.
I have a Moto Z2 Play and used this to get out of a rather sticky situation.. My IEMI shows 0 now and I'm curious if there's a way to fix this? Also, You say you've done OTA updates? My phone is telling my I have some, is it safe to try?
Necrowr said:
I have a Moto Z2 Play and used this to get out of a rather sticky situation.. My IEMI shows 0 now and I'm curious if there's a way to fix this? Also, You say you've done OTA updates? My phone is telling my I have some, is it safe to try?
Click to expand...
Click to collapse
Thanks for feedback and great on success.
IMEI will show zero if using oreo, It will show again if using N. Remember that if you go from O to N you need to use the "Alternative to RSD" as RSD will simply throw an error and stop.
If you have TWRP and/or Magisk you must get rid of them before ota - if twrp present you will soft brick and have to do alternative again - flash a stock recovery. Simply uninstalling/flash magisk will probably not be enough - it will likely d/l but error part way through update. If you are sitting on rafikowy's stock oreo, and haven't modified it, you should be fine. I know Apr and June are out there. I flashed his stock 8.0 and took June fine. Z2 should be no different though of course I can't guarantee it
If you have success, let us know what you have done so others looking in will know. Thanks!
KrisM22 said:
Thanks for feedback and great on success.
IMEI will show zero if using oreo, It will show again if using N. Remember that if you go from O to N you need to use the "Alternative to RSD" as RSD will simply throw an error and stop.
If you have TWRP and/or Magisk you must get rid of them before ota - if twrp present you will soft brick and have to do alternative again - flash a stock recovery. Simply uninstalling/flash magisk will probably not be enough - it will likely d/l but error part way through update. If you are sitting on rafikowy's stock oreo, and haven't modified it, you should be fine. I know Apr and June are out there. I flashed his stock 8.0 and took June fine. Z2 should be no different though of course I can't guarantee it
If you have success, let us know what you have done so others looking in will know. Thanks!
Click to expand...
Click to collapse
I actually flashed to this: ALBUS_C_7.1.1_NPS26.118-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which is a 7.1.1 variant and it is showing 0 when I check settings and when I dial *#06#. However upon connecting to the computer and running mfastboot getvar imei it returned a value. I only did the steps above which would mean I don't have TWRP or Magisk (when I fastboot and click recovery I get "no command")
****** Additional information *********
XT1710-01 Duel Sim Variant
I started your steps, only being able to access fastboot. The device would throw an error (I don't recall exactly but it ended up showing me them in the bootloader logs) whenever I tried to start it, or go to recovery. #DefinitelyThoughtItWasDead
Necrowr said:
I actually flashed to this: ALBUS_C_7.1.1_NPS26.118-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which is a 7.1.1 variant and it is showing 0 when I check settings and when I dial *#06#. However upon connecting to the computer and running mfastboot getvar imei it returned a value. I only did the steps above which would mean I don't have TWRP or Magisk (when I fastboot and click recovery I get "no command")
****** Additional information *********
XT1710-01 Duel Sim Variant
I started your steps, only being able to access fastboot. The device would throw an error (I don't recall exactly but it ended up showing me them in the bootloader logs) whenever I tried to start it, or go to recovery. #DefinitelyThoughtItWasDead
Click to expand...
Click to collapse
What rom was on phone when you got it and what have you done to it? Has it ever run 8.x?
original country of phone?
The bat file will always throw a lot of slot errors.
https://mirrors.lolinet.com/firmware/moto/albus/official/RETUS/
or
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
might have some stock ROMs of interest...
KrisM22 said:
What rom was on phone when you got it and what have you done to it? Has it ever run 8.x?
original country of phone?
The bat file will always throw a lot of slot errors.
might have some stock ROMs of interest...
Click to expand...
Click to collapse
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Necrowr said:
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Click to expand...
Click to collapse
Custom ROMs won't usually update the bootloader (even if they are newer) as stock ROMs typically only have the bootloader firmware.
You could look into flashing the stock Oreo albus 8.0 ROM https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153 or the 8.0 June 2018 firmware https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-albusretail8-0-0opss27-76-t3822195 but please check that firmware has been released for your device variant.
I don't know if updating your baseband to stock Oreo formally may fix your IMEI issue.
Necrowr said:
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Click to expand...
Click to collapse
"BL: C0.CD" even right after flashing that albus 7.1.1 using "alternative" above?
What happens if you flash one of the oreo roms from the links I gave you above?
Yeah, RR wouldn't change bootloaders... so you upgraded bootloaders independendently?- that could easily lead to a soft brick... -
I read RR on Z2 and it says nothing about bootloaders even though it says 8.1 based, so i wonder if it needs 7.x bootloaders? I did not read entire thread...
In a reverse, I would wonder if you put an 8 on there if you wouldn't see your IMEI. (On the Z if you flash 8 You won't see the IMEI until you return to 7.)(wondering if z2 is reversed)
KrisM22 said:
"BL: C0.CD" even right after flashing that albus 7.1.1 using "alternative" above?
What happens if you flash one of the oreo roms from the links I gave you above?
Yeah, RR wouldn't change bootloaders... so you upgraded bootloaders independendently?- that could easily lead to a soft brick... -
I read RR on Z2 and it says nothing about bootloaders even though it says 8.1 based, so i wonder if it needs 7.x bootloaders? I did not read entire thread...
In a reverse, I would wonder if you put an 8 on there if you wouldn't see your IMEI. (On the Z if you flash 8 You won't see the IMEI until you return to 7.)(wondering if z2 is reversed)
Click to expand...
Click to collapse
Yes, right after flashing that is the BL that fastboot is showing me. I don't recall updating the bootloader so to speak, however RR did require an updated variant of twrp which I flashed 3.2.2 I believe to get (unsure if that would have changed the bootloader or not). I also tried flashing a stock Oreo (which you've stated stock Roms usually only have the bootloaders so maybe somewhere during this process I updated it?). I wish I had all the notes for what I did to give more precise information, but I'm in a position where I really need my phone so I kinda just panicked and started flashing things when my service wouldn't work.
I'm highly considering trying to run an OTA (though very afraid of bricking). - On a side note though, it wouldn't even tell me I had OTA's until I did the steps in the original post here (doing the different 7.1.1. and 8.0 flashes, it wouldn't ever tell me I had updates, and now it does).
*** Edit ***
Looks like I'm able to enter stock recovery, which makes me believe everything is stock at the moment.
Necrowr said:
Yes, right after flashing that is the BL that fastboot is showing me. I don't recall updating the bootloader so to speak, however RR did require an updated variant of twrp which I flashed 3.2.2 I believe to get (unsure if that would have changed the bootloader or not). I also tried flashing a stock Oreo (which you've stated stock Roms usually only have the bootloaders so maybe somewhere during this process I updated it?). I wish I had all the notes for what I did to give more precise information, but I'm in a position where I really need my phone so I kinda just panicked and started flashing things when my service wouldn't work.
I'm highly considering trying to run an OTA (though very afraid of bricking). - On a side note though, it wouldn't even tell me I had OTA's until I did the steps in the original post here (doing the different 7.1.1. and 8.0 flashes, it wouldn't ever tell me I had updates, and now it does).
*** Edit ***
Looks like I'm able to enter stock recovery, which makes me believe everything is stock at the moment.
Click to expand...
Click to collapse
If you flashed a stock O that would have changed bl to O, but doing the above with the stock 7.1.1 would have changed them back to N. No matter (other than academic) that you don't remember the path - flashing a stock anything reverts it to that point in time. However, IMEI may have been moved - don't know. It will likely show on EITHER 7.x or 8.x stock - just don't know which.
If you flash a stock 8.x from those links I gave you above, it should offer you ota, ASSUMING there are any at this point in time(Z has 2). Adding Magisk at any point seems to hose you for receiving any more ota's - don't understand why, even with magisk uninstall, so that would mean going back to the latest stock and losing what you have (which is why I try to take a TBPro and copy that backup to PC (because re-flashing 8.x stock will likely reset internal storage.).
yes, if you enter stock recovery, you are likely at stock, though you could reflash the latest 7 or 8 stock to be sure, depending on which you want to use as base. Since 8 is having security fixes released, I choose 8 and will likely have no more interest (no time!) in 7.
So, ran the OTA and it was fine running the update and staying on N. I also downloaded the OTA for Oreo, when trying to update the recovery error'd out. It looked like the error said "Error in modem unexpected results" or something similar.
Necrowr said:
So, ran the OTA and it was fine running the update and staying on N. I also downloaded the OTA for Oreo, when trying to update the recovery error'd out. It looked like the error said "Error in modem unexpected results" or something similar.
Click to expand...
Click to collapse
did it offer to let you d/l it again? you could try that.
However, there exist O stock zips in those links I gave you so you could just flash the latest...
Related
My Phone Info:
Single sim 2gb ram + 16gb rom
Hello folks I've been searching for a nougat update for XT-1644, but unable to find over the xda if anyone of you havs upgraded your xt-1644 then kindly tell the procedure here, Thanks.
Here is my About Phone Info.
http://cloud.tapatalk.com/s/589c8f61b2eab/Screenshot_20170209-203359.png
http://cloud.tapatalk.com/s/589c8f48b01b2/Screenshot_20170209-203401.png
You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.
echo92 said:
You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.
Click to expand...
Click to collapse
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?
waseemmayaa said:
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?
Click to expand...
Click to collapse
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
echo92 said:
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Click to expand...
Click to collapse
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.
waseemmayaa said:
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.
Click to expand...
Click to collapse
I see you've received a response in the other thread regarding if XT1644 will accept the update; given you've flashed TWRP, if you wish to be very safe, I would suggest re-installing your Marshmallow ROM so you have a stock install before proceeding to Nougat. There's nothing stopping you from directly flashing Nougat, and the fastboot method for either Nougat build may correctly overwrite the relevant files, the only way is to try the procedure. Don't use the TWRP backup images of Nougat - they don't contain updates to your baseband modem and other core parts of your device - they are only meant to be used once your entire phone is updated to Nougat.
If you wish to restore back to stock MM before flashing Nougat, here's links to stock firmware for XT1644: https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-firmware-t3454980
But either way, read all the instructions first, ensure you've got all the firmware and tools you need installed/downloaded, your phone has at least 50 % battery and plenty of time, and you should be okay.
I once Hard Bricked my phone. Then when I somehow recovered it and tried to install stock firmware, it went into bootloop, then I used g5 plus software to flash boot.img and it worked but after that I lost my original recovery and I have TWRP recovery instead and I can't update my software because it will hard brick again. I have tried reflashing stock Android (problem remained the same) and I am not sure but I guess I somehow modified my system and that's why I am not able to get my stock recovery back(I tried to flash that but that failed). Please help as I need to update my system because Within months Android O updates will roll out. Thanks.
Fastboot to stock. It's the only true way to get what you want.
Karlinski said:
Fastboot to stock. It's the only true way to get what you want.
Click to expand...
Click to collapse
I'm not able to. In My Fastboot it says "System status: Modified" instead of system status Official, so any idea how to get Official System status?
fastboot doesn't care about firmware status. if you want to get official, you need to relock your bootloader. There are instructions on how to do so on the forums here.
Karlinski said:
fastboot doesn't care about firmware status. if you want to get official, you need to relock your bootloader. There are instructions on how to do so on the forums here.
Click to expand...
Click to collapse
Then I'd be able to download system updates?
harshtomar1308 said:
Then I'd be able to download system updates?
Click to expand...
Click to collapse
Depends on what happened to your device when you hard bricked it in the first place and how you recovered from it.
If you recovered using the albus (Moto Z2 Play) blankflash, then I don't think you'll be able to re-flash the stock firmware completely, as you have a different bootloader to what's expected (i.e. Moto Z2 Play bootloader on a G5 Plus). You'd still be able to flash the system and modem side of the firmware, just likely not the GPT or bootloader. Thus, you're likely better off waiting for TWRP flashables of the stock Oreo ROM, which would mean you don't have to worry about your bootloader. Of course, that means you won't be able to take OTA updates again.
What device do you have and what stock firmware were you/are you running on your device? Maybe you're flashing either the wrong firmware or too old firmware for your device.
echo92 said:
Depends on what happened to your device when you hard bricked it in the first place and how you recovered from it.
If you recovered using the albus (Moto Z2 Play) blankflash, then I don't think you'll be able to re-flash the stock firmware completely, as you have a different bootloader to what's expected (i.e. Moto Z2 Play bootloader on a G5 Plus). You'd still be able to flash the system and modem side of the firmware, just likely not the GPT or bootloader. Thus, you're likely better off waiting for TWRP flashables of the stock Oreo ROM, which would mean you don't have to worry about your bootloader. Of course, that means you won't be able to take OTA updates again.
What device do you have and what stock firmware were you/are you running on your device? Maybe you're flashing either the wrong firmware or too old firmware for your device.
Click to expand...
Click to collapse
Yes, I used this method to regain my phone. I'm on XT1686 and build number is NPN25.137-15
My device is hard bricked
harshtomar1308 said:
I once Hard Bricked my phone. Then when I somehow recovered it and tried to install stock firmware, it went into bootloop, then I used g5 plus software to flash boot.img and it worked but after that I lost my original recovery and I have TWRP recovery instead and I can't update my software because it will hard brick again. I have tried reflashing stock Android (problem remained the same) and I am not sure but I guess I somehow modified my system and that's why I am not able to get my stock recovery back(I tried to flash that but that failed). Please help as I need to update my system because Within months Android O updates will roll out. Thanks.
Click to expand...
Click to collapse
I have installed the stock firmware on my Moto g5 plus and when I updated it to .67
The phone started to be updating but when the bar fills up then my phone just stucked. Please help me I cannot even go to bootloader or the fast boot. No logo nor any kind of signals are showing but no results please help me
If some of the more experienced people here could check my steps for returning to stock, I'd really appreciate it. I have some questions and also want to confirm that I correctly understand how to do some of the others. Thanks.
My XT-1575 is running 6.0 build number MPHS24-49-18-16. I would like to change ROMs (probably to Lineage OS 14.1) but be able to return to the same build at a later time. I do not want to update the Moto firmware to 7.0.
Steps:
1) Use the instructions in the thread: [GUIDE] [XT1575] Return to stock and relock bootloader by @acejavelin
2) Download the latest 6.0 factory image available (MPHS24.49-18-8) with the link in the thread and place it in the adb platform-tools directory
3) Open a command prompt in the platform-tools directory and issue the commands listed in the thread to flash the firmware. This will not lock the bootloader because this is an earlier build.
4) As shown in the thread, go to @annoyingduck's post (post #366) to get the OTA .zip to go from 18-8 to 18-16
5) This needs to be sideloaded.Is TWRP used for this? Will TWRP still be in recovery after running the commands in step 3? Do I need to flash TWRP to recovery? When I flash the OTA, will this replace TWRP with the stock recovery?
6) Is there an additional step(s) to lock the bootloader? The instructions say flashing an older build will fail at locking the bootloader. Instead, the OTA is flashed manually, but how does the bootloader get relocked?
7) Are there any additional steps to return to official status to pass safetynet and get OTAs?
xdafan15 said:
If some of the more experienced people here could check my steps for returning to stock, I'd really appreciate it. I have some questions and also want to confirm that I correctly understand how to do some of the others. Thanks.
My XT-1575 is running 6.0 build number MPHS24-49-18-16. I would like to change ROMs (probably to Lineage OS 14.1) but be able to return to the same build at a later time. I do not want to update the Moto firmware to 7.0.
Steps:
1) Use the instructions in the thread: [GUIDE] [XT1575] Return to stock and relock bootloader by @acejavelin
2) Download the latest 6.0 factory image available (MPHS24.49-18-8) with the link in the thread and place it in the adb platform-tools directory
3) Open a command prompt in the platform-tools directory and issue the commands listed in the thread to flash the firmware. This will not lock the bootloader because this is an earlier build.
4) As shown in the thread, go to @annoyingduck's post (post #366) to get the OTA .zip to go from 18-8 to 18-16
5) This needs to be sideloaded.Is TWRP used for this? Will TWRP still be in recovery after running the commands in step 3? Do I need to flash TWRP to recovery? When I flash the OTA, will this replace TWRP with the stock recovery?
6) Is there an additional step(s) to lock the bootloader? The instructions say flashing an older build will fail at locking the bootloader. Instead, the OTA is flashed manually, but how does the bootloader get relocked?
7) Are there any additional steps to return to official status to pass safetynet and get OTAs?
Click to expand...
Click to collapse
All of these questions are answered in the threads you referenced...
1) Yup, that's fine.
2) Same, remember to extract it... Although I would recommend extracting it to a unique directory and add platform-tools to your path
3) Correct, sort of... You cannot use an older firmware to lock, but there are specific commands to attempt a lock and to just flash. When downgrading be aware gpt.bin (partition table) and bootloader.img may fail and that is normal.
4) Yup, good there
5) Sideload in this regard is accomplished through stock recovery, start stock recovery and select "Apply update from ADB" then execute "adb sideload update.zip"
6) Your only option at this time to lock the bootloader is to flash a Nougat firmware image... We do not have a Marshmallow 18-16 image and without one you cannot lock the bootloader, no matter how much you downgrade.
7) "Official" status is not required to pass SafetyNet API check on Marshmallow or Nougat, but you must have a purely stock /boot, /recovery, and /system partition. On Nougat you must also have a locked bootloader. The only way to get back to "Official" status is to flash an official firmware image and then take an official OTA successfully.
Thanks for your help, @acejavelin! Some further clarifying questions-
acejavelin said:
3) Correct, sort of... You cannot use an older firmware to lock, but there are specific commands to attempt a lock and to just flash. When downgrading be aware gpt.bin (partition table) and bootloader.img may fail and that is normal.
Click to expand...
Click to collapse
I assumed I would just copy and paste the commands you provided exactly as listed. Is that OK? Or do I need to substitute the commands you showed at the bottom:
fastboot oem fb_mode_set instead of fastboot oem lock begin
fastboot oem fb_mode_clear instead of fastboot oem lock
Or it doesn't matter?
acejavelin said:
6) Your only option at this time to lock the bootloader is to flash a Nougat firmware image... We do not have a Marshmallow 18-16 image and without one you cannot lock the bootloader, no matter how much you downgrade.
Click to expand...
Click to collapse
And the way to do this is to flash NPH25.200-22 from adb fastboot as shown in your other thread, correct? Can I also take the Moto OTA from 18-16 (the one I am currently being offered)?
acejavelin said:
7) "Official" status is not required to pass SafetyNet API check on Marshmallow or Nougat, but you must have a purely stock /boot, /recovery, and /system partition. On Nougat you must also have a locked bootloader. The only way to get back to "Official" status is to flash an official firmware image and then take an official OTA successfully.
Click to expand...
Click to collapse
So you are saying that if I follow the instructions to return to 18-16 I will be able to recieve OTAs and will pass safetynet. Only downside is that my bootloader will remain unlocked?
By flashing the Nougat image, my bootloader can be locked (part of the sequence of commands)
but only by doing this plus accepting a future OTA will the status return to "official"?
[/QUOTE]
xdafan15 said:
Thanks for your help, @acejavelin! Some further clarifying questions-
I assumed I would just copy and paste the commands you provided exactly as listed. Is that OK? Or do I need to substitute the commands you showed at the bottom:
fastboot oem fb_mode_set instead of fastboot oem lock begin
fastboot oem fb_mode_clear instead of fastboot oem lock
Or it doesn't matter?
Click to expand...
Click to collapse
Using the 'oem lock' commands will fail, and it will get stuck in fb_mode that you have to clear. Better to just use the fb_mode commands up front.
xdafan15 said:
And the way to do this is to flash NPH25.200-22 from adb fastboot as shown in your other thread, correct? Can I also take the Moto OTA from 18-16 (the one I am currently being offered)?
Click to expand...
Click to collapse
Guess I am confused... if you flash NPH25.200-22 you won't be offered 18-16 OTA, but will likely be offered the NPHS25-201.1 update. If you are on 18-8 and are pure stock you can accept the 18-16 update, and within 24 hours after that is successfully applied you should be offered the Nougat update(s).
xdafan15 said:
So you are saying that if I follow the instructions to return to 18-16 I will be able to recieve OTAs and will pass safetynet. Only downside is that my bootloader will remain unlocked?
By flashing the Nougat image, my bootloader can be locked (part of the sequence of commands)
but only by doing this plus accepting a future OTA will the status return to "official"?
Click to expand...
Click to collapse
You can chose whether to lock the bootloader or not by flashing the Nougat image, the question is which do you want? Just flashing an image won't make your software status "official" in most cases. We have seen some cases where it does, but we don't know why and in most cases it will stay unofficial until you accept an OTA update, then somehow it miraculously becomes official. The key to remember here is once you accept an OTA that is a higher version than the stock images we have, you have no way to lock the bootloader, so if you want to lock your bootloader in your current state the only possible way is to flash the NPH25.200-22 image using the locking commands, because if you don't lock at this point and accept an OTA update you cannot relock the bootloader until (or if) we get a newer factory image.
One more thing to keep in mind, if you accept an OTA to Nougat or manually upgrade, and decide to downgrade to Marshmallow, it is possible, but once this is done do NOT accept any OTA updates back to Nougat, it will hard brick... and I mean perma-brick such that a mainboard replacement is necessary to fix it, which Moto won't do because you unlocked the bootloader, so basically the phone is trash.
@acejavelin, thanks again and sorry for asking so many questions. For those of us who only play around at this stuff, it is hard to keep this all in our heads. Especially since a wrong move can hard brick the phone as you mentioned.
acejavelin said:
Guess I am confused... if you flash NPH25.200-22 you won't be offered 18-16 OTA, but will likely be offered the NPHS25-201.1 update. If you are on 18-8 and are pure stock you can accept the 18-16 update, and within 24 hours after that is successfully applied you should be offered the Nougat update(s).
Click to expand...
Click to collapse
Interesting- You say if I return to stock 18-8, Moto will offer me the 18-16 OTA first, I won't be offered Nougat directly?
Since I would want to relock the bootloader, is there any reason not to just go directly from Lineage OS to NPH25.200-22?
The string of commands to issue (shown in the "return to stock" thread) is the same whether it is a MM or Nougat image that is being flashed, correct?
acejavelin said:
One more thing to keep in mind, if you accept an OTA to Nougat or manually upgrade, and decide to downgrade to Marshmallow, it is possible, but once this is done do NOT accept any OTA updates back to Nougat, it will hard brick... and I mean perma-brick....
Click to expand...
Click to collapse
If I downgrade to MM and then flash the NPH25.200-22 image, at that point is it again OK to take an OTA to NPHS25-201.1 with causing problems?
Does it matter if the Nougat version I was originally on before downgrading was 200-22 vs 201.1?
Thanks again!
xdafan15 said:
@acejavelin, thanks again and sorry for asking so many questions. For those of us who only play around at this stuff, it is hard to keep this all in our heads. Especially since a wrong move can hard brick the phone as you mentioned.
Interesting- You say if I return to stock 18-8, Moto will offer me the 18-16 OTA first, I won't be offered Nougat directly?
Since I would want to relock the bootloader, is there any reason not to just go directly from Lineage OS to NPH25.200-22?
The string of commands to issue (shown in the "return to stock" thread) is the same whether it is a MM or Nougat image that is being flashed, correct?
If I downgrade to MM and then flash the NPH25.200-22 image, at that point is it again OK to take an OTA to NPHS25-201.1 with causing problems?
Does it matter if the Nougat version I was originally on before downgrading was 200-22 vs 201.1?
Thanks again!
Click to expand...
Click to collapse
Yes
No
Yes, except watch the number of sparse chunks
Yes, as long as you flash the full image and not as an OTA.
No
I guess this conversation is going all over the place... are you wanting to return to stock and lock the bootloader or run a custom ROM? You can't really do both. If you want to return to stock, that depends on your current version, if you want to run custom there are less constraints. This is a 2 year old device, just pick one and go with it.
Thanks for your patience with me, @acejavelin.
My intent is to switch to Lineage OS now, but make sure I understand the correct steps to return to stock in the future if I want to. I wanted to confirm that info before everyone is gone from the Moto X Pure forum. I tend to keep my phones for a long time.
I think I've got it now, but I do want to ask 1 more clarifying question:
I asked "If I downgrade to MM and then flash the NPH25.200-22 image, at that point is it again OK to take an OTA to NPHS25-201.1 with causing problems?"
and you answered
"Yes, as long as you flash the full image and not as an OTA."
Do you mean
(A) as long as I flash the full 25.200-22 image and then take the OTA (which motorola will offer to me at that point to get to 25-201.1),
OR
(B) did you mean after flashing the image to get to 25.200-22, I cannot take the OTA to 25-201.1, but must wait until (if) someone posts the image file for 25-201.1 and flash that?
Sorry for asking so many questions. I really appreciate it
xdafan15 said:
Thanks for your patience with me, @acejavelin.
My intent is to switch to Lineage OS now, but make sure I understand the correct steps to return to stock in the future if I want to. I wanted to confirm that info before everyone is gone from the Moto X Pure forum. I tend to keep my phones for a long time.
I think I've got it now, but I do want to ask 1 more clarifying question:
I asked "If I downgrade to MM and then flash the NPH25.200-22 image, at that point is it again OK to take an OTA to NPHS25-201.1 with causing problems?"
and you answered
"Yes, as long as you flash the full image and not as an OTA."
Do you mean
(A) as long as I flash the full 25.200-22 image and then take the OTA (which motorola will offer to me at that point to get to 25-201.1),
OR
(B) did you mean after flashing the image to get to 25.200-22, I cannot take the OTA to 25-201.1, but must wait until (if) someone posts the image file for 25-201.1 and flash that?
Sorry for asking so many questions. I really appreciate it
Click to expand...
Click to collapse
Honestly, the smart bet would be to flash the NPH25.200-22 image, then do NOT take any OTA. Then go ahead and flash TWRP and LineageOS. You can always go back to the full image without issues of "downgrading".
At this time the 25.200-22 image is the newest we have and downgrading can never be perfect. If there is no reason to take the OTA (like you are going to just flash Lineage anyway), then don't take it... At least you have an easy out.
The main reason for this is we don't have an image for 25-201.2 and we don't know when, or even if, we ever will. For example, we never did get an image of Marshmallow 18-16 and at this point I doubt we ever will.
Thanks for the excellent support, @acejavelin! That's why I love XDA.
@acejavelin I was on official (stock) 7.0, build NPH25.200-23. I installed unofficial LOS 14.1 (by Hashbang) because I have the N modem, and official LOS 14.1 only supports the M modem. I later decided to go back to stock. As we all know the NPH25.200-23 factory images have not yet been (or ever will be) released, so I followed your guide on how to revert to stock, except I flashed the available NPH25.200-22 partitions (the ones that flashed, anyway, minus the ones that gave Preflash Validation Error) without relocking the bootloader, and now I am back to NPH25.200-22. I also immediately received the notification for the -23 OTA but I did not install it. My question is this: Can I accept the -23 OTA or will I risk bricking? I never downgraded to M, I only had unofficial LOS 14.1 builds, and now the stock -22 build.
My battery is acting all weird, shutting down at about 70%, plugging it again and showing 50%. When I boot, if I unplug it will immediately shut down. Basically it's plugged in the whole time. I have no idea what's causing this, the fact that I flashed unofficial LOS, or because of a faulty battery since I had changed it before flashing LOS), or because of partitions mismatch. So I'm trying to narrow it down and pinpoint the cause. But it seems that every time I try something, it makes the battery worse.
The battery is probably reaching the end of it's life...
You can accept the -23 OTA, the risks are minimal if everything you told me is correct.
acejavelin said:
The battery is probably reaching the end of it's life...
You can accept the -23 OTA, the risks are minimal if everything you told me is correct.
Click to expand...
Click to collapse
Thanks for the reply. Are you sure that taking the OTA on mismatched partitions (bootloader and gpt from -22 and everything else from -23) would not brick? There have been cases like that in the past (https://forum.xda-developers.com/moto-x-2014/general/warning-hard-bricking-downgrading-t3116379) on the Moto X 2nd Gen because the updater script did not have the correct checks to prevent a brick. Maybe it was the case when downgrading to a previous full version i.e. from 5.1 to 4.4.4, or just on older phones/older versions. Do we know if the updater script from -22 to -23 has to correct checks to prevent a brick?
discovery94 said:
Thanks for the reply. Are you sure that taking the OTA on mismatched partitions (bootloader and gpt from -22 and everything else from -23) would not brick? There have been cases like that in the past (https://forum.xda-developers.com/moto-x-2014/general/warning-hard-bricking-downgrading-t3116379) on the Moto X 2nd Gen because the updater script did not have the correct checks to prevent a brick. Maybe it was the case when downgrading to a previous full version i.e. from 5.1 to 4.4.4, or just on older phones/older versions. Do we know if the updater script from -22 to -23 has to correct checks to prevent a brick?
Click to expand...
Click to collapse
Your not downgrading... Either it will work or the checks will fail. The chances of bricking are minimal.
The issue of the MM vs. N modems is part of the reason I started this thread. My understanding was that official Lineage OS 14.1 would only work properly if the phone was still running MM firmware because LOS 14.1 was not configured to handle the N modem as written above by @discovery94. It seems like the unofficial LOS 14 by @Hashbang173 has some problems, so it seemed safer to stay on MM. But @acejavelin's advice to me was to upgrade to N before switching ROMS which would seem to severely limit choices of ROMs
I guess the options are stay on MM and have a large selection of ROMS (including official LOS 14.1)
or upgrade to N and only select form Hashbang's LOS, RR by LuisG, and AOSP EX by Obsolete1,
or maybe upgrade to N, then extract the modem from MM stock firmware and flash it to avoid the modem mismatch problem.
Have I summed this up properly?
acejavelin said:
Your not downgrading... Either it will work or the checks will fail. The chances of bricking are minimal.
Click to expand...
Click to collapse
So the OTA was unsuccessful. The recovery first showed installing update, then displayed "Error", and then the phone rebooted and displayed an update not successful screen (Images attached). I guess the only way is to use the factory images, but I won't even get my hopes up for that.
Hello all
I installed the latest T585XXU4CRJ8 Oreo 8.1 update over Nougat 7 on the SM-T585. (BTU / UK)
Everything went well using Odin and the Oreo stock rom from the Updato website.
Cleared the cache and factory reset from recovery mode as normal practice. Booted up ok.
The problem is the device doesn't recognise the network sim card anymore (worked perfectly on Marshmallow & Nougat).
I've tried factory reset a few times, no difference.
Removed and reinserted the sim, even tried another sim.
Having checked 'about tablet > software details' , carrier is unknown and the IMEI has dissapeared !
I've tried to reinstall Nougat 7 and Marshmallow 6 back on the SM-T585 and Odin fails every time.
Tried 2 computers and 3 different usb cables.
Even trying to reinstall Oreo 8.1 again Odin fails!
Theres no frp lock activated, and the oem unlock tab is checked, usb debugging enabled too.
I've read somewhere Samsung have done something to Oreos BootLoader file to stop people downgrading back to earlier software.
I know its early days, but if anyone can offer any solutions, it'd be appreciated.:good:
How to change the BL file version, so i can reinstall earlier stock roms back?
The Oreo update seems more hassle than its worth and I didnt expect the sim card to be unrecognised once updated, let alone being faced with the puzzle of how to downgrade the software.
Thanks for reading. :good:
I think the problem was I used all four files (AP, BL,CP & CSC) from the Netherlands rom and that's whats screwed the device up!
As in no SIM card acknowledgement. I ran the IMEI number off the rear casing through a blacklist checking site and it came back clean.
After many attempts trying every Odin program variant possible and even tried mixing and matching files from different stock roms ( MM 6.0.1 , N7 and Oreo 8.1). To try and get the network carrier file installed, Odin refused to install anything.
https://desktop.firmware.mobi/device:754/firmware:1660
https://download.chainfire.eu/1069/CF-Root/CF-Auto-Root/CF-Auto-Root-gtaxllte-gtaxlltexx-smt585.zip
https://twrp.me/samsung/samsunggalaxytaba101wifi2016.html
Tried the above routes to root to no avail, but Magisk worked by patching the boot.img file (which worked ok). Then tried Odin to install TWRP recovery, again from the site above, nothing but blue and fuzzy lines on the boot screen. The device wouldn't boot into the OS, had to go straight to download mode. Prior to that, I even installed the TWRP manager apk and connected to wifi to flash the TWRP.img from inside the OS environment and the same happened again with all variants of TWRP! Wouldn't boot, properly, no screen visuals, but lines......
Surely someone else on here has the same device (BTU UK) SM T585 that has a working TWRP recovery?
After many hours, I couldn't get Odin to play ball , so the only option left was to try the route of root, twrp recovery then installing a custom rom from twrp.
(https://forum.xda-developers.com/ga...-ultra-lean-rom-galaxy-tab-10-1-2016-t3467942)
But it's a no go as TWRP wouldn't install properly, I'm totally miffed by the damage the software has done.
Surely just reflashing the CP file should have reinstated the network facility, but it hasn't.
The last resort is for me to wait until Samsung actually release the UK version of Oreo 8.1 and see if I can get the sim card working again.
Moral of the story is wait until a UK version of the update is released, and even then you have to question is it worth it, if Samsung are making bootloader files so no downgrades are possible, nor allowing any modifications.
Hopefully this info may help others out who are thinking of upgrading or having similar issues.
Cheers for reading
tsam19 said:
I think the problem was I used all four files (AP, BL,CP & CSC) from the Netherlands rom and that's whats screwed the device up!
As in no SIM card acknowledgement. I ran the IMEI number off the rear casing through a blacklist checking site and it came back clean.
After many attempts trying every Odin program variant possible and even tried mixing and matching files from different stock roms ( MM 6.0.1 , N7 and Oreo 8.1). To try and get the network carrier file installed, Odin refused to install anything.
https://desktop.firmware.mobi/device:754/firmware:1660
https://download.chainfire.eu/1069/CF-Root/CF-Auto-Root/CF-Auto-Root-gtaxllte-gtaxlltexx-smt585.zip
https://twrp.me/samsung/samsunggalaxytaba101wifi2016.html
Tried the above routes to root to no avail, but Magisk worked by patching the boot.img file (which worked ok). Then tried Odin to install TWRP recovery, again from the site above, nothing but blue and fuzzy lines on the boot screen. The device wouldn't boot into the OS, had to go straight to download mode. Prior to that, I even installed the TWRP manager apk and connected to wifi to flash the TWRP.img from inside the OS environment and the same happened again with all variants of TWRP! Wouldn't boot, properly, no screen visuals, but lines......
Surely someone else on here has the same device (BTU UK) SM T585 that has a working TWRP recovery?
After many hours, I couldn't get Odin to play ball , so the only option left was to try the route of root, twrp recovery then installing a custom rom from twrp.
(https://forum.xda-developers.com/ga...-ultra-lean-rom-galaxy-tab-10-1-2016-t3467942)
But it's a no go as TWRP wouldn't install properly, I'm totally miffed by the damage the software has done.
Surely just reflashing the CP file should have reinstated the network facility, but it hasn't.
The last resort is for me to wait until Samsung actually release the UK version of Oreo 8.1 and see if I can get the sim card working again.
Moral of the story is wait until a UK version of the update is released, and even then you have to question is it worth it, if Samsung are making bootloader files so no downgrades are possible, nor allowing any modifications.
Hopefully this info may help others out who are thinking of upgrading or having similar issues.
Cheers for reading
Click to expand...
Click to collapse
I had the same problem, went from Lineage 14.1 to Oreo stock rom (the flashable one you can find on this site, i flashed also the Bootloader/modem file in the thread). No imei, no baseband. Returned back to lineage and got back imei and baseband, but after my screen was going to sleep (after the regular 1 min) I had only black screen and vertical red lines. I flashed then Resurrection Remix 6.2, Lineage 15, Lineage 16, always the same problem. Then I used Odin and the original firmware of Nougat from SamMobile, at the first attempt i flashed only the AP file. I turned to have the same problem, but this time the lines were white. I flashed all the 4 files again with Odin, problem solved and back to Lineage 14.1 (the only custom rom were everything works)
Domenico F.
What version of TWRP have you installed for the T585 and from what site?
Also what root method did you use?
I have tried all available and all seem corrupt i.e don't install properly, no proper boot up with onscreen options. Just fuzzy lines.
Again root i've tried many, but don't work with this Oreo 8.1., even Magisk is problematic.
I think its pretty sad of Samsung sending out poor quality updates for us to use. Their heading the same way as Apple and the way they control customers.
If I could go back to a custom MM or Nougat, I would. But TWRP / ROOT are an issue. i.e no TWRP no custom rom!
If anyones thinking of updating and reading this topic, stay clear of the Oreo 8.1 update for the SM T585. Once installed theres no turning back.....so it seems
Thanks for replying.
tsam19 said:
Domenico F.
What version of TWRP have you installed for the T585 and from what site?
Also what root method did you use?
I have tried all available and all seem corrupt i.e don't install properly, no proper boot up with onscreen options. Just fuzzy lines.
Again root i've tried many, but don't work with this Oreo 8.1., even Magisk is problematic.
I think its pretty sad of Samsung sending out poor quality updates for us to use. Their heading the same way as Apple and the way they control customers.
If I could go back to a custom MM or Nougat, I would. But TWRP / ROOT are an issue. i.e no TWRP no custom rom!
If anyones thinking of updating and reading this topic, stay clear of the Oreo 8.1 update for the SM T585. Once installed theres no turning back.....so it seems
Thanks for replying.
Click to expand...
Click to collapse
just flash the nougat firmware from SamMobile. You have to flash all the 4 files in the zip you are going to download. AP, CSC, etc. Once you have your tablet completely stock you can install again TWRP and flash whatever CUSTOM rom you want.
I easily rooted the phone with odin flashing only the TWRP in AP box (twrp taken from this post https://forum.xda-developers.com/showpost.php?p=78145080&postcount=160) avoid the auto-reboot. You have to put the tab in DL mode, connect it to pc, start odin flash the twrp in AP file e unselect Auto-reboot. As soon as the process is done you have to log in recovery mode at the first boot with home + power + vol up and flash dm-verity. I rooted with Magisk without any problem just flashing the v17.3. Now i' m back to nougat (from Oreo) and i can install whatever custom rom i want. But honestly the only one fully working is Lineage 14.1. Resurrection remix 6.2 has problem with camera and gps don't lock. Same for Oreo version. Tried Pie, same problem.
Domenico F
Thanks for the info.
I tried to install MM 6.01 & Nougat 7 stock rom and they wouldn't install, no matter what I did. ( see Odin pictures )
The last chance was to try Oreo 8.1 again and I did manage to reflash the 'Netherlands stock Oreo 8.1 rom' (after 10 hours!) using all four files (AP,BL,CP,CSC).
I then reset the device a couple of times via stock recovery. Took the OEM lock off, theres no FRP lock either. Enabled developer mode > debug mode (all the usual setting changes prior to rooting / twrp install).
At this point the imei and sim card network ARE recognised and work on the device as normal.
HOWEVER I found once I rooted by any genuine means > Magisk v16 (patched boot img taken from stock rom) and also the CF gtaxlltex sm t585 auto root method.
And when the device booted back up, the 'imei and sim card' WERE NOT usable, nor recognised, no network...........I also noticed BusyBox wouldn't install at all, message about integrity of root.
Adaway and Lucky Patcher recognised root.
I also then tried installing TWRP 3.0.2.0 -3.2.3.0 from many locations and again, none of them worked at all. Just blue lines, fuzzy screen etc. On some occasions Odin wouldn't even process the files.
I include pictures of the files I used.
Its evident to me that I can use the device normally i.e sim card , make calls, data etc if I don't attempt to install root / twrp recovery.
So no root , no twrp , then no custom rom usable or installable. It sounds like Samsung are out to stop custom software on their products.
If the Netherlands stock rom 'BL' (boot loader) file is encrypted with this new binary v3 or v4 to stop OS modifications. I wouldn't recommend using it when flashing the new Oreo 8.1 rom or future new releases.
The best way is to just use the AP file ONLY and overlap Nougat 7 or MM 6. And because you've kept your original BL from earlier stock roms, it may be possible to downgrade back to MM or Nougat if need be.
Once the latest new Oreo / Pie 'BL files' are used in the Odin flashing process, it causes big problems.
Hopefully, maybe someone smart enough can find away to decipher these new BL files and offer a replacement method. which will allow software downgrades and modifications
tsam19 said:
Domenico F
Thanks for the info.
I tried to install MM 6.01 & Nougat 7 stock rom and they wouldn't install, no matter what I did. ( see Odin pictures )
The last chance was to try Oreo 8.1 again and I did manage to reflash the 'Netherlands stock Oreo 8.1 rom' (after 10 hours!) using all four files (AP,BL,CP,CSC).
I then reset the device a couple of times via stock recovery. Took the OEM lock off, theres no FRP lock either. Enabled developer mode > debug mode (all the usual setting changes prior to rooting / twrp install).
At this point the imei and sim card network ARE recognised and work on the device as normal.
HOWEVER I found once I rooted by any genuine means > Magisk v16 (patched boot img taken from stock rom) and also the CF gtaxlltex sm t585 auto root method.
And when the device booted back up, the 'imei and sim card' WERE NOT usable, nor recognised, no network...........I also noticed BusyBox wouldn't install at all, message about integrity of root.
Adaway and Lucky Patcher recognised root.
I also then tried installing TWRP 3.0.2.0 -3.2.3.0 from many locations and again, none of them worked at all. Just blue lines, fuzzy screen etc. On some occasions Odin wouldn't even process the files.
I include pictures of the files I used.
Its evident to me that I can use the device normally i.e sim card , make calls, data etc if I don't attempt to install root / twrp recovery.
So no root , no twrp , then no custom rom usable or installable. It sounds like Samsung are out to stop custom software on their products.
If the Netherlands stock rom 'BL' (boot loader) file is encrypted with this new binary v3 or v4 to stop OS modifications. I wouldn't recommend using it when flashing the new Oreo 8.1 rom or future new releases.
The best way is to just use the AP file ONLY and overlap Nougat 7 or MM 6. And because you've kept your original BL from earlier stock roms, it may be possible to downgrade back to MM or Nougat if need be.
Once the latest new Oreo / Pie 'BL files' are used in the Odin flashing process, it causes big problems.
Hopefully, maybe someone smart enough can find away to decipher these new BL files and offer a replacement method. which will allow software downgrades and modifications
Click to expand...
Click to collapse
Honestly i think this run for Oreo it's not really worth. I said you what I did and now i have no problems. I'm not in hurry to use Oreo (as stock rom). I think Lineage 14.1 is the most stable and fastest rom i tried till now, and most of all everything is working. I think i'll give a try via Odin to the official stock rom when it will be available for download (i live in Germany) but sadly I don't use most of the Samsung bloatware installed by default.
WRP Oreo 8.1 on Galaxy Tab 10.1 (T585)
Then I've tried
twrp_3.2.3-1_sm-t585_29918 which gives only stripes when booting into recovery
Do I have to flash the stock boot/recovery before flashing this one,
or this is broken, as well.
Many thanks for a hint,
Helmut
Hope this helps.
So, as I was trying to search for my Galaxy Tab A6 (SM-T585) for Deodexed Stock ROM, I stumbled upon this thread https://forum.xda-developers.com/galaxy-tab-a/themes/mod-twrp-odin-t3650215 just follow the instructions to fully flash Oreo. By the way when flashing Root, I would recommend Magisk Beta https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
it does not damage the IMEI at all(Thread here, read the comment:https: //forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) . The TWRP, I think we should leave it be, don't flash an update for the TWRP.
Thanks. Hope this helps.
MiaMOTo SU # said:
By the way when flashing Root, I would recommend Magisk Beta https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
it does not damage the IMEI at all
Click to expand...
Click to collapse
Neither does a custom recovery, so not sure what your point is?
I mean if your having problems using MAGISK use the beta version
Hello,
I'm having big problems flashing any ROM on my Oneplus 5 atm.
At the beginning of this month, I wanted to unroot my rooted Android 8.0 or 8.1 (One of them, it was OxygenOS, but not the newest version)+ Xposed Oneplus 5.
I got a couple of errors, most of the time error 7.
After hours, old and new recoverys (TWRP) from blu_spark, codeworkx and some xda user recoverys and diffrent OxygenOS versions i finally managed it to install a Oxygen version with Android 7.1.1 on the phone. The Problem was: I always got errors (Installation failed) when I wanted to intall Software Updates no matter if I tryed it by myself or with the official system update in android.
So and today the official beta build of OxygenOS for 9.0 released and I was so stupid and thought I can make this an easy one.
Now I'm sitting here since 9:30am and try to flash Android 9, or any Android except 7.1.1 (only Oxygen Versions). Most of the Time i'm getting ERROR:7, it doesnt matter with which Recovery or Build.
When I got this problem at the first Time, my Phone was shown as "" (The error was something like: This Package is for a "Oneplus 5" this is a "").
When I get this scentence now (not every Recovery is showing it) it says my Phone is a "OnePlus5T", but i have a Oneplus 5.
Also (maybe partly) important things are:
- I tryed to edit the updater-script and delete the assets lines but there were no asset lines. Tryed it anyways and it didnt work. (and i really dont want to try this again)
I tryed to google this error for hours and many people meant that this is the way to go but I dont belive it. Isn't there any way to rename my phone, if yes: what do I have to do? I have TWRP and access to the command prompt aswell. If anyone can successfully create the 9.0 beta without the assets I would be happy but i dont think that is the solution for my problem, just a workaround.
- I think the problem is just something about my devices name. The strange part is that it accepted 7.1.1. And this was 100% a Oneplus 5 ROM.
- 7.1.1 isnt the way to go for me anymore. I dont like android 7 and it has so old security patches..
- Fingerprint sensor and screen got replaced
thank you for reading this and maybe helping me. I dont have the best language skills, if you need more Information about my Phone, please ask
EDIT1: As I said, 7.1.1 is still successfull, i tryed it a couple of mins ago. no error 7 or sth
maybe you can try revert to fully stock setup{without TWRP) and update to pie?
I have problem with error 7 when i tried to flash latest open beta (pie). I didn't find any solution.... :crying:
petryrety said:
I have problem with error 7 when i tried to flash latest open beta (pie). I didn't find any solution.... :crying:
Click to expand...
Click to collapse
Make sure the download isn't corrupt or if you extract the compatibility.zip use a recommended tool.
I had this problem couple of months ago. I solved it by flashing an old os version then flashing stock recovery(I don't remember if I locked the bootloader). boot in to the phone and download and update through ota( I did 3 updates this way). Then install twrp and root. Now I can flash any oos update without error 7.
May work
This is a post I wrote for another thread. I have found that this method fixes the error 7 issue, and allows you to update all the way to Pie without issues. When updating to Pie, use 7-Zip, not winrar or any other non-recommended programs to remove compatibility.zip from the firmware archive before flashing. I found that winrar causes treble errors or error 7.
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
iwantademo123 said:
This is a post I wrote for another thread. I have found that this method fixes the error 7 issue, and allows you to update all the way to Pie without issues. When updating to Pie, use 7-Zip, not winrar or any other non-recommended programs to remove compatibility.zip from the firmware archive before flashing. I found that winrar causes treble errors or error 7.
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
Click to expand...
Click to collapse
Yeah, that's what I wrote here https://forum.xda-developers.com/oneplus-5/help/massive-problems-error7-t3878372/post78503983 and in flashing instructions for open beta and stable builds in their first posts.
strongst said:
Yeah, that's what I wrote here https://forum.xda-developers.com/oneplus-5/help/massive-problems-error7-t3878372/post78503983 and in flashing instructions for open beta and stable builds in their first posts.
Click to expand...
Click to collapse
That's good, It's good advice. I am just stressing to everyone in this thread, how important it is to follow that and use a recommended tool to remove compatibility.zip because removing compatibility.zip sounds very trivial thing, but it's actually really important to use a tool like 7-Zip that doesn't break the firmware in the process.
Also, the link to my other post ( https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13 ) should be detailed and comprehensive enough to help people with error 7 in other scenarios or that are trying to update to oreo or other stock firmwares too. This method restores the phone back to factory condition, including all the partitioning. Updating with a locked bootloader can fix a lot of update errors. I've found that after 5.1.5 it is safe to unlock the bootloader and take updates. But as you mentioned, for an unlocked bootloader, compatibility.zip needs to be removed from the firmware archive, and a tool such as 7-Zip must be used to do so as other archive managers break the update entirely (with error 7).
Good luck everyone trying to update, hope our advice helps :good:
So I flashed OOS 5.0.1 then went back to stock recovery. I then locked my bootloader. After which I booted into OxygenOS and updated it all the way to pie(took 3 OTAs). Now I've got a locked bootloader and pie but I'm wondering if the process to unlock the bootloader is the same or different now that there is a vendor drive?
TurtleSandals said:
So I flashed OOS 5.0.1 then went back to stock recovery. I then locked my bootloader. After which I booted into OxygenOS and updated it all the way to pie(took 3 OTAs). Now I've got a locked bootloader and pie but I'm wondering if the process to unlock the bootloader is the same or different now that there is a vendor drive?
Click to expand...
Click to collapse
The unlocking process of the bootloader is the same!
I am having the exact same problem, tried everything from above. Can get anything more recent than 7.1.1 on my oneplus 5. evrything else is error 7. Any update
mathgerm said:
I am having the exact same problem, tried everything from above. Can get anything more recent than 7.1.1 on my oneplus 5. evrything else is error 7. Any update
Click to expand...
Click to collapse
Please see here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post79938097