Here is the latest leak, in CWM flashable form, both stock and deodexed. (i know krylon360 posted a deodexed JL4 rom, but i was in the middle of batch uploading when i found out)
I have included untermensch's modded 3e recovery. this is COMPLETELY stock, even has annoying tmobile boot sounds. i took the modem and zimage from the ODIN file. It also comes rooted already.
DISABLE ANY LAGFIXES FIRST (like voodoo).
Stock Odex *Read Disclaimer*
Stock Deodexed (use this if you want to flash modded framework files, like future gingerbread themes, etc)
Wifi reboot loop fix included (thanks Krylon360/TeamWhiskey for alerting me that wifi reboot looping was a problem and providing the fix).
Disclaimer: To get the odex version to work, i had to remove a few things. it was having errors because /system was being filled. I had to remove a few files to get it to work. here is what i removed:
Slacker Radio
Layer
Amazon
Kindle
Power On Sound
Shutdown Sound
Now, all the apps i removed can be downloaded from the market (they would be updated anyway). I am attaching the annoying tmobile boot sounds for those that must have them. But it works now.
Using Root Explorer (or, android Commander when booted into CWM):
Put PowerOn.wav in /system/etc/
and
Put shutdown.ogg in /system/media/audio/ui/
Changelog
12-17-2010 11:25 AM Pacific
Latest working links live
You the man! Thank you for this.
Is the deodexed version faster?
Sent from my SGH-T959 using XDA App
hitman818 said:
Is the deodexed version faster?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
not really sure, but it makes it easier to use things like the gingerbread theme that th3man was working on, lockscreen mods, etc. (not that it works with jl4, just using as an example)
This does also include a kernel and a modem?
Sent from my SGH-T959 using XDA App
this is so crazy
hitman818 said:
This does also include a kernel and a modem?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
geoffcorey said:
I have included untermensch's modded 3e recovery. this is COMPLETELY stock, even has annoying tmobile boot sounds. i took the modem and zimage from the ODIN file. It also comes rooted already
Click to expand...
Click to collapse
please read before posting
Many, many thanks to all for everything.
Sent from my SGH-T959 using XDA App
Thank you so much, Flashing now oh wait.. 57 mins to go :/
EDIT: wow, i misread that post.
sorry
removed post
My first attempt to flash failed. trying again.
there is a bug in the script. i need to reupload the files.
Links will be back up when i've reuploaded.
Questions!
Questions:
1) Do I need to put a pit file into ODIN with this? If so, which pit file? Can I use the same 512 pit I used with JFD in ODIN?
2) I opened up the tar file, and I don't see a dbdata file. Last time I used odin to flash a tar without a dbdata I got an error upon reboot. Is no dbdata needed? Suggestion?
EDIT: WOOPS I meant to post this in the thread with the ODIN version. wrong thread.
Hmm. Worked for my husband? His cwm wasn't acting right. But it did flash ok.
Sent from my SGH-T959 using XDA App
SamsungVibrant said:
Questions:
1) Do I need to put a pit file into ODIN with this? If so, which pit file? Can I use the same 512 pit I used with JFD in ODIN?
2) I opened up the tar file, and I don't see a dbdata file. Last time I used odin to flash a tar without a dbdata I got an error upon reboot. Is no dbdata needed? Suggestion?
Click to expand...
Click to collapse
use 512 pit
flash the tar
once booted, go to Settings>Privacy>Reset
all done.
But that is the ODIN version, this and mine are the CWM versions, no ODIN needed.
krylon360 said:
use 512 pit
flash the tar
once booted, go to Settings>Privacy>Reset
all done.
But that is the ODIN version, this and mine are the CWM versions, no ODIN needed.
Click to expand...
Click to collapse
Thanks, but I meant to post that in the ODIN JL4 thread!
mrsvictoriarich said:
Hmm. Worked for my husband? His cwm wasn't acting right. But it did flash ok.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
which one did you flash, stock or deodexed
i'm re uploading the deodexed first. then the stock odex one. there wasn't a bug with the installer, but there was the wifi reboot loop that was apparent in jk6. that'll be fixed when the links are back up.
maydaysos said:
which one did you flash, stock or deodexed
Click to expand...
Click to collapse
Yes, I too would like to know the answer to this, because I am at 83% download of the deodexed version.
Thanks.
Edit: Never mind, I see that you are re-uploading both.
Related
Seems there are some asking in the XXJM6 thread but usually it gets buried with posts specifically for flashing the FW.
I tried downgrading using different PIT files and FWs but it would fail via ODIN.
Is there a way to downgrade XXJM6 and how?
Thanks.
Sent from my GT-P1000 using Tapatalk
Are you on the first or second versions of JM6?
2nd version but came from the 1st XXJM6 leak
Sent from my GT-P1000 using Tapatalk
try flashing LHA with repartition on and then another firmware..
xIllu said:
try flashing LHA with repartition on and then another firmware..
Click to expand...
Click to collapse
I think he meant JHA, and i agree.
Try to flash JHA with its PIT file and repartition and to upgrade to JJ4 from that.
Let us know if that worked.
xIllu said:
try flashing LHA with repartition on and then another firmware..
Click to expand...
Click to collapse
JHA you mean? Yup tried that with 816 PIT but it will immediately fail.
Sent from my GT-P1000 using Tapatalk
clubtech said:
I think he meant JHA, and i agree.
Try to flash JHA with its PIT file and repartition and to upgrade to JJ4 from that.
Let us know if that worked.
Click to expand...
Click to collapse
Never tried JJ4, will give it a try then post the result.
EDIT: tried JJ4 - FAIL. Same goes with almost all the fw posted in samfirmware website. So i guess to those who flashed to JM6, we are stuck!! Good thing JM6 is a good fw. Still hoping a workaround though.
Sent from my GT-P1000 using Tapatalk
have you tried the following?
1) Factory reset via HOME + VOL UP + POWER
2) Flash PIT only first (use the P1 from SAMFIRMWARE)
3) Flash JJ4 (make sure have dbdata file inside)
bdigitalstudio said:
have you tried the following?
1) Factory reset via HOME + VOL UP + POWER
2) Flash PIT only first (use the P1 from SAMFIRMWARE)
3) Flash JJ4 (make sure have dbdata file inside)
Click to expand...
Click to collapse
I have tried this too, still would fail. Anyone who successfully downgraded from JM6?
What do you mean, make sure you have dbdata file inside?
Sent from my GT-P1000 using Tapatalk
antz88c said:
I have tried this too, still would fail. Anyone who successfully downgraded from JM6?
What do you mean, make sure you have dbdata file inside?
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Open the TAR file using WINRAR or something and see for a file called DBDATA. This file is a must after PIT programming.
bdigitalstudio said:
Open the TAR file using WINRAR or something and see for a file called DBDATA. This file is a must after PIT programming.
Click to expand...
Click to collapse
Meaning after flashing PIT, flash dbdata then JJ4?
Sent from my GT-P1000 using Tapatalk
antz88c said:
Meaning after flashing PIT, flash dbdata then JJ4?
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
open the JJ4.TAR with WinRAR and you should see the DBDATA file inside. if it is not, find the firmware which has it..
bdigitalstudio said:
open the JJ4.TAR with WinRAR and you should see the DBDATA file inside. if it is not, find the firmware which has it..
Click to expand...
Click to collapse
Thanks but didn't work.
Sent from my GT-P1000 using Tapatalk
Well i was able to downgrade from JM6 to ANY firmware, but i never used the 2nd version of JM6 nor the full flash of JJ4, i was only flashing the pda part so far.
Note that my firmware was BUJI4 when i got the tablet.
sedde said:
Well i was able to downgrade from JM6 to ANY firmware, but i never used the 2nd version of JM6 nor the full flash of JJ4, i was only flashing the pda part so far.
Note that my firmware was BUJI4 when i got the tablet.
Click to expand...
Click to collapse
Really strange, tried also flashing only the pda but odin will immediately fail. I have flashed again with the first JM6.
Sent from my GT-P1000 using Tapatalk
antz88c said:
Really strange, tried also flashing only the pda but odin will immediately fail. I have flashed again with the first JM6.
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
I have never flashed no modem or csc or repartitioned my flash , so i guess thats why i can downgrade.
Seems like u can downgrade if you don't use repartition however it is not clear why Odin fails if we try to repartition ...
Sent from my GT-P1000 using XDA App
Euro Galaxy Tab can´t downgrade...
I installed the JM6 taken from the first post of this thread: http://forum.xda-developers.com/showthread.php?t=854300
V1.7 ODIN3 flashing with files that included his pit (to repartition marked), PDA, CSC, and PHONE ...
When I tried to other ROMs have been impossible before. Consistent with ODIN errors that interrupt the process and let the tablet dead. Resusitaste flashing is only possible from the outset JM6 ...
It is an excellent ROM (fixed the Swype extrallendo and installing a ROM that came before).
Anyway, to be calmer, we expect a possible solution. Thanks.
Did you guys try one of the full newer than JJ4 firmwares from gsmpl.com ?
Those are full Odin separated pit/pda/csc/modem JJ6, JJ7 and JK2.
Look for P1000->... http://gsmpl.com/index.php?id=Do_Pobrania
No idea if it will downgrade. Just trying to help.
Yes, and NO, that doesn't work either...
FredBE said:
Did you guys try one of the full newer than JJ4 firmwares from gsmpl.com ?
Those are full Odin separated pit/pda/csc/modem JJ6, JJ7 and JK2.
Look for P1000->... http://gsmpl.com/index.php?id=Do_Pobrania
No idea if it will downgrade. Just trying to help.
Click to expand...
Click to collapse
Does anybody know the difference between the two XWJS5 firmwares?
Difference...
Yes. The previous one is for Heimdall and the new one is for Odin.
As I saw.
I have heard that the new one contains a bootloader update.
I don't know if its true tho.
/qsec
temilla said:
Does anybody know the difference between the two XWJS5 firmwares?
Click to expand...
Click to collapse
Previous JS5 was an update flash (1 file), this one is a FULL Rom (3 file, 242mb). The same difference between JS3 and XEN JS3.
Anyway it shouldn't be 803 .pit. To recover from experimental partitioning I use JS3-full (which is tagged as 803) with 512.pit since 803 doesn't work for me.
matticala said:
Anyway it shouldn't be 803 .pit. To recover from experimental partitioning I use JS3-full (which is tagged as 803) with 512.pit since 803 doesn't work for me.
Click to expand...
Click to collapse
Thanks for that ! I'm trying to install these JS5 since yesterday with .pit 803 without success : mount problem at reboot after odin success, formating in recovery doesn't work and updating couldn't been done by new rom (vibrate loop reboot).
Changing to 512 .pit seems to solve this problem : my phone just restarts on JS5 now !
matticala said:
Anyway it shouldn't be 803 .pit. To recover from experimental partitioning I use JS3-full (which is tagged as 803) with 512.pit since 803 doesn't work for me.
Click to expand...
Click to collapse
OT- that's interesting as I flashed js3 with 803 unsuccessfully but it works with 512.
Sent from my GT-I9000 using XDA App
Content of I9000 XEN I9000XWJS5.rar:
Code:
GT-I9000-CSC-XENJS3.tar.md5
I9000XWJS5-REV03-ALL-low-CL869633.tar.md5
MODEM_I9000XXJPY.tar.md5
Confirmed there are a bootloader and a Sbl file, even though those are likely the same of those included in the previous XEN JS3. I'll make a checksum to verify
UPDATE: there is no update in this new XEN JS5, md5sum for boot.bin is identical to the one bundled within XEN JS3
MarkyG82 said:
OT- that's interesting as I flashed js3 with 803 unsuccessfully but it works with 512.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
guys please let me understand.... so why you are speaking about .512 and .803 .pit?
Using odin with last rom js5 from samsungfirmware I have to select just one file in pda tab, whitout .pit file.
what's wrong in my flashing way?
Be careful on updating. Double check the bootloader and Sbl.bin. We don't want the sgs to be locked, like the galaxy tab.
Sent from my GT-I9000 using XDA App
userinit said:
guys please let me understand.... so why you are speaking about .512 and .803 .pit?
Using odin with last rom js5 from samsungfirmware I have to select just one file in pda tab, whitout .pit file.
what's wrong in my flashing way?
Click to expand...
Click to collapse
.pit file is used to flash the full rom (phone + modem + csc) with re-partition flagged, basically the pit file tells odin where to write the filesystems.
Whenever you have just one file (phone), you don't need either pit or re-partition flag. This last XEN JS5 is a FULL rom.
g00ndu said:
Be careful on updating. Double check the bootloader and Sbl.bin. We don't want the sgs to be locked, like the galaxy tab.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
doublechecked boot.bin (where identical), not sbl.bin though
g00ndu said:
Be careful on updating. Double check the bootloader and Sbl.bin. We don't want the sgs to be locked, like the galaxy tab.
Click to expand...
Click to collapse
You're right !
I still have my DL mode after flashing these files ...
Wendigogo said:
You're right !
I still have my DL mode after flashing these files ...
Click to expand...
Click to collapse
Was Auto Reboot selected? Does Odin show a green success after completition?
Official thread
matticala said:
Was Auto Reboot selected? Does Odin show a green success after completition?
Click to expand...
Click to collapse
Yes for the two questions !
Wendigogo said:
You're right !
I still have my DL mode after flashing these files ...
Click to expand...
Click to collapse
Just for clarify it, Samsung's 'locked' bootloader on Galaxy Tab is not the problem about download mode... The signed bootloader also allow flashing the device later... The problem is just about the files what you can use... With Samsung's signed bootloader you can flash in the future just also signed kernels, you basically you willl not able to flash custom ROM-s in the future... You can flash firmwares with Odin, you can flash Samsung beta firmwares also, just simply could not flash custom ROM-s... This could be big problem or verly small also based on your usage habit. While I use 2.2.1 I simply not use custom ROM-s, but of course before I used... Nowadays 'signed' situations could not break my life with i9000, but with Galaxy Tab it could ... at least in the near future, as it's ROM not as good as the current i9000 versions...
Hi,
eboIa said:
Just for clarify it, Samsung's 'locked' bootloader on Galaxy Tab is not the problem about download mode... The signed bootloader also allow flashing the device later... The problem is just about the files what you can use... With Samsung's signed bootloader you can flash in the future just also signed kernels, you basically you willl not able to flash custom ROM-s in the future... You can flash firmwares with Odin, you can flash Samsung beta firmwares also, just simply could not flash custom ROM-s...
Click to expand...
Click to collapse
Thanks for explaining this ! But I couldn't understand why you couldn't donwgrade to a non-locked bootloader with Odin ? Don't have access to it ? But without access to it it couldn't be modified with latest Samsung FW via Odin ?
Hi
Still not patched to fixed.
for me it is interesting too why it is so messy about downgrade, could someone just wipe bootloader and force flash older back?
when i flash this i cant get the swedish keyboard in my phone
any ideas on this ist this the european ver i reverted back to I9000XWJM5 i kies tells me there is no update
Sorry one is not hiedemell both are odin one is full 3 file package which requires 803 pit file and other is single pda file flashable without pit or repartition from any previous stock rom
Sent from my GT-I9000 using XDA App
Hi all. I need to send my tab in for repairs and I tried following the other guides in the forum so I could return to stock but I haven't been successful.
What I did to return to stock: 1. Used Odin to flash DXK (my region) firmware which came from samfirmware.com 2. After the flash completed successfully (flashed with .pit and the rom itself) it reboots and just perpetually gets stuck in the Samsung boot logo. What did I do wrong and how can I get it to boot to stock?
Help would be really appreciated. Thanks!
EDIT: SOLUTION
Okay. It's confirmed. A fix for all your CSC and partition problems.
1. Go to noxxious' post # 53 http://forum.xda-developers.com/showpost.php?p=14160362&postcount=53
2. Follow instructions to the letter by flashing P1000DXJK2 - Full (Use Odin process not Heim)
3. Connect to Kies. Kies will notify you that there is an update, use that to upgrade to Gingerbread officially.
4. After the upgrade, it will have no partition problem and it will display properly XTC as your CSC on Kies. It's like a brand new non modified tab!
im in the same bout as you mate did just the same thing was working fine on voodoo lagfix wanted stock back flashed now stuck at samsung logo
All i can say is check to see if you still have the recovery mode in your tab by holding up volume and power button the let go of power and keep holdig up volume when you see it boot to samsung logo
If you have lost your recovery mode your stuffed your bootloader is locked and theres nothing you can do to bring it back its time for samsung service to sort it out
Can you still put your tab in Download mode?
If so, you can try to reflash DXK.
1. Use the p1.pit file for PIT and DXK for PDA.
2. Select re-partition on.
3. Maybe this time after the tab reboot and the odin pass you'll be stuck at the recovery mode, error will be E : Cannot mount dbdata. . .
4. To be out of this you could select format/restore, navigate using volume up/down then press home button to select that option.
5. Then go back to menu and select reboot.
-- inform me if this works.
Edited my first post :
Yeah, you're totally screwed with a protected bootloader!
I just downloaded the P1000DXKM2 @Samfirmware and discovered that it contains sbl.bin, boot.bin, and the zImage file size is 7860 Kb.
See this forum http://forum.xda-developers.com/showthread.php?t=888071
Sent from my GT-P1000 using XDA Premium App
Will try this and report back. Thanks!
Sent from my GT-P1000 using XDA Premium App
Followed your instructions but it's stuck on the Samsung logo.
Sorry, did u follow my first post?
After i download DXKM2 in samfirmware i discovered that it contains new bootloader, containing zImage more than 4,000-5,000Kb.
-- in short flashing that with repartition will have the same result as your first attemp.
This time will you try to flash Roto's JMEv4_full safe rom. Same steps as my first post.
Sent from my GT-P1000 using XDA Premium App
I flash roto's when I want to restore my tab and put a custom rom. What I need to find out is how to put a DX rom into it so I can send it to a service center.
Sent from my GT-P1000 using XDA Premium App
i encountered something similar to this before when i was testing out the 2.2.1 HK rom. i also made the mistake of flashing protected bootloaders onto my tab, though i reverted it back to unprotected bootloaders using Chainfire's and RotoHammer's bootloader patcher http://forum.xda-developers.com/showthread.php?t=888071.
as for my stock firmware then, mine was P1000DXJK2. what i did was dl the P1000DXJK2 from samfirmware. I then removed boot.bin and sbl.bin from the tar package (i patched the unprotected bootloaders onto my tab), and added a dbdata.rfs into the tar package. i then flashed using odin (flashed with no pit). and i got it back up and running.
my P1000DXJK2.tar file contains the following:
cache.rfs
dbdata.rfs
factoryfs.rfs
hidden.rfs
modem.rfs
param.lfs
zImage
noxxious said:
i encountered something similar to this before when i was testing out the 2.2.1 HK rom. i also made the mistake of flashing protected bootloaders onto my tab, though i reverted it back to unprotected bootloaders using Chainfire's and RotoHammer's bootloader patcher http://forum.xda-developers.com/showthread.php?t=888071.
as for my stock firmware then, mine was P1000DXJK2. what i did was dl the P1000DXJK2 from samfirmware. I then removed boot.bin and sbl.bin from the tar package (i patched the unprotected bootloaders onto my tab), and added a dbdata.rfs into the tar package. i then flashed using odin (flashed with no pit). and i got it back up and running.
my P1000DXJK2.tar file contains the following:
cache.rfs
dbdata.rfs
factoryfs.rfs
hidden.rfs
modem.rfs
param.lfs
zImage
Click to expand...
Click to collapse
So Samsung won't notice that I have unlocked bootloaders when I send the tab to them? Where do I get a dbdata from?
Sent from my GT-P1000 using XDA Premium App
nope. they won't notice. but if you want it to have signed bootloaders, you could just add the dbdata.rfs to the TAR package.
i have attached the dbdata.rfs that i used. got it form GT-P1000-CSC-MULTI-OXXJK2.
noxxious said:
nope. they won't notice. but if you want it to have signed bootloaders, you could just add the dbdata.rfs to the TAR package.
i have attached the dbdata.rfs that i used. got it form GT-P1000-CSC-MULTI-OXXJK2.
Click to expand...
Click to collapse
Thanks for this. So you mean the reason why the rom won't boot after flashing because it lacks this file? What does it do exactly?
Sent from my GT-P1000 using XDA Premium App
i actually don't know.
but from my experience this solved my flashing problem when i tried to roll back to stock firmware.
when using heimdall it is listed with cache.rfs under CSC
May i ask why you are sending your tab to samsung for repair?
noxxious said:
i actually don't know.
but from my experience this solved my flashing problem when i tried to roll back to stock firmware.
when using heimdall it is listed with cache.rfs under CSC
Click to expand...
Click to collapse
I placed dbdata.rfs into the exact same rom that you used and it fails at dbdata.rfs flash. Odd.
That's weird. You extracted the dbdata.rfs from my zip right?
Sent from my GT-P1000 using Tapatalk
noxxious said:
That's weird. You extracted the dbdata.rfs from my zip right?
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Yes, I did. Then I stuffed it into the .tar.
If it's not too much of a bother maybe you could upload the working .tar that you used?
Sent from my GT-P1000 using XDA Premium App
ok. im currently uploading the tar i used. i removed boot.bin and sbl.bin from the tar and dbdata.rfs added.
noxxious said:
ok. im currently uploading the tar i used. i removed boot.bin and sbl.bin from the tar and dbdata.rfs added.
Click to expand...
Click to collapse
Thanks a lot dude!
Sent from my GT-P1000 using XDA Premium App
DL Link added.
P1000DXJK2
Flash with no .pit
btw, what's the prob with your tab that you are gonna return it for warranty?
noxxious said:
DL Link added.
P1000DXJK2
Flash with no .pit
btw, what's the prob with your tab that you are gonna return it for warranty?
Click to expand...
Click to collapse
Thanks! Will try it now.
Sent from my GT-P1000 using XDA Premium App
If I upload custom kernel on my Galaxy S with 2.3.4 JVQ, is it possible to revert to original JVQ kernel in order to check if same issue will appear on original kernel to detect if custom kernel has bug?
Thanks.
Flash as pda with odin.
Sent from my GT-I9000 using XDA Premium App
To get just the stock kernel in a flashable state you need to extract the zImage file from stock ROM (either one file or PDA of 3-file), then put it in a tar file by itself. Then you flash that as PDA with Odin.
I'm just going to expand a bit.
Find a single file tar of the stock firmware that is meant to be flashed as a PDA. Use winrar to look inside the .tar file to get the zImage and put it in a tar by itself. You can then flash it as PDA in Odin.
Sent from my GT-I9000M using XDA App
I thought that it is proper way to extract zImage from original ROM but I wasn't sure that it is good way. Thanks, I will try in this way.
I created zImage.TAR with 7-zip but Odin cannot load it. It comes to step when zImage should be loaded but upload is not happening. Do I have to exec some certain parameters when zipping it in TAR with 7-zip or how can I do it?
EDIT: I managed to make proper (flashable) TAR with IZarc application. Nevertheless, I uploaded stock zImage but I still have root access although other mooded kernel specific applications are gone. So, basically, I didn't revert it to original state. Or I am wrong? Please, advise.
Thanks.
Rooting doesn't necessarily mean changing kernel. You can root a completely stock phone and still use stock kernel. You can also unroot the phone.
You can use the SGS kernel flasher free app to flash a zImage directly from the phone.
eLtOnI0 said:
Rooting doesn't necessarily mean changing kernel. You can root a completely stock phone and still use stock kernel. You can also unroot the phone.
You can use the SGS kernel flasher free app to flash a zImage directly from the phone.
Click to expand...
Click to collapse
He's right, root often stays behind. To get back to stock just do a factory reset.
Make sure you can get into download mode before flashing just in case.
Sent from my GT-I9000M using XDA App
eLtOnI0 said:
Rooting doesn't necessarily mean changing kernel. You can root a completely stock phone and still use stock kernel. You can also unroot the phone.
You can use the SGS kernel flasher free app to flash a zImage directly from the phone.
Click to expand...
Click to collapse
I've read through many threads, but in most they discribe to root a phone via flashing the kernel
like here.
and i also would like to have a backup of my stock kernel, if i would flash it, but i'm not sure from which version i should take it. i do have JVH, but i can't find a fitting csc (it's MOBJV2) on samfirmware or google.
THIS IS THE FULL BOOTLOADER, MODEM, RPM, AND TZ UPDATE.
this contains the NON-HLOS.bin modem.bin sbl2.mbn tz.mbn aboot.mbn rpm.mbn sbl3.mbn
It is recommended for CM to update the entire images images, we constantly update kernel so it is recommended to not fall behind on not updating full images.
this is an extension unknownforce tar.
in odin, check update phone bootloader and put it in pda
Beezer80 said:
When I went to Odin this my PhoneBootloader Update box was greyed out.
So, in order to update the bootloader we need to edit the .ini file that's in the Odin 3.07 folder.
Open the .ini with Notepad and change the line below
PhoneBootUpdate=0k
Change to.
PhoneBootUpdate=1
Save the file and start Odin. The box will still be greyed out but it will be checked.
Proceed with the update.
Once you are finished with the bootloader update it is recommended to revert the changes that you have made to the .ini
Thanks for noobnl for all the help.
Click to expand...
Click to collapse
faq:
do i need to check xyz option??!
doesn't matter
DOWNLOAD:
http://d-h.st/CKV
noobnl said:
THIS IS THE FULL UPDATE.
this contains the NON-HLOS.bin modem.bin sbl2.mbn tz.mbn aboot.mbn rpm.mbn sbl3.mbn
It is recommended for CM to update the entire images images, we constantly update kernel so it is recommended to not fall behind on not updating full images.
this is an extension unknownforce tar.
in odin, check update phone bootloader and put it in pda
DOWNLOAD:
http://d-h.st/CKV
Click to expand...
Click to collapse
Nice work! Thanks!
Who can use this? If i am rooted running FreeGS4 can i use this to Odin to MD4?
jbarresi19 said:
Who can use this? If i am rooted running FreeGS4 can i use this to Odin to MD4?
Click to expand...
Click to collapse
anyone with a sprint gs4
noobnl said:
anyone with a sprint gs4
Click to expand...
Click to collapse
Ok so let me get this right...lol cause i am a lil slow....so rooted and on freegs4 I can Odin this file and I will be fully updated to MD4....I just need to check Update Phone Boot Loader, put file in PDA, and do i leave Auto Reboot checked?
Odin 3.07 Help
When I went to Odin this my PhoneBootloader Update box was greyed out.
So, in order to update the bootloader we need to edit the .ini file that's in the Odin 3.07 folder.
Open the .ini with Notepad and change the line below
PhoneBootUpdate=0k
Change to.
PhoneBootUpdate=1
Save the file and start Odin. The box will still be greyed out but it will be checked.
Proceed with the update.
Once you are finished with the bootloader update it is recommended to revert the changes that you have made to the .ini
Thanks for noobnl for all the help.
jbarresi19 said:
Ok so let me get this right...lol cause i am a lil slow....so rooted and on freegs4 I can Odin this file and I will be fully updated to MD4....I just need to check Update Phone Boot Loader, put file in PDA, and do i leave Auto Reboot checked?
Click to expand...
Click to collapse
doesn't mattter
noobnl said:
doesn't mattter
Click to expand...
Click to collapse
AWESOME....Im an idiot and i was able to do that....great work and thank you...much appreciated...tried another method last night and failed....took me 2 hours....this took 5 mins....lol should have been patient
One question though I saw in QBKings video that after the update you should be able to go to Application Manager and move apps to the SD card but I dont see that option...I did a reboot...am i doing something wrong?
jbarresi19 said:
Who can use this? If i am rooted running FreeGS4 can i use this to Odin to MD4?
Click to expand...
Click to collapse
My phone says MF9. What is MD4? Did I miss something?
Sent from my SPH-L720 using xda premium
maxpower7 said:
My phone says MF9. What is MD4? Did I miss something?
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
No i meant MF9....can you move apps to the SD card from appliaction manager...i can not....
i just flashed this over freegs4 rom.. im on MF9 but build number is still MDL.. Whats not in this tar file?? i still cant move anything to my sd?? so what does thid file update?? modem?
Maybe i am doing something wrong or maybe its because i am running FreeGS4 but none of the few things that changed with the MF9 update are availabe....like the smart pause button in setting, add apps to sd card, and the legabilty option.....is it cause i am on a rom based on MDL...will this change when my rom gets updated?
---------- Post added at 02:43 PM ---------- Previous post was at 02:42 PM ----------
P.Mobile said:
i just flashed this over freegs4 rom.. im on MF9 but build number is still MDL.. Whats not in this tar file??
Click to expand...
Click to collapse
My build number just says FreeGS4 v2.0.....My baseband and Software version both say MF9 but i cant move anything to the SD card and im thinking/hoping its only cause our Rom hasnt been updated...can someone confirm or deny this? That once our rom gets updated we will have full function of MF9
This cannot be the "full upgrade". At 30MB how can that be compressed from 360mb download OTA. I believe this is just the modem and kernel.
Sent from my SPH-L720 using Tapatalk 4 Beta
daniel4653 said:
This cannot be the "full upgrade". At 30MB how can that be compressed from 360mb download OTA. I believe this is just the modem and kernel.
Sent from my SPH-L720 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Im starting to get the same feeling...think im gonna try the other method but i cant get stock MDL to download
People, it's the full firmware, not the operating system. Normally, we just update the modem and other small bits, but this includes the bootloader and other smaller partitions that get overlooked if you only flash the updated OS through a zip. If you took the OTA as it was pushed to your device, you do not need this.
Tapatalked from my GSIV
THIS IS THE FULL BOOTLOADER, MODEM, RPM, AND TZ UPDATE.
No android operating system files
Thank you. Worked great.
I must be doing something wrong. I edited the .ini to allow bootloader update. Put in PDA slot and hit start. It passes after ~16 secs then reboots and nothing is changed. Baseband is still MDL. Anyone know what I'm missing? I'm using Odin v3.07 and have tried different ports/comps.
Also on FreeGS4 with TWRP 2.6.0.0.
EDIT: Fixed by turning device off then booting into Download Mode instead of rebooting to download mode.
After downloading the 3.07 odin version, I edited the configuration settings for the program to check "bootloader update".
I select PDA and go to find the mf9fullupdate.tar.md5 on my desktop, and the program can't find it; I'm slightly stuck now.
EDIT: After ten seconds of posting this, I realized that I had to unzip the file xP
Got it!!
AND WORKS PERFECTLY! Thank you for this!
Great job.
This worked fine. Just a note to all. Once you get it started please wait for it to finish. It takes about a little over 2 minutes to get done. Once it's OK in the odin window. You will need to disconnect the phone and either pull the battery or hold the power button down till it turns off. Once that is off you can then turn it back on and it should be updated.
I love this. :victory: