Related
Starting to get frustrated. When I got the Galaxy Tab 10.1 from I/O it originally had a severe back-light bleed which I described in this thread:
http://forum.xda-developers.com/showthread.php?t=1076349
Samsung Level 3 Support was quite awesome and sent out a replacement. The back-light bleed is still somewhat present, but not nearly as bad. So a few weeks have passed and ran into another major issue: it entered a infinite reboot loop.
I have only about 10 apps or so installed from the "Featured" section in the Android Market. I have never bothered rooting this, dealing with custom ROMs, or anything of that sort.
I just get white text on the display with a black background which says:
Entering upload mode...
Upload_Cause: undefined
Holding down the power button again just takes the tablet into a infinite reboot loop. I see the start up animation and the Samsung logo, then it repeats over and over.
Samsung just set up a RMA to get this re-flashed. Anyone else have this issue? Is there an easy solution to solve this without having to send it back in?
Thanks!
And I have the same issue here any help guys!!
same issue, looking for a solution
exact same issue. Any solution or suggestions?
I have the I/O tab, unrooted. I had the exact same issue. Just overnight the tablet went bonkers. The tablet would continually load the Samsung Splash screen over and over. If I tried to wipe the table, I got Entering upload mode, Upload undefined error. I sent my tab in after pulling my hair out trying to get a fix. I couldn't even work on the tablet because it would not hold a battery charge. Some process was constantly draining the battery. I personally wish thye would just give me a production tablet. I'm afraid that when I get it back, the problem will re-occur.
I have the regular retail version. I've had it for about 9 days and have used it every single day. Last night I downloaded 2 movies onto it and everything was fine. Today it would not power on one bit! I charge it over night so the battery shouldn't have drained. Anyone experience this before???
Nevermind: Fixed my problem by doing the following!
Press and hold the on button.
At the same time, keep a finger on the screen.
Keep watching and you might see a slight change of color on the screen.
Hold it down for 15 seconds or more. Be patient.
IO Boot Loop
same issue for me - working great then all of a sudden it froze, i rebooted and got stuck in boot loop
tried:
ODIN flash recovery - still boot loop
NVFLASH recovery - installed but cannot get into recovery mode -only fastboot and ODIN
FASTBOOT mode - adb not seeing device even though ODIN sees it - installed PDANet to get Android USB driver - still not seeing device
any thoughts?
sINCE THE release of touchwiz roms, a bootloader file is included as bootloader.tar.md5. Flashing this (repartition unselected in odin) gives you retail like options in boot screen with keys combo viz. recovery and odin. Try extracting and flashing the bootloader file from stock roms I uploaded.
COUNT:5 repetitions of this solution!Gladly, though one should bother to search!Or check the similar threads suggested when starting a thread.
thanks mughalgxt - where might this bootloader.tar.md5 be downloaded? To clarify did you mean by the extracting comment below that the bootloader you provided already contains this update?
also as for repetition - since i am still looking for a solution and some of those thread have the same symptoms (boot loop) but different solution methods (nvflash, odin, fastboot) - i thought it might make sense to add my description to my issue to apply additional context/clues
mughalgxt said:
sINCE THE release of touchwiz roms, a bootloader file is included as bootloader.tar.md5. Flashing this (repartition unselected in odin) gives you retail like options in boot screen with keys combo viz. recovery and odin. Try extracting and flashing the bootloader file from stock roms I uploaded.
COUNT:5 repetitions of this solution!Gladly, though one should bother to search!Or check the similar threads suggested when starting a thread.
Click to expand...
Click to collapse
I had uploaded a stock euro rom(check under arabic rom topic in development section), courtesy of samfirmware.com. You can extract the bootloader.tar.md5 file from the rom rar file. This will help you to force key into recovery as the boot options will be replaced from fastboot to recovery. Just make sure you don't select repartition while flashing with odin as that'd leave you bootloader locked!
Hope this clears up! Once in recovery, the options are endless!
lost2030 said:
I have the regular retail version. I've had it for about 9 days and have used it every single day. Last night I downloaded 2 movies onto it and everything was fine. Today it would not power on one bit! I charge it over night so the battery shouldn't have drained. Anyone experience this before???
Nevermind: Fixed my problem by doing the following!
Press and hold the on button.
At the same time, keep a finger on the screen.
Keep watching and you might see a slight change of color on the screen.
Hold it down for 15 seconds or more. Be patient.
Click to expand...
Click to collapse
WORKED like a charm!
Hi all,
Yesterday my Jiayu S3 crashed and rebooted, after setting an alarm clock and using the Spotify app. However, it did not reboot into the OS as usual. It did not even show the Jiayu logo, but the phone vibrated (sign that it's booting), screen turned on, phone turned off again, repeating this cycle over and over (not the traditional bootloop as I know it). I was running a rom based on the original rom, with some slight modifications. This rom was running stable for more than a week. I know my way around Android, and am used to switching roms, flashing etc.
Right away, I checked the following things:
- Battery removal didn't help (I did not forget to put it in again ofcourse )
- Phone doesn't go into it's charging cycle when charger is connected
- I do NOT have access to recovery
- I can, however, access the boot menu (Volume up + power key, options: Normal boot, recovery, fastboot)
- I can get into fastboot mode (haven't tested ADB yet), that's the only thing that's still working
I tried to flash the original firmware using SP flashtool, and I am still able to upload firmware on the phone! I am sure that I'm using the correct ROM, and tried different PC's and drivers. Got a few succesful flashes, but still bootlooping.
I also had the idea that my battery was empty (didn't charge it overnight), and measured the battery at 3.52 V. So it was pretty empty but not that empty that it doesn't boot. In an effort to charge the phone, I left it bootlooping for an hour or so, and later on it turned out that it only drained the battery further, 2.99 V.
I didn't want to kill this battery so I did use 2 other batteries from an old Jiayu G4, which appear to work if you turn them around and hold them against the pins (note: I knew what I was doing here ). After a lot of Googling, and seeing a lot of generic "how to fix any brick" stuff I was not able to revive my phone again.
I still believe (and hope) that the error is on the software side of the phone. All the partitions should be ok and in working order according to SP flashtool.
Now this is where my knowledge stops and where (hopefully) your help comes in. What can be corrupted that I haven't checked yet? Do you guys have any suggestions to revive this "high-end" phone again? Once again, it did not happen because of bad flashing or something like that, it happened randomly when I was using the phone normally. I tried to be as accurate as possible (long story), but if there are any questions I'm happy to answer them.
Any suggestion is welcome!
Thanks in advance.
Bump..
Anyone?
bump
I've spent all day fighting with the boot loop on my A500f.
I had the phone running really well with Ahmed's Resurrection Remix ROM on this post:
https://forum.xda-developers.com/sa...om-resurrection-remix-5-8-2-sm-a500h-t3572062
He doesn't detail TWRP installation, so I used DeadSquirrel's 3.1.0 post here:
https://forum.xda-developers.com/sa...overy-twrp-3-0-2-0-samsung-galaxy-a5-t3439233
I hadn't seen that TWRP can be installed without root, so I rooted with Chainfire first. I'm not sure, but I think I got the Chainfire file from this post:
https://forum.xda-developers.com/sa...-to-root-galaxy-a5-a500fu-lollipop-5-t3137613
The file I downloaded for the A500f is "CF-Auto-Root-a5lte-a5ltexx-sma500f.zip" (contains tar.md5)
The post says it is for Lollipop, but the instructions say this is a Chainfire root zip for Android 4.4.4. One post suggested this might be the cause of my boot loop.
The instructions say that this Chainfire Auto Root solution also contains a recovery file, but I was never able to boot into this recovery, so I went directly to installing DeadSquirrel's TWRP. I was able to boot into this recovery. From there I installed the Resurrection Remix ROM. WIthin the ROM, I installed SuperSU from the Play Store, but SuperSU informed me the phone was not rooted, so I flashed the SuperSU root zip from their website, which I believe was the file, A500FXXS1CQC2_A500FOJV1CPH3_XFE.zip
SuperSU now reported root was present, so I installed WiFi Connection Manager from the Play Store, granted it root access in SuperSU, and used the Fix Problems menu item to repair the wifi shutting off the phone problem that I was originally working on. That fix worked well, so I left the wifi on and ran YouTube on Autoplay for about 4 hours. Deciding the problem was solved, I gave the phone back to my son, and he brought it back to me dead 5 minutes later. I'm not sure if it already that the boot loop problem at that point.
The phone would no longer boot. I noticed a seandroid enforcing notification, and thought it might be a security issue preventing boot. I found a thread that said I needed that flashing back to a Samsung ROM would remove the seandroid notice and that I needed to update to Android 6.0.1 before installing TWRP to solve the boot loop issue. I went to Sammobile and found the newest ROM for my A500f was the A500FXXS1CQC2_A500FOJV1CPH3_A500FXXU1CPH2_HOME.
I installed this in Odin, and the phone has never come back to me since then. I've made endless retries throughout the day, trying different combinations of the Chainfire root, different versions of TWRP, and different root methods, but all to no avail. One post even suggested that if you flash factory ROM from Odin just once, it will create a boot loop, but if you flash twice, it solves it, but it didn't work for me. It's also gotten increasingly difficult to get into recovery. Whether in stock ROM or TWRP, I was only able to get in about 10% of the time. Boot loop behavior has varied between boot logo - vibration - black screen and battery charge logo - vibration - black screen.
I found this thread that is supposed to address the boot loop problem, and I tried these versions of root and TWRP, but it didn't help:
https://forum.xda-developers.com/sa...overy-samsung-galaxy-a52015-sm-a500f-t3360802
At the moment, I'm on stock ROM. On power up, you get the Galaxy A5 screen, then it vibrates and goes black, then the lightening battery logo comes up, it vibrates, and goes black, and then the green battery status logo comes up, and then the phone goes black. It's also booting into stock recovery okay, and I can do the recovery functions. I just can't boot the phone.
So now, I try the instructions again in ashyx's TWRP post. Now I can get into TWRP. I power up and the phone sticks on the Galaxy A5 boot screen for a long time. Then it vibrates and repeats. It's basically the same as above, but there is a long delay before rebooting instead of instantly as before. Now I go back into TWRP and flash the Resurrection Remix ROM and the behavior is the same. Power up and get the Galaxy A5 boot screen for 8 seconds (this time sporting a warranty bit: kernal notice), 2 seconds of black screen, vibration, battery/lightening logo blinks on, then off, vibration, battery/lightening logo blinks on then off. Black screen, then standard battery charging percent indicator. I did that three or four times to make note of the behavior. Then the power switch wouldn't work, so I used the technique to press the volume up and down key together with the power key to turn it back on. Now it is in a non-stop 5 second cycle of vibrate - flash the icon - black screen that won't quit. Throughout the day I've been stuck with this in both stock and custom ROM. Only once during the day did I see the custom ROM boot all the way through. The stock ROM has never booted.
Now the recovery key combination won't boot TWRP either. The key combination just makes the Galaxy A5 screen flash instead of the battery icon. But I can get into TWRP by rebooting with the recovery key combination on leaving Download mode.
If anyone understands what's wrong here, I'd appreciate it.
Thanks
If I were you, I'd flash an older version of stock ROM with Odin, reboot with factory reset then I will let Samsung Smart Switch to upgrade my phone. After that I will notice the CORRECT version of ROM...
MoshPuiu said:
If I were you, I'd flash an older version of stock ROM with Odin, reboot with factory reset then I will let Samsung Smart Switch to upgrade my phone. After that I will notice the CORRECT version of ROM...
Click to expand...
Click to collapse
Thank you. That did the trick. Going back to the original factory ROM of Android 5.0.1 brought the phone back to being bootable again. I wish I understood what is going on on the low level to cause these things!
MoshPuiu said:
If I were you, I'd flash an older version of stock ROM with Odin, reboot with factory reset then I will let Samsung Smart Switch to upgrade my phone. After that I will notice the CORRECT version of ROM...
Click to expand...
Click to collapse
Samsung Smart Switch what is it?
Faraz_74 said:
Samsung Smart Switch what is it?
Click to expand...
Click to collapse
Samsung app:
http://www.samsung.com/us/smart-switch/
Same Issue
Hello PJK2011 . I'm having the same problem can you please help me to find the link of the Stock ROM you installed?
xoein said:
Hello PJK2011 . I'm having the same problem can you please help me to find the link of the Stock ROM you installed?
Click to expand...
Click to collapse
I believe Sammobile is the standard location to download stock Samsung ROMS:
https://www.sammobile.com/firmwares/galaxy-a5/SM-A500F/
xoein said:
Hello PJK2011 . I'm having the same problem can you please help me to find the link of the Stock ROM you installed?
Click to expand...
Click to collapse
you can download in here also updato.com
Sent from my SM-A500F using xda premium
Hi everyone,
When I tried to restart my Galaxy s8 it entered some kind of hardcore bootloop where I couldn't stop it from looping except by entering the download mode, letting it drain the battery or simply disconnecting the battery. When I exit the download mode it will just continue looping. It is also impossible to enter the recovery menu, which makes things much worse.
I have tried opening the phone and disconnecting everything except power supply (either battery or charger) and screen to see whether some detachable component is failing it (camera, speaker, etc.). But nothing.
I have also tried reinstalling the firmware (BL + CP + AP + HOME_CSC), it installs successfully but it doesn't fix the bootloop. I have also tried two most recent firmware, also without success. Somewhere on the Internet I have found a recommendation to install the firmware from June 2017 which I have tried but it doesn't work anymore because it's not possible to install earlier version of firmware on Samsung phones anymore (since November 2019 I believe).
Now I have started to believe that this could be a motherboard failure but it doesn't really make whole lot of sense because the phone can enter the download mode and reinstall firmware just fine. Or maybe there is a component which can make it able to enter the download mode, but nothing else would work?
Has anyone experienced something like this? How could it be fixed? Any recommendations? Is there any hope?
Edit: The phone has never been rooted, means it is in its original software state (currently on Android Pie with build number G950FXXS8DTC1). Is there any way to install anything on it (custom ROM, TWRP, etc.)?
Come on guys! Please don't tell me that I've tried everything and exhausted all the possibilities...
If there is still warranty on the phone, then send it in for repair. If there isn't, then I would take it to a repair shop and see what they can do about it. It is wierd that you can enter download mode, but can't flash stock firmware. I think it might be a motherboard problem
Nevin1901 said:
If there is still warranty on the phone, then send it in for repair. If there isn't, then I would take it to a repair shop and see what they can do about it. It is wierd that you can enter download mode, but can't flash stock firmware. I think it might be a motherboard problem
Click to expand...
Click to collapse
Unfortunately, there's no warranty and I'm pretty sure no one would repair this kind of failure for a price lower than the price of a used and fully functional Galaxy s8.
Yes, I can enter the download mode and I CAN flash stock firmware, but I can flash only the ones which are newer or the same as the one installed on the phone.
Yes, most probably it's a motherboard failure. In some YouTube videos I have seen people fixing similar issues by replacing the CPU (which I am unable to do by myself). Other suggestion I found on iFixit says that I could soak my motherboard in 99% Isopropyl alcohol and leave it overnight in it (I am going to try this if I get my hands on the alcohol).
BTW: One interesting thing I experienced while flashing the phone without its battery connected is that the phone's screen will go black when you press 'Start' button in Odin, but nevertheless the installation will finish normally and you can track its progress in Odin. At the end you'll need to restart your phone manually.
roberta-xda said:
Hi everyone,
When I tried to restart my Galaxy s8 it entered some kind of hardcore bootloop where I couldn't stop it from looping except by entering the download mode, letting it drain the battery or simply disconnecting the battery. When I exit the download mode it will just continue looping. It is also impossible to enter the recovery menu, which makes things much worse.
I have tried opening the phone and disconnecting everything except power supply (either battery or charger) and screen to see whether some detachable component is failing it (camera, speaker, etc.). But nothing.
I have also tried reinstalling the firmware (BL + CP + AP + HOME_CSC), it installs successfully but it doesn't fix the bootloop. I have also tried two most recent firmware, also without success. Somewhere on the Internet I have found a recommendation to install the firmware from June 2017 which I have tried but it doesn't work anymore because it's not possible to install earlier version of firmware on Samsung phones anymore (since November 2019 I believe).
Now I have started to believe that this could be a motherboard failure but it doesn't really make whole lot of sense because the phone can enter the download mode and reinstall firmware just fine. Or maybe there is a component which can make it able to enter the download mode, but nothing else would work?
Has anyone experienced something like this? How could it be fixed? Any recommendations? Is there any hope?
Edit: The phone has never been rooted, means it is in its original software state (currently on Android Pie with build number G950FXXS8DTC1). Is there any way to install anything on it (custom ROM, TWRP, etc.)?
Click to expand...
Click to collapse
I have an S8 with a similar issue. I can get to recovery menu but following similar steps to above by flashing combination firmware and still got stuck in bootloop. Subscribing to this thread in case anyone has a fix.
Just wanted to share a video I found. This is exactly how my s8 bootloops: https://youtu.be/gBlIcAJzgVA?t=5
PS: Obviously, the solution explained in the video didn't work for me.
PS2: This issue started by just restarting the phone. Before the restart it was in a perfect state, fully working, never had any hardware issues. Although there were some software issues introduced by an update (October or November 2019 I think) which made my phone need to restart 2 times to fully boot once if I wanted to restart it or turn it on after it was turned off. But those software issues were solved by a latter software update.
kjaved373 said:
I have an S8 with a similar issue. I can get to recovery menu but following similar steps to above by flashing combination firmware and still got stuck in bootloop. Subscribing to this thread in case anyone has a fix.
Click to expand...
Click to collapse
i know it's already an old comment, but was your phone also completely stock?
Leberkuchen said:
i know it's already an old comment, but was your phone also completely stock?
Click to expand...
Click to collapse
Yeah I believe so.
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"...