Problems Re-Rooting after ED05

[CarterGuy]

So after ED05 was installed it unrooted me, but I expected that. I tried re-rooting and can get temp root fine but when I restart my phone, it's gone again. I've tried twice and got the same result. I'm trying the ADB method from http://forums.androidcentral.com/ve...-please-read-post-1-before-posting-forum.html

Is anyone having the same problems?

 

[atomD21]

All you have to do to root the Fascinate is ODIN CWM 3-30 (2.5.x) and then after booting straight to recovery, flash the superuser+busybox zip (put that on your SD before ODINing CWM).

 

[CarterGuy]

So I was finally able to make it work without having to flash CWM. Like I said, I could get temp root but when I rebooted the phone it was gone. I used SuperOneClick to get the temp root but I didn't reboot the phone when it told me to. I opened adb shell and I followed the procedures in GingerBreak released - Page 6 - xda-developers after I got temp root. After I did those extra steps I rebooted the phone and opened the superuser app and updated the version and everything worked. I realize that maybe just the file permission changes are necessary but I did them all anyway. I hope this helps someone else.

Now, We need to make the root permanent by installing su:
1) Mount the system partition as read/write: mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
2) Change directory to where you pushed su, busybox and superuser.apk: cd /data/local/tmp
Step 2.1: chmod 777 /system/bin
3) Run busybox to copy itself to the proper directory: ./busybox cp busybox /system/bin
Step 3.1: chown root /system/bin/busybox
4) Change the permissions on busybox: chmod 4755 /system/bin/busybox
Step 4.1: chmod 777 /system/app
5) Run busybox to copy Superuser.apk to the proper directory: busybox cp Superuser.apk /system/app
Step 5.1: chmod 755 /system/app
6) Run busybox to copy su to the proper directory: busybox cp su /system/bin
Step 6.1: chown root /system/bin/su
7) Change the permission on su: chmod 4755 /system/bin/su
Step 7.1: chmod 755 /system/bin
8) Mount the partition as read-only: mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
9) Exit the root shell: exit

 

[JOrtenzi]

So I was finally able to make it work without having to flash CWM. Like I said, I could get temp root but when I rebooted the phone it was gone. I used SuperOneClick to get the temp root but I didn't reboot the phone when it told me to. I opened adb shell and I followed the procedures in GingerBreak released - Page 6 - xda-developers after I got temp root. After I did those extra steps I rebooted the phone and opened the superuser app and updated the version and everything worked. I realize that maybe just the file permission changes are necessary but I did them all anyway. I hope this helps someone else.

Now, We need to make the root permanent by installing su:
1) Mount the system partition as read/write: mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
2) Change directory to where you pushed su, busybox and superuser.apk: cd /data/local/tmp
Step 2.1: chmod 777 /system/bin
3) Run busybox to copy itself to the proper directory: ./busybox cp busybox /system/bin
Step 3.1: chown root /system/bin/busybox
4) Change the permissions on busybox: chmod 4755 /system/bin/busybox
Step 4.1: chmod 777 /system/app
5) Run busybox to copy Superuser.apk to the proper directory: busybox cp Superuser.apk /system/app
Step 5.1: chmod 755 /system/app
6) Run busybox to copy su to the proper directory: busybox cp su /system/bin
Step 6.1: chown root /system/bin/su
7) Change the permission on su: chmod 4755 /system/bin/su
Step 7.1: chmod 755 /system/bin
8) Mount the partition as read-only: mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
9) Exit the root shell: exit

you made this way to hard for yourself

 

[Landshark]

So I was finally able to make it work without having to flash CWM. Like I said, I could get temp root but when I rebooted the phone it was gone. I used SuperOneClick to get the temp root but I didn't reboot the phone when it told me to. I opened adb shell and I followed the procedures in GingerBreak released - Page 6 - xda-developers after I got temp root. After I did those extra steps I rebooted the phone and opened the superuser app and updated the version and everything worked. I realize that maybe just the file permission changes are necessary but I did them all anyway. I hope this helps someone else.

Now, We need to make the root permanent by installing su:
1) Mount the system partition as read/write: mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
2) Change directory to where you pushed su, busybox and superuser.apk: cd /data/local/tmp
Step 2.1: chmod 777 /system/bin
3) Run busybox to copy itself to the proper directory: ./busybox cp busybox /system/bin
Step 3.1: chown root /system/bin/busybox
4) Change the permissions on busybox: chmod 4755 /system/bin/busybox
Step 4.1: chmod 777 /system/app
5) Run busybox to copy Superuser.apk to the proper directory: busybox cp Superuser.apk /system/app
Step 5.1: chmod 755 /system/app
6) Run busybox to copy su to the proper directory: busybox cp su /system/bin
Step 6.1: chown root /system/bin/su
7) Change the permission on su: chmod 4755 /system/bin/su
Step 7.1: chmod 755 /system/bin
8) Mount the partition as read-only: mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
9) Exit the root shell: exit

See the highlighted and bold print from your post? Those are the partitioning and file systems for CM7, MIUI, and OMGB/OMFGB roms, not touchwiz roms which ED05 is. You used the completely wrong root method for your ROM. As posted earlier, flash CWM3 in ODIN, boot directly to CWM by holding volume +, volume -, and power buttons and letting go of all three as soon as the samsung logo flashes for the second time. Then flash the su + busybox file in CWM. Done, rooted properly.

CWM 3 --> http://dl.dropbox.com/u/36791/CWM3_Voodoo.tar.md5

su + busybox --> http://adrynalyne.us/files/odin/su-2.3.6.1+busybox1.19.zip

 

[jack22182]

See the highlighted and bold print from your post? Those are the partitioning and file systems for CM7, MIUI, and OMGB/OMFGB roms, not touchwiz roms which ED05 is. You used the completely wrong root method for your ROM. As posted earlier, flash CWM3 in ODIN, boot directly to CWM by holding volume +, volume -, and power buttons and letting go of all three as soon as the samsung logo flashes for the second time. Then flash the su + busybox file in CWM. Done, rooted properly.

CWM 3 --> http://dl.dropbox.com/u/36791/CWM3_Voodoo.tar.md5

su + busybox --> http://adrynalyne.us/files/odin/su-2.3.6.1+busybox1.19.zip

Something's not quite right with this method either. I followed the above instructions exactly on ED05 and got "Amend scripting was deprecated by Google in Android 1.5...etc...Installation aborted."

 

[Landshark]

Something's not quite right with this method either. I followed the above instructions exactly on ED05 and got "Amend scripting was deprecated by Google in Android 1.5...etc...Installation aborted."

Ah, sorry. Thought I gave you the edify version of su + busybox. I couldn't find an edify version of it so sorry to put you through the extra step, but you will need to flash CWM-all in ODIN, then boot directly to CWM and flash the su + busybox file.

CWM-all --> http://www.multiupload.com/SHV23CASBP

Then after flashing the su + busybox file, you can ODIN CWM 3 to have the current proper CWM

CWM 3 --> http://dl.dropbox.com/u/36791/CWM3_Voodoo.tar.md5

 

[jack22182]

Ah, sorry. Thought I gave you the edify version of su + busybox. I couldn't find an edify version of it so sorry to put you through the extra step, but you will need to flash CWM-all in ODIN, then boot directly to CWM and flash the su + busybox file.

CWM-all --> Multiupload.com - upload your files to multiple file hosting sites!

Then after flashing the su + busybox file, you can ODIN CWM 3 to have the current proper CWM

CWM 3 --> http://dl.dropbox.com/u/36791/CWM3_Voodoo.tar.md5

This worked perfectly. Thank you sir!

 

[krakerx]

So I just followed all the steps, but when I reboot the phone, it goes right into samsungs recovery and now CWM. Any advice would be great. Thanks

 

[Landshark]

So I just followed all the steps, but when I reboot the phone, it goes right into samsungs recovery and now CWM. Any advice would be great. Thanks

Which steps did you follow? Follow my steps from post 7 and you should be fine.

 

[krakerx]

Which steps did you follow? Follow my steps from post 7 and you should be fine.

OK, I got it to work, I found some steps on another forum, but I just can't seem to get it to stick. When I restart the phone, and go to go into it again, it boots back to the Samsung recovery.


Here is what I did:

Double click the ODIN file to open ODIN
Power down phone and pull battery
Hold volume down button while plugging phone into usb cord connected to pc
Yellow triangle will appear on phone and furthest left rectangle on ODIN will change to yellow
Click PDA button, find CWM file and double click on it, click Start button, should take 7 seconds
Close ODIN, unplug USB cord, put battery in phone but don't power on
Hold volume up, volume down, and power buttons until samsung logo flashes twice
As soon as samsung logo appears for second time, let go of all three buttons
You should be in CWM, volume buttons to scroll to "install zip from sd card", hit power button
Scroll to "choose zip from sd card", power button
Find the su + busybox file, scroll to it, power button
Scroll to Yes, power button
When that finishes, soft menu key until you are back at the main CWM menu where "Reboot system now" will be highlighted, power button to reboot phone, and you are rooted.

Any insight would be great

What I meant to say is that when I try to go back into CWM it goes to Samsung's recovery menu. Am I missing something, other than that the phone is rooted and working.

 

[Landshark]

OK, I got it to work, I found some steps on another forum, but I just can't seem to get it to stick. When I restart the phone, and go to go into it again, it boots back to the Samsung recovery.


Here is what I did:


Any insight would be great

What I meant to say is that when I try to go back into CWM it goes to Samsung's recovery menu. Am I missing something, other than that the phone is rooted and working.

Yes, what you are missing is flashing a custom kernel after flashing the su + busybox file. The instructions I gave were for someone who simply wanted to have a rooted stock ROM. If you want to do any further customization through CWM you have to flash a custom kernel through CWM before booting into a stock build, which will revert you back to stock recovery. You will need to ODIN the latest CWM then boot directly to CWM like you did before, then flash the custom kernel in CWM. Latest CWM is found here:

http://dl.dropbox.com/u/36791/CWM3_Voodoo.tar.md5

You can search for your choice of custom kernels in JaeKar99's Themes, Kernels, ROMs thread, post # 4 here:

http://forums.androidcentral.com/ve...s-roms-kernels-boot-animations-8-08-11-a.html

 

[krakerx]

ha i'm dumb... thanks

 

[Landshark]

ha i'm dumb... thanks

Not dumb. I forget steps all the time.

 

[dlcullen]

Landshark - thanks! I was running the Community ROM 1.3 but I noticed I was not getting calls and having quite a few force closes, especially when I used the camera. So I returned to stock updated to Verizon's latest update and rerooted by following your instructions, worked beautifully thank you!
I have a question tho... I've read about "touchwiz roms" which I understand is what I'm running, then there is the TWLauncher... LauncherPro... I prefer LauncherPro, does it matter which Launcher you use?!

 

[LukeBorgman]

I've been running stock prior to ED05 ROM rooted with no recovery ROM for a while now. To get OTA update prior to ED05, I had to unroot, do OTA update and re-root.

Then, on August 4, rooted apps stopped working. Under Settings -> About phone -> System updates -> Status it shows that on Aug. 4 I got an OTA update to "SCH-I500_ED04_ED05_Commercial" with status "Update successful". So it looks like an OTA update stomped my root. (Last OTA failed until I unrooted, so I was suprised that one snuck past me).

Trying to re-root is not sticking. I can use rage.bin to get # prompt in adb shell, but after doing the usual re-rooting below, and rebooting, I lose root access, After reboot, adb shell attempt to su from $ prompt says "Permission denied", Titanium Backup says its not rooted, and Quick Boot Reboot does nothing. SuperUser shows it's up to date. I noticed that su and busybox are still in /system/xbin with what look like good permissions. I'm re-rooting from # prompt as follows (skipped up to after successful rage.bin):

cd /system/xbin

mount -t rfs -o remount,rw /dev/block/stl9 /system

cat /sdcard/Root/su > ./su

cat /sdcard/Root/busybox > ./busybox

chmod 4755 su

chmod 4755 busybox
​

Any ideas on what went wrong and/or how I can get re-rooted with stock ROM?

 

[LukeBorgman]

In case it helps someone else with the same problem later: I finally got it to stick. Not sure what happened. The only thing I did different to get it to work was "rm /system/bin/su" which I'd stopped doing since in the past it did not exist (su is supposed to be in /system/xbin). Not sure how it got there this time but it seemed to keep root from sticking.

 

[Landshark]

Landshark - thanks! I was running the Community ROM 1.3 but I noticed I was not getting calls and having quite a few force closes, especially when I used the camera. So I returned to stock updated to Verizon's latest update and rerooted by following your instructions, worked beautifully thank you!
I have a question tho... I've read about "touchwiz roms" which I understand is what I'm running, then there is the TWLauncher... LauncherPro... I prefer LauncherPro, does it matter which Launcher you use?!

No, it doesn't matter which launcher you use. A touchwiz rom simply means the rom is based off a touchwiz build. You can use any launcher you want. I was a big fan of LP pro myself, but it hasn't been updated in quite a while. I switched to ADW EX launcher and I really like it. I'm seeing a lot of people switching to GO launcher too.