Related
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.
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
Hi everyone,
Long story short, my device wont boot. Ive got TWRP. I have the backup on my computer, but when i plug my phone in, i cant move the backup to my TWRP Backup directory because there is no way of getting to the internal storage. Im a noob with adb and i have no clue how to use it so can someone help with that. Thanks! :crying:
adb shell
mount /data
exit
adb push c:\users\provickers\desktop\backupfile /data/media/0/whereverTWRPbackupsGO
Sent from my Nexus 5 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
sent from my HAMMERHEAD
CRIME INC. said:
http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
sent from my HAMMERHEAD
Click to expand...
Click to collapse
Not really an option...
rootSU said:
adb shell
mount /data
exit
adb push c:\users\provickers\desktop\backupfile /data/media/0/whereverTWRPbackupsGO
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
that means nothing to me. can you write that in super duper nooby language please
Just read the adb stickie in q&a then
Sent from my Nexus 5 using Tapatalk
rootSU said:
Just read the adb stickie in q&a then
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I do adb shell
then mount /data
and it says: mounting /dev/block/mmcblk0p28 on /data failed: device or resource busy
Im currently in the home screen of TWRP
Maybe its already mounted by twrp in the mounts menu. If it is, skip that step. If not, mount in that menu
Sent from my Nexus 5 using Tapatalk
rootSU said:
Maybe its already mounted by twrp in the mounts menu. If it is, skip that step. If not, mount in that menu
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
alright thanks alot, hopefully it works!
rootSU said:
Maybe its already mounted by twrp in the mounts menu. If it is, skip that step. If not, mount in that menu
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Can u tell me where the twrp backups directory is? Coz obviously i cant get into my phone
I don't use twrp myself so im not sure where it is. If you use the ls command..... (thats LS in lowercase)
Eg....
ls /data/media/0
That will list all the directories on sdcard. I assume there will be a folder called twrp there. Within there not sure. But you can use ls to keep drilling down.
ls /data/media/0/twrp
I think there's a backup folder with dated folsers within it.
Take a twrp backup now and see....
Sent from my Nexus 5 using Tapatalk
Yes, the path's correct... TWRP makes a backup in /data/media/0/TWRP/3282387328 (random string)...
So, you will need to push the backup folder to /data/media/0/TWRP/... Now it will show up in the restore option.
vin4yak said:
Yes, the path's correct... TWRP makes a backup in /data/media/0/TWRP/3282387328 (random string)...
So, you will need to push the backup folder to /data/media/0/TWRP/... Now it will show up in the restore option.
Click to expand...
Click to collapse
Presuming he has the content of the random string folder, but not the folder itself, can he create a random string folder manually? Or must he take a backup and use that folder?
Sent from my Nexus 5 using Tapatalk
rootSU said:
Presuming he has the content of the random string folder, but not the folder itself, can he create a random string folder manually? Or must he take a backup and use that folder?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Like you, I've stuck with Philz for a long long time now.. Can't say for sure about twrp. I guess there's no harm in trying to make a folder and check.
However, sometimes while doing that, I faced a md5 mismatch error in twrp. But that's on a HTC One X.. No idea whether twrp has changed this since then.
rootSU said:
I don't use twrp myself so im not sure where it is. If you use the ls command..... (thats LS in lowercase)
Eg....
ls /data/media/0
That will list all the directories on sdcard. I assume there will be a folder called twrp there. Within there not sure. But you can use ls to keep drilling down.
ls /data/media/0/twrp
I think there's a backup folder with dated folsers within it.
Take a twrp backup now and see....
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I get "Permissions Denied". This is probably why nothing is working! What can i do?
ProVickers said:
Can u tell me where the twrp backups directory is? Coz obviously i cant get into my phone
Click to expand...
Click to collapse
/sdcard/TWRP/BACKUPS/your device serial number
Find the serial number in settings, about phone, status
Sent from my Nexus 5
Can't get to settings without booting phone.
OP can we keep this to one thread please? Its going to get confusing
Sent from my Nexus 5 using Tapatalk
i dont know why people dont do this, maybe they are worried of the little bit of space it takes in their storage, but i ALWAYS, since feb of 2009, keep a copy of my current rom and kernel in my storage. if i ever mess up doing anything, i always have my rom/kernel to flash again. no relying on computers(as im rarely around them). also, i always have one nandroid backup in my storage, just in case. it might not always be the most recent, but its there just in case.
@ProVickers
I'm not 100% sure of this but adb in TWRP doesn't work everywhere... You need to go to Advanced-Sideload.. then swipe right and then fire the adb push command..
rootSU said:
Can't get to settings without booting phone.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
He can get the serial number from the bootloader, right?
simms22 said:
i dont know why people dont do this, maybe they are worried of the little bit of space it takes in their storage, but i ALWAYS, since feb of 2009, keep a copy of my current rom and kernel in my storage. if i ever mess up doing anything, i always have my rom/kernel to flash again. no relying on computers(as im rarely around them). also, i always have one nandroid backup in my storage, just in case. it might not always be the most recent, but its there just in case.
Click to expand...
Click to collapse
Agreed.
Although i always have my rom, kernel and titanium backup. My nandoids move to my NAS as i don't have the space. However, I never modify anything that may require a restore when I'm away from home
Sent from my Nexus 5 using Tapatalk
Hi,
I have already posted some time ago about the problem with my phone ( http://forum.xda-developers.com/google-nexus-5/help/hardware-failure-t2822131 ) and now I come with a completion and a specific question to my problem.
The problem still persists ( https://www.dropbox.com/sh/5ym5v7z38fm6jfm/AAB7qHgWqcq5QxnkZOkAZrDna ) the apps randomly crashing at times. This problem was encountered even on the stock Android before installing any additional app next to those already on it.
I assumed that I might have some broken RAM sectors and that the only possibility to remedy this problem is to deny the OS to use these sectores. As I don't know which sectors are the faulty ones, I will reserve at first 1GB RAM, continuing to do binary search until I manage to izolate them.
I read and found that that the memmap kernel parameter could help me: ( http://unix.stackexchange.com/quest...-sector-according-to-memtest86-error-indicati )
My questions is how could I add this parameter to an Android kernel. At the moment I'm using ParanoidAndroid 4.45. I have tried until now apps such as Trickster MOD but memmap is not among the parameters I can edit.
Thanks for your help.
Every consider just rma'ing the device. If you have bad sectors I doubt you'll be able to exclude them
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Every consider just rma'ing the device. If you have bad sectors I doubt you'll be able to exclude them
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
As I have said in my previous post, "Sending it to warranty is out of the question since this is a used device bought from a shady guy who is not answering my calls."
I am sure there must be a way to exclude the bad sectors. There are some useful links online but I don't have any idea how to start.
Useful links:
https://android.googlesource.com/kernel/common/+/android-3.10/drivers/firmware/memmap.c
https://github.com/hypnos-android/Hypnos/blob/master/Documentation/ABI/testing/sysfs-firmware-memmap
cozmy said:
As I have said in my previous post, "Sending it to warranty is out of the question since this is a used device bought from a shady guy who is not answering my calls."
I am sure there must be a way to exclude the bad sectors. There are some useful links online but I don't have any idea how to start.
Useful links:
https://android.googlesource.com/kernel/common/+/android-3.10/drivers/firmware/memmap.c
https://github.com/hypnos-android/Hypnos/blob/master/Documentation/ABI/testing/sysfs-firmware-memmap
Click to expand...
Click to collapse
Have you tried checking the file structure using e2fsck in an adb shell? Double check this because it can be dangerous to use but it should go something like this:
Open a cmd window
Type adb shell
Type e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
Full disclosure, I have not run this on my own device
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Have you tried checking the file structure using e2fsck in an adb shell? Double check this because it can be dangerous to use but it should go something like this:
Open a cmd window
Type adb shell
Type e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
Full disclosure, I have not run this on my own device
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
This is what I have got after running your command: http://prntscr.com/4eobxy
The only exception is that I added the -n parameter since I have not unmounted anything.
Now that Dev Preview of Android 11 was published I would love to test it. Of curse I don't want to install it on my phone since it's my daily driver and especially the first previews are buggy as hell besides not working apps. Emulators are just slow as hell.
Now, Google did introduce Dynamic System Updates https://developer.android.com/topic/dsu a few month back to let GSIs run like a Linux Live distribution and to get rid of it via a simple reboot without any trouble like having to reset the device to flash the ROM.
Has anybody tested DSU installation in general and especially with the GSI of the Dev Preview? I followed it step by step, I even tried using simg2img system.img system_raw.img on the img but only got "Invalid sparse file format at header Failed to read sparse file" back.
On my phone the Dynamic update does start and asks me for my fingerprint but the notification just says "installation failed". Sadly I couldn't find a way to make adb shell print any information why it failed. Did anybody else have more success?
PS: since the commands seem to be written for Linux I tested it with Debian 10 inside the Windows Subsystem for Linux. I don't think it should make a difference though.
Have you unlocked the bootloader of your phone? DSU requires an unlocked bootloader.
I successfully installed the Android 11 GSI on my Pixel 3 XL using DSU.
MishaalRahman said:
Have you unlocked the bootloader of your phone? DSU requires an unlocked bootloader.
I successfully installed the Android 11 GSI on my Pixel 3 XL using DSU.
Click to expand...
Click to collapse
Did you download the GSI from here?
Might give it a go through DSU on my phone.
Sent from my Pixel 3a XL using XDA Labs
Skittles9823 said:
Did you download the GSI from here?
Might give it a go through DSU on my phone.
Sent from my Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
Yes.
MishaalRahman said:
Yes.
Click to expand...
Click to collapse
Sweet, thanks :good:
Sent from my Pixel 3a XL using XDA Labs
To both questions yes. I fear magisk is the one that might cause the falling. That would be sad
Artim_96 said:
To both questions yes. I fear magisk is the one that might cause the falling. That would be sad
Click to expand...
Click to collapse
That would make sense.
Sent from my Pixel 3a XL using XDA Labs
Skittles9823 said:
That would make sense.
Sent from my Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
Sideloaded DP1 yesterday and running nicely tbh
Skittles9823 said:
That would make sense.
Sent from my Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
It would make sense, but it doesn't seem to be true. Deactivated magisk by flashing stock boot image, tried again... Same result
Artim_96 said:
It would make sense, but it doesn't seem to be true. Deactivated magisk by flashing stock boot image, tried again... Same result
Click to expand...
Click to collapse
Are you current running stock Android 10?
Sent from my Pixel 3a XL using XDA Labs
Skittles9823 said:
Are you current running stock Android 10?
Sent from my Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
Yes. Latest stock Android, never had a custom ROM or recovery installed on my Pixel
Artim_96 said:
Yes. Latest stock Android, never had a custom ROM or recovery installed on my Pixel
Click to expand...
Click to collapse
Well, looking at the DSU documentation it does suggest you to be on a userdebug build. Stock is generally user unless you've built it yourself.
Sent from my Pixel 3a XL using XDA Labs
Skittles9823 said:
Well, looking at the DSU documentation it does suggest you to be on a userdebug build. Stock is generally user unless you've built it yourself.
Sent from my Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
It only says when you have a userdebug build you can activate that in the Flags. Else, you activate it via ADB shell
Artim_96 said:
It only says when you have a userdebug build you can activate that in the Flags. Else, you activate it via ADB shell
Click to expand...
Click to collapse
Ahh, fair enough. In that case I'm unsure, I'm currently running a custom rom I plan to stay on so I can't really fiddle around with flashing stock to test DSU.
Sent from my Pixel 3a XL using XDA Labs
Ok, I've made a log of the installation (with magisk still installed), from what I see it might abort because of too little space.
The question is only: is it too little space where I can make space or is it missing free space in a partition where it's not possible? And how much space do I have to free up? (Aka do I see it right I have to free up about 4 GB?)View attachment DSU.txt
Artim_96 said:
Ok, I've made a log of the installation (with magisk still installed), from what I see it might abort because of too little space.
The question is only: is it too little space where I can make space or is it missing free space in a partition where it's not possible? And how much space do I have to free up? (Aka do I see it right I have to free up about 4 GB?)
Click to expand...
Click to collapse
4gb probably isn't enough to install it.
Sent from my Pixel 3a XL using XDA Labs
Additionally, calculated from the numbers I've found in the log. I can free up nearly 6 GB additionally to what's already free by just deleting a Titanium Backup
From Stock 10 to RPP
Artim_96 said:
Additionally, calculated from the numbers I've found in the log. I can free up nearly 6 GB additionally to what's already free by just deleting a Titanium Backup
Click to expand...
Click to collapse
I went directly from stock 10 to RPP - and did NOT rely on an on-phone backup (which you are trying to do). Stock 10 backs up to the cloud (as has Android since 8) - this is by default. Samsung Experience included cloud backup, which OneUI retained (this is via the Samsung Members app). Dependng on your settings, you may not NEED to rely on on-phone backups any more. I use RPP as a daily driver - and have since it launched; however, Google doesn't recommend it - and I won't recommend it for anyone that hated Android 10 (The RPP is a superset of 10.)
PGHammer said:
I went directly from stock 10 to RPP - and did NOT rely on an on-phone backup (which you are trying to do). Stock 10 backs up to the cloud (as has Android since 8) - this is by default. Samsung Experience included cloud backup, which OneUI retained (this is via the Samsung Members app). Dependng on your settings, you may not NEED to rely on on-phone backups any more. I use RPP as a daily driver - and have since it launched; however, Google doesn't recommend it - and I won't recommend it for anyone that hated Android 10 (The RPP is a superset of 10.)
Click to expand...
Click to collapse
Of course I hope that I won't need Titanium Backups, because Google had more than enough time to figure out that problem themselves, especially on their own devices. It's more like a "better safe than sorry" solution. I just saved the backup to cloud so I hope I can try to install it tomorrow afternoon. Let's see if it was really only a problem of too little space
There are good news and bad news: the good news is I finally found out why the installation always immediately failed: you are required to have at least 40% free space on your phone. Now that I freed up enough space the installation starts.
There comes the bad news: the notification disappears shortly before the progress bar reaches the end, the installation falls again. At first I tried to install it with magisk still present, so I was able to make a log on device. It shows that it fails because it "failed to create or open data/gsi/dsu/userdata_gsi.img" and "File is too fragmented, needs more than 512 extents" (log attached). But I can't find a reason why. The same happened with stock boot.img flashed, I logged out through adb. (had to upload the log to GDrive since it's too big for xda and for pastebin: https://drive.google.com/open?id=1WEp5jydjYF2UmuLgOvx_fs4KGpJ1hKAq)View attachment 2020-02-26-19-00-05.txt