Let me start off by saying I have already scoured this forum and other sources for a solution to this problem. I should add that I am somewhat bound by the confines of my experience, also.
Like many others here, my Samsung S4 mini GT-I9195 is stuck in a boot loop, unable to get into recovery mode. It can get to download mode, but is not recognized by my PC.
Things I've done so far:
1. tried to boot in recovery mode - doesn't work, says "Recovery starting..." then restarts into boot loop
2. checked battery - not it
3. dissasembled phone and checked power button - works fine
4. tried Samsung Kies - "Device is not responding. To resolve the issue, reboot the device." - no can do (note that I only just installed Samsung Kies on my PC for the first time after the boot loop started)
5. flashed firmware using Odin - PASS! - still in bootloop w/no recovery mode
6. flashed firmware again using Odin w/Auto-Reboot unchecked - PASS! - then attempted to reboot into recovery - no go, still in bootloop w/no recovery mode
The firmware I successfully flashed was Poland/T-Mobile version 4.4.2 downloaded from sammobile.
The one thing I have NOT tried is to repartition the pit file. Would this possibly make any difference? If it's worth a try, can I do this using the tar.md5 package above, or do I need a separate .pit file and if so, how do I know I have the right one???
After doing a little reading, I downloaded CSB_signed_SERRANOLTE_ONEPIT_OPEN_130523.pit, which was included in a 'repair firmware' .zip file that also included separate bootloader, code, csc and modem files. I actually did try flashing those files (except for the pit file) and that failed (of course) with error "Device 2, Binary 1", so I flashed the firmware above again and it passed again.
What else?
- Phone is not rooted
- I have no idea if USB debugging is turned on or not
- I was doing nothing with the phone when it first died. I figured the battery might have somehow rapidly drained to zero even though it should have been around 70%. I had last touched the phone about an hour earlier, to shut off my alarm. I tried plugging in to wall charger but phone would not turn on even after an hour or more of charging. I really don't remember exactly how or when the bootloop started.
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB:0x30
BOOTLOADER AP SWREV: 2
WRITE PROTECTION: Enable
Anyone out there feel like helping out a noob today?
i have same problem
Actually , only one diferrent
KNOX WARRANTY VOID: 0x1
exactly same ,but i tried with pit 2 pit files and 2 diferent roms , and no result. Pleace help us!!!
Related
Hello,
I recently soft bricked my Sprint Samsung Galaxy S4 while trying to unlock the device to make it work with other US carriers (not sure if that would work). I modified the build.prop file following http://forum.xda-developers.com/showthread.php?t=2530610 forum. I think I did not made the correct changes and after that phone keeps rebooting. Phone shows Samsung Galaxy S4 logo and wouldn't pass this. Prior to this I did not make any copy of the files so doing a restore from back up is not possible at this time. I don't care about the data being lost. I only care about getting the phone back up and working.
I canget to ODIN mode and recovery mode. I had previously flashed it with SPH-L720_MDC_Modem.tar.md5 and CF-Auto-Root-jfltespr-jfltespr-sphl720.tar.md5 using ODIN before the problem started.
I tried all possible way to get my phone working but still it keeps rebooting.
I tried:
1. wipe data/factory reset
2. wipe cache partition
3. tried to update from ADB - this i can get to list my device using (adb devices) but cannot get to push or pull /system/build.prop file to edit it. I get "error:closed" when I type in "adb usb" or "adb shell". I was able to log in as SU prior to this problem. I have the latest SDK installed.
I know for sure that I had checked the "USB Debugging" checkbox prior to this issue.
4. I tried flashing it with L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 but I get the error that Binary=1 in download mode. Not sure if Triangle away apk will be of any help here to reset the binary counter since I cannot get past the samsung logo at all.
In recovery mode, my system reads:
Android system recovery <3e>
KOT49H.L720VPUFNAE
In ODIN mode, my system reads:
Product Name: SPN-L720
Current Binary: Custom
System Status: Custom
KNOX Kernel: 0x0
KNOX Warranty Void: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Can someone please help me to fix this issue? I can provide more information if needed.
Thanks so much.
temp4ling said:
Hello,
I recently soft bricked my Sprint Samsung Galaxy S4 while trying to unlock the device to make it work with other US carriers (not sure if that would work). I modified the build.prop file following http://forum.xda-developers.com/showthread.php?t=2530610 forum. I think I did not made the correct changes and after that phone keeps rebooting. Phone shows Samsung Galaxy S4 logo and wouldn't pass this. Prior to this I did not make any copy of the files so doing a restore from back up is not possible at this time. I don't care about the data being lost. I only care about getting the phone back up and working.
I canget to ODIN mode and recovery mode. I had previously flashed it with SPH-L720_MDC_Modem.tar.md5 and CF-Auto-Root-jfltespr-jfltespr-sphl720.tar.md5 using ODIN before the problem started.
I tried all possible way to get my phone working but still it keeps rebooting.
I tried:
1. wipe data/factory reset
2. wipe cache partition
3. tried to update from ADB - this i can get to list my device using (adb devices) but cannot get to push or pull /system/build.prop file to edit it. I get "error:closed" when I type in "adb usb" or "adb shell". I was able to log in as SU prior to this problem. I have the latest SDK installed.
I know for sure that I had checked the "USB Debugging" checkbox prior to this issue.
4. I tried flashing it with L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 but I get the error that Binary=1 in download mode. Not sure if Triangle away apk will be of any help here to reset the binary counter since I cannot get past the samsung logo at all.
In recovery mode, my system reads:
Android system recovery <3e>
KOT49H.L720VPUFNAE
In ODIN mode, my system reads:
Product Name: SPN-L720
Current Binary: Custom
System Status: Custom
KNOX Kernel: 0x0
KNOX Warranty Void: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Can someone please help me to fix this issue? I can provide more information if needed.
Thanks so much.
Click to expand...
Click to collapse
Friend
I am no expert on Android..... But I guess when I had a software brick I booted into recovery and flashed a custom rom..... U can install the zip file in ur SD card and then flash it with recovery?????
Sent from my MIND using my BODY....(JUST KIDDING)
Need Help toooooo!
Did you ever find a way to fix the challenge ?
temp4ling said:
Hello,
I recently soft bricked my Sprint Samsung Galaxy S4 while trying to unlock the device to make it work with other US carriers (not sure if that would work). I modified the build.prop file following http://forum.xda-developers.com/showthread.php?t=2530610 forum. I think I did not made the correct changes and after that phone keeps rebooting. Phone shows Samsung Galaxy S4 logo and wouldn't pass this. Prior to this I did not make any copy of the files so doing a restore from back up is not possible at this time. I don't care about the data being lost. I only care about getting the phone back up and working.
I canget to ODIN mode and recovery mode. I had previously flashed it with SPH-L720_MDC_Modem.tar.md5 and CF-Auto-Root-jfltespr-jfltespr-sphl720.tar.md5 using ODIN before the problem started.
I tried all possible way to get my phone working but still it keeps rebooting.
I tried:
1. wipe data/factory reset
2. wipe cache partition
3. tried to update from ADB - this i can get to list my device using (adb devices) but cannot get to push or pull /system/build.prop file to edit it. I get "error:closed" when I type in "adb usb" or "adb shell". I was able to log in as SU prior to this problem. I have the latest SDK installed.
I know for sure that I had checked the "USB Debugging" checkbox prior to this issue.
4. I tried flashing it with L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 but I get the error that Binary=1 in download mode. Not sure if Triangle away apk will be of any help here to reset the binary counter since I cannot get past the samsung logo at all.
In recovery mode, my system reads:
Android system recovery <3e>
KOT49H.L720VPUFNAE
In ODIN mode, my system reads:
Product Name: SPN-L720
Current Binary: Custom
System Status: Custom
KNOX Kernel: 0x0
KNOX Warranty Void: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Can someone please help me to fix this issue? I can provide more information if needed.
Thanks so much.
Click to expand...
Click to collapse
Phone specs:
Samsung Galaxy S3 Verizon SCH-i535
It was already running KitKat 4.4.2 before I rooted
This is my first time rooting and flashing ROMs to my Samsung Galaxy s3 and I have bricked it. I'm pretty sure it can be salvaged but have yet to find anything that works.
I have written the long version for those who need it, but the short version is that I screwed up and can no longer boot into recovery mode or normal mode, I'm not even sure if Download mode is working, and my device isn't recognized by Kies or Odin on my PC so I cannot yet do a recovery from there.
As of now my phone only boots into Odin Mode and gives the following info:
ODIN MODE
PRODUCT NAME: SCH-I535
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
QUALCOM SECUREBOOT: ENABLE
BOOTLOADER AP SWREV: 2
and displays the yellow triangle error and says: Firmware upgrade encountered an issue. Please use Software repair Assistant & try again.
I tried to use Samsung Kies which has an emergency firmware tool but my device will not connect and become recognized by the program.
This is pretty much where I'm stuck.
Keep reading if you need additional info.
Steps leading up to problem:
I was able to Root the device succesfully
I then downloaded the latest CM11 package (cm-11-20140217-NIGHTLY-d2vzw.zip) and Gapps
I also downloaded the TWRP recovery img (openrecovery-twrp-2.7.1.0-d2vzw.img)
Once I had these downloaded I got the app [ROOT] Rashr - Flash Tool
I opened the app and tried to do a backup but I'm pretty sure it failed, or at least it said it failed. I couldn't find out how to check, but was not worried since I have already backed up my important files to the verizon cloud.
On the app I went to recover using other file and found the TWRP recovery img I downloaded.
From here I booted into recovery manually, but it did not bring up the TEAMWIN screen for TWRP like I've seen in other video tutorials so I rebooted into normal mode went to the Rashr app again and followed the prompt to do a Recovery boot using the TWRP img.
THIS IS WHERE THE PROBLEMS BEGAN:
It began to lead into recovery mode but it gave a message that said something along the lines that I have tried installing a custom OS and to take my phone to the nearest verizon store.
I turned it off and tried to boot back normally but got the same error.
I tried to boot into Download mode and was successful! So I thought yaay!
Read a tutorial to reload a stock version of android here: http://forum.xda-developers.com/showthread.php?t=2586319
I followed all the steps but when i got to 7. which said You should see your phone under ID:COM (you should also see it has been added in message) I was not seeing my phone there. I figured it may be OK since I was able to install the drivers so that meant the USB was working so I went ahead and ran Odin to recover Jelly Bean 4.3 onto the device.
My thoughts and guesses as to what the problem is:
I think that it may be because I was already running 4.4.2 and/ or didn't have the proper bootloader when I tried to do the TWRP recovery.
Am I on the right track? Thanks for any help!
Please ask. In correct forum this is int'l s3 (i9300) forum
Hello,
I've Samsung Galaxy SM-J701F/DS and i did factory reset and started getting into panic mode. So, I tried to flash stock ROM through odin and I only selected AP and left other files like Bl, CP and CSC. Thus it took longer time without any result so, I closed the odin. Since then my phone only boots in download mode.
And while trying recovery or normal boot I get " Error Cannot Update Software ".
I used this ROM:
https://www.sammobile.com/firmwares/...-nxt/SM-J701F
And now my phone is showing as Samsung USB Modem while plugging in PC.
Hi,
I can't use my tablet anymore tried Odin to re-install the origin firmware "SM-T825Y_1_20180122165040_zf84f94qoe_fac.zip" (new android 8 stock ROM) but it fails, Odin shows the transfer has PASSED but I still get this message in the screen:-
"Security Error: This device has been flashed with unathorised software & is locked.
Call your mobile operator for additional support. "
I wasn't planning flashing a custom ROM the only thing I did is put OEM Lock on, not sure why I did that.
When I put in Download Mode it shows this in the screen:-
ODIN MODE [High Speed]
PRODUCT NAME: SM-T825Y
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
FAP LOCK: ON
OEM LOCK: ON
DID: 03EA1E00AE16
WARRANTY VOID: 0x1 (Ox20C)
QUALCOM SECUREBOOT: ENABLE
AP SWREV: B3 (1, 1, 1, 1, 1) K2 S2
SECURE DOWNLOAD: ENABLE
CCIC: S2 MM005 HW: 4
BOOT: 6 MAIN: DS
Regards,
Sal.
1. It's FRP not FAP ya perv.
2. Reflash firmware with odin, do not go into download mode afterwards before 3.
3. The rest watch this video carefully, and next time you want to leave your device stock, leave it stock, if you want to install a custom rom or twrp, do not have auto reboot ticked.
4. here is link ---> https://www.youtube.com/watch?v=o0T-CR-KpfM
I did reflash with odin but I still get this message "Security Error: This device has been flashed with unathorised software & is locked.
Call your mobile operator for additional support. " There is another small message on top , "Custom binary blocked by FRP. (boot.img)"
Odin tells me its PASSED but the Tablet still says its locked FRP and OEM locked .
In download mode I am getting same info.
I just went to the Samsung Shop and they fixed it for free, they said they just put a new firmware not sure how they did it but I tried it myself with latest firmware but I couldn't get rid of the lock, I am missing something? like software? or just not enough info about about getting rid of locks?
I had the same issue after i installed a Xposed module. Had to reflash Pie Bootloader and Rom via odin. Now it boots, but i can't flash twrp anymore... It always fails.
Hello androids, I have a big problem or a good challenge, depends on your optimism. I've been looking for and trying solutions for hours and hours, but I think I've come across a wall and I need your help:
Originally I wanted to root my s7 Edge / SM - G935F (OS Marshmallow 6.0.1) by following a tutorial using an autoroot ROM for this phone. I remember I had USB debugging and OEM unlock enabled. I also installed the USB / ADB drivers correctly.
I used Odin v3.11, since they recommended using it for this mobile and MM 6.0.1. According to Odin, the rom was installed successfully, but my phone entered a loop with the Samsung logo and "RECOVERY IS NOT SEANDROID ENFORCING". Something failed in the process and I decided to install a S7 Edge stock ROM in 8.0.0 from SAMMobile (this one) with Odin v3.13 using HOME_CSC so that I don't lose certain data
Unfortunately everything was going well until just at the end when "hidden.img" did not process correctly and resulted in FAIL. I've been since then stuck with this error:
"An Error has occurred while updating the device software. Use the Emergency Recovery in the Smart Switch PC Software."
It won't even turn off. From there I can only access the Download Mode and neither the Smart Switch or the ADB & Fastboot console won't detect the device. Odin does recognize the phone, but every time I try to install a rom, the log gets stuck in "SetupConnection ..".
I have tried a bunch of solutions such as removing the "hidden.img" from the package, reinstalling the drivers, changing the USB port, changing Odin's version, installing only the BL, etc., but nothing shows progress...
I'm sorry if during the process I managed to do some stupidity that I am not aware of. Other phones I have never had problems, but now I feel defeated and lost. I need a savior! :crying:
Any way to make Odin work, ADB detect my device or access a working bootload? Thanks in advance!