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.
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.
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.
Got a FreedomPOP SPH-L720, but it had issues with power cycling on boot.
During this, I activated TWRP 2.7.1.0 and "fixed permissions" and "factory reset"
Then made the mistake of "Formatting" after which the phone would reach the splash screen and go no further.
Attempted to resolve with http://forum.xda-developers.com/showthread.php?t=2486134
Wound up with:
ODIN MODE
PRODUCT NAME: SPH-L720
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 8X8
KNOX WARRANTY VOID: 8X1
CSB-CONFIG-LSB: 8X30
SECURE DOWNLOAD: ENABLE
WRITE PROTECTION: Enable
eMNC BURST MODE: enabled
With the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
However, all versions of Kies I tried were unable to connect.
Also, one of the message outputs upon entering TWRP was "SEANDROID RECOVERY NOT ENABLED"
You probably need to find the stock rom for your carrier and Odin that.
Using katodragon's OK3 ROM, and everything's fine now
Hallo,
I got a Galaxy S4 (GT-I9505) from a friend of mine. He did'nt know, what happens. The phone became very hot, made vibration-Noise and was not able to start it anymor.
I also tried to start the phone, but it got a boot-Loop.
So I thought to reflash the phone.
I am able to start the Download-Menü (Vol - + Power + HOME). The Recovery-Menü did not start finally. It hang.
So first I wanted to put an original Samsung-ROM to the Phone. But where can I get the right one?
On the sticker in under the accu is written:
Model: GT-I9505SSN: -I9505GSMH
When I start the Download-Modus and connect it with ODIN, I can read the following:
ODIN MODE
Product Name: GT-I9505
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0KNOX WARRANTY LOCK: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enable
I searched this forum and the net, but I did'nt get a Firmware-Image, the I was able to flash finally with ODIN to the phone.
I start ODIN with ADMIN-Rights and the KIES-App is deletet from the processes. The Samsung-USB-drivers are installed and the phone was found in ODIN.
Could anybody of You give me a way-sign where I have to read the solution of the problem? Or could anybody of you explain the process of flashing?
THanks a lot for your help.
with best regards
speedy8 said:
I searched this forum and the net, but I did'nt get a Firmware-Image, the I was able to flash finally with ODIN to the phone.
Click to expand...
Click to collapse
Sammobile.com for the firmware. Unzip the firmware, select "AP" in Odin, and point to the extracted tar.gz image. Odin should then flash the image.