• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Herp a derp!! Pay no attention!

Status
Not open for further replies.
and im telling you that that script doesnt put out this

PHONE WILL REBOOT
PLEASE SAVE WHATEVER YOU ARE DOING NOW
PRESS ENTER WHEN READY
Press any key to continue . . .
HERE WE GO
Click to expand...

so if you are getting teh same error then you are using kms 4.0 ;)
 
Exploit By Bliss

One Click Done by
Shabbypenguin

Press any key to continue...Starting adb server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
You need to enable usb debugging first
Go to settings > applications > development
* Running exploit [part 1 of 3]...
[*] Triggering core dump...
[1] Segmentation fault app_process 2>/d...
* Running exploit [part 2 of 3]...
[*] Rebooting phone. It may buzz a lot and loop on boot. Don't panic.
* Running exploit [part 3 of 3]...
error: protocol fault (no status)
* daemon not running. starting it now on port 5037 *
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
deleting all yo shit
* daemon not running. starting it now on port 5037 *
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now on port 5037 *
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now on port 5037 *
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now on port 5037 *
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now on port 5037 *
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now on port 5037 *
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
Copying files onto phone...
* daemon not running. starting it now on port 5037 *
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now on port 5037 *
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now on port 5037 *
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now on port 5037 *
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
Setting permissions...
* daemon not running. starting it now on port 5037 *
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now on port 5037 *
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now on port 5037 *
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now on port 5037 *
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now on port 5037 *
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
Installing busybox...
* daemon not running. starting it now on port 5037 *
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
Cleaning up files...
* daemon not running. starting it now on port 5037 *
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now on port 5037 *
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
All done!
 
I downloaded the OCR, but it only wants to open it as an iTunes file. What can I use to change it into something that will let it run so I can root?
 
ktfright said:
I downloaded the OCR, but it only wants to open it as an iTunes file. What can I use to change it into something that will let it run so I can root?
Click to expand...

What file did you try running? It sounds like you did something other than unzip the "Prevail-Replenish-NEW-OCR.zip" file and then run root.bat (Linux-Mac.sh for linux/mac oses)

When all else fails, try reading the Readme.txt :)
 
Koumajutsu said:
What file did you try running? It sounds like you did something other than unzip the "Prevail-Replenish-NEW-OCR.zip" file and then run root.bat (Linux-Mac.sh for linux/mac oses)

When all else fails, try reading the Readme.txt :)
Click to expand...
I finally got it to unzip, but now when I try to run the boot.bat, It says my phone isn't debugged, but it is, and it says that iw worked, but it didn't. Should I download a driver or something? my phone is unrooted w/ Gingerbread 2.3.5. I have a mac, but I'm using my bro's pc to root.
 
Koumajutsu said:
Ran shabbified OCR
let it complete
Once it was stuck repeatedly FC vibrating, I rebooted the phone into recovery
I then did a factory reset and rebooted
It took forever to boot, but when it did, root goodness

I did have to type su to get root in adb, and click allow when superuser popped up on the phone.
Click to expand...


Just did this on the new GB ROM, worked great

Thanks Shabby, Kouma, Interdpth
 
Will this work on the Galaxy Tab GB 2.3.5 update that was recently released?

If not, is there any word on when a root for that FW will be available?

Thanks guys!
 
aladdin99 said:
Worked great. Just reboot the phone once it starts doing the vibrating jingle. I had to pull battery.
Click to expand...
What did you exactly do to make your root work? The readme is kinda vague, and even though my phone is on debug mode, it still doesn't let me root.
It keeps saying "Not Recognized as an internal or external command." but says the root is finished.

Edit: Nevermind, got it.
 
Got the rooted copy then ended up using this on it to get it all working right (just a pain in general). Anyways, any ideas on why when uninstalling system stuff occasionally I get a force reboot? I have latest SU.apk and binary yet it still occurs. I had the CM7.1 copy of busybox 1.9 then went to 1.8 regular yet still have the reboots.
 
Man thanks again...............I updated my Prevail and I had a hell of a time trying to get root back but this worked for me. Thanks again man. I'll donate again....just for that.
 
i gutta get with qbking77 and see if we cant get another video made for yall on this new one.. i made this pre-gb so it needs some minor tweaks but hopefully i can get it going to where it goes without issues :)
 
When i try to root It keeps saying 'adb.exe' is not recognized as an internal or external command, operable program or batch file.
"You should have root!"
But it is not rooted
 
irishobo said:
When i try to root It keeps saying 'adb.exe' is not recognized as an internal or external command, operable program or batch file.
"You should have root!"
But it is not rooted
Click to expand...

are you trying to run the batch file while it's still in the zip file?
Adb is right there in the zip. You need to extract all the files from the zip into the same directory for it to work. just clicking into the zip file with windows explorer will cause it to only extract the .bat file to a temp directory and not work.
 
I used Rom Manager and bricked my phone...:( Went and purchased another Prevail and it upgraded to 2.3.5 and due to the new system I couldn't get my new phone to root using the old method. Thanks to this my 2.3.5 works fine rooted!
Thank you!

If there is any way that you know of to get my brick back up and running I'd appreciate it. This was definitely a user error on my part...
 
Chivalry10 said:
I used Rom Manager and bricked my phone...:( Went and purchased another Prevail and it upgraded to 2.3.5 and due to the new system I couldn't get my new phone to root using the old method. Thanks to this my 2.3.5 works fine rooted!
Thank you!

If there is any way that you know of to get my brick back up and running I'd appreciate it. This was definitely a user error on my part...
Click to expand...


I would try to ODIN the brick back to ED13 Stock and see if that takes.
 
Chivalry10 said:
I used Rom Manager and bricked my phone...:( Went and purchased another Prevail and it upgraded to 2.3.5 and due to the new system I couldn't get my new phone to root using the old method. Thanks to this my 2.3.5 works fine rooted!
Thank you!

If there is any way that you know of to get my brick back up and running I'd appreciate it. This was definitely a user error on my part...
Click to expand...


Did the same to mine with rom manager. Back in september. Wouldn't power on our anything. So sent it to samsung and it was so jacked up that they thought it was a phone defect and sent me another
 
DarkStarr said:
Got the rooted copy then ended up using this on it to get it all working right (just a pain in general). Anyways, any ideas on why when uninstalling system stuff occasionally I get a force reboot? I have latest SU.apk and binary yet it still occurs. I had the CM7.1 copy of busybox 1.9 then went to 1.8 regular yet still have the reboots.
Click to expand...


What are you using to remove the system apps?
 
Shabbypenguin said:
i gutta get with qbking77 and see if we cant get another video made for yall on this new one.. i made this pre-gb so it needs some minor tweaks but hopefully i can get it going to where it goes without issues :)
Click to expand...


Tweaks? It seems to run fine on gb. First try two times for me. I assume the segmentation fault is supposed to occur as part of the privilege escalation?
 
Status
Not open for further replies.
Back
Top Bottom