I have a sgh-i337, I tried to format my rom and threw everything at it but the kitchen sink but could not get it cleared. Then I looked around and found out about the write protect issue on the bootloader from at&t and verizon. (chattr +i /boot/system.tar.md5) It's not difficult to figure out what they did.
Needless to say I am softbricked right now with all the user data deleted. I did back up in kies but it is asking me for a number I never saw.
Is there a patch for fixing the at&t immutable bit on the bootloader?
Is there a download that will help me launch my phonetop?
We know the bootloader and system files are just fine... :silly:
The boot loader is still locked. The stock kernel and recovery cannot be replaced.
The link to stock firmware is available in http://forum.xda-developers.com/showthread.php?t=2616221
You can use Odin to flash the stock firmware. You can flash the same or newer version only.
Related
Hello,
This is will be my first XDA post ever since I always fix the most "brickiest" problems with all the Android based devices I have ever owned but not this time.
My Galaxy S4 has been updated to the latest MJA OTA (with successful CF root) and I have attempted to re-mod the hotspot service but this caused the annoying knox message to show. When attempting to restore the JAR and ODEX files, I think I have either overwritten the files in the incorrect order (ODEX -> JAR) and the phone rebooted as FX was trying to do that. So services.odex got corrupted and it was time for my to ODIN flash the MDC full stock rom as that USED to be my solution until Samsung's brand new knox protected bootloader. ODIN is not an option for me now, since the bootloader will prevent me flashing things like the pit, aboot and probably most of the other files inside the tarball. I can flash custom recovery and the MDC kernel successfully and that's about it. With custom recovery I have flashed rooted MF8 for the base operating system, and they applied the rooted MJA rom on top. The phone shows the S4 branding but then it reboots; It cannot boot into the operating system. I do not know the condition of the flash counter atm since I cannot check that in TriangleAway but it will stay "Official" under download mode, I think. I also do not know the versions of the firmware installed either in case something from MDC tar had an succession in replace some of the partitions. I am pretty sure the kernel however is still at MDC while I managed to install the system image of the MJA stock rom.
So my question is, what can I do bring back the working MJA stock rom image (/system and kernel) using TWRP recovery? Else I will have to go to Sprint and saying that the update from OTA has bricked my phone and that I have no idea how phones work.
Thank you.
45553543 450
Sorry, I forgot to add that I know that once you have MJA flashed, you cannot downgrade back unless of course someone figured out how to disable all the bootloader security but I really do not see that happening.
Fixed my own problem. Downloaded the official MJA stock tar.md5 rom from sammobile and flashed it, and managed to restore all my data using Titanium backup. This thread can be now closed.
My S4 is the i9505 (i think I got that right) M919 T-Mobile Version. It is currently running on CyanogenMod 11 M10 (latest stable release). I saved the latest 4.4.4 firmware (from SamMobile) and extracted the Modem.bin and NON-HOLS.bin (hindsight, should have just flashed the Modem.bin). And now my sound doesn't work. (Note: I flashed two kernels afterwards, not realizing the problem, but I reverted with a nandroid backup and in the about phone, it is the stock kernel of Cyanogenmod, so I don't think that had an effect)
So now that my sound doesn't work, I searched and realized that the NON-HOLS requires the same version Bootloader to work, so I first tried flashing the bootloader from the file mentioned above (aboot,rpm,sbl1 - sbl3). But I go and check my bootloader afterwards and it says that it was still the old one even through the flash passed. Next, I tried the NON-HOLS that matched the version of my bootloader, but again, still nothing.
So now I think it is something with my S4 that is not letting me flash. My phone's bootloader is unlocked (T-Mobile), and I don't have the Knox counter (probably because I switch to CyanogenMod before the 4.3 update from Carrier). I don't know what I should do now.
Brinith said:
My S4 is the i9505 (i think I got that right) M919 T-Mobile Version. It is currently running on CyanogenMod 11 M10 (latest stable release). I saved the latest 4.4.4 firmware (from SamMobile) and extracted the Modem.bin and NON-HOLS.bin (hindsight, should have just flashed the Modem.bin). And now my sound doesn't work. (Note: I flashed two kernels afterwards, not realizing the problem, but I reverted with a nandroid backup and in the about phone, it is the stock kernel of Cyanogenmod, so I don't think that had an effect)
So now that my sound doesn't work, I searched and realized that the NON-HOLS requires the same version Bootloader to work, so I first tried flashing the bootloader from the file mentioned above (aboot,rpm,sbl1 - sbl3). But I go and check my bootloader afterwards and it says that it was still the old one even through the flash passed. Next, I tried the NON-HOLS that matched the version of my bootloader, but again, still nothing.
So now I think it is something with my S4 that is not letting me flash. My phone's bootloader is unlocked (T-Mobile), and I don't have the Knox counter (probably because I switch to CyanogenMod before the 4.3 update from Carrier). I don't know what I should do now.
Click to expand...
Click to collapse
I would flash the full stock 4.2.2 .tar file in Odin from SamMobile. You should still be able to do that because you never upgraded to 4.3 with the knox protections.
That should restore your bootloader and modem back to exactly what it was when you bought the phone, overwriting the mismosh blend of 4.2 bootlaoder with 4.4 firmware parts.
You MAY have to flash it twice in Odin to get it to stick. Sometimes that's an issue when you try to use Odin to overwrite non stock firmware.
Once you get it flashed boot it and make sure it works properly in TouchWiz.
If it does, then go right back to Odin and flash whatever recovery you want to use and from there you should be able to flash whatever you want in recovery like normal.
You should NOT have to extract and push any audio files to make CM11 work like you said started this problem. That should not be a thing. I've still got the 4.2 bootloader and I'm running the latest CarbonROM (an offshoot of CM) and everything works fine. So something else must have been screwy to start.
Skipjacks said:
I would flash the full stock 4.2.2 .tar file in Odin from SamMobile. You should still be able to do that because you never upgraded to 4.3 with the knox protections.
That should restore your bootloader and modem back to exactly what it was when you bought the phone, overwriting the mismosh blend of 4.2 bootlaoder with 4.4 firmware parts.
You MAY have to flash it twice in Odin to get it to stick. Sometimes that's an issue when you try to use Odin to overwrite non stock firmware.
Once you get it flashed boot it and make sure it works properly in TouchWiz.
If it does, then go right back to Odin and flash whatever recovery you want to use and from there you should be able to flash whatever you want in recovery like normal.
You should NOT have to extract and push any audio files to make CM11 work like you said started this problem. That should not be a thing. I've still got the 4.2 bootloader and I'm running the latest CarbonROM (an offshoot of CM) and everything works fine. So something else must have been screwy to start.
Click to expand...
Click to collapse
Would a nandroid backup save the bootloader. I was thinking of installing the stock rom and then using the backup to revert to CyanogenMod.
Damn I flashed the stock ROM (pre 4.3) and I still got KNOX. Now it says "System software not authorized by Samsung has been found on your phone"
What should I do?
EDIT: I flashed the latest 4.4.4 Stock ROM since I already got KNOX (T_T, oh well warranty already over)
But what is the deal with the warning (shown above) and is there any way to prevent it from happening again other than reverting to stock everytime I want to flash something?
Brinith said:
Would a nandroid backup save the bootloader. I was thinking of installing the stock rom and then using the backup to revert to CyanogenMod.
Click to expand...
Click to collapse
No. The bootloader is not packaged with a nandroid.
And you do not need to mess with the bootloader. Just get it working and leave your bootloader alone forever.
---------- Post added at 03:56 PM ---------- Previous post was at 03:54 PM ----------
Brinith said:
Damn I flashed the stock ROM (pre 4.3) and I still got KNOX. Now it says "System software not authorized by Samsung has been found on your phone"
What should I do?
EDIT: I flashed the latest 4.4.4 Stock ROM since I already got KNOX (T_T, oh well warranty already over)
But what is the deal with the warning (shown above) and is there any way to prevent it from happening again other than reverting to stock everytime I want to flash something?
Click to expand...
Click to collapse
Are you sure its knox? Knox doesnt say that. Knox says 00x01 in the download screen.
Where are you seeing that message?
Skipjacks said:
No. The bootloader is not packago$h a nandroid.
And you do not need to mess with the bootloader. Just get it working and leave your bootloader alone forever.
---------- Post added at 03:56 PM ---------- Previous post was at 03:54 PM ----------
Are you sure its knox? Knox doesnt say that. Knox says 00x01 in the download screen.
Where are you seeing that message?
Click to expand...
Click to collapse
Im not sure if its Knox,but Knox is definitely now installed onto my phone. (KNOX warrenty void 0x1). Oh well my warranty is over so i don't really mind. But still, i want to know what that error (in above post) was as it didn't let me boot or go into recovery and only worked again once I reflashed.
And the reason why i flashed was that people say that updating the modem.bin and NON-HLOS would improve cell reception, and such. Which so far seems to be true, getting better signal in general (for wifi, uped by 10db than before so pretty significant), since i just flashed 4.4.4 for updated bootloader and modem since i already have Knox now.
i need help for my s4 gt-i9505
Hey folks. I'm finding a lot of threads from 2 years ago and unfortunately they aren't much help with my device. I've inherited this phone, and my goal is to upgrade to CM12. Unfortunately I'm dealing with AT&T's locked bootloader and other issues.
I'm currently on Android 4.4.4, Baseband I337UCUFNJ4. I've managed to get root access using the Odin method of flashing NC1 then back to NJ4, root is working., but I've been unable to flash an updated Recovery. I've tried everything except for the Safestrap method, which last I read wouldn't work for installing Cyanogenmod. Using Odin, I've tried to flash CWM Recovery after converting the .img to a .tar.md5 (Odin failed to transfer this), I've tried using ROM Manager to install Recovery (claimed to work, but actually did nothing), then also used Flashify and Rashr to flash, which seemed to get further, but upon reboot the phone gave an error about software not authorized by AT&T.
I've done way too much googling this weekend and trying all sorts of things that haven't worked, from all sorts of threads from 2013 and 2014, does anyone have a reliable method that works if I'm already on 4.4.4, or am I still out of luck with this device? There is no SIM in the phone right now, but I may want to use it as a phone later if I can upgrade to CM12.
You're pretty much stuck. Only ROMs you can flash are AT&T official stock ROMs for the S4, or ROMs that are specifically safestrap-compatible. No other recovery will work, either.
That being said, if you're interested in lollipop, there's a stock, deodexed lollipop ROM for our phone that is safestrap-compatible on here called Goldeneye v53 that I enjoy.
Sent from my SGH-I337 using Tapatalk
I'm in the same situation as you, I ended up using safestrap with Pure Nexus http://forum.xda-developers.com/galaxy-s4-att/development/rom-google-edition-s4-t2837239
Closest I could get to a desirable phone without original Samsung FW. Good luck
Hmmm. What I'm wondering at this point is how does the bootloader get onto the device originally? Can't a working bootloader from another model S4 be flashed in place of the AT&T one?
I would imagine that there must be some software that can be used to fully wipe the phone, repartition the memory, write a new bootloader, etc. If a phone were hard bricked, it would seem that there would be a way that Samsung or some carrier can use to get the phone working again.
I hit on UPDATE on the phone for an OTA update but it only says UNABLE TO CONNECT AT&T SERVER. When I bought it, it had 5.0.1 (I337UCUGOC3) out of the box. Searching on internet says that is bootloader locked (so I cant do anything).
- Can I Update to I337UCUGOK2 and bootloader will be unlocked (I mean, will I be able to do it)?
- Does anyone know where can I grab I337UCUGOK2 for offline install and is it ODIN safe to update it (remember I have I337UCUGOC3 bootloader locked)?
please help
Once the bootloader is locked, it will always be locked until someone finds a way to unlock it. Updating the bootloader will not allow it to be unlocked.
cybercuate said:
I hit on UPDATE on the phone for an OTA update but it only says UNABLE TO CONNECT AT&T SERVER. When I bought it, it had 5.0.1 (I337UCUGOC3) out of the box. Searching on internet says that is bootloader locked (so I cant do anything).
- Can I Update to I337UCUGOK2 and bootloader will be unlocked (I mean, will I be able to do it)?
- Does anyone know where can I grab I337UCUGOK2 for offline install and is it ODIN safe to update it (remember I have I337UCUGOC3 bootloader locked)?
please help
Click to expand...
Click to collapse
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.
help... I want to RMA it
sway8966 said:
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.
Click to expand...
Click to collapse
Everywhere says I need a kitkat rom as base.
My s4 came with 5.0.1 with OC3 and bootloader locked out of the box. I tried some post where says I can flash TWRP and CWM but my phone stucked on bootloops. Then I managed to get back to stock rom and now when I want to turn it on it says " SAMSUNG (and lower on the screen) Custom"
Camera began to fail and I want to return it as RMA but I was looking to reset the flash counter but every post I read is that OC3 bootloader locked users are just doomed.
Do you know a method that I can do for reset that counter?
Camera dont focus anymore and I tried all the posts about safemode, etc.
cybercuate said:
Everywhere says I need a kitkat rom as base.
My s4 came with 5.0.1 with OC3 and bootloader locked out of the box. I tried some post where says I can flash TWRP and CWM but my phone stucked on bootloops. Then I managed to get back to stock rom and now when I want to turn it on it says " SAMSUNG (and lower on the screen) Custom"
Camera began to fail and I want to return it as RMA but I was looking to reset the flash counter but every post I read is that OC3 bootloader locked users are just doomed.
Do you know a method that I can do for reset that counter?
Camera dont focus anymore and I tried all the posts about safemode, etc.
Click to expand...
Click to collapse
Flashing TWRP and CWM is for the AT&T S4 with older bootloader (MDL, MDB). After that two firmware versions the bootloader is locked.
For AT&T S4 the last full firmware released is NB1. After that they released incremental updates via OTA. That is why you need kitkat (NB1) as base.
For NB1, Muniz uploaded two firmwares. One is the stock and the other is rootable stock. Try the stock one and see you still have the custom symbol.
To reset the counter, there is an app calls Triangle away by Chainfire. However, it does not work on AT&T S4 with locked bootloader.
Trying Odin-Stock NB1
sway8966 said:
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.
Click to expand...
Click to collapse
sway8966 said:
Flashing TWRP and CWM is for the AT&T S4 with older bootloader (MDL, MDB). After that two firmware versions the bootloader is locked.
For AT&T S4 the last full firmware released is NB1. After that they released incremental updates via OTA. That is why you need kitkat (NB1) as base.
For NB1, Muniz uploaded two firmwares. One is the stock and the other is rootable stock. Try the stock one and see you still have the custom symbol.
To reset the counter, there is an app calls Triangle away by Chainfire. However, it does not work on AT&T S4 with locked bootloader.
Click to expand...
Click to collapse
Thanks. I'll try Odin it with the stock rom from your link. I'll post news here when it finish flashing
1st part - Success
I'm on 4.4.2 NB1, flash counter back to normal but still bootloader locked
Now I have to go back to OC3 to RMA it.
OTA does nothing, smartswitch shows no updates neither kies.
I'll have to Odin it back to OC3
Can I have some help?
And Success. I'm back on stock OC3 no root.
time to RMA
- camera still doesn't focus
- boot screen is back to normal but when in odin mode the counter shows 0x1
- sometimes shows "sim card could not be detected" or similar messages and force me to restart the phone (just happend 2 times until now, never happend before)
I followed this thread
http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
Post 2
Thanks to sway8966
This phone has been such a pain in the ass. My s4 was easy and my sprint s5 was cake to work with. This VZW s5 has been a royal headache.
Im living in a homeless shelter so I really dont wanna end up softbricked overnight before I can try to fix it at the library the next day.
Iam currently downloading a Deodexed/Debloted PF4 Rom for my VZW phone, got it on droidviews, PM me for the link it wont let me post it
So it looks like it has you use flashfire to install the rom and then has you Odin the proper Bootloader. Is this going to work for me?
When I was rooting the phone it had me messing with different kernals and stuff so I just wanted some clarification or something if anybody can provide some.
Thanks,
Raedon
I have both the Roms. The one for the unlocked bootloader and the locked one as well. Is there any easy way to see if my bootloader is unlocked?
Im pretty tech savvy but this **** is ridiculous.
Boot to download mode if you see a line that says developer mode you are bootloader unlocked
Sent from my SM-G900F using Tapatalk
In download mode it looks like my bootloader is locked. Is installing MM as simple as flashing the rom with flashfire and then flashing the new bootloader in odin?
Sounds like cake for real.
Yes you can install it in flash fire by having the firmware on your device then open flash fire app and click plus symbol in bottom right corner and choose flash firmware and choose the firmware let it check md5
then make sure inject su or root is off
Then click flash
You will lose root if you flash an official mm firmware and there is no way to root mm
Well I softbricked my phone and Im boned until tomorrow. I followed the instructions in the thread
"[How-To] Update to G900V_PF4 - 6.0.1"
It says at the top "**You can begin the following process from any Build/ROM but you must already have Root Access**"
You have to be rooted since it requires FlashFire. I downloaded the locked bootloader version since my bootloader is still locked. Followed all the directions and ended up stuck on the samsung screen. I have 40 minutes to try and fix this until Im stuck all night.
Im just gonna try to put the stock factory PB1 back on with the PB1 bootloader. Id love to get this 6.0.1 on my phone tomorrow tho
Boot to recovery and wipe data and cache
Sent from my SM-G900F using Tapatalk