Related
I got the OTA this morning, and it soft bricked my phone... so I used Odin and went to JI6 (from the stock ROM). Phone was rooted and unlocked before.
Now when I try to root, I place the update.zip in the root directory of the phone (not the sdcard), reboot into recovery using the volume buttons, it says it flashed.
But, when I go to use any app like Clockwork Mod, that requires root... I get the same error msg every time "The application Superuser Permissions (process com.noshufou.android.su) has stopped unexpectedly. Please try again. [Force Close] button.
I've tried to root repeatedly, same results.
What am I doing wrong? It was so simple the first time around.
Thanks
mtburner said:
I got the OTA this morning, and it soft bricked my phone... so I used Odin and went to JI6 (from the stock ROM). Phone was rooted and unlocked before.
Now when I try to root, I place the update.zip in the root directory of the phone (not the sdcard), reboot into recovery using the volume buttons, it says it flashed.
But, when I go to use any app like Clockwork Mod, that requires root... I get the same error msg every time "The application Superuser Permissions (process com.noshufou.android.su) has stopped unexpectedly. Please try again. [Force Close] button.
I've tried to root repeatedly, same results.
What am I doing wrong? It was so simple the first time around.
Thanks
Click to expand...
Click to collapse
Check to make sure, you have latest release of busy box installed.
Do I need busy box? I didn't need it the first time I rooted.
Did you rename the update.zip file that was already on your internal memory from when you flashed clockwork recovery the first time?
Are you sure you didn't name it update.zip.zip because your pc was hiding the file extension?
Check the general sticky. I odin to ji6 and routed no problem and put my steps in the sticky.
Try the OCLF by Ryan. I used that to re-root my Vibrant after successfully updated to JI6 via Kies Mini last night.
OCLF - One Click Lag Fix. That app is in market and it will root your phone so no pc is needed. You need to run it on your samsung vibrant phone once than reboot it. You should see super user permission icon in your apps.
If anybody here doesn't mind testing, could you check out the following thread and test the new z4mod app on your Captivate? I only have an I9000, but the app (and lagfix) should work fine on the Captivate as well. Let me know please!
http://forum.xda-developers.com/showthread.php?p=9307467#post9307467
Is there any difference between this one and the one from before? I used the z4mod to root my stock 2.1 on Sunday. It didn't work the first time I tried and it rebooted. The second time did work however. I was in the process of installing Doc's I9000 rom.
EDIT:
Scratch that. I mistook this for the rooting app. Oops.
Testing on top of cog 2.3B6. Had voodoo enabled already. Will also try to do this to my rom with voodoo disabled later.
EDIT: Don't flash on top of voodoo enabled rom. It soft bricked. Can't get past ATT screen. Will try again with lagfix disabled.
EDIT2: does not seem to work on any top of the cogkernerl (voodoo is part of it) at all.
when it reboots voodoo starts talking, even though it shouldn't. i'm thinking its detecting changes to the partitions, and changing them back, which then bricks the rom, as you then mount items that are not there.
Perhaps this would work on a kernel that does not have voodoo as part of it.
Works on Captivate stock JH7
I tried it last week and it worked great, it took about 8 or 9 minutes to root, but rooted I am. Just waiting for source now. Sorry, thought this was just root. I updated but haven't tried it out yet. I'll try it out after a fresh charge.
I decided to flash back to stock last night on a hunch that we will be getting an update in the coming day or so. When I checked around noon pacific standard time I saw nothing had happened with a numbers change in the About phone menu of the phone.
So I say screw it, I want to give JT's Superclean v.9 a shot. I have played with most of the other DJ05 roms listed under the development section here as well as multiple kernels.
I tried downloading the JT rom last night via ROM Manager and it was going excruciatingly slow. My signal readings were of the 1XL variety. Something I'm not even familiar with. After waiting for over an hour for the rom to download I rebooted my phone and 3G was back. Tried downloading the rom again and it was going quicker but still slow so I gave up until noonish today.
I downloaded it. Downloaded the voodoo kernel in ROM Manager, 12/14 stable, and then pulled the battery and went to download mode and used ODIN to install the DJ05 modem and CWRecovery.
When I went into recovery then applied the update zip and went to CwM, everything proceeded as normal with the exception of my volume keys and power button no longer function in CwM.
Needless to say I can't apply the signed copy of SU to my phone to gain root access and the one click root doesn't work and I cannot find z4root in the market.
Is Verizon/Samsung wise to the fun we are having and blocking some of the functions if returned to stock?
I have since went back to DI01 and tried installing CWMRecovery in ODIN and still get to the CWMRecovery screen and the volume/power button do nothing. Actually, the soft keys do nothing either.
Puzzled...
As a side note, my phone is fully functional otherwise.
Try Googling the z4root apk
so fresh and so superclean.
I tried that and had no success.
Tried CLShortFuse's Superoneclickroot v1.5.5 and it got me SU so I could use ROM Manager and pull the latest CWM. Working good again.
Not sure why the CWMRecovery was not working before.
Hello all,
Been rambling around the forums in ninja mode trying to gain enough knowledge to not mess up my phone before trying to mod it but alas best laid plans....
Anyhoo I was working to put the Froyo leak on my phone and everything was good till I did a cwm wipe of the phone and wammo it had problems. I managed to use Odin to get it back to barebones stock, lost my high score in Angry Birds too dang it.
Now that I am back to this point I tried to run the Verizin updates and it downloads and goes into install mode on reboot and it dies at Updating Modem section. At that point I saw I was rooted so I removed that and tried again, no dice amigo. Did a factory wipe, nothing. Cleared the cache, fail again.
If it helps its trying to do a dh12 to di01 update. Got any ideas?
When you went to stock did you flash the stock kernel and stock recovery as well? I had to do this when I updated to dl09
Good question and yes I believe I did, I followed this: http://forum.xda-developers.com/showthread.php?t=782204&highlight=return+stock thread to get the job done. Let me try it one more time.
Also I load the PIT file with each md5 correct?
Looks like I fixed it on the second time around. Not sure what I missed but the update went through. No worries. Might pay someone to hand hold my through getting DL30 on my phone cause even as an IT guy I'm missing something every time.
Strong thing is, once the DI01 update happens it actually doesn't find any other updates...wifi is off.
VZW pulled the DL09 update due to the e911 bug until it is fixed
Makes good sense. Sooo anyone wanna tutorialize me on how to de-crappify my phone? Its worth a donation from me.
You're on di01 right?
I would odin the dl09 package, then use cwm to flash super clean 2.2. Clean, debloated froyo goodness
Sent from my SCH-I500 using XDA App
Sounds good. The problem lies in me somehow fudging up the process at some point and having to set my phone back to stock again.
Where did you see this?
"VZW pulled the DL09 update due to the e911 bug until it is fixed"
Have any sources on this one? I really would like to see them.
Not doubting you, I have just been rebooting and *228 for 3 days trying to get this update only to see this quote...
VZW sent a message to all Fascinate owners the other night acknowledging the bug and a fix being in the works. Why would they continue to push it out after that?
Sent from my SCH-I500 using XDA App
Well...
0123456789
New EA update is being pushed out.
Verizon told me to go to a store as some phones will not accept OTA updates. Seems stupid and like a lie, but whatever...
Atst44 said:
"VZW pulled the DL09 update due to the e911 bug until it is fixed"
Have any sources on this one? I really would like to see them.
Not doubting you, I have just been rebooting and *228 for 3 days trying to get this update only to see this quote...
Click to expand...
Click to collapse
He's right. Google the source if you need it. Please don't take this response as me being snarky, I don't mean it that way.
I think the biggest issue people are having is not being careful and following the directions perfectly.
I was new two days ago and did this with only one hiccup.
1. I followed the Beginner's thread in this forum to get me rooted. First pass with Odin failed as the one click code didn't recognize the phone. 2nd pas worked. Trick was to just turn on USB debugging and plug in phone, do not then click the mount notification. Leave that off as USB debugging was all that was needed.
2. I installed Mod Manager and Titanium backup right after. This was part of the main directions and Titanium (though not mentioned) allowed me to save all my specific apps that had important data, like my 100% completed Angry Birds.
3. I then followed the directions in the developer forum for the How To.. install DL30 for Froyo. This scared me at first because the CW recovery stalled when wiping data. I waited over 30 minutes before getting the courage to pull the battery and start over. Figured its only deleting user data, should be ok. It was and then it worked the 2nd time without fail. I did reboot in normal recovery, but running the update.zip put it back into CW.
4. After that, I rebooted numerous times, checked all stock apps, upgraded firmware in camera, and used Titanium to add back my apps I bought or downloaded as well as restored my bookmarks and memo notes.
In the end I've had no bugs/issues as others have reported. Only functionality not tested is bluetooth as I don't use it for anything.
I hope this helps and if you are walking through it all again, I would be glad to help specific questions based on my experience.
I was DL09 stock OTA at first. I'd recommend getting rooted and using Odin to get the stock DL09 from these forums flashed before you try to put DL30 on. As a developer myself, it just makes sense to always put on builds that are in order of each other. So DI01, then DL09, then DL30.
0123456789
superchunkwii, thanks for the feedback. When I booted into cwm recovery mode it hung too. I think my fatal mistake was I booted in regular recovery mode and did my wipe....sad. I should have just rebooted and went back in cwm like you did.
As far as freezing apps I did not know freezing angry birds would save its data. Boy was my wife is mad (she plays it the most).
I did everything else on cue so I will try again and see how she goes. IT CAN BE TAUGHT! As the genie says.
On another note I did download the EA28 update today, can I install the DL30 Rom or do I need to "downgrade" to DL09 to get this done? Anyone try?
dlmcclou said:
superchunkwii, thanks for the feedback. When I booted into cwm recovery mode it hung too. I think my fatal mistake was I booted in regular recovery mode and did my wipe....sad. I should have just rebooted and went back in cwm like you did.
As far as freezing apps I did not know freezing angry birds would save its data. Boy was my wife is mad (she plays it the most).
I did everything else on cue so I will try again and see how she goes. IT CAN BE TAUGHT! As the genie says.
On another note I did download the EA28 update today, can I install the DL30 Rom or do I need to "downgrade" to DL09 to get this done? Anyone try?
Click to expand...
Click to collapse
1. Not freeze.. that makes it so app won't run. Backup with Titanium Backup is what you need I think.
2. What is EA28? I don't think the fascinate has had that build.
Just got an update EA28 any ideas what it does
Sent from my SCH-I500 using XDA App
EA28 build is the update to fix the emrgency dialing bug in DL09. As I understand, it is otherwise the same as DL09. I am by no means an expert though.
EA28 build is the update to fix the emrgency dialing bug in DL09. As I understand, it is otherwise the same as DL09. I am by no means an expert though.
Click to expand...
Click to collapse
Cool. Can anyone confirm this?
Hey folks, I'm hoping one of you can help me out with an issue that just cropped up on my phone. I've been running EB01 since it's release and have had no issues whatsoever except for today when I noticed my apps (Titananium Backup, Tapatalk, Root Explorer) we're remembering preferences anymore and/or every time I exit from them and launch again....it thinks it's the first run again.
Did something hose up my permissions/ownerships? Only think I did recently was flash the de-binged browser via CWM.
Any ideas??
What are you running? It may be a permissions problem. Have you tried uninstalling it and reinstalling it?
I'm having a similar issue. Help!
jpolzner said:
Hey folks, I'm hoping one of you can help me out with an issue that just cropped up on my phone. I've been running EB01 since it's release and have had no issues whatsoever except for today when I noticed my apps (Titananium Backup, Tapatalk, Root Explorer) we're remembering preferences anymore and/or every time I exit from them and launch again....it thinks it's the first run again.
Did something hose up my permissions/ownerships? Only think I did recently was flash the de-binged browser via CWM.
Any ideas??
Click to expand...
Click to collapse
I was just about to start a thread about this. I'm having the same problem. I upgraded from blackhole 4.1 (DL30) to Superclean 2.2 EB01 with voodoo lagfix. I got the red CWM flashed via odin and proceeded to install the EB01 modem and the superclean 2.2v (EB01).
The first time I flashed was a disaster, there were issues with Odin completing the flash, so I had to do USB pulls about 4 times (which ended up giving me full "light blue" screens during download mode at times).
After getting Odin to cooperate, I was able to flash the Superclean 2.2v (EB01), and then I restored everything from Titanium Backup, which worked fine until I restarted the phone or left it alone for a couple of hours. Everything would force close (like ADWLauncer Ex, forcing me to use ONLY TWLauncher) and all my preferences were lost. Like gmail would have to resync as if it were new, all the EULA dialogs would come up (like in android market), my trillian profiles were all lost, if i turned off haptic feedback that would turn back on, my ringtones would go back to the defaults, etc.
So I read some other thread in the Development section which said to reflash, and do not do any restores at all. So I reflashed with Super clean 2.3v (EB01), but it happened again, all my preferences would be lost. I also tried to do "fix permissions" from RED CWM, but it just ran for like a fraction of a second and didn't seem like it did anything, as the problem persisted.
I'm planning to go back to DL30 or even DL09 to see if my phone functioned properly or not.
If anyone has a solution to this problem please help!
- Superclean 2.3v (EB01)
I'm thinking it has something to do with flashing either the De-Binged browser or the new market update. Maybe something in the framework-res is getting hosed up?
I just did a wipe and reflashed plain old EB01 and I'm not going to flash any changes and see if the problem comes up again.
emortio said:
I was just about to start a thread about this. I'm having the same problem. I upgraded from blackhole 4.1 (DL30) to Superclean 2.2 EB01 with voodoo lagfix. I got the red CWM flashed via odin and proceeded to install the EB01 modem and the superclean 2.2v (EB01).
The first time I flashed was a disaster, there were issues with Odin completing the flash, so I had to do USB pulls about 4 times (which ended up giving me full "light blue" screens during download mode at times).
After getting Odin to cooperate, I was able to flash the Superclean 2.2v (EB01), and then I restored everything from Titanium Backup, which worked fine until I restarted the phone or left it alone for a couple of hours. Everything would force close (like ADWLauncer Ex, forcing me to use ONLY TWLauncher) and all my preferences were lost. Like gmail would have to resync as if it were new, all the EULA dialogs would come up (like in android market), my trillian profiles were all lost, if i turned off haptic feedback that would turn back on, my ringtones would go back to the defaults, etc.
So I read some other thread in the Development section which said to reflash, and do not do any restores at all. So I reflashed with Super clean 2.3v (EB01), but it happened again, all my preferences would be lost. I also tried to do "fix permissions" from RED CWM, but it just ran for like a fraction of a second and didn't seem like it did anything, as the problem persisted.
I'm planning to go back to DL30 or even DL09 to see if my phone functioned properly or not.
If anyone has a solution to this problem please help!
- Superclean 2.3v (EB01)
Click to expand...
Click to collapse
I'm having the exact same problem. I've been all the way down to DJ05 to see what happens, and when I come back to superclean 2.2 voodoo-ed, I get force closes on everything the first time I restart - that issue was due to the new feature froyo added "automatic restore" in settings > privacy. I got that taken care of by uninstalling all apps.
However, when I restart now, my entire phone defaults back to cleared data. I'm talking every setting that I could think of (usb debugging, sound, brightness, contacts, security pin cleared). I don't get it at all. Everything else has been working right though.
Just thought I would share - I'm kinda still in limbo till I figure out what I should do.
brettdacosta said:
I'm having the exact same problem. I've been all the way down to DJ05 to see what happens, and when I come back to superclean 2.2 voodoo-ed, I get force closes on everything the first time I restart - that issue was due to the new feature froyo added "automatic restore" in settings > privacy. I got that taken care of by uninstalling all apps.
However, when I restart now, my entire phone defaults back to cleared data. I'm talking every setting that I could think of (usb debugging, sound, brightness, contacts, security pin cleared). I don't get it at all. Everything else has been working right though.
Just thought I would share - I'm kinda still in limbo till I figure out what I should do.
Click to expand...
Click to collapse
I wonder if it has to do with the type of EB01 we're using or the CWM. I flashed CWM red via Odin, rather than updating via Rom Manager or update.zip. Also I used the EB01 Walkthrough in the fascinate developers section, the link is:
http://forum.xda-developers.com/showthread.php?t=948722
***UPDATE***
I resolved the problem... I think. I noticed there was a difference in the file names of the EB01 Modem in the walkthrough link I provided on the last line of the paragraph above and the EB01 Modem given in the original EB01 stock thread (http://forum.xda-developers.com/showthread.php?t=948679). I flashed with the eb01a_modem.tar given in the stock thread and then upgraded to Super Clean with Voodoo (v. 2.4 as of this writing). The market DID restore all the apps, before I was able to stop it, but after I restarted, there were no force closes nor were there any loss of preferences. I hope the modem issue was what was wrong...
Started doing it again this morning. This time I did not flash any mode via ROM Manager. Only things I did was de-bloat using Root Explorer and Titanium Backup.
Not every app started forgetting preferences, some still reemebered. Any of the devs have an idea of what's going on here? I'm running the plain old, fully-bloated EB01 ROM. No voodoo, no de-odexed, or anything like that.
I think it's a dbdata partition issue. I can't say how to fix because it's above my paygrade, but you may have to wait until it is officially released.
jpolzner said:
Started doing it again this morning. This time I did not flash any mode via ROM Manager. Only things I did was de-bloat using Root Explorer and Titanium Backup.
Not every app started forgetting preferences, some still reemebered. Any of the devs have an idea of what's going on here? I'm running the plain old, fully-bloated EB01 ROM. No voodoo, no de-odexed, or anything like that.
Click to expand...
Click to collapse
Try the Odin back to stock...DI01, wipe everything. Reroot and and get cwm. Then ODIN EB01 Modem Tar followed by super clean 2.4 install through cwm. Be sure to wipe data and cache before flashing super clean.
I there a reason I have to go all the way back to DI01, or can I use any All-In-One Odin package that writes the ROM, Kernel, & Radio?
jpolzner said:
I there a reason I have to go all the way back to DI01, or can I use any All-In-One Odin package that writes the ROM, Kernel, & Radio?
Click to expand...
Click to collapse
I suggest that typically before anything else b/c it seems to help most. I've never experienced these issues but many suggest this is a viable method to remedy certain problems. Don't see why you couldn't try the odin DL09 all-in-one and wipe the hell out of it and try again. Good Luck.
Is the corruption in the dbdata partition caused by an older version of CWM or a problem in the EB01 ROM itself?
Is it safe to go back to EB01?
jpolzner said:
Is the corruption in the dbdata partition caused by an older version of CWM or a problem in the EB01 ROM itself?
Is it safe to go back to EB01?
Click to expand...
Click to collapse
I believe it's currently inconclusive. There is speculation about exactly what causes it hence the reason I suggest wiping everything and then flashing the most recently provided stuff. That way it'll narrow things down. Someone can correct me, but if you odin back to stock, I'm 99% sure super cleans 2.4 voodoo kernel includes the new cmw. I was on green cmw unitl I flashed the seperate voodoo kernel posted by jt. I haven't had any issues.
Its almost certainly dbdata corruption. The cause is...yeah questionable. Seems most common with voodoo with the current hack being used to get it working with froyo.
Sent from my SCH-I500 using XDA App
I've never run Voodoo on my phone, but I did my initial install of EB01 with one of the older "Green" CWM versions.
adrynalyne said:
Its almost certainly dbdata corruption. The cause is...yeah questionable. Seems most common with voodoo with the current hack being used to get it working with froyo.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Any other suggestions or fixes?
I went all the way back to DI01, then flashed to EB01 using an Odin All-In-One and now 48-72 hours later, my apps (most notably Tapatalk, Root Explorer, and Titanium Backup) think it's the first time they've run every time I launch it.
Shouldn't have going back to DI01 fixed the corruption since it reformats the ROM partition? Also, something I notice was that flashing to DI01 or EB01 using odin did not get rid of the new CWM Recovery.
Would running the permission fix correct the issue?
jpolzner said:
Any other suggestions or fixes?
I went all the way back to DI01, then flashed to EB01 using an Odin All-In-One and now 48-72 hours later, my apps (most notably Tapatalk, Root Explorer, and Titanium Backup) think it's the first time they've run every time I launch it.
Shouldn't have going back to DI01 fixed the corruption since it reformats the ROM partition? Also, something I notice was that flashing to DI01 or EB01 using odin did not get rid of the new CWM Recovery.
Would running the permission fix correct the issue?
Click to expand...
Click to collapse
No...are you running voodoo? And what rom are you using?
EB01 Fully Bloated, Non-Voodoo Kernel
Baseband version: S:i500.04.V.EB01
Kernel version: 2.6.32.9
Build number: SCH-I500.EB01
http://forum.androidcentral.com/ver...roms-w-root-new-clockwork-updated-2-15-a.html
Try This...
This will hopefully repartition and clean dbdata corruption. BTW, I couldn't get 2.2 to run on my phone until I odin flashed a ROM which allowed me to then flash Adrynalyne's 2.4.
DI01, DJ05, DL09 did not work for the fix. Eclair worked fine, but Froyo would not work until I flashed a 2.2 odin.
Do I need to check the "Re-Partition" option in Odin when flashing or does it do it automatically?