Hi Guys,
Since a couple of days I had a lot of apps crashing on my OneX (rooted, Android Revolution) and thought there was something wrong with the rom so I reflashed it but even with a clean rom crashes kept coming back, even without installing anything a couple of processes like com.htc.bgp and android.acore kept crashing/stopping.
I started looking at the logcat output and noticed that the crashes were the result of the data partition being read only and causing Sqlite to throw all kinds of exceptions when trying to write (logically)
When booting everything seems fine, the data partition is mounted RW but somewhere during operation the system remounts /data as readonly.
Usually this is because Linux detects a disk- or journaling error, so I tried running e2fsck on the partition from Clockwork Recovery and this indicated some errors so I fixed these but the problem still persists, random ro remounts with no apparent cause.
So a few questions I have :
- Does anyone have any idea why the system keeps remounting the partition ?
- How to circumvent it from remounting it as read-only ?
- Could this be a hardware failure of the internal memory ?
- Could an application error / exception cause this ?
Thanks in advance !!!
Cheers
Rob
Think your in the wrong forum this is the HTC one xl and it appears you have the international one x tegra 3
Sent from my HTC One XL using Forum Runner
Please refrain from double posting. Also, please search before creating threads. Chances are, your question has already been asked.
Thread Closed.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my HTC One X, using XDA Premium.
Related
I have spent a couple of days in hell and would now like to share my experience as a big thank you to the XDA community. However, I am fairly noobish when it comes to Android so if you feel that this does not help, please feel free to delete this entry.
It all began when I restarted my G Tablet and got lots of popus about various applications, including acore, failing. I thought that this was due to me screwing up the system in some way after more or less having followed r34p3rex's superb guide here: http://forum.xda-developers.com/showthread.php?t=827209.
Ignoring this for a moment I tried to install one of the NDK sample apps on the device. This failed with the message: "read only file system". Looking in logcat it was pretty apparent that this was also causing all other applications to fail, since they were logging errors with not being able to write under /data/.
Looking at dmesg output finally confirmed this, where it reported that the /data partition had journal errors and could only be mounted as read only (this was also confirmed by issuing the mount command from within an adb shell).
This led me on a journey from just trying to remount the partition as read only (which failed with no further message), through installing clockworkmod, different versions of tnt lite, formatting and repartitioning (or so I thought), to flashing the device through its APX interface (using nvflash). None of them worked.
Not until I read a post by raydog153 - in this archived thread: http://forum.xda-developers.com/archive/index.php/t-857875.html - did I succeed by re-partitioning the sdcard (under the advanced section).
You could argue that it was stupid to not realize that a re-partitioning was required in the first place - since the ext3 partition obviously had errors and Android does not provide a fsck command (or does it?) - but I guess I thought that this was what was actually being done in other clockwork commands or at least when doing the nvflash, but obviously that was not the case.
Anyway, sorry for the lengthy entry. I just wanted to give back to the community and help others who might get the same problems I had. Also, on the positive side I have learned a lot and, like someone else wrote, I have completely lost my noob fear of bricking my G Tablet.
Keep up the good work, guys! You Rock!
almost a week without problems with FCs, thanks for this usefull info.
Hi all,
Sorry if this has been posted before, I have had a look but cant find the solution!
I have a HTC Desire HD that I have rooted using the AAHK, this has worked fine.
Next, I have searched around for a rom to use and found the Cibernodo Mod2Bravo V7.1 (English version) . . . I have put the zip file on to my SD card . . . restarted in recovery mode, wipe data/factory reset, wipe cache partition, wipe Dalvik cache, wipe battery stats, install zip from SD card, chosen the Cibernodo file and gone through the installation process . . . .
I have done all of this several times, and downloaded the zip again but I constantly get the same results:
Mounting and formatted partitions
Mounting /data
Mounting /sd-ext
Formatting /system
Mounting /system
Intalling System & Data partitions
Installing Gingerbread Keyboard
Installing Zeam Launcher
Installing ES File Manager
Installing CM/GB player
Installing 3DGallery
Removing Apps NOT selected
Installing Cibernodo Bootanimation
Configuring installed files
Setting permissions of /data
Configuring System Files
assert failed: write_raw_image("/tmp/boot.img","boot")
Yes, I am a noob, and no, I dont know much about this but I have followed everything to the letter as far as I can see ... is there something glaringly obvious that I am doing wrong?
To top it off, each time I complete this process a message pops up telling me:
Congratulations...
Cibernodo Mod2Bravo has been installed correctly on your phone
Click Finish, and restart your phone.
Thanks
Installation State: 1792
So is the 'assert failed' the issue here, and if so, how do I fix it?
Sorry to go into so much detail but I just want to see where I have gone wrong ... many thanks in advance!
[EDIT]
when my phone reboots it goes back to where I started from, i.e. the downgraded version of android from after rooting . . .
I will also try downloading and installing a previous version, V6.1z ...
Same issue with that version, so Im pulling hair out lol!
This has now gone from bad to worse ... I ran the aahk again as super user and busy box disappeared, thinking I would start from fresh again . . . there was a pause in the process and now my phone is stuck on the white HTC screen . . . anyone able to shed any light on this at all?
I've managed to speak to someone and apparenly I am not bricked and can run a ruu ... when I re-run the aahk it wont start as the error message comes up ... the phone is plugged in, the drivers are installed but I am guessing the USB debugging has been disabled . . . so does anyone know how to enable this from the aahk main screen with regards to the fact I can't boot into android?
Looks like there are lots of reasons for this... and it's a can of worms. Also, the Desire HD is one handset that my network has never sold direct, so I have seen one in eighteen months. I'm less familiar with it than I'd like... Just checking the thread and you're using the Desire HD, yes?
This thread degenerated a little and I think you've tried the chatroom too, but there are some useful pointers here: http://forum.xda-developers.com/showthread.php?t=1646178
And also here:
http://forum.xda-developers.com/showthread.php?t=1645285
Good luck. Keep us posted.
Thank you for that, I have got to the point where I don't know what to look for anymore lol! I will have a read through those ...
Hi Guys,
Since a couple of days I had a lot of apps crashing on my OneX (rooted, Android Revolution) and thought there was something wrong with the rom so I reflashed it but even with a clean rom crashes kept coming back, even without installing anything a couple of processes like com.htc.bgp and android.acore kept crashing/stopping.
I started looking at the logcat output and noticed that the crashes were the result of the data partition being read only and causing Sqlite to throw all kinds of exceptions when trying to write (logically)
When booting everything seems fine, the data partition is mounted RW but somewhere during operation the system remounts /data as readonly.
Usually this is because Linux detects a disk- or journaling error, so I tried running e2fsck on the partition from Clockwork Recovery and this indicated some errors so I fixed these but the problem still persists, random ro remounts with no apparent cause.
So a few questions I have :
- Does anyone have any idea why the system keeps remounting the partition ?
- How to circumvent it from remounting it as read-only ?
- Could this be a hardware failure of the internal memory ?
- Could an application error / exception cause this ?
Thanks in advance !!!
Cheers
Rob
If you installed android revolution and it worked, you have a tegra 3 HOX. How did you get clean rom working? It's for the snapdragon hox.
gunnyman said:
If you installed android revolution and it worked, you have a tegra 3 HOX. How did you get clean rom working? It's for the snapdragon hox.
Click to expand...
Click to collapse
Re read it
He says "A clean ROM" not just clean ROM
Wrong section OP
Sent from my One X using Tapatalk 2
gunnyman said:
If you installed android revolution and it worked, you have a tegra 3 HOX. How did you get clean rom working? It's for the snapdragon hox.
Click to expand...
Click to collapse
I think he meant a clean copy of the rom he was using (funny word play). But yes, wrong forum.
Doh. But yeah. Still wrong forum
thioz said:
So a few questions I have :
- Does anyone have any idea why the system keeps remounting the partition ?
- How to circumvent it from remounting it as read-only ?
- Could this be a hardware failure of the internal memory ?
- Could an application error / exception cause this ?
Thanks in advance !!!
Cheers
Rob
Click to expand...
Click to collapse
Try reposting the same questions over at the international One X forums. Although our phones look the same, they differ internally and software isn't compatible across both.
The forums you're looking for:
http://forum.xda-developers.com/forumdisplay.php?f=1533
Hey guys...
I would have loved to post this to the author of this CM10.1 rom i'm running but the forum won't allow me to do that yet. It's the HTC Aria/Gratia/Liberty running user WinSuk's CM10.1 homebrew mod. S-OFF and working beautifully with a bunch of other apps for many weeks now.
I've read a couple of dozen threads with the same issue and after trying maybe 10 different suggestions that solved other peoples problems, I am forced to post another topic with this boring subject. Any suggestions would be very helpful and grateful.
The questions is about Link2SD in conjunction with this ROM. Are there any limitations on using Link2SD with this rom?
I must have read 20 forum threads and I see that there are literally thousands out there about the "Mount script cannot be created"-error.
I've tried all file systems for the second partition (FAT16/FAT32/EXT2/EXT3/EXT4) and all give this error. The only difference is that when the file system is EXT3 I get a different error. Instead of being just plain "Mount script cannot be created" I get instead "Mount script cannot be created. Mount: Invalid argument".
Either Ext3 is showing some progress or it's the only file system not supported.
The phone is obviously S-OFF so nand is unlocked. I'm very close to trying the CronMod script instead but I really would like to try Link2SD before falling back on something potentially less popular.
Thanks for reading and helping out... /s
Hello XDA, I hope you can help me with this issue that is driving me crazy. Before you redirect to the search bar I must tell you I searched in all the threads with similar topics for a fix to no avail, all of them had as common denominator not being able to mount the second partition on reboot, which is not my case.
Followed instructions on: http://forum.xda-developers.com/showthread.php?t=1614700
Samsung Galaxy S4 Mini GT-I9091, Android 4.2.2 Stock ROM Rooted.
Second partion: Ext2 2GB
Link2SD paid version
After I create a link for an app (checking all 4 options), once I reboot the device, the apps simply "dissapear": no icon inside app cage, Link2SD doesn't displays them within external, linked or internal apps, and If I choose the option: Clear second partition, Link2SD will identify all the app's files that I tried to link and tell me they are not relevant!! For some reason, two apps DID link successfully and remained like that after rebooting, but I did nothing different to this two apps compared to the others: QuickOffice and BCC news. On boot, the displays shows no notification or warning about not being able to mount the second partition and the mount script creation showed no issues. What on earth could be causing this? Any support is really appreciated!
Hi!
All the detail you've provided is awesome!!
But you will need to ask in their Xda thread. Found here...
http://forum.xda-developers.com/showthread.php?t=919326&page=448
XDA Assist is here to provide guidance to threads and sections....we don't troubleshoot.
I'm sure they can help you in the thread I linked. ?
Good luck!