Dear experts
I am very new to Android, and this N90FHDRK is my very first Android device ….
So for my N90 I am using Glassrom V2a, and I have tried several others as well.
Since the last 2-3 weeks I face strange problems:
- Tablet does not boot
- Tablet does not switch off (goes off only after pressing on/off for 30sec)
- Invalid unlock-code
- Battery-status unknown
- Disappearing applications and wallpapers
- Apps crashing
- ‘cannot mount /cache or /data’ in CWM-mode
Of cause reinstalling and wiping everything helps, but the problems come back once a day … Once in a while just reformatting /data helps.
What could be the root-cause:
- Some application corrupting parts of the (internal 16GB) flash-memory – but which app? I might even restore the same app again and again
- Corrupt flash-memory (with cells loosing data, or not writable)
- Memory-controller
Looking at the internal 16GB ‘corrupt flash-memory’: in the ‘PC-world’ I would run some ‘chkdsk’, and I also know that during low-level-formating bad blocks are recognized and marked at ‘bad’
Is something similar available for Android or the underlying Linux operating system?
Even if I manage to identify a bad-block, can I mark it as ‘bad’, and would this marking survive a restore?
Of cause I could simply send the tablet back to China, but that brings other problems and potential risks ….
Thank you for your help
Tiemichael said:
Dear experts
I am very new to Android, and this N90FHDRK is my very first Android device ….
So for my N90 I am using Glassrom V2a, and I have tried several others as well.
Since the last 2-3 weeks I face strange problems:
- Tablet does not boot
- Tablet does not switch off (goes off only after pressing on/off for 30sec)
- Invalid unlock-code
- Battery-status unknown
- Disappearing applications and wallpapers
- Apps crashing
- ‘cannot mount /cache or /data’ in CWM-mode
Of cause reinstalling and wiping everything helps, but the problems come back once a day … Once in a while just reformatting /data helps.
What could be the root-cause:
- Some application corrupting parts of the (internal 16GB) flash-memory – but which app? I might even restore the same app again and again
- Corrupt flash-memory (with cells loosing data, or not writable)
- Memory-controller
Looking at the internal 16GB ‘corrupt flash-memory’: in the ‘PC-world’ I would run some ‘chkdsk’, and I also know that during low-level-formating bad blocks are recognized and marked at ‘bad’
Is something similar available for Android or the underlying Linux operating system?
Even if I manage to identify a bad-block, can I mark it as ‘bad’, and would this marking survive a restore?
Of cause I could simply send the tablet back to China, but that brings other problems and potential risks ….
Thank you for your help
Click to expand...
Click to collapse
Too bad, It seems I am quite alone with this problem
+1. If anyone has any expertise with this specific tablet that would be greatly appreciated. I think the problem we are facing is similar and that is I want to go to stock and which the .img file is released, its just the matter of using it. I am used to CyanogenMod for my nexus 4 where i would simply have the file already signed and used using recovery mode. But this .img file is a lot different and if someone could point in the right direction on how to do it that would be wicked. P.S. its so unlike my Nexus 4 with the actual seeing the android open and picking bootloader and all that, its jus a black screen and the computer recognizes it.
Related
As I suspected early on the issues boil down to corruption within the User Data or Cache partitions, less often on the system partition due to an unexpected shutdown of the device. Shut on these devices need to follow the proper shutdown routine as any linux environment. Following this best practice will ensure that all data is written out to its corresponding file system by flushing all cache, unmounting the file system, etc..
Here are the culprits of why we see so frequent random Force Closes, Market Resetting, etc. ultimately resulting in an unclean shutdown, corrupting some data.
1. The button we use is also a forced off button. Typically if you hold it down too long you are powering off the device.
2. Some times when in sleep mode you see the Viewsonic logo upon starting - that means that the system shutdown (most likely crashed).
3. If your running Vegan your hitting the reboot.. I dont know for sure but I suspect this is NOT performing a clean shutdown... (I dont have a copy of the source)
Anyway... wanted to pass this on... as last night my data partition became corrupt after using the Reboot function on the Poweroff menu of Vega 5.1..
shouldnt need source code to debug a dirty shutdown..Cant you just run an adb logcat? maybe run the shutdown command in a terminal on the device and pipe the output into a text file for later viewing
My internal memory has to be repartitioned every few weeks - I'm certain that something is corrupting it over time. I had massive FC's just a week or so back where the SD partition re-do was the only fix.
I suspect that this happens in stock, as well - the problem of course is that there is no fix for a stock user, other than a return / exchange.
roebeet said:
My internal memory has to be repartitioned every few weeks - I'm certain that something is corrupting it over time. I had massive FC's just a week or so back where the SD partition re-do was the only fix.
I suspect that this happens in stock, as well - the problem of course is that there is no fix for a stock user, other than a return / exchange.
Click to expand...
Click to collapse
I have been on stock since I got the device just moving to the newer versions when they come as OTAs and have never ever had to mess with my partition, so I don't THINK the issue is in the stock software. In fact, the only problems I've ever encountered were when I used the enhancement pack, in which case my screen started to become unresponsive and the calibration.ini I was told to try did not work. Since then I went back to 3389 and the device has been perfect ever since.
I could be wrong though and just very, very lucky....here's to hoping. Another thing to consider is maybe the memory is going bonkers for some reason. I've had flash memory that lasted forever and I've had flash memory that has gone wacky over a period of 6 months....even a wipe by the utility designed to do it doesn't fix it properly. I don't know how CWM wipes or partitions the memory, I do know there's supposed to be a special way to do it.
If it's not faulty memory off the bat, then that leaves something in the 'extras' being put into these ROMs. Maybe some of the newer tegra drivers or some coding to make the ROMs faster - I'm just saying, can't leave any stone unturned.
Has anyone that has stayed loyal to stock encountered these issues? We have to ask that question I think. Then we ask how many of the people playing with ROMs are seeing the issues, this would include people that have used CWM to partition and mess with their mounts initially.
I can say I've never seen data disappear from my internal memory or my SD and I can also say I've never seen multiple FCs except after putting in the enh. pack (keep in mind I got my tab on Dec 20something, so I had 3053 and then 3389 soon after).
The first sign of anything being 'corrupted' on it's own at stock and I'll be sending mine back. As an owner of Android since Android's been around, I've never had my G1 or MT4G (or any smartphone before it) become corrupted due to not being shutdown or reboot properly and while this is a tablet I think the fundamentals should be the same. Pampering 'faulty' memory is a risk. You can wipe and re-do all you want, but if it's faulty it's going to stay that way.
Ive done that but I guess you can say unfortunately I have had only clean shutdowns since then... The last corruption I had I formatted my data and cache partitions before I ran logcat.... Of course thought of that afterward....
Generally if any has FCs, etc. etc. run a logcat and post it here... we will be able to confirm this...
We could change the way the partitions are created and add a sync which will further reduce chances BUT will take a performance hit...
I am very surprised though as the EXT3 filesystem is very resilient to dirty shutdowns (more than EXT4)...
I reviewed the out of the box framework source on the google GIT and technically if a reboot command is given a clean shutdown is performed via the framework... but the widget on the shutdown screen I suspect is not calling the method properly or is not being called at all... All speculation at this point... But for sure there is corruption occurring..
Since the last corruption I switch over to pershoots kernel... Even though his kernel seems to be a little slower he seems to have included the latest drivers which other items relate to data integrity (im reading into the release notes).
NEO: The first thing I did when I got my device install CW, Vegan... Updated Kernels also... Never had an issue until the first time (yes about a day ago) I used the reboot feature of Vegan. That corrupted my user data. I suspect if you have not been performing clean shutdown then you are just lucky. Linux, like any other OS, even with Journaling if you do not perform a clean shutdown you will surely encounter SOME corruption. Typically the corruption is re-mediated by the the file systems integrity controls. You dont even know it happened... 1 in 1000 the integrity controls can not overcome the significant loss of data and thus results in crashes, etc. Some times the corruption happens in areas where are lightly used thus why you would get a Market Reset... that data is easily replaceable on the fly. Core components that require subsystem to run are not replaceable and thus why I had to reformtat. What upsets me is that this failsafe is not working properly most likely as its far too frequent.... I too suspect it has something to do with CW.
But again.. between the wrongly placed power switch, the unprovoked reboots (ie viewsonic screen showing when trying to wake up the device) and the reboot button possibly not performing a proper shutdown will sure increase the chances in a wider distribution of users. So it may not be a CW issue and just some poor design.
When I have time today I will verify if the reboot function performs a clean shutdown... if anyone has the time please post the logcat... Im going to be running around today and will try to get to it..
watson540 said:
shouldnt need source code to debug a dirty shutdown..Cant you just run an adb logcat? maybe run the shutdown command in a terminal on the device and pipe the output into a text file for later viewing
Click to expand...
Click to collapse
stanglx said:
I am very surprised though as the EXT3 filesystem is very resilient to dirty shutdowns (more than EXT4)...
Click to expand...
Click to collapse
AFAIK they're running yaffs ATM. Next move is to ext4...
Read some articles about this several weeks ago, apparently many apps do not properly flush file caches. One of the articles was a Google developer post about file corruption along with their API method which did a cache flush prior to a close, then a bit later was the Google indication that they were planning to move to ext4 FS to further help alleviate the problem.
stanglx said:
I am very surprised though as the EXT3 filesystem is very resilient to dirty shutdowns (more than EXT4)...
I suspect if you have not been performing clean shutdown then you are just lucky. Linux, like any other OS, even with Journaling if you do not perform a clean shutdown you will surely encounter SOME corruption. Typically the corruption is re-mediated by the the file systems integrity controls. You dont even know it happened... 1 in 1000 the integrity controls can not overcome the significant loss of data and thus results in crashes, etc. Some times the corruption happens in areas where are lightly used thus why you would get a Market Reset... that data is easily replaceable on the fly. Core components that require subsystem to run are not replaceable and thus why I had to reformtat. What upsets me is that this failsafe is not working properly most likely as its far too frequent.... I too suspect it has something to do with CW.
Click to expand...
Click to collapse
That's my point. How many times since we've had our Android and smart phones have we had situations where they are turned off or rebooted without the proper procedures? Power drains till they die, they drop and reboot, we clog them up with stuff or some app drives them nuts and they reboot or shut off....Yet you rarely if ever hear about a phone's data being 'corrupted' with stock software. Sure it may happen with official OTAs etc, but never just off-the-bat like what's happening with the G-Tab. But it's not happening to everyone either so I'm just looking to see if there's a pattern.
Even since the G1 and newer phones, you don't really hear about or see file corruption issues on stock software with these phones. It's when users start going to ROMs that you hear of issues cropping up. That's not to say it doesn't happen at all at stock, I just think we're seeing it in a more concentrated fashion here because of all the formatting, re-partitioning, etc. At first you hear, 4GB is a great partition size, then you hear there are problems so move to 2048, then you hear 256MB swap, then no swap since Android doesn't use it. Then dataloop for speed, then no dataloop because of critical issues. Rules and instructions change almost on a daily basis. I think it's more than these poor flash drives can take I find sometimes it's good to keep it simple.
I owned a Vibrant for a while...decided it was a PoS when at stock I was seeing bad lag (because of Sam's terrible FS). People said...do the speedhack, it'll be fast!, but what was the caveat? Having to reboot the phone almost weekly, sometimes several times a week, and people were seeing what? Data corruption. That's not for me. Give me something that is lag free (doesn't have to be a bullet train, just don't skip on video or audio and make sure my live wallpaper and drawer animation is fluid and I'm happy!). Point being....keeping it simple may help to alleviate some of the issues. If people are seeing these problems with stock, then you're absolutely right and it would be a point of contention that the failsafe isn't working right.
Otherwise it seems the stock OS on these things are able to self correct in most situations and it may just be some of the many tweaked features in these ROMs doing something it shouldn't - or, I may just be very lucky indeed.
I'm still dying to get the OTA - I haven't seen one since 3899 yet.
Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.
Rather than do that, I reset the phone, wiped Davlik cache and Fixed Permissions (took a long time!), then rebooted.
That sort of worked, but a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
What's the way-ahead here? Am I stuck doing a factory reset? Or even formatting the SD card?
Thanks in advance.
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
jeffsf said:
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
Click to expand...
Click to collapse
Okay, thanks!
Anything else on the SD card I should back up besides DCIM / Media-> Ringtones/MP3s / "ui" / TitaniumBackup?
(Got about an hour while this stuff goes off to my HD...)
Hoo! Thought I effed myself for a sec - from CWM I was wiping all partitions... including /sdcard.
Then I realized... $#¡+... my ROM is on there!
Fortunately CWM has the "mount USB storage" option.
*whew!*
I was going to add format the sdcard from the phone. But you did that. Typically when what happened to you would happen to me it would be from some app updating and for whatever reason got corrupted during install and fouled the phone up. If you use TiB I highly suggest setting a automated task to back up your TiB backups to drop box, google drive or box.net. Then in these situations you have a recent TiB to fall back on.
JaimeZX said:
Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.[...]...a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
Click to expand...
Click to collapse
Hi JaimeZX,
I am curious if you have recently rooted, flashed to stock, or installed the VB or Basic w/a twist kernel? I am running the exact same setup as you list (minus the modem) and this *exact* same scenario happened to me on the exact same day. March 12th, at about 10pm.
Detail as much information as you can, I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel. Perhaps there is an issue with the stock packages, or the USB driver ghosts (I've deleted all USB assigns at all ports and reinstalled for device detection in Heimdall). Hopefully we can get a good list of information to help us fix an issue that is apparently quite catastrophic (in that /data seems to corrupt) and save others from a future headache.
I have searched the dev threads to no avail, and as a general rule it seems that if problems are brought up they are usually met with "try flashing back to stock," "gremlins," "no one else is having problem 'X'," etc. even in cases of users with multiple complaints of the same issue. Both the DSP Sound force close upon EQ preset select and the issue that some had with the Messages, Phone Dialer, Search, Call Logs closing to homescreen are issues that I've seen this with. I believe this is a real issue, and I need to get it fixed without wasting time on messaging replies to anyone advising "try this," "Try that," etc.
My hope is that between the two of us we can address any of the common responses from developers before taking the issue to them and reporting it. I personally cannot today get my phone to boot without freezing (after boot cycle completes - not bootlooping or freezing during the bootleader seq) and am currently attempting to get into d'l mode without much luck.
When this happened to me on Tuesday night I was able to reboot to recovery, reflash the final-fixed.zip first without wiping data (which failed-/data is corrupted somehow here) and then *with* wipe/data and it booted, ran fine, so I then re-flashed BasicWithaTwist Kernel and was fine until late last night again.
I had been using the phone for some fairly constant web searching and the screen went black, appeared to soft reboot, and then froze. I pulled the battery, waited a few mins, reinstalled battery, once again, Freeze after boot.
No indication that an app crashes, phone just completely freezes, remains screen on, capkeys lit, power button does not respond, nor do softkeys or touchscreen. Makes it though the scan device and scan SD processes *sometimes* and other times freezes before it completes them.
I pulled the both the SD and the SIM and booted up, same issue, though it makes it through the scan device processes everytime since it's not scanning 18gb of data on an SD. This tells me it is not SD or SIM related, and is most likely software related, either ROM or Kernel. I've also ruled out the possibility of an old app/data package by reformatting the SD (long format - wipe all containers to "o,") let Android rebuild menu structure on SD, redownloaded a short list of commonly used apps and installed fresh - *NO* TiBackup apps were restored and the actual backup folder was not replaced to the SD after flashing.
I've tried both the Odin (Fb KJ6 back to stock) and the one click (lumin's tutorial) back to stock. Checked the download of Final-Fixed, MD5 checksum is correct. Cannot find MD5 on the sms-T959V-KJ6-antsvx.v1.1.3.zip file. Doesn't seem to be listed on Anton's github site, perhaps I don't know how to find it there. That is the only puzzle piece I haven't double checked.
All for now, looking forward to yours or anyone's replies or suggestions for anything I may be overlooking. Thanks.
0
---------- Post added at 11:19 AM ---------- Previous post was at 11:12 AM ----------
devlinandersen said:
Hi JaimeZX,
... I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel....
0
Click to expand...
Click to collapse
I should add that I have been on Valhalla Black Edition since it was in beta and have been quite happy with it. I only did a back to stock flash to try to (one more time) see if I could get a cooperative DSP sound manager. No such luck, and now a few headaches, and this issue on Tuesday coupled with yours in the exact same timeframe...I'm just thinking there is a problem somewhere in the chain of attack and hope to find it with the help of others.
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
devlinandersen said:
No indication that an app crashes
[...]
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
Click to expand...
Click to collapse
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
jeffsf said:
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Click to expand...
Click to collapse
I will try in a bit, collecting files for another fresh install, different ROM.
jeffsf said:
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
Click to expand...
Click to collapse
This is false logic and is just what I was trying to avoid. I will attempt to explain to hopefully help build a stronger environment that is conducive to problem solving. It still very well could be a dev issue if say, a certain ROM or Kernel begins to wrestle with an app that has recently updated. Is it the apps or the rom's fault? Maybe it is a seldom used feature of an app that just missed all the users testing until now, it's well within the realm of possibilities and would just like to see helpful comments (such as the first portion directly above) to help solve issues. Truth is, I don't know *what* is wrong and neither do you, so a focus on constructive commentary would just help everyone out.
Logs or it didn't happen.
Update...
After a factory reset/data wipe, wipe cache, wipe dalvik cache I had to let the battery charge for a bit. Came back and decided to just try to boot phone, still freezes after boot sequence. I decide that I will flash a different kernel and a different ROM in order to see if I can make a difference. Before flashing Blastoff v2.5 Kernel I decided to factory wipe/data wipe, wipe cache and dalvik again...I am not sure if this is news, but when doing the Dalvik cache wipe in CWM it returned no result, perhaps because I had previously performed and is empty, but I thought it strange that there was *no* communication that it was already empty/wiped, etc.
Installed Blastoff v2.5 and was able to boot without freezing. Something else was damaged with the Rom as well, would not load home screen, only had pulldown menu. Rebooted to Recovery and flashed Unnamed RC-2.zip and have been charging the battery, talking on the phone and reinstalling apps from market.
Same error happened twice to me and once with Jaime. Both of us on VB and Basic+Twist. After installing new kernel i'd point towards kernel. Also uninstalled DSP and installed voodoo sound on VB, but had that on previous version as well. If I had to start somewhere, I'd start right around there.
Hope this helps, will provide logs from SD backup I made before reflash of new kernel/rom. Gotta run. Adios...
-devil.
I had to get my phone going today, it appears to be working without freezing, though on this new app the phone dialer/phone caller force closes on outgoing calls (I am only mentioning here, I will visit the Q&A for the ROM if I need assistance). Unfortunately I was unable to replicate the problem without flashing back to my previous nandroid. I have it saved and given some time I will do my due diligence and get a logcat **if** Jaime doesn't do it before me...because I kinda have a feeling that something was updated in the market on Tuesday evening that is now fighting with the kernel somehow. But again...I didn't run a logcat so it's not even happening...yet...
...to be continued...
Devlin - sorry for the delayed reply.
I did notice that I'd had more and more apps FCing on me in the week leading up to the Über-crash. Unfortunately I don't have any more "background" to add than that.
I backed up everything I wanted on the SD card and then formatted that, plus /data, /system /everythingelsethatwasanoptioninCWM. Then did my installs.
FORTUNATELY (knock on wood) I have not had any recurrence of the major issue.
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...
Hey all,
I'm a little in a pickle, but first some background I have a nice phone, a Samsung Galaxy Note 2, running Android 12 (not actually relevant, but like mentioning it regardless ). A while ago, I had to replace the motherboard, because the modem wasn't working anymore. I had a spare motherboard that I bought off of Ebay some time ago (to do some experimentation/hacking with) and used that as the modem was actually still working.
Last week, my phone just started to bootloop all of a sudden, sometimes stuck on the logo, but often just the Lineage logo looping forever. Looking at adb shell just showed zygote crashing and restarting, not important, but after some experimentation from within twrp and memtester, it might seem that the RAM was bad, or so I thought.
A factory reset (e.g. wiping USERDATA), made the phone boot somewhat, but it was almost impossible to get through the setup wizard, very slow, lots of crashes.
Anyway, I dd-ed the USERDATA partition into a file (can mount it just fine on my desktop), fsck says its fine), and put it on my old motherboard (which after lots of cleaning of the whole phone, like an engine overhaul the modem works again!), the same linegae failing to boot/zygote crashing came back. Strange, wiping the userimage partition and setting up the phone makes everything work fine.
Right, so now, I want to move over some apps from the old partition to the new. I can't boot the old phone, not in safe mode, just twrp (though it's dissasembled, so is not really easy atm) and access the old partitions. Particularly, I want to move over Signal, as it contains my chat history and media. I can copy some folders around, but I'm sure the user permissions will be off. So my thinking right now is, install signal, note uid/gid, copy over files from old phone with proper permissions and be done. First thing I noticed though; is that Android 12 stores app and (secure?) app data with some ~prefix~, do I need to worry about that? Are the other gotcha's.
In the end I figure, if all the data is exactly there as on the old phone, it should 'just work (tm)' (in theory) but with signal particularly, there's some crypto magic of course (I don't mind factory resetting stuff and copying more stuff, but I have a dark feeling, that the bad ram caused some bits to be rotten in some 'slightly more important' files making my dump less prestine as I would have hoped.).
Thank you,
About a year and a half ago, most of my Google Play apps needed to update, but I've accidentally tapped to uninstall them. The most stupid idea I could got, was to restart the phone in order to revoke that miss - since than, phone can't start normally. It always boot in the safe mode, no matter what I've tried. There's always pop-up after loading that says sth alike "there is something preventing your system to start normally. Please backup your data and do factory reset, yadyyada..." I've managed to transfer most files to PC, but I can't access 2 years worth of notes saved somewhere in Samsung Notes. According to this thread, they should be saved in \data\data\com.samsung.android.app.notes but I can't access them, since Android Studio throws error "package not debuggable". I tried using ADB backup, but that will result in 1 KB file (empty), probably because Samsung Notes has parameter allowBackup="false" in its manifest. There was some effort to rewrite it, but mostly failed, since I can't use Linux commands on Windows. There is a chance, that the data is no longer here. All packages seen in Android Studio show size of 4 KB. But when i do space analysis using the files app after loading the safe mode system, it shows to house 11 GB of system data and 12 GB of apps - which I don't have access to.
Is there any way to either crack that Samsung Notes app, or to repair that corupted system? Maybe get some log to see, whats crashing the system? Last resort solution may be rooting it?
Thanks in advance for your help. Mark