Do Custom Roms ignore Bootloader versions? - Samsung Galaxy S7 Questions and Answers

I have just purchased an S7 which includes the Oreo operating system (binary 5). Will I be able to restore my TRWP backup of Superman Rom (Nougat binary 2) on it? If so, should I just restore boot, system and data?
Thanking you in advance.
EDIT: Thank you for your replies. Restored Superman Nougat ROM on the new device (binary 5). Seems to run perfectly, but yes, bootloader and modem haven't been (and probably can't be) downgraded. Cheers

Yes and no, TWRP will let you roll back the ROM, but the bootloader will stay as is. A mismatch between bootloader and OS version can cause issues, but not always. YMMV.

Beanvee7 said:
Yes and no, TWRP will let you roll back the ROM, but the bootloader will stay as is. A mismatch between bootloader and OS version can cause issues, but not always. YMMV.
Click to expand...
Click to collapse
ymmv? your methods may vary?
nvm, your mileage may vary

Related

[HELP] how to downgrade Galaxy S6 from LATEST 6.0.1 (DPFX BL) to 5.1.1

hi, i really want to downgrade my S6 to lollipop but i have one of the latest bootloader (DPFX).
Downgrade was perfectly possible when i was on first build of marshmallow, but now, since i upgraded to DPFX bootloader, i have only fails with odin, and bootloops with custom roms...
is there any solution? if only i could flash an older bootloader, then i will be saved.
but if i flash an old bootloader with odin, i have a fail, so i don't know what to do
Some people suggested to me to use an old TWRP backup and i found it on my pc (with all partitions files: bootloader,system,radio and data, but i didn't use data) but using it, it's the same of flashing a custom rom: bootloop, and i suspect that the old bootloader never was flashed.
help
cescof said:
hi, i really want to downgrade my S6 to lollipop but i have one of the latest bootloader (DPFX).
Downgrade was perfectly possible when i was on first build of marshmallow, but now, since i upgraded to DPFX bootloader, i have only fails with odin, and bootloops with custom roms...
is there any solution? if only i could flash an older bootloader, then i will be saved.
but if i flash an old bootloader with odin, i have a fail, so i don't know what to do
Some people suggested to me to use an old TWRP backup and i found it on my pc (with all partitions files: bootloader,system,radio and data, but i didn't use data) but using it, it's the same of flashing a custom rom: bootloop, and i suspect that the old bootloader never was flashed.
help
Click to expand...
Click to collapse
If you are on a newer mm bootloader then downgrading to lollipop is not possible
sofir786 said:
If you are on a newer mm bootloader then downgrading to lollipop is not possible
Click to expand...
Click to collapse
I knew this, but i want to know if there is a way, a not official way, like reinstalling bootloader in a forced way that doesn't care about security problems... this thing has no sense.... why totally prevent to downgrade? However, i thing it's NORMALLY impossible, but not
TOTALLY impossible
cescof said:
I knew this, but i want to know if there is a way, a not official way, like reinstalling bootloader in a forced way that doesn't care about security problems... this thing has no sense.... why totally prevent to downgrade? However, i thing it's NORMALLY impossible, but not
TOTALLY impossible
Click to expand...
Click to collapse
As far as I know if you're on a newer bootloader official or not there is no current method to downgrade. Maybe a phone shop has specialist equipment to do this but that's me taking a shot in the air
I was able to downgrade but not because i wanted, i flashed a corrupt firmware with ODIN and i have to do an emergency recovery with Smart Switch, my carrier doesn't have Marshmallow on the S6 so my phone restored in Lollipop

A9 Back to stock -> question about returning to Android Pay and eventually Nougat

I've a device that is S-ON , TWRP 3.0.2-0 recovery installed , unlocked USA. Was running CM13 and later a lineage build...i just wiped/ reflashed the stock boot and system image so i've got things more or less back to original. All's good. However my bootloader remains unlocked. Do i need to relock it to get Android Pay working again? I was able to add a card, but have not tested it in the real world yet. My understanding is locking the bootloader will erase my data. Given I'd like to try that Nougat flavor and I don't think that will come OTA with an unlocked bootloader, maybe now's the time sense I think i'll have to flash that manually
Sorry, still new to joy of working with these devices. Fun tho
mlecho said:
I've a device that is S-ON , TWRP 3.0.2-0 recovery installed , unlocked USA. Was running CM13 and later a lineage build...i just wiped/ reflashed the stock boot and system image so i've got things more or less back to original. All's good. However my bootloader remains unlocked. Do i need to relock it to get Android Pay working again? I was able to add a card, but have not tested it in the real world yet. My understanding is locking the bootloader will erase my data. Given I'd like to try that Nougat flavor and I don't think that will come OTA with an unlocked bootloader, maybe now's the time sense I think i'll have to flash that manually
Sorry, still new to joy of working with these devices. Fun tho
Click to expand...
Click to collapse
No, if Android pay has a problem, it will reject you DURING the process of adding a card, if you add a card sucussfully, your good to go.
If you want to try nougat, please note that that change is irreversible. The firmware is non-downgradeable. I don't think locking the bootloader will erase data, but if it does it PROBABLY will warn you.
The_scam said:
No, if Android pay has a problem, it will reject you DURING the process of adding a card, if you add a card sucussfully, your good to go.
If you want to try nougat, please note that that change is irreversible. The firmware is non-downgradeable. I don't think locking the bootloader will erase data, but if it does it PROBABLY will warn you.
Click to expand...
Click to collapse
Thanks for all that...just to be clear, the only way to get Nougat is to flash it ? or is it also OTA?
mlecho said:
Thanks for all that...just to be clear, the only way to get Nougat is to flash it ? or is it also OTA?
Click to expand...
Click to collapse
It is an OTA, you can have s-on, but you can't have an unlocked bootloader, root, or system modifications if any kind.
The_scam said:
It is an OTA, you can have s-on, but you can't have an unlocked bootloader, root, or system modifications if any kind.
Click to expand...
Click to collapse
Sorry I have a question, I have an A9 (European model) S-ON with CM 14.1 and I would like to get S-OFF in order to back to stock. The problem is that I have read that Sunshine only works with stock ROM and, out of the box, my phone came with vodafone uk ROM and I can't find, on the internet, the exact same ROM as mine ( I have found an older version but because I have S-ON I can't downgrade ). There is another way to make Sunshine works? Thanks in advance
Lolli26 said:
Sorry I have a question, I have an A9 (European model) S-ON with CM 14.1 and I would like to get S-OFF in order to back to stock. The problem is that I have read that Sunshine only works with stock ROM and, out of the box, my phone came with vodafone uk ROM and I can't find, on the internet, the exact same ROM as mine ( I have found an older version but because I have S-ON I can't downgrade ). There is another way to make Sunshine works? Thanks in advance
Click to expand...
Click to collapse
what is your rom version number/firmware version 1.57?
The_scam said:
what is your rom version number/firmware version 1.57?
Click to expand...
Click to collapse
No my firmware version is 1.62.161.2
Lolli26 said:
No my firmware version is 1.62.161.2
Click to expand...
Click to collapse
i cant find anything either, i guess you'll have to wait until the rom is released.
The_scam said:
It is an OTA, you can have s-on, but you can't have an unlocked bootloader, root, or system modifications if any kind.
Click to expand...
Click to collapse
ahh, so i will need to re-lock if i want this OTA.
And btw, Android Pay worked, just as you said it would!
mlecho said:
ahh, so i will need to re-lock if i want this OTA.
And btw, Android Pay worked, just as you said it would!
Click to expand...
Click to collapse
Good, I think you can download the ota and sideload it, should be in one of the general threads. Think it's called any news on 7.0
So, after all this, i had Android Pay (AP) working great w/ 1.57.617.60 flashed back to my phone. I never re-locked my bootloader. This a.m. i flashed nougat, both boot and system (RUU_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.18.617.1) - All's great. However while shopping i was rejected by AP with the message in the attached screen shot. Is this because i never re-locked the bootloader? What are the consequences by doing so? Can I eventually re-unlock for future flashing?
NOTE - my device is not rooted, despite the accusations from the modal!
mlecho said:
So, after all this, i had Android Pay (AP) working great w/ 1.57.617.60 flashed back to my phone. I never re-locked my bootloader. This a.m. i flashed nougat, both boot and system (RUU_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.18.617.1) - All's great. However while shopping i was rejected by AP with the message in the attached screen shot. Is this because i never re-locked the bootloader? What are the consequences by doing so? Can I eventually re-unlock for future flashing?
NOTE - my device is not rooted, despite the accusations from the modal!
Click to expand...
Click to collapse
In nougat, it checks for unlocked bootloaders sadly you can't relock bootloader in nougat.
The_scam said:
In nougat, it checks for unlocked bootloaders sadly you can't relock bootloader in nougat.
Click to expand...
Click to collapse
oh no...really? no 'fastboot oem lock'? crap. Perhaps the "upgrade" was a mistake. So i'm without?
mlecho said:
oh no...really? no 'fastboot oem lock'? crap. Perhaps the "upgrade" was a mistake. So i'm without?
Click to expand...
Click to collapse
Yep, looks like it unless you downgrade and relock bootloader, then upgrade back to nougat
MGfusion said:
Yep, looks like it unless you downgrade and relock bootloader, then upgrade back to nougat
Click to expand...
Click to collapse
My goal was keep su and also get nougat. A9 has the bug about OEM unlocking just like all other 7.0 devices. It will most likely get fixed at 7.1.1, the nexuses and all other devices running 7.0 seem to have this "bug"
The_scam said:
My goal was keep su and also get nougat. A9 has the bug about OEM unlocking just like all other 7.0 devices. It will most likely get fixed at 7.1.1, the nexuses and all other devices running 7.0 seem to have this "bug"
Click to expand...
Click to collapse
ahh, so that means, as i understand it, if all goes to plan, we should one day expect a 7.1.1 update that will allow me to finally get back to AP?
mlecho said:
ahh, so that means, as i understand it, if all goes to plan, we should one day expect a 7.1.1 update that will allow me to finally get back to AP?
Click to expand...
Click to collapse
As long as you don't care about root. You can always downgrade to mm, lock, and OTA back to nougat
The_scam said:
As long as you don't care about root. You can always downgrade to mm, lock, and OTA back to nougat
Click to expand...
Click to collapse
ok, but just so i am clear , if i lock while in nougat, there's no going back ? i can not then unlock and downgrade?
mlecho said:
ok, but just so i am clear , if i lock while in nougat, there's no going back ? i can not then unlock and downgrade?
Click to expand...
Click to collapse
No, you can only UNLOCK in nougat. If you want to relock the bootloader, you will have to downgrade to marshmallow and loose your root, or wait for Android 7.1.1
downgrade means i have to wipe data, right? The upgrade that was not the case. I am only assuming

Bootloop, oem, many problems

Hello there,
About year ago I've done an update to 6.0 android. Battery was charged near full and everything seemed okey. But, after update I faced a bootloop. So I tried to flash stock firmware and... failed. Many times. I'm unable to boot into recovery mode. Factory mode also isnt working. So, I tried to unlock my bootloader and flash another image, but when I try to unlock, I get a: "Check allow oem unlock in developer options". Sadly, I cant boot to check this option Is there any way to unlock oem without running android? What can I do? :crying:
Jaszka said:
Hello there,
About year ago I've done an update to 6.0 android. Battery was charged near full and everything seemed okey. But, after update I faced a bootloop. So I tried to flash stock firmware and... failed. Many times. I'm unable to boot into recovery mode. Factory mode also isnt working. So, I tried to unlock my bootloader and flash another image, but when I try to unlock, I get a: "Check allow oem unlock in developer options". Sadly, I cant boot to check this option Is there any way to unlock oem without running android? What can I do? :crying:
Click to expand...
Click to collapse
You can flash the /persist partition from a device which has had OEM Unlock previously enabled in Developer Options.
MotoJunkie01 said:
You can flash the /persist partition from a device which has had OEM Unlock previously enabled in Developer Options.
Click to expand...
Click to collapse
How can you flash the /persist partition in a device with a locked bootloader? Doesn't this contain other information as well?
I think the real problem here is either the OP is not using the correct factory firmware image, or incorrect user procedure.
acejavelin said:
How can you flash the /persist partition in a device with a locked bootloader? Doesn't this contain other information as well?
I think the real problem here is either the OP is not using the correct factory firmware image, or incorrect user procedure.
Click to expand...
Click to collapse
You are probably correct. Even with a locked bootloader, certain partitions can be flashed as long as downgrading is not detected. Example, if I have an xt1548 Moto G3 running on stock 5.1.1 firmware, and I have a locked bootloader, I can flash either an updated 6.0.1 stock firmware package or I can reflash the 5.1.1 firmware with the same build as the one already installed. The bootloader will, however, prevent downgrading. In flashing the /persist partition, the .img being flashed would need to be from an equal or newer build as well.
But again, your statement regarding the correct firmware procedure and/or correct firmware package is likely correct.
MotoJunkie01 said:
You are probably correct. Even with a locked bootloader, certain partitions can be flashed as long as downgrading is not detected. Example, if I have an xt1548 Moto G3 running on stock 5.1.1 firmware, and I have a locked bootloader, I can flash either an updated 6.0.1 stock firmware package or I can reflash the 5.1.1 firmware with the same build as the one already installed. The bootloader will, however, prevent downgrading. In flashing the /persist partition, the .img being flashed would need to be from an equal or newer build as well.
But again, your statement regarding the correct firmware procedure and/or correct firmware package is likely correct.
Click to expand...
Click to collapse
You can't flash anything except a bootloader. I was in this situation as MotoJunkie knows and nothing works. I did have a full backup of every partition on the phone and none flashed. Today I bricked it so badly that it doesn't even turn on anymore. My tip is to not mess with the bootloader and stuff and just use the phone normally as many things are encrypted on this phone.
purplefruity said:
You can't flash anything except a bootloader. I was in this situation as MotoJunkie knows and nothing works. I did have a full backup of every partition on the phone and none flashed. Today I bricked it so badly that it doesn't even turn on anymore. My tip is to not mess with the bootloader and stuff and just use the phone normally as many things are encrypted on this phone.
Click to expand...
Click to collapse
Yes I recall your situation and your hard brick. I'm saying that under normal circumstances you can flash full firmware packages with a locked bootloader, as long as downgrading is not attempted.
MotoJunkie01 said:
Yes I recall your situation and your hard brick. I'm saying that under normal circumstances you can flash full firmware packages with a locked bootloader, as long as downgrading is not attempted.
Click to expand...
Click to collapse
You can't flash regular ones too. It has to be a newer firmware for the locked bootloader to let it pass
purplefruity said:
You can't flash regular ones too. It has to be a newer firmware for the locked bootloader to let it pass
Click to expand...
Click to collapse
That's what I was saying. An equal or newer one. Downgrading isn't permitted.
MotoJunkie01 said:
That's what I was saying. An equal or newer one. Downgrading isn't permitted.
Click to expand...
Click to collapse
Mine was on marshmallow and it wouldn't want to flash marshmallow stock so what I was saying is that you can't go anywhere unless stock nougat is released for this device.
purplefruity said:
Mine was on marshmallow and it wouldn't want to flash marshmallow stock so what I was saying is that you can't go anywhere unless stock nougat is released for this device.
Click to expand...
Click to collapse
You obviously developed corrupt partitions some way or another. I flash stock firmware packages with a locked bootloader on a regular basis. You should always be able to flash the same firmware build that is currently installed on your device.
MotoJunkie01 said:
You obviously developed corrupt partitions some way or another. I flash stock firmware packages with a locked bootloader on a regular basis. You should always be able to flash the same firmware build that is currently installed on your device.
Click to expand...
Click to collapse
O well I guess my device was different then. Won't turn on at all now . Gonna sell it for parts so at least I get some money back.

[BACKUP-IMAGE] [XT1572 EU] Moto X Style Android 7.0 Nougat Build NPH25.200-15 (EU)

Hi guys,
I bought the "new" Moto X Style last week for 250€(new, white, 32gb) and updated it to the highest Android 6.0 version from Motorola. After that, i flash the OTA-file from:
https://forum.xda-developers.com/moto-x-style/general/ota-moto-x-style-android-7-0-nougat-t3630248
After that, i unlock the bootloader, flash TRWP, clean the data and create a System backup:
https://xda.bioharz.xyz/2017-07-15--06-20-47_NPH25.200-15.7z
This is unmodified! and unrootedI actually have no time to create a System image, but this should also work for you.
I hope this can help you.
Thanks,
One question, this backup work in XT1572 CID12?
Necrodaemon said:
Thanks,
One question, this backup work in XT1572 CID12?
Click to expand...
Click to collapse
nope, only for the EU model
Netflix not working after installing
anth0nymDROID said:
Netflix not working after installing
Click to expand...
Click to collapse
Probably failing SafetyNet API check but what is the error?
Nougat will fail if the bootloader is unlocked and you don't have the Magisk module to stop SafetyNet. In Nougat an unlocked bootloader is enough to get it to fail even if otherwise 100% stock.
Netflix could also be confused as to your region if you restored the backup in this thread.
acejavelin said:
Probably failing SafetyNet API check but what is the error?
Nougat will fail if the bootloader is unlocked and you don't have the Magisk module to stop SafetyNet. In Nougat an unlocked bootloader is enough to get it to fail even if otherwise 100% stock.
Netflix could also be confused as to your region if you restored the backup in this thread.
Click to expand...
Click to collapse
Im reteu fr in Germany but if that's the case well no mobile Netflix I can still live my life without it.
anth0nymDROID said:
Im reteu fr in Germany but if that's the case well no mobile Netflix I can still live my life without it.
Click to expand...
Click to collapse
Magisk 13.3 can help with the safety net test. Here is how to install at stock: post #4
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
dzidexx said:
Magisk 13.3 can help with the safety net test. Here is how to install at stock: post #4
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
Click to expand...
Click to collapse
That's good advice!! Thanks I'll try it later and see how it goes
What is the proper way to flash this backup using TWRP? I did a adb push to /sdcard with al files from the extracted .7z file but TWRP can't ze the backup.
What am I doing wrong?
xabr3 said:
What is the proper way to flash this backup using TWRP? I did a adb push to /sdcard with al files from the extracted .7z file but TWRP can't ze the backup.
What am I doing wrong?
Click to expand...
Click to collapse
Extract the backup zip file. Copy the last folder (containing the boot and system images) to your phone's TWRP Backup folder. Now you will see it in TWRP. Now perform a full backup. Then restore the copied-over nougat backup. Now you can pick on of the following two options.
1. f you have time, you do not need to delete your data before rebooting. You can always uninstall and reinstall any problem apps that show up after rebooting. That is what I did.
2. Of course, if you are in a hurry, you can delete your data and then reboot. That would be called a "clean install" and I don't do that very often.
Hope this helps.
@bioharz
Cheers for this. I was contemplating what method might be easiest for upgrading my rooted Moto X Style (EU) from MM 6.01 to Nougat 7.0. Ideally, this would have been a TWRP flashable ZIP, however, you have provided the second best option, which is a TWRP backup.
My method was as follows:
1) Make full TWRP backup of existing MM installation to extSD
2) Backup my Nova settings to extSD
3) Download, unzip and copy your backup to the TWRP location on extSD
4) Boot into TWRP and wipe Dalvik/ART, Cache, System and Data partitions via Advanced Wipe menu
5) Flash System and Boot partitions from your Nougat backup, BUT NOT EFS partition !!!
6) Reboot, log onto previous Google Account and restore all apps.
7) Restore Nova settings
8) Root with SuperSU (systemless) and SuHide
Worked a treat :good:
Are you sure - you need nougat with old radios?
You could reflash stock MM, update to Nougat, root, restore all you want. @Yemble
Will it work on moto x style Indian variant?
dzidexx said:
Are you sure - you need nougat with old radios?
You could reflash stock MM, update to Nougat, root, restore all you want. @Yemble
Click to expand...
Click to collapse
I am certain that I do not wish to screw up my phone with someone elses IMEI. Besides, what exactly is wrong with the MM radios? They are working perfectly on my phone.
Actually, given that I am now in a good position to experiment further, I have flashed the Nougat EFS partition on its own to my phone. Thankfully, it did not affect the IMEI or any network connectivity (SIM or WiFi). However, it has not changed the base band version either, so it may, in fact, be identical to the MM EFS anyway!
coolncoolest said:
Will it work on moto x style Indian variant?
Click to expand...
Click to collapse
Take a TWRP backup first, then give it a go. What have you got to lose?
I suggest that you try it without the EFS partition first. If that works, take another TWRP backup and then try flashing EFS on its own.
@coolncoolest @Yemble
Don't flash/restore EFS from another phone - you can lose your IMEI.
India - RetAsia version has the same baseband as RetEu - cid7.
Dual sim probably will not work.
dzidexx said:
@coolncoolest @Yemble
Don't flash/restore EFS from another phone - you can lose your IMEI.
India - RetAsia version has the same baseband as RetEu - cid7.
Dual sim probably will not work.
Click to expand...
Click to collapse
Clearly you are wrong about this (on this particular phone model), as I have already tried it and it proved that it did not break, or change, anything! I am aware that flashing EFS can be dangerous on older Samsung phones, hence my cautious approach that you appeared to be dissing in your previous post
I believe in hard facts, rather then hearsay. I have now upgraded three XT1572 (EU) phones from the posted TWRP image using the method that I outlined previously, together with the later flashing of the EFS partition. All three phones work perfectly and all three pass SafetyNet.
Someone else may be less fortunate than you and there is no reason to flash/restore efs.
Not only Samsung can lost imei in this way - Lenovo(+tablets), other Moto series, all Mtk devices(there is easy way to restore imei).
For Moto I don't know any restoring procedure. Sorry - one - mainboard replacement. @Yemble
dzidexx said:
Someone else may be less fortunate than you and there is no reason to flash/restore efs.
@Yemble
Click to expand...
Click to collapse
Really, then what was the point of your post at the top of this page?
Yemble said:
Really, then what was the point of your post at the top of this page?
Click to expand...
Click to collapse
Do you mean:
Nougat with old radios?
I meant:
Flash stock 6.0.1 24...58-5 with fastboot and get ota update.
Somewhere I uploaded my backup(6.0.1 EU) - without efs.

my maxx xt1225 br is hard brick help please!!!

hi guys i'm brasilian and my english is pretty poor but lets try. i was flash 4.4.4 rom br retail. and i update via ota for lollipop.. and brick .. i search in forums here ... and i go it to put in boot loader without robot.. already try many ways to recovery my boot loader but always get error remote failure.. and already used 6.0.1 stock .. maybe i need to files atualy for this? i'm very sad my maxx is dead .. someone give me light .. help me fix this ... thank you guys
Is your bootloader locked or unlocked?
ChazzMatt said:
Is your bootloader locked or unlocked?
Click to expand...
Click to collapse
unlocked
kenedi jr said:
unlocked
Click to expand...
Click to collapse
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
ChazzMatt said:
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
Click to expand...
Click to collapse
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
kenedi jr said:
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
Click to expand...
Click to collapse
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
So I'm stuck on the bootloader. If I connect charger or pc it will already pro boot loader without the robot. I have already tried to pass stock 4.4.4 and 6.0 and more etc always from the failure remote failure in bootloader appears in the log something with gt bin downgrade
ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
kenedi jr said:
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
Click to expand...
Click to collapse
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
I do not have twrp backup and I can not even install the recovery stock
kenedi jr said:
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
Click to expand...
Click to collapse
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that version to repair. Just reflash the entire full firmware.
Click to expand...
Click to collapse
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
thanks bro you saved me
kenedi jr said:
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
Click to expand...
Click to collapse
You can not flash any older gpt.bin files. You have to omit (leave out) that flash command.
Your gpt.bin file is 6.0.1, and you cannot downgrade. Even on 4.4.4, trying to accept the 5.0.2 OTA update is still older gpt.bin file in that OTA than your 6.0.1.
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
i don't have link .. i will wanting you so
kenedi jr said:
i don't have link .. i will wanting you so
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?p=72846593
ChazzMatt said:
https://forum.xda-developers.com/showthread.php?p=72846593
Click to expand...
Click to collapse
I was a bit confused with this link which is the last one? I discovered because I am Brazilian and my English was developed only by playing
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
ChazzMatt said:
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
Click to expand...
Click to collapse
Face first you're a myth. I just passed gpt.bin and got the bootloader ... I'm very happy. Do I need to pass the entire rom ??
:good::laugh:

Categories

Resources