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 backupscd backupsmkdir efs nandroid sdcard- Backup /efs to your PC
cd efsadb pull /efs/- Backup /sdcard to your PC
cd ..\sdcardadb 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 ..\nandroidadb 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.
Related
Good morrning everybody.
Yesterday I tried to flash the circle battery found in ROM Manager into my Android 2.2 system. Clockwork Recovery suggested to run a backup, which I naturally did, and then it started to flash the battery into the system.
Until that point it worked fine and never returned an error or something else, but after the first reboot, the battery was properly replaced but nearly every app installed in my android crashes (googlemail, sms, phone, launcher pro, and so on) and my phone went into a boot loop.
Trying to restore my system with the Clockwork recovery manager also didn't work as it should, so I had to perform a full factory reset. (By the way, I got the same boot loop after trying to deinstall crapware via titanium backup)
My phone is a o2 - branded HTC Desire with Froyo, HBOOT-093.0001 and was rooted by unrevoked (S-ON).
Does anyone have an idea about that problem and know a solution? thanks in advance ;-)
cheers
PS: please forgive my when i wrote nonsense, it's 6 o'clock in the morning
Okay, I played a little bit around with my mobile phone and i figured something.
I made it to activate the plane mode before my phone decided to reboot again, so I managed to break this loop.
Now "only" "RSS-Reader, MMS, NewsReader, the Google Mail App, the "Google-Services-Framework (Prozess com.google.process.gapps)" and the Sense-Launcher crashes (maybe because I've a Mail shortcut or something on the screens, I don't know it exactly (using LauncherPro+)
I also read that flashing could set the ringtones to NULL (for the guys who aren't that deep into informatics: NULL = nothing; but NULL is not the number "0" (null-pointer-exception). I took a look into my settings but there are definitively ring tones set but unfortunately I can't take a look into my GMail app due to these crashes.
greetings
Cuupa
Try using Advanced -> Fix Permissions in CWM. It is supposed to help with FCs
Cuupa said:
Okay, I played a little bit around with my mobile phone and i figured something.
I made it to activate the plane mode before my phone decided to reboot again, so I managed to break this loop.
Now "only" "RSS-Reader, MMS, NewsReader, the Google Mail App, the "Google-Services-Framework (Prozess com.google.process.gapps)" and the Sense-Launcher crashes (maybe because I've a Mail shortcut or something on the screens, I don't know it exactly (using LauncherPro+)
I also read that flashing could set the ringtones to NULL (for the guys who aren't that deep into informatics: NULL = nothing; but NULL is not the number "0" (null-pointer-exception). I took a look into my settings but there are definitively ring tones set but unfortunately I can't take a look into my GMail app due to these crashes.
greetings
Cuupa
Click to expand...
Click to collapse
I had a similar issues on CM7 while the wrong gapps version was flashed :S
Hey guys, thanks for your reply.
@frosty_ice: from the CWM recovery menu (power + "vol-") I've only the options of
- reboot recovery
- wipe dalvik cache
- wipe battery stats
- report error
- key test
- restart adbd
- process dump
which are listed at "advanced"
When I select "fix permissions" in ROM Manager, it throws the error "Error while executing privileged commands" (translated from german, I don't know the original sentence)
I'm using ROM Manager v4.1.0.0
@metalron: I did not flashed any version of gapps, I only flashed the circle battery "SuperCircle Battery v.B" found at "Pinkolin - Pinky Desire". Does this automaticly flash other components into my system?
greetings
Cuupa said:
Hey guys, thanks for your reply.
@frosty_ice: from the CWM recovery menu (power + "vol-") I've only the options of
- reboot recovery
- wipe dalvik cache
- wipe battery stats
- report error
- key test
- restart adbd
- process dump
which are listed at "advanced"
When I select "fix permissions" in ROM Manager, it throws the error "Error while executing privileged commands" (translated from german, I don't know the original sentence)
I'm using ROM Manager v4.1.0.0
@metalron: I did not flashed any version of gapps, I only flashed the circle battery "SuperCircle Battery v.B" found at "Pinkolin - Pinky Desire". Does this automaticly flash other components into my system?
greetings
Click to expand...
Click to collapse
I think thats your issues, as far as I know you need gapps, that too the right version although most apps can be downloaded via market but then you need market and for some odd reason not flashing gapps or flashing the wrong one put me in a boot loop.. so im guessing its the same for you.
http://goo-inside.me/google-apps/
I have an LG Optimus V (Virgin Mobile) with 2.3.3 Gingerbread with aospcmod-ov-20110415-signed.zip running before becoming stuck in Android System Recovery. It happened when I tried updating the rom to aospcmod-ov-20110427. I had the proper gapps and follwed the flashing rom instructions from romrepo wiki. After that we lost clockworkmod recovery 3.0.0.6 . We then installed clockworkmod recovery 3.0.2.8 because it was the only one that would reinstall and it was recommended. Once it was installed no files from the sd card could be accessed so I removed clockworkmod recovery 3.0.2.8 . Once we removed cwm recovery 3.0.2.8 I was faced with the blue fastboot screen. To get out of the blue fastboot screen I had to use vm fastboot root. Once I did that I was able to go thru the full process of 1. Move all files you intend to flash to the root of your sd card (ex. aospCmod.zip, GAPPS.zip, kernel (optional)).
2. First you need to wipe/format your phone, in clockwork recovery: Wipe data/factory reset, wipe cache partition. Under Partitions menu (or Mounts & Storage in 3.0.0.6) in recovery: Format boot, system, data, cache. Under advanced: wipe Dalvik Cache.
3. Flash in this order:
A. AospCmod
B. GAPPS
C. Kernel (optional).
4. Reboot System
5. NOTE: On Optimus V when first logging in, if you click "Sign In" it will ask you to slide of your keyboard. Just go back and press "Skip." You can sign into your Accounts later in settings.
All of the processed went thru successfully and went to reboot and it rebooted back to Android System Recovery. I have checked my steps and tried this process continually but it keeps looping me back to Android System Recovery instead of loading the Rom.
Any suggestions would be greatly appreciated!
P.S. You can email me at [email protected]
So I'm using lfaber's Supercharged V5 ROM and I tried to add the Reboot option to the power menu (JRW's method).
I messed up when following the instructions, however. I downloaded the ZIP to my phone and then installed it from the SD card, but forgot to wipe the cache first like the instructions said. So I wiped the cache and then went back and installed the ZIP again.
When I booted back up, I got force close messages for what seemed to be all my apps. Is this because I messed up the instructions? And what should I do to fix it? Can I backup into SCV5 again like I did at first or should I go back to the stock deodexed 2.3.6?
Thanks in advance for any advice!
Usually it will force close because of an issue with signing, not because of cache wiping... try flashing the different 1% battery mods. (Don't forget to wipe cache partition and Dalvik Cache)
Sent from my MB865 using Tapatalk
I'm not able to get my computer to recognize that my phone is plugged in (I think I saw a 'usb' force close message as some point) and I can't access the XDA app or the internet with my phone. Any suggestion on how to get the ZIP onto my SD card so I can flash it?
mcm743 said:
I'm not able to get my computer to recognize that my phone is plugged in (I think I saw a 'usb' force close message as some point) and I can't access the XDA app or the internet with my phone. Any suggestion on how to get the ZIP onto my SD card so I can flash it?
Click to expand...
Click to collapse
Is everything force closing or are just Google/Motorola apps force closing? Just keep closing the notification windows until they stop.
There's three ways of getting the zip onto your SD card, two of which may not be possible...
-Use the Motorola "Phone Portal" app to "Connect with wifi" and transfer the zip from your computer to your phone via wifi.
-Use the browser to download the zip file and make sure you can find it on your sd card
-Use a microSD card reader to put the file on your sd card
However there's another thing you can do that should fix you up.
-Make a CWM backup
-Flash SCV5, then the update zip
-Use CWM to "advanced restore" "data".
This will fix you up on any system modifications but restore your apps/data.
I didn't have an sd card reader, so I just backed up my system, then backed up into SCV5 and flashed the update. Phone is running fine with no force close issues.
If I understood you correctly, what I need to do now is put a different 1% battery mod than the one included in the ROM and then flash the reboot option again?
I'm a little confused as to why the 1% battery mod is involved at all?
Also, restoring data via CWM didn't seem to bring back my home screen setup. Would I need to restore system in CWM for that? I'm guessing if I did that my force close issue would just come back though, right?
Thanks again for all your help.
mcm743 said:
I didn't have an sd card reader, so I just backed up my system, then backed up into SCV5 and flashed the update. Phone is running fine with no force close issues.
If I understood you correctly, what I need to do now is put a different 1% battery mod than the one included in the ROM and then flash the reboot option again?
I'm a little confused as to why the 1% battery mod is involved at all?
Also, restoring data via CWM didn't seem to bring back my home screen setup. Would I need to restore system in CWM for that? I'm guessing if I did that my force close issue would just come back though, right?
Thanks again for all your help.
Click to expand...
Click to collapse
Restoring a CWM data backup should bring back your homescreen setup, as it restores the entire /data folder... Interesting. Don't restore system otherwise your problems will comeback
Very strange, shouldn't be nothing with the reboot.zip that would affect any of that unless you got a bad download?
farshad525hou said:
Restoring a CWM data backup should bring back your homescreen setup, as it restores the entire /data folder... Interesting. Don't restore system otherwise your problems will comeback
Click to expand...
Click to collapse
Yea, I got an error when I backed up through CWM, but it was just generic. I was more worried about having the phone working at that point than having everything backed up, so I didn't worry about.
JRW 28 said:
Very strange, shouldn't be nothing with the reboot.zip that would affect any of that unless you got a bad download?
Click to expand...
Click to collapse
Are you saying that you don't think flashing a different 1% mod would allow me to flash the reboot.zip without getting those force close errors again?
Thanks guys.
mcm743 said:
Are you saying that you don't think flashing a different 1% mod would allow me to flash the reboot.zip without getting those force close errors again?
Thanks guys.
Click to expand...
Click to collapse
Not at all. When I first released the reboot.zip it worked fine with V5 but I have always run my 1% vertical mod and when I flashed it I lost the ability to reboot with the power menu. So I then went back and modified all of my 1% battery mods to work correctly with my reboot.zip. you should have zero problems with them as long as they are mine or the one that comes with V5. I have not had a chance to test with anything on 2.3.5 yet though
The reason I first recommend you to flash a different 1% battery mod was because it re-writes any system files that the first flash may have messed up. Now that you're up and running again you don't need to do anything else.
It's odd that your homescreen configuration wasn't saved... what launcher do you use?
cogeary said:
The reason I first recommend you to flash a different 1% battery mod was because it re-writes any system files that the first flash may have messed up. Now that you're up and running again you don't need to do anything else.
It's odd that your homescreen configuration wasn't saved... what launcher do you use?
Click to expand...
Click to collapse
I use the one that comes with SCV5, Go Launcher. I was able to restore the home screen directly from the Go Launcher app. So at this point, I'm up and running, but I still don't have the reboot option. Should I just backup as is (with SCV5.1) and try flashing the reboot option again the same way I did before? I would just seem weird if I just did the same thing again, because why I wouldn't just have that same force close issue like the first time?
mcm743 said:
I use the one that comes with SCV5, Go Launcher. I was able to restore the home screen directly from the Go Launcher app. So at this point, I'm up and running, but I still don't have the reboot option. Should I just backup as is (with SCV5.1) and try flashing the reboot option again the same way I did before? I would just seem weird if I just did the same thing again, because why I wouldn't just have that same force close issue like the first time?
Click to expand...
Click to collapse
Sure, backup and try flashing reboot again. But this time redownload the zip first.
cogeary said:
Sure, backup and try flashing reboot again. But this time redownload the zip first.
Click to expand...
Click to collapse
I second that. Do a CWM backup then redownload the mod, and flash it. The download may have been corrupted last time around.
farshad525hou said:
I second that. Do a CWM backup then redownload the mod, and flash it. The download may have been corrupted last time around.
Click to expand...
Click to collapse
Running the backup now. I will let you know how it goes and I'll make sure to do a fresh download. Thanks.
Edit: this worked perfect. I realized when I did the download again that originally downloaded via the QR code, so maybe there's something wrong with that? Or something wrong with my phones QR code reader? I used Goggles.
Thanks again!
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
Updated: 03/24/2015
Hi all,
I did this mostly for practice but I thought it might be helpful so I went ahead and posted.
Stock LG D850 20f ROM
[*]Rooted/SuperSu
[*]Most bloat removed
[*]Oversharpening fix
[*]Flashable zip
[*]init.d support*
[*]CarrierIQ Remover*
*Init.d support is implemented in ROM only, not the kernel. CarrierIQ is removed automatically after first boot via an init script. Say thanks to @skeevydude for his help in getting this done. I shouldn't say "help", he pretty much did it!
Installation
Flash the Lollipop modem - see @autoprime 's thread here for modem zip
Flash the ROM zip
Wipe cache and dalvik (and in some cases data) if coming from a different ROM
Download
v3* - https://www.androidfilehost.com/?fid=95916177934548695
[QRCODE]https://www.androidfilehost.com/?fid=95916177934548695[/QRCODE]
*No change at all to the ROM itself since v2, I just realized that I've been forgetting to zero out the free space on the image file before uploading, which saves about 600 MB when zipped. New flashable zip is about 1.1 GB instead of 1.7 GB.
Older versions:
v1 - https://www.androidfilehost.com/?fid=95916177934543883
Apps Removed
/system/app:
Google Books
Google Chrome
Google Cloud Print
Google Drive
Facebook
Hangouts
Google Newsstand
Google Play Games
Google Play Music
Google Play Movies and TV
Google Plus
Twitter
/system/priv-app:
ATT Address Book
ATT Caller Name ID
ATT DriveMode
ATT Games
ATT Locker
ATT Lookout
ATT Mobile Locate
ATT Remote Support
ATT Smart Wifi
ATT Mobile TV
ISIS Wallet
ATT Visual Voicemail
MLT (LG tracker)
/system/vendor/app:
Amazon Kindle
ATT Family Map
ATT Home
ATT Keeper
ATT MHS Launcher
ATT Navigator
Uber
DeviceHelp
myATT
YP Mobile
ATT Apps
In case you want some of the ATT apps back, I have uploaded a zip here with those apps. This is NOT a flashable zip. You have a couple of options:
1. You may be able to install these as a normal (user) app by just pulling out the apk and installing the usual way.
2. If that doesn't work as expected, copy the app folder from the zip into the appropriate system folder as listed in the "Apps Removed" section.
Download: ATT Apps
Xposed Info
cmulk said:
Xposed has a couple of bad side effects at this point, so before doing anything you need to use Titanium or something similar to Freeze (this basically what the "helper" does):
LGSmartCover
Weather
Weather Theme
WeatherPlatform
Then you can install xposed as in the thread here: http://forum.xda-developers.com/showthread.php?t=3034811
However, there is still one more bug to keep in mind: Xposed will crash the Tethering and Networks menu. There is no fix for that yet, but as a workaround you can download some apps from the play store (like Mobile Network Settings), to shortcut around the menu that force closes.
Click to expand...
Click to collapse
Credits
@autoprime - Flashable zips, bump'd boot.img, and very clear instructions in his thread here
@timmytim - uploading the lollipop stock images (although I know a lot of others were working on that too)
@Skin1980 - Oversharpening fix
@skeevydude - init.d support and carrierIQ remover
CarrierIQ Removal
CarrierIQ has now been removed!
The removal is done via an init script that runs at boot to disable the IQ service before removing the files in order to prevent a force close. However, if you have to wipe data/factory reset without re-flashing the ROM, you will get a force close on the first boot. The good news is that I've tested this scenario and it should fix itself if you just wait about 20 seconds. In other words, the mentioned script does it's thing to stop the service to fix the force close and you are good to go after that.
Old info below:
cmulk said:
On the 20f lollipop rom (either mine or stock, there's no difference) either freezing LADDM or removing the libraries and LADDM as you mention will cause a force close unless you disable the "IQService" first, which is built into the framework-res.apk. I have repeated it multiple times and it has been discussed quite a bit in the Lounge and other threads. Disabling the service is easy for users to do with the "DisableService" app, and then you can remove LADDM and the libraries as mentioned. The difficulty is that disabling a service is a user setting, so, for example, if I reflash my ROM without the IQ files onto a phone with clean /data, I will again get the force close and an unusable ROM.
Click to expand...
Click to collapse
Manual Steps
In the meantime, here is how users can manually disable CarrierIQ. I take no credit for this method, it is posted in several places by several people, I'm just putting it here for convenience:
YOU MUST DO THIS IN ORDER (or at least the first few steps)
1. Download the "DisableService" app from the play store
2. In the DisableService app, go to System -> Android System and disable the "IQService" service
3. Use a root explorer to delete the folder /system/app/LADDM
4. Use a root explorer to delete /system/lib/libiq_client.so and /system/lib/libiq_service.so
5. (Optional) Uninstall DisableService
Remember, disabling the service is a user setting, so if you need to wipe /data for some reason, you will need to re-flash the ROM (which has the CarrierIQ files included) or else you will get a constant force close when your phone boots.
I'll give it a try, thanks
Flashing now. Will report.
I will be watching this ROM. Thanks for posting.
Exactly what does " if coming from a different ROM" mean? I'm on 4.4.2 10f Wulf (stock - rooted) ROM
JeffDC said:
I will be watching this ROM. Thanks for posting.
Exactly what does " if coming from a different ROM" mean? I'm on 4.4.2 10f Wulf (stock - rooted) ROM
Click to expand...
Click to collapse
Just clean flash to save yourself a hassle
2SHAYNEZ
Thanks for your work. I wish I had some skill in this realm. It'd be nice to pick and choose which apps you wanted removed. I prefer the stock ATT Visual Voicemail app over the one in the Play Store as its more reliable. I also use some of the Google Apps that are removed here as well. But great job in getting something debloated out there.
Sent from my LG-D850 using Tapatalk
Flashing lollipop Issues
Thanks for your work.... When flashing the 2 lollipop roms, 9 out of 10 times I get just a screen with icons, no wallpaper, no notification pull down no buttons at the bottom. I flash the modem the rom then SU and clear cache. I have only got the other ROM to flash successfully once. The same is going on with this ROM, is this happening to anyone else. I flashed it 5 times with the same results, would anyone know why this is happening, seems others dont have this issue. Thank you again for bringing us a debloated Lollipop rom.
shayneflashindaily said:
Just clean flash to save yourself a hassle
2SHAYNEZ
Click to expand...
Click to collapse
Here is what I understand for a clean flash:
"1. Boot into Recovery
2. Make a Nandroid backup
3. Wipe data/factory reset
4. Wipe cache partition
5. Wipe Dalvik Cache
6. Flash ROM
7. DO NOT REBOOT – STAY IN RECOVERY
8. Select backup and restore
9. Select advanced restore
10. Select the Nandroid backup you made above
11. Select Restore data
12. Select Yes – Restore data
13. WAIT!
14. REBOOT"
What I do not understand is step 8, which selects the backup made in step two... and then flashing the backup over the (new) ROM flash in step 6. Wouldn't that overwrite the new ROM you just flashed?
JeffDC said:
Here is what I understand for a clean flash:
"1. Boot into Recovery
2. Make a Nandroid backup
3. Wipe data/factory reset
4. Wipe cache partition
5. Wipe Dalvik Cache
6. Flash ROM
7. DO NOT REBOOT – STAY IN RECOVERY
8. Select backup and restore
9. Select advanced restore
10. Select the Nandroid backup you made above
11. Select Restore data
12. Select Yes – Restore data
13. WAIT!
14. REBOOT"
What I do not understand is step 8, which selects the backup made in step two... and then flashing the backup over the (new) ROM flash in step 6. Wouldn't that overwrite the new ROM you just flashed?
Click to expand...
Click to collapse
I always do a clean flash.. dont need to back up and restore and still get bad results.
louvass said:
I always do a clean flash.. dont need to back up and restore and still get bad results.
Click to expand...
Click to collapse
That's not encouraging.
louvass said:
Thanks for your work.... When flashing the 2 lollipop roms, 9 out of 10 times I get just a screen with icons, no wallpaper, no notification pull down no buttons at the bottom. I flash the modem the rom then SU and clear cache. I have only got the other ROM to flash successfully once. The same is going on with this ROM, is this happening to anyone else. I flashed it 5 times with the same results, would anyone know why this is happening, seems others dont have this issue. Thank you again for bringing us a debloated Lollipop rom.
Click to expand...
Click to collapse
I have not seen that issue, but in case you are not clearing data you may need to try clearing dalvik cache.
Also, (and this is just a shot in the dark) you could try formatting system before doing anything else just in case something strange is left behind there.
JeffDC said:
That's not encouraging.
Click to expand...
Click to collapse
You can try dirty flashing first without losing any of your data.
1. Back up your current Boot and System
2. Back up your current modem (if you're coming from the Kitkat modem), or just download a flashable KK modem already posted on XDA
3. Flash the modem and ROM in this post
4. Wipe cache and dalvik
5. See if it works
If it's not working, then you will need to restore your boot, system, and modem to go back to your original kitkat setup without losing data.
Otherwise, you'll have to backup with Titanium and do a clean flash (wipe data) as already mentioned. Using Titanium makes clean flashing not so bad
I do clear Wipe cache and dalvik I wipe everything and it boots back into a desktop and thats it no notification, the same thing happened with the first lollipop.. but after 10 flashes it finally took... so I thought Id try your de-bloated and the same thing is happening again, not sure why this is. I can jump back to kk after flashing the modem without issues. Thank you again for your work.
Pdj7969 said:
Thanks for your work. I wish I had some skill in this realm. It'd be nice to pick and choose which apps you wanted removed. I prefer the stock ATT Visual Voicemail app over the one in the Play Store as its more reliable. I also use some of the Google Apps that are removed here as well. But great job in getting something debloated out there.
Click to expand...
Click to collapse
I agree that I use most or all of these Google apps as well. However, they update so often anyway that I prefer to just have them as user apps (otherwise you end up with 2 copies - the old static version in the system apps folder, and the updated version in the user apps folder).
As for the visual voicemail, I have posted the ATT apps in a zip in the OP. Visual voicemail is in the VVM_ATT folder.
Thanks!
cmulk,
Would you please clarify post 5 and 9 questions?
JeffDC said:
cmulk,
Would you please clarify post 5 and 9 questions?
Click to expand...
Click to collapse
Sure thing! That's actually what I meant to do in post 13. I am not sure if you can flash over 10f without wiping data, but you could give it a try without losing anything (except time) if you look at post 13.
You should clear cache and dalvik mostly any time you are flashing, unless you are just flashing over another stock 20f ROM.
louvass said:
I do clear Wipe cache and dalvik I wipe everything and it boots back into a desktop and thats it no notification, the same thing happened with the first lollipop.. but after 10 flashes it finally took... so I thought Id try your de-bloated and the same thing is happening again, not sure why this is. I can jump back to kk after flashing the modem without issues. Thank you again for your work.
Click to expand...
Click to collapse
Have you tried formatting /system before doing anything else? I'm not sure that will make any difference, but just for process of elimination at least
cmulk said:
Have you tried formatting /system before doing anything else? I'm not sure that will make any difference, but just for process of elimination at least
Click to expand...
Click to collapse
Thanks I do clear everything but my external mem.
Ever since flashing this I'm getting "no sd card" messages every time I try to download anything ( I don't have an external sd card) but it's never been a problem before. I've restored a backup of my stock Tim and the problem followed me after full wipes.
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