I've been trying to root my G2 since last night, and before I start, I have to say I do NOT and WILL NOT have access to adb. Some drama with my father caused him to revoke my administrator privilages on all the computers in my house. So I can't install anything or run any unknown .exe's.
The only way I can go about this is using Visionary so far. However, it's been a piece of crap up to this point. I have +r14, USB debugging enabled. Regardless of whether I check "Set system to r/w after root", I always get the same two results when i hit Temproot.
Sometimes it'll go through a couple of triangle screens w/ "rooting device, please wait" and then go back to the main option screen. However, this seemed to do nothing but install Superuser with NO APPS requesting su permissions. After this I'll try to hit "Attempt Permroot now" and it will say "Please Temproot before attempting Permroot". "Unroot now" just says my device isn't rooted. >_> Going into terminal and typing "su" gives me a "su: Permission denied".
Other times when I hit Temproot, it'll go through a few triangle screens, and then just stop on a black screen with only the status bar visible. I can still Home out and use the notification bar and such though, so it's not a total system freeze.
Can someone please help me out here? I ordered my phone on 2/4/11 and got it maybe a week later if that makes any difference, because I've been hearing some things about people not being able to use Visionary on newer phones.
Try using this GUDIE HERE. No ADB needed.
I've tried that guide and one of the two scenarios I provided always happens. :\
I got my phone brand new from the tmo corp store sat night and I had no problem with rooting via visionary and gfree.
Mine did not have that 1.72 update tho. Maybe that's your problem.
From my permarooted overclocked HTC G2 with cyanogen 7 nightly via XDA app
tackleberry said:
I got my phone brand new from the tmo corp store sat night and I had no problem with rooting via visionary and gfree.
Mine did not have that 1.72 update tho. Maybe that's your problem.
From my permarooted overclocked HTC G2 with cyanogen 7 nightly via XDA app
Click to expand...
Click to collapse
Tmobile phones don't get the 1.72 updates, that's only for the desire Z's, Tmobile G2's only have the 1.19 or the 1.22 OTA roms on it.
Sent from my HTC Vision using XDA App
How do I check what update I have? (I heard having Wifi tethering and Wifi calling affects that, I have both)
legendaryxm90 said:
How do I check what update I have? (I heard having Wifi tethering and Wifi calling affects that, I have both)
Click to expand...
Click to collapse
If you have wifi calling and tethering built-in, then you have the 1.22 OTA update already (I think all of the newer G2's come with it). I'm not sure if it shows up anywhere you can check easily, but I do know the OTA came with a newer radio so you could check in your Settings->About phone. The baseband version should end in something like 26.03.02.08.
The version number is also stored on partition 17, but I don't think you can check that without at least temp root. Not positive though.
I have no idea why Visionary is having problems even temp rooting your phone. One problem may be that you tried the permroot function within it (I don't know what it does, but many users have reported strange behavior when it doesn't work right).
Maybe you can try doing a factory reset and then starting again. Also, you might want to try disabling all of the added functionality in Visionary (such as temp rooting or setting system as R/W on boot), restarting the phone, and then trying the temp root again. Or uninstalling Visionary and then reinstalling it.
If you can just get su to work in terminal, then you should be okay.
joemm said:
Tmobile phones don't get the 1.72 updates, that's only for the desire Z's, Tmobile G2's only have the 1.19 or the 1.22 OTA roms on it.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
me=de de dee! lol. thanks for that info. i didnt know that specific detail.
Ok, so I just factory reset my phone, and I'm going to try this with a fresh downloaded r14. Gonna try with no options checked. Also, is it better to do this with the phone connected to the computer or not?
EDIT: OK here's what I was talking about. -_- Just tried it TWICE. First time it went back to the option screen, Terminal gives me su: permission denied again. Did it a second time. Currently stuck on a black screen w/ only status bar visible. WTF IS GOING ON MAN.
legendaryxm90 said:
Ok, so I just factory reset my phone, and I'm going to try this with a fresh downloaded r14. Gonna try with no options checked. Also, is it better to do this with the phone connected to the computer or not?
EDIT: OK here's what I was talking about. -_- Just tried it TWICE. First time it went back to the option screen, Terminal gives me su: permission denied again. Did it a second time. Currently stuck on a black screen w/ only status bar visible. WTF IS GOING ON MAN.
Click to expand...
Click to collapse
Not sure what's happening. How long are you waiting on the blank screen? I've seen some people say the temp root took a while on their phones. I saw in one of the forums (maybe dev), someone posted another app that can achieve temp root as well. Might be worth taking a look...
I waited 15-20 minutes and nothing. >_> I'll look for that other app because I just read somewhere that VISIONary doesn't work on the latest OTA phones. Is that true?
EDIT: Haven't found anything. Is there ANY hope for me without adb? :<
Here's the other temp root program someone mentioned: http://forum.xda-developers.com/showthread.php?t=951208
Never tried it myself but maybe it'll work for you.
Also, I think the thing about Visionary not being compatible for OTA phones was only for the permroot option. Like I said, people have reported really strange behavior when it doesn't work.
Just thought of another thing to try. Maybe clear the data for the superuser app. Hopefully when you try su in terminal then, it'll pop up with the dialog box asking for permissions again.
ianmcquinn said:
Just thought of another thing to try. Maybe clear the data for the superuser app. Hopefully when you try su in terminal then, it'll pop up with the dialog box asking for permissions again.
Click to expand...
Click to collapse
D'OH. THAT DID IT. Got the superuser popup!
THANK YOU SO MUCH!! +REP
Related
I just got the notification for it, but I don't want to risk anything. Is it good to go?
no, before this gets moved, not good to go. don't flash it. you will lose root
seems like you will lose the root...
but some have posted that even after the ota update... the current root process will still work.
Strange. Thanks, guys.
You'd loose your root.
gabemeyers said:
seems like you will lose the root...
but some have posted that even after the ota update... the current root process will still work.
Click to expand...
Click to collapse
I rooted did OTA and still seemed to have root access. Just re-rooted and it seems cool flashing stock rom in a second I guess to confirm
Ok I didnt flash a rom but it is letting me do data wipes and all other functions it seems cool!
Flipz confirmed my successful Re-root looks like OTA is safe!
I rooted mine BEFORE the OTA upgrade.. and it stayed rooted after.. -m
I'm not taking any chances. The other dev team is supposed to release their root and it may be more complete than what we have now. No reason to take a chance on an update that isn't totally critical.
I just tried it.. it appears to fail, reboots, and you're still on 1.32.651.1.
sph33r said:
I just tried it.. it appears to fail, reboots, and you're still on 1.32.651.1.
Click to expand...
Click to collapse
What exactly does the this ota do anyway?
1wingangel said:
What exactly does the this ota do anyway?
Click to expand...
Click to collapse
It's supposed to fix the read/write permissions glitch with the MicroSD card.
diomark said:
I rooted mine BEFORE the OTA upgrade.. and it stayed rooted after.. -m
Click to expand...
Click to collapse
Let me correct this.. The OTA update did not work.. (I stayed at the old software version after trying to apply it.. but root stayed around..)
NOW has anyone managed to place the SD card fix on here manually?
-mark
Yes please. Just update.zip that goodness please. I am sure a complete SuperFresh Rom is on its way.
Well i guess I got this all backwards
I didnt know any better when I got the phone in the store, and I did the update...
then decided to root it.... did the process....
it worked.... but then I had the insufficient permissions on the SD card issue...
after reading a bunch of yea's and nay's on OTA update
I finally made the decision to just due the OTA update cuz I that SD card issue really bugged me...
I did the OTA update, the phone did this funny thing where its showing a green progress bar and then in the middle of it, a red question mark pops up as if it were saying " what the hell is this??" lol
it rebooted... and phone came back online, and now my SD card isnt having the same issue anymore...
UPDATE: Its back.... so now what do I do? Is there any way I can include all my info and settings and apps in a custom recovery cuz if i have to do this again im gonna freak. lol
lbheightsboy said:
I did the OTA update, the phone did this funny thing where its showing a green progress bar and then in the middidle of it, a red question mark pops up as if it were saying " what the hell is this??" lol
Click to expand...
Click to collapse
your having the same problem as me... the update failed.. which is why were waiting on a way to manually apply the update.
OTA worked perfectly. And I get root access
I still haven't gotten the OTA...no matter how many times I manually "check now" in HTC Software Updates, it does not show up. I don't know why this is happening, it's very odd. I'm waiting for someone to cook the update into a custom, or rather stock, ROM. It's driving me insane at the moment, not to mention a bunch of apps are missing from the market (a whole other issue in it's own right). If anyone has an update.zip I can flash or a way to fix this, please please please let me know. Thanks.
I wasn't getting the OTA notification either until I enabled WiFi, then restarted the phone. Worked perfectly after that. Didn't even have to go to system updates.
-------------------------------------
Sent via the XDA Tapatalk App
Hey everyone. between my brothers and I, we have five Evo's. two of us are running full roots and nand unlocks, the other three are using unrevoked. those that unrevoked can use the wifi router without issue, but for my brother and myself, using the wifi router results in the app crashing and having to force close.
has anyone seen anything similar? can anyone offer me some solution?
and btw, this is my third rom. they all have the same results(full wipe, data and davik cache clear each time)
Delete wi fi tether from the phone and re-download it. This has worked for me everytime i change roms =)
Hope it helps.
Do you mean the wireless tether app? I am running my own rom but it seems that it worked for me when I was using fresh. But that is the only other rom I have tried. Have you tried re-installing the tether app?
I'm not sure i can remove the base wifi tether app. it's always cooked into the rom. and i have tried reinstalling the app. i've gone from the original version, to the newer version and finally the beta version with no luck
I was having this issue for awhile. I'm not sure exactly what fixed it, but my work around was:
1. Re-install from the market place (Do not launch)
2. Reboot
3. Install this version http://code.google.com/p/android-wifi-tether/downloads/detail?name=wireless_tether_2_0_5-pre2.apk&can=2&q=NexusOne
(Don't lanch)
4. Reboot
5. Should work now
Hmmmmmm. I am sure someone else can offer better advice, but does the super user app come up to ask for permission or it fc's before that?
topdawgn8 said:
I was having this issue for awhile. I'm not sure exactly what fixed it, but my work around was:
1. Re-install from the market place (Do not launch)
2. Reboot
3. Install this version http://code.google.com/p/android-wifi-tether/downloads/detail?name=wireless_tether_2_0_5-pre2.apk&can=2&q=NexusOne
(Don't lanch)
4. Reboot
5. Should work now
Click to expand...
Click to collapse
okay, i did exactly as you said. now the app will start, but as soon as i click on the wifi symbol, it thinks for a second and says "Unable to start tethering. Please try again!"
Edit: and on first run, it asked me for super user permissions. i click grant and checked the box to allow future requests
I am not sure if your signature is correct but have you tried flashing the newest radio? I am not sure if that would fix it or not. And the same thing happens to the other phone? Puzzling indeed. I'm sure someone will drop in and tell you how to fix it soon. Worst case, start over. Even though I know you said you tried various roms, maybe you are accidentally skipping a step, I do that sometimes
SilverStone641 said:
okay, i did exactly as you said. now the app will start, but as soon as i click on the wifi symbol, it thinks for a second and says "Unable to start tethering. Please try again!"
Edit: and on first run, it asked me for super user permissions. i click grant and checked the box to allow future requests
Click to expand...
Click to collapse
Ok, go back through the same process and try this one instead of what was in step 3.
http://code.google.com/p/android-wi...me=wireless_tether_2_0_2.apk&can=2&q=NexusOne
If that doesn't work, I've got nothing else. The first one was the beta you probably tried earlier. This is the stable one; however, I never tried it with this one. I always got it working using the 2_0_5 version.
Also, for ****s and giggles, have you tried updating you profile and prl?
- you didn't flash the wireless n patch over a 1.47 base Rom correct? Can you connect to a WiFi router or is it just the tether app?
elegantai said:
Also, for ****s and giggles, have you tried updating you profile and prl?
Click to expand...
Click to collapse
uh....what?? you got me there! i thought i knew what those were, but it escapes me now.
the only thing i can think of is that the rooting process screwed up somehow. but for it to screw up in the same way for two separate phones is odd, but it's the only thing that has remained constant since the very beginning.
Menu - settings - system updates. The profile and prl won't mess with root or anything but its something I have heard to do in this case. Don't know if it will help.
Also did you see the note about the wifi n patch on the other page? I added it after I posted... like this
elegantai said:
Menu - settings - system updates. The profile and prl won't mess with root or anything but its something I have heard to do in this case. Don't know if it will help.
Also did you see the note about the wifi n patch on the other page? I added it after I posted... like this
Click to expand...
Click to collapse
done. same results. "Unable to start tethering. Please try again!"
Well crapola. I think I'm outta ideas man. if you didn't patch the wireless n over a 1.47 Rom then I have no clue what it could be. maybe Sprint is spying on you and has your phones on lock down! but if you can't find the answer just try starting fresh. it might be a pain but who knows what little quirk could have gotten messed up.
elegantai said:
Well crapola. I think I'm outta ideas man. if you didn't patch the wireless n over a 1.47 Rom then I have no clue what it could be. maybe Sprint is spying on you and has your phones on lock down! but if you can't find the answer just try starting fresh. it might be a pain but who knows what little quirk could have gotten messed up.
Click to expand...
Click to collapse
i do have the wireless N enabled, but i do not have the new 1.47 yet. i'm waiting on OMJ to release an update
Hey Guys,
im not new to rooting i have a nexus one that i rooted perfectly first time around, i am using the OTA simple-root now because my phone version is 1.47.651.1. So step 3 i run the link in my evo browser it doesn't do anything...but one time it did and then step 4 got stuck on "starting part2..." what's going on? i've been trying for hours and hours...please some1 help me i really want to root and get custom roms running.
Thanks guys
Did you refresh the browser page on step 3?
JelloB said:
Did you refresh the browser page on step 3?
Click to expand...
Click to collapse
yea i refreshed it like 10 times but nothing happens...i think its because im using windows 7...should i try on a xp pc?
You can also try unrevoked3, that gets you su permissions then do toasts part 2 then use whiteslacks "how to start over method. Seems the long way around but you can usually avoid the problems simpleroot seems to cause some people.
youngdhillon said:
yea i refreshed it like 10 times but nothing happens...i think its because im using windows 7...should i try on a xp pc?
Click to expand...
Click to collapse
Also when or if i try to run the PC36IMG.zip it says "older version" and it asks to reboot the phone.
youngdhillon said:
yea i refreshed it like 10 times but nothing happens...i think its because im using windows 7...should i try on a xp pc?
Click to expand...
Click to collapse
ifly4vamerica said:
You can also try unrevoked3, that gets you su permissions then do toasts part 2 then use whiteslacks "how to start over method. Seems the long way around but you can usually avoid the problems simpleroot seems to cause some people.
Click to expand...
Click to collapse
can you please give me links to those threads so i don't have to look all over for them? i would appreciate that!!!!
Thanks
Try here... ig you got 147.651.1 will be the bottom . explain step by step , easy and useful
http://forum.ppcgeeks.com/showthread.php?t=123714 (Right now the page is under maintenace) As soon they finish go here and do step by step . Easily
Enjoy it
I have win7 x64 and it worked fine once I refreshed the browser and manually put the files on my SD
Sent from my PC36100 using XDA App
They are easy to find, just run a forum search, use advanced search then forum title only, i dont have the links in front of me i would have to search for them too, you can also try this
http://forum.xda-developers.com/showthread.php?t=701835
This will only work if you have su permissions though. give it a try and let me know how it works. You can also pm me if you like so i can find out exactl where you are in the process.
ok guys good news...i tried the OTA simpleroot on the xp pc and everything went perfectly without any error, my phone is currently updating files in bootloader as we speak, but i have a question how do i user RA recovery instead of clockwork? does it matter or make a difference? or should i just leave clockwork and load a custom rom
personal preference really, i use Ra, just boot to recovery then flash away, either one is good, some say clockwork does not completely wipe ... I havent had any problems with either personally.
I had problems loading DC 3.2.X with clockwork... but ROM manager needs clockwork and is amazing
Sent from my PC36100 using XDA App
ive heard if u connect to wifi during step 3, that will fix your probelm, i had an issue like that too, plus i had one where it said "unable to find device" in part 2
Hey, I'm sorry I'm a noob, but I was wondering, I'm on the Virtuous 3.2 ROM which is pretty much like the stock ROM, minus the bloatware, buy has other features like battery percentage on the notification battery icon and other few tweeks. I got a notification saying that I was verified for the Android 2.3.4 Gingerbread update. Since I'm not on my stock sense ROM, would it be alright to just go ahead and install it or just manually install it?
I am on the skyraider 4.3, which I love. I woke up and saw the same notification, I believe that not update right now or it might brick your Di, can somebody help us? Thanks.
Sent from my ADR6300 using XDA App
I too received the notice to update. I am rooted with s-off bit still on the stock Rom. I don't want to lose root or s-off so I am going to wait a bit.
I think you can accept the OTA update and re-root but not 100% sure.
I want to start flashing roms but I need a bigger SD card first.
Sent from my rooted HTC Incredible using XDA App
I'm pretty sure the s-off part is not going to hurt anything, but if you are rooted and have a different recovery the OTA will not work. My suggestion is, even tho its annoying resist the urge to do the OTA until someone can root it, and make it flashable with CWM.
So i recently broke my original Incredible but got a basically unused one from a friend. It had stock 2.2 on it, so i manually upgraded to 2.3 with the previous gingerbread update verizon released, but then pulled. So i never rooted or S-off'd this phone. This might seem like an obvious answer, but should I, or even can I perform the OTA update?
I think there is someone who already made a flashable version of the OTA update, but its for root users only and it has to be done through CWM
Sent from my ADR6300 using xda premium
I've been on the stock ROM since I got the phone, and I'll probably just flash the OTA Rom once I get some clarification on the process
Is there a way to make the OTA update nag screen go away? I'm on skyraider 4.3, I'd rather just wait for 5.0.
@cpuspeed I'm getting there same problem. Hopefully, some of the ROM developers will update. I actually want a ROM based off the OTA release so I can keep on using my TV out cable lol
Sent from my ADR6300 using xda premium
Here's a link to it, but I'm gonna wait because I wanna do more research on it.
http://www.droid-life.com/2011/05/19/download-android-2-3-3-gingerbread-for-droid-incredible/
Sent from my ADR6300 using xda premium
Is there a way to force the nag/ notification to appear? I've been checking for it all morning
You can force your phone to check for an update by opening the phone screen (like you're going to make a call) and typing the following:
*#*#checkin#*#*
Don't spell out checkin in letters, those are simply the numbers on the keypad that you need to press. You should receive a notification that the checkin succeeded. Now you can go to menu>settings>about phone>system updates and see if it shows up. This doesn't guarantee that it'll immediately find the update, but it does force the phone to check for one.
But is there any way to get rid off the nagging message "there an update ready for the phone, install now or later?"
Sent from my ADR6300 using XDA App
joanchoma said:
But is there any way to get rid off the nagging message "there an update ready for the phone, install now or later?"
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Not that I'm aware of. I'm running Skyraider 4.3 and am encountering the same message. Rather annoying.
what if it says 'checkin failed'? Do I need to be on 3g for the checkin to work?
edit: Ok I switched to 3g and it said 'checkin succeeded', but still shows no update when I go to settings, about, system updates. Guess I'll have to wait.
thank you though.
to get rid of the nag screen delete or rename OTAcets.zip in /system/ect/security, I just renamed to OTAcets.zip.bak.
use root explorer or ghost commander w/busybox to edit root files.
reboot for the nag screen to go away. go to menu>settings>about phone>system updates if you want to update in the future or delete the file in /cache directory if you know you don't ever want to.
give thanks if this was helpful.
silly question I guess, but do I need to be on 3g in order for the update notification to show up? I work from home am connected to wifi 24/7. I rarely put my phone on 3g since it eats battery on 3g. I will keep it on 3g though for next few days if necessary.
veroson said:
silly question I guess, but do I need to be on 3g in order for the update notification to show up? I work from home am connected to wifi 24/7. I rarely put my phone on 3g since it eats battery on 3g. I will keep it on 3g though for next few days if necessary.
Click to expand...
Click to collapse
Nope, I was on WiFi only yesterday and it showed up all by itself in the evening. I'm also on Pagepluscellular, so you don't even have to be directly subscribed with verizon. Also don't have to have stock rom as I'm rooted, s-off and using custom rom (skyraider 4.3).
@cpuspeed, the method didn't work. Is there any way? Also there is another file in the same directory *.bks
Sent from my ADR6300 using XDA App
you do need to reboot after renaming.
an alternative is http://forum.xda-developers.com/showpost.php?p=17372850&postcount=638
Sprint Evo 4g Supersonic will not load my boot screen. Im not sure what is going on I do know that one of my phones is stock and the other is a rooted phone. What the hell is going on. Im not a noob to root FYI. I build gaming rigs and other computer related issues I can solve fairly easy. However, this is getting under my skin because I want to UNROOT so i can activate service on the one phone and then Root it again back to where I had it. The other phone that is Stock RUU sprint is having the same issue. For the love of God I just want to be able to unlock my stock and root! Awaiting a sound answer to my question and I do hope I posted this in the right catagory of the forums because I saw nothing of this issue for Supersonic RUU EVO 4G. Thanks!
So holding power and volume down at startup doesnt bring up the bootloader screen correct?
I know this may sound obvious, but power off the phone, pull out the battery, put it back in, then try again.
Did you make sure that Fastboot was disabled in your phone's Settings? Cuz that will keep it from booting into your bootloader
Sent from my EVO using xda app-developers app
You don't need to unroot to activate a phone.
Thanks for the suggestions I already had it off fastboot and I took the battery out and swapped with another one and it worked fine after. Its been a while since I messed with my phones technically.
Captain_Throwback said:
You don't need to unroot to activate a phone.
Click to expand...
Click to collapse
Captain,
other then the obvious "thanks" Sprint is the one that messed my rooted phones network when changing phone numbers. if I remember correctly its stuck on "Hands Free Activation" continually having the icon circle and "contacting the network" times out and I get code 1012. I can cancel this and use the phone just no service. I went back to a stock rom to do this in order to add a line and switch numbers on both evo 4g supersonics. the rooted failed connection and sprint stock is now my phone. I am going to root this one since it has hboot 2.16 but I have to downgrade windows 8 to 7 ultimate first. NOTHING is compatible with that OS... yet anyways. I will check out your methods as well. I was looking for a forum that would be able to explaine how to activate a rooted phone. Ill get back to you if I have an issue! Thanks
Sent from my PC36100 using xda app-developers app
Capt. Throwback,
If you wouldn't mind please email me specifically how to bring my phone in. Unless OTA ROOT APP works I need to know in order to restore the phone to its line. In forum mail is ok to reach me at. Thanks.
Sent from my PC36100 using xda app-developers app
No Bootloader Screen
DB13 said:
Did you make sure that Fastboot was disabled in your phone's Settings? Cuz that will keep it from booting into your bootloader
Click to expand...
Click to collapse
I have the same problem with being unable to bring up the Bootloader Screen.
So I tried to follow your advice, but I don't see how to disable Fastboot.
I don't know how it was enabled in the first place. I certainly was smart enough to do it.
I went to 'Settings' but see nothing related to Fastboot. Where can it be found?
If this is a common problem, wouldn't it be a good idea to address it in the instructions?
hsfrey said:
I have the same problem with being unable to bring up the Bootloader Screen.
So I tried to follow your advice, but I don't see how to disable Fastboot.
I don't know how it was enabled in the first place. I certainly was smart enough to do it.
I went to 'Settings' but see nothing related to Fastboot. Where can it be found?
If this is a common problem, wouldn't it be a good idea to address it in the instructions?
Click to expand...
Click to collapse
Usually, it is in menu/settings/apps depending on what rom you are on.
I'm on Decks Reloaded and I think it is disabled by default, therefore, no option to enable it.