So I am updating the update script file in the 4.3 update to remove the integrity checks for all files and removing the lines of code to remove the Bootloader.
I need help as to which file or files are linked to the bootloader.
Code:
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
ui_print("Update tz.mbn ota");
assert(package_extract_file("tz.mbn", "/dev/block/mmcblk0p8"));
ui_print("Package tz.mbn done.");
ui_print("Update aboot.mbn ota");
assert(package_extract_file("aboot.mbn", "/dev/block/mmcblk0p6"));
ui_print("Package aboot.mbn done.");
ui_print("Update rpm.mbn ota");
assert(package_extract_file("rpm.mbn", "/dev/block/mmcblk0p7"));
ui_print("Package rpm.mbn done.");
ui_print("Update sbl2.mbn ota");
assert(package_extract_file("sbl2.mbn", "/dev/block/mmcblk0p4"));
ui_print("Package sbl2.mbn done.");
ui_print("Update sbl3.mbn ota");
assert(package_extract_file("sbl3.mbn", "/dev/block/mmcblk0p5"));
ui_print("Package sbl3.mbn done.");
Once I get this last bit of information I can remove that from the update script and the update should apply everything with the exception of the bootloader and related files.
ui_print("Update aboot.mbn ota");
assert(package_extract_file("aboot.mbn", "/dev/block/mmcblk0p6"));
ui_print("Package aboot.mbn done.");
And we are sure there is nothing else relating to the bootloader?
I have the script updated however TWRP is not liking it. Keeps getting an Error. an someone look and see if they can see the issue here.
Problem solved. Flashing now. Will report back shortly. Hopefully my phone works after skipping the bootloader and all the checks.
James
All flashed fine. However bootloop and I forgot to take out the new recovery out of the script. Kept the same bootloader though. Hopefully I can odin back to MF9 otherwise I am screwed.
James
Ok so I was able to odin back to MF9. Will be trying the update script on a clean MF9 system.
So this is an absolutely a no go. I can update without the bootloader but it will 100% not boot. I get to the sprint bootscreen and it locks. Something in this rom seems like it requires the bootloader. I have tried clean system nothing on it and it will not boot. With a bit of modification to the script I can probably get the modem updating pretty easily.
James
Isn't there a way I could pull the img's from my fone? I did the full 4.3 update on a brand new fone, I flashed cf auto root and philz touch cwm recovery. If someone could tell me how to pull the img's, or couldn't I just use recovery to make a backup? and then post the backed up files?
Keithgordon said:
Isn't there a way I could pull the img's from my fone? I did the full 4.3 update on a brand new fone, I flashed cf auto root and philz touch cwm recovery. If someone could tell me how to pull the img's, or couldn't I just use recovery to make a backup? and then post the backed up files?
Click to expand...
Click to collapse
Check here http://forum.xda-developers.com/showpost.php?p=46961527&postcount=14
Or
And here Sac asked for anyone who has taken it to pm him!
Or here too.
Lastly here is a great tutorial.
I did still uploading...
Sent from my SPH-L720 using xda app-developers app
We (me and sac) figured it out, you AT LEAST need the new modem, as shown by the logcat here, or it won't boot.
Code:
D/QSEECOMAPI: ( 3716): QSEECom_start_app sb_length = 0x8271c
D/QSEECOMAPI: ( 3716): App is not loaded in QSEE
E/QSEECOMAPI: ( 3716): Error::Cannot open the file /system/etc/firmware/tima_pkm.mdt
E/QSEECOMAPI: ( 3716): Error::Loading image failed with ret = -1
cj10488 said:
So this is an absolutely a no go. I can update without the bootloader but it will 100% not boot. I get to the sprint bootscreen and it locks. Something in this rom seems like it requires the bootloader. I have tried clean system nothing on it and it will not boot. With a bit of modification to the script I can probably get the modem updating pretty easily.
James
Click to expand...
Click to collapse
Why would we not want to include the bootloader? I thought we wanted everything except recovery?
Where is freeza???
Sent from my SPH-L720 using xda app-developers app
I have attached my updater-script file. This removes all checks and the bootloader. The only issue is I cannot get the update to boot for the life of me. There is just a never ending bootloop at the samsung screen. I have tried everything I can think of. The good thing is as long as your on MF9 before running the update with my script it seems as though you can odin back to stock MF9 without any issues but I cannot confirm this completely. I have been able to go back multiple times but could something be hidden that I dont know about who knows. If you try to use my updater-script file within the stock update it is at your own risk obviously. For safe measures on my part I deleted the Aboot file out of the update.
Ingenium13 said:
Why would we not want to include the bootloader? I thought we wanted everything except recovery?
Click to expand...
Click to collapse
Currently the new bootloader enables Knox Void Warranty Binary. Its possible after you upgrade the bootloader from 4.3 that you will void your warranty and have no way to reset this binary ticker(Flash counter). This is currently the same issue with Samsung Galaxy Note 3.
Some people believe that this new bootloader could blow an efuse which would void your warranty and set the ticker to 0x1(This is only a rumor at this point in time). Others believe its software related. Either way its somehow tied into this 4.3 bootloaders that are being released by Samsung.
MasterZen88 said:
Currently the new bootloader enables Knox Void Warranty Binary. Its possible after you upgrade the bootloader from 4.3 that you will void your warranty and have no way to reset this binary ticker(Flash counter). This is currently the same issue with Samsung Galaxy Note 3.
Some people believe that this new bootloader could blow an efuse which would void your warranty and set the ticker to 0x1(This is only a rumor at this point in time). Others believe its software related. Either way its somehow tied into this 4.3 bootloaders that are being released by Samsung.
Click to expand...
Click to collapse
Just a small correction: it's not a flash counter nor is it related to the counter that methods like TriangleAway can currently reset. It's a binary flag, 0 or 1.
To add onto this, I believe I've read that after upgrading to a Knox equipped bootloader, people have been unable to downgrade. Not even through Odin.
I just updated the wife's phone..uh oh..NOT. everything is going good but I'm wondering if it is possible to run MJA modem on an MF9 base..I'm thinking yes but after noticing the Linux enforcement on MJA I'm asking some people a whole lot smarter than me.
From a Modded SPRINT Galaxy S4 on XDA PREMIUM
Related
I know wrong forum, but I'm looking to hear from some more experienced folks on here with the Tab.
Long story short. I knew flashing the modem would break something. I had previously downloaded the tab.rar file that had the restore files in it. My Tab would not update to the latest OTA because I deleted some sprint bloat on it. So my only alternative would be to restore the device since I deleted system files.
I went into odin and adding the pit.pit and the .tar file. Fails at trying to flash the modem.bin. I think at that point I tried it again with the modem.bin and it just gets stuck trying to flash it.
So then it's stuck at the Phone ! PC screen. Odin still sees it so I flash just the .tar (no .pit) and and it's back.
Does anyone have any modem files I can try? Or know of anyway to get my GPS back? I tested it today after doing some things and data seemed to be working again, but since I was indoors at work I couldn't test the GPS, to make it better I left it there accidentally today.
I also tried to flash the OTA via recovery and it failed at the modem part.
Any suggestions on how to get that file?
I'm that way, how should we solve the problem?
plz tell me how to do?
i con't use gps, so i want to flash modem.bin from ea24.but.......
yuanjie199775366 said:
I'm that way, how should we solve the problem?
plz tell me how to do?
i con't use gps, so i want to flash modem.bin from ea24.but.......
Click to expand...
Click to collapse
Yes, I posted a full EA24 modem.bin in the CDMA thread before it was re-joined to this thread. just search it's here somewhere.
shoman24v said:
I know wrong forum, but
Click to expand...
Click to collapse
Correct!
No "buts"
THIS IS ORIGINALLY INTENDED FOR USERS WITH KNOX BOOTLOADER [MJA+]
MF9 USERS CAN STILL USE THE APP SAFELY TO FLASH MF9/MJA FIRMWARE/RECOVERIES/KERNELS AS IT CONTAINS NO BOOTLOADER FILE
Also MF9 users should STAY AWAY from tz.mbn for now. It may contain Knox as well
Heimdall Suite is also a GREAT ODIN replacement, as it doesn't require you to make tar files. It will even flash .img files through download mode
If your dialer freezes and crashes when you make/receive calls, this will fix it
If you somehow can't get back to MJA baseband after the downgrade attempt to MF9, now you can!
I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE!!! USE AT YOUR OWN RISK!!!
ALL NEEDED FILES ARE INCLUDED! Bootloader NOT Included
1 - Download 'Heimdall Suite' with all files needed HERE: Heimdall_Suite-MJA_Firmware.zip
2 - Extract Zip to Somewhere Safe
3 - Put your phone into download mode and plug it in
4 - Click the 'Drivers' folder within the Folder you extracted and click on 'zadig.exe'
5 - In 'zadig.exe' Click on the 'options' menu drop-down and select 'List All Devices', Then From the drop-down menu of devices, choose 'msm8960', then select 'Replace Driver' and wait.
6 - Open 'heimdall-frontend.exe'
7 - Click on the 'Utilities' Tab and press the 'Detect' Button
8 - Select the 'Flash' Tab
9 - Select 'browse' under the 'pit' section and locate the 'jfltespr16gb.pit' file located in the 'firmware' folder of the extracted folder
10 - Press the add button and browse for the .bin or .mbn for the selected Package file.(All files Located in the Firmware Folder)
11 - Press The 'add' button again to add more firmware files(one at a time, select the package file code to the corresponding firmware file, then browse for the file)
12 - After Selecting All The Firmware Files, press 'Start' and wait for it to reboot
Firmware Package File Codes:
Code:
[COLOR=Lime]APNHLOS = NON-HLOS.bin
MDM = modem.bin
RPM = rpm.mbn
SBL2 = sbl2.mbn
SBL3 = sbl3.mbn[/COLOR]
[COLOR=Red]TZ = tz.mbn [/COLOR]
Thanks! So this will upgrade me to MJA modem and firmware without the new bootloader? I'm still on the MF9 bootloader and want to keep it for now!
Mudavo said:
Thanks! So this will upgrade me to MJA modem and firmware without the new bootloader? I'm still on the MF9 bootloader and want to keep it for now!
Click to expand...
Click to collapse
I left aboot out of the files for a reason but this is mainly intended for users with the Knox bootloader who have the issues I've had. It will definitely upgrade/downgrade firmware files a lot more successful than Odin.
Mudavo said:
Thanks! So this will upgrade me to MJA modem and firmware without the new bootloader? I'm still on the MF9 bootloader and want to keep it for now!
Click to expand...
Click to collapse
You don't want to do that because you would end up without sound stay away from mja modem and firmware and bootloader
tiger5969 said:
You don't want to do that because you would end up without sound stay away from mja modem and firmware and bootloader
Click to expand...
Click to collapse
Right. Well aware of the sound issue. I just missunderstood and thought this was a fix for sound issue on MJA modem with MF9 bootloader.
Mudavo said:
Right. Well aware of the sound issue. I just missunderstood and thought this was a fix for sound issue on MJA modem with MF9 bootloader.
Click to expand...
Click to collapse
Well although I do believe that is kernel related, you could always play around with the firmware files included, just stay away from aboot.mbn and you'll be safe from Knox bootloader
Edit: Although sbl2 and sbl3 stands for secondary boot Loader, I was able to downgrade/upgrade those. So I'm pretty sure they aren't the actual bootloader
this works great!!! thankyou so much your a life saver only one mod to the directions at lease for me I had to flash each one at a time. I was unable to add all and flash all
[Q
I chose to use all of the files in the firmware folder. (modem.bin, NON-HLOS.bin, rpm.mbn, sbl2.mbn, sbl3.mbn, and tz.mbn)
[/QUOTE]
I have had the sound and dialer issues as well as wifi issues. Seeing that you used all the files in the firmware folder, could this potentially fix the wifi issue also? I know of the wifi fix which I was planning on flashing but if this could fix everything in one go, I'd rather go with this.
Any suggestions?
crios42 said:
[Q
I chose to use all of the files in the firmware folder. (modem.bin, NON-HLOS.bin, rpm.mbn, sbl2.mbn, sbl3.mbn, and tz.mbn)
Click to expand...
Click to collapse
I have had the sound and dialer issues as well as wifi issues. Seeing that you used all the files in the firmware folder, could this potentially fix the wifi issue also? I know of the wifi fix which I was planning on flashing but if this could fix everything in one go, I'd rather go with this.
Any suggestions?[/QUOTE]
Are you full mja? Bootloader and all? If so, go flash the stock Mja rom from the developer section, it works great
Wifi is 100% kernel related. That Wifi fix resolves wifi data.
negamann303 said:
I have had the sound and dialer issues as well as wifi issues. Seeing that you used all the files in the firmware folder, could this potentially fix the wifi issue also? I know of the wifi fix which I was planning on flashing but if this could fix everything in one go, I'd rather go with this.
Any suggestions?
Are you full mja? Bootloader and all? If so, go flash the stock Mja rom from the developer section, it works great
Wifi is 100% kernel related. That Wifi fix resolves wifi data.
Click to expand...
Click to collapse
I am full MJA, bootloader and all. I'll give the MJA ROM a try. I'm still learning all this (this whole fiasco has been an excellent learning experience).
I THINK I know how to do this but I'm guessing that I can flash this using PhilZ. Would that be correct?
crios42 said:
I am full MJA, bootloader and all. I'll give the MJA ROM a try. I'm still learning all this (this whole fiasco has been an excellent learning experience).
I THINK I know how to do this but I'm guessing that I can flash this using PhilZ. Would that be correct?
Click to expand...
Click to collapse
Correct! Stay away from TWRP for it has a tendency to change your CSC to XAS instead of SPR
Negamann, just wanted to say thank you for helping us all out..
negamann303 said:
Correct! Stay away from TWRP for it has a tendency to change your CSC to XAS instead of SPR
Click to expand...
Click to collapse
Thanks for responses negamann. It is greatly appreciated.
I flashed the Stock 4.3 MJA ROM. It's up and running but I still have all the original issues, no sound, no dialing, no wifi.
I'm working through your guide and I have a question about step 10. Which firmwares go with which partitions?
Some are obvious and some I'd rather be safe than sorry. Let me know if I'm correct (Partition Name = firmware):
APNHLOS = NON-HLOS.bin
MDM = modem.bin
RPM = rpm.mbn
SBL2 = sbl2.mbn
SBL3 = sbl3.mbn
TZ = tz.mbn
crios42 said:
Thanks for responses negamann. It is greatly appreciated.
I flashed the Stock 4.3 MJA ROM. It's up and running but I still have all the original issues, no sound, no dialing, no wifi.
I'm working through your guide and I have a question about step 10. Which firmwares go with which partitions?
Some are obvious and some I'd rather be safe than sorry. Let me know if I'm correct (Partition Name = firmware):
APNHLOS = NON-HLOS.bin
MDM = modem.bin
RPM = rpm.mbn
SBL2 = sbl2.mbn
SBL3 = sbl3.mbn
TZ = tz.mbn
Click to expand...
Click to collapse
Those are correct. I'll update the first post later tonight, thanks
negamann303 said:
Those are correct. I'll update the first post later tonight, thanks
Click to expand...
Click to collapse
Thanks again Negamann.
I just realized that next to "File" in the "Partition Details" sections, It lists exactly which files are needed for each partition. I'm feeling a little thick.
I've got sound back and I can make calls again. Now onto the wifi fix.
Thanks again for all the help.
---------- Post added at 08:59 PM ---------- Previous post was at 08:42 PM ----------
Uh oh. The phone was great, I just needed to try the wifi fix. Shut it down. Tried to start up in recovery. Nothing. I've been messing with it for the past 10 minutes and nothing. I think it may be bricked.
I'm learning a lot from this series of unfortunate events.
crios42 said:
Thanks again Negamann.
I just realized that next to "File" in the "Partition Details" sections, It lists exactly which files are needed for each partition. I'm feeling a little thick.
I've got sound back and I can make calls again. Now onto the wifi fix.
Thanks again for all the help.
---------- Post added at 08:59 PM ---------- Previous post was at 08:42 PM ----------
Uh oh. The phone was great, I just needed to try the wifi fix. Shut it down. Tried to start up in recovery. Nothing. I've been messing with it for the past 10 minutes and nothing. I think it may be bricked.
I'm learning a lot from this series of unfortunate events.
Click to expand...
Click to collapse
Does it boot into download mode? try plugging it in and wait for the battery icon to pop up
negamann303 said:
Does it boot into download mode? try plugging it in and wait for the battery icon to pop up
Click to expand...
Click to collapse
It does nothing. Even plugging it in produces no charging light. It is dead. I've pulled the battery and letting it sit for awhile but I"m not hopeful. I'm searching around for ways to unbrick it, but it may be time to look at the Sprint website and see what I can do there. Maybe other people have been having issues with the OTA update and they'll replace it. It's worth a shot.
crios42 said:
It does nothing. Even plugging it in produces no charging light. It is dead. I've pulled the battery and letting it sit for awhile but I"m not hopeful. I'm searching around for ways to unbrick it, but it may be time to look at the Sprint website and see what I can do there. Maybe other people have been having issues with the OTA update and they'll replace it. It's worth a shot.
Click to expand...
Click to collapse
So what exactly caused it? just simply booting into recovery? did you flash anything after the firmware? did you select anything in the Heimdall app when flashing?
negamann303 said:
So what exactly caused it? just simply booting into recovery? did you flash anything after the firmware? did you select anything in the Heimdall app when flashing?
Click to expand...
Click to collapse
I'll recount everything that I've done with my phone:
Bought phone
Rooted phone and installed CWM
Used phone for several months
Updated to 4.3 OTA (I've learned my lesson)
Wifi stopped working on restart and after about a day of usage, sound and dialer also stopped working
Factory reset - still had the same problems
Rooted phone again using this guide.
Successfully rooted phone (again) and installed PhilZ recovery
Flashed the Stock ROM (Rooted) found here.
Restarted phone successfully. Still no wifi, sound, dialer
Flashed firmware using this guide
The phone was plugged in for about an hour before this attempt and had about 75% charge to begin with so it should have been on a full charge.
As far as I know, I followed the guide to the letter. I didn't check or change anything (that I know of)
Restarted. Sound and Dialer were functional again.
Shutdown to implement wifi fix
Could not restart. Nothing. Phone gave no response to any combination of button presses, battery removals, etc.
That's everything that I can think of. If I remember anything else I'll let you know.
My poor phone... :crying:
crios42 said:
I'll recount everything that I've done with my phone:
Bought phone
Rooted phone and installed CWM
Used phone for several months
Updated to 4.3 OTA (I've learned my lesson)
Wifi stopped working on restart and after about a day of usage, sound and dialer also stopped working
Factory reset - still had the same problems
Rooted phone again using this guide.
Successfully rooted phone (again) and installed PhilZ recovery
Flashed the Stock ROM (Rooted) found here.
Restarted phone successfully. Still no wifi, sound, dialer
Flashed firmware using this guide
The phone was plugged in for about an hour before this attempt and had about 75% charge to begin with so it should have been on a full charge.
As far as I know, I followed the guide to the letter. I didn't check or change anything (that I know of)
Restarted. Sound and Dialer were functional again.
Shutdown to implement wifi fix
Could not restart. Nothing. Phone gave no response to any combination of button presses, battery removals, etc.
That's everything that I can think of. If I remember anything else I'll let you know.
My poor phone... :crying:
Click to expand...
Click to collapse
wow that's just crazy. did you try holding the power button for 20 seconds? just a long shot haha
You will get the KNOX bootloader if you flash this.
YOU CANNOT UNDO THIS, ITS PERMANENT. FLASHING ANYTHING UNOFFICIAL AFTER FLASHING THIS TAR WILL VOID YOUR WARRANTY
Just the MK2 FULL stock tar extracted from Kies. Very hard to find online, and only extremely SLOW downloads available, so here it is.
md5 of the Tar: b90c2a1b5b32dca4edc56a3e6a8a3522
Do NOT rename the tar file. Even though it may be convenient to do so, Odin may fail the md5 check for no reason.
(L720VPUEMK2_L720SPTEMK2_L720VPUEMK2_HOME.tar.md5)
This is NOT ROOTED. Its the original TAR file for people who need an Emergency Recovery for their phones, and dont want to wait hours for it to download from slow file hosts.
Mediafire
FileDropper
Instructions:
1. Download tar.md5 from above and download Odin
2. Put phone into download mode (power off, then power button + Volume Down, then volume up when prompted)
3. Open Odin (right click > open as administrator)
4. Load stock tar into the PDA slot
5. Start flashing
6. Grab some popcorn because it will take a while
7. Profit
Danger......Read carefully before flashing.
so if im on stock unrooted mja or mk2 and for any reason i want to flash this file it will cause knox to trip?
i dont understand.
you say it will cause knox to trip!
en11gma said:
so if im on stock unrooted mja or mk2 and for any reason i want to flash this file it will cause knox to trip?
i dont understand.
you say it will cause knox to trip!
Click to expand...
Click to collapse
You will be alright. You have already upgraded to stock 4.3, so you already have the knox bootloader.
If you flash something unofficial, such as CF autoroot or a different recovery, you will trip the warranty void. The tar file I posted are Official, and will not trip the warranty.
Sent from my SPH-L720 using Tapatalk
what happens if i am rooted or have a custom recovery and my knox counter = 1 and i want to flash this with odin?
en11gma said:
what happens if i am rooted or have a custom recovery and my knox counter = 1 and i want to flash this with odin?
Click to expand...
Click to collapse
Well you have already voided your warranty then and currently there is no way to get the knox counter back to 0.
If you flash this, you will be going back to full stock, like you would expect. You are safe to do this.
Sent from my SPH-L720 using Tapatalk
random45 said:
Well you have already voided your warranty then and currently there is no way to get the knox counter back to 0.
If you flash this, you will be going back to full stock, like you would expect. You are safe to do this.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
i have been reading over and over if you try to flash an mk2 or mja over a rooted or custom recovery that you can brick the phone?
are you sure odin would flash this when it detects there is a knox = 1 and custum recovery or root?
dont think it is as simple as you say when you are knox = 1 with custum recovery or root.
hope your right. but i dont think so.
en11gma said:
i have been reading over and over if you try to flash an mk2 or mja over a rooted or custom recovery that you can brick the phone?
are you sure odin would flash this when it detects there is a knox = 1 and custum recovery or root?
dont think it is as simple as you say when you are knox = 1 with custum recovery or root.
hope your right. but i dont think so.
Click to expand...
Click to collapse
I've used Odin to go back to MJA a couple times with a tripped knox counter and custom recovery. It works every time. Why wouldn't it? It just doesn't reset the counter.
Sent from my Galaxy S4 using Tapatalk 4
xanaxdroid said:
I've used Odin to go back to MJA a couple times with a tripped knox counter and custom recovery. It works every time. Why wouldn't it? It just doesn't reset the counter.
Sent from my Galaxy S4 using Tapatalk 4
Click to expand...
Click to collapse
i would assume something is stripped from the MJA and MK2 we get for odin files
kies and ota definately do checks and WIPES better
for some reason the MJA and MK2 i been flashing (stock mja/mk2) on me no root or cust reoovery (knox = 0x0)
those files are not wiping like they should
why are we always having to do wipes 2 and 3x like alot of these instructions say????
something not right
anyhow yea usually i would think just odin over a stock and everything ok.
knox is wierd and i dont know alot about.
people are talking about OTA and KIES screwing their phones up
i see alot of diff stuff being posted and its moving fast.
why are we still having problems with rooting?
isnt cf-auto-root working 100% now for mja and mk2?
are both twrp and cwmr/philz working 100% as far as functioning correctly and not messing anything up in the rom or firmware they go on top of or happen to install with?
seems like alot of people in those channels/forums dont like talking about it to much.
i thin what i will do is stick with stock firmwares (rooted) and then disable the hands free activation and the android system update
then i will just keep those roms to restore to in case it gets bad
en11gma said:
i would assume something is stripped from the MJA and MK2 we get for odin files
kies and ota definately do checks and WIPES better
for some reason the MJA and MK2 i been flashing (stock mja/mk2) on me no root or cust reoovery (knox = 0x0)
those files are not wiping like they should
why are we always having to do wipes 2 and 3x like alot of these instructions say????
something not right
anyhow yea usually i would think just odin over a stock and everything ok.
knox is wierd and i dont know alot about.
people are talking about OTA and KIES screwing their phones up
i see alot of diff stuff being posted and its moving fast.
why are we still having problems with rooting?
isnt cf-auto-root working 100% now for mja and mk2?
are both twrp and cwmr/philz working 100% as far as functioning correctly and not messing anything up in the rom or firmware they go on top of or happen to install with?
seems like alot of people in those channels/forums dont like talking about it to much.
i thin what i will do is stick with stock firmwares (rooted) and then disable the hands free activation and the android system update
then i will just keep those roms to restore to in case it gets bad
Click to expand...
Click to collapse
Sorry I don't understand. Who's having trouble rooting? And that wipe 2 or 3 times stuff is bs. You only have to wipe once. As for the other stuff I don't know. All I know is my phone has worked fine and has never bricked. I don't use KIES either though and mostly run aosp roms.
Sent from my Galaxy S4 using Tapatalk 4
xanaxdroid said:
Sorry I don't understand. Who's having trouble rooting? And that wipe 2 or 3 times stuff is bs. You only have to wipe once. As for the other stuff I don't know. All I know is my phone has worked fine and has never bricked. I don't use KIES either though and mostly run aosp roms.
Sent from my Galaxy S4 using Tapatalk 4
Click to expand...
Click to collapse
i can verify the wiping/erasing from installing that mja or mk2 is not doing what it usually did with other fully stock rom
i think this phone has 2 firmwares and when you mod one the other one boots the next boot that is why you have to wipe it there too
there is DEFINATELY some double booting going on here
that is also why you tell cf-auto-root, twrp and cwmr NOT to reboot
pull battery and boot directly into recovery
i have had to do 2 and 3 wipes and its not just that
i was on mk2 firmware and i downflashed the modem to mdc
i had to reboot at desktop to get it to show in "about" settings
i then flashed the mk2 firmware (stock 2GB) and when i got in ui AGAIN it still showing MDC.....WTF???
ok so i boot into android recovery and wipe again and reboot and its now MK2
sometimes i just reboot and it will show it next time
its not just there either.
settings in ##3424# and *#9090# are also not getting erased with new official rom installs
really wierd stuff
yea i prob only used kies once in mylife and that was just to test it
usually im on CMnightly whatever is the latest
im not new and i most likely above avg on phone stuff
this KNOX stuff is wierd
even if you do an OTA the phone resets 2x during the install process and i think even with odin too
en11gma said:
i can verify the wiping/erasing from installing that mja or mk2 is not doing what it usually did with other fully stock rom
i think this phone has 2 firmwares and when you mod one the other one boots the next boot that is why you have to wipe it there too
there is DEFINATELY some double booting going on here
that is also why you tell cf-auto-root, twrp and cwmr NOT to reboot
pull battery and boot directly into recovery
i have had to do 2 and 3 wipes and its not just that
i was on mk2 firmware and i downflashed the modem to mdc
i had to reboot at desktop to get it to show in "about" settings
i then flashed the mk2 firmware (stock 2GB) and when i got in ui AGAIN it still showing MDC.....WTF???
ok so i boot into android recovery and wipe again and reboot and its now MK2
sometimes i just reboot and it will show it next time
its not just there either.
settings in ##3424# and *#9090# are also not getting erased with new official rom installs
really wierd stuff
yea i prob only used kies once in mylife and that was just to test it
usually im on CMnightly whatever is the latest
im not new and i most likely above avg on phone stuff
this KNOX stuff is wierd
even if you do an OTA the phone resets 2x during the install process and i think even with odin too
Click to expand...
Click to collapse
I let c.f. auto root reboot itself after odining to mk2 and it worked fine. And why are you mixing and matching firmwares and basebands? Also are you using "official" files or files that some guy with one post puts up? I'd say decide what you want to use and stick with it. Anyway good luck.
Sent from my Galaxy S4 using Tapatalk 4
random45 said:
...
Click to expand...
Click to collapse
Hey man. I wanted to let you know I appreciate the crap out of you doing this. The slow downloads are awful. However, I've flashed this .tar file twice now using 2 different version numbers of Odin and the phone boots up but hangs on the SAMSUNG screen. Not the very first boot screen that says samsung galaxy s4 but the next one that begins with the purple and blue swirl and turns into the samsung logo while the led pulses blue. The phone doesn't freeze per se, it just never moves beyond this screen. Unless it's supposed to take 20-30 minutes, which I doubt is the case. Did I possibly get a bad download?
FlowingAway said:
Hey man. I wanted to let you know I appreciate the crap out of you doing this. The slow downloads are awful. However, I've flashed this .tar file twice now using 2 different version numbers of Odin and the phone boots up but hangs on the SAMSUNG screen. Not the very first boot screen that says samsung galaxy s4 but the next one that begins with the purple and blue swirl and turns into the samsung logo while the led pulses blue. The phone doesn't freeze per se, it just never moves beyond this screen. Unless it's supposed to take 20-30 minutes, which I doubt is the case. Did I possibly get a bad download?
Click to expand...
Click to collapse
As with any rom when you first boot up, yes it's supposed to take a while. ("android is upgrading" in disguise maybe?)
Did you do a factory reset before booting up?
Let it do its thing for 10 min at least, and longer than that if you didn't factory reset. If it doesn't boot, then do a factory reset.
Sent from my SPH-L720 using Tapatalk
random45 said:
As with any rom when you first boot up, yes it's supposed to take a while. (android is upgrading in disguise maybe?)
Did you do a factory reset before booting up?
Let it do its thing for 10 min at least, and longer than that if you didn't factory reset. If it doesn't boot, then do a factory reset.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Just saw your reply, thank you. That was the one thing I didn't try. Right after I posted that last message I got into recovery (finally after 3 or 4 tries) and did the factory reset and it booted up perfectly! So handy having this file around. Thanks again for uploading.
I'm happy I found this post. I was able to help my friend with his phone. THANKS!
en11gma said:
i have been reading over and over if you try to flash an mk2 or mja over a rooted or custom recovery that you can brick the phone?
are you sure odin would flash this when it detects there is a knox = 1 and custum recovery or root?
dont think it is as simple as you say when you are knox = 1 with custum recovery or root.
hope your right. but i dont think so.
Click to expand...
Click to collapse
Just for reference, I just did this and it worked just fine. I downgraded the modem to MDC and had SACS installed on it, wifi was not working so did this and it works
i dont care about warranty -
its been over 10 minutes and im still on the yellow sprint screen
I understand that if your flash this MK2 tar you'll end up with the knox bootloader. But if someone wanted to get rid of knox, couldn't they just flash the MJA tar then re-root and update to an knox free MK2 firmware that unknownforce provided and you'd be all set?
LouRock said:
I understand that if your flash this MK2 tar you'll end up with the knox bootloader. But if someone wanted to get rid of knox, couldn't they just flash the MJA tar then re-root and update to an knox free MK2 firmware that unknownforce provided and you'd be all set?
Click to expand...
Click to collapse
There is no known method of removing the knox bootloader, to my knowledge.
I'm requesting someone find the Odin files to flash to an i537 model for KitKat 4.4.2, as I can't find it anywhere. If I can't, I'll go to Samsung at Best Buy and uh..... Ask for the Odin files(they use Odin there XD)
Please help as ODIN is the only way I have been able to update, OTAs fail and recovery install from cache, external SD fails. Everything but Odin fails, so anybody help?
Device details-
SGH-i537 AT&T running 4.3 Official Unrooted Stock
Thanks!!!
Have you tried flashing the 4.3 firmware then flashing the OTA? At this time I don't think they have released a full Odin 4.4.2
popfan said:
Have you tried flashing the 4.3 firmware then flashing the OTA? At this time I don't think they have released a full Odin 4.4.2
Click to expand...
Click to collapse
Yeah, I tried it all my friend, I need the Odin files.
yes i too in fact need the odin files asap. I know nobody likes being asked for ETA's but how long does it usually take to get the ODIN files?
jimmietilt said:
yes i too in fact need the odin files asap. I know nobody likes being asked for ETA's but how long does it usually take to get the ODIN files?
Click to expand...
Click to collapse
Considering we never got the Odin files for MF2 or MF3, we may never get Odin files for NC9.
Just do a hard reset (VOL+/HOME/POWER), boot your phone then do a Factory reset from within the phone with selecting format SD card option (back your stuff up!). Then go back, enable USB debugging and flash the stock ML2 firmware EXCEPT for the BL file! then re-enable USB debugging and download the 2400258.cfg file from here, rename it to update.zip and flash it via stock recovery, problem solved. As for the ODIN files, here's a good read on why @Devo7v is right with his assessment on not ever seeing them. More info on the stock SGH-i537 firmware here.
jkeuclid said:
Just do a hard reset (VOL+/HOME/POWER), boot your phone then do a Factory reset from within the phone with selecting format SD card option (back your stuff up!). Then go back, enable USB debugging and flash the stock ML2 firmware EXCEPT for the BL file! then re-enable USB debugging and download the 2400258.cfg file from here, rename it to update.zip and flash it via stock recovery, problem solved. As for the ODIN files, here's a good read on why @Devo7v is right with his assessment on not ever seeing them. More info on the stock SGH-i537 firmware here.
Click to expand...
Click to collapse
I tried that. Didn't work XD The only thing that works for me is forcing the update through ODIN.
Devildude24 said:
I tried that. Didn't work XD The only thing that works for me is forcing the update through ODIN.
Click to expand...
Click to collapse
How are you forcing the update through Odin? We don't have the Odin files for 4.4.2, so I'm not sure what you mean. Do you mean you can only flash the 4.3 files with Odin and you cannot get the cfg file to flash through stock recovery?
Devo7v said:
How are you forcing the update through Odin? We don't have the Odin files for 4.4.2, so I'm not sure what you mean. Do you mean you can only flash the 4.3 files with Odin and you cannot get the cfg file to flash through stock recovery?
Click to expand...
Click to collapse
Yes, sorry for the confusion. I forced 4.3 through ODIN and the cfg file doesn't work, in all possible ways. And it won't work when renamed to update.zip either.
Devildude24 said:
Yes, sorry for the confusion. I forced 4.3 through ODIN and the cfg file doesn't work, in all possible ways. And it won't work when renamed to update.zip either.
Click to expand...
Click to collapse
Did you check the MD5 to make sure that it downloaded properly? My suggestion would be to download it with a computer, rename it to "update.zip" on a computer, copy it to your internal memory on the phone, and flash it through stock recovery. This should work, what errors do you get when you try to flash it? You're on stock 4.3 when you try to update, correct? In order to flash the OTA you cannot be rooted or have modified the system in any way.
Devo7v said:
Did you check the MD5 to make sure that it downloaded properly? My suggestion would be to download it with a computer, rename it to "update.zip" on a computer, copy it to your internal memory on the phone, and flash it through stock recovery. This should work, what errors do you get when you try to flash it? You're on stock 4.3 when you try to update, correct? In order to flash the OTA you cannot be rooted or have modified the system in any way.
Click to expand...
Click to collapse
Good advice and I'll further add make sure when you rename the 2400258.cfg that you have known file extensions enabled and then right click and highlight the entire file "2400258.cfg" and then rename that to "update.zip"
Trust us, this will work.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
jkeuclid said:
Good advice and I'll further add make sure when you rename the 2400258.cfg that you have known file extensions enabled and then right click and highlight the entire file "2400258.cfg" and then rename that to "update.zip"
Trust us, this will work.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, I tried that. I tried everything, literally everything. Like Samsung told me they couldn't help me unless I sent it in. (Probably just send a replacement or do a full reset with a new partition and data)
Devildude24 said:
Yeah, I tried that. I tried everything, literally everything. Like Samsung told me they couldn't help me unless I sent it in. (Probably just send a replacement or do a full reset with a new partition and data)
Click to expand...
Click to collapse
I'm almost positive you're doing something wrong since you're the only one that is having this problem. I know @jkeuclid has already walked one person through this process step-by-step, I don't want to speak for him but he'd probably be willing to do the same for you.
Devo7v said:
I'm almost positive you're doing something wrong since you're the only one that is having this problem. I know @jkeuclid has already walked one person through this process step-by-step, I don't want to speak for him but he'd probably be willing to do the same for you.
Click to expand...
Click to collapse
Thank you. UPDATE-
I checked, my Baseband version and Build Number don't match.... MF1 vs. ML2. So that could be presenting some of the problem. I'm going to try to find a partition file for stick 4.3 then rehash everything through ODIN and attempt an update. Any other suggestions anyone?
Devildude24 said:
Thank you. UPDATE-
I checked, my Baseband version and Build Number don't match.... MF1 vs. ML2. So that could be presenting some of the problem. I'm going to try to find a partition file for stick 4.3 then rehash everything through ODIN and attempt an update. Any other suggestions anyone?
Click to expand...
Click to collapse
Did you ever figured this out? I'm having the same issue. Can't update using the cfg file.
Just my quess but the OP and others in this thread have possibly problem understanding relationship of Odin with Stock Recovery
If your phone is stock 4.3 and you have the 444 MB update renamed to update.zip already moved over to microSD card.....
See if this little video helps you
https://www.youtube.com/watch?v=B8TOJkBOZfs
Please Help
Devildude24 said:
I'm requesting someone find the Odin files to flash to an i537 model for KitKat 4.4.2, as I can't find it anywhere. If I can't, I'll go to Samsung at Best Buy and uh..... Ask for the Odin files(they use Odin there XD)
Please help as ODIN is the only way I have been able to update, OTAs fail and recovery install from cache, external SD fails. Everything but Odin fails, so anybody help?
Device details-
SGH-i537 AT&T running 4.3 Official Unrooted Stock
Thanks!!!
Click to expand...
Click to collapse
Please I need your help, I was trying to upgrade to 4.4 from 4.3 ML2, on i537, but when i did, I lost my wifi and camera and media, (I mean , I cant play any song, show me a message that cant play, "File not Suppoted') anyways, the help that I need is if you can help me with your stock rom, so I can flash my phone with your files, please. Im downgrade to 4.3 again and I used one backup that I did before upgrade, but still not work wifi and media, I already flashed the moden.bin from xda to fix wifi, but still not work, I want to try to flash a Real stock rom, and see what happen, cause Im very stress...
[SOLVED] Bricked i9305? - No Recovery - "Get PIT for mapping" stuck - sboot.bin FAIL
Yo.
Basically been using this phone for ages, having random freezing issues for a while, so I decided to /****it and re-stock everything because it is likely that I have been an idiot with kernels/messing around with stuff once.
This freezing has persisted through stable, unstable, nightly CM 10.2/10.3/11 ROM's as well as pure stock and unrooted, so I figured it was something deeper down - the kernel, and I got a stock kernel for i9305 (attached). Everything basically went to ****, the phone got stuck bootlooping on the initial Samsung logo, doing the button-combo to get into recovery just stucks it on that logo. I can enter Download mode.
No biggie, I'll just ODIN it up (3.0.7) and flash the stock firmware, except now (this did not happen before the kernel flash) it simply fails with "sboot.bin FAIL", which people claim to be a PIT error (Kies not open btw, no KiesTrayAgent either, it's on the PC though), so I grab a i9305 stock PIT that I try and flash with the stock firmware, except now it gets stuck at "Get PIT for mapping" and never moves onwards from there.
So I'm essentially stuck with a problem that can probably be fixed by a stock firmware ODIN flash, and a problem that prevents me from fixing the PIT stuff to get the stock firmware through.
I have tried ODIN-flashing CWM recovery as well as stock recovery (also attached), but I'm still stuck on the logo regardless.
Any help here? Kinda lost ATM.
EDIT: Can't link/attach the .rar with the files. :S
Just re-install your back up
Raistlin1158 said:
Just re-install your back up
Click to expand...
Click to collapse
Retarded answer.
@OP
We need more data... first, which kernel did you flash ? If you can't attach it, link to it.
Second, what stock rom did you try to flash ?
Third, are you knoxed?
Hey guys.
Cheers for the answers, I just figured it out though actually. The sboot.bin error was caused by some bootloader-stuff-thingy I could hardly explain if I got a book on it. I got ahold of another stock ROM which flashed fine, I cleaned up and all that (NAND erase all did the job), back to CM11 as TouchWiz didn't fix my problems.
To answer your questions (others might have the problem and find this thread):
http://forum.xda-developers.com/galaxy-s3/development-i9305/recovery-odin-flashable-tar-t1971265 <- kernel
I tried to flash an "XXBMD1" stock ROM from SamMobile, it had worked previously.
I am Knoxed and have "tripeed the fuse" (trying to fix the crashing issues I went back to stock ROM, then it prompted for the 4.3 TouchWiz update which brings KNOX), so I'm without warranty (ODIN returns "KNOX Warranty Void: 1), but I guess I can consider this a learning experience as everything turned out good enough in the end.
There you go:
Based on JellyBean 4.1.2_XXBMD1 <--- You can't flash 4.1.2 because of the knox bootloader.
Had you tried a stick 4.3 you might have been sucessfull
daedric said:
Retarded answer.
Click to expand...
Click to collapse
Hello...
Don't you do irony in your country,
only a moron would play about with his phone without making a back up first, but the point seems to have gone over your head as well... Durrr
Raistlin1158 said:
Hello...
Don't you do irony in your country,
only a moron would play about with his phone without making a back up first, but the point seems to have gone over your head as well... Durrr
Click to expand...
Click to collapse
soft bricks aren't fixed by restoring nandroids.
Update odin and change usb cable and port.
Raistlin1158 said:
Hello...
Don't you do irony in your country,
only a moron would play about with his phone without making a back up first, but the point seems to have gone over your head as well... Durrr
Click to expand...
Click to collapse
Apologies for not detecting the irony on your post.
Yet, what you wrote means you didn't even bother to read the OP. What good would a nandbackup do, if he cannot even get to recovery?
I take back the retarded and replace it with lazy.
chongc1996 said:
soft bricks aren't fixed by restoring nandroids.
Click to expand...
Click to collapse
A nandroid wouldn't do any harm as soon as he got a recovery working
Raistlin1158 said:
Update odin and change usb cable and port.
Click to expand...
Click to collapse
Again, OP second post not read. His issue was probably originating in a attempt to flash a stock 4.1 (with 4.1 bootloader) over a 4.3 bootloader. Knox won't allow it.
Add stubbornness to laziness.
@ OP: please change the [Q] in the op to [SOLVED]
daedric said:
Apologies for not detecting the irony on your post.
Yet, what you wrote means you didn't even bother to read the OP. What good would a nandbackup do, if he cannot even get to recovery?
I take back the retarded and replace it with lazy.
A nandroid wouldn't do any harm as soon as he got a recovery working
Again, OP second post not read. His issue was probably originating in a attempt to flash a stock 4.1 (with 4.1 bootloader) over a 4.3 bootloader. Knox won't allow it.
Add stubbornness to laziness.
@ OP: please change the [Q] in the op to [SOLVED]
Click to expand...
Click to collapse
heh, last time i soft bricked, i could access recovery like op, but nandroid didn't help. some other problem that flashing stock rom solved
.... the phone got stuck bootlooping on the initial Samsung logo, doing the button-combo to get into recovery just stucks it on that logo. I can enter Download mode.
Click to expand...
Click to collapse
chongc1996 said:
heh, last time i soft bricked, i could access recovery like op, but nandroid didn't help. some other problem that flashing stock rom solved
Click to expand...
Click to collapse
As you can see, OP could NOT get to recovery, only download. His fault was attempting to flash 4.1 with OLD BOOTLOADER on top of a 4.3 NEW BOOTLOADER.
daedric said:
As you can see, OP could NOT get to recovery, only download. His fault was attempting to flash 4.1 with OLD BOOTLOADER on top of a 4.3 NEW BOOTLOADER.
Click to expand...
Click to collapse
ok sir, you are right, calm down, I'm out of here.
Cheers for the helpful as well as not-so-helpful responses, all back up and running now.