Related
I'm trying to perm root my mytouch 4g using Visionary
I have android 2.2.1 and have successfully temp rooted using Visionary
I download the root folder from HERE
I put them in the root of the SD card and open up Terminal Emulator and type in
su
cd /sdcard/root
sh root.sh
when I type the first line (su) I get the # and am told that Terminal Emulator has been granted superuser permissions.
when I type in the second line (cd /sdcard/root) I get this message
cd: can't cd to /sdcard/root
What could be causing this?
Thanks
Jonathan
The "cd" command is a "change directory" command, and there is no directory called "root" on your SD card, because either you haven't unzipped what you downloaded, or you unzipped it in the wrong place.
Unzipping what you downloaded creates a directory (or a "folder", if you're a Windows user) called "root" that has several files in it -- a kernel module and a script, if I remember correctly. The script loads the kernel module and makes a call to it in order to set S Off.
thank you much, I think I figured out the problem. I'll try again later and see what happens. I'll post back with the results later. Thanks again!
Jonathan
NOTE: Ok, I can now run through the
su
cd /sdcard/root
sh root.sh
commands but when it's done and I check for s-off I don't have it (I still have s-on)
I've tried this twice to no avail. any advise?
i am having the same problem. i've tried this method about 15 times, mostly with visionary r14, but also a couple times with r11. i have also tried the gfree method a couple times as well via the semi-automated method. no s=off!
i have a new MT4G direct from phone upgrade order. i've read of others who have rooted the MT4G before multiple times, but can't do it now with a new phone. i'm wondering if it's something HTC has changed with the newest releases.....
kenrippy said:
i am having the same problem. i've tried this method about 15 times, mostly with visionary r14, but also a couple times with r11. i have also tried the gfree method a couple times as well via the semi-automated method. no s=off!
i have a new MT4G direct from phone upgrade order. i've read of others who have rooted the MT4G before multiple times, but can't do it now with a new phone. i'm wondering if it's something HTC has changed with the newest releases.....
Click to expand...
Click to collapse
HTC was going to install a measure that would prevent "rage methods" from working on their phones. How ever, none of the tech blogs are reporting that this has been rolled out. So i doubt that is the case.
make sure the its set up as sdcard/root. If you've just extracted the folder and copied the extraction to the sdcard it's not set properly.
neidlinger said:
HTC was going to install a measure that would prevent "rage methods" from working on their phones. How ever, none of the tech blogs are reporting that this has been rolled out. So i doubt that is the case.
make sure the its set up as sdcard/root. If you've just extracted the folder and copied the extraction to the sdcard it's not set properly.
Click to expand...
Click to collapse
yes, i understand the root folder in the root of the sdcard, and not 2 root folders. (sdcard/root/root)
like i mentioned, i read posts from a couple people on here with the same problems with new mt4g's after having done it multiple times before with success.
kenrippy said:
yes, i understand the root folder in the root of the sdcard, and not 2 root folders. (sdcard/root/root)
like i mentioned, i read posts from a couple people on here with the same problems with new mt4g's after having done it multiple times before with success.
Click to expand...
Click to collapse
then set up the ADB (see my sig) and do it the long way.
neidlinger said:
then set up the ADB (see my sig) and do it the long way.
Click to expand...
Click to collapse
after doing that, would i start on #4 in this guide?
http://forum.xda-developers.com/showthread.php?t=858996
kenrippy said:
after doing that, would i start on #4 in this guide?
http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
nope you would start @ number 1.
you need to download those files and check the MD5SUM of every download load. the files need to be PERFECT for it to work correctly.
and i cannot stress enough. take your time and read directions. Read through the list a few times and make sure you have a good understanding of what you are doing. Doing that wrong can make your phone an expensive paper weight.
instead of pushing stuff to the "SDK tools folder" you store it to the ADB folder TrueBlue had you create in his walkthrough. And make sure to change your target folder to "c:\adb".
and remember you are choosing to do this. so if you screw it up. it's on your shoulders not mine.
neidlinger said:
nope you would start @ number 1.
you need to download those files and check the MD5SUM of every download load. the files need to be PERFECT for it to work correctly.
and i cannot stress enough. take your time and read directions. Read through the list a few times and make sure you have a good understanding of what you are doing. Doing that wrong can make your phone an expensive paper weight.
instead of pushing stuff to the "SDK tools folder" you store it to the ADB folder TrueBlue had you create in his walkthrough. And make sure to change your target folder to "c:\adb".
and remember you are choosing to do this. so if you screw it up. it's on your shoulders not mine.
Click to expand...
Click to collapse
thanks for all the help/info. i'll hold off for a while to see what else unfolds in the coming weeks in regards to alternate root methods. i don't want to brick this thing, just to get it rooted.
kenrippy said:
thanks for all the help/info. i'll hold off for a while to see what else unfolds in the coming weeks in regards to alternate root methods. i don't want to brick this thing, just to get it rooted.
Click to expand...
Click to collapse
The way this phone is made it's going to be pretty difficult to write a "one click s=off" program.
If you are wanting the benefits of being rooted you can always use VISIONary.apk when you need the root features like AD-HOC tethering or Screen Shots.
neidlinger said:
The way this phone is made it's going to be pretty difficult to write a "one click s=off" program.
If you are wanting the benefits of being rooted you can always use VISIONary.apk when you need the root features like AD-HOC tethering or Screen Shots.
Click to expand...
Click to collapse
what i'd really like to do is remove some bloatware and demo games. (not just hide them) any way to do that aside from perm root?
kenrippy said:
what i'd really like to do is remove some bloatware and demo games. (not just hide them) any way to do that aside from perm root?
Click to expand...
Click to collapse
not really. As soon as you reboot they'll pop right back up.
ok thanks.
Two things.
1. I've decided to put off perm rooting until I can understand adb and use it properly. No need to rush, I've got time.
2. Is it true that given time, effort, and ingenuity there really isn't such a thing as a bricked phone? It can always be recovered, it's just a question of how far you have to go to do it?
I've read around a lot and though I've heard many people talk of bricking their phone, it seems like many say that if you can use things like adb commands you can pretty well fix any issue, it's just difficult.
Like I was saying in point 1, I'm newer to all this and I'm learning so thanks for answering!
Jonathan
lanternslight456 said:
2. Is it true that given time, effort, and ingenuity there really isn't such a thing as a bricked phone? It can always be recovered, it's just a question of how far you have to go to do it?
Click to expand...
Click to collapse
At minimum, I believe the phone requires a functioning bootloader in order to be able to connect via USB to fastboot.
Any update on this? I also just got a mytouch 4g yesterday and am trying to root it. Is it possible right now?
Root the mt4g
Friend, I used the adb method here on xda, after I got the forked childs msg, and restart terminal w/e, make sue to pull out battery. Restart, the LAST THING I DID WAS USE VISIONARY r14, to attempt permroot, took me a week before I figured out to try this, the guide said phone would be rooted after terminal commands went through. So, to recap if u entered everything correctly, (my avg protection was telling me my phone was rooted for a week after I pushed gfree using the adb method but had no s-off, tried visionary permroot, BINGO!) THANKS TO ALL THE HARD WORK/GUIDES ON XDA, using ICE GLACIER ROM, titanium backup, rom manager, root explorer, my internet security (ad free web) set cpu, cache cleaner ng, drocap, couldn't get barnacle to work, the tethering on board works fine. Quadrant standard for benchmarking.
My wifes mt4g arrived today, and I had it perm rooted, with s-off in about 20 minutes, following this guide from the wiki:
http://forum.xda-developers.com/showthread.php?t=858996
Sent from my Nexus One using XDA App
danger-rat said:
My wifes mt4g arrived today, and I had it perm rooted, with s-off in about 20 minutes, following this guide from the wiki:
http://forum.xda-developers.com/showthread.php?t=858996
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
dude this method is great especially if your a noob or cant use adb for whatever reason just use visionary for temp root and then using root explorer move the gfree file to data>local then open terminal emulator and follow the instructions that gives you s-off and allows you to use visionary to permaroot when you reboot and then rommanager it now supports 3.xx so you can flash gingerroms just be careful and have fun
I cannot flash roms or kernel. It won't boot recovery!!! I have stock rooted shift. How do I make a custom recovery? And install roms and kernel
Probably the easiest way is to download ROM manager from the market. The first option in the app is flash clockworkmod. Very fast and automagic. Have fun! Happy flashing.
I have that and kernel manager. Flashed it twice after it didn't work the first time. It hangs up on the HTC boot logo after I try to boot recovery
turn off your phone
power it on while holding vol down.
does the first line say S-OFF or S-ON?
S on I didn't do nand
I've tried a few more things. I used visionary to root my phone. Was that the wrong thing? It all works. But I can't flash. Lol
thronnos said:
I've tried a few more things. I used visionary to root my phone. Was that the wrong thing? It all works. But I can't flash. Lol
Click to expand...
Click to collapse
That's just a temp root. Go into the development section and use the GUI Root and recovery tool...worked for me.
Sent from my PG06100 using XDA App
Alright, is there a way to do this without a computer
thronnos said:
Alright, is there a way to do this without a computer
Click to expand...
Click to collapse
Yeah if you want you can use terminal emulator on your phone just open it up hit su get your super user permissions then start the commands the first time I rooted I did it using adb the second time I rooted I lost my adb and just chrome to phoned all the codes from my pc to root it from my phone
Sent from my PG06100 using Tapatalk
Alright!! Thank you all who have been helping. I have only a few more questions because I'm a little slow ^_^ ok, first. From the emulator I typed Su and gave permission.... now what? I looked for the commands in development and couldn't find. I'm trying to turn s off. I don't care so much about perm or temp root right now as long as I get that annoying s on to be s off. Lmao. I need commands please!!! Assume I have no access to a computer!
Check out the development subforum. It's a sticky thread by bcnice20.
i dont need a signature
Alright I have that, now its not explained there but in order to do that via the terminal do I need to dl the framework and sdk to my phone? I do not have a running computer right now. I had a crap amd system which is officially dead. It's now all spare parts. So doing the shell on a computer isn't going to work for me :/ yes, I'm difficult. Lol
thronnos said:
Alright I have that, now its not explained there but in order to do that via the terminal do I need to dl the framework and sdk to my phone? I do not have a running computer right now. I had a crap amd system which is officially dead. It's now all spare parts. So doing the shell on a computer isn't going to work for me :/ yes, I'm difficult. Lol
Click to expand...
Click to collapse
if you search that thread, there should be an answer.
thronnos said:
Alright I have that, now its not explained there but in order to do that via the terminal do I need to dl the framework and sdk to my phone? I do not have a running computer right now. I had a crap amd system which is officially dead. It's now all spare parts. So doing the shell on a computer isn't going to work for me :/ yes, I'm difficult. Lol
Click to expand...
Click to collapse
the commands given in that thread is the exact ones you would need, but since you're using a terminal emulator in your phone, you don't need adb.
do step 1
skip step 2
do step 3,4,5 via your terminal
do step 6
extra points:
once you're perma-rooted, you can go straight to installing Rom Manager, and flash clockworkrom that way.
then reboot your phone to recovery, and do a nandroid backup.
once that's done, you're all set.
Thank you dude!!!!!!! That rocks!!! I'm at work and I'm doing it right now. This is way more important than work ^_^ anyone else addicted to Android?
thronnos said:
Thank you dude!!!!!!! That rocks!!! I'm at work and I'm doing it right now. This is way more important than work ^_^ anyone else addicted to Android?
Click to expand...
Click to collapse
+1
When the perm root method was finally developed I was at work with no access to a PC. I ended up rooting via phone terminal just because I couldn't bear to wait a couple hours until I got home.
^ Shift Faced
Could someone explain step 1 and 3 for me if I'm using android terminal emulator. I tried it but nothing happened. My device is temprooted. I download the file into the download folder. I use root explorer to extract it... where?? I tried a couple places even the root folder (Its not in SD card) then once its good how do I check the md5 from the terminal. I type Su to get permission then what? The string in the post doesn't seem to do anything no matter how I type it. Or maybe I just don't know the command. I'm fairly new to this kinda thing. :/
That's awesome. I'm feeling the same way. I don't want to wait for a computer it might be a few weeks I'm impatient now lol
Wait, I got part of it. I just need to know how to save the file to the root of the SD card and then how to check the md5sum. Once I know that I'm good to go
Sent from my PG06100 using XDA App
thronnos said:
Wait, I got part of it. I just need to know how to save the file to the root of the SD card and then how to check the md5sum. Once I know that I'm good to go
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Download root explorer and long press the file in your download folder, then back out to your sd card directory and select move. You should be able to check mdsum5 in the term app using the commands given
Sent from my PG06100 using XDA Premium App
dears,
i have rooted 3G Xoom (MZ601).. 3.0.1
now i want to update it to 3.1 or 3.2
and i want to activate the US market ..
please, any one can guide me to do it ..
Simplest way i know.
1. Relock your zoom and go back to stock:
http://forums.androidcentral.com/xo...stboot-official-system-images.html#post708799
2. Update through the system update on your xoom.
3. Once you get up to 3.2 unlock and reroot your xoom:
http://forum.xda-developers.com/showthread.php?t=1170760
+ this way now you can reset it back to stock completely if you ever need too. Step by step guides are very easy to follow. Mostly copy and paste commands into notepad if your lazy like me. The whole process takes maybe 20 minutes.
is3od said:
dears,
i have rooted 3G Xoom (MZ601).. 3.0.1
now i want to update it to 3.1 or 3.2
and i want to activate the US market ..
please, any one can guide me to do it ..
Click to expand...
Click to collapse
Hi ,
I think you can go directly from 3.01 to 3.2 using this guide:
http://forum.xda-developers.com/showthread.php?t=1183416
If you don't already have ClockworkMod recovery v3.2.0.0 R4c installed, pay attention to post #7.
Good luck!
incase you dont have sdk installed put all files in a folder on your C:/ directory with a name you can find. Youll need these in addition to be able to use adb on your computer File name: SDK ADB.zip File size: 359.93 KB put them all in a folder called rootxoom or something.
prowlex said:
1. Relock your zoom and go back to stock:
http://forums.androidcentral.com/xo...stboot-official-system-images.html#post708799
2. Update through the system update on your xoom.
3. Once you get up to 3.2 unlock and reroot your xoom:
http://forum.xda-developers.com/showthread.php?t=1170760
+ this way now you can reset it back to stock completely if you ever need too. Step by step guides are very easy to follow. Mostly copy and paste commands into notepad if your lazy like me. The whole process takes maybe 20 minutes.
Click to expand...
Click to collapse
His Xoom is 3G there is no OTA update to 3.2 for 3G.
I really would not relock and go back to stock. He's rooted and that's more than half the battle.
is3od, the method I posted is for non-US Xooms as long as they are rooted.
i'll try it
prowlex said:
1. Relock your zoom and go back to stock:
http://forums.androidcentral.com/xo...stboot-official-system-images.html#post708799
2. Update through the system update on your xoom.
3. Once you get up to 3.2 unlock and reroot your xoom:
http://forum.xda-developers.com/showthread.php?t=1170760
+ this way now you can reset it back to stock completely if you ever need too. Step by step guides are very easy to follow. Mostly copy and paste commands into notepad if your lazy like me. The whole process takes maybe 20 minutes.
Click to expand...
Click to collapse
thank you for your help... today i'll try it and will inform you about the result.
Dear friends
Could you please confirm that above tutorial can be applied for 3G version of xoom?
I see some of guide with noted that applying for wifi version only.
Regards,
okantomi said:
Hi ,
I think you can go directly from 3.01 to 3.2 using this guide:
http://forum.xda-developers.com/showthread.php?t=1183416
If you don't already have ClockworkMod recovery v3.2.0.0 R4c installed, pay attention to post #7.
Good luck!
Click to expand...
Click to collapse
first i will relock my xoon then i'll update it ..
thank you,
prowlex said:
incase you dont have sdk installed put all files in a folder on your C:/ directory with a name you can find. Youll need these in addition to be able to use adb on your computer put them all in a folder called rootxoom or something.
Click to expand...
Click to collapse
ok
thanks...
k66473 said:
Dear friends
Could you please confirm that above tutorial can be applied for 3G version of xoom?
I see some of guide with noted that applying for wifi version only.
Regards,
Click to expand...
Click to collapse
it should be, because my Q is for 3G Xoom.
is3od said:
it should be, because my Q is for 3G Xoom.
Click to expand...
Click to collapse
You have ignored my posts which are for non-US 3G Xoom. Pleease check them again. I was not the one to tell you to go back to stock, unroot and relock. Please don't do that...no need.
Just try to follow the guide I posted in #3. Good luck.
thanks a lot
okantomi said:
You have ignored my posts which are for non-US 3G Xoom. Pleease check them again. I was not the one to tell you to go back to stock, unroot and relock. Please don't do that...no need.
Just try to follow the guide I posted in #3. Good luck.
Click to expand...
Click to collapse
I really appreciate your help .. thanks a lot ..
adb devices returns no devices
I have followed the tutorial after reading through it several time to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...
big flamingo said:
I have followed the tutorial after reading through it several time to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...
Click to expand...
Click to collapse
Make sure USB Debugging is checked under Settings/Applications/Development. If it is checked, then there is something wrong with your drivers.
big flamingo said:
I have followed the tutorial after reading through it several time to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...
Click to expand...
Click to collapse
Check the thread you started...people have answered there.
okantomi said:
Hi ,
I think you can go directly from 3.01 to 3.2 using this guide:
http://forum.xda-developers.com/showthread.php?t=1183416
If you don't already have ClockworkMod recovery v3.2.0.0 R4c installed, pay attention to post #7.
Good luck!
Click to expand...
Click to collapse
I'd like to do the same as OP, update a rooted stock 3.0.1 euro 3G to 3.2 - I've already come across the thread you link to, but there's something I don't get.
pienut (user whose post you linked to) is saying that he went from 3.0.1 to 3.2, but in step 3 he writes:
Step 3 - Install 3.2 EURO rom:
Just copied the Euro 3.2 update from this post to my SD Card and flashed it from recovery.
Just to be sure, I did a full wipe after flashing.
Click to expand...
Click to collapse
Am I missing something, or is the SD card not disabled in 3.0.1? I know it is for me, afaik it only started working with 3.1 and up. I can't wrap my mind around going from 3.0.1 -> 3.2 using the SD card method, and yet it's mentioned in quite a few more threads and posts.
Ideally, I'd like to update to the Xoom ROM 2.1 Hammerhead (http://forum.xda-developers.com/showthread.php?t=1203635), but in those instructions, too, step 2 says
Download the 2.1 rom zip file and place it on your external sdcard
Click to expand...
Click to collapse
How, if I can't access it in the first place? Should I install 3.1 first before I install Hammerhead? If so, do you know about any step-by-step I can follow?
Sorry to jump in on this thread like this... it was the closest I could find related to my problem after hours of searching and reading. Thanks.
Alright, I figured it out on my own... I took a leap of faith and installed the ClockworkMod Recovery 3.2.0.0 (R4c), booted to recovery, and in there it's possible to mount the SD card under mounts and storage > mount usb storage. It will then appear in Windows as an external drive (as usual).
Yay, learned something new today. Now on to the next battle
Here are the directions and files used to fix this problem (do not type any of the "quotation marks"):
1. Download the .zip file from here: http://www.megaupload.com/?d=YUYEMJNM
and put it on the root of your sdcard. (Do not unzip the file). Then rename it to PD15IMG.zip .
2. Download the miscnew file to your computer (uploaded as attachment to this post). Unzip it and place the miscnew.img file that was in the zip onto the root of your sdcard. You can delete the .zip file after you do this.
3. Boot your phone up like normal and connect your phone to your computer.
4. Make sure your sdcard is NOT mounted (but make sure those 2 files were copied to your sdcard).
5. Go into adb and type "adb shell"
6. Then type, "su"
7. Then type, "dd if=/sdcard/miscnew.img of=/dev/block/mmcblk0p17"
8. Once this is done after about 5 seconds, turn your phone off and unplug from the computer.
9. Once the phone is off, hold down the volume-down key and the power button until you arrive at the bootloader. Once there, the phone should automatically start checking that .zip file you downloaded to the root of your sdcard. After its done checking, it will ask you if you want to continue, and just follow the prompt to say "yes" and YOU'RE DONE!
This guide was made by travisjames and was just put into my own words. His guide was a derivative of Apache14's OTA and Radio downgrade guide for the T-Mobile G2.
Also, thanks to Clarknick27 for tipping me off on how to get back into my phone after it was unbootable.
***Please click "thanks" if this helped you!
Ignore/Wrong thread...
two questions-
if i used gfree, do i need to undo gfree 1st? (you make no mention of rooting techniques, and if this undoes all those or not)
second, my phone, about a month ago, lost data connectivity on the usb port-- in other words, it charges fine, but i can not get any computer to pick it up any more to transfer files are use adb, which is a royal pain. -- can i use terminal emulator to accomplish your commands, or am I SOL ?
thanks
Yes, you need to undo Gfree.
Yes, you can run the commands from Terminal Emulator.
Added to Wiki.
thanks jack,
would the syntax be exactly the same as above via term em?
Yes, just skip the "adb shell" command.
Is this to undo 2.3.4 GB update and take it back to 2.2.1?
How do I undo gfree? And if I just run the pg15img will I keep root? I need a way to return to stock but rooted.
Sent from my Incredible 2 using XDA App
andrewp3481 said:
How do I undo gfree? And if I just run the pg15img will I keep root? I need a way to return to stock but rooted.
Sent from my Incredible 2 using XDA App
Click to expand...
Click to collapse
First question, Here is the thread you need to undo gfree (get s-on) http://forum.xda-developers.com/showthread.php?t=858996 (about half way down OP)
Second question, no you will not keep root
witch stock rom do you want rooted, stock 2.3.4 can not be rooted right now
So... to summarize, this would be to revert back to Android 2.3.4, sense 3.5 STOCK, without root, eng. hboot, or s=off.
In other words, if you purchased a MT4G now, or received a replacement MT4G with 2.3.4.... Following these steps will give you this new gingerbread stock state (approximately).
Please confirm. Thanks!
can i use this steps with terminal emulator on my phone instead of adb?
unciviilized said:
can i use this steps with terminal emulator on my phone instead of adb?
Click to expand...
Click to collapse
Yes...check the 3rd and 4th post of this thread....
Just curious, so if I flash this ROM in recovery, will I lose root, s-off, etc.?
What I'm trying to do is flash the phone to the MT4G stock rom (which I assume this is), use gfree to sim unlock it, then revert back to my nandroid backup, so I wanna make sure this will not interfere with my root access before I proceed to flashing it. Thanks in advance to whoever answers me~!
ronin178 said:
Yes...check the 3rd and 4th post of this thread....
Click to expand...
Click to collapse
ok so when im on emulator i do "s" and it says permission denied,
then i got to command prompt and it says adb shell is not recognized as and internal or external command. Any suggestions?
unciviilized said:
ok so when im on emulator i do "s" and it says permission denied,
then i got to command prompt and it says adb shell is not recognized as and internal or external command. Any suggestions?
Click to expand...
Click to collapse
You don't need to type adb shell because you are on terminal emulator.
Just type su to gain superuser access.
Then type dd if=/sdcard/miscnew.img of=/dev/block/mmcblk0p17
Make sure you have the file miscnew.img in the root of your sd card.
Absolutely Perfect
I have looked and looked all over both XDA and the Interent in general. I was trying to restore my Glacier (MyTouch 4g) from stock 2.3.4 to stock 2.2. NOTHING worked. It got to the point that I didn't even remember everything that I tried. I followed this guide to the T. PERFECT!!! I am now back to having my phone exactly how I left the Tmo store with it.
I CANNOT THANK YOU ENOUGH!!
Great work in helping people out that don't understand. And making it a less strenious process
Sent from my HTC Glacier using xda premium
Jack_R1 said:
Yes, you need to undo Gfree.
Yes, you can run the commands from Terminal Emulator.
Added to Wiki.
Click to expand...
Click to collapse
Sorry, a complete noob to "gfree". I'm a new convert to GSM as I was with SPrint CDMA for 10 years until a couple weeks ago. I've rooted Samsing phones but never an HTC.
Anyways, I just purchased a MyTouch that had been rooted and loaded with Virtuous ROM. It's for my wife and she wants it back to stock. I tried all your directions exactly but still will not work. I'm assuming it's this "gfree" issue. I followed the link to the other thread but it's not clear on exactly what I need to do in my situation.
When I run the bootloader, it says bad or no such image... I have confirmed I have PD15IMG.zip and miscnew.img in the sdcard root directory.
Can someone please show me in simplified terms. Thanks!
socal88 said:
Sorry, a complete noob to "gfree". I'm a new convert to GSM as I was with SPrint CDMA for 10 years until a couple weeks ago. I've rooted Samsing phones but never an HTC.
Anyways, I just purchased a MyTouch that had been rooted and loaded with Virtuous ROM. It's for my wife and she wants it back to stock. I tried all your directions exactly but still will not work. I'm assuming it's this "gfree" issue. I followed the link to the other thread but it's not clear on exactly what I need to do in my situation.
When I run the bootloader, it says bad or no such image... I have confirmed I have PD15IMG.zip and miscnew.img in the sdcard root directory.
Can someone please show me in simplified terms. Thanks!
Click to expand...
Click to collapse
If you are new to this rooting stuffs, i suggest don't go with methods, that have potential to brick your phone.
Just do this simple method, Follow the link in my signature, you will see a Rooted version of the stock 2.3.4 rom.
Just flash the Rom through your recovery.........no big deal.......easy way to get the stock feel.....
Follow the instructions carefully.........Happy Flashing........
Thanks for the great help. One more question -- How do I turn "quick boot" off?
Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!
bohemianRhapsody said:
Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!
Click to expand...
Click to collapse
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.
root is easy
bohemianRhapsody said:
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.
Click to expand...
Click to collapse
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition
it0 said:
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition
Click to expand...
Click to collapse
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?
Lukas_a_1996 said:
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?
Click to expand...
Click to collapse
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.
it0 said:
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.
Click to expand...
Click to collapse
Thanks for the reply . I tried to run the command in impactor but whatever i do i get "Signature bugs unavailable" could it be that i have the wrong ADB drivers installed or is my Impactor setup wrong?
Edit: yeah im running 4.1.2 Build A1001231
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
All the adb commands basically work but nothing works with impactor i just get error
it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
Bump!
How to Root Medias N05e
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks
nguyenbuulam said:
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks
Click to expand...
Click to collapse
There is a way for temp root N05E, basically u can use pm disable command or other su stuff. But u cannot mount system rw right now.
Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working
How to enter recovery mode?
Despite starting this thread, in the end I never did bother to attempt rooting.
Anyway, unfortunately now the phone refuses to boot. Not triggered by anything obvious, haven't installed any new software recently, etc. Just hung one day and then when I removed and re-inserted the battery, it won't get any further than the "docomo" splash screen. I.e. the OS doesn't appear to be getting bootstrapped at all. The "docomo" splash screen appears and disappears then the phone sits there with both screens powered up but blank.
As it happens, I had ADB Debug enabled in the developer options at the time, so I've tried to see if I can adb shell into the device, but no luck. Not surprised as it's clearly not getting far enough into the boot for that to work.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?
bohemianRhapsody said:
Despite starting this thread, in the end I never did bother to attempt rooting.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?
Click to expand...
Click to collapse
In recovery mode, clear cache, etc..
To get there hold volume down and power at the same time,then you'll see the broken android then wait/ press vol down a couple of times to see the menu.
GRbit said:
Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working
Click to expand...
Click to collapse
did you ever figure out the recovery keys?
hamishhhhs said:
did you ever figure out the recovery keys?
Click to expand...
Click to collapse
No I didn't(
I'm actually sold this phone and lost interest in the topic.
GRbit said:
No I didn't(
I'm actually sold this phone and lost interest in the topic.
Click to expand...
Click to collapse
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far
hamishhhhs said:
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far
Click to expand...
Click to collapse
Sorry, but this was too long time ago. Nothing left
GRbit said:
Sorry, but this was too long time ago. Nothing left
Click to expand...
Click to collapse
how would j be able to get the files from my phone?
hamishhhhs said:
how would j be able to get the files from my phone?
Click to expand...
Click to collapse
I dunno man.
I've already described (in the first post you have quoted) what I achieved with this github repo https://github.com/android-rooting-tools/android_run_root_shell . That's all I've got.