Develop Bugs

[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

[Q] CM10.2 MK3 build support?

I want to flash CM10.2 on my rooted 4.3 MK3 s3. Is it possible to flash that rom on the phone although Cm10.2 is android 4.2.2?
Thanks!

WoodenDiamond71 said:
I want to flash CM10.2 on my rooted 4.3 MK3 s3. Is it possible to flash that rom on the phone although Cm10.2 is android 4.2.2?
Thanks!
Click to expand...
Click to collapse
As long as the file you download does not downgrade the boot loader. ROM zips will not do this unless otherwise noted. Flashing tar files through ODIN can brick your phone if you downgrade Android version number because tar files reflash every part of the phone, including bootloader.
sent from my GS3

joeyhdownsouth said:
As long as the file you download does not downgrade the boot loader. ROM zips will not do this unless otherwise noted. Flashing tar files through ODIN can brick your phone if you downgrade Android version number because tar files reflash every part of the phone, including bootloader.
sent from my GS3
Click to expand...
Click to collapse
You're correct about the downgrading the bootloader part since i have learned my lesson the first time, but as far as flashing the rom is concerned my recovery will not flash it and i get the broken android as the background and my recovery says the installation was aborted. I am using philz touch recovery 6 btw.

WoodenDiamond71 said:
You're correct about the downgrading the bootloader part since i have learned my lesson the first time, but as far as flashing the rom is concerned my recovery will not flash it and i get the broken android as the background and my recovery says the installation was aborted. I am using philz touch recovery 6 btw.
Click to expand...
Click to collapse
You should be also getting a status 7 error, because the bootloader you currently have (MK3) is not listed as one of the "approved" bootloaders in the updater-script for any 4.3.x ROM based on AOSP. You will need to go into the updater-script and modify one of the lines to match your bootloader, or get rid of the assert lines altogether. Any KitKat 4.4.x ROM's will have your bootloader listed, so this is not necessary for the newest ROM's.

How would I do that? Is there a tutorial I can follow
Sent from my SPH-L710 using Tapatalk

WoodenDiamond71 said:
How would I do that? Is there a tutorial I can follow
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
http://androidforums.com/virgin-mobile-galaxy-s3-all-things-root/791952-all-in-one-guide-modifying-custom-sprint-roms-virgin-mobile-use.html
This is a tutorial I have put together on Android Forums for the rooted Virgin Mobile community (SGS3), since we have to always modify or delete the asserts in order to get Sprint ROM's to flash on our phones. Principle is the same for any Sprint user in your situation. I also just made a YouTube video showing how to do the relevant parts of my tutorial.
https://www.youtube.com/watch?v=IZnYSrUIXKM
Hope this helps! Feel free to PM me if need be for any clarification.

Sweet!! Thanks I'll check it out later once I get out of work. Thanks once again I'll pm if it worked
Sent from my SPH-L710 using Tapatalk

CWM flashable bootloader safety concern.

CWM flashable bootloader safety concern.
I have recently seen users here flashing bootloader with CWM, here is my just head up for safety concern of CWM flashble bootloader
Here is link to post by well known X-Note ROM developer @soloilmeglio regarding forcing bootloader with CWM
http://forum.xda-developers.com/showthread.php?t=2609561
even chances are less than a 1% it will be huge for terms of breaking device. We rarely rare seen any reported brick device by bad method of flashing on XDA.
Irrespective of this another concern is MD5 check. I strongly recommend to flash bootloader with MD5 check only. Once on CWM flashable format hardly any newbies doing md5 check before every flashing (even Philz have included built in). Any corrupted bootloader download flashing will high possibly end with brick. Bootloader best to be flashed with Odin with tar.md5 format so any corrupt download will auto fail bootloader flashig even one have not checked it.
Hope this will be enough to understand
Regards
PS : Anyone requires safe ND3 Kitkat bootloader with tar.md5 it is here.-flash using Odin for bootloader tab.

dr.ketan said:
CWM flashable bootloader safety concern.
I have recently seen users here flashing bootloader with CWM, here is my just head up for safety concern of CWM flashble bootloader
Here is link to post by well known X-Note ROM developer @soloilmeglio regarding forcing bootloader with CWM
http://forum.xda-developers.com/showthread.php?t=2609561
even chances are less than a 1% it will be huge for terms of breaking device. We rarely rare seen any reported brick device by bad method of flashing on XDA.
Irrespective of this another concern is MD5 check. I strongly recommend to flash bootloader with MD5 check only. Once on CWM flashable format hardly any newbies doing md5 check before every flashing (even Philz have included built in). Any corrupted bootloader download flashing will high possibly end with brick. Bootloader best to be flashed with Odin with tar.md5 format so any corrupt download will auto fail bootloader flashig even one have not checked it.
Hope this will be enough to understand
Regards
PS : Anyone requires safe ND3 Kitkat bootloader with tar.md5 it is here.
Click to expand...
Click to collapse
Good Info today morning i've flashed with TWRP but went on successful I am happy it did not Brick, But here on in Future will keep this in mind, Any possibilities now that the device is working fine are there any chances of bricking in future.

If bootloader is flashable through cwm zip then its possible to flash it via a full custom rom zip too then ? logical ?
theres a dev in Note 2 community who included the bootloader in his 4.3 rom ...i make sure I look at the skeleton of the zip after downloading. i never went to his thread again.
at that time everyone said bootloader doesnt get flashed through cwm. but whatever the case all devs have a moral responsibility to inform from before in changelog or instructions if bootloader is included in his rom zip whether it gets flashed or not. It should not be done surreptiously.
anyway good post, important discussions, should be made sticky :good:

Thank you DR.KETAN for this very important advice.
I have flashed by odin but about to flash by CWM last night.

Who have successfully flashed have nothing to worry or nothing needs to do now.
If it includes in cwm plain or including rom risk remains same.
I can even make simple utility with which you can flash bootloader with simple application on device by just keeping bootloader file on SD card. But I will never do that.
Sent from my SM-N900 using xda premium

dr.ketan said:
Who have successfully flashed have nothing to worry or nothing needs to do now.
If it includes in cwm plain or including rom risk remains same.
I can even make simple utility with which you can flash bootloader with simple application on device by just keeping bootloader file on SD card. But I will never do that.
Sent from my SM-N900 using xda premium
Click to expand...
Click to collapse
So bootloader= odin. End of story

Bootloader.tar.md5 = odin.
Sent from my SM-N900 using xda premium

dr.ketan said:
Bootloader.tar.md5 = odin.
Sent from my SM-N900 using xda premium
Click to expand...
Click to collapse
You mean to say that if we flash it through CWM or through any simple utility like you mentioned then there are chances of the bootloader going to the wrong partitions? Is that what you are trying to say?
I am thinking is there any way to find out which is the correct partition for the bootloader then?
Sent From My New Galaxy S5 GT-N7100

dr.ketan said:
Bootloader.tar.md5 = odin.
Sent from my SM-N900 using xda premium
Click to expand...
Click to collapse
Hi Doc this bootloader.tar.md5 file should be put in which option in Odin?
PDA
Phone
Bootloader
I think its the bootloader but want to be 100% sure.:laugh:

Bootloader will flash to partition on which cwm script have mentioned. But look thread in op where partition was defined correctly even though it was bricked also we don't have complete mechanism and information about knox stuff and how Samsung have managed it.
When you flash with odin Samsung have already coded file where and how to flash and it will go correctly. Another big issue is cwm itself can't stop flashing if file is corrupted. Only concern here is bootloader, if you flashed corrupted recovery /modem/kernel chances of brick is almost nil and your device can be survived by correcting it. But when you flash wrong bootloader /corrupt bootloader there may not have any combo key working so you will be helpless. It may or may not rescued by jtag box.
So always wise decision is use only tar.md5 format with odin to make safest land.
Just remember if anything most dangerous in terms of flashing it's bootloader.
Sent from my SM-N900 using xda premium

palace35mm said:
Hi Doc this bootloader.tar.md5 file should be put in which option in Odin?
PDA
Phone
Bootloader
I think its the bootloader but want to be 100% sure.:laugh:
Click to expand...
Click to collapse
Bootloader or pda any.
I recommend bootloader.
Sent from my SM-N900 using xda premium

dr.ketan said:
Bootloader will flash to partition on which cwm script have mentioned. But look thread in op where partition was defined correctly even though it was bricked also we don't have complete mechanism and information about knox stuff and how Samsung have managed it.
When you flash with odin Samsung have already coded file where and how to flash and it will go correctly. Another big issue is cwm itself can't stop flashing if file is corrupted. Only concern here is bootloader, if you flashed corrupted recovery /modem/kernel chances of brick is almost nil and your device can be survived by correcting it. But when you flash wrong bootloader /corrupt bootloader there may not have any combo key working so you will be helpless. It may or may not rescued by jtag box.
So always wise decision is use only tar.md5 format with odin to make safest land.
Just remember if anything most dangerous in terms of flashing it's bootloader.
Sent from my SM-N900 using xda premium
Click to expand...
Click to collapse
Yeah that is the most important thing of all.
And it's better to be safe with the bootloader. I don't think we have a hard unbrick method like the note 3 through sdcard.
So it's better to be safe [emoji106]
Sent From My New Galaxy S5 GT-N7100

dr.ketan said:
CWM flashable bootloader safety concern.
I have recently seen users here flashing bootloader with CWM, here is my just head up for safety concern of CWM flashble bootloader
Here is link to post by well known X-Note ROM developer @soloilmeglio regarding forcing bootloader with CWM
http://forum.xda-developers.com/showthread.php?t=2609561
even chances are less than a 1% it will be huge for terms of breaking device. We rarely rare seen any reported brick device by bad method of flashing on XDA.
Irrespective of this another concern is MD5 check. I strongly recommend to flash bootloader with MD5 check only. Once on CWM flashable format hardly any newbies doing md5 check before every flashing (even Philz have included built in). Any corrupted bootloader download flashing will high possibly end with brick. Bootloader best to be flashed with Odin with tar.md5 format so any corrupt download will auto fail bootloader flashig even one have not checked it.
Hope this will be enough to understand
Regards
PS : Anyone requires safe ND3 Kitkat bootloader with tar.md5 it is here.-flash using Odin for bootloader tab.
Click to expand...
Click to collapse
I repeat--many thanks for the warning---I will take notice--might even re-flash with ODIN--since you say that the original zip was not correct?

dr.ketan said:
CWM flashable bootloader safety concern.
PS : Anyone requires safe ND3 Kitkat bootloader with tar.md5 it is here.
Click to expand...
Click to collapse
Thanks @dr.ketan for all your wonderful works, insight and knowledge:thumbup:
My concern is can we flash the above bootloader on DN3 rc2 rom provided by the great E-team?
Sent from my GT-N7100 using XDA Premium 4 mobile app

Bootloader is not rom dependent. You can flash on any kitkat based ROM.
Sent from my SM-N900 using xda premium

haybill said:
I repeat--many thanks for the warning---I will take notice--might even re-flash with ODIN--since you say that the original zip was not correct?
Click to expand...
Click to collapse
No you need not to Reflash if your bootloader information is correct.
I didn't get you about original zip. Can you point me exactly?
Sent from my SM-N900 using xda premium

Can we change bootloader frequently ?
Like I am on kitkat now then go to jellybean MJ5 then again kitkat ? No issue?

justkiddinghere said:
Can we change bootloader frequently ?
Like I am on kitkat now then go to jellybean MJ5 then again kitkat ? No issue?
Click to expand...
Click to collapse
No you can't downgrade your bootloader because of Knox security implemented
Sent From My New Galaxy S5 GT-N7100
---------- Post added at 11:24 AM ---------- Previous post was at 11:20 AM ----------
@dr.ketan
I was just wondering if we could remove the Knox security or Knox part of the code from the bootloader files I mean sboot.bin,param.bin and tz.img so that we can get a Knox free kitkat bootloader. I know that won't work for people who already flashed MK4 and later. But it would really be helpful for people on MJ5 as they can retain warranty and be Knox free.
Is this possible?
Sent From My New Galaxy S5 GT-N7100

i vote for no tinkering with official BL....for personal experiments fine but for community...no
ive come across many expert users who havent been able to use their wifi even with mj5 bl or later, reverting to stock hasnt helped either.

justkiddinghere said:
Can we change bootloader frequently ?
Like I am on kitkat now then go to jellybean MJ5 then again kitkat ? No issue?
Click to expand...
Click to collapse
No.
Probably this one is last for Note2, you may not need to flash bootloader in future. (I don't think Note2 will get 5.0 ever)
but No it's requires only when there is major OS change and once you have 4.3 OR 4.4 bootloader, you can't downgrade but still can use 4.3 by flashin ROM with CWM OR Odin without having bootloader in it.
smeet.somaiya said:
@dr.ketan
I was just wondering if we could remove the Knox security or Knox part of the code from the bootloader files I mean sboot.bin,param.bin and tz.img so that we can get a Knox free kitkat bootloader. I know that won't work for people who already flashed MK4 and later. But it would really be helpful for people on MJ5 as they can retain warranty and be Knox free.
Is this possible?
Sent From My New Galaxy S5 GT-N7100
Click to expand...
Click to collapse
I am too small to do it.

[Q] SGH-I747 Update Issues to 4.4.2

I'm trying to help out a friend and update his Galaxy S3 SGH-I747. He originally had cyanogenmod installed but he restored his phone back to stock and flashed a stock recovery back to the phone. When he tries to do an OTA updated it downloads but fails to install? His current android version is 4.1.1 but his baseband is I747UCUFNE4 which if im not mistaken is for android 4.4.2 what would be the easiest way to get his phone updated to the stock 4.4.2 software?

Follow one of enewman17's how to update threads in General.

4.4.2 upgrade stops at 28%
DocHoliday77 said:
Follow one of enewman17's how to update threads in General.
Click to expand...
Click to collapse
Can you be a bit more specific?
Thanks

bmoliver said:
Can you be a bit more specific?
Thanks
Click to expand...
Click to collapse
The beauty of search: http://forum.xda-developers.com/search.php?searchid=292146343
Two threads from enewman17: UCUEMJB to UCUFNE4 firmware update; How to update SGH-I747 to UCUFNE4_4.4.2

DocHoliday77 said:
Follow one of enewman17's how to update threads in General.
Click to expand...
Click to collapse
BWolf56 said:
The beauty of search: http://forum.xda-developers.com/search.php?searchid=292146343
Two threads from enewman17: UCUEMJB to UCUFNE4 firmware update; How to update SGH-I747 to UCUFNE4_4.4.2
Click to expand...
Click to collapse
Thanks, I had found the last link (....2789917) by doing a Google search (i.e., searching within the forum was less successful).

Hey bmoliver and BWolf56,
I am in the same boat as your friend where my baseband (bootloader) version is I747UCUFNE4 but the software version is stuck at 4.1.1. AT&T is identifying a OTA update, downloading but the update is failing.
I tried the method described in http://forum.xda-developers.com/showthread.php?t=2789917. But when I am trying to flash MJB bootloader, it is failing. I read elsewhere in this forum that downgrading from UCU to MJB is not really advisable.
I am stuck in 4.1.1 and my phone is half functional at the moment with the camera, nfc, bluetooth not functional :crying:.
Was your friend able to get this resolved bmoliver?
I tried searching for a I747UCUFNE4 md5 file that I can flash using odin (just a hope that it might work) but could not find.
It would be great if one of you can point me to it.
PS: I am a complete newbie to this entire thing and so far from what I read, my phone is probably soft-bricked and am hoping that someone would guide and help me get out of this.
EDIT: One more thing that I observed is when I am trying flash something in the download mode, I get the error and "sw rev check fail fused 3 binary 0" and it fails
Thanks,
CJ
bmoliver said:
Thanks, I had found the last link (....2789917) by doing a Google search (i.e., searching within the forum was less successful).
Click to expand...
Click to collapse

jchennuri said:
Hey bmoliver and BWolf56,
I am in the same boat as your friend where my baseband (bootloader) version is I747UCUFNE4 but the software version is stuck at 4.1.1. AT&T is identifying a OTA update, downloading but the update is failing.
I tried the method described in http://forum.xda-developers.com/showthread.php?t=2789917. But when I am trying to flash MJB bootloader, it is failing. I read elsewhere in this forum that downgrading from UCU to MJB is not really advisable.
I am stuck in 4.1.1 and my phone is half functional at the moment with the camera, nfc, bluetooth not functional :crying:.
Was your friend able to get this resolved bmoliver?
I tried searching for a I747UCUFNE4 md5 file that I can flash using odin (just a hope that it might work) but could not find.
It would be great if one of you can point me to it.
PS: I am a complete newbie to this entire thing and so far from what I read, my phone is probably soft-bricked and am hoping that someone would guide and help me get out of this.
Thanks,
CJ
Click to expand...
Click to collapse
You don't want to downgrade bootloaders, that will brick your phone.
You'll have to flash NE4 with Odin (or a NE4 custom ROM through custom recovery) to get your baseband and software matching.
The thread you linked should work if you follow it to a T. If something doesn't work, let us know and be specific about what happened.

Thanks for the info BWolf56,
Sorry for asking a trivial question (just getting accustomed to the lingo used here) .
When you say I should follow it to a T, are you just referring to follow all the steps.
I tried two things
1. follow each step, but failed at step 3 since I was trying to downgrade my bootloader.
2. I jumped from step 2 to step 6 and tried to flash 4.4.2OTA.zip in recovery mode but that also failed. I dont remember the exact error I got, I can try it again to give you more details if you think it is safe.
Thanks
BWolf56 said:
You don't want to downgrade bootloaders, that will brick your phone.
You'll have to flash NE4 with Odin (or a NE4 custom ROM through custom recovery) to get your baseband and software matching.
The thread you linked should work if you follow it to a T. If something doesn't work, let us know and be specific about what happened.
Click to expand...
Click to collapse

jchennuri said:
Thanks for the info BWolf56,
Sorry for asking a trivial question (just getting accustomed to the lingo used here) .
When you say I should follow it to a T, are you just referring to follow all the steps.
I tried two things
1. follow each step, but failed at step 3 since I was trying to downgrade my bootloader.
2. I jumped from step 2 to step 6 and tried to flash 4.4.2OTA.zip in recovery mode but that also failed. I dont remember the exact error I got, I can try it again to give you more details if you think it is safe.
Thanks
Click to expand...
Click to collapse
If you jumped to #6, you didn't flash a custom recovery, which you need to flash the OTA.

I did install TWRP 2.6.3.1 which I am guessing is the custom recovery (as part of step 2) and then I tried to flash the OTA. Am I missing something here?
BWolf56 said:
If you jumped to #6, you didn't flash a custom recovery, which you need to flash the OTA.
Click to expand...
Click to collapse

jchennuri said:
I did install TWRP 2.6.3.1 which I am guessing is the custom recovery (as part of step 2) and then I tried to flash the OTA. Am I missing something here?
Click to expand...
Click to collapse
What error did you get when flashing it?

I just tried flashing it again and got the following error.
I loaded the zip into my internal SD and went to recovery mode (twrp gui, Power+Home+Volume Up)
and tried installing the zip
_______________
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of samsung/d2u (the screen does not allowing me to scroll to the right to look at the complete line after 'd2u')
E: Error executing updater binary in zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Error flashing zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Updating partition details...
FAILED
_________________
This is the error I am getting.
Am I missing something? Please let me know if you need any more info
Thanks a ton!!!
BWolf56 said:
What error did you get when flashing it?
Click to expand...
Click to collapse

jchennuri said:
I just tried flashing it again and got the following error.
I loaded the zip into my internal SD and went to recovery mode (twrp gui, Power+Home+Volume Up)
and tried installing the zip
_______________
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of samsung/d2u (the screen does not allowing me to scroll to the right to look at the complete line after 'd2u')
E: Error executing updater binary in zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Error flashing zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Updating partition details...
FAILED
_________________
This is the error I am getting.
Am I missing something? Please let me know if you need any more info
Thanks a ton!!!
Click to expand...
Click to collapse
Sounds like you'll have to use Odin to flash Stock.
Your build.prop is most likely borked (or has been changed to something it's not). d2u is not a variant of the S3, nor does it exist.

Thanks a ton for helping me identify the problem.
I just have to look if a stock file to flash using odin is out there somewhere.
I will post in http://forum.xda-developers.com/showthread.php?t=2789917 to see if enewman17 or someone from the community have a tar or md5 file that I can use.
I will try that and update on how it goes.
BWolf56 said:
Sounds like you'll have to use Odin to flash Stock.
Your build.prop is most likely borked (or has been changed to something it's not). d2u is not a variant of the S3, nor does it exist.
Click to expand...
Click to collapse

jchennuri said:
Thanks a ton for helping me identify the problem.
I just have to look if a stock file to flash using odin is out there somewhere.
I will post in http://forum.xda-developers.com/showthread.php?t=2789917 to see if enewman17 or someone from the community have a tar or md5 file that I can use.
I will try that and update on how it goes.
Click to expand...
Click to collapse
You can grab the stock ROM here: http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
Just make sure you grab the right version.

Thanks for the pointing me there.
I could not find the stock firmware for NE4 though.
They only have MJ2, LK3, LG1, LEM versions, no MJB either.
BWolf56 said:
You can grab the stock ROM here: http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
Just make sure you grab the right version.
Click to expand...
Click to collapse

jchennuri said:
Thanks for the pointing me there.
I could not find the stock firmware for NE4 though.
They only have MJ2, LK3, LG1, LEM versions, no MJB either.
Click to expand...
Click to collapse
There isn't a NE4 stock for Odin. I just noticed the post hasn't been updated in a while.
I though I could find it on Sammobile.com but they have LK3 as their latest too.

Since you somehow have the 4.4.2 modem, you can not flash anything older than the 4.4.2 firmware. Currently there is nothing that you can flash to fix this. Normally, I would say to flash an older modem, but if Odin is seeing it as already updated to 4.4.2 (SWREV 3), and the only thing you have that is 4.4.2 is the modem, flashing anything older will likely hard brick.
You need either the full stock firmware, which there is not one, Thanks AT&T!, or a recovery flashable firmware for 4.4.2. Enewman17 has this, but it will not work for you because of how the modem is flashed. For some reason, he has it patching the 4.3 modem rather than including the full updated one like with the other partitions. If someone makes the same thing, but with the already updated modem, you could probably flash that. No guarantees though. Running 4.1.1 firmware/bootloaders with a 4.4.2 modem is a scenario which is highly unpredictable, so anything you try to flash might cause more problems, we just don't know.
I've PM'd enewman17 to ask if there was a specific reason he updated the modem the way he did. If there is not an issue doing it like i mentioned someone can try to make a new package like that for you to try.

Thanks Doc!
Hopefully enewman17 can come up with a solution for this.
Just an information which I was not able to completely comprehend but maybe pros like you or Bwolf56 will be able to.
I opened Kies and this is what it says.
Firmware information
This is the latest firmware.
Current firmware version: PDA:LK3 / PHONE:NE4 / CSC:LK3 (ATT)
Any thoughts on how do I get the PDA and CSC updated (not even sure what exactly they are)
Thanks
DocHoliday77 said:
Since you somehow have the 4.4.2 modem, you can not flash anything older than the 4.4.2 firmware. Currently there is nothing that you can flash to fix this. Normally, I would say to flash an older modem, but if Odin is seeing it as already updated to 4.4.2 (SWREV 3), and the only thing you have that is 4.4.2 is the modem, flashing anything older will likely hard brick.
You need either the full stock firmware, which there is not one, Thanks AT&T!, or a recovery flashable firmware for 4.4.2. Enewman17 has this, but it will not work for you because of how the modem is flashed. For some reason, he has it patching the 4.3 modem rather than including the full updated one like with the other partitions. If someone makes the same thing, but with the already updated modem, you could probably flash that. No guarantees though. Running 4.1.1 firmware/bootloaders with a 4.4.2 modem is a scenario which is highly unpredictable, so anything you try to flash might cause more problems, we just don't know.
I've PM'd enewman17 to ask if there was a specific reason he updated the modem the way he did. If there is not an issue doing it like i mentioned someone can try to make a new package like that for you to try.
Click to expand...
Click to collapse

Ok, enewman17 just put this together if you want to try it. This includes the full NE4 stock firmware minus system, kernel, cache and recovery.
So flashing it will preserve your current Rom, kernel and recovery, but will otherwise fully update your base firmware/bootloaders to NE4.
This should be perfectly safe to use, but seeing as it is untested, I cannot make any guarantees that it won't make things worse. (I wouldn't post it if I thought it would, but there is always the possibility)
Flash from custom recovery such as TWRP.
http://www.androidfilehost.com/?fid=23578570567716667
Sent from my SGH-T999 using Tapatalk
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
If you want to fully update your system (rom) to stock NE4, enewman17 has a thread in the development section with stock rooms you can flash via recovery after you update your firmware posted above.
Sent from my SGH-T999 using Tapatalk