Database Info

ROM Flashing Leftovers?

Has anyone else noticed leftover apps or info from your previous ROM that should not be in your current ROM? I am noticing this after the GB leak and the GB leaked based ROMs.
This is my process whenever I flash a ROM.
Boot into hboot and flash radio if neccessary.
Boot existing ROM and remove radio file from root of SD card.
Boot into recovery and clear data/factory reset. Wipe cache. Wipe Dalvik. Wipe battery stats. Fix permissions.
Flash ROM in recovery.
Flash kernel in recovery if neccessary.
(I don't use any type of app backup like Titanium or something like that. I just don't mind putting my apps back on because I don't have much to begin with.)
Now some examples, I flashed Teslacoil which I was running for about a week. It has a file manger app that I did not download. Then I flashed dhemke17's plain debloated GB ROM. The File Manager app remained in there which I thought was a little weird because he didn't say he was going to include it but I didn't pay much attention to it.
Then I flashed jcases GB ROM and played with it a little and noticed I couldn't lock GPS for the weather clock. Flashed back to dhemke's ROM and couldn't get a lock with the clock either but the first time it locked fine.
It seems like to me when flashing between other chef's roms it may be carrying over apps and/or info. This might be why we have been seeing extremes from both sides of some have been having great experiences and others it doesn't work for them at all.
Maybe flashing back to stock first before flashing to a new rom may he in order, I know we had to do that with some of the old skool winmo phones (remember those days?).
Anyhow, has anyone noticed these types of instances. Those of you who may be flashing to another's rom try to take notice and see if anything carries over.
Thanks gang!
And just to be sure, I do a wipe everytime I flash someone else's ROM.
Sent from my ADR6400L using Tapatalk

This also might be why some devs have been seeing their work in others Roms without being given credit.
Just guessing on this one.
Sent from my DROID PRO using Tapatalk

I also noticed, I don't like Sense so I normally change some of files to get a Sense-reduced experience from the GB Roms since we don't have a Senseless GB rom yet. I use Root Explorer to change the extension to .bak, when flashing the rom and doing this process for the new rom it would have the new file and still have the .bak file. So it would have like a Rosie.APK file and a Rosie.APK.bak file.
Sent from my DROID PRO using Tapatalk

I've also noticed something similar.. I also wipe on every install even updates to the rom i'm currently running. What I noticed is that after about five to ten minutes the wallpaper will change back to a custom one that I have saved on my sd card. Also when I turn on wifi it still remembers my password and connects to my network. to me if it isn't wiping these things it may not be wiping things that will conflict with any changes to my rom.
Now what I do is wipe data factory reset 3x, wipe cache, wipe davlick 2x, wipe battery stats ..thats clears out the issue I explained above.

To my knowledge that is just the built in restore Froyo has. You probably click to allow Google to store/backup your apps on setup, right?

Built in restore or you are not wiping.
Devs are seeing their work elsewhere because "devs" are asses.
Sent from my LG Revolution

jcase said:
Built in restore or you are not wiping.
Devs are seeing their work elsewhere because "devs" are asses.
Sent from my LG Revolution
Click to expand...
Click to collapse
OK so why am I seeing the .bak files when I change roms? It only does it from the rom right before it. Like I said I flashed from Tesla to dhemke and it had the file manager app. Then I flashed to your rom this was your first GB leak. It did not have the file manager but the weatherclock was not finding my current location. I flashed back to dhemke and this time there was no file manager app and weatherclock would not find current location. Flashed back to Tesla then back again to your rom jcase because you updated yours and file manager was there and weatherclock locked.
If the devs are being asses that's fine I was just throwing that out there, but I am sure our phones are not complete wiping when going from gb rom to gb rom. Like I said I wipe everything everytime because I don't have much crap to begin with and I am used to reinstalling my crap from the winmo days.
Try to flash and see if anything carries over.
And the wallpaper and wifi settings like others suggested is from your g account.
Sent from my ADR6400L using Tapatalk

This happens when you don't wipe and clear cache
Sent from my ADR6400L using XDA Premium App

Well I do wipe everything before each install via recovery. Read the first post for exact steps I take when flashing. When it boots it seems fresh, I have to resync my gmail account, download and install market apps, reinstall my apps that I sideload via sd card, etc. Just the apps that are in the core rom like in the system/apps folder are still there. I was just on chingys gingeritis version IV then flashed and wiped to version VI. On version IV I changed a few files to add .bak extension to get a senseless version like the Rosie.apk. After I flashed to version VI I went into system/apps and the .bak files were still there.
Again to my knowledge this is only happening with GB based roms. If I am wiping the wrong way please let me know that is why I posted my steps in the first post but that is how I wiped and flashed this whole time. The only thing I can think of is wiping, flash the rom, then wipe again. Or wipe via the settings menus.
Before someone flashes, could they try editing a core app in the system/apps folder with a .bak extension. Then wipe and install your ROM, and see if that .bak file is still there? Thank you.
Sent from my ADR6400L using Tapatalk

From looking at the updater-script file of the rom I flashed (1.13.605.7 Debloat/Deodex), it does a rm -rf /system
If your rom's updater-script file does not do that, then you should contact the head dev and ask them to add it in.
If it does have that, then there is definitely something going wrong to cause files to be left behind since that command is literally, "force recursive remove /system"
JM2c
P.S. BTW, wiping does not erase anything in /system. A rom that includes a file manager will have it in /system.
So the rom you flashed after the one with the file manager didn't erase /system before flashing its changes..

ICS installation for HTC Wildfire S

Cud anybody help me with the istallation procedure for the following link..
http://forum.xda-developers.com/showthread.php?t=1683874
Really confused here and wanna install ICS 4.0.4 for my phone :/

0. Make sure you're rooted
1. I think you also need s-off
1.5. Download the ROM file, and the Gapps file
2. Flash a custom recovery, such as ClockWorkMod. The easiest way is to download ROM Manager
3. Boot into that recovery. This can be done by using ROM Manager, or some device specific method (search it)
4. Make a backup (use the volume keys to navigate, select and back buttons are different for each phone, but should be easy to figure out)
5. Clear data/factory reset. OPTIONAL: under advanced clear dalvik cache
6. Install zip from SD card, navigate to the downloaded ROM, and select
7. Let it install, then install zip from SD card again, but this time select the google apps file
8. Reboot and enjoy! First bootup will always take longer than normal.
NOTE: since you do a factory reset, its a good idea to backup your apps with titanium backup, and various other things (like sms and mms) with mybackup root
This is the procedure for flashing any non-Sense (lol) ROM as well
Hope this helps!
Sent from my MB508 using xda premium

I really doubt the Wildfire S to be powerful enough to manage running ICS smoothly.
Anyway, good luck!

Rooting the phone is such a pain in the ass wid the bootloader requiring as many as 14-15 software's installed b4 it can work properly and also crashes everytime!!
gagdude said:
0. Make sure you're rooted
1. I think you also need s-off
1.5. Download the ROM file, and the Gapps file
2. Flash a custom recovery, such as ClockWorkMod. The easiest way is to download ROM Manager
3. Boot into that recovery. This can be done by using ROM Manager, or some device specific method (search it)
4. Make a backup (use the volume keys to navigate, select and back buttons are different for each phone, but should be easy to figure out)
5. Clear data/factory reset. OPTIONAL: under advanced clear dalvik cache
6. Install zip from SD card, navigate to the downloaded ROM, and select
7. Let it install, then install zip from SD card again, but this time select the google apps file
8. Reboot and enjoy! First bootup will always take longer than normal.
NOTE: since you do a factory reset, its a good idea to backup your apps with titanium backup, and various other things (like sms and mms) with mybackup root
This is the procedure for flashing any non-Sense (lol) ROM as well
Hope this helps!
Sent from my MB508 using xda premium
Click to expand...
Click to collapse

pavan shandilya said:
Rooting the phone is such a pain in the ass wid the bootloader requiring as many as 14-15 software's installed b4 it can work properly and also crashes everytime!!
Click to expand...
Click to collapse
Yeah man, the installation of the ROM is actually the easy and fun part
But good luck and if you need any help, you can post your questions in the respective threads. I'm sure you'll get lots of answers
Sent from my MB508 using xda premium

[Q] Upgrading to JB

I want to upgrade to JB custom ROM on TF101. I have seen a quite few. But I want to know which one is the best. Also please let me know do we need to download all the apps after upgrading the ROM. Is there a way to keep the apps intact after upgrading or reinstalling by taking back up. Downloading again will take a lot of data and a lot of time. Please help.

You can back up your apps with titanium backup onto an SD card or other external storage, but you must wipe the tablet when upgrading to JB, I recommend team eos nightlies with KAT kernel, they work very nicely.
You can also get the apk files from /system/app I think or /data/app and reinstall after putting those back on the tablet after wiping.

Shall you please let me know what is the purpose of KAT kernel
Thing O Doom said:
You can back up your apps with titanium backup onto an SD card or other external storage, but you must wipe the tablet when upgrading to JB, I recommend team eos nightlies with KAT kernel, they work very nicely.
You can also get the apk files from /system/app I think or /data/app and reinstall after putting those back on the tablet after wiping.
Click to expand...
Click to collapse

I'm running Revolver 4.2.1. What are the advantages going to JB from ICS? I'm going on a long trip soon, so I'm mainly looking for stability, battery performance and keyboard/dock compatibility.
Also, I'm reading that we need to install TWRP to run JB ROMs? Or can I still use CWM?
Thanks in advance!

tong143 said:
Shall you please let me know what is the purpose of KAT kernel
Click to expand...
Click to collapse
Lots of speed improvements over the stock kernel, fixes for different things like audio and gps
Grab the Kat-App too, that also boosts Audio and GPS
---------- Post added at 04:58 PM ---------- Previous post was at 04:53 PM ----------
needtoride said:
I'm running Revolver 4.2.1. What are the advantages going to JB from ICS? I'm going on a long trip soon, so I'm mainly looking for stability, battery performance and keyboard/dock compatibility.
Also, I'm reading that we need to install TWRP to run JB ROMs? Or can I still use CWM?
Thanks in advance!
Click to expand...
Click to collapse
Yes move to TWRP as soon as possible or risk bricking your TF as many have done trying to flash new ROMs with CWM
If you install Goo Manager you can easily install TWRP from the top right settings menu "Install OpenRecoveryScript"
Highly recommend TeamEOS4 and KatKernel in terms of everything you are looking for for your trip
Advantages over ICS are performance and stability and a new UI (Which is swappable with the ICS tablet version from settings in TeamEOS)

OK. I looked at some tutorials to get a sense of TWRP and Goo Manager. I know you can view and download ROMs from GM. So after downloading the ROM, boot into TWRP to install it? How about flashing kernels and the Kat app you referred to? Is that downloaded and installed in the same procedure?
Sent from my Infected HTC Incredible using Tapatalk 2

needtoride said:
OK. I looked at some tutorials to get a sense of TWRP and Goo Manager. I know you can view and download ROMs from GM. So after downloading the ROM, boot into TWRP to install it? How about flashing kernels and the Kat app you referred to? Is that downloaded and installed in the same procedure?
Sent from my Infected HTC Incredible using Tapatalk 2
Click to expand...
Click to collapse
Yep exactly the same as a ROM, I do it this way
For a ROM
Wipe Cache and Dalvik Cache and System
Install ROM
Wipe Cache and Dalvik Cache
---
For a Kernel
Wipe Cache and Dalvik Cache
Install Kernel
Wipe Cache and Dalvik Cache
---
For Gapps
Wipe Cache and Dalvik Cache
Install Gapps
Wipe Cache and Dalvik Cache
----
Basically Wipe Cache and Dalvik Cache between each flash and when your done, then reboot
For Kat App, its just an app, so wait until you're done with the above, boot into the ROM, get everything set up how you like it, then install the Kat App, its just an APK so you just use a file manager (ES File Explorer is my choice) and click it once to install it
Once in there, goto the Install section and install the GPS and Audio etc, the rest is pretty self explanatory, sections for Audio etc
EDIT - You don't have to use Goo Manager to download the ROMs or others either, sometimes its faster to use the PC and copy them over to the TF then reboot to recovery to flash them, you can use internal or external sdcards in TWRP, I have the links in my sig

EOS 4
I'll second the Team EOS 4 Recommendation

+1 for EOS4

Difficulty Installing Custom ROM

I'm having a lot of difficulty installing a new ROM on to my Sidekick 4G. I root my phone using SuperOneClick. After that, I downloaded Quick Boot, Root Browser, and ROM Manager. I use ROM Manager to get a custom recovery image through CWM. With Root Browser, I copy the Recovery file and paste it to /system/bin and overwrite the recovery file that's already in there. I use Quick Boot to reboot into Recovery. This is what I did when I went into Recovery.
1) Reinstall Packages (Stock Recovery)
2) Install zip from SD Card
3) Choose zip from SD Card
4) I picked whatever zip file had the custom ROM on it
After the installation, everything is fine. Its says its successful or completed. But when I reboot it, the screen is stuck on the screen where it says "T-Mobile Sidekick 4G". I've tried different ROMs and they've came out with the same outcome. And after I do install a ROM and fails, I have to go into Download Mode and unroot the phone again. Its getting a bit tedious and annoying.

You did it wrong
Reinstall packages (stock)
Factory reset/ wipe dalvik an cache
Mounts! Make sure system is unmounted
Then install zip
Reboot system
Sent from my SGH-T839 using xda app-developers app

Yes! It worked! Thanks for the help!

No problem
To install a different rom you have to install update (red) to (yellow) cwm must use yellow/orange to install new roms an just make sure you wipe everything an mounts
Ps back up your mobile (app)
An recovery an backup (just incase of malfuctions later on)
Sent from my SGH-T839 using xda app-developers app

immorality said:
No problem
To install a different rom you have to install update (red) to (yellow) cwm must use yellow/orange to install new roms an just make sure you wipe everything an mounts
Ps back up your mobile (app)
An recovery an backup (just incase of malfuctions later on)
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
why from red to yellow?

[Q] Which files should i keep in the "sd"??

My phones memory is almost full and i would like to delete everything from the virtual sd. But as far as i saw there are some strange files like "ADebugPath" or "Recovery-Tools", so i am a bit afraid of deleting everything.
I have s-off and rooted the phone because i wanted to flash cm11. So by deleting all the files from virtual sd i am afraid of deleting files that might affect adb or s-off. Is it going to be helpfull to send a print-screen of my files?
An other thought is that usually this type of files shouldn't be visible on sd but only on the root of the phone but i want to be 100% sure before doing anything.
Thanks a lot.

Nothing on the SD affects s-off, and pretty sure the same goes with adb. I don't know what that file is "ADebugPath", but I don't believe I have it and adb works fine.
In fact, there are folks on here that regularly format their SD (for instance, when they flash new ROMs) which if of course not mandatory, but just to "clean up shop".
The only things I would suggest you should keep on the SD are Titanium Backup files, and a known good nandroid. And possibly files for any apps (such as games). Other than that, everything can pretty much go.
You can always copy files to your computer before deleting them from the SD, in case you think you might want them later.

Shouldn't he mount via recovery and format? I was told that's the best way to format these integrated SD cards.
Sent from my HTC One X using Tapatalk

chrisb906 said:
Shouldn't he mount via recovery and format? I was told that's the best way to format these integrated SD cards.
Click to expand...
Click to collapse
You mean format using a computer, versus wipe in TWRP? I don't know if it would make much difference.
Or do you mean format, versus manually deleting selected files? I would guess from a technical standpoint a format is going to be better, to reduce fragments, etc. But the data is not written and read from the SD all that often (its not like its the OS memory), so in real world terms, I don't think it would make much difference.

I mean "mount USB storage" via recovery right click on it on PC and chose format
Sent from my HTC One X using Tapatalk

redpoint73 said:
Nothing on the SD affects s-off, and pretty sure the same goes with adb. I don't know what that file is "ADebugPath", but I don't believe I have it and adb works fine.
In fact, there are folks on here that regularly format their SD (for instance, when they flash new ROMs) which if of course not mandatory, but just to "clean up shop".
The only things I would suggest you should keep on the SD are Titanium Backup files, and a known good nandroid. And possibly files for any apps (such as games). Other than that, everything can pretty much go.
You can always copy files to your computer before deleting them from the SD, in case you think you might want them later.
Click to expand...
Click to collapse
I have already done a backup and copy everything to my pc (just in case) so i will format the sd card and after that i will put back for sure the backup and the titanium backup file. Thanks for you help i will let you know when i do the "cleaning" on my phone.
One more thing i changed the battery to a new one (of htc one x+) so do you know any programme that can test the mah just to check it is correctly recognized?

I wouldn't reinstall apps using TB. But that's your choice. I've run into nothing but probs using TB,but that could be just me
Sent from my HTC One X using Tapatalk

It's just you. Thousands of people, including me, have been using Titanium to backup and restore apps for years, that's why it's the single most popular and most used backup app for Android. If you're having problems with it, you're doing something wrong.
Sent from my Evita

Maybe my reasonings are cuz of all the system apps I restored.
Sent from my HTC One X using Tapatalk

Bad flashing has nothing to do with not being able to use Titanium.
Sent from my Evita

chrisb906 said:
I wouldn't reinstall apps using TB. But that's your choice. I've run into nothing but probs using TB,but that could be just me
Click to expand...
Click to collapse
I've restored apps and app data with Titanium countless times (every time I flash a ROM) on this device with no issue. Its migrating system data with Titanium that usually causes problems.

That is what I did. But I learned not to anymore. But I still don't use TB.
Sent from my HTC One X using Tapatalk

chrisb906 said:
Maybe my reasonings are cuz of all the bad flashing
Click to expand...
Click to collapse
Unless you have a definitive reason to blame Titanium, don't blame Titanium.
---------- Post added at 07:58 AM ---------- Previous post was at 07:54 AM ----------
chrisb906 said:
That is what I did. But I learned not to anymore. But I still don't use TB.
Click to expand...
Click to collapse
Its a well known issue that using Titanium to migrate system data does not work well. This is no surprise. You are trying to migrate OS specific data between different OS's, so obviously its not going to go well.
Titanium works perfectly to migrate apps and app data. If you want to make you life harder for no good reason, feel free. But others are going to be fine using the app properly.

Yea. Thanks. This was when I first started flashing Roms and modifying my device. But I learned
Sent from my HTC One X using Tapatalk

I did the format at the sd card throught the computer and i tried to flash the newest version of cm11 but i got an error.
So the format was ok and i deleted a lot of files without a problem. Does anyone know why i get this error. I had it one more before. After that i haven't manage to update the nightly! I tried to google it and i saw something strange like you have to go for an older version of your recovery!
So i decide to go for the PhilZ Touch as far i have read it is the best for cm11. But i still have the some error:
"E:Error executing updater binary in zip '/sdcard/cmupdater/cm-11-20140507-NIGHTLY-evita.zip'
Error flashing zip '/sdcard/cmupdater/cm-11-20140507-NIGHTLY-evita.zip'"
Any ideas why i get this error??
Thanks a lot.

If you read in the CM thread it says you need the latest TWRP recovery to flash the latest nightly.
Sent from my Evita

timmaaa said:
If you read in the CM thread it says you need the latest TWRP recovery to flash the latest nightly.
Sent from my Evita
Click to expand...
Click to collapse
As far as I read cm11 does not need any special recovery:
"Installation Instructions (These are all required)
S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
Update to 3.18 RUU or later.
Flash a custom recovery (TWRP/CWM with SELinux capabilities).
Download latest nightly from http://download.cyanogenmod.org/?device=evita.
Locate 4.4 Gapps via a quick Google search.
Wipe factory/data reset in recovery before installing CM11.0 (unless you are already on a CM11.0 build).
Reboot into recovery and install nightly and gapps.
can not flash if you have an old recovery but i saw that."
Ok but through reading, old version of CWM is fine. As far i have seen PhilZ Touch is the best CWM, most advanced and best choice for recovery (for cm11). That is what i use now....
Furthermore, before that i was using the unofficial recovery twrp-2.6.3.0 4.4. The latest one (until yesterday).
Can you please tell me where exactly did you see the thing about latest recovery??
So, i have to go for the "TWRP 2.7.0.8 Unofficial"????
Because to be honest i thought it is something else.... :/

What do you mean you thought it is something else? You need TWRP 2.7.0.8 to flash the latest nightly, that was reported pretty clearly.
Sent from my Evita