yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] :
Thanks for this, Gizmo! I've been having some strange problems with my phoen, and I'm interested in doing a full restore, from the beginning, like you suggested. I know this is probably discussed elsewhere, but what is your opinion of restoring apps/data using Titanium? Do you think this causes problems? It's so easy to just backup/restore all user apps AND data, but is this safe? Thanks for your help!
[Fascinate Android Development] GizmoDroid:
I use Titanium Backup regularly with no problem. However, I only usually restore data on user installed applications, and not on system applications.

But it probably works fine for those too.
[Fascinate Android Development] GizmoDroid:
Did you download the CWM package from this thread? The first version the JT posted on 3/29 had this problem.
[Fascinate Android Development] s44:
I think it's still not mounting dbdata by default. Mounting it manually before fixing permissions works.
[Fascinate Android Development] GizmoDroid:
The script is supposed to auto-mount it.

Let me make sure JT got my commits in there properly.

My changes included mounting /data and /dbdata before running the script, and then also verifying they are correctly mounted (and mounting if not mounted) inside of the script, for redundancy.

EDIT: *Facepalm* He missed one. Sorry guys for the troubles. I'll be posting new fies as soon as I talk to JT. He missed the menu one, and the one in the fix_permissions script is going to be modified to make sure this doesn't happen under any circumstance.
[Fascinate Android Development] Cythrawl:
Will this CWM update work on the Mesmerize too ? (I dont see why it shouldnt myself TBH)
[Fascinate Android Development] blackmamba0730:
very well written explanation. this will definitely help a lot of people (myself included :P)
[Fascinate Android Development] Jeff194:
Yup, this thread.

Edit: sorry I didn't see your update.
[Fascinate Android Development] minmongoblin:
Is that EB01 rooted? AKA would Odin'ing that .tar unroot my phone?
[Fascinate Android Development] Stilefish:
Sooooo, i just flashed over my existing jt1134's built from scratch kernel. Had some strange behavior, so I wiped cache(s), reflashed kernel and rom and everything seems okay.... Think I'm hosed or am i going to be okay....
[Fascinate Android Development] GizmoDroid:
There seems to be some weirdness in the way that CWM is interacting with the changes between the project voodoo files and JT's initramfs and how they are interacting with CWM.

Everything seems to work fine if you are starting from a clean Stock Odin flash, but upgrading a current install can cause issues.

Looking into it.
[Fascinate Android Development] JoeDat:
Its the full stock rom, factory, unrooted. But, by flashing the updated clockwork kernel, you regain access to flash a pre-rooted rom (ie, super clean). Giz's instructions will get you from anywhere to superclean 2.9.2 with the latest cwm fixes. Trust me, its worth following the whole process if ya can.
[Fascinate Android Development] minmongoblin:
Thanks JoeDat! I will follow them tomorrow.
[Fascinate Android Development] robertf57:
Are we there yet?

Please update us when you have the new files up and I'll flash again.

Thanks again for all the hard work.
[Fascinate Android Development] mzrdisi:
I don't think Koush has a Fascinate, and that is partly the reason why there has been not much work on his side. (afaik)
[Fascinate Android Development] djp952:
GizmoDroid ... while you're looking into the problems, do you think it would be possible to add an Advanced option for "Power Off"? I think it would be a nice addition to the fixed battery stats clear, in that you could clear stats and then power off to allow the battery to charge to 100% again before booting and creating a new stats file.

There is also one more thing that I was planning on looking into myself, but you/jt1134 would be *far* better equipped to do so (I still have trouble extracting the initramfs.cpio - lol) .... ODIN-based flashes that include dbdata.rfs/movinand.rfs(?) like the ones created by DroidXCon for SuperClean rely upon the stock blue recovery to do a data wipe on first boot, which this CWM appears to completely break. Is there a possibility of forking the CWM into 2 versions, one that auto-starts and one that you have to fake-flash through the stock recovery? (and if this becomes "yes", I've noted that the EB01 leak recovery.bin has a newer/different recovery than the one that was in fake-flash CWM 2.5.x.x, perhaps it might be worth extracting and including ... again, if the request is feasable in the first place)

Thank you so much for your hard work!!!
[Fascinate Android Development] Mesmerizeuser:
Make that 2 people who are curious about this.

I assume (though I know how dangerous that can be) that worst case scenario, all that would be required to fix it if it didn't work would be to reflash via odin. If this is the case, I'll give it a try and post results.

Sent from my voodoo froyo Mesmerize
[Fascinate Android Development] mzrdisi:
Followed instructions to the T and I'm currently being serenaded by the sexy robot voice.
[Fascinate Android Development] s44:
While you're at it, how about an incremented version number? ;)
[Fascinate Android Development] mrjake1970:
question :

does it make a difference what version of odin i use? i have been using 1.3

Samsung Fascinate

SuperClean 2.9.2 & 3/30 -50 Voodoo

Nitro Vivid 1.0 Theme

Member of Android Anonymous, as a recovering Android bricking addict. I have been brick free for over 30 days.
[Fascinate Android Development] scarfman4:
L

I tried restoring the stock Odin EB01 rom in the past with 1.7 and it wouldn't show the progress bar on the download screen of the phone and it kept getting stuck on factoryrs. Using 1.3 has no problems flashing. So I'd say probably yes it does make a difference.
[Fascinate Android Development] johntinman:
Gizmo, since I followed your instructions, I no longer have the screen responsiveness issues that have plagued some of us unlucky few. I have ODIN'd before, but never checked Repartion while doing so,as described in your OP. Could checking that have solved my problem?

Sent from my Bedazzled Fascinate
[Fascinate Android Development] sunder74:
Where is the link to the proper pit file? Im coming from stock deodexed bloated eb01. The one i found was for going back to stock 2.1
[Fascinate Android Development] neh4pres:
Look through these comments.. You will see someone posted a link

Sent from my Rocking dj05, themed superdark w/o swype mod, voodoo 5, with custom boot and shutdown.. With premium xda app.
[Fascinate Android Development] sfd0124:
The pit file is in original superclean thread in the repair from 2.7 section
[Fascinate Android Development] sunder74:
Yup got it. Thanks.
[Fascinate Android Development] landshark68:
I was having no problems with my set up at all.......or so I thought. I just went through the whole process, and now my phone is working incredibly better. Smoother, faster, more responsive. Used to be every time I rebooted my phone my Launcher Pro was basically "stuck" for lack of a better term. There would be an orange halo around my Google maps icon and I couldn't scroll between my homescreens, couldn't open my app drawer, couldn't open anything until I long pressed the home button, opened task manager, and ended Launcher Pro. Also after flashing a new ROM I used to always have to go into Root Explorer and delete the fede.launcher.com files before I could get the 3D app drawer in LP to stick. Now, no problem. Also used to have to change the contacts icon in my dock in order to be able to use the back button to get out of contacts. Not now. I just rebooted my phone twice, and none of these issues appeared. I would highly recommend everyone follow GizmoDroid's instructions to the letter. You won't be sorry.
[Fascinate Android Development] drnihili:
Having an odd issue were my phone sometimes won't turn on after flashing the roms from the OP.

Started on stock EA28, rooted. I installed CWM from the OP via Odin. Booted to CWM then wiped data/cache/dalvik each twice, then flashed zip from sdcard (voodo version from OP). Enabled lagfix in CWM, then booted to make sure everything worked. After that I added apps back one at a time from Titanium.

The phone works fine most of the time except for battery draining quickly (I haven't worked through the standard fixes for that yet) but if I leave it sitting for a while (~15-20 mins) then it no longer responds to the power on button. In that state it doesn't even respond to being plugged in. If I pop the battery out for a second, it will boot fine afterward until I leave it sitting too long again. I was not having this issue in stock EA28.

Ideas?
[Fascinate Android Development] GizmoDroid:
My first idea is that starting from stock EA28 might be the source of your issue. If you chose to start with the EB01 full Odin package, then installed superclean with only wiping cache/dalvik-cache (like the directions in the OP), you might see this problem fixed.

A lot of people have seen the problem you have had. It's nickname is "Sleep of Death" or SOD.

If you'd like to redo your phone using the directions in the OP, and report back on whether or not that fixed the issue, I think this would help confirm that the Sleep of Death issue does have a solution.
[Fascinate Android Development] jbjarko:
What apps have you restored? I had sleep of death, but no more. It was attributed to Youmail for me.
[Fascinate Android Development] drnihili:
Ah, I searched for "won't turn on" and didn't get anything. I'll look around for sleep of death. Thanks.

I'll give the OP instructions a try when I get a chance. In the meantime, why would it make a difference where I'm starting from? One would think that the end state was all that mattered. Are there things that EB01 overwrites that SC 2.9.2 does not? I don't mean this as an argument against your advice, I just like to understand the basis for why we do various steps rather than merely following a list.
[Fascinate Android Development] drnihili:
No Youmail here. Let's see, .... Backcountry Navigator, PowerAmp, Reversi, Backgammon, ADW Launcher, buzzbox, Gdocs, Bubble, Fancy Widget, Home Switcher, XDA, Circle Launcher, and Colorize Widget.

It doesn't seem to get SOD if I leave it plugged in, only if I leave it sitting while unplugged.
[Fascinate Android Development] scarfman4:
I followed the same steps from stock EA28. I rooted using FascinateRoot_v2, then installed CWM via Odin, then installed Superclean via .zip and so far everything is working fine.

Sent from my Fascinate

Superclean 2.9.1

EC10 voodoo kernel

EA28 radio
[Fascinate Android Development] drnihili:
Same path I followed, did you restore anything from Titanium Backup?

Whatever the cause of SOD, it is to some extent dependent on specific phones. After doing a bit of reading, it seems likely that two phones could follow identical processes and one would experience the SOD while the other would not. We tend to think of our phones as exact physical duplicates, but they aren't really.

That said, some ROMS are more prone to SOD than others. I wonder if perhaps the reason we haven't seen an official VZW froyo is that they're having trouble tracking down a similar issue.

BTW, do I need to disable lagfix if I'm going to ODIN the EB01 full package with the pit file? I'll do it if nobody says otherwise before I get there, but I'm still curious whether it's needed when I'm redoing the whole phone.
[Fascinate Android Development] neh4pres:
if you restore anything do not restore data! and for the things you must restore data too the very selective.

Sent from my Rocking dj05, themed superdark w/o swype mod, voodoo 5, with custom boot and shutdown.. With premium xda app.
[Fascinate Android Development] drnihili:
Ok, went through the OP steps. Haven't restored anything at all from TiB. No SOD yet, but it's only been 20 mins or so.

Market doesn't seem to be recognizing my paid apps. I've got the same accounts in the phone, checked email and such. I'm guessing it's just being slow in synching up? I'm willing to re-dl everything to avoid the SOD, but I would like my paid apps back. ;) I'll check back in after I've had more time with it.
[Fascinate Android Development] scarfman4:
Are you using Superclean 2.9.2 and waiting for them to come down from Google? Adryn disabled that feature. You will need 2.9.1 or older to sync apps.

Sent from my Fascinate

Superclean 2.9.1

EC10 voodoo kernel

EA28 radio
[Fascinate Android Development] drnihili:
Well, I'm not just waiting, I'm actively trying to download them. Went to the online store and told it to send to the phone. Did he disable all ability to track the paid app info? If so, why? Adryn is no fool, so there must be some reason, but it danged inconvenient from this end.
[Fascinate Android Development] scarfman4:
Over the course of the SC history many people were getting Force Closes after restoring apps I believe. Since most restore from Titanium Backup he decided to remove that ability to reduce the FCs. Most likely that ability will not be restored in future versions.

I would recommend installing 2.9 then patching to 2.9.1 then installing one of the EC10 kernels. This will be almost identical to the 2.9.2 kernel without losing your app sync.

Sent from my Fascinate

Superclean 2.9.1

EC10 voodoo kernel

EA28 radio
[Fascinate Android Development] landshark68:
As far as your problem restoring your paid apps from the market. Try two things: 1) go menu=>settings=>applications=>and make sure there is a checkmark in unknown sources, that allows third party apps to be restored. If that doesn't fix the issue go menu=>settings=>applications=>manage applications=>all, scroll to market, if clear cache is a lighter shade of gray and you can click it, try that first. If not you will need to click clear data, that should clear it out, but would be your last resort.

I'm not aware of Adrynalyne doing anything like that. In terms of Titanium Backup all he ever said was definitely don't restore any system data. The automatic restore of apps is a Froyo feature. To turn it off you have to do it manually. Go menu=>settings=>privacy and uncheck automatic restore. I highly doubt Adrynalyne is going to put something in superclean that is going to block your ability to restore the apps you paid for. The market is completely separate from the ROM. He definitely did not remove the ability to restore apps through titanium backup. And people weren't getting FC's because they were restoring apps through Titanium Backup, they were getting FC's because they were restoring system data though TiBu. I have been using superclean since .4, have always used TiBu to backup and restore, and have not run into the FC issue. That's because when I restore I only use the option of restoring all missing apps with data, not all apps, and definitely not either of the two options that restore system data.

ETA - My apologies scarfman4, you are correct. I completely missed that last item in the changelog where he says automatic restore is not possible. And I do remember now people's phones locking up a bit because of the automatic restore. Sorry about saying Adrynalyne did not do anything about the automatic restore of apps feature from Froyo. I'm not changing my original post and just adding this because I'm always willing to admit when I'm wrong. Sorry again.
[Fascinate Android Development] drnihili:
Actually, they finally showed up. Not sure what took so long. My best guess is that it was the result of removing all accounts except the one I purchase apps with, waiting a while, and some number of reboots.

Still no SOD on this go round.
[Fascinate Android Development] GizmoDroid:
I don't really know of an easy way to explain it, since I don't know exactly what the "proper" terms are for the different things. So bear with me if the following isn't 100% true (but it's at least mostly true, I promise):

ROM's like SuperClean are really just an supposed to be an overlay of whatever stock ROM they are made from. For proper installation, they require that the stock ROM be first installed before flashing. This is because some of the modified system files in SuperClean can not properly generate the helper data needed (on data and/or dbdata partitions) because of the signature mismatch errors. By installing stock first, they can generate the certificates and databases they need, then they can be replaced during CWM (otherwise, they will be blocked from install during bootup).

The reason why we can get away with upgrading SuperClean releases without re-flashing to Odin every time is because, if you leave the databases intact, then they are already created. Since the files are pushed during CWM, then it doesn't recheck the certificates/signatures against the files.

ROM's like CM7, AOSP, MIUI are different because they are modified at the source code level, then recompiled using all the same key. This means that all the signatures are valid and match the internal files. Because of this, they can correctly recreate the databases needed where data is stored.

So what it comes down to is that ROM's like SuperClean are not complete. They have all of the files needed for the System partition, but since important files are "broken" (by signature mismatch from being modified), they cannot set up certain things that are essential to the operating system.

A "debloated" style ROM, that doesn't modify any of the system apps/framework files, but only deletes unnecessary files, may be able to install properly. However, SuperClean and others, cannot.

The full package odin files overwrite the entire partitions, so in doesn't matter if lagfix is disabled or not.

The partitioning (pit) file goes even a step further in knocking out any lingering partition record that might cause issues.
[Fascinate Android Development] MattRussNC:
As for why one would disable the auto market redownload, i cant say for sure what his reasons was but i am extremely grateful that he did. Many here if not most i am guessing probably use titanium to restore apps and data (not system data). I know in the past every time i flashed a new rom (about once a week) i would always forget to turn off sync before the market started going crazy on the downloads before i got the chance to run titanium. That dang feature (i actually thought it was a bug first couple weeks) drove me crazy.

If there are enough ppl out there that like it and want it back in, then please please please make it optional.
[Fascinate Android Development] sfd0124:
Followed the instructions exactly and it's been functioning very well since yesterday. Only strange thing is I can't flash the Nitro Dark apps package after flashing theme. I did it successfully a couple of days ago and now no go, not a deal breaker though. Thanks for the walk through and hard work.

Edit:spoke to soon. GPS locks on really quick but if I type or use voice to navigate I get message "data connection lost" and the map closes.
[Fascinate Android Development] GizmoDroid:
This might be theme related. Can you post a link to which theme version you used?

Also, did you use SuperClean v2.9.2 from this post? Voodoo, or non-voodoo?

You say that you can't flash the Nitro Dark apps package. What error does it give?
[Fascinate Android Development] sfd0124:
I am running the SC non voodoo from this post. Theme is Nitro vivid. Message during app install is:

E: Failure at line 3

Copy_dir package : system SYSTEM

Installation aborted

Thanks
[Fascinate Android Development] GizmoDroid:
I just looked, and that package isn't scripted to mount the system partition first. :confused: Not sure why he wrote it that way.

You'll have to manually mount in the "mounts and storage" menu, or edit the update-zip inside of the apps package.
[Fascinate Android Development] drnihili:
No sleep of death so far, so it looks like it may have solved the problem.

Paid apps showed up in the Market after a few hours. I'm not sure why it took so long. I can understand not having everything auto restore, but for a while there it was looking like I would have to use TiB or lose my paid apps. That's problematic given that Adryn has said he thinks many cases of SOD can be traced to restoring with TiB. As it stands, I've only used TiB to restore a couple of small things that are no longer available in the market (a wallpaper app for example).

Thanks for the help all.
[Fascinate Android Development] sfd0124:
Thanks for the reply. I am going to start again tonight without using a theme. I'll test for 24 hours and see how it goes.

edit: Back to SuperClean 2.9.2, no themes. Will test for a day or two.

update: Followed steps exact again, no theme, stock kernal. NO issues at all 48 hours later. Have used all features repeatedly.
[Fascinate Android Development] inkdrink:
Thanks for this! I know it's old, but I ran into the same issue after trying somebody else's pre-rooted EB01 and it started booting into the Samsung recovery with a block mounting error. Going to try this EB01 that you just linked to.
[Fascinate Android Development] MattRussNC:
going through the thorough method now, coming from voodoo sc2.9.2. Out of curiosity during the odin of the eb01 how long does it normally take the factoryfs stage to complete? I guessed it would take around 10 mins but im coming up on 15 and didnt know at what point i should pull the plug and start over?
[Fascinate Android Development] cesium:
Wait, so based on the message in the OP, should I not flash this CWM? I would not be wiping data, or ODIN'ng or anything; I plan to keep my ROM install continuing as is.
[Fascinate Android Development] GizmoDroid:
At this point, I only recommend coming from the stock odin, until I get a chance to look at what's causing this new cwm to have errors with ROM's that were installed with the old cwm.
[Fascinate Android Development] s44:
I was looking at the fxpms script and... why does it have htc-specific stuff in it?

facepalm

Does the Red Clockwork one have this as well?
[Fascinate Android Development] GizmoDroid:
Because it's from Cyanogenmod, so it's made to work with multiple phones. If it's the same lines that I saw, then it won't do anything on our phones.

Do you mean the older cwm script? Yep. It had the htc stuff too.
[Fascinate Android Development] MattRussNC:
i finally pulled the plug and tried again (yay it still turned on). Anyways other attempts is still getting stuck and or failing on the factoryfs stage.

Any advise

using odin3 v1.30

repartition, auto reboot, reset time checked

files gotten from link in this thread

PIT atlas_v2.2.pit

PDA CI500_VZW_EB01_FROYO_REL.tar.md5

Solved. corrupt download of the eb01 image, fresh download fixed everything.
[Fascinate Android Development] s44:
Change usb ports or cables. Odin can be temperamental.
[Fascinate Android Development] mengineer:
Are you using the cable that came with your phone? When we first got roms people using different usb cables were having problems.

Sent from Tapatalk on my SC2.9.2 Honeycombed Fascinate.
[Fascinate Android Development] MattRussNC:
solved, feel like a id10t. after about ten attempts with different cables, ports, computers and os's i finally did the smart thing and verified the stock image to find my first download was corrupt. re downloaded and everything went smooth.

damn, i dont know how many times ive read about peoples issues starting from corrupt downloads and here it hits me and takes me half the day to figure out.
[Fascinate Android Development] SOTK:
Followed steps in OP today to start over, so to speak, with phone. Process went fairly smooth. I'm pretty happy with device responsiveness so far. I had a couple of force closes at the end of the process but things seemed to even out after a reboot into cwr and I clicked on fix permissions; however, need to point out that fix permissions didn't do normal process. It stated "done" pretty quickly. Not sure what gives with that. All in all though I'm glad I started over. Great guide. Thanks. :)
[Fascinate Android Development] adamantypants:
I appreciate all the work that's gone into this post, but can the OP PLEEEEAAAASE include the necessary files? A big part of the problem I've had with this phone is that files are EVERYWHERE and NEVER the same.