I guess there's nothing to be done, but I might as well try asking.
I had an issue with the tablet where it randomly shut the screen down. Haven't been able to figure out if it was a crash, it turned off or just the screen wouldn't turn on anymore.
So I figured I'd do a fresh install and flashed CM on it (had some other rom before). Same issue.
I tried installing yet another rom, but this time it turned off while installing.
Now it's stuck on the updating-Android-logo everytime I boot, both normally and with Power+Vol Down so I can't access fastboot or recovery that way. Leaving it on does nothing even after half a day.
Anything I could try or should I just scrap the thing?
The_Bard said:
I guess there's nothing to be done, but I might as well try asking.
I had an issue with the tablet where it randomly shut the screen down. Haven't been able to figure out if it was a crash, it turned off or just the screen wouldn't turn on anymore.
So I figured I'd do a fresh install and flashed CM on it (had some other rom before). Same issue.
I tried installing yet another rom, but this time it turned off while installing.
Now it's stuck on the updating-Android-logo everytime I boot, both normally and with Power+Vol Down so I can't access fastboot or recovery that way. Leaving it on does nothing even after half a day.
Anything I could try or should I just scrap the thing?
Click to expand...
Click to collapse
Maybe its just the display connector inside the tab whitch is loosing the connection. but be careful opening the tab is pitty
Gesendet von meinem REMIX SK1WG mit Tapatalk
I've tried that but no luck :| At this point I'm trying forcing the update from the microSD with the original image.
I'll write back if it works for future reference.
Related
Hi all,
seems like my OB is broken. But just in case this is still a repairable issue and since I would of course love to keep my good ol' OB, I'm posting my issue. Maybe there is still hope
It all started after OTA-Update from CM10 nightly to the stable release. I noticed that from time to time the power button did not work after charging the device over night. So for example, the device woultn't wake up when pressing the power button, but reconnecting to the charger did the trick. But then again, I often coudn't turn it back to sleep with the button.
Every time that issue appeared, the OB acted normally after removing the battery for a moment.
But not today.
Again, I couldn't get it to lock when it was active because the power button did not work. So I decided to wait until the screen turned off after the timeout which it actually did. But then again, I couldn't wake it up.
So, starting with the "normal" procedure, I removed the battery for a moment and tried to turn it back on, thinking that it'll be just fine again. But not this time. It didn't react at all. Even after connecting it to the charger - the display turned on and showed the charging animation, but I couldn't get the device to boot.
Next step: Common unbrick procedure. Since it was the only thing I could still do with the OB, I reflashed the good old patched v20n using SmartFlash. I used the exact same program and bin files that I used long ago when I initially rooted the device. So that should have worked like a charm. It didn't.
First try: Flashed with SmartFlash and restored an old nandroid with Zeus ROM on it. Rebooted and... oh great it's stuck already on the LG logo.
Okay, 2nd try: Flashed again but this time just selected the reboot option in CWM. Device boots, plays the animated LG bootlogo and reboots into bootlooop....
So far about my poor OB
Now does anybody have any idea what could have gone wrong with the device?
Of course it could just be a coincidence that these issues started right after the update and the cause may be an ancual failure of the HW button.
But really, how likely is that keeping in mind that my OB worked like a charm all the time before the update?
Any ideas, comments or even suggestions what else I could try?
Smartflash must unbrick the device if the problem is not a hardware problem, if you have tried it and it didn´t work, i am pretty sure that you have to take the phone to warranty.
Anyway, you can try to flash a patched bin/fls with root and recovery, after flash phone will go to recovery, then do a full wipe (Data, cache and dalvik) and reboot.
Reflashed with SmartFlash (to get into CWM), wiped all, booted v20n; no power button, all other HW-Buttons work :/
Hardware problem.
That's what I thought as well, but:
Just managed to restore my Zeus ROM Nandroid image, cleared cache and it booted without problems. Aaand: Power button is working again! Locking/unlocking as well as turning on/off the device entirely works normal!
Now seriously, this issue keeps buggin me - how can something like that happen at all??
I mean, if I would mess with the key mapping and remove the mappings of the power button, it might not work anymore for locking and unlocking the phone. But what could possibly cause that button to not even work for powering on the device? I always thought that must be a hard-wired functionality??
I have seen a lot of threads on similar problems, but none of them seem to have a fix for me. So, here I am!
A few weeks back, I flashed a custom CM11 ROM to my phone, and it went through without a hitch. The phone did have a few problems, but the dev had mentioned that the ROM had a few bugs, so I didnt think much of it. The phone screen would turn off at random, and if i plugged in the phone while it was not turned on, it would get stuck at the loading screen that precede the battery animation. Like I said, I didn't make much of these.
The dev released the newest update yesterday, so I downloaded it, and when I tried to boot my phone into recovery, the s3 mini splash screen came up for a few seconds, then the phone turned off. This happened several times, even when I tried to turn it on in download mode.
I decided to use Terminal Emulator to turn on recovery, but when I tried to turn my phone on normally, the same thing happened (s3 mini splash screen, then turned off).
I saw other threads on the same matter, but they were mostly due to a pressed-in power button, or were solved with steps that didnt work out for me. Please advise!!!
polski691 said:
I have seen a lot of threads on similar problems, but none of them seem to have a fix for me. So, here I am!
A few weeks back, I flashed a custom CM11 ROM to my phone, and it went through without a hitch. The phone did have a few problems, but the dev had mentioned that the ROM had a few bugs, so I didnt think much of it. The phone screen would turn off at random, and if i plugged in the phone while it was not turned on, it would get stuck at the loading screen that precede the battery animation. Like I said, I didn't make much of these.
The dev released the newest update yesterday, so I downloaded it, and when I tried to boot my phone into recovery, the s3 mini splash screen came up for a few seconds, then the phone turned off. This happened several times, even when I tried to turn it on in download mode.
I decided to use Terminal Emulator to turn on recovery, but when I tried to turn my phone on normally, the same thing happened (s3 mini splash screen, then turned off).
I saw other threads on the same matter, but they were mostly due to a pressed-in power button, or were solved with steps that didnt work out for me. Please advise!!!
Click to expand...
Click to collapse
is it turnoff and keep restart or turnoff and never turn on ?
Ahmed.ragab said:
is it turnoff and keep restart or turnoff and never turn on ?
Click to expand...
Click to collapse
I have the same problem, since two weeks the phone was stuck on the pre-charging logo loading.
This morning the phone showed the same problem of polski, but i can boot in recovery and in download mode.
Every time i try to change something, the phone's situation worsens.
First the phone reboots 5 seconds after the system completely boots.
After a nandroid restore the phone was stuck in S3 mini logo
After that i tried another nandroid restore and it failed.
The phone keep restart, anyway.
Sorry for double-posting, anyway i tried a way to resolve and it had been successful.
I downloaded original firmware from samsung site (obiouvsly the correct one) and i flashed it with odin.
After that i re-flashed Maclaw's CM11 by odin and now the phone work well
HylianHero said:
I have the same problem, since two weeks the phone was stuck on the pre-charging logo loading.
This morning the phone showed the same problem of polski, but i can boot in recovery and in download mode.
Every time i try to change something, the phone's situation worsens.
First the phone reboots 5 seconds after the system completely boots.
After a nandroid restore the phone was stuck in S3 mini logo
After that i tried another nandroid restore and it failed.
The phone keep restart, anyway.
Click to expand...
Click to collapse
HylianHero said:
Sorry for double-posting, anyway i tried a way to resolve and it had been successful.
I downloaded original firmware from samsung site (obiouvsly the correct one) and i flashed it with odin.
After that i re-flashed Maclaw's CM11 by odin and now the phone work well
Click to expand...
Click to collapse
As u can go.to download.mode.. flashing full stock.firmware via odin will solve it
As i said
There's another problem now... the phone works well but there's no more the Samsung Splash screen but a crashed image (like static of TVs)
HylianHero said:
As i said
There's another problem now... the phone works well but there's no more the Samsung Splash screen but a crashed image (like static of TVs)
Click to expand...
Click to collapse
Flash param and image will be alright again.
tys0n said:
Flash param and image will be alright again.
Click to expand...
Click to collapse
The problem started with the GT-i8190N_param.tar flash
Ahmed.ragab said:
is it turnoff and keep restart or turnoff and never turn on ?
Click to expand...
Click to collapse
It turns off and never turns on. :\
I bought a new battery today to see if it fixes the problem, but it didnt. :\
polski691 said:
It turns off and never turns on. :\
I bought a new battery today to see if it fixes the problem, but it didnt. :\
Click to expand...
Click to collapse
if it didn't respond at all so it is a hard brick for sorry
Ahmed.ragab said:
if it didn't respond at all so it is a hard brick for sorry
Click to expand...
Click to collapse
I dont think I made myself clear.
The splash screen does show up, but then the phone turns off immediately afterwards.
polski691 said:
I dont think I made myself clear.
The splash screen does show up, but then the phone turns off immediately afterwards.
Click to expand...
Click to collapse
(can u access download mode if yes so try complete stock firmware via odin
polski691 said:
The splash screen does show up, but then the phone turns off immediately afterwards.
Click to expand...
Click to collapse
First of all do you have a Custom Recovery installed??
If you don't this won't work.
(This happened to me on my S3.
I was using pimp my ROM and upon reboot, turned of after splash screen)
My way to fix this was:
•Download another ROM (for your device) (using a PC or another Android Phone) move downloaded ROM to External SD Card
•Insert External SD card back into Galaxy S3 Android Phone (or you can move ROM file to Internal SD Card if your using a PC)
•Boot into recovery mode.
Turn phone off
Press & hold Power Button, Volume Up & Home Button.
•Factory Reset
•Flash ROM from External or Internal depending on way used.
•Reboot
•Profit
Sent from S3 Mini
Using XDA App
polski691 said:
I dont think I made myself clear.
The splash screen does show up, but then the phone turns off immediately afterwards.
Click to expand...
Click to collapse
Discharge battery using download mode and return to seller for refund or replacement!
Everything worked fine for almost a whole year, then my tablet started acting strange last night. It got really bad this morning so i was trying to install a antivirus thinking that might help, but it wouldn't open. Reports of program failures were popping up like crazy, so i turned it off and back on about five minutes later. Now its been over an hour and its stuck in the cyanodenmod loading screen, its never taken this long.
Is there any program i can use on my laptop to wipe everything on my tablet and install another os? I'm not sure how it'd work seeing as how its stuck loading. Do i need to let the battery die? I really just want to plug it in and wipe the whole thing but i haven't a clue where to start.
Please help?
I took the back off and unhooked the colorful wire thing from it to turn it off, and put it back. It restarted fine and now I'm attempting to wipe everything on it. When i first pushed the erase all button it didn't do anything, then after trying a few more times it restarted to a "teamwin" something (have no idea what that is) and it restarted again, so far its back on the cyanogenmod loading loop again. (I'm a little amazed i even managed to root it in the first place, considering i didn't know what "os" stood for before that. I really need help with stuff like this.)
If i can get it back to the normal screen, is there any program i can use to reformat everything and like an alternative to cyanogenmod for the program?
Which CyanogenMod version are you running ? The teamwin that you saw when it booted up was the recovery you flashed to install custom ROMs like CyanogenMod. Make sure you have the latest recovery before anything . take a look here and let me know when your up to date and we can put you device back in working form
http://forum.xda-developers.com/showthread.php?t=2218796
I didn't want to make a new thread. But I've searched high and low.. And nothing has been answered. So here's my story. I have a note 4 sm-n910T. When I rooted the phone everything was fine and good. I then decided to give it to a family member. I flashed it back to stock.. All was fine for a while but it started acting up. Like randomly turning off and not responding to a charge or any commands to turn on into other modes... I had flashed stock again. All was good.. Till now. My madre and received a Ota update, downloaded and installed the update. When I pressed ok to reboot new update. The phone never came back on. So I went through all the fun stuff. I tried kies.. Kies days unsupported device connected.. There is however talk between the two because it's pushed errors onto my phone as well as has tried to download the stock rom. But every which way I've tried it fails. Next. I decided to go for custom roms... And flash cf-chainfire auto root. Then twrp.. Then install supersu.. Then a rom from twrp. Now here's where it gets interesting. Nothing would pass odin if I had auto-reboot and f.reset time checked.. Any and all roms.. Files..etc would only pass with auto reboot checked and f. Reset time unchecked. At first everything seemed ok.. I was able to actually get cm 12.1 installed as well as gapps. But only the one time.. Which you'd think was good enough. But here's what has happened and what I can't seem to fix. The phone yesterday after having everything installed and sitting at home untouched.. I came home clicked the home button.. And it came on.. I scrolled a few pages.. Thought.. OK cool.. Let's get madres Sim card in and call it a night.. When I turned the phone over.. (didn't even take our the battery) tried to see if I could fit the sim in.. Which didn't.. I then turned the phone back around just Cuz I wanted to make sure it was awake.. The screen was black.. I figured it was in sleep mode.. So I hit the home button.. No response.. I hit the power button.. No response. .. The phone had turned itself off.. And when I tried to turn it on it wouldn't. Now mind you the phone has these weird phases where when I try to install or flash a rom and it fails.. And I'm forced to remote battery.. A good portion of the time it won't turn back on.. Sometimes it can be instant.. Others.. A few mins.. Sometimes even longer for it to respond.. Right now I have been accessing twrp.. Wiping all data.. Davik...cache.. System.. One by one.. Then installing a rom.. I go for a reboot.. And I get a black screen. I need help.. I'm running out of ideas and basically just fishing random idea attempts. I'm no scared to brick it.. So all ideas are welcome. Plz. Thank you.
Malistoff said:
I didn't want to make a new thread. But I've searched high and low.. And nothing has been answered. So here's my story. I have a note 4 sm-n910T. When I rooted the phone everything was fine and good. I then decided to give it to a family member. I flashed it back to stock.. All was fine for a while but it started acting up. Like randomly turning off and not responding to a charge or any commands to turn on into other modes... I had flashed stock again. All was good.. Till now. My madre and received a Ota update, downloaded and installed the update. When I pressed ok to reboot new update. The phone never came back on. So I went through all the fun stuff. I tried kies.. Kies days unsupported device connected.. There is however talk between the two because it's pushed errors onto my phone as well as has tried to download the stock rom. But every which way I've tried it fails. Next. I decided to go for custom roms... And flash cf-chainfire auto root. Then twrp.. Then install supersu.. Then a rom from twrp. Now here's where it gets interesting. Nothing would pass odin if I had auto-reboot and f.reset time checked.. Any and all roms.. Files..etc would only pass with auto reboot checked and f. Reset time unchecked. At first everything seemed ok.. I was able to actually get cm 12.1 installed as well as gapps. But only the one time.. Which you'd think was good enough. But here's what has happened and what I can't seem to fix. The phone yesterday after having everything installed and sitting at home untouched.. I came home clicked the home button.. And it came on.. I scrolled a few pages.. Thought.. OK cool.. Let's get madres Sim card in and call it a night.. When I turned the phone over.. (didn't even take our the battery) tried to see if I could fit the sim in.. Which didn't.. I then turned the phone back around just Cuz I wanted to make sure it was awake.. The screen was black.. I figured it was in sleep mode.. So I hit the home button.. No response.. I hit the power button.. No response. .. The phone had turned itself off.. And when I tried to turn it on it wouldn't. Now mind you the phone has these weird phases where when I try to install or flash a rom and it fails.. And I'm forced to remote battery.. A good portion of the time it won't turn back on.. Sometimes it can be instant.. Others.. A few mins.. Sometimes even longer for it to respond.. Right now I have been accessing twrp.. Wiping all data.. Davik...cache.. System.. One by one.. Then installing a rom.. I go for a reboot.. And I get a black screen. I need help.. I'm running out of ideas and basically just fishing random idea attempts. I'm no scared to brick it.. So all ideas are welcome. Plz. Thank you.
Click to expand...
Click to collapse
Also how important is f. Reset time? I don't totally understand it. Next.. What about having the roms and files I flash on internal memory instead of sd. I'm not sure if I can access the Internal storage. But if I can does that help. Also I cannot access Android at all.. I can either access download mode or recovery. I have been using an external battery charger to charge my battery as well. Due to it doesn't read the charge... But! It did read a charge just fine when I had cm 12.1 working.
I would suggest:
1) In twrp wipe system, both the cache's and also data
2) use ODIN to install the stock Note 4 ROM
see -> http://forum.xda-developers.com/not...uide-odin-to-stock-unrooted-firmware-t2957156
3) When it is finished unplug the usb from your computer as the phone is rebooting
NOTE you might want to uncheck Reactivation Lock in Settings - Security first
w8wca said:
I would suggest:
1) In twrp wipe system, both the cache's and also data
2) use ODIN to install the stock Note 4 ROM
see -> http://forum.xda-developers.com/not...uide-odin-to-stock-unrooted-firmware-t2957156
3) When it is finished unplug the usb from your computer as the phone is rebooting
NOTE you might want to uncheck Reactivation Lock in Settings - Security first
Click to expand...
Click to collapse
Answering question one.. I do that already. I wipe everything one by one except sd... Answering question two. I have tried that already and odin fails.. However I'm sure if I tried to flash the rom and didn't check f. Reset time it might work. But as for flash stock.. I have tried several times.. I can't say one error or another I'd a cause because I get a different one each time.. What is the purpose of f. Reset time in Odin? I've searched it and to me the explanation didn't make since.
Malistoff said:
Answering question one.. I do that already. I wipe everything one by one except sd... Answering question two. I have tried that already and odin fails.. However I'm sure if I tried to flash the rom and didn't check f. Reset time it might work. But as for flash stock.. I have tried several times.. I can't say one error or another I'd a cause because I get a different one each time.. What is the purpose of f. Reset time in Odin? I've searched it and to me the explanation didn't make since.
Click to expand...
Click to collapse
Reactivation is unlocked. Also I wouldn't be able to change any setting in the phone.. As the phone does not boot into Android. I was just lucky enough to have usb debugging active before this all happened
I am not sure what that is for
But every time I have done a flash it works if you use the steps I had there. (Not really questions)
Sorry I do not have anymore ideas.
---------- Post added at 02:38 PM ---------- Previous post was at 02:37 PM ----------
Are you booting your phone into download mode before you use ODIN?
(I know it's proly a dumb question but just in case)
Yes I am in download mode when using odin.
Malistoff said:
Yes I am in download mode when using odin.
Click to expand...
Click to collapse
Just now I did another full wipe and wipe of cache, davik, system, internal memory and had a successful install of cm12. 1 with gapps.. Everything installed.. Clicked reboot and the phone never came back on. I will try your idea next. I have not tried an idea where I use twrp to wipe everything and reboot into download then do stock rom via odin. If the phone does boot into download from twrp recovery I will try this one time with auto reboot and f. Reset time checked.. If it fails I will try it again with f. Reset time unchecked. I am currently not by my laptop to try this so it will have to be much later in the day.
To boot into download mode: Power off Note 4, hit all 3 of these at the same time until it wakes and vibrates - Power Button, Home Button and Volume Down
I know how to do that lol. I know I'm a junior member. But I'm somewhat intermediate. So cm12. 1 has booted.. However it didn't from a reboot of a flash.. I just took a while shot.. And powered the phone on.. And it booted.. I'm pretty sure in going to run into the problem again.
OK - Well you never know!
I am only a senior member 'cause I am older than Dirt!
Lol. I'm oldish. And trust me this lucky catch I got.. Is temporarily. There is still boot issues. I fear when the phone goes off or is turned off that it won't come on. I do not have a sim card in the phone at the moment which means I can download helpful apps. Like supersu. .. But so far I was able to check settings and get what I can prepared. Also if like to keep this thread open as a log or research tool.
Alright so I like the rom sit most the day.. With minimal to no use.. Most of the day it was fine.. At one point I took a picture and it did as it should.. I cleared all open tabs.. Took another picture and I got a error saying camera wasn't connected.. Finally the phone froze up and rebooted.. And the Camera worked.. Gave it another rest.. Came back to it checked the camera and it was fine.. I put it away for like 10mins then decided to check recording. When I did the phone was not responding to turning back on from sleep mode. Now for as long as I can remember even before this initial issue started.. I was having thr same problems with the phone not coming back on from when in sleep mode.. I dunno what the cause is or hoe to approach it to fix it.
First attempt was to put it to a charger... Registered no charge.. So I removed the battery.. Gave it a few mins.. Pushed down power button.. No response. Something is off with the boot menu.. Like the boot img. File
And finally it's back on.. Normal boot.. I didn't boot from download menu or recovery.. But in all honesty I'm 100% sure this will just happen again.. It seems to happen when I put the phone in the charger.. Then take it out and play with it.. For now in going to let it sit till the battery is in caution. Then charge it. I still have not added the Sim and loaded apps.. I feel that will be a overload of cpu and will most certainly freeze up and crash the phone
Ok, so up to date now.. Here's what's going on. The phone struggles to reboot from any on screen commands.. Like if I'm in Android.. And hold power.. Click reboot.. Then say like recovery.. Or anywhere.. It just turns off... If I also do this in twrp.. Say like install a rom or supersu.. It won't reboot... But! After it turns off.. And I wait a while and power it back on.. The file.. Rom etc was installed. So I do now have supersu installed and busybox. But the issue remains..which is a unstable OS.. Nothing to do with it being custom os.. But there is something wrong with the booting process.. What can I download if any apks.. Or files to help this?
Malistoff said:
Ok, so up to date now.. Here's what's going on. The phone struggles to reboot from any on screen commands.. Like if I'm in Android.. And hold power.. Click reboot.. Then say like recovery.. Or anywhere.. It just turns off... If I also do this in twrp.. Say like install a rom or supersu.. It won't reboot... But! After it turns off.. And I wait a while and power it back on.. The file.. Rom etc was installed. So I do now have supersu installed and busybox. But the issue remains..which is a unstable OS.. Nothing to do with it being custom os.. But there is something wrong with the booting process.. What can I download if any apks.. Or files to help this?
Click to expand...
Click to collapse
Might be stupid I know, but try wiping clean your SD card (back up a copy on your pc first) as well when you factory wipe and make sure that after that, you only add the files you need for recovery. Start up the phone after reset. To get a backup, if you're synced through google, you'll get everything back. If not, only copy your backup from titanium back into your SD card.
I went through a very similar situation last week. Long story short, it seemed the SD card had copied files which would interfere with the system.
Curious, did it happen after marshmallow update?
And did you try to downgrade back to previous lollipop version?
I assume it was Marsh that I was trying to Ota too. I was unable to boot successfully after that first try, so I honestly don't know.. I'm going to try your SD card idea. .. But once all that's done. Are you wanting me to redo a full rom install like through and wipe system, Davik etc etx? Or like wipe everything and start from like odin installing a recovery and so forth?
I ask these questions because.. What if I was to just take the sd card. And format the whole thing.. And out it back into the phone? I mean I might try that first then the other option.
Malistoff said:
I ask these questions because.. What if I was to just take the sd card. And format the whole thing.. And out it back into the phone? I mean I might try that first then the other option.
Click to expand...
Click to collapse
Well even if you format and you put the SD card back in with all previous files, same might happen.
When you format, just wipe all. Then if you want to downgrade, you need to have the previous version bootloader and baseband FIRST prior to putting the firmware ROM.
A simple (restore) wipe would just keep you at current version. And you can't easily downgrade the easy way from marsh to lollipop. Believe me, I learned the hard way
Flash through ODIN
So... I found my old XT890 laying around in my house and i decided to pick it up to see if it works.
I turned it on and immediately appeared an OTA update, so i went there and downloaded it.
When i installed it, the phone restarted and is now looping on the recovery screen (Android system recovery <3e>). I tried factory resetting it, wiping every data to see if it solved anything, but it didn't work.
I can make it to the fastboot menu by using the volume keys, but no option actually seems to work, only "Switch console [NULL: null]" that changes to "Switch console [default: ttyMFD3]". Wondering if that does a thing.
I've tried some solutions from threads here, but none of them seem to work on my phone. RSD Lite looks like it cannot recognize anything, and drivers and "unbrickers" does not work on me too. (Am I doing something wrong?)
Is my phone recoverable? It's the second time I update a phone via OTA and it loops on the recovery menu.
Facing a similar issue, death by OTA update, did you find a solution?
dash-- said:
So... I found my old XT890 laying around in my house and i decided to pick it up to see if it works.
I turned it on and immediately appeared an OTA update, so i went there and downloaded it.
When i installed it, the phone restarted and is now looping.
Click to expand...
Click to collapse