Related
I know to most of you this post is kind of dumb, because you already know the drill..
But Im following a thread on android central specifically talking about the update.zip and yet there is still people bragging about installing the update...and they dont pull it from their phone first-__-
So anyway, please read these instructions before you do anything if you recieve the OTA notification, so the rest of us can have our scoop of FroYo
http://www.droid-life.com/2010/03/30/if-you-receive-the-2-1-update-do-this-first/
Its as simple as that...once your you do it, please post the update.zip either on here or on android central, or android forums and provide us with a link
schwartzman93 said:
I know to most of you this post is kind of dumb, because you already know the drill..
But Im following a thread on android central specifically talking about the update.zip and yet there is still people bragging about installing the update...and they dont pull it from their phone first-__-
So anyway, please read these instructions before you do anything if you recieve the OTA notification, so the rest of us can have our scoop of FroYo
http://www.droid-life.com/2010/03/30/if-you-receive-the-2-1-update-do-this-first/
Its as simple as that...once your you do it, please post the update.zip either on here or on android central, or android forums and provide us with a link
Click to expand...
Click to collapse
or u could use the RUU already available here. or extract the ROM from the RUU if you just really dont want to wipe your phone.
k.electron said:
or u could use the RUU already available here.
Click to expand...
Click to collapse
exactly....
k.electron said:
or u could use the RUU already available here. or extract the ROM from the RUU if you just really dont want to wipe your phone.
Click to expand...
Click to collapse
Dont i have to root to install the ROM?...i dont want to do that
You do not have to root.. the ROM is digitally signed by HTC, so your phone will accept it and install it as though it were the OTA.
1)Make sure your SD card is formatted in FAT32. The HBOOT can't read SD cards that aren't.
2)Take the ROM.zip from the RUU and place it in the root directory of your SD card (the main directory, not inside a folder)
3) Rename it PB31IMG.zip
4) Shut your phone off.
5) Hold down your volume down button and press the power button to boot up in HBOOT.
6) Leave the phone alone. It will go through three scans of the zip file, and say the first two times that an image isn't found, then load the data.. then it will ask you "Do you want to update now?" after it has read the zip. Press the volume up to say yes.
7) Just follow the on screen instructions from there. Takes maybe 10 minutes total. You'll be good to go after the phone reboots and says "Droooid!"
Just make sure to back up your apps first and your contacts. I did this on two of my family's four Incredibles last night. Wiped the apps on both, and the contacts. Same as running the RUU I guess. Just amke sure your battery is at least at 50% charge.
And for the usual legal reasons I must vehemently stress the disclaimer that everyone who makes roots here says: I'm not responsible if you damage your phone. Rawr! (kind of impossible since you're using an official HTC signed ROM that wouldn't even RUN for you otherwise, unless you were rooted).
NinjaRicky said:
You do not have to root.. the ROM is digitally signed by HTC, so your phone will accept it and install it as though it were the OTA.
1)Make sure your SD card is formatted in FAT32. The HBOOT can't read SD cards that aren't.
2)Take the ROM.zip from the RUU and place it in the root directory of your SD card (the main directory, not inside a folder)
3) Rename it PB31IMG.zip
4) Shut your phone off.
5) Hold down your volume down button and press the power button to boot up in HBOOT.
6) Leave the phone alone. It will go through three scans of the zip file, and say the first two times that an image isn't found, then load the data.. then it will ask you "Do you want to update now?" after it has read the zip. Press the volume up to say yes.
7) Just follow the on screen instructions from there. Takes maybe 10 minutes total. You'll be good to go after the phone reboots and says "Droooid!"
Just make sure to back up your apps first and your contacts. I did this on two of my family's four Incredibles last night. Wiped the apps on both, and the contacts. Same as running the RUU I guess. Just amke sure your battery is at least at 50% charge.
And for the usual legal reasons I must vehemently stress the disclaimer that everyone who makes roots here says: I'm not responsible if you damage your phone. Rawr! (kind of impossible since you're using an official HTC signed ROM that wouldn't even RUN for you otherwise, unless you were rooted).
Click to expand...
Click to collapse
lol, thats why i want the update.zip...i dont have to back up anything...but thanks for the tip...if i get desperate enough, ill do it XD
At some point I read about someone who hadn't accepted the update yet, but still couldn't find update.zip. Is there anywhere else it might be located?
schwartzman93 said:
lol, thats why i want the update.zip...i dont have to back up anything...but thanks for the tip...if i get desperate enough, ill do it XD
Click to expand...
Click to collapse
total bs. you will have to do a wipe if you want the ota to run without fc's and general sluggishness.
iamtotus said:
At some point I read about someone who hadn't accepted the update yet, but still couldn't find update.zip. Is there anywhere else it might be located?
Click to expand...
Click to collapse
It should be on the root of your SD card...the only other place i could think of is the Android folder on your sd card or phone
lafester said:
total bs. you will have to do a wipe if you want the ota to run without fc's and general sluggishness.
Click to expand...
Click to collapse
So your telling me that everyone(300,000+) who gets the OTA should wipe their phone first?
schwartzman93 said:
Dont i have to root to install the ROM?...i dont want to do that
Click to expand...
Click to collapse
trust me rooting is the best thing that will happen to ur phone. i have easy instructions too in my sig.
k.electron said:
trust me rooting is the best thing that will happen to ur phone. i have easy instructions too in my sig.
Click to expand...
Click to collapse
Im sorry, but im not touching bases with rooting again, lol...i did it once and messed up my radio since i was a noob...i had to have someone guide me through the whole process of unrooting my phone and getting it back to stock...not only that, i know that you have to run unrevoked forever for 2.2...and i still dont understand what the heck s-on/off is
schwartzman93 said:
Im sorry, but im not touching bases with rooting again, lol...i did it once and messed up my radio since i was a noob...i had to have someone guide me through the whole process of unrooting my phone and getting it back to stock...not only that, i know that you have to run unrevoked forever for 2.2...and i still dont understand what the heck s-on/off is
Click to expand...
Click to collapse
False. You don't have to run unrevoked forever to get 2.2. You just need it if you want root afterwards. s-on and s-off refers to nand being unlocked or locked. You can run the RUU that is posted here with out unrevoked forever.
lafester said:
total bs. you will have to do a wipe if you want the ota to run without fc's and general sluggishness.
Click to expand...
Click to collapse
schwartzman93 said:
So your telling me that everyone(300,000+) who gets the OTA should wipe their phone first?
Click to expand...
Click to collapse
while it is not required, a wiped 2.2 phone will behave much better than one with stale stuff from 2.1
even on computers trying to upgrade a windows to the next version inevitably leads to some apps not liking it. the ui is an app, so the same applies.
schwartzman93 said:
Im sorry, but im not touching bases with rooting again, lol...i did it once and messed up my radio since i was a noob...i had to have someone guide me through the whole process of unrooting my phone and getting it back to stock...not only that, i know that you have to run unrevoked forever for 2.2...and i still dont understand what the heck s-on/off is
Click to expand...
Click to collapse
the whole process of rooting has got nothing to do with the radio, so unless u mess with the radio, u cant really mess the radio up.
rooting is simply flashing a payload-update with the root exploit to the rom. thats it. for 2.1 unrevoked has a one step exe that u run, go get a red bull and its done. it cant get any simpler.
the phones nand has a security lock called S. when its on (S-ON) one can only flash packages that are digitally signed. obviously a payload-update for future roms isnt going to be, so u want to be S-OFF. that is where unrevoked-forever comes into place. once that is flashed on your phone, u will be S-OFF meaning that any future rom can be rooted. it doesnt really do anything else to your phone.
that being said, u dont need root or s-off for the RUU as it is an official and therefore signed package.
k.electron said:
while it is not required, a wiped 2.2 phone will behave much better than one with stale stuff from 2.1
even on computers trying to upgrade a windows to the next version inevitably leads to some apps not liking it. the ui is an app, so the same applies.
the whole process of rooting has got nothing to do with the radio, so unless u mess with the radio, u cant really mess the radio up.
rooting is simply flashing a payload-update with the root exploit to the rom. thats it. for 2.1 unrevoked has a one step exe that u run, go get a red bull and its done. it cant get any simpler.
the phones nand has a security lock called S. when its on (S-ON) one can only flash packages that are digitally signed. obviously a payload-update for future roms isnt going to be, so u want to be S-OFF. that is where unrevoked-forever comes into place. once that is flashed on your phone, u will be S-OFF meaning that any future rom can be rooted. it doesnt really do anything else to your phone.
that being said, u dont need root or s-off for the RUU as it is an official and therefore signed package.
Click to expand...
Click to collapse
Well, I should have been more specific...after i loaded, then unloaded CM6, my camera wasnt working...after that, i was told it was my radio and was lead through the whole processes of getting it to unrooted stock...but i do have a question...if i do root with unrevoked forever...how to i get rid of clockwork recovery if i decide to unroot?
...and yes, im still a noob, haha
Nope
lafester said:
total bs. you will have to do a wipe if you want the ota to run without fc's and general sluggishness.
Click to expand...
Click to collapse
Wow that's wrong. The benefit of accepting the OTA rather than a RUU is keeping your settings, etc. And to put a swift end to any debate on the topic (since I certainly don't agree to attend to any incorrect claims to the contrary), please keep on thing in mind:
"Does Verizon now want to start taking 500,000 calls from the technically inept people who just want to use their phones, because they phone is now FC'ing all the time?"
Absolutely not. Same as iPhone. Apple does not want the tech support calls, and NEITHER Verizon nor Apple is telling people to wipe and start again.
I still haven't seen anyone post the update.zip. has anyone else? Am I lookingfor froyo love in all the wrong places?
Sent from my ADR6300 using XDA App
jdmba said:
Wow that's wrong. The benefit of accepting the OTA rather than a RUU is keeping your settings, etc. And to put a swift end to any debate on the topic (since I certainly don't agree to attend to any incorrect claims to the contrary), please keep on thing in mind:
"Does Verizon now want to start taking 500,000 calls from the technically inept people who just want to use their phones, because they phone is now FC'ing all the time?"
Absolutely not. Same as iPhone. Apple does not want the tech support calls, and NEITHER Verizon nor Apple is telling people to wipe and start again.
Click to expand...
Click to collapse
the phone is not going to fc but some apps will.
most people will just reinstall the apps and use the phone as is.
sounds like you want to be one of those people and thats fine.
the fact is that the phone will run better with a full wipe before or after flashing just like it does with any other rom change.
i run unrevoked and nothing happens. this a new problem with the new update? this is my replacement phone anwaysy so.
anyone know anyways to root? i can't downgrade to old version. please help..
if you have s-off you just need to flash a custom recovery.
if you don't then i have no idea if the updated rom is rootable.
that would have been something to look for before upgrading
Good luck!
Having custom recovery is not the same as rooting (Superuser acess). Unfortunately, at the moment, Unrevoked won't work on the new OTA and if you install SU pack after the OTA it will just hang during boot up and you'll be in reboot hell. You can have Clockwork with the new OTA, just not root access.
downgrading to stock then s-off and upgrading work?
update. i tried downloading the super back to stock thread and the hboot says the file is older and i can't by pass it.. so hmm
I am in the same boat. Just got the phone and the f-ing salesman decided to install the OTA for me while he was setting it up. So do I return this thing in the hopes of getting one without the OTA or is it likely it will be rooted?
guessing no ones able to do anything with the new update to reroot yet huh... any manual way to actually do root or downgrade to where the hboot doesn't recognize it as a older version?
dadsterflip said:
guessing no ones able to do anything with the new update to reroot yet huh... any manual way to actually do root or downgrade to where the hboot doesn't recognize it as a older version?
Click to expand...
Click to collapse
Nope, can't downgrade...I'm out of ideas. Pretty pissed off actually to the point where I'm ready to take it back and get one that doesn't have the god damn OTA applied. I HATE owning devices that I don't really own.
i rooted with unrevoked. it will stay waiting on root or something then you stop kill the program after phone is booted up.
imma be lazy and let you do the work but...
1. use unrevoked (not forever) http://downloads.unrevoked.com/recovery/3.21/reflash_package.exe
2. wait for it to say waiting for root and phone is restarted, then exit unrevoked.
3. place clockwork mod on sd card as pb31img.zip http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
4. go into recovery(volume down + power button) and let it detect pb31img and let it install
5. then use clockwork mod to install superuser apk manually http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
and yes this works, because i done it to 3 phones already
and yes this isnt hard...think outside of the box
I seem to have a problem. I was following the Bob Denny procedure to apply the OTA. Everything was going good until I got to the second step of booting into HBoot and reapplying the Clockwork recovery again. I cannot get into the Recover option in HBoot, it gets me stuck with the triangle over the phone image. I can boot normally and the phone is working but no root. In addition if I plug the usb cable into the phone, it charges but will not allow me to connect the phone as a disk drive, as well as the USB Debugging option is not there. I went to settings and tried the Connect To PC option but it FCs on me. The OTA part of this was successful (if you want to call it that). Any ideas on how to get this rooted again? Any help is appreciated.
Thanks,
Cary
caleris said:
I seem to have a problem. I was following the Bob Denny procedure to apply the OTA. Everything was going good until I got to the second step of booting into HBoot and reapplying the Clockwork recovery again. I cannot get into the Recover option in HBoot, it gets me stuck with the triangle over the phone image. I can boot normally and the phone is working but no root. In addition if I plug the usb cable into the phone, it charges but will not allow me to connect the phone as a disk drive, as well as the USB Debugging option is not there. I went to settings and tried the Connect To PC option but it FCs on me. The OTA part of this was successful (if you want to call it that). Any ideas on how to get this rooted again? Any help is appreciated.
Thanks,
Cary
Click to expand...
Click to collapse
press Volume Up + Power I think when you see the triangle
magneticzero said:
i rooted with unrevoked. it will stay waiting on root or something then you stop kill the program after phone is booted up.
imma be lazy and let you do the work but...
1. use unrevoked (not forever) http://downloads.unrevoked.com/recovery/3.21/reflash_package.exe
2. wait for it to say waiting for root and phone is restarted, then exit unrevoked.
3. place clockwork mod on sd card as pb31img.zip http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
4. go into recovery(volume down + power button) and let it detect pb31img and let it install
5. then use clockwork mod to install superuser apk manually http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
and yes this works, because i done it to 3 phones already
and yes this isnt hard...think outside of the box
Click to expand...
Click to collapse
But???????????? This will only work if you are already s-off, correct?
blackwolf77 said:
But???????????? This will only work if you are already s-off, correct?
Click to expand...
Click to collapse
if you have clockwork mod installed with S-On and updated the ota already, you can flash unrevoked forever through clockwork recovery... that will take S-Off to off. I was messing around earlier and did that..
I am not sure how you got clockwork installed. Everytime I try it recognizes the PB31IMG and then just skips over it. It never asks about installing it.
The file name has to be PB31IMG.ZIP right? Also the LCD works different right?
SLCD PB31IMG.ZIP
Sent from my ADR6300 using XDA App
Would the old downgrade and root process work? I upgraded my stock INC to 2.2 before Unrevoked worked on it. I went through a fairly painless, albeit time-consuming, process of downgrading to 2.1, rooting, and then installing 2.2.
I would think the process could be utilized here, the only difference being specific files used. One may even be able to follow the process as is. The end result would be S-OFF, which would allow you to do whatever you wanted (upgrade to 2.2 + recent OTA, install custom ROM, etc)
If anyone gets this to work, please let everyone know.
Nitrogenus said:
Would the old downgrade and root process work? I upgraded my stock INC to 2.2 before Unrevoked worked on it. I went through a fairly painless, albeit time-consuming, process of downgrading to 2.1, rooting, and then installing 2.2.
I would think the process could be utilized here, the only difference being specific files used. One may even be able to follow the process as is. The end result would be S-OFF, which would allow you to do whatever you wanted (upgrade to 2.2 + recent OTA, install custom ROM, etc)
If anyone gets this to work, please let everyone know.
Click to expand...
Click to collapse
in for answer
tried it out, didn't work. the su trick with rageagainstthecage-arm5.bin does not work.
how to see page 3
Standing by!!!!! Will it work with s-on?
It shouldn't matter s-on or off. I have the SLCD screen don't know if it will make a difference. Just FYI
Sent from my ADR6300 using XDA App
I am new to the rooting scene and I am very eager to root my HTC Glacier|MyTouch 4G.
I am however hesitant because I cannot risk bricking my phone.
Advice on how to recover from brick and an easy to follow guide to perm-root.
Thanks
geronimo711 said:
I am new to the rooting scene and I am very eager to root my HTC Glacier|MyTouch 4G.
I am however hesitant because I cannot risk bricking my phone.
Advice on how to recover from brick and an easy to follow guide to perm-root.
Thanks
Click to expand...
Click to collapse
What is the end result you are trying to get to?
If you are wanting S=off so you can flash custom ROMs.
http://theunlockr.com/2010/12/10/how-to-temporarily-root-the-t-mobile-mytouch-4g-htc-glacier/; do that and it will lead you to perma root the easy way.
if you are wanting s=off so you can have complete control over your phone, which will enable the possibility of a brick. including SuperCID, ./gfree and some other goodies...... But this will give you the option to severally screw up your phone including up to a 500.00 paper weight.
http://forum.xda-developers.com/showthread.php?t=858996
If you haven't screwed up the HBoot and the bootloader you can use this to get back to a factory spec.
http://forum.xda-developers.com/showthread.php?t=863899&highlight=level
But if this is your first android, and your first time rooting i would HIGHLY suggest doing alot of reading before you jump in head first. There are alot of people who have tried to do and get stuck. This phone is confusing once rooted with 2.2 ROMs and 2.3 ROMs and different recovery images you need to read and make sure you understand everything before jumping in feet first.
Temp root with visionary is the easiest and safest way, but gfree is pretty simple as well. The hardest bit is getting the drivers and ADB to work, and thats not overly difficult. (remember to use the command "ADB devices" to know if the drives are working) It just matters what you plan on doing, stock root or custom ROM.
There is really only two points that risk a hard brick, flashing the radio or hboot.
The gfree method does not require either, but you can flash the engineering hboot as optional.
The biggest thing with recoveries and ROMs is know that gingerbread based ROMs (like CM7) use ext4 file system and froyo ROMs use ext3. So it is important to use the right version of Clockwork recovery. Use v2.5.1.2 for froyo ROMs and v3.0 for gingerbread ROMs. Soon clockwork mod will support both on the same version.
Just read the instructions well and have all files downloaded and ready to go.
If you want to use gfree and a custom ROM, there is no need to get perm root on the stock ROM first. After the steps that get s=off, just run visionary as temp root with system r/w access and install ROM manager from the market, then use ROM manager to flash a new recovery. Reboot into recovery backup your stock ROM then flash a new ROM.
If you never touch the hboot or radio firmware, then at worse you can bootloop or soft brick the device. That can be fixed with varying amounts of work, depending on the exact issue.
Read and learn how the different parts work, learn how to use ADB and you will be better prepared.
newbie here
This is my first post. I would really appreciate anybody helping me out here. I can't seem to get any straight answers, or answers I can understand, anyway, so here goes.
I have an HTC Mytouch 4g. I did a temporary root (using the method at theunlockr.com) and uninstalled the monopoly app. I was going to uninstall a bunch of other stuff but I got nervous and did a factory data reset (in the SD & phone storage area). All of my marketplace apps reinstalled, which I thought wasn't supposed to happen, but anyway.... I did the volume down/power on and see now that my phone is GLACIER PVT SHIP S-ON. So my question is how to interpret the state that my phone is now in. Is it factory? Is it rooted? Will the T-Mobile OTA updates work? Why is the monopoly app still gone? Is my warranty voided?
ibnird said:
This is my first post. I would really appreciate anybody helping me out here. I can't seem to get any straight answers, or answers I can understand, anyway, so here goes.
I have an HTC Mytouch 4g. I did a temporary root (using the method at theunlockr.com) and uninstalled the monopoly app. I was going to uninstall a bunch of other stuff but I got nervous and did a factory data reset (in the SD & phone storage area). All of my marketplace apps reinstalled, which I thought wasn't supposed to happen, but anyway.... I did the volume down/power on and see now that my phone is GLACIER PVT SHIP S-ON. So my question is how to interpret the state that my phone is now in. Is it factory? Is it rooted? Will the T-Mobile OTA updates work? Why is the monopoly app still gone? Is my warranty voided?
Click to expand...
Click to collapse
Temp root is just that, temporary. It creates a copy of the essential files in the system partition that it runs from rather than the actual system partition. If you allow it r/w access, (an option you can choose when using visionary) it can uninstall apps that normally can not be. (and more, but causing big changes would require more work on your part)
Because it is temporary, there is no need to get nervous. Unless you are doing some major changes, ones that need a root explorer app or terminal emulator, then you can't really hurt the phone. Download terminal emulator from market and run it, then type in the super user command "su" (no quotes) then hit enter, if the cursor changes to a # symbol then you have root. (you may get a popup asking for root permission, choose to allow) If it works after a fresh reboot, you either ran perm root in visionary, or you have the option checked to temp root every reboot.
S-ON means that the bootloader security is still in place. You need it off to install custom software. While you can root the stock software with S-ON you can not install any software that has potential to brick your phone, so no need to worry at all. If you are really that worried, keep a copy of the stock software on your SD card. Make sure it is named PD15IMG and at any time you get nervous, you can boot into hboot (the bootloader) and it will run automatically. It will wipe your phone and return it to complete stock. The irony is, that flashing this stock image file does things that can brick a phone if it goes wrong. It flashes more than just the OS, it also flashes hboot and recovery as well, and if the process is messed up in anyway like loosing power at the wrong time, it can brick the phone.
Really as long as you make sure you have the phone charged and you follow instructions you should be fine. The only times you can brick a phone to the point it can not be brought back is when flashing hboot and the radio firmware. Both of which you would rarely flash. Hboot only needs flashed to the engineering version once (OEM testing/DEV version) and only if you choose to, as it is not required. The radio will only need flashed if an update for it comes out, and that isn't often, and it is rarely mandatory.
The chance of truly bricking your phone is not very high, unless you just can't follow the directions. Now you can put it into a bootloop or soft brick it. (bootup stuck on mytouch screen) But if you can boot the phone into hboot (vol down + power on) then you can fix it. Even if you can not boot into recovery (an option in the hboot menu) you can even fix that with a good hboot.
theres a video on youtube by mackster its awesome and it gives you all the links very easy to use.
it wont let me post the link but just search root mytouch 4g on youtube and it should be the first or second one.
Thanks Marine and Tommy.
So with temporary root, as soon as I turned off and then back on the phone, it was back to its unrooted, original state, minus the T-Mobile application? Will I now get T-Mobile's Over the Air (OTA, right?) updates and not have a problem if I need warranty work?
ibnird said:
Thanks Marine and Tommy.
So with temporary root, as soon as I turned off and then back on the phone, it was back to its unrooted, original state, minus the T-Mobile application? Will I now get T-Mobile's Over the Air (OTA, right?) updates and not have a problem if I need warranty work?
Click to expand...
Click to collapse
Uninstalling an app will not hurt anything. OTA updates will still work fine. You can temp root and then perm root the stock ROM and revert easily. Heck, even perm rooting stock doesn't break OTA I believe.
Voiding the warranty is one of those grey areas. As long as you can revert to stock, then they will never know. Temp root does not void warranty at all, because you do not alter the system files. (unless you want to, and enable the ability to read/write system) Just uninstall terminal emulator and super user apps and there is no evidence.
The only time you might get caught, is if say the screen stops working, and you can not see to revert back. Though even then, just putting the stock OTA image on the sd card then booting up the phone in hboot will restore without needing to actually see anything. It does ask for confirmation to restore, just wait several minutes then hit the power button and it would do it on its own.
The set of circumstances needed to prevent you from restoring to stock, are rare. Basically a borked hboot or radio firmware, and you never need to touch those to get full root and custom ROMs. If you never touch them, the chance of issue is almost zero.
I just got my mt4g and I am looking to root my phone for the following reasons:
apps2sd
remove bloatware (I want the app to be disabled and I don't want the icon in my app drawer)
use adfree
I don't want any custom roms and I'd like to keep sense ui.
Can anyone tell me if this is at all possible? I've read around and I know it's possible but I don't know about rom flashing and I'm confused as to whether or not I need to flash a custom rom? What's the point of a custom rom anyways?
goldfish524 said:
I just got my mt4g and I am looking to root my phone for the following reasons:
apps2sd
remove bloatware (I want the app to be disabled and I don't want the icon in my app drawer)
use adfree
I don't want any custom roms and I'd like to keep sense ui.
Can anyone tell me if this is at all possible? I've read around and I know it's possible but I don't know about rom flashing and I'm confused as to whether or not I need to flash a custom rom? What's the point of a custom rom anyways?
Click to expand...
Click to collapse
You dont need apps2sd, as the mytouch 4g has Froyo installed, and you can move some apps to the SD card. Just go into settings-Applications-chose the applicaiton you want on your SD card, and look for "move to SD". If it's grayed out, then you cant move it.
Also download appfreezer from the market, and just "freeze" the bloatware. That's what I do, and it gets rid of those annoying looking apps they installed.
Question about clockworkmod
OK i just rooted my phone, flashed the rom, and installed all the goods... it works perfectly and looks great.
Ty for all the guides/ instructions.
My only question is about the clockworkmod. When I turn off my phone and plug it in to charge the recovery screen always appears when off and connected. Is this suppose to happen? Or is there a solution to this?
If there is a solution can some one post a link or provide instructions so it doesn't constantly boot to clockworkmod recovery.
Thanks.
I used the info on this page: *android.modaco.com/content/htc-desire-desire-modaco-com/310873/possible-hboot-downgrade/* it didn't downgrade the hboot, but that might be something to work on.
CHANGE STEP 3.4. "change it to 1.15.405.1" don't do that, change the "2.20.502.1" in the misc.img from your aria to 1.25.502.2
Oh and you'll need either a Temp root, or a Shell root for adb
I have done this and can confirm that this works
Thanks mate!
I just noticed the Aria got 2.2 finally, albiet through this silly sync method.... It's my wifes phone, I'm sure she's not going to be happy to have to hard reset it.. wth.
Anyway, so why are you guys going back to 2.1? I am surprised not to see more discussion on 2.2 in this forum, but I don't frequent it much since I don't own the Aria myself.
khaytsus said:
I just noticed the Aria got 2.2 finally, albiet through this silly sync method.... It's my wifes phone, I'm sure she's not going to be happy to have to hard reset it.. wth.
Anyway, so why are you guys going back to 2.1? I am surprised not to see more discussion on 2.2 in this forum, but I don't frequent it much since I don't own the Aria myself.
Click to expand...
Click to collapse
I went back to 2.1 because the 2.2.2 version that AT&T released was extremely slow, and my touchscreen would become unresponsive.
andrewishcool95 said:
I used the info on this page: *android.modaco.com/content/htc-desire-desire-modaco-com/310873/possible-hboot-downgrade/* it didn't downgrade the hboot, but that might be something to work on.
CHANGE STEP 3.4. "change it to 1.15.405.1" don't do that, change the "2.20.502.1" in the misc.img from your aria to 1.25.502.2
Oh and you'll need either a Temp root, or a Shell root for adb
Click to expand...
Click to collapse
How do you get a temp root or shell root with the new HBoot still in-place? If temp root is possible, then can't you install clockworkmod and get permaroot?
Gene Poole said:
How do you get a temp root or shell root with the new HBoot still in-place? If temp root is possible, then can't you install clockworkmod and get permaroot?
Click to expand...
Click to collapse
I got a shell root from super one click root (forum.xda-developers.com/showthread.php?t=803682)
after I downgraded to 2.1 I got z4root to get a temp root.
andrewishcool95 said:
I got a shell root from super one click root (forum.xda-developers.com/showthread.php?t=803682)
after I downgraded to 2.1 I got z4root to get a temp root.
Click to expand...
Click to collapse
I'm also very curious about this.
Sounds like the first steps to rooting and downgrading. I'm curious to see if any developers catch this
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
I've been reading up on this and the skinny is that the HBOOT image controls the S-ON and S-OFF flags of the NAND RAM in the device. Even with a temp root shell, you can't write to a partition with its S-ON flag set. This normally includes all the partitions on the phone except the data partition, so trying to root the device requires some sort of interaction with the HBOOT image to turn off the S-ON flag for the recovery and system partitions to properly root a phone.
In short, if and until someone hacks hboot_liberty_7227_1.02.0000_101104, your phone is unrootable.
Gene Poole said:
I've been reading up on this and the skinny is that the HBOOT image controls the S-ON and S-OFF flags of the NAND RAM in the device. Even with a temp root shell, you can't write to a partition with its S-ON flag set. This normally includes all the partitions on the phone except the data partition, so trying to root the device requires some sort of interaction with the HBOOT image to turn off the S-ON flag for the recovery and system partitions to properly root a phone.
In short, if and until someone hacks hboot_liberty_7227_1.02.0000_101104, your phone is unrootable.
Click to expand...
Click to collapse
Help me out, I may be thinking in the wrong direction, but I've been dealing with my nook which is why I thought of this.
Is there not a way to write an hboot to an sd-card or connect via usb at start to make the aria think that the sd-card or the usb connection is the corrected hboot, thus being able to modify?
FroztIkon said:
Help me out, I may be thinking in the wrong direction, but I've been dealing with my nook which is why I thought of this.
Is there not a way to write an hboot to an sd-card or connect via usb at start to make the aria think that the sd-card or the usb connection is the corrected hboot, thus being able to modify?
Click to expand...
Click to collapse
There may be. When I first got my Aria, the rooting procedure involved an HTC signed update that you fooled the hboot into partially loading, then swapped the sdcard with the root package. It involved some complex timing issues where you had to run adb in a loop and plug/unplug the usb cable at appropriate times.
I've been searching the net for that procedure and I can't seem to find the right search terms, or I'm just not looking in the right places or something, but I know that's how I did my Aria before there was an unrevoked plug-n-root.
I have the procedure u are looking for i think...let me know if this is what u were after because i have an archive of saved documents I have copied from forums in the past...GOOD LUCK!
well apparently i haven't posted enough to put the links up in the post
PM me if you want the process...
xerotix said:
PM me if you want the process...
Click to expand...
Click to collapse
May I have a copy of said process? Currently the only way is to buy a very expensive hardware called XClip. I have managed to get the updated 2.2.2 Stock ROM rooted but not deodex or EXT3 FOR ap2sd trying to play with some files from another source to get hboot s off.
econcep said:
May I have a copy of said process? Currently the only way is to buy a very expensive hardware called XClip. I have managed to get the updated 2.2.2 Stock ROM rooted but not deodex or EXT3 FOR ap2sd trying to play with some files from another source to get hboot s off.
Click to expand...
Click to collapse
That process does not work with the new HBOOT. That's why unrevoked doesn't work. Having root access does not unlock NAND.
Currently, the only way known is via hardware tools.
It works. I managed a work around for 2.2.2 update
Hey everyone I am in the second phase of testing my work around with the new HTC Aria update from ATT. I managed to load the update and keep my phone rooted. I am now in the setup mode with no bootloop.
Running into a couple of issues with the new radio but I believe I know how to fix that as well. Keep you all posted and once all bugs worked out I will post my findings and HOPEFULLY MY ROOTED ROM.ZIP with instructions.
IF AT FIRST YOU DON'T SUCCEED.....TRY TRY TRY and TRY I did and I am 99% there.
econcep said:
Hey everyone I am in the second phase of testing my work around with the new HTC Aria update from ATT. I managed to load the update and keep my phone rooted. I am now in the setup mode with no bootloop.
Running into a couple of issues with the new radio but I believe I know how to fix that as well. Keep you all posted and once all bugs worked out I will post my findings and HOPEFULLY MY ROOTED ROM.ZIP with instructions.
IF AT FIRST YOU DON'T SUCCEED.....TRY TRY TRY and TRY I did and I am 99% there.
Click to expand...
Click to collapse
This might be the wrong thread. Did you manage to get around the HBOOT issue with the 2.2 update? If not, then you've just done the same thing I did the day after this release was out:
http://forum.xda-developers.com/showthread.php?t=970272
Gene Poole said:
This might be the wrong thread. Did you manage to get around the HBOOT issue with the 2.2 update? If not, then you've just done the same thing I did the day after this release was out:
http://forum.xda-developers.com/showthread.php?t=970272
Click to expand...
Click to collapse
You are right this might be the wrong thread. But I managed a work around with the new update 2.2.2 and the HBOOT 1.0X. As soon as I can confirm without a doubt that it works and will be able to repeat the process successfully with my husband's ARIA (unfortunately we love hacking things and tend to buy multiple devices) I will be more than happy to share the results.
Again, my apologies if it's the wrong thread.
econcep said:
You are right this might be the wrong thread. But I managed a work around with the new update 2.2.2 and the HBOOT 1.0X. As soon as I can confirm without a doubt that it works and will be able to repeat the process successfully with my husband's ARIA (unfortunately we love hacking things and tend to buy multiple devices) I will be more than happy to share the results.
Again, my apologies if it's the wrong thread.
Click to expand...
Click to collapse
Perhaps I misread (or we're talking past each other). You do have, in fact, HBOOT 1.02.0000 on your Aria, and managed to write to the system partition?
Yes & No. I'm stuck on couple of things. First the will temporary give me root access but then it locks up saying I don't have busybox. I'm rooted but no s-off. I also noticed when I reboot into recovery I go into CWM 2.5.0.1 but other times it boots into CWM 2.5.0.7. When that happens I loose my unknown source in settings>application. Again, if this is the wrong thread, I really am sorry.
I googled alpharev and some others who have worked on rooting. Found some cached pages from Jan when they were testing to root/s-off the Aria. Basing my work on that and couple of other devices that are similar to the Aria.
Okay, here is the deal. I was trying to change around some stuff on my phone, the IMEI number to match the one on my prepaid tracphone. So far, before I changed the IMEI, i had it rooted and everything was slamming. But it would disconnect me after about a half hour. I am changing the IMEI to see if it fixes this, but after all this I had to revert back to a total stock flash of 2.2.1 HTC rom, it updated everything, one of those PBxx.img ones you do during the bootloader.
So now I've rooted it with visionary, and it hardly works, won't permaroot, but I get regular root. So I did another method on a wiki and have permaroot now. Updated SU, clockwork mod, ETC and everything works (well it installs and prompts me to give super user access then doesnt complain.)
HERE IS THE PROBLEM: I CANT CHANGE RECOVERY OR BOOTLOADER TO S-OFF
I have used gfree (multiple versions) to turn s off, and turn off all locks and to change the bootloader the nb0 one. BUT NOTHING gives.
>Clockworkmod from the rooted main screen, when i open the app, it won't install the clockwork mod recovery.
>When booting to recovery, the phone goes to stock recovery with the red triangle and phone. Upon where you have to push VOL UP + PWR button to see any options, and they are just the stock ones, (reboot, apply update:sdcard, etc)
I was wondering if someone had a signed image that they could link to me or send or whatever that has the s-off in a format that I can use with the BOOTLOADER; i.e.: Just put it on SD-CARD, hold "VOL UP+PWR" then it will do the update. U know, like radios are flashed.
If you can help me please, help me. I was so excited with this phone and moving along and now this.... ARG! lol. Thanks guys any and all input is appreciated no matter how irrelevant!
peace
GLACIER PVT SHIP S-ON
HBOOT-0.86.0000
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Sep 27 2010,11:12:59
You don't have perm-root.
Gfree can't work without root. Since you don't have perm-root without Gfree, you need temp-root.
While not S-OFF, you can't have perm-root. Period. End of story. Temp-root and execute Gfree.
Execute the rooting guide in Wiki properly, and you'll have S-OFF.
Of course, having no perm-root makes it impossible to flash recovery, or flash anything at all.
help.. tried root explorer, astro, es file..and have had no luck flashing to better roms...help
Sent from my HTC Glacier using XDA Premium App
If you are using Visionary R14, try R11. And f*ck wiki.
Jack_R1 said:
You don't have perm-root.
Gfree can't work without perm-root.
While not S-OFF, you can't have perm-root. Period. End of story.
Execute the rooting guide in Wiki properly, and you'll have S-OFF.
Of course, having no perm-root makes it impossible to flash recovery, or flash anything at all.
Click to expand...
Click to collapse
G-free turns s-off. If he has a bad eMMc chip, G-free is the only method he can use. And some phones have issues with the newer version of visionary.
lowandbehold said:
G-free turns s-off. If he has a bad eMMc chip, G-free is the only method he can use. And some phones have issues with the newer version of visionary.
Click to expand...
Click to collapse
I guess I wasn't clear enough in my response above, and wrote "perm-root" where just "root" was in order. Edited.
In any case, when was the last time you've read the Wiki? I suggest you look at it again.
I don't know if I am explaining correctly.
I applied the root method using visionary r14 because thats the latest from the site, it temp roots, but does not perma root.
I did a su, and got root, but I have to SU before i get root, it asks for SU permissions and I allow and I have root. (all this is done in a shell). So I know I have root, i can open up the system to read write and even delete some stock .apk and other files that aren't supposed to be deleted. So its all good. I can chmod 777, i know whats up there.
I did all this madness, SU updates to the most current binary, clockwordmod both an older and the newest version open, ask for and allow SU permission, and all that appears to work fine. EVEN with the friggen flash clockworkmod recovery, it says current recovery: clockworkmod x.x.x.x (meaning whatever the version is, tried a bunch).
BUT WHEN I BOOT TO RECOVERY OR BOOTLOADER, S-ON and friggen stock recovery for me. WHAT THE heck. its like its ignoring what I do to flash the bootloader.
Does anyone have a PBxx.IMG they can send, hopefully signed, that I can just use to update? or link to one? also, and update.zip for the stock recovery would work too.
HERE's the thing, its a T-mobile phone, and my TRACPHONE Prepaid sim works on it, but that *MIGHT* just be because TRACFONE = AT&T also T-Mobile=AT&T now also.
But I think the sim is unlocked, I'm waiting on other sim to come in the mail before I can verify for sure.
MAIN thing i need is a signed (or I'll even play with an unsigned) PBXX.img file for either the bootloader or recovery, or an update.zip one. At this point, if you have a lower version of 2.2.1 that has the whole entire shebang, (the radio, bootloader, os, recovery, etc) then I'll appreciate that too.
I just can't find it on here after days of searching and I am needing a push in the right direction. And google's overloaded with the SAME article just in different spam blog formats. Thx guyz
You CAN'T.
Everything you do when you're temp-rooted, DOESN'T GO TO THE eMMC! It stays in memory (eMMC cache), and the next time you reboot - everything is GONE. All your file deletions, chmods, etc - they're NOT REALLY EXECUTED. Reboot and see for yourself.
The only thing that will make it stay - is running gfree and gaining S-OFF.
The link, as everything else you're looking for, is in Wiki. Look in the Downgrade guide, there's a link for 2.2.1 RUU for MT4G. But it won't help you - you're just being stubborn and unwilling to read. YOU DIDN'T EXECUTE PERMAROOT PROPERLY, AND UNTIL YOU DO - YOU WON'T BE ABLE TO FLASH A DAMN THING.
The Wiki links to a Gfree method guide. Read it and execute it STEP BY STEP.
Okay, i did it
Here is what I did. I went in manually and copied the .nb0 to the file several times in a row.
Visionary does not work, the only way I can root this thing, without some type of temproot visionary app that messes up, is this way:
http://wiki.rootzwiki.com/index.php/HTC_myTouch_4G
Also, I am hoping I am correct, but this is how its laid out in the /dev block...
mmcblk0p18: HBOOT DATA (bits) And....
mmcblk0p21: RECOVERY DATA (bits) data or bits, whatever you want to call it. (its not a file)
Okay. So with that being said;
/dev/block/mmcblk0p18 = hboot 'file' and this is what i did.
Using 'dd' which is a unix command that just does low level convert and copy, will take the input file if=hboot_hacked_file.nb0 and then put it to the output device converting it and whatnot, the output file of=/dev/block/device
so it looks like this in example:
Code:
# dd if=/directory/filename.xxx of=/dev/block/output_device_or_file
Oh, and another thing that might just be paranoia... The wifi was on and it wasn't doing what it was supposed to do, I noticed it also being active unusually, I should have put wireshark on and checked it out, but didn't think about it at the time. Now that wifi off, it feels as if its fine now. It was almost like another user was in it. But thats probably just paranoia..... or the t-mob trying to mess me around!!!
This IS the gfree method, and you ARE running an app to gain temp-root there.
Copying the bootloader didn't help you at all, it was only a later step. It wouldn't stick if not for gfree.
Running gfree did.
Oh well, I guess that it's useless to explain. Glad it worked.
naw bro, its good that you explain what you mean, its not useless to explain anything. Here is what I'm saying... gfree -f is supposed to do the S-OFF right? well, it didn't. it also said failed or error or something at the end. Once I did the 'dd' command not just once, but several times and VERIFIED that it was working and different, while having # then I ran gfree again and it said SUCCESS at the bottom and THAT did it bro. SO that, in the end, turned my s-off and gfree unlocked my sim super unlock and cid unlock too.
I've cloned my IMEI because its legal, its my own phone and I'm not doing anything extra other than using it to make calls which I pay for at outrageous prepaid prices.
Does anyone know where that information is located by the way, just for information purposes... I've already done it using a hex editor and a part7.bin file... but I just am not quite sure on EXACTLY what I've done. like, the locations of what file or data that i've flashed. With CDMA, I usually enter QPST programming and all that and just just play till my heart's content... but now I'm trying to learn GSM and I want to know if there is a way to enter that kind of programming also. Or are us fellas forced to dump .bin files, hex edit, then reflash or reflex em...
Just lookin for some pushes in the right direction for programming in the GSM area.
Also if you have links to radios, all of them, previous and what not, I would appreciate it too
Flashing hboot, superuser or not, several times or not, didn't do a thing for unlocking.
For what reason gfree failed initially - I don't know, but when you ran it again and it didn't fail - that did it all. Otherwise you'd still be with S-ON, and the bootloader would still be the same.
You can't really argue against HW. That's how it works.
Radios are here:
http://forum.xda-developers.com/forumdisplay.php?f=796
Look for "Glacier Radios" sticky.
Like I said before as well. There are alot of issues with R14...find and use visionary R11. You are not the first person to have issues with visionary, and with the majority of them, the downgrade solved the problem.
Not true
I have try everything and nothing work. R11, r14 from visionary and it dosent work. Please devs try to get another method for the people that nothing work. I have hboot 0.86.0000
ahernandez646 said:
I have try everything and nothing work. R11, r14 from visionary and it dosent work. Please devs try to get another method for the people that nothing work. I have hboot 0.86.0000
Click to expand...
Click to collapse
Do you have Android version 2.3.4?
If so, Visionary won't work. You have to downgrade to 2.2.1 first. There is no way around this. But it's easy to do.
Skipjacks said:
Do you have Android version 2.3.4?
If so, Visionary won't work. You have to downgrade to 2.2.1 first. There is no way around this. But it's easy to do.
Click to expand...
Click to collapse
No, that's the froyo bootloader.
What happened when you ran visionary? Did you have usb debugging checked? Sometimes the temp root works on the first try, sometimes on the tenth. If it doesn't work, reboot and try again. If it still doesn't work after several attempts do a factory reset and try again. Sometimes a clean slate helps.
Sent from my HTC Glacier using XDA App
i do have 2.2.1 but i had a mytouch 3g slide and i root it. but for some reason i can't get the mytouch 4g to do it. i will re-try everything again.
Thanks to all that have reply.