I apparently did not do enough reading prior to trying to downgrade my AT&T S5 to 4.4.2 after taking the OTA 5.0 update.
I am now stuck at either the 'firmware upgrade failed' or phone constantly going to the recovery menu (depending on if i've tried to push an AP file via Odin).
I know understand downgrading is impossible at this point, but I'm trying to find a way to get my phone back up and running. Any assistance on what file(s) I can push via Odin to resolve would be greatly appreciated. My device was not rooted prior to the OTA lollipop update so I'm limited to the 'stock' recovery options.
DamnYank! said:
I apparently did not do enough reading prior to trying to downgrade my AT&T S5 to 4.4.2 after taking the OTA 5.0 update.
I am now stuck at either the 'firmware upgrade failed' or phone constantly going to the recovery menu (depending on if i've tried to push an AP file via Odin).
I know understand downgrading is impossible at this point, but I'm trying to find a way to get my phone back up and running. Any assistance on what file(s) I can push via Odin to resolve would be greatly appreciated. My device was not rooted prior to the OTA lollipop update so I'm limited to the 'stock' recovery options.
Click to expand...
Click to collapse
You need to flash the OC4 stock kernel.
muniz_ri said:
You need to flash the OC4 stock kernel.
Click to expand...
Click to collapse
Muniz, i would be more than happy to. I've been searching though for a 5.0 sm-g900a tar/md5 file that i can load/flash via Odin but I have not been able to find any (other than a 'pre-rooted' one but I want to stay stock/ unrooted if possible).
Do you have any tips on where I could find it?
Thank you!
muniz_ri said:
You need to flash the OC4 stock kernel.
Click to expand...
Click to collapse
I found your other thread, i tried using your G900A_OC4_Stock_Rooted_Firmware.tar.md5 file via Odin and selecting it for the AP field. When executing, Odin gives me:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900A_OC4_Stock_Rooted_Firmware.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
And the phone screen shows SECURE CHECK FAIL: system
It looks like I was able to resolve with the info in this post:
http://forum.xda-developers.com/att...phone-trying-to-downgrade-to-4-t3076706/page4
Sorry for not finding that sooner, usually my search-fu is pretty solid but my searches just weren't hitting that (or Muniz's other stock files available from androidfilehost).
Related
So lots of bad things have happened while trying to install a rom to my note 3. I had it rooted, with the safestrap bootloader installed, but then I tried to upload the Dynamic Kat rom but it when it went to boot it just had a blue flashing light. I then tried to restore through download mode and now it is saying
ODIN MODE
PRODUCT NAME: SM-N900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNAL LOCK: 0x0
KNOX WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION ENABLE
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
So I went through Odinv 3.09 and tried to flash back to stock using N900AUCUBMI9, but I keep getting failed messages through that. I also downloaded another program that was a one-click odin based restore but that also gave the same fail message. I eventually tried to go through Kies 3 & Kies but both said my device was not compatible with it. I am at a loss.
When trying to use odin I get this.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> One Click Downloader Mode
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
tomdrumtomthumb said:
So lots of bad things have happened while trying to install a rom to my note 3. I had it rooted, with the safestrap bootloader installed, but then I tried to upload the Dynamic Kat rom but it when it went to boot it just had a blue flashing light. I then tried to restore through download mode and now it is saying
ODIN MODE
PRODUCT NAME: SM-N900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNAL LOCK: 0x0
KNOX WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION ENABLE
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
So I went through Odinv 3.09 and tried to flash back to stock using N900AUCUBMI9, but I keep getting failed messages through that. I also downloaded another program that was a one-click odin based restore but that also gave the same fail message. I eventually tried to go through Kies 3 & Kies but both said my device was not compatible with it. I am at a loss.
When trying to use odin I get this.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> One Click Downloader Mode
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
UPDATE:
Through Odin, I have flashed just the .pit file. This allowed me to boot back into the stock OS. However, the stock OS is very buggy (Direct Pen Input has stopped x10) and various other problems.
The problem is now, that I still can't flash the stock OS through Odin. I just keep getting fails. Any idea why?
What baseband version does your device show in Settings/General/About Device?
andygev35 said:
What baseband version does your device show in Settings/General/About Device?
Click to expand...
Click to collapse
I don't know, because now its stuck in a bootloop.... it should be the baseband version for the stock firmware at 4.3 though. So it should've been N900AUCUBMI9.
I could be wrong here, but isn't DynamicKat based on kitkat? That would make it incompatible with 4.3. You may need to just Odin to stock kitkat 4.4.2. (NOT 4.4.4) Then you can use safestrap 3.75 and load DynamicKat.
http://forum.xda-developers.com/showthread.php?t=2703006
Use the four-file restore method and use the download links I provided in the OP.
andygev35 said:
I could be wrong here, but isn't DynamicKat based on kitkat? That would make it incompatible with 4.3. You may need to just Odin to stock kitkat 4.4.2. Then you can use safestrap 3.75 and load DynamicKat.
http://forum.xda-developers.com/showthread.php?t=2703006
Click to expand...
Click to collapse
I did flash to dynamic kat from 4.3 which resulted where I couldn't boot. But then I restored to 4.3. (It was broken as I said, something about the pen not working and lots of lag). The note 3 was on 4.3 to begin with. Right now I'm trying to get my 4.3 to work but Odin just gives me fail messages for when I try to flash 4.3. Flashing the BL and AP end in errors. Flashing everything else gives a pass.
The only thing I know to try is to update to NC2 (4.4.2) via Odin. Maybe someone else knows how to restore to JB.
andygev35 said:
I could be wrong here, but isn't DynamicKat based on kitkat? That would make it incompatible with 4.3. You may need to just Odin to stock kitkat 4.4.2. (NOT 4.4.4) Then you can use safestrap 3.75 and load DynamicKat.
http://forum.xda-developers.com/showthread.php?t=2703006
Use the four-file restore method and use the download links I provided in the OP.
Click to expand...
Click to collapse
Alright, I did this and it worked! Its on kitkat now! Thank you!
I have searched for about the past 3-4 hours which is a lot longer than it usually takes for me to get to the bottom of these dang things. My phone (Galaxy S5 G900A Lollipop 5.0) has been really screwy on the WiFi lately (home, out in public, family members homes) so I decided (after a factory reset, safe mode, etc failing) to go ahead and try to downgrade my phone. So I went online and found out you can do it with Odin (3.09, 3.10, 3.06) and attempted it. I downloaded a stock 4.4.4 firmware and went to work. Immediately it failed with the error I am still getting which is the following:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Example of the firmware update screen: Unable to post outside link, just google "firmware update encountered an issue galaxt s5" it's the first image.
Example of the download screen I use with Odin (as instructed): Unable to post outside link, just google "download mode glaaxy s5" it's the first image.
I have attempted using both the old and new version of Kies to perform the emergency and normal firmware update procedures. My phone does not show in the emergency firmware recovery screen and the firmware update mode ends in an error telling me to use the emergency firmware update, which as mentioned does not work.
With Odin I have attempted: Multiple computers, multiple USB ports on each computer, reinstalling Samsung drivers, restarting computer, multiple Odin versions, multiple firmware files (4.4.4, 4.4.2), running as administrator
Windows 8.1
Update on errors: My screen shows the following error on my phone in RED under "UDC Start" when Odin Fails:
SYS REV CHECK FAIL : Refer 2 > Binary 1
SECURE CHECK FAIL : system
You can't downgrade from 5.0. Flash 5.0 and you will be fine. If I'm not mistaken, the new bootloader is not backwards compatible and therefore won't let a downgrade happen.
Took to Best Buy, flashed and resolved in less than 10 minutes at Samsung center.
daddynexxus said:
Took to Best Buy, flashed and resolved in less than 10 minutes at Samsung center.
Click to expand...
Click to collapse
You won't be able to downgrade and that was your problem in the beginning
Same issue
I have having the same issue, I tried flashing Odin 4.4 back to the S5 once it has 5.0. It now errors out in Odin and in Kies, I really dont know what to do. Error: SW Rev Check Fail : Aboot Fused 3 > Binary
Rayman3030 said:
I have having the same issue, I tried flashing Odin 4.4 back to the S5 once it has 5.0. It now errors out in Odin and in Kies, I really dont know what to do. Error: SW Rev Check Fail : Aboot Fused 3 > Binary
Click to expand...
Click to collapse
Go here and follow direction. Do the last section of the OP.
http://forum.xda-developers.com/showthread.php?p=60012961
Sent from my SAMSUNG-SM-G900A
I did something stupid I know and I have looked everywhere and seem to find only info about rooted fixes Here is the steps that now have me brickked:
Started with 4.4.1 Rooted
Flashed via Oden 4.4.2 Stock
Then Did OTA updates to 5.1.1
Tried To Revert to 4.4.2 Stock Via ODEN - Phone Said Firmware Error Load KIES and restore... never worked again
Tried Loading G900A_OC4_Stock_Partitions.tar.md5 got me to Black and white Samsing Logo Nothing Else
I dont care what I get I just need a phone, HELP!!!!!
Flash the 5.0 file and you will be good once you upgrade to lollipop you can't go back to 4.4.4 after upgrading and there is no way to go back after
Sent from my SAMSUNG-SM-G900A using Tapatalk
I have looked for 5.0 files where might I find one?
Tried this G900AUCU3BOC4_OneClick
but it fails and goes to SW REV FAIL : [aboot]Fused 4 > Binary 3
On Oden it says
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> One Click Downloader Mode
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004>
<ID:0/004>
<OSM> All threads completed. (succeed 0 / failed 1)
ThanksTons!
Since you did OTA updates, your bootloader has been updated and you can NOT revert back to older version. You basically need to reflash 5.1.1 firmware and stay there. Try to restore using Kies application.
LoSt180 said:
Since you did OTA updates, your bootloader has been updated and you can NOT revert back to older version. You basically need to reflash 5.1.1 firmware and stay there. Try to restore using Kies application.
Click to expand...
Click to collapse
Again tried Kies, Kies 3, and the new smart swap, nothing allows me to complete this they all say no repair option available when tools and emergency recovery is selected. Tried initialization and it tried v 4.4.2 which crashes.
HELP!!
You should be able to use ODIN and the link to the 5.1.1 firmware in the top of this post http://forum.xda-developers.com/att...w-to-update-to-g900aoi5-5-1-unrooted-t3235774
Did you figure out what to do? I'm in the same boat. My phone boots to "Firmware Upgrade encountered an issue". Kies does not find the phone. I was on OF3 trying to downgrade to stock ROM. Link posted above does not have ODIN flashable files except for bootloader it seems.
Found out how to go back to working phone by flashing file at the end of first post here (http://forum.xda-developers.com/att...w-to-unbrick-flash-to-stocknce-g900a-t3077652)
Mine still is bricked did anyone have a fix?
This is the OI5 files. Try and see if these work in Odin.
http://forum.xda-developers.com/showthread.php?t=3360699
Sent from my SAMSUNG-SM-G870A using Tapatalk
Ok guys, so I flashed 5.1.1 on my phone but I lost root. So I decided to root using the Skipsoft Toolkit. I think it tried to install a bootloader (pretty sure it did). Before this I tried to use the chainfire root but didnt work. ok So then the phone started boot-looping and I decided to flash 4.4.4 back on. But now Odin keeps giving me this error
Code:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1100)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
On the phone side the error I'm getting is this:
Code:
UDC START
SW REV CHECK FAIL : [ABOOT]Fused 2 > Binary 1
[1] eMMC write fail: ABOOT
Idk what to do at this point. I'm assuming I have to flash the boot-loader right?
If I could get some advice, so I don't brick my phone further.
Please please please, help! v__v
If you mean latest 5.1.1 you most likely have updated Samsung kernel security that won't let you downgrade bootloader, you need to flash current stock firmware to recover your device.
Pp.
PanchoPlanet said:
If you mean latest 5.1.1 you most likely have updated Samsung kernel security that won't let you downgrade bootloader, you need to flash current stock firmware to recover your device.
Pp.
Click to expand...
Click to collapse
I tried flashing 5.1.1 But to no avail. Anything else I could do?
I had a similar problem with my note 3. What in did was I backed up my sd card and wiped it, redownloaded stock bootloader and firmwares, and used a different usb cable and port . Then odin worked like charm
My friend ended up putting 4.4.4 on it somehow. Maybe it was just an issue with my computer? Thank you guys for your suggestions btw. I tried all of them.
ChameleonQS said:
My friend ended up putting 4.4.4 on it somehow. Maybe it was just an issue with my computer? Thank you guys for your suggestions btw. I tried all of them.
Click to expand...
Click to collapse
Do you happen to have the link to the 4.4 build? I'm trying to downgrade from 5.1.1 as well
Hi, have a T-Mobile G920T S6 with 6.0.1 and want to downgrade to 5.11. Receiving the following odin FAIL error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU2BOFJ_G920FOXA2BOFJ_G920FXXU2BOFJ_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and following error on the phone:
"Sw rev check fail device 4 binary 2"
Tried (2) different original Samsung ROMs:
G920TUVU2COF6_G920TTMB2COF6_G920TUVU2COF6_HOME.tar.md5
on (2) different versions of Odin 10.+. No luck with any fixes in forums.
Any help would be greatly appreciated.
Thanks,
-Todd
cogancorp said:
Hi, have a T-Mobile G920T S6 with 6.0.1 and want to downgrade to 5.11. Receiving the following odin FAIL error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU2BOFJ_G920FOXA2BOFJ_G920FXXU2BOFJ_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and following error on the phone:
"Sw rev check fail device 4 binary 2"
Tried (2) different original Samsung ROMs:
G920TUVU2COF6_G920TTMB2COF6_G920TUVU2COF6_HOME.tar.md5
on (2) different versions of Odin 10.+. No luck with any fixes in forums.
Any help would be greatly appreciated.
Thanks,
-Todd
Click to expand...
Click to collapse
I thought I'd read that 6.0 was not going to prevent flashing back to 5.0 but I may be wrong. If I may inquire, what is your reasoning in wanting to go back to LP?
cwhiatt said:
I thought I'd read that 6.0 was not going to prevent flashing back to 5.0 but I may be wrong. If I may inquire, what is your reasoning in wanting to go back to LP?
Click to expand...
Click to collapse
Hi, thanks for the reply. All of the phones in our office are on 5.1 and we wanted to clone a new phone to save the time of setting up. We did a test run on 6.0.1 and the battery performance was horrible. Even on a rooted S6 phone with Greenify and most of the boatware frozen we got half the life as a 5.1. Let me know if you have any info on how to downgrade.
Thanks again for the note.
-Todd
coagncorp said:
Hi, thanks for the reply. All of the phones in our office are on 5.1 and we wanted to clone a new phone to save the time of setting up. We did a test run on 6.0.1 and the battery performance was horrible. Even on a rooted S6 phone with Greenify and most of the boatware frozen we got half the life as a 5.1. Let me know if you have any info on how to downgrade.
Thanks again for the note.
-Todd
Click to expand...
Click to collapse
Not sure of what MM setup you ran, but to each his own and if you like LP better by all means for what you like!
First question, you have a T model device correct? 920T or 925T?
I ask because I read that you mention a Tmo based device, but the tar file showing from your ODIN shot show a tar file meant for "F" device?
You will definitely want to make sure and use the correct file for your actual device! Maybe the shot was a generic one, IDK, but that is very important!
And to downgrade, I did this many times when MM first came out and I began my ROM update build.
Just check this post. Confirmed working and can be done in just a couple minutes.
The reason the odin fails at the sboot.img part is because if the screenshot is accurate and you tried flashing a F based tar on your T based device, it's because sboot.img is the bootloader and they aren't compatible with eachother.
Good luck and if you want the most customizable S6 rom for any device, check my OZOP v14 for LP and OZOP v5 is current MM build!
Hope the info works out for you!
coagncorp said:
Hi, thanks for the reply. All of the phones in our office are on 5.1 and we wanted to clone a new phone to save the time of setting up. We did a test run on 6.0.1 and the battery performance was horrible. Even on a rooted S6 phone with Greenify and most of the boatware frozen we got half the life as a 5.1. Let me know if you have any info on how to downgrade.
Thanks again for the note.
-Todd
Click to expand...
Click to collapse
Also, if you had a rooted S6, maybe try Deep Sleep battery saver over greenify. I have a flat S6 which is rooted and running stock firmware and Deep Sleep and I average about 17hours between charges with a 4hr 10min SOT.
Sent from my SM-G920T using XDA-Developers mobile app
stangdriver44 said:
Not sure of what MM setup you ran, but to each his own and if you like LP better by all means for what you like!
First question, you have a T model device correct? 920T or 925T?
I ask because I read that you mention a Tmo based device, but the tar file showing from your ODIN shot show a tar file meant for "F" device?
You will definitely want to make sure and use the correct file for your actual device! Maybe the shot was a generic one, IDK, but that is very important!
And to downgrade, I did this many times when MM first came out and I began my ROM update build.
Just check this post. Confirmed working and can be done in just a couple minutes.
The reason the odin fails at the sboot.img part is because if the screenshot is accurate and you tried flashing a F based tar on your T based device, it's because sboot.img is the bootloader and they aren't compatible with eachother.
Good luck and if you want the most customizable S6 rom for any device, check my OZOP v14 for LP and OZOP v5 is current MM build!
Hope the info works out for you!
Click to expand...
Click to collapse
Any ideas why i cannot downgrade, I perfer lollipop, and I have downgraded before, recently I jumped on your newest MM rom, and now I want to go back to Lollipop, but it wont allow me to flash the bootloader or modem, so I tried a whole firmware, and it still gives me this message
za33ck said:
Any ideas why i cannot downgrade, I perfer lollipop, and I have downgraded before, recently I jumped on your newest MM rom, and now I want to go back to Lollipop, but it wont allow me to flash the bootloader or modem, so I tried a whole firmware, and it still gives me this message
Click to expand...
Click to collapse
Just a noob question, what does apple has to do with android?
britchel said:
Just a noob question, what does apple has to do with android?
Click to expand...
Click to collapse
lol wow, I fixed it, wrong image attached.