Hello, this is my first post.
Introduction
So today & yesterday I tried rooting my stock ROM, Android M 6.0.1 G900F Galaxy S5 but I've had a few problems with it.
Details
I think I've done everything correctly to try to flash TWRP onto my phone:
Downloading the lastest version of TWRP-klte (I've used 3.0.2-1 & 3.0.2-2)
Unticking 'Auto-Reboot' in Odin (I've used Odin3_v3.09 & Odin3_v3.10.6)
Pull out the battery to get out of download mode, etc.
But nothing seems to work. When I go into download mode it tells me:
Code:
[B][COLOR="Red"]ODIN MODE[/COLOR]
[COLOR="Black"]PRODUCT NAME: SM-G900F
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x0[/COLOR]
[COLOR="DimGray"]QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1[/COLOR]
[COLOR="Blue"]SECURE DOWNLOAD: ENABLE[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
[/B]
To my understanding I find it weird that it says my Current Binary and my System Status say 'Custom' but my KNOX is still 0x0.
Now, of course before I tried to flash TWRP it said I my Current Binary and my System Status said 'Official'.
What I Think Is The Problem
Correct me if I'm wrong but I think the problem is that UDC START part in the download mode.
I've read online that some people get that when their phone is in a bootloop but I have no problem with my phone.
Conclusion
In conclusion I think that the problem may be resolved by factory restoring my phone, but if you have any other ideas, please reply to this thread.
Thanks.
None of those steps would root your phone though
TWRP is a custom recovery, once you've flashed that, you need to boot into TWRP, and flash SuperSU 2.xx beta (xx = whichever is the latest version)
Then you can reboot into Android and should be rooted
*Detection* said:
None of those steps would root your phone though
TWRP is a custom recovery, once you've flashed that, you need to boot into TWRP, and flash SuperSU 2.xx beta (xx = whichever is the latest version)
Then you can reboot into Android and should be rooted
Click to expand...
Click to collapse
The problem is that it won't let me flash TWRP. I have SuperSU on my device ready to be flashed but I need to get TWRP working.
Ah I see, and you are booting straight into recovery after replacing the battery?
1. Disable auto reboot & Flash TWRP
2. Disconnect USB & Pull battery to power off once flash is complete
3. Replace battery and boot immediately into TWRP
TWRP 3.0.2.0 Klte is the version I use
*Detection* said:
Ah I see, and you are booting straight into recovery after replacing the battery?
1. Disable auto reboot & Flash TWRP
2. Disconnect USB & Pull battery to power off once flash is complete
3. Replace battery and boot immediately into TWRP
TWRP 3.0.2.0 Klte is the version I use
Click to expand...
Click to collapse
Yes I booted once into recovery straight after flashing and it never worked.
Now I have to use ADB because it's a bit finicky and it wont always boot into recovery by doing Volume Up + Power.
I'll try using 3.0.2.0 and see what happens.
Edit: I just tried with Odin 3.09 & TWRP klte 3.0.2.0, still no luck. Also couldn't boot into recovery with buttons, had to use Volume Up + Power.
-removed
Related
Phone model: Rooted Galaxy S4 i9505 running stock 4.4.2, no CWM installed.
Here's the problem: I changed a few lines of build.prop and rebooted the phone. After the logo, an endless black screen looking at me.
The first thing I tried to do was flashing a custom rom, but it looks like it can't be done via stock recovery.
I installed CWM, but it's not the default and since my phone is soft-bricked I can't use an app to make it default.
Later on, I tried using Odin to reinstall the stock rom. It fails one second after it starts.
Tried using ADB PULL to get the build.prop and correct it, but it gives me "error: closed"
I tried following ibanezbass guide. the "adb shell" command won't work.
Tried flashing the rom through stock recovery. "E: Signature verification failed"
Other things I tried on stock recovery:
>Factory reset/wipe data
>Wipe cache
The lines I edited on build.prop were "ro.product.name=jfltexx" and "ro.product.device=jflte". I used Root Explorer to do so, and have made a backup (but can't access it because my phone won't turn on)
OH, and when Odin failed there was a message on the top left corner of the screen:
"ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMc BURST MODE enabled
START [224, 1440]
SW RV. CHECK FAIL : fused : 4 , Binary : 3"
You can do a few things depending on what you want.
1. Flash a custom recovery (TWRP or Philz touch) with Odin. I'm not sure if CWM is still updated.
2. Do a wipe from the recovery
3. Flash the custom rom you want.
or
1. Flash the stock rom you want with Odin.
2. See if it boots, if not step 3.
3. Boot into the stock recovery and do a data/cache wipe.
Almost all Odin errors can be resolved by the following:
- Different usb port
- Different usb cable
- Reinstall drivers
- Make sure Kies is not running in the background.
- Make sure to flash a 4.4.2 stock rom. You can't use older roms.
ps in your opening post you are mixing things up. Follow these steps and you will be fine.
I have SAMSUNG SM-G900F with firmware : FXX1BOJ1 and CSC: BOH1
I tried to root this device using CF-Auto-Root-klte-kltexx-smg900f.tar.md5 . After succseffuly flashed with ODIN, the phone din not boot anymore. No matter if I enter in recovery or normal boot on screen appear :
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING...
Set Warranty bit : recovery
Then I flashed a custom recovery in order to try to revive the phone and apply root as well. I flashed CWM : philz_touch_6.26.2-klte.tar.md5 in idea to use it and install SUPERSU. However after succesfullt flashed it with ODIN,the phone boot fine but when I enter recovery the normal ANDROID recvery was present instead of CWM.
In download mode following informations appear now on screen :
ODIN MODE (in red)
Product name : SM-G900F
Current Binary : Custom
System Status : Custom
Reactivation Lock(KK) : OFF
KNOW WARANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB) (in gray)
SWREV: S1, T1, R1, A1, P1 (in gray)
SECURE DOWNLOAD (ENABLE) (in blue)
UDC START (in red)
I understand the knox is deactivatedand there and is no known method yet to clear the bit, but I can live with it. However I don't understand what that (4) mean. It was from the beginning (when I first enter in download mode) However how to root it ?
Thank You
Flash twrp, boot in recovery, Flash supersu.zip
tapatalked
I tried to flash CWM but seem it was not flashed, because when I enter in recovery instead of CWM It was executed standard recovery. Where can I find twrp for Galaxy S5 (G900F) ?
Hey there, I got my S5 a week ago and had some flashing problems as well (G900F on official lollipop update). Got it after some research though, follow these steps. Also, I see you're more into CWM, but I recommend TWRP, that's what I'll be using below. Note that this method does trip Knox.
1. Not necessary, but recommended - If you can boot, go to the play store and download "Castro". Castro is a good looking app that shows you all the information about your phone, hardware and software. So you can see if you have root status, the system info, bootloader status etc. etc. This is good if you flash something you can always see how your phone was originally. Plus the root checker will be handy later on. You can export all this information to a PDF or DOC in the app using the three dot menu, then just copy this information online or on your sd card for safe keeping.
1. Boot into download mode.
2. Use Odin (you can use the one attached IF you want) and flash the stock firmware of your device to fix any problems the flashing you did might have caused, this will restore original recovery, boot and system.
2. After flashing the firmware, boot the phone into recovery to check if stock recovery is there, then boot normally to make sure the system is working fine.
3. Download the attached TWRP, it's a .tar so you can flash it in odin. Boot the phone in recovery, there should be some blue, red, and yellow writing in the top left, that's fine, it will go away within 5 seconds or so and then jump into TWRP.
4. Get the SuperSU zip attached below on your phone (if it isn't already, while in twrp you should have access to send files to your phone through usb), in TWRP, select install, then browse to where the file is. Choose it and swipe to flash. When done, reboot.
5. Look for the SuperSU app icon in your app drawer. If it's there, then that's good. Go to the playstore, search for SuperSU and select update.
6. Open SuperSU, it should be working fine.
7. Use Castro or any other root checker to test if root is working, it should be.
Just to add to the above instructions.....
Before you begin the TWRP/superSU flash process, go to .....
Settings>>Security
and disable Reactivation Lock......
Leaving it enabled *has* been known to cause problems during rooting. So whether you start by flashing full stock to your device (or not) check it.......
Edit......oh and after flashing TWRP, DO NOT let odin reboot the device......remove the battery to prevent this if you have to, make sure you boot into the newly installed TWRP and install the superSU zip BEFORE you boot up normally.....
http://i.imgur.com/rVnFwJM.jpg
spon901 said:
I tried to flash CWM but seem it was not flashed, because when I enter in recovery instead of CWM It was executed standard recovery. Where can I find twrp for Galaxy S5 (G900F) ?
Click to expand...
Click to collapse
Welcome to internet lol forum is clearly and easy for all user even me the illiterate ( you have search in tread is useful )
Thank You very much. The issue was that after flashing I was boot normally first (check auto reboot option in odin). Now after flashing (having auto reboot in odin not checked) , I power off the phone by pressing power button for few seconds, and then first time boot in recovery mode and install SUPER SU. Then boot normally and everything was fine , and I have root of course!!!
Thank again for help.
Hello guys.
I have successfully rooted my Samsung Galaxy S5 SM-G900F. (Checked root using root checker, and SuperSU)
I want to install a custom ROM and a custom recovery.
I followed dozens of guides online (I have done this before) to install a custom recovery.
However without success.
(Using Windows 10)
I have the USB drivers, I have tried the battery pull out trick when it doesn't boot into recovery after odin flash. Nothing seams to work. Every time it just goes into the default samsung recovery no matter what I do.
I have tried several recovery images without success. (using a USB 2 cable as well)
I have also tried different Odin versions (3.09 and 3.10.7).
I have USB Debugging enabled.
Tried different combinations of everything and nothing worked for my phone.
In recovery this is my information in the top:
Code:
ODIN MODE
PRODUCT NAME: SM-G900F
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, R1, A1, P1
UDC START
Does anyone have any idea what I can do about this?
When you say you tried the pull battery trick, how did you do it?
Did you uncheck the "Auto Reboot" option in ODIN first?
Did you allow the flash to complete, disconnect USB, and pull the battery before doing anything else?
Then try to boot directly into recovery instead of powering on normally?
*Detection* said:
When you say you tried the pull battery trick, how did you do it?
Did you uncheck the "Auto Reboot" option in ODIN first?
Did you allow the flash to complete, disconnect USB, and pull the battery before doing anything else?
Then try to boot directly into recovery instead of powering on normally?
Click to expand...
Click to collapse
Yes, I did exactly that and when I tried going into recovery after pulling the battery it would go into the default recovery
soit48 said:
Yes, I did exactly that and when I tried going into recovery after pulling the battery it would go into the default recovery
Click to expand...
Click to collapse
Make sure you're using TWRP 2.8.7.0 specifically that version
*Detection* said:
Make sure you're using TWRP 2.8.7.0 specifically that version
Click to expand...
Click to collapse
Am using exactly that version.
Odin 3.09
TWRP 2.8.7.0 klte
Always use the latest ODIN 3.10.7, and run as administrator (Right click > run as Administrator)
Leave TWRP as .TAR - don't unzip
If it still fails, try using this instead
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en
Requires busybox first
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
1. win 10 sux whn drivers are in question
2. When instaled drivers did you let windows 10 to obtain them over internet? Windows always tries to chek for drivers even after instaled vie exe file - click skip obtaining from win update
3. Did you used usb 2.0 port on your machine?
4. Did you checked alow mock location and debug on your phone?
5. On some sams phones i had to check unknown sources and uncheck verify aps via usb (why i dnt knw but i menaged to get root after)
6. I always put odin and recov file in root of partition ie c://odin or d://odin
Sent from my SM-G900F using Tapatalk
Hi all,
Please bear with me, I'm in way over my head here and don't understand most of what I've done. I was experimenting when I probably shouldn't have been.
So, I installed DarkLord's Note 7 kernel and rom. I found it to be quite buggy and am now wanting to wipe my phone and install Phronesis-N9005-N7-v6.0.
Problem is, when trying to boot into TWRP, I'm met with the the following:
ODIN MODE
Product name: SM-N9005
Current binary: Custom
System status: Official
Reactivation lock(kk): Off
Knox Kernel lock: 0x0
Knox warranty void: 0x1
Qualcomm secureboot: Enable (csb)
Rp swrev: S2, T2, R2, A3, P3
Write protection: Enable
UDC start
Downloading...
Do not turn off target
I've had it on for hours and it didn't do anything.
I managed to reboot it and it ran as it did before, in Darklords rom.
I read I have to install the official firmware and install it via Odin but I can't find anything about my device. On the back of it, it says:
SM N9005
FCC ID - A3LSMN9005
SNN - N9005GSMH
When I enter it into sammobile, nothing comes up.
Have I got this wrong? Should I be looking for something else?
You are booting to download mode not recovery .
Boot to recovery TWRP
#N9005 model firmware are on sammobile etc.
https://forum.xda-developers.com/galaxy-note-3/general/samsung-galaxy-note-3-sticky-roll-t3237249
Booting into recovery via TWRP manager just results in the same Odin screen for me
As for the firmware - I'm not really sure which region I should pick out of those. I just thought this was an international model, but then I downloaded an app called Phone INFO and it tells me it's Vietnam. Could this be because of the rom already on there? It does also say it's a Note 7, so I'm assuming it's incorrect.
TWRP manager
DO NOT USE just boot to recovery via the vol up home and power buttons as normal .
Copy Phronesis to ext sd card and flash as per instructions .
You have N9005 Pick your area /network where you are .
Phone Info can only go by what's on your phone and you flashed DarkLord's Note 7 firmware .
Booting via manager was a last resort. I was trying the usual way and it also resulting in the same thing.
Boot to download/ Odin mode flash stock rom .
Thanks JJEgan, I figured out how to use Odin3 and Odin mode, then install Phronesis. All is good now
Okay, so I have hard bricked my Note 3. I know, I know...months back my phone died out and I got a new phone on MetroPCS. So I didn't really try to do anything with it. It would load to the Verizon screen and go no further. Well I dropped my new MPCS phone in some (a lot of) water and after dismantling and cleaning it, its dead and buried. So, for now I was going to see if I could reflash stock software for my Note 3 and enable the LTE bands for Tmobile. Blah blah, long story short. I flashed TWRP and it worked, I went to reboot it after a wipe and I think I deleted everything. I used the OF1 unbrick img to see what would happen because there was no PL1 linked, and I get:
Boot Recovery Mode
Check boot partitions
Copy from T-Flash
Boot Recovery
Write 163840 Sectors
Flash Write Failure
ddi : mmc_read failed
Odin Mode
Product Name: SM-N900V
Current Binary: Samsung Official
System Status: Custom
Reactivation Lock: Off
Qualcomm Secureboot: Enable (CSB)
AP SWREV: S1, T1, A1, A4, P1
Secure Download: Enable
UDC Start
So, a sign of life...however I can't get into download mode. I think I need a PL1 unbrick image to get it there. Any takers on making me one? I've read the Unbrick hard brick forum and the farthest anyone has gone was to OF1 so I didn't know if anyone was running a PL1 version that could make the image for me. Please let me know.
Thanks In Advance
huskiesmike said:
Okay, so I have hard bricked my Note 3.
Thanks In Advance
Click to expand...
Click to collapse
Is your boot loader unlocked? If not you must use Odin to flash full stock ROM and recovery. The N900V will not boot with a custom recovery unless the boot loader is unlocked. You need a working, rooted phone with a CID # that starts with 15 in order to unlock the boot loader.
Bootloader is unlocked and it was rooted, obviously not now but I had no issue running TWRP before.
huskiesmike said:
Bootloader is unlocked and it was rooted, obviously not now but I had no issue running TWRP before.
Click to expand...
Click to collapse
Did the unbrick image replace the boot loader? I have not used/need the unbrick image and I'm not sure what is in it. If boot loader is unlocked and TWRP is working you should be able to flash any n900v ROM to get it working. I'll look at the unbrick image, if I can find it.
Well, it had TWRP. I installed TWRP with the intention of flashing a new ROM to it because it was soft-bricked and stuck on the VZW flash screen. When I rebooted it didn't respond. The only response I have now is the Recovery boot mode with the OF1 unbrick.img and it won't go into download mode or recovery. No response at all without the SD card in it.
Thanks