Develop Bugs

How to go from rooted to unrooted jellybean?

I use a friends account. I dont know much about rooting etc and iäve tried to google some info but i get nowhere..
Can someone explain to me how to do it from aokp-maguro-build 27 to jellybean?
I know its a worthless post to many here. But not for me. So i hope you can have some patient with me.
Yours

Do you need no root, or do you just want a stock ROM without customizations?
Edit: If you want stock everything the gnex toolkit is a good place to start.
Here is the link: http://forum.xda-developers.com/showthread.php?t=1392310
Sent from my Galaxy Nexus using Tapatalk 2

If you just want stock Jelly Bean you can download the stock image from here:
https://developers.google.com/android/nexus/images
Obviously this will be 100% stock, no root or customisations. You CAN still root though.
If you want AOKP Jelly Bean you have to wipe and flash. Use something like clockworkmod to wipe and flash the latest AOKP JB Build. Still experimental though.
In any case, copy off your data as you are going to wipe in any case. Restoring the factory image !!ALSO WIPES THE SD CARD!!

Just a really simple way to unroot your device:
- Download the GNex toolkit (sticky thread)
- run it and choose the unroot option
- read and do the steps which a displayed
- finish
Sent from my Galaxy Nexus using Tapatalk 2

Okey, thanks i will try it. its just that i dont know much about it and i think my phone is **** with root. It freezes and stop working/rebooting quiet often. which is to me a big problem. So i just want stock jellybean and nothing more =)

You are using a really old AOKP ICS Build (27) and you are wondering about issues?
Not really?!
Root isn´t the reason of your reboots/freezes.

pakjebakmeel said:
If you just want stock Jelly Bean you can download the stock image from here:
https://developers.google.com/android/nexus/images
Obviously this will be 100% stock, no root or customisations. You CAN still root though.
If you want AOKP Jelly Bean you have to wipe and flash. Use something like clockworkmod to wipe and flash the latest AOKP JB Build. Still experimental though.
In any case, copy off your data as you are going to wipe in any case. Restoring the factory image !!ALSO WIPES THE SD CARD!!
Click to expand...
Click to collapse
I've downloaded it and putterd it in my phone and went to recovery mode. And brows to it and i want to install it. and it just abort it. How do i solve it? I dont want any rom stuff. Just want it to be original with jellybean! Please help me to fix it. A small fee can be paid for the effort you put in! Im totaly dumb on stuff like this.. i wish i never bricked XD
Yours

xantyfication said:
I use a friends account. I dont know much about rooting etc and iäve tried to google some info but i get nowhere..
Can someone explain to me how to do it from aokp-maguro-build 27 to jellybean?
I know its a worthless post to many here. But not for me. So i hope you can have some patient with me.
Yours
Click to expand...
Click to collapse
If you want stock Jelly Bean, follow the instructions here. They are step-by-step and n00b-friendly.

xantyfication said:
I've downloaded it and putterd it in my phone and went to recovery mode. And brows to it and i want to install it. and it just abort it. How do i solve it? I dont want any rom stuff. Just want it to be original with jellybean! Please help me to fix it. A small fee can be paid for the effort you put in! Im totaly dumb on stuff like this.. i wish i never bricked XD
Yours
Click to expand...
Click to collapse
You can't just flash the factory images from recovery like any other rom. They should be flashed from fastboot using usb(the hardest part is making the drivers work).
When the drivers and fastboot work, all you need to do is run the following commands:
"fastboot flash bootloader <name of bootloader.img here>"
"fastboot reboot-bootloader"
"fastboot flash radio <name of radio.img here>"
"fastboot reboot-bootloader"
"fastboot -w update <name of zip-update-file included>"

xantyfication said:
I've downloaded it and putterd it in my phone and went to recovery mode. And brows to it and i want to install it. and it just abort it. How do i solve it? I dont want any rom stuff. Just want it to be original with jellybean! Please help me to fix it. A small fee can be paid for the effort you put in! Im totaly dumb on stuff like this.. i wish i never bricked XD
Yours
Click to expand...
Click to collapse
If you want to do it in recovery, you can use the files I had posted here to flash IMM76I and update to JRO03C using the instructions here. (I haven't had a chance to pack up the JB files for CWM-flashing).
But I would suggest this method I had posted earlier.

[FASTBOOT][GSM][4.1.2] Rooted Factory Images

I have modified the Yakju Galaxy Nexus factory images by completely wiping my Nexus, restoring using the factory images supplied by Google, rooting them and repacking the images with root intact.
After trying so many ROMs that are available, sometimes I think, especially considering the latest releases from Google, that stock is the way to go. Flashing it using these images is my preferred method, being the cleanest, and I have provided these for your convenience as I haven’t seen them anywhere else only ever seen flashable ROMs (i.e. from Recovery) based on the factory images, etc...
These are:
Factory Images “yakju” for Galaxy Nexus “maguro” (GSM/HSPA+)
Android 4.1.2 (JZO54K) with SU binary only
Android 4.1.2 (JZO54K) with SU binary and SuperSU app
Download links are here. MD5 and SHA1 sums are listed so you can check the downloads.
You have to use Fastboot to flash these to your device. The only requirement is that your device's bootloader is unlocked, which you can easily do, but be warned that this will wipe your user data as will flashing these factory images.
To Unlock Bootloader (in the terminal):
Code:
fastboot oem unlock
Unzip the factory image and just run the flash-all.sh in a Linux terminal or flash-all.bat in the Windows command line.

thanks 'mate! I'm gonna try this out in a bit last time I was on stock was still 4.1.1, and my current custom ROM is still on that version.
What are actually the differences of 4.1.1 and 4.1.2? Just thought you had any idea.. :cyclops:

In 4.1.2 I've noticed better battery life like others have reported and notifications can now be expanded and shrunk if you hold on them and drag up and down.
Sent from my Galaxy Nexus using Tapatalk 2

rhed said:
thanks 'mate! I'm gonna try this out in a bit last time I was on stock was still 4.1.1, and my current custom ROM is still on that version.
What are actually the differences of 4.1.1 and 4.1.2? Just thought you had any idea.. :cyclops:
Click to expand...
Click to collapse
Google the changelog..............
Gave you the fishing rod, fish yourself.
https://www.google.com.sg/search?q=...65784e5eeb7334&bpcl=35466521&biw=1360&bih=643

It would be really helpful if someone could help how to install this using a Mac?

Now that's more like it:good: People should start using fastboot more often other than toolkits:good:Learn to install drivers on your computer. Thanks for posting :highfive: I just hope people take the time and learn it..

harisn said:
It would be really helpful if someone could help how to install this using a Mac?
Click to expand...
Click to collapse
I'm not 100% sure as I have never used a Mac for that but there's a good guide here.

Hey, thanks for the links, just want to ask, if I'm already rooted and unlocked my bootloader, if I flash this via fastboot, will it erase my apps/internal memory/photos and such? Quite curious it's just the unlocking the bootloader that deletes all data. Will like inquiries. Thanks!

MoZuFi93 said:
Hey, thanks for the links, just want to ask, if I'm already rooted and unlocked my bootloader, if I flash this via fastboot, will it erase my apps/internal memory/photos and such? Quite curious it's just the unlocking the bootloader that deletes all data. Will like inquiries. Thanks!
Click to expand...
Click to collapse
If you just run the script as is, it will wipe everything. The best thing to do is just flash the system.img if you want to retain your data.
"fastboot flash system system.img"
Sent from my Galaxy Nexus using Tapatalk 2

chickenfeeder said:
If you just run the script as is, it will wipe everything. The best thing to do is just flash the system.img if you want to retain your data.
"fastboot flash system system.img"
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks a lot!

[Q] Revert to stock without USB

I have been having issues with my phone not charging and being recognized in my PC. I have tried everything I can think of to fix it without success. At this point I need to send it back to Verizon, but I am currently running AOKP. So I need to revert it back to stock before I can send it.
Since the phone is not being recognized, ADB is not an option. I have tried using Mobile Odin Pro, but with v3.45 and 3.50, I get this error when I try to flash the factory image from Google: "An error occurred extracting the update script"
Any ideas how I can revert back to stock?

There ARE other ways to do it. Read the stickies.
For odin, you need compatible images with ODIN, which is not supported by Google/Samsung (just be reminded of that); the ones we get from Google are to be flashed with fastboot.
Quick tip: i believe you need to relock bootloader with the app before going back to stock completely (since you'll loose root).
Sent from my i9250

I looked at all the stickies, and I can't find anything. Am i just missing it?

this may be a shot in the dark but I had a problem with my usb port not working on my gsm gnex, and thought i needed to send it in to sammy. Then i found a thread where a guy talked about pushing the tip of a razer blade(carefully) in between the tab in the middle of the usb port and the rear of phone. I tried it and since have had no charging problems. As a matter of fact I had forgotten about it until reading this thread.
Or mabye someone with a verizon gnex can upload a stock nandroid for you. As for bootloader unlocked..

3oudreaux said:
this may be a shot in the dark but I had a problem with my usb port not working on my gsm gnex, and thought i needed to send it in to sammy. Then i found a thread where a guy talked about pushing the tip of a razer blade(carefully) in between the tab in the middle of the usb port and the rear of phone. I tried it and since have had no charging problems. As a matter of fact I had forgotten about it until reading this thread.
Or mabye someone with a verizon gnex can upload a stock nandroid for you. As for bootloader unlocked..
Click to expand...
Click to collapse
This could be. Worth a shot, IMO.
zeppelin_one said:
I looked at all the stickies, and I can't find anything. Am i just missing it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1731993

Really, all you need is flashable radio image, flashable bootloader image, stock zip file from Google, and custom recovery (such as Clockworkmod or twrp)
Swyped on my Galaxy Nexus running AOKP with Franco Kernel

kyokeun1234 said:
Really, all you need is flashable radio image, flashable bootloader image, stock zip file from Google, and custom recovery (such as Clockworkmod or twrp)
Swyped on my Galaxy Nexus running AOKP with Franco Kernel
Click to expand...
Click to collapse
Have you read the thread...? Op is trying to return the device, bad usb port.
Sent from my i9250

Restore factory (unroot, stock recovery) without USB connection
I've read through all the threads that I can find on this an other forums regarding this challenge. Basically I have an locked bootloader rooted Galaxy Nexux Toro that has a slightly tweeked rooted JRO03O system and the Jelly Bean bootloader.
I want to restore stock recovery and stock system but the USB port is totally fried. (It actually smoked last time I plugged it in).
I have Odin Mobile Pro downloaded and a tarball for 4.0.4 (VzW-PDA-ODIN-I515EL03_ICL53F_signed.tar) ready to inject using ODIN. However I'm afraid to go ahead with this because I've read that ICS can't handle the Jelly Bean bootloader that is on my phone. As far as I see it I have 4 options:
1. Go ahead and flash the ICS tarball and hope that it works with the JB bootloader but potentially be screwed if it messes up the recovery partition with no way to reflash it as I have no USB.
2. Use the tarball that was in the google release mysid-jro03o-factory-f17426e6.tgz that the toolkit extracted when it unpacked the tgz (it's called mysid-jro03o-factory-f17426e6.tar and the toolkit pulled it from the tgz along with the zip and all the other bits and pieces)
4. Flash the tarball that I created using the GNex toolkit (Wug's) that I made using the img files for system, recovery, kernel and userdata that I pulled out of mysid-jro03o-factory-f17426e6.tgz after allowing the toolkit to unpack the TGZ
4. Try and reflash the ICS bootloader and hope the phone reboots ok into my current ROM and allows me to flash the ICF53F tarball using ODIN.
Any advice on which of these options (or another not listed) stands the best chance of success from those more knowledgeable would be greatly appreciated.
Thanks!

juscoll said:
that ICS can't handle the Jelly Bean bootloader that is on my phone.
Click to expand...
Click to collapse
True, only earlier versions support older bootloaders, not the other way round. Some of it could work, maybe doesnt boot at all (it may be a bit extreme for the device not to, but maybe there's the chance.)
juscoll said:
4. Try and reflash the ICS bootloader and hope the phone reboots ok into my current ROM and allows me to flash the ICF53F tarball using ODIN.
Click to expand...
Click to collapse
Not sure how to flash ICS bootloader on the phone... I assume you're relying on Odin Mobile for this task? Anyways, if you manage to do it, then go ahead and use odin again to restore to factory.
juscoll said:
Any advice on which of these options (or another not listed) stands the best chance of success from those more knowledgeable would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Yes, just return the device. Its got a freaking bad usb port. Even if they can see you modded the rom/updated system etc, and they give you trouble, just ask them to restore the device to its factory state, without USB!! "It's a developers phone people!!!" Personally, i think they will only look at unlocked/locked boot screen.
Sent from my i9250

[Q] Can I realy just flash to CM10.1 or do I still need to root first?

I've been reading these forums in my spare time for the last week or so but I'm still a bit confused or just overlooking something. According to the CM 10.1 thread install instructions are
Install instructions:
1. Install ClockworkMod Recovery for "I927". Sorry, CM cannot provide support for other recoveries, although they may work fine.
3. Reboot into recovery and install
Click to expand...
Click to collapse
and a few people in some of the guide threads have basically stated the same. Is it really this simple now or do I still need to follow the guide from a year ago or the one in this thread http://forum.xda-developers.com/showthread.php?t=1962633 ?
So far all I have done is install CWMR Touch 6.0.1.2 Recovery and run backup in both blob and tar formats. Actually does this even work properly without rooting first?

You don't need root, but you can't quite go straight either. The current SOP is:
Flash TW-ICS, meaning UCLG9 or UCLH2 or UCLJ3, using the respective OneClick
Flash CWMR using Odin (the previous step overwrites recovery so you will have to do this again even if you flashed CWM previously)
Boot into CWM
Flash your AOSP-JB ROM of choice
Flash the correct gapps for your ROM
Format /data (aka factory reset)
Reboot into ROM and enjoy
Step 1 may or may not be necessary -- nobody's tried going from TW-GB straight to AOSP-JB yet. If you're feeling adventurous, try it and let us know how it goes.
Once you've flashed a TW-ICS once, you won't need to do it again -- at that point flashing a new TW-ICS or AOSP-JB ROM is as simple as flash-format-boot.

Thanks for the updated info, I didn't think it would be that simple.
Not sure what TW stands for since I haven't seen that abbreviation yet.
But basically for step one I can grab the UCLG9 from this thread http://forum.xda-developers.com/showthread.php?t=1841502
and flash it with CWM and then follow on from step 2? Or would I be better off grabbing the newer UCLJ3 from SamMobile and using Odin?

Bram Skull said:
Thanks for the updated info, I didn't think it would be that simple.
Not sure what TW stands for since I haven't seen that abbreviation yet.
But basically for step one I can grab the UCLG9 from this thread http://forum.xda-developers.com/showthread.php?t=1841502
and flash it with CWM and then follow on from step 2? Or would I be better off grabbing the newer UCLJ3 from SamMobile and using Odin?
Click to expand...
Click to collapse
Nope no zips or Odin just use one click the first time. So for step 1 above follow this http://www.theandroidsoul.com/android-4-0-4-ice-cream-sandwich-update-for-att-captivate-glide-i927uclg9/. Can't get easier then this.

Bram Skull said:
Thanks for the updated info, I didn't think it would be that simple.
Not sure what TW stands for since I haven't seen that abbreviation yet.
Click to expand...
Click to collapse
TW == TouchWiz. Basically official Samsung stuff and ROMs based directly on such.
But basically for step one I can grab the UCLG9 from this thread http://forum.xda-developers.com/showthread.php?t=1841502
and flash it with CWM and then follow on from step 2? Or would I be better off grabbing the newer UCLJ3 from SamMobile and using Odin?
Click to expand...
Click to collapse
I would get the full EXE, just to be sure. The CWM zips generally don't include bootloader or baseband and that's the important stuff.

I would get the full EXE, just to be sure. The CWM zips generally don't include bootloader or baseband and that's the important stuff.
Click to expand...
Click to collapse
I used the CWM flash and can confirm the no updated baseband since it still had the stock Rogers one on AT&T-ICS and in CM-10.1. Not sure about ICS but in CM-10.1 I could get voice but no data and haven't tested txt.
Going to flash back to stock with the backup I made for now while I research solutions to a few personal gripes I have with CM-10.1.
And would the UCLJ3 from SamMobile with odin or kies be as effective as the EXE version since I already have it downloaded?
Thanks for helping a total noob and to be honest this is my first Android phone.

Bram Skull said:
I used the CWM flash and can confirm the no updated baseband since it still had the stock Rogers one on AT&T-ICS and in CM-10.1. Not sure about ICS but in CM-10.1 I could get voice but no data and haven't tested txt.
Going to flash back to stock with the backup I made for now while I research solutions to a few personal gripes I have with CM-10.1.
And would the UCLJ3 from SamMobile with odin or kies be as effective as the EXE version since I already have it downloaded?
Thanks for helping a total noob and to be honest this is my first Android phone.
Click to expand...
Click to collapse
I just took a peek... ooh. Looks like pretty much everything is in there. You should be good.

cannot flash new AOKP (error 7)!!!!

hi guys,
I have a galaxy s3, in Canada, and cannot flash the newest AOKP (aokp_d2att_ota-eng-task650_7.20.2013b), I downloaded the I747MVLDLK4_aio.tar.md5 file and flashed it with odin as per instructions, then did a format,cache wipe/dalvik wipe, then try and write the new ROM, and all i get is error 7! ive tried it a few times! All i can say is im sure glad i did a NAND backup before i tried.
i dont understand whats wrong? i wasnt sure if i did the bootloader file right, but i followed directions, i put the phone in write mode, opened odin, clicked PDA, chose the file, and it wrote fine.no errors or anything. is there something i maybe missed?
can someone help me out?
TIA,
GINNZ

Maybe check to see if you have the latest recovery installed
Sent from my SGH-I747 using xda premium

ginnz said:
hi guys,
I have a galaxy s3, in Canada, and cannot flash the newest AOKP (aokp_d2att_ota-eng-task650_7.20.2013b), I downloaded the I747MVLDLK4_aio.tar.md5 file and flashed it with odin as per instructions, then did a format,cache wipe/dalvik wipe, then try and write the new ROM, and all i get is error 7! ive tried it a few times! All i can say is im sure glad i did a NAND backup before i tried.
i dont understand whats wrong? i wasnt sure if i did the bootloader file right, but i followed directions, i put the phone in write mode, opened odin, clicked PDA, chose the file, and it wrote fine.no errors or anything. is there something i maybe missed?
can someone help me out?
TIA,
GINNZ
Click to expand...
Click to collapse
If you're in Canada chances are you're running the d2can recovery that the phone wants. You need to flash either the d2att recovery Odin from the twrp website or do a quick search for the latest tarp or cwm flashable zip files.
Status 7 can be
a) out of date bootloader
b) out of date recovery
or for Canadians
c) d2can recovery when the Roms are requiring d2att
Sent from my SGH-I747 using xda app-developers app

KorGuy123 said:
If you're in Canada chances are you're running the d2can recovery that the phone wants. You need to flash either the d2att recovery Odin from the twrp website or do a quick search for the latest tarp or cwm flashable zip files.
Status 7 can be
a) out of date bootloader
b) out of date recovery
or for Canadians
c) d2can recovery when the Roms are requiring d2att
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Ok, thanks, I had an older version of AOKP running, which was released in December or so, and the recovery flashed was "RecoveryGalaxyS3USCanada.tar", I thought the new I747M4LDLK4 file was all i needed to flash this newer rom?
What exactly do i need? Im sorry for so many questions, but this just isnt making sense to me.... I managed to root the phone initially last year, and havn't done anything with it since.
so what is the newer I747M4LDLK4 file that i flashed with Odin for? Is the recovery initially flashed not the right one? if not, which one is needed, and how do i flash it? Id imagine with Odin, if so, do i just flash it the same as the I747M4LDLK4 file (PDA)?
im almost there, i just need a small push in the right direction....
Thanks for all your help so far, and please bare with me. I was an Apple jailbreaker for years, so this stuff is pretty foreign to me still.
---edit---
ok, so i went to twrp and found 2 recovery's, one is "openrecovery-twrp-2.6.0.0-d2att.tar" and one is "openrecovery-twrp-2.6.0.0-d2can.tar", this is where im confused, should i flash the "d2att", or the "d2can"? I mean, im in Canada, on MTS, and flashed the I747M4LDLK4, which was meant for Canada already....
also, can someone please clarify what the I747M4LDLK4 file is? it clearly states that canadian users MUST flash this before flashing the new AOKP, as it wont wont flash without it.... I did that, and still get Error7, now im looking at a new "recovery" as well, as i hope this will fix my error 7 issue. No where in the massive AOKP thread did it say that a different recovery would be needed as well, only the new I747M4LDLK4_aio.tar.md5 file!
so, anyways, if i flash a new recovery, (all i need to know is which one at this point), then i should be able to flash the new (AOKP) rom? i really dont wanna brick this thing, and i wish there wasnt so much confusion with the d2att/d2can files. it would seem completely logical that i would need the d2can file, but who knows, .... there was some sort of error on my phone when i tried to flash the ROM last night and d2att was in it somewhere......
im assuming the I747M4LDLK4_aio.tar.md5 is the bootloader, if so, i have the most recent one flashed now, so i must be getting the error because my recovery is out of date? i think im almost there, all i need is to know which recovery to flash, and i should be golden! the original recovery that is on the phone now from my first AOKP flash is "RecoverygalaxyS3USCanada.tar"
Ginnz.

ginnz said:
Ok, thanks, I had an older version of AOKP running, which was released in December or so, and the recovery flashed was "RecoveryGalaxyS3USCanada.tar", I thought the new I747M4LDLK4 file was all i needed to flash this newer rom?
What exactly do i need? Im sorry for so many questions, but this just isnt making sense to me.... I managed to root the phone initially last year, and havn't done anything with it since.
so what is the newer I747M4LDLK4 file that i flashed with Odin for? Is the recovery initially flashed not the right one? if not, which one is needed, and how do i flash it? Id imagine with Odin, if so, do i just flash it the same as the I747M4LDLK4 file (PDA)?
im almost there, i just need a small push in the right direction....
Thanks for all your help so far, and please bare with me. I was an Apple jailbreaker for years, so this stuff is pretty foreign to me still.
---edit---
ok, so i went to twrp and found 2 recovery's, one is "openrecovery-twrp-2.6.0.0-d2att.tar" and one is "openrecovery-twrp-2.6.0.0-d2can.tar", this is where im confused, should i flash the "d2att", or the "d2can"? I mean, im in Canada, on MTS, and flashed the I747M4LDLK4, which was meant for Canada already....
also, can someone please clarify what the I747M4LDLK4 file is? it clearly states that canadian users MUST flash this before flashing the new AOKP, as it wont wont flash without it.... I did that, and still get Error7, now im looking at a new "recovery" as well, as i hope this will fix my error 7 issue. No where in the massive AOKP thread did it say that a different recovery would be needed as well, only the new I747M4LDLK4_aio.tar.md5 file!
so, anyways, if i flash a new recovery, (all i need to know is which one at this point), then i should be able to flash the new (AOKP) rom? i really dont wanna brick this thing, and i wish there wasnt so much confusion with the d2att/d2can files. it would seem completely logical that i would need the d2can file, but who knows, .... there was some sort of error on my phone when i tried to flash the ROM last night and d2att was in it somewhere......
im assuming the I747M4LDLK4_aio.tar.md5 is the bootloader, if so, i have the most recent one flashed now, so i must be getting the error because my recovery is out of date? i think im almost there, all i need is to know which recovery to flash, and i should be golden! the original recovery that is on the phone now from my first AOKP flash is "RecoverygalaxyS3USCanada.tar"
Ginnz.
Click to expand...
Click to collapse
Okay, first thing first. You are reading WAY TOO MUCH into this, You need to slow down and do some reading on what is what for your phone.
There is no confusion about d2can and d2att in here. Here it is as simple as I can explain.
You live in Canada (as do I) our phones are SGH-I747M when you install a custom recovery (Clockworkmod or TWRP) The phone is registered as a Canadian model. The developers on this forum build ROMS for d2att only. They just happen to work on our phones as they are identical. To be able to flash these ROMS on our Canadian phones you have to flash the d2att recovery (Clockworkmod or TWRP)
So my suggestion was to make sure you have flashed the d2att recovery to your phone. You can get the Odin files from the websites or a quick search here would get you the flashable .zip files you would flash in recovery like a ROM (no wiping needed though)
Anything on THIS FORUM ONLY will not brick your device. Anything labelled under anything outside this forum ie. i9300 (International S3) or the other carriers will cause harm to your phone and you'll be a sad panda.
I747M4LDLK4 is your bootloader.
What Is A Bootloader?
In literal terms, bootloader is code that is executed before any Operating System starts to run. The concept of bootloaders is universal to virtually all Operating systems that inculcates operating systems on your PC, laptop, smartphones, and other such devices. Bootloaders basically package the instructions to boot operating system kernel and most of them also have their own debugging or modification environment. As the bootloader kicks off before any piece of software on your device, it makes it extremely processor specific and every motherboard has it’s own bootloader. This is one reason that all Android phones have different Custom ROMS developed due to high variance of processing hardware present on the device.
Click to expand...
Click to collapse
If you were to flash a US bootloader on your phone you'll be a sad panda.
The newer ROMS are requiring an updated bootloader to work properly. The newest Canadian bootloader MF1 still won't work for most of these ROMS so don't update it that far.
I don't know what else to suggest.
There are 2 main reasons for status 7 (3 if you're on a Canadian carrier which you are)

@KorGuy123
Nice job on the explanations. Many Users (none of which are obviously in this section of course ) would see that he was running a version of Task's ROM from December and jumped all over him. Keep up the good work.
OP ~ KorGuy123's last post points out to what a Status 7 recovery error is. Most of the times Status 7's are mainly due to Recovery issues. Bootloader issues will usually throw a [getprop ro.bootloader] error instead of a Status 7 just for future reference.

KorGuy123 said:
If you're in Canada chances are you're running the d2can recovery that the phone wants. You need to flash either the d2att recovery Odin from the twrp website or do a quick search for the latest tarp or cwm flashable zip files.
Status 7 can be
a) out of date bootloader
b) out of date recovery
or for Canadians
c) d2can recovery when the Roms are requiring d2att
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for bearing with me guys!!! I got it. as was stated, i was overthinking the whole thing! i flashed a new recovery .d2att, and all went fine!
you guys are awesome!
ginnz.

ginnz said:
Thanks for bearing with me guys!!! I got it. as was stated, i was overthinking the whole thing! i flashed a new recovery .d2att, and all went fine!
you guys are awesome!
ginnz.
Click to expand...
Click to collapse
Glad it worked out for you. Enjoy!
Sent from my SGH-I747 using xda app-developers app