[HOW TO] Root Galaxy S7 Cricket G930AZ 7.0 Nougat - AT&T Samsung Galaxy S7 Guides, News, & Discussion

Hi All -
For all those wondering how to root the Galaxy S7 for Cricket on Nougat, I just successfully did it last night. I had rooted prior on Marshmallow 6.0.1 with the method here but after a year I had terrible battery and performance issues so wanted to start fresh. I just spent all night last night wiping, flashing and restoring my phone so don't have too much time to write in detail but here is the gist of what I did to successfully achieve upgrade to Nougat 7.0 and root without tripping Knox (after some trial and error)
First I backed up my phone with both Titanium Backup and Samsung Smartswitch (just in case). Also don't forget to manually copy your DCIM picture folder and also your whatsapp backup folder to your SD card
Next I used ODIN and the files found here to return to stock 6.0.1. https://forum.xda-developers.com/att-galaxy-s7/how-to/factory-odin-files-sm-g930az-t3569831. **THIS WILL COMPLETELY WIPE YOUR PHONE**
Next I wanted to upgrade to the newest firmware to see if I would have better performance and battery, and feel like after doing all this work at least I updated my phone. This can be done either via OTA or Samsung Smartswitch. I would recommend Smartswitch because it goes to the newest in one download whereas the OTA updates go sequentially. (However if you don't want the newest and want to stop at an update somewhere in between then you need to use OTA.
Now I successfully have a stock official Cricket Galaxy S7 running 7.0 Nougat with version G930AZUS4BRA1 (Security patch Jan 1, 2018)
Next I followed the instructions in this post https://forum.xda-developers.com/showpost.php?p=75668699&postcount=2573 you may have to reference the original post in that thread to figure some things out. (Note: I know this key part isn't very detailed but why reinvent the wheel. Basically all I had to do was flash those Eng Root files with PrinceComsy Odin and then run the root.bat from command prompt on my PC (I think I had the ADB thing set up from last year) in the order he instructs and it worked, for any q's and issues it is best to reference that thread)
Done! Rooted Cricket Galaxy S7 without tripping Knox. Samsung Pay won't work, but Root Access is achieved.
Restore all of your apps and appdata that you backed up
Thank you to all those on here that helped guide me on this overnight journey!

Question...
Have you experienced any issues so far, because I'm very nervous, but I really want to root my cricket galaxy S7, and I hope I don't mess up, is my first time doing all this steps
---------- Post added at 05:53 PM ---------- Previous post was at 05:44 PM ----------
And what's the root.bat, what do I need to do in step 7?

Another question...
What about the Kevtweaks, do I need to flash it too, and what if I don't have flashfire or a custom recovery???

Related

[Q] How do you know when to update the stock root?

I followed this thread to root: http://forum.xda-developers.com/showthread.php?t=2024207
I think I used the Root66 stock VRALJB I don't remember. My phone model number says SCH-I605, the Android version is 4.1.1, Baseband is I605VRALL4, Build number is JRO03C.I605VRALJB. I don't know if the kernel number is necessary because it's really long to type out, but if you need it I will post it.
Then I unlocked the Bootloader using AdamOutler's thread and now I have a custom TW recovery thing.
When I try to do the update in the Settings, it reboots to the TW recovery and doesn't do anything. When I select to turn on the phone with the TW recovery, it says the update failed. Someone told me that I shouldn't do that update because it's something called OTA and it's bad for my rooted phone, but then how do I know when I need an update? Do I have to check this forum every day for announcements? Which thread will the updates be in?
Thank you
The update option in settings is for Verizon OTA updates. OTA stands for over-the-air. The updates are sent to your phone using the Verizon data network. After the update is loaded onto your phone, it reboots into stock recovery to install the update. Since you have a custom recovery, (TWRP, I believe), the update will always fail. I see that you have the latest baseband, which is really the only reason for taking the OTA update to begin with.
Now that you have a custom recovery, you can flash any of the wonderful 4.1 ROMs that we have at our disposal. I'm currently on Jedi X11 and I recommend that, but there are more to choose from. One word of caution: if you decide to flash a 4.2 ROM, then you can't go back to a 4.1 ROM unless you flash the sd card downgrade .zip file. This is because 4.2 will change your directories around. I will try to link to a thread with the downgrade zip in it on another post.
---------- Post added at 02:40 PM ---------- Previous post was at 02:35 PM ----------
Here is the link to that thread. The downgrade .zip is in the third post
http://forum.xda-developers.com/showthread.php?t=2129787
I haven't installed a ROM because I want to keep all the stock stuff, but if there is a ROM that keeps all the stock but somehow increases speed, then I'd install it but I don't know of any that don't not have some stock stuff removed.
The annoying thing is that the phone keeps telling me to update every 3 days and I don't like it. Is there a way I can stop this without doing anything bad to the phone?
While it's true that all ROMs are not 100% stock, you have to ask yourself what you really want to keep. The ROM I'm running is Touchwiz-based, which means it has all the S-Pen apps along with true multi-window functionality. The stuff that I left coming from pure stock was mostly bloatware.
Either way, if staying on pure stock is all that you want and you want to stop receiving the OTA update notices, then you need to use an app that can freeze other apps. Freezing means that the app is disabled, will no longer appear in your app drawer, and will not start up when you boot the phone. I use Titanium Backup to freeze apps. I recommend freezing apps over outright deleting them because you may inadvertently soft brick your phone that way.
Once you have Titanium Backup or another app with the same functionality, then you need to find and freeze SDM 1.0. It was mentioned in this post here:
http://forum.xda-developers.com/showthread.php?t=2177551
---------- Post added at 09:07 PM ---------- Previous post was at 08:48 PM ----------
I will add that I am not sure why you would unlock your bootloader if you didn't intend to flash any ROMs. The act of unlocking the bootloader is what took away your stock recovery and causes your OTA updates to fail when the installation process starts. You may want to research how to get your phone back to 100% stock if you want to be able to take updates in the future.

OTA unlocked and rooted what to do ?

I'm on 4.1.1 and used one click root & unlock on this forum.
This morning I woke up to an OTA but declined and asked to post pone till 5/13.
What do I do ? I can't afford a bricked phone, nor do I care to grab an update.
I have a feeling on the post pone date it will automatically update.
Sent from my SCH-i605 on Verizon 4G LTE.
SoCalArm said:
I'm on 4.1.1 and used one click root & unlock on this forum.
This morning I woke up to an OTA but declined and asked to post pone till 5/13.
What do I do ? I can't afford a bricked phone, nor do I care to grab an update.
I have a feeling on the post pone date it will automatically update.
Sent from my SCH-i605 on Verizon 4G LTE.
Click to expand...
Click to collapse
I'd also like to know about this. I used CASUAL to root my phone, and while I appreciate the features in the 4.1.2 update, I really don't want to lose root. Any insight into this matter would be appreciated.
Perhaps this is what you are looking for if your just worried about keeping root:
https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=en
Updating won't 'brick' your phone (not sure if that is even possible with this phone without doing something incredibly drastic). Worst case you can always Odin back to stock - just back everything up first. Excellent guide here on how to do that:
http://forum.xda-developers.com/showthread.php?t=2024207
But since you are unlocked I would look into flashing a custom ROM to get the full advantage of it (Jelly Beans or CleanRom are excellent). Tutorial on that is also in the link above.
Hope this helps.
“System software not authorized by Verizon Wireless has been found on your phone.”
heric1 said:
Updating won't 'brick' your phone (not sure if that is even possible with this phone without doing something incredibly drastic). Worst case you can always Odin back to stock - just back everything up first. Excellent guide here on how to do that:
http://forum.xda-developers.com/showthread.php?t=2024207
Click to expand...
Click to collapse
I clicked yes on the update and now I get this message on boot and I can't get to the recovery menu:
“System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help.”
Things I did to my phone prior to this:
- rooted with Framapak
- CWM installed
- Encrypted the internal storage
I'll be praying to Odin tonight...
Use Root Explorer or equivalent and delete the SDM.apk in system/apps. This is the apk that checks for updates.
Oh and if you want to keep root it is never a good idea to accept an OTA update.
http://forum.xda-developers.com/showthread.php?p=36922297
Sent from my SCH-I605 using Tapatalk 2
markustlaumann said:
I clicked yes on the update and now I get this message on boot and I can't get to the recovery menu:
“System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help.”
Things I did to my phone prior to this:
- rooted with Framapak
- CWM installed
- Encrypted the internal storage
I'll be praying to Odin tonight...
Click to expand...
Click to collapse
Odin can be picky after using casual also (try the rooted odin file if stock fails as well, thats what i had to do). You may need to remove the casual drivers as well for odin to recognize the phone, below is a link on that:
https://www.youtube.com/watch?v=zzghcV8HVVk
Also the new release of casual for the 4.1.2 update is set to be released tonight, does anyone know if he could just re-run and to get root and a custom recovery back?
Hopefully not needed.
heric1 said:
You may need to remove the casual drivers as well for odin to recognize the phone
Click to expand...
Click to collapse
Thankfully I was able to get it to boot into recovery mode eventually. Odin and Kies worked correctly to recognize the phone in download mode and I tried the root66 image with no luck. I'm downloading the VRALJB now to see if that works.
Update: I got my phone back to stock using the guide heric1 posted and the "alternate restore" image here. No bricks in my house.
Use this to update won't loose root...
http://forum.xda-developers.com/showthread.php?t=2269736
TaPpEd from my TwEaKeD N2
SoCalArm said:
I'm on 4.1.1 and used one click root & unlock on this forum.
This morning I woke up to an OTA but declined and asked to post pone till 5/13.
What do I do ? I can't afford a bricked phone, nor do I care to grab an update.
I have a feeling on the post pone date it will automatically update.
Sent from my SCH-i605 on Verizon 4G LTE.
Click to expand...
Click to collapse
Take a look at this thread http://forum.xda-developers.com/showthread.php?t=2261478 created by developer beanstown106. Here you will find the latest update modified and placed into a flashable zip file through your custom recovery. If you flash one of those two files that he has, you can have the latest update, keep your root and unlocked bootloader, and be on a stock ROM.
There are two versions of the stock 4.1.2 ROM. The odex version doesn't allow for custom themes to be flash over the stock ROM, while the deodex version does allow for custom themes to be flashed over the stock ROM.
If you don't want 4.1.2 altogether, you can use Titanium Backup or My Backup Pro to freeze the SDM 1.0 file. A slightly more challenging method would be to use Root Explorer or something similar to it to go in and modify the name of the file.
---------- Post added at 10:16 AM ---------- Previous post was at 10:07 AM ----------
For me I use the odex because I have no intention on using themes. My custom ROM and theming days have long passed. All I need is the ability create backups of my stock ROM and the ability to take advantage or root required applications such as Titanium Backup and My Backup Pro.
---------- Post added at 10:26 AM ---------- Previous post was at 10:16 AM ----------
markustlaumann said:
I clicked yes on the update and now I get this message on boot and I can't get to the recovery menu:
“System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help.”
Things I did to my phone prior to this:
- rooted with Framapak
- CWM installed
- Encrypted the internal storage
I'll be praying to Odin tonight...
Click to expand...
Click to collapse
Check out this thread right here http://forum.xda-developers.com/showthread.php?t=2107738 if you are experiencing the "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help" crap. That should get your phone back up and running.
I ended up doing a nandroid back up aswell ass app and data backup and flashing beans. With the help from a admin over at note2forums. So that's my update and I'm digging 4.1.2
I also got something from here that made multi window fantastic and a clear notification bar as well as other goodies.
Sent from my SCH-i605 on Verizon 4G LTE.

[Q] Update from 4.3 to 4.4.2? root removed. Backup actually backed up?

Hello. I have done quite a bit of searching, just can't find a similar enough post to tag on some questions. Sorry if this has been asked...but I did look over a month of posts, and google searching.
I have a Note 3 from September, rooted in October...not sure how I got it done...but I jumped the gun and unrooted it with SU thinking I would be able to OTA to 4.4.2. Nope!
So, I am stuck on 4.3.
My big question is how can I get to 4.4.2 with OUT starting over on the phone.
I guess this is a backup question. I have some settings turned on that indicate that a back up is going somewhere, but I can't confirm, and I don't know what all is backed up.
Pictures are backed up, but I would hate to lose them. They are on SD card anyway...so I realize I could take the card out, but something I read suggested I might lose even the micro-simm card contents. Not sure how that would be possible.
But what about things like Quick Notes, and S Note, and Contacts, and all of my apps that I have installed, and settings for those apps.
When I rooted back in October, it worked with out disrupting anything.
How can I get that to happen now WITH an upgrade to 4.4.2 AND getting it rerooted?
If I can't upgrade with out wiping it clean, I am probably going to stay put. So, then what is the best way to root to get "Wifi Tether Router" back working...as it is the only thing I need the phone rooted for.
Finally, what is the difference between NC5 and NC5D. I saw a recent post of somebody else asking it...but none of the replies gave an answer.
Thanks for any feedback.
I don't know if this will help, but you can give it a try. First, you might want to consider that you are where most of us are trying to get back to ( i.e. 4.3 with no KNOX !!! ). Ok, I would go to Samsung Firmware, and download the latest version of 4.4.2 NC5 to your PC. I would backup that copy of 4.3 on your device to your sdcard then if have an ext sdcard copy it there, or copy that backup to your pc. Most of your Pics and data should be in that backup, that you can copy back later with a file explorer like Root Explorer. Now do a factory wipe. Then take the NC5 zip you got from sammie and extract it to a file on your desktop this will change it to a .tar file. Find a copy of Odin v1.85 don't use the 3.09 version on the Samsung website if possible. Cool, reboot your device into download mode, start odin, plug in your device to your PC. Now, load that extracted file on your desktop into PDA odin, and click start. It will take minute to read Md5 then start installing. You will lose root and recovery !!! Your new bootloader will have KNOX 0x0. So, you will have to start over with the root process, but isn't that half the FUN !!! Chainfires v1.94 supersu will root NC5. As for the difference between NC5 and NC5D, It is my understanding they are the same. The D stands for a version of NC5 that was used by Samsung employees ( i.e. programmers and developers ) in the development of NC5. :fingers-crossed::fingers-crossed:
Lokerd, I see you have read my response. Great!!! I would add the you can root 4.4.2 NC5 several ways. As I said above Chainfires v1.94 SuperSu, and One click autoroot, and Towelroot for 4.4.2. All should root your device without tripping KNOX. However, as soon as you flash a new custom recovery like TWRP or Philz CWM ( my favorite ) it will trip KNOX. If you are out of warranty no biggie, besides you need a custom recovery if you want to get back to your 4.3 backup. ( By the way remember you need the same recovery (i.e. TWRP or CWM ) that you made the 4.3 backup with, now on NC5 just a newer version. This will make it easier to recover the 4.3 backup later. They say the most popular recoveries will recover each others backups, but that is rarely the case.
jimzweb1 said:
First, you might want to consider that you are where most of us are trying to get back to ( i.e. 4.3 with no KNOX !!! ).
Click to expand...
Click to collapse
Thanks for taking the time to reply! And to reply with such a nice well though out steps.
So...I should NOT being trying to upgrade? I can do that...just reroot and be done with this. I really don't want to risk having to lose info I have put on the phone, etc. A few new features is not going to be worth it. But, reading about improved 4g and wifi performance. Wifi calling is not important to me. But it would be nice to have the camera on the lock screen...but I bet I could find something that would do that the rooted phone I had.
So, let me ask this. If I do not care about KNOX, is the process you outlined above any easier?
Thanks!
Drew
lokerd said:
Thanks for taking the time to reply! And to reply with such a nice well though out steps.
So...I should NOT being trying to upgrade? I can do that...just reroot and be done with this. I really don't want to risk having to lose info I have put on the phone, etc. A few new features is not going to be worth it. But, reading about improved 4g and wifi performance. Wifi calling is not important to me. But it would be nice to have the camera on the lock screen...but I bet I could find something that would do that the rooted phone I had.
So, let me ask this. If I do not care about KNOX, is the process you outlined above any easier?
Thanks!
Drew
Click to expand...
Click to collapse
Well, if you are out of warranty, and you don't care about KNOX go ahead and upgrade. But, consider this: One, so where clear the only reason for the 4.3 backup is to get to your pics and data at a later time. Here is a link about trying to go back http://forum.xda-developers.com/showthread.php?t=2630514 Once you install 4.4.2 NC5 ( this will include a new kernel, bootloader, baseband, and OS ) you CANNOT go to back to 4.3. If you try to install the 4.3 backup after you have upgraded to NC5 you will soft brick your phone. Then, there's KNOX what is KNOX, KNOX is security software written by the NSA for Samsung. Now I'm not saying its spyware, but Samsung is !!! You can go to Samsung's website and all the info about KNOX you need is there.
To answer your last question, no. You have to go through all the motions.
If it was me, knowing what I know now. I would stay at 4.3, install an engineering bootloader (read up on bootloaders they are not forgiving if you mess up ) then try to upgrade basebands. Here is a link for NAB engineering bootloader which should be 4.3, http://forum.xda-developers.com/showthread.php?t=2655674 Here is the link for a NC5 baseband, http://forum.xda-developers.com/showthread.php?t=2701837 I believe this will improve your 4G lte.
Last, what I'm running. I run Note 3 "Sprint" 4.4.2 NC5 ( no choice bought the device new with that OS, voided my warranty the second day I owned it ). Rooted with Philz CWM recovery ( hltespr v 6.12.9 ) KNOX disabled and removed. I definitely like 4.4.2 NC5 a lot better than 4.3 my daughters Note 3 had 4.3 before I upgraded to 4.4.2 and rooted it. Here is my XDA website http://forum.xda-developers.com/showthread.php?t=2770729 so if you do upgrade this is a good place to start.
Ok. Sorry for more noob questions.
Ok, the only thing I want to ensure is that I don't lose things like S Note, Action Memo, Contacts, Pictures, apps installed. I just don't want to redo everything. Basically, I just want to upgrade the operating system and have everything up and running like it was...just new OS. Is that possible? I understand what you are saying about not being able to use the back up. I guess I just don't understand if I can upgrade this phone with out having to start back over with everything.
I am not out of warranty (purchased October 2013), but I don't see that it would be a problem. I normally don't break or drop my phone...although I did drop it and picked up a nick a few weeks ago. It was unusual circumstances. Point is...I guess I will worry about warranty issues if that comes up. On the other hand, the home button is a getting a little finicky, so I avoid it...using swipe down, and a notification toggle to go to Home whenever possible.
I don't understand the difference between bootloader vs. flashing vs. upgrading basebands vs. rooting as opposed to those other things. it doesn't help that there are multiple ways to do each of the above.
I think I am in over myhead.
Can you help me figure out what I had done before...as it was working pretty good. I Rooted it to get root access, but not sure how I did it. It was easy, and it didn't erase anything. I think I simply used Odin. Attached is a screenshot of a folder of stuff that I might have used. Can you tell what root method I used?
I think I am just going to go back to what I had...and still with 4.3. I actually looked at my wife's identical phone that is on 4.4.2 and other than wifi calling, I don't see the camera on lock screen, so I don't really think I should be messing with stuff I can't wrap my mind around trying to get to 4.4.2.
lokerd said:
Ok. Sorry for more noob questions.
Ok, the only thing I want to ensure is that I don't lose things like S Note, Action Memo, Contacts, Pictures, apps installed. I just don't want to redo everything. Basically, I just want to upgrade the operating system and have everything up and running like it was...just new OS. Is that possible? I understand what you are saying about not being able to use the back up. I guess I just don't understand if I can upgrade this phone with out having to start back over with everything.
I am not out of warranty (purchased October 2013), but I don't see that it would be a problem. I normally don't break or drop my phone...although I did drop it and picked up a nick a few weeks ago. It was unusual circumstances. Point is...I guess I will worry about warranty issues if that comes up. On the other hand, the home button is a getting a little finicky, so I avoid it...using swipe down, and a notification toggle to go to Home whenever possible.
I don't understand the difference between bootloader vs. flashing vs. upgrading basebands vs. rooting as opposed to those other things. it doesn't help that there are multiple ways to do each of the above.
I think I am in over myhead.
Can you help me figure out what I had done before...as it was working pretty good. I Rooted it to get root access, but not sure how I did it. It was easy, and it didn't erase anything. I think I simply used Odin. Attached is a screenshot of a folder of stuff that I might have used. Can you tell what root method I used?
I think I am just going to go back to what I had...and still with 4.3. I actually looked at my wife's identical phone that is on 4.4.2 and other than wifi calling, I don't see the camera on lock screen, so I don't really think I should be messing with stuff I can't wrap my mind around trying to get to 4.4.2.
Click to expand...
Click to collapse
Cool, your version of 4.3 should be NAB and no KNOX. If this is the case then you should be able to root, and return back to stock, if you have say a hardware issue with your device and have to return it under warranty. So, according to your last post image on 10/24/2013 you used CF Autoroot, if you want to read up here is the link to that http://forum.xda-developers.com/showthread.php?t=2466423
Now to get to the latest version of CF Autoroot you need to go to ChainFires ( CF ) repository here is the link http://autoroot.chainfire.eu/ just find the model of your phone and click on File to download. Put that file on your desktop, now go to your android downloads copy and paste Odin v1.85 to your desktop. Click on Odin extract, and open it, now click on PDA a box will open, now select desktop and click on CF Auotroot. It should come up in Odin next to PDA. Now boot your device into download mode, then connect to your PC. In the upper left hand box will light up COMM: with some number in green, blue, or yellow doesn't matter just telling you that a connection was made. Now click start on the bottom of Odin, sit back and watch the magic!
When it says pass your done. Now reboot your phone if doesn't do it by itself go to your app drawer and see if SuperSu is there. To install the Recovery just follow the same steps just substitute the recovery .tar file in place of CF Autroot. I see you have ChainFires v1.65 SuperSu the latest version is v2.01 here is the link http://forum.xda-developers.com/showthread.php?t=1538053. If you use CF Autoroot it will probably install the latest version of SuperSu automatically.
I see on 10/25/2013 you downloaded CWM recovery for hltespr ( sprint ) here is the link for Philz CWM http://forum.xda-developers.com/showthread.php?t=2596001 the latest version for sprint is 6.12.9 I don't use his unified all in one recovery version, I use the sprint version, but the choice is yours. :fingers-crossed:
jimzweb1 said:
Cool, your version of 4.3 should be NAB and no KNOX.
Odin v1.85 to your desktop.
Click to expand...
Click to collapse
Thanks for the continued help. Just about ready to reroot the thing.
So, you mention using 1.85...is that only because that is what I have? The latest CF-Auto-Root came with 3.07 but I had already downloaded 3.09 a couple of days ago trying to figure stuff out. I also saw a warning about using the latest Odin...but I think it applied to trying to do the Kindle Fire, which I determined was 3.3 and not able to be rooted with out a special cable, which I have ordered.
Anyway, does it matter if I use the 3.07 that came with the latest version of CF-A-R? Should I use 3.09? Or def stick with 1.85.
EDIT #5: I end up using 1.85 and the original Root, then the new ROOT. So, does it matter that I used the Root from October vs the newest one or older Odin vs. newer? I have it up now, so it is just a matter of tryingt o figure this out.
BTW, I thought I had bricked my phone...went back and read YOUR instruction again, and got it restarted. The instructions on the main CF-A-R thread do not make it very clear.
Thanks a bundle!
Great !!! It doesn't matter which version of Odin you use, as long as it gets the job done. As for CF Autoroot, after your done rooting and boot the device back up. It my take awhile but you will automatically be asked update your apps, and SuperSu will update binarys at that time.

[Q] Could use a little help...I545 Have not taken Lollipop OTA

I've had my VZ S4 since sometime around Dec of 2013. Previously was on a DroidX, I've really honestly never had any problems rooting or installing custom rom's on my phones (A BIG THANK YOU TO ALL OF YOU HERE that made that possible) so I'm not a noob...but I'm not an expert either. I usually wait and read a lot of threads, follow the instructions and I've always been good to go. My S4 started at MK2, (took the OTA right out of the box, now I now better ) and with the help of K1mu's post on rooting the S4 with Saferoot everything went off with out a hitch (thank you!!). After successfully rooting the phone, I installed Safestrap, backed up the stock rom slot, created a custom rom slot and installed Hyperdrive 11...everything is working flawlessly.
So fast forward a year to KitKat I returned to XDA...read and read and read and followed the Dev's instructions and was good to go again. I know it involved Safestrap-I545-3.75-KitKat-A03.apk, TowelRoot, Odin and ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user_low_ship_Multi_Cert_Tar.md5. Definitely was one of muniz_ri post. Any way I basically used Odin...flashed back to factory stock followed muniz_ri post and was good to go again with KitKat(Thank You!!)
So now to the present, about a week or so ago I had an OTA screen pop asking to update, it actually showed 2 updates available (don't know if there is a log in the S4 that keeps track of the updates). So I came back here of course and started reading and reading and reading...and I was ready to begin the process in this thread by muniz_ri: http://forum.xda-developers.com/gal...-to-update-to-i545oc1-5-0-1-keeproot-t3096558 which again I am sure would have went flawlessly. Then I had an accident...I had been dismissing the update (it popped up a lot ) when the unthinkable happened...I pressed yes, the phone went thru the update process and I don't know what update it was but it wasn't Lolllipop...so I was like phewwww, clicked on my RootCheck (JRummy) and it said Rooted 4.4.2 KitKat (NK4), SuperSu 2.46 so I figured everything was ok. Not so, I don't know what the upgrade was but I no longer have root or access to safestrap, SuperSu or any apps that require root...and this is where I need guidance from the masters. I have a TWRP/Safestrap back up (stock-2014-12-08--19-33-37 KOT49H.I545VRUFNK1) from right after rooting for KitKat, nothing else...just root I'm pretty sure of that. So what would be the best way to fix? Is there a way to re-root the phone in it's present condition? Can I use the TWRP back up some how with out SafeStrap? How far back can I down grade with Odin using a VWZ factory image? Any idea what happened with the update prior to Lollipop? Sorry if this was long winded, just trying to figure out the best way moving forward. I don't really care about the data on the phone. Before going forward I'll do A Keis back up of the stuff I want to save. I appreciate any help/answers/suggestions...Jinx

How to unroot Kyocera Brigadier

I rooted my Kyocera with Kingroot, worked well. Wasn't to keen on some of the files it was adding and found I couldn't unroot with Kingroot built in feature. So I then found I could use SuperSu-Me to rid myself of Kingroot and purchased. It removed Kingroot and I am still unable to uninstall root so that I can upgrade to lollipop. All I get is software update failed. Any suggestions. I even did a factory reset and phone is still rooted. I have not tried any install and custom roms.
Did you ever fix this?
OTA uptate to lolipop bricked my phone... I was able to find a Rooted 5.1 rom to rescue it. But like you, I cannot remove root and all future update attempts keep failing...
Did you try to flash a stock 5.1 rom on your rooted 5.1 rom? That should allow to get back to normal upgrade (back in time, it usually worked, still I am not aware of latest android pains regarding that matter)
Harsher said:
Did you try to flash a stock 5.1 rom on your rooted 5.1 rom? That should allow to get back to normal upgrade (back in time, it usually worked, still I am not aware of latest android pains regarding that matter)
Click to expand...
Click to collapse
I was not able to find an unrooted Verizon factory ROM for my Brigadier.
ghj018 said:
I was not able to find an unrooted Verizon factory ROM for my Brigadier.
Click to expand...
Click to collapse
I am not sure you need it to be verizon to just be able to leap to "future" android version, unless this version is only available via kies from your PSP/carrier.
flashing any stock rom might work. Alternative would be to find an unrooted kernel for your android version of a rooted but else stock ROM (as some people do as they like TW experience but with the added benefits of root). But they are just guesses, I wish someone with more technical know-how would join, I just talk from past experiences, not from current ones, so it might have changed.
Harsher said:
Did you try to flash a stock 5.1 rom on your rooted 5.1 rom? That should allow to get back to normal upgrade (back in time, it usually worked, still I am not aware of latest android pains regarding that matter)
Click to expand...
Click to collapse
this phone may have been carrier specific to Verizon...
I did find some custom roms for marshmallow and nougat. But that's totally new territory for me to learn how to put those ones on and of course no updates. 5.1 is as far as the Brigadier went officially. This was not a common phone so it's support and information for it is scarce
---------- Post added at 08:48 PM ---------- Previous post was at 08:21 PM ----------
This is the update it keeps asking me to install , and it keeps failing . I suppose if anybody had a fully updated ROM for the Brigadier that would be useful solution...
https://www.verizonwireless.com/support/kyocera-brigadier-update/
Do you have xposed installed? Sometimes that can cause problems.
I do not, I am going to attempt to put TWRP on and then flash the Super SU Binary so that I can run FlashFire.
Lots a learning lol
Locked bootloader. You can run TWRP from adb but you cannot permanently flash it to the device.
I rooted with Kingroot and updated my phone. It was on 4.4.2 1.102vz. My phone boots up but screen goes blank after the Kyocera screen. I powers it off one time but it was luck. I can boot it into stock recovery. I would like to flash the 5.1 ROM to it and beagle to use it. I do not know how to flash a ROM to the phone since it does not have fast boot. Can anyone assist me? The phone was new and never used too. Was going to be a great phone for me at work. I have rooted before and took a ota and I only risked loosing root. But that was with Droid phones. That is where I have more experience in.

Categories

Resources