I spent All day yesterday trying to root my phone. I tried different methods but none seem to work. I have used visionary 11 and 14. I need help. Any suggestions?
Sent from my HTC Glacier using XDA App
trofeo.08 said:
I spent All day yesterday trying to root my phone. I tried different methods but none seem to work. I have used visionary 11 and 14. I need help. Any suggestions?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Have you tried Cyanogen's method ?
how do you know you are not getting SU access.
No and through hboot
Sent from my HTC Glacier usting XDA App
trofeo.08 said:
No and through hboot
Sent from my HTC Glacier usting XDA App
Click to expand...
Click to collapse
Okay so you are trying to S=off i take it. If you have Androids SDK on your computer with ADB up and running i highly suggest Cyanogen's method if nothing else is working.
Personally i have tried The Unlockr's, the Ultimate Guide and Cyanogen's and they have all worked perfectly. Yes i unrooted and rerooted my phone 3 times.
I had to go hunting through your post history, since you started this new thread. Looking through that history, it appears that you might have been able to obtain obtain Temp root with VISIONary. If you got that far, you would be able to confirm it by running a shell and issuing the "su" command. It is not clear to me that you confirmed this.
The VISIONary method requires temp root as the first step, but to get S-Off with VISIONARY typically requires one to download and install a shell script into the proper directory structure while in temp root mode, and executing that script, and noting the scripts success.
I can't tell how far you've gotten, but many newbies have had trouble putting this root.sh script in the right place, executing it, and interpreting the results.
VISIONary worked for me, but I was careful to ensure I had the 2.2.1 update from T-Mobile first, and I studied all the guides and howto documents carefully before starting.
There are other methods. If VISIONary has caused you grief, try another. You will find any number of videos on Youtube that show step by step instructions, as well. Just be sure you're looking at MT4G documentation, and not the steps for some other phone.
Ok i see if it works
Sent from my HTC Glacier using XDA App
Thanks I have tried to do it through visionary. Now I do the command script method as well. The sh root.sh . And once I reboot I to hboot still shows s on. Now. I have v 2.2.1. Sine I just recently got this phone seems they come with the update alreAdynow. The thing I prob get lost is when I enter sync. Then nothing happens. I tKe out my battery Nd then power on and still hboot shows s on. Now I was T home all day yesterday trying to figure it out. Yesterday I downloaded the development kit but I didn't quite understand how to work it.
Sent from my HTC Glacier using XDA App
jggimi said:
I can't tell how far you've gotten, but many newbies have had trouble putting this root.sh script in the right place, executing it, and interpreting the results.
Click to expand...
Click to collapse
to the OP if you are having problems getting the Root.sh file in the right place.
What you have to do is download the root.sh files. Which can be found Here (link to megaupload via the unlockr)
Unzip that folder. Then enter that folder you will see a second folder (first one is the folder you get from the extraction, the second one is in that folder) The attachment should help you out.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
once you store the root folder on the SDcard the phone will see it like this.
on the left side you will see what the phone see in the SD card. Notice the Root folder... once you open that you will three files, (on the right side).... that is what you need to have on your phone.
trofeo.08 said:
Thanks I have tried to do it through visionary. Now I do the command script method as well. The sh root.sh . And once I reboot I to hboot still shows s on. Now. I have v 2.2.1. Sine I just recently got this phone seems they come with the update alreAdynow. The thing I prob get lost is when I enter sync. Then nothing happens. I tKe out my battery Nd then power on and still hboot shows s on. Now I was T home all day yesterday trying to figure it out. Yesterday I downloaded the development kit but I didn't quite understand how to work it.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Something tells me you are not following directions properly. And here is why i say that. Before you can use the Android SDK you also need Eclipse Plug In and JavaJDK. If you just downloaded the SDK it will not work properly.
There are thousands of people of have stated and claim that the methods posted work perfectly for them to root, turn s=off, Flash Engineering screens and flash custom ROMS, and there a few who do have problems.
the sides look a little unfair that the methods of rooting are flawed.
trofeo.08 said:
Thanks I have tried to do it through visionary. Now I do the command script method as well....
Click to expand...
Click to collapse
neidlinger said:
Something tells me you are not following directions properly....
Click to expand...
Click to collapse
It's not "as well" -- it's a required step. To repeat those here for you, from The Unlockr:
Temporary Root via VISIONary
Download root.sh toolkit
Install root.sh kit (kernel module, script, etc.) on SD card
Execute root.sh
Permanent root via VISIONary
Based on your comments, it appears you are only now going to Step 2. But you have not yet confirmed you have accomplished Step 1.
Well I just got out im gonna try doing the sdk . I have tried step 2
Sent from my HTC Glacier using XDA App
trofeo.08 said:
Well I just got out im gonna try doing the sdk . I have tried step 2
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
the method that jggimi posted are not options.
That is one of the ways to Root your phone.
you HAVE to download and install VISIONary.apk.
you HAVE to download extract and move the root folder to the SDcard
you HAVE run VISIONary.apk with the proper boxes checked
you HAVE to open the term emulator and execute the script
.
It's not multiple choice, those are steps on what to do
edit :
I'm not trying to sound like Capitan Douchebag here but if you are having this much trouble with such an easy method you need to rethink rooting your phone. Or allowing someone that knows what they are doing do it for you.
you are giving yourself access to the very kernel of the OS, and you can screw something up to the point that you own a 500 dollar paper weight.
I've done all steps properly. I've downloaded v11 and I have 14 on my SD card . Wich version works better. And should I at any point remove the battery
Sent from my HTC Glacier using XDA App
trofeo.08 said:
I've done all steps properly. I've downloaded v11 and I have 14 on my SD card . Wich version works better. And should I at any point remove the battery
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
should should never remove the battery. until s=off. Once you remove the battery [or turn the phone off] you will lose temproot. and most people on here use r14 of VISIONary.apk.
before you attempt to execute the root.sh file you need to make sure the "run VISIONary.sh" and set system to r/w are checked so the files can do what they need to do.
I'll ask again - how did you prove you passed step 1 successfully?
HTC Glacier running CM7 #18
step 1?. downloading visionary? or temprooting?... im currently downloading sdk on my comp , its just uploading the platforms.
deleted
i kan has 10 char
trofeo.08 said:
step 1?. downloading visionary? or temprooting?... im currently downloading sdk on my comp , its just uploading the platforms.
Click to expand...
Click to collapse
how can you tell that you do not have root access to your phone.
What steps lead you to believe you are not rooted.
trofeo.08 said:
Well I just got out im gonna try doing the sdk . I have tried step 2
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
You don't need the sdk to run adb. Go find my thread in the dev section or click on it in my signature. It is alot easier than you trying to figure out how to set up the sdk.
trofeo.08 said:
step 1?. downloading visionary? or temprooting?...
Click to expand...
Click to collapse
Established and confirmed temporary root. I thought I was clear.
HTC Glacier running CM7 #18
Related
I do everything correctly when starting perm root...then i get to terminal emulator and after I do "sh root.sh" I get tgis message:
/sdcard/root/wpx.ko failed (function not implemented)
Any ideas as to whats going on here? Ive never had it do this when rooting .
*edit* went into the store and got a new one, still doing the same error. So, any ideas what's up?
Sent from my HTC Glacier using XDA App
bballcat03 said:
I do everything correctly when starting perm root...then i get to terminal emulator and after I do "sh root.sh" I get tgis message:
/sdcard/root/wpx.ko failed (function not implemented)
Any ideas as to whats going on here? Ive never had it do this when rooting
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
From some on going research by the fine science team here at the XDA research facility it appears as if you may have a bad eMMC.
There are are two different rooting methods ./gfree and root.sh. It's becoming clear that if you have problems with the root.sh method, Which is a scripted out version of what you are trying to do, and if it doesn't work it's most likely your phone has faulty hardware that will not allow it to work properly. IF i were in your shoes i'd get ADB up and running (if you dont already) then look @ the "post your eMMC thread" to see if you have a bad one or not. If you have a good one use the ./gfree method. If you have a bad one i'd reconsider rooting your phone as the chances of bricking goes up alot.
I am only on my first day of having this phone, so if I have a bad one, I could just take it back to tmobile and get a new one for free.
If its good, can I do the gfree on my mac? Cause I dont have windows.
Sent from my HTC Glacier using XDA App
How do I do ADB for MAC?
The thread on here is for windows....
So I went to the T-Mobile store today and got a new one...so this is 2 MT4G's in 24 hours...brought it home...SAME THING
what are the odds off two bad emmc's??? Something's fishy here, wouldn't one think?
can you post the link of the guide your following .Also have u set up adb on mac
I am using "the unlockr's" method to temp root, and then followed by the perm root method...it's in the perm root method that this is happening obviously.
No, trying to get that figured out on how to do it on my mac right now
jeff7790 said:
can you post the link of the guide your following .Also have u set up adb on mac
Click to expand...
Click to collapse
http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/
Have you tried visionary method for your phone. I know it doesn't work for everyone, but it worked perfectly for me. Saved me quite a few steps, too.
Did u CD/ sdcard first
Sent from my HTC Glacier using XDA App
Make sure that you have both
Code:
Run VISIONary.sh
and
Code:
Set /System to r/w
both check marked.
If those are checked it will not work
also make sure you have ADB debugging turned on
Options > application management > development > should be the top option.
rockstarar said:
Did u CD/ sdcard first
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
No...what is that?
Sent from my HTC Glacier using XDA App
neidlinger said:
Make sure that you have both
Code:
Run VISIONary.sh
and
Code:
Set /System to r/w
both check marked.
If those are checked it will not work
also make sure you have ADB debugging turned on
Options > application management > development > should be the top option.
Click to expand...
Click to collapse
I run visionary first in the temp root method and that works just fine. Installed screenshot it to verify I had root access
Sent from my HTC Glacier using XDA App
bballcat03 said:
I run visionary first in the temp root method and that works just fine. Installed screenshot it to verify I had root access
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I understand your theory behind wanting to make sure you have root access. But unless you change the /system files to a read/write point it will not allow you to make changes to it. Which is required for the command to work. If it's not working there is a GOOD chance you may have a bad eMMC and i wouldn't advise rooting it.
neidlinger said:
I understand your theory behind wanting to make sure you have root access. But unless you change the /system files to a read/write point it will not allow you to make changes to it. Which is required for the command to work. If it's not working there is a GOOD chance you may have a bad eMMC and i wouldn't advise rooting it.
Click to expand...
Click to collapse
Would I really have a bad emmc on a 24 hour old phone? I thought they went bad when the phone got old?
Sent from my HTC Glacier using XDA App
bballcat03 said:
Would I really have a bad emmc on a 24 hour old phone? I thought they went bad when the phone got old?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Try this guide. I have the bad eemc too and it worked fine.
http://www.youtube.com/watch?v=XDFMR4UUdt0
That is the unlockr way... had the same issue
Sent from my HTC Glacier using XDA App
Got my MT4G wednesday...couldn't root with visionary
Got it replaced yesterday...couldn't root with visionary
Got it replayed today...can't root with visionary.
3 phones, in 3 days...all cannot root with visionary
Something weird is going on here. The odds of this happening have to be astronomical, or is this phone going to sh*t now?
I also had problems Rooting a friends new MT4G a couple days ago with the VISIONary Method and Thats all I had ever used. I think it's somthing with the new phones? Did you try the G-FREE Method?
No cause Gfree is windows and I have OSX, so I'm SOL on that...which is why I'll probably switch to the G2X if I can't get to another computer with windows.
use cm method
bosina said:
use cm method
Click to expand...
Click to collapse
which is what? Never even heard of that...
You keep replacing your device because you can't root it? Seriously? Why? You think the devices are damaged in some way because you can't root them?
coupetastic-droid said:
You keep replacing your device because you can't root it? Seriously? Why? You think the devices are damaged in some way because you can't root them?
Click to expand...
Click to collapse
So it's my computer's fault?
There is a thread going on about bad eMMC's that won't allow you to root...so yes, it is the device...
way to be a d*ck dude!
I think you're likely incorrect about the reason you can't root it. My myTouch4G has the good eMMC, yet I was unable to root it using Visionary. Gfree worked without a hitch though. Also, why do you think gfree is exclusive to any OS? I think it should work on any OS, as gfree is executed on the phone, not via your PC. You run gfree through terminal emulator or through adb shell.
I've gone through half a dozen mytouch 4gs because they all keep turning off on me. I get the feeling that t-mobile just sends out refurb after refurb so you keep getting phones with the bad chip. At least I wouldn't be surprised considering my experience with this phone.
I also have the M4G2DE chip and I could not root with visionary. I don't know if my sleep of death problems are related to this but like I said before I wouldn't be surprised.
crawler9 said:
I think you're likely incorrect about the reason you can't root it. My myTouch4G has the good eMMC, yet I was unable to root it using Visionary. Gfree worked without a hitch though. Also, why do you think gfree is exclusive to any OS? I think it should work on any OS, as gfree is executed on the phone, not via your PC. You run gfree through terminal emulator or through adb shell.
Click to expand...
Click to collapse
excuse me, according to the thread in the general section, the MT4G can come with bad eMMC's. I have no proof of this of course, just going off what I read. I tend to give people the benefit of the doubt, when I see other's with the same issues at least.
The instructions on the gfree method are for windows...do the same exact commands apply to OSX if I use terminal? I'm not a mac guy, by any means, but I figured commands and all would be different between OS's.
Yes, it's highly suspected that certain eMMcs are more prone to failing, though this hasn't definitively been determined yet.
The instructions in the gfree thread should be universal. I used them successfully on Ubuntu. For some reason, I couldn't get Visionary to properly function on my device either. Apparently it did work after a factory reset, after I restored it to stock again, but first time around, I used z4root to temp root and manually installed the superuser application from the market instead of the step that tells you to use Visionary in the gfree instructions.
crawler9 said:
Yes, it's highly suspected that certain eMMcs are more prone to failing, though this hasn't definitively been determined yet.
The instructions in the gfree thread should be universal. I used them successfully on Ubuntu. For some reason, I couldn't get Visionary to properly function on my device either. Apparently it did work after a factory reset, after I restored it to stock again, but first time around, I used z4root to temp root and manually installed the superuser application from the market instead of the step that tells you to use Visionary in the gfree instructions.
Click to expand...
Click to collapse
but what's the "C" drive called on OSX (as per the instructions)...right now my android-sdk-mac_x64 folder is in the macintosh hd
bballcat03 said:
but what's the "C" drive called on OSX (as per the instructions)...right now my android-sdk-mac_x64 folder is in the macintosh hd
Click to expand...
Click to collapse
I don't see any mention at all of the C drive in the gfree thread. Are you following the same thread I am? http://forum.xda-developers.com/showthread.php?t=858996
crawler9 said:
I don't see any mention at all of the C drive in the gfree thread. Are you following the same thread I am? http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
yup same thread, but in order to get to the "tools" portion, you had to do C right? It says I'm supposed to "cd your way to your SDK tools directory"...how do you do that on OSX?
cause when I do step 4 ""adb push gfree /data/local""....I type that into terminal and it says "command not found"
bballcat03 said:
yup same thread, but in order to get to the "tools" portion, you had to do C right? It says I'm supposed to "cd your way to your SDK tools directory"...how do you do that on OSX?
cause when I do step 4 ""adb push gfree /data/local""....I type that into terminal and it says "command not found"
Click to expand...
Click to collapse
Never used MAC OS, but it seems like the cd command would work the same way. Just open terminal or a prompt or whatever you use in MAC and type "ls" and hit enter. That should show you all the files or directories in that folder. Use that to find your way around to where your SDK is located. To go up a folder, you can type "cd .." or to enter another folder located in your current working directory, "cd insertfoldernamehere". Maybe someone with a little more experience with MACs can help you with exactly where your SDK is, but that should help if you can play around with it for a while.
@crawler9 u must have great patients for ignorance... if he can't figure out how to use his comp, goodluck on getting him to understand android... not trying to sound like a **** OP but educate urself a bit more on things u r unsure of..
Sent from my demonSPEED Glacier
thederekjay said:
@crawler9 u must have great patients for ignorance... if he can't figure out how to use his comp, goodluck on getting him to understand android... not trying to sound like a **** OP but educate urself a bit more on things u r unsure of..
Sent from my demonSPEED Glacier
Click to expand...
Click to collapse
thanks @$$.
I had a MT4G before, but I was on windows...I could do everything perfectly fine, never had an issue. Flashed and rooted flawlessly
But I switched to mac, and don't know my way around this full yet. So I'm trying to admittedly re-learn everything as I went a few months without my MT4G before getting it replaced.
Thanks for your input! Next time just keep your mouth shut if you don't have anything constructive to add, hmmm?
bballcat03 said:
which is what? Never even heard of that...
Click to expand...
Click to collapse
http://wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide
that is cm method...
\the best you can find and the most easy
Thanks everyone for the help! Got it rooted and up and running...finally. Trial and error might not be fun, but it get's the job done and you learn!
I rooted mine using the gfree method and didn't even have to touch a computer... All through terminal...
Sent from my doped up HTC Glacier.
Hi all! This is a tool I made that will bypass your need to downgrade from 2.11.605.9 or .19 to get S-OFF. It uses the fre3vo exploit by TeamWin/Agrabren and the Revolutionary tool. I take no credit for this method.
Thank Agrabren here.
Thank the revolutionary team at Revolutionary.io
*I am NOT responsible for any bricked devices*
*Rooting voids your warranty! If you do not know that by now, you probably need to research more before you root*
This means that you will not have to deal with large files, and you will not lose any data.
Happy rooting!
*If you have any PG05IMG.zip files on your sdcard, remove them first!*
-----------------------------------------------------------------------------
File: Goo-inside.me Downloads - Downloading DowngradeBypass.zip
MD5 is on download page.
Mirror: http://dl.dropbox.com/u/61129367/DowngradeBypass.zip
MD5: BCD3A6982E819400E87CED8CFA6D3FB7
-----------------------------------------------------------------------------
All you do is download this, unzip it (very important!), and run the RUN-ME.bat. Just make sure to read and follow all directions in the program carefully.
Please copy and paste the beta code for Revolutionary when that step comes along (I tell you how in the tool), because if it gets put in wrong you will need to manually start Revolutionary from the support_files folder.
========= FULL TEXT TUTORIAL! =========
1. Download the file. Check the MD5sum of it. (If you do not know how, download this, open it, paste in the MD5sum that is above, click browse and select the zip file. If it is green, continue. If it is red, redownload the file and start over.)
2. Uninstall Droid Explorer if you have it. If you have any PG05IMG.zip files on your sdcard, remove them. Plug in your phone, set it to charge only (Through the notification menu on your phone), Go to Settings > Applications > Development and make sure to select "Stay Awake" and "USB Debugging" and hit OK on the popup if there is one. Keep the screen on during the process.
3. Right click on the .zip file, and then click extract.
This window will pop up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure "Show extracted files when complete" is checked, and hit extract.
4. Now a folder will pop up. In that folder, double click RUN-ME.bat.
5. A window will pop up. It should say something like "*Daemon not running. starting it now* *Daemon started successfully*"
If it says something like "*Failed to start daemon* adb server didn't ACK", you need to uninstall HTC Sync or other syncing software (EasyTether, PDAnet, etc.) then restart the tool.
5. You will now be at a menu. If this is your first time rooting, you probably do not have the fastboot drivers installed, so enter N and press enter. (If you do have them installed, enter Y and skip to step 8.)
6. Wait for the driver window to close. It will take awhile. (The big window, not the small one)
7. Click back on the tool window and press enter.
8. It should now find your device. If not, try rebooting your phone and computer and retrying.
9. Then it should say:
-Getting root with fre3vo, thanks TeamWin!
-This will take a minute.
There will be some static-y lines going across your phone's screen. This is normal.
10. After a few minutes, it should finish and say:
-Success!
-Restarting adb...
*daemon not running. starting it now*
*daemon started successfully*
-Putting superuser files on your sdcard...
[some random numbers here]
-Starting Revolutionary and the Website....
And then the window will close.
If not, and it says root unsecessful, then try pulling your phone battery and running again.
11. 11. At this point, a textbox pops up. Once you close it there will be another one. Keep the first one open until you get your beta key (After step 13).
12. The website revolutionary.io and one or two other black boxes will also pop up. If only the website pops up, and no revolutionary window, open the support_files folder and double click revolutionary.exe. If there are two revolutionary windows, you can close one.
13.On the revolutionary website, please scroll down to Download for Windows. Click that button, then cancel the download. Enter your phone's information in the prompts that pop up. The info you need is in the text boxes.
14. Click "Generate Key".
15. Once you do that, copy your beta key from the website, then paste it into the Revolutionary window. To paste it, right click the title bar of the Revolutionary window then click edit then click paste.
16. Press enter on the Revolutionary window.
17.It should say something like:
Code:
Root acquired!
Sending in Caroline...
Cleaning up...
Rebooting to fastboot...
When life gives you lemons, don't make lemonade. Make life take the lemons back!
Waiting for fastboot...
Rebooting to fastboot (Once moar...)
SUCCESS - Life gave us lemons, we didn't make lemonade!
Do you want to download (Internet connection required) and flash ClockworkMod Reocvery? [Y/n]
18. Press Y and press enter.
19. Now it should say:
Code:
Downloading recovery for your phone (mecha)... Done.
Flashing recovery over fastboot...SUCCESS!
Then the window will close.
20. Now, using volume buttons to navigate and power to select, select bootloader.
21. Wait a few seconds, and then select recovery.
22. Your phone will now go to CWM recovery and automatically flash superuser.
23. Reboot your phone and you're rooted.
24. Enjoy!
I think its awesome that someone did this but this method seems way more complicated than doing it the other way. Maybe its just because you spelled out every step though hehe.
Sent from my ADR6400L using Tapatalk
disconnecktie said:
I think its awesome that someone did this but this method seems way more complicated than doing it the other way. Maybe its just because you spelled out every step though hehe.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Yeah that's why ;P
These are pretty much the only instructions needed
All you do is download this, unzip it (very important!), and run the RUN-ME.bat. Just make sure to read and follow all directions in the program carefully.
Please copy and paste the beta code for Revolutionary when that step comes along (I tell you how in the tool), because if it gets put in wrong you will need to manually start Revolutionary from the support_files folder.
Click to expand...
Click to collapse
It's not really hard at all, I just wanted to give people something to go by
Yea I figured that. It makes the actual task of rooting seem a lot longer when you put it all to words like you did.
Sent from my ADR6400L using Tapatalk
disconnecktie said:
Yea I figured that. It makes the actual task of rooting seem a lot longer when you put it all to words like you did.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
my original posts in other forums didn't have it, but I got a lot of questions so i decided to add it
I have two replacement Thunderbolts arriving today, and I plan to give this tool a whirl. I'll report back when I'm finished.
I was thinking of writing a tool like this, but I'm *so* glad I don't have to now!
I'm the type of coder who will spend hours trying to automate a process that would take only a few minutes if done manually
This def works.
Sent from my ADR6400L using XDA
Maybe someone here can help me out in this thread? It's about the Unroot tool... http://forum.xda-developers.com/showthread.php?t=1639830&page=2
Is it doing that when you do adb devices?
Sent from my ADR6400L using Tapatalk
disconnecktie said:
Is it doing that when you do adb devices?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
I figured out the problem. Thanks though. I'll be rooting my new 'bolt as soon as the one I'm sending back is unrooted so there may be more questions headed your way. Thanks in advance.
Does it work for software version #2.11.605.9?
---------- Post added at 06:24 PM ---------- Previous post was at 05:53 PM ----------
This worked, thanks very much!!!!
Used this method to root my first thunderbolt. Had to get a replacement. The replacement had the .19 build on it. This method does not work on the new build. Its says failed to find root. Help please?
Sent from my ADR6400L using XDA
dblkspecial said:
Used this method to root my first thunderbolt. Had to get a replacement. The replacement had the .19 build on it. This method does not work on the new build. Its says failed to find root. Help please?
Sent from my ADR6400L using XDA
Click to expand...
Click to collapse
Nevermind. I figured it out. All I did was take the stock rom from the unroot tool flashed via bootloader then ran the downgrade bypass tool n am now rooted again
Sent from my HTC Mecha using XDA
dblkspecial said:
Used this method to root my first thunderbolt. Had to get a replacement. The replacement had the .19 build on it. This method does not work on the new build. Its says failed to find root. Help please?
Sent from my ADR6400L using XDA
Click to expand...
Click to collapse
It worked for me
Sent from my ADR6400L using Tapatalk 2
Double tested yesterday, this does work with 2.11.605.19
Sent from my ADR6400L using Tapatalk 2
worked perfectly, had to unroot cause i thought i was gonna send it in for warranty exchange, but i ended up fixing the issue in nonrooted state, now i used this to go back to root on .19 and flawless. thanks a bunch for ur work!
HTCDEV
If I have my phone unlocked using the HTCdev method do I have yo relock?
zbergmark said:
If I have my phone unlocked using the HTCdev method do I have yo relock?
Click to expand...
Click to collapse
yes you should
MOD EDIT
Seems this guide, if not properly followed will cause a (soft)brick. Also there are more up to date guides.
[how to]change your MID without the eng bootloader
[TOOL] MID change without ENG HBOOT | Aroma GUI
In the interests of all users the guide is hidden, below.
If you wish to follow it go ahead. If you brick your handset, you were warned.
FIRST OF ALL THANKS AND CREDITS GOES TO THE FOLLOWING XDA MEMBERS
@fnoji111 for working on the ENG HBOOT in the Droid DNA forum
@Argumentation for creating the flashable zip that I used for this tuttorial
@daddioj for doing the leap of faith and used the ENG HBOOT on his device which lead me to writing this tutorial
NOTE: I created this tutorial because HTC One has different variants. After reading mike1986. article on HTC One variants I realized why I can't install OTA updates with my model ID (MID). Now since we have S-OFF I wanted to get updates from the UK. But since I have a different MID to the UK version, I can't install OTA updates. And this is the only solution I found to work at this time. So I hope it will help people who wants to change their MID
VIDEO LINK AT THE BOTTOM OF THIS POST
REQUIREMENTS:
1: S-OFF
2: KNOWLEDGE OF ADB COMMANDS
3: PATIENCE
PLEASE MAKE SURE YOU PAY ATTENTION TO EVERY STEP ON THIS TUTORIAL
***** I WILL NOT BE HELD RESPONSIBLE IF YOU BRICK YOUR PHONE*****
STEP 1:
Make sure you don't have HTC Sync Manager installed, if you do uninstall it!! Also make sure you have HTC drivers installed!
Step 2:
Go here http://forum.xda-developers.com/showpost.php?p=38180376&postcount=6 and download the Argumentation's zip file
Step 3:
After downloading the PL83IMG.zip you will need to edit the android-info-txt inside. Please see sample picture below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 4:
Now you have to place the zip file in C:\Android SDK\sdk\platform-tools folder. I know some people don't have the same directory as I have so this is just an example. Just make sure you place in the platform-tools folder.
Step 5:
Now connect your HTC One (MAKE SURE YOUR DEVICE HAS PLENTY OF CHARGE) to your PC and start a command prompt in the "platform-tools" folder. The quickest way to do this is (see picture below):
Step 6:
When you start your command prompt follow the steps in the picture below. PLEASE BE PATIENT!! After flashing the ENG HBOOT your HTC One will not boot up but you'll just get a gray spotted screen. Your device is not bricked. You can still use adb commands to write the model ID and CID even with a gray screen. WHEN REBOOTING HOLD DOWN POWER BUTTON FOR A FEW SECONDS. You might have to press and hold power button and volume down button when rebooting your phone.
NOTE: When you run the RUU and it says "waiting for bootloader" you will need to restart your phone manually by holding down the power button for a few seconds until it reboots. EACH TIME (does it twice) the RUU says "WAITING FOR BOOTLOADER" you will need to restart the phone manually
You will not lose S-OFF and still have unlocked bootloader. I suggest that backup all important stuff before doing this I hope it helps.
If the mods feels that this doesn't belong here, please feel free to remove it. Thanks.
Here's a short video that shows how I changed my MID (model ID) on my HTC One
Just a side note: better to edit all kind of text with notepad++.
1) It formats text better (not just one single line)
2) It keeps Unix coding if needed
EDIT 05.12.2013 by the request of user @alray
THIS METHOD WILL NOT WORK USING WINDOWS 8.1
After flashing ENG hboot, Windows 8.1 won't detect the device and fastboot won't work, so you can't change MID and execute the RUU. (win 8.1 drivers issue).
I'll give this a go shortly
The warning on step six makes no sense
Does it automatically reboot after flashing the zip or what
Sent from my HTC One using xda app-developers app
tyler1234567 said:
The warning on step six makes no sense
Does it automatically reboot after flashing the zip or what
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Which warning? Like it states in the last picture when you flash the ENG HBOOT it will get stuck at 3/4 of a way in the status bar. You will need to restart the phone yourself. Then you will get a gray screen and won't be able to see anything. You might think it's bricked but it's not. You just have to proceed with adb command to write the MID and then another adb command to write the CID.
Once you have changed the MID and CID. You may have to reboot your phone and then run the RUU even when it's only a gray screen you see. The RUU will flash back the proper HBOOT and you will see the RUU screen (black screen with HTC logo). Just be patient and wait until the RUU is finished its operation. And that is it.
I will make a video when I get home to assure people that this mod works.
Don't know why you started two threads like this? But you have one in General and this one in Development.
But it doesn't belong in Development.
shadowboy23 said:
Which warning? Like it states in the last picture when you flash the ENG HBOOT it will get stuck at 3/4 of a way in the status bar. You will need to restart the phone yourself. Then you will get a gray screen and won't be able to see anything. You might think it's bricked but it's not. You just have to proceed with adb command to write the MID and then another adb command to write the CID.
Once you have changed the MID and CID. You may have to reboot your phone and then run the RUU even when it's only a gray screen you see. The RUU will flash back the proper HBOOT and you will see the RUU screen (black screen with HTC logo). Just be patient and wait until the RUU is finished its operation. And that is it.
I will make a video when I get home to assure people that this mod works.
Click to expand...
Click to collapse
Oh ok I got ya. Didn't see that before.
Xstop said:
Don't know why you started two threads like this? But you have one in General and this one in Development.
But it doesn't belong in Development.
Click to expand...
Click to collapse
If it doesn't belong here then the mods can delete that is fine by me.
EDIT:
Just sent a message to one mod so he can delete this thread if it doesn't belong here.
thank you very much it worked like a charm just changed a tmous mid so far so good waiting to install ota
Xstop said:
Don't know why you started two threads like this? But you have one in General and this one in Development.
But it doesn't belong in Development.
Click to expand...
Click to collapse
False. How is this not developement. And if this isn't developement then neither is the cid thread, or all the stock rom threads.
shadowboy23 said:
If it doesn't belong here then the mods can delete that is fine by me.
Click to expand...
Click to collapse
No harm, just easier to follow one thread since I am interested in this.
I converted my ATT One to the Dev Edition (hoping that nothing ATT is on m phone now except service), easy since both have the same MID but will be doing this for the PN0710000 soon.
Thank you for the tutorial. :good:
so to make sure i just put the same info from the YOUR text file picture in the one i downloaded ?
CheesyNutz said:
so to make sure i just put the same info from the YOUR text file picture in the one i downloaded ?
Click to expand...
Click to collapse
Which one? Do you mean the "android-info-txt"? If that's what you meant then you have to put in your current model ID, CID and ROM version..If it's the same as mine then you just copy what is written in the first picture. Just remember that Argumentation's zip file is intended for Droi DNA but all you have to edit id the "android-info-txt" and you don't have to touch the HBOOT.nb0.
A video lesson would be perfect
Tried to do something, but adb is not for me, I guess...
It would be perfect to change from carrier to free uk version..
darenas said:
A video lesson would be perfect
Click to expand...
Click to collapse
Uploading now, will post it in the OP when finished. The video is not a tutorial of some sort but more of a guide. It just shows you the process of actually flashing the ENG HBOOT and what I typed using adb/fastboot commands.
shadowboy23 said:
Uploading now, will post it in the OP when finished. The video is not a tutorial of some sort but more of a guide. It just shows you the process of actually flashing the ENG HBOOT and what I typed using adb/fastboot commands.
Click to expand...
Click to collapse
It's perfect will it include only the procedure of changing mid/cid, or maybe it will also include the beginning of downloading and setting up s-off? it would be great, because i didn't find how to get and use adb correctly...
---------- Post added at 10:20 PM ---------- Previous post was at 10:18 PM ----------
darenas said:
It's perfect will it include only the procedure of changing mid/cid, or maybe it will also include the beginning of downloading and setting up s-off? it would be great, because i didn't find how to get and use adb correctly...
Click to expand...
Click to collapse
I see already.
darenas said:
It's perfect will it include only the procedure of changing mid/cid, or maybe it will also include the beginning of downloading and setting up s-off? it would be great, because i didn't find how to get and use adb correctly..
Click to expand...
Click to collapse
Well my phone has S-OFF and have a unlocked bootloader. S-OFF is a MUST! You will see in the video very clearly what I type in adb/fastboot so I'm pretty sure people can work it out.
Video link is up! It is at the bottom of the OP. I hope it helps people.
Done with OTA :thumbup:
Sent from my HTC One using Tapatalk 2
Update: Successfully working atm, survives a hard reboot.
Status: In testing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Congrats!! Hard work surely pays off.
Thanks bud. I'm gonna run it for a bit and make sure there isn't any issue that are gonna come about but I doubt it. I could release a IMG out also for people to flash, but I removed a ton of apps I don't ever use, but unsure about the user who will download it.
Sent from my XT1254 using XDA Free mobile app
savagebunny said:
Thanks bud. I'm gonna run it for a bit and make sure there isn't any issue that are gonna come about but I doubt it. I could release a IMG out also for people to flash, but I removed a ton of apps I don't ever use, but unsure about the user who will download it.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah run it all this weekend and hopefully all is well. Dont hesitate About making the IMG but just specify which apps you have removed and what not beforehand on the op when you make the post. Remember there are all types of users out there so don't question who would be interested dont question that who would be interested.
wadamean said:
Yeah run it all this weekend and hopefully all is well. Dont hesitate About making the IMG but just specify which apps you have removed and what not beforehand on the op when you make the post. Remember there are all types of users out there so don't question who would be interested dont question that who would be interested.
Click to expand...
Click to collapse
Well.. Right when I thought I got it, already ran into a issue. What I did BEFORE was I made sure was the V4A .apk in priv-app had 0755 permissions. I installed the driver and worked, but then i did a SOFT reboot. Driver was successful and no issue. I just now did a hard reboot, and the driver gets uninstalled, and the permissions get set to 0666. Whats weird though is in the img in linux, I made sure priv-app folder is 0755 and I just checked and V4A apk is 0755 in the image. Some how along the line it gets changed to 0666 by the system.
tl;dr only way for it to work is set apk to 0755 via root browser, install driver, Do a soft reboot and it works. Doesn't survive hard reboot. unsure why
savagebunny said:
Well.. Right when I thought I got it, already ran into a issue. What I did BEFORE was I made sure was the V4A .apk in priv-app had 0755 permissions. I installed the driver and worked, but then i did a SOFT reboot. Driver was successful and no issue. I just now did a hard reboot, and the driver gets uninstalled, and the permissions get set to 0666. Whats weird though is in the img in linux, I made sure priv-app folder is 0755 and I just checked and V4A apk is 0755 in the image. Some how along the line it gets changed to 0666 by the system.
tl;dr only way for it to work is set apk to 0755 via root browser, install driver, Do a soft reboot and it works. Doesn't survive hard reboot. unsure why
Click to expand...
Click to collapse
Figure out where the apk installs the driver and manually insert the driver in that location with the proper permissions in the IMG then flash. Should work then I'd think
Edit: looks like you may have to add some lines to the build.prop as well
viper
brennam7 said:
Figure out where the apk installs the driver and manually insert the driver in that location with the proper permissions in the IMG then flash. Should work then I'd think
Click to expand...
Click to collapse
hello. am a lover viper. I had on other cell. there is a way to install without root on droid turbo? thank you. greetings: P
brennam7 said:
Figure out where the apk installs the driver and manually insert the driver in that location with the proper permissions in the IMG then flash. Should work then I'd think
Edit: looks like you may have to add some lines to the build.prop as well
Click to expand...
Click to collapse
Ya I'm thinking that too. It's a new day so I'm gonna start digging into it today and see what's up. The only down fall is that I gotta keep sending over that 3.5GB img each time which takes a lot of time into work.
Already added the lines to build.prop also. There may be a few extra ones that could be lingering
pialletti said:
hello. am a lover viper. I had on other cell. there is a way to install without root on droid turbo? thank you. greetings: P
Click to expand...
Click to collapse
Nope, gotta have root due to dependencies needed by the V4A and various other files that need to be written in /system/
Sign me up!
Sent from my XT1254 using XDA Free mobile app
Hello guys, I may have figured out the issue. In V4A options, we can choose High Quality (HQ) and Super High Quality (SQ). From what I've read SQ doesn't use too much battery more than HQ, and we are using quite a powerful CPU. Should I make a image with HQ or SQ driver installed?
savagebunny said:
Hello guys, I may have figured out the issue. In V4A options, we can choose High Quality (HQ) and Super High Quality (SQ). From what I've read SQ doesn't use too much battery more than HQ, and we are using quite a powerful CPU. Should I make a image with HQ or SQ driver installed?
Click to expand...
Click to collapse
SQ! Did you get it figured out so that it survives a reboot?
PerCompLLC said:
SQ! Did you get it figured out so that it survives a reboot?
Click to expand...
Click to collapse
I'm gonna find out once the image flashes over. I'm crossing my fingers I figured it out... only can hope. I'll update this post if it survives a hard reboot
EDIT: Nope, didn't stick. Now during a soft-reboot it doesn't even work now.. Man this is a struggle
Quick updated, with some mind boosting affect from computerfreek274, I was digging into V4A why it wouldn't stay after hard reboot. I've done 3 hard reboots so far and the driver is sticking without the driver install loop. Can't believe it's taken me this long, but its finally done
Have computerfreek274 add it to the IMG he's been uploading! Could be a fantastic addition! Congrats on getting it to work. No better feeling in the world
JakeDHS07 said:
Have computerfreek274 add it to the IMG he's been uploading! Could be a fantastic addition! Congrats on getting it to work. No better feeling in the world
Click to expand...
Click to collapse
Ya me and him have been talking about it. He is in testing phase atm also
Sent from my XT1254 using XDA Free mobile app
savagebunny said:
Ya me and him have been talking about it. He is in testing phase atm also
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Awesome thanks for your work
@savagebunny It sucks how long it takes to flash each time you need to test something. I hope one day we get an unlocked boot loader and some custom recovery so we can just flash shot as we need it.
Thanks @savagebunny for keeping me going this. I am testing now the changes we just talked about we will see if it works. I also did the same things but when I do a full clean wipe and flash it asked for the driver. I am doing a clean and wipe and fresh install if all works good I will post 1.5.2a with ad blocking and V4A.
Thanks buddy now we will need to work on something new after this. lol.
PS 46% like wet paint.
Ya I feel ya. Made some good progress, although it took us longer than usual, seems like there is only a handful of us working on things. Like you said, gotta think of something else good to bake into the images until we get unlocked boot-loader and we can flash all day