Request Rom Manager vs Boot Loader Clarification - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

Not a Dev, but not a Noob, either. Formerly had a SGH-i897 Galaxy S for 3 years and flashed like crazy on it, while transitioning from Eclair to Froyo to Gingerbread to ICS to Jellybean, mostly using the fine offerings from the AOCP Collective folks. While familiar with Odin, CWM was my usual go-to utility.
Upgraded recently to a SGH-i337 Galaxy S4. Must have owned it for two, maybe three hours, before I rooted it with MotoChopper. This allowed me to re-install Titanium Backup. I left it as merely rooted, while I read up on CWM and some new-fangled thing called TWRP, which I wanted to get installed before casting about for a new ROM. (At the time, AOCP did not have an offering here, or it would have been a no-brainer for me.)
One morning, I turned on the phone and noticed it was doing an OTA update. . . . . . . . .
Mildly curious, I logged onto XDA to read what the community thought about the update, only to discover that I had missed all the dire warnings by a day and my (now) version I337UCUAMF3 ROM had it's boot-loaders locked from a blown Q-Fuse, courtesy of Samsung and AT&T.
Took me a week before I found the rooting solution from jortex, but thankfully, I'm now rooted again.
This background now leads to my questions:
I have ROM Manager Premium (from previous purchase) but have not installed it.
I was aware on my previous SGH-i897 that mixing the Gingerbread and Jellybean boot loaders was like, a Bad Thing when flashing ROMs and would promptly brick the phone.
Does CWM require the ability to load from a boot loader?
I know it creates an update.zip file to restore the original ROM, and usually does so by using whatever ROM is installed at the time.
So wouldn't it just create an update based on the I337UCUAMF3 ROM?
Even if I can't flash new ROMs (unless or until somebody comes up with a Q-Fuse Fix) couldn't I at least have all the recovery and .zip flashing of apps and cache clearing menu choices available to me from CWM?
Or would the act of just installing CWM on a I337UCUAMF3 ROM immediately brick my phone?
In Other Words, how close can I dance to the water's edge?
Been to the ROM Manager web site and they claim I can do any thing at any time.
(Easy for them to say: It ain't THEIR phones!)
Been searching these threads and can't come up with anything explicitly stating yea or nay.
So far, I have been happy enough with the TW stock ROM, but I always felt better being able to boot to recovery to fix things, on those few occasions I got just a leeeeeetle too close to the Bleeding Edge!
What is the consensus out there?
Will CWM 6.0.3.6 bork a I337UCUAMF3? Yes or no?
Would appreciate any thoughts that might enlighten me! :fingers-crossed:

It sure could brick the phone, the only thing you can do at the moment is root. I have seen a couple people try running a recovery on it, and it required a jtag service to restore the device.
Be careful.

TheAxman said:
It sure could brick the phone, the only thing you can do at the moment is root. I have seen a couple people try running a recovery on it, and it required a jtag service to restore the device.
Be careful.
Click to expand...
Click to collapse
Appreciate the response!

This phone is far different from the Captivate. There is no flashing anything on MF3. Basically you are waiting for a work around if that is even possible.
Sent from my SGH-I337 using xda premium

Related

CWM recovery

Ok so I got my AT&T S4 successfully rooted using the guide I found on here that uses the Motochopper tool. Root Checker verified I am indeed rooted. But that's it. I'm only rooted to the stock ROM. Nothing custom. Now how to I go about getting a CWM recovery thing on my phone, while still maintaining the stock ROM?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
On the play store, download goo manager (for twrp) or rom manager (for cwm) to install a custom recovery. Don't use either app to do anything but just install the recovery. Once it's installed, boot into recovery and make a backup, even if you're planning on staying stock. Cheers
Step 1. Go to the development forum and read about how to do it.
Step 2. Know how to do it.
Step 3. Do it.
I need more basic. I mean I know CWM means ClockWorkMod, but I don't know what that means. I also know that CWM is more popular than TWRP (I don't know what TWRP stands for) because the rom manager app has tons more downloads in the play store than the goo one does. What is a recovery mode and why do you need one? I mean if I screw up I can just use Odin to flash the AT&T stock ROM back. I wish someone would post a link to a ROMS for Dummies page.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
If I were you I'd be happy that your rooted and now find out what that means to you and what you want to do with a rooted phone. You don't need a custom recovery if all you're interested in is being rooted. And if you mess up, Odin back to stock may not be an option. You may permanently hard brick your phone. So really decide what you want to do with the phone before you proceed any further.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
feetr2c said:
I need more basic. I mean I know CWM means ClockWorkMod, but I don't know what that means. I also know that CWM is more popular than TWRP (I don't know what TWRP stands for) because the rom manager app has tons more downloads in the play store than the goo one does. What is a recovery mode and why do you need one? I mean if I screw up I can just use Odin to flash the AT&T stock ROM back. I wish someone would post a link to a ROMS for Dummies page.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
you really should have read and understood this first: http://forum.xda-developers.com/showthread.php?t=2301762
These guys are correct and trying to help you avoid a brick. If you are not aware of the basics start reading. Even if you are experienced at flashing on another device.
I had extensive experience on HTC phones and feel like a noob here, but getting better. But I have read over a thousand posts, at least, and dozens of how to videos since early may. And only feel comfortable now to flash a custom rom. Not ready yet as phone stock is pretty good for me atm. And would prefer an unlocked bootloader first. I only rooted and flashed a recovery about a week ago. May be a little slower than some, but never got into a problem I couldn't get out of on my HTC phones using the same learning process.
If you come back with specific questions where they know you have researched things they will gladly help. Googling some of the terminology is a good idea too. Had to do that when I first started flashing roms. A different language for sure.
Good luck and enjoy the phone and the rooted world.
In my experience with the S4 CWM does not work as well as TWRP. I had many issues installing a few custom ROMS with CWM, but as soon as i loaded TWRP those ROMS which wouldn't install would install properly. TWRP also was able to read my ext SD when it was formatted in exFat.

Note 2 - 4.3 Update coming soon:

Well instead of me writing, here is the link:
http://www.guru3d.com/news_story/galaxy_s4s3note_2_getting_4_3_gear_support_in_the_coming_weeks.html
I hope someone can leak out the final built for the n7105 section... I live in Australia, if America is getting it in a couple of weeks it means I'm getting it in a couple of years so we would appreciate the leak once it's released.
new thread, subsribed!!
via Note2
agreed mate
electroking said:
Well instead of me writing, here is the link:
http://www.guru3d.com/news_story/galaxy_s4s3note_2_getting_4_3_gear_support_in_the_coming_weeks.html
I hope someone can leak out the final built for the n7105 section... I live in Australia, if America is getting it in a couple of weeks it means I'm getting it in a couple of years so we would appreciate the leak once it's released.
Click to expand...
Click to collapse
im the same live in brissy been trying the at&t version seanz rom everything works but dont have wifi due to bootloader issues be sweet once that is sorted the rom is butter smooth but no wifi is the killer as vodafone data sucks nuts on 4g where i am
This is the update schedule for American carriers. Does that mean that unlocked phones will get it sooner? I hope so. I only just bought the note 2 (Best decision ever) and would love it to be running on 4.3 ASAP.
mattytheflasher said:
im the same live in brissy been trying the at&t version seanz rom everything works but dont have wifi due to bootloader issues be sweet once that is sorted the rom is butter smooth but no wifi is the killer as vodafone data sucks nuts on 4g where i am
Click to expand...
Click to collapse
I live in Brizzy too and I'll second or third that if its the only way we can get it? Sorry for the possibly stupid question, but is it true that if you have rooted and installed a custom rom, then you won't get the push update from your carrier anyway?... so.... the only way to get 4.3 on my (and I assume your rooted phone) is via custom rom download?
whokilledsanta said:
I live in Brizzy too and I'll second or third that if its the only way we can get it? Sorry for the possibly stupid question, but is it true that if you have rooted and installed a custom rom, then you won't get the push update from your carrier anyway?... so.... the only way to get 4.3 on my (and I assume your rooted phone) is via custom rom download?
Click to expand...
Click to collapse
or if you go back to stock.
have issues with the ota updater as soon as i root my device. The moment i do that i get the message that my device has been changed and i cannot use the updater then. if i flash stock withouth root i don't have this issue.
reckon its best to make a backup of your apps with TB or any similar program when the official update is available, then flash back stock (no root) and update, afterwards simply restore your normal (non-system) apps and your ready
I'm in Aus too, but the official story (courtesy of Telstra) is that there won't be any updates as of JB 4.1.2, unless there's sufficient backlash ...
morph000 said:
I'm in Aus too, but the official story (courtesy of Telstra) is that there won't be any updates as of JB 4.1.2, unless there's sufficient backlash ...
Click to expand...
Click to collapse
To answer you and the gentleman above... Australia will probably be the last country on earth to get the update as usual. So we might have to reside to getting it of some kind developer who uploads it here somewhere.
If you do wish to get updates you should go back to stock firmware (probably the first backup you made for your telstra 4.1.2) doesn't matter if it's rooted. Connect your phone to the PC and have KIES installed. Click update firmware and update (done, it will automatically unroot your phone and put back the stock recovery). You can easily update after that.
If anyone finds any android 4.3 working please update us here as soon as you can with a link to the page. If I find a working ROM for the official android 4.3 TW ROM I'll post it here too.
I don't think Aussie tel companies will well I don't have high hopes when it comes to Samsung I've always had HTC and Samsung and it's always the same get f all. I'm using 4.3.1 carbon I use GMD spen features for spen control and gestures don't use stock Sammy apps anyway.. just the 4.3 would be good because it's smooth as
Sent from my GT-N7105 using Tapatalk
I like the update 4.3 but ill want rom without knox. I need root
Sent from my GT-N7100 using xda app-developers app
Well now...I've been holding off playing with rooting my phone (as I'm new to 'droid and have an awful lot to learn, but have come a LONG way in 2 weeks) as I was expecting Telstra to release an update. Since that appears NOT to be forthcoming, Ill consider the various root options, none of which are particularly appealing at the moment mainly as it seems no-one has a stock ROM for this phone online and I can't backup mine without root. Catch 22 it seems. Information on locked bootloaders, Telstra ROM mods, rooting the 7105 "T" version is VERY limited
So...if anyone happens to have a link for a ROM copy please let me know.
(Or info on a rooting technique that works)
Ultimately every one on xda will be using the custom 4.3 rom for the note 3 goodies because Samsung will not be releasing those features in it's official release
Sent from my GT-N7100 using Tapatalk 2
morph000 said:
Well now...I've been holding off playing with rooting my phone (as I'm new to 'droid and have an awful lot to learn, but have come a LONG way in 2 weeks) as I was expecting Telstra to release an update. Since that appears NOT to be forthcoming, Ill consider the various root options, none of which are particularly appealing at the moment mainly as it seems no-one has a stock ROM for this phone online and I can't backup mine without root. Catch 22 it seems. Information on locked bootloaders, Telstra ROM mods, rooting the 7105 "T" version is VERY limited
So...if anyone happens to have a link for a ROM copy please let me know.
(Or info on a rooting technique that works)
Click to expand...
Click to collapse
Okay I will explain what I done for you...
When I first rooted my Galaxy Note 2 in May, I was a new-comer to android, I had an iPhone for a long time. What I done was root my phone, I Odin installed TWRP after rooting because I really don't like CWM (those are the names of the 'recoveries' available), they will replace the default Samsung recovery. Just make sure you get TWRP. I think it's up to TWRP 2.6.3
Well yeah let's get back to the topic, as soon as I rooted I used TWRP to make a backup of my default Telstra ROM (completely with EFS, MODEM, basically tick everything you can possibly backup).
I took that backup and put it on my laptop and on my PC and I kept a copy on my external card the whole time. That was the best idea, any time I ever had any problems with my phone I went back to that backup. I even soft bricked my phone once and after hours of panicking I realised I can just Re-install the default backup, and it fixed my phone.
Oh and I just recently un-rooted my phone to check for updates. All I done was use SuperSU to do an UNROOT. Then went into recover, restored the original backup I made of the Telstra ROM. Plugged my phone into the PC, and used Samsung KIES to check for firmware update. It just restarted my phone, removed TWRP recovery, re-installed the samsung one, and it removed the root completely and I'm basically went back to my original telstra ROM. I can go into settings and check for updates and everything. (I can confirm there is no update as of yet).
AS for your other QUESTION.
ALL THE ROMS in the N7105 Section will WORK with your N7105T Model. It's the same thing. JUST WATCH OUT and make sure you never install N7100 ROMS (They will soft-brick and could hard-brick your phone).
Thanks for the input.
I've been considering between 3, namely CF AutoRoot, Galaxy Note Toolkit And (exploit based) Framaroot, with a bias towards Toolkit so far ( as it specifies the 7105 "T" variant).
But if you've actually ODINed a GT-7105T (Telstra) with CWP without issues, I'll certainly consider that.
Any one else care to chime in on this (if you've done the same phone/telco only though !)
I've come far enough to understand rooting,boot processes, CWM/TWRP, exploits AND the importance of picking the exact model !:laugh:
I'll take the plunge when I get enough input to decide.
morph000 said:
Thanks for the input.
I've been considering between 3, namely CF AutoRoot, Galaxy Note Toolkit And (exploit based) Framaroot, with a bias towards Toolkit so far ( as it specifies the 7105 "T" variant).
But if you've actually ODINed a GT-7105T (Telstra) with CWP without issues, I'll certainly consider that.
Any one else care to chime in on this (if you've done the same phone/telco only though !)
I've come far enough to understand rooting,boot processes, CWM/TWRP, exploits AND the importance of picking the exact model !:laugh:
I'll take the plunge when I get enough input to decide.
Click to expand...
Click to collapse
It's not that hard really, you can't really mess it up if you follow the instructions... Hey root it whichever way you see fit, whatever you think is easier for you, don't listen to me. But I do highly recommend you get TWRP for backing up and formatting and installing your ROMS. Also I recommend PAC-MAN it's a good ROM, but it's not very stable at the moment (kind of).
electroking said:
It's not that hard really, you can't really mess it up if you follow the instructions... Hey root it whichever way you see fit, whatever you think is easier for you, don't listen to me. But I do highly recommend you get TWRP for backing up and formatting and installing your ROMS. Also I recommend PAC-MAN it's a good ROM, but it's not very stable at the moment (kind of).
Click to expand...
Click to collapse
Don't take offense at my asking for multiple inputs. I just don't want to brick at $600 phone needlessly
I've now sourced a ROM from Sammobile and downloaded it last night.
I'm backing up settings and stuff tonight and will run with Galaxy Note 2 Toolkit tomorrow (I went PRO) and go for option 3 - THE LOT !
Hopefully it'll all go ok.
morph000 said:
Don't take offense at my asking for multiple inputs. I just don't want to brick at $600 phone needlessly
I've now sourced a ROM from Sammobile and downloaded it last night.
I'm backing up settings and stuff tonight and will run with Galaxy Note 2 Toolkit tomorrow (I went PRO) and go for option 3 - THE LOT !
Hopefully it'll all go ok.
Click to expand...
Click to collapse
Haha you don't go pro over night my friend. Hope it all went all, if you have any issues or like to share your experience with the ROMS let us know.
electroking said:
Haha you don't go pro over night my friend. Hope it all went all, if you have any issues or like to share your experience with the ROMS let us know.
Click to expand...
Click to collapse
Well, I did the deed last night with Toolkit PRO and it all went smoothly. No Telstra or Samsung nasties reared their heads PLUS there wasn't a yellow triangle either !
That's the trouble with being in Oz. It's such a small market and REAL information is very hard to come by...so one is very cautious !
Anyway thanks for your assistance :victory:
morph000 said:
Well, I did the deed last night with Toolkit PRO and it all went smoothly. No Telstra or Samsung nasties reared their heads PLUS there wasn't a yellow triangle either !
That's the trouble with being in Oz. It's such a small market and REAL information is very hard to come by...so one is very cautious !
Anyway thanks for your assistance :victory:
Click to expand...
Click to collapse
I Odin flashed mine straight out of the box before I even set it up pulled backup and kept stock rom for warranty only.. these phones are pretty much unbrickable to an extent just don't go trying flashing n7100 roms and you'll be fine at&t roms are ok too just don't flash their bootloaders or even try to.. I change roms daily and have for like the last 2 years on my original note plus HTC's if your unsure on anything this place is helpful more than bloody Samsung
Sent from my GT-N7105 using Tapatalk
Sammobile: 4.3 is rolling out for the S3.

Flash ROM & some crazy nintendo graphics

Hi guys, I'm wondering if anyone can shed some light on a few things for me.
I have an ATT SGH i-337 MK2 with SafeStrap 3.71
Today I tried to flash PAC ROM and Dirty Unicorn into ROM Slot-1, and upon reboot when the ROM's logo should appear the whole screen just looked like when a nintendo cartridge isn't working. It was just a few crazy colors with some blocks and lines here and there.
Then I tried AOKP with it's Loki'd Kernel being part of the ROM. The nintendo screen came back again, but then the AOKP logo popped up clear as day for a second. Then went back to the lines and colors.
So could this be a problem with Safestrap compatibility? If so, how can I uninstall it? (I did read the dev's thread, and it just says use .APK and IDK what that means)
Or could it be that I also need to use Loki Doki with the other two? (Didn't see anything about that in PAC or DU threads)
Thanks!
Same issues apon using The Samsung Galaxy S4 for Verizon (jfltevzw) Build MK2 rooted using vRoot (English) and using safestrap. if needed I can upload the safestrap apk or version. If I install any type of AOSP ROM the boot logo is either missng or baby blue with wierd static lines. AOKP is the only AOSP ROM that eventually boots (with static boot logo) but no wireless works, and this is the same wether MK2 and/or MJ7 modules are installed or not. the only rom I can successfuly install and use daily that has no bootloader based issues is Hyperdrive ROM For jfltevzw & jflteatt. Any info would be much apreciated!
Sent from my SCH-I545 using xda app-developers app
^ Interesting. I didn't expect anyone else to have this issue. I never read about it before. I really feel like it has something to do with SafeStrap.
Heath Cliff said:
Hi guys, I'm wondering if anyone can shed some light on a few things for me.
I have an ATT SGH i-337 MK2 with SafeStrap 3.71
Today I tried to flash PAC ROM and Dirty Unicorn into ROM Slot-1, and upon reboot when the ROM's logo should appear the whole screen just looked like when a nintendo cartridge isn't working. It was just a few crazy colors with some blocks and lines here and there.
Then I tried AOKP with it's Loki'd Kernel being part of the ROM. The nintendo screen came back again, but then the AOKP logo popped up clear as day for a second. Then went back to the lines and colors.
So could this be a problem with Safestrap compatibility? If so, how can I uninstall it? (I did read the dev's thread, and it just says use .APK and IDK what that means)
Or could it be that I also need to use Loki Doki with the other two? (Didn't see anything about that in PAC or DU threads)
Thanks!
Click to expand...
Click to collapse
If you would have read 1st, then you would know that you can NOT flash any non TW rom on MK2. This is stated over & over on XDA. Safestrap is NOT the problem it is a Godsend from Hashcode for us to be able to flash custom roms onto our locked boot loader devices. Please read before flashing, bricking & then bashing the developers. Follow the directions posted on how to restore your phone, or better yet make a trip to Best Buy & they'll do it for you. Good Luck.
REEEEEEAAAAADDDD!!!!
It's been very well documented that AOSP does not work with safestrap. Neither does loki. There currently is no way/fix to flash AOSP.
So
1. No AOSP or GPE
2. No loki
3. No flashing custom kernels
Sent from my GT-I9505 using Tapatalk
John The Rhino said:
If you would have read 1st, then you would know that you can NOT flash any non TW rom on MK2. This is stated over & over on XDA. Safestrap is NOT the problem it is a Godsend from Hashcode for us to be able to flash custom roms onto our locked boot loader devices. Please read before flashing, bricking & then bashing the developers. Follow the directions posted on how to restore your phone, or better yet make a trip to Best Buy & they'll do it for you. Good Luck.
Click to expand...
Click to collapse
I did read first. I've been reading this forum for quite a while actually. But there is so much information it's hard to keep it all straight. This ATT stuff is a lot different then my VZW Razr was. That phone was just flash and forget. There are so many different ROM's for this phone now that are 4.3 or KitKat I guess I just didn't realize that, that Android version came with the ROM and was originally something more mod-able stock.
Any way I wasn't bashing SS or Hashcode. I clearly said "compatibility issue" i.e. some programs just don't play well together hence the existence of compatibility mode, virtual machines, and x86 processors. So maybe you should read before bashing novice community members and making yourself look like a big asshole.
And I don't need best buy to fix anything I have a NANDroid, backup on Kies3, and Google+. Besides, I did all of this flashing I on a separate partition so the stock ROM was never altered. Thanks for absolutely nothing at all.
For anyone else that feels like they can move on with me, I would really like to try to install TWRP in place of SS. I'd appreciate any help with how to go about doing that. TIA
Heath Cliff said:
I did read first. I've been reading this forum for quite a while actually. But there is so much information it's hard to keep it all straight. This ATT stuff is a lot different then my VZW Razr was. That phone was just flash and forget. There are so many different ROM's for this phone now that are 4.3 or KitKat I guess I just didn't realize that, that Android version came with the ROM and was originally something more mod-able stock.
Any way I wasn't bashing SS or Hashcode. I clearly said "compatibility issue" i.e. some programs just don't play well together hence the existence of compatibility mode, virtual machines, and x86 processors. So maybe you should read before bashing novice community members and making yourself look like a big asshole.
And I don't need best buy to fix anything I have a NANDroid, backup on Kies3, and Google+. Besides, I did all of this flashing I on a separate partition so the stock ROM was never altered. Thanks for absolutely nothing at all.
For anyone else that feels like they can move on with me, I would really like to try to install TWRP in place of SS. I'd appreciate any help with how to go about doing that. TIA
Click to expand...
Click to collapse
Well stating Safestrap may have a compatibility issue is offensive to the developer, especially since you did not read the instructions or posts from other members who did as you. If you would follow the directions it's perfect. I have 4 different roms on my phone + stock to choose from! How cool is that? I understand the overwhelming urge to flash a rom, as I too have been flashing on my Skyrocket since the factory warranty expired last year, and flashing roms is a breeze on that device. However, this S4 is more complicated since the introduction of the KNOX & the LOCKED boot loader. These phones are expensive so unless you really want a $700.00 brick, read, read some more, then read it all again. Safestrap uses TWRP to flash the roms, but TWRP alone is not compatible with MK2 nor is CWM. If you want to flash roms on your ATT MK2 S4 Safestrap is the only way to do that at this writing.
John The Rhino said:
Well stating Safestrap may have a compatibility issue is offensive to the developer, especially since you did not read the instructions or posts from other members who did as you. If you would follow the directions it's perfect. I have 4 different roms on my phone + stock to choose from! How cool is that? I understand the overwhelming urge to flash a rom, as I too have been flashing on my Skyrocket since the factory warranty expired last year, and flashing roms is a breeze on that device. However, this S4 is more complicated since the introduction of the KNOX & the LOCKED boot loader. These phones are expensive so unless you really want a $700.00 brick, read, read some more, then read it all again. Safestrap uses TWRP to flash the roms, but TWRP alone is not compatible with MK2 nor is CWM. If you want to flash roms on your ATT MK2 S4 Safestrap is the only way to do that at this writing.
Click to expand...
Click to collapse
Okay, well thank you for that. I just see so many ATT S4's in here with other ROMs and Recoverys I thought I could get something to happen. Anyway, sorry for the poor thread and response. I appreciate the plain blunt fact that SS and the ROMs that work with it are my choices for now. And don't worry about me. The worst that I'd probably get is a soft brick and I've recovered from that before Thanks again
Heath Cliff said:
Okay, well thank you for that. I just see so many ATT S4's in here with other ROMs and Recoverys I thought I could get something to happen. Anyway, sorry for the poor thread and response. I appreciate the plain blunt fact that SS and the ROMs that work with it are my choices for now. And don't worry about me. The worst that I'd probably get is a soft brick and I've recovered from that before Thanks again
Click to expand...
Click to collapse
Hey man I totally understand. It's hard to watch all these other roms pop up for the original S4 & we can't flash them. But we no longer have to suffer with only the stock rom option since Hashcode's brilliant Safestrap was released. Once you get use to it, the ability of being able to multi-boot roms really kind of makes up for the locked boot loader. Soon though, we will have 4.4 Kit Kat & then we can start this process of getting off the stock rom all over again. Right? It could be worse, we could have I-phones. We do have a ever growing number of great custom TW based roms available to us here for our device. So try them, you'll be surprised how much better your phone performs. Glad I made sense & forgive my bluntness that's just how us Rhinos roll.

[Q] How to install CWM or TWRP?

I have tried many methods to bypass boot loader and install CWM or TWRP on i337 phones, all for which they failed, I am not sure whether because I have NC1 device
My phone is Rooted, NC1, My ultimate objective is to install T mobile Rom, so I can get Wifi-calling on my at&t, what do I need to do in order to that??? I am willing to downgrade or anything to reach my objective.
Here are some guides that I saw at
galaxys4root dot com
"How to Install GT-i9505/T-Mobile Custom ROMs on AT&T Galaxy S4!"
But i couldn't Install cwm or TWRP to proceed. Please Help.
you are post mdl build and can not run cwm or custom twrp only safestrap recovery. surprised you didn't run across that when you rooted and installed safestrap--
as far as wifi calling--don't know, but believe i have read not on an att phone
rugmankc said:
you are post mdl build and can not run cwm or custom twrp only safestrap recovery. surprised you didn't run across that when you rooted and installed safestrap--
as far as wifi calling--don't know, but believe i have read not on an att phone
Click to expand...
Click to collapse
OH right (I did this long time ago so forgot most of it), So if I wanted to install a tmobile s4 custom rom (DARTHSTALKER) on my i337 I could use safestrap, and then flash my kernel using odin for it to work? or that would break the phone?
not sure, i don't use SafeStrap and not familiar with rom
i would make sure it is safestrap compatible and see if any other att folks have flashed it
i do that by skimming last 30 pages and in-forum search for safestrap and att
or you can ask, but have found most times you get no answer on those type of questions. it has to be TW based--
You can get full root access on NC1
devil_2 said:
I have tried many methods to bypass boot loader and install CWM or TWRP on i337 phones, all for which they failed, I am not sure whether because I have NC1 device
My phone is Rooted, NC1, My ultimate objective is to install T mobile Rom, so I can get Wifi-calling on my at&t, what do I need to do in order to that??? I am willing to downgrade or anything to reach my objective.
Here are some guides that I saw at
galaxys4root dot com
"How to Install GT-i9505/T-Mobile Custom ROMs on AT&T Galaxy S4!"
But i couldn't Install cwm or TWRP to proceed. Please Help.
Click to expand...
Click to collapse
It's very hard to achieve what I did in these screen shots... sorta lol I just got the phone delivered yesterday at 2pm and hit Red Bull for 15 hours hacking it... I have full root access in system... knox is frozen by TiBu as you can see SELiniux is permissive, SuperSU Pro in control without a popup warning... I do have a new boot screen though with the unlocked lock lol. Bye bye warranty! I bought the 2 year replacement one and they don't care if it's rooted lol.
Check out the screen captures... I had to slug it out getting one app at a time til I finally figured out how to get TiBu su access... that was the key! I'd have to write a small novel explaining it, and I'm tired as heck lol. Some shots were too big. Point is... its stable I don't think you get this with safe strap do ya? Maybe ya do... but I hacked it lol. Still stock OS with a lot of freezes. If this is something different and ya wanna know reply to the message, but it takes a while and you need to really know your adb commands and be good with terminal emulator because it' s literally all you'll have for most of the 'fight' with Knox... and it really is. Lucky it didn't boot loop lol but I wanted full root access. I'll just deodex it and get rid of the bloatware later. I still wish I could flash CWM though lol. I like AOSP roms
Lt1streconbn said:
It's very hard to achieve what I did in these screen shots... sorta lol I just got the phone delivered yesterday at 2pm and hit Red Bull for 15 hours hacking it... I have full root access in system... knox is frozen by TiBu as you can see SELiniux is permissive, SuperSU Pro in control without a popup warning... I do have a new boot screen though with the unlocked lock lol. Bye bye warranty! I bought the 2 year replacement one and they don't care if it's rooted lol.
Check out the screen captures... I had to slug it out getting one app at a time til I finally figured out how to get TiBu su access... that was the key! I'd have to write a small novel explaining it, and I'm tired as heck lol. Some shots were too big. Point is... its stable I don't think you get this with safe strap do ya? Maybe ya do... but I hacked it lol. Still stock OS with a lot of freezes. If this is something different and ya wanna know reply to the message, but it takes a while and you need to really know your adb commands and be good with terminal emulator because it' s literally all you'll have for most of the 'fight' with Knox... and it really is. Lucky it didn't boot loop lol but I wanted full root access. I'll just deodex it and get rid of the bloatware later. I still wish I could flash CWM though lol. I like AOSP roms
Click to expand...
Click to collapse
Would have been easier on you to use TowelRoot which would give full root access and then use safestrap for its recovery. Could of avoided the 15 hours in about 1 minute with the TowelRoot app
I did try it. Several times. Didn't work at all... It was a lot of fun doing this honestly I haven't had a good challenge in a while lol. I managed to hack knox out of my device using nothing but the device itself and knowledge I have. I really don't want multiple Roms in my device. I just want one ROM like I have in all the others, and that's what I have now and I got CWM installed last night finally... A bit glitchy and not 100% stable yet... It has issues backing up to external SD for some reason. It'll backup to internal though. I used it to flash a small and meaningless update.zip I assembled to test it and it worked with it I'm not sure it would be successful using a backup yet either to restore the device... If I just used towel root I wouldn't have ever figured any of this out, and if I can get it a bit more simplified and figure out which particular steps or combinationof steps allowed me to exploit the system and get it in tthere and I can get it stable... I can tell everyone else how to do it. A friend on XDA is working on a tool now to simple install SuperSU into system... He done it on another device and got cwm installed on a device with a locked boot loader also. I used some of the code to get an idea how to do it on the sgh-i337. Its not impossible... Just hard to figure out I think that's one of the things XDA exist for... To learn and progress and help others... Right?
Lt1streconbn said:
I think that's one of the things XDA exist for... To learn and progress and help others... Right?
Click to expand...
Click to collapse
Sent from my Nexus 5 using XDA Free mobile app
Right, absolutely. Good job. We'll be curious how you do it once you get it figured out.
devil_2 said:
OH right (I did this long time ago so forgot most of it), So if I wanted to install a tmobile s4 custom rom (DARTHSTALKER) on my i337 I could use safestrap, and then flash my kernel using odin for it to work? or that would break the phone?
Click to expand...
Click to collapse
Why a T-Mobile rom on an AT&T phone. Why not use one for an AT&T phone?
tailgunner9 said:
Why a T-Mobile rom on an AT&T phone. Why not use one for an AT&T phone?
Click to expand...
Click to collapse
For t-mobile wifi-calling
Well Great Job then, I do applaud you for your work you done. Hopefully for those that are stuck using safestrap you can get it to the point they could use cwm. That would be awesome.
tailgunner9 said:
Why a T-Mobile rom on an AT&T phone. Why not use one for an AT&T phone?
Click to expand...
Click to collapse
I seriously would not try that using safe strap in i337 @ this point. The ROM would need to be ported as a multicarrier , which is pretty simple in and of itself... A lot of debugging I'd imagine though. You'll only get 2g speed using ATT device on TMO ya know. They have different 3g and 4g LTE bands. It just won't work. If you flash that ROM.. IIt's very likely you'll soft brick or hard brick the device. I have the ATT kernel decomped now working with it... I haven't downloaded any existing ROMS used with i337 yet, but I'll get one and check it out and see what has been done with Knox in it. Just very risky flashing a ROM not specific to your device...

[Q]Want GPE, but can't get custom recovery - Help please! :(

Hey guys... Before I get into this, I would like to say that i'm very new to this whole rooting thing, so please forgive me for my lack of knowledge on various terms and such, and I'm a first time user here at xda.
What's written below might get a little bit complicated so i will try to make it as detailed as possible. Please bare with me here.
So I have a Samsung Galaxy S4 sgh-i337 (AT&T) running on android 4.4.4 (with touchwiz, you guys know the deal). I really wanted stock android lollipop, because I really like the look and feel to it. When I decided to root the phone, I went through many tutorials and I tried many different methods, and none of them worked. The phone still worked fine, but SuperSU was not installed and Root Checker said the phone was not rooted. After scouring the internet, I found one tutorial that had my S4 type and the same version. At that point I realized that my android version was hindering my rooting process. The tutorial used Odin to flash a kernel (NC1), root the phone using towelroot, install SuperSU, (Root Checker too to check if it worked), and then flashing the original kernel again (my original kernel was NJ4). After following this process, my phone was rooted, and everything worked fine.
As I said before, I wanted a GPE ROM, and so I needed a custom recovery. I decided to install CWM, since most GPE ROMs used this specific recovery. Again, I followed many different tutorials, and after each and every one, I would try to go into Recovery mode, and it would just launch the stock recovery. I found another tutorial on another website that involved flashing the recovery from an app in the google play store, so I decided to try it out. I now regret this as it led to more problems. I followed these instructions, and when launching into recovery mode from that point on, I get the yellow triangle with the error message "System software is not authorized by AT&T"
Sure, I could get around it by going into download mode from there, canceling, and it would reboot like normal, and the phone still worked, but I needed to get ride of that error message.
Once again doing my research, I figured out that if I flash a stock firmware specific to my phone, it will reset the phone (the only stock firmware available has android version 4.2.2, which is a really popular version, and is compatible with most custom recoveries and ROMs, so I decided to flash the firmware, as it would also change the version back, right?) When I flashed it using Odin like the directions said, it failed. i then figured out that it failed because my binary counter is not 0. I looked into resetting the binary counter for the AT&T S4, and I found Triangle Away. However, in order to reset your binary counter, you need an unlocked bootloader, and the AT&T S4 (sgh-i337) has a locked bootloader (I don't want to use Triangle Away if it's going to brick my phone, i'd rather unroot and keep touchwiz than brick). In the process of finding this out, I also figured out that the only custom recovery that you could use on a locked bootloader S4 sgh-i337 is SafeStrap. But i heard when using SafeStrap you are limited as far as ROMs go? Would I be able to get a GPE 5.0 Lollipop ROM with SafeStrap? Cause if not I might just unroot using SuperSU and software update my phone (will that fix the error when trying to get to Recovery mode?) Also, if I install Safestrap, will it fix the error message?
Again, sorry for my inexperience in all of this, and thanks for staying with me here. Any help and additional information on what I should do (or any GPE Lollipop ROMs I should use that are compatible with my phone and version and such), as well as any links to tutorials are greatly appreciated (also, keep in mind that all of the vocab I know when rooting is used in this post, I am not aware of most other terms - again, forgive me).
You wrote a lot but I'm not sure what state your device is in right now and what you want to do. But as you've found out, safestrap is the only custom recovery you can use. And touch wiz based roms are the only ones you can use. Afaik there are no 5.0 custom roms you can use at this time.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You wrote a lot but I'm not sure what state your device is in right now and what you want to do. But as you've found out, safestrap is the only custom recovery you can use. And touch wiz based roms are the only ones you can use. Afaik there are no 5.0 custom roms you can use at this time.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Oh, thanks for the help! The phone currently works fine, and it is rooted, but when I go into Recovery Mode it gives me the yellow triangle with the error... Will installing SafeStrap fix that? Regardless, thanks for the help, really do appreciate it!
jd1639 said:
You wrote a lot but I'm not sure what state your device is in right now and what you want to do. But as you've found out, safestrap is the only custom recovery you can use. And touch wiz based roms are the only ones you can use. Afaik there are no 5.0 custom roms you can use at this time.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Also, if i were to update the phone to the next version (i heard there is a way to bump the S4 up in android version) would that reset the error in Recovery Mode? And I also heard that with SafeStrap, you are limited to ROMs on the same android version as the one on your phone? I really like 5.0, but if it's not possible to get it as the moment (and I haven't found any 5.0 ROMs for the sgh-i337 yet - you were right) i might just unroot using SuperSU and just update my version, unrooted and all. I'd rather have my phone be nice and clean than to have root on it with a corrupted recovery mode, and not make use of the root at all (I've seen other ROMs and I prefer 5.0). I might just try to make the phone feel as close to stock as possible by using more google apps and such (keyboard, messages, etc.). Regardless, thanks for the help and additional input, really do appreciate it!
EvilLemon said:
Also, if i were to update the phone to the next version (i heard there is a way to bump the S4 up in android version) would that reset the error in Recovery Mode? And I also heard that with SafeStrap, you are limited to ROMs on the same android version as the one on your phone? I really like 5.0, but if it's not possible to get it as the moment (and I haven't found any 5.0 ROMs for the sgh-i337 yet - you were right) i might just unroot using SuperSU and just update my version, unrooted and all. I'd rather have my phone be nice and clean than to have root on it with a corrupted recovery mode, and not make use of the root at all (I've seen other ROMs and I prefer 5.0). I might just try to make the phone feel as close to stock as possible by using more google apps and such (keyboard, messages, etc.). Regardless, thanks for the help and additional input, really do appreciate it!
Click to expand...
Click to collapse
I would recommend you flash the nb1 tar file in Odin. That'll bring your device to like new. Then you can let it ota nj4. There are root methods for nc1 and nj4. See this
http://forum.xda-developers.com/showthread.php?p=56453100
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I would recommend you flash the nb1 tar file in Odin. That'll bring your device to like new. Then you can let it ota nj4. There are root methods for nc1 and nj4. See this
http://forum.xda-developers.com/showthread.php?p=56453100
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks so much! I followed the instructions and now my phone is back to normal, Recovery mode and all! Really do appreciate it, thanks!
EvilLemon said:
Thanks so much! I followed the instructions and now my phone is back to normal, Recovery mode and all! Really do appreciate it, thanks!
Click to expand...
Click to collapse
No problem. I'm glad you got it working again
Sent from my Nexus 9 using XDA Free mobile app

Categories

Resources