Related
Hey guy's, I've beentrying to install clockworkmod on my Epic for some time now to no avail. See, I just rooted my phone using the noobnl's "one click method v2.2.6". The only recovery I have on my phone as of right now is tthe stock recovery. I've read just about every post about the installation on clockworkmod recovery and tried accordingly. Still no custom ecovery. Im really noob to all this "wiz stuff", and would greatly appreciate any help you guy's could give me. Perhaps some DETAILED step by step instructions ( CUZ IM REAL BRAIN DEAD AT TIMES )?? I have DI11 installed on my phone as of now, and im running the stock kernel v2.6.29. again, Im rooted with "noobnl's one click" and I do have root. Also, I need to know if you download to my pc, then push it to my phone using command prompt? Do I flash it with Odin? And what do I do after I run the clockworkmod exploit? Will I have custom recovery after that, is there anymore steps involved? Thank you all for making this site the best web site I"ve been on so far. You guy's are the best. Please hel[p with my dumb question, and sorry to waste your time. Thankx IA..
http://forum.xda-developers.com/showthread.php?t=782300
Download the .zip from that. Extract it to your desktop and rename the folder "cwm". Open up command prompt. Type this:
Code:
cd C:\Users\YOUR USER NAME\Desktop\cwm
adb shell
su
remount rw
exit
exit
After that, run the run.bat from the folder.
Download the .zip from that. Extract it to your desktop and rename the folder "cwm". Open up command prompt. Type this:
Code:
cd C:\Users\YOUR USER NAME\Desktop\cwm
adb shell
su
remount rw
exit
exit
After that, run the run.bat from the folder.
Click to expand...
Click to collapse
Excuse the stupid question please, do I have the sdcard mounted, or unmounted? I heard it can be done either way...
The only thing you use Odin for is to flash a complete .tar file. Ie, returning to stock, or updating to a new release DG27, DI07, or DI18
sniperkill said:
Excuse the stupid question please, do I have the sdcard mounted, or unmounted? I heard it can be done either way...
Click to expand...
Click to collapse
Make sure it is NOT mounted as a mass storage device. Make sure you can access it from the phone. So, don't mount it.
LSanna1488 said:
The only thing you use Odin for is to flash a complete .tar file. Ie, returning to stock, or updating to a new release DG27, DI07, or DI18
Click to expand...
Click to collapse
Technically, custom ROMs can be made for Odin, too... But since it's not a very good method, everyone prefers the recovery method. noobnl released his first rooted kernel for Odin. Odin does a lot more than just complete .tars.
LSanna1488 said:
The only thing you use Odin for is to flash a complete .tar file. Ie, returning to stock, or updating to a new release DG27, DI07, or DI18
Click to expand...
Click to collapse
I ran the commands as you stated, then ran the exploit. It keeps saying,
"remove stock recovery patcher"
"device not found"
system (something) install recovery.sh permission denied
"system/recovery-from-boot.p permission denied
failed to copy 'zImage' to /sdcard/zImage: permission denied
reboot: operation not permitted
im failed for /sdcard/zImage, permission denied
So what do you think is going on? Any thoughts?
I had same exact issue. Went back to completely stock then rooted then did clockwork. Do not mount sd card. Follow instructions exactly.
Sent from my SPH-D700 using XDA App
I'm having the same issue. When trying to 'su' to do the remount I'm getting a permission denied... but apps that require root seem to be working.
sniperkill said:
I ran the commands as you stated, then ran the exploit. It keeps saying,
"remove stock recovery patcher"
"device not found"
system (something) install recovery.sh permission denied
"system/recovery-from-boot.p permission denied
failed to copy 'zImage' to /sdcard/zImage: permission denied
reboot: operation not permitted
im failed for /sdcard/zImage, permission denied
So what do you think is going on? Any thoughts?
Click to expand...
Click to collapse
Is your phone in debug mode? (Settings -> Applications -> Development -> USB Debugging) Did it actually let your run those commands I told you?
Yes, my phone is in fact in debugg mode. My desktop command prompt does let me run the commands.
Adb devices
Adb shell
Su #
Remount rw
Exit
Exit
After I type the command "su" it gives me the #. Then on my phone a superuser request comes thru and askes to chose "yes" or "no". So I hit "yes". But when I run the exploit in the beginning it says "mount", and it says that the operation is not permitted... then it starts saying "I'm failed for" and "operation not permitted" and so on.. I think I'm missing a step somewhere but I don't kno...
Sent from my SPH-D700 using XDA App
Running su through adb shouldn't ask for permission the phone... that is weird.
Sent from my SPH-D700 using XDA App
I spent the weekend trying to get my Epic rooted and cwm installed. I was finally successful with both. CWM I had to install by typing in each command that was in the bat through the cmd window with adb.
Flak said:
I spent the weekend trying to get my Epic rooted and cwm installed. I was finally successful with both. CWM I had to install by typing in each command that was in the bat through the cmd window with adb.
Click to expand...
Click to collapse
So exactly what are the steps you took to install clockworkmod manually through windows command prompt? Do I just look in the bat exploit?
OK. I have been searching all over the place, and there were solutions, but my phone will not listen to me.
Instructions
1)Download and extract the file below
2)Use a terminal emulator or ADB shell and type.. (or you can use Root Explorer or SGSTools to mount system RW)
Code:
mount -o rw,remount /dev/block/stl9 /system
3)Use a file manager like Root Explorer and copy the recovery file to /system/bin and replace the one there
4)Now, reboot and you should have a modded 3e recovery with no signature verification
Click to expand...
Click to collapse
On the 2nd part, it will not allow me to mount -o rw,remount /dev/block/stl9 /system.
The terminal emulator is not receiving the "superuser permission", since it's not even asking for the superuser permission.
I did not deny the app nor ignore. I tried reinstalling the terminal emulator, same thing happens.
Also I downloaded ROM Manager. It downloaded me the flashclockworkmod recovery, but it will not reboot into that. Instead it shows the regular recovery mode, and when I try to install the update.zip manually, the error shows again despite the fact that I did all the parts except the 2nd step, because my terminal emulator kept getting denied access when I entered that in.
Please help me. I don't know what hard life my phone is going through.
Asked and answered many times. You could have posted in an existing thread. If your phone is not rooted you will not be able to do this.
My phone is rooted. It has superuser app, along with other apps that require superuser permissions.
How would I have done step 3 without my phone being rooted? if by using root explorer?
I just stated that Terminal Emulator is not receiving the "superuser permission".
I don't know how to manually give Terminal Emulator the "Superuser permission" since, it is not asking me for it, as previously in Eclair.
Are you entering
Su
Sent from my SGH-I897 using XDA Premium App
? I am sorry, I did not understand what you said.
on my Su, I have
Allow
AdFree
ROM Manager
SGS Tools
because they asked for su permission.
But on the terminal emu, it does not even ask for a su permission.
to do unrooted you use adb to push
or root it then use root explorer to drop new 3e fix
try uninstalling terminal em and reinstall. you might have pressed back when it asked the first time, that will screw you
When you mean drop new 3e fix, does that mean to delete file and replace with the updatedone on xda?
I did that previously and rebootseveral times before, but same error came up
Thread closed, already answered.
Anyone know how I can restore to stock recovery? I rooted and flashed CWM recovery, but I need to restore to stock because I am having so many problems with random reboots that I see lots of people are also having problems with. I have downloaded the dump. If someone could tell what I need to do on would be extremely grateful.
Even on stock this thing has issues... Im gonna try and return it for a mytouch 4g instead....
Sent from my SGH-T839 using Tapatalk
Ace42 said:
Even on stock this thing has issues... Im gonna try and return it for a mytouch 4g instead....
Sent from my SGH-T839 using Tapatalk
Click to expand...
Click to collapse
That's my problem too, but I can't send it back until I get the stock recovery back. I installed CWM after I rooted.
see my next post for the 1 click
ehall2k7 said:
That's my problem too, but I can't send it back until I get the stock recovery back. I installed CWM after I rooted.
Click to expand...
Click to collapse
Me too, which is why I regret it now....I want a phone hat I less buggy, this thing crashes all the time which sucks. Also the phone won't get much faster since it doesn't have enough space for the galaxy s lagfix, which applies to this since it has rfs and not ext4 like it needs..
@person above, if we brick it then they would replace it, right? You would just need to do some "acting" in the store and play dumb with the rep, if you know what a mean.
Sent from my SGH-T839 using Tapatalk
I edited noobnl's one click uninstaller for epic4g with what i posted above.
Extreme warning: Untested! I do not know if it will work, use at your own risk. Possibility of bricking you!
This one click SHOULD
1. remove root and replace with original files
2. reflash stock bml8 over modified? one (I think CWM is bml8)
Theoretically it shouldnt brick you, but no guarantees.....
If anybody has the guts to test this let me know
updated to Here
http://forum.xda-developers.com/showthread.php?t=803682
that is the link to SuperOneClick its a Root app that you can also use to unroot the device.. i Haven't Received my other SK4G yet to test but it should work its universal and works on multiple phones.
hopefully those that have root can use this method to unroot
blu9987 said:
I edited noobnl's one click uninstaller for epic4g with what i posted above.
Extreme warning: Untested! I do not know if it will work, use at your own risk. Possibility of bricking you!
This one click SHOULD
1. remove root and replace with original files
2. reflash stock bml8 over modified? one (I think CWM is bml8)
Theoretically it shouldnt brick you, but no guarantees.....
If anybody has the guts to test this let me know and i'll post a thread in the dev forum
edit: updated the zip due to a silly error
edit2: in the off chance that you get "mount: operation not premitted" that means it failed to mount /system as rw and wont remove superuser. If you let it continue it will still flash over bml8 though. You can manually remove superuser another way. My phone was only permitting me to mount by
Code:
adb shell
su
(look on phone press allow for superuser popup)
remount rw
then removing all the files using these commands
Code:
adb shell rm /system/bin/joeykrim-root.sh (most likely not there this is old)
adb shell rm /system/bin/jk-su (same as above)
adb shell rm /etc/passwd (pretty sure this isnt here either)
adb shell rm /etc/group (same)
adb shell rm /system/bin/su
adb shell rm /system/xbin/su
adb shell rm /system/app/Superuser.apk
adb push playlogo /system/bin/playlogo
adb shell chmod 755 /system/bin/playlogo
adb shell rm /etc/resolv.conf
adb shell rm /system/bin/remount
adb shell rm /system/bin/busybox
Not saying that you'll have to do that could just be my phone since im on ext4 and such.
Click to expand...
Click to collapse
I'll try it out in the next few hours and let you know. I'm not worried if it bricks cuz I'm still in the 14 days to return it and have had nothing but problems with it random rebooting. I'll let you know. Thanks again.
ehall2k7 said:
I'll try it out in the next few hours and let you know. I'm not worried if it bricks cuz I'm still in the 14 days to return it and have had nothing but problems with it random rebooting. I'll let you know. Thanks again.
Click to expand...
Click to collapse
Just to give a heads up a bricked device will stay at the splash screen or may not even turn on, so it will be hard for them to know.I wish this phone was better, since I wanted I ever since I heard it was being remade by sammy.
Sent from my SGH-T839 using Tapatalk
blu9987 said:
I edited noobnl's one click uninstaller for epic4g with what i posted above.
Extreme warning: Untested! I do not know if it will work, use at your own risk. Possibility of bricking you!
This one click SHOULD
1. remove root and replace with original files
2. reflash stock bml8 over modified? one (I think CWM is bml8)
Theoretically it shouldnt brick you, but no guarantees.....
If anybody has the guts to test this let me know and i'll post a thread in the dev forum
edit: updated the zip due to a silly error
edit2: in the off chance that you get "mount: operation not premitted" that means it failed to mount /system as rw and wont remove superuser. If you let it continue it will still flash over bml8 though. You can manually remove superuser another way. My phone was only permitting me to mount by
Code:
adb shell
su
(look on phone press allow for superuser popup)
remount rw
then removing all the files using these commands
Code:
adb shell rm /system/bin/joeykrim-root.sh (most likely not there this is old)
adb shell rm /system/bin/jk-su (same as above)
adb shell rm /etc/passwd (pretty sure this isnt here either)
adb shell rm /etc/group (same)
adb shell rm /system/bin/su
adb shell rm /system/xbin/su
adb shell rm /system/app/Superuser.apk
adb push playlogo /system/bin/playlogo
adb shell chmod 755 /system/bin/playlogo
adb shell rm /etc/resolv.conf
adb shell rm /system/bin/remount
adb shell rm /system/bin/busybox
Not saying that you'll have to do that could just be my phone since im on ext4 and such.
Click to expand...
Click to collapse
I tried it and still no luck. Here is what I am seeing:
one click uninstaller based off of noobnl's
Press any key to continue . . .
copy and run the exploit (may take 2 minutes)
84 KB/s (0 bytes in 5392.000s)
2 KB/s (0 bytes in 88.000s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={2650, 2650}
[*] Searching for adb ...
[+] Found adb as PID 2390
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] 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.
remove joeykrim root method
mount: Operation not permitted
rm failed for /system/bin/joeykrim-root.sh, Read-only file system
rm failed for /system/bin/jk-su, Read-only file system
rm failed for /etc/passwd, Read-only file system
rm failed for /etc/group, Read-only file system
rm failed for /system/bin/su, Read-only file system
rm failed for /system/xbin/su, Read-only file system
rm failed for /system/app/Superuser.apk, Read-only file system
failed to copy 'playlogo' to '/system/bin/playlogo': Read-only file system
Unable to chmod /system/bin/playlogo: Read-only file system
rm failed for /etc/resolv.conf, Read-only file system
rm failed for /system/bin/remount, Read-only file system
rm failed for /system/bin/busybox, Read-only file system
copy recovery and flasher
384 KB/s (0 bytes in 313888.000s)
495 KB/s (0 bytes in 7864320.015s)
flashing recovery
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/bml8.bin
dst: /dev/block/bml8 partition size: 0x0
part_size: 0x0
reboot: Operation not permitted
wait 60 second
cleanup
done
Press any key to continue . . .
Do you think it would be possible to flash the bml8.bin with ODIN? I haven't tried to go into download mode but it should be possible seeing how its almost identical to the vibrant and it's made by samsung.
I wonder if this has a bootloader like htc devices where you can flash system images which have the stock recovery, or if the system dump has it, then we can do.. flash recovery /sdcard/xxx.img from term or adb or fastboot, which ever one.
Sent from my SGH-T839 using Tapatalk
you can try making your filesystem r/w before running it.. I dunno why its not mounting properly with adb...
you all have usb debugging enabled right?
Open up command prompt,
cd C:\path\to\uninstaller
adb shell
su
(check prompt on screen superuser)
mount -o remount,rw /dev/block/stl9 /system
then just click the run.bat while the first window is still open
Also before trying this try clearing data on superuser.apk on your phone
You can also try remounting to RW on your phone with like root explorer or terminal emulator... I honestly have no idea why adb keeps getting permission denied
blu9987 said:
you can try making your filesystem r/w before running it.. I dunno why its not mounting properly with adb...
you all have usb debugging enabled right?
Open up command prompt,
cd C:\path\to\uninstaller
adb shell
su
(check prompt on screen superuser)
remount rw
then just click the run.bat while the first window is still open
Also before trying this try clearing data on superuser.apk on your phone
You can also try remounting to RW on your phone with like root explorer or terminal emulator... I honestly have no idea why adb keeps getting permission denied
Click to expand...
Click to collapse
Okay so the original recovery is located on a different part, which CWM doesnt write to, allowing the old one to be used again using this method, correct?Just want to better understand how it works.
Ace42 said:
Okay so the original recovery is located on a different part, which CWM doesnt write to, allowing the old one to be used again using this method, correct?Just want to better understand how it works.
Click to expand...
Click to collapse
I'm pretty sure clockworkmod one click you guys used flashed CWM recovery to /dev/block/bml8 so this restores the original bml8 image
and heres a copy paste from the dump thread
Code:
bml4 1280 KB contains Sbl.bin (1310720 bytes) Secondary Boot Loader (loads the Linux kernel and passes the necessary arguments)
bml5 1280 KB contains Secondary Boot Loader (for recovery, ect)
bml8 7680 KB empty - on Epic 4G and Fascinate, contains recovery.bin
And since you all used the epic recovery flasher, i concluded that it probably flashed bml8 and that you just replace it with the stock bml8 ya?
Also the epic recovery flasher pushes recovery files into /system/bin which need to be removed and I realised that I didnt include that in the one click uninstaller *facepalm*
blu9987 said:
I'm pretty sure clockworkmod one click you guys used flashed CWM recovery to /dev/block/bml8 so this restores the original bml8 image
and heres a copy paste from the dump thread
Code:
bml4 1280 KB contains Sbl.bin (1310720 bytes) Secondary Boot Loader (loads the Linux kernel and passes the necessary arguments)
bml5 1280 KB contains Secondary Boot Loader (for recovery, ect)
bml8 7680 KB empty - on Epic 4G and Fascinate, contains recovery.bin
And since you all used the epic recovery flasher, i concluded that it probably flashed bml8 and that you just replace it with the stock bml8 ya?
Also the epic recovery flasher pushes recovery files into /system/bin which need to be removed and I realised that I didnt include that in the one click uninstaller *facepalm*
Click to expand...
Click to collapse
Oh I see, well I'll let you know how it turns out then.
Edit: In system /bin I have
-recovery(ukn file type)
-recoveryfiles(folder)
-recoveryres(folder)
Also these "bml" files are in /SYS/BLOCK <--according to root explorer
While /DEV/Block only shows "vold" folder, nvm term shows that bml is there
Ace42 said:
Oh I see, well I'll let you know how it turns out then.
Edit: In system /bin I have
-recovery(ukn file type)
-recoveryfiles(folder)
-recoveryres(folder)
Also these "bml" files are in /SYS/BLOCK <--according to root explorer
While /DEV/Block only shows "vold" folder, nvm term shows that bml is there
Click to expand...
Click to collapse
-recovery(ukn file type) comes with the stock system but the one click installer pushed over a modified one. Youd need to replace with the original...I'll add that into the uninstaller
-recoveryfiles(folder) is from the one click installer
-recoveryres(folder) is also from the one click installer
There is also
/system/xbin/remount
and
/system/xbin/busybox
and /system/bin/playlogo (which I already have in the uninstaller..the playlogo they use is what gives permanent root if i remember correctly)
It would be so much easier if somebody on 100% stock would gain temporary root using rageagainstthecage and root.sh and pull the images for a tar then we can put together a stock flash with factoryfs.rfs cache.fs intram.lfs recovery.bin boot.bin sbl.bin and modem.bin
If anyone is interested pm me and i'll give you the info you need on how to do it
blu9987 said:
-recovery(ukn file type) comes with the stock system but the one click installer pushed over a modified one. Youd need to replace with the original...I'll add that into the uninstaller
-recoveryfiles(folder) is from the one click installer
-recoveryres(folder) is also from the one click installer
There is also
/system/xbin/remount
and
/system/xbin/busybox
and /system/bin/playlogo (which I already have in the uninstaller..the playlogo they use is what gives permanent root if i remember correctly)
It would be so much easier if somebody on 100% stock would gain temporary root using rageagainstthecage and root.sh and pull the images for a tar then we can put together a stock flash with factoryfs.rfs cache.fs intram.lfs recovery.bin boot.bin sbl.bin and modem.bin
If anyone is interested pm me and i'll give you the info you need on how to do it
Click to expand...
Click to collapse
Thr thing is..I'm exchanging mines today so I will try what you said and then do a factory erase afterwards. If it leaves some files there's not much I can do, can you fix he uninstaller to add the other files today, ill really appreciate it.
Sent from my SGH-T839 using Tapatalk
Disregard this post i'll make something and put it up after portfolio is done in a few hours
I have attached a one click uninstaller for root, revised and will work. Just extract and run the run.bat
It should remove all root and reflash stock over clockworkmod!
If this works let me know and i'll post it in its own thread
Shameless triple post:
Anyone end up testing this? It would be highly beneficial if somebody could remove CWM and root, restore to stock, and follow some instructions to pull the necessary images to make an odin tar. I would do this myself but I don't have a sidekick. Or maybe once we get a working CWM make a pre-rooted odin flash
EXPLOIT NO LONGER WORKING DUE TO OTA UPDATE. BE WARNED.
Thanks to beaups for his exploit!
Download the zip file below, unzip it somewhere, run root.bat with your phone plugged in and usb debugging enabled. Currently this is for windows only.
Includes a fully working su binary and Superuser.apk, make sure to update the su binary the first time you run SuperSu!
Follow the instructions on the screen, they are very simple, only one thing to do!
Download:
http://www.gigashare.in/738af
HELP SECTION:
After you are rooted, I strongly suggest you unlock your bootloader immediately!!
http://briefmobile.com/how-to-unlock-att-one-x-bootloader
Make sure HTC sync is NOT RUNNING (down in system tray)
Make sure phone is set to "charge only" and usb debugging is enabled!
Make sure Wifi is enabled and connected! (seems to help, but not required)
If you are stuck at "waiting for device to reboot" for a long time or you get "/data/local.prop was not created, exit the script, try again." followed by lots of junk, reboot your phone and push your clock forward two days, reboot, and try again.
If the update fails to check for updates, reboot your phone and push your clock forward two days, reboot, and try again.
usb drivers, if you need them: http://binary100100.googlecode.com/files/HTCDriver3.0.0.007.exe
You're the man and you know this...
Sent from my HTC One X using Tapatalk 2
Damn. I'm already rooted yet disappointed I can't be part of this . Lol well Friday I will be donating like I said I would. Good job
Sent from my HTC One X using xda premium
Great work! Wonder how long this will last.
Sent from my HTC One X using xda premium
Pure awesomeness, worked make sure you let it reboot a few times, I think mine rebooted 3 or 4, I just left it in the cradle. I now have root
Pumpiron579 said:
Pure awesomeness, worked make sure you let it reboot a few times, I think mine rebooted 3 or 4, I just left it in the cradle. I now have root
Click to expand...
Click to collapse
should only reboot twice
I got this error when I tried it.
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
/data/local.prop was not created, exit the script, try again.
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rm failed for /data/local.prop, Permission denied
Done! Rebooting...
Press any key to continue . . .
Any suggestions?
StrykerGT said:
I got this error when I tried it.
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
/data/local.prop was not created, exit the script, try again.
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rm failed for /data/local.prop, Permission denied
Done! Rebooting...
Press any key to continue . . .
Any suggestions?
Click to expand...
Click to collapse
check out the bolded part
kick the date forward two days and reboot your phone, run the script again
you might have to do that a couple times...
designgears said:
should only reboot twice
Click to expand...
Click to collapse
Is that taking into account the unstableness and the potential for it to spontaneously reboot on its own?
Mine doesn't get past "waiting for device to reboot"
Thanks for the script sir!
skatin707 said:
Mine doesn't get past "waiting for device to reboot"
Click to expand...
Click to collapse
well, its waiting for the update process to create files, once it does it will reboot, if it sits there to long, reboot your phone and try again
designgears said:
should only reboot twice
Click to expand...
Click to collapse
mine rebooted once after checking for update, but when it ran all the code, prior to rebooting, i got errors in the code. looked and no SU on my phone. not sure what i did wrong. didn't reboot the first time, so i pushed the date ahead two days and then it did with the code that everyone is reporting.
designgears said:
well, its waiting for the update process to create files, once it does it will reboot, if it sits there to long, reboot your phone and try again
Click to expand...
Click to collapse
I'll keep waiting, it hasn't even been 10 minutes.
hahaha...that was magical!!!! works!!!!
skatin707 said:
I'll keep waiting, it hasn't even been 10 minutes.
Click to expand...
Click to collapse
did you run the updater on the phone? if it is completed or still spinning after a few min just reboot and try again.
skatin707 said:
I'll keep waiting, it hasn't even been 10 minutes.
Click to expand...
Click to collapse
I set my date ahead and turned on my WiFi, checked for updates and it rebooted right away.
love you guys.
designgears said:
check out the bolded part
kick the date forward two days and reboot your phone, run the script again
you might have to do that a couple times...
Click to expand...
Click to collapse
Thanks! I didn't read the message. I'm an idiot.
Rooted! Woot!
So the next step is to follow these instructions right?
http://forum.xda-developers.com/showthread.php?t=1671396
beppomarx said:
heres what i get... i did get the reboot after checking for updates though.
Exploit by beaups, script by designgears
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
32 KB/s (334 bytes in 0.010s)
rm failed for /data/data/com.redbend.vdmc/lib/libvd*, No such file or directory
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
/data/local.prop was not created, exit the script, try again.
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rm failed for /data/local.prop, Permission denied
Done! Rebooting...
Press any key to continue . . .
Click to expand...
Click to collapse
reboot and try again! push your clock up two days.
StrykerGT said:
Thanks! I didn't read the message. I'm an idiot.
Rooted! Woot!
So the next step is to follow these instructions right?
http://forum.xda-developers.com/showthread.php?t=1671396
Click to expand...
Click to collapse
YUP! but there is a one click for that too
HTC Inspire 4G - AT&T
Android - Stock GB 2.3.5 + HTC Sense 3.0
Build - 3.20.502.52
PC OS - Windows XP Pro SP3
Method - Easy Ace Root Tool
Noob - Yes
Problem - Bootloader unlock successfully achieved, but installation of BusyBox, Clockworkmod, and SuperUser interrupted during process.
Text from Post-Unlock on shown below. Trouble Areas Colored Red
Summary of Problem according to Tool - "Parameter Format not correct," "Read-Only file system," and "No such file or directory"
USB Debugging and Unknown Sources enabled when errors occur
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
< waiting for device >
sending 'recovery' (3554 KB)... OKAY [ 0.641s]
writing 'recovery'... OKAY [ 0.953s]
finished. total time: 1.594s
rebooting...
finished. total time: 0.297s
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Make sure that USB debugging is enabled and charge only is set as default
Achieving Temp Root
cannot stat '/tools/tmp/fre3vo': No such file or directory
Unable to chmod /data/local/tmp/fre3vo: No such file or directory
/data/local/tmp/fre3vo: not found
Pushing Busybox, SU and Superuser
1 KB/s (536 bytes in 0.312s)
1829 KB/s (380532 bytes in 0.203s)
1906 KB/s (1372660 bytes in 0.703s)
Trying to gain Perm Root
mount: permission denied (are you root?)
/system/xbin/busybox: cannot open for write: Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'tools\su\su' to '/system/bin/su': Read-only file system
failed to copy 'tools\su\Superuser.apk' to '/system/app/Superuser.apk': Read-onl
y file system
Unable to chmod /system/bin/su: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
FIND: Parameter format not correct
rm failed for EasyAceRoot.cmd, No such file or directory
Perm Root achieved...
I too am looking for the answer. I'll edit this post if I find something
If CWM would install, that wouldn't be a problem
Scozzar said:
I too am having this issue at the moment. The bootloader is unlocked, but I will not get perm root, even though it says it was achieved...
EDIT: Turning off Fastboot yields different results. But still no SuperSU.
EDIT2: I GOT IT! Basically, I downloaded the latest SuperSU .zip off XDA, put it on the phone, then flashed it in CWM. SuperSU now appears as an app!
Click to expand...
Click to collapse
I'll try turning off fastboot, but I can't get CWM to install at the moment either. SuperSU and Busybox also can't install.
Again, I'll try turning fastboot off and see how it behaves.
Prestige0813 said:
I'll try turning off fastboot, but I can't get CWM to install at the moment either. SuperSU and Busybox also can't install.
Again, I'll try turning fastboot off and see how it behaves.
Click to expand...
Click to collapse
What have you done? Also, you can't turn off fastboot; it's a mode selected from the bootloader. Do you mean ADB? Turning that off won't do anything either, other than making your phone's system inaccessible from the computer.
Scozzar said:
Fastboot, as in the check box in the stock ROM. You can't get into bootloader with it on. Also, if I was able to flash a new ROM, does that mean busybox is installed?
Click to expand...
Click to collapse
Depends on the ROM.
Scozzar said:
V2 Oxygen JB is what I'm using.
Click to expand...
Click to collapse
Er, I don't know for every ROM. If it's a custom ROM, probably. If you're rooted (and again, if you're using a custom ROM, you probably are), you can always install it from the play store.
Update:
First off, I've already downloaded the SuperSU App from Google Play, and it's failed to obtain root abilities, so a perm root is not being acheived.
Also, I've downloaded the latest SuperSU via PC, and it's ready to go once I manage to successfully install CWM (however, if the Ace Root Kit succeeds, then using CWM to install root isn't a needed method)
I've tried continuing the process with the Fastboot setting disabled, and I didn't see any difference in the end result. It seems that recovery is successfully written, but it doesn't succeed in installing SuperSU, CWM, or busybox.
On another note, I've downloaded the busybox installer app from Google Play, and it states the phone is rooted; but runs into errors when I attempt to install (regardless of the version I select). I've run two root checking apps, and both say that the phone is not rooted.
In short, All I've been able to achieve is getting the Boot Loader unlocked.
Can you flash recovery manually from fastboot?
New Update
I just found that CWM is in fact installed. I did not realize until just now that from the HTC bootloader I had to select recovery to access it.
I placed the SuperSU.zip on the phone and installed it via CWM, as scozzar had suggested, and the phone is now rooted (verified by two root checking apps)!
From there I installed busybox via Google Play with no hiccups.
I apologize for not trying this sooner I hope that others find success. The Inspire's a great phone, and now I've made mine even better!
Yess
bananagranola said:
Can you flash recovery manually from fastboot?
Click to expand...
Click to collapse
Yes! here is the tutorial
1- Download Android.zip and unzip it
2- make a folder called "Android" in C:/ like that: C:/Android.
3- put inside of the folder Android the files: adb.exe, fasttboot.exe, AdbWinApi.dll and the recovery.img
4- go to cmd and write:
cd \Android
fastboot flash recovery recovery.img
READY! now you have a CWM Recovery
Sorry for my bad english