Database Develop

[Q] How to completly get rid of root

Good evening,
A few months ago I tried to root my S3 I9305, unfortunately it didn't really worked out. I had it rooted, installed some kind of clockwork app, but stopped right here, as I had no idea what I was exactly doing, and I did not want to take the risk to brick my phone. So I unrooted it, got rid of the supersu and the clockwork custom app.
Now the problem is, whenever I want to see if there is an update for my phone, it says I cannot do this, as my device is modified... So here is my question, how do I REALLY get completly rid of the root, because root checkers say im not rooted anymore, but for some reason my device says it is still rooted...
I've read that factory resets wont help, but flashing the stock rom with odin does ... Can someone explain to me what exactly I can do to just get completly rid of root?
Greetings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you can see in the picture above, it says my apparaatstatus (Status device) is aangepast (modified)

I suppose that before rooting your phone, you were on stock rom 4.3? In that case you have installed knox automatically. Knox will let Samsung update know that you modified your phone.
Flashing firmware with pc and Odin should fix it but i never tried this myself. I'm happy with a rooted phone and modified recovery

zertyx said:
I suppose that before rooting your phone, you were on stock rom 4.3? In that case you have installed knox automatically. Knox will let Samsung update know that you modified your phone.
Flashing firmware with pc and Odin should fix it but i never tried this myself. I'm happy with a rooted phone and modified recovery
Click to expand...
Click to collapse
Thank you for your answer, so as I thought, flashing to stock ROM with ODIN is the best solution..? Altough I have absolutely no idea what that consists of...
The thing is, I really wanted root as well, as we all know 4.3 is a big failure on the S3 (Battery drain, slow, wake up lag, ...) But the problems were 1st of all, I didn't really find a clear guide on how to do it, so I was just doing things without knowing what exactly I was doing.
2nd of all, I have some apps I use on a regularly base who do not run when rooted, for example to watch TV or my bank application ... So I couldn't really root because of all this.

Would be appreciated if someone could link me how to flash my device, I9305 from Belgium, with proximus providor.

palmenmichiel said:
Would be appreciated if someone could link me how to flash my device, I9305 from Belgium, with proximus providor.
Click to expand...
Click to collapse
Go here, read it, then read it again before you do it...
http://forum.xda-developers.com/galaxy-s3/help-i9305/compiled-guide-rooting-gt-i9305-s3-lte-t2287234

Raistlin1158 said:
Go here, read it, then read it again before you do it...
http://forum.xda-developers.com/galaxy-s3/help-i9305/compiled-guide-rooting-gt-i9305-s3-lte-t2287234
Click to expand...
Click to collapse
Thank you for answering, but that is a methode to flash root with odin, what I want to do is flash stock rom so my phone is just as new WITHOUT root.
I think with a little bit of research I can figure out how to work with Odin myself, but I can't see to find a firmware the same as my phone.

Since you have Knox, I guess your device status will stay on "modified" until there is a way to reset the Knox counter.
If you only want to get rid of root to use apps which require an unrooted phone, I suggest you try root with SuperSU. There you have an option to (temporarily) deactivate root. On my i9305 phone, I can watch TV like this (in Belgium). This method however doesn't seem to work on my older HTC phone with CM 11 (although it used to in the past with an older version of the TV-app).

zertyx said:
Since you have Knox, I guess your device status will stay on "modified" until there is a way to reset the Knox counter.
If you only want to get rid of root to use apps which require an unrooted phone, I suggest you try root with SuperSU. There you have an option to (temporarily) deactivate root. On my i9305 phone, I can watch TV like this (in Belgium). This method however doesn't seem to work on my older HTC phone with CM 11 (although it used to in the past with an older version of the TV-app).
Click to expand...
Click to collapse
So even flashing a stock rom wont get rid of my root status, therefor I'll never be able to download following android updates via kies or OTa again... My god never ever a samsung device for me again, next one will be a nexus..

palmenmichiel said:
So even flashing a stock rom wont get rid of my root status, therefor I'll never be able to download following android updates via kies or OTa again... My god never ever a samsung device for me again, next one will be a nexus..
Click to expand...
Click to collapse
I'm not sure; I think you can do updates (maybe not OTA) and your phone will be completely unrooted, but Knox counter will say that in the past, you modified your phone (voiding warranty).

zertyx said:
I'm not sure; I think you can do updates (maybe not OTA) and your phone will be completely unrooted, but Knox counter will say that in the past, you modified your phone (voiding warranty).
Click to expand...
Click to collapse
Oh well if its only about warrenty, I don't really care about that, device isn't under warrenty anymore anyways so!

then what's the problem? updates? if you got the 4.3 you are on the latest version...s3 is not nexus to receive updates every week/month...
the next update that is important is 4.4...and should get out soon...just go to samfirmware.com and get it(when it will roll)..

spiderman07 said:
then what's the problem? updates? if you got the 4.3 you are on the latest version...s3 is not nexus to receive updates every week/month...
the next update that is important is 4.4...and should get out soon...just go to samfirmware.com and get it(when it will roll)..
Click to expand...
Click to collapse
What you're saying is my problem , I cant just update with kies/OTA anymore because my device says its modified. Now what I've already learned now is that once it comes out, I can just flash it with odin, just as I can flash my stock rom with odin now. But the problem is that my PDA number is nowhere to be found on that site with firmwares, and I don't want to ruin my phone by flashing a wrong firmware..

hermmm why do you root your device when you don't even know what is root and why u need it? You understand that you are taking risk when you are rooting/flashing custom recovery on your device right? And one thing u will have to understand is that, literally speaking, there's no way you can brick you phone if you didn't modify anything after rooting, so you won't brick your phone "again(?)" if you now leave your phone as it is. Another thing is that rooting will not affect the functionality of other apps, instead it allows you to access more apps, so it is impossible that you can't run an app that you previously can after rooting, but the story will be different if you made other modification besides rooting and installing custom recovery. I think you might want to check out triangle away. I'm not sure whether this app can save you or is what you need, since I never use this app, but I know it can reset flash counter. But again, it needs root.

nikctsh said:
hermmm why do you root your device when you don't even know what is root and why u need it? You understand that you are taking risk when you are rooting/flashing custom recovery on your device right? And one thing u will have to understand is that, literally speaking, there's no way you can brick you phone if you didn't modify anything after rooting, so you won't brick your phone "again(?)" if you now leave your phone as it is. Another thing is that rooting will not affect the functionality of other apps, instead it allows you to access more apps, so it is impossible that you can't run an app that you previously can after rooting, but the story will be different if you made other modification besides rooting and installing custom recovery. I think you might want to check out triangle away. I'm not sure whether this app can save you or is what you need, since I never use this app, but I know it can reset flash counter. But again, it needs root.
Click to expand...
Click to collapse
I do know what root is, I just found no clear guide on how to root and install custom roms from scratch on these forums. I wanted a new rom because 4.3 on an S3 is ridiculously bad, battery drain etc ... I never bricked my phone before or anything like that, I just stated that I do not want to flash the wrong firmware causing my device to go broken.
Sadly, some applications do NOT work after you rooted. An example is a TV app called 'TV overal' or a banking application 'Bancontact mobile'. Now that I removed my root, together with supersu, my tv app works again, but my banking app still doesn't work as it says my device is modified. To what I've learned on this thread, it's because of the Knox app that still thinks my device is rooted...
I guess the only thing I can do is wait for the 4.4 firmware to come online and flash it with odin, however I need to do that ...

palmenmichiel said:
I do know what root is, I just found no clear guide on how to root and install custom roms from scratch on these forums. I wanted a new rom because 4.3 on an S3 is ridiculously bad, battery drain etc ... I never bricked my phone before or anything like that, I just stated that I do not want to flash the wrong firmware causing my device to go broken.
Sadly, some applications do NOT work after you rooted. An example is a TV app called 'TV overal' or a banking application 'Bancontact mobile'. Now that I removed my root, together with supersu, my tv app works again, but my banking app still doesn't work as it says my device is modified. To what I've learned on this thread, it's because of the Knox app that still thinks my device is rooted...
I guess the only thing I can do is wait for the 4.4 firmware to come online and flash it with odin, however I need to do that ...
Click to expand...
Click to collapse
Yes you are right, knox did that, from what I know, there's no way a regular app can find out the status of your device without asking for SU permission, so that's why I say "rooting will not affect the functionality of other apps", but since knox is there, then...
Anyway, I'm not sure whether I'm right, but I think the 4.4 firmware is ald up since the device is ald updated for quite some time. You can try to grab it from sammobile.

nikctsh said:
Yes you are right, knox did that, from what I know, there's no way a regular app can find out the status of your device without asking for SU permission, so that's why I say "rooting will not affect the functionality of other apps", but since knox is there, then...
Anyway, I'm not sure whether I'm right, but I think the 4.4 firmware is ald up since the device is ald updated for quite some time. You can try to grab it from sammobile.
Click to expand...
Click to collapse
Mh, as far as I can see, my CSC number (Which I think is the guideline to make sure you're downloading the right firmware?) I9305LUXEMK1, 4.3 is the latest, no such thing as 4.4 for it yet.

palmenmichiel said:
What you're saying is my problem , I cant just update with kies/OTA anymore because my device says its modified. Now what I've already learned now is that once it comes out, I can just flash it with odin, just as I can flash my stock rom with odin now. But the problem is that my PDA number is nowhere to be found on that site with firmwares, and I don't want to ruin my phone by flashing a wrong firmware..
Click to expand...
Click to collapse
then don't update via OTA or kies....just go to samfirmware.com and get firmware for the country you live on.... or any firmware from any country.
For example: i live in Romania and i got firmware from Netherlands(cause it was latest in samfirmware)...and it's working perfect...no battery drain no nothing....
As long as you are flashing firmware for your device it won't get bricked....
One small tip: after you flash firmware and got the the point where it says upgrading apps.....i manually enter recovery mode(stock one) and do a full wipe to make sure it works perfect.

nikctsh said:
Yes you are right, knox did that, from what I know, there's no way a regular app can find out the status of your device without asking for SU
Click to expand...
Click to collapse
Well, in Belgium they can
Me too, I have an app called Yelo tv, to watch some of the channels that the cable provider offers. It doesn't try to ask for root access and nevertheless it knows when the phone has root.
I don't have Knox.

Flash a stock rom with odin , the only solution i see there , then retry a root , it'd be okay then

So I'm back to trying to fix this... I found out that apperantly I have clockwordmod recovery still installed, when i use the key combo volume up + power+home button, and I have a backup on my SD card ... When I reboot from this menu, it says that I do not have root, so I chose yes there (to root it) , once it rebooted, went to play store to get supersu/root checker and both said I wasn't rooted ...
So what should I do to just get rid of it all and have a stock phone again? Because you've got all kinds of options in clockwordmod (Wipe data/factory reset, wipe cache partition, ... )

[Q] Verizon G2 acting crazy after FDR

Hello, and thank you in advance for any support on my issues. I have done some extensive searching regarding my issues but am coming up empty. I consider myself a relative noob and am now facing multiple questions and issues with my phone.
Device Info:
Verizon LG G2
Rooted, stock
Android Version 4.2.2
Software Version VS98011A
I did not personally root my phone - I paid to have it done for me remotely.
I have been using Titanium Backup to freeze or remove applications and bloat.
I also have used the paid version of ROM Manager for when/if I need it - I have never personally flashed a custom ROM or Kernel, etc.
I did personally side load the HotSpotProvision apk to use the Verizon Hotspot feature with my unlimited data and it worked great.
I also have the Verizon versions of the Galaxy S5 and LG G3. I recently did a 4G LTE speed test with all 3 devices and got insane speeds (attached) with the S5 and G5 but not the G2. I tried researching whether KitKat was the reason for being able to access XLTE speeds or not but couldn't find anything definitive there either. So I decided to attempt the Verizon OTA KitKat update for the G2. Here is where my nightmare begins...
To my knowledge, no backup had ever been done to my phone unless it was done when it was rooted. Regardless, I wanted to do one before making any changes to the phone but I have a feeling I was unsuccessful. After more searches on how to perform a backup and trying 6 times with ROM Manager (unsuccessfully), I decided to try the physical key option to launch into Recovery Mode. Based on what I did find online, this method would take you to the FDR screen but not to worry and to continue because it would actually take you to the TWRP home screen. Well, it did not. My phone reset and I lost everything in my gallery, etc. On reboot, I did see that I was still rooted but not able to do the OTA (because I am still rooted, I assume?). I have done 2 more FDRs and now my phone is acting out of it's mind.
Issues:
Touch screen unresponsive or turning off/on all by itself
Contact info not syncing to native messaging app
Previously installed free or purchased apps not reinstalling (although they did after the first FDR)
Can't receive OTA
At this point, I might as well do whatever I need to do to get things working correctly since I'm already reset.
My questions are:
How can I check if I do in fact have, or don't have a backup that I can access?
How do I create a backup so this doesn't happen again?
What do I need to do to get the OTA and will KK allow me to access the XLTE band?
Can I still do a Factory Data Reset and get back to the true "out of the box" version of the phone? If so, how?
I think that's it for now!! Thanks for any help that can be offered. Cheers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Sounds like whoever you paid to root the phone didn't install a recovery or you lost it from applying the KK OTA.
You can install TWRP using Autorec if you're on KK (4.4.2) now.
http://forum.xda-developers.com/showthread.php?t=2715496
Personally I'd start clean to see if it clears up your issues, the touch screen thing sounds more like a hardware problem. If all is well after returning it to stock, re-root it yourself using ioroot/towelroot and install a recovery again and make a back up to save somewhere once you get it set up the way you want it.
http://forum.xda-developers.com/showthread.php?t=2448960

Thank you very much, Matt.
KK never did get installed...I am still on 4.2.2 and every time I try to go back to stock through various methods on this site I get the attached image. I would definitely like to start with the out-of-box device again, OTA KK and re-root but I'm not even having any luck with that either. This whole project began with the thinking that I needed KK to access the XLTE network since I was getting incredible speeds with the G3 and S5...do you know if that is accurate?
mjones73 said:
Sounds like whoever you paid to root the phone didn't install a recovery or you lost it from applying the KK OTA.
You can install TWRP using Autorec if you're on KK (4.4.2) now.
http://forum.xda-developers.com/showthread.php?t=2715496
Personally I'd start clean to see if it clears up your issues, the touch screen thing sounds more like a hardware problem. If all is well after returning it to stock, re-root it yourself using ioroot/towelroot and install a recovery again and make a back up to save somewhere once you get it set up the way you want it.
http://forum.xda-developers.com/showthread.php?t=2448960
Click to expand...
Click to collapse

lantzman said:
Thank you very much, Matt.
KK never did get installed...I am still on 4.2.2 and every time I try to go back to stock through various methods on this site I get the attached image. I would definitely like to start with the out-of-box device again, OTA KK and re-root but I'm not even having any luck with that either. This whole project began with the thinking that I needed KK to access the XLTE network since I was getting incredible speeds with the G3 and S5...do you know if that is accurate?
Click to expand...
Click to collapse
Follow the directions in the return to stock guide provided, see if you can get the phone in download mode...
Install the LG Flash Tool and drivers then try this.
1) Go ahead and put phone in Download mode by VolUp + plug in USB to PC. At this time your computer should install the device, if it hadnt already. Open device manager to check if un der "Ports (Com and LPT)" it shows up as LGE AndroidNet for VZW USB Serial Port (COM##) IF the COM number is anything other than 41, which it probably will be. Right click it in device manager and choose peroperties, then go to port settings tab and click advanced. On the bottom choose COM41 and hit OK. (if you get an error about it being in use I'll write more about that later)
hit ok and all that and close out the properties.
Click to expand...
Click to collapse

OK, I'm on download mode, the computer installed drivers and I changed to COM41. Phone still shows "Firmware Update" screen and 0% on progress. Where do I go from here?
mjones73 said:
Follow the directions in the return to stock guide provided, see if you can get the phone in download mode...
Install the LG Flash Tool and drivers then try this.
Click to expand...
Click to collapse

lantzman said:
OK, I'm on download mode, the computer installed drivers and I changed to COM41. Phone still shows "Firmware Update" screen and 0% on progress. Where do I go from here?
Click to expand...
Click to collapse
Did you unplug and replug in the phone?

I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
mjones73 said:
Did you unplug and replug in the phone?
Click to expand...
Click to collapse

OK, it's doing the OTA!
lantzman said:
I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
Click to expand...
Click to collapse

lantzman said:
I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
Click to expand...
Click to collapse
Yes, returns the phone to out of the box stock basically. Now if you want to re-root, you can use ioroot25 or towelroot.
ioroot25 - http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Once rooted, use autorec to install a recovery (kitkat requires some additional steps besides just flashing a recovery and it does them for you)
http://forum.xda-developers.com/showthread.php?t=2715496
Make sure you grab the vs980 version of autorec.

So I can't create a stock recovery prior to root, correct...so that I can go back to stock from root?
mjones73 said:
Yes, returns the phone to out of the box stock basically. Now if you want to re-root, you can use ioroot25 or towelroot.
ioroot25 - http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Once rooted, use autorec to install a recovery (kitkat requires some additional steps besides just flashing a recovery and it does them for you)
http://forum.xda-developers.com/showthread.php?t=2715496
Make sure you grab the vs980 version of autorec.
Click to expand...
Click to collapse

lantzman said:
So I can't create a stock recovery prior to root, correct...so that I can go back to stock from root?
Click to expand...
Click to collapse
No, you need to root it first if you want to back it up.

OK, so I can root with the Towelroot app and use Autorec for backup. Does it give me TWRP?
mjones73 said:
No, you need to root it first if you want to back it up.
Click to expand...
Click to collapse

and where do I find the process for installing Autorec?
lantzman said:
OK, so I can root with the Towelroot app and use Autorec for backup. Does it give me TWRP?
Click to expand...
Click to collapse

sorry, I was making this way too difficult. I ran Towelroot and Autorec and I believe we are good to go. Now, when would I use Autorec...when I have an issue flashing other ROMs, kernels, etc?
How do you prefer to receive donations? I really appreciate your help...you've been great!

lantzman said:
sorry, I was making this way too difficult. I ran Towelroot and Autorec and I believe we are good to go. Now, when would I use Autorec...when I have an issue flashing other ROMs, kernels, etc?
How do you prefer to receive donations? I really appreciate your help...you've been great!
Click to expand...
Click to collapse
Autorec is a one and done, you can remove it now, it installs TWRP, that's all you need it for. You should now be able to get into recovery using the same sequence you used before if it installed clean for you. Any flashing of rom, kernels, etc would be via TWRP.
One last note, don't install any OTA's while you're rooted.
You don't have to donate anything but if you really want to, just hit the Donate to Me button under my name.

OK, thank you. One last question: it seems the touch screen may be starting to fail. If I needed to unroot or at least show unrooted to turn it in for a warranty replacement, can that be done and if so, how?

lantzman said:
OK, thank you. One last question: it seems the touch screen may be starting to fail. If I needed to unroot or at least show unrooted to turn it in for a warranty replacement, can that be done and if so, how?
Click to expand...
Click to collapse
This will get you back to stock. Make sure you read the first page before you do this...if needed. FYI: Device needs to be off to get into download mode and you should be in download mode before installing the drivers. http://forum.xda-developers.com/showthread.php?t=2448960
Sent from my XDABBEB VS98025A v2.0.0 using XDA free mobile app

Perfect, that's the process I just did from root so I could get the KK OTA. Just wasn't sure if there was an easier way to just show "unrooted" in "about phone" before having them look at it. Love your call sign/avatar. Huge Huge Huge Zeppelin fan here! Ever since hearing "Stairway" in 7th grade! Mght need to see if "LantZeppelin" is available! Thanks again.

[Q] Safestrap 3.75 - Unable to display splash screen

I'm in the process of trying to upgrade my Dynamic Kat 4.3 ROM to the most recent 4.4 version, and saw that I needed to update my Safestrap from 3.71 to 3.75. I downloaded the Safestrap 3.75 apk (as well as made sure I had the most recent Busybox version already installed), and installed it. Everything appeared to install fine with no issues. I rebooted to try to go into Safestrap, but did not get the splash screen with an option to boot in the Safestrap recovery. I noticed on the 3.75 post that not seeing a splash screen is known issue and the suggestion was just to try re-installing the apk. I have since tried uninstalling/reinstalling the 3.75 apk probably about 6-8 times, then I tried uninstalling 3.75 and back-leveling to 3.71... still no splash screen. Then I tried uninstalling and re-installing 3.75.... again, no splash screen. At this point I've uninstalled/reinstalled over 10 times now, and am at a loss as to where to go next. I've spent about an hour looking around on google and in the forum here for people with the same issue but haven't had any real luck. This seems like such a trivial problem that should be able to fixed that I really don't want to have to revert back to Stock through ODIN mode and re-root, re-flash ROM, etc. if at all possible. Is there anything else that can be done to resolve this?
Any help/suggestions would be greatly appreciated.

MorningThunder said:
I'm in the process of trying to upgrade my Dynamic Kat 4.3 ROM to the most recent 4.4 version, and saw that I needed to update my Safestrap from 3.71 to 3.75. I downloaded the Safestrap 3.75 apk (as well as made sure I had the most recent Busybox version already installed), and installed it. Everything appeared to install fine with no issues. I rebooted to try to go into Safestrap, but did not get the splash screen with an option to boot in the Safestrap recovery. I noticed on the 3.75 post that not seeing a splash screen is known issue and the suggestion was just to try re-installing the apk. I have since tried uninstalling/reinstalling the 3.75 apk probably about 6-8 times, then I tried uninstalling 3.75 and back-leveling to 3.71... still no splash screen. Then I tried uninstalling and re-installing 3.75.... again, no splash screen. At this point I've uninstalled/reinstalled over 10 times now, and am at a loss as to where to go next. I've spent about an hour looking around on google and in the forum here for people with the same issue but haven't had any real luck. This seems like such a trivial problem that should be able to fixed that I really don't want to have to revert back to Stock through ODIN mode and re-root, re-flash ROM, etc. if at all possible. Is there anything else that can be done to resolve this?
Any help/suggestions would be greatly appreciated.
Click to expand...
Click to collapse
It sounds to me as if you were on JB and tried to use a KK rom through Safestrap. You can't do that because SS doesn't flash the kernel. You can't run a TouchWiz based KitKat rom on a JellyBean kernel. Your only option is to either Odin back to stock JB and use the setup you had been running, or Odin to stock 4.4.2 KitKat after which you can root, install SS 3.75. Only then will you be able to run the latest DynamiKat rom. All this is assuming you're using an AT&T note 3.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
---------- Post added at 02:40 PM ---------- Previous post was at 02:03 PM ----------
I misread your post thinking you were no longer able to boot at all. If you want to stay on JB, just reinstall SS 3.71. Make sure you're actually installing the recovery and not just the apk. But if you want the latest DynamiKat Kitkat version, you're going to have to upgrade your phone to 4.4.2 first.
Sent from my AT&T Galaxy Note 3 using Tapatalk®

andygev35 said:
I misread your post thinking you were no longer able to boot at all. If you want to stay on JB, just reinstall SS 3.71. Make sure you're actually installing the recovery and not just the apk. But if you want the latest DynamiKat Kitkat version, you're going to have to upgrade your phone to 4.4.2 first.
Click to expand...
Click to collapse
Thanks for the reply!!
OK, so maybe I misunderstood what it would take to upgrade to KK... The ROM I'm running now is JB and I had thought that I could just download the APK for Safestrap 3.75, and uninstall the 3.71 version I already had, install 3.75, then go into the 3.75 SafeStrap and install my new KK rom.... it sounds like it isn't that simple.
My phone is booting and working just fine right now on the older Dynamic Kat JB rom I've been running, it just doesn't display the splash screen for Safestrap now when I reboot. You mentioned I need to upgrade my phone to 4.4.2 first in order to use SS 3.75 and install a KK rom, and I thought that just installing the 3.75 Safestrap apk did that. What is the process to upgrade the recovery to 4.4.2 if I can't just install the SS 3.75 APK?

I could be wrong but I'm pretty sure SS 3.75 only works if you're on 4.4.2. I think you're misunderstanding though. SS doesn't upgrade your phone. You have to upgrade your phone's firmware yourself to 4.4.2. Then you can use SS 3.75 which is COMPATIBLE with 4.4.2.
Sent from my AT&T Galaxy Note 3 using Tapatalk®

andygev35 said:
I could be wrong but I'm pretty sure SS 3.75 only works if you're on 4.4.2. I think you're misunderstanding though. SS doesn't upgrade your phone. You have to upgrade your phone's firmware yourself to 4.4.2. Then you can use SS 3.75 which is COMPATIBLE with 4.4.2.
Click to expand...
Click to collapse
Ahh ok. I do have an AT&T Note 3, and I know I haven't updated the firmware to 4.4.2 yet. Is there a post stickied somewhere with a link and instructions to install the new firmware?

This should lead you in the right direction
http://forum.xda-developers.com/showthread.php?t=2838117
Sent from my AT&T Galaxy Note 3 using Tapatalk®

Right on. Thank you for help sir!

You're welcome.
Sent from my AT&T Galaxy Note 3 using Tapatalk®

Flashfire with AROMA

Hey Guys, I was wondering if its possible to flash AROMA ROMs with flashfire. I've used flashfire once, I think, but it just came into my mind maybe we could use AROMA installers. Ill see if I'm able to flash an international N3 ROM with AROMA from flashfire in a little bit as I am busy atm.

I can confirm this working. I installed darklord s6 (international) using flashfire

coollkidd said:
I can confirm this working. I installed darklord s6 (international) using flashfire
Click to expand...
Click to collapse
Hello, how did you do that? I want to install darklord v3.0 to my att note 3 with aroma installer.
Downgraded to NC2 kitkat, rooted and installed flashfire. But when i attempt install darklord v3.0 using with flashfire, it's failed. Shows me a blackscreen after i see flashfire loading.
Can you tell me which steps did you follow?
Thanks for help.

Quentin86 said:
Hello, how did you do that? I want to install darklord v3.0 to my att note 3 with aroma installer.
Downgraded to NC2 kitkat, rooted and installed flashfire. But when i attempt install darklord v3.0 using with flashfire, it's failed. Shows me a blackscreen after i see flashfire loading.
Can you tell me which steps did you follow?
Thanks for help.
Click to expand...
Click to collapse
What was your reason to downgrade? I didn't downgrade or anything, took a nandriod backup, booted into os, went into flashfire, selected OTA/ZIP option, don't edit any options or anything, selected wipe and installed, make sure you have screen timeout set to 10 minutes, give it some time it'll reboot and you'll be on the new rom. I flashed back stock because Darklord was overheating my phone like crazy.

Also, make sure to get Safestrap apk after you install the new rom, I guess it removes Safestrap from the system.

I think you can. @carl1961 would know I want to say he said you could
Sent From My Not3-N900A/S6 Hybrid[/color="Red"]

BLK♤Ninja said:
I think you can. @carl1961 would know I want to say he said you could
Sent From My Not3-N900A/S6 Hybrid[/color="Red"]
Click to expand...
Click to collapse
Yeah I've gotten it to work smoothly. I still prefer stock ATT rom due to stability and battery life. The international roms aren't really meant for our N900A variant, most of them have overheating, battery, and stability issues on the N900A side.

Quentin86 said:
Hello, how did you do that? I want to install darklord v3.0 to my att note 3 with aroma installer.
Downgraded to NC2 kitkat, rooted and installed flashfire. But when i attempt install darklord v3.0 using with flashfire, it's failed. Shows me a blackscreen after i see flashfire loading.
Can you tell me which steps did you follow?
Thanks for help.
Click to expand...
Click to collapse
I've gotten a few ROMs to work with FlashFire; just be careful with installers that don't let you keep the stock kernel/boot.img.
I almost bricked my Note 3 because an S6 port forced a different kernel/boot.img while I wasn't paying attention.
coollkidd said:
Yeah I've gotten it to work smoothly. I still prefer stock ATT rom due to stability and battery life. The international roms aren't really meant for our N900A variant, most of them have overheating, battery, and stability issues on the N900A side.
Click to expand...
Click to collapse
This.
@carls1976 OC2 for stability/battery life; @TheDriller AllianceROM for customization are the ways to go atm.

KTownGT said:
I've gotten a few ROMs to work with FlashFire; just be careful with installers that don't let you keep the stock kernel/boot.img.
I almost bricked my Note 3 because an S6 port forced a different kernel/boot.img while I wasn't paying attention.
@carls1976 OC2 for stability/battery life; @TheDriller AllianceROM for customization are the ways to go atm.
Click to expand...
Click to collapse
Yeah haha, that happened to me too, but thanks to locked bootloader I was saved yay.

Any way to root Verizon Samsung SM-T377V tablet?

I'm trying to know if there is any way to root this device cuz I've been looking around and I haven't found a good tutorial on how to root this device in particular and I tried it earlier but it didn't seem to work at all. Any help would be much appreciated.

Is anyone going to help me with this? I have a Samsung SM-T377V tablet and I'm trying to find out how to root it. Thanks!

I had luck a few months ago using Kingroot v4.8.5 after downgrading the stock rom to android 5.1.1 (verizon's official build which the tablet originally shipped with at launch, Build LMY47X.T377VVRU1AOL7).
More recent versions of Kingroot simply fail and do not work. Also, the newer builds of the stock rom appear to be patched and I was unable to root via any method so the downgrade is required. (use Odin to flash verizon's original build)
While Kingroot does shoehorn a working way to root a running system, root doesn't appear to stick forever and eventually did stop working for me. I did have enough root time to at least break google apps and disable other bundled apps from running, but I wasn't unable to fully uninstall all the google spyware and verizon cruft - very frustrating!
Kingroot seems to take advantage of a zero-day vulnerability to grant us a rootkit.
I didn't have much luck replacing Kingroot with Chainfire's SU binaries to keep root working with something known-clean and backed by the community, which is a shame since Kingroot does appear to be running in the background doing who-knows-what with said rootkit. If you need root, Kingroot will get us at least that, but it's a two-way backdoor we're opening up and is really not a longterm solution.
Unfortunately, verizon has the bootloader locked down pretty hard. There's no way to flash in a custom Recovery which would open the door for developing a custom rom for SM-T377V with root already built in and none of the google/verizon undesirables. The current bootloader simply rejects any of the custom recoveries I've tried to flash in since they don't pass Verizon's signature checks.
What we really need is help from someone with experience cracking Verizon's bootloaders.. This bit is above my head and I'm at a roadblock.

electronhacker said:
I had luck a few months ago using Kingroot v4.8.5 after downgrading the stock rom to android 5.1.1 (verizon's official build which the tablet originally shipped with at launch, Build LMY47X.T377VVRU1AOL7).
More recent versions of Kingroot simply fail and do not work. Also, the newer builds of the stock rom appear to be patched and I was unable to root via any method so the downgrade is required. (use Odin to flash verizon's original build)
While Kingroot does shoehorn a working way to root a running system, root doesn't appear to stick forever and eventually did stop working for me. I did have enough root time to at least break google apps and disable other bundled apps from running, but I wasn't unable to fully uninstall all the google spyware and verizon cruft - very frustrating!
Kingroot seems to take advantage of a zero-day vulnerability to grant us a rootkit.
I didn't have much luck replacing Kingroot with Chainfire's SU binaries to keep root working with something known-clean and backed by the community, which is a shame since Kingroot does appear to be running in the background doing who-knows-what with said rootkit. If you need root, Kingroot will get us at least that, but it's a two-way backdoor we're opening up and is really not a longterm solution.
Unfortunately, verizon has the bootloader locked down pretty hard. There's no way to flash in a custom Recovery which would open the door for developing a custom rom for SM-T377V with root already built in and none of the google/verizon undesirables. The current bootloader simply rejects any of the custom recoveries I've tried to flash in since they don't pass Verizon's signature checks.
What we really need is help from someone with experience cracking Verizon's bootloaders.. This bit is above my head and I'm at a roadblock.
Click to expand...
Click to collapse
So you're saying that the only way to root the device is to downgrade to an earlier version of Android, and because Verizon locks down the bootloader to the point where it rejects any recoveries to flash an older ROM, it's impossible to downgrade?

Not quite:
We can flash official Verizon roms without issue since these are signed by Verizon and the bootloader will accept them and allow the flash.
Downgrade to the oldest official Verizon rom using Odin, and root with Kingroot v4.8.5.
It's not a permanent solution since root doesn't stick for much longer than about a week, and Kingroot is of questionable safety in terms of privacy and your data. This is the furthest I could get to developing a custom rom for SM-T377V with root already built-in which "just works".
The Verizon bootloader is certainly aware that Kingroot has done something nasty to the stock rom - during bootup it now shows an Unlocked Lock symbol and says "CUSTOM" before loading the Verizon bootup animation (the animation is part of the rom). This behavior gets reset when an official Verizon rom is reflashed. I'm assuming a new official bootloader (signed by verizon) is being updated as part of their package as well.
We need the expertise of someone with experience cracking a Verizon bootloader so that we can flash a custom recovery which will allow flashing custom roms and making full backups.
I did attempt to flash TWRP in via Fastboot using root on a running system to circumvent the boot process and signature checking, but I was unsuccessful getting Fastboot working. I'm not sure that Verizon allows Fastboots for this reason.

electronhacker said:
Not quite:
We can flash official Verizon roms without issue since these are signed by Verizon and the bootloader will accept them and allow the flash.
Downgrade to the oldest official Verizon rom using Odin, and root with Kingroot v4.8.5.
It's not a permanent solution since root doesn't stick for much longer than about a week, and Kingroot is of questionable safety in terms of privacy and your data. This is the furthest I could get to developing a custom rom for SM-T377V with root already built-in which "just works".
The Verizon bootloader is certainly aware that Kingroot has done something nasty to the stock rom - during bootup it now shows an Unlocked Lock symbol and says "CUSTOM" before loading the Verizon bootup animation (the animation is part of the rom). This behavior gets reset when an official Verizon rom is reflashed. I'm assuming a new official bootloader (signed by verizon) is being updated as part of their package as well.
We need the expertise of someone with experience cracking a Verizon bootloader so that we can flash a custom recovery which will allow flashing custom roms and making full backups.
I did attempt to flash TWRP in via Fastboot using root on a running system to circumvent the boot process and signature checking, but I was unsuccessful getting Fastboot working. I'm not sure that Verizon allows Fastboots for this reason.
Click to expand...
Click to collapse
So there's no way to disable Verizon's detection system that would make it reset the to the stock ROM after installing the previous version? I don't think I'd be with it to have my tablet rooted for only a week.

Root is working for the SM-T377V!
!! Great news! Your curiosity got me thinking about this again, and I got root working fully!
We finally have a working Root for the Samsung SM-T377V Galaxy Tab E 8.0" (Verizon)!
The trick is to use KingoRoot. (not Kingroot)
http://www.kingoapp.com/
First, downgrade the stock ROM to the very first version that Verizon shipped with. Build RU1AOL7, dated 2016.02.11. It's about 1.5gig, and I have no way to host such a large file, so search for it before you ask for mine. I found it pretty easily directly from Verzion. Use ODIN to flash it, yadda yadda yadda.
Then, use the Windows version of KingoRoot to actually root the tab. You will need to enable Developer Mode and USB Debugging, which KingoRoot walks you through if you don't know how. Be sure to uncheck the "Install recommended software" checkbox to avoid the bloatware they try to sneak by you.
After it finishes successfully, reboot the tab. During the boot, a message will pop up that says Android is Optimizing 1 new app. Badda boom, you're rooted!
To verify, use a Terminal Emulator and type the command "su" and press enter. If you're rooted, the prompt will change from a $ to a #. I also recommend that you use a root check app to double-check what is actually installed. I used "Root Check" by gsmdev since it's completely free and no frills unlike the other hundreds up on the market.
https://play.google.com/store/apps/details?id=com.gsmdev.rootcheck&hl=en
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm successfully uninstalling all of the Google spyware and Verizon cruft now without any hangups for the first time since getting this tablet It's not on the level of a custom ROM by any means, but this gets us a lot closer to that day!

Please help!
Please post a link to the older version of the SM-T377V Build. I looked endlessly and could not find it.
I have odin and tried to downgrade to T337VVRS3BPL1 (5.1.1) from T377VVRS1BPL1 (6.0.1). It didn't work. Odin got stuck at "checking status".
Said screw it and tried to run kingoroot, on current build (6.0.1) and failed. :crying:
I can not find LMY47X.T377VVRU1AOL7 anywhere. I searched the verizon and samsung but could not find it.

try SAMMOBILE website for stock firmware
BrentM94 said:
Please post a link to the older version of the SM-T377V Build. I looked endlessly and could not find it.
I have odin and tried to downgrade to T337VVRS3BPL1 (5.1.1) from T377VVRS1BPL1 (6.0.1). It didn't work. Odin got stuck at "checking status".
Said screw it and tried to run kingoroot, on current build (6.0.1) and failed. :crying:
I can not find LMY47X.T377VVRU1AOL7 anywhere. I searched the verizon and samsung but could not find it.
I must find a way to change the IMEI number. I can't do that without root access. Please this is the only thread that sounded promising on the WHOLE internet about the SM-T377V Tablet. :good:
Click to expand...
Click to collapse
IDK about the 'LMY47X' prefix but the ROM/firmware T377VVRU1AOL7 (5.1.1) dated 02-10-16 is posted for SM-T377V on the SAMMOBILE site.

I found it, thanks!
I looked again and I was searching in the wrong areas. I couldn't find it on the Verizon website.
I downloaded it off of samsung-firmware.org

Temporary Root Successful
I was able to downgrade my MMB29K.T377VVRS1BPL1 (6.0.1) Marshmallow to LMY47X.T377VVRU1AOL7 (5.1.1) Lollipop with Odin with no problems.
Then I downloaded Kingoroot for Windows, and it took me three or four times to get it Rooted. The Root is only temporary though and I lose it after restarting the tablet.

BrentM94 said:
Please post a link to the older version of the SM-T377V Build. I looked endlessly and could not find it.
I have odin and tried to downgrade to T337VVRS3BPL1 (5.1.1) from T377VVRS1BPL1 (6.0.1). It didn't work. Odin got stuck at "checking status".
Said screw it and tried to run kingoroot, on current build (6.0.1) and failed. :crying:
I can not find LMY47X.T377VVRU1AOL7 anywhere. I searched the verizon and samsung but could not find it.
I must find a way to change the IMEI number. I can't do that without root access. Please this is the only thread that sounded promising on the WHOLE internet about the SM-T377V Tablet. :good:
Click to expand...
Click to collapse
You're right, I searched quickly and it looks like VZW took it down... no surprise there :laugh:
Here's a MEGA link to my copy (1.39 GB, zipped):
https://mega.nz/#!bB0wyahB!wf4RW4sGoGv5pp9Co9S1mRVJE1e32v7-9hZt8BGlYKw
I'm curious about your intents to change up your IMEI, I've never had much luck and would love to move mine over to sprint.

electronhacker said:
You're right, I searched quickly and it looks like VZW took it down... no surprise there :laugh:
Here's a MEGA link to my copy (1.39 GB, zipped):
https://mega.nz/#!bB0wyahB!wf4RW4sGoGv5pp9Co9S1mRVJE1e32v7-9hZt8BGlYKw
I'm curious about your intents to change up your IMEI, I've never had much luck and would love to move mine over to sprint.
Click to expand...
Click to collapse
I have made a post hoping that someone could help me. I've been having a really hard time trying to make this tablet stay rooted. I'm not sure if you've seen it. Here is the title of the thread "Rooting Samsung Galaxy Tablet E (8.0) SM-T377V Please Help".
https://forum.xda-developers.com/galaxy-tab/general/rooting-samsung-galaxy-tablet-e-8-0-sm-t3553154
Is that your rooted firmware or just the stock? I would really love if you could post your already rooted firmware that you are using because I keep getting stuck in bootloops with Kingoroot (I only get stuck in bootloops with the android version Kingoroot.apk, and Windows Kingoroot gives me a temporary Root and can't seem to figure out how to keep it rooted.
I wanted to ask you if it was possible for you to post your already rooted firmware of stock (5.1.1) since it is still Verizon I don't see how the Bootloader would lock me out. Would that work?
I'm trying to do the same thing you are trying to do and switch over to Sprint. :laugh:
I also cleaned up my posts on this thread so they're not all over the place.

Sadly things don't look too promising for this tablet, considering the bootloader's preventing us from installing custom recovery. Though, in theory, would it be possible to install a custom recovery by temporarily rooting, then using that to write a recovery.img directly to the recovery partition on the tablet? That'd get around the verification for installing custom recovery if that works...

Ugh. I'm seeing bootloops now too, even immediately after a reflash to stock and then running Kingoroot.
The stock recovery shows "dm-verity verification failed..." at the base of the window.
For those that installed Kingoroot, you can undo the boot loops by rebooting into stock recovery
Reboot, PWR + VOL UP + HOME, and select "wipe data/factory reset..." to pull out all the kingoroot binaries. (this step is necessary, unfortunately)
Then, PWR + VOL DOWN + HOME to go into boot loader mode, and use Odin to reflash the stock rom. This will at least get your tab back to factory stock.
I'm going to explore a bit more with Kingroot, I hadn't realized until I went to reflash over the bootlooping system that unless a full "wipe data/factory reset" is run prior to Odin, that most of the existing system remained intact. In my last writeup I did have a functional tab that could be rebooted without problems. I'm wondering now if it was a combination of the root tactics that I had tried earlier that were all still installed in the system that got things working....
When thing worked prior, I had been playing with: Kingroot 4.8.5, Official SuperSU, BusyBox-free, and of course Kingoroot
---------- Post added at 07:00 PM ---------- Previous post was at 06:54 PM ----------
tomiga said:
Sadly things don't look too promising for this tablet, considering the bootloader's preventing us from installing custom recovery. Though, in theory, would it be possible to install a custom recovery by temporarily rooting, then using that to write a recovery.img directly to the recovery partition on the tablet? That'd get around the verification for installing custom recovery if that works...
Click to expand...
Click to collapse
These were my thoughts too. If we can get root, we can flash over recovery.img using ADB and/or Fastboot. The latter appears to be disabled/locked, however. Also, I'm not certain that the sm-t377p recovery image will actually work... They're reportedly the same hardware, but one cannot be sure that things will jive with a crossflash at such a low level. My thoughts were if it's even an option, gamble it, and if the tab is bricked oh well...
This tab is worthless to me anyway if I can't pull out the Google spyware. Should have bought a rootable Tab A anyway, it would have been cheaper

I've gambled it quite a bit, over the process I've gotten stuck in like 7 bootloops, 5 soft bricks, and 3 hard bricks. Which is about 15 Odin flashes, or factory resets.
I had it temporarily rooted with your suggested firmware downgrade and Kingoroot windows version. The android version only gives me bootloops.
I've never been able to install SuperSu. It gets stuck at disable Knox. Which just ultimately fails and I don't get anywhere. I've used my temporary root and pirated Titanium Backup Pro to Freeze and Uninstall Knox. Which for some reason SuperSu still wants me to disable it and detects it, prevents it from installing.
I really wanted to try the rooting method with this tablet that was used on the SM-T377P because like you said about hardware. I'm not going to risk it, mainly because I need a break from running in circles with this damned SM-T377V.
So I recently flashed with Odin to get out of my last bootloop and my tablet came back on it still had the Kingoroot applications and Root Checker which I had downloaded before the bootloop. I was going to ask if these stayed on there because I didn't wipe to factory defaults before flashing?
Good luck and thanks again for all the help you've provided so far. We do have a temporary root with Kingoroot. I believe a lot of progress had been made. I'll update my thread and clean it up, just giving my experience with the rooting process of the SM-T377V. I'll clean it up when I can get around to it.
Thank you electronhacker.

Can I Re-Flash the current firmware (6.0.1) Marshmallow with Odin? I'm still newbie to Flashing firmware.

I'm an S7 Edge owner and one of these Tab E 8.0 SM-T337V and have some possible ideas for you guys to try. I've rooted my S7 Edge on Nougat Android 7.0. You can go into the Verizon S7 Edge forums to find a lot of this. Download the Odin Prince Comsy Edition. You are NOT able to flash a custom recovery to the tablet as Verizon and Samsung keep the bootloader locked down,even with root,there's no possibilities of a custom recovery. That means no custom recovery at all. Follow the steps on these websites and see what you get. There may be some possibilities here.
---------- Post added at 08:23 PM ---------- Previous post was at 08:00 PM ----------
Check out these sites: forum.xda-developers.com/verizon-s7-edge/how-to/verizon-root-knox-t3410624
forum.xda-developers.com/verizon-s7-edge/how-to/root-method-nougat-t3566978
forum.xda-developers.com/verizon-galaxy-s7/how-to/how-to-notes-root-install-xposed-unroot-t3411039
This may be a good way to try and root the tablets
Sent from my SM-G935V using XDA-Developers Legacy app
---------- Post added at 08:41 PM ---------- Previous post was at 08:23 PM ----------
BrentM94 said:
Can I Re-Flash the current firmware (6.0.1) Marshmallow with Odin? I'm still newbie to Flashing firmware.
Click to expand...
Click to collapse
You should be able to to flash the stock firmware with Odin. I use Prince Comsy Odin as it skips SHA checks. Even with a newer bootloader version,you should be able to flash an older firmware. Just use the AP slot in Odin to do it and nothing else.
Sent from my SM-G935V using XDA-Developers Legacy app

So you're saying that I can temporary flash a previous version of Android on the device but by the time Verizon checks the software the root will be voided almost immediately upon its exploit?

DMon04 said:
I'm an S7 Edge owner and one of these Tab E 8.0 SM-T337V and have some possible ideas for you guys to try. I've rooted my S7 Edge on Nougat Android 7.0. You can go into the Verizon S7 Edge forums to find a lot of this. Download the Odin Prince Comsy Edition. You are NOT able to flash a custom recovery to the tablet as Verizon and Samsung keep the bootloader locked down,even with root,there's no possibilities of a custom recovery. That means no custom recovery at all. Follow the steps on these websites and see what you get. There may be some possibilities here.
---------- Post added at 08:23 PM ---------- Previous post was at 08:00 PM ----------
Check out these sites: forum.xda-developers.com/verizon-s7-edge/how-to/verizon-root-knox-t3410624
forum.xda-developers.com/verizon-s7-edge/how-to/root-method-nougat-t3566978
forum.xda-developers.com/verizon-galaxy-s7/how-to/how-to-notes-root-install-xposed-unroot-t3411039
This may be a good way to try and root the tablets
Sent from my SM-G935V using XDA-Developers Legacy app
---------- Post added at 08:41 PM ---------- Previous post was at 08:23 PM ----------
You should be able to to flash the stock firmware with Odin. I use Prince Comsy Odin as it skips SHA checks. Even with a newer bootloader version,you should be able to flash an older firmware. Just use the AP slot in Odin to do it and nothing else.
Sent from my SM-G935V using XDA-Developers Legacy app
Click to expand...
Click to collapse
The problem I see with that is that those guides use an engineering bootloader specific for the S7. As far as I know, there isn't an engineering bootloader for the T377V. Sadly, still haven't found any reliable results in getting this thing rooted.