My setup: I am rooted, with Philz Touch installed and Xposed frameworks.
I have made a backup using Philz Touch.
When I finally finished my customisation, my phone was running great for a few days, however the screen began to play up.
Occasionally, when using apps such as Facebook and Whatsapp, the image on half the screen would freeze, and the other half of the screen would be functional. This split would be straight down the middle of the device vertically.
If I proceeded to switch the screen off, I would be unable to switch the screen back on. I can hear the system being active, vibrations such as taking the S-Pen out still work, but the screen will remain black.
A soft reboot fixed this the first few times, but now my display is completely black when the phone switches on. Again I can hear the phone being switched on and running fine, but the display only shows black.
I guess there is a problem with one of the Xposed frameworks but I can't uninstall any without being able to use my screen.
Somebody please help!
Is it possible to use an MHL adapter and connect the phone to an HDMI port on your monitor or TV to see what you can't see on the phone itself? It's definitely software related.
TsunKit said:
My setup: I am rooted, with Philz Touch installed and Xposed frameworks.
I have made a backup using Philz Touch.
When I finally finished my customisation, my phone was running great for a few days, however the screen began to play up.
Occasionally, when using apps such as Facebook and Whatsapp, the image on half the screen would freeze, and the other half of the screen would be functional. This split would be straight down the middle of the device vertically.
If I proceeded to switch the screen off, I would be unable to switch the screen back on. I can hear the system being active, vibrations such as taking the S-Pen out still work, but the screen will remain black.
A soft reboot fixed this the first few times, but now my display is completely black when the phone switches on. Again I can hear the phone being switched on and running fine, but the display only shows black.
I guess there is a problem with one of the Xposed frameworks but I can't uninstall any without being able to use my screen.
Somebody please help!
Click to expand...
Click to collapse
arjun90 said:
Is it possible to use an MHL adapter and connect the phone to an HDMI port on your monitor or TV to see what you can't see on the phone itself? It's definitely software related.
Click to expand...
Click to collapse
Unfortunately I don't have a MHL adapter, I may pick one up tomorrow if it means fixing my phone though.
I hope it is software related, but that really could go either way. Can you get into recovery, and does your display work then? If so, you could flash a stock ROM and see if your screen is working. If not, you might need warranty replacement. Hoping for the best, good luck.
screen problem
Hi
I had the exact same problem brand new out of the box with my Note 4 (N910G). I had it replaced by the retailer as it was clearly faulty as I hadn't installed any software or modifications.
1st power up resulted in no display and just a blank screen, but I heard the startup melody. I somehow managed to get the accessibility features running without a screen and it was reading out what was supposed to be there, but still no display. I could also feel the vibrations when taking out s-pen as you describe.
I managed to get the screen sort of working by putting some light pressure around the frame of the screen and it started to work normally, but after a reboot and just randomly over the next 24 hours I had the split screen issue you describe - vertically down the middle. Frozen on the left side, but the right moved. I took it back the following day and luckily I was able to replicate the problem in front of the staff so they just replaced it. The fact that I could get it to work by putting pressure around the screen lead me to believe it was a hardware fault.
Looks like a glitch in manufacturing.. oooo scary
Bemathkata said:
Hi
I had the exact same problem brand new out of the box with my Note 4 (N910G). I had it replaced by the retailer as it was clearly faulty as I hadn't installed any software or modifications.
1st power up resulted in no display and just a blank screen, but I heard the startup melody. I somehow managed to get the accessibility features running without a screen and it was reading out what was supposed to be there, but still no display. I could also feel the vibrations when taking out s-pen as you describe.
I managed to get the screen sort of working by putting some light pressure around the frame of the screen and it started to work normally, but after a reboot and just randomly over the next 24 hours I had the split screen issue you describe - vertically down the middle. Frozen on the left side, but the right moved. I took it back the following day and luckily I was able to replicate the problem in front of the staff so they just replaced it. The fact that I could get it to work by putting pressure around the screen lead me to believe it was a hardware fault.
Click to expand...
Click to collapse
Thank you for this reply.
Right now the phone is back on and working, after a DAY of rebooting.
Hearing this does suggest it is a hardware fault, so I shall be heading to Carphone Warehouse in an attempt to get it exchanged. Will there be any issues returning a rooted device?
rcobourn said:
I hope it is software related, but that really could go either way. Can you get into recovery, and does your display work then? If so, you could flash a stock ROM and see if your screen is working. If not, you might need warranty replacement. Hoping for the best, good luck.
Click to expand...
Click to collapse
I'm reluctant to flash a stock ROM after hearing the above response. I'm going to see what Carphone Warehouse is able to do first before I tinker with it anymore.
Will I still be entitled to my warranty privileges after rooting my device?
Rooting usually isn't an issue but I always go back to stock before returning a device.
rcobourn said:
Rooting usually isn't an issue but I always go back to stock before returning a device.
Click to expand...
Click to collapse
Going to return to stock now.
Do you know where I can find the stock recovery.img for the Note 4? Had no luck searching for it currently.
EDIT: Searched properly, CF Root installs stock recovery.
rcobourn said:
Rooting usually isn't an issue but I always go back to stock before returning a device.
Click to expand...
Click to collapse
Just a comment on that: Always a good idea...
Staff in the stores usually doesn't know how to check if your device is rooted (or if the dreaded Knox counter is on 0x1) - but they all know how the regular Samsung UI looks like.
So chances are far better if your device just looks like never being rooted.
That's why you'd go with the stock firmware prior to showing your device to anyone at the store.
I'm having issues returning to stock.
This is what the Odin screen looks like after failing.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910FXXU1ANJ4_N910FEVR1ANJ1_N910FXXU1ANJ4_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> modem.bin
<ID:0/006> cache.img.ext4
<ID:0/006> hidden.img.ext4
<ID:0/006> RQT_CLOSE !!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas?
Since it failed the first time, I have been unable to boot my phone as well. My problems seem to only be getting worse.
Related
Today my phone randomly restarted. Then it started acting very strange, bluetooth failing etc.
I got home and then in restarted one last time. Couldnt use the screen, tried to slide to unlock and nothing happened. Wouldnt detect my finger.
So i soft reset.
The phone started up, (unlocked) and i was able to use the hard buttons. Screen still not working.
Finally restarted on its own again, and got the message "microp version mismatch 0, Please Update Latest Microp Firmware"
Screen wont even turn on now.
O2 are going to replace. However they are out of stock currently.
Anyone got any ideas why this has happened? and will it happen again, i.e fault unstable design of phone, or did I just get a duff one?
PS I did not flash the rom or anything. Only used BSBtweeks.
Don't worry. Odds are you get a good one next try. At least you did the right thing sending it back straight away. It saved you many frustrated hours
4tune said:
Don't worry. Odds are you get a good one next try. At least you did the right thing sending it back straight away. It saved you many frustrated hours
Click to expand...
Click to collapse
I use some magnets to stick the phone to my dashboard.
Just checking could this have caused it?
up.
same to me here.
up................................
So, I would appear to have done something nasty to my SGS. Right now I don't seem to be able to even turn it on. A few minutes back, it would turn on, but I would have a phone and PC seperated by --!-- on the screen.
I can get into 'download mode' though. I just don't seem to be able to flash anything to it...
It either gets to 'DO NOT TURN OFF TARGET!!' and then does absolutely nothing, or it goes about 10-15% on the Odin progress bar, the screen goes all one colour (red, grey, white) and the progress bar goes no further.
Do you think the on board memory has become corrupted?
I'm using Odin3 v1.0 with Pit512 and a whole variety of different firmwares. I was on JG5 with the redirect to a partition on the SD card for speed fix.
As I type this, finally I've managed to flash JM1 on, but as it boots, after the animation, the screen stays blank, with the two side buttons lit up.
Any ideas?
In the end I rebooted my PC, just kept trying and eventually one went through... how odd. Took 2 to 3 hours
All seems to be working now though, with speed fix too
Hey! I got sort of the same problem... Black screen with the side buttons lit up, after some flashing.
What firmware did work for you at last?
Ciao!
Erm, the last 2.1 firmware... JG2? All 3 components of it. (Code, CSC and Phone)
Skip the next paragraph if you aren't interested in the water damage story...I'd like to pull anything off the internal memory if possible, then restore the phone to factory settings. I'm already getting a replacement, so my hope is to sell this as a water damaged phone (possibly just for parts) to recoup some of my replacement cost. I don't want to pass on my personal data and Google Account to the buyer though. Relevant details below.
My GS4 had an unfortunate trip through the washing machine on Saturday night. I tried a space heater+rice on the first night and got nothing the next morning. I tried without the battery and just a charging cable and still nothing. Last night I took apart the phone (using iFixit teardown/repair guides) and used Qtips and 90% isopropyl alcohol (IPA) to go over any parts of the phone which looked like water might have gotten to. I also submerged and rinsed the whole motherboard in IPA. After letting everything dry over night, I was able to turn on the phone with just a charging cable. I checked the voltage on the battery and it was 3.3 V. I think the nominal voltage is much higher (my old Nexus S 4G was above 4 V), so I'm guessing the battery is dead or close to it.
At the moment, the phone turns on but gets stuck on the white Samsung Galaxy S4 boot screen. If I use volume up+power I get a tiny blue "BOOTING RECOVERY..." in the top left, but nothing happens after that. I'm guessing the memory is partially corrupted. If I use volume down+power+home I get into download mode. I can select continue, and then it looks like I'm in download mode. It has the normal Android guy/Downloading...Do not turn off target and in the top left it says:
Code:
ODIN MODE
PRODUCT NAME: SPH-L720
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
Before the water damage the phone had MF9 rooted (CF Auto root) + hotspot mod. I used CWM recovery instead of TWRP. I hadn't updated to MJA yet, though I had the notification that wouldn't go away.
So questions:
So is there a way to access the internal memory if I can't get into recovery? Can I check if it's intact, if it's corrupt but reflashable, or if it's unusable? I assume if ODIN will fail in some way if it's unusable, but I wanted to check before I started flashing in case I could recover anything. If ODIN fails at flashing, is there a way to erase all my personal data (NAND Erase all)?
If I do try to reflash, I guess first go straight back to stock recovery and then the stock MF9? (as described in step 2 of this thread). Do I need to rewrite the PIT as described here?
Does anyone know if the battery charges during the bootscreen/recovery/download mode? Doesn't look like mine is charging, but I thought I'd check.
i have done some bad things to my s4 but no doubt water is probey the worse, even if u recover it you more than likely u will have touch screen issues at the least but after saying that i would start with flashing recovery with odin. if u get that far with it.. oudhs recovery isnt fancy but will work with out touch input
An update for those interested, and some more questions.
Thanks to many posts on this forum and a few others, I was able to recover my data from the phone. After I got into recovery I was able to use ODIN to return to stock (approximately following the directions here). I was rooted stock with CWM, and this brought me to stock with stock recovery. I did all this without the battery in the phone and just connecting it to the computer USB. I charged the battery with a separate charger and then tried to reboot, but it was stuck. I was able to boot into stock recovery, and I had the normal options plus a green android icon with a red exclamation in the middle of the screen. I think I used a multi CSC version of the MF9 and that brought up the error. When I rebooted from there the phone started up! I had expected the phone to be wiped, but it booted up as if it hadn't missed a beat.
I was able to do a few quick backups from there and upload the files to Dropbox before the battery died. Later I flashed Philz recovery and was able to backup everything to a separate SD card for later use. The phone still has multiple problems though.
The phone won't charge the battery and the phone won't connect to the computer by USB when normally powered on. Download mode works though. The phone reports the battery at 100% and won't charge it. If you pull the battery while on, but connected to power, it won't stay on. You can pull the battery while plugged in download mode. I checked with a good battery and the behavior is the same. I assume some USB circuit is fried, and I've found other reports but I haven't tracked down the definitive cause.
Now that I have my data off, I'm going to wipe everything in Philz recovery (which is great, BTW) and once again flash to MF9 total stock so that I can sell the phone for parts or repair. Thanks to all the people who put work into the development of all these tools and all the people who participate in the discussion.
water damage
ramk13 said:
Skip the next paragraph if you aren't interested in the water damage story...I'd like to pull anything off the internal memory if possible, then restore the phone to factory settings. I'm already getting a replacement, so my hope is to sell this as a water damaged phone (possibly just for parts) to recoup some of my replacement cost. I don't want to pass on my personal data and Google Account to the buyer though. Relevant details below.
My GS4 had an unfortunate trip through the washing machine on Saturday night. I tried a space heater+rice on the first night and got nothing the next morning. I tried without the battery and just a charging cable and still nothing. Last night I took apart the phone (using iFixit teardown/repair guides) and used Qtips and 90% isopropyl alcohol (IPA) to go over any parts of the phone which looked like water might have gotten to. I also submerged and rinsed the whole motherboard in IPA. After letting everything dry over night, I was able to turn on the phone with just a charging cable. I checked the voltage on the battery and it was 3.3 V. I think the nominal voltage is much higher (my old Nexus S 4G was above 4 V), so I'm guessing the battery is dead or close to it.
At the moment, the phone turns on but gets stuck on the white Samsung Galaxy S4 boot screen. If I use volume up+power I get a tiny blue "BOOTING RECOVERY..." in the top left, but nothing happens after that. I'm guessing the memory is partially corrupted. If I use volume down+power+home I get into download mode. I can select continue, and then it looks like I'm in download mode. It has the normal Android guy/Downloading...Do not turn off target and in the top left it says:
Code:
ODIN MODE
PRODUCT NAME: SPH-L720
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
Before the water damage the phone had MF9 rooted (CF Auto root) + hotspot mod. I used CWM recovery instead of TWRP. I hadn't updated to MJA yet, though I had the notification that wouldn't go away.
So questions:
So is there a way to access the internal memory if I can't get into recovery? Can I check if it's intact, if it's corrupt but reflashable, or if it's unusable? I assume if ODIN will fail in some way if it's unusable, but I wanted to check before I started flashing in case I could recover anything. If ODIN fails at flashing, is there a way to erase all my personal data (NAND Erase all)?
If I do try to reflash, I guess first go straight back to stock recovery and then the stock MF9? (as described in step 2 of this thread). Do I need to rewrite the PIT as described here?
Does anyone know if the battery charges during the bootscreen/recovery/download mode? Doesn't look like mine is charging, but I thought I'd check.
Click to expand...
Click to collapse
I dropped my S4 in the toilet last week. I was able to recover it fully. here's what I did- dont turn it on!! I took my off back cover battery sd card etc...took a super strong shop vac adn vaccuummed it for about 20 minutes in all the holes over and over again. then I stored it in a bag of rice for about 8 hours- turned it on and boom no problems.
Water Damage wRepair
Read, what i've written after your Post Quote
ramk13 said:
Skip the next paragraph if you aren't interested in the water damage story...I'd like to pull anything off the internal memory if possible, then restore the phone to factory settings. I'm already getting a replacement, so my hope is to sell this as a water damaged phone (possibly just for parts) to recoup some of my replacement cost. I don't want to pass on my personal data and Google Account to the buyer though. Relevant details below.
My GS4 had an unfortunate trip through the washing machine on Saturday night. I tried a space heater+rice on the first night and got nothing the next morning. I tried without the battery and just a charging cable and still nothing. Last night I took apart the phone (using iFixit teardown/repair guides) and used Qtips and 90% isopropyl alcohol (IPA) to go over any parts of the phone which looked like water might have gotten to. I also submerged and rinsed the whole motherboard in IPA. After letting everything dry over night, I was able to turn on the phone with just a charging cable. I checked the voltage on the battery and it was 3.3 V. I think the nominal voltage is much higher (my old Nexus S 4G was above 4 V), so I'm guessing the battery is dead or close to it.
At the moment, the phone turns on but gets stuck on the white Samsung Galaxy S4 boot screen. If I use volume up+power I get a tiny blue "BOOTING RECOVERY..." in the top left, but nothing happens after that. I'm guessing the memory is partially corrupted. If I use volume down+power+home I get into download mode. I can select continue, and then it looks like I'm in download mode. It has the normal Android guy/Downloading...Do not turn off target and in the top left it says:
Code:
ODIN MODE
PRODUCT NAME: SPH-L720
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
Before the water damage the phone had MF9 rooted (CF Auto root) + hotspot mod. I used CWM recovery instead of TWRP. I hadn't updated to MJA yet, though I had the notification that wouldn't go away.
So questions:
So is there a way to access the internal memory if I can't get into recovery? Can I check if it's intact, if it's corrupt but reflashable, or if it's unusable? I assume if ODIN will fail in some way if it's unusable, but I wanted to check before I started flashing in case I could recover anything. If ODIN fails at flashing, is there a way to erase all my personal data (NAND Erase all)?
If I do try to reflash, I guess first go straight back to stock recovery and then the stock MF9? (as described in step 2 of this thread). Do I need to rewrite the PIT as described here?
Does anyone know if the battery charges during the bootscreen/recovery/download mode? Doesn't look like mine is charging, but I thought I'd check.
Click to expand...
Click to collapse
Maybe you've been to unpatient.
Try letting for a week in the rice or 20 min destilled water (do replace water with destilled water inside of the phone) and then Isopropanôl-Alcohol. Well... 90% must be enough but try letting longer in by being more patientionary!
Very Important informations inon my Posts here! (Last Pages = 5 or 9/10 depends on something that i don't know )
Wish you a nice day, have a nice day.
I hope i could help you. If i did help anyone, then „Thank me! “
4900d
Hello,
My Samsung Galaxy S5 has been restarting on its own since yesterday. I first tried to turn off my phone and when I press power off it instead restarts. I then decided to back up my important stuff and factory wipe the phone from the android operating system and clear the cache. Both of those things also didn't work. I then tried to adjust the battery a bit even putting a small piece of paper in the very thin gap to seal up any space and that also didn't work. The phone is still restarting randomly. I tapped on the power button assuming it might be stuck and it clearly isn't. A definite click and it feels comfortable. Going into safe mode on the phone also hasn't helped as the phone still restarts. I truly am stuck. Any help would be appreciated!
Thanks,
Jordan
A good thing to try is flash in odin the same firmware you are currently on you can check which firmware you are on by booting to recovery mode and check what it says there then download firmware from sammobile.Com
Sent from my iPhone using Tapatalk
I did flash my phone using Odin to the latest firmware for S5 6.0.1. Would this potentially be causing the issue? My phone was randomly restarting before I flashed it as well on my old firmware.
I did go ahead and re-flash the firmware that I installed and it has continued to do the same thing.
is your phone very hot when it restarts
Sent from my iPhone using Tapatalk
After several restarts the phone does start to get pretty warm
So your phone is not rooted? No custom kernel?
Sent from my SM-G900V using Tapatalk
---------- Post added at 07:19 PM ---------- Previous post was at 07:12 PM ----------
If your not rooted then the next step is to have the latest firmware and flash it in odin but check these options In odin reparatition and nand erase and put a g900v pit file in the appropriate slot and leave what is checked by default checked also in odin
Then flash it will softbRick boot to recovery and wipe cache and data then boot to download mode and flash latest firmware with only default options checked it should boot and tell me if you still have an issue
Sent from my SM-G900V using Tapatalk
Riley4376 said:
Hello,
My Samsung Galaxy S5 has been restarting on its own since yesterday. I first tried to turn off my phone and when I press power off it instead restarts. I then decided to back up my important stuff and factory wipe the phone from the android operating system and clear the cache. Both of those things also didn't work. I then tried to adjust the battery a bit even putting a small piece of paper in the very thin gap to seal up any space and that also didn't work. The phone is still restarting randomly. I tapped on the power button assuming it might be stuck and it clearly isn't. A definite click and it feels comfortable. Going into safe mode on the phone also hasn't helped as the phone still restarts. I truly am stuck. Any help would be appreciated!
Thanks,
Jordan
Click to expand...
Click to collapse
This could be a damaged battery. My phone did this previously and changing to a brand new battery fixed it. Have you dropped your phone before or was it preowned?
My phone is encased in an Otter Box and I've maybe dropped it once or twice in a light fall. The battery still charges well and has no physical signs of wear. The phone is not preowned as I bought it new. Hauckk I will definitely want to try that. Thank you so much for your help so far everyone. I'll let you know the results of what I find.
Riley4376 said:
My phone is encased in an Otter Box and I've maybe dropped it once or twice in a light fall. The battery still charges well and has no physical signs of wear. The phone is not preowned as I bought it new. Hauckk I will definitely want to try that. Thank you so much for your help so far everyone. Only question I have is could you re-explain this in a different way? I am just not understanding this part. :/ Sorry! Thanks again. "but check these options In odin reparatition and nand erase and put a g900v pit file in the appropriate slot and leave what is checked by default checked also in odin"
Click to expand...
Click to collapse
Even a light drop can mess up your battery. I had an OtterBox and my phone feel from a bus seat to the floor of the bus and it was enough to mess up the battery internally, as mine had no physical signs of damage either. It's most likely either the connection inside the battery or your phone and not a software/firmware issue. Still, do what Hauckk is instructing you to do and if that fails it's definitely your battery or possibly the phone itself.
A translation of his instructions:
Check the nand erase and repartition options in Odin, these should be next to the slots to put files in. After that download a g900v pit file off the internet and hit the pit button that should be above AP/PDA depending on the version you are using. It will give you the option to choose a file, select the pit file you have downloaded.
The locations of the options described are circled
WhiteHawk I really do appreciate the fast responses. I'll let you know the results as soon as possible.
Thank you,
Jordan
My boyfriend put my battery in his phone and it crashed so I know for sure its the battery. Thank you both so much for the assistance. I really do appreciate this forum. You both are wonderful!
Best Regards,
Jordan Schoenmann
We switched batteries but the phone is now restarting when I choose power down. As far as I know, the phone is not restarting on its own anymore but the phone restarts instead when I chose the power off option. Any suggestions? Thanks.
Jordan
Phone just restarted on its own which means that it seems to still be performing the same problem as before with the suggestion to flash and put a pit file in. Any more help would be appreciated. Thanks
The phones battery is definitely one of the issues as it caused my boyfriends phone to shutdown and restart as well. However even with my boyfriend's battery in my phone, it still restarts. The phone freezes for a few seconds and then restarts.
Riley4376 said:
The phones battery is definitely one of the issues as it caused my boyfriends phone to shutdown and restart as well. However even with my boyfriend's battery in my phone, it still restarts. The phone freezes for a few seconds and then restarts.
Click to expand...
Click to collapse
You're welcome for the help!
If the phone is still restarting it could possibly be an issue with the internal connection to the battery port in the phone. You might need a replacement or repair.
My G900V was working fine, until all of a sudden it just... died. Kind of.
When plugging it in, nothing appears on the screen for 48 hours. After around 48 hours of being plugged in, the charging lightning bolt (sometimes) comes on, but does not proceed to the charging animation. Other times, it just sticks at the S5 screen. The power button does work, but it will not vibrate or boot when attempting to power on; it will only boot at will when plugged in for 2 days.
The last time it did turn on, it was after a factory reset where I miraculously managed to boot it into download mode. Using the Verizon SUA, it restored the firmware. However, during setup, it crashed at some point and hung on the S5 screen again. I read somewhere that leaving it in a freezer for 10 minutes can help, and sure enough, leaving it outside in this Chicago weather gave me a narrow shot at putting it into download mode. It's plugged into the computer and awaiting its update from the SUA.
What on earth could this problem be? I know that this phone had no problems up until its death. I do believe I got some modem errors when trying to resurrect it though. I tried putting an S4 battery in to see if it would boot normally (in an attempt to rule out battery failure), but the outcome remained. Putting the S5 battery in the S4 went fine as well, and I didn't notice any problems during operation, so I'm almost certain it isn't a battery problem.
Sometimes, it will try to get past the S5 screen, other times it just hangs. When it tries to though, the display glitches slightly and it vibrates twice, before returning to the S5 screen.
I sent the phone to a Samsung plant in Plano, TX to have it checked out, and even they were stumped. I have never in my life seen a phone act this way, and any input or advice would be appreciated. Thanks for reading!
Sure enough, the restore failed. I received a "SECURE CHECK FAIL: aboot" message, which I hear is because of flashing the incorrect baseband. How could the official Verizon tool flash the wrong baseband? The name of the .md5 is "ALL_VZW_G900VVRU2DQI2_G900VVZW2DQI2_CL8025411_QB15163032_REV00_user_low_ship_MULTI_CERT.tar.md5". I have no way to boot the phone, so I cannot check what baseband was previously installed. Any ideas...?
dzvxo said:
My G900V was working fine, until all of a sudden it just... died. Kind of...
Click to expand...
Click to collapse
Your best bet is to take a look at the following threads and, if needed, post your question within one of them.
https://forum.xda-developers.com/showthread.php?t=2784860
https://forum.xda-developers.com/showthread.php?t=3319848
https://forum.xda-developers.com/showthread.php?t=2700073
https://forum.xda-developers.com/showthread.php?t=2784880
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE