Database Info

[Q] Veizon S3 Insurance claim, pre-rooted? OTA Update? Not sure what's been done

Hello all! I need to know what has been done to my insurance replacement phone, and how I can safely update my phone to VRBMV1.
The short version...
I hard bricked my Verizon Galaxy S3 phone by installing a custom ROM wrong, I got an insurance replacement that came pre-rooted, has Clockworkmod already installed and I believe has an unlocked bootloader. Clockworkmod stopped the OTA Update, but I want the update installed. I need to know what to do.
The long, more informative version...
So, I wanted to increase the volume of my Bluetooth headset and after trying different apps and nothing working, I found some modded system files that had a great review that increase all of the phones volumes. The instructions said the phone had to be rooted. Well I rooted the phone and the modded files didn't work. So reading the reviews of the mod, people were saying it worked great with the OMEGA AOPK ROM. So I rooted my Verizon Galaxy S3 i535 phone and installed a the custom rom and hard bricked my phone. I didn't pay enough attention and installed a rom for an i9000 not a i535, at least I think that's what happened... Anyways, I got a new phone through my insurance and the screen wouldn't rotate, so they sent me a 2nd replacement. I got that one in the mail today and it appears to already be rooted, and possibly have an unlocked bootloader, but i'm not sure how to do the VRBMV1 OTA update now.
The first thing the phone did once I activated it was do an OTA update from Verizon, so I let it. Clockworkmod popped up and said it couldn't verify the publisher for the files it was trying to install and asked if I wanted to continue. I clicked NO.
So, since I recently found out what Clockworkmod was and know it's not stock on the S3, I knew someone had done something to the phone. So i'm trying to figure out what exactly has been done, and if it's safe for me to do the OTA update or not.
After searching this forum I found out I can use an app to see if the phone is rooted or not, so I checked it and the app say "root access granted". I also see an app already installed on the phone called SuperSU. So I now know the phone is rooted.
After searching more I found one way to possibly tell if the bootloader is unlocked is to restart the phone, if the Samsung logo goes away within 1 second you probably have an unlocked bootloader. The logo goes away instantly on my phone, so i'm guessing the bootloader is unlocked?
The rest of the phone appears to be the same visually and settings wise as my old S3, so I think it's the stock ROM. "About phone" says Android Version 4.1.2 - Baseband Version i535VRBMB1 - Kernel Version 3.0.13-861013 [email protected] #1 SMP PREEMPT Thu Feb 14 15:16:58 KST 2013 - Build Number JZ054K.I535VRBMB1. Putting the phone Download Mode says everything is "Official", whereas it said "Custom" just before I bricked my old phone.
Sorry this is getting so long. I'll get to the questions now...
From what I've read on the forum, it appears to not be a good idea to do the OTA updates. Without knowing what else has been done to the phone, how can I "safely" get VRBMV1 installed? It appears to fix some problems with battery life and 4G signal, so it would be nice to have.
I for sure don't want to brick another phone as my insurance most likely will not like me anymore. So i'm not sure i'm comfortable trying anymore custom ROMs that already have the update in them. Is there a way to take the phone back to factory with having any of the backups that may or may not have been done before the phone was modded?
Thank you very much!

Odin flash VRBMB1 tar.

SlimSnoopOS said:
Odin flash VRBMB1 tar.
Click to expand...
Click to collapse
And you will be on the very latest OEM OTA version , no need to worry about updates. QED

SlimSnoopOS said:
Odin flash VRBMB1 tar.
Click to expand...
Click to collapse
That worked PERFECT! Thank you very much!!!! :good:

You may have gotten one of my 5 returns...
However i am fairly certian I returned them with the stock recovery, and rom unless I missed that step on one or two... I was having screen issues when they sent me refurbs
Sent from my SCH-I535 using xda premium

Colomonster said:
You may have gotten one of my 5 returns...
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Well everything seems to work perfectly on it, so thank you for not breaking it! :fingers-crossed:

[Q] Stock NE1 keeping unlocked bootloader possible?

I have spent the last week researching how to proceed with updating my Verizon Galaxy S3, but haven't found a clear concise answer pertaining to my current scenario. I thought a thread with a definitive answer would help others in my same boat save alot of time.
The last time I updated my phone was with a stock rooted MB1 rom with CWM 6023 recovery and 3.0.31-861013 kernel (2/14/13) and unlocked bootloader. Knowing that nothing good has ever come from taking OTA updates, I then removed the OTA Certs. I've kept my fingers crossed with the releases of ML1, MF1, and ND3 hoping that they would be better than MB1 but public opinion of the downsides has kept me from updating to any of these previous versions.
Now I'm DYING to update to Kit Kat and a better modem/radio than what I currently have. I've had really really poor experiences with a variety of handsets over the last 4 years using custom roms like AOSP, Cyanogen, etc. Therefore, I typically like to run a stock rooted version of whatever the current rom at the time is and remove some of the bloat myself or often there will be bloatware free stock roms for various handsets floating around so those are what I gravitate toward. More often than not custom roms have too many bugs (ie, camera not working or mms failures, etc) for production use.
So that being said, what would be the best course of action for someone such as myself to get on NE1 (or a really, really, really solid KitKat with NO bugs) and keep an unlocked bootloader for future flexibility. And, more importantly be able to update the modem/radio without locking the bootloader (as I've read some have found their bootloader locked after modem update)?
Any advice would be greatly appreciated.

Muleguy said:
I have spent the last week researching how to proceed with updating my Verizon Galaxy S3, but haven't found a clear concise answer pertaining to my current scenario. I thought a thread with a definitive answer would help others in my same boat save alot of time.
The last time I updated my phone was with a stock rooted MB1 rom with CWM 6023 recovery and 3.0.31-861013 kernel (2/14/13) and unlocked bootloader. Knowing that nothing good has ever come from taking OTA updates, I then removed the OTA Certs. I've kept my fingers crossed with the releases of ML1, MF1, and ND3 hoping that they would be better than MB1 but public opinion of the downsides has kept me from updating to any of these previous versions.
Now I'm DYING to update to Kit Kat and a better modem/radio than what I currently have. I've had really really poor experiences with a variety of handsets over the last 4 years using custom roms like AOSP, Cyanogen, etc. Therefore, I typically like to run a stock rooted version of whatever the current rom at the time is and remove some of the bloat myself or often there will be bloatware free stock roms for various handsets floating around so those are what I gravitate toward. More often than not custom roms have too many bugs (ie, camera not working or mms failures, etc) for production use.
So that being said, what would be the best course of action for someone such as myself to get on NE1 (or a really, really, really solid KitKat with NO bugs) and keep an unlocked bootloader for future flexibility. And, more importantly be able to update the modem/radio without locking the bootloader (as I've read some have found their bootloader locked after modem update)?
Any advice would be greatly appreciated.
Click to expand...
Click to collapse
Unfortunately, the ML1 update locked the bootloader and that hasn't changed with NC1 or NE1 (as far as we know). MF1 is the latest update I know of that still has the option for an unlocked bootloader. I've never used custom ROMs (but would very much like to) but I am currently on NE1 so I can't. Granted, I will say that Kitkat is a good update and things are running well. HOWEVER, from someone who would LOVE to have that option for an unlocked bootloader, I would personally discourage updates that would lock your bootloader. But the choice is yours.
Quick question (to someone with a little more expertise), If you were still on an update BEFORE MF1, and you had the option to download it OTA, could you extract the update.zip from /cache/fota like we did for the Kitkat update and distribute it so people could then flash it with Odin (and get unlocked bootloaders)? Or am I missing some flaw with that plan?

Muleguy said:
I have spent the last week researching how to proceed with updating my Verizon Galaxy S3, but haven't found a clear concise answer pertaining to my current scenario. I thought a thread with a definitive answer would help others in my same boat save alot of time.
The last time I updated my phone was with a stock rooted MB1 rom with CWM 6023 recovery and 3.0.31-861013 kernel (2/14/13) and unlocked bootloader. Knowing that nothing good has ever come from taking OTA updates, I then removed the OTA Certs. I've kept my fingers crossed with the releases of ML1, MF1, and ND3 hoping that they would be better than MB1 but public opinion of the downsides has kept me from updating to any of these previous versions.
Now I'm DYING to update to Kit Kat and a better modem/radio than what I currently have. I've had really really poor experiences with a variety of handsets over the last 4 years using custom roms like AOSP, Cyanogen, etc. Therefore, I typically like to run a stock rooted version of whatever the current rom at the time is and remove some of the bloat myself or often there will be bloatware free stock roms for various handsets floating around so those are what I gravitate toward. More often than not custom roms have too many bugs (ie, camera not working or mms failures, etc) for production use.
So that being said, what would be the best course of action for someone such as myself to get on NE1 (or a really, really, really solid KitKat with NO bugs) and keep an unlocked bootloader for future flexibility. And, more importantly be able to update the modem/radio without locking the bootloader (as I've read some have found their bootloader locked after modem update)?
Any advice would be greatly appreciated.
Click to expand...
Click to collapse
You are basically going to have to wait until a dev puts out a stock, rooted, knoxless ROM based on NE1. I've never heard of a modem flash locking a bootloader. Modern has nothing to do with the bootloader. Anyone who said this happened to them most likely flashed the firmware or full factory tar instead of the modem file by accident.
Sent from the Shark Tank using XDA Premium 4 mobile app
---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------
JacobManning17 said:
Unfortunately, the ML1 update locked the bootloader and that hasn't changed with NC1 or NE1 (as far as we know). MF1 is the latest update I know of that still has the option for an unlocked bootloader. I've never used custom ROMs (but would very much like to) but I am currently on NE1 so I can't. Granted, I will say that Kitkat is a good update and things are running well. HOWEVER, from someone who would LOVE to have that option for an unlocked bootloader, I would personally discourage updates that would lock your bootloader. But the choice is yours.
Quick question (to someone with a little more expertise), If you were still on an update BEFORE MF1, and you had the option to download it OTA, could you extract the update.zip from /cache/fota like we did for the Kitkat update and distribute it so people could then flash it with Odin (and get unlocked bootloaders)? Or am I missing some flaw with that plan?
Click to expand...
Click to collapse
Flashing that update.zip file through ODIN before a dev had a chance to remove Knox and the locked down bootloader would be the same exact thing as accepting the OTA. You would then be locked down.
Sent from the Shark Tank using XDA Premium 4 mobile app

landshark68 said:
You are basically going to have to wait until a dev puts out a stock, rooted, knoxless ROM based on NE1. I've never heard of a modem flash locking a bootloader. Modern has nothing to do with the bootloader. Anyone who said this happened to them most likely flashed the firmware or full factory tar instead of the modem file by accident.
Sent from the Shark Tank using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I ran across a thread on here just this morning where someone was trying to update just the modem and ended up with a locked bootloader. The replies suggested that Samsung may have slipped something in with the modem file this go around. That's why I included it in this question. I will have to try to find the link to the other thread when I have more time later.

Muleguy said:
I ran across a thread on here just this morning where someone was trying to update just the modem and ended up with a locked bootloader. The replies suggested that Samsung may have slipped something in with the modem file this go around. That's why I included it in this question. I will have to try to find the link to the other thread when I have more time later.
Click to expand...
Click to collapse
You might be referring to this post in the general section. I am still unsure how they managed to do this if they downloaded the 20 MB VRUCML1 modem from our S3 forum. There is only one person whom I know to have extracted it and that is Invisiblek. Not a single other person before this user has mentioned having their bootloader locked from installing the VRUCML1 modem in CWM or TWRP. I really did not understand what they were trying to say so I just kept the convo moving in a different direction.

landshark68 said:
Flashing that update.zip file through ODIN before a dev had a chance to remove Knox and the locked down bootloader would be the same exact thing as accepting the OTA. You would then be locked down.
Sent from the Shark Tank using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm on ML1 unlocked bootloader/rooted from here
http://forum.xda-developers.com/showthread.php?t=2591895
If I flash NE1 via ODIN will it wipe my phone resulting in a clean NE1 with locked bootloader or will it be a non-destructive upgrade to fully stock/locked NE1?

lexluthor said:
I'm on ML1 unlocked bootloader/rooted from here
http://forum.xda-developers.com/showthread.php?t=2591895
If I flash NE1 via ODIN will it wipe my phone resulting in a clean NE1 with locked bootloader or will it be a non-destructive upgrade to fully stock/locked NE1?
Click to expand...
Click to collapse
Not sure whether the tar file you can download from sammobile will wipe your phone, but the tar file provided by open1your1eyes0 in the below linked thread will not wipe your phone. Either way, you will be on locked down NE1. Read the disclaimer at the top of the OP in open1your1eyes0's thread:
http://forum.xda-developers.com/showthread.php?t=2795659

landshark68 said:
Not sure whether the tar file you can download from sammobile will wipe your phone, but the tar file provided by openyoureyes1 in the below linked thread will not wipe your phone. Either way, you will be on locked down NE1. Read the disclaimer at the top of the OP in openyoureyes1's thread:
http://forum.xda-developers.com/showthread.php?t=2795659
Click to expand...
Click to collapse
I don't care if I'm locked going forward. So if I flash that, after I'll still have all my apps and appdata and be on NE1, locked? And then I can root with towelroot?

lexluthor said:
I don't care if I'm locked going forward. So if I flash that, after I'll still have all my apps and appdata and be on NE1, locked? And then I can root with towelroot?
Click to expand...
Click to collapse
I believe that is correct. I thought I saw a few people in the 4.4.2 update thread post that towelroot worked on NE1. May want to read the last few pages of that thread just to make sure about towelroot.

lexluthor said:
I don't care if I'm locked going forward. So if I flash that, after I'll still have all my apps and appdata and be on NE1, locked? And then I can root with towelroot?
Click to expand...
Click to collapse
That is correct. Towelroot works just fine with NE1
Sent from my SCH-I535 using XDA Premium 4 mobile app

landshark68 said:
I believe that is correct. I thought I saw a few people in the 4.4.2 update thread post that towelroot worked on NE1. May want to read the last few pages of that thread just to make sure about towelroot.
Click to expand...
Click to collapse
So far, looking ok. I flashed via ODIN and now it's at Android is upgrading and it's optimizing 502 apps, so looks like the apps are still there.
Hopefully towelroot works fine and then I can tweak my system settings back, install xposed and I'm good to go.
---------- Post added at 09:17 PM ---------- Previous post was at 08:25 PM ----------
lexluthor said:
So far, looking ok. I flashed via ODIN and now it's at Android is upgrading and it's optimizing 502 apps, so looks like the apps are still there.
Hopefully towelroot works fine and then I can tweak my system settings back, install xposed and I'm good to go.
Click to expand...
Click to collapse
All went great. It took a good half hour after the upgrade for the CPU to stop being pegged at 100% and have the phone be responsive again.
Very easy, it kept all of my applications and settings and I didn't really need to do much other than towelroot and re-install xposed.
I'm due for an upgrade soon anyhow, so I didn't really want to go through a lot of work getting to Kitkat.

Towel root not working any longer. Keep getting unsupported device with NE1 .. Ugh ..

[GUIDE] Straight Talk Galaxy S4 (S975L) running AT&T towers Guide and Info

If you are using the Straight Talk Galaxy S4 with build number
JSS15J.S975LUDUANB1 and just want root and simple recovery
You can root using towelroot.
SuperSU will also deactivate Knox.
Safestrap version 3.72 works for getting a proper recovery installed with the option at boot for system or recovery. Note that it will say safestrap is disabled but will still allow your choice to boot into recovery.
Make a backup in recovery as soon as you can.
Or if you want awesomeness!! Do THIS!!
Here is the definitive guide for those wondering what to do that will work and be stable and AWESOME!
From the beginning:
1.Root with towelroot (search) AND install SuperSU from the play store.
2.Install the latest recovery from here using the DD method listed directions from the TWRP site. This is from T-Mobile and works! http://forum.xda-developers.com/showthread.php?t=2263001
MAKE A BACKUP!!! DO IT! No more messing around with Safestrap and the bitter warnings!
To get into recovery hold "home+volume up" during boot. Whoooo!!!!
3. Install the Lollipop gpe ROM from here: http://forum.xda-developers.com/showthread.php?t=2539361
This uses the aroma installer and works well.
You may, or may not have to input *#6463*# into dialpad to change settings to LTE etc.. This adjustment may alsobe in the ROM settings!
4. Optional - install the googy kernel
I like this kernel better though there isn't a huge difference from the hulk kernel. Make sure to install the GE edition 1.3.0. NOT TOUCHWHIZ! : http://forum.xda-developers.com/showthread.php?t=2741181
ENJOY!

sleekmason said:
Moderator, please move to relevant forum or incorporate into the general info thread if this isn't the right place.
If you are using the Straight Talk Galaxy S4 with build number
JSS15J.S975LUDUANB1,
You can root using towelroot.
SuperSU will also deactivate Knox.
Safestrap version 3.72 works for getting a proper recovery installed with the option at boot for system or recovery. Note that it will say safestrap is disabled but will still allow your choice to boot into recovery.
Make a backup in recovery as soon as you can.
The zip to allow tethering WILL NOT work, and you will be stuck on the Samsung logo.
Xposed works well, but do not use the option in gravity box to add the recovery option to your power menu or your device will freeze upon pressing the power button.
Greenify works well.
Advise against ROM installation, as well as initial upgrade. You will lose app to SD ability if you upgrade.
The boot loader is not unlocked, so no cool kernels here
Click to expand...
Click to collapse
I was able to use towelroot and my att s4 is running on the att towers with straight talk.

mrphotoman said:
I was able to use towelroot and my att s4 is running on the att towers with straight talk.
Click to expand...
Click to collapse
Have you downloaded safestrap? Or tried anything with Xposed?

sleekmason said:
Have you downloaded safestrap? Or tried anything with Xposed?
Click to expand...
Click to collapse
No not yet, I just got the phone so I haven't done a lot to it yet. I was able to get tethering working and it was pretty easy and I got a nice extended battery case for it yesterday that I love. Other than that I haven't had time to do a lot else to it.

mrphotoman said:
No not yet, I just got the phone so I haven't done a lot to it yet. I was able to get tethering working and it was pretty easy and I got a nice extended battery case for it yesterday that I love. Other than that I haven't had time to do a lot else to it.
Click to expand...
Click to collapse
Can you tell me what you did for tethering? I tried once but was unable to get it to work.

sleekmason said:
Can you tell me what you did for tethering? I tried once but was unable to get it to work.
Click to expand...
Click to collapse
sure, i have a how to vid but i am waiting on the mod to approve it so i can post it. it definately works on the newest updated att phone

mrphotoman said:
sure, i have a how to vid but i am waiting on the mod to approve it so i can post it. it definately works on the newest updated att phone
Click to expand...
Click to collapse
Excellent! Please post a link to it here as well when you get it uploaded

Updated
See first post

I used tmo twrp. Flashed tmo and att roms. I also have the Odin file. I am not sure but I am on the s975L which I thought was att not sure but pretty sure. However it also says i337 underbattery ...I've tried more tmo roms than anything. No safestrap but I might try that later. Seems we don't have locked bootloader. This is great. However unlock is next for me. Having a blast hacking the hell out of it. So far I have had no issues. Again I'm not new to this. Lol. It's an addiction. I have sprint note 4 as my DD. So this is my fix. Lmao.
Sent from my SM-N910P using XDA Free mobile app

Droid2drummer said:
I used tmo twrp. Flashed tmo and att roms. I also have the Odin file. I am not sure but I am on the s975L which I thought was att not sure but pretty sure. However it also says i337 underbattery ...I've tried more tmo roms than anything. No safestrap but I might try that later. Seems we don't have locked bootloader. This is great. However unlock is next for me. Having a blast hacking the hell out of it. So far I have had no issues. Again I'm not new to this. Lol. It's an addiction. I have sprint note 4 as my DD. So this is my fix. Lmao.
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
As far as I know, the bootloader IS locked, but can be bypassed using Loki to patch kernels for custom roms. Glad to see somebody else on this phone

sleekmason said:
As far as I know, the bootloader IS locked, but can be bypassed using Loki to patch kernels for custom roms. Glad to see somebody else on this phone
Click to expand...
Click to collapse
That's strange. If it was locked I wonder how I've used tmo twrp no loki or SS and flashed tons of roms so far...I just odined back from a modem issue. But rerooted now off to get some modems etc...boot and all. I'll keep reporting. Thank you bro. I maintain many devices and carriers and am about to start a channel on YouTube. I do music writing now with keyboard. Now I'm just getting a hand on s4 straight talk and will make a list of all working roms.
Sent from my SM-S975L using XDA Free mobile app

Droid2drummer said:
That's strange. If it was locked I wonder how I've used tmo twrp no loki or SS and flashed tons of roms so far...I just odined back from a modem issue. But rerooted now off to get some modems etc...boot and all. I'll keep reporting. Thank you bro. I maintain many devices and carriers and am about to start a channel on YouTube. I do music writing now with keyboard. Now I'm just getting a hand on s4 straight talk and will make a list of all working roms.
Sent from my SM-S975L using XDA Free mobile app
Click to expand...
Click to collapse
True.. I don't know as much about it as I like. I just wasn't able to use fastboot or "unlock" using fastboot.
If you are working with the modems let me know how that goes, and maybe you can help with an issue I'm having? My GPS won't work after trying a ROM with safestrap. What I've posted here is a result of trying to fix it. I consistently show NO satellites. I consulted the local phone fixers to no avail. I was wondering if it could be related to a modem issue? I think the ROM I first tried did something deep to my phone, though Phone Info showed at the time everything to be original concerning baseband etc.. And a factory reset didn't help.
I'm at the point now of thinking its hardware rather than software but the coincidence to trying the ROM was too high.

Hey everyone!
I am working with this phone and am trying to get a backup modem, can you please ,make a suggestion?
Also are there any ROMs that allow easy access to umts menu through servicemenu? I know the base firmware cripples this and I'm trying to get a work around!
thanks in advanced!

[Q] Flash NE1 baseband (??), Or Stay With 4.2.2 baseband?

Going back to an S3 after a year. A friend of mine is giving me his old S3, I plan on transferring the motherboard over from MY old S3 which was broke. My motherboard is rooted and was last running PA 3.99. It has the old JB baseband. However, I want to keep root and flash whatever the hell I please without an issue like I use to with the S3. Since I've been out of the loop with the S3 for a year I need catching up. I've been reading all around about the bootloader issues since the KitKat update. Bottom line - based on wanting to keep root and flash whatever the hell; should I just stay away from the NE1 basedband? Or is just the new boot loader I want to stay away from?
Thanks in advance.

RoxRedEye said:
Going back to an S3 after a year. A friend of mine is giving me his old S3, I plan on transferring the motherboard over from MY old S3 which was broke. My motherboard is rooted and was last running PA 3.99. It has the old JB baseband. However, I want to keep root and flash whatever the hell I please without an issue like I use to with the S3. Since I've been out of the loop with the S3 for a year I need catching up. I've been reading all around about the bootloader issues since the KitKat update. Bottom line - based on wanting to keep root and flash whatever the hell; should I just stay away from the NE1 basedband? Or is just the new boot loader I want to stay away from?
Thanks in advance.
Click to expand...
Click to collapse
I suggest stay with your old base band and bootloader if you still want to enjoy custom rom.

buhohitr said:
I suggest stay with your old base band and bootloader if you still want to enjoy custom rom.
Click to expand...
Click to collapse
Right on. Keep the MF1 radio? A year away from the S3 and it's like I'm back in foreign territory.

RoxRedEye said:
Right on. Keep the MF1 radio? A year away from the S3 and it's like I'm back in foreign territory.
Click to expand...
Click to collapse
Yep keep it. It give you zero benefit with new radio and not too worry, you once a flashing legendary, you will be back in no time.:good:

[Q] Question about NE1 bootrom lock issue

I have an sch-i535 Galaxy S3 Verizon phone. I'm not using it on a network anymore and just want to use a custom rom. Is there ANY way to wipe, replace, do something with the locked bootloader since I'm not using the phone as a phone?

oneway2k said:
I have an sch-i535 Galaxy S3 Verizon phone. I'm not using it on a network anymore and just want to use a custom rom. Is there ANY way to wipe, replace, do something with the locked bootloader since I'm not using the phone as a phone?
Click to expand...
Click to collapse
Your out of luck. Locked bootloader means no way to return to a previous version on Android. Even if its not being used as a phone it's basically stuck there. There are jtag services out there to revert back to 4.1.2 but I've heard a lot of mixed thoughts on those
Sent from my N5

ShapesBlue said:
Your out of luck. Locked bootloader means no way to return to a previous version on Android. Even if its not being used as a phone it's basically stuck there. There are jtag services out there to revert back to 4.1.2 but I've heard a lot of mixed thoughts on those
Sent from my N5
Click to expand...
Click to collapse
Since I'm not too concerned about breaking this phone, can someone point me to info on the procedure for using JTAG to go back to 4.1.2? I have found some advertisements but no how-to.

oneway2k said:
Since I'm not too concerned about breaking this phone, can someone point me to info on the procedure for using JTAG to go back to 4.1.2? I have found some advertisements but no how-to.
Click to expand...
Click to collapse
I'd suggest mobile tech videos. There is a thread on xda about them but there are mixed reviews
Sent from my N5

http://forum.xda-developers.com/showthread.php?t=1734949

Moved to Q&A.

If you decide not to go the jtag route you could:
1) install SafeStrap
2) flash SuperliteROM into stock slot
3) flash XPosed and the modules that would make SLR look and act as you like.
This is what I have done with the i535 I picked up that was on NE1.