Develop Bugs

[Q] "Lost" Internal Storage and ODIN after failed encryption on ICS (AOKP Build 39)

[Q] "Lost" Internal Storage and ODIN after failed encryption on ICS (AOKP Build 39)
I have kind of an odd one. I flashed AOKP Build 39 today (using ODIN to EL29 CWM then flash). That went fine. Then I tried to encrypt the phone, which failed and kicked me back out to reboot. It mentioned something about having to do a full factory reset. I think I saw the default recovery logo show for a second before the AOKP boot animation kicked in. Phone booted fine, then I noticed that I lost the Internal storage. My SD card is at /emmc, and it works fine. I tried to ODIN back to EL29 CWM to do a full reflash (using the 1 Click Restore in the Sticky section) and now ODIN keeps failing at "Setting up Connection"
I'm hoping you guys can give me some insight

I dont have much to say on whats going on or how to fix it but.... From what I've read from your post you said something about a "factory wipe" form the "stock recovery"!!! I know you said that you didn't do the wipe, the phone did when it reset itself... I know that is a big no no with this rom. And the mention of eMMC... Sounds like the eMMC hardbrick bug.
On a side: This has got to be at least the 3rd or 4th post I've read today with the words "AOKP Build 39", "eMMC" and "factory reset" in them. And not one of them has turned out good.
Sent From My Galaxy Class StarFighter

I don't think it is the eMMC hardbrick bug. From what I have read of that, it completely hoses the phone. Also Build 39 has CWM 5.5 (which I heard is a bad build), so I didn't see it boot into Recovery.
I looked into it more and I keep seeing things in logcat about bad partitions. I would try an reformat it, 'cept I don't know how (safely at least). Maybe flashing Caulkin's Format All? I've pasted in the logcat info for anyone that wants to look
Code:
D/VoldCmdListener( 1745): volume mount /mnt/sdcard
D/DirectVolume( 1745): Checking for bad partition major number
D/DirectVolume( 1745): Found bad partition
E/DirectVolume( 1745): Fixing major number from 179 to 259 for partition 11
I/Vold ( 1745): /dev/block/vold/259:3 being considered for volume internal
D/Vold ( 1745): Volume internal state changing 1 (Idle-Unmounted) -> 3 (Checking)
D/MountService( 1865): volume state changed for /mnt/sdcard (unmounted -> checking)
I/StorageNotification( 1955): Media {/mnt/sdcard} state changed from {unmounted} -> {checking}
D/MountService( 1865): sendStorageIntent Intent { act=android.intent.action.MEDIA_CHECKING dat=file:///mnt/sdcard (has e
xtras) }
I//system/bin/fsck_msdos( 1745): ** /dev/block/vold/259:3
I//system/bin/fsck_msdos( 1745): Invalid signature in boot block: f616
I/logwrapper( 1745): /system/bin/fsck_msdos terminated by exit(2)
E/Vold ( 1745): Filesystem check failed (not a FAT filesystem)
W/Vold ( 1745): /dev/block/vold/259:3 does not contain a FAT filesystem
E/Vold ( 1745): /dev/block/vold/259:3 failed to mount via NTFS (No such device)
E/Vold ( 1745): Volume internal found no suitable devices for mounting :(
D/Vold ( 1745): Volume internal state changing 3 (Checking) -> 1 (Idle-Unmounted)
I/PackageManager( 1865): Updating external media status from unmounted to unmounted
D/MountService( 1865): volume state changed for /mnt/sdcard (checking -> unmounted)
D/MountService( 1865): sendStorageIntent Intent { act=android.intent.action.MEDIA_UNMOUNTED dat=file:///mnt/sdcard (has
extras) }
D/MediaScannerReceiver( 2029): action: android.intent.action.MEDIA_UNMOUNTED path: /mnt/sdcard
I/MemorySettings( 4775): Received storage state changed notification that /mnt/sdcard changed state from unmounted to ch
ecking
I/MemorySettings( 4775): Received storage state changed notification that /mnt/sdcard changed state from checking to unm
ounted
I/StorageNotification( 1955): Media {/mnt/sdcard} state changed from {checking} -> {unmounted}
D/VoldCmdListener( 1745): volume shared /mnt/sdcard ums
D/VoldCmdListener( 1745): volume shared /mnt/emmc ums

So I managed to fix the issue myself. I'll put the instructions down here in case anyone needs them
I tried "normal" Odin and that let me flash the EL29 CWM. From there I just flashed Caulkin's Format All (several times) and then reflashed my ROM.

"normal" odin as opposed to ? mobile odin ? I never mobile odin .. I personally do not trust it .. I have always and will always "normal" odin

i think people should just stop flashing those aokp
i try to time and it fail on my phone
better safe than sorry

yoo0angg said:
"normal" odin as opposed to ? mobile odin ? I never mobile odin .. I personally do not trust it .. I have always and will always "normal" odin
Click to expand...
Click to collapse
As opposed to the EL29 Restore executable, ie this http://forum.xda-developers.com/showthread.php?t=1433101

Kyral Retsam said:
So I managed to fix the issue myself. I'll put the instructions down here in case anyone needs them
I tried "normal" Odin and that let me flash the EL29 CWM. From there I just flashed Caulkin's Format All (several times) and then reflashed my ROM.
Click to expand...
Click to collapse
Awesome m8!!!
Glad it wasn't as bad...
mrej201 said:
i think people should just stop flashing those aokp
i try to time and it fail on my phone
better safe than sorry
Click to expand...
Click to collapse
That's what I'm saying...
Sent From My Galaxy10.1 Class Starship...

[Q] Galaxy nexus showing error after every boot

i just bought a used Galaxy nexus Gsm. but every time it boots this error comes up "Unfortunately, the process com.android.phone has stopped"
when i press ok it goes away and phone seems to work fine.
i have tried flashing the stock rom thorough ODIN and also tried couple of custom Roms but the error still persists. i'll be grateful if someone could help me out. cheers

coolshan said:
i just bought a used Galaxy nexus Gsm. but every time it boots this error comes up "Unfortunately, the process com.android.phone has stopped"
when i press ok it goes away and phone seems to work fine.
i have tried flashing the stock rom thorough ODIN and also tried couple of custom Roms but the error still persists. i'll be grateful if someone could help me out. cheers
Click to expand...
Click to collapse
Flash the factory images available on Google's servers using this guide: http://forum.xda-developers.com/showthread.php?t=1626895. Don't use Odin unless you have to, fastboot is the preferred method for flashing a Nexus.
If that doesn't help, post a logcat (use adb to get it). We can try finding the cause with that.

Petrovski80 said:
Flash the factory images available on Google's servers using this guide: http://forum.xda-developers.com/showthread.php?t=1626895. Don't use Odin unless you have to, fastboot is the preferred method for flashing a Nexus.
If that doesn't help, post a logcat (use adb to get it). We can try finding the cause with that.
Click to expand...
Click to collapse
how to get the logcat ? can you tell me the procedure? i have adb and all the drivers installed already

coolshan said:
how to get the logcat ? can you tell me the procedure? i have adb and all the drivers installed already
Click to expand...
Click to collapse
- enable usb debugging via developer options
- reboot phone
- wait for error to display
- connect phone via USB to computer
- open a command prompt where the adb executable is located
- type: abd logcat > c:\MyLogcat\logcat.txt

Petrovski80 said:
Flash the factory images available on Google's servers using this guide: http://forum.xda-developers.com/showthread.php?t=1626895. Don't use Odin unless you have to, fastboot is the preferred method for flashing a Nexus.
If that doesn't help, post a logcat (use adb to get it). We can try finding the cause with that.
Click to expand...
Click to collapse
Petrovski80 said:
- enable usb debugging via developer options
- reboot phone
- wait for error to display
- connect phone via USB to computer
- open a command prompt where the adb executable is located
- type: abd logcat > c:\MyLogcat\logcat.txt
Click to expand...
Click to collapse
i have attached the logcat.txt file. have a look at it. i personally dont understand a thing lol

coolshan said:
i have attached the logcat.txt file. have a look at it. i personally dont understand a thing lol
Click to expand...
Click to collapse
Looking through your logcat, I see several exceptions, one of them concerns the RIL (radio interface layer). I'm thinking this causes your error after each boot:
Code:
D/CAT ( 584): RilMessageDecoder: decodeMessageParams: caught ResultException e=result=CMD_DATA_NOT_UNDERSTOOD additionalInfo=-1 explantion=length < 0x80 length=0 curIndex=3 endIndex=113
W/dalvikvm( 584): threadid=1: thread exiting with uncaught exception (group=0x41a30300)
E/AndroidRuntime( 584): FATAL EXCEPTION: main
E/AndroidRuntime( 584): java.lang.NullPointerException
E/AndroidRuntime( 584): at com.android.internal.telephony.cat.CatService.handleRilMsg(CatService.java:172)
E/AndroidRuntime( 584): at com.android.internal.telephony.cat.CatService.handleMessage(CatService.java:619)
E/AndroidRuntime( 584): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 584): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 584): at android.app.ActivityThread.main(ActivityThread.java:4896)
E/AndroidRuntime( 584): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 584): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 584): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
E/AndroidRuntime( 584): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
E/AndroidRuntime( 584): at dalvik.system.NativeStart.main(Native Method)
However, I have no idea what causes the exception. I would try flashing the appropriate RIL for you device, look here: http://forum.xda-developers.com/showpost.php?p=27441945
As for the rest of your logcat, the following apps cause exceptions as well:
- geniewidget: file not found exception. Probably nothing to worry about if it's working OK.
- SuperSU: java IO exception when executing /system/.bash/.ssu, -v. Not sure what's going on there, are SuperSU and its su binary up to date? Worth checking out imho.
- Go SMS sinaweibo plugin: illegal argument exception. Again, if this is working OK don't worry about it.
- Plume: arrayindex out of bounds exception. If this is working OK don't worry about it.

Petrovski80 said:
Looking through your logcat, I see several exceptions, one of them concerns the RIL (radio interface layer). I'm thinking this causes your error after each boot:
Code:
D/CAT ( 584): RilMessageDecoder: decodeMessageParams: caught ResultException e=result=CMD_DATA_NOT_UNDERSTOOD additionalInfo=-1 explantion=length < 0x80 length=0 curIndex=3 endIndex=113
W/dalvikvm( 584): threadid=1: thread exiting with uncaught exception (group=0x41a30300)
E/AndroidRuntime( 584): FATAL EXCEPTION: main
E/AndroidRuntime( 584): java.lang.NullPointerException
E/AndroidRuntime( 584): at com.android.internal.telephony.cat.CatService.handleRilMsg(CatService.java:172)
E/AndroidRuntime( 584): at com.android.internal.telephony.cat.CatService.handleMessage(CatService.java:619)
E/AndroidRuntime( 584): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 584): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 584): at android.app.ActivityThread.main(ActivityThread.java:4896)
E/AndroidRuntime( 584): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 584): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 584): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
E/AndroidRuntime( 584): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
E/AndroidRuntime( 584): at dalvik.system.NativeStart.main(Native Method)
However, I have no idea what causes the exception. I would try flashing the appropriate RIL for you device, look here: http://forum.xda-developers.com/showpost.php?p=27441945
As for the rest of your logcat, the following apps cause exceptions as well:
- geniewidget: file not found exception. Probably nothing to worry about if it's working OK.
- SuperSU: java IO exception when executing /system/.bash/.ssu, -v. Not sure what's going on there, are SuperSU and its su binary up to date? Worth checking out imho.
- Go SMS sinaweibo plugin: illegal argument exception. Again, if this is working OK don't worry about it.
- Plume: arrayindex out of bounds exception. If this is working OK don't worry about it.
Click to expand...
Click to collapse
its not working... i flashed the RIL with GETRIL app. and it says it a matching one. i even tried an other one for JB but in vain. its really irritating me now.. what is the problem :/

coolshan said:
its not working... i flashed the RIL with GETRIL app. and it says it a matching one. i even tried an other one for JB but in vain. its really irritating me now.. what is the problem :/
Click to expand...
Click to collapse
Have you tried going completely back to stock using this guide: http://forum.xda-developers.com/showthread.php?t=1626895

Petrovski80 said:
Have you tried going completely back to stock using this guide: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
i did. i even flashed other radios but nothing seems to work. could you tell me what is the purpose of this process ? "com.android.phone"

coolshan said:
i did. i even flashed other radios but nothing seems to work. could you tell me what is the purpose of this process ? "com.android.phone"
Click to expand...
Click to collapse
That's the phone app in /system/app.
I'm beginning to think your problem might be related to hardware. I'm out of suggestions I'm afraid.
Sent from my Galaxy Nexus using Tapatalk 2

Petrovski80 said:
That's the phone app in /system/app.
I'm beginning to think your problem might be related to hardware. I'm out of suggestions I'm afraid.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
yeah me too.. thanks for the help though. but still i dont understand why is they phone functioning properly? what disfunction this process can cause ? it seems to make and receive calls and sms without any probelm

Petrovski80 said:
That's the phone app in /system/app.
I'm beginning to think your problem might be related to hardware. I'm out of suggestions I'm afraid.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
i found the problem !! its neither software nor hardware infact its my sim card thats causing it. changed the sim card and it booted normally my sim card is quite old so may be that could be a reason. but its a relief.. thanks man u really helped me out alot. learned alot from you. :good:

coolshan said:
i found the problem !! its neither software nor hardware infact its my sim card thats causing it. changed the sim card and it booted normally my sim card is quite old so may be that could be a reason. but its a relief.. thanks man u really helped me out alot. learned alot from you. :good:
Click to expand...
Click to collapse
Great you fixed it. Thanks for posting the solution here.
Sent from my Galaxy Nexus using Tapatalk 2

Can't install Dropbox, Chromium ROM 11

Hello i got a strange problem. Few days ago I got crash when i want to open (installed before and updated before to the last version) Dropbox. It happens suddenly. After update it works fine, but with next trying to open, apps got crash and closed. I decided to do reinstall, uninstalling and installing again, but i had some bugs/errors.
When i want to download i got problem called Error -24, i found sollution for it, but don't work for me.
Sollution is like:
Qewbicle said:
Go to
/data/data/
and search for your
com.application-address.whatever-it-may-be
Some of them you can tell what they are just by the names, the others, google-em.
If you wish to keep the information that it contains for the app, I recommend making a copy of it first.
Delete it
Install the application, it'll work, trust me.
Now replace it with your copy.
Done.
Click to expand...
Click to collapse
But it didn't works for me, after this i got problem with package lost in google play store. Sometimes i got LOW STORAGE info, but it is fake, cause i could install other apps, much bigger than dropbox - so i have space to install.
I delete folder com.dropbox from:
/data/data
/data/usr/0/
/data/system
every dropbox folder
I tried to install dropbox from official homepage, i get the app on my phone, but installation is not finish. I also tried to restore backup of Dropbox via titanium backup, but it stuck on the restoring (app only and same for app + data)
I don't have no idea what is wrong. I did also FIX APK Permission from 4EXT Recovery without any result.
Here is my logcat:
Code:
I/SystemServer( 418): DropBox Service
I/BootReceiver( 418): Copying /proc/last_kmsg to DropBox (SYSTEM_LAST_KMSG)
I/ActivityManager( 418): START u0 {act=android.intent.action.VIEW dat=file:///storage/sdcard0/Download/Dropbox.apk typ=application/vnd.android.package-archive cmp=com.android.packageinstaller/.PackageInstallerActivity} from pid 2538
I/AppSecurityPermissions( 2763): Ignoring unknown permission:com.dropbox.android.permission.C2D_MESSAGE
I/ActivityManager( 418): START u0 {dat=file:///storage/sdcard0/Download/Dropbox.apk cmp=com.android.packageinstaller/.InstallAppProgress (has extras)} from pid 2763
W/ActivityManager( 418): No content provider found for permission revoke: file:///storage/sdcard0/Download/Dropbox.apk
W/ActivityManager( 418): No content provider found for permission revoke: file:///storage/sdcard0/Download/Dropbox.apk
I/PackageManager( 418): Running dexopt on: com.dropbox.android
E/installd( 84): dexopt cannot open '/data/dalvik-cache/[email protected]@[email protected]' for output
W/PackageManager( 418): Package couldn't be installed in /data/app/com.dropbox.android-1.apk
I/InstallAppProgress( 2763): Finished installing com.dropbox.android
Any sollution? I am working with it about few hours... Thanks for help.
I almost forgot, after some restarts and clean dalvick-cache my Titanium Backup was gone, and i had to install it again, strange situation when app suddenly dissappear, any fix for it too?
Update:
I tried to install via terminal emulator but got message:
Code:
pkg: Dropbox.apk
Failure [INSTALL_FAILED_DEXOPT]

adb restore not working

I've upgraded my tablet from Cynogen to Lineage. When still on CM, I made a full adb backup. I used a tool to see what is in it, and it seemed all fine.
Now it's upgraded to Lineage. I did an adb restore, and it finished without errors or warnings. And the result: *nothing* got restored, not even after a reboot. Absolutely nothing.
What do I do to get the backup file restored?

adb logcat has entries for each and every app:
Code:
09-15 14:41:56.641 678 3422 I BackupManagerService: Package bz.ktk.bubble not installed; requiring apk in dataset
09-15 14:41:56.642 678 3422 D BackupManagerService: APK file; installing
09-15 14:41:56.642 678 3422 D BackupManagerService: Installing from backup: bz.ktk.bubble
09-15 14:41:56.686 2816 2828 W asset : Asset path /data/cache/backup_stage/bz.ktk.bubble is neither a directory nor file (type=0).
09-15 14:41:56.687 2816 2828 W DefContainer: Failed to parse package at /data/cache/backup_stage/bz.ktk.bubble: android.content.pm.PackageParser$PackageParserException: Failed to parse /data/cache/backup_stage/bz.ktk.bubble
09-15 14:41:56.689 678 3422 D BackupManagerService: [discarding file content]
How do I fix that??

Hi thany2
I had the exact same issue when trying to restore a backup made on Android 8.1 to Android 8.1.
Through trial and error, I found that `abe unpack` and `abe pack` fixes the issue and I was able to restore the backup. abe: android-backup-extractor. You might need to install apks beforehand. Just run `adb logcat` while restoring.

Ota 10.0.6 broke my mobile data. Files needed.

Oh well..
Upgraded from 10.0.4 to 10.0.6 via ota and boom my mobiledata is gone.
I do NOT want to factory reset. Lets try it if nothing else helps.
Can someone put somewhere where I can download files from 10.0.4 eu rom:
/system/priv-app/TeleService/*
My logcat shows:
FATAL EXCEPTION: main
Process: com.android.phone, PID: 10338
java.lang.RuntimeException: Unable to instantiate application com.android.phone.PhoneApp: java.lang.ClassNotFoundException: Didn't find class "com.android.phone.PhoneApp" on path: DexPathList[[zip file "/system/priv-app/TeleService/TeleService.apk"],nativeLibraryDirectories=[/system/priv-app/TeleService/lib/arm64, /system/priv-app/TeleService/TeleService.apk!/lib/arm64-v8a, /system/lib64, /product/lib64, /system/lib64, /product/lib64]]
at android.app.LoadedApk.makeApplication(LoadedApk.java:1226)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6594)
at android.app.ActivityThread.access$1600(ActivityThread.java:231)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1952)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7682)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:516)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:950)
Caused by: java.lang.ClassNotFoundException: Didn't find class "com.android.phone.PhoneApp" on path: DexPathList[[zip file "/system/priv-app/TeleService/TeleService.apk"],nativeLibraryDirectories=[/system/priv-app/TeleService/lib/arm64, /system/priv-app/TeleService/TeleService.apk!/lib/arm64-v8a, /system/lib64, /product/lib64, /system/lib64, /product/lib64]]
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:196)
at java.lang.ClassLoader.loadClass(ClassLoader.java:379)
at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
at android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
at android.app.Instrumentation.newApplication(Instrumentation.java:1153)
at android.app.LoadedApk.makeApplication(LoadedApk.java:1218)
... 9 more
Suppressed: java.io.IOException: Failed to open dex files from /system/priv-app/TeleService/TeleService.apk because: Failure to verify dex file '/system/priv-app/TeleService/TeleService.apk': Bad checksum (c0c2207c, expected 277e206c)
at dalvik.system.DexFile.openDexFileNative(Native Method)
at dalvik.system.DexFile.openDexFile(DexFile.java:365)
at dalvik.system.DexFile.<init>(DexFile.java:107)
at dalvik.system.DexFile.<init>(DexFile.java:80)
at dalvik.system.DexPathList.loadDexFile(DexPathList.java:444)
at dalvik.system.DexPathList.makeDexElements(DexPathList.java:403)
at dalvik.system.DexPathList.<init>(DexPathList.java:164)
at dalvik.system.BaseDexClassLoader.<init>(BaseDexClassLoader.java:126)
at dalvik.system.BaseDexClassLoader.<init>(BaseDexClassLoader.java:101)
at dalvik.system.PathClassLoader.<init>(PathClassLoader.java:74)
at com.android.internal.os.ClassLoaderFactory.createClassLoader(ClassLoaderFactory.java:87)
at com.android.internal.os.ClassLoaderFactory.createClassLoader(ClassLoaderFactory.java:116)
at android.app.ApplicationLoaders.getClassLoader(ApplicationLoaders.java:114)
at android.app.ApplicationLoaders.getClassLoaderWithSharedLibraries(ApplicationLoaders.java:60)
at android.app.LoadedApk.createOrUpdateClassLoaderLocked(LoadedApk.java:851)
at android.app.LoadedApk.getClassLoader(LoadedApk.java:950)
at android.app.LoadedApk.getResources(LoadedApk.java:1188)
at android.app.ContextImpl.createAppContext(ContextImpl.java:2499)
at android.app.ContextImpl.createAppContext(ContextImpl.java:2491)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6497)
... 8 more

Here you go.

Thanks mate. Did not help. Was weird cache problem and only factory reset solved it.

tohtorin said:
Thanks mate. Did not help. Was weird cache problem and only factory reset solved it.
Click to expand...
Click to collapse
By what means did you do factory reset? Did you lose root?

Cowbell_Guy said:
By what means did you do factory reset? Did you lose root?
Click to expand...
Click to collapse
Nothing else helped out. Factory reset does not lose root because it keeps magisk modded boot image. You just need to install it again from magisk manager.

i had the same, and after monster process of rooting and 1:1 backup restoration (3 days), the last thing was to insert the SIM card (only after phone is secure), bang. Factory reset is something i never do unless i'm switching phone so i started checking files (same vs backup), log tracing, reverse engineering but then i quickly realized why bother if we have a patch boy - OOS Native Call Recording - here, so i just removed and installed the magisk plugin and it's fixed the problem.