I have a Moto X(XT1049) with 4.4.2
At one point I had it rooted with safestrap installed. I dont know what I did, but I will try to recap as best I can remember.
-Installed Safestrap and rooted
-At some point I lost root. The safestrap appeared, but no functionality.
I decided I no longer needed root. In fact, I needed to return to stock.
-I used TowelPie.apk to give root access(which I thought was temporary).
-I uninstalled safestrap using the following process found online:
Code:
Enter adb shell from your pc:
Code:
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system
Afterwards safestrap no longer appeared on reboot. However, my phone is now looping "starting services". I believe I need to reflash firmware. However, I can't find a copy of the Republic Wireless 4.4.2 firmware.
I also cannot perform any type of factory reset.
2 Questions
1. Do I need to flash firmware to stock?
2. Does anyone have a copy of Republic Wireless(XT1049) firmware?
Apparently, after reading a bit on Republic Wireless's website this is impossible? That doesn't sound exactly right. Is this correct?
For anyone in a similar predicament:
4.2.2 for Republic Wireless Moto X = ghost_repw-user-4.2.2-13.9.0Q2.X-178-RW-17-15-release-keys-cid6.xml.zip
Upgrade to 4.4.2 = Blur_Version.139.4.17.ghost_row.RepublicWireless.en.US
The 4.2.2 is available online but the naming convention is a bit "weird". Hope this helps others.
Related
Obviously a radio difference, but what else prevents roms being easily ported to Milestone from Droid? Im not sure on the internals differences, but could we start porting.
NB do we even have root !?
we have root on both devices i think the exploit may be the same? forgive me if i am wrong.
(root guide for 2.1) the latest update at time of this post.
http://android.modaco.com/content/m...m/308422/milestone-2-1-update-and-root-guide/
the problem on the milestone as anyone will tell you, the LOCKED BOOT LOADER this isnt a problem for the Droid users, they got this for free. Hopefully with the power of the XDA super Dev team, we will have a solution for this, and start pumping out custom roms!
all of the accessories fit for each other, which maes it handy if you want some cheap bits from china, there isnt any carrier in the uk that has the milestone, what i am saying... carrier.. i mean mobile phone network!
i got my milestone from here. buymobilephones.net on a contract, but you can also get them from expansys, as far as i have researched, they are all unlocked. So you shouldnt even need to post about unlocking the sim.
there is another differnce i remember, if you are loading busybox on your device, this will not load if you use droid root helper from the market, you will need to manually do this via ADB and the loaction on the partition is different.
carphone warehouse sell the milestone on t-mobile and you can install busybox with droid root helper.
The kexec modules are nearly working. So there will be a 2nd bootloader in near future.
http://and-developers.com/motorola_milestone
I messed my first one up when I used droid root helper, but I have recently download titaium backup and that says it has installed busy box for me over the net. But terminal tells me no busy box found, the only way I have had it working was via the manual install.
iamdarren said:
I messed my first one up when I used droid root helper, but I have recently download titaium backup and that says it has installed busy box for me over the net. But terminal tells me no busy box found, the only way I have had it working was via the manual install.
Click to expand...
Click to collapse
Titanium installs busybox in its own data directory so that only it can access it.
Cool that answers that. I want to put busybox back on to use cachemate again. But can't find any instructions. So haven't yet
Main difference is the locked bootloader , there is a signature verification at boot time that prevents us from running custom Kernel .
Its unlikely that the bootloader signature will ever be cracked , other workaround like Kexec will most likely help achieve further mods to our device eventho it seem to be right around the corner there is still much work to be done
iamdarren said:
Cool that answers that. I want to put busybox back on to use cachemate again. But can't find any instructions. So haven't yet
Click to expand...
Click to collapse
Download Busybox and use this to install it:
Code:
ADB push busybox /sdcard/busybox
ADB shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system
# cat /sdcard/busybox > /system/bin/busybox && chmod 700 /system/bin/busybox
# sync
# mount -o ro,remount -t yaffs2 /dev/block/mtdblock6 /system
Its better to push it to xbin and not to bin, as the most apps search there for the busybox
After Titanium had installed busybox, I opened Root Explorer and moved it from Titanium's data folder to /system/xbin (had to temporarily mount R/W to do so, using the button up top). Titanium is still happy as it still finds busybox. Do I need to do anything else for other programs that require it?
cmstlist said:
After Titanium had installed busybox, I opened Root Explorer and moved it from Titanium's data folder to /system/xbin (had to temporarily mount R/W to do so, using the button up top). Titanium is still happy as it still finds busybox. Do I need to do anything else for other programs that require it?
Click to expand...
Click to collapse
your good ..
Hey guys,
I rooted my N1, then (only days later) somehow my microusb port got damaged, and now won't charge or connect to the computer. My guess is that HTC would honor a replacement request regardless of root because it's solely a hardware issue, unless someone thinks otherwise, but I am curious as to whether it's possible to unroot without USB anyway.
Ideas?
You could try the 'Unroot' button in Universal Androot?
Hmm, that just tells me that I'm not rooted.
Hmmm, you could try downloaind a terminal emulator and using that to remove /system/bin/su and /system/app.Superuser.apk although you'd need to us SU to gain the rights to delete them, so not sure if it would like that. Worth a go though.
Edit: Just tested it, that works fine, go for it.
Code:
su
mount -o remount,rw /dev/block/mtdblock3 /system
cd /system/app
rm Superuser.apk
cd ..
cd bin
rm su
exit
why don't you copy a passimg.zip on your sdcard and flash it in hboot?
adbWireless
I really just want to unroot my Captivate and I was wondering if there was a way to do so through adb or terminal. I am on stock 2.2.
okachowwa said:
I really just want to unroot my Captivate and I was wondering if there was a way to do so through adb or terminal. I am on stock 2.2.
Click to expand...
Click to collapse
Take a look at this. It's the one-click root/unroot.
I know you said you wanted terminal, and if you look at the batch files for this program, you should be able to see the commands being used to do the rooting/unrooting.
....Or you could use the program. Either way.
(One other thing - are you wanting to place your phone in a rooted state, or remove it from a rooted state? Rooting is putting it in the rooted state, unrooting is removing it from the rooted state. Not trying to be definition crazy, but knowing what you're wanting to accomplish sometimes requires different steps.)
jmtheiss said:
Take a look at this. It's the one-click root/unroot.
I know you said you wanted terminal, and if you look at the batch files for this program, you should be able to see the commands being used to do the rooting/unrooting.
....Or you could use the program. Either way.
(One other thing - are you wanting to place your phone in a rooted state, or remove it from a rooted state? Rooting is putting it in the rooted state, unrooting is removing it from the rooted state. Not trying to be definition crazy, but knowing what you're wanting to accomplish sometimes requires different steps.)
Click to expand...
Click to collapse
I'm definitely trying to unroot lol and thanks...and I didn't root with that however so should it still work the same?
EDIT: I got E:verification error thing when i used that method. As stated, I'm on 2.2.
Please you guys, I just need to know the commands, I have found some online, but I don't know if they are the same for the Captivate. Please help me. I have root to use the Terminal Emulator, so I need to confirm they are the same.
This is the one I found, is it the same for the Captivate?
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
rm /sdcard/Superuser.apk
rm system/xbin/busybox
rm /system/xbin/su
rm /sdcard/su
rm /sdcard/busybox
mount -t rfs -o remount,ro /dev/block/stl9 /system
exit (first "exit" takes you out of su)
exit (second "exit" takes you out of the terminal)
reboot
Anyone figured out how to do it? I've tried following the guides with no success (gingerbreak). Model is P970g and software is 10a. Country code is TLS.
Anyone have a Telus OB and been able to root it? How did you do it?
I've rooted a couple of them, both 10a on Telus, one of them was pretty easy using z4root. Another one wouldn't work with z4root, latest superoneclick, gingerbreak or manually using adb shell to gingerbreak, rageaggainstthecage & psneuter. I did finally get the stubborn one to root wither an older superoneclick; version 1.6.5. Attached it below as it doesn't seem available in CLShortFuse's thread anymore.
Goodluck
alexredford said:
I've rooted a couple of them, both 10a on Telus, one of them was pretty easy using z4root. Another one wouldn't work with z4root, latest superoneclick, gingerbreak or manually using adb shell to gingerbreak, rageaggainstthecage & psneuter. I did finally get the stubborn one to root wither an older superoneclick; version 1.6.5. Attached it below as it doesn't seem available in CLShortFuse's thread anymore.
Goodluck
Click to expand...
Click to collapse
I tried both z4 and the superoneclick you suggested to no avail.
Do you think it's safe to try flashing another vulnerable rom? 10b or 10c? I'm worried the basebands may be different and the phone will have no voice/data connection.
Running out of ideas.
Attempted to root another one, same model, same version and none of the previous methods worked, was able to root this one as well using a combination of SOC 2.1.1 and the attached ADB Shell.
1. Download and run SuperOneClick 2.1.1, choose psneuter and click Shell Root
2. It should get stuck on step #4, run task manager, end superoneclick and terminate any adb.exe processes. (You should have Shell Root now)
3. Extract ADB.zip and open a command prompt to where you extracted it.
4. Enter the following commands
Code:
adb push su /tmp/
adb push Superuser.apk /tmp/
adb shell
mount -o rw,remount -t ext3 /dev/block/mmcblk0p8 /system
cat /tmp/su > /system/bin/su
cat /tmp/superuser.apk > /system/app/Superuser.apk
chown root.root /system/bin/su
chmod 06755 /system/bin/su
chown root.root /system/app/Superuser.apk
chmod 0644 /system/app/Superuser.apk
reboot
The permissions on /system/bin/su didn't stick the first time for me, and the phone rebooted a couple times, but eventually it all went through. To verify permissions on su, type "adb shell", then "ls -l /system/bin/su". The permission should read -rwsr-sr-x, if it doesn't repeat the shell root process and type
Code:
adb shell
mount -o rw,remount -t ext3 /dev/block/mmcblk0p8 /system
chmod 06755 /system/bin/su
ls -l /system/bin/su
Ok, i've figured out what the problem is. As soon as the adb process from SOC is shut down, the phone soft reboots and I lose temporary root. I've tried the psneuter exploit in the same adb command shell, but it hangs just like SOC. I've tried to be "quick" and get the commands in before the reboot, but it isn't possible.
Suggestions on how I may bypass that? Otherwise i'll wait for the official 2.3 update in september and try again then.
One of the phones I tried it on, did the same thing, ended the adb process and phone would reboot, pushed a file, phone would reboot, set permissions, phone would reboot. Occasionally the phone would appear to hang, buttons flash at the bottom for awhile, phone becomes unresponsive. Just wait a minute or 2 and it should return to normal. I also tried creating a script to do all of the above before the device had time to reboot and it didn't help.
Persistence was the key.
Did you try that ? If following the instructions don't work for you, I let you know how it works for me.
EDIT : Sorry, forget link's thread : http://forum.xda-developers.com/showthread.php?p=14458927
Sent from my LG-P970 using xda premium
Hey i am having the same problem and am fearing bricking my phone from making a mistake. is there an easier method than those above mentioned?
Android 2.2.2
software: v10a
Sobralobo said:
Did you try that ? If following the instructions don't work for you, I let you know how it works for me.
EDIT : Sorry, forget link's thread : http://forum.xda-developers.com/showthread.php?p=14458927
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
This method worked when rooting my wife's P970g.
KDZ file
hey does anyone have the Telus firmware KDZ file? i will need it to restore my phone back to original state to cash in on a waranty (ended up bricking it, had to install a german 1&1 firmware to get it back)
s0dhi said:
This method worked when rooting my wife's P970g.
Click to expand...
Click to collapse
...which ROM did you use, the v10a EEU from the thread?
I'm worried cause on Telus 970g as well.
The_non_rootable said:
hey does anyone have the Telus firmware KDZ file? i will need it to restore my phone back to original state to cash in on a waranty (ended up bricking it, had to install a german 1&1 firmware to get it back)
Click to expand...
Click to collapse
http://lg-phone-firmware.com/index.php?id_mod=1
Ok, I don't think I'm the only one out there that lost root after the JB OTA update today... Anybody else? I was using Voodoo OTA RootKeeper and everything.... Crap... Any news on an exploit yet?
Lost root too. Rootkeeper didn't do it's job. Now just waiting for a solution.
Not sure how useful but someone on the main JB update thread mentioned they were able to restore with a few adb commands. Apparently for some OTA keeps root but doesn't reinstall it correctly with the button and a few adb's will regain it. FWIW.
Odd, mine kept root without an issue. I'm curious why it's different for some.
Mine kept it but I did the full download and booted to stock recovery and did flash update.zip. then restored root
Sent from my DROID BIONIC using xda app-developers app
neo1738 said:
Not sure how useful but someone on the main JB update thread mentioned they were able to restore with a few adb commands. Apparently for some OTA keeps root but doesn't reinstall it correctly with the button and a few adb's will regain it. FWIW.
Click to expand...
Click to collapse
I've looked and looked for any ADB commands to fix root and cant find them, do you have a link to the post? Thanks
Ok, I've also tried Dan Rosenburg's Motochopper exploit and that didn't work either.... We might be stuck without root until a viable exploit pops up.
awaiting for root too.
Hmmm. I kept root using ota root keeper. Just selected protect root and ashed in recovery the new jb
Sent from my DROID BIONIC using xda app-developers app
have you try the razr-blade exploit?
Updated SU with stock ICS, installed Voodoo, backed up root, flashed JB and restored root. I have SU and voodoo says successful but superuser is not working. Tried, razr-blade, and MotoChopper, both a no-go.
I used Voodoo, Updated to JB, and re-rooted unsuccessfully. I've even tried to go in and restore Su manually and change it's permissions but nothing seems to be working. :/
I lost root, but you can bring it back! NOTE: This will ONLY work if you backed up root with Voodoo OTA RootKeeper prior to updating to Jelly Bean!!!
Make sure you have android debugging enabled and mount it as a media device.
Follow these instructions: (copied from another site)
1) Download the unsure su from here and put it somewhere on your C Drive. It will be used in the following push step (Assuming windows) (This is a WIDE OPEN su without any controls). (sparky root i believe?)
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
2) start a CMD window and logon to adb (type "adb shell" without the quotes to log on)
3) su -
4) verify you have root:
id
uid=0(root) gid=0(root)........
If you don't you can try these instead of 'su':
"/system/su-backup" or "/system/su_backup"
5) remount system as RW:
mount -o remount,rw /dev/block/mmcblk0p1 /system
6) make a backup of current su just in case in adb
cat /system/bin/su > /system/bin/su1
7) open a new CMD window and push the su binary from step 1 to the sdcard using the path from where ever you put it.
adb push c:\<some path>\su /sdcard/
8) Then copy it to /system/bin from the adb session where you su'd.
cat /sdcard/su > /system/bin/su
9) Change permissions for SU
chmod 6755 /system/bin/su
10) download superuser (NOT SUPERSU) from play store if you do not have it already.
11) have superuser upgrade the su binary. It may fail to remount system as RO. Just rerun the update in superuser and it will work the 2nd time. You don't need to remount system as RO manually since superuser update of SU will do that for you.
12) congrats. your now rerooted.
13) remove the backup after you know your OKAY.
mount -o remount,rw /dev/block/mmcblk0p1 /system
rm /system/bin/su1
mount -o remount,ro /dev/block/mmcblk0p1 /system
Hope this helps you guys!
Does anyone have the fixed dropbox link for the post above?
So I managed to get root back. Then I downloaded SuperSU and when I tried to update binaries, I lost root. Is there a fix for that?
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
I just googled part of the text and found the source I think
chetmichaels said:
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
I just googled part of the text and found the source I think
Click to expand...
Click to collapse
Yup, that looks right. If this ceases to work soon as well I will go ahead and upload it to my Dropbox as I still have the su file. I included that link you provided into my post above.
Frankie1588 said:
I lost root, but you can bring it back!
Follow these instructions: (copied from another site)
1) Download the unsure su from here and put it somewhere on your C Drive. It will be used in the following push step (Assuming windows) (This is a WIDE OPEN su without any controls). (sparky root i believe?)
2) start a CMD window and logon to adb
3) su -
4) verify you have root:
id
uid=0(root) gid=0(root)........
If you don't you can try these instead of 'su':
"/system/su-backup" or "/system/su_backup"
5) remount system as RW:
mount -o remount,rw /dev/block/mmcblk0p1 /system
6) make a backup of current su just in case in adb
cat /system/bin/su > /system/bin/su1
7) open a new CMD window and push the su binary from step 1 to the sdcard using the path from where ever you put it.
adb push c:\<some path>\su /sdcard/
8) Then copy it to /system/bin from the adb session where you su'd.
cat /sdcard/su > /system/bin/su
9) Change permissions for SU
chmod 6755 /system/bin/su
10) download superuser (NOT SUPERSU) from play store if you do not have it already.
11) have superuser upgrade the su binary. It may fail to remount system as RO. Just rerun the update in superuser and it will work the 2nd time. You don't need to remount system as RO manually since superuser update of SU will do that for you.
12) congrats. your now rerooted.
13) remove the backup after you know your OKAY.
mount -o remount,rw /dev/block/mmcblk0p1 /system
rm /system/bin/su1
mount -o remount,ro /dev/block/mmcblk0p1 /system
Hope this helps you guys!
Click to expand...
Click to collapse
your download link is not working can you check the link.
briafalk said:
your download link is not working can you check the link.
Click to expand...
Click to collapse
Check now. I fixed the link. Sorry about that guys!
Frankie1588 said:
Check now. I fixed the link. Sorry about that guys!
Click to expand...
Click to collapse
I am stuck at steps 3 and 4, it does not seem to be working for me. I am not getting root through adb.