I had been playing with it, trying to put an android system on it. When I was done, I flashed some other ROM onto it, not sure what...I recall getting frustrated with it when I tossed it into the drawer. Well, now I am wanting to set it up to simply run Slacker Radio and some other streaming media. I don't need it as a phone, just use it as a cheap media player.
So I dig it out, charge it, boot it mess with it for a minute and it reboots. Then I let it reboot and just looked at it. After a few minutes, it reboots....endless cycle. So I did a hard reset. It boots up to where I align the screen and then it goes to the today page, and immediately goes into some automatic customization thing....after which it reboots and reboots...
Okay, fine, I'll flash a new ROM (I found a light one here that has no carrier...perfect). At my current location all I have is a Windows 7 x64 laptop and I cannot get a driver anywhere that I've looked that will work. I can get the phone into bootloader mode, but that of course does me no good if the laptop won't recognize it. I've searched the forums as well as the web, and most of the Wiki for this phone is broke. I'm remembering perhaps why it ended up in a drawer.
Any ideas? Thanks.
Calis
I always flash using the micro sd card. Works great!
can you virtualize xp? then you should be able to see it in bootloader
Guys, I don't usually post on forums but now I just can't make myself sending it back without making sense of this first.
So I got the Nexus 7 one month ago, barely used it and didn't install any fancy stuff on it. One week ago I saw an app that I wanted and before installing it I had to install BusyBox. In my foolishness I didn't read the description that the tablet has to be rooted before I install it.
When the installation finished this exact problem suddenly happened: youtube.com/watch?v=5d319gUeYLM
Why I'm determined it's a hardware problem:
- The next morning I turned it on and everything was back to normal, however, after 15 seconds it slowly dimmed and got back to that exact screen
- You can navigate the menus and hear the sounds
- The morning after again, back to normal, I hurried and did a factory reset and deleted everything. This didn't help at all, the problem was still there and the screen never went back to normal even for a few seconds.
- It keeps the same lines in the recovery menu and on boot.
While everything points it's a hardware problem and the guy on YouTube said Asus replaced his display, how can this simply be a COINCIDENCE? For this to happen exactly when I installed something it wasn't supposed to be installed if the tablet wasn't rooted?
Help! my 15 month old Umi Super shut itself off (battery almost full) and now won't reboot. The Umi logo appears as normal, then goes to the pulsing android thing. and stays like that for a few minutes until the screen goes blank. I have to hold the power button for a couple of minutes to start the sequence again.
I haven't rooted it (wouldn't know how, or feel confident doing so) Only thing I've done recently was update the OS to Nougat, using the update feature on the phone, so it's completely unmolested apart from the update. Since then, I've lost the fast charge facility, and it auto-locks the screen, and won't display the clock overnight, like it used to do. And all the settings menus have radically changed (for the worse). Can't even turn off the Auto-lock feature, just set the delay.
Is the update to blame? Can I undo it and revert to Marshmallow? Can someone please help? All my contacts are in the phone memory...
Sorted!
Don't know what happened but it eventually rebooted itself. I then deleted all the recently installed apps, and it's now working again. Must have been a rogue app, but I don't know which one. Slowly and methodically worked through the setup menu and found, in the Security submenu, some settings I hadn't previously found and was able to set a safe location at home where it doesn't Autolock. I have my phone back! And I take it all back. Nougat is a big improvement on Marshmallow, once you know how it works. Happy Days!
Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?
XxXPhantomXxX said:
Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?
Click to expand...
Click to collapse
Might Be A Malicious OTA Uptade , My Advice For You , Install Stock Rom
Try installing a different rom and if that works, retry installing LOS. Two years ago i became unable to update/install LOS. RR was an instant success and i kept using that till becoming somewhat instable one year ago, so back to LOS, w/o difficulties(probably a clean install of RR would have solved the problems i had, but i didn' t want to do this two times, if really RR and only that was the culprit).
Of course you can start by reinstalling stock rom in Download Mode, as this will be the last attempt if all previous measures may fail. Then re-root, re-install TWRP etc.
XxXPhantomXxX said:
Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?
Click to expand...
Click to collapse
I Heard That The Last Uptade For Lineage Doesn't Work So Download A New ROM In Your Computer And Put It On A SD-CARD And Boot To Recovery And Clean-Flash It
Oh If You Want To Know My ROM I'm Using : Resurrection Remix.
XxXPhantomXxX said:
Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?
Click to expand...
Click to collapse
Since it's old, possibly hardwqre related.
Recently, I had that with my stock s5 s906s.
I reloaded stock firmware but to no avail.
Occasionally it boots up but I noticed it would go past the boot loop after I gave up and gave it a rest for a few days. Then I realized it was a temperature thing. When it's hot and I put the batt in, it would automatically start and go into a boot loop.
But then, it does not always boot well even after giving it a long rest.
I then reached out for my Qi wireless receiver, slapped it on top of the battery, pressed the 3 pins onto the connectors on the phone, and pressed the power button. And the phone booted well right after.
So, something in the old phone has made it sensitive to internal heat. Cool it down by turning it off, even if you have to remove the battery. Leave the battery out. If you have to recharge it with a charger or with another s5, do that.
Then, once cool, put the battery back into the phone with the qi receiver strapped onto it, and make the 3 contacts in the wireless receiver touch with the 3 connectors in the phone as you slide the battery in. Then press the power button. Somehow, this makes up for the old phone's faulty circuitry's tendency to start by itself when the battery's put in.
It is a quirk in my old phone, but other than that I have loaded it with an RR rom and it is running now like a champ. Just expect it to go into a bootloop each timeI I restart as there is heat already from its operation. When that happens, remove the battery and let the phone cool off before putting in back in to start.
yerrag said:
Since it's old, possibly hardwqre related.
Recently, I had that with my stock s5 s906s.
I reloaded stock firmware but to no avail.
Occasionally it boots up but I noticed it would go past the boot loop after I gave up and gave it a rest for a few days. Then I realized it was a temperature thing. When it's hot and I put the batt in, it would automatically start and go into a boot loop.
But then, it does not always boot well even after giving it a long rest.
I then reached out for my Qi wireless receiver, slapped it on top of the battery, pressed the 3 pins onto the connectors on the phone, and pressed the power button. And the phone booted well right after.
So, something in the old phone has made it sensitive to internal heat. Cool it down by turning it off, even if you have to remove the battery. Leave the battery out. If you have to recharge it with a charger or with another s5, do that.
Then, once cool, put the battery back into the phone with the qi receiver strapped onto it, and make the 3 contacts in the wireless receiver touch with the 3 connectors in the phone as you slide the battery in. Then press the power button. Somehow, this makes up for the old phone's faulty circuitry's tendency to start by itself when the battery's put in.
It is a quirk in my old phone, but other than that I have loaded it with an RR rom and it is running now like a champ. Just expect it to go into a bootloop each timeI I restart as there is heat already from its operation. When that happens, remove the battery and let the phone cool off before putting in back in to start.
Click to expand...
Click to collapse
Well, this worked for a while. Then, bootloop became more stubborn.
By then, I had already bought a phone to replace it, so I was in no hurry to fix this issue but still, I hate to see a good phone go. Still has a screen that stood the test of time, and at high res, and I love the size of the phone.
So, another Hail Mary. And it worked!
I put the phone, worked in tissue paper, then enclosed in bubble wrap, in the freezer overnight, surrounded by grains of rice in a plastic container, that had been vacuumed by a FoodSaver machine.
The following morning, removed the phone from the freezer and laid it bare, separating the battery from it, and wiped it clear of moisture, and let it sit to evaporate any more moisture from the temperature gradient.
Then started the phone, and the bootloop once again gone.
So, phone saved. But since it's no longer that reliable due to the recurring bootloop problem, it would be my phone to watch streaming movies from Amazon Prime or Netflix, but not my phone for receiving calls and text messages, or for Waze and all.
The lesson I got from this is that with this phone, the circuitry inside has become finicky. To open it up and fix it would be too bothersome, especially with the circuitry being composed of embedded modules. Probably somewhere inside there is a capacitor that has reached its reliable end of life, but still breathing and needing an occasional handholding. So, I just gotta learn to live with this quirk, and this quirk is tolerable for the use I have it for.
So, if you run across this problem, I hope I gave you a workaround for you to remain loyal to a workhorse that served you long enough.
it has been giving me small issues like wifi not wanting to connect, radio app missing all numbers on startup and volume taking forever to respond on first boot. Ive had this unit a couple of years and contacted eonon support for answers. They led me to download update.zip and update the unit with it. I attempted it yesterday and it loaded the update about 75% and paused for a few minutes. It finally completed relativly quickly and rebooted...It hung on the android screen(loading) for 15 mins and rebooted...same hangup then it shut down and wouldnt restart. folks...I think I killed it. It did try to start the next morning but with the same hangup-reboot-hangup-shutdown rince repeat game. any advice on it its saveable let me know please I have no idea how to enter recovery mode on this unit but i can reboot it while its trying to unsuck-sessfully load android...lol
Pull the power completely from the device, by pulling the fuse or pulling the ground from the battery. Just for some seconds.... and remove the update sd card/USB