Hello all,
I'm in a bit of a fix and really need some help,
After some water immersion my Samsung S4 ceased to function, as can be expected. EDIT: (BTW this is on the Canadian version I337 as best as I know)
I dried it in silica for an extended period of time and have reached the situation where the following is possible:
Plug in and have the battery logo appear
Fiddle with the cable and power button to get the logo to show up - and it gets stuck on it
Only powers up after cable is withdrawn
Go from there to enter ODIN mode with the power and down arrow, only after this mode has been entered and exited it becomes possible to access CWM
CWM can be accessed and searching for a zip to install shows me all directories on internal storage
Cleared cache and dalvik cache
Installed what I believe is the same ROM from the external SD card (Kangapop 2.5)
Went through all steps as normal for an allegedly successful install
Still however certain things are not possible:
Back up to external SD (crashes when reaching backing up system)
Starting the phone cold regularly without fiddling with charger and power button
Getting past the Samsung S4 logo to actually boot into the ROM
In the beginning both cameras were completely soaked with water but by now all has dried.
If I could just extract a few files I would be happy to wipe everything and try further or just leave it dead, any suggestions in the mean time?
Should I use ODIN to flash the ROM? Go back to stock ROM?
If only I could get ADB to work and pull some files off...
UPDATE:
The S4 could not power up or charge at all with the old battery. Received new battery and it worked, tried Fonepaw recovery but it didn't worked, that ruined recovery to the point where it would only flash with the blue text for a moment as opposed to getting stuck like before.
I transferred the 6.0.4.4 CWM for the Canadian version I downloaded from here, now it just gets stuck on entering recovery.
The S4 cannot power up at all at the moment, probably because the new battery was barely charged and it couldn't charge while in the phone.
What should I do if I manage to power up again and get into Odin mode?
Verify the model number in download mode. If it says sgh-i337m, the phone is the Canadian version and you can flash a stock ROM from sammobile.com.
Related
Well, not really didn't test with real bullets, but I yet to brick it to a degree it makes it hard to restore, i.e. resort to using windows to run ODIN to re-flash stock firmware.
Got really close to bricking it to that point today with the lag fix that uses EXT4.
The phone started FC while copying the data to a new ext4 formated partition, and it looked like it reloaded but the uptime never showed the full powerdown. So, on it came back up I was back to TW with a bunch of apps missing including the ROM Manager, and market
As suggested by a member here I manually boot it into clockworkrecovery (moved recovery-update.zip into /sdcard as update.zip and adb reboot recovery), once in CWMR I restored from the latest nandroid backup and volia! I am back.
Well, it goes back under the warranty replacement anyway because of the bad 3.5 mm jack
I hopethe replacement does not disappoint.
Odin froze up on me during a flash last night and I couldn't get the phone to power on at all. No recovery mode, no download mode...I couldn't even get the charging indicator to come on when I plugged in the USB. It was TOTALLY DEAD...no signs of life at all whatsoever.
After about an hour and a half of fiddling, I found that if I
removed the battery
removed SD card and SIM card
plugged into USB on the PC
held down vol-up and vol-down
popped the battery back in while holding vol buttons
unplugged from USB
I could get it to start in download mode. What a huge relief. After a few more tries I was able to get Odin to finish flashing the stock firmware. I was sweating for a while there.
Hear you man. I weary of odin I hope there will be a way to flash from linux in the future
Sent from my SGH-T959 using XDA App
Hi,
Just wanted to share my experience getting JPC Rom installed and rooted.
Prior to upgrade, I had the JP3 Rom, rooted with clockwork and 1-click lag fix.
I had some major issues installing JPC. In fact, I ended up with the dreaded USB logo a few times.
This is not a complete guide, but hopefully it will help avoid the problems I had.
1) Before installing the new rom, I strongly suggest that you Factory Reset the phone.
2) Install the JPC Rom using the other guides on this page. I used Odin and choose Repartition to get a clean install.
3) Here is where the problems started. After the rom installed cleanly and the phone rebooted, it would get stuck on the second Samsung logo and eventually go black. This happened to me twice. The fix I found out, is to go into Rececovery mode (Vol Up, Home, Power) after the install and clear the cache, reformat SD and factory reset. After you do this the phone will boot normally.
4) After that I followed the rooting guide on this forum, but ended up with the dreaded USB logo. If this happens to you, just go back into DOwnload mode and reflash with Odin again (following the guide in this forum)
IMPORTANT: I have TWO galaxy s phones. The strange thing is, one of them is VERY easy to get into Download or recovery mode. The other is almost impossible. For those of you that have a similar model to me that seems like it does not have a 3 button download or recovery mode you probably do.
I thought I was bricked, and tried for over an hour to get my second phone into download mode (take out battery, hold three buttons, put in battery, over and over again). I was about to give up, but found I was able to get the phone into download mode if I ....
1) Take Battery Out. Put it back in.
2) Plug phone into USB on computer (do not turn it on)
3) Now try to do the 3 button Download mode. Press all three buttons at one time and release power about 1 second after seeing Samsung logo.
Again my second phone I can very easily get to download mode 100% of the time. I am really not sure why the two phones would be any different. I hope this helps people that have a stubborn phone like mine.
P.S. I did not install Clockwork on JPC, but I did root the phone and installed 1 click lag fix. Phone is running VERY stable and all features seem to work (including Mobile AP).
I hope this helps others like me who tried to install update.zip as explained in some posts & got the dreaded USB logo on boot & didn't know what to do because I am sharp but no programming & all that. I got mine to go ahead ONLY after I put in my SIM & External SD card. With both OUT, I get the USB logo 100% of the times.
I hope this helps.
Ive installed jpc a few time now and a factory reser after flashing did it for me every time
Hello All -
My wife got a new S7 Edge, so I thought I would update from my N2 to her N3.
I originally rooted it before the bootloader got locked down, flashed a stock modified KK 4.4.2 ROM, and prevented further OTAs.
I can't recall if I installed a custom recovery, so i tried it and in the upper left hand corner it says Recovery Booting..., it fails to enter recovery mode and then rebooted normally.
So I installed Safestrap, booted into recovery, and backed up the Stock ROM slot. I then did a Factory Wipe and Advanced Wipe the system partition as per the instruction to install Jasmine ROM.
I choose then chose reboot into Recovery again so that I could use the SD Card to install Jasmine. Unfortunately, I'm stuck in a bootloop where it says Recovery Booting... and never gets back into Safestrap.
I've tried holding down the Power Button, Volume Up or Down, and Home and I can't get into recovery or download mode.
I also tried using a USB Cable plugged into my PC and the button combo thing, but no luck.
Any ideas guys?
Thank you in advance!
Pull the phone battery.
Wait 5 or more seconds.
Reinsert battery.
Start phone with Vol-Down + Home + Power. (as if you wanted to use Odin Download mode)
When the "do you really want to do this?" dialog pops up, select cancel.
This will boot to the normal OS (and also clear the boot communication block so that the next time you reboot it doesn't try to boot the recovery again)
For some reason this sequence won't work if you omit the battery pull. (Don't leave it plugged in to USB or a charger, either)
It works this way with MJ7 firmware; since this is a bootloader behavior, it is possible that it won't work the same way with later firmwares. Simple enough to try and find out though.
good luck
Good news!
I was about to select download mode finally, but only after I removed the SIM card!!
I odin'd 4.3 stock, towel-rooted, safestrapped, and installed Jasmine.
Thanks again all!
So I don't really know how to describe this best but I'll try to explain it.
So my fathers old S4 just randomly crashed one day and when he tried to boot it back up it just got stuck on the boot screen. And since it was beginning to get old anyways he decided to get an new phone and ended up getting an S8.
His pictures and such were stored on an SD Card so he was able to easily move those files over. But since it refused to boot back up he couldn't get the files of it. And so I decided to try to help him as I'm quite familiar messing with Android and so I flashed TWRP on there to try to get the files of it as I knew that TWRP has support for MTP.
But just one problem, when I had moved about 40% of the files it just randomly crashed again. And now I can't get into the recovery anymore as it just gets stuck on Recovery booting. And most times it wont even react to me holding the power button or plugging it in.
I decided to reflash TWRP and it's still not working and the issue described above is still true.
Any ideas on how to get those files of it? :|
Once I get those files off I will reflash stock and see if everything is working but I wont reflash stock through Odin until the files are on my PC.
Thanks for any help!
Tested:
Download mode - Succesfully got into, can flash through Odin. (Edit: 2018-06-29, trying to flash TWRP again, Odin gets stuck on "Initializaltion")
Recovery mode - Used to work but phone crashed during MTP file transfer and now it gets stuck on recovery booting (I have TWRP flashed).
Starting - Stuck on Samsung Galaxy S4 logo, wont even go past to the animated Samsung one.
Safe mode - Not sure if it registred as me going into safe mode, but it did show the animated Samsung logo until it froze after about 10 seconds and a few seconds after that the screen went black, but the notification LED was still on.
Charging - When I first tried charging it after the file transfer failed (It was at 10% according to TWRP during the file transfer and it was only about 7-8 GBs of files and I thought that it should last for long enough while being plugged in) the phone didn't respond in any way, after a while it started to heat up so I knew it was charging. Then after trying some more things I plugged it in again this time it showed the logo it shows right before it starts showing you the charging animation but got stuck there. Then just now when I plugged it back in it got past that and showed the actual animation, but just when I was hoping it had started functioning as it should it just crashed and the screen went black. This is a reocurring problem with basically all parts of the system, the screen goes black and it doesn't vibrate or anything, and after this happens I can't turn it on until I've taken the battery out and let it rest for a few moments.
*Edit: After testing all of these things I realise that the title of this thread is a bit missleading, but I hope you understand.
*Edit 2: In download mode it says that Binary and System are custom even though I haven't modified it more than installing TWRP? Other things it says: KNOX Kernel Lock: 0x0. KNOX Warranty Void: 0x1. CSB-CONFIG-LS0: 0x30. WRITE PROTECTION: Enable. eMMC BURST MODE enabled. (I think this is what might be causing the issue but have no idea on what it is yet)
The problem isn't that eMMC Burst Mode is enabled, as that is normal for the S4. What you're dealing with is an eMMC failure. In short, the flash memory has gone belly up and died on you. You can try flashing again through Odin using a PIT file, but I believe your dad's S4 is now only suitable for spare parts.
Strephon Alkhalikoi said:
The problem isn't that eMMC Burst Mode is enabled, as that is normal for the S4. What you're dealing with is an eMMC failure. In short, the flash memory has gone belly up and died on you. You can try flashing again through Odin using a PIT file, but I believe your dad's S4 is now only suitable for spare parts.
Click to expand...
Click to collapse
I was kinda thinking that was the problem, what exactly would flashing the PIT file do and would it wipe /data? Also, thank you so much for the help as I wasn't exactly sure what the eMMC Burst Mode meant and thought that it might have been the problem.
PIT = Partition Information Table. Using one will re-partition the internal storage. It can correct corruption, but at the price of the data on the device. Realistically, I don't think the PIT file will help here. The eMMC would have to be replaced, which is simply not worth doing for a five year old device.
Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.
PinkElf said:
Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.
Click to expand...
Click to collapse
Hi, try to flash the stock firmware otherwise I really don't know :/
I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?
PinkElf said:
I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?
Click to expand...
Click to collapse
Are you using Lineage OS? If yes, then definitely yes. On my Xiaomi, I couldn't get into fastboot mode or into recovery, I don't know why and somehow I got there, I don't even know how I think I held the power mode for a long time and when the phone turned on I held the volume up button to get into recovery finally succeeded on the umpteenth attempt and from recovery I restarted the phone in fastboot mode and flashed the stock firmware. And yes, being able to boot your phone into fastboot is a good sign. It would be worse if it wasn't possible.
I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.
PinkElf said:
I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.
Click to expand...
Click to collapse
Yes, you can use download mode to install the firmware via Odin. Look
That means giving up hope for my personal data...
But even if I want to do this, I run into the problem, that I can't install anything due to "could not find PIT partition"...