Help for rooting!! - Galaxy S 5 Q&A, Help & Troubleshooting

Hey guys,
I installed the TWRP recovery ad followed the steps as mentioned in that thread but I cannot boot into the recovery nor does any app like Flashify say that I have root access. When I go to download mode it shows that Knox is void but then the volume up + home + power button goes to normal android recovery.
I have Samsung Galaxy S5 G900H.
Any idea where I went wrong and what I can do to fix this? I am sort of new to rooting android.

Use cf-Auto-Root of Chainfire
assasin93 said:
Hey guys,
I installed the TWRP recovery ad followed the steps as mentioned in that thread but I cannot boot into the recovery nor does any app like Flashify say that I have root access. When I go to download mode it shows that Knox is void but then the volume up + home + power button goes to normal android recovery.
I have Samsung Galaxy S5 G900H.
Any idea where I went wrong and what I can do to fix this? I am sort of new to rooting android.
Click to expand...
Click to collapse
Hi,man
At first if you have any bootloop or issues
you must download the latest firmware from samobile http://www.sammobile.com/firmwares/download/51740/G900HXXU1BOG4_G900HOXY1BOG4_SKZ
By using odin flash
& you will repair your device (softbrick)
After that yu can use Cf-Auto-Root http://download.chainfire.eu/402/CF-Root/CF-Auto-Root/CF-Auto-Root-k3g-k3gxx-smg900h.zip
It s good for newbies
Follow all steps of root
Perhaps yu ve to reflash root if not works once
Good luck assasin93!

How to recover after a power failure during booting?
Anyone know how to recover from power failure during booting? Thank you and very much appreciated!

Repair soft brick by odin flashing latest firmware
If i ve understand well your question
in twrp recovery mode yu have restore option
(if yu have an backup) & 3 wipes options :
- You can restore if backup is on
- You can try wipe dalvik after that wipe cache
If all else fails wipe data for installing firmware
What's your twrp version ?
For repair softbrick (bootloop) go on downlooad mode
& flash by odin the latest firmware of g900h from sammobile link.

Hi, I use this thread for my question.
I've got a brand new G900F since my SGS 2 died.. I read here and there that there are some problems to root the new S5' without triggering knox.
What Ive done so far, im coming from the POG7 (german BOE5 with Vodafone branding), flashed the unbranded DBT_BOE5 without problems and tried to downgrade to ANE2 to use towleroot. The flash to ANE2 was successful, but the screen appears to be black, so I cant work with the phone. I blind started the download mode so I could flash back to BOE5. Is there a way to root the newer S5' coming with stock 5.0?
Greetings

Related

Please Help Very Frustrated.

hello guys,
i bought a used galaxy s5 from someone running Poland Android lollipop 5.0 and it shows the model as SM-G900F When i try to root it with CF-Auto-Root-klte-kltedx-smg900f It gets stuck on the boot screen saying
"1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)"
i googled alot and flashed Phillz recovery which removed the error above but when i go to recovery its the stock recovery? .... I cant install twrp-2.8.7.0-klte.img.tar Either because after flashing it when i go to recovery its stock recovery again. Activation lock is off, SE for Android status is "enforing" does this mean this phone has a locked bootloader? Maybe this phone was on At&T, Sprint or Verizon and the last owner flashed 900f firmware on it to make it look carrier free but it maybe a carrier phoone? Please help me i am very very frustrated right now. i dont even know what recovery is seandroid enforcing means.....:crying::crying::crying:
dork997 said:
hello guys,
i bought a used galaxy s5 from someone running Poland Android lollipop 5.0 and it shows the model as SM-G900F When i try to root it with CF-Auto-Root-klte-kltedx-smg900f It gets stuck on the boot screen saying
"1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)"
i googled alot and flashed Phillz recovery which removed the error above but when i go to recovery its the stock recovery? .... I cant install twrp-2.8.7.0-klte.img.tar Either because after flashing it when i go to recovery its stock recovery again. Activation lock is off, SE for Android status is "enforing" does this mean this phone has a locked bootloader? Maybe this phone was on At&T, Sprint or Verizon and the last owner flashed 900f firmware on it to make it look carrier free but it maybe a carrier phoone? Please help me i am very very frustrated right now. i dont even know what recovery is seandroid enforcing means.....:crying::crying::crying:
Click to expand...
Click to collapse
Akalsemann said:
Ok guys, try this.
1. Download philz kernel that matches your modem number. I think philz_touch_6.26.6-klte.tar.md5 works good.
2. Put it in ODIN on PDA/AP
3. Uncheck "Auto Reboot" and make sure Re-Partition is NOT CHECKED (keep F. Reset time)
4. Flash
5. It will say RESET on Odin and nothing further when it is done so just wait 2-3 minutes when RESET appears to be entirely sure that the procedure is done.
6. Pull out phones battery.
7. Put it back in and now go into Recovery directly (Vol up+home+power)
8. ???
9. Profit
Hopefully this might work, i think i did the same
Click to expand...
Click to collapse
Try that
Akalsemann said:
Try that
Click to expand...
Click to collapse
Kindly note that i am able to boot fine now, but the recovery wont stick and whenever i try to root this seandroid error happens
Did u do the following steps correctly
it should work bro
Been there
done the same process
thanx again Akalsemann
vinura kithmal said:
Did u do the following steps correctly
it should work bro
Been there
done the same process
thanx again Akalsemann
Click to expand...
Click to collapse
yes i entered philz recovery > selected format to install new rom > now stuck on samsung logo maybe it removed rom files. Now downloading flash roms from sammobile. Dont know if it will let me root it or not. can u please explain what this error is and why is it caused?
dork997 said:
Kindly note that i am able to boot fine now, but the recovery wont stick and whenever i try to root this seandroid error happens
Click to expand...
Click to collapse
You need to just boot into download mode (voldown+home+power) then push volup to enter download mode
Use Odin to flash trwp 2.8.6.0 tar file in AP spot
Download a pre rooted rom of your choice for g900f
Place on sd card
Reboot to twrp by holding volup+home+power immediately during start of boot
Flash the rom you just downloaded
Now you'll be rooted
(That's what I did in order to get my phone rooted after installing the newest stock lollipop ota)
Sent from my SM-G900F using Tapatalk
dork997 said:
yes i entered philz recovery > selected format to install new rom > now stuck on samsung logo maybe it removed rom files. Now downloading flash roms from sammobile. Dont know if it will let me root it or not. can u please explain what this error is and why is it caused?
Click to expand...
Click to collapse
Common bro
u haven't rooted your device,
u have to flash the supersu zip to get the root access
http://download.chainfire.eu/supersu
first download this file and place it in your device storage,once u pull the battry off and put it back in go straightly to the recovery
select install zip and flash the supersu.zip
then reboot it,after the first boot then go to the recovery and
install your custom rom
Swimguy14 said:
You need to just boot into download mode (voldown+home+power) then push volup to enter download mode
Use Odin to flash trwp 2.8.6.0 tar file in AP spot
Download a pre rooted rom of your choice for g900f
Place on sd card
Reboot to twrp by holding volup+home+power immediately during start of boot
Flash the rom you just downloaded
Now you'll be rooted
(That's what I did in order to get my phone rooted after installing the newest stock lollipop ota)
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
vinura kithmal said:
Common bro
u haven't rooted your device,
u have to flash the supersu zip to get the root access
http://download.chainfire.eu/supersu
first download this file and place it in your device storage,once u pull the battry off and put it back in go straightly to the recovery
select install zip and flash the supersu.zip
then reboot it,after the first boot then go to the recovery and
install your custom rom
Click to expand...
Click to collapse
I followed instructions given earlier to install philz recovery, i opened it by booting into it immediately i selected format for new rom install. after that i am stuck on samsung logo i think the old rom is now deleted. Now i am downloading fresh 5.0.2 UK from sammobile i will download it and try to root it normally with flashing CF ROOT via odin. if it does not work then i will do what u guys said. I dont know if TWRP will work by the same method (booting immediately into recovery) but philz recovery did. And i will also try flashing a prerooted Rom. What i dont understand is that why is this happening in the first place? i had an alpha before i could enter into TWRP normally i rooted it with CF AUTO root normally...no errors or anything why is this happening on my S5? the last owner must have done something weird with it ...i am trying to figure out why is this happening in the first place. Appreciate ur feedback.
I also dont know why this is happening
and yeah
i had all the galaxy S series upto S5 and this the only device that is not rooting with CF-auto root
the latest updates from samsung may have done something i dnt knw
and eralier mentioned method worked 100% for me and i did root my device like that
And last owner may b or may not done anything with it because my device is a brand new and still i had that issue

Unable to install custom recovery and flash custom roms on rooted note 3 lte

I am on a UK (vodafone) phone 4.4.2 KK and after rooting with odin and tripping knox (obviously) i installed CWM And TWRP and entered recovery but only after a long time i discovered that the recovery mode i was entering was stock .
In the recovery mode i couldnt find the option to install from zip only the option to install from external storage.
I have downloaded the CM 11 4.4.4 and put it on the external sd card.
In the recovery mode i navigated to the location of the CM 11 zip and attempted to flash it .
It goes through the process and at the end it says something like installation successful but the the phone boots into the normal stock firmware.
After reading a ton of material and articles i have discovered that my bootloader may be locked and this is the reason i cannot install CWM and flash custom roms.
In the end i have 3 questions.
Is there curently a solution to install CWM and flash custom roms on phones with locked bootloders ?
Will i be able to update to lollipop via Kies when is released ?
Will i be able to return my phone to its original state so that the lollipop update when it is released wont detect that the phone has been modified ?
Basically i am stuck. I have a rooted phone with void warranty and unable to install roms because the bootloder is locked ??????
I would really apreciate some help because i have run out of options and the frustration has reached stratospheric levels.
Thanks in advance for your help.
You rooted with ODIN and installed both CWM and TWRP .Thats all wrong odin is not root and you don't flash two recovery s .
You say your bootloader is locked = what model phone do you have .
Its reading as fail read the very basics .
Start at the beginning at for that you need to know what model number you have . You then find the correct root for your model and flash a recovery either CWM or TWRP not both .
JJEgan said:
You rooted with ODIN and installed both CWM and TWRP .Thats all wrong odin is not root and you don't flash two recovery s .
You say your bootloader is locked = what model phone do you have .
Its reading as fail read the very basics .
Start at the beginning at for that you need to know what model number you have . You then find the correct root for your model and flash a recovery either CWM or TWRP not both .
Click to expand...
Click to collapse
I did not flash both.
I only installed both and tried to flash either.When i saw that i couldn flash one i tried the other one.
My phone model number is SM-9005 ..
The root file i used was CF-Auto-Root for SM-N9005 .
uxaar said:
I did not flash both.
I only installed both and tried to flash either.When i saw that i couldn flash one i tried the other one.
My phone model number is SM-9005 ..
The root file i used was CF-Auto-Root for SM-N9005 .
Click to expand...
Click to collapse
Flash this in Odin.
https://dl.twrp.me/hlte/twrp-2.8.7.0-hlte-4.4.img.tar.html
Sent from my SM-N9005 using Tapatalk
Untick auto reboot in Odin when you flash recovery then boot to recovery using three button combo stock ROM rewrites stock recovery when it boots iirc
celderic said:
Flash this in Odin.
https://dl.twrp.me/hlte/twrp-2.8.7.0-hlte-4.4.img.tar.html
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Thank you very much.
That worked flawlessly and afterwards i managed to install CM12 5.1.
you saved me .Thanks again

S4 GTI9505 flashed recovery without root help

So I accidentally flashed the recovery package through Odin to a friend's s4 gt i9505 and i get a no access error in the recovery with an android and a red triangle. Since it has a custom recovery odin doesnt detect it. My question is what should i do ? . There is literally noone that has experienced the same (noob) mistake so there is no real fix. The phone is running 4.4.2 with an official upgrade to lollipop but KNOX was tripped so I would like to fix for him without having to pay for official service.
Thanks in advance.
Odd. I have a custom recovery on my S4 and Odin detects my S4 without a problem, meaning something else is causing your connection woes. Obviously, make sure you're in download mode first (hold down the volume down, home, power keys), which wouldn't be affected by a custom recovery, and change USB ports until Odin does recognize the device. Then flash the stock ROM again to restore the S4 to working order.
Strephon Alkhalikoi said:
Odd. I have a custom recovery on my S4 and Odin detects my S4 without a problem, meaning something else is causing your connection woes. Obviously, make sure you're in download mode first (hold down the volume down, home, power keys), which wouldn't be affected by a custom recovery, and change USB ports until Odin does recognize the device. Then flash the stock ROM again to restore the S4 to working order.
Click to expand...
Click to collapse
the thing is it bypassed download mode straight into the recovery so it didnt recognize it at all. Maybe it was because it had a non rooted recovery? Anyway i rooted the phone with kingoroot which on the one hand it worked on the other hand the phone laggs like hell but it wiped the custom recovery somehow so i got samsung's download mode back flashed cf auto root but it doesnt update su binary so thats my problem now . The phone is a 4.4.2 firmware so should i Flash first lollipop and then root it or flash a recovery to install the su binary from there?
CostasV23 said:
the thing is it bypassed download mode straight into the recovery so it didnt recognize it at all. Maybe it was because it had a non rooted recovery? Anyway i rooted the phone with kingoroot which on the one hand it worked on the other hand the phone laggs like hell but it wiped the custom recovery somehow so i got samsung's download mode back flashed cf auto root but it doesnt update su binary so thats my problem now . The phone is a 4.4.2 firmware so should i Flash first lollipop and then root it or flash a recovery to install the su binary from there?
Click to expand...
Click to collapse
Based on your first post and this post I have come to the conclusion that you have absolutely no idea what you are doing. You are mixing everything up. And I mean everything.
- A non rooted recovery? What is that? It doesn't excist. A recovery has nothing to do with root.
- Because you had a custom recovery Odin doesn't detect it? Completely impossible. A custom recovery has nothing to do with Odin detecting or not detecting.
- Wiping the recovery and getting download mode back? Dude that's impossible. Download mode and recovery are two completely different things.
1. Flash Lollipop if you want Lollipop. With .pit and re-partition.
2. Perform a factory reset.
3. Flash cf-auto root.
That's all there is to it.
Lennyz1988 said:
Based on your first post and this post I have come to the conclusion that you have absolutely no idea what you are doing. You are mixing everything up. And I mean everything.
- A non rooted recovery? What is that? It doesn't excist. A recovery has nothing to do with root.
- Because you had a custom recovery Odin doesn't detect it? Completely impossible. A custom recovery has nothing to do with Odin detecting or not detecting.
- Wiping the recovery and getting download mode back? Dude that's impossible. Download mode and recovery are two completely different things.
1. Flash Lollipop if you want Lollipop. With .pit and re-partition.
2. Perform a factory reset.
3. Flash cf-auto root.
That's all there is to it.
Click to expand...
Click to collapse
What I meant was that I accidentally flashed the recovery tar.md5 file before cf-auto-root and it wasn't working . aside that I get an su binary update error is there a fix for that?
CostasV23 said:
What I meant was that I accidentally flashed the recovery tar.md5 file before cf-auto-root and it wasn't working . aside that I get an su binary update error is there a fix for that?
Click to expand...
Click to collapse
Root and recovery are two unrelated things. You don't need root for a custom recovery and you don't need a custom recovery to root.
I would start with a clean install since you used Kingoroot and cf auto-root.
Flash a stock rom with re-partition and .pit. Then only use cf auto-root.
Lennyz1988 said:
I would start with a clean install since you used Kingoroot and cf auto-root.
Flash a stock rom with re-partition and .pit. Then only use cf auto-root.
Click to expand...
Click to collapse
If I flash the official lollipop firmware via odin will it work you mean ? (Sorry for noob question ) also about that .pit I haven't found anywhere a .pit file is it necessary ?
CostasV23 said:
If I flash the official lollipop firmware via odin will it work you mean ? (Sorry for noob question ) also about that .pit I haven't found anywhere a .pit file is it necessary ?
Click to expand...
Click to collapse
You can also wipe /system and /data in TWRP and then flash Lollipop firmware.
Lennyz1988 said:
You can also wipe /system and /data in TWRP and then flash Lollipop firmware.
Click to expand...
Click to collapse
Is it obligatory i wipe the system partition because odin flash rewrites it anyway or am i wrong on this one?
Also after kingroot the recovery was wiped clean for some reason
Bro my s4 GT I9505 have stock rom v5 .0.1 UHOE3.now I need rooted and install philz touch recovery so pls proper guide and file.thanks in advance.
Philz is outdated, and certain ROMs will not install with it. Use TWRP instead. For installing, it's just like installing a stock ROM through Odin. We have guides on this in the General section.

dm-verity verification failed

2 days ago i flashed twrp on my pure stock note 4, i did backup my rom including EFS using twrp and then flash kyubi rom with nameless kernel, it all went well. just now i wipe data ,system, cache on twrp and restore my backup stock rom and it went well too...and then i try to flash stock rom using odin so i can get back the stock recovery mode for OTA update when MM releases.. the flashing was a sucess and phone booted but my data inside werent wipe.
so i went to recovery mode and saw this dm-verity verification failed on the bottom i proceed to wipe data and reboot my phone, its all working now no problems except i cant reset my phone with the setting inside it will just bring me to recovey mode and stay there with that message.
now i did some research, some saying will bootloop and stuffs but mine is all ok no problem except i cant reset it inside the settings..
anyone can help me get rid of that message/problem?
If you format everything in advance format in twrp and then flash stock firmware this message will go away.
got the same problem. Then I went to a local store. They helped me. Here are steps
1. Pull out your battery, check your serial number (S/N:....)
2. Download smart switch, enter emergency software recovery..... Enter your serial number
3. Turn off your phone. Enter download mode or sth ( I don't remember it clearly. just power + vol down or up. just try it)
4. Smart switch will recognize your phone. Choose a firmware to download. then wait
5. Enjoy stock firmware
Use kies3 reinstall drivers, then use emergency recovery in kies to reinstall your current firmware or opt to update to latest or most recent release or version then follow kies instructions
rooted s5 smg900r4
Hello everyone
I have found a way to fix dm-verity and DRK issues and it works like official, meaning no errors in stock recovery and OTA works with Official firmware, the problem is related to corrupted/deleted 3 files on /efs partition. I have tested it on SM-N910C so I guess it works on other Exynos variants, perhaps even on snapdragon if the partition layout is similar? Kies won't restore DRK or dm-verity check because it doesn't write to EFS. I can fix yours if someone is interested via Team Viewer, you will need the following:
1. PM contact me for Skype ID
2. Stock rom, rooted (any root method)
3. Adb debugging enabled and drivers installed (Kies or SmartSwitch)
After repair you can enter your stock recovery and confirm there is no DRK/dm-verity red letters error.
Regards,
magix01
please guide us the proceedure here .. i have a phone with same problem & i have to update it to MM ...
dork997 said:
If you format everything in advance format in twrp and then flash stock firmware this message will go away.
Click to expand...
Click to collapse
Mine still says fail. but it also says "need to check drk first" could anyone possibly help me im stuck.the phone loads up and everything. but when i try to root or anything or flash any other firmware than n910pvpu5dqi5 it fails about 4 seconds in to flashing on odin. ive downloaded every possible firmware specific to the SM-N910P but only one worked.
im a big noob with the note 4 this is my first luckily its not my daily phone yet. im very familiar with the note 3 n900t but im finding they are very different. any advice would be appreciated!
Sir, please reply
When i unlocked my bootloader on my redmi phone this warning comes, but after clicking power button it will successfully boot to system but i m confused did i flash any rom in it, is it safe or not
Manish_k said:
Sir, please reply
When i unlocked my bootloader on my redmi phone this warning comes, but after clicking power button it will successfully boot to system but i m confused did i flash any rom in it, is it safe or not
Click to expand...
Click to collapse
If you just unlocked your bootloader and thats it, your rom should still be the stock one.

[HELP] Note 4 boot loop after installing TWRP recovery (possibly soft brick?)

I have Note 4 model N910H firmware 5.1.1 and I rooted it using chainfire method. I checked using root checker and it says my phone was rooted properly. So I install TWRP latest recovery using flashify. The phone rebooted to recovery mode fine but it says that my phone not rooted so I'm confused and I let TWRP rooted it again. After that I reboot to system and I can't enter it instead it was stuck looping samsung and android logo.
So, what can I do? I can enter TWRP recovery and download mode. I know I can flash it to stock 5.1.1 but I dont know what version to use from SamMobile (XID/XSE, I'm from Indonesia) and there's different PDA/CSC version. So if I just pick one of them and flash it to my phone will it be okay? I want to avoid flashing to be honest because the rom size is so big so is there's a way to fix it without flashing?
Any help would be appreciated. Thank you.

Categories

Resources