Database Users

[Q] Root Question related later ota

after a few hours searching, I am still a bit confusing on following question:
1. trip rootchecker
If I do not choose do this during rooting, in other word, I only have adb shell root.
a) should I still be able to install twrp and flash other rom? my impression is "yes", am I right?
b) But if I choose do this, then my warranty is gone. If I later flash back the stock,
will this be wiped and "forget"? i.e. the warranty is back?
Or is this "root checker" will send somthing to LG once it is tripped, hence warranty
is permanently voided?
2. ota
It seems once rooted, one can not take any ota, right? even the kitkat in future?
would "trip rootchecker" matter in this case?
even though thanks to thecubed, it seems we do have a solution.

If you choose not to trip the root checker, root will not work properly and neither will the apps that require it.
It doesn't send any info to LG or your carriers. All it does is... If in the future you break your phone somehow and take it into your carrier store to get it fixed, they will check the phone to see if it's ever been rooted. If it's been tripped, it'll give a number code on the screen to tell them it either was rooted in the past but isn't anymore, is currently rooted, or was never rooted.
Then it will be at the store's discretion on whether or not they'll help you out or make you pay full price to fix it or get it replaced.
I don't know how it is for the G2, but I know awhile back some newer HTC phones got S-OFF which allowed them to reset the root checker to make the device think it's never been rooted. Our phones may have a similar method out there somewhere... Though probably not as it'd be fairly big news. I am however, willing to bet that there is a crack team or two working on disabling that for our devices.
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM.

[Q] Note 4 Rooted, Then What?

I'm coming from the HTC environment and the Note 4 will be my first Samsung phone. I have a few concerns regarding root. Assuming the Note 4 can be rooted, using the Note 3 and the S5 as a precident, how does one maintain updates? With HTC, if you had root, you could flash a new ROM for software updates (newer android versions, bug fixes, carrier updates). However, to update firmware, like updated radios, you needed S-Off.
Please help explain. With the Note 4, what will we need in order to do the following, and what is the likelyhood each of the following will be possible:
1) Obtain Root to run apps requiring root (Titanium, adblocker, WIFI tether...)
2) Install custom recovery
3) Flash custom ROMs
4) maintain a phone with updated and current Firmware and Radios.
Otherwise, what do people do who root there phone on day 1? Do they go 1-2 years with the phone without updating firmware?
Thank you

you can update samsung software with no issues. Assuming they'll keep it like the Note 2, there under the settings>update, there are different tabs, and one is Samsung.
Modems and other such updates, you'll just need to wait a day or two for someone to upload the newer OTA with root. Sometimes, some of the root tools, like SuperUser, will have OTA survivor mode, but they're not guaranteed to worked.
End of the day, it's not anything you're not already use to

Thanks for the response. So if the bootloader is NOT able to be unlocked, what will we be missing out on then? If the bootloader IS locked and there is no way around it, we can still root, flash ROMS, and update radios/firmware?

we can only go by the past to predict the future, but in US ATT Note 3 had locked bootloader, T-mobile loader was unlocked, so it was up to the carrier, but I believe both had way to root. One problem with Samsung was Knox software, which once triggered by root or loading custom firmware couldn't be reset back to zero. Based on that flag some people claimed to be refused warranty repairs, others didn't, so who knows. One thing is that Samsung "donated" knox to Google L Android, so it may be on all Android phones in the future, but again who knows how Google will implement it. It may take a time for developers to find their way around new phone, so if you have concerns, wait a little until all is clear, for now we can only guess. My Note 3 is rooted, "official" with Knox flag 0, but I had to wait for proper methods to be developed and every time I update I need to re root (and make some other changes) again. There could be developer model also with everything open, who knows.

Thanks for the response.
I just need to clarify what can be done on a rooted Samsung device vs what can be done with a rooted AND unlocked Samsung device.
Am I correct:
Rooted Only:
-superuser
-can run root required apps (Titanium, Wifi Tether)
-can flash custom ROM but must be stock based only, and must be on stock kernel
-can NOT install CM or TWRP custom recovery
-can update firmware and radios but must OTA and then re-root

you cant flash a rom with stock recovery
if no bootloader unlock, and no custom recovery, then no rom flashing..

flyhighx said:
.... Rooted Only:
.. -can flash custom ROM but must be stock based only, and must be on stock kernel .../QUOTE]
As stated above, this not correct. You'll able to flash the stock firm via Odin. In fact, you'll be able to get the tar file from Samsung if you wanted.
Click to expand...
Click to collapse

I haven't used it in awhile, but I believe you still need a custom recovery to use Mobile Odin, don't you?

i want root mostly for four reasons:
Disable logging
Multi window enable more apps
Make one hand mode background black
because its mine and i can...
But I also need it rooted without tripping knox (for work purposes..)

(Soft?)-Bricked My S7 with a Flashfire Update, Need Help to Fix It?

So I've been rooting me phone for a while and have managed to never f*** up, till now, and I sincerely hope you guys can help me.
After rooting my S7 a while back, I just recently noticed SuperUser telling me that I didn't have root anymore, so I decided to follow these instructions to re-root my phone:
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I successfully followed all the steps to get root, but when I opened Flashfire it told me I could install a new update while maintaining root, so since my android is at 6.0.1, I did that and it bricked my phone.
On boot it says "Startup Failed - Use the Verizon Software Repair Assistant . . . " and on top it also says "Custom binary blocked by SECURE BOOT." I have tried going into recovery mode and deleting the system cache, but that doesn't do it. So is there any way to get the phone to properly boot while not deleting my data? I was rooting my phone precisely so I could use Titanium Backup again, so I don't have any backups stored anywhere. I have heard that flashing a recovery image with Odin can work, but would that delete my files? Someone please lend me your expertise.
My phone is a Verizon S7.

Fixed
I am surprised that no one responded to me, but what's important is that, miraculously, I managed to un-brick the phone myself without losing any data! What I did was, as my last hope (since Odin wasn't able to flash the stock image, a la the traditional soft-brick fix), decide to follow the on-screen instructions my phone was giving me and to download and run something called the "Verizon Software Repair Assistant," which can be found in the top google results after searching for the quoted name (xda doesn't let me post the link).
After putting my phone into download mode, I plugged it in, ran the software and let it work overnight. Checking on it in the morning, I found my phone, not only completely functional and working, but updated to Android 7.0 (it was 6.0.1 previously before the failed Flashfire OTA update) and still holding all of my data intact.
So, the interesting thing that I learned is that flashing to stock via Odin to fix a soft-bricked phone should not be the default resolution for potentially most people, as the carrier's default (in my case, Verizon's) repair utility managed to completely fix my phone without any side effects or data loss.
Is there anyone who could chime in on why the Repair Utility did not wipe my phone's memory, even though it warned it would?
**Note**
Verizon links to the Windows version of the repair assistant on their site, but to get the Mac version (which I used), the only way you can get it is by changing the end of the url they mention within the thread from "Win" to "Mac."

Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here

*Detection* said:
Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here
Click to expand...
Click to collapse
I guess I am not acquainted with this forum enough then, thanks!

Most likely the cause of the fault would be updating via FlashFire and keeping root. When the update was flashed, it most likely flashed the stock kernel and patched it for root, which is not a compatible root for our devices. Flashing the root kernel with Odin probably would have made the phone boot normally.

XT1684 (UK) - Returning to Stock

Hi all.
I've asked this question in numerous threads so, to be fair to all the others whose questions I'm getting in the way of, I thought I'd post it here and wait with baited breath for a potential solution.
I very recently bought an XT1684 (3GB/32GB) UK G5 Plus. I installed all the official OTAs and got myself up to firmware version NPNS25.137-33-11. All was well, amazing battery life, but needed root for some apps. The steps I followed are roughly as follows:
1. Unlocked bootloader: I did this the usual way, got my code, chucked it into fastboot etc voila, job done.
2. BOOTED Twrp: I did this so I could attempt to back everything up without modifying, for purpose of returning to stock. It didn't work, I could not back anything up nor could I install magisk or a custom kernel. My Twrp would not read the internal storage and said something about formatting data. I ended up formatting data, which actually formatted the whole damn thing, losing my stock ROM completely.
3. FLASHED Twrp: By this point I had to, as I had limited access to the internet outside of my phone so put a lineage ROM on my phone and some gapps and flashed it.
4. Installed magisk 15.3
5. Installed Alize kernel: I did this because I was looking for improved battery life over the lineageos kernel. It hasn't been better.
So that's where I am. I have two main reasons I need to return to stock:
1. The battery life was better on my stock firmware.
2. Whenever I use lineage, I find my signal not to be as strong, and it seems to randomly lose all signal for a few seconds several times an hour, usually affecting my data more than voice calls. This is absolutely not something that happened on stock. I dunno if it's related to baseband or something, but it happens and I don't like it.
My main issue is I have seen several retUS versions of the firmware above, and lots about many other XT16xx models but nothing about my XT1684 and no fastboot images for retGB. I'm comfortable flashing pretty much anything via Twrp as I have a full backup of all partitions including OEM, system image etc but these were taken after installing lineage. I'm just totally not comfortable fastboot flashing anything except the exact correct firmware, as I've had this phone literally a week.
If anyone can help me locate the right firmware, or advise me how I could possibly return totally to stock, that would be amazing. I can provide any logs or other information required, but may need walking through more obscure commands as I am only technically proficient enough to do a basic fastboot flash, Twrp, etc.
Many thanks for reading and my apologies to all of those whose threads I've muscled in on up to this point.

Filmware is here https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
And there is a tool that automates flashing in the development section here..
https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203

Firmware - https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
How to flash - https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
?hope it helps.

Thing is, there's no xt1684 version or retgb version. I fear it could be the wrong one, can't afford to replace phone so can't risk hard bricking it.
Could someone confirm that these are safe to flash for me? Thanks for the replies, though.

Your filmware is there yes? Having said that mine is a xt1685 the same filmware number as yours but mine is euret dual SIM. Sold by Amazon UK

My confusion is that I thought they were for US models.

Well US version has no NFC but had a compass.
Has yours?

Mine has NFC and no compass lol!

darkglobe87 said:
Mine has NFC and no compass lol!
Click to expand...
Click to collapse
Seems to be typical for EU G5+ devices, NFC but no compass.
The retail firmwares don't appear to have region restrictions, hence no labelling for retEU/retGB/retUS etc. However, as you may have noticed, flashing the incorrect build for your region causes all sorts of headaches, including loss of SIM network.
That being said, you know what firmware you need (NPNS25.137-33-11) and that particular firmware was only released for EU/UK devices to the best of my knowledge. India/Brazil, US and other territories had different firmware builds released.
So, you should be okay with flashing that particular firmware - but please verify you have the correct firmware downloaded and the correct flashing instructions, and take your time in flashing.
Also, if you choose to re-lock your bootloader, re-locking your bootloader will unfortunately not restore your warranty with Motorola (which is 2 years now for EU/UK users at least). However, UK consumer laws may cover you in the eventuality of hardware repairs, just be careful. Also, re-locking will erase your device and requires firmware of the same build or newer than what is currently on your device.
Good luck whatever you decide.

I have the UK version and have gone back to stock a few times, I used this thread, and the linked firmware is the same as UK one. The guide is for bootloader locking, but ignore that part if you only wish to return to stock.
https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952

How to backup stock firmware & recovery?

Hi, recently I accidentally bricked my Galaxy Tab A 10.1 with Spen (SM-P580) by accidentally disabling "OEM Unlock" in the developer settings while I had TWRP and a custom ROM installed. I was only able to get into download mode due to the factory reset protection lock, so I tried downloading the stock firmware online and then flashing it to bring the device back to fully stock firmware so I could get past the lock and not have a brick. Unfortunately, when I flashed the firmware, despite it seemingly being for my specific device (and matching my build number), I was no longer able to boot the device at all. It would turn on and would seem to immediately lose power, charging would turn on the flash and cause it to heat up, and no amount of charging would fix the issue. It was completely bricked and there was no way for me to go back into download mode to try flashing again or try flashing a different firmware. Thankfully, I contacted Samsung and because it's still under warranty they were nice enough to fix it for free, and did so by completely replacing the motherboard according to the repair slip, which is not something I would have been able to do.
My question is: How do I make a full backup of the stock firmware and recovery so if this somehow ever happens again where the FRP lock kills my device, I can reflash in download mode the original firmware that I know is 100% going to work with it and is correct? I don't want to gamble with potentially using the wrong firmware again, seeing as that gamble killed the thing.
The Model is SM-P580NZKAXAR. Based on the last part (XAR) and the fact that other non-sammobile sites listed the US wifi only firmware as XAR, I assumed "Cellular south (XAR)" was the correct firmware I needed which was obviously incorrect as it completely bricked the device. For this reason, I'm wondering if there's a way with software on windows or something to completely backup the existing stock firmware before I do anything, because I doubt Samsung would be so nice a second time, and I'd really rather not go through all this again. Obviously these websites get the original firmware that's flashable via download mode somehow, so I'd like to know how or if that's possible. Also before I went and downloaded the firmware I checked the Samsung desktop app that allows you to fix firmware issues but it said my device wasn't supported so it wasn't much help. I'd like to avoid installing any custom recoveries ahead of time as if something gets messed up there will be no way for me to actually boot into recovery as far as I'm aware, and the FRP lock will block me from reflashing the custom recovery or anything else that isn't stock. It goes without saying that if this is possible I'd like to do it without installing a custom recovery or rooting as I'd like to have a proper fully stock backup that isn't going to trip the FRP lock.
Also the way I accidentally disabled OEM Unlock was I simply toggled the developer options off and then back on in a slimmed down version of the stock rom, but in doing so it also reset the OEM unlock setting and I completely forgot to make sure it was still enabled. Next thing I know I go to reboot (was trying to figure out an issue with a usb device) and then the thing was FRP locked. Needless to say, it was something extremely simple and easy to do by accident. I also just checked the device and the build number matches the firmware that I downloaded, so I don't know if it was mislabeled or what but something was not correct.