Develop Bugs

[Q] Why does my Galaxy S3 fail when I try to install a rogers Stock ROM on it?

Here's the error I get:
Code:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks guys!
The phone is an I747 from AT&T.
I'm trying to flash the Rogers ROM on it because I am on a Rogers plan and the AT&T version is full of bloatware.

bump

Try downloading the file again. I would also try another usb slot or even pc
Sent from my SAMSUNG-SGH-I747M

mymusicathome said:
Try downloading the file again. I would also try another usb slot or even pc
Sent from my SAMSUNG-SGH-I747M
Click to expand...
Click to collapse
Just tried it again. It keeps failing at sbl2.mbn it seems.
If it means anything, I just noticed in download mode it says
Code:
SECURE CHECK FAIL : sbl2

SevKempf said:
Here's the error I get:
Code:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks guys!
The phone is an I747 from AT&T.
I'm trying to flash the Rogers ROM on it because I am on a Rogers plan and the AT&T version is full of bloatware.
Click to expand...
Click to collapse
I may be wrong but I don't think you can flash the stock ATT ROM on a Rogers device and vice versa. Also, the ATT ROM contains a different modem that may not work well for us on Rogers. Your best bet is to keep the ATT ROM and freeze/delete the bloatware using Titanium Backup Pro and flash the Rogers modem.
Or run a custom ROM.

Tony_YYZ said:
I may be wrong but I don't think you can flash the stock ATT ROM on a Rogers device and vice versa. Also, the ATT ROM contains a different modem that may not work well for us on Rogers. Your best bet is to keep the ATT ROM and freeze/delete the bloatware using Titanium Backup Pro and flash the Rogers modem.
Or run a custom ROM.
Click to expand...
Click to collapse
Yeah, I'm currently running CM10 but I find it has WAY too many bugs for me to use it, things constantly crashing, graphical glitches. The LED doesn't light up for anything except charging.
I originally did use TiBa to delete the bloat, no problem. Except AT&T replaces the Address Book with their own version the "AT&T Address Book" which syncs with some AT&T server every time I open it, super annoying.

Then why not try using one of the custom ICS/JB stock-based ROMs? As he said, i'm pretty sure it's impossible to flash a Rogers ROM on an AT&T device.
And.... which build of CM10 are you using? You could always try Task & Ktoonsez CM10-based ROM. Never experience a graphical glitch (though, i never did even on older CM10 builds, either), hardly ever have anything crash..... and as far as i'm aware, even in stock CM10, you actually have to go into the settings or find an app and manually set up the notification LED colors and what they blink for.

elementaldragon said:
Then why not try using one of the custom ICS/JB stock-based ROMs? As he said, i'm pretty sure it's impossible to flash a Rogers ROM on an AT&T device.
Click to expand...
Click to collapse
Where can I find one of these ROMs? I've searched for them but I haven't found anything. I asked someone and they suggested an AOSP, but I wasn't able to find any, so I used a AOKP ROM and when I booted the phone all that displayed was some 8bit looking gradient from Yellow to Purple, got worried and rebooted my phone and reinstalled Cyanogenmod.
elementaldragon said:
And.... which build of CM10 are you using? You could always try Task & Ktoonsez CM10-based ROM. Never experience a graphical glitch (though, i never did even on older CM10 builds, either), hardly ever have anything crash..... and as far as i'm aware, even in stock CM10, you actually have to go into the settings or find an app and manually set up the notification LED colors and what they blink for.
Click to expand...
Click to collapse
I installed Cyanogenmod from the ROM Manager app. This ROM, specifically.
Also, when I install a ROM, can I do it from CWM? Or do I need to install using Odin?

SevKempf said:
Where can I find one of these ROMs? I've searched for them but I haven't found anything. I asked someone and they suggested an AOSP, but I wasn't able to find any, so I used a AOKP ROM and when I booted the phone all that displayed was some 8bit looking gradient from Yellow to Purple, got worried and rebooted my phone and reinstalled Cyanogenmod.
I installed Cyanogenmod from the ROM Manager app. This ROM, specifically.
Also, when I install a ROM, can I do it from CWM? Or do I need to install using Odin?
Click to expand...
Click to collapse
That link you provided shows that it points to a Galaxy S2 ROM in the url. The link itself didn't work though when i clicked on it.
Try this ROM: http://forum.xda-developers.com/showthread.php?t=1766684

I wonder if the problem you're having is related to the build.prop
ATT have a device model name d2att while the Canadian variants have device model name d2can.
Search the forums add I think I've read something about that.
Also, even though you want to flash a Rogers Rom, make sure you use an ATT modem.
Sent from my SGH-I747M using xda premium

what can be error sbl2.mbn than use Odin ?
i try use other usb port in notebook, any versions Odin (v. 1.85; 3.4; 3.7), reinstalling the USB drivers and use stock SGS3 USB but problem steel be
Thanks

Definitely try out Task650's AOKP rom, Its very stable and has very few (if any) bugs.

nate_benji said:
Definitely try out Task650's AOKP rom, Its very stable and has very few (if any) bugs.
Click to expand...
Click to collapse
i'm use Task650's AOKP rom at that moment, but they are not support extSdCard 64Gb and then i'm try upload stok JB 4.1.1. from Odin i recive a fail massage i think truble in sbl2.mbn
Code:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I747MVLDLK4_I747MOYCDLK4_538866_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> sbl2.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Tybalt said:
Also, even though you want to flash a Rogers Rom, make sure you use an ATT modem.
Click to expand...
Click to collapse
Are you suggesting that I download both stock ROMs, extract them, then do a simultaneous mix and match of the parts in ODIN?
I have the AT&T i747 but want to have the reduced Rogers bloatware.

Anonymously_Unknown said:
Are you suggesting that I download both stock ROMs, extract them, then do a simultaneous mix and match of the parts in ODIN?
I have the AT&T i747 but want to have the reduced Rogers bloatware.
Click to expand...
Click to collapse
No, just get a cwm recovery and flash a AT&T modem.
Also, there's a unbloated AT&T stock ROM, why go for Rogers?

Go to twrp or cwm website and get the recovery for d2can instead of d2att. I'm not sure but it could be the source of your issue.
Sent from my SGH-I747 using xda app-developers app

Im having similar problem and need help too
I also have this secure check fail:sbl2 problem, but what I did was diffident. installed ParanoidKangDroid custom rom and then i realized that i use allshare play from stock rom pretty much so i decided to put back to stock my GS3. I used odin 3.0.7 to do that. I download the original stock rom from sammobile exactly the puerto rico version (were i live), but as i said it gives me the sbl2 fail problem.
---------- Post added at 05:19 AM ---------- Previous post was at 05:07 AM ----------
As you see Im a noobie here and I have another question. I like ParanoidKangDroid in my device but cant install allshare play so th question is: If i flash the [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][4/6/2013] KT747 - LJ7 - KTweaker, Can I install allshare play then? if yes what do i need to install it. Is there any other 4.2.2 rom that i can use the kernel mentioned above? or is there any rom which has touchwiz integrated?

sycol65 said:
but as i said it gives me the sbl2 fail problem.
Click to expand...
Click to collapse
I had downloaded the one from the stock firmware page and flashed it with the custom recovery to eliminate that issue. What you are experiencing is a bootloader mismatch.

Can you explain me the correct entire process to do that?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

slb2.mbn error, fail
SevKempf said:
Here's the error I get:
Code:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks guys!
The phone is an I747 from AT&T.
I'm trying to flash the Rogers ROM on it because I am on a Rogers plan and the AT&T version is full of bloatware.
Click to expand...
Click to collapse
This error is caused because a BAD USB CABLE. Please, use an original Samsung GGalaxy Cable. I had that problem with my GT-I9195. Fortunatelly it's working again.
The symptom was that i couldn't copy files from my computer to my smartphone.

[Q] [HELP] installed setuidoff now stuck in stock boot

So i have a T-Mobile Galaxy S4 SGH-M919, and the story goes like this
so i decided to root it, and used CWM, and installed superuser. Superuser read that there was no binary, so i searched on forums to help me out. Someone said that installing MDB-setuidoff.zip would help, and now it is soft bricked, stuck on the Galaxy S4 logo reading
"Kernel Not Seandroid Enforcing"
So i figured, that it was a kernel problem, so i looked for the stock kernel, and upon attempted installation, CWM recovery said it was aborted and not installed. At this point i said screw it, and decided to try and unroot, but now using ODIN 3.07, using the stock tar.md5 from galaxys4root website
when i try to flash the PDA, it reads "FAIL" and an error
"<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)"
i can still reach odin, and recovery mode, but need help getting a working phone again. Completely out of ideas, maybe someone can chime in and help? I don't mind going back into stock unrooted state, or some kind of different root/rom as long as its stable. Help me get my phone back!
thanks in advance

Get the stock firmware from Sammobile . com
My S4 Is Insane
Deviant Team Member

The Sickness said:
Get the stock firmware from Sammobile . com
My S4 Is Insane
Deviant Team Member
Click to expand...
Click to collapse
do i have to be a premium member, or is something wrong with their site, it wont let me download the firmware, page just says "user is not a premium member"

thewrongkyle said:
do i have to be a premium member, or is something wrong with their site, it wont let me download the firmware, page just says "user is not a premium member"
Click to expand...
Click to collapse
Just register
My S4 Is Insane
Deviant Team Member

[Q] [Help] Flashed stock ROM via ODIN, hangs at T-Mobile splash screen

Need to warranty my Note 3 due to hardware camera problem. I unlocked my factory 4.3 bootloader, installed TWRP, and went to W03 Slim 8.5. I have never ran the official 4.4.2 update which I believe implies my bootloader is still the 4.3 version.
I launched ODIN 3.07, and flashed the N900TUVUBMI7 rom from this page: AndroidRootz
Everything appears to have ran in ODIN successfully:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
The phone boots up with no warnings on the Samsung splash and then gets to the white T-Mobile 4G LTE splash and just hangs there. I've tried reflashing the firmware from ODIN with the same result.
What should I do? Should I flash up to the 4.4.2 version? The phone is going back regardless so I don't care about anything other than getting this to boot up so I can exchange it.

Tried from ODIN 3.09 with the same result. I have the 4.4.2 firmware but I am hesitant to flash it until someone can shed some light on this issue.

negativefx said:
Tried from ODIN 3.09 with the same result. I have the 4.4.2 firmware but I am hesitant to flash it until someone can shed some light on this issue.
Click to expand...
Click to collapse
Try wiping /data or a factory reset in recovery.

Have you tried re-downloading the 4.3 firmware. Sometimes this can happen from a bad download.

Shawn said:
Try wiping /data or a factory reset in recovery.
Click to expand...
Click to collapse
You read my mind... Just read that an ODIN firmware flash doesn't wipe. Booted to recovery, did a wipe data from recovery and rebooted. Works like a champ. Thanks!

happened to almost everyone, I had to odin v3.09 and run 2 times... the 1st time it said it was successful, but stuck at the Samsung screen, the 2nd time booted up just fine..
on my link I have odin and the new firmware, old firmware my stock not rooted roms... all u need for my stock not rooted is chainfire superuser app, then download busybox, your done,
look on my signature for any files needed, also uploading the Samsung driver.. no kies needed.

negativefx said:
You read my mind... Just read that an ODIN firmware flash doesn't wipe. Booted to recovery, did a wipe data from recovery and rebooted. Works like a champ. Thanks!
Click to expand...
Click to collapse
No problem, I used to forget to wipe when I put my phones back to stock with Odin.

I'm currently running an AOSP rom 4.4.2...what are the steps to flash the 4.3 stock rom touchwiz??

4.4.2 is out? newest firmware available atm is nk3 4.4.2
anyway
1. d/l firmware file from sammobile.com
2. boot to download mode
3. run odin and plug phone into pc(if you have a mac your on your own from here as i have a pc and not a mac)
4. load file you just d/led(in tar.md5 format) into the pda slot(i'm assuming you have odin 3.07)
5. click start and wait to profit.
you can also d/l 4.3 firmware from same site if you really want it.
good luck

I meant I have a AOSP custom rom its regular google not touchwiz
Sent from my SM-N900T

right. thats how you restore stock touchwiz though. it's pretty simple.

will I lose root?..so if I have this current baseband which is MI7..does that mean that I still have 4.3 bootloader?
Sent from my SM-N900T

yeah you will lose root. but you can reroot it afterwards. and yes if you flash the 4.3 firmware it'll keep the 4.3 bootloader or should anyway. might want to wait on someone else to chime in here on the bootloader and baseband though as i am not really sure. i just upgraded from a note 2 to my note 3. and i run nk3 on my note 3. it's fine with all the roms i have tryed so far though. no issues at all.

I'll wait a lil bit cause someone just told me that since I'm on 4.4.2 custom aosp rom I won't be able to revert back to 4.3 Touch wiz
Sent from my SM-N900T

i'd just go with the nk3 firmware. it's 4.4.2 stock touchwiz. works great. but thats me. hehe

this is my android version and that is my baseband..im soo confused
View attachment 3079890
Sent from my SM-N900T

ok. your baseband and bootloader are 4.3, but your custom rom is a 4.4.2 rom. if you install the nk3 firmware. you'll have stock touchwiz 4.4.2 with the nk3 baseband and bootloader along with the csc file. and a bunch of otherstuff. it will all be upgraded. instead of having a custom 4.4.2 rom you'll be on the newest stock touchwiz version which is nk3.
nk3 can be rooted. you can install a custom recovery and still reinstall custom roms.
if that makes sense.

that's wat I was looking for, thanks dude..this is my version of ODIN that I have..this is what I used to root the phone when I first got it last year
View attachment 3079899
Sent from my SM-N900T

1.8.5 will work. been so long since i seen that version. just add the tar.md5 file to the pda slot. click start and profit

is it better to upgrade ODIN to tge latest version or just stick with 1.85?
Sent from my SM-N900T

Go back to stock 4.4 from CM12

Anyone know how to do this? I thought it would be simple..just flash the stock firmware from Odin while in download mode. However when I tried that, Odin failed to flash the firmware for some reason. I'm on P600 with CM12 by Rayman.

C2Q said:
Anyone know how to do this? I thought it would be simple..just flash the stock firmware from Odin while in download mode. However when I tried that, Odin failed to flash the firmware for some reason. I'm on P600 with CM12 by Rayman.
Click to expand...
Click to collapse
Try flashing with another odin version, if you are on 3.09 try with 3.07, happened to me before & 3.07 did the trick

lsherif said:
Try flashing with another odin version, if you are on 3.09 try with 3.07, happened to me before & 3.07 did the trick
Click to expand...
Click to collapse
I tried with ODIN 3.07 and it's still failing
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Edit: Nevermind I think it was the firmware. I downloaded a newer firmware and it started flashing.

Unable to Odin stock OB7 or stock NK2.

I don't seem to be able to Odin stock OB7 or stock NK2. When I attempt to Odin either I get this on Odin:
<OSM> N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and get this on the download screen:
UDC START
SW REV CHECK FAIL : [tz]Fused 3>Binary 1
[4]eMMC write fail: TZ
Right now I'm running HYBRID_OB7sbl_SPT_N910PVPU4COG5 unrooted. Any potential help with what I've done would be great. Thanks guys.

Cant go back. Period.
Sent from my SM-N910P using Tapatalk

I have the same problem. Updated the phone with the latest from Sprint / Samsung, then tried to root and got into a boot loop. I can get into download mode and recovery. Trying to flash a ROM with CWM recovery fails too.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Read frezzas stockish thread.
Sent from my SM-N910P using Tapatalk

It's failing because the bootloader is not authenticating. Since you flashed my custom rom odin package I'm surprised it's not letting you flash the official OB7 rom tar. Apparently there's more to this equation than just the bootloader or else you tried or successfully flashed the pre-rooted kernel before you tried to odin the OB7 rom tar. Try flashing my custom OB7/OG5 rom tar again THEN flash the official OB7 rom tar. You need to be bone stock before attempting the odin of OB7. If it still fails then give up because you can't win this battle. Just update to OG5 and don't worry about it.
I'll be honest, there's really no reason why you shouldn't just go ahead and wipe everything clean and flash my custom OB7/OG5 rom tar again or the official OG5 rom tar and let your bootloader update to OG5. I think 5.1.1 is by far the best version of Android to date. I see absolutely no reason to flash older software versions because 5.1.1 is much more responsive in every way and battery life is improved as well. Don't sweat this. If I had any trouble with my OB7 bootloader I'd update mine to OG5 in a second.

After blowing nearly an entire day....
To start off my phone was stock / rooted, I then installed the latest update via Kies (OE1, wanted the Stagefreight patch) and attempted to re-root my phone which I then found was stuck in a boot loop. I got lazy, updates had been going well on the Note 4 and I failed to come to XDA to see if there were any problems rooting it, turns out there is :crying: and I couldn't get Kies to recover it, and factory reset didn't work either. To recover I tried to use ODIN to flash OB7 and received the above results, I tried a few other stock ROMs and got the same problem.
At this point I was about ready to chuck my phone out the door until I noticed a comment saying that once you flash OE1 you can't go back and the only option is to flash an AOSP ROM such as Notirized. I downloaded Notorized, following the OP directions step by step and I now have my phone back! So far I like this ROM, so maybe this was fate
http://forum.xda-developers.com/not...-noterized-rom-super-speedy-reliable-t3099382
Thanks XDA! Now if I only had come here first and saved myself an entire day of grief! (Took away from my time playing Elite Dangerous! lol).

Thanks man. I appreciate the response and the explanation. I thought it was an issue with the bootloader, but I was confused about what I had done. I did wind up wiping everything clean and flashing your custom OB7/OG5 rom tar. Thanks for putting that together. I definitely should have updated everything sooner. I appreciate the advice on the OG5 bootloader as well. Have a great weekend.
tx_dbs_tx said:
It's failing because the bootloader is not authenticating. Since you flashed my custom rom odin package I'm surprised it's not letting you flash the official OB7 rom tar. Apparently there's more to this equation than just the bootloader or else you tried or successfully flashed the pre-rooted kernel before you tried to odin the OB7 rom tar. Try flashing my custom OB7/OG5 rom tar again THEN flash the official OB7 rom tar. You need to be bone stock before attempting the odin of OB7. If it still fails then give up because you can't win this battle. Just update to OG5 and don't worry about it.
I'll be honest, there's really no reason why you shouldn't just go ahead and wipe everything clean and flash my custom OB7/OG5 rom tar again or the official OG5 rom tar and let your bootloader update to OG5. I think 5.1.1 is by far the best version of Android to date. I see absolutely no reason to flash older software versions because 5.1.1 is much more responsive in every way and battery life is improved as well. Don't sweat this. If I had any trouble with my OB7 bootloader I'd update mine to OG5 in a second.
Click to expand...
Click to collapse