Samsung Galaxy S7 Edge (935FD) - boot loop after water damage - Samsung Galaxy S7 Edge Questions and Answers

Hi - Running an SM-G935FD. Had water damage that caused reboots, had to shut down. pulled apart, used ultrasonic + 99% isopropyl to clean. Installed new battery. Am now able to power up phone, but get flickering screen [screen since stopped flickering - could have been some alcohol still not evaporated?] and won't boot in safe or standard mode - sticks on SAMSUNG - GALAXY S7 EDGE - POWERED BY ANDROID screen. Blue light pulses (assume this is power?). I CAN reboot into recovery. I can see with adb but can't execute any commands other than side load [can use adb fully once TWRP installed]. I've wiped cache and done factory reset. I can enter ODIN mode, and have installed CF Autoroot for the 935F, and then TWRP, but still stuck in same mode unable to complete a boot. I can access logs from recovery mode but not sure what to make of them. I installed TWRP Recovery and can use TWRP, access the file system, etc.
I flashed factory ROM successfully using 4-file and PIT (G935FXXU1APD1), did a NAND ERASE ALL, EFS Clear and Bootloader Update, all successfully. After the 4-file flash/PIT/reset, in ODIN mode I get “Current Binary: Samsung Official” and “System Status: Custom” “Warranty Void: 1” “AP SWREV: B:1 K:0 S:0” I then reinstalled CF Autoroot, then TWRP. Using TWRP, wiped data, repaired file system, and fixed contexts. Binary is now also showing "custom." I still can't complete a system boot, safe mode or otherwise. TWRP recovery seems to be working fine, and I can browse file system using TWRP or adb. The "System Status of "custom" after a full flash and before CF autoroot/TWRP seems fishy to me... I once got an "Android is starting..." screen with turning gears and "Starting apps." but the system hung on that screen for over 20 minutes. Reboot to recovery got me the blue "Installing system update" and then dead android screens before getting to recovery. It feels like I'm close but not quite there yet. I'm downloading a single file firmware to try to flash (the BPH6 instead of APD1. At one point I had a recovery screen showing the APEQ version - not sure where that came from... I have a sense the FW version I'm trying to load isn't right.
I'm at a loss as to what I should do next. Seems like the hardware is working given TWRP and ODIN functionality, so I would have thought one of these system flashes would have solved the problem. I'm cycling through different FW versions in hopes that one does the trick. I seem to be able to use CF Autoroot and TWRP successfully no matter which version, I just cannot seem to get through a system boot, even in safe mode!
Any suggestions most welcome! I'm hoping to avoid having to replace the motherboard...

[help needed]
Bumping this request as it was just moved to this forum (and ended up pretty far back), so hoping for some suggestions!
Thanks in advance,
Mike

Hard ware issues cant be fixed with software.
Ultrasonic blasted something off the board..... RIP best bet is to transplant the NAND chip.

Related

[FIX?] Stuck on bootloop

Hi all,
I have a UK N910F 32GB Snapdragon Note 4, with a custom Lollipop rom that I've been using with no problems for a few months (http://forum.xda-developers.com/note-4/snapdragon-dev/rom-bob4-devbase-multi-csc-safe-bloat-t3033881). Yesterday the weirdness began - my Note 4 froze randomly in normal use and rebooted. It was then fine for around 5 hours, then froze again, and when it restarted it would continue to freeze on start-up. At that stage I could still boot into recovery (Clockwork Manager custom recovery), so I tried clearing cache and dalvik, which changed nothing. But now I am unable to do even that - it just gets stuck in bootloop and won't even go into recovery.
When I turn it on, it will stay on the Samsung splashscreen for 10 seconds, then reboot and vibrate twice, then go back onto splashscreen, reboots, etc. I need to remove the battery to stop this. The only thing I am able to do is boot into download mode, where the phone works with Odin fine, and I am able to flash successfully with Odin.
So far I have tried reflashing a stock UK 5.0.1 ROM - it initially gave me the ext4 error but I then got the N910F pit file and repartitioned - Odin flashing completed fine, then still got stuck on splashscreen with "Recovery booting...."). I have also tried to flash CWM and TWRP, which both flash fine, but then the phone still won't boot into recovery - I get:
#1 Battery in
#2 power on
#3 vibrate
#4 screen on RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
and doesn't boot into recovery. I'm pretty sure I'm using the correct TWRP and CWM versions.
I've spent all day trawling XDA and the wider web with no luck. Does anyone have any ideas on how to fix this? I'm hoping it is a softbrick but cannot work out how to get it back. I don't care about losing any data at this stage, just keen to bring my Note 4 back to life!
TL;DR: phone will stay on bootloop when powered on - not caused by failed software install, just started happening randomly. Cannot boot into recovery. Download mode works and can flash with Odin, but all attempted flashes so far haven't helped even when Odin succeeds in flashing.
Markachy said:
Download mode works and can flash with Odin, but all attempted flashes so far haven't helped even when Odin succeeds in flashing.
Click to expand...
Click to collapse
.
Have you tried flashing your variants cf-root file with auto reboot unchecked, let it Pass, remove USB abd battery, wait 30 seconds and reboot? Sounds weird.. i know, but for a while that put many users on 5.0.1 softbricks back to their previous working ROM.
I've just done that, it flashed successfully, I took battery and cable out and then rebooted after 30 seconds - it is now booting onto Samsung bootscreen, says:
RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Then reboots itself, same thing happens, reboots itself - back to a bootloop, but with the above written.
What's the fix for the above? Does it mean the recovery installed is wrong for the Android Rom version I have?
Thanks for your help so far, much appreciated.
Markachy said:
I've just done that, it flashed successfully, I took battery and cable out and then rebooted after 30 seconds - it is now booting onto Samsung bootscreen, says:
RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Then reboots itself, same thing happens, reboots itself - back to a bootloop, but with the above written.
What's the fix for the above? Does it mean the recovery installed is wrong for the Android Rom version I have?
Thanks for your help so far, much appreciated.
Click to expand...
Click to collapse
If you can still boot into the download mode and want to boot into the system as normal, using Samsung's Smart Switch tool will work. Search Google for "Samsung Smart Switch" no quotes, install the program then after finished installing, in the application, click MORE at the Smart Switch window, then click Emergency software recovery and initialization, then follow on-screen steps.
phongpan355 said:
If you can still boot into the download mode and want to boot into the system as normal, using Samsung's Smart Switch tool will work. Search Google for "Samsung Smart Switch" no quotes, install the program then after finished installing, in the application, click MORE at the Smart Switch window, then click Emergency software recovery and initialization, then follow on-screen steps.
Click to expand...
Click to collapse
Just tried that, same issue. When it boots after installation, it says "Recovery booting..." in top left corner, then goes into bootloop. Thanks for the tip though.
Any other ideas out on the grapevine? Or is it time for a return?
I'm having the same issue. Tried stock ANK4, BOB4 and BOC3. Only bootloops and can't reach recovery mode.
Than I tried TWRP 2.8.7.0 and "philz_touch_6.59.0-trlte" but they don't work either.
Don't know what to do now. Never had this issue before on any Samsung device
EDIT: Tried Samsung Smart Switch and it dowloaded PDA: OC3 / CSC: OB6 / PHONE: OC3 (DTM). But my Note bootloops furthermore
Saw 2 other guys with the same Problem and no solution here.
And I found this. This could be the same issue we are facing:
http://forum.xda-developers.com/showthread.php?t=1840030
Hope there is a dev that can make this for our 910F
Hi all
This is now also happening to me...
Have Odind back to stock and it works for about 4 hours,
Then issue starts...
Reboots randomly
Then reboots to blank screen... No recovery
Again uk note 4. 910f

Samsung Galaxy S5 SM-G900F No Recovery Mode always restart Brick

Hello,
I´ve got a problem with my Samsung Galaxy S5
The History:
I bought a Samsung Galaxy S5 SM-G900f from Ebay with a Software Problem. The seller said, he try to flash a Custom Room like Cyanogenmod, he don´t know which)
The flash failed (i don´t know why). Now the S5 have a brick.
I tried so much, but i can´t repair it, pls help me.
The Problem is:
I can not start the Recovery Menü to flash a new Custom room. Always i tried to start the Menü, there is just a text "recovery Booting", then the phone restarts after round about 10 sec.
So even if i tried to start the S5 normally without recovery Menü, it´s just the Samsung Galaxy S5 Logo power by Android, then the phone restarts all the time.
The only thing i can do is start the download mode.
Things i tried:
- Firmware installation about Kies (pass, but still the Same Problem)
-Firmware Installation about Odin (pass, but still the same Problem)
- CF-Autoroot flashing (pass) then i tried to flash a recovery like PhilZ but then when i tried to open the recovery it`s "Recovery is not seandroid enforcing" Set Warranty bit
I tried so many firmwares but still the same Problem. Now it is installed Lollipop 5.0 G900FXXU1BOI3_G900FDBT1BOI1_G900FXXU1BOI3_HOME
There is no chance to repair it over ADB oder Fastboot, cause USB-debugging is disabled
Maybe you can help me and help me to stop spend all my time for this phone, cause im interested to know how i can repair it.
flash twrp from odin
then sideload a rom
install the rom
tell me if it works
.
I tried to install twrp 2.7.0.0-klte with odin. It´s pass, but when i tried to boot into Recovery he said "recovery is not seandroid enforce" Set Warranty bit: recovery
Pls help me i´ve got no idea more
Try this hold on (power volume up and home) then do not release until recovery mode boot
sh4dow6oy said:
flash twrp from odin
then sideload a rom
install the rom
tell me if it works
Click to expand...
Click to collapse
I tried to install twrp 2.7.0.0-klte with odin. It´s pass, but when i tried to boot into Recovery he said "recovery is not seandroid enforce" Set Warranty bit: recovery
Pls help me i´ve got no idea more
With some of the newer LP based firmwares, twrp 2.8.7.0 klte is the only version that works.....
Other than that, you might find it necessary to odin back to KitKat (flashing a pit file too) and try 'towelrooting' your device.......
BE WARNED.......If you *do* flash a pit file, make sure it's the CORRECT pit for your device.....In some cases, flashing the wrong pit will permanently kill a device.
http://i.imgur.com/rVnFwJM.jpg
So i had try it.
1.)hold on ( volume up and home) then do not release until recovery mode boot
--> The phone always restart no recovery is possible
2.) I try to install on LP the TWRP 2.8.7.0 Still the Same error "recovery is not seandroid enforce" Set Warranty bit: recovery
Before i root the device with CF-Autoroot and it´s pass
3.) I downgrade to 4.4.2 with a full package of Firmware with CSC,BL,AP,CP and a pit file.
The downgrade pass, when the phone starts it says recovery booting in blue script, then the phone restarts. I can´t intstall towelroot, cause the system is not booting, so i´d tried to install CF-Autoroot (pass) and then also the TWRP 2.7.0.0 pass but not booting and then 2.8.0.0.
But still the same "recovery is not seandroid enforce" Set Warranty bit: recovery
If you got a pass on your KK flash, you have a stock recovery......
Have you tried booting into that recovery and wiping cache and factory resetting? It is necessary to do this when downgrading......
http://i.imgur.com/rVnFwJM.jpg
Yes it was a KK stock recovery.
I tried to boot in this recovery, but when the phone starts it says recovery booting in blue script, then the phone restarts after a few seconds.
It´s not possible to wipe cache or make a factory reset, cause the recovery is not booting. That´s my problem. Also when i have flash the stock firmware i tried to go into the recovery but when the phone starts it says recovery booting in blue script, then the phone restarts after a few seconds. ( 4.4.2 and 5.0)
I´can´t flash a custom rom cause the recovery is not booting. I´ve no idea
Are you attempting the 3 button combination from powered off to get into recovery?........
@'detection' does the OP's situation sound familiar?.....
http://i.imgur.com/rVnFwJM.jpg
Very familiar -
https://dl.twrp.me/klte/
Flash TWRP 2.8.7.0 .TAR (Do not unzip) with ODIN 3.10.7 - in Download mode (Volume Down & Home & Power)
It will say "recovery is not seandroid enforce" Set Warranty bit" at the top when you boot into recovery, give it a few seconds and you should see the TWRP blue splash screen, and then recovery should load up
Then flash a custom ROM from TWRP
--
If that all still fails, try flashing the PIT file for the G900F along with a Stock ROM
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract this one so it is .PIT, and add it to ODINs PIT section
If that still fails, try flashing just the PIT file with ODIN, and then the TWRP 2.8.7.0 with ODIN and see if you can get in that way
Or PIT and TWRP together
Try a combination until you get back in
Also try different versions of TWRP from 3.07 up to 3.10.7
keithross39 said:
Are you attempting the 3 button combination from powered off to get into recovery?........
@'detection' does the OP's situation sound familiar?.....
Yes i did, than the it happen what i wrote upside
What do you mean with "@'detection' does the OP's situation sound familiar?....."
Click to expand...
Click to collapse
It sounds familiar because it's happened to many other people recently too, although TWRP usually fixes it
Follow my instructions above
No chance guys,
i´d tried to install all TWRP which i found once in 5.0 and also i tried to install on 4.4.2. But always the same mistake. (recovery is not se.....)
Now i´ve tried to install CWM-Recovery and now there is no mistake like upside. Now in blue "recovery booting" and in yellow set warranty bit: recovery
But the recovery is not booting, the phone always make a restart. I´d also tried to install the recovery without auto-reboot in odin. But no help.
I don´t understand, cause when i flash a Stock Firmware, the recovery menu ,in my opinion, it have to start, but it doesn´t. Maybe i have anexpensive paper weight now
I search the internet to install a Custom room over Odin, but i don´t find any results, so i think it is not possible.
Do you have more ideas? Pls help. Thanks
I have the exact same problem, some are calling it the Black Screen of Death (with the blue led flicker). This is what happened to me:
0) had TWRP + latest 12.1 Cyanogenmod
1) installed the alpha 13 Cyanogenmod, which worked, more-or-less...
2) lost access to TWRP recovery, did not lose access to download
3) tried every single type of black magic from XDA (Kies, pit files, bootloader files, etc)
4) now it turns on, the LED turns blue and slowly, slowly flickers, but the screen is blank. At some point it plays the Samsung boot sound
Any help will be enormously appreciated.
check PM
bowzee said:
I have the exact same problem, some are calling it the Black Screen of Death (with the blue led flicker). This is what happened to me:
0) had TWRP + latest 12.1 Cyanogenmod
1) installed the alpha 13 Cyanogenmod, which worked, more-or-less...
2) lost access to TWRP recovery, did not lose access to download
3) tried every single type of black magic from XDA (Kies, pit files, bootloader files, etc)
4) now it turns on, the LED turns blue and slowly, slowly flickers, but the screen is blank. At some point it plays the Samsung boot sound
Any help will be enormously appreciated.
Click to expand...
Click to collapse
Another idea?
Joda899 said:
Another idea?
Click to expand...
Click to collapse
Ithink you should try re instal original firmware using odin and get ur warranty back then fix it on samsung
I found a trick that seems to help slightly, until an actual solution is published. During a misbehave episode, assuming that something shows up (which is not always the case):
1) press <power + home + vol-down> until the download thing shows up
2) press <up-arrow> so that it actually gets into download mode
3) press <power> until the screen turns off and immediately release (otherwise it will try to reboot); this makes it stay off
4) let it "rest" for a certain period of time (could be 5 minutes or more)
5) back to normal
Did u root your device vai CF auto root? Did it work?

*Help* Phone keeps on booting into TWRP and then doesn't respond.

I just flashed TWRP for the first time but it comes up with "Unmodified System Partition" but touchscreen doesn't work for some reason so I cant select anything. I tried removing the battery and rebooting my phone (Galaxy S4 19505) But it just boots back into recovery for TWRP in the "Unmodified System Partition" . Please Help, thanks.
Edit: Should I delete the TWRP disk image from my pc? (My phone also keeps vibrating while turned off). I have also noticed that there is a non physical home back and menue button, did I download the wrong version? I used the TWRP app to download and flash the image.
Hi,
Download the latest image or tar from here: https://dl.twrp.me/jfltexx/ and flash it with either Odin or Heimdall.
Not quite sure about the notice, is it on the screen that asks you if you want to keep the system partition read-only? Then you either need to swipe or click ok.
Normally flashing a recovery should not produce the problems you are describing, did you only flash the recovery?

SM-T580 Softbricked, Currently on reboot loop, can't flash any stock firmware

Here's what happened:
1. flashed wrong twrp version for 8.1 oreo, used correct CF-auto root
- tablet booted to stock recovery screen a few times but i figured it was part of the process so I just rebooted
-ended up getting a failed identification verification
-i know the auto root worked because my warranty is void :silly:
2. reset my tablet from the failed verification screen
-eventually got myself to a blue erasing screen loop
-flashed twrp again and got myself to a point where booting into recovery resulted in glitchy lines
3. attempted to factory reset from reboot with adp
-not sure if it worked tbh
-also tried to reboot to recovery screen and that didn't really do anything
4. found and installed the proper version of twrp (3.2.3-4)
-now stuck in feedback loop that occasionally shows the twerp screen so i know something's right
-won't boot to recovery screen but will boot to download page
-doesn't show up in adp devices during this loop
-- have CONTINUOUSLY tried flashing firmware (I've tried 6.0, 7.0?, and 8.1) none of them have worked, sporting some variant of secure check fail (PIT, bootloader, or RADIO)
-- have tried the mod here but it fails after param.bin and i can't use it directly after auto root without rebooting because it gets stuck on setup connection
-- most likely not a hardware problem because i had this tablet for basically a day before i did this to myself
--OEM is unlocked, not that i could change it even if it wasn't
---is there anything that anyone would recommend trying before i take this to geek squad (who may not help me but i'm still going to try) or should i just cry myself to sleep over wasting $300 :crying::crying:
abstractartemis said:
Here's what happened:
1. flashed wrong twrp version for 8.1 oreo, used correct CF-auto root
- tablet booted to stock recovery screen a few times but i figured it was part of the process so I just rebooted
-ended up getting a failed identification verification
-i know the auto root worked because my warranty is void :silly:
2. reset my tablet from the failed verification screen
-eventually got myself to a blue erasing screen loop
-flashed twrp again and got myself to a point where booting into recovery resulted in glitchy lines
3. attempted to factory reset from reboot with adp
-not sure if it worked tbh
-also tried to reboot to recovery screen and that didn't really do anything
4. found and installed the proper version of twrp (3.2.3-4)
-now stuck in feedback loop that occasionally shows the twerp screen so i know something's right
-won't boot to recovery screen but will boot to download page
-doesn't show up in adp devices during this loop
-- have CONTINUOUSLY tried flashing firmware (I've tried 6.0, 7.0?, and 8.1) none of them have worked, sporting some variant of secure check fail (PIT, bootloader, or RADIO)
-- have tried the mod here but it fails after param.bin and i can't use it directly after auto root without rebooting because it gets stuck on setup connection
-- most likely not a hardware problem because i had this tablet for basically a day before i did this to myself
--OEM is unlocked, not that i could change it even if it wasn't
---is there anything that anyone would recommend trying before i take this to geek squad (who may not help me but i'm still going to try) or should i just cry myself to sleep over wasting $300 :crying::crying:
Click to expand...
Click to collapse
Flash twrp, FORMAT (not wipe) data, install Magisk.
Reboot.
ashyx said:
Flash twrp, FORMAT (not wipe) data, install Magisk.
Reboot.
Click to expand...
Click to collapse
So just keep flashing it until i can boot to twrp recovery basically?
abstractartemis said:
So just keep flashing it until i can boot to twrp recovery basically?
Click to expand...
Click to collapse
What's stopping you boot to Download mode?
ashyx said:
What's stopping you boot to Download mode?
Click to expand...
Click to collapse
I can boot to download mode but i can't boot to recovery mode after flashing twrp. When I try I just get stuck in a reboot loop, so I can't try to boot to recovery from adp either.
abstractartemis said:
I can boot to download mode but i can't boot to recovery mode after flashing twrp. When I try I just get stuck in a reboot loop, so I can't try to boot to recovery from adp either.
Click to expand...
Click to collapse
If you can flash twrp then not booting to twrp must be pilot error.
It MUST be done immediately after flashing in odin.

Samsung S8 is stuck on start logo after flashing

Hi there. I know this question has been posted but none of the solutions is working for me.
I flashed official ROM using Odin on my S8 950FD. The process was smooth, the phone rebooted, installed update (blue screen), erased, rebooted again and then stuck on logo. I waited for a long time, then pressed Power + Vol down buttons. As soon as it turned off, I pressed Power + Bixby + Vol up. I was in stock recovery. Wiped cache and data, rebooted again, same result.
I went to download mode again, my KG state was showing Prenormal. I tried flashing TWRP, OFRP recoveries but of course got Official Binaries blah blah error. I tried flashing stock firmware again and again but no luck. All I can see on my phone is either Samsung Galaxy S8 or I can go to recovery or download mode. The phone will never boot.
I tried Miracle Box 2.82 cracked version as well, but still no luck, it shows PACKET SIZE TOO BIG or something like that.
Any chance I can get my phone working and alive again??
shoaibahmad121 said:
Hi there. I know this question has been posted but none of the solutions is working for me.
I flashed official ROM using Odin on my S8 950FD. The process was smooth, the phone rebooted, installed update (blue screen), erased, rebooted again and then stuck on logo. I waited for a long time, then pressed Power + Vol down buttons. As soon as it turned off, I pressed Power + Bixby + Vol up. I was in stock recovery. Wiped cache and data, rebooted again, same result.
I went to download mode again, my KG state was showing Prenormal. I tried flashing TWRP, OFRP recoveries but of course got Official Binaries blah blah error. I tried flashing stock firmware again and again but no luck. All I can see on my phone is either Samsung Galaxy S8 or I can go to recovery or download mode. The phone will never boot.
I tried Miracle Box 2.82 cracked version as well, but still no luck, it shows PACKET SIZE TOO BIG or something like that.
Any chance I can get my phone working and alive again??
Click to expand...
Click to collapse
What you want to do is flash full latest stock firmware for G950F (yes even tho you have fd, they are same exact device and share fw) with CSC and not HOME_CSC together with AP, BL and CP files, you can find latest firmware on samfw.com they dont have download speed limit or you can use tools that can be found here on xda for downloading samsungs latest fw.
using CSC will format device and return it to factory state
I have already done that, grabbed firmwarre from SamFW G950FXXUCDVG4 as this was what written in my Settings, VG4. I flashed AP, CP, BL and CSC using Odin in my windows and when it didn't work, did it from JOdin3 from my Mac. Nothing changed after several tries.
Any help? Did I trip the knox? The last time it happened to me, I flashed TWRP recovery and wiped/repaired file system and it worked. This time, I am unable to install unofficial binaries.
Update: I downloaded combination fw and flashed it but no luck. One thing I observed in stock recovery that it says DM-VERITY VERIFICATION FAILED. Could this be the issue? How to resolve this?

Categories

Resources