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
Related
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.
]So I was stuck in a hard place and needed a recovery fix and couldn't find one... I stumbled across an .Img file so u converted it to a .tar file and shall share in hopes that people who make the mistake as I did don't have to go the the grueling process of flashing all the way back to mk2 and lose everything that they currently had and starting over
Download = https://www.dropbox.com/s/mx1933wuc...short route to recover from such a situation.
Cool!
Sent from my iPhone using Tapatalk
Maybe this is very commendable, but maybe not. What phone do you have? What rom did you have to begin with? What firmware was this image file made from? Basically, you need to be much more specific if you're actually trying to help some other people.
Yrs,
dkephart
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Can you Be more Specific
Which recovery is this . I downloaded it and the file is only 10.5kb . Its a really small file .. also my bootloader is locked so if i flash this in odin . I most likely will get a fail or a paper weight ...
spirodave said:
Which recovery is this . I downloaded it and the file is only 10.5kb . Its a really small file .. also my bootloader is locked so if i flash this in odin . I most likely will get a fail or a paper weight ...
Click to expand...
Click to collapse
i had boot fail odin flashed it and it booted; so im sharing.
dkephart said:
Maybe this is very commendable, but maybe not. What phone do you have? What rom did you have to begin with? What firmware was this image file made from? Basically, you need to be much more specific if you're actually trying to help some other people.
Yrs,
dkephart
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
This is for the White AT&T Branded S4, i found the img file, converted it for .tar; i believe its the MK2 version, i was locked out of phone because of trying to flash a custom recovery because im experimentive; i flashed this and my phone booted back and i didnt lose anything...
Im personally running a rooted NC1 4.4.2 rom using Safestrap since the bootloader is locked.;;
s0xpan said:
This is for the White AT&T Branded S4, i found the img file, converted it for .tar; i believe its the MK2 version, i was locked out of phone because of trying to flash a custom recovery because im experimentive; i flashed this and my phone booted back and i didnt lose anything...
Im personally running a rooted NC1 4.4.2 rom using Safestrap since the bootloader is locked.;;
Click to expand...
Click to collapse
.. pLEASE VERIFY WHICH VERSION THIS IS . ? YOU SAID IT MIGHT BE MK2 . CAN YOU FIND OUT FOR SURE
Im pretty sure this is in the wrong thread .. this should be in Q/A help and troubleshooting.. Be prepared for a bunch of PMS 'ers
spirodave said:
.. No one will be able to use this file because it isnt labeled in the title .. SO MY ? IS ..WHAT IS THIS FILE PLEASE TITLE IT ..? SORRY MY CAPS LOCK IS STUCK ON MY COMPUTER..
I GUESS IT WOULD BE USEFUL FOR SOMETHING ..BUT NO ONE WILL KNOW WHAT IT IS UNLESS YOU TELL US ..YOU SAID YOU THINK IT MIGHT BE MK2 ???? WHY WOULD I FLASH SOMETHING THAT I DONT EVEN KNOW WHAT IT IS AND WHATS WORSE IS YOU DONT EVEN KNOW FOR SURE ..ITS A GOOD WAY TO BRICK SOMEONES BABY..DONT TAKE THIS THE WRONG WAY EITHER. I APPRECIATE ANY TOOLS I CAN PUT IN MY BOX ..THIS COULD BEA NICE THING TO HAVE ..
Click to expand...
Click to collapse
it's simply the mk2 stock recovery img; incase you tried to custom flash a recovery (which has been proven to fail) and the bootloader kicks you out (non-safestrap recovery like actual recovery recovery)
...i apologize for not being more specific.
i was in a jam at work when i tried to flash custom clockworkmod recovery to my main recovery via safestrap and got bootlooped due to our locked bootloader. I found the recovery.img file under some thread and i formatted it to work with odin; flashed it to my device an SGH-i337 and it allowed me to boot back up normally. so for me it was a safe haven, and im just trying to help others who tend to experiment even when told not to.
s0xpan said:
it's simply the mk2 stock recovery img; incase you tried to custom flash a recovery (which has been proven to fail) and the bootloader kicks you out (non-safestrap recovery like actual recovery recovery)
...i apologize for not being more specific.
i was in a jam at work when i tried to flash custom clockworkmod recovery to my main recovery via safestrap and got bootlooped due to our locked bootloader. I found the recovery.img file under some thread and i formatted it to work with odin; flashed it to my device an SGH-i337 and it allowed me to boot back up normally. so for me it was a safe haven, and im just trying to help others who tend to experiment even when told not to.
Click to expand...
Click to collapse
Right on ...Thanks man .. Yeah this will help .. I had it happen when falshing a rom and i lost safestrap and was stuck in a boot loop ..So this would be very helpful in that case ..I wish this would be for NB1 or NC1 ..Especially since there is a root method for 4.4 usinf towelroot
Hey all, I need some help. I bricked my phone, and I can only get into download mode and recovery. Flashing through odin fails each time, and so does flashing through recovery. Gives me a status 7 error. Ive made sure I'm downloading all the proper files, but Im stumped here. My phone also isnt recognized in Kies. Ive uninstalled and reinstalled the drivers multiple times now. Im too nervous to go to an AT&T store because theyll see I voided my warranty from the recovery (using philz recovery).
Anyone got any clue on what Im doing wrong? Any help would be much appreciated.
Syst3m Deadlock said:
Hey all, I need some help. I bricked my phone, and I can only get into download mode and recovery. Flashing through odin fails each time, and so does flashing through recovery. Gives me a status 7 error. Ive made sure I'm downloading all the proper files, but Im stumped here. My phone also isnt recognized in Kies. Ive uninstalled and reinstalled the drivers multiple times now. Im too nervous to go to an AT&T store because theyll see I voided my warranty from the recovery (using philz recovery).
Anyone got any clue on what Im doing wrong? Any help would be much appreciated.
Click to expand...
Click to collapse
EDIT: In your sig, it says you have an S2? this is the S3 section.
What happened exactly to soft-brick?
The software you're flashing with Odin might not be good, try another one. Also, since you can get in recovery, you can try clean flashing the ROM you had running previous to the brick.
BWolf56 said:
EDIT: In your sig, it says you have an S2? this is the S3 section.
What happened exactly to soft-brick?
The software you're flashing with Odin might not be good, try another one. Also, since you can get in recovery, you can try clean flashing the ROM you had running previous to the brick.
Click to expand...
Click to collapse
I have an S3 now, just havent updated my sig.
And I was trying to root. I was on the latest stock 4.4.2 and flashed the wrong file by mistake. Forgot what it was. So now I cant flash any files in recovery or odin. It just fails each and every time. I know all these files cant be bad
So root wasnt successful and now I cant even revert back to stock
Kies interferes with odin. Uninstall it from your computer and try odin again.
DocHoliday77 said:
Kies interferes with odin. Uninstall it from your computer and try odin again.
Click to expand...
Click to collapse
Still didnt work. Odin let me install a recovery file, but it just wont let me install files to restore back to stock. Same with recovery, I'm still getting the status 7 error. It doesnt make any sense. Ive downloaded and redownloaded from different places, so I highly doubt that all these files are bad
Are you running the latest Philz? Sometimes, the status 7 error occurs with an outdated recovery. Have you tried flashing a custom ROM with TWRP?
audit13 said:
Are you running the latest Philz? Sometimes, the status 7 error occurs with an outdated recovery. Have you tried flashing a custom ROM with TWRP?
Click to expand...
Click to collapse
I'm running 6.0.5 - no I haven't tried TWRP
What rom were you running before? What do you want to be running now?
And what is your current firmware/bootloader version? Not sure about philz recovery, but status 7 errors usually occur when you dont have the required firmware build.
Also, at least for the T999, cm roms updater-scripts are outdated. So if we have the newest available, it still gives the status 7 errors because the new builds haven't been added. Just thought I'd mention this in case you're updated to the new kk firmware and are trying to flash a cm rom.
DocHoliday77 said:
What rom were you running before? What do you want to be running now?
And what is your current firmware/bootloader version? Not sure about philz recovery, but status 7 errors usually occur when you dont have the required firmware build.
Also, at least for the T999, cm roms updater-scripts are outdated. So if we have the newest available, it still gives the status 7 errors because the new builds haven't been added. Just thought I'd mention this in case you're updated to the new kk firmware and are trying to flash a cm rom.
Click to expand...
Click to collapse
I was running official 4.4 unrooted. I'm trying to install Likewise S5.
Install terminal emulator from the play store and enter this:
getprop ro.bootloader
If it returns I747UCUEMJB you should be ok to flash likewise and something else is preventing it. If its anyway but that, you probably need to update your base firmware/bootloaders first.
If you're still unable to boot anything, the build should be shown on the Download Mode screen. You can probably reflash your previous rom and boot to that for right now though.
I was able to get a custom ROM installed, but now I have no reception. Im guessing the bootloader needs to be updated. So I tried updating it via odin. That failed. I also tried flashing it in recovery and still got a status 7 error. Im at my whits end here
You probably need to flash your modem. Run the Terminal Emulator command I posted before, and if it returns I747UCUEMJB, flash the MJB modem. If it returns anything else, flash the modem that matches, but let us know first just to be on the safe side.
DocHoliday77 said:
You probably need to flash your modem. Run the Terminal Emulator command I posted before, and if it returns I747UCUEMJB, flash the MJB modem. If it returns anything else, flash the modem that matches, but let us know first just to be on the safe side.
Click to expand...
Click to collapse
Terminal Emulator tells me my bootloader is 1747UCUFNE4
Syst3m Deadlock said:
Terminal Emulator tells me my bootloader is 1747UCUFNE4
Click to expand...
Click to collapse
So yeah, you need the 1747UCUFNE4 baseband. Look in Settings/About Phone to know which one you have before going and flashing it.
BWolf56 said:
So yeah, you need the 1747UCUFNE4 baseband. Look in Settings/About Phone to know which one you have before going and flashing it.
Click to expand...
Click to collapse
I cant seem to find the 1747UCUFNE4 baseband,
Syst3m Deadlock said:
I cant seem to find the 1747UCUFNE4 baseband,
Click to expand...
Click to collapse
Did you check which one you have atm?
And here, from Doc http://forum.xda-developers.com/showpost.php?p=53626873&postcount=4
BWolf56 said:
Did you check which one you have atm?
And here, from Doc http://forum.xda-developers.com/showpost.php?p=53626873&postcount=4
Click to expand...
Click to collapse
Thanks a bunch, it worked!!!
Links removed while investigating the cause of a couple of bricks. Sorry, but don't want to have any more of these happen!
I747 and I747M 4.4.2 Firmware
NE4 / NE6 / NF2 / NH2
For use with TWRP, CWM or Philz Recoveries
The following packages will flash the base 4.4.2 firmware to your device. This can be used to update to the latest build, or in the event that you need to reflash it for whatever reason. The following partitions will be flashed:
aboot - AP Bootloader
NON-HLOS - Modem/Baseband
rpm - Resource and Power Management
sbl2 - Secondary Bootloader 2
sbl3 - Secondary Bootloader 3
tz - Trust Zone
This will NOT flash the system, cache, recovery or boot (kernel) partitions, so it will preserve your current Rom, Recovery and Kernel. There is no requirement that you be on a certain build prior to flashing this, though I will not make any guarantees you will not encounter some issues if making a large jump in versions, such as going from 4.0.4 or 4.1.1 straight to 4.4.2. It should be fine, but I'm just not making any promises.
General Disclaimer
As with everything you use here on XDA, you use this at your own risk. I would not release this if I felt it were unsafe, but things do go wrong, even with fully tested and vetted projects.
How It Works
Flash in the custom recovery of your choice. (Initially tested on TWRP 2.8.0.1)
Once the flash is initiated, it will run the "assert" checks we should all be getting used to by now. This is to prevent downgrading and bricking your device!
Next, each of the firmware files are checked for any corruption using the sha1 checksum. If it fails any of these checks the flash will abort without actually flashing anything.
After passing these checks, the flashing begins! The modem is flashed last! This is in case anything goes wrong, there is no way to end up with a 4.4.2 modem on 4.3 bootloaders!
Once complete, reboot and you are done!
I747M Unified Packages"One Package To Rule Them All!"
You may notice that each I747M build is for each of its relevant carriers, rather than having individual packages for every build, every carrier. While rebuilding these packages, I noticed that they are identical regardless of the carrier. For example, the base firmware in Bell's NE6 is identical to Koodoo's, Sasktel's and Telus'. The same is true for both NF2 and NH2! So we only need one flashable zip for each version! In other words... One Package To Rule Them All!!
REMEMBER!!!Once you update, there is no going back! You cannot flash older firmware, so once you flash to 4.4.2, that is the only firmware you can flash from now on!
DOWNLOADS
I747
UCUFNE4 - AT&T
I747M
VLUFNE6 - Bell, Koodoo, Telus
VLUFNF2 - Fido, Rogers
VLUFNH2 - Bell, Koodoo, Telus
I hope these prove useful for some of you! Good Luck!
Thanks to:
@Aerowinder - for his script I borrowed from a similar project for the T999 and helping fix some issues!
@enewman17 - for everything he does around here, and helping me to solve some problems along the way!
@mnasledov - for doing this the first time for the T999
everyone - for their patience while I got this working!
Reserved
never before, so here goes...
1st.
thank you doc
will ride this huckleberry-special from Fort Dodge to the end of the line. (still on mj2). had just downloaded the S3Rx from @enewman17
err on the side of kindness
Cool! Let me know how it goes!
flashed on my brothers S3 i747(my old S3). flawless.
:good:
err on the side of kindness
Right on! Thank you for trying it out and reporting back! Very much appreciated!
Corrupt
Been flashing the Koodo one and all I get is a corrupt error...
Did you check the md5 on the download?
If that matches up and youre still having issues copy the recovery log to sd and then attach it to your post.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
Did you check the md5 on the download?
If that matches up and youre still having issues copy the recovery log to sd and then attach it to your post.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
DLed multiple times, checked the Md5 on my PC and the phone. Can't get the log as a file, this device has been hell. Koodo is an awful company, I've gotten two phones from them and they've both had countless hardware issues and incompatibilities with otherwise standard files, I don't know if they pay discount for Samsung's dropped merchandise or what. TWRP doesn't work at all, only CWM, when I boot TWRP it just can't find any storage medium whatsoever.
Anyway, all it says when I show it is that it verifies the checksum, finds corruption,and aborts. There's a bit below it as well, copied everything meaningful:
minzip: extracted "/tmp/sb12.mbn",
minzip: extracted "/tmp/sb13.mbn",
minzip: extracted "/tmp/tz.mbn"
verifying checksums...
FILE CORRUPTION DETECTED!!! Script result was [7]
aborting
cleaning up
Ok, ill double check it shortly. I know in twrp's advanced menu there is an option to copy log to sd. Are you sure cwm doesnt have the same? Id be surprised if it didnt.
Sorry for the trouble though. It is possible i made a simple mistake somewhere. If so i will find and fix it.
Everything checks out so far on my end. Im downloading the firmware again in case something went wrong there.
In the meantime, what recovery are you using? Maybe try using a different one ir a different version?
Ok, ive checked everything on the Koodoo firmware and i couldnt find anything wrong. Picked it apart twice, re-downloaded the original firmware and checked that nothing was corrupt. Other than the recovery, i cant think of any other reason itd be failing like that.
Might be best for you to flash the full firmware with odin if using a different recovery doesnt work.
mrrocketdog said:
flashed on my brothers S3 i747(my old S3). flawless.
:good:
err on the side of kindness
Click to expand...
Click to collapse
What recovery did you use?
twrp 2.6.3.1(att)
err on the side of kindness
Thanks. Kinda suspected as much. The update binary may not be compatible with the latest version.
DocHoliday77 said:
Everything checks out so far on my end. Im downloading the firmware again in case something went wrong there.
In the meantime, what recovery are you using? Maybe try using a different one ir a different version?
Click to expand...
Click to collapse
CWM 6.0.4.7. TWRP doesnt work for me.
JohnHorus said:
CWM 6.0.4.7. TWRP doesnt work for me.
Click to expand...
Click to collapse
So are you saying CWM worked for you then?
DocHoliday77 said:
So are you saying CWM worked for you then?
Click to expand...
Click to collapse
No, TWRP doesn't work AT ALL for me. It can't even locate my internal SD.
CWM 6.0.4.7 is all I've tried with.
I dont use cwm so im not sure about the version right off hand. If thats the latest, try a slightly older one, or if its older try the latest.
I got file corruption error in at&t i747. Did not tried to flash again. Using latest twrp recovery.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
ive lost my computer HD and lost a bunch of stuff. as for ace ii related things, ive lost mg2 firmware, temp root, samsung drivers, custom recoveries and roms. custom recoveries and roms arent much of an issue since ace2nutzer, chronomonochrome and sergeyl are still actively developing. as for stock firmware and temp root, i cant seem to be able to find a good download site (site that supports resuming/pausing)
id like to humbly request an upload for the barebone basics such as stock firmware, temp root, odin and all the other you-need-these-to-install-custom-rom stuff to an easy to use download service (like google drive)
*EDIT*
my phone is currently out of order and it seems i need to reflash using odin. i was using ace2nutzers cm11 and ran into some issues. then i tried flashing chronokernel 4.4.2 when trying to upgrade to ace2nutzers more recent cm11 build, but im facing philz recovery error 'status 7' when trying to flash anything. it is currently systemless, with only recovery mode (philz) and download mode working
*EDIT2*
in philz it is stating my internal storage as sdcard1 and not 0. my external is called sdcard0
If you have ace2nutzer's kernel, install it by recovery, power off and boot on recovery again.
Then install the ROM you want.
I've never faced status 7 error with CWM recovery 6.0.5.0 of this kernel.
me too, only TWRP didnt work once, and chrono admitted it was a bug he couldnt fix.
i opened up the rom on my friends PC and it turned out it was a corrupted archive. CWM flashed it anyways and that was why i lost the OS. i dont understand why i couldnt just reflash a newly downloaded and checked archive but that too didnt work. i also tried installing the kernel again, rebooted and tried installing the rom again and nope. then removing the whole assert thing under updater-script, it only worked once when installing a kernel. annnd finally after a sleepless night i tried adb sideloading and fastboot recovery, it was a bad decision as now even recovery mode doesnt work -.-
theres a good thing though, download mode still works. im hoping someone can upload a stock rom somewhere safe. i read but dont understand why people say mg2 is preferred.
Mg2 is the newest base band but for your target it doesn't matter right now.
What model do you have, 8160 or 8160P with NFC?
sorry for the late reply, I needed something to get my mind off my old friend
its a standard ace ii, non P/L version
fonzacus said:
sorry for the late reply, I needed something to get my mind off my old friend
its a standard ace ii, non P/L version
Click to expand...
Click to collapse
Just install by Odin Russian gingerbread following instructions from YouTube video below.
After this, you'll have the phone like a brand new taken from the factory (at least the firmware).
Then, install any jelly bean stock you want.
And finally you can install the custom ROM you want.
Download Russian gingerbread from this link:
https://www.dropbox.com/s/3okawqmw8gbazns/I8160XXLK6.rar?dl=0
huge kudos, its all running just fine again with ace2nutzers cm11
im hoping dropbox wont die/expire
fonzacus said:
huge kudos, its all running just fine again with ace2nutzers cm11
im hoping dropbox wont die/expire
Click to expand...
Click to collapse
Don't worry about that, I uploaded this Dropbox link and I probably won't retire it for a long time.
This is the only 3 part stock firmware for GT-i8160 and it's the only ROM that can repair almost anything we "do" the phone.