Database Info

Still learning

Still pretty new to this stuff so I have a couple questions,
I am conflicted on whether I still have to "unlock bootloader" or not. Some threads I read seem like it has been unlocked now and isn't a manual thing. Is this true?
What is the purpose of backing up IMEI?
Are the results any different if I load CWM via ODIN, EZ Recovery, etc? Is one better then the other as far a funtion not ease of method?
Once I'm rooted and have a custom recovery (CWM) can I still connect for software updates (stock rom of course) or can Verzion tell I've made changes?

gfausey211 said:
Still pretty new to this stuff so I have a couple questions,
I am conflicted on whether I still have to "unlock bootloader" or not. Some threads I read seem like it has been unlocked now and isn't a manual thing. Is this true?
What is the purpose of backing up IMEI?
Are the results any different if I load CWM via ODIN, EZ Recovery, etc? Is one better then the other as far a funtion not ease of method?
Once I'm rooted and have a custom recovery (CWM) can I still connect for software updates (stock rom of course) or can Verzion tell I've made changes?
Click to expand...
Click to collapse
Short answers:
Yes, you have to do it manually
You back up IMEI/NV because some people have lost it by flashing custom roms or kernels and it is much easier and more effective to have a backup than to repair the damage without one.
There shouldn't be a difference in terms of recovery function depending on install method
You should NEVER accept updates from Verizon once rooted and there really is no need to because we devs will have the updates shortly after...or sometimes before...they are official
For a longer discussion, see this thread:
http://forum.xda-developers.com/showthread.php?p=30591784

Bleelas said:
Short answers:
Yes, you have to do it manually
You back up IMEI/NV because some people have lost it by flashing custom roms or kernels and it is much easier and more effective to have a backup than to repair the damage without one.
There shouldn't be a difference in terms of recovery function depending on install method
You should NEVER accept updates from Verizon once rooted and there really is no need to because we devs will have the updates shortly after...or sometimes before...they are official
For a longer discussion, see this thread:
http://forum.xda-developers.com/showthread.php?p=30591784
Click to expand...
Click to collapse
Thanks that is great info

for the boot loader, as far as i know, After you root, there is an app called Ez root which unlocks your verizon S3 in a second.

the_incredble said:
for the boot loader, as far as i know, After you root, there is an app called Ez root which unlocks your verizon S3 in a second.
Click to expand...
Click to collapse
Careful there turbo. The app that unlocks the bootloader is called EZ-unlock. Unlocking is different than rooting.
Sent from my SGS3 on Synergy Nightlies

the_incredble said:
for the boot loader, as far as i know, After you root, there is an app called Ez root which unlocks your verizon S3 in a second.
Click to expand...
Click to collapse
For some reason Google Play is throwing an error when I try to download EZ Unlock.
I tried to flash Synergy (lastest nightlies) but I couldn't get my wifi to connect. IT wouldn't let me toggle it on at all. Anyone have this problem?
Should I keep trying to down the nightlies as they come out or is their certain what I should go with?

gfausey211 said:
For some reason Google Play is throwing an error when I try to download EZ Unlock.
I tried to flash Synergy (lastest nightlies) but I couldn't get my wifi to connect. IT wouldn't let me toggle it on at all. Anyone have this problem?
Should I keep trying to down the nightlies as they come out or is their certain what I should go with?
Click to expand...
Click to collapse
I am running Beans build 9 and really like it everything seems to be stable for me. I also would suggest using EZ unlock to unlock your bootloader and EZ recovery to flash CWM and use that to flash roms.

KIS
gfausey211 said:
For some reason Google Play is throwing an error when I try to download EZ Unlock.
I tried to flash Synergy (lastest nightlies) but I couldn't get my wifi to connect. IT wouldn't let me toggle it on at all. Anyone have this problem?
Should I keep trying to down the nightlies as they come out or is their certain what I should go with?
Click to expand...
Click to collapse
Don't know about all these ez apps. Its probably best to do it manually so you know what you are doing. That being said you can use Adam Outlers "Casual" app that does it all. Its easy and does it all.
http://forum.xda-developers.com/showthread.php?t=1762709
---------- Post added at 05:26 PM ---------- Previous post was at 04:54 PM ----------
Well I spoke to soon I guess. EZRecovery is for flashing Recoveries. I'm coming from an OG Droid and someone eleses Droid Bionic. I don't get why we need anything other than Clock Work Mod for recovery. I never bothered with flashing kernels. Just ROMs

gfausey211 said:
For some reason Google Play is throwing an error when I try to download EZ Unlock.
I tried to flash Synergy (lastest nightlies) but I couldn't get my wifi to connect. IT wouldn't let me toggle it on at all. Anyone have this problem?
Should I keep trying to down the nightlies as they come out or is their certain what I should go with?
Click to expand...
Click to collapse
You can get around the play error by just downloading the apk over here:
http://rootzwiki.com/topic/32456-app-ez-unlock-easiest-way-to-unlock-your-bootloader/
As far as when to update to the nightlies, it's all preference. If something gets changed that you like, go ahead and flash. Otherwise if it aint broke don't fix it
Generally what I do when I'm on a nightly rom is download the rom daily or every other day, go into recovery, wipe cache & Dalvik cache and flash the rom. Once a week or every other week I'll wipe the whole phone out instead of just wiping the caches.

Small carrier, model/build version, flashing decision issues

Just got an upgrade from my carrier (a small local carrier) and I chose the s3. Came from some Motorola peice of fail. I'm looking to root and flash an insecure bootloader but I have encountered a confusing conflict. Having a Verizon model phone with a us cellular build of android loaded. And yes I'm certain it is a Verizon model phone (google schi535mbb if you don't believe me) with us cellular stock rom loaded (with some tweeks like 4g disabled). Rom and software model say the following R530 & d2usc. Bootloader is I535VRALE6 baseband I535VRLF2. This as far as I can tell was acomplished by a company called ultimobile. Which customizes devices to function on small mobile carriers. If anybody has any ideas or suggestions on what I might try, please let me know. I just don't want to screw something up and have a brick, just coming from a device that was all but brickable.
Sent from my SCH-I535 using xda premium

Lrs121 said:
Just got an upgrade from my carrier (a small local carrier) and I chose the s3. Came from some Motorola peice of fail. I'm looking to root and flash an insecure bootloader but I have encountered a confusing conflict. Having a Verizon model phone with a us cellular build of android loaded. And yes I'm certain it is a Verizon model phone (google schi535mbb if you don't believe me) with us cellular stock rom loaded (with some tweeks like 4g disabled). Rom and software model say the following R530 & d2usc. Bootloader is I535VRALE6 baseband I535VRLF2. This as far as I can tell was acomplished by a company called ultimobile. Which customizes devices to function on small mobile carriers. If anybody has any ideas or suggestions on what I might try, please let me know. I just don't want to screw something up and have a brick, just coming from a device that was all but brickable.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Interesting. From the sound of it it may just be software blocked. Verizon root and unlock should work. The trick is gonna be finding software that will work with that carrier. If it is using straight UC Cellular may be able to run what those guys are running. If it is that small carrier that controls access then that would be the problem. Without a backup of the stock rom don't know how you would get it running again. According to the numbers it is a Verizon S3 running Us Cellular. Good luck.

prdog1 said:
Interesting. From the sound of it it may just be software blocked. Verizon root and unlock should work. The trick is gonna be finding software that will work with that carrier. If it is using straight UC Cellular may be able to run what those guys are running. If it is that small carrier that controls access then that would be the problem. Without a backup of the stock rom don't know how you would get it running again. According to the numbers it is a Verizon S3 running Us Cellular. Good luck.
Click to expand...
Click to collapse
The recovery that's on it right now has built in options for nvbackup. From what I've read that is the radio, imei, and other files used to connect to the network. I was gonna make several backups of everything as soon as I gained root control. The real problem comes down to when I go to throw cm on here. Figuring out which vzw or usc will cooperate with the carrier files.
Sent from my SCH-I535 using xda premium

Lrs121 said:
The recovery that's on it right now has built in options for nvbackup. From what I've read that is the radio, imei, and other files used to connect to the network. I was gonna make several backups of everything as soon as I gained root control. The real problem comes down to when I go to throw cm on here. Figuring out which vzw or usc will cooperate with the carrier files.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Make a nandroid backup and maybe post to see what your running as?
Sent from my SCH-I535 using Tapatalk 2

Addiso said:
Make a nandroid backup and maybe post to see what your running as?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Was definitely gonna make a nandroid, but as for 'post to see what I'm running as' what do you mean?
Sent from my SCH-I535 using xda premium

Lrs121 said:
Was definitely gonna make a nandroid, but as for 'post to see what I'm running as' what do you mean?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Maybe the build.prop?
Edit: Attach it via Pastebin!

SlimSnoopOS said:
Maybe the build.prop?
Edit: Attach it via Pastebin!
Click to expand...
Click to collapse
Here ya go. Have fun http://pastebin.com/eUj5z2VT
Sent from my SCH-I535 using xda premium

Lrs121 said:
Here ya go. Have fun http://pastebin.com/eUj5z2VT
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Looks like us cellular under the ultimobile ID?
Sent from my SCH-I535 using Tapatalk 2

Addiso said:
Looks like us cellular under the ultimobile ID?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
It's weird though right? I'm not sure how to go about suggesting how to flash roms. I have to side with prdog1 and say it's a VZW GSIII running USC. I really can't suggest a good way to proceed since it's hard to tell what you would use to revert back to stock in case of emergences.
Anyone familiar with Team US Cellular? Any input from there?

Addiso said:
Looks like us cellular under the ultimobile ID?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
thats what i saw too. the difficult thing to figure out is if to use the verizon unlock and root or the us cellular model. it is most definately a verizon model of phone just loaded up with us cell software. ive flashed verizon a based rom over a locked down motorola peice of fail, but that couldnt touch the kernel, base band, or anything but the system with out it requiring a complete reflash to stock. i dont exactly have that option if every thing screws up in the process of gaining root. id have to take it into the store and wait till they can reflash it there.

Lrs121 said:
thats what i saw too. the difficult thing to figure out is if to use the verizon unlock and root or the us cellular model. it is most definately a verizon model of phone just loaded up with us cell software. ive flashed verizon a based rom over a locked down motorola peice of fail, but that couldnt touch the kernel, base band, or anything but the system with out it requiring a complete reflash to stock. i dont exactly have that option if every thing screws up in the process of gaining root. id have to take it into the store and wait till they can reflash it there.
Click to expand...
Click to collapse
I'm fairly certain you should use the unified toolkit to root and maybe unroot. In your build.prop, I noticed it reads on the fifth line:
ro.build.version.incremental=R530UVXALK5
Click to expand...
Click to collapse
and the toolkit supports LK5 build for the d2usc. I think they're both locked down the same but on Team US Cellular's website that's what I'm seeing some people have used too. Idk about your specific case using another carrier but a d2usc GSIII but I'm thinking that's a start. Idk about returning to stock though.
Edit: Gonna add this, this means there is an Odin flashable of LK5 available somewhere.
Edit x2: POW!

SlimSnoopOS said:
I'm fairly certain you should use the unified toolkit to root and maybe unroot. In your build.prop, I noticed it reads on the fifth line:
and the toolkit supports LK5 build for the d2usc. I think they're both locked down the same but on Team US Cellular's website that's what I'm seeing some people have used too. Idk about your specific case using another carrier but a d2usc GSIII but I'm thinking that's a start. Idk about returning to stock though.
Edit: Gonna add this, this means there is an Odin flashable of LK5 available somewhere.
Edit x2: POW!
Click to expand...
Click to collapse
really i need to gain fastboot access to the phone. there are some files i need to check and i need to pull the special recovery that came with the phone. if i can do that i should be able to pull what i need from the phone to be able to return to stock. im also gonna perform an nvback up, a qpst backup and the synergy back up. but first things first i need fastboot access to the phone. i know how to get into recovery and download mode but for the life of me i cant figure out how to get to a fastboot compliant mode. from there i can figure how im gonna proceed to root.
edit: what i see in download mode
odin mode
Product name: sch--i535
custom binary download: yes (1 counts)
current binary: custom
system status: custom
Qualcom secureboot: enable

Lrs121 said:
really i need to gain fastboot access to the phone. there are some files i need to check and i need to pull the special recovery that came with the phone. if i can do that i should be able to pull what i need from the phone to be able to return to stock. im also gonna perform an nvback up, a qpst backup and the synergy back up. but first things first i need fastboot access to the phone. i know how to get into recovery and download mode but for the life of me i cant figure out how to get to a fastboot compliant mode. from there i can figure how im gonna proceed to root.
edit: what i see in download mode
odin mode
Product name: sch--i535
custom binary download: yes (1 counts)
current binary: custom
system status: custom
Qualcom secureboot: enable
Click to expand...
Click to collapse
Here's a left field suggestion, could you call this UltiMobile company and ask about what they used?

SlimSnoopOS said:
Here's a left field suggestion, could you call this UltiMobile company and ask about what they used?
Click to expand...
Click to collapse
havent done that yet. its on a list of things to do the problem is that everywhere they put information out they say to contact the carrier not them for everything. i may just have to wait till the phone isnt so new at my carrier and let the IT department play around with it for a while. i can then get information from them.

Lrs121 said:
havent done that yet. its on a list of things to do the problem is that everywhere they put information out they say to contact the carrier not them for everything. i may just have to wait till the phone isnt so new at my carrier and let the IT department play around with it for a while. i can then get information from them.
Click to expand...
Click to collapse
That's real tricky but sounds like your best option. At least you're rooted and unlocked with the VRALE6 bootloader and can debloat. Out of curiosity, what recovery are you using that has all these options?
As an aside, this table tells you where the recovery partition is. I've heard of people using dd commands to pull whatever partition they want to their sdcard but idk how viable an option this is in terms of pushing a recovery to that partition. I'm not recommending you try it either.

SlimSnoopOS said:
That's real tricky but sounds like your best option. At least you're rooted and unlocked with the VRALE6 bootloader and can debloat. Out of curiosity, what recovery are you using that has all these options?
As an aside, this table tells you where the recovery partition is. I've heard of people using dd commands to pull whatever partition they want to their sdcard but idk how viable an option this is in terms of pushing a recovery to that partition. I'm not recommending you try it either.
Click to expand...
Click to collapse
The vrale6 is unlocked? If so then why does it say that the qualcom secure boot is enabled. And I haven't rooted just yet but am working on it. Its a recovery built by ultimobile.
Sent from my Nexus 7 using XDA Premium HD app

Lrs121 said:
The vrale6 is unlocked? If so then why does it say that the qualcom secure boot is enabled. And I haven't rooted just yet but am working on it. Its a recovery built by ultimobile.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Yes indeed. VRALE6 is the prerelease bootloader that was leaked which EVERY d2vzw (d2usc I suppose too) uses in order to allow flashing of roms/kernels. It's a little weird to explain but basically everyone's Download Mode reads almost the same. Mine reads "custom binary: Samsung Official" though and I'm rooted/unlocked. Idk the technical or even the proper way to explain it but the unlocked VRALE6 bootloader has no bearing on what Download mode says. Although your custom binary should be at 0 if/when you do warranty exchanges.

SlimSnoopOS said:
Yes indeed. VRALE6 is the prerelease bootloader that was leaked which EVERY d2vzw (d2usc I suppose too) uses in order to allow flashing of roms/kernels. It's a little weird to explain but basically everyone's Download Mode reads almost the same. Mine reads "custom binary: Samsung Official" though and I'm rooted/unlocked. Idk the technical or even the proper way to explain it but the unlocked VRALE6 bootloader has no bearing on what Download mode says. Although your custom binary should be at 0 if/when you do warranty exchanges.
Click to expand...
Click to collapse
Ah makes sense now it just doesn't do a hash/encryption check. I've dealt with a lot of bootloader stuff with my old phone. the phone came like that with the count at 1. Was like that before I tried anything. Probably was triggered when the d2usc stock was flashed onto it. Which probably means I should stick with d2usc builds to ensure compatibility with connecting with my carrier.
Sent from my Nexus 7 using XDA Premium HD app

[Q] Unauthorized software message ONLY when booting into recovery

This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?

Sleix said:
This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window, rebooting the phone normally. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?
Click to expand...
Click to collapse
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.

Sleix said:
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.
Click to expand...
Click to collapse
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?

Sleix said:
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?
Click to expand...
Click to collapse
No, but it wouldn't hurt.
Use 1.2 of ez unlock, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
These are the most recent recoveries, download and flash in the ez recovery app if you need to.
http://forum.xda-developers.com/showthread.php?t=2096735
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
No, but it wouldn't hurt.
Use 1.2, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.

Sleix said:
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.
Click to expand...
Click to collapse
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Before flashing anything, use a newer recovery image. The one provided by ez recovery is from last year, the newer versions are better written to prevent possible errors that come up with jellybean.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll keep that in mind, thanks again!
Any roms you'd recommend?

Sleix said:
I'll keep that in mind, thanks again!
Any roms you'd recommend?
Click to expand...
Click to collapse
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Will do. Thanks for pointing that edit out.

The [GT-I9505][Leaked firmware] I9505XXUFNA1 (Android 4.4) - Open Europe (OXA) [10-01

The gt-i9005 has a leaked fireware of 4.4. I hope that we get in the next two or there months!
http://forum.xda-developers.com/showthread.php?t=2465713
Sent from my SGH-I337 using xda premium

killer5000 said:
The gt-i9005 has a leaked fireware of 4.4. I hope that we get in the next two or there months!
http://forum.xda-developers.com/showthread.php?t=2465713
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
I just downloaded
Has anyone tried unzipping it and rezipping without the bootloader, etc and tried flashing it rather than using odin and replacing the bootloader everything? I am working on that as we speak, just wondering if someone has done it already and what their experience was as far as what worked. I imagine there will be some issues with wifi or what not.

neo4uo said:
I just downloaded
Has anyone tried unzipping it and rezipping without the bootloader, etc and tried flashing it rather than using odin and replacing the bootloader everything? I am working on that as we speak, just wondering if someone has done it already and what their experience was as far as what worked. I imagine there will be some issues with wifi or what not.
Click to expand...
Click to collapse
If you're on i337 you cannot flash it through Odin, not authorized... I have been tinkering with putting together a zip to flash via recovery...but I'm a novice and couldn't get past the boot animation with sound...

ZPaul2Fresh8 said:
If you're on i337 you cannot flash it through Odin, not authorized... I have been tinkering with putting together a zip to flash via recovery...but I'm a novice and couldn't get past the boot animation with sound...
Click to expand...
Click to collapse
I was working on it the other day and just got to busy. There is a rom already in the I9505 thread...
http://forum.xda-developers.com/showthread.php?t=2555569
The only catch is from what I have read that the Wifi will not work unless you odin the leak first. For some reason it seems that you have to have the new leaked bootloader. I have talked to a couple of the people that made a zip flash keeping the bootloader we are on, but no wifi. I stopped working on making a zip after I found that out. I have thought about using odin to flash the leak then flashing the Rom from the link above, but am not sure if I would be able to go back to the roms that I am running on the old bootloader. I am just going to wait until some people that knows what they are are doing picks the leak apart more. Anywho if you are interested goto that thread above and do some reading. I personally am just going to stay away until we know more about the new bootloader. I know that the leak can be rooted though because chainfire released an update specifically for the 4.4.2 leak.

neo4uo said:
I was working on it the other day and just got to busy. There is a rom already in the I9505 thread...
http://forum.xda-developers.com/showthread.php?t=2555569
The only catch is from what I have read that the Wifi will not work unless you odin the leak first. For some reason it seems that you have to have the new leaked bootloader. I have talked to a couple of the people that made a zip flash keeping the bootloader we are on, but no wifi. I stopped working on making a zip after I found that out. I have thought about using odin to flash the leak then flashing the Rom from the link above, but am not sure if I would be able to go back to the roms that I am running on the old bootloader. I am just going to wait until some people that knows what they are are doing picks the leak apart more. Anywho if you are interested goto that thread above and do some reading. I personally am just going to stay away until we know more about the new bootloader. I know that the leak can be rooted though because chainfire released an update specifically for the 4.4.2 leak.
Click to expand...
Click to collapse
I did try flashing with Odin a day ago, I'm assuming since the Download Mode has "No authorization" it's due to the locked bootloader we have. About 10% into the flash it fails with an authorization error... I'm going to look into that thread to see if I can learn more...trial and error is a great learning tool for me
Downloading now to try it out. The updated link for that referenced rom is http://forum.xda-developers.com/showthread.php?t=2372286...

ZPaul2Fresh8 said:
I did try flashing with Odin a day ago, I'm assuming since the Download Mode has "No authorization" it's due to the locked bootloader we have. About 10% into the flash it fails with an authorization error... I'm going to look into that thread to see if I can learn more...trial and error is a great learning tool for me
Downloading now to try it out. The updated link for that referenced rom is http://forum.xda-developers.com/showthread.php?t=2372286...
Click to expand...
Click to collapse
Let us know, or pm and let me know how it goes

known bugs
Hi so far after using for the last two days I notice when holding the home button for open apps what ever you press will always open the last app used and not what you have selected!
Andy the native Samsung e mail app continuously tells me about e mails I've viewed
That is all so far!

what kernel are you using?

neo4uo said:
Let us know, or pm and let me know how it goes
Click to expand...
Click to collapse
Well after hours of farting around with their build and mine, I pretty much lost interest with the ROM now. Their build definitely has WiFi broken. I'm not sure if it's kernel related or not.
I think I'm with you on waiting for this to improve before using. Besides CM11 with Google Experience Launcher is looking and feeling great this past month...

Here is a like to Echoe13_4.4.2Deodex_12JAN2013.zip it works but you need to loki patch it and wifi don't work.
http://www.androidfilehost.com/?fid=23311191640113279

hello my friends somebody have one solution for the problem of wifi in rom stock o custom deodex of echoe in 4.4.2... And please can explainme what is the loky patch...? tks for your help and sorry for my english..!

Loki only has to be flashed on the At&t variant of the S4 after installing a zip that was not an At&t rom. The WiFi issue I believe is from not updating the bootloader via OTA and possibly kernel tweaks as well but it will get there. We have great devs for this device.
Sent from my SGH-I337 using XDA Premium HD app

scalamusical said:
hello my friends somebody have one solution for the problem of wifi in rom stock o custom deodex of echoe in 4.4.2... And please can explainme what is the loky patch...? tks for your help and sorry for my english..!
Click to expand...
Click to collapse
You need a kernel made from the 4.4.2 source code which has not been released yet for the wifi.
For loki patch on att, download loki-doki, put it on your SD, go to recovery, flash rom,flash loki doki. If you are using a rom made for att chances are the kernel will already be patched.

C13v3r0n3 said:
You need a kernel made from the 4.4.2 source code which has not been released yet for the wifi.
For loki patch on att, download loki-doki, put it on your SD, go to recovery, flash rom,flash loki doki. If you are using a rom made for att chances are the kernel will already be patched.
Click to expand...
Click to collapse
what kernel were you guys using on the echoe roms? I couldn't get past the boot screen and it hung using the i337m Canadian variant which should be the same as their TMO version minus the leaked bootloader.

There is a new NA5 leak out. I am in the I337 and have tried the NA1 leak Roms Indies Omega and Echoe and I always hang up on the boot menu. Guess we will have to wait for the official and the Kernel info for it to work for us.

rfb813 said:
There is a new NA5 leak out. I am in the I337 and have tried the NA1 leak Roms Indies Omega and Echoe and I always hang up on the boot menu. Guess we will have to wait for the official and the Kernel info for it to work for us.
Click to expand...
Click to collapse
You give me a few hrs, at work right now. I will have this running for att the NA5 base...so stay tuned....

TheAxman said:
You give me a few hrs, at work right now. I will have this running for att the NA5 base...so stay tuned....
Click to expand...
Click to collapse
I didn't know there was a nlthread on this on my native device. I Have been posting on the Tmobile thread since the leak first came out.
I also unpacked both Leaks and repacked only their respective boot, system and cache files and successfully flashed via Odin. the cool part was that I didn't lose root and only needed to add the new supersu. I had a titanium backup zip which I also flashed.
the problems are as follows
1. No WiFi. attempting to flash KT kernel bricked it. had to start all over
2. Security settings caused a FC. so couldn't enable installation from unknown sources.
3. Restoring user apps using Titanium backup (after freezing all Knox apps) worked. but adding any system apps caused a bad series of forced closures
so unless u have got an unlimited data plan, this is just something to play around with for now it would seem

AFAIK I337M devices share the same hardware with I9505 ones; so can I flash I9505XXUFNA5 onto my I337m?

guerouig said:
AFAIK I337M devices share the same hardware with I9505 ones; so can I flash I9505XXUFNA5 onto my I337m?
Click to expand...
Click to collapse
The bootloader would block odin from accepting the full package. The best u can do is pick n choose parts to flas like i did. And you'll end up with a similar scenario
But you could use this modified version and search for Magical unicorn kernel and see
http://forum.xda-developers.com/showthread.php?t=2608134

@gangsta101: so what bits did you chose to flash? is AP and CP and exclude BL and CSC for instance?

[SUMMARY] Rooting and Roming the i337

The i337, S4 can be a very difficult device to come to grips with. With each firmware version there are new root methods and recoveries that can be used. The purpose of this guide to try to put all those in one place and provide a basic summary. There are many smarter than I who have done the hard work and I'll try to give them credit in this guide. If I've missed anyone please pm me or post here and I'll correct it.
FULL DISCLOSURE, I DON'T OWN THIS DEVICE AND NEVER HAVE. I JUST KNOW A LOT ABOUT IT. IF THERE ARE ANY ERRORS OR IF SOMETHING CAN BE CLEARER PLEASE LET ME KNOW.
The very first thing you need to know is what bootloader version you're on. To determine that go to menu, settings, more, about device. Look at the last three characters of your baseband or buildnumber. You'll be on either mdb, mdl, mf3, mk2, nb1, or nc1. NOTE, if you’ve flashed a modem your baseband may not reflect the current firmware version. Alternately if you’re rooted, for a definitive answer, in a terminal emulator on your phone type the commands:
su (return)
getprop ro.bootloader (return)​​
1. You're on MDB or MDL, your bootloader is easily exploited and you can use a common custom recovery, TWRP or CWM with loki. See this excellent guide by @ xBeerdrioDx, http://forum.xda-developers.com/showthread.php?t=2314494
2. You're on MF3 or MK2. DON'T TRY TO USE TWRP, CWM, ROM MANAGER, or TWRP MANAGER. My personal recommendation is to upgrade to NB1 (once you upgrade you will not be able to go back). To do that see @muniz_ri stock odin tar's at http://forum.xda-developers.com/showthread.php?t=2674223 . You'll need to extract the file using winrar or 7-zip. You'll end up with a .tar.md5 file. Use that in odin's PDA slot or AP slot if you're using odin 3.09. For odin I'd use this, http://www.google.com/url?sa=t&rct=...=9V2YMclcePs8PugxewUhmw&bvm=bv.73231344,d.b2U
NOTE: Using odin will wipe your device so backup everything up on your internal sd card that you want to keep to your PC.
To root, install Safetrap and flash your rom:
If you've used the rootable version to upgrade your firmware you can boot into your device and use towelroot to root it. Towelroot by @geohot can be found here. https://towelroot.com
Now download and install chainfire’s supersu apk from the play store, https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Use Safestrap 3.72 as your custom recovery http://forum.xda-developers.com/showthread.php?t=2448925
Before installing safestrap go to the play store and install SELinux Mode Changer, grant it root access and change mode to “permissive”, https://play.google.com/store/apps/details?id=com.mrbimc.selinux&hl=en
Flash your rom and the nb1 modules, https://www.androidfilehost.com/?w=files&flid=17227 Thanks to @guut13
NOTE: you can only use the stock rom slot
3. You’re on NB1. DON'T TRY TO USE TWRP, CWM, ROM MANAGER, or TWRP MANAGER. I’d take the OTA to NC1 which is rootable. Use towelroot to root and Safestrap 3.72, see above, but flash the nc1 modules.
4. You’re on NC1. DON'T TRY TO USE TWRP, CWM, ROM MANAGER, or TWRP MANAGER. Use towelroot to root and Safestrap 3.72, see above, but flash the nc1 modules
5. You’re on NI1. DON'T TRY TO USE TWRP, CWM, ROM MANAGER, or TWRP MANAGER. Use this by @muniz_ri http://forum.xda-developers.com/galaxy-s4-att/general/how-to-root-i337ucufni1-t2881298
And the most important link I can give you is the great work of @guut13 which is mandatory reading for everyone on the i337, http://forum.xda-developers.com/showthread.php?t=2616221

Thank you so much for posting this! You really ron the fear out of it for me.

Recoverable or brick?
I am so very bummed I did not come across this thread before I jumped feet first into playing with my new S4. Suffice it to say I did not know of the pitfalls involved, nor was I aware of the different S4 iterations.
I did not pay close attention to any of the things I was supposed to note. I know it's an i337 from ATT and that it was running 4.4.2. I rooted using towelroot and then tried to install TWRP using their interface available on Play marketplace. When I rebooted, I found that I was stuck in Odin mode. Having very quickly come up to speed on the complexities address in the OP, I'm going to try using the 4.4.2 Odin OTA all in one linked above to bring everything back to stock. Odin does connect and recognize the phone.
My question is...is there any hope this might work? I have no idea if I'm on MDB, MK2, MF3 or NB1. No way for me to find out that I know of.
Thanks!

magdelaine said:
I am so very bummed I did not come across this thread before I jumped feet first into playing with my new S4. Suffice it to say I did not know of the pitfalls involved, nor was I aware of the different S4 iterations.
I did not pay close attention to any of the things I was supposed to note. I know it's an i337 from ATT and that it was running 4.4.2. I rooted using towelroot and then tried to install TWRP using their interface available on Play marketplace. When I rebooted, I found that I was stuck in Odin mode. Having very quickly come up to speed on the complexities address in the OP, I'm going to try using the 4.4.2 Odin OTA all in one linked above to bring everything back to stock. Odin does connect and recognize the phone.
My question is...is there any hope this might work? I have no idea if I'm on MDB, MK2, MF3 or NB1. No way for me to find out that I know of.
Thanks!
Click to expand...
Click to collapse
Yes, there's a lot of hope it'll work
Sent from my Nexus 5 using XDA Free mobile app

It worked!
jd1639 said:
Yes, there's a lot of hope it'll work
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you so very much for saving me from myself. It worked! It took a long time to download but once I had it the process went off without a hitch. 30 minutes later I had it rooted again, but I think I'll hold off on trying any new ROMs and just use Titanium to remove the bloatware and stick with what I have.
Whew!

magdelaine said:
Thank you so very much for saving me from myself. It worked! It took a long time to download but once I had it the process went off without a hitch. 30 minutes later I had it rooted again, but I think I'll hold off on trying any new ROMs and just use Titanium to remove the bloatware and stick with what I have.
Whew!
Click to expand...
Click to collapse
Just freeze bloat ware on titanium, don't delete it. That way if you freeze something that's needed you can simply unfreeze it
Sent from my Nexus 5 using XDA Free mobile app

Galaxy s4 question
Hello im new to this rooting stuff but i want to root my Samsung Galaxy s4 At&t i337 4.4.2 , Baseband version :I337UCUFNC1. I have multiple questions for you. If i root with towel root will i lose my service with att because i see on alot of videos it shows no sim card inserted when you follow through with this process. Secondly can you give me a guide step by step to root and what needs to be done. thank you.

rizuh1234 said:
Hello im new to this rooting stuff but i want to root my Samsung Galaxy s4 At&t i337 4.4.2 , Baseband version :I337UCUFNC1. I have multiple questions for you. If i root with towel root will i lose my service with att because i see on alot of videos it shows no sim card inserted when you follow through with this process. Secondly can you give me a guide step by step to root and what needs to be done. thank you.
Click to expand...
Click to collapse
When you say lose at&t service are you referring to your warranty, if so, yes if you're rooted when you go in for service. To root, just download the towelroot app. That's the only step by step you need.
Before you root ask your self why are you rooting. If you don't have a good answer then don't root. Don't do it just because you can.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
When you say lose at&t service are you referring to your warranty, if so, yes if you're rooted when you go in for service. To root, just download the towelroot app. That's the only step by step you need.
Before you root ask your self why are you rooting. If you don't have a good answer then don't root. Don't do it just because you can.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you on the second question. What i mean by my service is like your mobile data, like 4G or 4GLTE. do lose that in the process when you root?

rizuh1234 said:
Thank you on the second question. What i mean by my service is like your mobile data, like 4G or 4GLTE. do lose that in the process when you root?
Click to expand...
Click to collapse
No, rooting does not affect that in any way.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
No, rooting does not affect that in any way.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
can NC1 be rooted? 4.4.2 aswell.

rizuh1234 said:
can NC1 be rooted? 4.4.2 aswell.
Click to expand...
Click to collapse
Did you read the op? Yes, use towelroot
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Did you read the op? Yes, use towelroot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Do i need to backup my files before i root?

rizuh1234 said:
Do i need to backup my files before i root?
Click to expand...
Click to collapse
I have baseband I337MVLUFNE1 on my Rogers S4 running 4.4.2. (Build number also ends in NE1).
I don't see NE1 anywhere on the OP. What does this mean? I was looking to try CyanogenMod but am afraid I may break something.

No you don't
Sent from my SGH-I337 using XDA Free mobile app

DrZEUS said:
I have baseband I337MVLUFNE1 on my Rogers S4 running 4.4.2. (Build number also ends in NE1).
I don't see NE1 anywhere on the OP. What does this mean? I was looking to try CyanogenMod but am afraid I may break something.
Click to expand...
Click to collapse
This thread was written specifically for the i337, not the i337m. You have an i337m. You have an unlocked bootloader and can use twrp or cwm recoveries.
Sent from my Nexus 5 using XDA Free mobile app

Thanks jd1639. I didn't realize there was a difference between i337 and i337m.

DrZEUS said:
Thanks jd1639. I didn't realize there was a difference between i337 and i337m.
Click to expand...
Click to collapse
This is a good place for you to start
http://forum.xda-developers.com/showthread.php?p=42320391
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
This is a good place for you to start
http://forum.xda-developers.com/showthread.php?p=42320391
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I read your mind...was starting to read that same thread when you suggested it.
Thanks again!

I have root now thanks. For some reason safestrap is disabled and how do I get a custom rom?
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app