Related
Trying to downgrade...
C:\Program Files (x86)\Android\android-sdk\platform-tools>crackin.bat
"Copying tools"
cannot stat 'busybox': No such file or directory
cannot stat 'flash_image': No such file or directory
cannot stat 'misc1-2.img': No such file or directory
Unable to chmod /data/local/busybox: No such file or directory
Unable to chmod /data/local/flash_image: No such file or directory
"Freeing primary PERM linker"
rm failed for /data/DxDrm/fuse/*, No such file or directory
rm failed for /data/DxDrm/fuse, No such file or directory
rmdir failed for /data/DxDrm/fuse/, No such file or directory
cannot create /data/DxDrm/fuse: directory nonexistent
Unable to chmod /data/DxDrm/fuse: No such file or directory
"Freeing secondary PERM linker"
rmdir failed for /data/DxDrm/fuse/, No such file or directory
rmdir failed for /data/DxDrm, No such file or directory
link failed Permission denied
"Rebooting to normal mode to unlock CHMOD links"
rmdir failed for /data/dontpanic, Permission denied
rm failed for /data/DxDrm, No such file or directory
link failed File exists
link failed Permission denied
"Rebooting to normal mode to downgrade ROM"
/dev/mtd/mtd0: Permission denied
/data/local/busybox: not found
/data/local/flash_image: not found
"Freeing links"
rm failed for /data/DxDrm, No such file or directory
rm failed for /data/dontpanic, Permission denied
PATH: C:\Program Files (x86)\Android\android-sdk\tools
Copied the hack4legend files to C:\Program Files (x86)\Android\android-sdk\platform-tools & C:\Program Files (x86)\Android\android-sdk\tools
Following this guide:
http://forum.xda-developers.com/showthread.php?t=725430
You have your adb and crackin.bat in the folder " /android-sdk/platform-tools"
And it looks like the other files (line 3 - 5) are in another folder.
Assuming you followed the instructions exactly, you probably extracted those files into "/android-sdk/tools"?
If so, just copy all files from "/android-sdk/platform-tools" to "/android-sdk/tools" and it should work.
Also, do i need to root HBOOT first?
New error:
C:\Program Files (x86)\Android\android-sdk\tools>crackin.bat
"Copying tools"
1364 KB/s (698452 bytes in 0.500s)
608 KB/s (76044 bytes in 0.122s)
1438 KB/s (655360 bytes in 0.445s)
"Freeing primary PERM linker"
rm failed for /data/DxDrm/fuse/*, No such file or directory
rm failed for /data/DxDrm/fuse, No such file or directory
rmdir failed for /data/DxDrm/fuse/, No such file or directory
cannot create /data/DxDrm/fuse: directory nonexistent
Unable to chmod /data/DxDrm/fuse: No such file or directory
"Freeing secondary PERM linker"
rmdir failed for /data/DxDrm/fuse/, No such file or directory
rmdir failed for /data/DxDrm, No such file or directory
link failed Permission denied
"Rebooting to normal mode to unlock CHMOD links"
rmdir failed for /data/dontpanic, Permission denied
rm failed for /data/DxDrm, No such file or directory
link failed File exists
link failed Permission denied
"Rebooting to normal mode to downgrade ROM"
/dev/mtd/mtd0: Permission denied
cr--rw---- 1 1001 2002 90, 0 Mar 9 14:13 /dev/mtd/mtd0
error writing misc: Permission denied
"Freeing links"
rm failed for /data/DxDrm, No such file or directory
rm failed for /data/dontpanic, Permission denied
- Get visionary+
- Temproot your legend with it
- Use commandline with adb on your pc to flash misc1-2.img.
type the following commands from the folder where you have adb;
Code:
adb shell
su
accept the notification on your phone if one comes up
and then in the command line type this;
Code:
/data/local/flash_image misc /data/local/misc1-2.img
After that you should be able to run the 1.31 RUU
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ su
su
# adb push flash_image /data/local/
adb push flash_image /data/local/
adb: not found
#
Edit:
Is this what suppose to happen?
C:\Program Files (x86)\Android\android-sdk\tools>adb shell
$ su
su
# /data/local/flash_image misc /data/local/misc1-2.img
/data/local/flash_image misc /data/local/misc1-2.img
#
kmtse1 said:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ su
su
# adb push flash_image /data/local/
adb push flash_image /data/local/
adb: not found
#
Edit:
Is this what suppose to happen?
C:\Program Files (x86)\Android\android-sdk\tools>adb shell
$ su
su
# /data/local/flash_image misc /data/local/misc1-2.img
/data/local/flash_image misc /data/local/misc1-2.img
#
Click to expand...
Click to collapse
From what I remember, yes it is.
You can now continue the guide in your first post from the point where you have to insert your gold card into your phone.
Still the same errors...
kmtse1 said:
Still the same errors...
Click to expand...
Click to collapse
Which errors?
The errors you posted in your first post were from running crackin.bat.
That is not necessary after running the steps I posted.
You can skip to the part where you insert your goldcard into your phone and then run the 1.31 RUU.
I get stuck at step 6 http://theunlockr.com/2010/06/07/how-to-load-a-custom-rom-on-the-htc-legend/
No menus load.
So if I understand correctly, you have now already succesfully downgraded (Link as in your first post) and rooted (Link)your phone? Since the link you gave in your last post is for flashing a custom rom, which is the last step in the process.
Oops, no, not downgraded yet - I lost my patience, I will try properly again.
Azaruc said:
So if I understand correctly, you have now already succesfully downgraded (Link as in your first post) and rooted (Link)your phone? Since the link you gave in your last post is for flashing a custom rom, which is the last step in the process.
Click to expand...
Click to collapse
How do I install the RUU to downgrade? I get an error if I run the .exe on my laptop.
Error Code: -5001 : 0x80070002
Error Information:
>SetupNew\setup.cpp (142)
PAPP:
PVENDOR:
PGUID:
$
@Windows 7 / Server 2008 R2 Service Pack 1 (7601)
IE Version: 8.0.7601.17514
Have you installed HTC Sync v2.0.33 ?
Download here
You need this version of HTC Sync, so if you have a newer version, uninstall that version first.
Once installed, run the RUU again (you might need to run it as admin).
Azaruc said:
Have you installed HTC Sync v2.0.33 ?
Download here
You need this version of HTC Sync, so if you have a newer version, uninstall that version first.
Once installed, run the RUU again (you might need to run it as admin).
Click to expand...
Click to collapse
Yes I have that specific version.
Tried run as admin.
Just to be sure, you still have your phone connected in charge only state right?
If so, are you sure you didn't get any error in the earlier steps?
I downgraded using the exact same method and didn't get this error (recognized all of the others), so I'm not sure what might cause this otherwise.
Azaruc said:
Just to be sure, you still have your phone connected in charge only state right?
If so, are you sure you didn't get any error in the earlier steps?
I downgraded using the exact same method and didn't get this error (recognized all of the others), so I'm not sure what might cause this otherwise.
Click to expand...
Click to collapse
I showed you what I got from following your steps earlier. You said it looked ok, then I went to downgrade with the RUU.
Is the RUU compatible with 64bit Windows 7?
Looking at your other post, it looks like you managed to complete the downgrading?
What turned out to be the problem with the second step?
Azaruc said:
Looking at your other post, it looks like you managed to complete the downgrading?
What turned out to be the problem with the second step?
Click to expand...
Click to collapse
The downgrade guide doesn't work for me - I followed this instead: http://android.modaco.com/content/h...-r4-htc-legend-rooting-guide-now-with-1-31-x/
But now, I still can't delete widgets/apps. http://forum.xda-developers.com/showthread.php?t=987023
Azaruc said:
- Get visionary+
- Temproot your legend with it
- Use commandline with adb on your pc to flash misc1-2.img.
type the following commands from the folder where you have adb;
Code:
adb shell
su
accept the notification on your phone if one comes up
and then in the command line type this;
Code:
/data/local/flash_image misc /data/local/misc1-2.img
After that you should be able to run the 1.31 RUU
Click to expand...
Click to collapse
Mate, just wanted to let you know I was having the exact same issues under Win7 x64 and after trying your Visionary+ and manually executing adb commands method, I was able to run RUU successfully.
My Legend is now 1.3.1 and Im performing the root as I type.
Thanks for your help and contritubtion.
Error 170: Usb connection error
Tried to downgrade many time using guides on the forum but when running RUU always get:
ERROR 170: USB CONNECTION ERROR
- downloaded the drivers with HTC SYNC (phone shows up at device manager)
- made the gold card (with two different cards 2GB Kingston, 8GB SanDisc)
- ran ADB ended up with: cr--rw----
- did a temproot, ran adb shell .... su and so on
but still get:
ERROR 170: USB CONNECTION ERROR
Have no clue what to do now whatsoever. Any suggestions?
Having successfully semi-rooting my device through pauls root i was trying to install the SDE, i followed all steps correctly and ran the batch file but when rebooting into recovery mode no such menu appeared, i have confirmed root shell access so now i'm wondering if anyone else has had a problem? really would want to get the menu installed. It just seems not to work at all and i've ran the script from both my pc and from the internal device memory but this seems not to have worked, any ideas? Thanks
I followed all paul's instruction but I can't root my 101, I tried SDE script too but I can't see any differcence in recovery
Nadrian,
could you try this for me:
start a cmd.exe, and launch the script from this cmd window.
Do a copy/paste of the execution log and post it here please ?
(to copy paste from cmd, do Alt+space, select "edit", "mark", then select text with mouse, press enter then do a paste here)
Moskiller, you problem is different if you don't have the # prompt when doing Paul's root, could you show me the log of the adb session ?
@letama i'll pm you those tomorrow and thanks for the help!
letama said:
Nadrian,
could you try this for me:
start a cmd.exe, and launch the script from this cmd window.
Do a copy/paste of the execution log and post it here please ?
(to copy paste from cmd, do Alt+space, select "edit", "mark", then select text with mouse, press enter then do a paste here)
Moskiller, you problem is different if you don't have the # prompt when doing Paul's root, could you show me the log of the adb session ?
Click to expand...
Click to collapse
If u explain to me how do it, with pleasure
Sent from my ARCHOS 101G9 using Tapatalk
Moskiller said:
If u explain to me how do it, with pleasure
Click to expand...
Click to collapse
I need all the text in the cmd window with the adb commands and the results.
you can do the copy/paste the same way I explained to Nadrian.
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>enable_sde
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push zimage /data/
local/tmp
306 KB/s (2655004 bytes in 8.450s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push initrd.cpio.l
zma /data/local/tmp
314 KB/s (398045 bytes in 1.236s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push abcbox /data/
local/tmp
323 KB/s (277204 bytes in 0.838s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell chmod 755 /d
ata/local/tmp/abcbox
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell /data/local/
tmp/abcbox kd_flasher -k /data/local/tmp/zimage -i /data/local/tmp/initrd.cpio.l
zma
Generating KD...
Updating KD (3053305 bytes)...
0
100
It worked when i executed the script through command prompt, but here's the execution log anyway, thanks for the tool and for all help!
My log (Windows XP SP3):
C:\android-sdk-windows\platform-tools>enable_sde.bat
C:\android-sdk-windows\platform-tools>adb push zimage /data/local/tmp
1999 KB/s (2655004 bytes in 1.296s)
C:\android-sdk-windows\platform-tools>adb push initrd.cpio.lzma /data/local/tmp
1776 KB/s (398045 bytes in 0.218s)
C:\android-sdk-windows\platform-tools>adb push abcbox /data/local/tmp
1925 KB/s (277204 bytes in 0.140s)
C:\android-sdk-windows\platform-tools>adb shell chmod 755 /data/local/tmp/abcbox
C:\android-sdk-windows\platform-tools>adb shell /data/local/tmp/abcbox kd_flashe
r -k /data/local/tmp/zimage -i /data/local/tmp/initrd.cpio.lzma
Generating KD...
Updating KD (3053305 bytes)...
0
100
C:\android-sdk-windows\platform-tools>
Even for me, SDE doesn't work (archos 101 G9 8gb)
EDIT: WORKS!
at the fourth attempt it worked (ext4 firmware)! After removing the root and before reboot, the only thing I changed was disconnect the USB cable from tablet (???). ciao
hitman72 said:
at the fourth attempt it worked (ext4 firmware)! After removing the root and before reboot, the only thing I changed was disconnect the USB cable from tablet (???). ciao
Click to expand...
Click to collapse
Weird!
I guess a couple of md5sum could help pinpointing adb push or flash issue.
I'll add that someday.
Thanks for the report!
Hi guys .. i am using htc hero(t-mobile g2 touch)..i tried flashing clockworkmod recovery using adb,rom manager and terminal emulator..here is what i got
adb--cannot stat 'recovery-clockwork-2.5.0.7-hero.img': no such file or directory
for terminal emulator--error no such file or directory
for rom manager--unable to contact server
please help ..is there other way or did i make mistake??
thanks in advance
I'm a noob but did you by chance forget to Root your device?
Is it a .zip or .img file?
I'll give you a simple tutorial
1. Right-Click platform-tools and click Open CMD from here.
2. To be sure the device is detected do
adb devices
Click to expand...
Click to collapse
2.1 (optional) If no device is detected follow this tutorial.
3. extract the zip file to platform-tools and put the .img file in the same folder.
4. type the following commands:
adb push recovery-clockwork-2.5.0.7-hero.img /data/local/
adb push flash_image /data/local/
adb shell chmod 777 /data/local/recovery-clockwork-2.5.0.7-hero.img
adb shell chmod 777 /data/local/flash_image
adb shell rm /data/local/rights/mid.txt
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
adb reboot
Click to expand...
Click to collapse
5. the device will reboot wait until it is on the homescreen again.
6. then type the following command:
adb shell /data/local/flash_image recovery /data/local/recovery-clockwork-2.5.0.7-hero.img
Click to expand...
Click to collapse
7. and you are done
I'm trying to adb push a zip file onto my Prime so I can install the ROM, but adb push always fails, saying that the file system is read only.
What can I do to change this?
Please post full adb command which you are using.
Johnotronz said:
I'm trying to adb push a zip file onto my Prime so I can install the ROM, but adb push always fails, saying that the file system is read only.
What can I do to change this?
Click to expand...
Click to collapse
Send the file to a writable location?
adb push file.ext /sdcard/
or
adb push file.ext /data/local/
I had been using the "adb push file.ext /sdcard/" command, and it returned "Failed to copy....blah: Read-only file system."
This also happens when using "adb push file.ext /data/local"
Try adb push file.ext /mnt/sdcard/
Johnotronz said:
I had been using the "adb push file.ext /sdcard/" command, and it returned "Failed to copy....blah: Read-only file system."
This also happens when using "adb push file.ext /data/local"
Click to expand...
Click to collapse
?
what happens if you type:
Code:
adb remount
First?
Worked once, now no more. I had to re-flash using heimdall, successfully recovered but now can't re-root my phone. Originally had safestrap running like a charm and cant get back to it now.
adb shell confirmed, phone reboots but looks like saferoot is trying to remove temporary files when the phone is rebooting.... see below
Any thoughts? Suggestions?
Thanks - cpiercew
usermbp:saferoot user$ adb shell
[email protected]:/ $ exit
usermbp:saferoot user$ sh ./install.sh
--- Samsung i545 VRUEMJ7 Root ---
--- Based on the CVE-2013-6282 exploit by cubeundcube ---
Waiting for device...
Watch your phone. Unlock it and give permission for the install to run.
Sending files to your device...
2363 KB/s (17804 bytes in 0.007s)
3412 KB/s (104800 bytes in 0.029s)
2208 KB/s (13592 bytes in 0.006s)
3248 KB/s (2139595 bytes in 0.643s)
4732 KB/s (1109128 bytes in 0.228s)
293 KB/s (629 bytes in 0.002s)
Starting rooting program.
ro.build.product=jfltevzw
ro.build.id=JSS15J
selinux enforcing known.
Succeeded in getroot!
Remount success!
Copying files..
Removing temporary files...
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
Rebooting...Please wait.
error: device not found
Waiting for device to re-appear...
Unlock your phone, and when prompted, give SuperSU permission for
'ADB shell' to run.
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
Installing busybox
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
--- All Finished ---
usermbp:saferoot user$
cpiercew said:
Worked once, now no more. I had to re-flash using heimdall, successfully recovered but now can't re-root my phone. Originally had safestrap running like a charm and cant get back to it now.
adb shell confirmed, phone reboots but looks like saferoot is trying to remove temporary files when the phone is rebooting.... see below
Any thoughts? Suggestions?
Thanks - cpiercew
usermbp:saferoot user$ adb shell
[email protected]:/ $ exit
usermbp:saferoot user$ sh ./install.sh
--- Samsung i545 VRUEMJ7 Root ---
--- Based on the CVE-2013-6282 exploit by cubeundcube ---
Waiting for device...
Watch your phone. Unlock it and give permission for the install to run.
Sending files to your device...
2363 KB/s (17804 bytes in 0.007s)
3412 KB/s (104800 bytes in 0.029s)
2208 KB/s (13592 bytes in 0.006s)
3248 KB/s (2139595 bytes in 0.643s)
4732 KB/s (1109128 bytes in 0.228s)
293 KB/s (629 bytes in 0.002s)
Starting rooting program.
ro.build.product=jfltevzw
ro.build.id=JSS15J
selinux enforcing known.
Succeeded in getroot!
Remount success!
Copying files..
Removing temporary files...
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
Rebooting...Please wait.
error: device not found
Waiting for device to re-appear...
Unlock your phone, and when prompted, give SuperSU permission for
'ADB shell' to run.
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
Installing busybox
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
--- All Finished ---
usermbp:saferoot user$
Click to expand...
Click to collapse
I'm assuming the files copied to the tmp directory because of the adb output, but have you checked?
Edit: derp, you said adb shell confirmed.
From reading the install script your phones state shouldn't change before the device is first not recognized (it should still be on and responding to adb commands). So if you can successfully start an adb shell there is no reason the script shouldn't work. Maybe try running the commands manually?
gnubian said:
I'm assuming the files copied to the tmp directory because of the adb output, but have you checked? Also, what happens when you type "adb shell" ? Because from reading the install script your phones state shouldn't change before the device is first not recognized (it should still be on and responding to adb commands).
Click to expand...
Click to collapse
I included the adb shell output, I verified it could connect to the device first. Prior to installing ADB I first installed Kies and drivers, then put adb in my path to ensure it would run properly.
I haven't check the tmp directory, I will but not sure if this would matter as it seems something else is going on. I have a total of three errors that seem to be happening:
1) Removing temporary files
Removing temporary files...
error: device not found
2) When the phone reboots I unlock it immediately but dont get prompted to allow ADB shell to run
Rebooting...Please wait.
error: device not found
Waiting for device to re-appear...
Unlock your phone, and when prompted, give SuperSU permission for
'ADB shell' to run.
/system/bin/sh: /system/xbin/su: not found
3) Installing busybox seems to fail, "su" is not found
Installing busybox
/system/bin/sh: /system/xbin/su: not found
I also get the "all finished" prompt before the phone is finished booting up.
gnubian said:
I'm assuming the files copied to the tmp directory because of the adb output, but have you checked?
Edit: derp, you said adb shell confirmed.
From reading the install script your phones state shouldn't change before the device is first not recognized (it should still be on and responding to adb commands). So if you can successfully start an adb shell there is no reason the script shouldn't work. Maybe try running the commands manually?
Click to expand...
Click to collapse
Good idea, I didn't know that was an option, is there a list of commands I can find somewhere?
- just realized looking in install.sh shows the source. However, still noob'd and don't know how to translate some of the basic shell scripting
cpiercew said:
Good idea, I didn't know that was an option, is there a list of commands I can find somewhere?
Click to expand...
Click to collapse
Edit: i was assuming that was a linux error, not an error in adb shell. It seems the files did not properly copy. Did you check if they are in the tmp folder?
---------- Post added at 08:50 PM ---------- Previous post was at 08:46 PM ----------
[/COLOR]If you give me a minute I can post the commands without the unnecessary scripting that should allow for manual installation.
Edit: don't know why I assumed mac, thought I read it in your post. What are you running?
gnubian said:
I believe you need to install the package that has the su command (not sure about mac, I use linux). Just open the .sh file rather than run it and the commands are in there. Obviously just ignore the echos and such.
---------- Post added at 08:50 PM ---------- Previous post was at 08:46 PM ----------
If you give me a minute I can post the commands without the unnecessary scripting that should allow for manual installation. Google your errors about system/bin/sh and su to find the appropriate package you need for your mac distribution in the meantime.
Edit: don't know why I assumed mac, thought I read it in your post. What are you running?
Click to expand...
Click to collapse
Correct, using a mac
The following are the individual commands. Should let you know exactly when your problems are starting if you enter them manually. I believe the repeated system/xbin/su command is repeated incase the device isn't responding/rebooted yet. So you may only need to enter it once. Sorry the .sh worked for me so I didn't do it this way. Hopefully this sheds more light on your problem.
Remember to run these from the folder that contains the "file" folder.
adb wait-for-device
adb push files/getroot /data/local/tmp/
adb push files/su /data/local/tmp/
adb push files/selinuxoff /data/local/tmp/
adb push files/Superuser.apk /data/local/tmp/
adb push files/busybox /data/local/tmp/
adb push files/install-recovery.sh /data/local/tmp/
adb shell "chmod 0755 /data/local/tmp/getroot"
adb shell "chmod 0755 /data/local/tmp/busybox"
adb shell /data/local/tmp/getroot
adb shell "rm /data/local/tmp/getroot"
adb shell "rm /data/local/tmp/su"
adb shell "rm /data/local/tmp/selinuxoff"
adb shell "rm /data/local/tmp/Superuser.apk"
adb shell "rm /data/local/tmp/busybox"
adb shell "rm /data/local/tmp/install-recovery.sh"
adb reboot
adb wait-for-device
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb shell "/system/xbin/su -c mount -o remount,rw /system"
adb shell "/system/xbin/su -c chmod 6755 /system/xbin/su"
adb shell "/system/xbin/su -c chmod 6755 /system/xbin/daemonsu"
adb shell "/system/xbin/su -c /system/xbin/busybox --install -s /system/xbin"
adb wait-for-device
adb shell "/system/xbin/su -c mount -o remount,ro /system"
gnubian said:
adb wait-for-device
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
Click to expand...
Click to collapse
Please note that all of that is to give the user a chance to notice the SuperSU prompt asking them to give permissions for adb shell.
k1mu said:
Please note that all of that is to give the user a chance to notice the SuperSU prompt asking them to give permissions for adb shell.
Click to expand...
Click to collapse
Thanks for clearing that up. As I said I did not root by manually issuing the commands.
gnubian said:
Thanks for clearing that up. As I said I did not root by manually issuing the commands.
Click to expand...
Click to collapse
Ok, I resolved the issue after going with my hunch the stock verizon GS4 VRUEMK2 build from Surge1223 I had previously recovered from may have been the issue.
I went back into Kies backed up apps, settings and performed a firmware recovery to MK2. Once rebooted and reconfigured - it worked as designed.
For what it's worth, the build I would suggest avoiding if you want to use saferoot or root your phone at all is what I found from Surge1223 on androidforum: SCH-I545_VZW_1_20131212083410_mwx72ql56g_fac.zip
Not a dig on Surge1223, as with anything I use all downloads at my own risk.
Thanks again for the responses, any info I can provide from this that will help anyone else trying to use Saferoot please let me know.
cpiercew said:
Ok, I resolved the issue after going with my hunch the stock verizon GS4 VRUEMK2 build from Surge1223 I had previously recovered from may have been the issue.
I went back into Kies backed up apps, settings and performed a firmware recovery to MK2. Once rebooted and reconfigured - it worked as designed.
For what it's worth, the build I would suggest avoiding if you want to use saferoot or root your phone at all is what I found from Surge1223 on androidforum: SCH-I545_VZW_1_20131212083410_mwx72ql56g_fac.zip
Not a dig on Surge1223, as with anything I use all downloads at my own risk.
Thanks again for the responses, any info I can provide from this that will help anyone else trying to use Saferoot please let me know.
Click to expand...
Click to collapse
FWIW, I don't have an androidforums account. Also, my upload is fine, otherwise it wouldn't flash in Odin. Next time come tell me or comment in my thread about the issues your having with my upload.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
FWIW, I don't have an androidforums account. Also, my upload is fine, otherwise it wouldn't flash in Odin. Next time come tell me or comment in my thread about the issues your having with my upload.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sure - there could have been a few reasons it didn't work.