Related
I rooted my Htc nexus one, droid, droid X, and the htc evo. I just bought the mt4g. Im good at procedures. I cant unlock the S off. Ive done every single. way visonary, gfree, emulator, and adb. and even tired some guyz zip. for some reason. I cant now root this freaking phone. Ive tired multiple times and nada. Is there anything out there that works. I even tired the root explorer. nothing. did they put a different lock on this phone. i got it a week ago and nothing. HELP any one ?
My wife's MT4G arrived last weekend, and I rooted it with s-off in a few minutes. This is the method I followed:
http://forum.xda-developers.com/showthread.php?t=858996
Sent from my Nexus One using XDA App
Go to Settings >> About Phone and look for the Baseband Version. What do you see there?
jdkoren said:
Go to Settings >> About Phone and look for the Baseband Version. What do you see there?
Click to expand...
Click to collapse
HTC has yet to push out the OS that will prevent the Rage method from working. Even if they did the ./gfree method should still work.
Im gonna try
baseband version12.28b.60.140eU_26.03.02.26_m
Thats what it says. Im gonna keep trying this method. thanks guyz for the help. Im just baffled.
Sir0 said:
baseband version12.28b.60.140eU_26.03.02.26_m
Thats what it says. Im gonna keep trying this method. thanks guyz for the help. Im just baffled.
Click to expand...
Click to collapse
if you are doing the "ultimate guide" look at the screen, the phone and the ADB Shell commands, and see if anything says about a fail or error between each step.
neidlinger said:
HTC has yet to push out the OS that will prevent the Rage method from working. Even if they did the ./gfree method should still work.
Click to expand...
Click to collapse
Reading my mind. I guess that was only for the G2 then.
I'm guessing temproot works with Visionary?
Does the ./gfree -f say anything about errors at the end? It seems to be kind of particular about when you reboot. I also found that I had some files from my previous phone (warranty replaced mt4g) on my sd card. It was not until i removed those files that the ./gfree -f worked.
Here is what I did.
Temproot via visionary.
ADB push the gfree files to /data/local
terminal emulator
su
cd /data/local
chmod 777 gfree
./gfree -f
reboot
temproot with system r/w
permroot, should cause a reboot.
jdkoren said:
Reading my mind. I guess that was only for the G2 then.
Click to expand...
Click to collapse
well no not really. from the blogs that i've been reading HTC will be pushing out a ROM update that will prevent all "Rage against the cage" style of rooters from working on their ROMs. So the HTC Glacier is included. but the ./gfree method i don' "think" uses Rage to work.
Another thing to watch is that when a guide says to power off, you pretty much have to pull the battery, because the MT4G typically just goes into hibernation, and doesn't do a true power cycle...
Sent from my Nexus One using XDA App
Ive giving up
Ive tired and ive tired and nothing, Im about to send this phone back. NOT. but wait and see it out. Try the next method. If anything comes out. Thank you guyz for the support. Im gonna wait it out stock or now.
I was having a hard time just like you. I ended up doing it all on the phone (no pc)
Temp root & r/w in visionary
Copied gfree to /data/local with root explorer
terminal emulator
su
cd /data/local
chmod 777 gfree
./gfree -f
reboot
temproot with system r/w
permroot, should cause a reboot.
Just read & follow all steps in the True s-off guide right after step 4 where it says "optional"
Sent from my HTC Glacier using XDA App
lincoln131 said:
I'm guessing temproot works with Visionary?
Does the ./gfree -f say anything about errors at the end? It seems to be kind of particular about when you reboot. I also found that I had some files from my previous phone (warranty replaced mt4g) on my sd card. It was not until i removed those files that the ./gfree -f worked.
Here is what I did.
Temproot via visionary.
ADB push the gfree files to /data/local
terminal emulator
su
cd /data/local
chmod 777 gfree
./gfree -f
reboot
temproot with system r/w
permroot, should cause a reboot.
Click to expand...
Click to collapse
Perm root never wanted to run for me, so after making system r/w I used ROM manager to flash clockwork recovery and then flashed Iced Glacier.
My wife's phone was impossible to S-OFF. It would even flash the eng hboot successfully and still show S-ON. Grankin suggested it was a faulty eMMC controller; swapped it and the phone rooted first try. I was at my wit's end after my phone was so simple.
This was all pre-gfree, FYI, so I don't know if that would have worked on her original phone or not. Seriously consider a swap if nothing else works.
I was the same way. I was about to pull my hair out. Then I did the gfree method and got s-off in one try and in less than ten minutes. Definitely the way to go.
Sent from my HTC Glacier using XDA App
I followed this method: http://forum.xda-developers.com/showthread.php?t=858021
Make sure that you leave the option "temproot on boot" unchecked.
Works like a charm.
Hours later
I got it.SERiously everyone thank you so much. cost me 2 bucks. I ended getting root explorer. ANd i Copied gfree andro zip to my sd card. Then i Moved the file gfree. To DATA/local AND put it In there. Ta da
su
#cd data/local hit enter
#chmod 777 gfree Hit enter
#./gfree -f
THen u get all these commands. says DOne turn of the device.
HOLD volume down. POWER button and S off. thank you i just got home and did this method thanks guyz your all awesome. wow the support. just when i was about to give up. Ive done other phones but this one was a lil ticky. THank U
Sir0 said:
I got it.SERiously everyone thank you so much. cost me 2 bucks. I ended getting root explorer. ANd i Copied gfree andro zip to my sd card. Then i Moved the file gfree. To DATA/local AND put it In there. Ta da
su
#cd data/local hit enter
#chmod 777 gfree Hit enter
#./gfree -f
THen u get all these commands. says DOne turn of the device.
HOLD volume down. POWER button and S off. thank you i just got home and did this method thanks guyz your all awesome. wow the support. just when i was about to give up. Ive done other phones but this one was a lil ticky. THank U
Click to expand...
Click to collapse
Super Manager is a free Root explorer, and would of done the same thing. So if your phone moved the file to the correct spot then there is something wrong with your ADB.
kenrippy said:
I was having a hard time just like you. I ended up doing it all on the phone (no pc)
Temp root & r/w in visionary
Copied gfree to /data/local with root explorer
terminal emulator
su
cd /data/local
chmod 777 gfree
./gfree -f
reboot
temproot with system r/w
permroot, should cause a reboot.
Just read & follow all steps in the True s-off guide right after step 4 where it says "optional"
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Where did you get the gfree file for this method?
idelgado782 said:
Where did you get the gfree file for this method?
Click to expand...
Click to collapse
Should be the first download in this thread
http://forum.xda-developers.com/showthread.php?t=858996
I have searched google far and wide, found a few cases of similar issues but haven't found a solution yet. Got my T-mobile g2 /DZ about 2 months ago, love the hardware and the form factor, but I cannot stand stock froyo. First of all:
Phone build/firmware (?) number is: 1.22.531.8
Release keys: cl277427
I initially tried rooting the phone with visionary r14, which gave me a temp root, then rebooted when I tried perm-root. Ever since then, the program hangs when trying to even temp root (I have tried visionary r11,12,13, and 14, as well as uninstalling and reinstalling countless times [not to mention downloading from different sources]).
After a bit of searching, decided to try rage method - again it didnt work (terminal emulator > /data/local/tmp/rage - permission denied) no matter how many times I tried it.
Tried rage method with gfree (both .02 and .04), which is where I had the most success. I managed to get s-off, but still no superuser access. The problem occurs when I enter the code /data/local/tmp/root
described in this page: http://forum.xda-developers.com/wik...Subsidy_Unlock.2C_SuperCID.2C_and_Radio_S-OFF where it tells you how to 'lock in' the root.
After entering the '/data/local/tmp/root' code, I get an error message that reads something like:
mkdir failed for /system/xbin/, File exists
cp: can't stat `/system/xbin/busybox': Not a directory
Unable to chmod /system/xbin/busybox: Not a directory
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
I have checked, double-checked, and triple-checked that I have pushed busybox etc correctly, and they definitely write to the folder as I am not getting any error messages in CMD.
I would greatly appreciate anyone who can give me a straight answer as to what to look for (somebody said you can't have a file/folder on SD card called 'su' so I have checked that). This is driving me crazy - I bought the G2 thinking froyo would be so much better than Symbian/Motoblur, but I am really disappointed. Even Launcherpro etc are pretty lame compared to some of the custom roms out there.
Please help me!
Alternatively, seeing as I have s-off, any way to flash a rom without superuser? Sorry for the noob question
s-off and gfree ? i don't have g2 version, only desire z. but you can always flash clockwork recovery from adb fastboot. using that, you can switch to other ROM or backup the current one...
fajarep said:
s-off and gfree ? i don't have g2 version, only desire z. but you can always flash clockwork recovery from adb fastboot. using that, you can switch to other ROM or backup the current one...
Click to expand...
Click to collapse
Can you give me a bit more detail? About to try and flash a pre-rooted modaco rom. Will probably have to wipe the phone so if it doesnt work I will try gfree again on the wiped phone
Bumping bump
Anybody?...
Still needing help on this
I am trying to root a motorola i886. Its a really wierd nextel iDEN PTT phone that is running (i believe) android 2.0 or 2.1 but has no touchscreen...
Basically I have been able to get a root shell (#) from 'adb shell' by pushing some program called psneuter to the phone and running it. Once I had this I could install apps via adb ok, but it seems like whenever I try to run any apps that require root they error saying they do not have root access.
As far as I can tell pretty much every rooting guide for every other phone has you putting 'su' and sometimes 'busybox' into /system/bin and 'Superuser.apk' into /system/app. I did both of these but still got the same errors about apps not having root. I tried a few different versions of these files I found from different sites to no avail. Running su on a terminal emulator on the phone itself would get the error "operation not allowed" or something like that. Then I found some other guide where you just copy 'sh' to 'su' and chmod su to 4755. When I did that I could get to a # prompt on the phone's terminal emulator app by typing 'su' but still got root errors for apps that need root.
I though maybe someone here would know something that I missed. As far as I can tell, I have applied the correct permissions to all these files or have at least tried every combination I can think of to no avail (shouldn't chmod 777 just make everything work?)
Also, does the phone usually come with a stock version of busybox on it? Do you need a specific version of these files for your device or version of android?
When an app on the phone tries to get root access is it just basically trying to run 'su' internally or something like that?
Also forgot to mention I have tried all the one-click-root apps and they do not work for this stupid phone. (well the super one click one was how I figured out how to get the adb shell root but the regular root button doesn't work...)
I can't help with your specific questions, but there is some info about rooting the i1, another iDEN with Android. Although it looks like the i1 is actually Android, and not the Motorola-altered, not-really-Android, proprietary software that the i886 has.
http://www.howardforums.com/showthread.php/1662431-Motorola-i1-Rooted
http://forum.cyanogenmod.com/topic/5520-ive-rooted-my-i1/
garbb said:
I am trying to root a motorola i886. Its a really wierd nextel iDEN PTT phone that is running (i believe) android 2.0 or 2.1 but has no touchscreen...
Basically I have been able to get a root shell (#) from 'adb shell' by pushing some program called psneuter to the phone and running it. Once I had this I could install apps via adb ok, but it seems like whenever I try to run any apps that require root they error saying they do not have root access.
As far as I can tell pretty much every rooting guide for every other phone has you putting 'su' and sometimes 'busybox' into /system/bin and 'Superuser.apk' into /system/app. I did both of these but still got the same errors about apps not having root. I tried a few different versions of these files I found from different sites to no avail. Running su on a terminal emulator on the phone itself would get the error "operation not allowed" or something like that. Then I found some other guide where you just copy 'sh' to 'su' and chmod su to 4755. When I did that I could get to a # prompt on the phone's terminal emulator app by typing 'su' but still got root errors for apps that need root.
I though maybe someone here would know something that I missed. As far as I can tell, I have applied the correct permissions to all these files or have at least tried every combination I can think of to no avail (shouldn't chmod 777 just make everything work?)
Also, does the phone usually come with a stock version of busybox on it? Do you need a specific version of these files for your device or version of android?
When an app on the phone tries to get root access is it just basically trying to run 'su' internally or something like that?
Also forgot to mention I have tried all the one-click-root apps and they do not work for this stupid phone. (well the super one click one was how I figured out how to get the adb shell root but the regular root button doesn't work...)
Click to expand...
Click to collapse
PM to me,i rooted sucefully, and install many applications with android SDK suite.
Regards.
geminis said:
PM to me,i rooted sucefully, and install many applications with android SDK suite.
Regards.
Click to expand...
Click to collapse
Wow, I can't believe someone found this thread and replied after so long. Thanks, but in the meantime I actually figured out how to root it fully and get root apps to work. I think i just tried different su's and superuser.apk's that I found on the internet until one worked...
Now, if you have figured out how to change the nextel push-to-talk chirp/beep sounds then let me know how you did that. I actually found the .wav files for the PTT sounds in some .apk in /system (phone.apk I think?) but for some reason changing them had no effect on the sound the phone makes when using the push-to-talk feature...
Its been 10 years but do you still have the firmware for this device? I need to flash it, it doesnt finish booting up
I don't have a full ROM .zip file for this phone, only some update .zips. But the first link result for a google search for "motorola admiral stock rom" worked for me for downloading a file.
Wrong phone, sorry.
Sorry but i don't understand. Isn't the Motorola admiral a different device? Does that zip work for the i886? If so, how do I flash it, because the i886 doenst have a recovery mode.
Oh, oops sorry, I was confusing this phone with another one. I looked and I don't have and firmware files for this, sorry.
OK, thanks for replying
Hey guys. I admit it....I'm a noob here (man it hurts to say that).
Anyway, I've been attempting to root my Tab 2 10.1 (P5113 w/ 4.0.4 upgrade) using the method weltwon describes here: thread 1657056 and I keep running into the following problem. When attempting to root it Odin keeps getting stuck at the "recovery.img" step (I've let the tablet sit for nearly 30 minutes at that step with no luck).
Based on some other posts I've attempted all the following with no luck:
Removed Lockout Security & Antivirus from the tablet
Disabled antivirus on the computer
Ensured the tablet is directly plugged into a motherboard usb port
Nothing has helped. The only thing I haven't tried is shifting to a different computer (only have a single computer at home). Fortunately I can force reboot the tablet and it comes back up to the stock ROM with no issues.
I'm using Odin V1.85_3 and running Windows 7 64-bit. Any ideas would be greatly appreciated.
Alan
SlickAl41 said:
Hey guys. I admit it....I'm a noob here (man it hurts to say that).
Anyway, I've been attempting to root my Tab 2 10.1 (P5113 w/ 4.0.4 upgrade) using the method weltwon describes here: thread 1657056 and I keep running into the following problem. When attempting to root it Odin keeps getting stuck at the "recovery.img" step (I've let the tablet sit for nearly 30 minutes at that step with no luck).
Based on some other posts I've attempted all the following with no luck:
Removed Lockout Security & Antivirus from the tablet
Disabled antivirus on the computer
Ensured the tablet is directly plugged into a motherboard usb port
Nothing has helped. The only thing I haven't tried is shifting to a different computer (only have a single computer at home). Fortunately I can force reboot the tablet and it comes back up to the stock ROM with no issues.
I'm using Odin V1.85_3 and running Windows 7 64-bit. Any ideas would be greatly appreciated.
Alan
Click to expand...
Click to collapse
Keep trying... odin sucks. Heimdale is better, but it is a little more complicated lol still figuring it out on my end with my infuse every once in a while.
If nothing else works you might be able to restore to stock... but I agree Heimdall is a better option.
Ryanscool said:
Keep trying... odin sucks. Heimdale is better, but it is a little more complicated lol still figuring it out on my end with my infuse every once in a while.
Click to expand...
Click to collapse
Heimdall did it. Thanks for pointing me that direction. :highfive:
SlickAl41 said:
Heimdall did it. Thanks for pointing me that direction. :highfive:
Click to expand...
Click to collapse
Well, I thought Heimdall did it. Guess I celebrated a bit early there. When attempting to boot into CWM I get thrown over to the Stock Android Recovery. Based on some more searching it looks like I'll have to roll back to 4.0.3 before flashing recovery.img. Back to the web and to figure that portion out.
Alan
SlickAl41 said:
Well, I thought Heimdall did it. Guess I celebrated a bit early there. When attempting to boot into CWM I get thrown over to the Stock Android Recovery. Based on some more searching it looks like I'll have to roll back to 4.0.3 before flashing recovery.img. Back to the web and to figure that portion out.
Alan
Click to expand...
Click to collapse
Alan, that's because the tabs have a script called install-recovery.sh that re-installs the stock recovery on each boot. you will need to find and remove that before the recovery flash will hold.
trying to find the thread that talked about where that script is located.... but if you have root explorer installed search and you'll find it. I would suggest saving a copy of it to the sdcard before removing it from the system... just incase it is ever needed for anything.
Ryan79 said:
Alan, that's because the tabs have a script called install-recovery.sh that re-installs the stock recovery on each boot. you will need to find and remove that before the recovery flash will hold.
trying to find the thread that talked about where that script is located.... but if you have root explorer installed search and you'll find it. I would suggest saving a copy of it to the sdcard before removing it from the system... just incase it is ever needed for anything.
Click to expand...
Click to collapse
Ok, now I feel like my head is starting to spin. The script is located in /etc (not to surprising there). This is where my head starts to spin. /etc has permissions of 777 (which rather blew my mind based on past unix and linux experience). Install.recover.sh has permissions of 544 which I would expect for an executable in /etc. That means I have to have root permissions to modifiy the file since root is the owner.
So, from my understanding I need to get CWM recovery installed so I can flash cwm-root which will grant me root access......seems kinda like a case of the chicken and the egg to me.
SlickAl41 said:
Ok, now I feel like my head is starting to spin. The script is located in /etc (not to surprising there). This is where my head starts to spin. /etc has permissions of 777 (which rather blew my mind based on past unix and linux experience). Install.recover.sh has permissions of 544 which I would expect for an executable in /etc. That means I have to have root permissions to modifiy the file since root is the owner.
So, from my understanding I need to get CWM recovery installed so I can flash cwm-root which will grant me root access......seems kinda like a case of the chicken and the egg to me.
Click to expand...
Click to collapse
Ok, I think I may see how to get around this.....Heimdall is rebooting my tablet after the recovery flash. Need to figure out the command line parameter that prevents reboot and then reboot directly to CWM Recover (guessing there but that's what I'm going to look for at least).
That did it.....found the --no-reboot common argument for Heimdall and then manually rebooted directly to CWM Recovery. That allowed me to boot into CWM Recovery without the install.recover.sh shell running. Waiting for first reboot after flashing the CWM-Root.....rebooted installed SuperUser and disabled SuperSU but still can't rename or delete the /etc/Install.recover.sh (even though the root browser was given su permissions by SuperUser) ..... sigh
I know I'm rooted because I can reboot using Quick Boot after granting it su access - that's just strange.
Finally, figured it out...You can't modify or delete Install.recover.sh in /etc. You must do it at the following location /system/etc
Alan
SlickAl41 said:
Ok, I think I may see how to get around this.....Heimdall is rebooting my tablet after the recovery flash. Need to figure out the command line parameter that prevents reboot and then reboot directly to CWM Recover (guessing there but that's what I'm going to look for at least).
That did it.....found the --no-reboot common argument for Heimdall and then manually rebooted directly to CWM Recovery. That allowed me to boot into CWM Recovery without the install.recover.sh shell running. Waiting for first reboot after flashing the CWM-Root.....rebooted installed SuperUser and disabled SuperSU but still can't rename or delete the /etc/Install.recover.sh (even though the root browser was given su permissions by SuperUser) ..... sigh
I know I'm rooted because I can reboot using Quick Boot after granting it su access - that's just strange.
Finally, figured it out...You can't modify or delete Install.recover.sh in /etc. You must do it at the following location /system/etc
Alan
Click to expand...
Click to collapse
Hey Alan, sorry... been away from the forums for a couple days. But it looks like you got it figured out you are correct on the Heimdall command, the only thing different that I did is that I already had root explorer purchased... so after the SuperUser install I just ran it to move the install_recover.sh to my SD card
Glad to hear you got it working!
I am trying to Flash the Stock ROM on my Galaxy Y PRO after it is gone into a bootloop (by itself), i am using ODIN , but it got stuck on Flashin the recovery img
i tried all The USB ports of my computer and only 1 worked. Please i need help and a sure answer thx
MultipleMonomials said:
If nothing else works you might be able to restore to stock... but I agree Heimdall is a better option.
Click to expand...
Click to collapse
How to use Heimdall when I have bl, ap, etc
Hi, Im new to this device but right after I got it I did the right thing and voided my warranty Rooted and installed a custom recovery. The recovery has been a bit of a pain but that is a story for another thread.
The problem I am having is that when I try to take a backup from recovery it errors (I forget the error, sorry. ) however the backup is still right there in the backup directory. I tried a second attempt at a backup (to see if it would error again) and these two backups filled my remaining memory. lI of course used my file explorer to delete these extraneous backups-- only to see that they are not deletable. I also tried on the PC. The folder lists read and write in the permissions. I am kind of at a loss as to what to do. IIRC correctly from a while back with this issue the answer lies somewhere in CHMOD, but I cant quite seem figure it out. CD to the directory in a terminal emulator and then CHMOD 777? Thanks for your help in advance.
knoober said:
Hi, Im new to this device but right after I got it I did the right thing and voided my warranty Rooted and installed a custom recovery. The recovery has been a bit of a pain but that is a story for another thread.
The problem I am having is that when I try to take a backup from recovery it errors (I forget the error, sorry. ) however the backup is still right there in the backup directory. I tried a second attempt at a backup (to see if it would error again) and these two backups filled my remaining memory. lI of course used my file explorer to delete these extraneous backups-- only to see that they are not deletable. I also tried on the PC. The folder lists read and write in the permissions. I am kind of at a loss as to what to do. IIRC correctly from a while back with this issue the answer lies somewhere in CHMOD, but I cant quite seem figure it out. CD to the directory in a terminal emulator and then CHMOD 777? Thanks for your help in advance.
Click to expand...
Click to collapse
If you are using TWRP, It is not possible to delete twrp backup images using normal ways. Either you can install esfile explorer and navigate to device/data/media/0/twrp/backups/ and delete from there. Or use file manager in TWRP to delete the backups. I think there is also another option in twrp to view or delete backups.
Sent from my Moto G using Tapatalk 2
Ill check out the other things you said, but Im actually getting this problem in ESfile... Ill report back if I can get at it through the recovery.
Edit: ESfile works. I followed the path you laid out ad got there just fine I didnt realize Id have to take such a roundabout path. Thank you.