Related
Hi!
Sorry I'm not sure if i searched properly the forums, but I'm wondering if anyone else haves problems with the original rom ( I think its called stock ) 4.1 from HTC One S. I own the phone from 6 months and before updating the g-sensor randomly stopped working it would only start working again with factory reset ( later I found out with restart also worked, because shutdown doesn't clean memory? ).
I was patient for the update and since I updated I noticed that the phone seems slower, already factory reseted, deleted everything, it no longer seems to bug the g-sensor, but it seems to bug quiet often notification bar stuck at mid screen.
Anyway I was wondering if anyone else haves this kind of problems? should I just send it to the factory, it is still on the guarantee.
Thanks for any answers
Edit: by the way, can't seem to use Swift Key, after a while starts blinking
" ( later I found out with restart also worked, because shutdown doesn't clean memory? )."
You probably have fastboot enabled. Its roughly the same as windows sleep-mode, it saves everything in memory to provide almost instant start up.
There seems to be quite a lot of random problems with the official JB rom. I'd suggest you to try one of the many custom roms available here.
Goatshocker said:
" ( later I found out with restart also worked, because shutdown doesn't clean memory? )."
You probably have fastboot enabled. Its roughly the same as windows sleep-mode, it saves everything in memory to provide almost instant start up.
There seems to be quite a lot of random problems with the official JB rom. I'd suggest you to try one of the many custom roms available here.
Click to expand...
Click to collapse
I tought of getting it rooted, but I still have 1 year and half of guarantee so I don't want to lose it , i have my other phone desire rooted through
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
Hi all. 1st post here.
I've been having a lot of trouble with my Galaxy Tab 2 lately. I rooted it a long time ago. Never had trouble with it. A few days ago, after charging it, I tried to start it, but when it starter, after a minute or so, it restarted. Normally the tablet only did that when it was froze due to many apps or processes being used at the same time. The problem is that the tablet never started properly after that one time. It's on some type of infinite loop. It starts, stays on for 1 or 2 minutes and then freezes and restarts. Well, i thought what most people would think at the moment: "I need to reset the tablet". I went to Recovery mod, made the format, but when the tablet rebooted, everything was untouched. No format. Odd to me. I then tried to return to stock. If it after that the problem was still there, at least I could be able to call for warranty. Odin gave me a lot of failed errors when I was trying but there was once that it said "Pass". Rebooted, still the same. Updated the recovery, tried to format, still the same. I'm running out of options right now. I don't really know what can be the problem and how can I fix it. I thought that if there was a way to format it like in recovery but using my PC it would do something (or not)
I appreciate any type of help.
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
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...