[Q] Soft-bricked device after editing build.prop (NO CWM) - Galaxy S 4 Q&A, Help & Troubleshooting

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.

Related

[Q] Possible Soft Brick? S4 AT&T

Hey guys,
I decided that I wanted to root my phone for a custom rom. I used towelroot and odin to root my phone. It rooted successfully.
Heres where the problem is:
I installed twrp, and scrolled through menu options so I could install a Recovery. However, whenever I tried to install the rom, it would always take me to the default boot menu, therefore i was unable to get a rom. Long story short, twrp has caused my download mode menu to enable write protection. I went onto supersu, and removed my root. I just want to go back to factory/ stock rom and remove root. I downloaded samsungs firmware from their site and tried using odin, but this gives me a fail and states that "complete (write) operation failed".
My phone displays:
SGH-I337
Samsung Official
Custom system status
Knox kernal lock: 0x0
Knox Warranty viod: 0x0
CSB-config-lsb 0x30
write protection: enable
eMMC burst mode enable
I have tried to flash it back to stock so many times. Now I am getting a msg that says "firmware upgrade encountered an issue" -kies does not help remove this.
-I am using the original cable
-I can only boot into recovery and download mode.
-My main goal is to go back to stock.
Akluu said:
Hey guys,
I decided that I wanted to root my phone for a custom rom. I used towelroot and odin to root my phone. It rooted successfully.
Heres where the problem is:
I installed twrp, and scrolled through menu options so I could install a Recovery. However, whenever I tried to install the rom, it would always take me to the default boot menu, therefore i was unable to get a rom. Long story short, twrp has caused my download mode menu to enable write protection. I went onto supersu, and removed my root. I just want to go back to factory/ stock rom and remove root. I downloaded samsungs firmware from their site and tried using odin, but this gives me a fail and states that "complete (write) operation failed".
My phone displays:
SGH-I337
Samsung Official
Custom system status
Knox kernal lock: 0x0
Knox Warranty viod: 0x0
CSB-config-lsb 0x30
write protection: enable
eMMC burst mode enable
I have tried to flash it back to stock so many times. Now I am getting a msg that says "firmware upgrade encountered an issue" -kies does not help remove this.
-I am using the original cable
-I can only boot into recovery and download mode.
-My main goal is to go back to stock.
Click to expand...
Click to collapse
What firmware version are you on? You're probably going to have to use odin to get your phone working correctly again.
Sent from my Nexus 5 using XDA Free mobile app
Akluu said:
Hey guys,
I decided that I wanted to root my phone for a custom rom. I used towelroot and odin to root my phone. It rooted successfully.
Heres where the problem is:
I installed twrp, and scrolled through menu options so I could install a Recovery. However, whenever I tried to install the rom, it would always take me to the default boot menu, therefore i was unable to get a rom. Long story short, twrp has caused my download mode menu to enable write protection. I went onto supersu, and removed my root. I just want to go back to factory/ stock rom and remove root. I downloaded samsungs firmware from their site and tried using odin, but this gives me a fail and states that "complete (write) operation failed".
My phone displays:
SGH-I337
Samsung Official
Custom system status
Knox kernal lock: 0x0
Knox Warranty viod: 0x0
CSB-config-lsb 0x30
write protection: enable
eMMC burst mode enable
I have tried to flash it back to stock so many times. Now I am getting a msg that says "firmware upgrade encountered an issue" -kies does not help remove this.
-I am using the original cable
-I can only boot into recovery and download mode.
-My main goal is to go back to stock.
Click to expand...
Click to collapse
What firmware are you on?
If you upgraded past 4.4.2 mdlish then you have to safestrap.
Sounds like a soft brick to me, you have to Odin back and try again.
Make sure you Odin back to what you have/had or your stuck forever with safestrap.
If you don't know how to Odin read the giant back to stock guide.

Unable to gain root on SAMSUNG G900F

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.

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

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

My i9505 getting Bootlop

Dear XDA User,
I get bootloop after flashing stock firmware via ODIN, from Thread [GUIDE] Unroot/Unbrick, Flash stock Firmware i9505 I've try many way, but my i9505 still bootlop after Samsung Logo and vibrate.
I can't enter recovery mode, but when I enter Downloading Mode, here the status:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
I've try ODIN with PIT File to, but still get bootloop, Please help me, this is my only cellular phone.
* Sorry for my bad English
Did you do a factory reset in recovery?
GDReaper said:
Did you do a factory reset in recovery?
Click to expand...
Click to collapse
I can't enter Recovery mode, it's always bootloop, after flash custom recovery like TWRP, it's still same, just Downloading mode that I can enter...
Open Odin, uncheck everything except f reset time, flash rom, when you see the reset in the status window, remove USB cable from the phone, remove battery, replace battery, use buttons to boot into recovery (power, home, volume up) wipe, and reboot.

Categories

Resources