Database Info

[Q] Restore Root - Stuck

Hopefully someone can help me out on this one because I'm not quite sure what to do at this point. I have a G2x that was having multiple issues so I decided to root and install clockworkmod recovery so that I could flash CM7RC1. I flash CM7RC1 successfully but failed to realize that I did not properly install CWM as I accessed it via ROM manager (lack of proper reading on my part). Since going to CM7RC1 I've lost root and am unable to use Super One Click 1.9.1.0 to get it back. I seem to have lost all Linux commands (ls won't even work through the terminal emulator) so when Super One Click runs it says FAIL as it cannot chmod or mount. If you have any idea on how I can restore root or CWM let me know. Thanks!
Output from Super One Click
SuperOneClick v1.9.1.0
Checking drivers...
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Getting OS Version...
2.3.4
OK
2.3.4
Pushing GingerBreak...
249 KB/s (16830 bytes in 0.066s)
OK
chmod GingerBreak...
chmod: no such tool
OK
Running GingerBreak...
ROOTED
Pushing busybox...
1817 KB/s (1062992 bytes in 0.571s)
OK
chmod busybox...
chmod: no such tool
OK
Getting mount path...
mount: no such tool
FAILED

Wrong section
Post in Q&A

Moved to proper section.

Epic Fail! Your Soul Is Mine!
Sent from my LG-P999 using XDA Premium App

HA! Well be that as it may, is there anything I can do...or am I stuck?

Fixed the issue by NVFlashing Clockworkmod recovery with TGA_Gunnman's excellent one-click utility. After that it was easy to restore the backup I had made.

Issue with 1.85 One-Click Root

I'm too new of a member to be able to post my issue in that forum so I will post it here.
I got to the point where It checked for updates on the phone, then starts to reboot, and during the reboot the program continues and starts giving more errors. I didn't see a similar issue in the thread that pertained to my particular issue. Here is the error I'm getting :
Exploit by beaups, script by designgears
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
46 KB/s (334 bytes in 0.007s)
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 created, looking good.
remount succeeded
3905 KB/s (91980 bytes in 0.023s)
5023 KB/s (1116332 bytes in 0.217s)
rm failed for /system/app/Superuser.apk, No such file or directory
4918 KB/s (574184 bytes in 0.114s)
Error: Could not access the Package Manager. Is the system running?
Unable to chmod /system/app/Superuser.apk: No such file or directory
Done! Rebooting...
Press any key to continue . . .
I'm assuming the root didn't work. How would I know? Any ideas?
Thanks

Znichols513 said:
I'm too new of a member to be able to post my issue in that forum so I will post it here.
I got to the point where It checked for updates on the phone, then starts to reboot, and during the reboot the program continues and starts giving more errors. I didn't see a similar issue in the thread that pertained to my particular issue. Here is the error I'm getting :
Exploit by beaups, script by designgears
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
46 KB/s (334 bytes in 0.007s)
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 created, looking good.
remount succeeded
3905 KB/s (91980 bytes in 0.023s)
5023 KB/s (1116332 bytes in 0.217s)
rm failed for /system/app/Superuser.apk, No such file or directory
4918 KB/s (574184 bytes in 0.114s)
Error: Could not access the Package Manager. Is the system running?
Unable to chmod /system/app/Superuser.apk: No such file or directory
Done! Rebooting...
Press any key to continue . . .
I'm assuming the root didn't work. How would I know? Any ideas?
Thanks
Click to expand...
Click to collapse
Check your app drawer for SuperSU. If it's there click it and see if you can update the binary. If you can, you're rooted. If you can't or if it's not there than you need to repeat the process until it works.

_MetalHead_ said:
Check your app drawer for SuperSU. If it's there click it and see if you can update the binary. If you can, you're rooted. If you can't or if it's not there than you need to repeat the process until it works.
Click to expand...
Click to collapse
Ok. It is there and it asked me to update, and that part worked. So... I guess I'm rooted then? I can move on to the bootloader unlocking then?

Znichols513 said:
Ok. It is there and it asked me to update, and that part worked. So... I guess I'm rooted then? I can move on to the bootloader unlocking then?
Click to expand...
Click to collapse
Yep, youre rooted. Now go and get that bootloader unlocked and flash CleanROM!

Okay so I rooted and unlocked BL. I also used fastboot to flash CWM, but when I try to boot into recovery, it just gets stuck on the "HTC Quietly Brilliant" page and a message in red text underneath.
I've tried reflashing it a few times and no results.

Hello,
Try downloading Goomanager in Google Play and going to "options" install recovery script, it isn't CWM but I actually like it much more. Good Luck

ryan9316 said:
Hello,
Try downloading Goomanager in Google Play and going to "options" install recovery script, it isn't CWM but I actually like it much more. Good Luck
Click to expand...
Click to collapse
This worked. Thanks a lot!

[Q] Rooting with OSX

Im Looking to root my Verizon GS3. only catch is im using OSX, OSX doesn't seem to be highly supported in the android realm. I found a thread on androidcentral about 'mac-root-tool-s3-casual-verizon-s3'
so my question is since that thread seems a bit dead, is will this work with build, VRALHE?

(For Mac/Linux/*Windows) How to install Adam Outler's Casual for Rooting/Unlocking Bootloader/CWM recovery
*This method does not work for VRBLI5/J1/K1 JellyBean
* I have successfully installed and ran Casual on Windows 7, but I recomend Windows users refer to section 1 of my guide
*More Information on Casual can be found HERE
Step 1: Download and install these files to your pc:
Samsung driver- http://tinyw.in/Fdoz
Adam Outler's Casual- http://d-h.st/ypJ
Java JDK-http://www.oracle.com/technetwork/java/javase/downloads/jdk-7u4-downloads-1591156.html(Should only be needed for windows users)
Step 2: On your device, Make sure USB Debugging(settings/developer options/usb debugging) and Install of Unknown Sources(settings/security/unknown source) is checked.(Also, make sure there are no other android devices, emulators, or any tethering programs running!!).
Step 3: Open the Casual file you downloaded in step1. you should here a voice say "casual", then the program should open.
Step 4: While fully booted up into android, connect the pc to the device using the oem usb cable. Casual should come up in green letters saying "device connected".
Step 5: Congrats, you are now ready to flash away.
Step 6: If you are not currently rooted, then flash DebugFSroot first, DO IT!
Step 7: Next flash unsecure aboot to unlock bootloader, DO IT!
Step 8: Finally flash ClockWork Mod Recovery(it should be version cwm 6.0.1), DO IT!

It works!
Everything works fine! i was able to root, i used EZ-unlock from the play store instead, but i was able to Load CM10 successfully onto it.
Thanks!

I wish I saw this post earlier

Replacement Phone
So are we sure that Casual still works for the "VRALHE" update? I just got a replacement phone today that ran this version and I'm not having any luck. I ran Casual on my phone when it first came out without a hitch. This time around it just gets stuck on: "Copying Su:" any ideas?
Edit: After a couple of restarts I made it past that stage and I'm faced with an error at the end...
"tep 1 - Setup...
Copying files:
Copying su:1147 KB/s (380532 bytes in 0.323s)
Copying debugfs:987 KB/s (1862336 bytes in 1.841s)
Copying debugfsinput:44 KB/s (144 bytes in 0.003s)
...done copying files.
Linking /system to tmp...
...done linking /system
Rebooting...
Step 2 - Rooting...* daemon not running. starting it now on port 5037 *
* daemon started successfully *
debugfs 1.42 (29-Nov-2011)
debugfs: debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: debugfs: debugfs:
debugfs: Allocated inode: 2144
debugfs: debugfs: debugfs: debugfs:
Cleaning up...
Restoring tmp...
...done restoring tmp
Removing files...protocol failureerror: device not found
done. "

sspediacci said:
So are we sure that Casual still works for the "VRALHE" update? I just got a replacement phone today that ran this version and I'm not having any luck. I ran Casual on my phone when it first came out without a hitch. This time around it just gets stuck on: "Copying Su:" any ideas?
Edit: After a couple of restarts I made it past that stage and I'm faced with an error at the end...
"tep 1 - Setup...
Copying files:
Copying su:1147 KB/s (380532 bytes in 0.323s)
Copying debugfs:987 KB/s (1862336 bytes in 1.841s)
Copying debugfsinput:44 KB/s (144 bytes in 0.003s)
...done copying files.
Linking /system to tmp...
...done linking /system
Rebooting...
Step 2 - Rooting...* daemon not running. starting it now on port 5037 *
* daemon started successfully *
debugfs 1.42 (29-Nov-2011)
debugfs: debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: debugfs: debugfs:
debugfs: Allocated inode: 2144
debugfs: debugfs: debugfs: debugfs:
Cleaning up...
Restoring tmp...
...done restoring tmp
Removing files...protocol failureerror: device not found
done. "
Click to expand...
Click to collapse
I don't know why this worked or why I thought of it, but I installed Samsung Kies and restarted my computer just for ****s and giggles. After that it rooted, flashed the unsecure bootloader, and flash CWM without a hitch.

droidstyle said:
(For Mac/Linux/*Windows) How to install Adam Outler's Casual for Rooting/Unlocking Bootloader/CWM recovery
*This method does not work for VRBLI5/J1/K1 JellyBean
* I have successfully installed and ran Casual on Windows 7, but I recomend Windows users refer to section 1 of my guide
*More Information on Casual can be found HERE
Step 1: Download and install these files to your pc:
Samsung driver- http://tinyw.in/Fdoz
Adam Outler's Casual- http://d-h.st/ypJ
Java JDK-http://www.oracle.com/technetwork/java/javase/downloads/jdk-7u4-downloads-1591156.html(Should only be needed for windows users)
Step 2: On your device, Make sure USB Debugging(settings/developer options/usb debugging) and Install of Unknown Sources(settings/security/unknown source) is checked.(Also, make sure there are no other android devices, emulators, or any tethering programs running!!).
Step 3: Open the Casual file you downloaded in step1. you should here a voice say "casual", then the program should open.
Step 4: While fully booted up into android, connect the pc to the device using the oem usb cable. Casual should come up in green letters saying "device connected".
Step 5: Congrats, you are now ready to flash away.
Step 6: If you are not currently rooted, then flash DebugFSroot first, DO IT!
Step 7: Next flash unsecure aboot to unlock bootloader, DO IT!
Step 8: Finally flash ClockWork Mod Recovery(it should be version cwm 6.0.1), DO IT!
Click to expand...
Click to collapse
when i download first link it downloads a windows file that doesnt open on mac
i know old thread but if some one can point me into the direction of a new thread or answers for a mac that would be great

You don't need the drivers for Mac. I think you will have to downgrade your software to stock ICS in order to root with your Mac using Casuals.

HHF2 said:
You don't need the drivers for Mac. I think you will have to downgrade your software to stock ICS in order to root with your Mac using Casuals.
Click to expand...
Click to collapse
And is there a download for that? You'll have to excuse my ignorance, I haven't had an android phone since the htc evo was out. I have been on iPhone. But trying to maybe go back to android with s3

I *THINK* that Casual works for the verizon galaxy sIII again... anybody try it yet?

Lost Root after Safestrap Recovery

I have a Droid Razr Maxx HD on 4.1.2 which I easily rooted with Motochopper a few days ago. I installed Safestrap and all went well. I did a recovery of the stock ROM from a backup that was made only a few hours before. All went well except that I lost Root. I am unable to get root back through Motochopper or VooDoo. I tried restoring without wiping anything and also wiping everything. I also tried with two older rooted backups. Safestrap is still available on boot and I can still use it for recovery. I have tried restoring the backups and using Motochopper numerous times over the past few days but cannot get root again.
Next, using Safestrap, I created a Rom Slot-1 and restored my stock backup to it. When I boot from Slot-1 one I get my system back plus I have root again. Only problem is that the system storage is low in that slot even though I chose the 3gb option (I have a lot of apps). Everything is also sluggish running from Slot-1. I can't figure out why I can't get root in the Stock slot when I wipe it and restore, but I get it in Slot 1 with the same backup restored.
How can I restore the stock ROM from my backup and keep root? Any help would be very much appreciated!
Here's what I get when trying to re-root with Motochopper:
[*][*] Motochopper: Android root exploit (Windows version)[*] v1.0[*] by Dan Rosenberg (@djrbliss)[*][*] Tested on the Motorola Razr HD, Razr M, Razr Maxx HD, and Atrix HD.[*] Supports lots of other devices as well. [*][*] Before continuing, ensure that USB debugging is enabled, that you[*] have the latest USB drivers installed, and that your phone[*] is connected via USB.[*][*] WARNING: This will likely void the warranty on your device. I am[*] not responsible for any damage to your phone as a result using this[*] tool.[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*][*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *[*] Device found.[*] Pushing exploit...
3819 KB/s (1283460 bytes in 0.328s)[*] Pushing root tools...
3822 KB/s (366952 bytes in 0.093s)
3765 KB/s (1867568 bytes in 0.484s)
3794 KB/s (1578585 bytes in 0.406s)
pkg: /data/local/tmp/Superuser.apk
Success[*] Rooting phone...
[+] This may take a few minutes.
[+] Success!
sh: /system/xbin/busybox: not found
cp: /system/xbin/su: No such file or directory[*] Cleaning up...[*] Exploit complete. Press enter to reboot and exit.
Press any key to continue . . .

No one has any ideas or help???

[Q] Problems Rooting Verizon Razr XT912 4.1.2

I have been trying to root my Verizon Razr XT912 running Device Software Version: 98.72.16.XT912.Verizon.en.US with the only tool I can find to use on mac (DROID_RAZR_Utility_Jellybean_XT912_WinMacLin) and I keep getting the following error. I am not sure what I am doing wrong and this seems like the most knowledgable forum. Can anyone guide me in the right direction? Is it my phone, my OS, my connection? I am pretty certain I followed all the steps exactly and I've searched through all the threads on the forum and most of them say something to the effect of "...then I tried again and it worked". Well I've tried about 15 times over the course of two weeks and nothing worked, I hate to admit defeat... but I need some help. Thanks in advance.
[*] Phase three (this will take a minute)...
failed on '/data/logger' - Permission denied
mkdir failed for /data/logger, File exists
Unable to chmod /data/logger: Operation not permitted
link failed File exists
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase four...
2254 KB/s (543080 bytes in 0.235s)
2961 KB/s (1867568 bytes in 0.615s)
2933 KB/s (476557 bytes in 0.158s)
1841 KB/s (63838 bytes in 0.033s)
[*] Cleaning up...
/system/bin/sh: su: not found
[*] Rebooting...
[*] Exploit complete!

Here's what worked for me
I was having the exact same problem until I ran across this in another forum:
Windows-
-Download the zip file and extract.
-Connect device via USB (Make sure you have the current Moto drivers FIRST!)
-Make sure USB Debug is on
-Make sure you have Smart Actions fully installed, unfrozen and unmodified
-Make sure the phone IS NOT in mass storage mode
-Double click run.bat
For some reason, that fifth line is not included in the batch file's instructions. Once I knew to change from mass storage to camera mode, all went well!