Database Info

Misnamed apps? Wrong versions? Fix here

Taking some advice I saw on the BAW forum one step further, I deleted the entire /data/boot-cache directory (after doing a nandroid backup of course).
Took about 3-4 extra minutes to boot up, presumably to recreate the contents of the directory, but now all of my apps are showing the correct version, correct icon, and correct name. Haven't run into any issues yet.

I didn't want to suggest this just in case something else would mess up. If you have a lot of bad apps this is perhaps faster than deleting each one.

gilroykilroy said:
I didn't want to suggest this just in case something else would mess up. If you have a lot of bad apps this is perhaps faster than deleting each one.
Click to expand...
Click to collapse
Hey there you are! Hah.
I did have a lot of bad apps and had some trouble finding the proper directories for a few. I had just done a backup so I thought I'd give it a try.
I also figured this was the perfect place to suggest it for people to try - around here people are smart enough to do real backups before they start deleting things

Is this with just rooting the phone or after you install the custom rom?

goku14238 said:
Is this with just rooting the phone or after you install the custom rom?
Click to expand...
Click to collapse
I haven't touched the custom ROM yet. You do need to root the phone to do this, and it must be done from a shell.

goku14238 said:
Is this with just rooting the phone or after you install the custom rom?
Click to expand...
Click to collapse
Just rooting the phone.

So this fixes the issue of my chompSMS thinking its name is "com.p1.chomps..."??

Negrito said:
So this fixes the issue of my chompSMS thinking its name is "com.p1.chomps..."??
Click to expand...
Click to collapse
It should, yes. I had a bunch of apps misnamed in that way (EasyMoney, Spades, a few others) and it fixed them.
One of them, Buka Lite, reverted back, though.

I tried this out and all the programs I'd been having issues with were fixed. I rebooted. Still fixed.
But then I installed three updates and after reboot, the same issue came back again. There must be another cache store somewhere...maybe Android Market related, or at least the Android package manager. Either way, I guess some more digging is in order.

mercado79 said:
I tried this out and all the programs I'd been having issues with were fixed. I rebooted. Still fixed.
But then I installed three updates and after reboot, the same issue came back again. There must be another cache store somewhere...maybe Android Market related, or at least the Android package manager. Either way, I guess some more digging is in order.
Click to expand...
Click to collapse
I think there's just a bug with the way the phone handles the cache. Did the versions go back to what they were before you deleted the cache, or what they were after you deleted the cache and before you updated the apps?

Looks like the versions didn't revert. Last night, I used aTrackDog to send myself a list of all my apps. I can't remember the three that I updated today, but the two I do remember, Flixster Movies and Handcent did not revert.
Lastnight:
Movies,2.0.1
Handcent Sms,2.9.12
Now:
Movies,2.1.0
Handcent Sms,2.9.13

Well, I decided to remove Dolphin browser since I noticed it kept opening up and running in the background (active, at least that's what Taskiller says). Of course, the next reboot caused all the icons to get messed up again.
So, I thought to look for other cache directories. Does anyone think that deleting /data/dalvik-cache in addition to the /data/boot-cache directory might help? Is it safe to try it out? I'm assuming it'll just get repopulated automatically.

mercado79 said:
I tried this out and all the programs I'd been having issues with were fixed. I rebooted. Still fixed.
But then I installed three updates and after reboot, the same issue came back again. There must be another cache store somewhere...maybe Android Market related, or at least the Android package manager. Either way, I guess some more digging is in order.
Click to expand...
Click to collapse
After you install any updates you will have to continue to remove the /data/boot-cache version until HTC/Sprint fixes the bug.

gilroykilroy said:
After you install any updates you will have to continue to remove the /data/boot-cache version until HTC/Sprint fixes the bug.
Click to expand...
Click to collapse
Would uninstalling the original, then installing the newest version alleviate the issue? As opposed to just update the app...

Negrito said:
Would uninstalling the original, then installing the newest version alleviate the issue? As opposed to just update the app...
Click to expand...
Click to collapse
Nope. I even tried uninstalling, rebooting twice, then installing again. Reverted on next boot.

jonnythan said:
Nope. I even tried uninstalling, rebooting twice, then installing again. Reverted on next boot.
Click to expand...
Click to collapse
Damn. It sounded good in theory.

I had this issue with Google Sky Maps and it worked to let me back in. What was displaying after a day or so renamed itself to 'End User License Agreement' and wouldn't let me get past the EULA screen, only offering the option to force close.
The only caveat is that now Sky Maps is still named 'End User License Agreement', but it at least let's me in.
Odd

I tried removing both boot-cache and dalvik-cache. Didn't make any difference...eventually, the errors return if/when you update or install an app.

this must be a bug with the hero. i had the Moment and no apps renamed themselves at all. reset after reset the apps were fine. i reset my hero once and it messes up the apps

Doh! Doesn't seem like there's any easy perm fix in sight... hope it doesn't happen w/ 2.0 and Sense...

[Q] Using ROM: "JVU[2.3.6] SAUROM", but Apps go away after Reboot

Hi All,
I seriously read all 17 pages of SAUROM's Dev page and only found 1 other use having this issue but post has no response:
http://forum.xda-developers.com/showpost.php?p=20344195&postcount=31
I also searched and most people have somewhat similar issues but not like mine where it works first time fine then upon reboot Apps disappear.
I've rooted my Infuse a long time ago and have been ROM'ing it for several months now. I've changed several ROMs and some have lots of pieces I love but has issues with something I really need (like bluetooth).
So I gave SAUROM 'One rom to rule em all' a shot. I actually really am impressed upon initial Flash. I made lots of changes, and then lost root/SU, then found SU-fix and applied. It worked for about one day then when I reboot my Apps (including Market) were dimmed-out. So I tried to search but no decent threads.
I thought perhaps another Flash of the ROM would fix, but same issue, then thought perhaps a kernel change so I did that too.
But I just did it again and during first boot everything looks good, I make changes add my gmail acct, use some Apps (actually last time I used Supercharger and installed busybox) but even prior to this it was doing the same thing. Then thinking perhaps it might have fixed it, rebooted and still same thing.
Is there any *.zip or setting that perhaps I can check to fix this? Some script that may help to check where this issue lies? How about fstab file that I can check and edit to fix this??
This happens every time I reboot! I installed apps last night and actually held off posting this, then this morning I rebooted and Apps disappear again (even Play Store).

Furosh said:
Hi All,
I seriously read all 17 pages of SAUROM's Dev page and only found 1 other use having this issue but post has no response:
http://forum.xda-developers.com/showpost.php?p=20344195&postcount=31
I also searched and most people have somewhat similar issues but not like mine where it works first time fine then upon reboot Apps disappear.
I've rooted my Infuse a long time ago and have been ROM'ing it for several months now. I've changed several ROMs and some have lots of pieces I love but has issues with something I really need (like bluetooth).
So I gave SAUROM 'One rom to rule em all' a shot. I actually really am impressed upon initial Flash. I made lots of changes, and then lost root/SU, then found SU-fix and applied. It worked for about one day then when I reboot my Apps (including Market) were dimmed-out. So I tried to search but no decent threads.
I thought perhaps another Flash of the ROM would fix, but same issue, then thought perhaps a kernel change so I did that too.
But I just did it again and during first boot everything looks good, I make changes add my gmail acct, use some Apps (actually last time I used Supercharger and installed busybox) but even prior to this it was doing the same thing. Then thinking perhaps it might have fixed it, rebooted and still same thing.
Is there any *.zip or setting that perhaps I can check to fix this? Some script that may help to check where this issue lies? How about fstab file that I can check and edit to fix this??
This happens every time I reboot! I installed apps last night and actually held off posting this, then this morning I rebooted and Apps disappear again (even Play Store).
Click to expand...
Click to collapse
Move your apps to phone.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2 Beta-5

bigfau said:
Move your apps to phone.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
First thanks for the response bigfau!
I have checked this to see if this option would be a good way to resolve my issue but weird thing is that these dimmed-out apps that appear to be on my sdcard actually go away. If they were truly installed on sdcard like SS above says, then I should be able to:
Go to Settings > Applications > Manage applications > On SD Card >
Select App > "Move to phone" but they're not there, only XDA Premium . (attached SS)
After a reboot, I have to go to My Files, App_Manager > App_Backup > user_apps > Re-install My Apps again. But any reboot puts me back at square one.

1. Uninstall and install your launcher app (don't restore)
2. Wipe your dalvik cache (if rooted)
Try this and let me know if that helps.

diablo009 said:
1. Uninstall and install your launcher app (don't restore)
2. Wipe your dalvik cache (if rooted)
Try this and let me know if that helps.
Click to expand...
Click to collapse
*Thanks, your response makes sense as I remember TWLauncher errors with this ROM and think yes my Launcher is the culprit.
Ive been trying to Uninstall and install a launcher (which I thought would be relatively simple).
1. I downloaded/installed 2 different Launchers (Launcher Pro & Go Launcher Ex) from Play Store.
2. Downloaded TW4Manager.apk, tw4key.zip, and ShareApp.apk (for TWLauncer 4.5).
3. Moved TouchWiz30Launcher.apk out of system/apps/ and backed up *just in case*, then rebooted into Recovery and Wiped Dalvik Cache.
When it was booting, it stayed on the Galaxy S boot animation screen for the longest and never booted.
I decided to attempt to Flash Saurom again, (wipe user data, which cache, wipe Dalvik Cache, install ROM zip) and I'm trying again.
But seems like I got some weird chicken/egg thing going on. I can only install apps while booted or phone is on.
Did i do something incorrect?

Furosh said:
I can only install apps while booted or phone is on.
Click to expand...
Click to collapse
Isn't this how it works? I am not sure how you would install apps when the phone is turned off? Or do you mean screen on?

diablo009 said:
Isn't this how it works? I am not sure how you would install apps when the phone is turned off? Or do you mean screen on?
Click to expand...
Click to collapse
Hi diablo009,
Sorry what I was referring to was that it seems yes I can install Apps while phone is on, but they're only available during that time (after installed). Its like they are in RAM and lose them if I shutdown or reboot.
I'm sure it's not the ROM I used as stated in the Title because I've recently done lots of testing on my phone. I again Re-flashed the ROM again doing:
1. Wipe user data/wipe cache/wipe dalvik cache, install ROM .zip.
2. Run Su-fix su-3.0.5-efgh-signed.zip
*Ive tried this with and without reboot in between 1 & 2.
Still same symptoms, loads first time fine. Runs setup, is rooted, can install Apps, then upon reboot they're gone.
So I said okay let's test out another ROM to see if same results, and so yesterday I changed to GamerzRom v8.1, then upped to 9.0 and same results with Apps.
I've used different kernel's (DD_03042012.zip & kernel-2011-11-27.12-40.zip), used diff ROMs, and have also attempted to get back to Stock either by using:
-SGH-I997_UCLB3_INFUSE.zip (I guess this is Stock with Root & couple more things)
-Get back to Stock ROM by using Download-Mode and SGH-i997-UCKJ4-One-Click.jar
After either of these, attempt to re-flash and see if problems go away but they haven't.
Weird thing is sometimes I lose SU/Root sometimes I don't. I'm sure it's something I've done to my phone or the filesystem which is why I'd like to be able to check it out, like fstab, mtab (if there's one), permissions or something else but I'm not sure what to look for =/
Thoughts or other areas I can check?
A checklist would be awesome right now if I could find one....

Backup the data you have on your internal/external SD cards, and format them please. And try to install an app, reboot, and let me know if the issue is still present.

SD
I had the same issue. I blamed it on a bad SD card. I removed the SD card all together and never had the problem since. I only had the stock 2gb card in there so it was not worth the hassle.

icecreamwhat said:
I had the same issue. I blamed it on a bad SD card. I removed the SD card all together and never had the problem since. I only had the stock 2gb card in there so it was not worth the hassle.
Click to expand...
Click to collapse
This is what even I am suspecting now. So only wanted him to format both internal and external. And this one reason I recommend no less than class 6 cards for phones, preferably class 10.
---------- Post added at 04:44 PM ---------- Previous post was at 04:39 PM ----------
1. Clean wipe and ROM install
2. Clean wipe with a different ROM
3. Clear dalvik cache and cache
4. Wipe data for launcher
5. Fresh install of launcher
6. Fresh install of apps and no restoring with TiBu
7. Formatting internal and external memory
8. Take out external memory
9. Change external SD card
There's your checklist, as far as I can think of. And I have marked in green the options you said you have tried.

Hi, you just have to replace the file vold. Fstab and place it on /system /etc
Pm with your mail and I will send to you b/c I have it with me but don't know how to upload here
The file is suppose to say that the apps must stay on the sdcard..
Qkster explain that to me very well, if I were you, I look in his roms thread..
Let me see
Sent from my SAMSUNG-SGH-I997 using XDA

http://forum.xda-developers.com/showthread.php?p=22723345
Sent from my SAMSUNG-SGH-I997 using XDA

diablo009 said:
Backup the data you have on your internal/external SD cards, and format them please. And try to install an app, reboot, and let me know if the issue is still present.
Click to expand...
Click to collapse
Okay glad to report this has helped me! Not sure if the scard (internal/external) was bad or getting full or what but here's what I did:
1. Copied all my data (sdcard [int/ext]) to PC.
2. Format scard: Settings > SD Card/Storage > Unmount SD Card > Format
*Did this for both SDCard & USB Storage
Result in "Lady voice on partioning boot mesg, (basically inoperable phone).
*My fault because I didn't need to do USB storage? Should I have done both SDCard & USB Storage? Either way I think i wanted to restart from scratch with factory type reset/stock ROM.
3. Boot Download-Mode and ROM using: SGH-i997-UCKJ4-One-Click.jar
4. Root phone and tried to Re-flash with custom ROM (Saurom) but need CWM recovery. CWM was in blue-mode, needed Green or Red to flash ROM.
5. Downloading SGS Kernel flasher and flashing it with Entropy's DD
For this I used: DD_03042012.zip, but for me I noticed Market and Maps were "dimmed" out and thought I'm back to square one!
Dunno if this was coincidence or something I did to cause this or what but I think it's important to note because issue seemed to reappear.
I changed the kernel to: kernel-2011-11-27.12-40.zip and dimmed Market/Maps went away.
6. Booted in Recovery, wipe user data/wipe cache/ wipe Dalvik cache, Flash ROM: JVU[2.3.6] SAUROM
7. Booted up, went through SetupWizard, then realized lost Root.
8. Run Su-fix su-3.0.5-efgh-signed.zip
9. Boot phone, verified Root, installed some Apps, and rebooted & Power-Off over 10 times.
All looks good now!
So far its looking like my issue went away!

@OP: This happens many times when the android data files on the external SD get corrupted. And happy to know your issue is resolved

[ROM] Barebone SGS4G KJ6 1.1.3

Barebone SGS4G KJ6 ROM
Use at your own risk, I take no responsibility for anything that may happen to your phone because of this ROM.
Here is a ROM that I made for myself, but what the heck, let's share. This ROM is very stock-like with just few usability mods.
Features
Will not wipe your programs or data, /data is preserved upon install
Heavily debloated. Most essentials apps are still there (like WiFi Calling)
No extra programs added, you need to add your own
ODEXed to save space in /data
CarrierIQ is completely removed
Extended Power Menu (including Screenshot)
Extended Quick Panel (10 buttons, including Data toggle)
1% battery (horizontal)
CRT-Off
Time zone version 2012b
/etc/hosts to cut ads out of the box (keep up to date with AdAway or similar)
Few conservative presets in build.prop and init.d
Basic with a Twist 1.1.3 kernel included
Notes
* Don't get confused about ODEXing, it's actually better to run and saves quite a bit of space in /data.
* Some Google apps (Maps, Streets, Voice) and Adobe Flash are removed from /system. Install them from market. Benefit - they can be moved to SD card this way.
* Original Swype is removed, is somebody needs it flash this.
* In case you need it, use this thread to add some bloat back.
* Factory Reset is removed from Settings->Privacy, use CWM if you ever need to reset all data.
* KJ6 modem included. Use this thread to flash a different modem if needed.
Install
Flash with CWM. Wait until the system boots up, then wait few more minutes for it to settle.
Download
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.8
Changelog
1.1.3
Removed "Mobile data connection disabled. Connect?" popup on boot
1.1.2
Removed Factory Reset from Settings->Privacy
Updated kernel
1.1.1
Fixed voicemail notifications not working without Visual Voice Mail installed
1.1.0
CIQ is properly removed
Some neutral cosmetics (logo, animations)
Minor update to the kernel
1.0.8
Fixed slow stock browser scrolling
1.0.7
Extended Quick Panel
1.0.6
Added Screenshot to power menu
1.0.5
Removed DriveSmart and Software Update from Settings menu
1.0.4
Put original framework-res.apk certificate back
1.0.3
Added power menu mod
1.0.2
Original public release​

does it have a screenshot option from the power menu??

m0bstr said:
does it have a screenshot option from the power menu??
Click to expand...
Click to collapse
Nope, never bothered with power menu. I don't reboot the phone too often and to say the truth don't even remember when last time I needed to take a screenshot. I use ShootMe and QuickBoot when I need to, they both do the job just fine.
Yes, power menu is fully modded now, including Screenshot option.

Thank you for this, Anton! Love your kernel. Is this ROM ok for OC/UVing with you OC/UV kernel? I think this will be the second ROM I have ever installed. Haven't bothered to try anything since first getting Val Final.

Download link is not working
Sent from my SGH-T959V using XDA

Does this come pre-rooted?

Blaggah said:
Does this come pre-rooted?
Click to expand...
Click to collapse
Yeppers it does.

I updated the link. I actually took it down on purpose, wanted to look at something but never had time.
I was troubleshooting an error message during boot time, so I traced it to the CIQ trying to execute some on-boot code, which was removed by Krylon. Strangely the original code itself doesn't do much, it's initilizing a broadcast receiver with an empty onReceive method. Removing this was a moot point, it probably didn't do much. I disabled the BOOT_COMPLETED permission for the service to avoid the error message.
So I looked at the CIQ more closely. What I found is a little peculiar. The main CIQ code is integrated quite deeply into the framework, it cannot be removed easily, there are just too many calls that send various metrics to the CIQ Agent. The main CIQ classes are not in the framework.jar, they are in ext.jar. Probably that's why nobody noticed them and never tried to modify them. What is strange that many calls seem to be not implemented. For example the sumbitMetric is an empty method, shouldSubmitMetric always returns zero, etc.
It's possible that T-Mobile decided not to use CIQ on our phone (at least extensively), but instead of removing it completely just plugged few calls.
I'm removing the "CIQ removed" description because it's actually not removed, although may not be doing much.

I cannot get it to boot. After the "Galaxy S 4G" screen, the screen goes back then nothing ever happens. I rebooted into CWM (which still shows Team Acid's logo) and tried fixing permissions to no avail.
Given that the OP says it won't wipe programs, data, etc, was it possibly a Bad Idea™ to have wiped everything before installing this ROM?
Update:
Indeed, installing from a blank phone (literally, I wiped everything) didn't work for me. I flashed Bryan's one-click with CWM, it booted, rebooted into recovery, flashed this, and it booted. Now for testing. Thanks, Anton!

I had the same issue as well... Thought it was just my phone
Sent from my SGH-T959V using xda premium

Would be interesting to look at the logcat to see where it's stuck.
There was a possible problem with 1.0.3 that I pulled off. The current one that I re-uploaded - I tried to install in on both fresh phone (after factory reset) and on top of a running ROM , everything seemed fine.
The problem was with framework-res.apk. I had to resign in because I changed some permissions in AndroidManifest.xml (related to CIQ), but something went wrong the first time.
There is a little bit of controversy with signing of framework-res.apk. Some say it's OK, some say the original cert should be kept. Maybe somebody else would chime in and tell me if I screwed it up or not.

wont flash
I wipe everything, the ROM installs, and then black screen...noting. Let it sit for 20min however this did not resolve issue. I was able to install Valhalla no prob. flashed your rom on top of Valhalla and then my phone boots your rom. Do i need to install on top of another rom? I should just be able to whipe my phone and install your rom correct?

AntonX said:
Would be interesting to look at the logcat to see where it's stuck.
Click to expand...
Click to collapse
I can probably capture that because I can use adb to get into the OS. I ran top to see what, if anything, was hogging CPU but there was nothing obvious & CPU usage was minimal. I have the phone running now but I'm willing to wipe it again and re-flash. Mind you, I did more than factory reset. I was quite literally trying to start from scratch, so here's what I did (if this helps at all):
Backed up /efs to my PC
Backed up the SD card to my PC
Wiped cache
Wiped Davlik cache
Wiped battery stats
Performed a nandroid backup
Copied the backup from /sdcard/clockworkmod/backup to my PC
Formatted /data, /system, & /sdcard
Rebooted back into recovery
Copied the ROM to the SD card
Flashed it
Let it cook for ~20 minutes
So it was quite literally a blank slate.
AntonX said:
There was a possible problem with 1.0.3 that I pulled off. The current one that I re-uploaded - I tried to install in on both fresh phone (after factory reset) and on top of a running ROM , everything seemed fine.
The problem was with framework-res.apk. I had to resign in because I changed some permissions in AndroidManifest.xml (related to CIQ), but something went wrong the first time.
There is a little bit of controversy with signing of framework-res.apk. Some say it's OK, some say the original cert should be kept. Maybe somebody else would chime in and tell me if I screwed it up or not.
Click to expand...
Click to collapse
I appreciate all of your hard work. When I get the chance I'll download the latest, follow my steps above, & let you know what I find.

stephen_w said:
I appreciate all of your hard work. When I get the chance I'll download the latest, follow my steps above, & let you know what I find.
Click to expand...
Click to collapse
Wow, you really wiped everything from your phone
I'd appreciate if you send me the log. All you need to do is to save the file with "adb logcat -d >MyLogFile.log" after couple of minutes of this black screen. On an factory reset phone ODEXed ROM should boot very fast the first time because it doesn't have to build Dalvik.
I just tried downloading from my own link and reinstalling, everything seems OK. I also tried installing after full phone reset yesterday, it went fine too. I don't want to reset and restore everything anymore, too lazy
If it proves to be the certificate in the framework-res.apk, I may need to put the original AndroidManifest.xml back.

Hey Anton,
You can snag the logcat from here. In case anyone wants them & to clarify what I did, here are the steps I followed (similar to above but more detailed):
- Boot into CWM
adb reboot recovery​- Disable voodoo lagfix
- voodoo lagfix​- disable lagfix​- /system lagfix off​- Reboot
- Create a backup directory structure on your PC (mine is in C:\Users\username\Downloads\SGS4G)
mkdir backups​cd backups​mkdir efs nandroid sdcard​- Backup /efs to your PC
cd efs​adb pull /efs/​- Backup /sdcard to your PC
cd ..\sdcard​adb pull /sdcard/​- Boot into CWM
adb reboot recovery​- Wipe cache
- wipe cache partition​- Wipe Dalvik cache
- advanced​- Wipe Dalvik Cache​- Wipe battery stats
- Wipe Battery Stats​- Create a nandroid backup
- +++++Go Back+++++​- backup and restore​- backup​- Copy the backup to your PC
cd ..\nandroid​adb pull /sdcard/clockworkmod/backup/​- Format /data
- mounts and storage​- format /data​- Format /sdcard
- format /sdcard​- Format /system
- format /system​- Reboot into CWM (necessary for CWM to see the sdcard contents)
- +++++Go Back+++++​- advanced​- Reboot Recovery​- Copy the ROM to the sdcard (this is from the directory in which the ROM is located on your PC)
adb push ROM-sms-T959V-GB2.3.6-antsvx.1.0.3.zip /sdcard/​- Flash the ROM
- install zip from sdcard​- choose zip from sdcard​- ROM-sms-T959V-GB2.3.6-antsvx.1.0.3.zip​- Reboot & let it sit for ~10 minutes
Sorry for the lengthy post, but I wanted to ensure there was transparency in what I did.

stephen_w,
Seems that it's not framework-res.apk issue, it's not complaining about any certificates.
A lot of unknown permissions in the log, but it's OK, we've removed some of the system packages that grant those permissions but they do more harm than good in the end.
The crash has something to do with that: *** FATAL EXCEPTION IN SYSTEM PROCESS: PowerManagerService. Hm......
Question. If after loading the ROM you shut down completely (power off) first and then boot instead of rebooting right from CWM, will it still do the same?
Btw you don't have to clean everything that extensively. Just do factory reset to erase /data and flash. Dalvik and /cache are cleared but the installer, the /system is completely overwritten anyway.

Weird...it flashed fine for me with no wipe....
I did move on and never gave it a break in....but it did work
Sent from my SGH-T959V using xda premium

AntonX said:
stephen_w,
Question. If after loading the ROM you shut down completely (power off) first and then boot instead of rebooting right from CWM, will it still do the same?
Btw you don't have to clean everything that extensively. Just do factory reset to erase /data and flash. Dalvik and /cache are cleared but the installer, the /system is completely overwritten anyway.
Click to expand...
Click to collapse
I usually don't do it that extensively at all. I was writing a process for myself in case I wanted to really clean it out So this gave me a good excuse to test it. I was having some weirdness which prompted me to write the instructions for myself.
I haven't tried shutting it down after the install. I can certainly try that for you, if you like.

So its something to do with power management. That's weird. Is there something we did to our phones before that is causing the issue now?
Sent from my SGH-T959V using xda premium

Lawful123 said:
So its something to do with power management. That's weird. Is there something we did to our phones before that is causing the issue now?
Click to expand...
Click to collapse
Doubtful. Nothing I can think of, off-hand. I have to wait until later this afternoon/evening to reflash it and try powering off vs. rebooting from recovery. If you have the chance, please feel free and let us know what happens.

Link2SD completely messed up my phone

Alright guys I'm about to blow my top off here. The most recent Link2SD update completely messed up my entire phone.
For reference, I'm currently running an LG G3 D851 4.4.2, stock ROM and rooted. Everything was fine until recently when I started noticing a Play Store update app error "-110".
Not knowing what it was, I investigated, and found that my entire group of app installations have been completely screwed up.
1) First off, I can't install ANYTHING. No app, no nothing. I need to probably install an updated Link2SD to fix this nonsense...right? Can anyone direct me to how I would install the apk using ADB?
2) My mount script is broken and it's not working. It tells me "Mount script cannot be created. mount: Unknown error 150". As a result, my SD 2nd partition remains unmounted....which I think is the source of this entire problem.
3) Viewing my internal storage through DiskUsage, I've discovered that every single app I used to have installed has been "merged" into a single folder simply called "System data". Referenced through this photo here: http://i.imgur.com/ksukQGG.png . Instead of showing the individual folders, e.g.: Google Translate, Pocketcasts, etc, it just shows that big anonymous block of "System Data".
4) If I go to Settings -> Apps. Every single app shows up with "0.00b" as their app size.
HELPPPPP PLEASEEEE I will seriously monetarily tip someone if they can provide me with a solution to this.

crazylilazn said:
Alright guys I'm about to blow my top off here. The most recent Link2SD update completely messed up my entire phone.
For reference, I'm currently running an LG G3 D851 4.4.2, stock ROM and rooted. Everything was fine until recently when I started noticing a Play Store update app error "-110".
Not knowing what it was, I investigated, and found that my entire group of app installations have been completely screwed up.
1) First off, I can't install ANYTHING. No app, no nothing. I need to probably install an updated Link2SD to fix this nonsense...right? Can anyone direct me to how I would install the apk using ADB?
2) My mount script is broken and it's not working. It tells me "Mount script cannot be created. mount: Unknown error 150". As a result, my SD 2nd partition remains unmounted....which I think is the source of this entire problem.
3) Viewing my internal storage through DiskUsage, I've discovered that every single app I used to have installed has been "merged" into a single folder simply called "System data". Referenced through this photo here: http://i.imgur.com/ksukQGG.png . Instead of showing the individual folders, e.g.: Google Translate, Pocketcasts, etc, it just shows that big anonymous block of "System Data".
4) If I go to Settings -> Apps. Every single app shows up with "0.00b" as their app size.
HELPPPPP PLEASEEEE I will seriously monetarily tip someone if they can provide me with a solution to this.
Click to expand...
Click to collapse
Latest (free) Link2SD version
Latest Android Commander for Windows
Enable usb debugging in your phone's settings (Make sure you have the latest drivers for your phone installed)
Install Android Commander (AC)
Open AC while your device is connected
If your device is listed, press okay
On the right upper side in AC there is a option "Install"
Select the Link2SD APK (Try "update" if it doesn't work "normal insstallation"
Link2SD should be installed again

LS.xD said:
Latest (free) Link2SD version
Latest Android Commander for Windows
Enable usb debugging in your phone's settings (Make sure you have the latest drivers for your phone installed)
Install Android Commander (AC)
Open AC while your device is connected
If your device is listed, press okay
On the right upper side in AC there is a option "Install"
Select the Link2SD APK (Try "update" if it doesn't work "normal insstallation"
Link2SD should be installed again
Click to expand...
Click to collapse
Thank you so much for the detailed response. Unfortunately though, it looks like I already have the most recent version installed, 4.0.9? Would this solve anything by basically reinstalling it? I was hoping there would be like a 4.1 version that would fix the issue or revert changes or something.

Update:
Tried installing an app through ADB and it now shows me this:
WARNING: linker: app_process has text relocations. This is wasting memory and is a security risk. Please fix.
pkg: link2sd-4-0-8-multi-android.apk
Failure [INSTALL_FAILED_INTERNAL_ERROR]
Any idea anybody? Like before, I'd be willing to donate to anybody who can provide me with the solution. Thanks!

crazylilazn said:
Update:
Tried installing an app through ADB and it now shows me this:
WARNING: linker: app_process has text relocations. This is wasting memory and is a security risk. Please fix.
pkg: link2sd-4-0-8-multi-android.apk
Failure [INSTALL_FAILED_INTERNAL_ERROR]
Any idea anybody? Like before, I'd be willing to donate to anybody who can provide me with the solution. Thanks!
Click to expand...
Click to collapse
Seems as you have 4.0.8 at the moment. 4.0.9 is the latest official and released 03/10/2015. By the way (most) people here won't help more willingly if your offer some bucks

LS.xD said:
Seems as you have 4.0.8 at the moment. 4.0.9 is the latest official and released 03/10/2015. By the way (most) people here won't help more willingly if your offer some bucks
Click to expand...
Click to collapse
Oh, I was trying to downgrade Link2SD in hopes that it would fix whatever happened with 4.0.9.
According to the about page in Link2SD, I currently have 4.0.9.
And haha thanks for the heads up...I'm really desperate though which is why I pulled that card out.

crazylilazn said:
Oh, I was trying to downgrade Link2SD in hopes that it would fix whatever happened with 4.0.9.
According to the about page in Link2SD, I currently have 4.0.9.
And haha thanks for the heads up...I'm really desperate though which is why I pulled that card out.
Click to expand...
Click to collapse
Please fix.
pkg: link2sd-4-0-8-multi-android.apk
Click to expand...
Click to collapse
looks like 4.0.8. Thats why I asked. Have you tried to reinstall the app or does it offer an option to reload the mount script?

LS.xD said:
looks like 4.0.8. Thats why I asked. Have you tried to reinstall the app or does it offer an option to reload the mount script?
Click to expand...
Click to collapse
I can uninstall apps, but I can't install or update anything. That's why I was trying to install through adb instead, which unfortunately still doesn't work. When I open up Link2SD, it doesn't give me an option to reload, it only gives me the option to "Recreate mount scripts". If I click on it, it gives me the mount script error - "Mount script cannot be created. mount: Unknown error 150."

crazylilazn said:
I can uninstall apps, but I can't install or update anything. That's why I was trying to install through adb instead, which unfortunately still doesn't work. When I open up Link2SD, it doesn't give me an option to reload, it only gives me the option to "Recreate mount scripts". If I click on it, it gives me the mount script error - "Mount script cannot be created. mount: Unknown error 150."
Click to expand...
Click to collapse
Is there any really important data on your installed apps? If I was you I would simply reflash the firmware and start from scratch instead of spending hours to find a solution. The point is that you don't know what you changed that your phone became like this. I have send a email to the Link2SD developer but I'm not sure if he can provide a solution.

LS.xD said:
Is there any really important data on your installed apps? If I was you I would simply reflash the firmware and start from scratch instead of spending hours to find a solution. The point is that you don't know what you changed that your phone became like this. I have send a email to the Link2SD developer but I'm not sure if he can provide a solution.
Click to expand...
Click to collapse
I'm actually backing up all my app data as I'm typing this. The only concern I have though, is that my phone is actually on the stock recovery. I only rooted it because I didn't want to deal with the potential for something like this to happen (which would suck up all my time, haha). As a result, I can't flash anything. So if I decide to stock factory reset, would that clean the /system /data, and everything else that needs to be cleaned for my phone to work properly again? I thought that root (and potentially whatever screwed my phone) persisted through a stock factory reset, which would make trying to do that pointless.

crazylilazn said:
I'm actually backing up all my app data as I'm typing this. The only concern I have though, is that my phone is actually on the stock recovery. I only rooted it because I didn't want to deal with the potential for something like this to happen (which would suck up all my time, haha). As a result, I can't flash anything. So if I decide to stock factory reset, would that clean the /system /data, and everything else that needs to be cleaned for my phone to work properly again? I thought that root (and potentially whatever screwed my phone) persisted through a stock factory reset, which would make trying to do that pointless.
Click to expand...
Click to collapse
I really don't know, if your root survives a factory reset. Probably it will. A custom recovery is really usefull as you can make complete nandroid backups

LS.xD said:
I really don't know, if your root survives a factory reset. Probably it will. A custom recovery is really usefull as you can make complete nandroid backups
Click to expand...
Click to collapse
I suppose so, I'll have to make sure I can flash it properly though considering I'm finding it impossible to install apps right now. This is getting to be highly frustrating

crazylilazn said:
I suppose so, I'll have to make sure I can flash it properly though considering I'm finding it impossible to install apps right now. This is getting to be highly frustrating
Click to expand...
Click to collapse
Any progress here? Developer has answered my mail, but not offered any solution yet

LS.xD said:
Any progress here? Developer has answered my mail, but not offered any solution yet
Click to expand...
Click to collapse
Well, I solved the mount problem by formatting my SD card. But that didn't fix anything else unfortunately.
I also noticed a couple interesting things:
1) Android and Link2SD show my data and cache for ALL apps to be 0.00b. I know that's not true because I went to the /data/data/app directories and found the data exists.
2) I can use all my apps normally with no problem. that means all the files are there, and can communicate correctly(?)
3) I still can't install any app at all.
Next course of action: Completely disable link2sd's boot script perhaps? So what would that entail, deleting install-recovery.sh from /system/etc/ ? Anything else, or would that be good enough?

Uninstalled Updates to Android System Intelligence and Now Stuck in Infinite Boot?

Hi, I'm kinda at my wit's end with this problem that I'm currently facing and would very much appreciate some help. For some background, I'm on a Oneplus 7 Pro running stock firmware (OOS 11.0.7.1). I originally was planning on installing a Magisk module to spoof my device (Pixelify) to gain Pixel features. I noticed that one of the features was patching over the Android System Intelligence. It didn't work out the way I was expecting and I decided to uninstall the module. That went fine, but I wanted to make sure I was on the correct version of Android System Intelligence as well, so afterwards, I went into settings and "uninstalled all updates" to the app, which I assumed would have reset that particular app back to the version that originally shipped with the device.
Now, here's where the problem began. I restarted my device and I ended up sitting on the boot animation screen for over 20 mins. At that point, I knew something was wrong as it still hadn't booted into the system yet. I went into TWRP and decided to do a full reflash of the ROM (without wiping my data) and reflashed magisk as well. No luck either, still stuck at the infinite boot. So I went a step further and dirty flashed again without reinstalling magisk to see if it might have been any other modules not playing nice. Of course, that didn't work either and I'm still currently bootlooping. It's been going for the past 3 hours now...
In any case, would anyone have any suggestions on what I can do without doing a full wipe? I have access to TWRP and decrypting works fine. All of my files seem intact at the moment and from what I see, the ROM is has installed mostly fine, just something is causing it to hang during boot. Is there any way I can view the code running in the background during boot to see what's causing it to hang? Or maybe some other potential solution that I could try?

HunterBlade said:
Hi, I'm kinda at my wit's end with this problem that I'm currently facing and would very much appreciate some help. For some background, I'm on a Oneplus 7 Pro running stock firmware (OOS 11.0.7.1). I originally was planning on installing a Magisk module to spoof my device (Pixelify) to gain Pixel features. I noticed that one of the features was patching over the Android System Intelligence. It didn't work out the way I was expecting and I decided to uninstall the module. That went fine, but I wanted to make sure I was on the correct version of Android System Intelligence as well, so afterwards, I went into settings and "uninstalled all updates" to the app, which I assumed would have reset that particular app back to the version that originally shipped with the device.
Now, here's where the problem began. I restarted my device and I ended up sitting on the boot animation screen for over 20 mins. At that point, I knew something was wrong as it still hadn't booted into the system yet. I went into TWRP and decided to do a full reflash of the ROM (without wiping my data) and reflashed magisk as well. No luck either, still stuck at the infinite boot. So I went a step further and dirty flashed again without reinstalling magisk to see if it might have been any other modules not playing nice. Of course, that didn't work either and I'm still currently bootlooping. It's been going for the past 3 hours now...
In any case, would anyone have any suggestions on what I can do without doing a full wipe? I have access to TWRP and decrypting works fine. All of my files seem intact at the moment and from what I see, the ROM is has installed mostly fine, just something is causing it to hang during boot. Is there any way I can view the code running in the background during boot to see what's causing it to hang? Or maybe some other potential solution that I could try?
Click to expand...
Click to collapse
When you removed the magisk module and uninstalled the updates, did you boot into TWRP and wipe your cache and dalvik cache(but not factory reset or wipe data partition)? If you didn't wipe cache or dalvik, try booting into TWRP and wipe cache and dalvik cache(but DO NOT factory reset). To wipe cache and dalvik cache, boot into TWRP and sekect the Wipe option, then select "advanced wipes", you'll see a list of partitions, select only the cache and dalvik partitions(do not select any other partitions) then swipe the slider to initiate the wipe, when it finishes, reboot your device, it might take 10 or 20 minutes to boot because it has to rebuild the cache and dalvik cache with the new changes that you've made.
Generally, when making changes to the system partition, booting into recovery after making the changes and wiping cache is required in order for the device to load the system with the changes that were made instead of continiung to load cached data from before the changes were made, this tends to cause issues because the device is loading cached data that it can't use or understand anymore. Also, reflashing your ROM without wiping cache and dalvik cache would not solve this issue. You should do this any time you add/remove/modify/delete/uninstall/edit anything at all in the system partition, even if you only changed one tiny thing, you still need to boot into recovery then wipe cache and dalvik cache then reboot to apply the changes. This is not required when changing things in the user partition but it is absolutely vital that you do it when changing anything involved in the system partition.

Droidriven said:
When you removed the magisk module and uninstalled the updates, did you boot into TWRP and wipe your cache and dalvik cache(but not factory reset or wipe data partition)? If you didn't wipe cache or dalvik, try booting into TWRP and wipe cache and dalvik cache(but DO NOT factory reset). To wipe cache and dalvik cache, boot into TWRP and sekect the Wipe option, then select "advanced wipes", you'll see a list of partitions, select only the cache and dalvik partitions(do not select any other partitions) then swipe the slider to initiate the wipe, when it finishes, reboot your device, it might take 10 or 20 minutes to boot because it has to rebuild the cache and dalvik cache with the new changes that you've made.
Generally, when making changes to the system partition, booting into recovery after making the changes and wiping cache is required in order for the device to load the system with the changes that were made instead of continiung to load cached data from before the changes were made, this tends to cause issues because the device is loading cached data that it can't use or understand anymore. Also, reflashing your ROM without wiping cache and dalvik cache would not solve this issue. You should do this any time you add/remove/modify/delete/uninstall/edit anything at all in the system partition, even if you only changed one tiny thing, you still need to boot into recovery then wipe cache and dalvik cache then reboot to apply the changes. This is not required when changing things in the user partition but it is absolutely vital that you do it when changing anything involved in the system partition.
Click to expand...
Click to collapse
Thanks for the response! Unfortunately, I already wiped the dalvik cache after I reflashed my ROM yesterday and it didn't end up being able to boot. Since the OnePlus 7 Pro is an a/b device, there's no other cache partition to wipe.
I ended up leaving it to run on the boot animation screen until it ran out of battery (just to see what would happen). Besides for the phone becoming burning hot to the touch, it just stayed at that screen for another hour or 2 before it finally ran out of battery. This leads me to believe that it's definitely doing something in the background at that time, but just not sure what.
Edit: Just for some extra context, I also created a flashable zip of the latest OEM version of the Android System Intelligence APK and flashed it to system/app through twrp. Since I'm not able to boot to unlock my device, I thought this was the only way to install the app. In any case, it didn't make a difference either. Not sure if this means maybe the APK wasn't the issue or if this just didn't install the app the way I was expecting. No error codes when flashing the zip though.

HunterBlade said:
Thanks for the response! Unfortunately, I already wiped the dalvik cache after I reflashed my ROM yesterday and it didn't end up being able to boot. Since the OnePlus 7 Pro is an a/b device, there's no other cache partition to wipe.
I ended up leaving it to run on the boot animation screen until it ran out of battery (just to see what would happen). Besides for the phone becoming burning hot to the touch, it just stayed at that screen for another hour or 2 before it finally ran out of battery. This leads me to believe that it's definitely doing something in the background at that time, but just not sure what.
Edit: Just for some extra context, I also created a flashable zip of the latest OEM version of the Android System Intelligence APK and flashed it to system/app through twrp. Since I'm not able to boot to unlock my device, I thought this was the only way to install the app. In any case, it didn't make a difference either. Not sure if this means maybe the APK wasn't the issue or if this just didn't install the app the way I was expecting. No error codes when flashing the zip though.
Click to expand...
Click to collapse
Use TWRP to create a backup of your device in its current state, then try to extract the data from the backup, if the data is intact, it can be restored once you get the device working. If your data is intact in the backup, you can do a full system and data wipe via TWRP then reflash your ROM then restore the data that you want restored. This "should" get you back to where you want to be. Be careful, be certain of what you do at every step or you may end up losing data or not being able to get it to work while at the same time be able to keep your previous data.

Droidriven said:
Use TWRP to create a backup of your device in its current state, then try to extract the data from the backup, if the data is intact, it can be restored once you get the device working. If your data is intact in the backup, you can do a full system and data wipe via TWRP then reflash your ROM then restore the data that you want restored. This "should" get you back to where you want to be. Be careful, be certain of what you do at every step or you may end up losing data or not being able to get it to work while at the same time be able to keep your previous data.
Click to expand...
Click to collapse
Just finished backing up my data through TWRP and and did a full reformat of my device. After reflashing my ROM, I was back up and running! So thanks for the tip! However, after restoring the data partition, I realized that the issue was with the data partition specifically rather than on the system side as I had the same problem again. So I cleared the data partition again but kept data/media (internal storage) intact, and just like that, the device booted just fine this time.
Would you have any suggestions on what I could do to to troubleshoot the data partition? I have some important app info that I need to get the data back from.
Or if not, do you know how to capture logs from a failed boot?

HunterBlade said:
Just finished backing up my data through TWRP and and did a full reformat of my device. After reflashing my ROM, I was back up and running! So thanks for the tip! However, after restoring the data partition, I realized that the issue was with the data partition specifically rather than on the system side as I had the same problem again. So I cleared the data partition again but kept data/media (internal storage) intact, and just like that, the device booted just fine this time.
Would you have any suggestions on what I could do to to troubleshoot the data partition? I have some important app info that I need to get the data back from.
Or if not, do you know how to capture logs from a failed boot?
Click to expand...
Click to collapse
Logs from logcat do not persist through reboot. You need to look at your last_kmsg file, kmsg persists after reboot and it should capture the issue. If you have important app data, it should have been stored in data/media in your Android/(name of app) folder and your apps should be in data/data/app folder.
In the future, I recommend booting into TWRP and creating a backup before you make any kind of changes to your device, then, if the change causes an issue you can just boot into TWRP and restore the backup, this will put you back to what you had right before you made the change. Then you can troubleshoot what caused the issue and find a solution to how to apply your change without causing the issue again.

Droidriven said:
Logs from logcat do not persist through reboot. You need to look at your last_kmsg file, kmsg persists after reboot and it should capture the issue. If you have important app data, it should have been stored in data/media in your Android/(name of app) folder and your apps should be in data/data/app folder.
In the future, I recommend booting into TWRP and creating a backup before you make any kind of changes to your device, then, if the change causes an issue you can just boot into TWRP and restore the backup, this will put you back to what you had right before you made the change. Then you can troubleshoot what caused the issue and find a solution to how to apply your change without causing the issue again.
Click to expand...
Click to collapse
Yeah, lesson learned with that. I'm just glad I was able to backup my data in TWRP, which means I should theoretically be able to extract them back out again if I really need them. But back to the topic, I did check my last_kmsg file and it was unfortunately empty.
What I did do though was since I still have access to my recovery, I pushed my PC's adb keys to my device to be able to execute the command and grab a logcat during boot.
Could you by any chance take a look at the file (it's a onedrive preview link) to see if you might be able to notice the issue? I'm going into the territory of Googling everything and I was just completely lost when I looked at the file as I have no idea which errors actually matter and which ones don't. Thanks in advance!

HunterBlade said:
Yeah, lesson learned with that. I'm just glad I was able to backup my data in TWRP, which means I should theoretically be able to extract them back out again if I really need them. But back to the topic, I did check my last_kmsg file and it was unfortunately empty.
What I did do though was since I still have access to my recovery, I pushed my PC's adb keys to my device to be able to execute the command and grab a logcat during boot.
Could you by any chance take a look at the file (it's a onedrive preview link) to see if you might be able to notice the issue? I'm going into the territory of Googling everything and I was just completely lost when I looked at the file as I have no idea which errors actually matter and which ones don't. Thanks in advance.
Click to expand...
Click to collapse
Too many errors for me to volunteer my time to figure out.
All I can say is, at each line that reports an error, it states the error then lists the service(s) or app(s) that are involved in or effected by that error, everything listed after the error all the way down the list to the next error are related to that error.
Do a Google search for each error and the name of the package that immediately follows that error.

Droidriven said:
Too many errors for me to volunteer my time to figure out.
All I can say is, at each line that reports an error, it states the error then lists the service(s) or app(s) that are involved in or effected by that error, everything listed after the error all the way down the list to the next error are related to that error.
Do a Google search for each error and the name of the package that immediately follows that error.
Click to expand...
Click to collapse
No worries, totally understandable. I think Titanium Backup might actually be my saving grace, as it's able to read TWRP files as well. So all I have to do is run my backup through that and have it directly restore my data. In any case, appreciate the advice you've given so far!

you might probably found a fix but you're supposed to put the other os in the internal storage and not the micro sd card since it wont detect bootable drives just like on a pc and if u didnt install the os on the sd card then you can search for a boot unlocker which can unlock your phone from the infinite boot based on your phone and os
have a good day