Database Users

[Q] Soft-bricked device after editing build.prop (NO CWM)

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.

SM-G900F (XXU1BOJ1) rooting failed -> recovery is not seandroid...

Hi,
I try to root my (S5 SM-G900F XXU1BOJ1), but id did not work...
Here are the Steps I did:
1. Starting Odin 3.10.7 as Admin (Win10); Autoreboot on, F. Reset Time on; rest off.
2. Click on AP, choose File "CF-Auto-Root-klte-kltedx-smg900f.tar.md5" taken from here (for 5.0)
3. Put Galaxy s5 in download mode (switch off phone then hold VolDown+Home+Power)
4. Connect S5 with USB to PC and hit "Start" on Odin; Odin quits with: success: 1 / failed: 0
Phone rebooted automaticaly, but halt with:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
Battery out & in, booting in recovery (VolUP+Home+PWR) result allways in Set Warranty Bit: recovery;
Battery out & in, booting in download mode still working, so I flashed "twrp-2.8.7.0-klte.img.tar" with Odin to get my Phone work...
What is wrong? How can I get my S5 rooted?
Thank you & best wishes,
cya

Try KLTExx and not dx
cyaneo said:
Hi,
I try to root my (S5 SM-G900F XXU1BOJ1), but id did not work...
Here are the Steps I did:
1. Starting Odin 3.10.7 as Admin (Win10); Autoreboot on, F. Reset Time on; rest off.
2. Click on AP, choose File "CF-Auto-Root-klte-kltedx-smg900f.tar.md5" taken from here (for 5.0)
3. Put Galaxy s5 in download mode (switch off phone then hold VolDown+Home+Power)
4. Connect S5 with USB to PC and hit "Start" on Odin; Odin quits with: success: 1 / failed: 0
Phone rebooted automaticaly, but halt with:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
Battery out & in, booting in recovery (VolUP+Home+PWR) result allways in Set Warranty Bit: recovery;
Battery out & in, booting in download mode still working, so I flashed "twrp-2.8.7.0-klte.img.tar" with Odin to get my Phone work...
What is wrong? How can I get my S5 rooted?
Thank you & best wishes,
cya
Click to expand...
Click to collapse

androidtweaker1 said:
Try KLTExx and not dx
Click to expand...
Click to collapse
OK, flashed with "CF-Auto-Root-klte-kltexx-smg900f.tar.md5" taken from this Post but same here, the only different is the screen turns black and no response (waiting 20 min.).
Maybe the files is for 4.4 and not for 5.0; any idea where get kltexx for 5.0?
Also tried it with "Auto Reboot" off in Odin and rebooted manualy.

Hmm, I looked at the Chainfire Site and found both files listet for my G900F, but none of them is for the actual Stock ROM release ( G900FXXU1BOJ1).

Now I habe a rooted S5
1. copy "UPDATE-SuperSU-v2.46.zip" to phone internal storage
2. flash the "twrp-2.8.7.0-klte.img.tar" with Odin (with "Auto Reboot" OFF)
3. After battery out and in, boot into recovery (VolUP+Home+PWR)
4. In recovery with TWRP go to install zip, choose "UPDATE-SuperSU-v2.46.zip".
Reboot Phone and tested with a root Checker from Playstore and -> Congratulations! Root access is properly installed on this device!

cyaneo said:
Now I habe a rooted S5
1. copy download.chainfire.eu/696/SuperSU"]UPDATE-SuperSU-v2.46.zip to phone internal storage
2. flash the dl.twrp.me/klte/"]twrp-2.8.7.0-klte.img.tar with Odin (with "Auto Reboot" OFF)
3. After battery out and in, boot into recovery (VolUP+Home+PWR)
4. In recovery with TWRP go to install zip, choose "UPDATE-SuperSU-v2.46.zip".
Reboot Phone and tested with a root Checker from Playstore and -> Congratulations! Root access is properly installed on this device!
Click to expand...
Click to collapse
Thanks, I had the same problem and thanks to this method it workes just fine.

Does this mean you don't need CF-Auto-Root-klte-kltexx-smg900f.tar.md5 if you are using the above method?

As long as you have a custom recovery and use the flashable SuperSU.zip you don't need cf auto root. I think it's a safer method personally, as I've seen a few people on here have issues using cf auto root. I used the recovery + SuperSU method myself without problem on the G900F

Rooted Galaxy S5 Custom Recovery Install Issues (SM-G900F)

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

Purchased a Note3, stuck on Custom ROM boot screen

Haven't rooted a phone in a little but am generally pretty savvy. I can get into recovery, tried restoring factory settings and clearing cache, same result unfortunately. I tried running an Odin .exe I found in another thread but it just opens and closes.. :/
When in download mode, product name: SMN900V, System Status: Custom
Knox Kernel Lock: 0x0, Knox Warranty Void: 0x0, Qualcomm Secureboot: Enable (CSB), RP SWREV: S1, T1, A3, P1
Write Protection: Enable, UDC START
Any help anyone can offer or provide a working rom or flashable file to get me booted would be most appreciated! No idea what ROM or Android version he put on this thing (purchased from Swappa).
TIA!!

Re download Odin and tar file. Have you gotten Odin to flash anything or does it fail or do you mean Odin itself isn't working? It sounds like you didn't extract Odin files and just opened it.
Sent from my SM-N900V using XDA-Developers mobile app

I was able to flash a Verizon firmware (thru Odin) and get it booted but I don't have root (seller claimed he did beforehand). Sounds like I should start with unlocking bootloader or root first? Thanks for the response man, I appreciate all the help I can get!
Sent from my SM-N900V using XDA-Developers mobile app

Start with the root first. Can't unlock the bootloader without it.

Awesome is there a one click by chance or is it complicated?
Sent from my SM-N900V using XDA-Developers mobile app

DNak206 said:
Awesome is there a one click by chance or is it complicated?
Sent from my SM-N900V using XDA-Developers mobile app
Click to expand...
Click to collapse
I had installed jasmine rom and ended up having problems with certain apps not working due to the modified framework he was using. I used odin to flash the new OB6 & pit (returns to locked boot loader with stock lollipop rom). I took the OTA to OF1, then used the yemen 1 click root. At this point the only issue I have is trying to get a customer bootloader installed. The TWRP version 3.0.2-0 just leaves me stuck at boot loader and I had to reinstall the pit file to get phone to boot again. Hope that helps you. I like stock rom but am trying to get native tether to work, without customer bootloader I can't flash anything.

I just got note3 Verizon, I rooted it couple days ago. I am on tmobile, so far everything works with stock lollipop except hotspot. Contemplating on unlocking boot loader at the moment.

santas16 said:
I had installed jasmine rom and ended up having problems with certain apps not working due to the modified framework he was using. I used odin to flash the new OB6 & pit (returns to locked boot loader with stock lollipop rom). I took the OTA to OF1, then used the yemen 1 click root. At this point the only issue I have is trying to get a customer bootloader installed. The TWRP version 3.0.2-0 just leaves me stuck at boot loader and I had to reinstall the pit file to get phone to boot again. Hope that helps you. I like stock rom but am trying to get native tether to work, without customer bootloader I can't flash anything.
Click to expand...
Click to collapse
[threadjack]
I was fooling around with flashing custom recoveries from within a rooted ROM today, and found something useful - when I "got stuck at bootloader" because TWRP failed to boot. So long as the main ROM is still bootable and is rooted, you can clear the "always tries to boot the recovery" behavior the following way:
1) Pull the battery (and plug back in after a couple seconds)
2) Vol-Down+Home+Power (as if you are trying to enter Download mode)
3) When you get the Custom ROM Warning menu, choose Cancel (not Continue)
This clears the BCB (Boot Communication Block) in eMMC and the phone will thereafter attempt to boot normally, rather than continuing to try to boot the recovery again. The sequence #2-3 does not work if you don't start by pulling the battery - if you soft-boot by holding the Power button down (~ 15 seconds), the phone will always attempt to boot the (broken) recovery, whether you enter Odin mode or Cancel.
Well, that's the way my phone behaves at this moment. (I am using a older bootloader however - it is always possible that this is a bootloader behavior that changed in later versions). Anyway - if you get "stuck" again, this could save you some labor, rather than having to go back to Odin, flash everything, and re-root.
Having said that, I'm not sure what you would use as alternative custom recovery. You could do something like pull just the stock kernel from the OF1 and re-pack it into your own customization of TWRP to see if that changes anything. Thing is, I could have sworn I saw a report from someone who said they are using TWRP 3.0.2 with the OF1 bootloader successfully.
Are you using "twrp-3.0.2-0-hlte.img" ?
[/threadjack]

bftb0 said:
[threadjack]
I was fooling around with flashing custom recoveries from within a rooted ROM today, and found something useful - when I "got stuck at bootloader" because TWRP failed to boot. So long as the main ROM is still bootable and is rooted, you can clear the "always tries to boot the recovery" behavior the following way:
1) Pull the battery (and plug back in after a couple seconds)
2) Vol-Down+Home+Power (as if you are trying to enter Download mode)
3) When you get the Custom ROM Warning menu, choose Cancel (not Continue)
This clears the BCB (Boot Communication Block) in eMMC and the phone will thereafter attempt to boot normally, rather than continuing to try to boot the recovery again. The sequence #2-3 does not work if you don't start by pulling the battery - if you soft-boot by holding the Power button down (~ 15 seconds), the phone will always attempt to boot the (broken) recovery, whether you enter Odin mode or Cancel.
Well, that's the way my phone behaves at this moment. (I am using a older bootloader however - it is always possible that this is a bootloader behavior that changed in later versions). Anyway - if you get "stuck" again, this could save you some labor, rather than having to go back to Odin, flash everything, and re-root.
Having said that, I'm not sure what you would use as alternative custom recovery. You could do something like pull just the stock kernel from the OF1 and re-pack it into your own customization of TWRP to see if that changes anything. Thing is, I could have sworn I saw a report from someone who said they are using TWRP 3.0.2 with the OF1 bootloader successfully.
Are you using "twrp-3.0.2-0-hlte.img" ?
[/threadjack]
Click to expand...
Click to collapse
I get a different kind of stuck, I'm not going to try it again but it said the phone has detected software that is not authorized or something along those lines. I cannot just pull battery as it just repeats over and over. I actually do not ever get to enter any recoveries at all, it automatically detects that's it's not the original bootloader and tells me such. anyways, I had to reload the image and take the OF1 update again... all is working back to normal.
I had used "twrp-3.0.2-0-hltevzw-4.4.img" from the twrp manager app, flashed via app, restarted to end up having the error message immediately on bootup of device... no recoveries or anything could load. I would have to assume the 4.4 means kk version and that's why it didn't work?

santas16 said:
I had installed jasmine rom and ended up having problems with certain apps not working due to the modified framework he was using. I used odin to flash the new OB6 & pit (returns to locked boot loader with stock lollipop rom). I took the OTA to OF1, then used the yemen 1 click root. At this point the only issue I have is trying to get a customer bootloader installed. The TWRP version 3.0.2-0 just leaves me stuck at boot loader and I had to reinstall the pit file to get phone to boot again. Hope that helps you. I like stock rom but am trying to get native tether to work, without customer bootloader I can't flash anything.
Click to expand...
Click to collapse
Hmmm. Maybe I was reading something into your post that wasn't there. I assumed that you had also performed the retail-to-dev edition CID change "unlock" after you gained root on OF1. Is that wrong - did you simply flash a recovery after getting root?
In my case I flashed a non-bootable TWRP (dd of=/dev/block/mmcblk0p15...) onto the recovery; doing this tripped my Knox Warranty flag, but otherwise the bootloader didn't complain about unauthorized software. After figuring out how to clear the "always try to boot the recovery" near-disaster, I used a 2.8.x TWRP series custom recovery successfully (In addition to flashing the stock recovery back into place and verifying that it still worked) But this is on a truly ancient bootloader (MJ7), so maybe all bets are off about expecting later bootloaders to behave in this same fashion.
Still, the point of developer edition functionality is to allow for custom boot (& recovery) partitions, so it's surprising that you were getting warnings like that if your phone was in developer mode.

@santas16
Hey. For what it's worth, I was able to boot twrp-3.0.2-hltevzw-4.3.img from my SM-N900V ... with a MJ7 bootloader!
But not the hltevzw-4.4.img. (That could be due to the old bootloader however, I don't know for sure)
Note that my phone has the retail-to-deved CID change that puts it into developer mode. (I used @donc113 's executable with adb)
This allows unsigned boot or recovery partitions to proceed to load/execute, but it will burn your Knox Warranty flag (which is unimportant to me at this point). I think that is actually the expected behavior when the phone is in developer mode.
I've been flashing all sorts of recoveries without worrying whether they will boot or not (as I know I can get back into the rooted ROM to flash into place a working version)**
Probably the best advice about not getting stuck in the "continually tries to re-enter the recovery" mode is to NOT use "reboot to recovery" methods (in Safestrap, other recoveries, or root-privileged Apps (flashfire?)), but to always shut the phone down to a powered-off state, and just use the three-button startup method (Vol-Up+Home+Power) to enter the recovery. That way nothing is being written into the BCB that will make it want to loop back to a failed recovery.
cheers
** what was interesting is that I could successfully boot any of the MI9, MJ7, MJE stock recoveries on my MJ7 phone. Moreover, the bootloader would not pop up the yellow "Set Warranty Bit: recovery" message right before they loaded. The NC4 recovery would not boot to a menu, but it also did not present a "Set Warranty Bit: recovery" message. I presume this means that the boot layer is not looking for exact version matches, but rather just checking that the Samsung signing operation is correct. I could not boot OB6 or OF1 recoveries; somewhat curiously though, these attempts *would* throw the "Set Warranty Bit: recovery" error message even though they are validly signed Samsung recoveries. I don't know if it is a reasonable hypothesis, but I think that indicates that Samsung may have altered the details of their signing verification method someplace between NC4 and OB6 so that earlier bootloaders fail this check. Ugh. As if there weren't enough details already.

If your bootloader is still 0F1 then download flashify from Google and hit recovery and tap top twrp.. Your all set...sounds like a lot of craziness for nothing.
Sent from my SM-N900V using XDA-Developers mobile app

santas16 said:
I get a different kind of stuck, I'm not going to try it again but it said the phone has detected software that is not authorized or something along those lines. I cannot just pull battery as it just repeats over and over. I actually do not ever get to enter any recoveries at all, it automatically detects that's it's not the original bootloader and tells me such. anyways, I had to reload the image and take the OF1 update again... all is working back to normal.
I had used "twrp-3.0.2-0-hltevzw-4.4.img" from the twrp manager app, flashed via app, restarted to end up having the error message immediately on bootup of device... no recoveries or anything could load. I would have to assume the 4.4 means kk version and that's why it didn't work?
Click to expand...
Click to collapse
If you get the " not authorized or something along those lines" error, it means you're not unlocked.

Need Help With Rooting G900F 6.0.1

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