Unable to root 800F under Lollipop 5.1.1 - Galaxy S5 Mini Q&A, Help & Troubleshooting

Hi guys,
I have successfuly updated my SM-G800F phone using G800FXXU1BOL4_G800FVFG1BOL1_G800FXXU1BOL3_HOME (Cyprus version) today. I also tried to root it using Odin3-v3.07.exe and CF-Auto-Root-kminilte-kminiltexx-smg800f.tar.md5. Unfortunately, this leads into instant boot loop. I just reflashed phone to Lollipop again. Can you help me with rooting this version?

Rooting certainly is possible, even on that exact ROM.
Some notes:
- With stock ROMs you should generally not root before you have completed the setup wizard
- The only variant of root that works with the stock Lollipop ROM is "Systemless" root
- The Odin version you're using is outdated. It *might* make a difference to update.
When you ran AutoRoot, did it claim it was performing systemless root?

Thanks for your reply, got rooted. I found CF-Auto-Root-kminilte-kminiltexx-smg800f was outdated too.

Related

[Q] Enryption fails on rooted S5 mini (G800F)?

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...

Note3 n900a firmwares/NL1 to NC2/NO PC/TOWELROOT/HELP?

Ok so first let me apologize if I overlooked a similar post but I've been having root issues for weeks now and haven't found my exact situation yet.
Here's the background. I have an AT&T Note 3 N900A. When I got the phone I had no issue using towel root to root the device. Worked first try. I'm new to rooting and I was in love with all the new options. I started small playing with xposed and fonts overclocking etc. Then started researching custom Roms. Discovered cwm twrp wouldn't work with my locked boot loader so researched and got safestrap. Did the backup made my new Rom slot and with a guide I attempted my 1st custom Rom flash. FAIL. bootloop. Revert to stock Rom via Odin. Download towel root. Rooted. No problem.
2nd attempt at custom Rom flash with safe strap. fail. Download another stock firmware (at this point I was still dumb to the difference between NL1 NC2 OC2 etc). And in still dumb to oxed and deoxed. But apparently I got out of bootloop with a different firmware version this time around. First I decided to run lollipop 5.0. Towel root said device not suported. Now I'm running 4.4.4 NL1. device not supported. Also can't get kingoroot king root(pc or non pc) cf or anything else I've tried to work. From what I've read I need to go back to the NC2 4.4.2 and run towel root from there.
My current issue is I have no windows pc to run Odin on and my wife's MacBook refuses to install the Mac version correctly nor will it load the Web based version on the casual page.
I just figured out that I can't use safe strap to flasthe nc2 until I'm rooted. And without Odin to revert I'm scared to try any other method without some guidance.
First off... Is there any way to root my current 4.4.4 without going to the nc2 or if I allow my phone to upgrade to 5.o again is there a non pc root method on lollipop yet?
Or would I be able to download a nc2. Zip to my phone save to sd and use the note 3 stock recovery to revert? ?
I'm open to any suggestions you guys may have even if I haven't mentioned it in my post. Hope to get some answers asap and thanks in advance!!
I'm not familiar with the Note 3 for AT&T but Heimdall (in place of Odin on a PC) may work on your mac to flash ROMs.
http://glassechidna.com.au/heimdall/
Yeah I tried that a while back but it was b4 I knew this much. Maybe j can get it working now. I was just hoping there was an easier way.

G920AUCS5DPJ1 Root?

Any way to root 6.0.1 G920AUCS5DPJ1 yet? Did some research but could not find a way to root for this particular build. Any update?
I've been searching for an easier method to root my phone and I'm shocked at how few options there are to root my s6. I've always been able to come across more than enough information to root all the previous galaxy phones but for some reason there doesn't seem to be an easy method (like ping-pong root or something automated) I'd appreciate if anyone has any feedback on rooting the new build after the November security patch the build number is G925AUCS5DPK1
Hidd3nD3Ath said:
I've been searching for an easier method to root my phone and I'm shocked at how few options there are to root my s6. I've always been able to come across more than enough information to root all the previous galaxy phones but for some reason there doesn't seem to be an easy method (like ping-pong root or something automated) I'd appreciate if anyone has any feedback on rooting the new build after the November security patch the build number is G925AUCS5DPK1
Click to expand...
Click to collapse
Feedback is, there is no root for the new builds.
Sent from my SAMSUNG-SM-G920A using Tapatalk
And is there any way to go back to old builds flashing with ODIN an old stock firmware?
I confirm: once you get the phone on a newer version, you can't downgrade it. I tried to go from 6.0.1 to 5.1.1 flashing with ODIN. The ODIN process went well, but after the phone took the older load, it got stuck in the ANDROID screen
To get it back to life i had to flash again its original stock version at 6..0.1
So the question is if there will be any developement on S6 ATT 6.0.1 to get it rooted or TWRP. RIght now it seems we are stuck. No root, No custom rom I will keep my S4 that performs like a charm with root and custom roms!
ronniler said:
I confirm: once you get the phone on a newer version, you can't downgrade it. I tried to go from 6.0.1 to 5.1.1 flashing with ODIN. The ODIN process went well, but after the phone took the older load, it got stuck in the ANDROID screen
To get it back to life i had to flash again its original stock version at 6..0.1
So the question is if there will be any developement on S6 ATT 6.0.1 to get it rooted or TWRP. RIght now it seems we are stuck. No root, No custom rom I will keep my S4 that performs like a charm with root and custom roms!
Click to expand...
Click to collapse
Development has been essentially dead on the ATT version for many months.
Sent from my SAMSUNG-SM-G920A using Tapatalk
Thanks @dandrumheller for the reply
I am debating myself to try something even i know is highly possible i break the phone. I really need a rooted phone and this s6 is a replacement for my s6 given to me by ATT. If i can't get it rooted, it will sit there forever. So probably i will take the risk to try to root/load anything experimental
:S

Root SM-T810 running Marshmallow 6.01?

I don't want to be lame and ask anyone to do my homework for me, but I am not finding a clear method here in these boards. There are of course methods out there on the web, but I don't exactly trust them when there isn't a clear method on XDA. I see the international models have all the goods, and I also see some interesting looking ROMS avail for the T810 which certainly gives the impression that root is out there.
Anyways, my goal is to get root and eventually get upgraded to Nougat. TWRP would be nice, but I did read in one of the threads that there is a bug with the t810 on 6.01 that causes a bootloop. I am running stock 6.01 currently with nothing. Anyone able/willing to assist?
I just updated from marshmallow my self, and what i did was install nougat normally, then install twrp using hemidall( or odin if your on windows), and then installed the super su zip in twrp to get root access.

KFFOWI Stuck at Fire boot animation - Which version to restore?

Hello,
I have a KFFOWI which I rooted some months ago with Superjunky tool, and it worked great. Recently I lost root following Supersu messy update. I tried today to restore root with Superjunky tool : King root rooted succesfully, then when it was time to install supersu and delete Supersu something went wrong, script maybe didn't have root access, well I don't know.
My device is now stuck at the Fire boot animation. I'm ready to restore a stock version, but how can I be sure of the one which was installed, as I don't want to restore a different version and hard brick ? Is there a way from recovery or bootloader to identify firmware version ?
Any help will be appreciated.
Displaying logs under recovery, I think I identified version : 5.1.1
madxxcow said:
Hello,
I have a KFFOWI which I rooted some months ago with Superjunky tool, and it worked great. Recently I lost root following Supersu messy update. I tried today to restore root with Superjunky tool : King root rooted succesfully, then when it was time to install supersu and delete Supersu something went wrong, script maybe didn't have root access, well I don't know.
My device is now stuck at the Fire boot animation. I'm ready to restore a stock version, but how can I be sure of the one which was installed, as I don't want to restore a different version and hard brick ? Is there a way from recovery or bootloader to identify firmware version ?
Any help will be appreciated.
Click to expand...
Click to collapse
madxxcow said:
Displaying logs under recovery, I think I identified version : 5.1.1
Click to expand...
Click to collapse
5.1.1 likely references the underlying version of Android which FireOS and all custom ROMs for this device are built upon.
To be absolutely safe reload FireOS 5.3.1 which is the highest rootable build. Before doing that try a factory reset (clearing cache/data) from the recovery menu. Often does the trick.
Thanks. Installed 5.3.1.
Then several attempts to root it with Supertool/King root, around 6 or 7.
Everything works great now.

Categories

Resources