Hi there,
Just got a new S5 mini (SM-G800F) today. I've updated to latest Android version (4.4.2). I did not install any custom ROM. Build ID was KOT49H.G800FFXXU1ANJ1.
I've then rooted the phone successfully with CF-Auto-Root (http://autoroot.chainfire.eu/) and Odin. The closest file I found was KOT49H.G800FXXU1ANH2. ANJ1 to ANH2 looks like a "downgrade"... perhaps this is the issue? But read on..
I then started to install corporate access (Exchange account). Our corporation wants to have the device encrypted so I started to do that.
What basically happens is that the encryption droid symbol shows on the screen for about 20 minutes and after that the device reboots.
Yet, no encryption has happened! (is the anywhere a logfile I can look at for more info?)
I have a Samsung Galaxy S3 with 4.1.2, stock ROM as well and rooted with CF-Auto-Root. On that device the encryption process was more verbose and worked fine (although slowed down the phone considerably during normal usage).
So, does rooting the S5 mini with Autoroot break the encryption process? How can I encrypt the phone? Do I have to go back to pure unrooted stock, encrypt first and root later?
Thanks for any insights.
Dan
I still do not know why encryption would not work, but I found a workaround:
I reset the phone to the latest stock firmware with the help of Kies 3. I got G800FFXXU1ANG7. Obviously I lost all data, but that is ok since its a brand new phone.
Started the phone and configured WLAN to accept and install pending OTA upgrade. Just to get to the very latest release at the moment (G800FFXXU1ANJ2).
Encrypted device. I installed the corporate access tools which required the encryption...
Then I installed latest TWRP for my device with ODIN.
Last step was to install SuperSu with TWRP, using the zip file from chainfire.
Some remarks:
- I am not sure why encryption fails while the phone is rooted. Perhaps someone could explain to me?
- If I use CF-Autoroot after encryption of the device, the phone would go into a boot loop, i.e. not asking for the decrypt password and fall back to the boot logo. I thought that encryption would only touch /data. Most likely there is something that initiates decryption during boot, which is replaced by the CF-Autoroot image.
- OTA updates are not possible anymore after installing TWRP recovery (the phone complains that there are changes to the stock ROM). However, if I re-flashed with a stock recovery, OTA was not complaining anymore. If an update would actually work, I have not checked.
- If SuperSu is already installed however, even TWRP re-flashing with stock recovery would not make OTA work again. I would assume that the OTA update routine checks several components to decide if there is stock installed. Temporarily disabling SuperSu did not work, un-rooting through the SuperSu menu left me with SuperSu hanging for an hour until I switched the phone off. I also tried the OTA survival mode (I have SuperSU Pro) and it does not work either (in that try I left out step 2 above).
So for now I have a rooted S5 mini on Android 4.4.2 with encryption and I am happy. I did live without OTA with my S3 (which still is on 4.1.2) since I rooted it and frankly, I did not really miss 4.3...
Regards
Dan
If you change some files (like Recoery or rooting) OTA won't work anymore on any Samsung Rom...only pure Stock!
User_99 said:
If you change some files (like Recoery or rooting) OTA won't work anymore on any Samsung Rom...only pure Stock!
Click to expand...
Click to collapse
Thanks. That is what I thought.
1 - Encryption fails if the phone (S5 mini, 4.4.2) is rooted. Why? However, encrypting a rooted S3 (4.1.2 stock) did work fine. Was there anything changed with the newer Android versions?
2 - Do we know what the OTA process is checking to decide if it can go ahead or stall? SuperSu's OTA survival surely knows a bit more on that.. but unfortunately it still won't work..
Mahesh Senghani here please help me. Long time trying but not properly Root Access not properly configured or was not granted. Please sir how to fix this problem deeply request to you please solution easiest explain to me
Mahesh Senghani
Please help me you send Email [email protected]
How to fix this problem
grokit said:
Thanks. That is what I thought.
1 - Encryption fails if the phone (S5 mini, 4.4.2) is rooted. Why? However, encrypting a rooted S3 (4.1.2 stock) did work fine. Was there anything changed with the newer Android versions?
2 - ..
Click to expand...
Click to collapse
Hey, please read about KNOX, hope you may get your answer...
Q&A for [UTILITY][RESTORE][UNLOCK][ROOT][RECOVERY] Samsung Gear Live Restore Tool
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [UTILITY][RESTORE][UNLOCK][ROOT][RECOVERY] Samsung Gear Live Restore Tool. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
V3 Bluetooth
I too used the V3 tool to root but at the end my phone wouldn't recognize the Gear. I ended up wiping everything, used the V1 then the V2 and finally got the gear back to where I could use it. Did the OTA and all seems okay. Going to try an root using V2 instead. My question is once that is all successful what can I do different? Can I download a keyboard onto the Gear? As a NOBE where do I go to find a new ROM , find out how to flash it and then what I can do from there? I will apologize upfront for my beginner questions. Thanks
armisis said:
It looks like your download link is broken.... doah just caught that your all over it... sorry...
Thanks,
Dave
Click to expand...
Click to collapse
APK Apps aren't working?
I installed Nova Launcher and Flesky Keyboard and each time I try to use them on the Gear Live I get this message "unfortunately Nova Launcher has stopped". Can anyone tell me what I've done wrong or need to do to be able to use these apps on my Gear Live?
Did you have time to test it with the recent 5.0.1 update? I'd love to use your Utility to restore my watch to its factory state but I'm not sure if it would break (I know, there's always a chance).
Do you think I can try flashing the images without damaging it?
Used V3 of this utility to flash stock image after of temp rooting for data extraction. Now it won't pair with any phone anymore. No Bluetooth. Can't get adb to work as I can't authorize the computer to flash anything else.
Watch is a useless now. Heads up to others.
At leat I have an excuse to buy a Moto now
UPDATE: IT LIVESSSSS!!!!!!!!!!
So I didnt know that the watch could go into fastboot with some custom taps and such. Did those, got into fastboot, used V2 toolkit and all is well now!!!
How to for others:
1. Hold the power button until the Gear Live reboots
2. When you see the Samsung Logo on the screen swipe your finger from top left to bottom right of screen twice while still holding power
Success!!!!!!!!!!
No Download
Hey all,
Am I the only one who is not getting a ZIP file when the download starts; the file that downloads is not usable. Any suggestions would be appreciated.
Crooter777 said:
Hey all,
Am I the only one who is not getting a ZIP file when the download starts; the file that downloads is not usable. Any suggestions would be appreciated.
Click to expand...
Click to collapse
rename the file 'samsung' to 'samsung.zip'
Thank you.
Galaxy Gear Unauthorized
I am not able to pair phone with watch via Bluetooth after using this tool. I unlocked the bootloader but when I could not use the watch I decided to relock the bootloader and reattempt the steps again. Now I am getting (R3AF700JARM UNAUTHORIZED). I factory reset watched became a developer and enable ADB debugging, but I still cannot unlock the bootloader and still shows unauthorized. WHat is the next step
I cannot get it to recognize my watch
I purchased a Samsung Gear Live refurbished off amazon and it had Build Number = sprat-userdebug 4.4W.1 KGW42N 1387258 dev-keys installed. It will not update and I want to be able to put other watch faces on it. I heard that if you reset to stock google wear it would fix it.But I used your software v3 and installed adb drivers but does not recognize the watch?
Any help would be Great!!!
ratdog420 said:
I purchased a Samsung Gear Live refurbished off amazon and it had Build Number = sprat-userdebug 4.4W.1 KGW42N 1387258 dev-keys installed. It will not update and I want to be able to put other watch faces on it. I heard that if you reset to stock google wear it would fix it.But I used your software v3 and installed adb drivers but does not recognize the watch?
Any help would be Great!!!
Click to expand...
Click to collapse
Read the user debug thread. Try v2
Superuser.apk in my Gear Live
Hello.
After using the Tool, I was able to restore my Gear Live, and get updates (Originally it comes with bad firmware, from bestbuy).
I only have one problem. After several updates, I have AndroidWear 5.1.1. I got OTAS from 4.4w, justo normally, but the process
left me with Superuser.apk installed.
I can't uninstall it, and if I try to run it, I get an error, and the apk closes.
Is there something I can do, to eliminate this app? I tried with temproot, but I can't access to original system folder in my Gear Live.
Can you, or anyone help me with this problem?
I flashed KMV78Ystock.zip. In theory, it is a stock rom dump. I can't see the Superuser.apk, if I mount the image.
I just want my Gear Live factory restored. I hope you can help me.
Thanks in advance!
arieru01 said:
Hello.
After using the Tool, I was able to restore my Gear Live, and get updates (Originally it comes with bad firmware, from bestbuy).
I only have one problem. After several updates, I have AndroidWear 5.1.1. I got OTAS from 4.4w, justo normally, but the process
left me with Superuser.apk installed.
I can't uninstall it, and if I try to run it, I get an error, and the apk closes.
Is there something I can do, to eliminate this app? I tried with temproot, but I can't access to original system folder in my Gear Live.
Can you, or anyone help me with this problem?
I flashed KMV78Ystock.zip. In theory, it is a stock rom dump. I can't see the Superuser.apk, if I mount the image.
I just want my Gear Live factory restored. I hope you can help me.
Thanks in advance!
Click to expand...
Click to collapse
Did you try removing via adb? In theory, a factory reset of watch and flash image again it should clear non stock files
Brendo said:
Did you try removing via adb? In theory, a factory reset of watch and flash image again it should clear non stock files
Click to expand...
Click to collapse
I just flashed recovery, boot and system images again. Whitout flashing twrp recovery. And have a perfectly pure gear live. Thanks for the advice.
Seems like custom recovery was the problem the first time.
Enviado desde mi Nexus 5 mediante Tapatalk
Samsung Gear Live
I have installed the ADB driver, but when I run the test my device is not found and my computer is saying USB device not recognized. Also, I never got a pop up on my phone. Any suggestions?
Thanks
Gear Live watch only shows TWRP menu from team win
So i am not a programmer and don't know most of this stuff, I just followed instructions. I installed root, recovery, and system images through cmd prompt. I lost bluetooth and other functionallity but it seemed to update to a newer version. I then attempted to flash TWRP which put my phone in a state that only shows the TRWP menu. I have restarted, rebooted, tried installing other images but i really don't know what to do. Can anyone help, Please!
I have a note 5 phone
watch is reconditioned, it was in some kind of mode that is not the original factory mode, many features were not working or not there. that is why i started this process.
http://forum.xda-developers.com/showthread.php?t=2846696 do stock restore, make sure you have watch plugged in, factory reset and connected bluetooth to phone. The updates will begin
Sent from my SM-N910T3 using XDA-Developers mobile app
Hi all !
I have decided to root my tab s2 to gain access to system to modify parameters to disable add user option in notification. I see no other working option.
Request to help me with the required tools and guide to root. Will it be possible to update to nougat after I root ?
Is it possible to root the device and stay on the same andriod version ? I have previous rooted my other phones including pantech burst and samsung wave 2 but not able to find a complete guide for tab s2 SM-T715
Thanks a lot !
Yes, it possible to root the device and stay on the same andriod version. Matter of fact, once rooted you should disable OTA updates for thyat can break root and your device.
You could update the OS manually via TWRP.
But first and for most, you had better make a system backup before tinkering about.
https://www.howtogeek.com/240582/how-to-back-up-and-restore-your-android-phone-with-twrp/
Moreover, TWRP can give you temporary root access.
Hello friends -
Looking for some help. I am trying to upgrade several Galaxy S6 Active SM-G890A devices with 5.1.1 to Android 6.0.1 without wiping the existing apps. I have a device that has the OTA file downloaded, I followed the steps shown on XDA-Developers to capture the URL via ADB or via Take bug snapshot, didn't find the URL.
I read some posts that using Odin and HOME_CSC you can upgrade the firmware without wiping the device. I can't seem to find HOME_CSC - where or how do I find it or how can I take a backup of this? None of my devices are rooted. I am trying to upgrade several of these devices in the field and want a process that I can document and then have my team upgrade these.
Any help will be appreciated!!
Deejas
I've recently acquired a used galaxy s10e which has some carrier apps left that can't be uninstalled. How would I go about flashing clean, stock firmware with minimal hustle? I don't want to unlock the device or root it.
Thank you for any help.
if you can connect it to PC via adb, you can disable them using the adb commands.