You need ADB and an understanding of how to use it and have a rooted device (although I didn't test this). You will also need a hex editor like HxD.
BACK UP YOUR DATA BEFORE DOING THIS!!!! WHEN HTCDEV UNLOCKS YOUR DEVICE YOU MUST START FROM SCRATCH!!!
1. Fire up your command prompt and go to the directory that you have ADB installed to. Type "adb shell" and hit enter.
2. Type "su" and hit enter. You now have root privileges.
3. Next type "dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4" and hit enter. This will dump the partition to your sdcard.
4. Next type "exit", hit enter, type "exit", and hit enter again. This should take you back to a command prompt for your computer.
5. type "adb pull /sdcard/mmcblk0p4" and hit enter. NOTE THE SIZE OF THE FILE BEFORE THE NEXT STEP!
6. Open the file (mmcblk0p4) with your hex editor.
7. Look for the area that contains the CID with your IMEI number attached to it.
8. Change your CID to 11111111 and save the file as mmcblk0p4MOD. This will give you SuperCID. MAKE SURE AT THIS POINT THAT THE FILE IS THE EXACT SIZE IT WAS BEFORE YOU HEX EDITED IT!
9. Now go back to your command prompt and type "adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD" and hit enter.
10. Type "adb shell" and hit enter then type "su" and hit enter again. This will put you back into the android shell and give you root privileges.
11. Type "dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4" and hit enter. To test if it worked restart the phone into fastboot (type "adb reboot bootloader" and hit enter) and once the bootloader screen comes up type "fastboot oem readcid" and hit enter. It should read "11111111".
I have modified my file as I had the O2__001 CID and it changed successfully, with the same file size etc, I am now just kind of crapping my self to test it by continuing onto step 9.
So do people think it will work, and or ready to risk it.
lol ... I do not believe it ... prefer to wait for another idiot ... what's going on ... no nuts in the pants to test it yourself
nintendolinky said:
You need ADB and an understanding of how to use it and have a rooted device (although I didn't test this). You will also need a hex editor like HxD.
BACK UP YOUR DATA BEFORE DOING THIS!!!! WHEN HTCDEV UNLOCKS YOUR DEVICE YOU MUST START FROM SCRATCH!!!
1. Fire up your command prompt and go to the directory that you have ADB installed to. Type "adb shell" and hit enter.
2. Type "su" and hit enter. You now have root privileges.
3. Next type "dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4" and hit enter. This will dump the partition to your sdcard.
4. Next type "exit", hit enter, type "exit", and hit enter again. This should take you back to a command prompt for your computer.
5. type "adb pull /sdcard/mmcblk0p4" and hit enter. NOTE THE SIZE OF THE FILE BEFORE THE NEXT STEP!
6. Open the file (mmcblk0p4) with your hex editor.
7. Look for the area that contains the CID with your IMEI number attached to it.
8. Change your CID to 11111111 and save the file as mmcblk0p4MOD. This will give you SuperCID. MAKE SURE AT THIS POINT THAT THE FILE IS THE EXACT SIZE IT WAS BEFORE YOU HEX EDITED IT!
9. Now go back to your command prompt and type "adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD" and hit enter.
10. Type "adb shell" and hit enter then type "su" and hit enter again. This will put you back into the android shell and give you root privileges.
11. Type "dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4" and hit enter. To test if it worked restart the phone into fastboot (type "adb reboot bootloader" and hit enter) and once the bootloader screen comes up type "fastboot oem readcid" and hit enter. It should read "11111111".
I have modified my file as I had the O2__001 CID and it changed successfully, with the same file size etc, I am now just kind of crapping my self to test it by continuing onto step 9.
So do people think it will work, and or ready to risk it.
Click to expand...
Click to collapse
as long as you were careful with the hex editor,there is not much danger. im willing to bet,however,that mmcblk0p4 is write protected,so the flash may appear successful,yet,not actually change anything.
you could also try changing it like on the one vx: http://forum.xda-developers.com/showthread.php?t=2161402
nintendolinky said:
You need ADB and an understanding of how to use it and have a rooted device (although I didn't test this). You will also need a hex editor like HxD.
BACK UP YOUR DATA BEFORE DOING THIS!!!! WHEN HTCDEV UNLOCKS YOUR DEVICE YOU MUST START FROM SCRATCH!!!
1. Fire up your command prompt and go to the directory that you have ADB installed to. Type "adb shell" and hit enter.
2. Type "su" and hit enter. You now have root privileges.
3. Next type "dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4" and hit enter. This will dump the partition to your sdcard.
4. Next type "exit", hit enter, type "exit", and hit enter again. This should take you back to a command prompt for your computer.
5. type "adb pull /sdcard/mmcblk0p4" and hit enter. NOTE THE SIZE OF THE FILE BEFORE THE NEXT STEP!
6. Open the file (mmcblk0p4) with your hex editor.
7. Look for the area that contains the CID with your IMEI number attached to it.
8. Change your CID to 11111111 and save the file as mmcblk0p4MOD. This will give you SuperCID. MAKE SURE AT THIS POINT THAT THE FILE IS THE EXACT SIZE IT WAS BEFORE YOU HEX EDITED IT!
9. Now go back to your command prompt and type "adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD" and hit enter.
10. Type "adb shell" and hit enter then type "su" and hit enter again. This will put you back into the android shell and give you root privileges.
11. Type "dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4" and hit enter. To test if it worked restart the phone into fastboot (type "adb reboot bootloader" and hit enter) and once the bootloader screen comes up type "fastboot oem readcid" and hit enter. It should read "11111111".
I have modified my file as I had the O2__001 CID and it changed successfully, with the same file size etc, I am now just kind of crapping my self to test it by continuing onto step 9.
So do people think it will work, and or ready to risk it.
Click to expand...
Click to collapse
If this actually worked like stated, does this mean that AT&T HTC One users (HTCDev will stop supporting the phone on the 19th) can use this to unlock their bootloaders? Will they be able to choose "Other Devices" on HTCDev and unlock their bootloaders using this mod?
Hi,
doesn't work
edit: attached is a bat file in self extracting zip
cheers
starbase64
D:\Handy\HTC_One\SuperCID>adb devices
List of devices attached
HT332W900709 device
D:\Handy\HTC_One\SuperCID>adb remount
remount succeeded
D:\Handy\HTC_One\SuperCID>adb shell "dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4"
2+0 records in
2+0 records out
1024 bytes transferred in 0.011 secs (93090 bytes/sec)
D:\Handy\HTC_One\SuperCID>adb pull /sdcard/mmcblk0p4
85 KB/s (1024 bytes in 0.011s)
D:\Handy\HTC_One\SuperCID>adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD
85 KB/s (1024 bytes in 0.011s)
D:\Handy\HTC_One\SuperCID>adb shell "dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4"
2+0 records in
2+0 records out
1024 bytes transferred in 0.007 secs (146285 bytes/sec)
D:\Handy\HTC_One\SuperCID>adb reboot bootloader
D:\Handy\HTC_One\SuperCID>fastboot oem readcid
< waiting for device >
... INFOcid: O2___102
OKAY
Click to expand...
Click to collapse
Code in superCID.bat said:
@echo off
adb devices
echo "******************************************************"
echo "* current CID *"
echo "******************************************************"
adb shell "getprop ro.cid"
pause
adb remount
adb shell "dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4"
adb pull /sdcard/mmcblk0p4
echo "******************************************************"
echo "* open the file in HEXEditor *"
echo "* press any key to push modifid file back on device *"
echo "******************************************************"
pause
adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD
echo "******************************************************"
echo "* press any Key to flash SuperCID *"
echo "* at you own RISK!!!!!!!!! *"
echo "******************************************************"
pause
adb shell "dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4"
echo "******************************************************"
echo "* current CID *"
echo "******************************************************"
adb shell "getprop ro.cid"
pause
echo "******************************************************"
echo "* press any Key to reboot into Bootloader *"
echo "******************************************************"
pause
adb reboot bootloader
echo "******************************************************"
echo "* reboting into Bootloader *"
echo "******************************************************"
pause
fastboot oem readcid
echo "******************************************************"
echo "* press any key to reboot *"
echo "******************************************************"
pause
fastboot reboot
exit
Click to expand...
Click to collapse
nintendolinky said:
You need ADB and an understanding of how to use it and have a rooted device (although I didn't test this). You will also need a hex editor like HxD.
BACK UP YOUR DATA BEFORE DOING THIS!!!! WHEN HTCDEV UNLOCKS YOUR DEVICE YOU MUST START FROM SCRATCH!!!
1. Fire up your command prompt and go to the directory that you have ADB installed to. Type "adb shell" and hit enter.
2. Type "su" and hit enter. You now have root privileges.
3. Next type "dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4" and hit enter. This will dump the partition to your sdcard.
4. Next type "exit", hit enter, type "exit", and hit enter again. This should take you back to a command prompt for your computer.
5. type "adb pull /sdcard/mmcblk0p4" and hit enter. NOTE THE SIZE OF THE FILE BEFORE THE NEXT STEP!
6. Open the file (mmcblk0p4) with your hex editor.
7. Look for the area that contains the CID with your IMEI number attached to it.
8. Change your CID to 11111111 and save the file as mmcblk0p4MOD. This will give you SuperCID. MAKE SURE AT THIS POINT THAT THE FILE IS THE EXACT SIZE IT WAS BEFORE YOU HEX EDITED IT!
9. Now go back to your command prompt and type "adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD" and hit enter.
10. Type "adb shell" and hit enter then type "su" and hit enter again. This will put you back into the android shell and give you root privileges.
11. Type "dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4" and hit enter. To test if it worked restart the phone into fastboot (type "adb reboot bootloader" and hit enter) and once the bootloader screen comes up type "fastboot oem readcid" and hit enter. It should read "11111111".
I have modified my file as I had the O2__001 CID and it changed successfully, with the same file size etc, I am now just kind of crapping my self to test it by continuing onto step 9.
So do people think it will work, and or ready to risk it.
Click to expand...
Click to collapse
Respect for trying anyway
Sent from my HTC One using xda app-developers app
I will probably try other methods as we might be pulling the wrong file from the device.
Sent from my M7 using Tapatalk 2
Stop trying this, CID partition is write protected. You have to figure out a way to crack that or bypass it first.
Hunt3r.j2 said:
Stop trying this, CID partition is write protected. You have to figure out a way to crack that or bypass it first.
Click to expand...
Click to collapse
That's correct. I have contacted Beaups, he's the one who got s-off for the DNA/Butterfly. I'm going to see if he can teamview around on my device to look for exploits.
Related
Well guys there are over 9000 threads here on how to root the Nexus 4.
I thought I'd make one thread that says all this in simple English and makes it quick and simple for everybody.
CREDITS:
1wayjonny - Universal Naked Driver
Koushik Dutta (koush) - CWM
Chainfire - SuperSU
HQRaja - SU & Busybox package
Click to expand...
Click to collapse
DISCLAIMER:
UNLOCKING THE PHONE WIPES DATA AND THE INTERNAL SD CARD. UNLOCKING THE PHONE WIPES DATA AND THE INTERNAL SD CARD. UNLOCKING THE PHONE WIPES DATA AND THE INTERNAL SD CARD. Therefore I HIGHLY suggest you do this before you start setting up the phone/installing apps so that you don't have to redo/reinstall much.
You can re-lock and unroot the phone, but I am still going to say that this voids the warranty.
I am not responsible for what you do to your device. This is for reference only.
Please follow each step carefully (ESPECIALLY make sure to read the part before step 14 VERY CAREFULLY.)
The CWM recovery may not be 100% functional yet, but you can install zips/roms and do backups for sure.
STEPS:
1 - Download this file and unzip it to C:\Nexus4
2 - Open a command prompt (On windows vista/7, go to Start menu and type cmd and press enter. On XP & below, go to Start > Run and type cmd and press enter.)
3 - In the command propmpt, run
Code:
cd C:\Nexus4 <press enter>
4 - On the phone, go to Settings > About phone. In the About phone menu, scroll down to "build number" and tap it until it says "You are now a Developer!"
5 - Go back to the main settings menu, and the Developer options tab should now be visible. Open that tab.
6 - In the Developer options menu, check USB debugging and Stay awake.
7 - Install the driver from here.
8 - Connect the device via USB.
9 - In the command prompt, run the command
Code:
adb devices <press enter>
and your serial number should pop up. If not, try unplugging the device, reinstalling the drivers, rebooting PC, and then retry.
10 - Now run the command
Code:
adb push SUBusybox.zip /sdcard/SUbusybox.zip <press enter>
It should say something like "XXXX KB/s (1191942 bytes in X.XXXs)"
11- If it said that, run the command
Code:
adb reboot-bootloader <press enter>
12 - The phone will show up in the bootloader. Now run the command
Code:
fastboot devices <press enter>
and your serial number should pop up.
13 - If your serial number popped up, run the command
Code:
fastboot oem unlock
and your phone will ask you if you want to unlock. Select yes with the volume buttons and press power.
13 - Your phone will go back to the bootloader screen, and at the bottom it will now say LOCK STATE - unlocked
****DO WHAT IS BETWEEN THESE RED DIVIDERS IF AND ONLY IF YOU WANT OTA UPDATES TO STILL WORK. IF YOU DON'T CARE, CONTINUE ON STEP 14 BELOW THE DIVIDERS.****
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
Run
Code:
fastboot boot CWMrecovery.img <press enter>
and it should say something like
Code:
downloading 'boot.img'... OKAY [ X.XXXs]
booting... OKAY [ X.XXXs]
and your phone will boot into CWM recovery.
NOW SKIP TO STEP 17. ON STEP 18 IF IT ASKS YOU TO DISABLE RECOVERY OVERWRITE, TAP NO. STEP 19 SAYS YOU WILL HAVE CWM INSTALLED. YOU WON'T.
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
14 - Now run the command
Code:
fastboot flash recovery CWMrecovery.img <press enter>
and it should say something like
Code:
sending 'recovery' (7754 KB)... OKAY [ X.XXXs]
writing 'recovery'... OKAY [ X.XXXs]
15 - If it said OKAY twice, then press the volume down key on the phone twice and it will say Recovery mode. Press the power key.
16 - Once in recovery mode, run the commands
Code:
adb shell mount system <press enter>
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak <press enter>
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak <press enter>
adb shell umount system <press enter>
the command prompt will say nothing back to you if there were no errors.
17 - On the phone, tap install zip from sdcard (NOT INSTALL ZIP FROM SIDELOAD), then tap choose zip from sdcard. Tap 0/. Now scroll down to SUBusybox.zip and tap it. Tap yes. It will then install.
18 - Now tap Go Back and then tap reboot system now. If it asks you to disable recovery overwrite tap yes.
19 - Once the phone boots back up it will be fully wiped and you will be rooted with CWM, SuperSU, and busybox installed
Thanks! So I'm assuming the latest CWM also runs a script that renames the auto reflash recovery? For my GN it was good enough to just rename the script in /system.
Sent from my cm_tenderloin using Tapatalk
jimmyz said:
Thanks! So I'm assuming the latest CWM also runs a script that renames the auto reflash recovery? For my GN it was good enough to just rename the script in /system.
Sent from my cm_tenderloin using Tapatalk
Click to expand...
Click to collapse
It didn't work for me, so I put adb commands in there to do it manually just in case.
Sent from my Nexus 4 using Tapatalk 2
Hello every one,
I am using the latest nightly bild from CM10.1 and I am trying to install GPSCountryOptimizer app with adb but all the time it give me error INSTALL_FAILED_INVALID_APK ?
Can anyone please explain me what do I need to do? Also tried to wipe devlik after copying the same app in system folder and setting permissions as well but no use.
Thanks.
sPEADy said:
Hello every one,
I am using the latest nightly bild from CM10.1 and I am trying to install GPSCountryOptimizer app with adb but all the time it give me error INSTALL_FAILED_INVALID_APK ?
Can anyone please explain me what do I need to do? Also tried to wipe devlik after copying the same app in system folder and setting permissions as well but no use.
Thanks.
Click to expand...
Click to collapse
check settings in Developer Options about adb. may be you do not have some check point there...
also uncheck <verify application> and check <unknown sources> and try again
gtdaniel said:
check settings in Developer Options about adb. may be you do not have some check point there...
also uncheck <verify application> and check <unknown sources> and try again
Click to expand...
Click to collapse
Thanks for your quick reply. I have checked USB Debugging, Debugging over network is unchecked, Apps over USB checking is unchecked.
It should be right or maybe I am wrong.
With the Following Process it worked out how to install the unsigned apps.
Here are a couple of different options to try.
For both options you will need to put the gallery apk into the same directory as your sdk install. (if you don't know what this is try to pull a file from your device and see where it ends up. Mine is /AndroidSDK/tools because I installed the SDK in the /AndroidSDK directory on my PC)
with all of the commands to type below ignore the single quotes (')
*Install from PC*
1) connect your phone and make sure adb can detect it.
- Launch command prompt
- Navigate to your sdk directory
- type 'adb devices' - you should now see your device listed.
2) Go back to the command prompt and type 'adb install [apk name.apk]
3) You should now see a success message, if you it fails try my other option below.
*Manually place APK into /system/app*
1) connect your phone and make sure adb can detect it.
- Launch command prompt
- Navigate to your sdk directory
- type 'adb devices' - you should now see your device listed.
2) push gallery apk to your sd card.
-type 'adb push [apk name.apk] /sdcard/[apk name.apk]
3) Launch a second command prompt
-type 'adb shell'
-type 'su'
-type 'mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system'
4) go back to first command prompt
-type 'adb shell'
-type 'su'
-type 'cd /system/app'
-type 'cp /sdcard/[apk name.apk] [apk name.apk]'
-command prompt will show 'cp /sdcard/[apk name.apk] [apk name.apk]'
-type 'exit' (this will get you out of su)
-type 'exit' again (this should get you out of adb shell)
-type 'exit' again (this should close the command prompt)
5) go back to first command prompt
-type 'exit' (this will get you out of su)
-type 'exit' again (this should get you out of adb shell)
-type 'adb reboot' (this will reboot your phone)
-type 'exit' again (this should close the command prompt)
You may not need to do this in 2 command prompts, but for some reason I've had issue using just one before.
one of these should work.
Thanks to ezun for so detailed post.
Having the same problem here with the PwnMyMoto rooting file. Thing is, the Droid maxx does not have a sd card. Should I just type "System" instead of sdcard in the command?
I tried to do what in http://forum.xda-developers.com/showthread.php?t=2281254
but my current default.xml file had all languages , but i only see 13 in settings
is there anyway to do it ?
am runing android 4.2.2 stock rom
Anyone ?
!!!!!!!!!!!! really ? no one !!!!!!!!!!!!!!!
enable hidden languages
mjrshark said:
!!!!!!!!!!!! really ? no one !!!!!!!!!!!!!!!
Click to expand...
Click to collapse
phone has to be rooted -- tested and working with HTC One X
1. boot in FASTBOOT and check CID , start cmd type
Code:
fastboot getvar all
2. start phone normally, enable usb debugging
3. start CMD type:
Code:
adb pull system/customize/CID/default.xml
4. rename saved file "default.xml" to "your_cid.xml" // my cid was HTC__Y13 so it will be HTC__Y13.xml
5. start CMD type:
Code:
adb push your_cid.xml/sdcard/
6. start CMD type:
Code:
adb shell
su (tap grant access on your htc screen)
mount -o remount,rw /system
cat /sdcard/your_cid.xml > /system/customize/CID/your_cid.xml
exit
exit
7. do factory reset
artur223 said:
phone has to be rooted -- tested and working with HTC One X
1. boot in FASTBOOT and check CID , start cmd type
Code:
fastboot getvar all
2. start phone normally, enable usb debugging
3. start CMD type:
Code:
adb pull system/customize/CID/default.xml
4. rename saved file "default.xml" to "your_cid.xml" // my cid was HTC__Y13 so it will be HTC__Y13.xml
5. start CMD type:
Code:
adb push your_cid.xml/sdcard/
6. start CMD type:
Code:
adb shell
su (tap grant access on your htc screen)
mount -o remount,rw /system
cat /sdcard/your_cid.xml > /system/customize/CID/your_cid.xml
exit
exit
7. do factory reset
Click to expand...
Click to collapse
thanks for answer after a year dont have HTC anymore , but maybe someone will read your answer and learn from it
[Q] change "relocked" to "locked" when putting phone back to stock?
I followed this thread but mine says "relocked" and it still says S-OFF. is it possible to get it to say "locked" without going through the whole process of unlocking, rooting, and using revone again?
I'm sending my phone back to get the screen replaced which isn't under warranty, so does it even matter that it says "relocked?"
mcarswell said:
I followed this thread but mine says "relocked" and it still says S-OFF. is it possible to get it to say "locked" without going through the whole process of unlocking, rooting, and using revone again?
I'm sending my phone back to get the screen replaced which isn't under warranty, so does it even matter that it says "relocked?"
Click to expand...
Click to collapse
Use revone -l to change back to "locked"
There is not a way without rerooting for Tue device to day say locked and not relocked BUT you can easily get rid of S-Off. It doesn't take long either...
1.) Reroot.
2.) Download revone to computer.
3.) Navigate Using Command Prompt to where revone file is located on computer and move the Downloaded file to /data/local/tmp using the command "adb push revone /data/local/tmp" without quotations while phone is booted into OS and connected to computer.
3.) Use Command Prompt with phone connected to computer to run these commands or you can use Terminal Emulator app without a computer but will need a computer later on to run RUU again...
3A.) adb shell
3B.) su(SU Will Now Request SU Access For ADB Shell, Grant It)
3C.) cd /data/local/tmp
3D.) chmod 755 revone
4.) Reboot device
5.) Once device is fully booted back up run these commands again while connected to computer
5A.) adb shell
5B.) su(Will Not Need To Request Access Again)
5C.) cd /data/local/tmp
5D.) ./revone -P(If It Tells You "No Need To Reboot" Then Move On To Step 7 And If It Tells You To "Reboot To Continue" Move On To Step 6).
6.) Reboot
7.) Once fully booted back into OS open another command prompt and run these commands with Command Prompt while connected to computer.
7A.) adb shell
7B.) su
7C.) cd /data/local/tmp
7D.) ./revone -s 0 -u(To Be Safe).
7E.) Reboot
8.) Once again open another command prompt window and run these commands
8A.) adb shell
8B.) su
8C.) cd /data/local/tmp
8D.) ./revone -t -l
9.) Reboot
10.) Run RUU And Allow It To Successfully Complete.
11.) Once booted back into OS open command prompt and type in the final two commands
11A.) adb reboot bootloader
12.) Once it boots into bootloader and recognizes device type in this command
12A.) fastboot oem writesecureflag e
Sent from my HTCONE using Tapatalk 4
I'm on the last step of mjphillips1981's mac toolkit for 4.4 rooting and it won't finish:
Code:
Press ENTER to finish the SlapMyMoto process.
Open a new terminal window by pressing Command+N
In the new terminal window type the following command
./adb shell echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
Press ENTER when you have finished the above command
I keep getting the error:
Code:
-bash: /sys/kernel/uevent_helper: No such file or directory
I've been at this all day
try this
open terminal
cd to the toolkit folder
type the following (one line at a time)
./adb shell
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
I think these lines need to be separated.
Hit me up on Google+ and lets see if we can work through this.
An I would suggest that you put questions in the toolkit thread. I was just browsing and noticed this. If you put the question in the thread I get an email.
nwinston96 said:
I'm on the last step of mjphillips1981's mac toolkit for 4.4 rooting and it won't finish:
Code:
Press ENTER to finish the SlapMyMoto process.
Open a new terminal window by pressing Command+N
In the new terminal window type the following command
./adb shell echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
Press ENTER when you have finished the above command
I keep getting the error:
Code:
-bash: /sys/kernel/uevent_helper: No such file or directory
I've been at this all day
Click to expand...
Click to collapse
nwinston96 said:
I'm on the last step of mjphillips1981's mac toolkit for 4.4 rooting and it won't finish:
Code:
Press ENTER to finish the SlapMyMoto process.
Open a new terminal window by pressing Command+N
In the new terminal window type the following command
./adb shell echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
Press ENTER when you have finished the above command
I keep getting the error:
Code:
-bash: /sys/kernel/uevent_helper: No such file or directory
I've been at this all day
Click to expand...
Click to collapse
missed some commands it looks like but im not sure if anything is diffrent because your on a mac
but here is the step by step from jcase's thread
Step1)
Unzip SlapMyMoto-1,0.zip and push the jar file to your internal storage
Code:
adb push SlapMyMoto.jar /sdcard/SlapMyMoto.jar
Step2)
Use http://www.cydiaimpactor.com/ to open up a telnet session as system user on port 2222. We covered how to use Impactor and telnet in the RockMyMoto root, I won't be covering it again since this post is going to be long enough already, see here -> http://forum.xda-developers.com/show....php?t=2509590 or http://rootzwiki.com/topic/107098-ro...the-first-ota/
Connecting over telnet, and run Stage1 with this command:
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
When the device tells you to reboot, do this manually with "adb reboot" or your power button. It will not auto reboot on this step
Step3)
Once the device has rebooted, run Impactor again and connect over telnet just like in the previous step, then run the same command
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
Once the device has rebooted, please take the 4.4 OTA.
Step4)
Now that we are on 4.4, we can finish the process with adb shell:
Code:
adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
dray_jr said:
missed some commands it looks like but im not sure if anything is diffrent because your on a mac
but here is the step by step from jcase's thread
Step1)
Unzip SlapMyMoto-1,0.zip and push the jar file to your internal storage
Code:
adb push SlapMyMoto.jar /sdcard/SlapMyMoto.jar
Step2)
Use http://www.cydiaimpactor.com/ to open up a telnet session as system user on port 2222. We covered how to use Impactor and telnet in the RockMyMoto root, I won't be covering it again since this post is going to be long enough already, see here -> http://forum.xda-developers.com/show....php?t=2509590 or http://rootzwiki.com/topic/107098-ro...the-first-ota/
Connecting over telnet, and run Stage1 with this command:
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
When the device tells you to reboot, do this manually with "adb reboot" or your power button. It will not auto reboot on this step
Step3)
Once the device has rebooted, run Impactor again and connect over telnet just like in the previous step, then run the same command
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
Once the device has rebooted, please take the 4.4 OTA.
Step4)
Now that we are on 4.4, we can finish the process with adb shell:
Code:
adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
Click to expand...
Click to collapse
These commands are all in the toolkit. The only one that needed to be enter on individual lines is the one he listed.
I just wish he would have posted the question in the Toolkit thread so I could have helped earlier.
mjphillips1981 said:
These commands are all in the toolkit. The only one that needed to be enter on individual lines is the one he listed.
I just wish he would have posted the question in the Toolkit thread so I could have helped earlier.
Click to expand...
Click to collapse
Ok I have the toolkit for Windows but I'm not familiar with the Mac one thanks for correcting my mistake and getting him
Sent from my XT1056 using XDA Premium 4 mobile app
mjphillips1981 said:
try this
open terminal
cd to the toolkit folder
type the following (one line at a time)
./adb shell
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
I think these lines need to be separated.
Hit me up on Google+ and lets see if we can work through this.
An I would suggest that you put questions in the toolkit thread. I was just browsing and noticed this. If you put the question in the thread I get an email.
Click to expand...
Click to collapse
Thanks, I think this did it. The only thing is that I had to manually reboot my phone, but it appears I am rooted as I'm able to run root-only apps. XDA wouldn't let me post on your thread because I don't have the required number of posts. Glad you came across this thread! Thanks again
nwinston96 said:
Thanks, I think this did it. The only thing is that I had to manually reboot my phone, but it appears I am rooted as I'm able to run root-only apps. XDA wouldn't let me post on your thread because I don't have the required number of posts. Glad you came across this thread! Thanks again
Click to expand...
Click to collapse
You're welcome! From what I read. Some people do experience that the phone does not reboot on its own.
Glad you got it working.
I just removed the toolkit. It's too hard to for me to get things working correctly when I do not have a consumer device to test with.