My friend has a GT-I9500 that gets stuck at the Samsung logo when booting and the status led is blue blinking slowly.... We have verified that it is not a fake through Sammy. The problem is that the phone will not go into download mode... We can get into recovery, but not download. Odin will not recognize the phone in either state (boot loop or recovery). I have read the threads about shorting the jumpers, but when we took the phone apart, it does not look like the pics (that sounded really noob...) and we were not able to locate the correct pins to jump... We ordered a jig off of ebay and it will be here soon, but does anybody have any other ideas??
Thanks for the input ahead of time!
mcookmpd said:
My friend has a GT-I9500 that gets stuck at the Samsung logo when booting and the status led is blue blinking slowly.... We have verified that it is not a fake through Sammy. The problem is that the phone will not go into download mode... We can get into recovery, but not download. Odin will not recognize the phone in either state (boot loop or recovery). I have read the threads about shorting the jumpers, but when we took the phone apart, it does not look like the pics (that sounded really noob...) and we were not able to locate the correct pins to jump... We ordered a jig off of ebay and it will be here soon, but does anybody have any other ideas??
Thanks for the input ahead of time!
Click to expand...
Click to collapse
Next time use this help thread: http://forum.xda-developers.com/forumdisplay.php?f=2164
and search bricked and u will end up with this: http://forum.xda-developers.com/showthread.php?t=2265477
I got my phone once it a bootloop, reflashed Rom and done.Dont know if u flashed a rom
Tunestwo said:
Next time use this help thread: http://forum.xda-developers.com/forumdisplay.php?f=2164
and search bricked and u will end up with this: http://forum.xda-developers.com/showthread.php?t=2265477
I got my phone once it a bootloop, reflashed Rom and done.Dont know if u flashed a rom
Click to expand...
Click to collapse
Yep....read that one before. The problem is I can't do step 1.....download mode. Down + home + pwr won't take the phone into download mode, it simply turns it on.
Try using terminal.
Type :
su
reboot download
I know in twrp recovery there is also an option to boot to download mode.
Best of luck
Sent from my SGH-I337M
Guys,
I was using the Cyanogenmod 11 for about 2 weeks and I always got the "kernel is not seandroid enforcing" message and the phone always booted up fine 90% of the times. Today I got the message saying that there was a new version of the firmware and I clicked ok for the phone to restart and begin the update process.
After that, I was stuck in the "kernel is not seandroid enforcing" message no matter what I did.
I entered the recovery mode and wiped the cache partition to see if that solved the problem. After this, I'm not able to access the recovery mode anymore and the phone is stuck on the samsung logo.
So I put it in download mode, opened Odin (It recognized the phone just fine) and flashed the original firmware in order to unbrick the phone. Got a PASS on Odin and I was still stuck on bootloop with no recovery mode.
Tried flash it again with the pit file (thought it would fix the partition) and the problem stills perssists.
I tried to run the Cyanogenmod installer and it doesn't recognize the phone anymore, saying the model is not compatible. Odin still recognizes the phone as always when I put it in download mode.
Any ideas?
Have I lost the phone ?
Thanks in advance for the help.
Best Regards
menaum said:
Guys,
I was using the Cyanogenmod 11 for about 2 weeks and I always got the "kernel is not seandroid enforcing" message and the phone always booted up fine 90% of the times. Today I got the message saying that there was a new version of the firmware and I clicked ok for the phone to restart and begin the update process.
After that, I was stuck in the "kernel is not seandroid enforcing" message no matter what I did.
I entered the recovery mode and wiped the cache partition to see if that solved the problem. After this, I'm not able to access the recovery mode anymore and the phone is stuck on the samsung logo.
So I put it in download mode, opened Odin (It recognized the phone just fine) and flashed the original firmware in order to unbrick the phone. Got a PASS on Odin and I was still stuck on bootloop with no recovery mode.
Tried flash it again with the pit file (thought it would fix the partition) and the problem stills perssists.
I tried to run the Cyanogenmod installer and it doesn't recognize the phone anymore, saying the model is not compatible. Odin still recognizes the phone as always when I put it in download mode.
Any ideas?
Have I lost the phone ?
Thanks in advance for the help.
Best Regards
Click to expand...
Click to collapse
Hi,
When you run the stock firmware through odin , you must wipe the cache an data before and after the flash.
Did you do that?
malybru said:
Hi,
When you run the stock firmware through odin , you must wipe the cache an data before and after the flash.
Did you do that?
Click to expand...
Click to collapse
I can't to that without the recovery mode, right?
I have no acess to the recovery mode.
menaum said:
I can't to that without the recovery mode, right?
I have no acess to the recovery mode.
Click to expand...
Click to collapse
Hi,
Are you sure you are trying to access it correctly?
Try holding the power button + volume up.
When the blue writing comes up , let go of all the buttons , and tap volume down.
If that still does not work , install the stock firmware again , and see if you can then get back to recovery mode.
malybru said:
Hi,
Are you sure you are trying to access it correctly?
Try holding the power button + volume up.
When the blue writing comes up , let go of all the buttons , and tap volume down.
If that still does not work , install the stock firmware again , and see if you can then get back to recovery mode.
Click to expand...
Click to collapse
Already did that, still no sucess. It enters the download mode normally but when I try to enter the recovery mode the blue text appears and then the screen goes black and the phone tries to boot and gets stuck on the samsung logo. (And yes I already tried holding the buttons until something else appears on the screen and nothing happens. )
And yes I'm trying to acess it correctly.
Thansks!
menaum said:
Already did that, still no sucess. It enters the download mode normally but when I try to enter the recovery mode the blue text appears and then the screen goes black and the phone tries to boot and gets stuck on the samsung logo. (And yes I already tried holding the buttons until something else appears on the screen and nothing happens. )
And yes I'm trying to acess it correctly.
Thansks!
Click to expand...
Click to collapse
Hi,
Do you have the knox bootloader?
What firmware are you trying to flash?
AT&T version here, same problem
malybru said:
Hi,
Do you have the knox bootloader?
What firmware are you trying to flash?
Click to expand...
Click to collapse
Quick ?: I have the AT&T s4 i337 with the same problem. Can i use the same method ? And no on the knox(saferoot) . 4.2 i believe. Thanx & sorry for butting in ! Ardonie
ardonie said:
Quick ?: I have the AT&T s4 i337 with the same problem. Can i use the same method ? And no on the knox(saferoot) . 4.2 i believe. Thanx & sorry for butting in ! Ardonie
Click to expand...
Click to collapse
Hi,
Then , you should try flashing a non-knox firmware .
Unfortunately ,I do not know AT&T firmwares.
Perhaps someone HERE can help.
I have the same issue on verizon, and searching for a solution. If you guys got any further in solving i would appreciate sharing the methods here
recovery is not Seandroid Enforcing
lorenzoraj said:
I have the same issue on verizon, and searching for a solution. If you guys got any further in solving i would appreciate sharing the methods here
Click to expand...
Click to collapse
I also have the same problem with Galaxy s4 Active (i9295)
Flashing recovery finish successfully (tried Philz,CWM, TWRP )
But afterwards no recovery exists anymore
only:
recovery is not Seandroid Enforcing
When I flash stock ROM again, the basic recovery it there - no option for applying zip files
Hi guys, I just recently attempted to root my Note 3 using CF-Auto-Root however after downloading and installing using my version (SM-N900T since I have tmo) it is stuck at a screen saying
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
SET WARRANTY BIT: RECOVERY
It seems that I cannot leave this boot screen to get into download mode and the device will not boot into android so I am at a loss of what to do. My computer does not see the device when I plug it in.
nrkid9 said:
Hi guys, I just recently attempted to root my Note 3 using CF-Auto-Root however after downloading and installing using my version (SM-N900T since I have tmo) it is stuck at a screen saying
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
SET WARRANTY BIT: RECOVERY
It seems that I cannot leave this boot screen to get into download mode and the device will not boot into android so I am at a loss of what to do. My computer does not see the device when I plug it in.
Click to expand...
Click to collapse
Use below file for rooting & once rooted successfully, switch off your phone & reboot in recovery.
http://d-h.st/J32
re: download mode
nrkid9 said:
Hi guys, I just recently attempted to root my Note 3 using CF-Auto-Root however after downloading and installing using my version (SM-N900T since I have tmo) it is stuck at a screen saying
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
SET WARRANTY BIT: RECOVERY
It seems that I cannot leave this boot screen to get into download mode and the device will not boot into android so I am at a loss of what to do. My computer does not see the device when I plug it in.
Click to expand...
Click to collapse
Remove battery, wait 10 seconds replace battery and
hold down the volume down+power+home key at the
same time. Then the phone will go into download mode.
I have 4 sprint Note 3's I rooted with CWM for all 4 but one is "stuck" at recovery like this any time I turn it on it always tries to boot into recovery and gets stuck.
I can get into download mode. will cf auto root fix this? (trying to avoid a full odin restore)
the only thing different about this sprint note 3 that I am aware of is that its flashed to boost (if that matters it should not matter)
the other 3 went flawlessly. yes I tried to odin the cwm root a second time no change.
Thanks!!!
Thanks for the link. Just unboxed the note 3 (sprint) with version 4.3 and followed qbking77 and it was stuck on that same screen (tried it 3 times).
Your link saved me. :good::good::good:
I wonder why qbking's didn't work ... it always has in the past.
jdomadia said:
Use below file for rooting & once rooted successfully, switch off your phone & reboot in recovery.
http://d-h.st/J32
Click to expand...
Click to collapse
chickenmusket said:
Thanks for the link. Just unboxed the note 3 (sprint) with version 4.3 and followed qbking77 and it was stuck on that same screen (tried it 3 times).
Your link saved me. :good::good::good:
I wonder why qbking's didn't work ... it always has in the past.
Click to expand...
Click to collapse
Why didn't you use the specific file for your device (Note 3 Sprint): http://download.chainfire.eu/362/CF-Root/CF-Auto-Root/CF-Auto-Root-hltespr-hltespr-smn900p.zip
thought I was...
Maybe I'm getting dumber, or maybe it's getting more confusing to root. Seems like there's a crap load of how to root this device pages and it takes a long time to figure out which one actually works. Then once I find it, I'm faced with dead links to the downloads.
I read on many posts and comments that everyone is able to boot in download mode. My Note 3 just stuck on recovery boot and I can't get it to boot in download mode. I tried all of the suggestions about pressing three buttons, removing battery etc.
Does anyone know solution for when you can't get into download mode?
Thanks
Do you have access to a USB jig?
luqmaanki said:
I read on many posts and comments that everyone is able to boot in download mode. My Note 3 just stuck on recovery boot and I can't get it to boot in download mode. I tried all of the suggestions about pressing three buttons, removing battery etc.
Does anyone know solution for when you can't get into download mode?
Thanks
Click to expand...
Click to collapse
same problem here did you find solution please reply
As already posted .
Try USB Recovery Jig.
Fails then service centre .
twrp
vndnguyen said:
Why didn't you use the specific file for your device (Note 3 Sprint): http://download.chainfire.eu/362/CF-Root/CF-Auto-Root/CF-Auto-Root-hltespr-hltespr-smn900p.zip
Click to expand...
Click to collapse
i know this thread is old....but sometimes i have to access download mode, and then chose cancel in order for it to boot. usually from recovery when i tap reboot system, it brings me back to recovery. so i have to pull the battery and button combo to download mode then cancel. does this issue have any familiarity?
Someone please help I have a Samsung note edge that I just reset through the menu settings backup and reset option and phone turned off but did not fully come back on its just sitting on black Samsung Screen and on top left corner it says recovery booting set warranty bit : recovery in blue and yellow letters and I am able to got into the download screen but I press volume down just to cancel and reboot and stars coming on but gose back to same black Samung screen. Like i said I did not try rooting it or any such thing.
Wrong forum this is not EDGE model .
Download mode and flash stock rom through Odin is generic advice .
"Recovery Booting" Bootloop fix
A few months ago, my rooted Galaxy Note 3 (sm-n900t) was force closing and freezing my apps often. So I decided to boot into recovery to clear device cache. The 'recovery booting' would appear on the screen with the logo, but after 7 seconds it would reboot normally instead of opening recovery(I had version 3.2.3.0). So I did reboot recovery with Rom Toolbox and it began bootlooping with the message:
Recovery Booting....
Set Warranty Bit : recovery
It wouldn't boot normally, in recovery or download mode.
STEPS TO FIX:
1.) Let phone Bootloop until completely dead
2.) On PC downloaded (2.8.7.0) twrp file for device from twrp.me/devices
3.) Press and hold volume down + home + power until phone reboots into download mode.
4.) Plug device into PC USB where drivers are loaded.
5.) Start Odin or Samsung Tool z3x flashing tab
6.) Load twrp in AP or PDA section and flash
7.) Phone should reboot normally!
I have a tmobile note 3 and whenever i try to boot my phone it trys to go inot recovery but it says RECOVERY IS NOT SEANANDROID ENFORCING i cant do anything please i will do anything to fix it as long as its not bricked I am litteraly so sick I am throwing up please help me
androidmasterrace said:
I have a tmobile note 3 and whenever i try to boot my phone it trys to go inot recovery but it says RECOVERY IS NOT SEANANDROID ENFORCING i cant do anything please i will do anything to fix it as long as its not bricked I am litteraly so sick I am throwing up please help me
Click to expand...
Click to collapse
Well based on the limited info you gave I'm going to assume you flashed a rom. Likely a bad download.
If so download a different rom or re download the rom and flash again. Make sure you're doing a full wipe. Also be sure you're on the latest stable recovery.
Worst case if all of the above fails, odin the stock rom and start over and you'll be fine
running DECEPTICON rom (coming soon)
for best xda results, click to enlarge ?
http://img268.imageshack.us/img268/9564/searchitnoob.gif
re: RECOVERY IS NOT SEANANDROID
androidmasterrace said:
I have a tmobile note 3 and whenever i try to boot my phone it trys to go inot recovery but it says RECOVERY IS NOT SEANANDROID ENFORCING i cant do anything please i will do anything to fix it as long as its not bricked I am litteraly so sick I am throwing up please help me
Click to expand...
Click to collapse
When you see "RECOVERY IS NOT SEANANDROID" as the phone
tries to boot or boots it's perfectly normal after the phone is rooted.
Here is a fix which works 90% of the time for most people with the same
issue you are experiencing with your phone.
Power down the phone, then power it backup while holding the
phone's power/volumeUp/home buttons down all at the same time
until you see tiny blue text appear on top of your screen, as soon as
you see that let go of all buttons.
The phone will boot into Recovery mode.
Once you are in recovery mode do a "factory data reset" or factory reset
which ever way the option is displayed.
After that the phone reboots itself and it should fully boot making the phone
ready to use.
Good luck!
androidmasterrace said:
I have a tmobile note 3 and whenever i try to boot my phone it trys to go inot recovery but it says RECOVERY IS NOT SEANANDROID ENFORCING i cant do anything please i will do anything to fix it as long as its not bricked I am litteraly so sick I am throwing up please help me
Click to expand...
Click to collapse
Take the battery out for a minute or so, then reboot into recovery. If no go, reflash your recovery (make sure you're using the right one obviously.
RECOVERY IS NOT SEANANDROID ENFORCING is normal when you have a custom recovery installed. It's just telling you that the official samsung signature isn't there. There's many threads regarding bootlooping around, a quick read probably would have sorted you :good:
PS: For the record, if you're getting physically sick about it, maybe you should read up a bit more before messing around with your very expensive device. I might sound awful but it's the truth.
Fixed It
The problem was i flashed the wrong recovery and my phone would not load or even go into download mode. I found somewhere online that if i held the download mode buttons before i put the battery in it would work and it did which allowed me to re flash my recovery.
Hi,
**Long Story**
I'm new here - I refrained from posting as I know a repeat post can p*** people off but I can't find my problem or fix it.
My own Sony was stolen a week ago - My brother in law kindly gave me his old S5 as a back up phone.
He has never had any problems with it EVER. I did a factory reset (from the settings menu) to clear his data and straight away I was in a boot loop (Handset vibrates, Samsung logo displays, blue LED, vibrates, handset switches off.. over and over again) the only way to stop this is to remove the battery. I cannot enter recovery mode but I CAN enter download mode. According to the settings the handset was running the latest version of lollipop.
I took the phone home anyway, thinking I could fix it - leaving the battery out in my pocket.
When I got home, I put the battery in and the phone turned on, unfortunately I forgot to put the sim card in - so I removed the battery, put in the sim card and... Boot Loop!
At this point I was really frustrated so I left the battery out and went to sleep. I woke up in the morning, put the battery in and it worked fine, all day, then all of a sudden the phone switched itself off and now I'm back in a boot loop and this time it isn't wanting to work again.
I have:
- Flashed with stock roms using Odin (5.0 & 4.4.2) - Yes, I used the correct firmware for my handset.
- Flashed with Kies to the latest firmware
- In desperation, tried the "Bash your power button against a hard, flat surface" trick
- Shouted at the handset
None of these have worked and every post I have found says to put the phone in recovery mode, I CANT. When I try, the blue "Recovery Booting" text is displayed, but just restarts anyway...
Weirdly and at random times, twice, the phone has powered on while plugged into my laptop, but the screen is blank, I get message sounds and the soft keys below the screen light up, but the screen is blank.
Any body have any idea?!?!! I'm vaguely techy, however not with this kind of thing. Any help would be much appreciated. What confuses me is there was no problem before I did the factory reset.
didscub said:
Hi,
**Long Story**
I'm new here - I refrained from posting as I know a repeat post can p*** people off but I can't find my problem or fix it.
My own Sony was stolen a week ago - My brother in law kindly gave me his old S5 as a back up phone.
He has never had any problems with it EVER. I did a factory reset (from the settings menu) to clear his data and straight away I was in a boot loop (Handset vibrates, Samsung logo displays, blue LED, vibrates, handset switches off.. over and over again) the only way to stop this is to remove the battery. I cannot enter recovery mode but I CAN enter download mode. According to the settings the handset was running the latest version of lollipop.
I took the phone home anyway, thinking I could fix it - leaving the battery out in my pocket.
When I got home, I put the battery in and the phone turned on, unfortunately I forgot to put the sim card in - so I removed the battery, put in the sim card and... Boot Loop!
At this point I was really frustrated so I left the battery out and went to sleep. I woke up in the morning, put the battery in and it worked fine, all day, then all of a sudden the phone switched itself off and now I'm back in a boot loop and this time it isn't wanting to work again.
I have:
- Flashed with stock roms using Odin (5.0 & 4.4.2) - Yes, I used the correct firmware for my handset.
- Flashed with Kies to the latest firmware
- In desperation, tried the "Bash your power button against a hard, flat surface" trick
- Shouted at the handset
None of these have worked and every post I have found says to put the phone in recovery mode, I CANT. When I try, the blue "Recovery Booting" text is displayed, but just restarts anyway...
Weirdly and at random times, twice, the phone has powered on while plugged into my laptop, but the screen is blank, I get message sounds and the soft keys below the screen light up, but the screen is blank.
Any body have any idea?!?!! I'm vaguely techy, however not with this kind of thing. Any help would be much appreciated. What confuses me is there was no problem before I did the factory reset.
Click to expand...
Click to collapse
Who is your service provider? Is the phone unlocked? Where did you get the stock firmware from?
Cryceratops said:
Who is your service provider? Is the phone unlocked? Where did you get the stock firmware from?
Click to expand...
Click to collapse
Thanks for the reply!
Service Provider - o2 UK
Stock from sanmmob
Phone is not unlocked
I did my best to try & get the firmware for my particular service provider but sammob and a few of the other sites use those awful restricted speed file sharing sites.
didscub said:
Thanks for the reply!
Service Provider - o2 UK
Stock from sanmmob
Phone is not unlocked
I did my best to try & get the firmware for my particular service provider but sammob and a few of the other sites use those awful restricted speed file sharing sites.
Click to expand...
Click to collapse
Did you try the one I linked to you or a different one?
Cryceratops said:
Did you try the one I linked to you or a different one?
Click to expand...
Click to collapse
Only just saw that - I didnt - thank you.
I will try now but may take a while to get back to you while I wait to download.
Try flashing the PIT file along with the stock ROM in ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract to .pit - add to PIT section in ODIN, add ROM to AP or PDA section, flash them both at the same time
*Detection* said:
Try flashing the PIT file along with the stock ROM in ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract to .pit - add to PIT section in ODIN, add ROM to AP or PDA section, flash them both at the same time
Click to expand...
Click to collapse
Thanks, did that, now the phone has started but it stuck at the first "Powered by Android" screen, not restarting but can't go any further and still cant get into recovery.
didscub said:
Thanks, did that, now the phone has started but it stuck at the first "Powered by Android" screen, not restarting but can't go any further and still cant get into recovery.
Click to expand...
Click to collapse
Try flashing just the ROM again, and then try booting into recovery, and factory reset
Or try flashing TWRP 2.8.7.0 with ODIN, and then boot into recovery and factory reset
Use this guide (Don't worry about the SuperSU part if you don't need root, and ignore the reactivation part as you can't boot the phone yet - start at No.3)
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Are you flashing the latest Lollipop ROM too?
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM
*Detection* said:
Try flashing just the ROM again, and then try booting into recovery, and factory reset
Or try flashing TWRP 2.8.7.0 with ODIN, and then boot into recovery and factory reset
Use this guide (Don't worry about the SuperSU part if you don't need root, and ignore the reactivation part as you can't boot the phone yet - start at No.3)
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Are you flashing the latest Lollipop ROM too?
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM
Click to expand...
Click to collapse
flashed TWRP 2.8.7.0 - Doesn't go into revovery:
Recovery is not SEANDROID ENFORCING
Set Warranty Bit : Recovery
I was flashing with G900FXXU1BOJ1_G900FOXA1BOJ1_G900FXXU1BOJ1_HOME.tar.md5
didscub said:
flashed TWRP 2.8.7.0 - Doesn't go into revovery:
Recovery is not SEANDROID ENFORCING
Set Warranty Bit : Recovery
I was flashing with G900FXXU1BOJ1_G900FOXA1BOJ1_G900FXXU1BOJ1_HOME.tar.md5
Click to expand...
Click to collapse
Did you follow the guide I linked?
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Pull the battery after flash, do not allow the phone to reboot first etc?
Because that error is usually associated with you allowing the phone to reboot Automatically after flashing TWRP
*Detection* said:
Did you follow the guide I linked?
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Pull the battery after flash, do not allow the phone to reboot first etc?
Because that error is usually associated with you allowing the phone to reboot Automatically after flashing TWRP
Click to expand...
Click to collapse
Pulled as soon as it said Pass.
This is so confusing, is the Stock firmware that you've linked to in Mega the same as the one I have downloaded?
Will retry with TWRP again. BRB
didscub said:
Pulled as soon as it said Pass.
This is so confusing, is the Stock firmware that you've linked to in Mega the same as the one I have downloaded?
Will retry with TWRP again. BRB
Click to expand...
Click to collapse
BOJ1 yea, same one
Try different versions of ODIN, 3.09 up to 3.10.7 (Maybe even 3.07)
*Detection* said:
Did you follow the guide I linked?
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Pull the battery after flash, do not allow the phone to reboot first etc?
Because that error is usually associated with you allowing the phone to reboot Automatically after flashing TWRP
Click to expand...
Click to collapse
Definitely didt let it reboot & pulled the battery. Tried it twice to make sure.
I am downloading the Stock firmware that you have linked and will try that, is there any reason why it started to reboot constantly after I factory reset? It can't be hardware because there was never a HW problem before I reset it. I don't suppose you want to pop down from Durham and fix it?! lol
didscub said:
Definitely didt let it reboot & pulled the battery. Tried it twice to make sure.
I am downloading the Stock firmware that you have linked and will try that, is there any reason why it started to reboot constantly after I factory reset? It can't be hardware because there was never a HW problem before I reset it. I don't suppose you want to pop down from Durham and fix it?! lol
Click to expand...
Click to collapse
To London? wanna pay the plane fare? lol
If you got that firmware from Sammobile, the one I linked you to is the same one, that's where I got it from, you could try some different droid versions, try a KitKat ROM too
Not sure why it would boot loop after you factory reset it, if reactivation lock was left on, you should still have managed to get to the welcome screen, but then be locked out of the phone until you entered his samsung account login
Sounds like something bugged out during the reset, and didn't reset properly, or corrupted one of the partitions, which the PIT file should have fixed
Stock recovery is cr4p though, I've ended up with a bootloop just clearing caches from it before, and had to flash TWRP to clear them properly, then flash stock on top again just to get it to boot
*Detection* said:
To London? wanna pay the plane fare? lol
If you got that firmware from Sammobile, the one I linked you to is the same one, that's where I got it from, you could try some different droid versions, try a KitKat ROM too
Not sure why it would boot loop after you factory reset it, if reactivation lock was left on, you should still have managed to get to the welcome screen, but then be locked out of the phone until you entered his samsung account login
Sounds like something bugged out during the reset, and didn't reset properly, or corrupted one of the partitions, which the PIT file should have fixed
Stock recovery is cr4p though, I've ended up with a bootloop just clearing caches from it before, and had to flash TWRP to clear them properly, then flash stock on top again just to get it to boot
Click to expand...
Click to collapse
OK - Sorry for the delay but unfortunately I had to do stuff - I would have happily sat and tried to fix it all day.
So, I did spend some time on it earlier and a few things happened.
I reinstalled different firmwares, and also tried TWRP 2.8.7.0 a few times with different versions of Odin but nothing would work.
I reinstalled the firmware BOJ1, nothing
Tried PIT again, nothing
Then, after trying PIT I got the Firmware error and connected to Kies... It worked, but now I just have a blank screen (another seemingly common issue with these paperweights) - Unsure what to do now, the phone is on, i can call it, find it with device manager but the screen is just blank. FML.
didscub said:
OK - Sorry for the delay but unfortunately I had to do stuff - I would have happily sat and tried to fix it all day.
So, I did spend some time on it earlier and a few things happened.
I reinstalled different firmwares, and also tried TWRP 2.8.7.0 a few times with different versions of Odin but nothing would work.
I reinstalled the firmware BOJ1, nothing
Tried PIT again, nothing
Then, after trying PIT I got the Firmware error and connected to Kies... It worked, but now I just have a blank screen (another seemingly common issue with these paperweights) - Unsure what to do now, the phone is on, i can call it, find it with device manager but the screen is just blank. FML.
Click to expand...
Click to collapse
OK, so they phone is working, there's just no display...
OK, try resetting the phone remotely from here first
https://www.google.com/android/devicemanager
If it's not connected to the network - try this
http://forums.androidcentral.com/sa...ory-reset-galaxy-s5-computer.html#post4365754
If that still fails, try flashing a stock KitKat ROM from Sammobile, see if downgrading the OS is a big enough change for it to overwrite whatever is causing the problem
Wondering if TWRP has flashed, but the no screen thing is stopping you from knowing one way or another - if we could get into TWRP, we'd have a lot more options, including custom ROMs
---------- Post added at 10:00 ---------- Previous post was at 09:44 ----------
Uploaded the latest KitKat ROM
Code:
https://mega.nz/#!eIQEAQ6a!ztOhVwFuI2MpD6OBhxC-TtgwUJQCxtwnfDQvFOl3g40
*Detection* said:
OK, so they phone is working, there's just no display...
OK, try resetting the phone remotely from here first
https://www.google.com/android/devicemanager
If it's not connected to the network - try this
http://forums.androidcentral.com/sa...ory-reset-galaxy-s5-computer.html#post4365754
If that still fails, try flashing a stock KitKat ROM from Sammobile, see if downgrading the OS is a big enough change for it to overwrite whatever is causing the problem
Wondering if TWRP has flashed, but the no screen thing is stopping you from knowing one way or another - if we could get into TWRP, we'd have a lot more options, including custom ROMs
---------- Post added at 10:00 ---------- Previous post was at 09:44 ----------
Uploaded the latest KitKat ROM
Code:
https://mega.nz/#!eIQEAQ6a!ztOhVwFuI2MpD6OBhxC-TtgwUJQCxtwnfDQvFOl3g40
Click to expand...
Click to collapse
Thanks,
I'll wait for that to download and try.
So - I used accessibility mode to get into settings and do a factory reset... It was difficult, I even thought that the Dark Screen setting might have mysteriously have been turned on but nope.
Rebooted and got the Bootloader screen with the Samsung logo and Recovery Booting text, after a few minutes the screen went blank and the phone vibrated and then nothing!!! :crying::crying::crying:
I have just put it into download mode (I only know this because the many hours I've spent doing this I noticed that the battery and device goes cool when its in download mode) and will try the KitKat flash once its downloaded - Thank you for that btw.
Its so strange - it cant be an issue with the actual screen because it *sometimes* displays the logo.. What can it be?? Its also odd that from when I originally reset it, it could'nt boot into recovery. I'm worried that everything I have done has screwed it up more? Can the Recovery/Bootloader be "Broken"? Its so confusing, I hate tech that doesn't behave.
didscub said:
Thanks,
I'll wait for that to download and try.
So - I used accessibility mode to get into settings and do a factory reset... It was difficult, I even thought that the Dark Screen setting might have mysteriously have been turned on but nope.
Rebooted and got the Bootloader screen with the Samsung logo and Recovery Booting text, after a few minutes the screen went blank and the phone vibrated and then nothing!!! :crying::crying::crying:
I have just put it into download mode (I only know this because the many hours I've spent doing this I noticed that the battery and device goes cool when its in download mode) and will try the KitKat flash once its downloaded - Thank you for that btw.
Its so strange - it cant be an issue with the actual screen because it *sometimes* displays the logo.. What can it be?? Its also odd that from when I originally reset it, it could'nt boot into recovery. I'm worried that everything I have done has screwed it up more? Can the Recovery/Bootloader be "Broken"? Its so confusing, I hate tech that doesn't behave.
Click to expand...
Click to collapse
Does sound like a possible hardware problem, but unlikely or a huge coincidence that it all started after resetting, so I'd be more inclined to think otherwise
Just remembered about this unbrick image / tutorial
http://forum.xda-developers.com/galaxy-s5/general/g900f-debrick-img-lollipop-t3240626
Might be worth giving that a shot
*Detection* said:
Does sound like a possible hardware problem, but unlikely or a huge coincidence that it all started after resetting, so I'd be more inclined to think otherwise
Just remembered about this unbrick image / tutorial
http://forum.xda-developers.com/galaxy-s5/general/g900f-debrick-img-lollipop-t3240626
Might be worth giving that a shot
Click to expand...
Click to collapse
OK - might be a massive chore rooting and installing busybox.. Worth a shot though. Can I not use it with Odin??
didscub said:
OK - might be a massive chore rooting and installing busybox.. Worth a shot though. Can I not use it with Odin??
Click to expand...
Click to collapse
You don't need busybox, that's for creating your own debrick image, the tutorial stops here:
Flash this Debrick file to your 16GB Micro SD card with Win32DiskImager
*Insert your Micro SD card into your computer (backup any information you may have on it we are going to ERASE, FORMAT it to ex FAT
*Open win32DiskImager
*Navigate to the location where you downloaded the correct Debrick file
*Select your Debrick file by double clicking on it
*In the upper right corner of Win32DiskImager you should make sure that the drive letter assigned to your sd card is selected.
***Which ever drive that is listed will be erased, formatted
*Click write in the bottom right hand side
put the Debrick SD card in the Phone, Pull and Replace the Battery
Plug phone in usb and boot into download mode
yout phone should boot into download mode then flash stock firmware via odin
Download link : https://drive.google.com/file/d/0ByA...ew?usp=sharing
You're saying you can't see anything on screen in download mode, just guessing it's there because it cools down - but that could also mean it's not in any mode
With this method, you might get a display to use, then you can flash normally with ODIN with download mode visible on screen