[FrankWhite77]

you are not rooted,,,, pull the battery and try again

-click-root/Files/root.sh
Starting installation...
Copying files...
620 KB/s (26277 bytes in 0.041s)
3872 KB/s (1867568 bytes in 0.471s)
18 KB/s (5392 bytes in 0.284s)
0 KB/s (24 bytes in 0.052s)[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}[*] Searching for adb ...
[+] Found adb as PID 2200[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] 7-4-3-C@web.de so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.

Mounting system
error: device not found
Moving su
error: device not found
Moving busybox
error: device not found
Changing permissions on su
error: device not found
Changing permissions on busybox
error: device not found
Installing superuser.apk
error: device not found
Rebooting device...
error: device not found
You can now close terminal.



And my phone is frozen unless I do a batt pull.

[DroidXcon]

-click-root/Files/root.sh
Starting installation...
Copying files...
620 KB/s (26277 bytes in 0.041s)
3872 KB/s (1867568 bytes in 0.471s)
18 KB/s (5392 bytes in 0.284s)
0 KB/s (24 bytes in 0.052s)[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}[*] Searching for adb ...
[+] Found adb as PID 2200[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] 7-4-3-C@web.de so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.

Mounting system
error: device not found
Moving su
error: device not found
Moving busybox
error: device not found
Changing permissions on su
error: device not found
Changing permissions on busybox
error: device not found
Installing superuser.apk
error: device not found
Rebooting device...
error: device not found
You can now close terminal.



And my phone is frozen unless I do a batt pull.

let me try to get intouch with braydon see if he can add a pause to give you and the phone time to create a connection before it continues


meanwhile:when the phone turns back on did you unlock it?

[Braydon525]

-click-root/Files/root.sh
Starting installation...
Copying files...
620 KB/s (26277 bytes in 0.041s)
3872 KB/s (1867568 bytes in 0.471s)
18 KB/s (5392 bytes in 0.284s)
0 KB/s (24 bytes in 0.052s)[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}[*] Searching for adb ...
[+] Found adb as PID 2200[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] 7-4-3-C@web.de so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.

Mounting system
error: device not found
Moving su
error: device not found
Moving busybox
error: device not found
Changing permissions on su
error: device not found
Changing permissions on busybox
error: device not found
Installing superuser.apk
error: device not found
Rebooting device...
error: device not found
You can now close terminal.



And my phone is frozen unless I do a batt pull.

Run the 1-click-remove root. Then try rooting again. You will probably get some errors during the 1-click-removeroot, but as long as they aren't device not found it will have worked

[FrankWhite77]

Run the 1-click-remove root. Then try rooting again. You will probably get some errors during the 1-click-removeroot, but as long as they aren't device not found it will have worked

/1-click-remove-root/Files/unroot.sh
Starting uninstallation...[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}[*] Searching for adb ...
[+] Found adb as PID 2200[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] 7-4-3-C@web.de so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.

Mounting system
error: device not found
Removing su
error: device not found
Removing busybox
error: device not found
Removing superuser.apk
error: device not found
error: device not found
Cleaning up
error: device not found
error: device not found
error: device not found
error: device not found
Rebooting device...
error: device not found
You can now close terminal.



Phone frozen again.

[Braydon525]

And my phone is frozen unless I do a batt pull.

During the testing procedure, I noticed if the root exploit doesnt finish successfully, my phone would freeze on the second attempt if i didnt reboot in between. thats why your phone is freezing, no need to fret, its not harming anything permanently

[FrankWhite77]

During the testing procedure, I noticed if the root exploit doesnt finish successfully, my phone would freeze on the second attempt if i didnt reboot in between. thats why your phone is freezing, no need to fret, its not harming anything permanently

yeah I'm not too worried I've seen you guys get people out of much bigger jams haha do you have an instant messenger at all? I feel bad filling the thread with my one problem.

[DroidXcon]

yeah I'm not too worried I've seen you guys get people out of much bigger jams haha do you have an instant messenger at all? I feel bad filling the thread with my one problem.

Dont feel bad , this could happen to others its good for it to be seen , maybe they can learn

[FrankWhite77]

Braydon is the man! A thousand thanks to him.

[DroidXcon]

Braydon is the man! A thousand thanks to him.

I know he is awsome

[Braydon525]

Braydon is the man! A thousand thanks to him.

So what happened is his phone was already rooted. When the root exploit was run, it froze the phone.

If anyone else is having this issue, please be patient. I am working on a fix. For now, just wait an hour or so and try again. That should disable the root exploit.

[ls5012]

Although I still can't get my phone rooted, ( I have searched these forums and every other forum I could find on the internet & I'm on my last nerve!!!! I did find this method for having the phone recognized by the mac. Hope this helps!

After you plug in the phone and these messages come across the status bar, swipe down on the screen and select "USB Connected" "Select to copy files to/from your computer" Then select "Mount" when the blue USB connected message pops up. Wait a few minutes until you get the "Disk you inserted was not readable" error, select "Ignore". At this point, just to be sure, open "Disk Utility" on your Mac, you should see an entry for "Samsung SCH -I500. Select it and then hit "Info". Look at the Disk Identifier, it should say disk1 or some other number. If it is disk1 just copy "gpt show /dev/disk1" without quotes and paste it in Terminal. If it is disk2 or another number just change the 1 to whatever number yours happens to be. When you have that copied in Terminal, look back at your phone and "Turn off USB Storage" select "Turn off" on the blue message that pops up, wait a few seconds and the "USB connected" "select to copy files" message comes back on your phone "select it and mount again. Then bring up your Terminal and hit enter to run the command. You should get something like this,
start size index contents
0 1 MBR
1 128
129 30904191 1 MBR part 12

[ls5012]

I am also having the same issues with the terminal not find the directory or device. As I posted 2 days ago. I really appreciate all of the help from the people on the forums. But I am starting to think that Samsung/Verizon installed something with the last patch that just makes impossible to root. I have tried every method multiple times that I could find going all the way back to Sept. And I have searched and tried every video tutorial I could find. Would anyone be able to root the Fascinate using a way to get in to my computer remotely? I have had Verizon and other software companies do this & it's a miracle! I am going Crazy!!!! Can't get certain apps like updated Angry birds etc. anymore because no root!!! HELP!!!!!!

[Braydon525]

I am also having the same issues with the terminal not find the directory or device. As I posted 2 days ago. I really appreciate all of the help from the people on the forums. But I am starting to think that Samsung/Verizon installed something with the last patch that just makes impossible to root. I have tried every method multiple times that I could find going all the way back to Sept. And I have searched and tried every video tutorial I could find. Would anyone be able to root the Fascinate using a way to get in to my computer remotely? I have had Verizon and other software companies do this & it's a miracle! I am going Crazy!!!! Can't get certain apps like updated Angry birds etc. anymore because no root!!! HELP!!!!!!

Do you have google chat? If you do, set it up in ichat and PM me your user name. We can do screen sharing and I can see exactly whats going on.

[Mindgrind]

Here's where I get stuck:

[*] adb connection will be reset. restart adb server on desktop and re-login.
RedBend Update Agent 6,1,14,1

FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
open device file: Permission denied
bmldevice_get_size: bmldevice_open failed!src: /sdcard/zImage
dst: /dev/block/bml7 partition size: 0x0
part_size: 0x0
reboot: Operation not permitted

By the way, after the first line I always need to unplug the usb and plug it back in before it will continue; I've had to do this on all steps and it seems to work if anyone is stuck in limbo waiting for terminal to do something.

Anyway- any clues what to do from here? I'm installing the 2.1 to 2.2 CWM. I think this is the right one (yes, noob here) for me to install. Help?

[wiccanpie]

Did we ever get anywhere with the mounting of the phone so it shows as a mass storage device on a mac yet? The one person I saw recently had the same thing I'm getting where I get the display that asks me if I want to initialize eject or whatever.

I did do Step 1, and I did get the OK to close the terminal, but alas, no such luck - just the lovely CD Rom on my desktop that says "Verizon Wireless".

[Mindgrind]

I don't even get the "initialize" option anymore. I persisted and got past my errors and went to finish the install and now all I get is the disk in un-readable!

You can ignore the "initialize" like was said in previous posts for root, but now I can't even get a reading at all. Very strange... guess I'll pull out my old Windows laptop and see if I can pick it up from there. Frustrating.

[FrankWhite77]

So I want to try the new kernel adrynaline put out yesterday to see if I get better battery life. To do this I just push to SD - and then install from SD through CWR? And if it sucks I just reflash Superclean?

[ls5012]

I am so determined to get this phone rooted. The push sd terminal seems ok. Now when I click root.app I get this:

Installing superuser.apk
180 KB/s (196521 bytes in 1.064s)
pkg: /data/local/tmp/superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Does this mean that the root is already somewhere in a file on the phone?? I have searched MY FILES & there is a 1-click -root file. If I click & hold it downI get the options page with options to Delete,Move, Copy,Rename etc.
Any Ideas?

[ls5012]

Sorry for all the posts. Out of curiousity I opended titanium back up and it now allowed me in. Gave me the option of which apps to back up, but when I checked in settings, the firmware version still says 2.1 . So confused

[Braydon525]

looks like you have root installed. You should have firmware 2.1 unless you ran 1-click-clockworkmod-2.1-2.2

Sorry for all the posts. Out of curiousity I opended titanium back up and it now allowed me in. Gave me the option of which apps to back up, but when I checked in settings, the firmware version still says 2.1 . So confused

Sent from my SCH-I500 using Tapatalk

[Braydon525]

So I want to try the new kernel adrynaline put out yesterday to see if I get better battery life. To do this I just push to SD - and then install from SD through CWR? And if it sucks I just reflash Superclean?

Yep. And if you want to go back to the original kernel, you can find that on the forums and flash it the same way, or reflash superclean.

[Braydon525]

Did we ever get anywhere with the mounting of the phone so it shows as a mass storage device on a mac yet? The one person I saw recently had the same thing I'm getting where I get the display that asks me if I want to initialize eject or whatever.

I did do Step 1, and I did get the OK to close the terminal, but alas, no such luck - just the lovely CD Rom on my desktop that says "Verizon Wireless".

Not really sure what you're asking. When you plug in your phone, do not connect to mass storage device...

[ls5012]

" You should have firmware 2.1 unless you ran 1-click-clockworkmod-2.1-2.2"
Ok I downloaded clockwork but I can't get the files extracted from the zip. I click on open, it unzips with archive. But the file shows up as: /1-click-clockworkmod-2.1-to-2.2 2 2 2.zip.cpgz. There is no application that extracts the files any further. What's up? Oh & I tried just pasting the file into the terminal & it comes up denied. I'm almost there!!!

[Braydon525]

" You should have firmware 2.1 unless you ran 1-click-clockworkmod-2.1-2.2"
Ok I downloaded clockwork but I can't get the files extracted from the zip. I click on open, it unzips with archive. But the file shows up as: /1-click-clockworkmod-2.1-to-2.2 2 2 2.zip.cpgz. There is no application that extracts the files any further. What's up? Oh & I tried just pasting the file into the terminal & it comes up denied. I'm almost there!!!

Macs come with an archive utility preinstalled that works with zips. You should be able to upzip it just by double clicking. How did you unzip the root? Use the same process. Or try right clicking and choose open with > archive utility.app

[Braydon525]

I don't even get the "initialize" option anymore. I persisted and got past my errors and went to finish the install and now all I get is the disk in un-readable!

You can ignore the "initialize" like was said in previous posts for root, but now I can't even get a reading at all. Very strange... guess I'll pull out my old Windows laptop and see if I can pick it up from there. Frustrating.

How the progess? Still having the same errors?

I haven't come across this "initialize" messages you guys keep getting. Not sure what thats all about. Let me know if you are still getting the same errors. I'll dig a little more into it.