"Attempt to write a readonly database" - Nexus S Q&A, Help & Troubleshooting

Hi everyone,
it' my first messagg over here but i read you all the times, it's the most powerful forum i've ever heard, But now, I need you because I have a problem with my phone.
Well, some weeks ago I installed on my device Nexus S Europe (model version, I9023 i think) a custom rom called Nexus Beam, faboulus let's say, ICS, battery drain , never had problem...but a day all the processes started to crash, system.android.process, system.android.markert, etc ...let's say: all the processes, so i thought: "reboot" , it has always been so useful. Not this time...i rebooted the phone and again after 2-3 housrs of usage, the same crashes.
So i decided to put on it the latest MIUI rom (2.3.30)...everything was wonderful, everything was so speedy that "wowww" but again...2-3 hours of usage the same error messages...rebooted again, and..."Google" text for ever!!
SO agaia, deleted EVERYTHING from my sd card, i've done all the kind of formatting thing proposed by cwm (data, system, boot, cache), then tryed to flash an older version on MIUI with Gingerbread. Same stuff! after one hourse the same errors and now i really don't know what to do.
I've tried everytinhg but i'm always on the Google texct while the system is trying to reboot. Tried also with fastboot but it doesn't recognize the device.
Please, can you give me some suggestions?"! I'm really, resperate!!
Just for knowledge, attached here you can find the error i got for all the applications installed on my device. It's always the same, and change only the name of the app:
app_vercode:15
device_model:crespo
build_version:2.3.30
condition:1
processName:com.android.calendar
pid:3280
uid:10006
tag:null
shortMsg:android.database.sqlite.SQLiteException
longMsg:android.database.sqlite.SQLiteException: attempt to write a readonly database
stackTrace:java.lang.RuntimeException: An error occured while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:278)
at java.util.concurrent.FutureTask$Sync.innerSetExcep tion(FutureTask.java:273)
at java.util.concurrent.FutureTask.setException(Futur eTask.java:124)
at java.util.concurrent.FutureTask$Sync.innerRun(Futu reTask.java:307)
at java.util.concurrent.FutureTask.run(FutureTask.jav a:137)
at java.util.concurrent.ThreadPoolExecutor.runWorker( ThreadPoolExecutor.java:1076)
at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:569)
at java.lang.Thread.run(Thread.java:856)
Caused by: android.database.sqlite.SQLiteException: attempt to write a readonly database
at android.database.DatabaseUtils.readExceptionFromPa rcel(DatabaseUtils.java:179)
at android.database.DatabaseUtils.readExceptionFromPa rcel(DatabaseUtils.java:135)
at android.content.ContentProviderProxy.query(Content ProviderNative.java:358)
at android.content.ContentResolver.query(ContentResol ver.java:311)
at android.content.CursorLoader.loadInBackground(Curs orLoader.java:56)
at android.content.CursorLoader.loadInBackground(Curs orLoader.java:42)
at android.content.AsyncTaskLoader.onLoadInBackground (AsyncTaskLoader.java:255)
at android.content.AsyncTaskLoader$LoadTask.doInBackg round(AsyncTaskLoader.java:66)
at android.content.AsyncTaskLoader$LoadTask.doInBackg round(AsyncTaskLoader.java:55)
at android.os.AsyncTask$2.call(AsyncTask.java:264)
at java.util.concurrent.FutureTask$Sync.innerRun(Futu reTask.java:305)
It would be really great if you could help me!
Thank you so much and happy easter to everyone!

Related

kadspd error in latest initrd

First of all i would like to thank all the devs who spent alot of time and effort in developing android for us.
Down to business i finally got time to spend trying out android, im using haret method and i know its not as fast and complete way of using android, but im just gonna do this to provide feedback.
Alright heres my setup,
Using Atool
Polaris, 320x240 panel 1 (pola 100), no vibrate on boot, sd system, sd data. made the default.txt.
2.6.32_zImage-11-29-10-liquid-latest
androidinstall.tgz from Super Froyo release 16
androidupdate.tgz from androidhtc
Initrd from androidhtc
Installscript from atools, erase data and system, advance mode, install system, install update, fix permission, clear davik cache.
The install begins and never finishes, it keeps repeating infinitely around
INFO: task kadspd:17 blocked for more than 120 seconds.
and alot of other memory address related stuff
i did check this thread, but after a few pages i didnt see a solution there
Kaspsd:17
after some testing i think it was the initrd because i changed it dzo's last initrd from dzo and it worked. could this have to do with my sd card being class 2.
I hope this can help you guys. I'll post further results when i get more testing done.
Update:
Ok it seem, the loop is not within the install script, but the boot up process although i saw it say "Install module for this kernel", why is it installing again when the last script is still disabled?
Btw, this occurred when i tried replacing the initrd back again after the install was successful using dzo's initrd.
Dzo's initrd was causing a weird issue on wake up, the lock screen, was inverted like in a mirror. wth?
Regards,
Lord Meshadieme
waiting for more detailed results...
Um, can you be more specific im not very linux oriented.
Lets see, here's the steps, starting trying to do a fresh install which basically succeeded (this is using your kernel and initrd), but concurrently its stuck booting. BTW why does the booting process have a line saying "Install modules for this kernel" so here's the dmesg from the successful install. no bootlog since it never completes booting in the loop..
It does boot using dzo's initrd, although quite buggy, (the bootlog below is from that successful boot using dzo's initrd) i'm gonna try it again and see what works and what doesn't. anything specific you want me to check?
Update:
So far testing shows BT turning on, haven't testing file transfer or headset.
Turning on Wifi freezes the phone, already applied the androidupdate..
Calling works GSM.
Battery is showing incorrect value, there's a fix for it somewhere right? i'll search for it.
Waking up from sleep does that weird inverted screen for like a second then it goes to normal. (it is literally like a mirror, text is even flipped)
USB Mass Storage, is connecting but the drive does not show up in windows.
can't test market without internet, not sure how to use internet through usb yet.
no gprs/edge/3g to test right now.
Camera, is weird i was able to take a picture but it was a dark shade of green... but now i cant the app hangs.
cant test gps since the default map tool asks for internet too.
I think you did a really mess!!
what you call "kadspd error" is when kernel kill a script due to long time execution (you probably wait too long). The action is the message "install modules!!!!".
Please next time pay more attention!
Follow all the steps in atools guide. You forget to mix the rom with the module update!!!!
BTW install MY kernel, and apply update before the first boot.

[Q] To root or not to root for update

Hi
I have a Samsung Galaxy GT-I5801 with me for past couple of years.
Its current OS spec are:
Firmware version- 2.2
Baseband version- I5801DDJP2
Kernel version- 2.6.32.9 [email protected] #2
Build Number- FROYO.DDJP6
My phone has become kind of slow, like for even basic tasks like opening call log or messaging app, it takes good 10-15 seconds. Sometimes it even goes unresponsive when trying to end a call thus causing call to continue thus carrier balance reduction. There are no 3rd party apps installed on it. Even updating the pre-installed apps gives the message of memory being low.
Now my query is:
Will flashing it to a custom ROM will improve its working at least in the basic areas of call and texting?
If so, then which is the most suitable custom ROM?
Is it necessary to root the phone before flashing it ?
Which tool is best/easiest for said purposes?
Please go easy on me, I've been out of the IT and tech game since past 1 year and bit rusty on these things
RudraP said:
Will flashing it to a custom ROM will improve its working at least in the basic areas of call and texting?
If so, then which is the most suitable custom ROM?
Is it necessary to root the phone before flashing it ?
Which tool is best/easiest for said purposes?
Click to expand...
Click to collapse
I would say yes. I don't know what is causing the freezes, but (beside that this could also be a hardware problem) a custom ROM should fix that.
Any GB-based ROM should do a fine job. There are also Froyo-based ROMs for our device. The CM7.2 build by marcellusbe does a very good job.
Nope. If you flash via Odin (Flash-Software for Windows) you just need a usb-connection. If you flash it via recovery, you may need to flash a custom recovery first.
Derp - another proud Galaxy3 user :highfive:
DerpyDerp said:
I would say yes. I don't know what is causing the freezes, but (beside that this could also be a hardware problem) a custom ROM should fix that.
Any GB-based ROM should do a fine job. There are also Froyo-based ROMs for our device. The CM7.2 build by marcellusbe does a very good job.
Nope. If you flash via Odin (Flash-Software for Windows) you just need a usb-connection. If you flash it via recovery, you may need to flash a custom recovery first.
Derp - another proud Galaxy3 user :highfive:
Click to expand...
Click to collapse
I tried SuperOneClick but it failed to even detect my phone, let alone root. Tried rooting directly through phone by installing z4root on it. It too failed to root my device, just a blue screen saying "Running Exploit" with z4mod logo kept on displaying for 10-15 minutes, after which phone switched off itself. Had to power it back on myself. Tried it couple of times more but no success.
So now if I use Odin to directly flash the firmware to a modded one, would it work, considering the fact that the phone hasn't been rooted. More importantly, would it be wise to do so? Don't want to hard brick the device as its my backup device after my Xperia SP took a plunge in the water and now fails to even boot, just vibrates thrice and that's it.
Update:
Took a leap of faith with Odin and Cyanogen & now the device is rockin' like a grandma with a new hip replacement Lags no more, operation is smooth, but a 2nd minor problem has cropped up.
It now refuses to install any app from Play Store citing Insufficient Space. I changed the default installation space to external but still the problem persists.
Update 2:
For my above mentioned problem, looks like something to do with Gapps but I don't know what it is and what to do about it. Moreover as today I tried to make calls or send messages, I found out I'm unable to do so. The dialler dials after good 2-3 minutes of pressing/selecting the dial option for a number while message inbox is empty but it refuses the receive any sms citing Inbox is full. I thought just flashing the firmware should do the trick but looks like it just was the tip of the iceberg.
You can find the gapps (Google Apps - like Play Store, Gmail, ...) here:
http://goo.im/gapps/
Assuming you're on Gingerbread (CM 7.x) it's this package: http://goo.im/gapps/gapps-gb-20110828-signed.zip
Put this zip-file on your SD card, power off your phone and/or reboot to recovery. Navigate to "Select zip from sd card" -> select your gapps.zip and flash. Then "wipe cache" and "wipe dalvik cache" anywhere in the submenus Just to make sure the gapps get recognized correctly.
Another trick for expanding the internal storage is Link2SD. You need a 2-partition sd-card for this. 1. partition with FAT and 2. one with ext2/3/4
Link2SD will mount this second partition to the internal storage to expand your storage for apps and other system stuff.
You know... Getting the most of a half-dead low-end device needs a bit of geekiness
bad zip
Well I selected erase all data option in the phone which booted it into recovery mode. Here I cleared the cache and the user data. When I tried to install zip file from sd card it gave the following error message, "Can't open /sdcard/gapps-gb-20110828-signed.zip (bad) Installation Aborted"
What seems to be the problem now?
Update:
Tried again and this time it worked. Now everything is running fine. Thanks a ton for the help mate, can't express my gratitude through words.
I do want to ask one thing here.
If I install this, http://forum.xda-developers.com/showthread.php?t=1803180, will the JB experience be coupled with performance drop ?
Honestly Cyanogen has turned me into a junkie, now I want to try on the new but stable mods. Moreover as my Xperia SP is now out of warranty, I'm planning to get it fixed and then root and flash it too!

[Q] Kernel Partition Corrupt?

So I flashed C-Rom (a ROM similar to Carbon) and it worked mostly fine -- a few SystemUI crashes, and Play Music acted weirdly. However, I stuck with it until it randomly did a soft reboot. When the OS was back up, I noticed that the GPS ceased to function. Then it soft rebooted again. Up for 30 seconds. Soft reboot. It went on and on; my phone was unusable.
Until I flashed Carbon ROM -- as the last time I did it was featureless, but it had been updated -- to my device. I am currently loving it! Just as great as C-Rom but much more stable. However, something weird occurred. I tried to flash RenderBroken's Render Kernel later. I got the unlocked bootloader warning screen, but it just stayed there...I thought the ROM wouldn't boot, until I got the notification sounds all of the sudden. So the ROM booted, just the screen only showed the bootloader screen and wouldn't respond except to the power button. So I flashed CM11, flashed the kernel, same problem.
I got curious about this problem, and noticed that an issue that appeared with it is that when uploading Instagram photos -- they would appear as a black box, on both Carbon and CM11. So I plugged my phone into my PC, ran LogCat while trying to upload an Instagram photo:
E/ConnectivityService( 1058): Can't set delayed ACK size:java.io.FileNotFoundException: /sys/kernel/ipv4/tcp_use_userconfig: open failed: ENOENT (No such file or directory)
E/ConnectivityService( 1058): Can't set delayed ACK size:java.io.FileNotFoundException: /sys/kernel/ipv4/tcp_delack_seg: open failed: ENOENT (No such file or directory)
The issue with GPM is that when playing downloaded music, the Play/Pause button has about a 10 second delay till the music stops or starts. I tried to run LogCat there, but my screen froze, the terminal wasn't showing anything and then my phone crashed and the terminal filled with errors -- a lot of them kernel related. (I also tried instagram on a Moto G running C-Rom, works fine).
So I believe that the problem is kernel related, even though I've flashed quite a few kernels recently so the partition "should" have been cleaned. Is there any way to debug the kernel and know for sure? Or how else can I go about looking for a solution? I'm a debugging noob, but I know my way around the Android OS for the most part. Any help would be greatly appreciated.
You don't mention doing a 'Dalvik cache' wipe in Recovery. I believe it's generally good practice to do this when changing kernels. I suggest you do a wipe and reflash current or alternative kernel. If you still have issues, post in the thread for that kernel.
Ultimately, you might have to return to stock firmware; since all custom ROMs [currently] are very much a work-in-progress and come with an assortment of bugs and quirks.
Just tried that, didn't work unfortunately ? The problem is it has worked for me before, so I need to figure out how to debug and fix it. So I'm curious is, how should I go about searching for it?
Sent from my Moto G using XDA Free mobile app
It sounds like you are running logcat on the phone itself, try doing it on PC via adb.
adb logcat -v long > logcat.txt​
lost101 said:
It sounds like you are running logcat on the phone itself, try doing it on PC via adb.
adb logcat -v long > logcat.txt​
Click to expand...
Click to collapse
Just did that; now what am I looking for? Because since I'm having trouble with both Instagram and getting the kernel to work, I believe they are related. So the question is how do I find the problem with Instagram? I had it only output lines with the E tag but a lot of them look like:
E/mm-camera-CORE( 506): new_ew[157]=0.813300, 0.860912, 0.809075, 0.688594, 0.837469, 0.830200, 0.790950
The file will show up in my gallery if I take it through the Instagram app, which would mean that Instagram is having trouble retrieving the file...which is what the kernel assists with, correct? I also have tried sharing to Instagram through the gallery with the same issue. So what do you think? Sounds like a kernel issue?

OmniRom Twlight Zone - WTH is going on?

This is my first attempt into breathing life back into my tf300t I've had for almost 3 years. Hardly used it do to the continuing blog down that always occurred and the lack of updates by Asus eventually led me to unlocking/custom rom/rooting and then soon thereafter to here. Knowing nothing about the process and procedures, although somewhat computer literate (I started on a TRS-80 in the early 80s), I did the cursory research for the uneducated I decided to try the lollipop variant of Kisskat 5.1.1. I used TWRP to make a recovery back up and then wiped/flashed/booted. Fooled around with it some but discovered a few quirks. For one, the zone closest to the Asus logo was rather warm to almost hot even if you throttle back the performance. But more importantly after installing my apps via the play store I began to notice some media issues. For one, the video was a bit choppy (I use VLC player) and my mp3s seem to be inoperable on almost any app. (I typically use Fusion and EZ Folder Player but nothing seemed to work). I kept getting issues that seemed to be related to the recognition of folders of file types. Often telling me an mp3 file was not a recognized folder or that the file type was not recognized or in some cases (EZ Folder Player) I simply could not change directories to access files. Any help in these areas may put me back in the KissKat Camp... at least until the thing catches on fire... then we can roast marshmallows and have a camp sing along.
Before jumping on the forum I thought I'd try a more simple fix - try another rom. Tried OmniRom and while not as zippy (or hot) it seemed stable enough to go with for a while. Did the Gapps recommended for the latest pop rom and the superSU file. Loaded my apps from the play store. Then decided that perhaps I should back up all my apps after having went though applying all the correct passwords and what not. Read the Titanium Backup was a the best option. Made an initial internal mem backup of all apps then read that I could create a zip of the apps to use as a recovery method off of an SD Card which sounded the better option for me (seems far more secure). Then I felt that I was at a juncture where I should test my backups before moving on the custom folders and docs and so forth only to find out a problem was in the works when the time came at an inopportune moment down the road. Well I discovered a problem. I booted into TWRP and wiped then used my recovery to bring it back to the last known state before my first flash of a custom rom (not sure if this is even a necessary step but it seemed like it certainly couldn't hurt). Then boot/re-boot to TWRP, and having read a full/complete wipe was necessary I wiped everything (Full data format - then wiped all options in the advanced wipe section other than my SD Card where I was holding my files for flashing). Then flashed (1)OminiRom 5.1.1 (2)Recommended Gapps package (3) SuperSU, and - this is where I may have had a bad moment - the Zip file generated by Titanium Backup Pro - Is this even where I can flash install this file???Was kinda lost there. Well... I think I then tapped the TWRP button for wiping/clearing the Cache / Dalvik Cache having read (although also having read to the contrary) that this was necessary to avoid a bootloop. Then I rebooted and arrived shortly thereafter at the OmniRom Boot animation of the droid bot blinking eyes and wiggling his antennae which is as far as this Rom, which once loaded and operated fine, will now go.
I have since tried several times to reload the rom only to the same end. I have even tried the latest nightly on the rom. Same result. Tried the latest version of TWRP (2 updates since the 2.8.5.0 I initially installed with) and both updated TWRPS were riddled with problems for me - Most importantly they would not reboot - had to force close via the power button only to have TWRP reboot to itself and the process start again. As well, TWRP would not do anything as no partitions were mounted nor could I mount them - just red error messages on the console screen when I attempted to do even a simple wipe. Obviously I was getting deeper into the omniRom twlight zone.
KEEP IN MIND - this is the weird part - I COULD and still can (1) Boot to TWRP and recovery to my initial recovery file I made of JB 4.2.1 stock from Asus (if it didn't suck with lag I would have stayed there to begin with) and (2) I COULD ALSO FLASH THE KISSKAT CUSTOM ROM but as I said I had issues with it which led me to try OmniRom which I thought was a good choice until the problems.
At this point, as I sit here - I have used fastboot to reinstall the TWRP 2.8.5.0 (since it was what worked initially) and I have TWRPed to the recovery JB 4.2.1 and then wiped everything using TWRP - Data Format and all advanced wipe options less my own SD Card. Another issue - I tried the latest release of KissKat #26 and this time, in addition to the problems noted earlier, I cannot seem to mount the SD Card as it is now unrecognized by the TF300t (although it worked fine in the #25 build).
I am at an impasse and any help with any of these problems would be greatly appreciated. I just want to get a decent functioning custom rom on this tablet to get some more life out of it.
Thanks in advance,
Dog.... from somewhere near the outer limits of the realm of... the twlightRom

Always about 100% CPU usage... :/

Hey, I got a little problem with my Tab2 10.1 - with different ROMs and even with stock firmware, I always get nearly 100% CPU usage by "other processes".
Im getting that information by the app "System Panel 2". And the tab runs like sh*t... What can I do now? Im not that new to rooting and flashing, but something like this never happend to me... :crying:
Its a Tab 2 10.1 WiFi (P5110)...
I tried:
- (clean) flash of different ROMs
- (dirty) flash of old backups
- wipe of everything (incl. Internal Storage etc...)
- flashing stock FW with Odin
- tried phh's superuser instead of SuperSU
- tried in terminal "setenforce 0" (or something like that)
Some flashes run the first minutes like always and some of them are from the beginning sh*tty to use, cant even open settings app...
Hope anyone got an idea for that problem :/
Chriss97ST said:
Hey, I got a little problem with my Tab2 10.1 - with different ROMs and even with stock firmware, I always get nearly 100% CPU usage by "other processes".
Im getting that information by the app "System Panel 2". And the tab runs like sh*t... What can I do now? Im not that new to rooting and flashing, but something like this never happend to me... :crying:
Its a Tab 2 10.1 WiFi (P5110)...
I tried:
- (clean) flash of different ROMs
- (dirty) flash of old backups
- wipe of everything (incl. Internal Storage etc...)
- flashing stock FW with Odin
- tried phh's superuser instead of SuperSU
- tried in terminal "setenforce 0" (or something like that)
Some flashes run the first minutes like always and some of them are from the beginning sh*tty to use, cant even open settings app...
Hope anyone got an idea for that problem :/
Click to expand...
Click to collapse
Finally I got it!!! I dont know why, but it was my SD Card... I unplugged it and boom, no problems anymore...
I wiped the SD Card and now I can use it like before without this weired problem. Huh...
SD card formatting stopped high CPU on custom ROM. Thanks!
Thank you!
This solved my problem with a custom rom (NAOSPROM 7.1.2 december with OpenGapps pico) on my Samsung Galaxy Tab 2.
After installing gave me alternating high CPU after a reboot. One time reboot gave a low CPU and than next time high.
'Simple OS Monitor' (great tool) just showed system_server around 16-17% hardly ever lower. Stopping almost all non essential system apps and all user apps. Didn't make any difference. Even removing SD card.
A network reset seemed to do something, but hardly.
But then after formatting SD card, putting back the files I had stored there, except the Android .secure android folder, I rebooted and all was well. CPU usage of system_server went from 17 to 1 % and total CPU to normal
So Samsung Galaxy Tab 2 works well with NAOSPROM 7.1.2 custom rom ... but don't forget to format your SD (when you experience high CPU usage).
Just in case somebody finds this information. Like I did yours.

Categories

Resources