Should updating a phone to the PacRom kitkat 4.4 based system be blocking unlocking a phone from the carrier? Or should it have nothing to do with that?
I have a samsung galaxy s1/captivate i897 which I first updated with PacROM to kitkat 4.4 to be sure it would work first, and then got the unlock code from AT&T - i've tried it three times and it's failed now 3 out of 5 before it bricks apparently. Does being on PacROM have anything to do with it/is it a general thing that custom roms will block this? Or should it have nothing to do with it? (if it should have nothing to do with it and sounds like an error i'll post the specific info, this was just a more general question)
unit_shifter said:
Should updating a phone to the PacRom kitkat 4.4 based system be blocking unlocking a phone from the carrier? Or should it have nothing to do with that?
I have a samsung galaxy s1/captivate i897 which I first updated with PacROM to kitkat 4.4 to be sure it would work first, and then got the unlock code from AT&T - i've tried it three times and it's failed now 3 out of 5 before it bricks apparently. Does being on PacROM have anything to do with it/is it a general thing that custom roms will block this? Or should it have nothing to do with it? (if it should have nothing to do with it and sounds like an error i'll post the specific info, this was just a more general question)
Click to expand...
Click to collapse
You'll have to go back to stock touchwiz first and use the unlock code there. After that you should be ok.
Nick0703 said:
You'll have to go back to stock touchwiz first and use the unlock code there. After that you should be ok.
Click to expand...
Click to collapse
Do I have to mess around with that TriangleAway stuff to reset the how-many-times-updated counter? (which doesnt list the S1 as compatible anyways, so....) Or just stock firmware, unlock, then go back to kitkat and I should be fine for life?
unit_shifter said:
Do I have to mess around with that TriangleAway stuff to reset the how-many-times-updated counter? (which doesnt list the S1 as compatible anyways, so....) Or just stock firmware, unlock, then go back to kitkat and I should be fine for life?
Click to expand...
Click to collapse
No, you don't need to mess with the TriangleAway. Just flash stock firmware with the .pit file on Odin3, use your unlock code then flash back to kitkat.
Related
Is it possible to modify a carrier OTA (lets say change the stock kernel with custom) before pushing it to your device via TWRP recovery??
(reason, i hear the Knox bootloader cannot be removed in TW 4.3 update because the kernel depends on it. And id like to flash the OTA instead of full odin image to avoid full wipe and re-installation)
Any help appreciated, and thanks in advance
Anyone? Bump
I know there is a lot of talent in here..
Xdenwarrior said:
Is it possible to modify a carrier OTA (lets say change the stock kernel with custom) before pushing it to your device via TWRP recovery??
(reason, i hear the Knox bootloader cannot be removed in TW 4.3 update because the kernel depends on it. And id like to flash the OTA instead of full odin image to avoid full wipe and re-installation)
Any help appreciated, and thanks in advance
Click to expand...
Click to collapse
I believe it is not possible to change the direct OTA zip as it's not in the same format as usual ROM zips. If you have a real custom recovery and exploit, you'll have to wait for a modified update to install 4.3, or run a custom 4.3 ROM from the development section or check the other S4 forums (i9505 may have one).
DeadlySin9 said:
I believe it is not possible to change the direct OTA zip as it's not in the same format as usual ROM zips. If you have a real custom recovery and exploit, you'll have to wait for a modified update to install 4.3, or run a custom 4.3 ROM from the development section or check the other S4 forums (i9505 may have one).
Click to expand...
Click to collapse
Well how do I modify the update?? Not interested in custom roms really since they get rid of like all Samsung stuff, which is what Galaxy S4 is all about. (I can't stand pure nexus experience - so dull and boring)
Xdenwarrior said:
Well how do I modify the update?? Not interested in custom roms really since they get rid of like all Samsung stuff, which is what Galaxy S4 is all about. (I can't stand pure nexus experience - so dull and boring)
Click to expand...
Click to collapse
Like I said, I don't believe it is possible. There are plenty of ROMS that do keep the Samsung stuff, such as StockUp and other ROMS in the i9505 section.
DeadlySin9 said:
Like I said, I don't believe it is possible. There are plenty of ROMS that do keep the Samsung stuff, such as StockUp and other ROMS in the i9505 section.
Click to expand...
Click to collapse
um, ok. Didnt really get what you meant by wait for modified update, or run custom 4.3 ROM which i believe is essentially same thing unless you mean someone takes the original mk6 odin image and modifies it. But us Canadians don't need an exploit, since carriers don't lock bootloaders
Xdenwarrior said:
um, ok. Didnt really get what you meant by wait for modified update, or run custom 4.3 ROM which i believe is essentially same thing unless you mean someone takes the original mk6 odin image and modifies it. But us Canadians don't need an exploit, since carriers don't lock bootloaders
Click to expand...
Click to collapse
This update is ONLY for ATT I337 phones. You will damage your phone if you push this update to your I337M phone. Do not do it unless you are developer and you can create your onw rom.
Follow this thread : http://forum.xda-developers.com/showthread.php?t=2535801
What is the difference between devices hltetmo and hltecan? I have a hltecan. Will we need CyanogenMod compiled for hltecan? I notice that recoveries have different versions for both devices. Also I am wondering about downgrading for 4.4 (when it comes) to 4.3. Is there a surefire way to upgrade and downgrade between 4.4 TW 4.4 CM and 4.3TW? I would not mind voiding my Knox counter. Just worried about being stuck or getting a brick for another 21 months on contract :silly:
jtl999 said:
What is the difference between devices hltetmo and hltecan? I have a hltecan. Will we need CyanogenMod compiled for hltecan? I notice that recoveries have different versions for both devices. Also I am wondering about downgrading for 4.4 (when it comes) to 4.3. Is there a surefire way to upgrade and downgrade between 4.4 TW 4.4 CM and 4.3TW? I would not mind voiding my Knox counter. Just worried about being stuck or getting a brick for another 21 months on contract :silly:
Click to expand...
Click to collapse
you cant downgrade if you want cm you have to stay on 4.3 for now
jaythenut said:
you cant downgrade if you want cm you have to stay on 4.3 for now
Click to expand...
Click to collapse
Sigh. I would do anything to be able to upgrade and downgrade between versions. Even Knox counter. If anyone finds something let me know
jtl999 said:
Sigh. I would do anything to be able to upgrade and downgrade between versions. Even Knox counter. If anyone finds something let me know
Click to expand...
Click to collapse
I played around a bit earlier... The only firmware you can upgrade to 4.4.2 and downgrade back to 4.3 is the mexican telco one for the n900w8, however I had some issues but will play some more tomorrow when I get time. As for KNOX, it's just one of them things we have to live with I'm afraid..
EDIT: I'm gonna mess with the bootloader and see, doubt it can be matched/mixed to work with the N9005 but what's the harm in trying.
radicalisto said:
I played around a bit earlier... The only firmware you can upgrade to 4.4.2 and downgrade back is the mexican telco one for the n900w8, however I had some issues but will play some more tomorrow when I get time. As for KNOX, it's just one of them things we have to live with I'm afraid..
Click to expand...
Click to collapse
Please try with Telus firmware please. Currently on MJ1
radicalisto said:
I played around a bit earlier... The only firmware you can upgrade to 4.4.2 and downgrade back to 4.3 is the mexican telco one for the n900w8, however I had some issues but will play some more tomorrow when I get time. As for KNOX, it's just one of them things we have to live with I'm afraid..
EDIT: I'm gonna mess with the bootloader and see, doubt it can be matched/mixed to work with the N9005 but what's the harm in trying.
Click to expand...
Click to collapse
The harm in trying is a hardbrick.
Well yes there is that, however I am not overly fussed about it, as most HB's can be revived. I am aware of all the risks, so will be my fault 100% if I brick myself.
I upgraded my note 3 yesterday to android 4.4 with cm 11, using the probam rom.
I noticed that it lacked the s pen features, so i downgraded back to stock rom.
Download a stock rom and flash it trough twrp
Sent from the Android beast: Galaxy Note 3
Rajito said:
I upgraded my note 3 yesterday to android 4.4 with cm 11, using the probam rom.
I noticed that it lacked the s pen features, so i downgraded back to stock rom.
Download a stock rom and flash it trough twrp
Sent from the Android beast: Galaxy Note 3
Click to expand...
Click to collapse
Flash a tar.md5 through twrp? What version of the stock rom?
Did you have the new bootloader?
Rajito said:
I upgraded my note 3 yesterday to android 4.4 with cm 11, using the probam rom.
I noticed that it lacked the s pen features, so i downgraded back to stock rom.
Download a stock rom and flash it trough twrp
Sent from the Android beast: Galaxy Note 3
Click to expand...
Click to collapse
CM is based on MJ/MK Bootloader. You could run Android 9.6 and it'd make no difference. It's all about the bootloader
radicalisto said:
CM is based on MJ/MK Bootloader. You could run Android 9.6 and it'd make no difference. It's all about the bootloader
Click to expand...
Click to collapse
Sorry. Can't understand exactly. What exactly means what versions you can run with a new bootloader?
MJ7 is the bootloader that powers CM currently. You need a bootloader to be able to boot into the operating system. Like a key into the phone.
If you upgrade your bootloader to a newer version aka NA6 it locks the phone. Therefore anything that runs lower than NA6 aka MJ7 won't work.
Think of it like, you broke your door, you got a new door and tried to use the old key. It no long works.
Sent from my SM-N9005 using XDA Premium 4 mobile app
radicalisto said:
MJ7 is the bootloader that powers CM currently. You need a bootloader to be able to boot into the operating system. Like a key into the phone.
If you upgrade your bootloader to a newer version aka NA6 it locks the phone. Therefore anything that runs lower than NA6 aka MJ7 won't work.
Think of it like, you broke your door, you got a new door and tried to use the old key. It no long works.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I know how bootloaders work. Isn't there a way to omit bootloaders from Odin tar.md5 updates? Once I/Someone figures that out I'm golden staying with my old bootloader. Currently on MJ1.
jaythenut said:
you cant downgrade if you want cm you have to stay on 4.3 for now
Click to expand...
Click to collapse
hi, can you elaborate?
i always thought samsung doesn't let you downgrade to an older bootloader. but if you install CM (not samsung official updates) the bootloader doesn't get updated so you can downgrade in the future.
unless you upgrade to 4.4.2 official samsung ROM and update the bootloader, then you'll never be able to downgrade again?
jtl999 said:
Flash a tar.md5 through twrp? What version of the stock rom?
Did you have the new bootloader?
Click to expand...
Click to collapse
No, if you want to try out kitkat i recommend you to use a cyanogenmod based 4.4 like probam, it doesn't update your bootloader and you can just downgrade back to jellybean
Sent from the Android beast: Galaxy Note 3
I've been wanting to have Android 4.4.2 on my Note 3 N9005 for a long time and my Carrier still hasn't released official 4.4 update. I've had enough waiting and want to root and install a custom 4.4 rom on my Note 3 N9005(international). Would anyone be so kind to give me detailed information on how to do so, or at least point me in the right direction. I've also got a few questions.
1. Is there any way to leave Knox not tripped?
2. Is there any way to downgrade from a custom ROM to my official 4.3 rom if I'll need my garrancy?
Thanks in advance! :fingers-crossed:
markslo112 said:
I've been wanting to have Android 4.4.2 on my Note 3 N9005 for a long time and my Carrier still hasn't released official 4.4 update. I've had enough waiting and want to root and install a custom 4.4 rom on my Note 3 N9005(international). Would anyone be so kind to give me detailed information on how to do so, or at least point me in the right direction. I've also got a few questions.
1. Is there any way to leave Knox not tripped?
2. Is there any way to downgrade from a custom ROM to my official 4.3 rom if I'll need my garrancy?
Thanks in advance! :fingers-crossed:
Click to expand...
Click to collapse
On N9005 there is no way back. Knowing that you must really analyze the benefits vs losses/risks. Which for instance for me at this point do not justify the move (but I am rooted and I already have 99% of what 4.4 brings).
xclub_101 said:
On N9005 there is no way back. Knowing that you must really analyze the benefits vs losses/risks. Which for instance for me at this point do not justify the move (but I am rooted and I already have 99% of what 4.4 brings).
Click to expand...
Click to collapse
Are you suggesting that I should stay on my stock ROM and wait for 4.4? I've read things about 4.4 and a lot of people say it's a lot better than 4.3, faster, etc. I'm really tired of waiting, my carrier sucks.
If you just want to have 4.4.2 and stay official, pick one of any released official 4.4.2 firmwares available to flash.
Spoon feeding at it's finest...
Sent from my N9005
nlatifolia said:
If you just want to have 4.4.2 and stay official, pick one of any released official 4.4.2 firmwares available to flash.
Click to expand...
Click to collapse
Alright, but do I need to be rooted or do I need to have a custom recovery before flashing via Odin? Will flashing an official ROM trigger Knox to 0x1 or will it leave it unchanged because I don't want my garrancy void?
@markslo112 you don't need nothing but your phone, usb cable and pc to flash with odin. Flashing an offcial rom will NOT trigger Knox!
Sent from Note 3 Superphone!
ione2380 said:
@markslo112 you don't need nothing but your phone, usb cable and pc to flash with odin. Flashing an offcial rom will NOT trigger Knox!
Sent from Note 3 Superphone!
Click to expand...
Click to collapse
Ok that's good to hear. If I flash 4.4, will I still be able to install a custom recovery and then a custom Rom? I'm just asking because if I get tired of stock 4.4. Also, is it safe to flash via Odin? I don't want my phone to get bootloops or anything.
Thanks!
I think before you do anything to your phone for the good of yourself you better stop posting and do more reading instead in this forum. You will confuse yourself by asking more and seems not knowing what you are asking about.
markslo112 said:
Ok that's good to hear. If I flash 4.4, will I still be able to install a custom recovery and then a custom Rom? I'm just asking because if I get tired of stock 4.4. Also, is it safe to flash via Odin? I don't want my phone to get bootloops or anything.
Thanks!
Click to expand...
Click to collapse
You will be able to install custom recovery/rom but it will trip your knox.
It is safe but do some reading maybe even watching a video or two on youtube to familiarize yourself on which files goes to which slot. Also, you won't be able to roll back to 4.3 at this time once you go to 4.4.
nlatifolia said:
I think before you do anything to your phone for the good of yourself you better stop posting and do more reading instead in this forum. You will confuse yourself by asking more and seems not knowing what you are asking about.
Click to expand...
Click to collapse
Well I've actually rooted and installed custom ROMS on almost every other phone I had, but the Note 3 is far the best mobile I've had and I really don't want to screw anything up. I do have experience with Odin, but I've never had any experience with Knox as no other phones had it. But I will go ahead and read stuff up.
Thanks to everyone that helped though! :fingers-crossed:
UPDATE:
Alright, so I tried flashing an official 4.4.2 firmware for my region onto my Note 3 with 4.3 via Odin 3.09. It started perfectly, but then gave me an error which said "invalid ext4 image". After a long search I did manage to find a PIT file for my phone. I then tried flashing again, but this time with the PIT file that I downloaded. It flashed fine, had to factory reset and wipe cache also. :victory:
I've spent hours searching and I know this is an old phone. Is ther anyway to root the Lollipop and download Jelly Bean (custom or stock) to it? I'm not worried about Warranties. I'm not exactly a newb and I don't like Lollipop at all. I don't mind KitKat, but what I hate is the front facing camera can't be flipped. Dumbest thing ever.
http://forum.xda-developers.com/galaxy-s4-sprint
Search for CF-Autoroot.
Strephon Alkhalikoi said:
http://forum.xda-developers.com/galaxy-s4-sprint
Search for CF-Autoroot.
Click to expand...
Click to collapse
I'm supposedly rooted. I used KingRoot and then switched over yo SuperSU. But I can't seem to get the Rom's to install. This is where I'm probably going wrong. I'm assuming it has to do with the Bootloader.
BikerSk8rKid said:
I'm supposedly rooted. I used KingRoot and then switched over yo SuperSU. But I can't seem to get the Rom's to install. This is where I'm probably going wrong. I'm assuming it has to do with the Bootloader.
Click to expand...
Click to collapse
Ask the right questions if you want the right answer.
You said you're not a newb. So what exactly was the procedure used to to install those ROMs?
Well, you should be using CF-Autoroot, as it's the recommended method to root these devices. That said, unless you have a frankenphone, only AT&T and Verizon models have locked bootloaders. Enter download mode and verify your device's model number please?
GDReaper said:
Ask the right questions if you want the right answer.
You said you're not a newb. So what exactly was the procedure used to to install those ROMs?
Click to expand...
Click to collapse
I was half asleep and stressed out when I posted this. It's been a couple weeks or longer since I messed with the phone. Damn forums weren't resetting my password. When I mean I'm not a newb I mean I'm not like brand new to this and I know how to research. I guess you could say I'm not THAT stupid. haha
I'mma have to try this again and figure out what path's I kept trying. I'm so spaced out I can't remember hard any of it. Just that I tried to flash a stock and rooted rom with old odin and new odin. Spent 2 days straight messing with it and trying to get around it. But I kept getting blocked. I didn't come across CF-Autoroot. So I'll try that.
Strephon Alkhalikoi said:
Well, you should be using CF-Autoroot, as it's the recommended method to root these devices. That said, unless you have a frankenphone, only AT&T and Verizon models have locked bootloaders. Enter download mode and verify your device's model number please?
Click to expand...
Click to collapse
Of all the researching I've done (I couldn't login) that one never showed up in my searchs. haha I'll have to give that one a try. It's been a couple weeks or longer. SPH-L720. I had a few Tri-Bands, but it seemed those were limited compared to the standard model.
Update: I went the CF-AutoRoot route and then tried to use Odin to flash stock mk2 rom. Now that I remember it kept failing everytime and then it would corrupt the current rom. I also tried using TWRP and couldn't get it to work properly.
That's a Sprint device, so your bootloader is unlocked.
Here's something you should note: If you want to flash a ROM, of any kind, you don't necessarily have to be rooted.
Stock ROMs require Odin and custom ROMs require a custom recovery. None of them require root.
Your flash to an older version fails most probably due to the fact that you're trying to downgrade the bootloader (Any stock ROM flash also modifies the bootloader and modem partitions).
But your windows, cable, USB port and windows can also be at fault here.
GDReaper said:
That's a Sprint device, so your bootloader is unlocked.
Here's something you should note: If you want to flash a ROM, of any kind, you don't necessarily have to be rooted.
Stock ROMs require Odin and custom ROMs require a custom recovery. None of them require root.
Your flash to an older version fails most probably due to the fact that you're trying to downgrade the bootloader (Any stock ROM flash also modifies the bootloader and modem partitions).
But your windows, cable, USB port and windows can also be at fault here.
Click to expand...
Click to collapse
For some reason I kept reading that it was locked or thinking it was locked because of not being able to downgrade.
So that's what I thought and I guess that's what I was trying to get at in my first post. Trying to go from Lollipop 5 to Jelly Bean 4.3 or so. Is it possible to do that whether it's custom or not?
I just hate the Lollipop and the KitKat. My Galaxy S2 had the JB and Power Button took a crap. So I ended up getting a S3 and now been sitting on an S4.
I know it's not the cable or at least it shouldn't be because it works to flash the stock current rom everytime I corrupt it. The computer is like brand new and running Windows 8.1
BikerSk8rKid said:
For some reason I kept reading that it was locked or thinking it was locked because of not being able to downgrade.
So that's what I thought and I guess that's what I was trying to get at in my first post. Trying to go from Lollipop 5 to Jelly Bean 4.3 or so. Is it possible to do that whether it's custom or not?
I just hate the Lollipop and the KitKat. My Galaxy S2 had the JB and Power Button took a crap. So I ended up getting a S3 and now been sitting on an S4.
I know it's not the cable or at least it shouldn't be because it works to flash the stock current rom everytime I corrupt it. The computer is like brand new and running Windows 8.1
Click to expand...
Click to collapse
Downgrading sometimes succeeds. There are also guides on how to downgrade, though there aren't any special procedures. Maybe the bootloader version of the firmware-to-be-flashed matters.
With custom ROMs it's definitely possible, as they do not change the bootloader.
GDReaper said:
Downgrading sometimes succeeds. There are also guides on how to downgrade, though there aren't any special procedures. Maybe the bootloader version of the firmware-to-be-flashed matters.
With custom ROMs it's definitely possible, as they do not change the bootloader.
Click to expand...
Click to collapse
I guess I'm more of a newb with this than I expected. :/ It's been years since I've been on the forums or even tinkered with phones. HTC Touch Pro 2 was the last one I believe. haha
So... With that being said. Custom Roms are typically to the current stock rom, correct? or is it possible to get a Custom Jelly Bean and flash/overwrite it to the Lollipop/current? Since I just tripped wit the Knox Warranty with the CF-AutoRoot. LoL
BikerSk8rKid said:
I guess I'm more of a newb with this than I expected. :/ It's been years since I've been on the forums or even tinkered with phones. HTC Touch Pro 2 was the last one I believe. haha
So... With that being said. Custom Roms are typically to the current stock rom, correct? or is it possible to get a Custom Jelly Bean and flash/overwrite it to the Lollipop/current? Since I just tripped wit the Knox Warranty with the CF-AutoRoot. LoL
Click to expand...
Click to collapse
If you can find some viable download links, then yes, you should be able to flash custom jelly bean ROMs. But you need a custom recovery in order to do that.
The recovery can be flashed with Odin. Or, since you're rooted, you can also flash a recovery by using an app called Flashify.
Odin requires a .tar file and Flashify requires a .img file.
Oh, and you also need the gapps package for the Google Apps. You need a package for that specific android version, so it should be jelly bean gapps.
GDReaper said:
If you can find some viable download links, then yes, you should be able to flash custom jelly bean ROMs. But you need a custom recovery in order to do that.
The recovery can be flashed with Odin. Or, since you're rooted, you can also flash a recovery by using an app called Flashify.
Odin requires a .tar file and Flashify requires a .img file.
Oh, and you also need the gapps package for the Google Apps. You need a package for that specific android version, so it should be jelly bean gapps.
Click to expand...
Click to collapse
I'll look into that and give it a shot. Thank you! I knew it wasn't THAT easy. LOL
Hey guys, everything I've read has said once you update beyond 4.3 you can never go back down because of knox. I also saw someone mention you actually can downgrade to a custom ROM based on a previous build just not to stock. Can anyone clarify this for me? I'm not worried about breaking my warranty since it's long since expired. I'm on the rooted 5.01 Goldeneye ROM and want to go back to a 4.2 ROM. strictly for tethering purposes
What is the model # for the s4?
It's the AT&T sgh-i337
With a locked bootloader, the phone is limited to customs roms based off a stock Samsung rom. Aosp and cm will not install or run.
audit13 said:
With a locked bootloader, the phone is limited to customs roms based off a stock Samsung rom. Aosp and cm will not install or run.
Click to expand...
Click to collapse
Thanks for the reply! So if I stick to TouchWiz based custom roms I can downgrade without bricking my phone?
Yes, just don't touch the bootloader or modem.
audit13 said:
Yes, just don't touch the bootloader or modem.
Click to expand...
Click to collapse
Ok thanks. Can you suggest a good 4.2 ROM? Also, since I'm already rooted with safestrap, do I just wipe and flash the new ROM or do I need to install a different version of safestrap and kernal etc? I'm have trouble finding any instructions on how to downgrade. I appreciate all your help!
I can't recommend any 4.2 roms as I don't have the phone. Also, I don't think such an old rom will work on an lp modem and bootloader.
audit13 said:
I can't recommend any 4.2 roms as I don't have the phone. Also, I don't think such an old rom will work on an lp modem and bootloader.
Click to expand...
Click to collapse
Ok so based on your statement "I don't think such an old rom will work on a lp modem and bootloader," does that mean you actually don't think I can downgrade?
You can try but I don't think you will have a functioning phone in that the imei will not be properly displayed which means the phone wouldn't be able to connect to the carrier.
audit13 said:
You can try but I don't think you will have a functioning phone in that the imei will not be properly displayed which means the phone wouldn't be able to connect to the carrier.
Click to expand...
Click to collapse
I appreciate your help!