the tablet is stucked in bootloop: the message "samsung galaxy note 10.1" appears and after the display turns off and again reappears the message "samsung galaxy note 10.1" and so on ad infinitum, what can I do?
thanks a lot
gulluwing said:
the tablet is stucked in bootloop: the message "samsung galaxy note 10.1" appears and after the display turns off and again reappears the message "samsung galaxy note 10.1" and so on ad infinitum, what can I do?
thanks a lot
Click to expand...
Click to collapse
Have you tried accesing the recovery or download mode, by pressing the top/bottom volume? If so, you should be able to just flash a new fimware onto it.
gulluwing said:
the tablet is stucked in bootloop: the message "samsung galaxy note 10.1" appears and after the display turns off and again reappears the message "samsung galaxy note 10.1" and so on ad infinitum, what can I do?
thanks a lot
Click to expand...
Click to collapse
I too am experiencing this with my N8000.
What you should do is when you start or power on the device, Just leave it sit frozen with the writing you too.
Eventually, the device does boot, its like has a corrupt partition, or some type of corrupt memory or drive, or at least thats what I suspect.
Still experimenting and equally frustrated by this.
I also bought a used fully functional N8020 4G version to see if I could replicate or assist trouble shooting.
My efforts show that both S Pens works on the N8020 fine, and both S Pens do not work on the N8000 which has the boot issue too.
Tell me, does your S Pen work fine if and when you get your device booted?
Its really weird but if I dont get it sorted soon, I might just keep the N8020 and ebay off my N8000 which is a shame as both are cool, but I only need one & especially one that works.
Would be keen to hear from other users with similar issues or fixes.
ps:
I have tried a couple of stock roms, and issues (slow boot appears frozen and no S Pen functionality) are the same.
When in recovery, caches cleared and full factory date wipe data and install.
Other symptoms.
After doing the total wipe and reboot, the device still takes it time booting to do the install.
With and without charger inserted, its still the same.
Another point, when you turn off the device, the battery icon appears, it hangs on the battery picture with a little circle on it.
After about 2 minutes, the full battery colour progress icon shows and shows the charge happening.
Hence, suspicions towards potentially corrupt memory or drive, plus maybe cracked circuit board even? I rule nothing out here.
There you have it, appreciate feedback or other recommendations.
after installing a stock rom the tablet starts in bootloop then I discovered that letting the battery becomes exhausted, re-starting recovery screen appeared, I pressed on wipe memory rekindled and tablet restarted without encountering any difficulties.
The s-pen did not work because the csc was unknown, after flashing the right csc the spen has started to work well.
Anyway attentive to the stock rom you have installed I Have flashed a (4 files) from a site very close to samsung and it was fine, another downloaded from another site (1 file) not good.
Excuse for my bad english and I hope to help you
zzsomebody said:
I too am experiencing this with my N8000.
What you should do is when you start or power on the device, Just leave it sit frozen with the writing you too.
Eventually, the device does boot, its like has a corrupt partition, or some type of corrupt memory or drive, or at least thats what I suspect.
Still experimenting and equally frustrated by this.
I also bought a used fully functional N8020 4G version to see if I could replicate or assist trouble shooting.
My efforts show that both S Pens works on the N8020 fine, and both S Pens do not work on the N8000 which has the boot issue too.
Tell me, does your S Pen work fine if and when you get your device booted?
Its really weird but if I dont get it sorted soon, I might just keep the N8020 and ebay off my N8000 which is a shame as both are cool, but I only need one & especially one that works.
Would be keen to hear from other users with similar issues or fixes.
ps:
I have tried a couple of stock roms, and issues (slow boot appears frozen and no S Pen functionality) are the same.
When in recovery, caches cleared and full factory date wipe data and install.
Other symptoms.
After doing the total wipe and reboot, the device still takes it time booting to do the install.
With and without charger inserted, its still the same.
Another point, when you turn off the device, the battery icon appears, it hangs on the battery picture with a little circle on it.
After about 2 minutes, the full battery colour progress icon shows and shows the charge happening.
Hence, suspicions towards potentially corrupt memory or drive, plus maybe cracked circuit board even? I rule nothing out here.
There you have it, appreciate feedback or other recommendations.
Click to expand...
Click to collapse
sirduffy said:
after installing a stock rom the tablet starts in bootloop then I discovered that letting the battery becomes exhausted, re-starting recovery screen appeared, I pressed on wipe memory rekindled and tablet restarted without encountering any difficulties.
Click to expand...
Click to collapse
Hi Sirduffy,
Hey, thanks mate.
I only just finished doing some testing and made some progress myself.
It seems that it was one ROM that I seemed to get bogged down on.
Here is what happened for me.
I was using
Australia 2013 February 4.1.2 N8000XXCMB1 N8000XSACMB1
http://www.hotfile.com/dl/197957288/5d7de66/N8000XXCMB1_N8000XSACMB1_XSA.zip.html (GAVE SLOW STARTUP + FREEZING)
I then just installed this, and then did a cache wipe and full wipe reset. Now it boots perfectly every time.
Australia 2013 March 4.1.2 N8000XXCMC4 N8000XSACMB1
http://www.hotfile.com/dl/203343140/6bd284b/N8000XXCMC4_N8000XSACMB1_XSA.zip.html
sirduffy said:
The s-pen did not work because the csc was unknown, after flashing the right csc the spen has started to work well.
Anyway attentive to the stock rom you have installed I Have flashed a (4 files) from a site very close to samsung and it was fine, another downloaded from another site (1 file) not good. Excuse for my bad english and I hope to help you
Click to expand...
Click to collapse
Excellent, this is likely exactly the info I am looking for.
Can you tell me, is it possible to update only a CSC file with Odin 3.07 flash??
Or do I need to redo the whole ROM above and also include a individual added CSC file?
If so, where do or can we access these files or choices of files to match my Rom, or country, N8000 model etc etc.
Or where or how did you get your one?
sirduffy said:
The s-pen did not work because the csc was unknown, after flashing the right csc the spen has started to work well.
Click to expand...
Click to collapse
You out there still SirDuffy?
Can you please elaborate a bit more on where to get such csc for the S Pen to work.
My Rom as mentioned boots up fine and shuts down and does everything perfectly except S Pen which does not work.
Or at least when I pull the pen out of the tablet the Shortcut sidebar pops out confirming the pen is in use.
Would really appreciate more info or instruction if you can help.
I read on a few other threads about how to change CSC but I do not know where to get or what I am meant to be changing as yet.
Plus I am wondering why this would even be the issue when the CSC (Consumer Software Customization) denotes to a specific geographical region or carrier. The CSC code contains the info about software packages specific to a particular region, carrier branding and also APN (Access Point Name) settings for data connection. (as written from droid views).
So a little lost in the S Pen department.
Any body else out there got any suggestions to why my S Pen does not work?
I have done some tests as mentioned above previously and any suggestions would be great.
zzsomebody said:
So a little lost in the S Pen department.
Any body else out there got any suggestions to why my S Pen does not work?
Click to expand...
Click to collapse
Hi again folks,
Just replying to myself to advise others who may also have similar experiences as this, that I have now fixed my issue with S Pen.
I went back to ICS Stock Samsung 4.0.1 XSA, done a cache clean, then full data/wipe to finish install.
(with the SPen always inserted).
I then updated to JB Stock Samsung 4.1.2 via Kies, which also shows that the Pen is still working.
This is a very weird problem when it happens, how it happens, or why is not exactly known.
But my guess would be a partial corruption at some stage, some where through a process or a combination event that corrupts something obviously.
Anyway, persistence wins the race in the long run.
I have never rooted my device and always installed Stock Sammy Roms which for this model for me there are only 2 (but a 3rd using a different country as I did also use a German JB Rom to also try a CSC change, which also needs to have a cache reset and Data/Wipe type install too. And then when moving back to the Rom of your country of requirements, also do these cache cleans and full Wipes each step of the way which also enables the correct CSC as shown in Recovery Mode.
Eventually its like the device just gives in and surrenders back to S Pen Functionality.
The last thing I am going to say is that my device was or is still under warranty through Kogan.
I told them via email that I had been trying a few ideas from reading this site and they then in some way accused me of flashing with a custom rom which I have not.
---edited---
To this day, my N8000 has had NO Custom Roms on it, and I am totally Sickened by the fact of their reply which still shocks me.
But then, hence my reply.
All the best out there to those with S Pen issues or Bootup Freezing, as XSA through time will help you be persistent and move forward with or without warranty providing you have the patience to succeed.
Cheers~!
I have sent you a private messagge
zzsomebody said:
You out there still SirDuffy?
Can you please elaborate a bit more on where to get such csc for the S Pen to work.
My Rom as mentioned boots up fine and shuts down and does everything perfectly except S Pen which does not work.
Or at least when I pull the pen out of the tablet the Shortcut sidebar pops out confirming the pen is in use.
Would really appreciate more info or instruction if you can help.
I read on a few other threads about how to change CSC but I do not know where to get or what I am meant to be changing as yet.
Plus I am wondering why this would even be the issue when the CSC (Consumer Software Customization) denotes to a specific geographical region or carrier. The CSC code contains the info about software packages specific to a particular region, carrier branding and also APN (Access Point Name) settings for data connection. (as written from droid views).
So a little lost in the S Pen department.
Any body else out there got any suggestions to why my S Pen does not work?
I have done some tests as mentioned above previously and any suggestions would be great.
Click to expand...
Click to collapse
I leave it bootloop for long
I have left it for about an hour now it still bootlooping .. How much it take yours to finally boot ,thanks
zzsomebody said:
I too am experiencing this with my N8000.
What you should do is when you start or power on the device, Just leave it sit frozen with the writing you too.
Eventually, the device does boot, its like has a corrupt partition, or some type of corrupt memory or drive, or at least thats what I suspect.
Still experimenting and equally frustrated by this.
I also bought a used fully functional N8020 4G version to see if I could replicate or assist trouble shooting.
My efforts show that both S Pens works on the N8020 fine, and both S Pens do not work on the N8000 which has the boot issue too.
Tell me, does your S Pen work fine if and when you get your device booted?
Its really weird but if I dont get it sorted soon, I might just keep the N8020 and ebay off my N8000 which is a shame as both are cool, but I only need one & especially one that works.
Would be keen to hear from other users with similar issues or fixes.
ps:
I have tried a couple of stock roms, and issues (slow boot appears frozen and no S Pen functionality) are the same.
When in recovery, caches cleared and full factory date wipe data and install.
Other symptoms.
After doing the total wipe and reboot, the device still takes it time booting to do the install.
With and without charger inserted, its still the same.
Another point, when you turn off the device, the battery icon appears, it hangs on the battery picture with a little circle on it.
After about 2 minutes, the full battery colour progress icon shows and shows the charge happening.
Hence, suspicions towards potentially corrupt memory or drive, plus maybe cracked circuit board even? I rule nothing out here.
There you have it, appreciate feedback or other recommendations.
Click to expand...
Click to collapse
---------- Post added at 02:06 AM ---------- Previous post was at 01:53 AM ----------
I have left it for about an hour now it still bootlooping .. How much it take yours to finally boot ,thanks
zzsomebody said:
I too am experiencing this with my N8000.
What you should do is when you start or power on the device, Just leave it sit frozen with the writing you too.
Eventually, the device does boot, its like has a corrupt partition, or some type of corrupt memory or drive, or at least thats what I suspect.
Still experimenting and equally frustrated by this.
I also bought a used fully functional N8020 4G version to see if I could replicate or assist trouble shooting.
My efforts show that both S Pens works on the N8020 fine, and both S Pens do not work on the N8000 which has the boot issue too.
Tell me, does your S Pen work fine if and when you get your device booted?
Its really weird but if I dont get it sorted soon, I might just keep the N8020 and ebay off my N8000 which is a shame as both are cool, but I only need one & especially one that works.
Would be keen to hear from other users with similar issues or fixes.
ps:
I have tried a couple of stock roms, and issues (slow boot appears frozen and no S Pen functionality) are the same.
When in recovery, caches cleared and full factory date wipe data and install.
Other symptoms.
After doing the total wipe and reboot, the device still takes it time booting to do the install.
With and without charger inserted, its still the same.
Another point, when you turn off the device, the battery icon appears, it hangs on the battery picture with a little circle on it.
After about 2 minutes, the full battery colour progress icon shows and shows the charge happening.
Hence, suspicions towards potentially corrupt memory or drive, plus maybe cracked circuit board even? I rule nothing out here.
There you have it, appreciate feedback or other recommendations.
Click to expand...
Click to collapse
Guess you'll wait forever.
What a sick advice that was.
Read about flashing with odin in download mode + go to sammobile web page and download a for your device - it's a BASIC knowledge, you must know.
Bootloop does not mean that the internal drive is corrupted; it is the least possible issue which may happen.
Bootloop means that the system files are messed up or kernel is wrong or blah blah blah
Don't think too much about CSC... just flash the full firmware with odin and your device will be working again. Btw, firmwares are described with CSC names: i.e. XEO for Poland, EUR for Greece, etc. Choose one your CSC - or any other you wish (it will work without issues; you will have your language version; some not essential added content may differ only...).
And if after that your device will still refuse to recognize s-pen then it's a good point to admit that it's a hardware issue.
You may want to regulate spen potentiometers hidden under the button, with a knife. But that's the other story.
Sent from my GT-N8000 using Tapatalk 4
Related
I am having a very annoying problem with my Rogers I727R S2 phone on ICS stock.
The problem started to increase in frequency to become a real pain.
My phone would suddenly freeze and stop responding to screen touches for a bit, sometimes as long as 2 minutes, before bouncing back. When it comes back, it initializes as if it is restarting, so I would feel a vibration, lose all open applications and see icons start appearing on notification bar one by one. The media scanner would start working and software installed on SD card start appearing.
The problem happens spontaneously and out of the blue. It was occurring at less intensity on gingerbread before upgrading to ICS. After upgrading, it was not that frequent until only recently.
I noticed the problem goes away when I remove the SD card or when I am on flight mode with no Wi-Fi. I changed the SD card but this did not help. Connecting from home or work does not differ, so a problem with Wi-Fi would be ruled out. I once had a problem with home Wi-Fi when somehow the router’s DNS was not resolving, when this problem of mine was at its prime, and my phone was rendered unusable as it only takes couple of minutes before acting up.
I spent quite long time searching for an answer and so far no luck
I just placed a video illustration of the problem, and hope to get feedback on even where to head.
watch?v=akS59vFfIAI
raymonko said:
I am having a very annoying problem with my Rogers I727R S2 phone on ICS stock.
The problem started to increase in frequency to become a real pain.
My phone would suddenly freeze and stop responding to screen touches for a bit, sometimes as long as 2 minutes, before bouncing back. When it comes back, it initializes as if it is restarting, so I would feel a vibration, lose all open applications and see icons start appearing on notification bar one by one. The media scanner would start working and software installed on SD card start appearing.
The problem happens spontaneously and out of the blue. It was occurring at less intensity on gingerbread before upgrading to ICS. After upgrading, it was not that frequent until only recently.
I noticed the problem goes away when I remove the SD card or when I am on flight mode with no Wi-Fi. I changed the SD card but this did not help. Connecting from home or work does not differ, so a problem with Wi-Fi would be ruled out. I once had a problem with home Wi-Fi when somehow the router’s DNS was not resolving, when this problem of mine was at its prime, and my phone was rendered unusable as it only takes couple of minutes before acting up.
I spent quite long time searching for an answer and so far no luck
I just placed a video illustration of the problem, and hope to get feedback on even where to head.
watch?v=akS59vFfIAI
Click to expand...
Click to collapse
Try a different launcher.
the only way to troubleshoot is to start from scratch, read my 2nd link in my sig to restore to stock ics, reset within the recovery when odin finishes flashing, also keep out your sdcard out just to make sure your sdcard or its slot is not the problem. if still having probs its hardware failure, should still be under warranty
odeccacccp said:
Try a different launcher.
Click to expand...
Click to collapse
For reference, a different launcher did not do it
vincom said:
the only way to troubleshoot is to start from scratch, read my 2nd link in my sig to restore to stock ics, reset within the recovery when odin finishes flashing, also keep out your sdcard out just to make sure your sdcard or its slot is not the problem. if still having probs its hardware failure, should still be under warranty
Click to expand...
Click to collapse
I went through your instructions restoring to stock ICS (which did not wipe my data as I thought it would). This did not help though, and the problem persisted. After that I decided to a hard factory reset. This appears to have done the job and my phone was working very smoothly.
Because my phone is rooted, I restored to the buggy stock again using CWM in hope to be able to figure out how to my migrate my purchased software, data and settings after hard reset. I wonder if there is a way to preserve important files even with replacing systems. I want to hard reset again but I keep my important information
raymonko said:
I went through your instructions restoring to stock ICS (which did not wipe my data as I thought it would). This did not help though, and the problem persisted. After that I decided to a hard factory reset. This appears to have done the job and my phone was working very smoothly.
Because my phone is rooted, I restored to the buggy stock again using CWM in hope to be able to figure out how to my migrate my purchased software, data and settings after hard reset. I wonder if there is a way to preserve important files even with replacing systems. I want to hard reset again but I keep my important information
Click to expand...
Click to collapse
after restoring stock perform a reset in the recovery, if old data is still there after reset its a hw defect in the nand
edit: reread your post so nm what i just posted, use titu or other backup software
TL;DR - Flashed a ROM designed for N3+ (which is supposed to be same phone) but touch screen is unresponsive now. Need help with SP MDT or editing uboot
EDIT 15. July, 2014.: I've asked a guy from www.NeedRom.com to tell me his LCM driver and touchscreen which are located in factory mode (VOL- + HOME + POWER). He gave me same driver names as mine. LCM driver is RX_5720TM_813a and touchscreen is ili2113a.
I've tried removing the digitizer from my phone (lost warranty, but **** it, i'm not sending it back to china) and when i've entered factory mode again, it said touchscreen: (null).
So it seems that digitizer is properly attached (and should be working?).
Does anybody have a clue what's going on here? I've tried flashing 15 ROMs and NONE fixed the touchscreen. It's fully unresponsive. It doesn't work even if I off/on the screen few times like it worked before.
____________________________________________________________________________________________
Hello everyone, like title says I have unresponsive touchscreen on my Star N9800 phone. It's pretty much a new phone, octa core, quad core GPU, 2GB RAM, 16GB storage, etc.
What I've done is I flashed the ROM designed for Star N3+ (which is supposed to be same phone) but my touch screen is unresponsive ever since then. I've googled and read some articles on xda about SP MDT. It's a tool which can help us choose the display driver we want the phone to run with. I actually ran into a problem when i downloaded SP MDT. I can select the database etc, but when i get to scatter file it just doesn't want to load it. Either it's incorrect name or file type. I've downloaded 3 original ROMs from needrom.com and strangely the scatters seem to be different. But none is accepted by SP MDT. I need someone of knowledge who can teach me where to find uboot and how to edit it correctly. I'm not a linux/android programmer and I really don't wanna get involved into much programming. I understand basic stuff, i can find files on the system, i can edit build prop correctly, remove or edit boot_logo, boot anim etc, but this is a bit more than that. 2
Please share some knowledge with me and please don't point me to google. There's no solution there, i've googled for 3 days now. The last resort for me is to make a post here (and hopefully don't get ignored for spamming because this isn't spam).
My email is: [email protected] - you can notify me here if I don't get automatically emailed by xda.
Thanks in advance.
BUMP
Have no solution but would like to learn as well if anyone can help us...
I had the same issue but gave up and flashed another rom instead.
Flashing another ROM didn't help my problem. Well partially it did. I've flashed 2014-1-7 original N9800 ROM and the touchscreen only needs 1 or 2 off/ons till it starts working. I'm kinda fine with it because it was completely unusable. Flashing drivers with SP MDT didn't really help. I've tried flashing RX5720TM_828A (from N3+ ROMs) and LP057APK (default in N9800 ROMs) and RX5720TM_813A (2nd in N9800 ROMs), and so far my touchscreen works only with 813A LCM driver. When i turn off the phone and then hold VOL- & POWER & OFF/ON it goes to factory mode. There i clicked version and it showed that 813A is installed as LCM driver, BUT touchscreen says (null). Could it be that my digitizer is no longer connected or what? Cuz it sometimes works correctly without turning the display off/on at all.
EDIT 15. July, 2014.
EDIT 15. July, 2014.: I've asked a guy from www.NeedRom.com to tell me his LCM driver and touchscreen which are located in factory mode (VOL- + HOME + POWER). He gave me same driver names as mine. LCM driver is RX_5720TM_813a and touchscreen is ili2113a.
I've tried removing the digitizer from my phone (lost warranty, but **** it, i'm not sending it back to china) and when i've entered factory mode again, it said touchscreen: (null).
So it seems that digitizer is properly attached (and should be working?). It is possible that digitizer is detected but not working?
Even if i boot into recovery, screen doesn't react to touches.
Does anybody have a clue what's going on here? I've tried flashing 15 ROMs and NONE fixed the touchscreen. It's fully unresponsive. It doesn't work even if I off/on the screen few times like it worked before.
Apparently it's the calibration which ****ed up my phone. I'm now trying to figure out how to calibrate the screen through CWM.
ever find a solution?
i have a star n9800 too. suddenly i have been having all of the same issues, but here is the kicker: i never flashed anything but the stock rom that came with my phone, which was the same as kitkat version available on needrom.com. i have tried full factory resets, i have restored my original backup, none of it has fixed my phone. in factory mode, everything tests fine, but even when i launch in to TWRP, about 75% of the time, my touch doesn't work. i am wondering if one of the cables inside has come loose or something, but it is so intermittent that i find it doubtful.
hopefully you have found a solution that you can share with me.
Touch screen sometimes not react
AlexZap said:
i have a star n9800 too. suddenly i have been having all of the same issues, but here is the kicker: i never flashed anything but the stock rom that came with my phone, which was the same as kitkat version available on needrom.com. i have tried full factory resets, i have restored my original backup, none of it has fixed my phone. in factory mode, everything tests fine, but even when i launch in to TWRP, about 75% of the time, my touch doesn't work. i am wondering if one of the cables inside has come loose or something, but it is so intermittent that i find it doubtful.
hopefully you have found a solution that you can share with me.
Click to expand...
Click to collapse
-------------------------------------------------------
I have exactly the same issue and same signes, the phone itself is working good, ring for incomming phone but the the screen is not reacting i cannot take the call, it receives emails.
Did someone have a solution please let me know... thanks
My phone is star N9800, 2Gb memory and 16 Gb storage, android 4.4.2 originaly installed and was working fine during 9 months
Touchscreen - hardware failure
Hi,
I am wondering if you may have experience and be able to help me with my Star N9008 phone which has has had its touch screen stop working while I had it in storage for about 3 months.
Very well stored, no shock, no humidity. I keep it with my laptop backpack as a spare in case my everyday phone fails.
Today I powered it up to make sure battery was good (found it good at 95%) and update applications, etc. Basically, just checking it was still good to serve as a backup should I need it.
Thing is, I found the touch screen is completely unresponsive. Connected a mouse to it and verified all was working good, did up the updates, etc.. using the mouse. Reboot and boot into service mode and restore menu. Also, no touchscreen response (I use TWRP). Thus, it must be hardware failure.
From experience, would you know what would cause this, and how to resolve?
Thank you.
So, its been a while.
So, it's been a while. I still have the phone in storage and pity it doesn't work...
I haven't bothered opening up the phone if I don't know what to really try and also risk damaging it.
Also didn't bother ordering a new digitizer to replace as it's economically unviable.... the phone is now really getting behind as new tech is further evolving, so I do unfortunately see it going in the rubbish soon (along with two brand new batteries I had purchased for it just before it died).
Has anyone been successful at finding the culprit?
In my case, it was fine and very well stored... so I don't really have an explanation other than the phone possibly having a 'countdown timer' to break it... (yeah, a bit too conspiratorial, lol)
I did not find a solution yet , phone still sits in storage
i just got my note pro 12.2 wifi version (international) a few days ago and already experiencing problems, firstly the wifi was so slow so i updated it OTA to the latest stock firmware i can't remember what it is but it's the latest official 4.4.2 they have and that improved the wifi but now i'm encountering issues of rebooting randomly after using facebook app. it's always after i lock the screen it suddenly reboots after 2 mins or something especially if i have say been using a lot of memory for it.. ie if i scroll down 4000 friends that's when it always reboots once i lock the screen. is this liekly to be hardware or software issue or an app issue?
i have only had it a few days so haven't managed to play with it enough to test it to the max.
just now it rebooted and i played one youtube HD video and used multi window to use the facebook app (old version 7.0 - i like this version).. but i hadn't used the facebook app that much while on, the only thing i did different was i plugged in my samsung s3 charger into the note pro to test how long it would take to charge using a usb 2.0 connection instead. it's official charger official cable, is that likely to cause reboot issues?
previously it was just after using facebook for a long time for a ram intensive amount, i also tested it after reboot and using facebook a bit and locking screen and it didn't reboot so it made me think ok it's just when facebook is being used a lot and all the ram and memory is exhausted caching 4000 friends viewing so i didn't think anything of it.
is this likely to be hardware or software issue? are hardware issues ever the main problem with rebooting?
I know the usual tests, having to use odin to flash official firmware, trying a different facebook version, removing and not using facebook at all and see if it still reboots and lastly factory reset.
ideally i'd like to avoid all of those things as it is a major hassle and i can live with the reboot issue provided it isn't a hardware problem. is there anyway to test it to know for certain it is hardware and not software and the app?
edit: it keeps rebooting even if i dont use the app
seems to happen when i lock the screen sometimes it just reboots randomly.
anyone else have this?
You could try to remove that facebook app and see if that fixes the problem.
does anyone know what is causing this?? is it hardware?
i've factory reset removed all apps, then added one app at a time then added about 6gb of videos and added wakelock detector. all seemed fine
then i tried to unmount the sd card and then it rebooted.. why is it doing this??
pete101 said:
does anyone know what is causing this?? is it hardware?
i've factory reset removed all apps, then added one app at a time then added about 6gb of videos and added wakelock detector. all seemed fine
then i tried to unmount the sd card and then it rebooted.. why is it doing this??
Click to expand...
Click to collapse
Could it be a bad sector on the SD card? I'd long format it using a pc to be sure.
Sent from my SM-P900 using Tapatalk
it's not the faceboook k app i've realised now it just coincidentally seemed to be that as it is ram intensive.
i factory reseted and then put the app back on but didn't log in. 3 times it has rebooted by itself over different scenarios.. 1 plugging in a samsung usb 2.0 charger from a samsung s3, 2 when unmounting sd card, 3 when closing the screen when any ram intensive app is in the background (there's still like 500mb of ram left!! i dont know why it's rebooting like this.
i can't figure it out. is anyone else having these issues? im not sure if it's a kitkat 4.4.2 issue.. reading forums from other users with different devices i'm seeing the reboot issue coming up alot especially on the s4.
http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046/page22
but i dont know for certain if it's a hardware issue.
my next steps which i really want to avoid is to factory reset AGAIN and not load any apps (the problem with this is it requires a certain amount of ram intensity to be used before it randomly happens.. if i dont add any apps like instagram or facebook or tumblr i can't get it back to the state where it reboots randomly)
i've also enabled all apps (i usually disable all the bloatware i can without being rooted) but it does bring up errors of android.core.process has stopped etc and some gapps errors (im hoping this is the cause of the reboot) and see if it reboots. it's difficult recreating the scenario consistently.
i udnerstand it might reboot if you've overused the memory but it clearly shows lots is free so i can't figure out what is causing it?
my next step after all this is to flash the latest version of stock so i can't put it down to the OTA updates that is causing it. if that fails i revert to odin to flash the original 4.4.2 it came with.. and failing that i'll have to return it
does anyone have any ideas whether it is hardware (maybe the power button is slightly off so when you press down it in a certain angle it triggers a restart?)
or is the motherboard or corrupted sector of the memory which when it writes over it causes the reboot?
i always assumed reboot issues were normally always firmware issues and not hardware.. surely samsungs quality control is a bit better than that??
If it were me I would yank the microsd card out, factory reset, set up just my gmail without allowing auto backup/restore and apply all updates. I'd then let the tablet run for a full day and use it just for web browsing and Youtube to see if the problem is still there. I would not install anything for at least a day, including the microsd card. This would be as stock as one could get and rule out the possibility of it being any software that I installed or the microsd that I was using.
I suspect it's software but the only way to know is to be patient and test it out for sure.
Sent from my SM-P900 using Tapatalk
Hi,
same tablet, bought there is 3 weeks. I installed the latest firmware update (XXUANI1)
I rooted the tablet (to allow sd-card writing).
and that's it.
like some of you, I have random reboot.
I can't remember if it happened before the root or not. I think that yes, but I am not 100% sure.
I don't see anyone reported that the root cause random reboot...
it is really random. sometime, the tablet stay one night without reboot, sometime, I can have 3 reboot in one hour.
I don't find what kind of application is causing that issue.
I really believe that it is software. before the firmware update, I stayed 2 weeks without any issue.
I tried to reboot in recovery mode, and wipe the cache, without success.
I will probably try to do a factory reset...
Olivier
orobin said:
Hi,
same tablet, bought there is 3 weeks. I installed the latest firmware update (XXUANI1)
I rooted the tablet (to allow sd-card writing).
and that's it.
like some of you, I have random reboot.
I can't remember if it happened before the root or not. I think that yes, but I am not 100% sure.
I don't see anyone reported that the root cause random reboot...
it is really random. sometime, the tablet stay one night without reboot, sometime, I can have 3 reboot in one hour.
I don't find what kind of application is causing that issue.
I really believe that it is software. before the firmware update, I stayed 2 weeks without any issue.
I tried to reboot in recovery mode, and wipe the cache, without success.
I will probably try to do a factory reset...
Olivier
Click to expand...
Click to collapse
Assuming you have custom recovery installed as well; have you tried wiping dalvic? It will force applications to recompile and possibly fix a corrupted application or its associated files.
Hi,
I just checke.…
I was thinking that the root method was not setting the knox flag, so i was thinking there is no recovery in the file flashed… .
I was wrong.
My waranty is void, knox is set. I still have no custom recovery : in the file provided by chainfire, there is a recovery which is probably coming from samsunG…
So i will install a new recovery and try to wipe all caches dalvik.etc.
Hi,
since my knox is set now :
I tried to install TWRP recovery, which allow me to do a wipe of the cache AND dalvik Cache.
it did not resolved anything. the tablet still reboots randomly.
then, I decided to restart from scratch :
I flashed the same firmware I had, using ODIN, and do not root it.
this is this firmware : http://www.sammobile.com/firmwares/database/SM-P900/XEF/
I will keep you updated if it solve the reboot issue or not.
thanks
Olivier
pete101 said:
i always assumed reboot issues were normally always firmware issues and not hardware.. surely samsungs quality control is a bit better than that??
Click to expand...
Click to collapse
Hi
I had the same problem and also thought it was the power button that was faulty but then I flashed the previous firmware then tried to use it a bit and no reboots since so I guess samsung released a new firmware that solved the slow wifi problem but then boosted it a little too much or so it seems judging by the reboots whenever there's too much overload.
So I guess for now I will stick with an older firmware
oops... it rebooted while I was surfing the play store so I guess I spoke too soon
I purchased the new Verizon Ellipsis 10 in late November. I believe the tablet was released for sale in mid November. My question is can it be rooted? I see the Ellipsis 7 and 8 can rooted. Wondering if anyone would be working on this or because it from Verizon no one cares. I can't find the tablet mentioned on any search that I do. I Have been checking daily to see if the device will have development on it. Thanks in advance for any information.
In the same boat. Need some help you smart tech guys out there. How can I root my Ellipsis 10?
I have the same tablet, and I do not think it could be rooted, at least not in the near future. The tablet comes encrypted (which I am not too happy about....I just noticed it) and cannot be decrypted, even if you do a factory reset. It runs fine as it is, but would be greatly enhanced if it could be decrypted. I also think there are very few devs on this forum that really care a lot about this tablet, so you may not see too much work being done on it.
Same here, just picked one up. Really hoping that there will be a root for this at some point soon. Someone please help us all out!
wish I would have saved the 50$ now, and got the Samsung tablet for free... it's OK, the biggest problem for me is the audio output being too quiet. all the "volume booster's" on the play store have been jenky, to say the least. if anyone has suggestions of a "good, volume booster", or work around, please let me know. thank you for you time.
Oh, No! Sadness!
mikekoz said:
I have the same tablet, and I do not think it could be rooted, at least not in the near future. The tablet comes encrypted (which I am not too happy about....I just noticed it) and cannot be decrypted, even if you do a factory reset. It runs fine as it is, but would be greatly enhanced if it could be decrypted. I also think there are very few devs on this forum that really care a lot about this tablet, so you may not see too much work being done on it.
Click to expand...
Click to collapse
Please, influence some senior devs to help you with this issue!
qtair7 firmware files
https: / / " www dropbox com " /s/f8ye7yw24mjqiva/IR7-20C59.7z?dl=0
just fix the text when u enter in address bar (-""'s,+.'s)
so i downloaded the IR7-20C59..7z package from the software upgrade/repair tool from verizon... I extracted the files and sent the boot.img to my tablet (qtair7) and used magisk manager to patch the boot.img then I used ubuntu to adb pull the magisk-patched-boot.img and modded it using abootimg and changed a few things from default.prop.. ro.secure=0 ro.debuggable=1 and drm.service.enabled=false .. (just saying im an amateur android enthusiast with little experience. ive played with image kitchens and compiled a kernel and ported a rom for the samsung on5 indie variant to have sound on my smg550t1. worked but all google services and apps crash constantly.. but anyways) i dont really know what im doing just saying this is what i did. repacked magisk-patched-boot-new.img then i sent the adb reboot fastboot command to my tablet and it fastboot flashing unlock , fastboot flashing unlock boot, fastboot flash boot magisk-patched-boot-new.img. fastboot continue, fastboot reboot.. the tablet boots and is rooted with magisk.. now i installed busybox to sbin. i have done this 2 times. im not sure if its the busybox or the magisk, but when i reboot following the above steps i get the verizon splash screen and in the bottom righthand corner of the screen it says modified. then boots to recovery. and now can only boot to recovery. now i have the upgrade/repair tool .iso on usb flashdrive that i use to repair my device from this state. which sometimes is a pita.. i have to continually attempt to repair sometimes it takes 2 days.. before it finally works.. i dont know why.. but it boots from fastboot the first time fine. and would like to know how to stop the soft bricking of my device or how i can obtain a twrp.img for this device QTAIR7.. please help ive been working on rooting my tablet for over a year. and feel that i am very close . thanx
Anyone interested in the system.img or any other partitions.. the Dropbox file is only the recovery flash files. I think. I know I couldn't edit system.img from the file with any kitchen but the system.img I dd'd from my device can be edited with kitchen. It's is 3.7gb so in not going to post unless someone can do something with them
Please share some info on the file you posted,..
jonthn41 said:
qtair7 firmware files
https: / / " www dropbox com " /s/f8ye7yw24mjqiva/IR7-20C59.7z?dl=0
just fix the text when u enter in address bar (-""'s,+.'s)
Click to expand...
Click to collapse
Hello, THANK YOU!! This is the most progress I have made in months! I don't know what it is, what it offers, or what to do with it yet, but it is a step!
Could you maybe say what it is, what it will do (how it helps..) and what to do with it?
My Verizon Ellipsis 10 (qtair7), even after wiping the cache, even after doing a factory reset, (even after 'disabling' all but FEW APPS!) JUST SPONTANEOUSLY REBOOTS every time i try to do anything, I try to watch a video it is fine for 5 minutes or an hour then I push volume up or touch the screen and suddenly it reboots, totally random, Clearing the cache gets it to works for a while but it always does it again it has NEVER been usable really,.. It pops up some screen often like"Google Play Services have stopped' something like that,.. Will this help with any of that? Make it more,. stable?
I wish I could just do ANYThING simple to make it better I just use it for video playback,.
THANK YOU!
I have the same tab with the same issues. Rebooting, random cut out and full on reboot. Just before it became target practice I decided to take it apart, just because that's what I do when I'm bored and my ADHD is taking over. I looked up the tab on youtube to see if there was any vids of how to get it apart and found a guy that said he fixed the with the tablet that no one could figure out. Meh I was like ok I'll give him a couple seconds checked it out. He found that all connections, screws holding boards down, and power were all loose. Once he went through all of that it had fixed the issues. So I tried it and damn, everything from screws holding boards down to power feeds were all loose, really bad loose. Got mine working good now. Haven't had issues since. Now if I can get it rooted I'll be good. And I suspect the loose connections would also potentially cause the battery to go bad from excessive amperage draw and charge in short time, over time.
Greetings xda-developers,
I own a galaxy tab 2 P3100 16GB model since march 2013 (pretty old yeah, but i like it, its my first tab ) It is running everything stock (recovery plus OS, JB 4.1.2).
It was working all good and serving good for my browsing, whatsapp, mails, youtube, hotstar etc etc. (heavy user of tab) Suddenly on one fine Sunday morning it restarted by itself. I thought this to be normal but it wasn't. After every 10 to 20 seconds I could hear the starting tone. When i looked to the tab, it was pretty warm on the left side where it usually does when used heavily, but it was acting strange.
The tab was restarting by itself! The home screen appears, i could start an app and suddenly it restarts and this continues every 20 seconds until the battery goes low.
I thought two new installed apps would e problem so i removed them and to my surprise(!), they were back again after next 'auto restart'. The 'auto restart' stuff happened back in January this year (after my nephew installed many games on it) but was solved when I did factory reset from settings menu.
But this time nothing successful. Neither factory reset from settings menu nor from recovery. I have tried using twrp and CM11 last year but returned to stock after few months.
I tried flashing twrp, cwm recoveries but after every boot it returns to stock. Even flashing OS didn't helped.
My problem is similar to these:
https://forum.xda-developers.com/showthread.php?t=2641158
and
https://forum.xda-developers.com/showthread.php?t=2627490
and
https://forum.xda-developers.com/galaxy-tab-2/help/unable-to-install-twrp-t3696545
Also the stock recovery screen shows the following at bottom:
# Manual Mode #
-- Appling Multi-CSC...
did not match sized '/system/csc/common/system/csc/default_workspace.xml'(No data available)
(I wanted to attach image to this post but could not find an option.)
From all my readings on this forum, I can conclude (?) that its an emmc issue (end of life?).
Need your help guys.
The tab is in excellent condition except this issue. Can this be solved?
I am from electronics and embedded system (microcontrollers) profession and hobbyist. I know replacing emmc or motherboard (or scrapping the tab, NO! i don't want to though i now own the Lenovo tab 4 8 plus 3GB RAM+16GB version ) is an obvious solution.
A (may be obvious) possibility came in my mind if external memory card could be used for booting and I (and many others) could bring their tab to use (instead of making it a paperweight )
I though this to be possible solution: https://forum.xda-developers.com/galaxy-tab-2/general/discussion-alternative-tab-2-emmc-bug-t3306862
but i am not able to understand the instructions and the links posted by OP are not functional.
Can this be a solution:
https://forum.xda-developers.com/showthread.php?t=1866675
OR
I am thinking of this:
I got schematics and service manual for p3100 from internet. I looked the datasheet for OMAP4430. I am thinking whether the boot sequence can be changed (or may be no need to change the sequence) and we can boot from external micro SD card
or something like
https://forum.xda-developers.com/showthread.php?t=1312391
or can https://forum.xda-developers.com/showthread.php?t=2109044 be used?
But whenever i plugged my tab in windows without battery or with battery, initially i could see new device found 'OMAP....' something but immediately after 2 or so seconds it shows device unplugged.
Any comments guys?
Thanks for reading patiently the long write up...
You can't boot from external SD because you aren't able to flash a high modified boot.img if your emmc got read only.
You'll need to replace the emmc or find someone who can flash an updated emmc firmware via isp (but the issue might come back in short time after firmware update).
Thanks for reply.
Well i have to search someone from my nearby city for such service.
Is it not possible booting from external even if the boot sequence is changed, i mean if hardware is modded to change boot sequence?
Humm but it will require the primary and secondary bootloaders then...
The pandaboard has increased by curiosity of such possibility. I think i need to study more...